From 94f33628d8251b614d47b75fd4fd19d1a9965ffa Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Wed, 30 Apr 2003 22:52:23 +0000 Subject: Rebuild docs (This used to be commit 7cafdf9e9576f7988d72fccbc2fad3fbcd3c67df) --- docs/Samba-Developers-Guide.pdf | 13719 +++++++++--- docs/Samba-HOWTO-Collection.pdf | 31244 ++++++++++++++++++++++------ docs/faq/FAQ-ClientApp.html | 52 + docs/faq/FAQ-Config.html | 16 + docs/faq/FAQ-Install.html | 194 + docs/faq/FAQ-Printing.html | 16 + docs/faq/FAQ-errors.html | 99 + docs/faq/FAQ-features.html | 214 + docs/faq/FAQ-general.html | 50 + docs/faq/faq-clientapp.html | 281 - docs/faq/faq-config.html | 182 - docs/faq/faq-errors.html | 373 - docs/faq/faq-features.html | 601 - docs/faq/faq-general.html | 484 - docs/faq/faq-install.html | 582 - docs/faq/faq-printing.html | 181 - docs/faq/samba-faq.html | 377 +- docs/htmldocs/Samba-Developers-Guide.html | 10356 ++------- docs/htmldocs/Samba-HOWTO-Collection.html | 27326 +++++++----------------- docs/htmldocs/bugreport.html | 476 +- docs/htmldocs/compiling.html | 1067 +- docs/htmldocs/diagnosis.html | 1115 +- docs/htmldocs/domain-member.html | 461 +- docs/htmldocs/editreg.1.html | 146 +- docs/htmldocs/findsmb.1.html | 314 +- docs/htmldocs/groupmapping.html | 277 +- docs/htmldocs/install.html | 656 +- docs/htmldocs/integrate-ms-networks.html | 862 +- docs/htmldocs/introduction.html | 156 +- docs/htmldocs/lmhosts.5.html | 215 +- docs/htmldocs/msdfs.html | 307 +- docs/htmldocs/net.8.html | 1654 +- docs/htmldocs/nmbd.8.html | 743 +- docs/htmldocs/nmblookup.1.html | 503 +- docs/htmldocs/ntlm_auth.1.html | 268 +- docs/htmldocs/optional.html | 157 +- docs/htmldocs/pam.html | 656 +- docs/htmldocs/passdb.html | 1838 +- docs/htmldocs/pdbedit.8.html | 641 +- docs/htmldocs/printing.html | 1653 +- docs/htmldocs/problems.html | 602 +- docs/htmldocs/profiles.1.html | 143 +- docs/htmldocs/rpcclient.1.html | 1202 +- docs/htmldocs/samba-bdc.html | 464 +- docs/htmldocs/samba-pdc.html | 1616 +- docs/htmldocs/samba.7.html | 762 +- docs/htmldocs/securing-samba.html | 413 +- docs/htmldocs/securitylevels.html | 613 +- docs/htmldocs/smb.conf.5.html | 21379 +++---------------- docs/htmldocs/smbcacls.1.html | 523 +- docs/htmldocs/smbclient.1.html | 1631 +- docs/htmldocs/smbcontrol.1.html | 489 +- docs/htmldocs/smbcquotas.1.html | 419 +- docs/htmldocs/smbd.8.html | 780 +- docs/htmldocs/smbmnt.8.html | 200 +- docs/htmldocs/smbmount.8.html | 482 +- docs/htmldocs/smbpasswd.5.html | 339 +- docs/htmldocs/smbpasswd.8.html | 671 +- docs/htmldocs/smbsh.1.html | 505 +- docs/htmldocs/smbspool.8.html | 229 +- docs/htmldocs/smbstatus.1.html | 292 +- docs/htmldocs/smbtar.1.html | 368 +- docs/htmldocs/smbtree.1.html | 314 +- docs/htmldocs/smbumount.8.html | 142 +- docs/htmldocs/speed.html | 549 +- docs/htmldocs/swat.8.html | 541 +- docs/htmldocs/testparm.1.html | 353 +- docs/htmldocs/testprns.1.html | 262 +- docs/htmldocs/type.html | 167 +- docs/htmldocs/unicode.html | 396 +- docs/htmldocs/unix-permissions.html | 941 +- docs/htmldocs/vfstest.1.html | 540 +- docs/htmldocs/wbinfo.1.html | 459 +- docs/htmldocs/winbind.html | 2087 +- docs/htmldocs/winbindd.8.html | 982 +- docs/manpages/editreg.1 | 82 +- docs/manpages/findsmb.1 | 148 +- docs/manpages/lmhosts.5 | 126 +- docs/manpages/net.8 | 672 +- docs/manpages/nmbd.8 | 347 +- docs/manpages/nmblookup.1 | 335 +- docs/manpages/ntlm_auth.1 | 168 +- docs/manpages/pdbedit.8 | 358 +- docs/manpages/profiles.1 | 82 +- docs/manpages/rpcclient.1 | 789 +- docs/manpages/smb.conf.5 | 10669 +++++----- docs/manpages/smbcacls.1 | 372 +- docs/manpages/smbclient.1 | 1317 +- docs/manpages/smbcontrol.1 | 311 +- docs/manpages/smbcquotas.1 | 310 +- docs/manpages/smbd.8 | 426 +- docs/manpages/smbmnt.8 | 115 +- docs/manpages/smbmount.8 | 364 +- docs/manpages/smbpasswd.5 | 220 +- docs/manpages/smbpasswd.8 | 419 +- docs/manpages/smbsh.1 | 255 +- docs/manpages/smbspool.8 | 145 +- docs/manpages/smbstatus.1 | 187 +- docs/manpages/smbtar.1 | 196 +- docs/manpages/smbtree.1 | 221 +- docs/manpages/smbumount.8 | 70 +- docs/manpages/swat.8 | 268 +- docs/manpages/testparm.1 | 173 +- docs/manpages/testprns.1 | 134 +- docs/manpages/vfstest.1 | 286 +- docs/manpages/wbinfo.1 | 286 +- docs/manpages/winbindd.8 | 511 +- 107 files changed, 62431 insertions(+), 100298 deletions(-) create mode 100644 docs/faq/FAQ-ClientApp.html create mode 100644 docs/faq/FAQ-Config.html create mode 100644 docs/faq/FAQ-Install.html create mode 100644 docs/faq/FAQ-Printing.html create mode 100644 docs/faq/FAQ-errors.html create mode 100644 docs/faq/FAQ-features.html create mode 100644 docs/faq/FAQ-general.html delete mode 100644 docs/faq/faq-clientapp.html delete mode 100644 docs/faq/faq-config.html delete mode 100644 docs/faq/faq-errors.html delete mode 100644 docs/faq/faq-features.html delete mode 100644 docs/faq/faq-general.html delete mode 100644 docs/faq/faq-install.html delete mode 100644 docs/faq/faq-printing.html diff --git a/docs/Samba-Developers-Guide.pdf b/docs/Samba-Developers-Guide.pdf index ad043bf0ff..9dcb2a1825 100644 --- a/docs/Samba-Developers-Guide.pdf +++ b/docs/Samba-Developers-Guide.pdf @@ -1,2734 +1,10999 @@ -%PDF-1.3 -% -1 0 obj<>endobj -2 0 obj<>endobj -3 0 obj<>endobj -4 0 obj<>endobj -5 0 obj<>endobj -6 0 obj<>endobj -7 0 obj<>endobj -8 0 obj<>endobj -9 0 obj<>endobj -10 0 obj<>endobj -11 0 obj<>endobj -12 0 obj<>endobj -13 0 obj<>endobj -14 0 obj<>endobj -15 0 obj<>endobj -16 0 obj<>endobj -17 0 obj<>endobj -18 0 obj<>endobj -19 0 obj<>endobj -20 0 obj<>endobj -21 0 obj<>endobj -22 0 obj<>endobj -23 0 obj<>endobj -24 0 obj<>endobj -25 0 obj<>endobj -26 0 obj<>endobj -27 0 obj<>endobj -28 0 obj<>endobj -29 0 obj<>endobj -30 0 obj<>endobj -31 0 obj<>endobj -32 0 obj<>endobj -33 0 obj<>endobj -34 0 obj<>endobj -35 0 obj<>endobj -36 0 obj<>endobj -37 0 obj<>endobj -38 0 obj<>endobj -39 0 obj<>endobj -40 0 obj<>endobj -41 0 obj<>endobj -42 0 obj<>endobj -43 0 obj<>endobj -44 0 obj<>endobj -45 0 obj<>endobj -46 0 obj<>endobj -47 0 obj<>endobj -48 0 obj<>endobj -49 0 obj<>endobj -50 0 obj<>endobj -51 0 obj<>endobj -52 0 obj<>endobj -53 0 obj<>endobj -54 0 obj<>endobj -55 0 obj[13 0 R -14 0 R -15 0 R -16 0 R -17 0 R -18 0 R -19 0 R -20 0 R -21 0 R -22 0 R -23 0 R -24 0 R -25 0 R -26 0 R -27 0 R -28 0 R -29 0 R -30 0 R -31 0 R -32 0 R -33 0 R -34 0 R -35 0 R -36 0 R -37 0 R -38 0 R -39 0 R -40 0 R -41 0 R -42 0 R -43 0 R -44 0 R -45 0 R -46 0 R -47 0 R -48 0 R -49 0 R -50 0 R -51 0 R -52 0 R -53 0 R -54 0 R]endobj -56 0 obj<>endobj -57 0 obj<>endobj -58 0 obj<>endobj -59 0 obj<>endobj -60 0 obj<>endobj -61 0 obj<>endobj -62 0 obj<>endobj -63 0 obj<>endobj -64 0 obj<>endobj -65 0 obj<>endobj -66 0 obj<>endobj -67 0 obj<>endobj -68 0 obj<>endobj -69 0 obj<>endobj -70 0 obj<>endobj -71 0 obj<>endobj -72 0 obj<>endobj -73 0 obj<>endobj -74 0 obj<>endobj -75 0 obj<>endobj -76 0 obj<>endobj -77 0 obj<>endobj -78 0 obj<>endobj -79 0 obj<>endobj -80 0 obj<>endobj -81 0 obj<>endobj -82 0 obj<>endobj -83 0 obj<>endobj -84 0 obj<>endobj -85 0 obj<>endobj -86 0 obj<>endobj -87 0 obj<>endobj -88 0 obj<>endobj -89 0 obj<>endobj -90 0 obj<>endobj -91 0 obj<>endobj -92 0 obj<>endobj -93 0 obj<>endobj -94 0 obj<>endobj -95 0 obj<>endobj -96 0 obj<>endobj -97 0 obj<>endobj -98 0 obj<>endobj -99 0 obj<>endobj -100 0 obj[56 0 R -57 0 R -58 0 R -59 0 R -60 0 R -61 0 R -62 0 R -63 0 R -64 0 R -65 0 R -66 0 R -67 0 R -68 0 R -69 0 R -70 0 R -71 0 R -72 0 R -73 0 R -74 0 R -75 0 R -76 0 R -77 0 R -78 0 R -79 0 R -80 0 R -81 0 R -82 0 R -83 0 R -84 0 R -85 0 R -86 0 R -87 0 R -88 0 R -89 0 R -90 0 R -91 0 R -92 0 R -93 0 R -94 0 R -95 0 R -96 0 R -97 0 R -98 0 R -99 0 R]endobj -101 0 obj<>endobj -102 0 obj<>endobj -103 0 obj<>endobj -104 0 obj<>endobj -105 0 obj<>endobj -106 0 obj<>endobj -107 0 obj<>endobj -108 0 obj<>endobj -109 0 obj<>endobj -110 0 obj<>endobj -111 0 obj<>endobj -112 0 obj<>endobj -113 0 obj<>endobj -114 0 obj<>endobj -115 0 obj<>endobj -116 0 obj<>endobj -117 0 obj<>endobj -118 0 obj<>endobj -119 0 obj<>endobj -120 0 obj<>endobj -121 0 obj<>endobj -122 0 obj<>endobj -123 0 obj<>endobj -124 0 obj<>endobj -125 0 obj<>endobj -126 0 obj<>endobj -127 0 obj<>endobj -128 0 obj<>endobj -129 0 obj<>endobj -130 0 obj<>endobj -131 0 obj<>endobj -132 0 obj<>endobj -133 0 obj<>endobj -134 0 obj<>endobj -135 0 obj<>endobj -136 0 obj<>endobj -137 0 obj<>endobj -138 0 obj<>endobj -139 0 obj<>endobj -140 0 obj<>endobj -141 0 obj<>endobj -142 0 obj<>endobj -143 0 obj<>endobj -144 0 obj<>endobj -145 0 obj[101 0 R -102 0 R -103 0 R -104 0 R -105 0 R -106 0 R -107 0 R -108 0 R -109 0 R -110 0 R -111 0 R -112 0 R -113 0 R -114 0 R -115 0 R -116 0 R -117 0 R -118 0 R -119 0 R -120 0 R -121 0 R -122 0 R -123 0 R -124 0 R -125 0 R -126 0 R -127 0 R -128 0 R -129 0 R -130 0 R -131 0 R -132 0 R -133 0 R -134 0 R -135 0 R -136 0 R -137 0 R -138 0 R -139 0 R -140 0 R -141 0 R -142 0 R -143 0 R -144 0 R]endobj -146 0 obj<>endobj -147 0 obj<>endobj -148 0 obj<>endobj -149 0 obj<>endobj -150 0 obj<>endobj -151 0 obj<>endobj -152 0 obj<>endobj -153 0 obj<>endobj -154 0 obj<>endobj -155 0 obj<>endobj -156 0 obj<>endobj -157 0 obj<>endobj -158 0 obj<>endobj -159 0 obj<>endobj -160 0 obj<>endobj -161 0 obj[146 0 R -147 0 R -148 0 R -149 0 R -150 0 R -151 0 R -152 0 R -153 0 R -154 0 R -155 0 R -156 0 R -157 0 R -158 0 R -159 0 R -160 0 R]endobj -162 0 obj<>endobj -163 0 obj<>endobj -164 0 obj<>endobj -165 0 obj<>endobj -166 0 obj<>endobj -167 0 obj<>endobj -168 0 obj<>endobj -169 0 obj<>endobj -170 0 obj<>endobj -171 0 obj<>endobj -172 0 obj<>endobj -173 0 obj<>endobj -174 0 obj<>endobj -175 0 obj<>endobj -176 0 obj<>endobj -177 0 obj<>endobj -178 0 obj<>endobj -179 0 obj<>endobj -180 0 obj<>endobj -181 0 obj<>endobj -182 0 obj<>endobj -183 0 obj<>endobj -184 0 obj<>endobj -185 0 obj<>endobj -186 0 obj<>endobj -187 0 obj<>endobj -188 0 obj<>endobj -189 0 obj<>endobj -190 0 obj<>endobj -191 0 obj<>endobj -192 0 obj<>endobj -193 0 obj<>endobj -194 0 obj<>endobj -195 0 obj<>endobj -196 0 obj<>endobj -197 0 obj<>endobj -198 0 obj<>endobj -199 0 obj<>endobj -200 0 obj<>endobj -201 0 obj<>endobj -202 0 obj<>endobj -203 0 obj<>endobj -204 0 obj[163 0 R -165 0 R -167 0 R -168 0 R -169 0 R -170 0 R -171 0 R -172 0 R -173 0 R -174 0 R -175 0 R -176 0 R -177 0 R -178 0 R -179 0 R -180 0 R -181 0 R -182 0 R -183 0 R -184 0 R -185 0 R -186 0 R -187 0 R -188 0 R -189 0 R -190 0 R -191 0 R -192 0 R -193 0 R -194 0 R -195 0 R -196 0 R -197 0 R -198 0 R -199 0 R -200 0 R -201 0 R -202 0 R -203 0 R]endobj -205 0 obj<>endobj -206 0 obj<>endobj -207 0 obj<>endobj -208 0 obj<>endobj -209 0 obj<>endobj -210 0 obj<>endobj -211 0 obj<>endobj -212 0 obj<>endobj -213 0 obj<>endobj -214 0 obj<>endobj -215 0 obj<>endobj -216 0 obj<>endobj -217 0 obj<>endobj -218 0 obj<>endobj -219 0 obj<>endobj -220 0 obj<>endobj -221 0 obj<>endobj -222 0 obj<>endobj -223 0 obj<>endobj -224 0 obj<>endobj -225 0 obj<>endobj -226 0 obj<>endobj -227 0 obj<>endobj -228 0 obj<>endobj -229 0 obj<>endobj -230 0 obj<>endobj -231 0 obj<>endobj -232 0 obj<>endobj -233 0 obj<>endobj -234 0 obj<>endobj -235 0 obj<>endobj -236 0 obj<>endobj -237 0 obj<>endobj -238 0 obj<>endobj -239 0 obj<>endobj -240 0 obj<>endobj -241 0 obj<>endobj -242 0 obj<>endobj -243 0 obj<>endobj -244 0 obj<>endobj -245 0 obj<>endobj -246 0 obj<>endobj -247 0 obj<>endobj -248 0 obj<>endobj -249 0 obj<>endobj -250 0 obj<>endobj -251 0 obj<>endobj -252 0 obj<>endobj -253 0 obj<>endobj -254 0 obj<>endobj -255 0 obj<>endobj -256 0 obj[205 0 R -206 0 R -207 0 R -208 0 R -209 0 R -210 0 R -211 0 R -212 0 R -213 0 R -214 0 R -215 0 R -216 0 R -217 0 R -218 0 R -219 0 R -220 0 R -221 0 R -222 0 R -223 0 R -224 0 R -225 0 R -226 0 R -227 0 R -228 0 R -229 0 R -230 0 R -231 0 R -232 0 R -233 0 R -234 0 R -235 0 R -236 0 R -237 0 R -238 0 R -239 0 R -240 0 R -241 0 R -242 0 R -243 0 R -244 0 R -245 0 R -246 0 R -247 0 R -248 0 R -249 0 R -250 0 R -251 0 R -252 0 R -253 0 R -254 0 R -255 0 R]endobj -257 0 obj<>endobj -258 0 obj<>endobj -259 0 obj<>endobj -260 0 obj<>endobj -261 0 obj<>endobj -262 0 obj<>endobj -263 0 obj<>endobj -264 0 obj<>endobj -265 0 obj<>endobj -266 0 obj<>endobj -267 0 obj<>endobj -268 0 obj<>endobj -269 0 obj<>endobj -270 0 obj<>endobj -271 0 obj<>endobj -272 0 obj<>endobj -273 0 obj<>endobj -274 0 obj<>endobj -275 0 obj<>endobj -276 0 obj<>endobj -277 0 obj<>endobj -278 0 obj<>endobj -279 0 obj<>endobj -280 0 obj<>endobj -281 0 obj<>endobj -282 0 obj<>endobj -283 0 obj<>endobj -284 0 obj<>endobj -285 0 obj<>endobj -286 0 obj<>endobj -287 0 obj<>endobj -288 0 obj<>endobj -289 0 obj<>endobj -290 0 obj<>endobj -291 0 obj<>endobj -292 0 obj<>endobj -293 0 obj<>endobj -294 0 obj<>endobj -295 0 obj<>endobj -296 0 obj<>endobj -297 0 obj<>endobj -298 0 obj<>endobj -299 0 obj<>endobj -300 0 obj<>endobj -301 0 obj<>endobj -302 0 obj<>endobj -303 0 obj<>endobj -304 0 obj<>endobj -305 0 obj<>endobj -306 0 obj<>endobj -307 0 obj<>endobj -308 0 obj[257 0 R -258 0 R -259 0 R -260 0 R -261 0 R -262 0 R -263 0 R -264 0 R -265 0 R -266 0 R -267 0 R -268 0 R -269 0 R -270 0 R -271 0 R -272 0 R -273 0 R -274 0 R -275 0 R -276 0 R -277 0 R -278 0 R -279 0 R -280 0 R -281 0 R -282 0 R -283 0 R -284 0 R -285 0 R -286 0 R -287 0 R -288 0 R -289 0 R -290 0 R -291 0 R -292 0 R -293 0 R -294 0 R -295 0 R -296 0 R -297 0 R -298 0 R -299 0 R -300 0 R -301 0 R -302 0 R -303 0 R -304 0 R -305 0 R -306 0 R -307 0 R]endobj -309 0 obj<>endobj -310 0 obj[309 0 R]endobj -311 0 obj<>endobj -312 0 obj<>endobj -313 0 obj<>endobj -314 0 obj<>endobj -315 0 obj[312 0 R -314 0 R]endobj -316 0 obj<>endobj -317 0 obj<>endobj -318 0 obj<>endobj -319 0 obj<>endobj -320 0 obj<>endobj -321 0 obj<>endobj -322 0 obj<>endobj -323 0 obj<>endobj -324 0 obj<>endobj -325 0 obj<>endobj -326 0 obj<>endobj -327 0 obj<>endobj -328 0 obj[317 0 R -319 0 R -321 0 R -323 0 R -325 0 R -327 0 R]endobj -329 0 obj<>endobj -330 0 obj<>endobj -331 0 obj<>endobj -332 0 obj<>endobj -333 0 obj<>endobj -334 0 obj<>endobj -335 0 obj<>endobj -336 0 obj<>endobj -337 0 obj<>endobj -338 0 obj<>endobj -339 0 obj<>endobj -340 0 obj<>endobj -341 0 obj<>endobj -342 0 obj<>endobj -343 0 obj<>endobj -344 0 obj<>endobj -345 0 obj<>endobj -346 0 obj<>endobj -347 0 obj<>endobj -348 0 obj<>endobj -349 0 obj<>endobj -350 0 obj<>endobj -351 0 obj<>endobj -352 0 obj<>endobj -353 0 obj<>endobj -354 0 obj<>endobj -355 0 obj<>endobj -356 0 obj<>endobj -357 0 obj<>endobj -358 0 obj<>endobj -359 0 obj<>endobj -360 0 obj<>endobj -361 0 obj<>endobj -362 0 obj<>endobj -363 0 obj<>endobj -364 0 obj<>endobj -365 0 obj<>endobj -366 0 obj<>endobj -367 0 obj<>endobj -368 0 obj<>endobj -369 0 obj<>endobj -370 0 obj<>endobj -371 0 obj<>endobj -372 0 obj<>endobj -373 0 obj<>endobj -374 0 obj<>endobj -375 0 obj<>endobj -376 0 obj<>endobj -377 0 obj<>endobj -378 0 obj<>endobj -379 0 obj<>endobj -380 0 obj<>endobj -381 0 obj<>endobj -382 0 obj<>endobj -383 0 obj<>endobj -384 0 obj<>endobj -385 0 obj<>endobj -386 0 obj<>endobj -387 0 obj<>endobj -388 0 obj<>endobj -389 0 obj<>endobj -390 0 obj<>endobj -391 0 obj<>endobj -392 0 obj<>endobj -393 0 obj<>endobj -394 0 obj<>endobj -395 0 obj<>endobj -396 0 obj<>endobj -397 0 obj<>endobj -398 0 obj<>endobj -399 0 obj<>endobj -400 0 obj<>endobj -401 0 obj<>endobj -402 0 obj<>endobj -403 0 obj<>endobj -404 0 obj<>endobj -405 0 obj<>endobj -406 0 obj<>endobj -407 0 obj<>endobj -408 0 obj<>endobj -409 0 obj<>endobj -410 0 obj<>endobj -411 0 obj<>endobj -412 0 obj<>endobj -413 0 obj<>endobj -414 0 obj<>endobj -415 0 obj<>endobj -416 0 obj<>endobj -417 0 obj<>endobj -418 0 obj<>endobj -419 0 obj<>endobj -420 0 obj<>endobj -421 0 obj<>endobj -422 0 obj<>endobj -423 0 obj<>endobj -424 0 obj<>endobj -425 0 obj<>endobj -426 0 obj<>endobj -427 0 obj<>endobj -428 0 obj<>endobj -429 0 obj<>endobj -430 0 obj<>endobj -431 0 obj<>endobj -432 0 obj<>endobj -433 0 obj<>endobj -434 0 obj<>endobj -435 0 obj<>endobj -436 0 obj<>endobj -437 0 obj<>endobj -438 0 obj<>endobj -439 0 obj<>endobj -440 0 obj<>endobj -441 0 obj<>endobj -442 0 obj<>endobj -443 0 obj<>endobj -444 0 obj<>endobj -445 0 obj<>endobj -446 0 obj<>endobj -447 0 obj<>endobj -448 0 obj<>endobj -449 0 obj<>endobj -450 0 obj<>endobj -451 0 obj<>endobj -452 0 obj<>endobj -453 0 obj<>endobj -454 0 obj<>endobj -455 0 obj<>endobj -456 0 obj<>endobj -457 0 obj<>endobj -458 0 obj<>endobj -459 0 obj<>endobj -460 0 obj<>endobj -461 0 obj<>endobj -462 0 obj<>endobj -463 0 obj<>endobj -464 0 obj<>endobj -465 0 obj<>endobj -466 0 obj<>endobj -467 0 obj<>endobj -468 0 obj<>endobj -469 0 obj<>endobj -470 0 obj<>endobj -471 0 obj<>endobj -472 0 obj<>endobj -473 0 obj<>endobj -474 0 obj<>endobj -475 0 obj<>endobj -476 0 obj<>endobj -477 0 obj<>endobj -478 0 obj<>endobj -479 0 obj<>endobj -480 0 obj<>endobj -481 0 obj<>endobj -482 0 obj<>endobj -483 0 obj<>endobj -484 0 obj<>endobj -485 0 obj<>endobj -486 0 obj<>endobj -487 0 obj<>endobj -488 0 obj<>endobj -489 0 obj<>endobj -490 0 obj<>endobj -491 0 obj<>endobj -492 0 obj<>endobj -493 0 obj<>endobj -494 0 obj<>endobj -495 0 obj<>endobj -496 0 obj<>endobj -497 0 obj<>endobj -498 0 obj<>endobj -499 0 obj<>endobj -500 0 obj<>endobj -501 0 obj<>endobj -502 0 obj<>endobj -503 0 obj<>endobj -504 0 obj<>endobj -505 0 obj<>endobj -506 0 obj<>endobj -507 0 obj<>endobj -508 0 obj<>endobj -509 0 obj<>endobj -510 0 obj<>endobj -511 0 obj<>endobj -512 0 obj<>endobj -513 0 obj<>endobj -514 0 obj<>endobj -515 0 obj<>endobj -516 0 obj<>endobj -517 0 obj<>endobj -518 0 obj<>endobj -519 0 obj<>endobj -520 0 obj<>endobj -521 0 obj<>endobj -522 0 obj<>endobj -523 0 obj<>endobj -524 0 obj<>endobj -525 0 obj<>endobj -526 0 obj<>endobj -527 0 obj<>endobj -528 0 obj<>endobj -529 0 obj<>endobj -530 0 obj<>endobj -531 0 obj<>endobj -532 0 obj<>endobj -533 0 obj<>endobj -534 0 obj<>endobj -535 0 obj<>endobj -536 0 obj<>endobj -537 0 obj<>endobj -538 0 obj<>endobj -539 0 obj<>endobj -540 0 obj<>endobj -541 0 obj<>endobj -542 0 obj<>endobj -543 0 obj<>endobj -544 0 obj<>endobj -545 0 obj<>endobj -546 0 obj<>endobj -547 0 obj<>endobj -548 0 obj<>endobj -549 0 obj<>endobj -550 0 obj<>endobj -551 0 obj<>endobj -552 0 obj<>endobj -553 0 obj<>endobj -554 0 obj<>/XObject<<>>>>>>endobj -555 0 obj<>stream -x+2T0BCs#c3\..}7K#4CCK=ccS=3=DFKjYjN~AjQ{ifJfHkW S?endstream -endobj -556 0 obj<>/XObject<<>>>>/Annots 55 0 R>>endobj -557 0 obj<>stream -x[moG_S~K $=KO -Z:XRNzͿCrf]%HyHYΐəUs ɓNn7gY;&oK+pnWigȢA*m1hS@f9 D2Y6I PU[=]"&2LÐUJZ ja o%~XRZ#yYNb. &#"L~Pn^$cwSqb$6ٶ0*Djo_n،:m5d$Kv~t/ojmT/L`9;+Xh߳)h.!a׸h3yty2\.UZ=26rmXn8QQK@ik0Ƈݪ͂֩(mQ*HQO1]}S>w>YD{l 6ؑןί. r*]EZL_7# !kP&0Gmgfd -pIM:_nn4n\|>73V;ce0|=wm/+93ZQolŇa}xz{{LGⓠCGRr6sXG=MȲc4]OI8TFp86m_MĦjlf#ˁC,W~/cM.@nnrAzfb5x%M_tR{.yt_EA2%B3x?%H+zOa=gyFS35&$TjPh~}& }Xwvt1s]¯$TSί:MmQQMj2k`W7l闟mԂZ۲aQ4nX -{{rç Im1AOMVIR1&C!fL̂I##V`]#`2͖5n,ovMݢҸx{B܅w]'yuӛ+y۠>G;5tv(9׳/!0J4Lx4"V {%* 'O?He7\7fc{,tMw43a=E6]I%j\a9pK5 -Z{/~_^uՔ e ]rxݓt , C= -{ -RpQ^Y[Q܏P_xzn@Xߟ*/ބQc&WO4+ϡxi2C+Q4'O; ?I i'9ϣhQkn?(pSq`C]ӫ. ]F;!ݎ@a'IQQ8)VA?`jճv\c_+?aʣ^ -kOV}pסϫmo&!~ ˲b$$E!;YugDendstream -endobj -558 0 obj<>/XObject<<>>>>/Annots 100 0 R>>endobj -559 0 obj<>stream -x[r9}Wffg.r'RjeYh#d&I[xv"y*HE?KjU2__?>J$UũU20pi3p49IƐyE%Ġn\z@Nz@ ڐ8e [eA -97Pݐ H! IL[,#}"i1 ې* -KH@\A2Q@ i1آ(@Yv@q : - Ŵ9fVV!%]5 M9iZZH"Wg -\BW%E5,T2)6cdzOIʤAygմQVT—E%4Pʰ k0ض hRq9 ,Tl2K"-:%ŦRU^@pW=ȵ%R@̗=b-XW֎-1l]* [<&4TjI%%IYk\JʌfdC-"rBGPId9 ",(U9Cuj+FcH/Fy@v q4hAF;gz $M)ؕAQrq tPϵT35 iW˱@c -o# \'Xn QbX0?Z r5ĬkX9 \'U]3JZ Hʲ;b+C bCR~t -8QYYK*,I0*,Ƹcza#g LY hm +M$%B؝9*蹬8PRSS\)7qmH9SU,k-k0؆BLte y\++ ,`VbrXa+S3:$A$00EC@ȉZdQ挜!vX(j1Ѥ mfO`8FVF[0Shۑ&.ðEv,k0*+*ai,0е_HZI]C -+k0)L6eyR}8gdH2QN!FQ9j"NJBQ̑2&s0M94D9եȱ"($1sT32s d)$%xOӐA)6?hW)xLS) -FJRK8Dy9 Qs32z "%WfwRIh!6r$qoP2UR+3Q9ơ{ O,Sa5G*ĘwsyKrỷwQV(F}l5l0B+ߍO_#ʅ،ő{7 /ڷTdބ_zrG|X G`OKs2Y{q[(~;%-C iS^3KI+m8bSWָIiS@ݭnfʹ6ti_\.EINhZ|"9:i#D -[hh8i8} e286͒M]UmWB8:m_\!+EkeS-jv=1oյ{F88}wԠ&Ж$co$n=LU~\aN'D&{z}RsMb@D<YxՄ'>J!}k -z\}iHp'Oy󽿃S2O4oLZ?]Cs̛ԊKa`NJaW 8>Lv =3&y,}]<,B R퍨M0n;\\pM!';édߢq?l}ߋby@ <1Ǥ\\L8Q[oaoIh徢ƨE v?~{ka$Z*UNkU/ -fn5 -N-r\nȗkx)F=ɒᚩjqH<:ONjk{W۶9?{Q)`Fxf6Z5Fs:[r/77{-DV+j6oZ#3~K_iXCp$Or~G:%txo77@9[No&-x_iN6 -ߕT)g~k|O[2wp׭sZ= -)@o9[^ÎϿ7:gxѷ{zoz!!/g 75?6Ծcopw%sNY@6j'5oH׌#&o__&o_ɯ |(R:mť咜)endstream -endobj -560 0 obj<>/XObject<<>>>>/Annots 145 0 R>>endobj -561 0 obj<>stream -x[r}W웝{%E -ElUJ,Vs2= )\%`f6==>˒eI'EIo7/雤.;Nn)X%g*qq,m'ce:[$NQMZSJ fɿ$cEFFaxbI6=w\$pOjܴ[ MIHЕau6eє$ 2*13rMd&#E]T-8Y$cڢ4c XvDcEekW HʩFziz Nʢ0, ..bǶhdE0aXUUsF@:H&jGR|VeCE@V $ci: d+&*R* eiE5cL [NJ-Z3i\']K Mʲ1ئ GaƊiBAS98D &+ZHb e|# 9iIJTl`9ac)eC -j`N \K"=ƴ8l$lEʱHqfQeS8cޏط&.D*GGLDRB.:H9- @To#e`A> d*F g@y;g*okNh$E,d%U1AdyL. LIiZsd)ʕAXB [G. =]w38R=Zqσ?Wضm؋ûaCߢضiݐXut -q9#ljjYLϫ~xAĚr\"5=fŸnۏjh\4+\ |0pV';G'V]GN}r۠XlSvVyejVŅ/_h/Uٓ?yóԼj%"qQ=QA~+Vܮ9& FO^H~ 6z+wb^=^cjʞ,Umf?bOwûm~Ʌ$us7Kqg:)PGG)Q抜5N$Ws<Otq,wrDk3Vz(v aE-TSA4T[7 uOZ=H#-4=;a;9j=Z3jOɻjuf1hdi@/SާRQM&єC+ m\Iߐ@$@O$no{2ܪ_oenA !Mh{f'Ps-|pBMp?~{jאD#lB2h-4܇-W\:pX84l_reptv*Dbs) @g!Í3@ X,.?aʁ䴗M]x6=27xQ;{/)<3|=ֺ+qn+gov F09Dc47b .=BɔLr'')y 2:؆lK4*t`oK胋#xshOy6A2oRR`MdN7(Z#5{!aͰ1* cVl%{ؑ2=WD.=S^×*?ޕ9(aE4^B(ߏƍHXn6[݄} +ײ__N8TX G^̗[FNN=s˷DB.V}I& -?N3>^-փ<'mow /.dy=y6 -/[5;HiYGURN߼7U0u= 7{޲E =xӣx nVhߌa_"@"M/~ƚaD#\cZ[A*t_^ZEn{MWžK uD t!x;X]%7M~bz~.Xky[}(VԎbI;zkk\R/f~z?1yendstream -endobj -562 0 obj<>/XObject<<>>>>/Annots 161 0 R>>endobj -563 0 obj<>stream -xXMs6WD$A8NK=-+HWKdx V9je UjYjs&lL2&'N5MV -NҺɜ %[CV`TQ̊˚dH;*$N@!#H*k˛c8 9R9Va:+&DuDzCWr$Ya X7qz\B~+~ q-HoHi[iiM7!U.`\Ɛ H.8$]˜\f鮁ӕDRblXIb,pV`d:v&/9(\Ѝ 58N +I\@j`mrO,{jr&{݃svv1k Ue $\Sڙ5ǾH87aTt|i' ݥFwH^ wI $0pՏ#" :w2d N[*r*rGquJ-V<[wN rǮ~Y|A< 2;|hnO~du hM7ʧn{ZDYټ m"*W E.t>=}fE}[=1lp>_`vwtd)I-0.lMw>zQF_H\m5!T'GZƘ9)Ec%ň^^~l^f -r@kjG+%ࡈOCkT)-4ɥENьvl͒ ܅╒ :aYeA ^;)$^CC.M:cB' F9j7iL  {vm(wGVi1B5m4,2pfMO'h1;CY?̓xaEW/0{ g_n.LVFu7;1Eש '*.{]VuhkwHVͼ=X~eUwvJz){/ _*SO)F!HgG}P=͂q (&Nv޿P0 T}oL2Mu.F_}x;u N/fnï8\I%]ntOqo/8Mo/]K uYq,lЫyB>]endstream -endobj -564 0 obj<>/XObject<<>>>>>>endobj -565 0 obj<>stream -x}0 E|a iH؊Ā6"~\ډY,#? CPu,!d+c1pdoPYpiM5;&vOW[\WǫEjz%`>`؊9Ұ7~endstream -endobj -566 0 obj<>/XObject<<>>>>/Annots 204 0 R>>endobj -567 0 obj<>stream -xWnF}W[ERO%q ؎k)y -PJbJrUri3Ҥ0`̜ħ~|J -cZ'#oO_Ϸ'qERI~{I -IMz6oС(|/{^@%Ew)` s 4G)HsDO:$A1d`] 6q&[*\<-NX)g#qEM|.8Ӂp X!90A%G]@r zƃXEPK~೪ p:lD Ј]-ask]ӱ\k*qݱAa{ֺbֹG8΄B@CqP#u kȜeD\J$8HpH# -Z'L,? Dv\e{`q!۳V9F[EG q<#yO2#keGDvَC']̲#gE6J,7 1߱CNbŜCk{ZkL S@"tkbg+YYxݽ8q bBw @["=gxK,ĎQXѳ&\s =L.}p%RD[\S$n: `pU-b]K!$t $Ҡ//h n d`7gb4#!YA=9V01 詴[i#nS?#P>Ý&Jk2ak !"Ոf+\IJS1u0f`cX3<C(k3lNtES5Q^E͌%`Cgk7oF ]jar--Ue2P7FڂVBRBojMMV3e6QWFժ1jr |A{tg~kfVIBunh2P5ʘ@ ^eEjbduۆYP;9}mFGX% !JmDZJ ]\׍1ۋs4<]=z*T6 -v5NB7U~t09#[> V|@n?ѭT΋|A9A/O_U]b@o-TWqC(h󚛍m Ezae^{MYW -9ҵ[5+iS9_o |L\^<ܯ5fS{k7G7jW"<*suqJODcV*zV.Z{K%p6HAjtF]#WS?s#@d*ݽ;ҸL\os=Σ08ZeK\Hxi֛5|yd1v-YDUrN7Z6^Y/ݼtKHɡB;^ckӷd^WQr~>2ŠO,BEby'V kXF}7,tbY;==V@Xef.ռ]uյ?j$~倧zՌk(99〔PafT&vɟ\A7 - X 8xu`k,(osTN%=oWous-nK#DI?C˦r pP4JM?J֯Re%L``y_[}0>(Aũ>/XObject<<>>>>/Annots 256 0 R>>endobj -569 0 obj<>stream -xuXrH}WB/&\6U‹"+6e X*{Y`| L(5|gzIY{2B/'[d^aRAM -/6RAdKL06YB)A>IY&T5fNl"4BUB4l $H*LUIfbm2>#W$ h"5^q&E$ 3TZUpmjSpm:'&/e36d$INftq"¬NUxmB?Ak ' + )#k 9Vab:c(a!&ֺ9P -#H*L[ -p.bTS"'۸e#y\F* 1ValfhVaXN.S[P0@IaKZpBFAd]+k]Rwí˃mp9ٻOXY313X'o+lWzǫM߳y .!7k7? -XUZUarvmʶ|{3/w^0c3e_82B]%C[֦z -fPޭN%S,k]yUޛ -ikx.MU̬-WF:e\5f*D -ZikDM+k -:x"fIy{̟ۡ}\` &4vٰ[bte7sӴ4=\h[Bǣ3߶uߢS3PtsEQxs_].ξendstream -endobj -570 0 obj<>/XObject<<>>>>/Annots 308 0 R>>endobj -571 0 obj<>stream -x}Y]SH}W[fP-yv@P =p & )pu@LCJ FQnt $=Fajs Ũ0f('5SJz7vUfKt̓3U -M^b(#n]H:E(Q ؊ b* 6G{̽wd$$WN1Y,NUlګ0XteYVڕH&eȝL_YR,tO%~O {pĞuCVZAjD-V"'Ń~Gܩ ,iF 8Ulq* r]X-3>)rn<6".j]D\ 3' 91x<< 등>9lɦxօc%xĂ$^R-Bq !t*Rclf犕=W@ClDM@j 18U,R[=p<14#ALՓ$@NT @=d%m%! -VW>+(VE|:1#r{؂Wg]q$S4K񆈝Yq)͑)T8= p%z<xҙxJ)*iN|UIBfw cAnV=r|WB]k_M-S֚e5?OZoX{aShmjS`F:=R Ɋ(< 0[D~ThVmmuTfx>/XObject<<>>>>/Annots 310 0 R>>endobj -573 0 obj<>stream -x==0 04$8 -Цh)AY=~* #f榌6CV I k=y9{ɝѩ*Ŗ`-B6{ 43+ݽ8Uh6wΉbv,wUu|Èz1)23o5Wl4s.`:q7endstream -endobj -574 0 obj<>/XObject<<>>>>>>endobj -575 0 obj<>stream -xWRH}+ʖ-`C8*ه4'Hef|]lRgZߏBOH R|M M3>?#)9\nh2uٜ1DvpP;\9s Iw_h#oGcNpNd>Jۼױ|Å*dp: z>CS -dzuLSr;ԠTU%gD^h9OabyZ~h% *m-첮!<t "rVZ㕴YI"~N85"k |.5|hLqT'9&A4`%AF J*He&s'|CN5c@\'kiHd;ҥbWF62eL{v*+-]H do -^TF*ǵF&҈M -לʭCA!>KOZ!>x5)2V+ - -PE; ,P@ _7PK`r fXcl{5q7G9/Ê>;C ˴F~*Ŋm-1c .\ oL%0w[L{vʭk'?CU<`/&o H<ݢrd@-}5Qޢ[.̩J׿JNw/}Xt_6Z h,ťA>=Be1{HVWti#\ ~z7tz{`wWuRNst $F-)T S. K)@khQi -*T)xT HtMtNLs<É+LEF[2vK.jq=]f y)RQ=s{k~{|2XX -( n*D(+WKl>lRޣ:7+~k7w #Vs/a}7TH]2zMN4"exm씉(ITЗnN@=TzMUE -I!jXH?1,ȸ.;Pa2:%ๅ3/Lyue^ѻt>)^tʥ^>3vmendstream -endobj -576 0 obj<>/XObject<<>>>>>>endobj -577 0 obj<>stream -xV]o6}ϯ{J8x nndhHFRvw.)9a(ԑx?9\sRZLzN:$/ɔf?ŏU:xp9Q&GrAg2p{ 䴵FdR8Oފ<򻿒8~C)NY2C4NhuZJOk"6d&L9iVeޒ/4[RUkS3jB8D]:ZJZٝ<ԉk vt+[+, - Ҏ,;4Dڏhz*OFސ/>I%5@#!C{ z#Q#،6T!i"}BaO2%JG!dY;RßRw]>Q3ӌp8pJd`_?ji3U[ ʆr]).Dht=)yA#cQd!RL}23(ؙLkYN nUqWv<+b8pTG4  i-~vnW#]ܡyy|FP@};DzYjp̊A[Ezt! & -HpQr7)֐x)1&0,!(\rLif;4*Nh3I)Bk5$( яf= /%>^ dk? BԁKs3A9ڴ޳|ܙxSkʒm^2{FabɃ]^`W̨6b g BZTQ*^/cAf2FX QC%#5khb@$:[YKyĔ Ş#_ [9^d0R(}9Z}ڐfDjpp 0Ak{` r>JeI;_*)xTQo7Qa -yuO%(̳7݄B$K0VS^xVk%vqOh9QC :T+,rQ*Gl/`"Ȟ-T3t7 dWE}28_i;ǻ7ƍBc|us~ACyD%x, MUĚ>줽Yp#ಔ[SQ<Pbz}A#\+ǍbD٣M-{p1IbYuk=WA0P!Lmx;2qejT6 'D}v: -#V֕y:j* qd=vPFN'2rǂ1-|-ë{WL09"^:G4“ x7'Pá|. - 5An_Mݍ;], n-Ek WCWWޱgI\p=w~ٜq/M?endstream -endobj -578 0 obj<>/XObject<<>>>>>>endobj -579 0 obj<>stream -xWn8|W[ qI{) -E!/ -J-^$R%)+ %َáHa"wwfvvRw)3>N2,d~Ujz/xO˓_d6 -1nn,Os=ȃ3%}^z}'_\'3?M.'rowEGl\./7g,Mmm Jj*q7FwVRnHs9˪NdYụV*HFNNOm3D4y)H$L( dƻ~;J9Qe2q{.A'Qq㘹!zz]MQVjV~J?y.wՄ!dN*T"rv8:pP)b+B>DТXP0`*@Zcmˇ_i*WTH(smLsσʬ CT)g<(rĉEmת`|ceqmFy`W _] _Xn"Rm4U7*upUKyJ' HuW}6NٵPy|}?Ko:v G@lBEk !k(2$IGhAƓ%b} P'fu2U=%8Y~0\F",Y./S $kP F#]xs"h3k]# J0e﨤>7  1AX˖" [[#fUtkU.gL䛳`ΛQ?7yUz9J쪍2%h -S2v!qcs #S2.;שX k6`b $ LNLny4ҽ*sD= v9 -\`攌 6 i]C[ 4*俋܃\N:nk01t[5kYJ5ƴ ͓׸_9U#kLl|KP"K2v|# ,z؄:4L 2e dm + m[gԭ&뷉!1}bqԤFZ*ǚt -&% %' oJ?om1Aַ9Ob:Y,.`.O:3l)endstream -endobj -580 0 obj<>/XObject<<>>>>>>endobj -581 0 obj<>stream -xuWnF}W Xql/"MRXA`X#i#r]Z,D M̙3g ߂n Uټ|.oyi/f_hqK l, vsZWWuA]`S[%ז \'fzg#|T2ٚMsIeh)Rݞ#u>$SƦ#B- +nkru`lb28&JQƖ#m|$#xɸhgo.W񼏒Ip@J6mOvSLb؊ej0$Dlp[L#S#qO3G?pr})w>T{`f\BTjF ZК=LaؐB`xmce=xI!%DK$@Ӣ;Vc\̩#O~v0 |x͞E"%0c%0ڱK84 $A;-Z1ܑ>8`}ǂ~7OR A~3;}vQHtݫn'G꣕%jM\guG!T:0gb*3kxA\5ՎF) .[n=G@cxU+ۚjI`9?J -ΣMIJTomCZedgY'IyIE6*0:F@0R}6y \[%9Yлv0 թ=zGQL;(Kd$X(#yx! -9vH!A#e*7Y喴&k8dòXU3LÇGLw\Pآ׺ oQF vʚ#55a33dƐ?FfXFt |-_}]_gPYpyݷ%C8Mnpmbq=JL|Ļp&j/"98Ɔ(E'Zo6\M,h0ub5scɔE-SYL<鄩 AHI-{ybJ K| _ P*z:gd#b^vePma2Kg~Q$x*v$z0ۨs'V 1 - -G>/XObject<<>>>>>>endobj -583 0 obj<>stream -xVmo6 _oNĵ7Koz9 4E!J͖_IW7 wcnZsw}UW-ҫol޹leރxe^ǃٯ;<ԃxum4/{z="z/ g.Kd2Ц"t*b54ftnh7.W#k'?PZ5eIX5*KHbˋs`˦ 1(M,k -YUFj͎iXs+z[HV[$H[)ED$0Gl.:ze D[K5H'3H[V+UskRvp+v894ecr[.\i 5`}и'͑;t,jc}lDRyvLƗ 4t |Y$N`h \`$B!eL+ 6f?Iw+ -V ΍*Xo |Y >D8g0~v\,C6ѰNs)`AY*a9 sME/o_28=hbfz:Nz=Q(.B,0i*rA-zpP%Y#v^?Y"endstream -endobj -584 0 obj<>/XObject<<>>>>>>endobj -585 0 obj<>stream -xV]o6|X(ErO .(=}ͳ$D2>)g'uC";;;;^D!~# rLI F`Dwq?hB 'ӈ)aw<\À+w>,SzIN_pnDsI0'ͤ22G -w&[&+Q.9 fMf(pq\K8?sҥ֜2*:$2d5R<'pe փ6p oDfVr|$&*gڬdBliyԱ4=dU6)mji-N~L8֔55jmR|ĕov3z3`(9t.*U]:^=1 ։{2SzDx(qۨ1ٳM0rH"߈nu9; --Ķg$ 8 #UZqߞDn[hضk0\p釤UBF1V6knRlzN..a30(ar b wLh_D޴?4/;f%57*%o0x"qnOjN)UORYLx XRR HBI@PĮוp@Z٥;'fP6~Yn -amYv# ne.2%l(n#b#-*Ex.|kRN<[t-a`3B/A@{οnn96?s{&ƽA|1i!rPըW,.P-zw J ԯ2v_^_D#yjёygÐ<1TX!+ck?0oj|\-LlF㫖?ooo轻c -1`e>/XObject<<>>>>>>endobj -587 0 obj<>stream -xVkF?b8`+)$MzhK݃RVji׷7+˖s`cқ7̗>d@ޘu\NG|e$E0iF #@}ץyϡJ }7x &D&E -Z팑L@jĿiTupiVa ŸۥEzB}(1yaw uM:LO l[Prhcfb/ dٟͦփw{7w$Np*`m-:U(%2r{<{syy43la-VG=YJZA{\# -:`Xp@ZUKl"ۤ9pR3߮> CT"]f"/YlvGn#+]N!y+$/VultVn,~]SscvȠ]Vߗ|qwCXl/*M@k**DŵQ4eG:M6?O!ylb:bj\Ãk6¯pQ7}?|yR0}9Xkjൔ$KRaмK;RI-%GCƬl<*YF47%& s)E)wuER3>+e>/XObject<<>>>>>>endobj -589 0 obj<>stream -xU]o0}ﯸq`LH/;!Ks#i{ι7&MɨQz3)9e NSL,_[Ϧb1^,'oޝSVPd̨T(g>mNӉӜ*njpwtw)CL~::*S3ģmgltկh+MJcZMwG*:My֭ȸqFѝr9 `g1p'I3Bp٭ZqiOlr]qm:%Ʈ8QRCN'a+U=@_oδ-r -ۏ#lrjOSO4ID8AL6=zU?Aky( Ү3!j\{m]jEֻQ871I>Ƒf j 9J\ }]S6lG <h8cl"M4ܜtx*Q -h,(:{x!UdvS4U?^K^oc(L(iESE'o5"c `Z2aDmg`5V ƽQ'Te'klcP' 5~. |Ÿl6~?%k8$;v R ,eA^kyb-0Q2} _Ć'112͆nmVZZ /b9X9">_|׭۲>׽Qbz~!/_/b.o ,gE6Jendstream -endobj -590 0 obj<>/XObject<<>>>>/Annots 315 0 R>>endobj -591 0 obj<>stream -xW]s6|=6eScv}v,]*r "A1pPZק )N]jk]03==דߌ/<;ǝ|Ws&4-ҳ -f3~3^˓-]ӲDZqk'wht4ʬiѮe4g7Ov0%QBW,tvqyɓdK -B&p R|!qvD]#SAu]5t>]eJs#!f#QeA^Rm} LL.ѲxpVDF[éi9Q%u(^X*dRZ)PxCbd9 \ؼQm֣d܃5Ai#-:Pu粃D)JP2 -n+H[P?+a֒V*hTa 4%~m얄G;8SOZ -gX6]ur:"x=f[4'wg?}"';u*5}Ӌ='Z.(W1!(UhԮcc送-x -ԂA&rs;}Qeč=@6O*c葉>*P]Ne.(x/X9xH6k)s7ZfM/(9-Wqs[=ao{OBh>N˴2؞2`zv̬[OQ^3$\_ͳ*Խ\؟hu0d-QaB6:+] Bm<ӶPApjբ>nSocD}e[]EbS22w7J<}qS֫z"wAV;U p('&IAx5p +Dޯ1>KHs%Xfm2wAuXJO526ap86dlk?V*,j.ӈ[.ZN47"(ZGV+u@T}KKr32s$1)c(ז?yS> X6l23PV*tB??~8".e^RE&eANj`';Z[^˿Nqe0в(2 mX j=8 'A -nP QD&;|")/ I! ))5Fc+ֽ᭸3L, w[|z}x?̮tRk[`'E+5>G™\ k"WH8e{ Z??.[F780<-1/_L\ wŋR~O*̤êW-{g<6pqu%Nx֬O# .Ž:b?8 8)i+> xU uD[i޳{`g:0 e>)l2a~oaR`'0 K̉.b..I(dk+vIUO8$mīGcG(¹ o%Xzp\^r?~z巗 Z3ʾ7z-ǧC8K@6,LnJS-Gg=)ba?B叝(% G_[|A>0IH:j5C7&6aPԸ?JfꘞQ&-f -1o4|~U7#:qm,Rh_gPVۅv{\ax8z  g0ѵ4|G]-$i ;0J]vW{g=O Nnς-/RS;y~=Ϯn~y?4endstream -endobj -592 0 obj<>/XObject<<>>>>>>endobj -593 0 obj<>stream -xmWas8_.MJ o5moBd&#luȒO!_oelt2M}埋! oH}PZ\ ƃdB)'iuq<+>;"# h^V^4XI*D꬧]. UF5=?{zRҲҺL$'a2R&HgIfӗ*5b^ʭt5WD8In=4&Oh6HeTj3I(JEPx+Js #6$3/+_beד'ktyÕhUv i[%*2׶ -T -' -Lu]r+TP&@UPΩ(S{ Bm`M*B>*T:ԲL>_-ky`Y9e je ©l-dPi%e*cc- }]Qmq4gdߠN'^CV)* E7K3uߜ{*=k=o? uY#/eV -׳ܱ;QLC Xpy" -!ClKFj3-Y:JBH֧"Ii:W\~*{|&JN$D[%̖k$y@'0@?SM:SJM5i. !hw'ʀ4[H蝨=[]|_~m_uDZT692V^BoA 貾;8KXYX!#кl BV0~4++j48ԆƺBhޢ&x+ 8#2&ǣϮ\I3usBN:|L&\#oaVp -(fT*.٨z&WH3Z?{( G~~$Qܓ|+5aш< a>=% t–ALǠV}|nñЖhY)Whf8 P>@dD:!Rȱ*B`4Hg'+@|g+ѻ -&R ysvЂ/*X[@ǀ -oW slXiZWAf = -̾f7-$CƜ6UDpX5fVu8sn+b4ا 1v%/|FOK%yb"fAV T} `a[sd`#0V% I[cO=aq%/`cc -Q -8ȃ?}8ң%XH@zvBԔK]2{̪N+sJb'17,|8!#w{884(2g9 oz_ N |Uri=TNŸ_No FfX~Fp, 0Ratp,ۘ3~c<'-~?xNendstream -endobj -594 0 obj<>/XObject<<>>>>>>endobj -595 0 obj<>stream -x}X]O8}W\D+&00t߶hvVBBNL$v; $3 lUs?ܟGS:ǟ)-g4>:Ob)Yjgj*>n>V\.hMvr]&.SuѪX+;˸s2_$3=H a_2ye:_tگ-K^*'`\5'xO!c#~9BjR{l&KD[BQ>*gnIecg*  -eu ge.״] *yDeSYcwujɇx -h]M_~aa>;ܺ -0-g2E`ZcX?92w7DΚƲ#vȚuj%AGOZWdG&͔(0խI'זw" Vo謈+X>ky@ cTh? ؏5񗺫۠*Yv=|P caEbaXzL Nt&H_7c$fEF^gU1KR`0:#rf!W -WUn*b(0Ϻ٠oRJUUiH\HZG gȔvE1!@,i0`堽H {{=UH - #=K: B3VΗc1 E/]NIt(8;.fK&l\b,Cc#%`n `K6EE۹2ًfTPNRAMڕwE&L z?F=aZfQn&]Y'9&h .8hJ@cFÉ gW12Dĵ16֊t$;/@ag)7!<+9`qA5$̭#\ό繳.a\xǗywxV8v PAGϘKI錏XVq)W(Qg]hcLQ١xz&q<nkƏ@0#ǧ4{"]0hۉPE7u{\2dћChU<s{~ -Hc{8yhʍa/Ӌx Y!YSpϙ*sZ"<>w9Q @,2CswPza.SۡjAAl2)- (zu`O`]HU)s?4gUe3E"撋עrz8Zc$\W[B}6S.X0z&T}n)$cԊjpK B` kdƸU5G@o2E>/XObject<<>>>>>>endobj -597 0 obj<>stream -xUMs0+vr)68i;L?p{"5V 2d}W qHH0H'~yg>I҄4B^9v, ] QuK"ADD&,Jœ.nqE;s+'R&@B>E_f T*l+~!JނZap٨7F-Q[QBC`5O=Pβ0pWpV #I2n HFYSXBD)$wDSh9ABZ#׉Jr'!F$ -]xkQE<#1tES"2!BgӸ?iEcƧ\*N\*TA 7NPBQ:^E-(,Oxb"٥0sT(sFUTd8@2#"j Y1LLZ;CU)QQk+vHvvohlLA 䊓'|<0p_w[u{F]]6^_ ij4 ޷Dg~ۺEIĒ8]J 8endstream -endobj -598 0 obj<>/XObject<<>>>>>>endobj -599 0 obj<>stream -xVrH}WtIv}ͮki40h!>gu }to?s=Q8q=Wq%.&nxl!}8b*'v|̈́9ƸAxlav&M~OX|bl\פWU4-~DЋ3R -u.3$ +b@c02'\7?{[udKoDfu#;rHO; -fڎ_14Pm%qjwt=r2UE;|?4\w3!p"z%0zaߓH;ev2a49"ndXDM5O$eNHx[y#$oy+ٿ؎WpZ2Tɬ(\[ÿ́QgV -)ҶW628H:n;#*mJ.ҍ6JុBf6#/1* -whkkG#[IkJ}a4e= K']1EkXyAM4ҹ2IYB2[B!i!ZZnI+&k֦`D&/+ >]A5W!,;HþD }WEQ=Wff3R]˦LPQ1.$|j`bhfC@2}p6 (0m͕(/Ƅ]3Gx~i 3l*2z+sPbeЇLC(GYDfں3 P6-}p[08q[޶ -5JeS9:JgJtz|*~x-oA̿ h2(z}6k@c;~<:Nϝ8th}>kIMPendstream -endobj -600 0 obj<>/XObject<<>>>>>>endobj -601 0 obj<>stream -xW]oF|X6`1,Krޔ) $AZ -Z0ѺSyUw>(VJٙg߄SSV1&dJSՒ -goh2ug̗ ZscZgu.mҍ16SeI$+٭f#qyZ$W(Kd -(rlL5b\Uk%L4g)KLOxǵ˄W]&sޏ$9E%%޴dڧ J_nsv+Yg2.΢}}Wt敦V[IO攪;SWHU*Dvc2q~Ϣl%l6t冴i6L)"YuIfJe #^xw٦V 8@/T)Z5h - ?>Grěnt(TRw^ -i%dJ5H L§/Raq=Oyo'F\ ݊@Dr(-0%0 ^][ -zVvp pSdJs\~{R^/c5@h^8J:$4cOJgeG,{Av9f"ȃeԙ|_ -mQ8;쩅@@Zfx'99NŞ9Ms-m[Lp~jelt%- ˎ9 8/ܲmڱ*]wTtWt)W.aX}Rfsh`Ŕܕ(+ԟd$ʝ[x<owpO CJ0d"7\zQB9u oF]q'޳oY暕a6vFrcҡc4=\3=NtSРO TiO`Cl -sr}{Ǝ~-C_У̃{5,}L2- >0;GԼ|D݇A ꉑ;a1C'FM4 N'g#c -!nAA a&7ݦMFEm*^n8 \%kkG][`81Xטnҍ''ؤ,%+Rg=?a(qyZl~5Tnyvw}Y0׹s ^!luhCj͗M22Y8[݀Q3)A#AX|=Ý幫L"fPA9>eʧIJ3ƫPB4Hl X;+9m(ͅrh[O<9-Ҫlqh1eGN-fbDǚ-׳Uhkendstream -endobj -602 0 obj<>/XObject<<>>>>>>endobj -603 0 obj<>stream -xTMo0 Wڎ]$]YvEX#eܬ klXaĐG1zBH#'Pg19Fhu]P4d!5Px@Ql`jW5X^vxUBw~RgԖ 5}e{8h*-J|=ri@5zݽX!w*%0(Z48@v@ᜪ"wB*ޏ|@Ce-^KH;.קҨ,dtpVzi~ӗo>/XObject<<>>>>>>endobj -605 0 obj<>stream -xVn6+.Ѕm VL1AȢE ̢mHH'|}Ͻ,Nf K}{!]i1-&4SV^MfɄf ?Oi-/&˫;hF▖9!OV킮hrɗ$svMkS_;^Ľ)'^y2NQLɪg4׫'dΫ?+ 5d<*iuNΒXMC[T7N{rkYLyYmP\ʈi,+U\w4wROtd̤B٧:ŐQ'@nPlq T>D@3, gWzc{1aKP"K3\H޹ɛEѽzK/\[g V^OM?g%m`*=H5L'E?r '}f[Ȱ!A%8$sNŬɯxT>PxqBy׬{1:50uA]e@1u gZ$[t)4} `D?ȐZ/71gUR#:G)H08Q# q~d$ X <1\(F`*  -a} ٬"p:dÁ(Aypb"N#F#6qXsc4夜Cxly>j)NA,Λ]eh(+{cy>دzҥ{Emzx3P)#B蠉hQnq(<9䤪 UEWoGq*N~Cv5-_/lYiP?,̬rq W'X5W8|=#iʧBȦbl{qmZIŁi!-@ _j)4i:;lQn|>a~rNr5-Ⱦ#b`ƖW*l*EM}U5׎P~U%{È,z/_R}N+Q3>T4m&3Jo6K]<ғҧW/ AhŖA+U:?d1ɘK}y endstream -endobj -606 0 obj<>/XObject<<>>>>>>endobj -607 0 obj<>stream -xV]oF}W7PCHMVYV< nf;c>(ǹsv'qHÈ3CD!~ IK |}zys; ɘf !`@{KIZ#IpIوXZ,T9mug72o -i*ZՎVJP  PK,UG2RW!C,edpi42>ͻKӣ_b]퐥*NQZBH@+ٺ&E!R2.dBZ"&#ȗĥ^"H#i\E(JT 1T*A\" -x'}x4o~ozF͕_E[1:Q8rXd.iId:o؁?|ݛ\-}II:W?c~=5[UkҰiN,!YHmݦ:=ND$\t:6 G{Ok -G7Q;y8K~zCwZIce<`+B)JvkC9DhMPaƿBL?|!X#(bL1PVң[e~fAoxHO_#~{T;fĐ9n&kNЏ..(n>O?\Og$3C}S?Om>/XObject<<>>>>>>endobj -609 0 obj<>stream -x}SM0Wma|T586ll@RE -{f oQeG1Qd+KN%p1+fbYG9uAy1j1`ph$odejl9kJo)5p+ݹ$Dg*z'(4XJcGR"jyWs,|=S"|mLӂ|/:gݨ#o3 (k}Uuo`Ֆ0=Xq7=@> ߖph+ -u=zy'ܭn=Gi~V@B:[<4i$`)KYe}_0Yz_aXݪ-Z86aЃN'3S'8q!&Ti@:4n6yw֮ -}d+}k97a$wAg( t -KT~=:)Xi%gߪe(;noelvZƋ9+94ͫ:q&endstream -endobj -610 0 obj<>/XObject<<>>>>>>endobj -611 0 obj<>stream -xW]o6}ϯ00,\%v8k[\%/DYl$Q#);;]@"s?ق.oA%]Pޜ]fMvK׷+ y4yv}vq-/i]%*hџ:x$ӒyOūgX^_]gK8_elv Ah7y!q@«_'j@K^S*[fkתF_ j润 -Aڶh Wtӹp6?ǧWpگ,3` ZNڀWW2 -@6] ,O}: &k syœ3q>Nզncx`5vMyR:A2( mqq)`2MCªHdJtP\;D)%~j+N22\HmqCB65zd <)N37\=cEB$>b-@:3V߰ -({cҺŊ5pQĊ_HT2wq;4o4i Kx-8i47A)E5r҂m>7{nZ^? $ZX\J&\Qyn1~गM|m/xoIiPX)k$b†bi$6`Ҹy,`BK{4I>ejդ6}vyTTmB[Oy&Ѩg= `Qt]g$=gUn.njW^]g[|Ogyޯ:uendstream -endobj -612 0 obj<>/XObject<<>>>>>>endobj -613 0 obj<>stream -x}Wn8}W i(c/"@tkwy$bK*IRr`8H$r.gΜ:?SZjAEs2&X\z3|*nK/n&l㜦SZW^Һ$؟Lh]k / M^Sju/sR]̆:/F-0%UVoe*UZ8 -˳5VN GF(>ӗoh`9ꋫ92ƽe6~g]ӱ.flZIpPz󧯫sc[e;VL?|J!s'gQE#9bQ\ff;[$p&E yVf.U,:0-tV܃3cW+TVNa|O3<4OɶLOH5l!O0rYUz!kADW0]ýRvWRTCX#)H V)s+B8 SoDQrt*pye=zXZˌ6i -O52ԶQd`Eos`d֑I^z[22Cre:|! Ha)%պ7}AAVb6,A&$&?e O;uE$g0Qc^pIl~D3%:EЇ%Y2ť*g 5У:̟g; # -xg>B2+*jkRHYJPtc9FhBlX]A(:c8 2٭(WazG4m#~hK>>Q(fl)uڍ%"u7EM<("#&+Q[w=p3nATv<-lo c/5HtX( #LpX 5(~4g֖X JZX,= :\*pR*qN`pu -y`}*Ήۣ༔M` omh;.|@_=K2T(Q=e >!5:}ncN-B]K9ĺr iI a>/XObject<<>>>>>>endobj -615 0 obj<>stream -x}W]O;}WR*AJ MJ|^U*ЖTJ]oe^B=3ބU*ڞ3gΌF4= e>M=_ビ?o|8|:єfLG4 hN!]hkq4.޾ 8{_jK(\mRa*M& - -(MV k=hTsrbpzHR- ݋˛#yl|kzu~FiݯbEREqˀʢq$rvPU[ -׬դ+x,Eot8Z,'wP5MxϾ ]=[ pIM6 TnpM2^Bjؙ8 njOkT#5Y1vG-ּK8zi7znPIJ5,K4Lv*ꬴ  -c4o0Ty8U0XS4=^AN RlXMmL3ĻSqB:d{a*ArYG!Et#p䳔hTU5Q{ T5 ^FOy % -ڎ& :.5(P s71LVԟd5hrg/Xd 4*-2NtvcBnKkZ7duH_ -.^ fݭA eiZ`nD$0&ty̗H J]o+)>/XObject<<>>>>>>endobj -617 0 obj<>stream -xmUn6+4lv9&I`C.4HJR6_7j M9o޼yw4~^튲z4Kf/-7k|^1yI9 Ymִ SET|[<Xўgӊ P# JRrk~Mc] Fĉi5d~)SUug4029@%RUm}]PT'J )*Y*+QuQ+`/IRo}$Ɇ)K9=(])TU@{TrTj@;P%Y$ycUS`3[H3o* DG^'5.[͙s/6ɄM+8l -#' e+{L[  (ᥣ -M r)CYG$Ot=2.srhAgN+f?Uhۇ}pmZ}G s.OǺF!2AU_K>nB/!pƽBfׁZH (P{uM@K%m#Fи;_e6&t,5*10 Qz!pMf#ߩ963ըTW:hF -Uާ g ŐLs;Hh8- -~I&"?|B{q&x-2tWo k|hvCqԑIU:[u(c>qX\֍<9@Ѡղ;"|bjDA1H`tΪDS(`BJ  \[bV -IagZiaat欷E,dt URJ8 >< Oa/&0&)г\N>0 !"-jJC#;f -}t¿9Qft2OVnVz4}d]ܴ`͠J -xdWpN(£8lJHJÄ' H.BTNMf%a@>/XObject<<>>>>>>endobj -619 0 obj<>stream -xWko6_q 8NZ`u Mx %Q6H*%)?H}sϽbJ^/(/>.^}zK JY\Ъx2|V4^Zʊ\ 9QgyYS.ʽ\}9MfE CҙiX]_\ޏ``)-ӭF`,SŃ^lO[bd QdT(70Z*Ȃ 3;k76X;G:ƊACYP#[YKm~h!vwBΕ3j(XGk xq >bxD:L9N2NI05(4,;%BU \ -d8$+!b,`kgr>+ݞ`H&\hw)ߵ恬xI=̷+mu`ѱņ`"T3:B"=gBQ ?f# XiT#\ԭWN}"sjV~LXt!lekRjD];4ӀG*̃n*8<,3@і!2qhb:hOO%hcBFz -"ls?=18r¨!>} B34z d.^n)p:2h^ygZD+ < DvLa6 -EºZk P#P8,Am; 3CK@!Zٷ3ț<Ğ%^$۬A&Iee0!/zOT<'O\hICE%]۪|˴GG:Z~]ېU -1.!ϰડˏ 9h-HnA^T uH+McَII肃cLcbk5eSn xd&v P* E~ M;6޿>qE\W0ߎ#0BFi: {x-^Z^gzuLMaUU6@i D&<~:!:ύ3Pǚw -Qɺ~~Iben,oܙ_׋|1Aaf7l\endstream -endobj -620 0 obj<>/XObject<<>>>>>>endobj -621 0 obj<>stream -xTao6_q'e[5lP$iRؖ51P KQ0)fCI;J3`E޻wߣ9*wK*,b -Z+b_LS -d;Yj|E„"G}("[- ,pDkyu} [endstream -endobj -622 0 obj<>/XObject<<>>>>/Annots 328 0 R>>endobj -623 0 obj<>stream -xWmOGίK@w>l*BbWi*Kr{3K{;;`Ҵ ^m^yfu/.?F]l_%GQ~DvUЄS8z|6Ev=E'8K'x+>KhHIt^+>}1n5w7r{xG2g?::~= >{?݋FPF9 Ohg_,E奥QDwS`J4ݏ/޺_e2l^vGpx$+G$qsTrեԞ2=;Rznl))yC5+KMx4Q%f+IwHijO~)IK-ѥNo$~"-L3[aϱf3ջ88eie."iH"kdԪ ,x ] 2Ω줓<  ^5uE}ʦD⭣8CJ/>;N9P ]10ޯ+ 衮2Z*_ y]k^MX v5Wø9⒊쁀ԖS%Ba$bȳCv%*Ɍ@Nל -ŀ6dn@%#ˬJ2$$S/}+&kJ!XK01)SpkFbvcНё|}15-&Oa*y} -Ol dn )9dlP);JsTPHOwT8a,ʭ2Z@V.ɵऩ:s, !T2:˫-@xy*Z:v"pHReˀB=* dV0) gBLX`m2\U!S o0 -["d&q?ʛޱs MIG{N, -ԓMJ4Mf -2=mXJFfU~iwj! -(SpQ8A!cbpdɡ`Qt@WkFeZu -lIU^ _#E(Lēt>.wt>vONo϶O?z[3җ3 ձo@˕ݡRiM -xo8[Nt\]M8h(E폒M)n%41@drXJZY=-f, Uiu]K>m:sdK%W0*`6jY?Ц -5fO<|0mNjle2ߋC Lq  l,,Zp@ Sݚ$LꁱKvVv?G24Ѓ u|Xқ[%RU߽!U3WgRX%j HZ<T{6=j)*xTt>E㌕" Lhii؛wWB-lRcv9 ذZ2pURѫ҆Jb c!H8 @8,(( t$T*JބGΆ>`4?]\;5`xY;0aS?7Ldt! ^0lkW'mvzHIcQ]N~ɶ5endstream -endobj -624 0 obj<>/XObject<<>>>>>>endobj -625 0 obj<>stream -xWMsFWtrwr8*IVLahdf y=KT&Mp?^~jH ihJyu5H4Y:kiG}1VW>i8FO3ZՎShPFumЋnUjsk2QmM[UrҥW\%(%pfHXn=2ŏ) )z3&rXoɿU6\N`5[U yn%l:DGYa) ^zn_c ЧmMd *H桫ٛs8t -bwKwNH1{0v+_Ec:R K?; z2;>p2xT!qe 1㰅\84k*8)u/;HSDz0+jQ -^lj?'(߃(.4FhΠ>}nII*t2,xYgt6?rկWendstream -endobj -626 0 obj<>/XObject<<>>>>>>endobj -627 0 obj<>stream -xoo0SK;qxn+Lc(s֬3AO%nY"w*U=?s ? - ,'! 3 ;`!'|2:=+f<CƬ8 -2&% ?Rjf?:Q#)jyw T^(w OXȺ,cni$4|PKp׏zTk?^ hDXSiO9,gϘ1~̥àCgpuơuΎ;N]k'#뛯JW׽-.ߴ[誢8Ui!l\M'NO'^|_Cp[|'Kq[/N=yA}ksSBȺ63Bb?[{a Fy#+k:i;|k$"F amCG]1׶%Npxh=67}LOPg4)pm.b6+KF>bb$L}'1I*:|endstream -endobj -628 0 obj<>/XObject<<>>>>>>endobj -629 0 obj<>stream -xUr0+t -q5d0X#\$ﻂ6akDƋ G60KY0( $I،8} ϣ/!P -Qg39k30U\.ne^[&qW!8ulmbPUR$El+lAhGR65zePu3R|0yܶj[V u`YezySAYwaX̮4g?Omپ|n=Ú{c.fYaSEtls C`c9Wgg0|]lp k%RnYX˷Cs@5G^(@endstream -endobj -630 0 obj<>/XObject<<>>>>>>endobj -631 0 obj<>stream -xVr0}+tjշN_NƑ(c,"iIKaݳgw}rƏ ^tѲ c(.~{ ^2 N=|@2EAB=6$!.gzn jΠCgW''-"1Q⹕ٯ͘x +d=]@keYVQn;TِFU5 N&.Rfb)eZŒ=nV_Ti9yʸTqMXz4`aRLrsϑ6A3flc-'q׆K`qM Cr!7:~p"dN-r0J@H9J3XT5xtiLPT+Lh)L#Wּ邿0>ь -hzTRǸJlkt]\pu/(?.8٨]XLӜe|?si3/]al 'AE&)JOf)T6RDk6 _ 盿N֯?+MO.endstream -endobj -632 0 obj<>/XObject<<>>>>>>endobj -633 0 obj<>stream -xVN@}+&VZ'Ր f :e;Swڪ@l ps=  ZAC;l ٧W0/ n+Wx%㉐s( q4m#KsS?e3֎AD~yN}SEg\hxa\鄭X[ &ϷWyvŽ])A+g?_wendstream -endobj -634 0 obj<>/XObject<<>>>>>>endobj -635 0 obj<>stream -xVQo0~WcA(Lh;[InBc$NmsL@ >wwg?u4ؖ c[.xHbkZp>ڽqvN.8.щ 6hhVr \JTs+' &I8X V-юȻWUȤ11AzV7xr RRlInPR"iO/f.RL>3s䆄dNu.˛[Nf`b)C8+j, YƈTS X)݅!ɕM.Pm@,q3Q<&Eai92̢.3Jr < c+IP@W>*I֦"d$ +$GWhJ+f'! jVE׷eEY FPR0Unتl_ iܵ3~ #QӇ.,wј?ʚ'gb$bx9L` -VVuUni͸FD-YiشC ;}@(yo]xnjݼ7UX0/T7f)3" Ʃ2@ - i~3]7'2fS@qfЌHNk)<Aږewr-yNwL$j(Aup<+0WFFq"cx^<*bokCcZ `=#C- <|ؾDendstream -endobj -636 0 obj<>/XObject<<>>>>>>endobj -637 0 obj<>stream -xVo0~篸HI iMJ$xKlf'д}g' -A -">ߝsƷ ^Iѳ-!>H?]H -1xN` Z߆w4q 4z;6G(u/dz cT:Nn&ʭ=vHEAN +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (chapter.1) >> +endobj +8 0 obj +(1 Definition of NetBIOS Protocol and Name Resolution Modes) +endobj +9 0 obj +<< /S /GoTo /D (section.1.1) >> +endobj +12 0 obj +(1.1 NETBIOS) +endobj +13 0 obj +<< /S /GoTo /D (section.1.2) >> +endobj +16 0 obj +(1.2 BROADCAST NetBIOS) +endobj +17 0 obj +<< /S /GoTo /D (section.1.3) >> +endobj +20 0 obj +(1.3 NBNS NetBIOS) +endobj +21 0 obj +<< /S /GoTo /D (chapter.2) >> +endobj +24 0 obj +(2 Samba Architecture) +endobj +25 0 obj +<< /S /GoTo /D (section.2.1) >> +endobj +28 0 obj +(2.1 Introduction) +endobj +29 0 obj +<< /S /GoTo /D (section.2.2) >> +endobj +32 0 obj +(2.2 Multithreading and Samba) +endobj +33 0 obj +<< /S /GoTo /D (section.2.3) >> +endobj +36 0 obj +(2.3 Threading smbd) +endobj +37 0 obj +<< /S /GoTo /D (section.2.4) >> +endobj +40 0 obj +(2.4 Threading nmbd) +endobj +41 0 obj +<< /S /GoTo /D (section.2.5) >> +endobj +44 0 obj +(2.5 nbmd Design) +endobj +45 0 obj +<< /S /GoTo /D (chapter.3) >> +endobj +48 0 obj +(3 The samba DEBUG system) +endobj +49 0 obj +<< /S /GoTo /D (section.3.1) >> +endobj +52 0 obj +(3.1 New Output Syntax) +endobj +53 0 obj +<< /S /GoTo /D (section.3.2) >> +endobj +56 0 obj +(3.2 The DEBUG\(\) Macro) +endobj +57 0 obj +<< /S /GoTo /D (section.3.3) >> +endobj +60 0 obj +(3.3 The DEBUGADD\(\) Macro) +endobj +61 0 obj +<< /S /GoTo /D (section.3.4) >> +endobj +64 0 obj +(3.4 The DEBUGLVL\(\) Macro) +endobj +65 0 obj +<< /S /GoTo /D (section.3.5) >> +endobj +68 0 obj +(3.5 New Functions) +endobj +69 0 obj +<< /S /GoTo /D (subsection.3.5.1) >> +endobj +72 0 obj +(3.5.1 dbgtext\(\)) +endobj +73 0 obj +<< /S /GoTo /D (subsection.3.5.2) >> +endobj +76 0 obj +(3.5.2 dbghdr\(\)) +endobj +77 0 obj +<< /S /GoTo /D (subsection.3.5.3) >> +endobj +80 0 obj +(3.5.3 format\137debug\137text\(\)) +endobj +81 0 obj +<< /S /GoTo /D (chapter.4) >> +endobj +84 0 obj +(4 Coding Suggestions) +endobj +85 0 obj +<< /S /GoTo /D (chapter.5) >> +endobj +88 0 obj +(5 Samba Internals) +endobj +89 0 obj +<< /S /GoTo /D (section.5.1) >> +endobj +92 0 obj +(5.1 Character Handling) +endobj +93 0 obj +<< /S /GoTo /D (section.5.2) >> +endobj +96 0 obj +(5.2 The new functions) +endobj +97 0 obj +<< /S /GoTo /D (section.5.3) >> +endobj +100 0 obj +(5.3 Macros in byteorder.h) +endobj +101 0 obj +<< /S /GoTo /D (subsection.5.3.1) >> +endobj +104 0 obj +(5.3.1 CVAL\(buf,pos\)) +endobj +105 0 obj +<< /S /GoTo /D (subsection.5.3.2) >> +endobj +108 0 obj +(5.3.2 PVAL\(buf,pos\)) +endobj +109 0 obj +<< /S /GoTo /D (subsection.5.3.3) >> +endobj +112 0 obj +(5.3.3 SCVAL\(buf,pos,val\)) +endobj +113 0 obj +<< /S /GoTo /D (subsection.5.3.4) >> +endobj +116 0 obj +(5.3.4 SVAL\(buf,pos\)) +endobj +117 0 obj +<< /S /GoTo /D (subsection.5.3.5) >> +endobj +120 0 obj +(5.3.5 IVAL\(buf,pos\)) +endobj +121 0 obj +<< /S /GoTo /D (subsection.5.3.6) >> +endobj +124 0 obj +(5.3.6 SVALS\(buf,pos\)) +endobj +125 0 obj +<< /S /GoTo /D (subsection.5.3.7) >> +endobj +128 0 obj +(5.3.7 IVALS\(buf,pos\)) +endobj +129 0 obj +<< /S /GoTo /D (subsection.5.3.8) >> +endobj +132 0 obj +(5.3.8 SSVAL\(buf,pos,val\)) +endobj +133 0 obj +<< /S /GoTo /D (subsection.5.3.9) >> +endobj +136 0 obj +(5.3.9 SIVAL\(buf,pos,val\)) +endobj +137 0 obj +<< /S /GoTo /D (subsection.5.3.10) >> +endobj +140 0 obj +(5.3.10 SSVALS\(buf,pos,val\)) +endobj +141 0 obj +<< /S /GoTo /D (subsection.5.3.11) >> +endobj +144 0 obj +(5.3.11 SIVALS\(buf,pos,val\)) +endobj +145 0 obj +<< /S /GoTo /D (subsection.5.3.12) >> +endobj +148 0 obj +(5.3.12 RSVAL\(buf,pos\)) +endobj +149 0 obj +<< /S /GoTo /D (subsection.5.3.13) >> +endobj +152 0 obj +(5.3.13 RIVAL\(buf,pos\)) +endobj +153 0 obj +<< /S /GoTo /D (subsection.5.3.14) >> +endobj +156 0 obj +(5.3.14 RSSVAL\(buf,pos,val\)) +endobj +157 0 obj +<< /S /GoTo /D (subsection.5.3.15) >> +endobj +160 0 obj +(5.3.15 RSIVAL\(buf,pos,val\)) +endobj +161 0 obj +<< /S /GoTo /D (section.5.4) >> +endobj +164 0 obj +(5.4 LAN Manager Samba API) +endobj +165 0 obj +<< /S /GoTo /D (subsection.5.4.1) >> +endobj +168 0 obj +(5.4.1 Parameters) +endobj +169 0 obj +<< /S /GoTo /D (subsection.5.4.2) >> +endobj +172 0 obj +(5.4.2 Return value) +endobj +173 0 obj +<< /S /GoTo /D (section.5.5) >> +endobj +176 0 obj +(5.5 Code character table) +endobj +177 0 obj +<< /S /GoTo /D (chapter.6) >> +endobj +180 0 obj +(6 The smb.conf file) +endobj +181 0 obj +<< /S /GoTo /D (section.6.1) >> +endobj +184 0 obj +(6.1 Lexical Analysis) +endobj +185 0 obj +<< /S /GoTo /D (subsection.6.1.1) >> +endobj +188 0 obj +(6.1.1 Handling of Whitespace) +endobj +189 0 obj +<< /S /GoTo /D (subsection.6.1.2) >> +endobj +192 0 obj +(6.1.2 Handling of Line Continuation) +endobj +193 0 obj +<< /S /GoTo /D (subsection.6.1.3) >> +endobj +196 0 obj +(6.1.3 Line Continuation Quirks) +endobj +197 0 obj +<< /S /GoTo /D (section.6.2) >> +endobj +200 0 obj +(6.2 Syntax) +endobj +201 0 obj +<< /S /GoTo /D (subsection.6.2.1) >> +endobj +204 0 obj +(6.2.1 About params.c) +endobj +205 0 obj +<< /S /GoTo /D (chapter.7) >> +endobj +208 0 obj +(7 NetBIOS in a Unix World) +endobj +209 0 obj +<< /S /GoTo /D (section.7.1) >> +endobj +212 0 obj +(7.1 Introduction) +endobj +213 0 obj +<< /S /GoTo /D (section.7.2) >> +endobj +216 0 obj +(7.2 Usernames) +endobj +217 0 obj +<< /S /GoTo /D (section.7.3) >> +endobj +220 0 obj +(7.3 File Ownership) +endobj +221 0 obj +<< /S /GoTo /D (section.7.4) >> +endobj +224 0 obj +(7.4 Passwords) +endobj +225 0 obj +<< /S /GoTo /D (section.7.5) >> +endobj +228 0 obj +(7.5 Locking) +endobj +229 0 obj +<< /S /GoTo /D (section.7.6) >> +endobj +232 0 obj +(7.6 Deny Modes) +endobj +233 0 obj +<< /S /GoTo /D (section.7.7) >> +endobj +236 0 obj +(7.7 Trapdoor UIDs) +endobj +237 0 obj +<< /S /GoTo /D (section.7.8) >> +endobj +240 0 obj +(7.8 Port numbers) +endobj +241 0 obj +<< /S /GoTo /D (section.7.9) >> +endobj +244 0 obj +(7.9 Protocol Complexity) +endobj +245 0 obj +<< /S /GoTo /D (chapter.8) >> +endobj +248 0 obj +(8 Tracing samba system calls) +endobj +249 0 obj +<< /S /GoTo /D (chapter.9) >> +endobj +252 0 obj +(9 NT Domain RPC's) +endobj +253 0 obj +<< /S /GoTo /D (section.9.1) >> +endobj +256 0 obj +(9.1 Introduction) +endobj +257 0 obj +<< /S /GoTo /D (subsection.9.1.1) >> +endobj +260 0 obj +(9.1.1 Sources) +endobj +261 0 obj +<< /S /GoTo /D (subsection.9.1.2) >> +endobj +264 0 obj +(9.1.2 Credits) +endobj +265 0 obj +<< /S /GoTo /D (section.9.2) >> +endobj +268 0 obj +(9.2 Notes and Structures) +endobj +269 0 obj +<< /S /GoTo /D (subsection.9.2.1) >> +endobj +272 0 obj +(9.2.1 Notes) +endobj +273 0 obj +<< /S /GoTo /D (subsection.9.2.2) >> +endobj +276 0 obj +(9.2.2 Enumerations) +endobj +277 0 obj +<< /S /GoTo /D (subsubsection.9.2.2.1) >> +endobj +280 0 obj +(9.2.2.1 MSRPC Header type) +endobj +281 0 obj +<< /S /GoTo /D (subsubsection.9.2.2.2) >> +endobj +284 0 obj +(9.2.2.2 MSRPC Packet info) +endobj +285 0 obj +<< /S /GoTo /D (subsection.9.2.3) >> +endobj +288 0 obj +(9.2.3 Structures) +endobj +289 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.1) >> +endobj +292 0 obj +(9.2.3.1 VOID *) +endobj +293 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.2) >> +endobj +296 0 obj +(9.2.3.2 char) +endobj +297 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.3) >> +endobj +300 0 obj +(9.2.3.3 UTIME) +endobj +301 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.4) >> +endobj +304 0 obj +(9.2.3.4 NTTIME) +endobj +305 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.5) >> +endobj +308 0 obj +(9.2.3.5 DOM\137SID \(domain SID structure\)) +endobj +309 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.6) >> +endobj +312 0 obj +(9.2.3.6 STR \(string\)) +endobj +313 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.7) >> +endobj +316 0 obj +(9.2.3.7 UNIHDR \(unicode string header\)) +endobj +317 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.8) >> +endobj +320 0 obj +(9.2.3.8 UNIHDR2 \(unicode string header plus buffer pointer\)) +endobj +321 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.9) >> +endobj +324 0 obj +(9.2.3.9 UNISTR \(unicode string\)) +endobj +325 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.10) >> +endobj +328 0 obj +(9.2.3.10 NAME \(length-indicated unicode string\)) +endobj +329 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.11) >> +endobj +332 0 obj +(9.2.3.11 UNISTR2 \(aligned unicode string\)) +endobj +333 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.12) >> +endobj +336 0 obj +(9.2.3.12 OBJ\137ATTR \(object attributes\)) +endobj +337 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.13) >> +endobj +340 0 obj +(9.2.3.13 POL\137HND \(LSA policy handle\)) +endobj +341 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.14) >> +endobj +344 0 obj +(9.2.3.14 DOM\137SID2 \(domain SID structure, SIDS stored in unicode\)) +endobj +345 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.15) >> +endobj +348 0 obj +(9.2.3.15 DOM\137RID \(domain RID structure\)) +endobj +349 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.16) >> +endobj +352 0 obj +(9.2.3.16 LOG\137INFO \(server, account, client structure\)) +endobj +353 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.17) >> +endobj +356 0 obj +(9.2.3.17 CLNT\137SRV \(server, client names structure\)) +endobj +357 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.18) >> +endobj +360 0 obj +(9.2.3.18 CREDS \(credentials + time stamp\)) +endobj +361 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.19) >> +endobj +364 0 obj +(9.2.3.19 CLNT\137INFO2 \(server, client structure, client credentials\)) +endobj +365 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.20) >> +endobj +368 0 obj +(9.2.3.20 CLNT\137INFO \(server, account, client structure, client credentials\)) +endobj +369 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.21) >> +endobj +372 0 obj +(9.2.3.21 ID\137INFO\1371 \(id info structure, auth level 1\)) +endobj +373 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.22) >> +endobj +376 0 obj +(9.2.3.22 SAM\137INFO \(sam logon/logoff id info structure\)) +endobj +377 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.23) >> +endobj +380 0 obj +(9.2.3.23 GID \(group id info\)) +endobj +381 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.24) >> +endobj +384 0 obj +(9.2.3.24 DOM\137REF \(domain reference info\)) +endobj +385 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.25) >> +endobj +388 0 obj +(9.2.3.25 DOM\137INFO \(domain info, levels 3 and 5 are the same\)\)) +endobj +389 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.26) >> +endobj +392 0 obj +(9.2.3.26 USER\137INFO \(user logon info\)) +endobj +393 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.27) >> +endobj +396 0 obj +(9.2.3.27 SH\137INFO\1371\137PTR \(pointers to level 1 share info strings\)) +endobj +397 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.28) >> +endobj +400 0 obj +(9.2.3.28 SH\137INFO\1371\137STR \(level 1 share info strings\)) +endobj +401 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.29) >> +endobj +404 0 obj +(9.2.3.29 SHARE\137INFO\1371\137CTR) +endobj +405 0 obj +<< /S /GoTo /D (subsubsection.9.2.3.30) >> +endobj +408 0 obj +(9.2.3.30 SERVER\137INFO\137101) +endobj +409 0 obj +<< /S /GoTo /D (section.9.3) >> +endobj +412 0 obj +(9.3 MSRPC over Transact Named Pipe) +endobj +413 0 obj +<< /S /GoTo /D (subsection.9.3.1) >> +endobj +416 0 obj +(9.3.1 MSRPC Pipes) +endobj +417 0 obj +<< /S /GoTo /D (subsection.9.3.2) >> +endobj +420 0 obj +(9.3.2 Header) +endobj +421 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.1) >> +endobj +424 0 obj +(9.3.2.1 RPC\137Packet for request, response, bind and bind acknowledgement) +endobj +425 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.2) >> +endobj +428 0 obj +(9.3.2.2 Interface identification) +endobj +429 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.3) >> +endobj +432 0 obj +(9.3.2.3 RPC\137Iface RW) +endobj +433 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.4) >> +endobj +436 0 obj +(9.3.2.4 RPC\137ReqBind RW) +endobj +437 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.5) >> +endobj +440 0 obj +(9.3.2.5 RPC\137Address RW) +endobj +441 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.6) >> +endobj +444 0 obj +(9.3.2.6 RPC\137ResBind RW) +endobj +445 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.7) >> +endobj +448 0 obj +(9.3.2.7 RPC\137ReqNorm RW) +endobj +449 0 obj +<< /S /GoTo /D (subsubsection.9.3.2.8) >> +endobj +452 0 obj +(9.3.2.8 RPC\137ResNorm RW) +endobj +453 0 obj +<< /S /GoTo /D (subsection.9.3.3) >> +endobj +456 0 obj +(9.3.3 Tail) +endobj +457 0 obj +<< /S /GoTo /D (subsection.9.3.4) >> +endobj +460 0 obj +(9.3.4 RPC Bind / Bind Ack) +endobj +461 0 obj +<< /S /GoTo /D (subsection.9.3.5) >> +endobj +464 0 obj +(9.3.5 NTLSA Transact Named Pipe) +endobj +465 0 obj +<< /S /GoTo /D (subsection.9.3.6) >> +endobj +468 0 obj +(9.3.6 LSA Open Policy) +endobj +469 0 obj +<< /S /GoTo /D (subsubsection.9.3.6.1) >> +endobj +472 0 obj +(9.3.6.1 Request) +endobj +473 0 obj +<< /S /GoTo /D (subsubsection.9.3.6.2) >> +endobj +476 0 obj +(9.3.6.2 Response) +endobj +477 0 obj +<< /S /GoTo /D (subsection.9.3.7) >> +endobj +480 0 obj +(9.3.7 LSA Query Info Policy) +endobj +481 0 obj +<< /S /GoTo /D (subsubsection.9.3.7.1) >> +endobj +484 0 obj +(9.3.7.1 Request) +endobj +485 0 obj +<< /S /GoTo /D (subsubsection.9.3.7.2) >> +endobj +488 0 obj +(9.3.7.2 Response) +endobj +489 0 obj +<< /S /GoTo /D (subsection.9.3.8) >> +endobj +492 0 obj +(9.3.8 LSA Enumerate Trusted Domains) +endobj +493 0 obj +<< /S /GoTo /D (subsubsection.9.3.8.1) >> +endobj +496 0 obj +(9.3.8.1 Request) +endobj +497 0 obj +<< /S /GoTo /D (subsubsection.9.3.8.2) >> +endobj +500 0 obj +(9.3.8.2 Response) +endobj +501 0 obj +<< /S /GoTo /D (subsection.9.3.9) >> +endobj +504 0 obj +(9.3.9 LSA Open Secret) +endobj +505 0 obj +<< /S /GoTo /D (subsubsection.9.3.9.1) >> +endobj +508 0 obj +(9.3.9.1 Request) +endobj +509 0 obj +<< /S /GoTo /D (subsubsection.9.3.9.2) >> +endobj +512 0 obj +(9.3.9.2 Response) +endobj +513 0 obj +<< /S /GoTo /D (subsection.9.3.10) >> +endobj +516 0 obj +(9.3.10 LSA Close) +endobj +517 0 obj +<< /S /GoTo /D (subsubsection.9.3.10.1) >> +endobj +520 0 obj +(9.3.10.1 Request) +endobj +521 0 obj +<< /S /GoTo /D (subsubsection.9.3.10.2) >> +endobj +524 0 obj +(9.3.10.2 Response) +endobj +525 0 obj +<< /S /GoTo /D (subsection.9.3.11) >> +endobj +528 0 obj +(9.3.11 LSA Lookup SIDS) +endobj +529 0 obj +<< /S /GoTo /D (subsubsection.9.3.11.1) >> +endobj +532 0 obj +(9.3.11.1 Request) +endobj +533 0 obj +<< /S /GoTo /D (subsubsection.9.3.11.2) >> +endobj +536 0 obj +(9.3.11.2 Response) +endobj +537 0 obj +<< /S /GoTo /D (subsection.9.3.12) >> +endobj +540 0 obj +(9.3.12 LSA Lookup Names) +endobj +541 0 obj +<< /S /GoTo /D (subsubsection.9.3.12.1) >> +endobj +544 0 obj +(9.3.12.1 Request) +endobj +545 0 obj +<< /S /GoTo /D (subsubsection.9.3.12.2) >> +endobj +548 0 obj +(9.3.12.2 Response) +endobj +549 0 obj +<< /S /GoTo /D (section.9.4) >> +endobj +552 0 obj +(9.4 NETLOGON rpc Transact Named Pipe) +endobj +553 0 obj +<< /S /GoTo /D (subsection.9.4.1) >> +endobj +556 0 obj +(9.4.1 LSA Request Challenge) +endobj +557 0 obj +<< /S /GoTo /D (subsubsection.9.4.1.1) >> +endobj +560 0 obj +(9.4.1.1 Request) +endobj +561 0 obj +<< /S /GoTo /D (subsubsection.9.4.1.2) >> +endobj +564 0 obj +(9.4.1.2 Response) +endobj +565 0 obj +<< /S /GoTo /D (subsection.9.4.2) >> +endobj +568 0 obj +(9.4.2 LSA Authenticate 2) +endobj +569 0 obj +<< /S /GoTo /D (subsubsection.9.4.2.1) >> +endobj +572 0 obj +(9.4.2.1 Request) +endobj +573 0 obj +<< /S /GoTo /D (subsubsection.9.4.2.2) >> +endobj +576 0 obj +(9.4.2.2 Response) +endobj +577 0 obj +<< /S /GoTo /D (subsection.9.4.3) >> +endobj +580 0 obj +(9.4.3 LSA Server Password Set) +endobj +581 0 obj +<< /S /GoTo /D (subsubsection.9.4.3.1) >> +endobj +584 0 obj +(9.4.3.1 Request) +endobj +585 0 obj +<< /S /GoTo /D (subsubsection.9.4.3.2) >> +endobj +588 0 obj +(9.4.3.2 Response) +endobj +589 0 obj +<< /S /GoTo /D (subsection.9.4.4) >> +endobj +592 0 obj +(9.4.4 LSA SAM Logon) +endobj +593 0 obj +<< /S /GoTo /D (subsubsection.9.4.4.1) >> +endobj +596 0 obj +(9.4.4.1 Request) +endobj +597 0 obj +<< /S /GoTo /D (subsubsection.9.4.4.2) >> +endobj +600 0 obj +(9.4.4.2 Response) +endobj +601 0 obj +<< /S /GoTo /D (subsection.9.4.5) >> +endobj +604 0 obj +(9.4.5 LSA SAM Logoff) +endobj +605 0 obj +<< /S /GoTo /D (subsubsection.9.4.5.1) >> +endobj +608 0 obj +(9.4.5.1 Request) +endobj +609 0 obj +<< /S /GoTo /D (subsubsection.9.4.5.2) >> +endobj +612 0 obj +(9.4.5.2 Response) +endobj +613 0 obj +<< /S /GoTo /D (section.9.5) >> +endobj +616 0 obj +(9.5 \134\134MAILSLOT\134NET\134NTLOGON) +endobj +617 0 obj +<< /S /GoTo /D (subsection.9.5.1) >> +endobj +620 0 obj +(9.5.1 Query for PDC) +endobj +621 0 obj +<< /S /GoTo /D (subsubsection.9.5.1.1) >> +endobj +624 0 obj +(9.5.1.1 Request) +endobj +625 0 obj +<< /S /GoTo /D (subsubsection.9.5.1.2) >> +endobj +628 0 obj +(9.5.1.2 Response) +endobj +629 0 obj +<< /S /GoTo /D (subsection.9.5.2) >> +endobj +632 0 obj +(9.5.2 SAM Logon) +endobj +633 0 obj +<< /S /GoTo /D (subsubsection.9.5.2.1) >> +endobj +636 0 obj +(9.5.2.1 Request) +endobj +637 0 obj +<< /S /GoTo /D (subsubsection.9.5.2.2) >> +endobj +640 0 obj +(9.5.2.2 Response) +endobj +641 0 obj +<< /S /GoTo /D (section.9.6) >> +endobj +644 0 obj +(9.6 SRVSVC Transact Named Pipe) +endobj +645 0 obj +<< /S /GoTo /D (subsection.9.6.1) >> +endobj +648 0 obj +(9.6.1 Net Share Enum) +endobj +649 0 obj +<< /S /GoTo /D (subsubsection.9.6.1.1) >> +endobj +652 0 obj +(9.6.1.1 Request) +endobj +653 0 obj +<< /S /GoTo /D (subsubsection.9.6.1.2) >> +endobj +656 0 obj +(9.6.1.2 Response) +endobj +657 0 obj +<< /S /GoTo /D (subsection.9.6.2) >> +endobj +660 0 obj +(9.6.2 Net Server Get Info) +endobj +661 0 obj +<< /S /GoTo /D (subsubsection.9.6.2.1) >> +endobj +664 0 obj +(9.6.2.1 Request) +endobj +665 0 obj +<< /S /GoTo /D (subsubsection.9.6.2.2) >> +endobj +668 0 obj +(9.6.2.2 Response) +endobj +669 0 obj +<< /S /GoTo /D (section.9.7) >> +endobj +672 0 obj +(9.7 Cryptographic side of NT Domain Authentication) +endobj +673 0 obj +<< /S /GoTo /D (subsection.9.7.1) >> +endobj +676 0 obj +(9.7.1 Definitions) +endobj +677 0 obj +<< /S /GoTo /D (subsection.9.7.2) >> +endobj +680 0 obj +(9.7.2 Protocol) +endobj +681 0 obj +<< /S /GoTo /D (subsection.9.7.3) >> +endobj +684 0 obj +(9.7.3 Comments) +endobj +685 0 obj +<< /S /GoTo /D (section.9.8) >> +endobj +688 0 obj +(9.8 SIDs and RIDs) +endobj +689 0 obj +<< /S /GoTo /D (subsection.9.8.1) >> +endobj +692 0 obj +(9.8.1 Well-known SIDs) +endobj +693 0 obj +<< /S /GoTo /D (subsubsection.9.8.1.1) >> +endobj +696 0 obj +(9.8.1.1 Universal well-known SIDs) +endobj +697 0 obj +<< /S /GoTo /D (subsubsection.9.8.1.2) >> +endobj +700 0 obj +(9.8.1.2 NT well-known SIDs) +endobj +701 0 obj +<< /S /GoTo /D (subsection.9.8.2) >> +endobj +704 0 obj +(9.8.2 Well-known RIDS) +endobj +705 0 obj +<< /S /GoTo /D (subsubsection.9.8.2.1) >> +endobj +708 0 obj +(9.8.2.1 Well-known RID users) +endobj +709 0 obj +<< /S /GoTo /D (subsubsection.9.8.2.2) >> +endobj +712 0 obj +(9.8.2.2 Well-known RID groups) +endobj +713 0 obj +<< /S /GoTo /D (subsubsection.9.8.2.3) >> +endobj +716 0 obj +(9.8.2.3 Well-known RID aliases) +endobj +717 0 obj +<< /S /GoTo /D (chapter.10) >> +endobj +720 0 obj +(10 Samba Printing Internals) +endobj +721 0 obj +<< /S /GoTo /D (section.10.1) >> +endobj +724 0 obj +(10.1 Abstract) +endobj +725 0 obj +<< /S /GoTo /D (section.10.2) >> +endobj +728 0 obj +(10.2 Printing Interface to Various Back ends) +endobj +729 0 obj +<< /S /GoTo /D (section.10.3) >> +endobj +732 0 obj +(10.3 Print Queue TDB's) +endobj +733 0 obj +<< /S /GoTo /D (section.10.4) >> +endobj +736 0 obj +(10.4 ChangeID and Client Caching of Printer Information) +endobj +737 0 obj +<< /S /GoTo /D (section.10.5) >> +endobj +740 0 obj +(10.5 Windows NT/2K Printer Change Notify) +endobj +741 0 obj +<< /S /GoTo /D (chapter.11) >> +endobj +744 0 obj +(11 Samba WINS Internals) +endobj +745 0 obj +<< /S /GoTo /D (section.11.1) >> +endobj +748 0 obj +(11.1 WINS Failover) +endobj +749 0 obj +<< /S /GoTo /D (chapter.12) >> +endobj +752 0 obj +(12 The Upcoming SAM System) +endobj +753 0 obj +<< /S /GoTo /D (section.12.1) >> +endobj +756 0 obj +(12.1 Security in the 'new SAM') +endobj +757 0 obj +<< /S /GoTo /D (section.12.2) >> +endobj +760 0 obj +(12.2 Standalone from UNIX) +endobj +761 0 obj +<< /S /GoTo /D (section.12.3) >> +endobj +764 0 obj +(12.3 Handles and Races in the new SAM) +endobj +765 0 obj +<< /S /GoTo /D (section.12.4) >> +endobj +768 0 obj +(12.4 Layers) +endobj +769 0 obj +<< /S /GoTo /D (subsection.12.4.1) >> +endobj +772 0 obj +(12.4.1 Application) +endobj +773 0 obj +<< /S /GoTo /D (subsection.12.4.2) >> +endobj +776 0 obj +(12.4.2 SAM Interface) +endobj +777 0 obj +<< /S /GoTo /D (subsection.12.4.3) >> +endobj +780 0 obj +(12.4.3 SAM Modules) +endobj +781 0 obj +<< /S /GoTo /D (section.12.5) >> +endobj +784 0 obj +(12.5 SAM Modules) +endobj +785 0 obj +<< /S /GoTo /D (subsection.12.5.1) >> +endobj +788 0 obj +(12.5.1 Special Module: sam\137passdb) +endobj +789 0 obj +<< /S /GoTo /D (subsection.12.5.2) >> +endobj +792 0 obj +(12.5.2 sam\137ads) +endobj +793 0 obj +<< /S /GoTo /D (section.12.6) >> +endobj +796 0 obj +(12.6 Memory Management) +endobj +797 0 obj +<< /S /GoTo /D (section.12.7) >> +endobj +800 0 obj +(12.7 Testing) +endobj +801 0 obj +<< /S /GoTo /D (chapter.13) >> +endobj +804 0 obj +(13 LanMan and NT Password Encryption) +endobj +805 0 obj +<< /S /GoTo /D (section.13.1) >> +endobj +808 0 obj +(13.1 Introduction) +endobj +809 0 obj +<< /S /GoTo /D (section.13.2) >> +endobj +812 0 obj +(13.2 How does it work?) +endobj +813 0 obj +<< /S /GoTo /D (section.13.3) >> +endobj +816 0 obj +(13.3 The smbpasswd file) +endobj +817 0 obj +<< /S /GoTo /D (chapter.14) >> +endobj +820 0 obj +(14 Modules) +endobj +821 0 obj +<< /S /GoTo /D (section.14.1) >> +endobj +824 0 obj +(14.1 Advantages) +endobj +825 0 obj +<< /S /GoTo /D (section.14.2) >> +endobj +828 0 obj +(14.2 Loading modules) +endobj +829 0 obj +<< /S /GoTo /D (subsection.14.2.1) >> +endobj +832 0 obj +(14.2.1 Static modules) +endobj +833 0 obj +<< /S /GoTo /D (subsection.14.2.2) >> +endobj +836 0 obj +(14.2.2 Shared modules) +endobj +837 0 obj +<< /S /GoTo /D (section.14.3) >> +endobj +840 0 obj +(14.3 Writing modules) +endobj +841 0 obj +<< /S /GoTo /D (subsection.14.3.1) >> +endobj +844 0 obj +(14.3.1 Static/Shared selection in configure.in) +endobj +845 0 obj +<< /S /GoTo /D (chapter.15) >> +endobj +848 0 obj +(15 RPC Pluggable Modules) +endobj +849 0 obj +<< /S /GoTo /D (section.15.1) >> +endobj +852 0 obj +(15.1 About) +endobj +853 0 obj +<< /S /GoTo /D (section.15.2) >> +endobj +856 0 obj +(15.2 General Overview) +endobj +857 0 obj +<< /S /GoTo /D (chapter.16) >> +endobj +860 0 obj +(16 Notes to packagers) +endobj +861 0 obj +<< /S /GoTo /D (section.16.1) >> +endobj +864 0 obj +(16.1 Versioning) +endobj +865 0 obj +<< /S /GoTo /D (section.16.2) >> +endobj +868 0 obj +(16.2 Modules) +endobj +869 0 obj +<< /S /GoTo /D [870 0 R /Fit ] >> +endobj +872 0 obj << +/Length 241 +/Filter /FlateDecode +>> +stream +xڍJ19&g$9'snEhX|{']KA! !d Ť,ӮCɢ"rQaJ{9)0+#%I]z4A$9"u`gAv=s_vxkC .>^փ{wM= 5> endobj +873 0 obj << +/D [870 0 R /XYZ 85.039 786.531 null] +>> endobj +874 0 obj << +/D [870 0 R /XYZ 85.039 766.606 null] +>> endobj +871 0 obj << +/Font << /F20 877 0 R /F21 880 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +884 0 obj << +/Length 1042 +/Filter /FlateDecode +>> +stream +xڭVK6-4{Kf`S,٢m$HtP׏ (V$g8Ggʙ?9 :YN̶`y#68<O͵Yϛ-,Isϖ,?׫E[ߖS>Wd|<\E(Yr%cd$+͵اe45g1<Ř GPX> ֚}$^{i˯KL .#?S\`&JY 3k&g5Q:֮n[>< .Bh;o’0,p?dߴ= u)GbT[]ҖC` + }p=gg`? 퀡ݘ$Ϫ/nfK3h䂽(dzܮ +bL1?Cs>JTξy.瞆*e|z -:8拴d ,z<-57 +=LA33O/̎ $YZ : Ѻ@R[ù:cܫd+O:-wu%Bx[҉v}B?i+/η!nvXTǞA ,HЎ TW$HCoA+s_,JnɪJ:yvqaZIODPqӧؖ(q\n"S'^pg¡6үbxo}>QMOVWRQT)yj[UaiAO a ́-Tg7:Bsԇͱ 14uz5YPQjMqICEAa$餵FzFQ%kP3ăF"29Z-ߣ6zJ[R`Q c854K_I +^;+j}~O+^$8`8ȫ^QKQ5^~endstream +endobj +883 0 obj << +/Type /Page +/Contents 884 0 R +/Resources 882 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 881 0 R +/Annots [ 897 0 R 901 0 R 902 0 R 904 0 R ] +>> endobj +897 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [428.769 653.951 539.579 665.943] +/Subtype/Link/A<> +>> endobj +901 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [84.043 640.401 108.944 652.394] +/Subtype/Link/A<> +>> endobj +902 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [227.588 640.401 309.793 652.394] +/Subtype/Link/A<> +>> endobj +904 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [97.376 584.489 299.821 596.481] +/Subtype/Link/A<> +>> endobj +885 0 obj << +/D [883 0 R /XYZ 85.039 786.531 null] +>> endobj +889 0 obj << +/D [883 0 R /XYZ 85.039 740.382 null] +>> endobj +896 0 obj << +/D [883 0 R /XYZ 85.039 709.447 null] +>> endobj +903 0 obj << +/D [883 0 R /XYZ 85.039 626.133 null] +>> endobj +882 0 obj << +/Font << /F35 888 0 R /F36 892 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +907 0 obj << +/Length 1430 +/Filter /FlateDecode +>> +stream +xIs8 +ƣ}9BHg6Kw0K1c;%6LR ؎oyYP_X:\0bjF}Jjt:C> l pn8a;Hu܋iQ2~t.˿N/)6d>V='̆CG.zuI +:tHD4qw:0a}mws^xL ҧV=35 +s}6YݍH_w3C_1'cW[X~%.6PBZ6`ro/.B{u +Dʃ>wu2Kg~5UvMP-6<ĕ; 6Z2䮲_L<#@]yƊW"JO|w:dR]'xz LiĽ8 {<7 <,@~)NfPfڑCI2a36Mۼx ~3xFÝ$dWǑj M to2zm!"py鎴y'8d3}P3M+ØBLv!Vra30Fzq[l l1B >@LbiÃVw;0i1;^񀝠x1DЍszIe8 +&Gq7t(\N.3t&a5[YxKSf$+? ρFϊ0lby%]c 4Ӹ}PEZ,.%FZRIӳWWv:32b~U1k{cld(eUQ˶ΪK8?QlM%xbt7@|/rl+(EldG9ݠ'HlT,I() +ǐ{c̘dҺdUq%vUHaV@Ȝ_{_%XPKuG&AREQ\G/̓U| Jonfp&|{쎦 dUM8c{gEU2nT $"KhrrHǣ9(º 1{ݸͷF0q֫{l%_Džmcݵkc?BWQ endstream +endobj +906 0 obj << +/Type /Page +/Contents 907 0 R +/Resources 905 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 881 0 R +/Annots [ 910 0 R 911 0 R 912 0 R 913 0 R 914 0 R 915 0 R 916 0 R 917 0 R 918 0 R 919 0 R 920 0 R 921 0 R 922 0 R 923 0 R 924 0 R 925 0 R 926 0 R 927 0 R 928 0 R 929 0 R 930 0 R 931 0 R 932 0 R 933 0 R 934 0 R 935 0 R 936 0 R 937 0 R 938 0 R 939 0 R 940 0 R 941 0 R 942 0 R 943 0 R 944 0 R 945 0 R 946 0 R 947 0 R 948 0 R 949 0 R ] +>> endobj +910 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [531.586 631.159 539.579 640.727] +/Subtype /Link +/A << /S /GoTo /D (chapter.1) >> +>> endobj +911 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [532.132 617.61 539.579 626.632] +/Subtype /Link +/A << /S /GoTo /D (section.1.1) >> +>> endobj +912 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [532.132 604.06 539.579 613.083] +/Subtype /Link +/A << /S /GoTo /D (section.1.2) >> +>> endobj +913 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [532.132 590.511 539.579 599.534] +/Subtype /Link +/A << /S /GoTo /D (section.1.3) >> +>> endobj +914 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 566.053 539.579 575.621] +/Subtype /Link +/A << /S /GoTo /D (chapter.2) >> +>> endobj +915 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 552.504 539.579 561.527] +/Subtype /Link +/A << /S /GoTo /D (section.2.1) >> +>> endobj +916 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 538.955 539.579 547.977] +/Subtype /Link +/A << /S /GoTo /D (section.2.2) >> +>> endobj +917 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 525.405 539.579 534.428] +/Subtype /Link +/A << /S /GoTo /D (section.2.3) >> +>> endobj +918 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 511.856 539.579 520.879] +/Subtype /Link +/A << /S /GoTo /D (section.2.4) >> +>> endobj +919 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 498.307 539.579 507.33] +/Subtype /Link +/A << /S /GoTo /D (section.2.5) >> +>> endobj +920 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 473.849 539.579 483.417] +/Subtype /Link +/A << /S /GoTo /D (chapter.3) >> +>> endobj +921 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 460.299 539.579 469.322] +/Subtype /Link +/A << /S /GoTo /D (section.3.1) >> +>> endobj +922 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 446.75 539.579 455.773] +/Subtype /Link +/A << /S /GoTo /D (section.3.2) >> +>> endobj +923 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 433.201 539.579 442.224] +/Subtype /Link +/A << /S /GoTo /D (section.3.3) >> +>> endobj +924 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 419.652 539.579 428.675] +/Subtype /Link +/A << /S /GoTo /D (section.3.4) >> +>> endobj +925 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 406.103 539.579 415.125] +/Subtype /Link +/A << /S /GoTo /D (section.3.5) >> +>> endobj +926 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 392.553 539.579 401.576] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.5.1) >> +>> endobj +927 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 379.004 539.579 388.027] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.5.2) >> +>> endobj +928 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 365.455 539.579 374.478] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.5.3) >> +>> endobj +929 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 340.997 539.579 350.565] +/Subtype /Link +/A << /S /GoTo /D (chapter.4) >> +>> endobj +930 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 316.538 539.579 326.107] +/Subtype /Link +/A << /S /GoTo /D (chapter.5) >> +>> endobj +931 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 302.989 539.579 312.012] +/Subtype /Link +/A << /S /GoTo /D (section.5.1) >> +>> endobj +932 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 289.44 539.579 298.463] +/Subtype /Link +/A << /S /GoTo /D (section.5.2) >> +>> endobj +933 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 275.891 539.579 284.914] +/Subtype /Link +/A << /S /GoTo /D (section.5.3) >> +>> endobj +934 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 262.342 539.579 271.364] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.1) >> +>> endobj +935 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 248.792 539.579 257.815] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.2) >> +>> endobj +936 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 235.243 539.579 244.266] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.3) >> +>> endobj +937 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 221.694 539.579 230.717] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.4) >> +>> endobj +938 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 208.145 539.579 217.168] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.5) >> +>> endobj +939 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 194.596 539.579 203.618] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.6) >> +>> endobj +940 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 181.046 539.579 190.069] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.7) >> +>> endobj +941 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 167.497 539.579 176.52] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.8) >> +>> endobj +942 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 153.948 539.579 162.971] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.9) >> +>> endobj +943 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 140.399 539.579 149.422] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.10) >> +>> endobj +944 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 126.85 539.579 135.872] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.11) >> +>> endobj +945 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 113.3 539.579 122.323] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.12) >> +>> endobj +946 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 99.751 539.579 108.774] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.13) >> +>> endobj +947 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 86.202 539.579 95.225] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.14) >> +>> endobj +948 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 72.653 539.579 81.676] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.3.15) >> +>> endobj +949 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 59.104 539.579 68.127] +/Subtype /Link +/A << /S /GoTo /D (section.5.4) >> +>> endobj +908 0 obj << +/D [906 0 R /XYZ 85.039 786.531 null] +>> endobj +909 0 obj << +/D [906 0 R /XYZ 85.039 656.613 null] +>> endobj +905 0 obj << +/Font << /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +952 0 obj << +/Length 2006 +/Filter /FlateDecode +>> +stream +xI{8 Z&i>Ri& S2ߏ>I5)f3XzcīsYA`P7Wuj́Sﻵ?8nٖg{f&]#WfT;ݤA-ڷzO3c[Zƌlpe A_n|3mHx#mLLfڌ 0B<==0[}}8a`(Ӷze5YLKď{e?7 +nr4Wq6g Wf+Z8`c58p)P ѨZ4Tg% QC6K#kwߘ-nBTr^0^o9 .Mع s%wcufr`T##?S!yG9M_}]ѽؿ6 #V秳ϩ2^:M`0, +Bձy֩ / eR()(bi9DG8LNeWTO~ƪRQ_= +8b]d["G+M]o6Ӱ< +/N3pB+GlisMkH;TJ;>#AQbZ]0wV'X dpDC=\~^ sm~ ~ɡ ?u"%K\=kz"2R,0|@m~/}U%Q[G[%:Ӊ.5?Sk_?V x^<M@'꼱 NӠ݉"D[lh1I~($=F+@WϒsAՃ:n#,%vUI:wd] ť=ApY.k[ + !TXbǟvg^ܓ2[PזT#YH ͗?IP2Nl Ћ_Qׁe0ȇXN_"!q%yߟwB/J+I  <=F +nդκ]0qSq_BUTFut~:P.ճ JTNyrVqi"9Q2dy:,+ +Gi%>;ZaڹJRȚ +Y3TTt8~BLh!nTv>׫z^wbZyhl 8Fv~ېzQWhue;U>RD&. 1(q@Y%/$F0v'Jt.3-BW3+\yi6ߺ?7a;KzlcXjb53\ ](89 Z#/D. ,,ڞs?ÝZmOx~\+;\P;$ QAtF*=.x?+j^$\m 7$rRwjǢbhL4(Hendstream +endobj +951 0 obj << +/Type /Page +/Contents 952 0 R +/Resources 950 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 881 0 R +/Annots [ 957 0 R 958 0 R 959 0 R 960 0 R 961 0 R 962 0 R 963 0 R 964 0 R 965 0 R 966 0 R 967 0 R 968 0 R 969 0 R 970 0 R 971 0 R 972 0 R 973 0 R 974 0 R 975 0 R 976 0 R 977 0 R 978 0 R 979 0 R 980 0 R 981 0 R 982 0 R 983 0 R 984 0 R 985 0 R 986 0 R 987 0 R 988 0 R 989 0 R 990 0 R 991 0 R 992 0 R 993 0 R 994 0 R 995 0 R 996 0 R 997 0 R 998 0 R 999 0 R 1000 0 R 1001 0 R 1002 0 R 1003 0 R 1004 0 R 1005 0 R ] +>> endobj +957 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 754.651 539.579 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.4.1) >> +>> endobj +958 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 741.102 539.579 750.125] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.4.2) >> +>> endobj +959 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 727.553 539.579 736.575] +/Subtype /Link +/A << /S /GoTo /D (section.5.5) >> +>> endobj +960 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 703.094 539.579 712.663] +/Subtype /Link +/A << /S /GoTo /D (chapter.6) >> +>> endobj +961 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 689.545 539.579 698.568] +/Subtype /Link +/A << /S /GoTo /D (section.6.1) >> +>> endobj +962 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 675.996 539.579 685.019] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.1.1) >> +>> endobj +963 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 662.447 539.579 671.469] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.1.2) >> +>> endobj +964 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 648.897 539.579 657.92] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.1.3) >> +>> endobj +965 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 635.348 539.579 644.371] +/Subtype /Link +/A << /S /GoTo /D (section.6.2) >> +>> endobj +966 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 621.799 539.579 630.822] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.2.1) >> +>> endobj +967 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 597.341 539.579 606.909] +/Subtype /Link +/A << /S /GoTo /D (chapter.7) >> +>> endobj +968 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 583.792 539.579 592.814] +/Subtype /Link +/A << /S /GoTo /D (section.7.1) >> +>> endobj +969 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 570.242 539.579 579.265] +/Subtype /Link +/A << /S /GoTo /D (section.7.2) >> +>> endobj +970 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 556.693 539.579 565.716] +/Subtype /Link +/A << /S /GoTo /D (section.7.3) >> +>> endobj +971 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 543.144 539.579 552.167] +/Subtype /Link +/A << /S /GoTo /D (section.7.4) >> +>> endobj +972 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 529.595 539.579 538.618] +/Subtype /Link +/A << /S /GoTo /D (section.7.5) >> +>> endobj +973 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 516.046 539.579 525.068] +/Subtype /Link +/A << /S /GoTo /D (section.7.6) >> +>> endobj +974 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 502.496 539.579 511.519] +/Subtype /Link +/A << /S /GoTo /D (section.7.7) >> +>> endobj +975 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 488.947 539.579 497.97] +/Subtype /Link +/A << /S /GoTo /D (section.7.8) >> +>> endobj +976 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 475.398 539.579 484.421] +/Subtype /Link +/A << /S /GoTo /D (section.7.9) >> +>> endobj +977 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 450.94 539.579 460.508] +/Subtype /Link +/A << /S /GoTo /D (chapter.8) >> +>> endobj +978 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 426.481 539.579 436.05] +/Subtype /Link +/A << /S /GoTo /D (chapter.9) >> +>> endobj +979 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 412.932 539.579 421.955] +/Subtype /Link +/A << /S /GoTo /D (section.9.1) >> +>> endobj +980 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 399.383 539.579 408.406] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.1.1) >> +>> endobj +981 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 385.834 539.579 394.857] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.1.2) >> +>> endobj +982 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 372.285 539.579 381.307] +/Subtype /Link +/A << /S /GoTo /D (section.9.2) >> +>> endobj +983 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 358.735 539.579 367.758] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.2.1) >> +>> endobj +984 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 345.186 539.579 354.209] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.2.2) >> +>> endobj +985 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 331.637 539.579 340.66] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.2.1) >> +>> endobj +986 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 318.088 539.579 327.111] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.2.2) >> +>> endobj +987 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 304.539 539.579 313.561] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.2.3) >> +>> endobj +988 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 290.989 539.579 300.012] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.1) >> +>> endobj +989 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 277.44 539.579 286.463] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.2) >> +>> endobj +990 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 263.891 539.579 272.914] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.3) >> +>> endobj +991 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 250.342 539.579 259.365] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.4) >> +>> endobj +992 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 236.793 539.579 245.815] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.5) >> +>> endobj +993 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 223.243 539.579 232.266] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.6) >> +>> endobj +994 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 209.694 539.579 218.717] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.7) >> +>> endobj +995 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 196.145 539.579 205.168] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.8) >> +>> endobj +996 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 182.596 539.579 191.619] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.9) >> +>> endobj +997 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 169.047 539.579 178.069] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.10) >> +>> endobj +998 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 155.497 539.579 164.52] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.11) >> +>> endobj +999 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 141.948 539.579 150.971] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.12) >> +>> endobj +1000 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 128.399 539.579 137.422] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.13) >> +>> endobj +1001 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 114.85 539.579 123.873] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.14) >> +>> endobj +1002 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 101.301 539.579 110.323] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.15) >> +>> endobj +1003 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 87.751 539.579 96.774] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.16) >> +>> endobj +1004 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 74.202 539.579 83.225] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.17) >> +>> endobj +1005 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 60.653 539.579 69.676] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.18) >> +>> endobj +953 0 obj << +/D [951 0 R /XYZ 85.039 786.531 null] +>> endobj +950 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1008 0 obj << +/Length 1848 +/Filter /FlateDecode +>> +stream +x][s8~W3EՒ$MII݇.8\C(Mfl};GGAMPS0lrFPs0n:r@lR7޾g P6wJu:h#1klsP@lՍ>6 R42HA=jci9@B}B ͞ ,Q vuz>`ݑ^5nw!YZQ%o(vmlMyb0_$QZMqK iϠA %PW1P7DNa ; *r.XF(*u-^< /^Y#%Vg mPS =l\ +4ծ84k1_8+v-m9n)4uvcY^Z֙]i rI*6Ùed.!RvvlEw8dE ެzJ/qwⴃ$WN ldeٿzjv ]a(.fƄMv Z ʁD&.˗Rme)|1q*5]v'q5>Ku5w 3BP(kq$ő3h}PFU˶LI~r{^PPYY秚J5 OsTωK'!|-P_CٴŦ + H?Jv5"qSO: "XOo JI:\ο뺒y,uct{f(3Pȭ`ޱ!Ofkeq80i8*yCF^#HI ]Aj(,.%8-@WZId[NȎHidcߵ#f& u 5mkd.S4N )ePLsw FƖ#5BD<6>D^AC*`K:ܢ~p-5S=;]HeSM$eU'áy5sp{FlKBQٻxRJφ2Wqtɸ|x=T`QATGRAy76&O#B/iVMIRKDo2-×p9>21ci):7laaœo-˗Fq׀(XIvgiON;*di)/6,p\;k%/jE:}*T:˗-ZɽVJ+EQ+be8wr[H{TS]o.ƱhRx8^ 먅kaepCnE&% ^*k{%Xp>*LZy:jb~NzZ^/+l[p5/UKT˫6ȽצwySո +#XpqodIn8Nq: {u> endobj +1010 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 754.651 539.579 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.19) >> +>> endobj +1011 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 741.102 539.579 750.125] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.20) >> +>> endobj +1012 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 727.553 539.579 736.575] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.21) >> +>> endobj +1013 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 714.003 539.579 723.026] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.22) >> +>> endobj +1014 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 700.454 539.579 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.23) >> +>> endobj +1015 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 686.905 539.579 695.928] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.24) >> +>> endobj +1016 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 673.356 539.579 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.25) >> +>> endobj +1017 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 659.807 539.579 668.829] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.26) >> +>> endobj +1018 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 646.257 539.579 655.28] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.27) >> +>> endobj +1019 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 632.708 539.579 641.731] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.28) >> +>> endobj +1020 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 619.159 539.579 628.182] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.29) >> +>> endobj +1021 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 605.61 539.579 614.633] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.2.3.30) >> +>> endobj +1022 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 592.061 539.579 601.083] +/Subtype /Link +/A << /S /GoTo /D (section.9.3) >> +>> endobj +1023 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 578.511 539.579 587.534] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.1) >> +>> endobj +1024 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 564.962 539.579 573.985] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.2) >> +>> endobj +1025 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 551.413 539.579 560.436] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.1) >> +>> endobj +1026 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 537.864 539.579 546.887] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.2) >> +>> endobj +1027 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 524.315 539.579 533.337] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.3) >> +>> endobj +1028 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 510.765 539.579 519.788] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.4) >> +>> endobj +1029 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 497.216 539.579 506.239] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.5) >> +>> endobj +1030 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 483.667 539.579 492.69] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.6) >> +>> endobj +1031 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 470.118 539.579 479.141] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.7) >> +>> endobj +1032 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 456.569 539.579 465.591] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.2.8) >> +>> endobj +1033 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 443.019 539.579 452.042] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.3) >> +>> endobj +1034 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 429.47 539.579 438.493] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.4) >> +>> endobj +1035 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 415.921 539.579 424.944] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.5) >> +>> endobj +1036 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 402.372 539.579 411.395] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.6) >> +>> endobj +1037 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 388.823 539.579 397.845] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.6.1) >> +>> endobj +1038 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 375.273 539.579 384.296] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.6.2) >> +>> endobj +1039 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 361.724 539.579 370.747] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.7) >> +>> endobj +1040 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 348.175 539.579 357.198] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.7.1) >> +>> endobj +1041 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 334.626 539.579 343.649] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.7.2) >> +>> endobj +1042 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 321.077 539.579 330.099] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.8) >> +>> endobj +1043 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 307.527 539.579 316.55] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.8.1) >> +>> endobj +1044 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 293.978 539.579 303.001] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.8.2) >> +>> endobj +1045 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 280.429 539.579 289.452] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.9) >> +>> endobj +1046 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 266.88 539.579 275.903] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.9.1) >> +>> endobj +1047 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 253.331 539.579 262.354] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.9.2) >> +>> endobj +1048 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 239.781 539.579 248.804] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.10) >> +>> endobj +1049 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 226.232 539.579 235.255] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.10.1) >> +>> endobj +1050 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 212.683 539.579 221.706] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.10.2) >> +>> endobj +1051 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 199.134 539.579 208.157] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.11) >> +>> endobj +1052 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 185.585 539.579 194.608] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.11.1) >> +>> endobj +1053 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 172.036 539.579 181.058] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.11.2) >> +>> endobj +1054 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 158.486 539.579 167.509] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.12) >> +>> endobj +1055 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 144.937 539.579 153.96] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.12.1) >> +>> endobj +1056 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 131.388 539.579 140.411] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.3.12.2) >> +>> endobj +1057 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 117.839 539.579 126.862] +/Subtype /Link +/A << /S /GoTo /D (section.9.4) >> +>> endobj +1058 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 104.29 539.579 113.312] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.1) >> +>> endobj +1059 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 90.74 539.579 99.763] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.1.1) >> +>> endobj +1060 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 77.191 539.579 86.214] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.1.2) >> +>> endobj +1061 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 63.642 539.579 72.665] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.2) >> +>> endobj +1009 0 obj << +/D [1007 0 R /XYZ 85.039 786.531 null] +>> endobj +1006 0 obj << +/Font << /F58 956 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1064 0 obj << +/Length 1717 +/Filter /FlateDecode +>> +stream +x]w8+|pa@\NM7um&6oNHIMD'eGΌ@.˂/=G0nsWNmr^zkz+dNޥ7jĦ#}{ozs=j|6Eټ h\0GpVƧ}7?Kg|9v ɍD)Vo.ag%t!0*y*)JT%Y\[R)nI};}-iLHxZ6-p}fY9\U}8RbrM +Ӵ-:[n]B1-nۘb/mAāsf\hKZehq҆ `}I&w:26#OŷxDžX{nB/l|,{dV&P.ZM;ϣA`H)KM'^ɤ;YyUЉrM^Y9QB0|>\6^okICE9=d%#tLV*z/>Syn4QS-v+`ԨAֵ;#6#;KV#&^<f!⾖I<'e1ʥJ8*jMbr WbL?X+N̯bK8h1v#H_ ]3ɵVb|#SCV(xgH -wY ˝5;&ٱvkaRLx*CCm!\-F#~&*dM1n`t<%rqs/&p!ؐbDQ7}4LP YƳq5qQ+ `datYC JYD_{1K_k]&vَlwkrM} *B('ۣD>?) \/S6[8ٸX2 lЀ.b3\!+OJ$N +9º>/ʜHQ]`xAJ]@<+xp}4[2л8t|2au4:Mٿf@';BɕFnXf*LeW6g0Yw}@2W9 1r &6}vfOx+/ -"w!endstream +endobj +1063 0 obj << +/Type /Page +/Contents 1064 0 R +/Resources 1062 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 881 0 R +/Annots [ 1066 0 R 1067 0 R 1068 0 R 1069 0 R 1070 0 R 1071 0 R 1072 0 R 1073 0 R 1074 0 R 1075 0 R 1076 0 R 1080 0 R 1081 0 R 1082 0 R 1083 0 R 1084 0 R 1085 0 R 1086 0 R 1087 0 R 1088 0 R 1089 0 R 1090 0 R 1091 0 R 1092 0 R 1093 0 R 1094 0 R 1095 0 R 1096 0 R 1097 0 R 1098 0 R 1099 0 R 1100 0 R 1101 0 R 1102 0 R 1103 0 R 1104 0 R 1105 0 R 1106 0 R 1107 0 R 1108 0 R 1109 0 R 1110 0 R 1111 0 R 1112 0 R 1113 0 R 1114 0 R 1115 0 R 1116 0 R 1117 0 R 1118 0 R ] +>> endobj +1066 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 754.651 539.579 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.2.1) >> +>> endobj +1067 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 741.102 539.579 750.125] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.2.2) >> +>> endobj +1068 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 727.553 539.579 736.575] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.3) >> +>> endobj +1069 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 714.003 539.579 723.026] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.3.1) >> +>> endobj +1070 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 700.454 539.579 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.3.2) >> +>> endobj +1071 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 686.905 539.579 695.928] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.4) >> +>> endobj +1072 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 673.356 539.579 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.4.1) >> +>> endobj +1073 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 659.807 539.579 668.829] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.4.2) >> +>> endobj +1074 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 646.257 539.579 655.28] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.5) >> +>> endobj +1075 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 632.708 539.579 641.731] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.5.1) >> +>> endobj +1076 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 619.159 539.579 628.182] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.4.5.2) >> +>> endobj +1080 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 605.61 539.579 614.633] +/Subtype /Link +/A << /S /GoTo /D (section.9.5) >> +>> endobj +1081 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 592.061 539.579 601.083] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.5.1) >> +>> endobj +1082 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 578.511 539.579 587.534] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.5.1.1) >> +>> endobj +1083 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 564.962 539.579 573.985] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.5.1.2) >> +>> endobj +1084 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 551.413 539.579 560.436] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.5.2) >> +>> endobj +1085 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 537.864 539.579 546.887] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.5.2.1) >> +>> endobj +1086 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 524.315 539.579 533.337] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.5.2.2) >> +>> endobj +1087 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 510.765 539.579 519.788] +/Subtype /Link +/A << /S /GoTo /D (section.9.6) >> +>> endobj +1088 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 497.216 539.579 506.239] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.6.1) >> +>> endobj +1089 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 483.667 539.579 492.69] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.6.1.1) >> +>> endobj +1090 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 470.118 539.579 479.141] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.6.1.2) >> +>> endobj +1091 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 456.569 539.579 465.591] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.6.2) >> +>> endobj +1092 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 443.019 539.579 452.042] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.6.2.1) >> +>> endobj +1093 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 429.47 539.579 438.493] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.6.2.2) >> +>> endobj +1094 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 415.921 539.579 424.944] +/Subtype /Link +/A << /S /GoTo /D (section.9.7) >> +>> endobj +1095 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 402.372 539.579 411.395] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.7.1) >> +>> endobj +1096 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 388.823 539.579 397.845] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.7.2) >> +>> endobj +1097 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 375.273 539.579 384.296] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.7.3) >> +>> endobj +1098 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 361.724 539.579 370.747] +/Subtype /Link +/A << /S /GoTo /D (section.9.8) >> +>> endobj +1099 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 348.175 539.579 357.198] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.8.1) >> +>> endobj +1100 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 334.626 539.579 343.649] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.8.1.1) >> +>> endobj +1101 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 321.077 539.579 330.099] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.8.1.2) >> +>> endobj +1102 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 307.527 539.579 316.55] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.8.2) >> +>> endobj +1103 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 293.978 539.579 303.001] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.8.2.1) >> +>> endobj +1104 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 280.429 539.579 289.452] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.8.2.2) >> +>> endobj +1105 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 266.88 539.579 275.903] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.8.2.3) >> +>> endobj +1106 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 242.422 539.579 251.99] +/Subtype /Link +/A << /S /GoTo /D (chapter.10) >> +>> endobj +1107 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 228.872 539.579 237.895] +/Subtype /Link +/A << /S /GoTo /D (section.10.1) >> +>> endobj +1108 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 215.323 539.579 224.346] +/Subtype /Link +/A << /S /GoTo /D (section.10.2) >> +>> endobj +1109 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 201.774 539.579 210.797] +/Subtype /Link +/A << /S /GoTo /D (section.10.3) >> +>> endobj +1110 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 188.225 539.579 197.248] +/Subtype /Link +/A << /S /GoTo /D (section.10.4) >> +>> endobj +1111 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 174.676 539.579 183.698] +/Subtype /Link +/A << /S /GoTo /D (section.10.5) >> +>> endobj +1112 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 150.217 539.579 159.786] +/Subtype /Link +/A << /S /GoTo /D (chapter.11) >> +>> endobj +1113 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 136.668 539.579 145.691] +/Subtype /Link +/A << /S /GoTo /D (section.11.1) >> +>> endobj +1114 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 112.21 539.579 121.778] +/Subtype /Link +/A << /S /GoTo /D (chapter.12) >> +>> endobj +1115 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 98.661 539.579 107.683] +/Subtype /Link +/A << /S /GoTo /D (section.12.1) >> +>> endobj +1116 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 85.111 539.579 94.134] +/Subtype /Link +/A << /S /GoTo /D (section.12.2) >> +>> endobj +1117 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 71.562 539.579 80.585] +/Subtype /Link +/A << /S /GoTo /D (section.12.3) >> +>> endobj +1118 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 58.013 539.579 67.036] +/Subtype /Link +/A << /S /GoTo /D (section.12.4) >> +>> endobj +1065 0 obj << +/D [1063 0 R /XYZ 85.039 786.531 null] +>> endobj +1062 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F43 1079 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1121 0 obj << +/Length 1144 +/Filter /FlateDecode +>> +stream +xZMsHWpfe˛JMEY'Ve0YKhA*~AeȖa*3 h^w(1(BEEF%{iԓjSz/(1Jb{oAULnYnUuzMBIxz_R/zףD[޸' J +w~;}\I^ղP2NPPb\nMZIXj)4`(Mf#xP3 T ι wZr*4ejk,z|!89.ކEqئI)MtCiSeZT8L7\o^(;:zG)-0f*;t]keendstream +endobj +1120 0 obj << +/Type /Page +/Contents 1121 0 R +/Resources 1119 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1148 0 R +/Annots [ 1123 0 R 1124 0 R 1125 0 R 1126 0 R 1127 0 R 1128 0 R 1129 0 R 1130 0 R 1131 0 R 1132 0 R 1133 0 R 1134 0 R 1135 0 R 1136 0 R 1137 0 R 1138 0 R 1139 0 R 1140 0 R 1141 0 R 1142 0 R 1143 0 R 1144 0 R 1145 0 R 1146 0 R 1147 0 R ] +>> endobj +1123 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 754.651 539.579 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsection.12.4.1) >> +>> endobj +1124 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 741.102 539.579 750.125] +/Subtype /Link +/A << /S /GoTo /D (subsection.12.4.2) >> +>> endobj +1125 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 727.553 539.579 736.575] +/Subtype /Link +/A << /S /GoTo /D (subsection.12.4.3) >> +>> endobj +1126 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 714.003 539.579 723.026] +/Subtype /Link +/A << /S /GoTo /D (section.12.5) >> +>> endobj +1127 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 700.454 539.579 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsection.12.5.1) >> +>> endobj +1128 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 686.905 539.579 695.928] +/Subtype /Link +/A << /S /GoTo /D (subsection.12.5.2) >> +>> endobj +1129 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 673.356 539.579 682.379] +/Subtype /Link +/A << /S /GoTo /D (section.12.6) >> +>> endobj +1130 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 659.807 539.579 668.829] +/Subtype /Link +/A << /S /GoTo /D (section.12.7) >> +>> endobj +1131 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 635.348 539.579 644.917] +/Subtype /Link +/A << /S /GoTo /D (chapter.13) >> +>> endobj +1132 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 621.799 539.579 630.822] +/Subtype /Link +/A << /S /GoTo /D (section.13.1) >> +>> endobj +1133 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 608.25 539.579 617.273] +/Subtype /Link +/A << /S /GoTo /D (section.13.2) >> +>> endobj +1134 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 594.701 539.579 603.724] +/Subtype /Link +/A << /S /GoTo /D (section.13.3) >> +>> endobj +1135 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 570.242 539.579 579.811] +/Subtype /Link +/A << /S /GoTo /D (chapter.14) >> +>> endobj +1136 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 556.693 539.579 565.716] +/Subtype /Link +/A << /S /GoTo /D (section.14.1) >> +>> endobj +1137 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 543.144 539.579 552.167] +/Subtype /Link +/A << /S /GoTo /D (section.14.2) >> +>> endobj +1138 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 529.595 539.579 538.618] +/Subtype /Link +/A << /S /GoTo /D (subsection.14.2.1) >> +>> endobj +1139 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 516.046 539.579 525.068] +/Subtype /Link +/A << /S /GoTo /D (subsection.14.2.2) >> +>> endobj +1140 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 502.496 539.579 511.519] +/Subtype /Link +/A << /S /GoTo /D (section.14.3) >> +>> endobj +1141 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 488.947 539.579 497.97] +/Subtype /Link +/A << /S /GoTo /D (subsection.14.3.1) >> +>> endobj +1142 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 464.489 539.579 474.057] +/Subtype /Link +/A << /S /GoTo /D (chapter.15) >> +>> endobj +1143 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 450.94 539.579 459.963] +/Subtype /Link +/A << /S /GoTo /D (section.15.1) >> +>> endobj +1144 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 437.39 539.579 446.413] +/Subtype /Link +/A << /S /GoTo /D (section.15.2) >> +>> endobj +1145 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [525.586 412.932 539.579 422.5] +/Subtype /Link +/A << /S /GoTo /D (chapter.16) >> +>> endobj +1146 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 399.383 539.579 408.406] +/Subtype /Link +/A << /S /GoTo /D (section.16.1) >> +>> endobj +1147 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [526.677 385.834 539.579 394.857] +/Subtype /Link +/A << /S /GoTo /D (section.16.2) >> +>> endobj +1122 0 obj << +/D [1120 0 R /XYZ 85.039 786.531 null] +>> endobj +1119 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1151 0 obj << +/Length 2942 +/Filter /FlateDecode +>> +stream +xڕ]o8"X+Ԥ"nk\t^[u%/%o7_h[n{(p87_x1K ..Yqxؾ +.ְP04$ԬN| 'F_x=u. +.ϲb"Nixo4ISMBf2kWͼ;\/k#?oazfT,yNmɗ?/ϣBeLjYvusw8,_đ+0$;/{; rؒ Ӌ0 +ܝ +*sOzM\3yf~(% o¨kB|`hp赺w:&aq|Ыۇ[֖Nǵgo q1% +M"@M!Ը QmQ-R(U/NrUj$ +CFq=auHJLdP[:κ.8OG`~&.WEEXaCX2yS"Sy@b^3pqYBD~ap"@ỳ*_#^<=*""dƅQ&v:vZ*hiԆ/$=+-4,vwdc|CktpȇEl+uh{K 9at1i_s܁p,@knary udY{`G_{4>s0D"HQ`P}P]5O4D75qE0h蕵Fb1!ONE}M9 ,$ w3PTj! g\eV5j]Be~.ҟqӋ5%.S&G| C|!fQvL4 uji(} +o13τ!HTZvH=.BŦ ߔC#* 6)x6PdThF1ښ9OïAJR(q)_x$a3pQj~!*D"Ir{1$5z6DJe%{Ȗ(V"V#63$Rxf3"_3w Ԃk]s0Kb!bHK(j[*tWxQpj[K:94"!c,'P|9 vue +`piAI%™5 +JAngX- :iٜ=ّ,ĩ.~uDM9:$,ҡThnx^TtRh/dsW35:S.(5hvr}'t\^v.4RTURc O"j Z J4UFVn\@^>/_S&*Q(%)P2Avz[)c@fſ) V$IgpQR*0H̯hIh:/O^R^0ݻX@ԦZ fzzKW#_1Q> )7TJ*VCH§j9֓'@U&.B6 xwoy[+?Ms a(m IABLC[>#cu%f>Jci-5EJwdipH:f~ξhh|~ +y58e﷢oJb`ʖ1\0`XC׆Rqx¹WC(rus`Hq_nĽr(e'鲇GӑALUejEce/bbx%%-eπÆs44L@ld_ GQB]}(0z}eC>*uK-wWO $ '+jgU6yf"4:ف 3(y%ᖗkBB$`55Bu3.CcnwJ3NNˉ%X׆=F'W[/t BqK:ƹƳ_ +¸8,'MX ͎9hA0](0]ii9t *]1ШF=BxkjrL0 +LWXBk ̒&9PcwA2l9^ բ:WERٞΟHKlVZ-#ΙkС\82w6hY6l> endobj +1152 0 obj << +/D [1150 0 R /XYZ 85.039 786.531 null] +>> endobj +6 0 obj << +/D [1150 0 R /XYZ 85.039 766.606 null] +>> endobj +1153 0 obj << +/D [1150 0 R /XYZ 85.039 651.298 null] +>> endobj +10 0 obj << +/D [1150 0 R /XYZ 85.039 651.298 null] +>> endobj +1154 0 obj << +/D [1150 0 R /XYZ 85.039 622.563 null] +>> endobj +14 0 obj << +/D [1150 0 R /XYZ 85.039 240.295 null] +>> endobj +1155 0 obj << +/D [1150 0 R /XYZ 85.039 211.559 null] +>> endobj +1149 0 obj << +/Font << /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1158 0 obj << +/Length 2860 +/Filter /FlateDecode +>> +stream +xڵZ_o[( "ۢ8=9U](PKRq;vIJt4(wZf|̃Y^̖q䆁?fq \W˷a<=7zK<oW ߝ/ys=7 +sZ]_ss{|8Ws}}YVox=,f;_k^wPenR=Né@ ?v=_sgoé g0\?If @Z1ܷYwa+AL!w-٣T=K> W複E,dٛ_H0*JC+txmL +jw?=? o}T+QG!ްPt<<:ٍwxď;"X}^ΥbJVF,S"qgݠQ' %wC?IIFPc%@HŞiUxhּGG| )Zx: +!.^Fݰw{$z*` ;ys^9G/Mlvfuǣ;fwU\hzx7Ҷm9)#/T&bQx AAuvZWCR\h;hklG,y3G ia'07t~`2(v* 6cTWf^b27Mqpݽ +lτl| #D9X9<;K3l*튜ZcxGgԨI)1jvZYbWlaO< vrOS}{wqDH8W#G@/ܦ.ựƣlߔr9!!Ǒk#1/FHr:((x:S KX׆yzf&Weǒ^4p!F5Y-X} 6?c!I-FFZ(BB_՝p6iǜ${VH͕˪q*b׻R!:, +?g%s6QvZ>tz6ߌG+|-rcc4AyvGs8jװ䓺trOTӵ(}gNTP$;r $ jx'ztS3UJ +95S]UP8ǎ"~;`HܰUviԓ*_D5ipnj% RpĂ@.#28"Ftt"i'`9( r4ZuTis/ 1:ƴ$A i7aa%O~jLOX )&ڒbx 3:=Z`)֜9e<idT'0ȋ>WLplm~P v_EbMs' ?gQ}V婾ƕuQdmI-o0.㣝OKiSU6F ̐N!3HuJY }- 8*ǛJL@{tra^.!2Ur +fˊ]L!qa>iQ` +z+],*ld4mg6nڿSD T: +PE? Rv^ 193tu24g{endstream +endobj +1157 0 obj << +/Type /Page +/Contents 1158 0 R +/Resources 1156 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1148 0 R +>> endobj +1159 0 obj << +/D [1157 0 R /XYZ 85.039 786.531 null] +>> endobj +18 0 obj << +/D [1157 0 R /XYZ 85.039 766.606 null] +>> endobj +1160 0 obj << +/D [1157 0 R /XYZ 85.039 744.844 null] +>> endobj +1156 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1166 0 obj << +/Length 2761 +/Filter /FlateDecode +>> +stream +xYY7~_7NǾb6v1!%H!w#O~E[ x&EXWppQ~(&Xla7H$iI wv. /(ˀ?! +QgYx|"ͯ^K{PJ-,~Zޅ^iSWb?Σ+_t0$2Zl#6}m42a8v9]q]ۀ(֨z 6va*{JzU + +O7v$u`%,IQx>JxRވڪe{H"vYTy'uǔd%3& Dxd5@WcFtԃ AGdxdE>L" <(0;S_}Rvp^=>9̗juX Caz;J ?)ːI{kӠUxdpK߇IGq#ڼ庖iW>L*^^ S7"T֠8QNҳtҿ'8z&j[qs<),GyY}GF!m)k JmMQKXzݍdztAfUR(E,4 &>&8Yvj4ɠʰ9C_qiQ-~Qw{+BH0o캓f5ƓExq}\bTHϠ|ע }b'~vq5^7\.c~itpMmú *?R ) +Q>ҥ-$Ng솳Ȩ^67\/I@n'IZ8]a֌r {J<ܕ"FwH{_eo$ b>L?)6hR3+f۷£.=UD¼#[X|F@Au0Es0bX K{-OP_#z0>1+f R憭'xr=WMK^ ָ=y2VRפOh0BqL뱧9$Vz>>87h\'nk.UcN_bINO,hݐtԄ8@K.=CürT!֋Dg-[nWp_qeg|H4̛7H1=lK;{FsJ of ܁[Eq\^cҟ:͑j`K(\ + n/ J9*w@NuIFfRW_ ʌʐI{ a\S9t"-Rͽ3Dpԑ4;=P#c+ރGfmwsy>்X@1j-U 79V&STvPZ&} {bMvSe)8]$L+628#Ct[LnbI vBSP|ǽd"o̘ sK7OOTM+'ҟ>ub?GoÏ$Cwh_S~+ϟ̪1h"Qo1Џۀ1tZ[9;ϩ ;̼yM"27?liClI`/7,6`o?.ځ墹y$#H5;^q*u.v`GC|iGV޾,b s0 m02 A=83'莢|?s%%Rendstream +endobj +1165 0 obj << +/Type /Page +/Contents 1166 0 R +/Resources 1164 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1148 0 R +>> endobj +1167 0 obj << +/D [1165 0 R /XYZ 85.039 781.388 null] +>> endobj +22 0 obj << +/D [1165 0 R /XYZ 85.039 761.463 null] +>> endobj +1168 0 obj << +/D [1165 0 R /XYZ 85.039 671.062 null] +>> endobj +26 0 obj << +/D [1165 0 R /XYZ 85.039 671.062 null] +>> endobj +1169 0 obj << +/D [1165 0 R /XYZ 85.039 642.326 null] +>> endobj +1170 0 obj << +/D [1165 0 R /XYZ 85.039 578.536 null] +>> endobj +1171 0 obj << +/D [1165 0 R /XYZ 85.039 544.592 null] +>> endobj +1172 0 obj << +/D [1165 0 R /XYZ 85.039 519.956 null] +>> endobj +30 0 obj << +/D [1165 0 R /XYZ 85.039 485.484 null] +>> endobj +1173 0 obj << +/D [1165 0 R /XYZ 85.039 456.08 null] +>> endobj +34 0 obj << +/D [1165 0 R /XYZ 85.039 277.719 null] +>> endobj +1174 0 obj << +/D [1165 0 R /XYZ 85.039 248.314 null] +>> endobj +1175 0 obj << +/D [1165 0 R /XYZ 85.039 227.962 null] +>> endobj +1176 0 obj << +/D [1165 0 R /XYZ 85.039 191.291 null] +>> endobj +1177 0 obj << +/D [1165 0 R /XYZ 85.039 157.953 null] +>> endobj +1178 0 obj << +/D [1165 0 R /XYZ 85.039 92.669 null] +>> endobj +1164 0 obj << +/Font << /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1181 0 obj << +/Length 3267 +/Filter /FlateDecode +>> +stream +xڭn7]_!-/x7Iij>}Ho]dsfZ +0!bXw+ _xY~yqQ\nۋr+#L Kqۋ#-./Pn_w]}&c/6y^x7Ww7M럯?ܾwPC_u$~xؗ_.+ Ɓe{&̛Y*\+m &Hpah+N+~Rd'_R 5}I;\m'7$-%82oAZ#nwLlo궞xMk] `8"Z?IC'<g<@p239 +xoQ;d +xQ{6&i<{Gy o6-'p}uoXLqy([^C!j$cܭjJ~'C +;ByPS 1߂4!c9 SH#qW5V[kNutEF_6aql_ pI@'W4 08/˽yQYIfp]'kC~jޚЛ'H@!"y~&l~YWm޵#÷Hɠh VX0@2.ýPa q/L&퉜FF"p(诐tٮe!PzAFNט0==#yl\$>rԆ]ʑ +x=@<̀=Z0A o[ͣ7(+U$mLL})gDžA<:w2pUxĺts8>ӊU5pČu{ N2mh4)`hdGG3&=@J%<3#?۹(ČÒ_=KGP?i%&̍4p8 [װ T(ngk1!3n?<q$^4j':-K\K4]^"&nYԕѲ lTufSͣLK0Ds֕P)L~ѯGy +k;siN Jg4[V^,]#ɚPsv x::6Y-Gy+**F +v21X6J +&]rUH%Љ8iPan>(ćEDڈ(X[vx%\ޢ83rr' +XNZ!L_kq^ '$<@7-dKt3 ϝ`Ф)nN-e$+މG0ܐuBxϪsDݍӠB&f$Gc CԠ&T&tY\?"ͼ<)"%_sZ U}"lKI`wݞqǕS6t &|ܚ0Jؽ Kw?ڊˊ2aW&KyJM(% /%Ԩ~}XBȕTݝ!ë(sWy= uQOo1eu2dq](I*;q ç=Z<&)d52(pwRH?>KՃFG7E8(HeL*_s Q")kuGb^׺~bB7JeOK` Jd8;Ջ6x [}j{%#5PyL 8~*bOM*z9b2tL q+޴Ү[6yכ<) _؍B ++'v*Rg/C)f){B T+xToN3n!ĥ~JT[D'ǡ^.Ɛ7jjHwlaT')ӠV\4cF|c=NQᾛw;g4D7b@\y)]wśa 2Y):=z2ϼ/ȔhQksq0 +DωC"j"5W٩ǟ C|Ɖ9FKwLϸEˣ3BZ&i='ї(euVM1c|h$RMlh"' +X$L[MDT6G*j9EW`8CvEɔ;|ⳓYEdMt&DI֎ +E1RO.VL ncЇFm_p͚/Cn\Or6JZqJ<'b;l*ziq#rdbQ 9(Js {Zi-m8oU7[_ "wtBP;hF%;!BluE_|uC8 xǓ5enw:+ Ր-ƇGjT`k\Ɂ*cءdy??8ED702N-,W7Ze8:lّ" 0 :"tEJ"> endobj +1182 0 obj << +/D [1180 0 R /XYZ 85.039 781.388 null] +>> endobj +1183 0 obj << +/D [1180 0 R /XYZ 85.039 761.463 null] +>> endobj +1184 0 obj << +/D [1180 0 R /XYZ 85.039 732.472 null] +>> endobj +38 0 obj << +/D [1180 0 R /XYZ 85.039 684.451 null] +>> endobj +1185 0 obj << +/D [1180 0 R /XYZ 85.039 652.925 null] +>> endobj +42 0 obj << +/D [1180 0 R /XYZ 85.039 393.269 null] +>> endobj +1186 0 obj << +/D [1180 0 R /XYZ 85.039 363.865 null] +>> endobj +1179 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1189 0 obj << +/Length 1818 +/Filter /FlateDecode +>> +stream +xڵXYoF~ׯЛ)p<@ȩA(i(";E{gvvyT\8)lh99|j3E0|΄OĜ&ṉm,ܵi{c{ܲY`ŅeN-.etcqLcgszF3nfsn8os|~GCv~X/ɏ2$đE.X>fv2N^{#2kƟF2?›A tnշGuJ$.Z4!7bX7i,sTIvdF6x[Oq+ 2qWj4A}u4D ޜ 7F sDNq; F]0) 4d=,{qش=آ!Eg>Kd )TNr>Mپ3^8Þz {Y:OgF|GR`[s|Y?]Au/1Umʁ6fÎJMuAR\W-oB鸴zGͥޘ2+Ws.3]?R$MuQV\5M6PɕI"A(cHr_WyۋBXu6Q!Q] sTdxuF.NoxKeҦbh Ik`iё Z˰YFGˮ0,?΢@ˢ0, 0uYVhy!IYO. CR.3kMk rdVT {DɅb̠M Z +[%J>K0y6eg,f 5o"j_ #e*Y ;cYؠqNPQjEM w8Jִ!j۱@ګQ|$̅4wl$krskN#Q'&DC߄`O4&&enyÞOB|? (.ꣵ'w> endobj +1190 0 obj << +/D [1188 0 R /XYZ 85.039 781.388 null] +>> endobj +46 0 obj << +/D [1188 0 R /XYZ 85.039 761.463 null] +>> endobj +1191 0 obj << +/D [1188 0 R /XYZ 85.039 667.044 null] +>> endobj +50 0 obj << +/D [1188 0 R /XYZ 85.039 667.044 null] +>> endobj +1192 0 obj << +/D [1188 0 R /XYZ 85.039 639.536 null] +>> endobj +1193 0 obj << +/D [1188 0 R /XYZ 85.039 351.388 null] +>> endobj +1194 0 obj << +/D [1188 0 R /XYZ 85.039 328.872 null] +>> endobj +1195 0 obj << +/D [1188 0 R /XYZ 85.039 292.807 null] +>> endobj +1196 0 obj << +/D [1188 0 R /XYZ 85.039 201.94 null] +>> endobj +1187 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1199 0 obj << +/Length 2079 +/Filter /FlateDecode +>> +stream +xڽYYoF~ׯ  +Y+}JZ'qۤGEZd˸c\Tmsvofo.7OBW,K7 pXhb54y'B;/uSO`Onlo0z!qAV4,Z>jWjoHP٭aBZfM@X8i5 Օ;ƠWHhYȦg|9=h0r4L='`6\|}IP|sZfٲzRX u5AݠP2e{Nҋ(JiiOc!&`6@j#o$R2"HP@$G[wƩ<r~$^/ a)m1h>4_\`tl7tC*ԏMqPw +3~gӭ}:㶹vhp]"}OE>A %t2҉Bwa ߡS[P8&d7Rxϰ I?2C _RX}j4m QaE@5;j&7J Wdص7hMZPLl .T]_UnSc8"H=fU@ڗ2FBᢅQ{6 Фj]--<"HUp"-Av*j)Vs.աqQ-*Dk?ߕJ˭NJ1Pisj2[7,ZwCw暲iE=I:D%Y >R;em5,(jۣ]'! Zс|S[;SS)F~F g\uMd1~,0!dhstԳ y |~ w|ˊ9|SoƖ~#7T_qN~sAƩj܆TPx-Oj)oȺ] Ř"?-0+<ڧA̘臷(n?_( N,3f/Dendstream +endobj +1198 0 obj << +/Type /Page +/Contents 1199 0 R +/Resources 1197 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1202 0 R +>> endobj +1200 0 obj << +/D [1198 0 R /XYZ 85.039 781.388 null] +>> endobj +54 0 obj << +/D [1198 0 R /XYZ 85.039 707.104 null] +>> endobj +1201 0 obj << +/D [1198 0 R /XYZ 85.039 674.781 null] +>> endobj +1197 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F37 900 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1205 0 obj << +/Length 1639 +/Filter /FlateDecode +>> +stream +xڭko6P` X +)R&}ź0E [-DWQ+NBxw- +} +B0Y+qC,鲩+?8s#Y&%_o>.;B[c'B{> O>㋿^ q|!bHWN>Y n\5ˣG/9gO?:.x#yrsPv/KgVù+}VdiD{ͧ|BGe)wq&-gޔ5."N^q |^! 5?_֐7mҞe [`q"Ud1%oTMf6yruώJ p1ݐ;᚜#\y4hӡx~ ZSCʁÇ=zx zV' L5U}lv-ָ/3o܇\[ +},-v269J49]M( M+TbTb&޵VQ"iiYb.3z:͐}3%;۴]="J0&Zʼnз z)o6;I+暸5m`C}ŶZ ^B;Q:Vx-J;u6PߡGAm}/d*Ll5HM,oǡDO%7y7&oV.Ad:;;7`*)up@ F^ylcYmt1  ɽyzGeRhC˦>#l]T-drr!g]vxO[EY$wŷJݾ½=c}4I0&b-];ࣁ}vZ'E&59y_{?枰?|r]-DGAǩ ~B.!IkD}Wl4kH8p7rYtWUbd+etF}fW+=&K}53zh9aʚMTUӮs؜rgx].;`{Y'.p)E吖yje{1VEr8Q% 95 s1ˍ߲M{F4!H'v^f].UUn7-D"ޞcQSVY9GmoQUd^0(y/<{K*yWV` mkl7UxJWf7C{Rb]픟+i6w7 {5Hd!^;bl\}؁D>)"Mva<D?Ucp:! }CdODu_}:Q&k{8yb|xOcG<5u z6Fݬ(L <(p}><=IzTV~` W?endstream +endobj +1204 0 obj << +/Type /Page +/Contents 1205 0 R +/Resources 1203 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1202 0 R +>> endobj +1206 0 obj << +/D [1204 0 R /XYZ 85.039 781.388 null] +>> endobj +58 0 obj << +/D [1204 0 R /XYZ 85.039 665.791 null] +>> endobj +1207 0 obj << +/D [1204 0 R /XYZ 85.039 635.59 null] +>> endobj +62 0 obj << +/D [1204 0 R /XYZ 85.039 383.634 null] +>> endobj +1208 0 obj << +/D [1204 0 R /XYZ 85.039 351.312 null] +>> endobj +1203 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1211 0 obj << +/Length 2161 +/Filter /FlateDecode +>> +stream +xڽY68 Ī(R($-C8-Xȶl"K>I^g?~$6i 3r؃?58x؎f^PxczaSg/_Xyn%يHfߜy=i2Z;ڝL(vfxD97?x\02F-:J23l<3H]owVpAԂG24?'BsC!YMI\8*r;;0l\m  2d/+wH&ZD+7A<FFh; 界vC/:D£/9+!cb:^G\ Abf+!`KZU0cw/E_.Us$9"T>b<_CmH%D&Ξs la”!$f{$)/ܿQ#"]fAnbVeFPMn/: RMl[qSܾ$tx*cd5 D+?Ñȱ΀df"%n +Ʌ+nb=-ґqB;&t#s=ܘ]aE>η+:jG8LO;u$EG9V"|P]j*|mPh/ k?[m3B Ūv%{{Й\Jփw.r4Λޒ6qQ9徔̆ ܺR26qR +UEgxo# e%͆ t7WO'>RĖoDwøͼ- ytxeuAbm9dZʊۻ)"|uyU'|/fZUXi(*OKT ^LTeq]!D4dO`L]5(54 aW^H0KKKIݐs3aU_K\uF;,ǏGaD܁9@U7D[ +ITWdu̯^١ ..pըGاk&%:eD\d\xdȯ9m+9աdl/Kv[m"+:)#C;9!{J_L"hE+4{Kǂ^lHrMJy%yY}eͤ0r4$pOȎDހZWa`UDֶ?L^اYլ'C<,RNR-[@8lr +&/(-R|)f|e3{i98UQh)Pbendstream +endobj +1210 0 obj << +/Type /Page +/Contents 1211 0 R +/Resources 1209 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1202 0 R +>> endobj +1212 0 obj << +/D [1210 0 R /XYZ 85.039 781.388 null] +>> endobj +1213 0 obj << +/D [1210 0 R /XYZ 85.039 634.111 null] +>> endobj +1214 0 obj << +/D [1210 0 R /XYZ 85.039 611.596 null] +>> endobj +1215 0 obj << +/D [1210 0 R /XYZ 85.039 577.652 null] +>> endobj +66 0 obj << +/D [1210 0 R /XYZ 85.039 529.631 null] +>> endobj +1216 0 obj << +/D [1210 0 R /XYZ 85.039 500.895 null] +>> endobj +70 0 obj << +/D [1210 0 R /XYZ 85.039 500.895 null] +>> endobj +1217 0 obj << +/D [1210 0 R /XYZ 85.039 476.914 null] +>> endobj +74 0 obj << +/D [1210 0 R /XYZ 85.039 407.713 null] +>> endobj +1218 0 obj << +/D [1210 0 R /XYZ 85.039 386.459 null] +>> endobj +78 0 obj << +/D [1210 0 R /XYZ 85.039 303.709 null] +>> endobj +1219 0 obj << +/D [1210 0 R /XYZ 85.039 282.454 null] +>> endobj +1209 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1222 0 obj << +/Length 3244 +/Filter /FlateDecode +>> +stream +xڽksf!RDMs$L$Ӂ%Hb">Nv~}KϘb,$OG?b€4aᓻEh+12ZYJ.$zsځzG +s$(8pxO7uPWkޟfy<}Dž}h-a#3|g}7n)%Yv;m9WrXb&K4 V q*vvӪB3êmIgj/Fۺ#ǨV5jid3TYzI7v.S +{ZQu?Y?-[тy ,KUєf; |BZy >K}xU !nXS uFƕ +(++l8=fcg#V pkuA2)`{3ng!  m `yilA]7Z]WlY#$WP"ǫFU܂[YKdPЁIX + +=I " a "cJvEN{b92q8M=;ZHY`CC@qa(eCdl?2(Qݘ + Uqv;XCbbLL{A(OYL!ǕapUtl_,ʲe},;j'h6*݊2{!qJh) + XCÓ8aM2S=4c[!kb @!׺IX0.{8p $edQuliaq\|kcqVt{Y'd^g"Y)EķUxua8mل"9gLY}T8Eлy h$ dE0F~ñm/+{*c yE< \d^$ ;j9qoݬ=So_STU,m+Gd>l]"KFd]΀^uB,(q X<"3``Յ FYn*^8HDd.Dzj8fs`|lwV ņ8;uAn1 6ei`ꢦE VFtؒ(WtYՕCMp 9,v)2AL "-ꦕߟukAM& 6痗x㬏\PU(f(v~KJ* 2$0l{j7伥gBx5cѶ+}9g 'ZStQrCN w +!$%( t.ۥ! -*M|<wNÁa1vE+Q0h+T X a,:Fd*KnhVk!Hnekx06+2BgLrno8 +Qd1@C)I_̝cM-P 䕹c14lrz +V|ͷw\t'd%u߲C/ء0!3 bnWDPKID?|7a;#UiםK&o5c݂ϰXsFBvbvT|Qܕc1[ɰK2Җ"D$䀓635*`EGwRx)iP4N`Wr5 +{CBcq* D6]t܋ A`ɟqQ$ +E>9`<dwyaI[CF>LD^aִZ MRd4R2Yc-Mh^r=IWT )l͜g.u|GU5x s#*)+tjcKH֩$pad/#ᗑr_߾>]?=ARn߾ +^ +ʈ~VX+f#54َ}YQK/1엸" +k-(62lg >yf3=Qϛ{~z.q;uq?X%q9ca›o !^'bJ JaHİ,2HƂ0%sh@IA1) f o WWEs8 JR)0}rv-da%\lIAdmec9zPc;NO'sOK +JݚȝfJR!U-:rt.1h9u gn'\aٯP?K2W  #[0`"-7IT`"U#˧{UB ұƦ.qݹ] B8pvJKŊ͆Ox_$ -IgJ*r}> q5BT\)_8F*-B\%cb2E#H?Y߳.,RAh0l _qh eAȫ-%4l=J榲OJDVd v)@;p5F97? 䒢qÒ?] ^a P*bk]3=/6{?? 2$ / +?-$#^flendstream +endobj +1221 0 obj << +/Type /Page +/Contents 1222 0 R +/Resources 1220 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1202 0 R +/Annots [ 1225 0 R 1226 0 R ] +>> endobj +1225 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 477.953 394.76 489.945] +/Subtype/Link/A<> +>> endobj +1226 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 464.403 337.488 476.396] +/Subtype/Link/A<> +>> endobj +1223 0 obj << +/D [1221 0 R /XYZ 85.039 781.388 null] +>> endobj +82 0 obj << +/D [1221 0 R /XYZ 85.039 761.463 null] +>> endobj +1224 0 obj << +/D [1221 0 R /XYZ 85.039 667.044 null] +>> endobj +1227 0 obj << +/D [1221 0 R /XYZ 85.039 309.189 null] +>> endobj +1228 0 obj << +/D [1221 0 R /XYZ 85.039 273.125 null] +>> endobj +1229 0 obj << +/D [1221 0 R /XYZ 85.039 250.609 null] +>> endobj +1230 0 obj << +/D [1221 0 R /XYZ 85.039 216.666 null] +>> endobj +1231 0 obj << +/D [1221 0 R /XYZ 85.039 180.601 null] +>> endobj +1232 0 obj << +/D [1221 0 R /XYZ 85.039 155.964 null] +>> endobj +1233 0 obj << +/D [1221 0 R /XYZ 85.039 119.293 null] +>> endobj +1234 0 obj << +/D [1221 0 R /XYZ 85.039 70.285 null] +>> endobj +1220 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1237 0 obj << +/Length 3357 +/Filter /FlateDecode +>> +stream +xڽZKs8W*sozv̮`XH I/Vl\.@uyΓwU3| =|C׋#zs}Qz{ne ".~s.w͕RNI:^~|mW3;jg'n+ΟgJ%#6 +5NvΒihك(̀]1EWm6aCixi{qD~Fi}Kв?51 D?T~k= 3]Yl-Pw/U)Ct,TYh.V@XF8%nį j#a'@뢜a@Y#\~ロ4F1oG/Dпֹays-6XÐ( `_w EI1P wRn +~yY#uݻEKN#ٴ[eڦdcK^EY?,E'A|V?_C. Qy` +WE{qU0sc?"_(ƭl{MLרfk!|Ni*6Cg+ƈuB#~/g!\_l3d,^ Dҏ[!7eT+Ƭbvčt^]v ۺd@,J%`nhމBpw7-˫]cT)b aer-e/|#`gq \qZojlTq7🞳rduk]s^s?y,s+Z5t ŋgiZ֊+tר劇M+3??t#60 @0Z+V3wi}/6{e2ڦFL:ڵзu1 + [i`ZY醲|m`+2a +6T dTҾSsH"kbv*O-Frf1ϼGS+öC0U5z*I%K9Ǡ~Sf?t|ɘ-+[M7YDGGXȴԭ|IQ&SI'zdqKߒ-]|&Alo6\Vd75:~3ђܒ+'-?K#Hw5MNQ \M%ܾ /-e-%/Q V4;J%-|tf,YaDA.Ж FQc +%sۇl*Vժ!r귾쮢|.e`UQX%#fd!9.?6D-?nySF% +QCY`ΞRʜ[8~΁Ƃ4+۴0P-Xe9'6G +RIF2XT%f՟N!3uATӖKƑ -O]xyGvu;soU%$@@0 ٨'d|݋N/+{ A_"@ +Q ւ 8tA\"օL7^32HoF ߃߲ߟdEG Pfiʺ'S`E W <HH&ʔсՎ؅.r#/1SB˥YM48~;53TDI1B9\~i +[Odm%Nq+->`rLbI> endobj +1238 0 obj << +/D [1236 0 R /XYZ 85.039 781.388 null] +>> endobj +1239 0 obj << +/D [1236 0 R /XYZ 85.039 761.463 null] +>> endobj +1240 0 obj << +/D [1236 0 R /XYZ 85.039 730.35 null] +>> endobj +1241 0 obj << +/D [1236 0 R /XYZ 85.039 694.286 null] +>> endobj +1242 0 obj << +/D [1236 0 R /XYZ 85.039 658.221 null] +>> endobj +1243 0 obj << +/D [1236 0 R /XYZ 85.039 622.156 null] +>> endobj +1244 0 obj << +/D [1236 0 R /XYZ 85.039 599.641 null] +>> endobj +1245 0 obj << +/D [1236 0 R /XYZ 85.039 562.97 null] +>> endobj +1246 0 obj << +/D [1236 0 R /XYZ 85.039 516.083 null] +>> endobj +1247 0 obj << +/D [1236 0 R /XYZ 85.039 491.446 null] +>> endobj +1248 0 obj << +/D [1236 0 R /XYZ 85.039 468.931 null] +>> endobj +1249 0 obj << +/D [1236 0 R /XYZ 85.039 432.26 null] +>> endobj +1250 0 obj << +/D [1236 0 R /XYZ 85.039 396.801 null] +>> endobj +1251 0 obj << +/D [1236 0 R /XYZ 85.039 374.286 null] +>> endobj +1252 0 obj << +/D [1236 0 R /XYZ 85.039 326.793 null] +>> endobj +1253 0 obj << +/D [1236 0 R /XYZ 85.039 274.452 null] +>> endobj +1254 0 obj << +/D [1236 0 R /XYZ 85.039 225.444 null] +>> endobj +1255 0 obj << +/D [1236 0 R /XYZ 85.039 148.731 null] +>> endobj +1235 0 obj << +/Font << /F58 956 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1258 0 obj << +/Length 3217 +/Filter /FlateDecode +>> +stream +xڽZYs8~p51cv2LQvf恖hԐT)q*&huC225a$J"ȿ.FFk\e,H's4R0hoet)0-]biL\廛|Tq],EPB/~@I]$axwCCiP"h$7zs&9&M<0!̥@(٘m-25pVثX=nܿ.hdՖ7Б:y 9D·znl@R580׹U^AWfT=N=wE)l5O=]% &ˆqSK#R(R'@H.`UeAtGNydoq|Cvim'_/A6@j4ڑ /<_XZWM~!T"x{iПiY +1 ')P%e@wpvdN`L:&ۖ+rsм`슉Pf&PGWd싿瞉i@s_܋x3owy5{:rrEiy'+P9T!Hqvm Wn)ōc3< C=^3aMVypɕ +e.j $]z$,"SPm:*x勺An/ *?.D$G}s}=Rnp|=魥1sV{_HR(v:5 +hw$G#OJPj7s22gL(-dySZ-֪7c (pDթ"\wa>K#O]$qML4&mtWVpp.b /1O:A@H1B"Y~\HpqF.v7lkYS[Y@Cc(OP-Jf1qˁSZɪ'- ǫ 7˞'ߢߒYIF 4x %@z[+ݰ7eYaBvrlF@Ѳ,ʢƚi,^:&^i#FCV[iKAy5o*"L SW:0.Sy&,#LWU 7d0̚\SgwH QEVy 3`ܝCE{-pHG?3%9A({yioLR&pK#WQtuR=;dG182>' +F>``n&tF +%@GoiB)t (G>CȔ#[ Vqr۴'!t 9ElӮfYUiyF§LFК(&. 2thŅCUM̈́0,IQF?.נ|?_;Bû Ejϭ?~8DrZn)7*QqK~bEȘj =Uզs~wߣ@vcwH9;*Z,bmQ"j +:ЧaγPg/*İ+ZNt0de_!c-أ =szh$(Ǣ) +ͪRacQ@7@" Ymd~htZ0;n]T}&2C B3 3ls,jaNZh~SlP~ nɹ. ]7E Whɩm]R㋷gm~~RWHϕ" Q_n.v<[_s?e̅ã3I%[ӘeXIfJk>"8nbKAi( *nn~cST17i8wokƻ6|1lUvq%ˈ3tW'sI;{?pq^]c ;w Vvo,/ +::~_7rAuPQ44Wgl]-U:2ءOA>W%4sTI( k?ΰP1Ģx(s)0 7Bƪ.*eϿ:Hs/vc@g-qzy~@`AE;a@~7 ,SI/|`F$ $ +[_iޑҕ7zgK03/NxȫgakK L9G,^~lFqrw˟CECfg =p4*wUC=α"B~xAF!B`\~]v[ެ,~?@KB):i_?G$t5I9@\j UG;_߾Yz&r.iVMݎ&fx7j=Rdw {Wzte)jm|m  `Hh <ν).4Eda&͸uZWN΋e9Wendstream +endobj +1257 0 obj << +/Type /Page +/Contents 1258 0 R +/Resources 1256 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1202 0 R +>> endobj +1259 0 obj << +/D [1257 0 R /XYZ 85.039 781.388 null] +>> endobj +86 0 obj << +/D [1257 0 R /XYZ 85.039 761.463 null] +>> endobj +1260 0 obj << +/D [1257 0 R /XYZ 85.039 671.655 null] +>> endobj +90 0 obj << +/D [1257 0 R /XYZ 85.039 671.655 null] +>> endobj +1261 0 obj << +/D [1257 0 R /XYZ 85.039 640.13 null] +>> endobj +94 0 obj << +/D [1257 0 R /XYZ 85.039 543.278 null] +>> endobj +1262 0 obj << +/D [1257 0 R /XYZ 85.039 516.663 null] +>> endobj +1263 0 obj << +/D [1257 0 R /XYZ 85.039 494.657 null] +>> endobj +1264 0 obj << +/D [1257 0 R /XYZ 85.039 459.047 null] +>> endobj +1265 0 obj << +/D [1257 0 R /XYZ 85.039 418.185 null] +>> endobj +1266 0 obj << +/D [1257 0 R /XYZ 85.039 400.499 null] +>> endobj +1267 0 obj << +/D [1257 0 R /XYZ 85.039 370.476 null] +>> endobj +1268 0 obj << +/D [1257 0 R /XYZ 85.039 339.847 null] +>> endobj +1269 0 obj << +/D [1257 0 R /XYZ 85.039 281.905 null] +>> endobj +1270 0 obj << +/D [1257 0 R /XYZ 85.039 218.59 null] +>> endobj +1256 0 obj << +/Font << /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1273 0 obj << +/Length 2079 +/Filter /FlateDecode +>> +stream +xYIsFW|hqTgg"N.I (% -q~{[S4?taC_[;]'t +#F~\f9NOdЖ޷?\|l?/ֻO\!5|z?_}qn3(迓 7 ˏ׉>8$'Ѿ̋-MԈ:schlO}NЌ j`>vz#]ʷ۬FK5Lhv`Y*_-lg/5~5L0SkĂ&8r|aD]1Ӻ=M_5e)S)''~]2͟t+|;-aa5R"]|W&o5}?0dz)M5 wTO;a`sbeg9\FoZ j:MU`sA2[<WsffE(޳]¬MCӰo9nx5sTf|'c +}wȈ\xB<хLq Ds6Z.q4 J8AQ(Ȯ" 9`YY/0*N*߫8W@ӫU[K|2&~Ћ)q;0{0\hpku`X'uS@#6RKah9uo5 ]sRn2+[lCvI`LJ&~yMzۋ3#S8%CGwtM?BzŦ],tbe`9ZC8QmFP@|Î ؘzdE㘥!vR:]ⷺ*7Ҭ*E zcWZRIήgnցeo^C˵v4 -j^ W1qyc0%cDᳮJ dXOyW!\FG#@#LпIC*cƷyD+~f U>`uD팊FS1} …^Pea8Խ#6@H%J.HxNR.z+cwq*~r8Mk?fзe(痋c>83P;J)_ +C'/FWؽNvm#ȥ,e{m"IP("$$m^ >}Z\(\ئ`qp9'%C" z8_P ZYDR i`lŅBQ`zF]ԻyPa'X.ٜ 9`m)U"7 +\bF<EB(;C7?,HV.|](&Z{LǞw(lU."I{>o%{3uOz]"3uw>PtG]UDܸ@UYvOL Co]a6,oHnd./$ת*[0qK8E$Ub[\Ot”~<'\+S)a Z3H$.A˕]2h[{1cq;JB6|狗_x$S@Xp7l%\o_u^y䥠t[֕nǃ8 Λ\Q.?AN bWuu)jTz k"pz_>{vA}kO #i%iba۟o8=FdE˺08둎}8Xq +@^R0q۰eGңhz*[#vP^ВHgN%J֞JV|ٟ#ڴx09P ~ Vfendstream +endobj +1272 0 obj << +/Type /Page +/Contents 1273 0 R +/Resources 1271 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1289 0 R +>> endobj +1274 0 obj << +/D [1272 0 R /XYZ 85.039 781.388 null] +>> endobj +1275 0 obj << +/D [1272 0 R /XYZ 85.039 761.463 null] +>> endobj +1276 0 obj << +/D [1272 0 R /XYZ 85.039 678.275 null] +>> endobj +1277 0 obj << +/D [1272 0 R /XYZ 85.039 653.638 null] +>> endobj +98 0 obj << +/D [1272 0 R /XYZ 85.039 619.166 null] +>> endobj +1278 0 obj << +/D [1272 0 R /XYZ 85.039 589.762 null] +>> endobj +102 0 obj << +/D [1272 0 R /XYZ 85.039 550.188 null] +>> endobj +1279 0 obj << +/D [1272 0 R /XYZ 85.039 526.206 null] +>> endobj +106 0 obj << +/D [1272 0 R /XYZ 85.039 498.26 null] +>> endobj +1280 0 obj << +/D [1272 0 R /XYZ 85.039 476.399 null] +>> endobj +110 0 obj << +/D [1272 0 R /XYZ 85.039 447.846 null] +>> endobj +1281 0 obj << +/D [1272 0 R /XYZ 85.039 426.592 null] +>> endobj +114 0 obj << +/D [1272 0 R /XYZ 85.039 398.645 null] +>> endobj +1282 0 obj << +/D [1272 0 R /XYZ 85.039 376.784 null] +>> endobj +118 0 obj << +/D [1272 0 R /XYZ 85.039 335.288 null] +>> endobj +1283 0 obj << +/D [1272 0 R /XYZ 85.039 313.427 null] +>> endobj +122 0 obj << +/D [1272 0 R /XYZ 85.039 285.481 null] +>> endobj +1284 0 obj << +/D [1272 0 R /XYZ 85.039 263.62 null] +>> endobj +126 0 obj << +/D [1272 0 R /XYZ 85.039 235.067 null] +>> endobj +1285 0 obj << +/D [1272 0 R /XYZ 85.039 213.813 null] +>> endobj +130 0 obj << +/D [1272 0 R /XYZ 85.039 185.866 null] +>> endobj +1286 0 obj << +/D [1272 0 R /XYZ 85.039 164.005 null] +>> endobj +134 0 obj << +/D [1272 0 R /XYZ 85.039 135.452 null] +>> endobj +1287 0 obj << +/D [1272 0 R /XYZ 85.039 114.198 null] +>> endobj +138 0 obj << +/D [1272 0 R /XYZ 85.039 86.251 null] +>> endobj +1288 0 obj << +/D [1272 0 R /XYZ 85.039 64.39 null] +>> endobj +1271 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1292 0 obj << +/Length 1935 +/Filter /FlateDecode +>> +stream +xYms7_әt~ + 0$/tb3]to>'teyvRЇ|+dŜ8_jCPa?Not{h,(&#]I 'R*pV߸F!5 L˼'`]Q,铓& pxŘuz){*`vqSA(^(|[I i$ %ZLRAO*&}ye%AbݡZт_2!66 KPy)@6kWi4{"B +0]f[rvf~t9=0vdhMZ[PZہ~ޟ]RƂU@Pn>Y+3HX x~> endobj +1293 0 obj << +/D [1291 0 R /XYZ 85.039 781.388 null] +>> endobj +142 0 obj << +/D [1291 0 R /XYZ 85.039 761.463 null] +>> endobj +1294 0 obj << +/D [1291 0 R /XYZ 85.039 740.47 null] +>> endobj +146 0 obj << +/D [1291 0 R /XYZ 85.039 712.523 null] +>> endobj +1295 0 obj << +/D [1291 0 R /XYZ 85.039 690.662 null] +>> endobj +150 0 obj << +/D [1291 0 R /XYZ 85.039 651.288 null] +>> endobj +1296 0 obj << +/D [1291 0 R /XYZ 85.039 627.306 null] +>> endobj +154 0 obj << +/D [1291 0 R /XYZ 85.039 599.359 null] +>> endobj +1297 0 obj << +/D [1291 0 R /XYZ 85.039 577.498 null] +>> endobj +158 0 obj << +/D [1291 0 R /XYZ 85.039 538.124 null] +>> endobj +1298 0 obj << +/D [1291 0 R /XYZ 85.039 514.142 null] +>> endobj +162 0 obj << +/D [1291 0 R /XYZ 85.039 473.593 null] +>> endobj +1299 0 obj << +/D [1291 0 R /XYZ 85.039 442.067 null] +>> endobj +166 0 obj << +/D [1291 0 R /XYZ 85.039 295.167 null] +>> endobj +1300 0 obj << +/D [1291 0 R /XYZ 85.039 276.295 null] +>> endobj +1301 0 obj << +/D [1291 0 R /XYZ 85.039 253.152 null] +>> endobj +1302 0 obj << +/D [1291 0 R /XYZ 85.039 230.637 null] +>> endobj +1303 0 obj << +/D [1291 0 R /XYZ 85.039 208.121 null] +>> endobj +1304 0 obj << +/D [1291 0 R /XYZ 85.039 185.606 null] +>> endobj +1305 0 obj << +/D [1291 0 R /XYZ 85.039 163.09 null] +>> endobj +1306 0 obj << +/D [1291 0 R /XYZ 85.039 140.575 null] +>> endobj +1307 0 obj << +/D [1291 0 R /XYZ 85.039 118.059 null] +>> endobj +1308 0 obj << +/D [1291 0 R /XYZ 85.039 81.388 null] +>> endobj +1290 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1311 0 obj << +/Length 3054 +/Filter /FlateDecode +>> +stream +xZYoF~`q;o `2D[L$KRx~a{0/ fuwQWVS,0_,[lz~dD _g y/nhg\* C/4ͼK]w; 彻~a:"?JB\?,/?̳ځ|qЏP.ip_Y3YE0^ϲȞK3ݕ-n3+mw;jC+q|WNE:wH<-۫* +":J׮_n+2(XVz<,Wn@c%JeX)̜n^hZW6,6 ~f,S( Kv@Y9(:,ic/r3g;YdpaGsw[S pQ(Ο{rmCP$\{Y@?pkԧYUN02bSɔsx-{{Kes/5 7Xw,ߏ4pf{=ʦfTPfڴY +νIPs!-۴n, 2WEu+[k3QM!cWG}%9&;oJ&7a'?>/F[;4 +!UYpmFWzy(Fn]aAs/6pElgXjYj: +n-OX+/Xkh,'N&vh0zd]K Mnp c| #<ⱒaRH&9dĠ@ֱG6)gBll3pdvP?qTos!ؕŻ߷$˄Qš>~A3Rn- +h%·;aˍ"8 PڮR1n&[.: 3LbSR4K5UY "*6nP cڮh:4xƂr8U4P~1l Y&ͧ륑P3a~|RtT_2Wٙ`S NYd,…G5fR-Hm@*- $%OmX78r1iU_0Omy;a24*ؔJ?UOUEғ 5L%LQ\TWxI&Uw;|ѕٌn_lp#[Po܊I\lC#?q/;n[R@UO&'~-qM.`g68B>1BA[t_xE*p;rR%4!yT4֊kk:{w+IJ[-[T2*fNhol! )SЦ3D*:j1xNguywuA" KYendstream +endobj +1310 0 obj << +/Type /Page +/Contents 1311 0 R +/Resources 1309 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1289 0 R +>> endobj +1312 0 obj << +/D [1310 0 R /XYZ 85.039 781.388 null] +>> endobj +1313 0 obj << +/D [1310 0 R /XYZ 85.039 727.362 null] +>> endobj +1314 0 obj << +/D [1310 0 R /XYZ 85.039 693.418 null] +>> endobj +1315 0 obj << +/D [1310 0 R /XYZ 85.039 628.134 null] +>> endobj +1316 0 obj << +/D [1310 0 R /XYZ 85.039 605.618 null] +>> endobj +1317 0 obj << +/D [1310 0 R /XYZ 85.039 569.553 null] +>> endobj +1318 0 obj << +/D [1310 0 R /XYZ 85.039 519.333 null] +>> endobj +170 0 obj << +/D [1310 0 R /XYZ 85.039 436.16 null] +>> endobj +1319 0 obj << +/D [1310 0 R /XYZ 85.039 415.167 null] +>> endobj +1320 0 obj << +/D [1310 0 R /XYZ 85.039 391.419 null] +>> endobj +1321 0 obj << +/D [1310 0 R /XYZ 85.039 355.354 null] +>> endobj +1322 0 obj << +/D [1310 0 R /XYZ 85.039 281.369 null] +>> endobj +1309 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1325 0 obj << +/Length 985 +/Filter /FlateDecode +>> +stream +xڽMs6<"I]u:=$9@$q" +bAZTh{Ƒ3:P܂0n^D,) +wsBwߝݔGy/(d"|mW?f/$I< ֏هZSf~ y7[s9?'HY%8]\;!KDC;dIyxʹu/u髉tG &b>r)r1$9eI&Cj [)xdJ^[LV.ZjT1 aOWв!n{+% +o\K죡ѵjO*j] ? Oȵc=P{gƑ5t5=gW˫oh8.7@Sc<&1_[9Ij 9e&Ho'Hizئ H910r˄BN&aD8h҂g!9KŇ!H􎖎 AL+uCF֥+ޗڬ:@EVB EKڳ789ЁfVMY=* 'ދP&"/^LKhgab~|2ųnڝp( 9WJagY=o_`,ßw`Vendstream +endobj +1324 0 obj << +/Type /Page +/Contents 1325 0 R +/Resources 1323 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1289 0 R +>> endobj +1326 0 obj << +/D [1324 0 R /XYZ 85.039 781.388 null] +>> endobj +174 0 obj << +/D [1324 0 R /XYZ 85.039 761.463 null] +>> endobj +1327 0 obj << +/D [1324 0 R /XYZ 85.039 739.701 null] +>> endobj +1328 0 obj << +/D [1324 0 R /XYZ 85.039 705.131 null] +>> endobj +1329 0 obj << +/D [1324 0 R /XYZ 85.039 680.494 null] +>> endobj +1330 0 obj << +/D [1324 0 R /XYZ 85.039 660.099 null] +>> endobj +1331 0 obj << +/D [1324 0 R /XYZ 85.039 635.463 null] +>> endobj +1332 0 obj << +/D [1324 0 R /XYZ 85.039 612.341 null] +>> endobj +1333 0 obj << +/D [1324 0 R /XYZ 85.039 590.432 null] +>> endobj +1334 0 obj << +/D [1324 0 R /XYZ 85.039 567.916 null] +>> endobj +1335 0 obj << +/D [1324 0 R /XYZ 85.039 544.794 null] +>> endobj +1336 0 obj << +/D [1324 0 R /XYZ 85.039 522.885 null] +>> endobj +1337 0 obj << +/D [1324 0 R /XYZ 85.039 500.369 null] +>> endobj +1323 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1340 0 obj << +/Length 2148 +/Filter /FlateDecode +>> +stream +xYKoϯ0El`J"G/3s" E#+0J$/σI1)1wd_ʵdX<_7֎M3B+e [7MliN&Jz$Z%HSIWfuWLp6^ (bT?~zͤYr8!'R3NDL\ڍ4 loM8Զwp,/ NzG"ര]fThwrN6mwmK P!Ѫ_CX2MRy@fvh#6KP>=O2=3vY=}$4Yyfdz)T@L +ݶ_|sI)xIA[/1;`@bv/# f(mW݂Le!"jUi,NBz٘PE~sLP¹sY -5\Sni~qc5MYOx&H2i-w Kayߡ(4GG:Ǻx[Eln V:"4Сޖ]C]8E)C}Nx;t P~</U9}ev~Q\/!+~/8,+!'^YeJpOAI1 @x5^}qc49SkrN`AΓ&@,A/3: bBl缫n  ,]8n1C0 lT:xlJ$D07ҸmDzdk;n?:TA`Q{_a)(@>):o}]=}>oKUF03b:> =RN!zy3yxϪ}k +ʿ8laj2Z'1kK<̬᫹&/Fkx}Gr:g!ˌ٘=hw-ȫ@wn#&Lk:^q]plmk’P"8,NWضTf˚,8>Hz';GÎvZ=0> endobj +1341 0 obj << +/D [1339 0 R /XYZ 85.039 781.388 null] +>> endobj +178 0 obj << +/D [1339 0 R /XYZ 85.039 761.463 null] +>> endobj +1342 0 obj << +/D [1339 0 R /XYZ 85.039 671.062 null] +>> endobj +182 0 obj << +/D [1339 0 R /XYZ 85.039 671.062 null] +>> endobj +1343 0 obj << +/D [1339 0 R /XYZ 85.039 639.536 null] +>> endobj +1344 0 obj << +/D [1339 0 R /XYZ 85.039 605.028 null] +>> endobj +1345 0 obj << +/D [1339 0 R /XYZ 85.039 583.119 null] +>> endobj +1346 0 obj << +/D [1339 0 R /XYZ 85.039 559.997 null] +>> endobj +1347 0 obj << +/D [1339 0 R /XYZ 85.039 537.482 null] +>> endobj +1348 0 obj << +/D [1339 0 R /XYZ 85.039 473.53 null] +>> endobj +1349 0 obj << +/D [1339 0 R /XYZ 85.039 453.135 null] +>> endobj +1350 0 obj << +/D [1339 0 R /XYZ 85.039 430.62 null] +>> endobj +186 0 obj << +/D [1339 0 R /XYZ 85.039 356.148 null] +>> endobj +1351 0 obj << +/D [1339 0 R /XYZ 85.039 334.951 null] +>> endobj +1352 0 obj << +/D [1339 0 R /XYZ 85.039 289.156 null] +>> endobj +1353 0 obj << +/D [1339 0 R /XYZ 85.039 264.519 null] +>> endobj +1354 0 obj << +/D [1339 0 R /XYZ 85.039 228.455 null] +>> endobj +1355 0 obj << +/D [1339 0 R /XYZ 85.039 191.784 null] +>> endobj +190 0 obj << +/D [1339 0 R /XYZ 85.039 159.092 null] +>> endobj +1356 0 obj << +/D [1339 0 R /XYZ 85.039 137.896 null] +>> endobj +1338 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1359 0 obj << +/Length 1295 +/Filter /FlateDecode +>> +stream +xڵWYoF~ׯH#ryCcM4iEiY0E<⦿s,) qaܝ攲$)+ԉJ8ֻ6pBiB\-Hdbe]ا~}ujP8n>:8} ߞ97~@7 )t[wB%[;X|\|os\_B,9t4c>ӝ^`. Y5o?Egޖ^RGS>%$n0C-͵uU۲KmU +\#Px\ _$O'+2qqurڰ#w$,B|M5U-YN[D뜗im>IgNjmCjnx UQTrNJ0 wxT,8,7g@IBq_37%v;+* 2Q5 21<\8HHlXxd(! PRX-͊9HOHܶ3IglBѝ몃M;2wFM?k9aZ잚Pz|:ȿXy؟xG^8[U7,fM0nxsQ@IK췽Z:v4?w( @!MY bbSݫ"ŧny7a + -Z?&nG@mʳW7CQ; k wɸZ4dzO0SK5$}, UP1ۓRxA0\DCD.8|m3ޔ2Уft\1ǡy]! +!\ =,I~' +G/SIYaA`zD0!=,ۆ'rU{T3^#8$\ v{ՍҖi;Ml{ĜF7PzR +9kАO~Bo=? A&4&Ght}kM`wlPM& PlͤoKFLq#`|<)lFT=pf~F:OG&> endobj +1360 0 obj << +/D [1358 0 R /XYZ 85.039 781.388 null] +>> endobj +194 0 obj << +/D [1358 0 R /XYZ 85.039 536.7 null] +>> endobj +1361 0 obj << +/D [1358 0 R /XYZ 85.039 516.567 null] +>> endobj +1357 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F43 1079 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1364 0 obj << +/Length 1373 +/Filter /FlateDecode +>> +stream +xڵWKs6Wf*S"A3cgnk5XmN(!);nXz۴.%q /UKRdzň{7pHXE +*gϼa/wN~RJ?f IR~B?wgD8d2~MkzEDE_Fܛ[>8Y=3eb)T$w9:Kȣ[QX*/i%Ԁ]ő߀  E^dZDqm>늺*T~%K 63wыh2vX`iT& D2){+C GLFlУXu2!K +BT>ucXG%Ƌ5YĿ +y·|s-ڮpTe:Zf%!XLEsn'߂>ervl0F pomyc%:=&.o,׹[Ֆ@lvbN?Nhw7$nX5)VÓ,񆿏A| h.%Ut7"X9}68ۖ(Utm[yQ^ ֜.R`fa njKmh]ԮKMW,@qQTm”xt̴N@ٱ{wJ6SGaB/$o 18$;rSG: x2p2(h eţ C ;tc;'5Է# a z{G4:ϩ?;9'3$Rb +n,#6k=C(>(:xVxꄛάb`^Gf+,@$v;lԽwne솴o?.j > b;T&"!ܙg6i,%1@zq{E f.-n*f(}4q͓pvJVc w/\)D8mjuo)2$|p $.V n3ILcwn=j0)j`pcL?U"s{, 7Z2|\@B{z %ABF1|Bx4nM2T;[K0i]W.FetSIv# 6 +k]RK l2++Lafoi%8^,zqp]i *F1fh3]U&2o060;D 4?@.I`بe<=\ծKiШB8G:Bo x%C7 T;id> endobj +1365 0 obj << +/D [1363 0 R /XYZ 85.039 781.388 null] +>> endobj +198 0 obj << +/D [1363 0 R /XYZ 85.039 667.913 null] +>> endobj +1366 0 obj << +/D [1363 0 R /XYZ 85.039 636.387 null] +>> endobj +1367 0 obj << +/D [1363 0 R /XYZ 85.039 497.28 null] +>> endobj +1368 0 obj << +/D [1363 0 R /XYZ 85.039 474.158 null] +>> endobj +1369 0 obj << +/D [1363 0 R /XYZ 85.039 452.249 null] +>> endobj +1370 0 obj << +/D [1363 0 R /XYZ 85.039 418.305 null] +>> endobj +202 0 obj << +/D [1363 0 R /XYZ 85.039 355.182 null] +>> endobj +1371 0 obj << +/D [1363 0 R /XYZ 85.039 334.592 null] +>> endobj +1362 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F37 900 0 R /F20 877 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1375 0 obj << +/Length 3268 +/Filter /FlateDecode +>> +stream +xڥ]۸=b@q2I,@[wH+z͡=@۲F Qf}瓢l9)P,"p8o:y/y(Wج2Y|؞Dfd+\egt)OqV͉li7߿O4^yxӤݿbZ?S ?ET/ϯ-¾p緅Inao[oo=RaH˵1!I4Y>!q0?!MCv@F.{HX~@J6!7pcOzE訙u$:.Pr4^:$+n{*ʳ\w^Žn QD=R9 +!D0R#`M;A5q<^E1G{rw۝K Ñ_.dܯ^y";7˜ =vw򵭞:Nq(sםf6o'aCяǼ t]w &L޻ SHV,1u_(Kί]ϞQ5.@G䐹3)&vS< +v"ɼ)lwqhL;ذdd9i1!β3+m3׼d Щ&*ta2*l~qV$jط#:J2'-~>QR א'l\ݏO l\^-ܬeUGbq{-0Ԓ3ōz{BkWsM~s#_sA:&t4riL!!^=EۈK˄ėWLƶ7]sܠtZYN:MQO%|6<<>~qzH.o1ȻUL$TB=,ˢtaZuO pl KFFYޚϽm.3_m:@[LDdA(ܫ@sBe*/֓Mb:.RwmۣLT xZB.wZag@AVfaY)<4btQojVpzs(.u6k>2y;'AMR,SnU8Wߪ + +|b~UHs3[޾i\(/>SR6*4;sO6[Ua m_T7@T4sW2X!ȶ鳘}W m[7, +a! )^F,dE@bwg^fae,_Nt/'Ԑz LI>^RQc {MyJŞ sԊ)ƫ=X\adCj(»? M޲&%vQ!5a3Ua5>8 42=;=`Dm4ȅN`ƫ7Dn +gVC cHαtkGG\.`u^*t&?|P '8]$Go+V w79f_X3UA]$x It@Bd`$)t xA ɼB,WN7"o&F}3BIzqCd$^ȈohK_3okt3Y2Q,}!p |zAx]B#'3X>7neh\+*@uyy9#jrk[|ę>þ*LNΧ.{ZTFn6ޞԟWǓ7eZC@JVSՠ+$Gr_˿Zm0K!-/\>p +sA.Ui/:jpcӨHr10 9(ft9y+eJz;.8 E=Ocgņo%p+mdLpBh?5Ԥ4-|tkendstream +endobj +1374 0 obj << +/Type /Page +/Contents 1375 0 R +/Resources 1373 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1372 0 R +>> endobj +1376 0 obj << +/D [1374 0 R /XYZ 85.039 781.388 null] +>> endobj +206 0 obj << +/D [1374 0 R /XYZ 85.039 761.463 null] +>> endobj +1377 0 obj << +/D [1374 0 R /XYZ 85.039 671.062 null] +>> endobj +210 0 obj << +/D [1374 0 R /XYZ 85.039 671.062 null] +>> endobj +1378 0 obj << +/D [1374 0 R /XYZ 85.039 642.326 null] +>> endobj +214 0 obj << +/D [1374 0 R /XYZ 85.039 569.569 null] +>> endobj +1379 0 obj << +/D [1374 0 R /XYZ 85.039 542.954 null] +>> endobj +218 0 obj << +/D [1374 0 R /XYZ 85.039 212.156 null] +>> endobj +1380 0 obj << +/D [1374 0 R /XYZ 85.039 183.358 null] +>> endobj +1373 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1383 0 obj << +/Length 3686 +/Filter /FlateDecode +>> +stream +xڽZKsFWtY0e<ږ,y-f$@Q $hmT% 4r'2I=7HEu1\/<1 Iқr)W?}| pw4NԹyh9]~tq3?0?/~}r?]L`^=q@ˋNj*<^m7u~4,1n=aAHp4ixNֶ (85kVoq"a6#꼠Xڠ:‰n8YVv/qI\9ǡ%L@C4֪r0ROH_q'.U$kAI+5i\. +4j nyQ@V%, +e/,zx|ȩ78`װxBs#Sv6@'~:>cOܧi59׻|ޢgU79fr*<2k^S2V-.`RNx8Z|ź÷yl"qykզ-FHj"]kDlTųyuNI4r{DEKUv )$AsldtvC/v@q\< 7lbwh$ι#cjh^z.rb`ESnHk"rqFIY.p#W8XgZ&~h\mˌ +v8E]!F*Bi(R/"kn%ϖ? 0/?H>n?쨽VhF7T#/7P~)r3, +BR(!"5R3J dSƞAx(uޠh;3$jt3$.'),g N8o`fBXu5c@[fyF -ufة병aّ@`(ՑzZjTu¤uvJf$/iP +NA+$1 91y0I)pb%sU3ʨ2öXmzMxJ4L +yt{> +'d!<Bϙ$NyȗexU

ԷDBdjY^dFxYd|溳FKJÃ+-#sRGjPtltb`\Q?L%@׫Su/tZ*0=$Sa7z3|vU5 ra)0GXVӛfj|91]WnGMB []!21Z8{IőV플ͺQx &4-{qP>GRaAMk~rEԋ/m`g䨲Uu %|hlV_AƖ!`*I2a cuY)*!aƋĘ;k/RcYžRɒQi,! ʒpi-Ӥcܙ`6`oBXajHǹT֮9s{-v~|qh;N*!Eۧ˄!UcoYȮJm +lǾN䦞Ze'εڐ)$G/$Je\'ۓO+6ۄ:nYi qBA2ƀ+3ʕ#Tv pRzF'V FF; 4$B`UEg)i&IV wMxpXQ`B |[vai 1>NLHorQJ :ktʬ(S̗ >Y;:|厓S+-օ.37X2FVҽ`bĥ[^Ϳ9Cg]xQ #}BQ)WKş|aMꁡ=E?svٮ%U_8][eRn;oi0@N:m18A\CcZ=Ҝ_Tendstream +endobj +1382 0 obj << +/Type /Page +/Contents 1383 0 R +/Resources 1381 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1372 0 R +>> endobj +1384 0 obj << +/D [1382 0 R /XYZ 85.039 781.388 null] +>> endobj +222 0 obj << +/D [1382 0 R /XYZ 85.039 761.463 null] +>> endobj +1385 0 obj << +/D [1382 0 R /XYZ 85.039 739.701 null] +>> endobj +226 0 obj << +/D [1382 0 R /XYZ 85.039 547.122 null] +>> endobj +1386 0 obj << +/D [1382 0 R /XYZ 85.039 515.597 null] +>> endobj +230 0 obj << +/D [1382 0 R /XYZ 85.039 242.391 null] +>> endobj +1387 0 obj << +/D [1382 0 R /XYZ 85.039 212.987 null] +>> endobj +1381 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1390 0 obj << +/Length 3974 +/Filter /FlateDecode +>> +stream +xڥZYoG~ׯ!2s/ ؎ H$yCjC<3yٻXY]]] .} .dGe(/ rM=t4w?K~qy!w?7zYE^6β,nNtxWowu+|~Kw? s?8wx3⏿%Ӆ?<(ED$\^b/ĬۜarZ3zRXaϣ8uͳ,I|nZ^/hlxQ{foW?'γ a0Oв$'΃G-krC-1t;zxD!g>Ѡ=P/_:F@MiBO'" ђHQb:zH +'_mRqup9!hl!rₘ$0Ah=פS1P",H}Jf[n cV'bVwY<%Ǻ7 +SD/ʟ]= =KZ*|n?r8= %" 4P "HVOR9{Sv#L2_0M/u=a}ދ͢`1Cm;`>$ݒ?4rugglrEj9f#TT=ZeX4!q!z1ȼ%IQwޜvTh5 {z]oAf(yAoѿ4d -혫0ۗk%9-p@vor9Tw ͈_dXɚ$9d^Ucty >Q-rimw\Ug1~G8r' Sc0$v|w\D%!ÝLڌq,֏Lr0|wg9Q@f1]r# tM +b y*`Ğy' 1-Qγ4sQpnuGȕ <>QI$ݎ$zR݈l&,[b[Xd!ke7ީXYcl)IBZ4M.|j  l~bnoAtET( )&3J,^=އ7>fBHv1 NG )瞖_ݯqe7wL\Mu BiZ(ҤswssaXTH4bėG`]#0يz}\#~l65(n“>r yHebvf`k>Qp\X$IҰzICOZqjiW,K6UBO]h*CkmǑkYpn~@٨uq\zl6%Gyqg~fe%.%ZpD rT㸠C*? +ǨX!ż=͒= I;pIġwb꩸tglUm5þEQxUЂĘ8:SE\˸̈Q|.E!ԡ@5g1r|>6hKa@,6@Ŵ4 ;+ڞ[3x#W"K,6qLOIg#QVڍ눇Rx`l`VndTM&<&fhEXG`d橩@Qlql-EřEnn~~|HJ:̱=f)TB-Η3=CnũlX;F 0ef3B§umVg3rJA ", S/tg6IDβ2rqJ?O6+=VSۼrQ@9W7ʯ:IF/$;/?qf˧R7(^:a2rJ3ljJsIW#0ƇpΝ cSx9sO +ja,~),޲ugOS ;h4wF|K{= o?2{x(APZG-C74(6*5S2|{1tyuh=65#oרpk1ӆ>Q曂\DB'4>-Vn%c0/@zAYݘ %&&zc'n7$Z,1ÃK]^ lml#O5MgXc 4BH@r??V ~yddkMeB[MMSM6*8WroY5V1.g]pHzi܆-G@e#r+zIfޢ3Ț݋!>+ 1LO(h~Ng[̛.l & ~dIvn'B-]熾(cFZ`# +ՒMpt["c[b1*i*)j!p=*QtQ7t(qvu*H%MѬeHO78~b#:Qٜ&%zil.gƊx?h|x<&#rY_n7Dg"a<Ø؝Ybcm/띰oQH%lLF|Gxws/fMW +҈bZʽqRYv0&L2jh6#F~ha<:N#:糛_ExQ=#q~2n]u"?gd?x^4 XN/< _;ax C\hW*6I_ sPGK sz$З RԵK(>Rزnt$}-\Gy3h)cJ~RcөDũfU&LOhiv%>$[蛁fnFngb~8?LSj}s޽P^*Hq|FZ5U&L P$jW3C.&P{6+5 $?Jh/E6ET&<+OJ> endobj +1391 0 obj << +/D [1389 0 R /XYZ 85.039 781.388 null] +>> endobj +234 0 obj << +/D [1389 0 R /XYZ 85.039 761.463 null] +>> endobj +1392 0 obj << +/D [1389 0 R /XYZ 85.039 736.911 null] +>> endobj +238 0 obj << +/D [1389 0 R /XYZ 85.039 641.966 null] +>> endobj +1393 0 obj << +/D [1389 0 R /XYZ 85.039 613.231 null] +>> endobj +242 0 obj << +/D [1389 0 R /XYZ 85.039 391.432 null] +>> endobj +1394 0 obj << +/D [1389 0 R /XYZ 85.039 362.028 null] +>> endobj +1388 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1397 0 obj << +/Length 434 +/Filter /FlateDecode +>> +stream +xڥRMS0W(,$K#P´w`88:6jN` {}+&BYɕ1XA};BPEC$#GgRp+,V#$+lvJ) LS@$%_^cn1,`ivD]^> endobj +1398 0 obj << +/D [1396 0 R /XYZ 85.039 781.388 null] +>> endobj +1395 0 obj << +/Font << /F58 956 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1401 0 obj << +/Length 3331 +/Filter /FlateDecode +>> +stream +xڵ]~vr2VD"izA.9)^d[k+KDew}eSpiu[awZz};0;%3tО\*#͉ݼcQZ%w';X/iEU 42YeA_-C,*(OZP/ǻou[d%1Y*S@rͱy/ҸKd]"wЭe E^cZRiqBqøsak쥁mà- Rhg#PH2By s:CD&)gEA<:ncɣ, iw<0t;ȴJvN SmW{G1W1p6o'vqvdm7x/+L  . p'>-#4 +l=OaSMmhp Њ~"=DPT,8JFX0 ͡){+_h, $g\kVDD]IXI,Kc"/Qn3ҭb .X#k:Mո;CNSS,*\e+Sn)H"T[N^s29y*:1jiBcmK)x"3gmE9 +]eLV2?{;]|$HH*K#Bs `d~n3t+dz%sOsE`K|5e$n`é?Q n5{i} }q oL=O#~euD8I}\U3DĠC3ŜMg +-։ ^/Ud/nTbQrل'*jٖTP"r7m̒Ngfl8¬Pir`4xm}<d-J"%$xYFW~px.d!7̓%qK ٧Ӽ2OFu0x~YM`w>^0 Ү$QU&_95pwCO7җo|]l#$tdɥ +ĝRa{kc74":Y5>粱 d5d+H$zV읈r\ac3RqK*E7k^(\Á sU<$)†l[u#V̮a!6#[3VnߡP̡Jm`#x]޺zDx *ZI !56<nkpb$[2#(}cVN߶/"ižTBjW^t|$gLA_ӹ.?%jfdtkEN4 +HB3KI!u[@i P+XNv,/z8 %<==M|cd}>JG9gk*֖h pﹳ`qEs~ + })8,-^f\KKǜ!Ď<8 'ϭ +pviMhۨϞ8D8v|˺eI)!ȃ$~;+]e pl4Ḧ́.]F4ܨ[6&؉%;2g&vGOdӤFCL|,y1wtdRz彜 1Dϩ&;{&.:Ֆͮ*If&<=҈Xl 6z$B˟~/iHZ>˜{БK(a!:8YS3{m 4 s=odTk Vb90sku)?PW$,k`5]eJqܣmD7Z7u E{O20e|׎rl⻻ңIa%Jjq>F0uASqD$R{"r,FI$6Pq6mc*QnL3F3mKlt-*Bʋ͸mB bt[o1^s|ƕGÕdf©JZ&$_iĿB>n'2'Cdq.?GqjZt83L}͹6R.Cp+xh1džA0n +*ˆ}pWQc +G`^[%PūYDRd'<\2BhD0A.aG< $rL1`8au#crg !.9͘w<{lDyIf*ILA$'_fvaB)řL.\7Q"c#B5% ,GߟFs9'6%'lkh?WZ"@5 |u w^I#+,4{MːkfF%#q'5/0St9\DS?.yϩiW{J:[Wjkcɶ^4H*=ڳ2Ab*kЄKRH4 h&O< 6wކxL)E |WWhSny2[Lw B-tQNhIcߑB3Al7Vld GWfrq;Ueb_\[j㇁L>Hd;dEOչB=^3V~wab*[F"/ƴ\x>Dj~ ({5W!{b`κ %RUhQ=: ^~E1r^2WHq omoS%`p>S4x?@k*L);ҧ|O MqAOdCg+zW|_6eg-DTp#DJb?\QDUa-wX@uoύW +N4݅_崲O5ɴ " Xj +C3##h3¶1!퀭dp8}4r?f+>g%Tp3d2L6\ndZ%V,N㤙:N~%]ClcX,Chm/L=c1Y߀:o\yqZ)]Oqg.γ1vs]Wh=yYg<Oh̔k4Lh'k\mmQiZwm҇pQ8 8u3ңDe?JKql1h~Yendstream +endobj +1400 0 obj << +/Type /Page +/Contents 1401 0 R +/Resources 1399 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1372 0 R +>> endobj +1402 0 obj << +/D [1400 0 R /XYZ 85.039 781.388 null] +>> endobj +246 0 obj << +/D [1400 0 R /XYZ 85.039 761.463 null] +>> endobj +1403 0 obj << +/D [1400 0 R /XYZ 85.039 667.044 null] +>> endobj +1399 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F61 1406 0 R /F37 900 0 R /F62 1409 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1412 0 obj << +/Length 819 +/Filter /FlateDecode +>> +stream +xڥUmo0_#5mL`[շAj)# KҢنAˤN>s>?0 (O(fcwtȩìuE@aNd2$4qӹ6I;2:N眓8(I:xaLF:F㩑u,U*ˋJ>{27[C5b.VZbJJV }DfXUCDVxSa4L`i:P,k}kY݉xEWw-5 r|3xDVcO >cPp"{xi|Wz߆9<=Ȁśˬ5ݭYl#u9J:\#W48y}쳲hugZK#oendstream +endobj +1411 0 obj << +/Type /Page +/Contents 1412 0 R +/Resources 1410 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1414 0 R +>> endobj +1413 0 obj << +/D [1411 0 R /XYZ 85.039 781.388 null] +>> endobj +1410 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1417 0 obj << +/Length 3435 +/Filter /FlateDecode +>> +stream +xڵks~&_ +̈́ ؎TvTK4uHx0xH֗mkO&aooooo'܁8?9b<-Ϝ ̼:s#}; L.bN8 /&=[9cV!fbb"µµT^15|=K{g/og7rm7JNpFv{S.|\^Uce}Wu1h۸6ۼXoe@݋/5R.p*R:k ]%.P0DԺvkj\}g0 VBĨLޅ=v[&E60ZH% x e<Ǫ4xyhx,'2`Guc_,"dz.;d"inHHeQB3hCh4 '`}G3eb[];i$i,ui~V]V>tl-ıUﴖp!))1kVSk#z|ObB 9#I\%\Ź|DVM7kgHMQ:]hcX 28ZNpu'M4ucߝ1Du ^^^BO:bpC_˓d$|ydFYl$ɺ;VXYV% IH`Aw%Z_5i:͈W|)=@G8\W·0Cf9#X(9h݊;vi"lͮ$)jE"#>$`*ȗB4ĚpD95FG3CZf|ڴYundُ\kmGYrD +;lh,B ]O{Șm'Bf'oTJq7}S`٘Doq*xˏƫh6|E"\ L '%l[O=vQbr39%!%+H=xGةY3|piIdy ۫_^{YCWʫm[^ľըUGʭ>lc-̀y{P-1riy '{3<Ń .O P޵ $| RgסV(iY +eNjrV3uMB<HsaHq=J5;|DOIY6TV yQ$eȈ]5WHȗ;~o\t{|Vh+Ϫh';>FBOBWz! ®8 d 0lI1z$'+:pFa0&Ƨ|c<"]iԎdD4=*| To~8LAu"p͜1"wjMR!;D.ZdP"t0Hn4B" IF0pVhFUȈ(0 3J&&rM$K%Pȍ4]-G8*H NURխ x?&A;Ryf3^4$r'WO'<}!g۱{_!ߤC mWGeHi)3;atQ7E* r'V/6$ڙL)xl? ҚeR?fo8XOvQ`n8/*^+:-R9L?8t3hpc#Vk? \ZuY|rejY޵K]fn&IL"oZ8T̊W?ӸlC:e7f9~'ForH %㴶-c&׌Lϣ3X͐ + ~}9G\ϤZvnt7C0:?-LNrL'Agҁ7uuN :_FIWD0x)4 ҋ4^pTY~ ,w mGG:0׀b]PN%#ӎ0Q4#XJy$u;NȨՍ@=wzS~&7h~ۥԡSBD@.;Vw.Q +gb"r316_eϜG-]4 Sݖ^1~ea+ \/!$b @5gҙ ZàU\%Ff7hS (|;Am*j>P.+6CSr(6a P535~u;qT,˩.xX菴5I)cwV!VjUɴrĚ1R|;:~~?yCYz-(>P[fo,JjlP= 9e`?Wݤ6tq:;L/p9vTvC{'z?J5? /-TK>Dc^L9Ma8Ǐ(Yx ?rx_]$?p̙<,+RT:iǒ> endobj +1421 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [365.77 614.001 539.579 625.993] +/Subtype/Link/A<> +>> endobj +1422 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [84.043 600.754 177.671 612.444] +/Subtype/Link/A<> +>> endobj +1423 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 410.763 520.758 422.755] +/Subtype/Link/A<> +>> endobj +1424 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 397.213 326.033 409.206] +/Subtype/Link/A<> +>> endobj +1425 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [281.346 383.967 357.854 395.657] +/Subtype/Link/A<> +>> endobj +1426 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 370.115 435.348 382.108] +/Subtype/Link/A<> +>> endobj +1427 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [94.952 356.566 320.306 368.558] +/Subtype/Link/A<> +>> endobj +1418 0 obj << +/D [1416 0 R /XYZ 85.039 781.388 null] +>> endobj +250 0 obj << +/D [1416 0 R /XYZ 85.039 761.463 null] +>> endobj +1419 0 obj << +/D [1416 0 R /XYZ 85.039 673.255 null] +>> endobj +254 0 obj << +/D [1416 0 R /XYZ 85.039 673.255 null] +>> endobj +1420 0 obj << +/D [1416 0 R /XYZ 85.039 644.52 null] +>> endobj +1428 0 obj << +/D [1416 0 R /XYZ 85.039 221.223 null] +>> endobj +1429 0 obj << +/D [1416 0 R /XYZ 85.039 197.66 null] +>> endobj +1430 0 obj << +/D [1416 0 R /XYZ 85.039 177.43 null] +>> endobj +1431 0 obj << +/D [1416 0 R /XYZ 85.039 155.989 null] +>> endobj +1432 0 obj << +/D [1416 0 R /XYZ 85.039 108.661 null] +>> endobj +1415 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F43 1079 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1435 0 obj << +/Length 2548 +/Filter /FlateDecode +>> +stream +xr6_K x>%qMQ;}hKıDjI0{n(3N=g8`_0bϏI^e̟`秳@ $ƭwWg1&~>!ԍɽ3ϟ~?~>p5xUJ"|gOgd{ȋU$ߛ[xOM%pxZX^M'q;kn,֒6ro{q>hxYtd/Tx /aN) jENrnǬ0ۺ* Ïy|)\z2HcK^SjB(=Caicp0Fo5aJ0`{1\1,z-s][^+zūN_qjǹ ݖ]E(-\&aQ޴g–'DlP?wKOY5&d![Xh6VyJ\(d}gSkdfPS0ͭ|fͳ|(JS7jH5Z0V iօQwB8mPh)b5zٜh mSl!a'Ic' -3r'4(9\ qI6Cٱ{jH߭Jk{]{Rn`؎[7ȒUY&ךP,O; +{I^DjŨ!a(+ (R + + ewS|I;ToK0ox!e#&78f=~DM 8$1#\ ;.-J]^7K#kgVw}{[I6β<\,{L,M;63q)w1;V^Cw,xVԡ(IA<[λMB#r=A7 '¨1{GL}?Dz DK;0+{fIPVzw@78k+9ESlo#̵ +x>Ѝ`]7{xoM.9&.HTqgLu!*gxBBh "dcl~fmy a/ HEbDK=>.ʖݵğ[ {N Q"m#xN6-_F3%`z8>x.76fCвVgZcԲ/%.MTGip?Bňh9ɒ(s^KCk6J[pDv/E=DOiA ۵\R@ xαYq@i\7[xAr ,+w5cP9J:p!SB2< 70[=x/pc7#8qGdf;KQw}+X~ЗŮ)7`[u^ (@LB֚sG5/oѥwVF. UP* CW4ֱ( +T^(|Nͮ}z@:TVЛ8F`/@%K %\/S^khےũ:gJJ\iܪЁqdk>E~=(*(E=z dF^b9bfWo'F4a M;GH Fʎtf`8$r?-)Уu]I\j2Wq+:b*I5?4fFUꘗjY.ClDG.*lH#^xS{Evm@]7౛Z5du-?ulp@#<H"@z\ՄJ=7\;<'f鋓E-;0{(#%OE;}ӫK"3@O =M9endstream +endobj +1434 0 obj << +/Type /Page +/Contents 1435 0 R +/Resources 1433 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1414 0 R +>> endobj +1436 0 obj << +/D [1434 0 R /XYZ 85.039 781.388 null] +>> endobj +258 0 obj << +/D [1434 0 R /XYZ 85.039 761.463 null] +>> endobj +1437 0 obj << +/D [1434 0 R /XYZ 85.039 743.459 null] +>> endobj +262 0 obj << +/D [1434 0 R /XYZ 85.039 644.976 null] +>> endobj +1438 0 obj << +/D [1434 0 R /XYZ 85.039 626.104 null] +>> endobj +266 0 obj << +/D [1434 0 R /XYZ 85.039 499.35 null] +>> endobj +1439 0 obj << +/D [1434 0 R /XYZ 85.039 472.735 null] +>> endobj +270 0 obj << +/D [1434 0 R /XYZ 85.039 472.735 null] +>> endobj +1440 0 obj << +/D [1434 0 R /XYZ 85.039 451.742 null] +>> endobj +1441 0 obj << +/D [1434 0 R /XYZ 85.039 456.225 null] +>> endobj +1442 0 obj << +/D [1434 0 R /XYZ 85.039 404.49 null] +>> endobj +1443 0 obj << +/D [1434 0 R /XYZ 85.039 368.425 null] +>> endobj +1444 0 obj << +/D [1434 0 R /XYZ 85.039 334.482 null] +>> endobj +1445 0 obj << +/D [1434 0 R /XYZ 85.039 203.572 null] +>> endobj +1433 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1448 0 obj << +/Length 1182 +/Filter /FlateDecode +>> +stream +xXRH+)SRLH€M" Ēke - UrU}Ϲ ( S +#"˂r> f0D~>HeDSfI>;ϣXjitw|jg]D|XwLAJ΂M :ODI7_S $q"fhƈN5^ F&^M8XȣX)6y,zѴ=SB哗d[O.Ρ{v&i*ҶH[谰 )A2"SIIk+dmnY-0h>kԮcc. d+,+J8Ԟdt|:JHK@-nrdiF;bn!)W0"IQX820p (&Q3>MHpN&H3t ){cT#uIg.l`2Z$@Ԑ9ͮZ/z \/: VeZVϽ-I]eu?e:~g3NY[gO_0odmGݵd=lbv) +w <0MY,`T)1Ñ0CD@ 45ֵomTfӺ, ]=֓f5V )̝՚mvc!e# )%Q,\[ͫufz67!]g'QE܀P J"nY lHe=/T*oZ,1ins6 [$F|g@Du&_]4 GѮ +6̊~d;͌3W#{mOr +ܚw#endstream +endobj +1447 0 obj << +/Type /Page +/Contents 1448 0 R +/Resources 1446 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1414 0 R +>> endobj +1449 0 obj << +/D [1447 0 R /XYZ 85.039 781.388 null] +>> endobj +274 0 obj << +/D [1447 0 R /XYZ 85.039 761.463 null] +>> endobj +1450 0 obj << +/D [1447 0 R /XYZ 85.039 743.459 null] +>> endobj +278 0 obj << +/D [1447 0 R /XYZ 85.039 743.459 null] +>> endobj +1451 0 obj << +/D [1447 0 R /XYZ 85.039 720.743 null] +>> endobj +282 0 obj << +/D [1447 0 R /XYZ 85.039 600.999 null] +>> endobj +1452 0 obj << +/D [1447 0 R /XYZ 85.039 580.404 null] +>> endobj +286 0 obj << +/D [1447 0 R /XYZ 85.039 368.476 null] +>> endobj +1453 0 obj << +/D [1447 0 R /XYZ 85.039 347.483 null] +>> endobj +290 0 obj << +/D [1447 0 R /XYZ 85.039 347.483 null] +>> endobj +1454 0 obj << +/D [1447 0 R /XYZ 85.039 326.889 null] +>> endobj +294 0 obj << +/D [1447 0 R /XYZ 85.039 298.074 null] +>> endobj +1455 0 obj << +/D [1447 0 R /XYZ 85.039 277.48 null] +>> endobj +298 0 obj << +/D [1447 0 R /XYZ 85.039 248.665 null] +>> endobj +1456 0 obj << +/D [1447 0 R /XYZ 85.039 228.071 null] +>> endobj +302 0 obj << +/D [1447 0 R /XYZ 85.039 182.98 null] +>> endobj +1457 0 obj << +/D [1447 0 R /XYZ 85.039 165.113 null] +>> endobj +1446 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1460 0 obj << +/Length 1316 +/Filter /FlateDecode +>> +stream +xYKo6WVH[vznco/rΐ;h c47qf(3sbI(O(fDZ3u3_;JPGJz?(cQwn[Ktw`;$vM Kg)O;ok-fN8$~%᳄$lF#:oB1y z>sԁ1IJ?~lF*i|n]eY&WrU(eQ@8l`Q%$$x8︫nf.%!r&Ͻ vW 'Ńaru8^NE\-d0 ++PuKIIDKD2ن!\gC P?eDUM|G_pp4[c3BG]V>jhV+F)me~P&}jUNPCz/.i:O 2Ap\y-/8-q T٧B~h \# F`qI$zޢ/՝2[dl [f$sG +WSQOFsUd`k%Qt(bR>5߆&;1M76LV=D$#u`\s˕/vA=/35A%Bh<`_YflT^ U/]uzTŒ4p' ?\!OsLdt+jVy>#F hin ډ6m$S5Cq|ˀ0<+8?_xo,D`˞ p4YG~)v:Ԫ2Ti q 4mxH27؄K3\ܯ>ixPwC|bYygk:UwnH[/vn>DS[PL)uQaG-0nEp`eDN֜&6jK$V jayţư6 +F{W sov^%W,LcZj̈{@6Q xB.WyO NBI`ۡ/9Q秱pN88v8"3Kg=T. ǪܩA`*p-F+'k]iQRKI}jM{R)LU4k卖t o==w%Vhر)`DB4D@B.ns*Nendstream +endobj +1459 0 obj << +/Type /Page +/Contents 1460 0 R +/Resources 1458 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1414 0 R +>> endobj +1461 0 obj << +/D [1459 0 R /XYZ 85.039 781.388 null] +>> endobj +306 0 obj << +/D [1459 0 R /XYZ 85.039 761.463 null] +>> endobj +1462 0 obj << +/D [1459 0 R /XYZ 85.039 740.731 null] +>> endobj +310 0 obj << +/D [1459 0 R /XYZ 85.039 587.122 null] +>> endobj +1463 0 obj << +/D [1459 0 R /XYZ 85.039 563.801 null] +>> endobj +314 0 obj << +/D [1459 0 R /XYZ 85.039 534.986 null] +>> endobj +1464 0 obj << +/D [1459 0 R /XYZ 85.039 514.392 null] +>> endobj +318 0 obj << +/D [1459 0 R /XYZ 85.039 431.318 null] +>> endobj +1465 0 obj << +/D [1459 0 R /XYZ 85.039 407.996 null] +>> endobj +322 0 obj << +/D [1459 0 R /XYZ 85.039 345.317 null] +>> endobj +1466 0 obj << +/D [1459 0 R /XYZ 85.039 324.117 null] +>> endobj +326 0 obj << +/D [1459 0 R /XYZ 85.039 283.347 null] +>> endobj +1467 0 obj << +/D [1459 0 R /XYZ 85.039 262.753 null] +>> endobj +330 0 obj << +/D [1459 0 R /XYZ 85.039 199.468 null] +>> endobj +1468 0 obj << +/D [1459 0 R /XYZ 85.039 178.873 null] +>> endobj +1458 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1471 0 obj << +/Length 1990 +/Filter /FlateDecode +>> +stream +xZ[s8~ϯ`aْ/Or)-fu&Bĉ:#Yt.ߑ+aE a28Khy93T56=P:"r'gލ#Hأ 1?=8:wƯkSPs| 'GxQ8\#d =g(ܦV&HF"ru#NGK}]GH–'kvHZ75#hXyՊ7/5#~`h8&5?u]Λ:En.p‡\A/jZ(nYG14U(GNClFkK3Ul_#(+Kz.2˹vC뺆ޘ,OfY~a҃!j BjRaߜSWYذV +B@iBVy\A*4N^RCB8Gg>-9 +! k!#; Ha>ԁvkWuor4@H9Xb )4Em\QIڝ]a\t$`ٻ@؉g48fYV\ZȗYGd2f+5KMOZ`im*+ee``E(&,$KweLLcÝw-0lۃlFUa)d= +yL[w5qxݜ1Pܳ+s +С|Bh#MR7e>[Fª.08$MM>K + ycsggC(0M?07N&,ldo"[;RL˛i< j $ʊNV\BvPgPsmn/i@vif_cx0-4QmCi%57ޭ)]sS3l(gbK{$-̈́[U!$y*! +\΃K_¤s:ľtm L섙~\l:X-f6#QO`;A =Eic_wvKsK Cp[mQu}I.b"υOd kVu I,58c3q'n JIuwl)/=.uaAе12tAls5)_t1Mǹ.w lB|6q$ K>aȄm,)"נSN .^We7ӶFh^Y gxMsJezInf!)foJc]~}5ySwܜ~1^C'EZyvFY+yت|sp˞>p^_С*i)$)6O %C>3\ sw!Kv@GVFșRKCD!UuY2MM)#H^h&{hJD6<)Lli!QӔL*U8n"A&!@Q6+G-'\H$UJkd/ nChzЏZi/rLAqzo7m`0-1o̘QÇܛ7ID@v"}z:sF92{kw@S:btCDvɠ<'mT4ѶotQ˪ћ\>cK{fBVo7Dž$x;r+<[¾]_q;r,,{a$U'mH͏.LuC|(O-V\ᯥ54endstream +endobj +1470 0 obj << +/Type /Page +/Contents 1471 0 R +/Resources 1469 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1414 0 R +>> endobj +1472 0 obj << +/D [1470 0 R /XYZ 85.039 781.388 null] +>> endobj +334 0 obj << +/D [1470 0 R /XYZ 85.039 761.463 null] +>> endobj +1473 0 obj << +/D [1470 0 R /XYZ 85.039 740.731 null] +>> endobj +338 0 obj << +/D [1470 0 R /XYZ 85.039 593.908 null] +>> endobj +1474 0 obj << +/D [1470 0 R /XYZ 85.039 572.708 null] +>> endobj +342 0 obj << +/D [1470 0 R /XYZ 85.039 534.363 null] +>> endobj +1475 0 obj << +/D [1470 0 R /XYZ 85.039 513.769 null] +>> endobj +346 0 obj << +/D [1470 0 R /XYZ 85.039 348.645 null] +>> endobj +1476 0 obj << +/D [1470 0 R /XYZ 85.039 325.323 null] +>> endobj +350 0 obj << +/D [1470 0 R /XYZ 85.039 224.255 null] +>> endobj +1477 0 obj << +/D [1470 0 R /XYZ 85.039 200.933 null] +>> endobj +1469 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1480 0 obj << +/Length 1880 +/Filter /FlateDecode +>> +stream +xZKo8WVibEc/EGylviFm˕;áE(|GҼ"!g" ɨvo͇7=ܮd^͡ +eu{׺K/>;ێŠAhzg{.OނG2 sƧDvo2EQG*>\tBdjA=ShD^m1k}*`Vo]i(ދN0n߬W0X\喠K5V2`+jx%}ViRM pcaB?,Or-*ˆan+n䠕PUf<k2ZEURvPT@9u~ +9'Q"c걤bR) } +[yVȈ)%N&+qQ8'NHpӣ?VqՑ#F|adZFe +t>*Ki_M7 c8ѝst1ӻh +..E[^ -@sr=S,W}$ۄ&ۜC`b"KMpGaI1Oz/t ]:OK!=1,d!<;I?^\ܺ n2_yS\SLoJNxBS5<3s{G TvSISQ`*@54.`BWg%4vG5YFq$k2jS0ؓRρ~5v7T/J7kõUqG 1Dg+ȅ@AyAH2N4 w4ʹp/G3 Lh- +&qjn^ щ ^\!ʤXߛh!uq>gq_z*|9ryF5*b{ m]?؂_9af(Qə-[ۀH+4(ǨIP \[=}Yg3牓$uG>|0g@ި8Ddh6h&p=7).g/ Qj9 iqLH{_/!q1BĐ)ϝSr]_@&gҁjCPC*ICȎΞR٘nWy?lt0i(qU dqdܾ\7B7AK:67v4Q6]ϓ^` 1 Sj:ƳNwws0-b ZorE>l29_B"?2qr\ݼ/|:̷ryФkҒU6~#K/wϡ"19~)+o^//lY\Sv+}H3ĥmܣ0 kM9 7K|DHЇ/[_S&endstream +endobj +1479 0 obj << +/Type /Page +/Contents 1480 0 R +/Resources 1478 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1487 0 R +>> endobj +1481 0 obj << +/D [1479 0 R /XYZ 85.039 781.388 null] +>> endobj +354 0 obj << +/D [1479 0 R /XYZ 85.039 761.463 null] +>> endobj +1482 0 obj << +/D [1479 0 R /XYZ 85.039 740.731 null] +>> endobj +358 0 obj << +/D [1479 0 R /XYZ 85.039 621.561 null] +>> endobj +1483 0 obj << +/D [1479 0 R /XYZ 85.039 600.361 null] +>> endobj +362 0 obj << +/D [1479 0 R /XYZ 85.039 539.126 null] +>> endobj +1484 0 obj << +/D [1479 0 R /XYZ 85.039 517.925 null] +>> endobj +366 0 obj << +/D [1479 0 R /XYZ 85.039 372.869 null] +>> endobj +1485 0 obj << +/D [1479 0 R /XYZ 85.039 350.456 null] +>> endobj +370 0 obj << +/D [1479 0 R /XYZ 85.039 249.785 null] +>> endobj +1486 0 obj << +/D [1479 0 R /XYZ 85.039 227.372 null] +>> endobj +1478 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F43 1079 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1490 0 obj << +/Length 1505 +/Filter /FlateDecode +>> +stream +xYr6}W-dDp%}V.4rj}q<Z-N%!)N("e&gw0?DP;aĈ"gPF $4P8dFILcgrE&{ɫ#B10Ĵ_ctnj/ iprJn@#3|SY DIa*fL:fV_0 JHv(",Fiǣ߆!au;w{٘Иm,TDziHcnȰ!3|2DZ 2R9Q,֐8A"@^P}k?{(΋[6E+6[{?~Y Y3F$N`A8|{n!'Q$d kOP* +ǪP[؞C,#e7O0մ^Zɰ +k.T$4>'!vi.$Q,ZodU)hU|G8552x<;vqwjO-m"R"+4ቮ9ZEY].A/C'J ['R¢q)0yoђ)Cv?Xу>ŮlkVa+KC_d6n: +l{#N5wFF {7 kuXE.o8-K>Rxv߬뉻4˒T<5%8v I=gM0L<u6TFjOնOL /-%COJuyWCER+ѰoR:okm[H`7S 4A $ܾ܏{wP)u.-m *4endstream +endobj +1489 0 obj << +/Type /Page +/Contents 1490 0 R +/Resources 1488 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1487 0 R +>> endobj +1491 0 obj << +/D [1489 0 R /XYZ 85.039 781.388 null] +>> endobj +374 0 obj << +/D [1489 0 R /XYZ 85.039 688.087 null] +>> endobj +1492 0 obj << +/D [1489 0 R /XYZ 85.039 666.886 null] +>> endobj +378 0 obj << +/D [1489 0 R /XYZ 85.039 404.883 null] +>> endobj +1493 0 obj << +/D [1489 0 R /XYZ 85.039 381.562 null] +>> endobj +382 0 obj << +/D [1489 0 R /XYZ 85.039 318.277 null] +>> endobj +1494 0 obj << +/D [1489 0 R /XYZ 85.039 297.682 null] +>> endobj +1488 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1497 0 obj << +/Length 1360 +/Filter /FlateDecode +>> +stream +xY]s8}Wvg,iKҙ@%; `6a{$&$o]{$SÁ?j8,4`r!|nQ18qLJiB-F>7P]&>C9dպ"-G*UQ [;>ks0S8A1$!7'荳P@DR39ӡ'aE[P Ap5j?oI:cD#)% 8^XXmCB[{z3bafe\wqtJ[͑>_rSGt s\")d_=H|}i#ދ"T$.EFi:Ȥ-wQ InBD Ȫ66ƍxܬb@3m֡IzM1CXEսG0QV@1(h1. {$(>K'£9̯ޤҽKHi$O_񹕇~W.Wo<| +^U5vendstream +endobj +1496 0 obj << +/Type /Page +/Contents 1497 0 R +/Resources 1495 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1487 0 R +>> endobj +1498 0 obj << +/D [1496 0 R /XYZ 85.039 781.388 null] +>> endobj +386 0 obj << +/D [1496 0 R /XYZ 85.039 761.463 null] +>> endobj +1499 0 obj << +/D [1496 0 R /XYZ 85.039 740.731 null] +>> endobj +390 0 obj << +/D [1496 0 R /XYZ 85.039 567.596 null] +>> endobj +1500 0 obj << +/D [1496 0 R /XYZ 85.039 544.274 null] +>> endobj +1495 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1503 0 obj << +/Length 1584 +/Filter /FlateDecode +>> +stream +xZKs6WS K'P&qKAhTIq}*H=jF=dơv[쒤J0UPDNܝq3p!,s]ª;2SFK٫=R)Pzg#8d4zy>bjw.?U1"Ju)⌺ΰ~c]T&>))FR91K p=xۚ0K+,Mxt&ixBp'vЛFzyyzlf]Gim~ NĝGne[e8Qo5d\*UE']cwq3fHq` +p ~g&냐Kkh$mk}~OV+X8-TN52S=3N7|X|+B1]X̹OtkK8M".Hk0gz#bo2.jV +tCQ6ٿp) i^7(mܙZÛ7N g.Xb^p<{(w8C42A&G j*dpѭJe1kED-SP$? ߓjgl>Zi/[(ISr1r-iUᙷ `0p*4w~Ą͝:1o>fN5< {eߎ> +>2+4|y=Mgh8eD *,Ke^S^JS;.1 ;qHV `m~.sBreP*${P2G@:ݹ*>wZ^1m-ղzE#ۇdhh`N,;7͊pLǎd:i!4P bB0VAsf!S(@ Iץ=Lږ&9=1ȃ.9VIM{H^E}LT'EvU<ؑĊ pH R]. +Z*03tvS\zX<ӷ&Elk{-U;s ֳfp@$EPUB2I%/TҤGMjƓmvc;pR~ؗ=[G3x纵ެ^7)Ut/Xxr7~e3+O^JbwlU2(50?))\.,X5%siTp8kpj"COCUx1ߦ7DAo3]?)ίBX PJS.44We쎳~m3}owKɓK+ Eqeek4v1mdQEl}2u':bQ_,bqX-:*oL\VBaBl]Ea2۠UvT^cV4w?%R^S?oڡ;xĶ_Tb$QlJwmq,@2bl3endstream +endobj +1502 0 obj << +/Type /Page +/Contents 1503 0 R +/Resources 1501 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1487 0 R +>> endobj +1504 0 obj << +/D [1502 0 R /XYZ 85.039 781.388 null] +>> endobj +394 0 obj << +/D [1502 0 R /XYZ 85.039 372.262 null] +>> endobj +1505 0 obj << +/D [1502 0 R /XYZ 85.039 351.668 null] +>> endobj +398 0 obj << +/D [1502 0 R /XYZ 85.039 125.402 null] +>> endobj +1506 0 obj << +/D [1502 0 R /XYZ 85.039 104.202 null] +>> endobj +1501 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1509 0 obj << +/Length 1839 +/Filter /FlateDecode +>> +stream +x[S8_gjUՇ 4\B-`C2 I_ZI +sib˲Vi+CX'P d5 baXmTpZ=Bl\E"$Jw:iToc̑ tr\;lo-kg͈8>+_qg#&ꝺƈHYp+tW[%xYH$(턜KqQ!*]O>\8MXϫrPYC~j6\p )閅T_iLLIݏyaQͫ%ƥ f"JM81pmQ$)yrOe5 ~c@]aqPHj)RM%:T2 "b4/cA2H6JyFRJ*zIQĝR~)E +nƄi#ARc! +,3A ϪE0QXss#J'depF<^4v^e}!οx(^rhևG8{G +2Q>0&-h?2Sej6LW zʙ j NQT;`V1|} \!+AFJxr}}Gj)A̹6MQ:[x3UmإI9/r{T?qw =FX"ѝ]sb^^i@';LK]n6tJDk!X@/\yʛ +ue|<(E1vcmz\3(Yh-N1)z$gHd%6Xq4q}4Nw߇`p֫=)N{ ttI]'Iޥ!(x{4L]LOy'xh^H=3l@RM{rߌ#B)3B #ӉVcZNRv6LثX? +V2'Gn<9`f3+EByhe8"hQ&+"$ -= 䴬3?wQ[|G5N͕QBUhq#D7I ;0#*|B 0)͙TɸĔ"AΔ+ -5/0,lkث5iBlbJ-[|vdwjaׇ]>OX~<*G),M:MHxdB`+߁lQG 0exS$a3x#67܋. oFB ֐x\/q,[Kc$p0f$Q!l-ԖD{@ͱս"UkN 0Hf@.AoF!T:P2@b] Ǧ%b"Z4`NsY2/ 냍` 38sM:G~pqVIlDF3sH9{6%]&%'Oa/֎ %RZqtcNSʌJ$ܡn5_/U0C-}YLtAã6xw4MxvޞQ5!K:ȧ)pHG'\:5p^H]y/9)`/yx2xwjueI-}^ԥVb @\ \ݤۏ!>Tl +[21W.*(P'јi_LL?jztaxk2gn> endobj +1510 0 obj << +/D [1508 0 R /XYZ 85.039 781.388 null] +>> endobj +402 0 obj << +/D [1508 0 R /XYZ 85.039 761.463 null] +>> endobj +1511 0 obj << +/D [1508 0 R /XYZ 85.039 743.459 null] +>> endobj +406 0 obj << +/D [1508 0 R /XYZ 85.039 457.432 null] +>> endobj +1512 0 obj << +/D [1508 0 R /XYZ 85.039 438.958 null] +>> endobj +1507 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F40 1163 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1515 0 obj << +/Length 2890 +/Filter /FlateDecode +>> +stream +xZYsF~ׯ`j-fQZ"!kdPo38Pޘ\J%13I:p="Rdq `? ؋{"O9ǯǧ7Ñ҉(s9%oz;|?tܸb\JwˁX>s8,T @I3:Ԁdư7 \mwOs ݰÑ\}t~?GC9x}}q[A膡[~l?9y=Q2axn +|,P gG܁g(rHFB*?8 N7=9UC")JF0 9< ~?xO񪋷L}k,IC⮹h'Y~aѷtg3`ojB7~>û%[4,I le>4i/q*OpÄH?? ˧/:|ԮP_F)8)и*+xV﬊ -t=4C*&SNXB=!̧e.JȢs @++ +CK o7X0b^Vsd_ׅE$wv~V6SDu$bf{uv>\%byk {)YC NZ_]~pH#02 v,=Tm.wY |^5}o^DS@ңoBig+D)2t>]#C7Vފ~P^\p4ctB_F)2ރ:`E3 6Έ%"cf(=0)q,{A,]-7SE' A=~'KNO*;P9e 1?1w]}z3CdwvJyH^igZ-)G(Ji(yԣrְy-+~,/f G<ٳib$taGCi@aST+! +<7#Fclb^6)yǔיi㛻0 77 +iujU%|ӴLyaOs<Ԓ$EBJ6jLMauUYh6̹~NCDJ +AF;Z1๭VJ–^)K IOM @:YͤԬrv*-n(*S+q7#]Bu5 `F/l0"ad&S@$)3F3ZrEyKŰݺ^PFfῼC9Wpw-9#pj)Vic/Ei?ZDz(G00>rfn[Wl 9*X?ڞ]FiQ"ivCv%k7=FxQ:GktT + "[n m"$m4zx3-7ֹFz6N$n6+pI ;}W|d^",UEյӤ$#,q؀ÉӶ(Ls6YKXw.8ۑw3G 2MLm;n"et5E]W(#nsΫ] +wU_.G0تŖOlӥ +cSMq򸁔XG<_Y~KCK9 +NƪNv݈63hۥ9ύGM*{~}焚h +[vJx +`%vdR3px}ƃcS7& +Zis="+lɍ.q$,yER N +h&#P>J$5-+dkE{% x%OP=>A5A=WLE-sktls`An!YWodqV =8"0,*iLvKYW麾Op+hgH54d$/)EV>ȝ2 +Bxƈ6'($%Uf+=YN#ў<OQ6R{֐N, V]r7rm$ƣ}0YfL3YS8uc2H*N$wd^ 敲IOnM wMk5k=h{:>p `E.ycI +6D9v,&MUm4k}/jaYe~*#f@fi2ʖGAgr7 +Ǽ8a߭l9udRBj`TL<:4N*Z^a_xT̒aI'v4u4ͻgSTC`.'ku`J +:^D8PP2oFqT2nE16e]o- p[MW޸u[O*f9l;s%PJO*z~)~B&endstream +endobj +1514 0 obj << +/Type /Page +/Contents 1515 0 R +/Resources 1513 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1487 0 R +>> endobj +1516 0 obj << +/D [1514 0 R /XYZ 85.039 781.388 null] +>> endobj +410 0 obj << +/D [1514 0 R /XYZ 85.039 410.554 null] +>> endobj +1517 0 obj << +/D [1514 0 R /XYZ 85.039 381.755 null] +>> endobj +414 0 obj << +/D [1514 0 R /XYZ 85.039 353.62 null] +>> endobj +1518 0 obj << +/D [1514 0 R /XYZ 85.039 332.423 null] +>> endobj +1513 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1521 0 obj << +/Length 2651 +/Filter /FlateDecode +>> +stream +xZ[wH~ϯ+7} C@3gKq4ؒ\oUW,۲I`8_[bD>*`*La[fAb+_=]+HD`12 "ϗ>r\}YfuB RLkPjTɼGsҳ:GQVȯߍ.6Bۖ흮.tjGV#_Mh:fH{gb+XYQl^am>$)؎gXəH&XIU A*o|Wά6&س<:"po{LȬK5w9͋\ͅb5?^F:kpOz]Aq;i{<]k9 `'g(v|cV D7UșՇL6%}^@;/xGȄ/ 2T9T5AEHDB].zmLLT+#4mHʟIُS?…ȆB\W +T5t?rD!*:1q>Wܩ2+h5v1_U2?K\ 3nS񅉹\bw ;! | E{GaK'sL50Ԩ20thƥT7Z l$ +nzHjid"J5 Ԥ'`NCJI_>c=𻻂g}R##|@{%PFU%I$YOfYU~:LV_PŻÑbÒ휣}s0S3 "!C{n^Z56J_4`G!:tŚRI}p=sGy{l}9{=E(G >YNA(o4iS'h r |s/L(i F\aiaa1JqY۫މŏ*|`Z{yaIio'*MV~ O|ܚ$^YlH.-݋=0ĝRmD=.վY'#'uPpx-ƥTЊUYǃXё @޳˜Q{ޏKx93~j,=T_&,oTB +)Z7cVth9ț'5pcEEhk:9}p7XHE($Λt")nҷ&w7L];|z9awm6,Hzr2TxPUzPq|Č}f[ Br6w#J[u ]83 i]zN1]4[!Sp'bmc {{^ q%ftg K\W,oŲ9]x,nS=K7a Q/׷fee)x8f 8XY}pȋ>!A|BE6qZϽlT`Q:6i?;2JvS 1..Ȍ<мRV Lf PE)99&þVBE3{Nx1:j"u`LLC.cCZrU2]]ٝxoظ\U3a!F絼~}`5Ey<-7=S7jl.v1s?"8H$<\—P{ wֶjNM1pPX~ὅ P:({zH5ˍqx4w©UF6fnzqRu3oL:#=jZf=6 &<Gx"˾ߞ7"ն0L5a?endstream +endobj +1520 0 obj << +/Type /Page +/Contents 1521 0 R +/Resources 1519 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1525 0 R +>> endobj +1522 0 obj << +/D [1520 0 R /XYZ 85.039 781.388 null] +>> endobj +418 0 obj << +/D [1520 0 R /XYZ 85.039 601.341 null] +>> endobj +1523 0 obj << +/D [1520 0 R /XYZ 85.039 580.348 null] +>> endobj +422 0 obj << +/D [1520 0 R /XYZ 85.039 277.822 null] +>> endobj +1524 0 obj << +/D [1520 0 R /XYZ 85.039 257.834 null] +>> endobj +1519 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F43 1079 0 R /F37 900 0 R /F20 877 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1528 0 obj << +/Length 1854 +/Filter /FlateDecode +>> +stream +xYYoF~ׯ07{˧r6⦶>y%Z&*QH9}g/(s1j̐1JSXGB- G7'B F+e4~?8:>1/B? w:2|8|wj~}UkR7ʍ/35ܫ[4$ĥHBYR`Ԉ6YiJD]yJeY)Ch]" +(]p lbT!| %PC=|7ַVp1ٮ\vL(endstream +endobj +1527 0 obj << +/Type /Page +/Contents 1528 0 R +/Resources 1526 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1525 0 R +>> endobj +1529 0 obj << +/D [1527 0 R /XYZ 85.039 781.388 null] +>> endobj +426 0 obj << +/D [1527 0 R /XYZ 85.039 761.463 null] +>> endobj +1530 0 obj << +/D [1527 0 R /XYZ 85.039 743.459 null] +>> endobj +430 0 obj << +/D [1527 0 R /XYZ 85.039 635.092 null] +>> endobj +1531 0 obj << +/D [1527 0 R /XYZ 85.039 614.498 null] +>> endobj +434 0 obj << +/D [1527 0 R /XYZ 85.039 551.405 null] +>> endobj +1532 0 obj << +/D [1527 0 R /XYZ 85.039 528.689 null] +>> endobj +438 0 obj << +/D [1527 0 R /XYZ 85.039 281.19 null] +>> endobj +1533 0 obj << +/D [1527 0 R /XYZ 85.039 262.717 null] +>> endobj +442 0 obj << +/D [1527 0 R /XYZ 85.039 197.503 null] +>> endobj +1534 0 obj << +/D [1527 0 R /XYZ 85.039 179.03 null] +>> endobj +1526 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1537 0 obj << +/Length 2527 +/Filter /FlateDecode +>> +stream +xZmo8_at?}XHJbCuM{@[Iڲki慔YNpR!@De83gHS + ͔Y6,N +F~|`ILtr.9l:*Ќ<|:{^_z*\s9ykqahwe,P]*a3nB%׷ B?v&8mBb^sċ=y,wODI~ b}O9djN .)qJ:=6 +yY]kY_WH0vWZx/;jO꿛ח9HgXӴ p(w˭#i|w_/~aȺ kz7ꥠ`B3b^0qz>6E:p0s6 MhΊOˑɯ;' /0AT}bg¤[  +ӢE+2p|_ъe7uY_첆uq4ٙ?Q(` ]5}Tz=UM")zssyGUOMcߊ춨&#pTŗ}!N#Z7Q3,ɒ# j3߉G&)++PrZ,WQ gړz6Pc  u<.|GcB-(D eߤ-Mr\d+YTx6 Ct͚U؃EfG//DOy]#0rFWih^N|8)bB,\c8ABbBCPn@sfXVQ@ke`e1*]\!;Y+N9|8}]nT qƒK,ZєhPV> + #i夘F7>] +{QMwn|T"clۇζXu"xi=zOi4Zϔ]5B_iVLԀ2cѺX1@a~fuJ?`f@xKa[qH FNMg+_s:ﴞAO9}5t{ ?IA =:;>/e3+kLyrYqs-PV׵nXmJ6 +dR<K +juܷІ顃%])OwŒ*HzIݦ^OpTnML}&,:e $W=쟳1`kQ,.o#=_jHQ zhTy=,z: [X"++"o_2{K09`|@ރ`~qȰ-{iox2<[둺K  jwk3I'<53< !5ڀ׸{U$>d\wQJ"F=#wo m+.] .V6<|:aث15/%khQB=`{gdʳY\z[|(i8+ +<7Ik'^{A3dyx eUCʣ˴` B,;w<:n] >$t&҇E= 1on#TY: + 찰rTyłr\$Y7fpHwOE: z2V'wN UodNs4l3e_ӑ^B\TJɮoA1v{~?p(.6ޣMaB*endstream +endobj +1536 0 obj << +/Type /Page +/Contents 1537 0 R +/Resources 1535 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1525 0 R +>> endobj +1538 0 obj << +/D [1536 0 R /XYZ 85.039 781.388 null] +>> endobj +446 0 obj << +/D [1536 0 R /XYZ 85.039 643.264 null] +>> endobj +1539 0 obj << +/D [1536 0 R /XYZ 85.039 622.67 null] +>> endobj +450 0 obj << +/D [1536 0 R /XYZ 85.039 486.952 null] +>> endobj +1540 0 obj << +/D [1536 0 R /XYZ 85.039 469.084 null] +>> endobj +454 0 obj << +/D [1536 0 R /XYZ 85.039 336.481 null] +>> endobj +1541 0 obj << +/D [1536 0 R /XYZ 85.039 317.609 null] +>> endobj +458 0 obj << +/D [1536 0 R /XYZ 85.039 240.984 null] +>> endobj +1542 0 obj << +/D [1536 0 R /XYZ 85.039 217.002 null] +>> endobj +1535 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1545 0 obj << +/Length 1726 +/Filter /FlateDecode +>> +stream +xZmo6_a&5K$[ڦh7m? Ēd;ov- +$_N]ʺn( 0쎦ڽ7fOЮ ԗu4z-.DQ^#s?4'ees:\DOs]ڍwJ +L S;ɉܾO:ǚ]sIOȐ(qJPDH Qh kc2s`}2'g.s-t TMɺ.dkU`wjٮqZɶnps5sDד$.fm`J0%I3`i0Q?@$)wQ + +'6wF/n&@|=Me텊D̰Q#y./MY\9|=6KgSCc˨-Ge<FHx^qg3O)Yk{2>`*XenWy0b ppZoz0Hh?oIDrXOKai Gkk'aL.BldRl*:Wl$|ޘc&i1P +,f@hp@n&=fV 1{XpTJ;G*#ʼ'1-nˊFF4L qL5g I:'HS7%ESVBCwf8xB823eb|GxQN91;4$iX;W<;]92_ + Qpw8$8Omi&CÌ|92պ_Y匦I^XVfQ泥k[JȒx[/k Q._Z)~ 4t̲!O^gBX!Kco"i$/~ i2x8횘bm2p`Wfo%[W؎ Zxe"f]̊}[[F*o.Ouօ&\x 8hB0*߽Q(+(q̪%DǠTMxRuX;fs]"YgyesYQ ]M#MMN }‚i,i8%AM,XHX?mp78A} NZRn^߯tti mp&D: +Tʝ$ ?c9eNh{_hl~[߾iJlU:\Kem 3a@\&Gvuee Hմwy ٝPY=Cv&Yo,xCendstream +endobj +1544 0 obj << +/Type /Page +/Contents 1545 0 R +/Resources 1543 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1525 0 R +>> endobj +1546 0 obj << +/D [1544 0 R /XYZ 85.039 781.388 null] +>> endobj +462 0 obj << +/D [1544 0 R /XYZ 85.039 493.545 null] +>> endobj +1547 0 obj << +/D [1544 0 R /XYZ 85.039 470.227 null] +>> endobj +466 0 obj << +/D [1544 0 R /XYZ 85.039 97.038 null] +>> endobj +1548 0 obj << +/D [1544 0 R /XYZ 85.039 73.72 null] +>> endobj +1543 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F43 1079 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1551 0 obj << +/Length 1323 +/Filter /FlateDecode +>> +stream +xXmOF~*^"PrG$π;_}TwfA +gv3$TVJYɸGK%Nzo%! B/wNSB!q Pv?2ǽi9sFǽh +#/=JDhS<)DzS̜g]HfBrٍEt2lrځ7$8 s\)}^OӲ SI< pIy3M7#=8iff!Cf3q}L<7=r+JK]/$L/9_Gg)_>S$Cba* (}ZCq-v4Y+'WCKʪpEK&L;nĬA0otgrqd-]nV,Hh wuBV݃xx.m6oJz|{N(:]_J|?'~*]h őX5c5 X0-"5DzYvo2nxH?_ ]nh"<|_gWxg{ |;ʒ;3pHGt +"pB<"pH[ Vyt%1zaS}1n6aS Hta_r??MM3]bb:'Z(C:-\poHH +O]Ў0He}9\8:&X2Kԛ Pzp$l.vA=:=Ӳ2sĴ2;h\6q9]oZ]0\S#Wb3eXSDD?6"އKRv/Txe0iZ543CXw0 …P?-٪ +\M^Li]HK[sh9 6$eKh"q9"w@YbB.(4?\jBs !Rjɥ#{:4?$\|80ۆqq(kQYk~M3qQ߮C6PRnbdAQy 6I>y$DAB[<> endobj +1552 0 obj << +/D [1550 0 R /XYZ 85.039 781.388 null] +>> endobj +470 0 obj << +/D [1550 0 R /XYZ 85.039 761.463 null] +>> endobj +1553 0 obj << +/D [1550 0 R /XYZ 85.039 741.337 null] +>> endobj +474 0 obj << +/D [1550 0 R /XYZ 85.039 645.559 null] +>> endobj +1554 0 obj << +/D [1550 0 R /XYZ 85.039 622.843 null] +>> endobj +478 0 obj << +/D [1550 0 R /XYZ 85.039 568.877 null] +>> endobj +1555 0 obj << +/D [1550 0 R /XYZ 85.039 545.559 null] +>> endobj +482 0 obj << +/D [1550 0 R /XYZ 85.039 517.707 null] +>> endobj +1556 0 obj << +/D [1550 0 R /XYZ 85.039 497.113 null] +>> endobj +486 0 obj << +/D [1550 0 R /XYZ 85.039 440.419 null] +>> endobj +1557 0 obj << +/D [1550 0 R /XYZ 85.039 420.43 null] +>> endobj +490 0 obj << +/D [1550 0 R /XYZ 85.039 223.846 null] +>> endobj +1558 0 obj << +/D [1550 0 R /XYZ 85.039 202.853 null] +>> endobj +494 0 obj << +/D [1550 0 R /XYZ 85.039 202.853 null] +>> endobj +1559 0 obj << +/D [1550 0 R /XYZ 85.039 180.137 null] +>> endobj +498 0 obj << +/D [1550 0 R /XYZ 85.039 154.203 null] +>> endobj +1560 0 obj << +/D [1550 0 R /XYZ 85.039 131.487 null] +>> endobj +1549 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1563 0 obj << +/Length 1264 +/Filter /FlateDecode +>> +stream +xYKoFW,ۛkr-Fbk!zz I}gv(YI( ̷"'0|2TEiG/QfigE3}4#L.7GI=KRl@n/Ώ'W׃f*q۹ÙY iGŌVe{w~Bc:U5KSmWBg%"Ij OGuqJ3jXh+j׍GLJshWl]S)$eL;$Lٜ|Z|^-rU^#I&mR:ɍNKheRô (δ M @-⁒5g;bw`#~زb D2) *b/LÄRJff^1Q2r hsN{q_%i.Q5tuY`/ ,V0.!vaՒ&:VH0՞YY̾^g{xCFcߊaU8ߐ{RE1[rw+m3@P7_L A4)p¼3\XV2~ҘhںaϗtJ&s !8 +9 6y '+챘/Wke{(ءDe#!s8OqiIq}Sx}Hw5:m1G$۷Rc9|bZ1)YXf"1n4Nk`PosLm_r&eW9ECaIHv,\6"?{v'^bSr]a`&%!}b!G)S +#PyCqiQp|XՇ'2EPAl\n͟e_1 +NΧ!NQ(ʎE2WZ r9[SdEd1a$A1*RLz xMRʭۥ!! '!R7NܾsBG\o5=h0ҽTM$d^e+J5l'Ux2S5NAE\F2,(z:OT5_ +[A1ekf1)_8)s+D8]I=0_ʷCe gfL=Fw&c|娵* /7{endstream +endobj +1562 0 obj << +/Type /Page +/Contents 1563 0 R +/Resources 1561 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1525 0 R +>> endobj +1564 0 obj << +/D [1562 0 R /XYZ 85.039 781.388 null] +>> endobj +502 0 obj << +/D [1562 0 R /XYZ 85.039 761.463 null] +>> endobj +1565 0 obj << +/D [1562 0 R /XYZ 85.039 741.134 null] +>> endobj +506 0 obj << +/D [1562 0 R /XYZ 85.039 741.134 null] +>> endobj +1566 0 obj << +/D [1562 0 R /XYZ 85.039 720.743 null] +>> endobj +510 0 obj << +/D [1562 0 R /XYZ 85.039 694.05 null] +>> endobj +1567 0 obj << +/D [1562 0 R /XYZ 85.039 671.334 null] +>> endobj +514 0 obj << +/D [1562 0 R /XYZ 85.039 517.119 null] +>> endobj +1568 0 obj << +/D [1562 0 R /XYZ 85.039 496.126 null] +>> endobj +518 0 obj << +/D [1562 0 R /XYZ 85.039 496.126 null] +>> endobj +1569 0 obj << +/D [1562 0 R /XYZ 85.039 473.41 null] +>> endobj +522 0 obj << +/D [1562 0 R /XYZ 85.039 432.64 null] +>> endobj +1570 0 obj << +/D [1562 0 R /XYZ 85.039 412.046 null] +>> endobj +526 0 obj << +/D [1562 0 R /XYZ 85.039 347.893 null] +>> endobj +1571 0 obj << +/D [1562 0 R /XYZ 85.039 324.575 null] +>> endobj +530 0 obj << +/D [1562 0 R /XYZ 85.039 295.965 null] +>> endobj +1572 0 obj << +/D [1562 0 R /XYZ 85.039 275.37 null] +>> endobj +1561 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1575 0 obj << +/Length 1193 +/Filter /FlateDecode +>> +stream +xZsF[Nuoq8`H_? 7L {$a&C0n.f?ŊPa(fDı7: v~ﰒzPoϯU1J 5ޑ 77g~ +!|C0b7ջ^_0no; $R ssK1C0\SŒT()igcܓ>UI!zmC2k}9A3Fx*E~P2QY\HR J$7uH@wԽ +Bcq|v7Z\nPy[CadyLf5 6ݯ.+3ًԒʧ%` XX"!D1=b(6IQ30 @d5+-,DmnR'C;?PE ᚧcRrG<#) +D]5WzxgTd+%->P&K-ptIzQQ[;9Q:sofE"A 3Ogjn= i0mZcߢ-7S8]t7lo3<Å~X?!ޮA*;)$ I8j٠ +"JE 1d6 FI9:~ֲ(=B>Ҧ 2(T]Wy3CGuI>KjOp$C EzP,qmL2PY"K^읹dO-V# n|B߂]b?֊Tf o힣I \P%* \T7+BdӵiyUmY|46zT1 %T1 "іVmilƶOnOE7luOԎ63ܓ2Zw9^34m9;sOy.PE 3io8_ 4Q%lпa!endstream +endobj +1574 0 obj << +/Type /Page +/Contents 1575 0 R +/Resources 1573 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1581 0 R +>> endobj +1576 0 obj << +/D [1574 0 R /XYZ 85.039 781.388 null] +>> endobj +534 0 obj << +/D [1574 0 R /XYZ 85.039 761.463 null] +>> endobj +1577 0 obj << +/D [1574 0 R /XYZ 85.039 741.337 null] +>> endobj +538 0 obj << +/D [1574 0 R /XYZ 85.039 564.607 null] +>> endobj +1578 0 obj << +/D [1574 0 R /XYZ 85.039 541.289 null] +>> endobj +542 0 obj << +/D [1574 0 R /XYZ 85.039 512.678 null] +>> endobj +1579 0 obj << +/D [1574 0 R /XYZ 85.039 492.084 null] +>> endobj +546 0 obj << +/D [1574 0 R /XYZ 85.039 315.615 null] +>> endobj +1580 0 obj << +/D [1574 0 R /XYZ 85.039 295.626 null] +>> endobj +1573 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1584 0 obj << +/Length 1995 +/Filter /FlateDecode +>> +stream +xYYsF~`eSep+c.NFdr +~g@eŴWhtӗ؇?>4e<#dӻ?GRc@ַt4>x1$d*b6a].h׳ŏ׋ST 7oq3G-}x|7RZ2GO)Հ$SG11v鸕WbR]yc&S}ɔ{(az=r/b J +$'K҆6.lIYU6`a|UD*Y2^yu~7`(/&MDDp[Riq=LrX=. .0ycib5;`b++E1$r_m"kZw@ +.mR,*gɦ+pU0p8Dp%z;J$[l0P"eh$ f͛UF_!/.7" 6(fg38I"`? zpW 7o ʖۆrFh#2v:.w#3ktuMdp?wvѥVkޫa'M8TR[fN9-8&+i^문͜-;G$Nkt{uUnunзڧC`L'Cm7V9ZugN2׭ waɮ-ˇ.|~B4V NWbֺ{D#tBsc #v~݃&C7O):~&N.zy 3n"v萓 ( @ADw3ޏg% qoxd<`$*&y6#E%,g]Ќ6fM եem9 S=tB1pŨej<'^ͅ + 3?SzBq{kR5˝tRa{%NjP 2KR +sFpm=Iq!D + z>?,D`?(ìh$ző>N7=ipDӲhr%Y$qdڈLdCKqa\`Wb& 5yus %67B$bFd0 ei| ҩұ.'WG^]MR55m] fk:Db=*(0'RBhA"941 L=J@LG5it d*Ž<+5ȬhD6f.IWya)BTK$|[?SJ8o&XS``-Iq-t$bxM񂫫ĵ Y ۶ aXHjg|V~Mf4Njv I]-b@(b"dM>ֈ +xfOAlX6s)}Z}G[pƚdBĉH8kW3}o5cD ,o54(HԐ7(+ڦ΋[1 +L:'EC͊uY"~(7^,3w Z`ͫ7Zkr@dďY6H^/AӓghG֜qhs>= i|c:hXr~YOLg Oo*  +?=@٫- cō鉔r0U(:;j!;pe+GU uՋ*f\x|y6_\AaT`Õ$^ii]*'j'b%0鿁^E+n05/''IS !o,6[+6E 4zep8<:L=`pn;Vu ?lmߢN nOʚM5ig4M?OM;6LugKi>W%ƴy "^hJendstream +endobj +1583 0 obj << +/Type /Page +/Contents 1584 0 R +/Resources 1582 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1581 0 R +>> endobj +1585 0 obj << +/D [1583 0 R /XYZ 85.039 781.388 null] +>> endobj +550 0 obj << +/D [1583 0 R /XYZ 85.039 761.463 null] +>> endobj +1586 0 obj << +/D [1583 0 R /XYZ 85.039 736.911 null] +>> endobj +554 0 obj << +/D [1583 0 R /XYZ 85.039 356.436 null] +>> endobj +1587 0 obj << +/D [1583 0 R /XYZ 85.039 335.239 null] +>> endobj +558 0 obj << +/D [1583 0 R /XYZ 85.039 238.63 null] +>> endobj +1588 0 obj << +/D [1583 0 R /XYZ 85.039 218.642 null] +>> endobj +562 0 obj << +/D [1583 0 R /XYZ 85.039 114.582 null] +>> endobj +1589 0 obj << +/D [1583 0 R /XYZ 85.039 94.594 null] +>> endobj +1582 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1592 0 obj << +/Length 1994 +/Filter /FlateDecode +>> +stream +xr6]_R +Ah\'mI4v<0mqlQ +b$RǴMf, 쁽id440Q4MW9&!2m4UR2^\:;Ǔ7/yF͟~uoߜ~q>{/ wtd4R8&57-O'bbk;qǯe+vXb<=[+']z'M=+ou&uFwƽpM0"ܳ5)\Yb}_^,|li=)E}˱R'7p$mnrP&68T^=OL-Mj@8mS+D]EJ+Ҋ0l$~2>oK NJ% 5]n{%wpaؖіj6NW6fCE`:aK3vp'у:T6b"' kօ-ACW-4UɊGIb 7KOz3XhWEʽ*b11=~r,ά/|ɐRKgb4V=MM:UYG=&`CN8# 2pC +'I| ^:I +::/ :蜕u:g=͜Dj4TX[Fx Ô|>VmDc01/ξ '.Vvbp\tDFhGw쬤Fuo0ťsBGUE.AO EX9c'&6i09Sh036J8Pfl0s+a//⽈ SOg~,l^A\qK}ϟ@}\Jn+~=:)YgC,[9LV } m4[b3z:#VԊl|]gBG^0>삄$\g JXg;05UMog6l2݊IGkR21#cs8ǎ>ҍ֍c8p<;%%-Z9"0/p1~[q\]oPaTXl;Ul$M[aYݔvCT P9dk Җ[z}x4eES\#5j]1TI9ބA|9Q+l8|<`j|pl|"U" +uɅ3tՎdJ!JkgiN5e/tinC{^\e}  H\_e7Q+Sh gp嘌!b!κJH= ]Wogt1Q+ֆ/݉ڷ6tIu͗R`EX587t(=$mlY )Ozf66% lE3BKk*>&@w,Ngīo_͏:渶ӗ]8ȑ;C| 0s_&m29]"a "i*1N!!&8]#k4uam"o-#hIj|jӻo POb&A>AU+JwpC|MՃ.|fmP' M %%7 ?dBn a"G˗N,/_K~;2Hvk!2V2F[O @،Î;Q_˜zx15cFb uxKooGՑNI_ uZ'$|i+Nx)>OWaPFXp ҨVId 03t`]2Ʈr2j3Sub,x!gIӾFv̓bc;[endstream +endobj +1591 0 obj << +/Type /Page +/Contents 1592 0 R +/Resources 1590 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1581 0 R +>> endobj +1593 0 obj << +/D [1591 0 R /XYZ 85.039 781.388 null] +>> endobj +566 0 obj << +/D [1591 0 R /XYZ 85.039 761.463 null] +>> endobj +1594 0 obj << +/D [1591 0 R /XYZ 85.039 743.459 null] +>> endobj +570 0 obj << +/D [1591 0 R /XYZ 85.039 658.326 null] +>> endobj +1595 0 obj << +/D [1591 0 R /XYZ 85.039 637.732 null] +>> endobj +574 0 obj << +/D [1591 0 R /XYZ 85.039 528.809 null] +>> endobj +1596 0 obj << +/D [1591 0 R /XYZ 85.039 508.821 null] +>> endobj +578 0 obj << +/D [1591 0 R /XYZ 85.039 422.153 null] +>> endobj +1597 0 obj << +/D [1591 0 R /XYZ 85.039 401.16 null] +>> endobj +582 0 obj << +/D [1591 0 R /XYZ 85.039 275.38 null] +>> endobj +1598 0 obj << +/D [1591 0 R /XYZ 85.039 254.785 null] +>> endobj +586 0 obj << +/D [1591 0 R /XYZ 85.039 190.894 null] +>> endobj +1599 0 obj << +/D [1591 0 R /XYZ 85.039 170.905 null] +>> endobj +590 0 obj << +/D [1591 0 R /XYZ 85.039 104.632 null] +>> endobj +1600 0 obj << +/D [1591 0 R /XYZ 85.039 83.435 null] +>> endobj +1590 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1603 0 obj << +/Length 1646 +/Filter /FlateDecode +>> +stream +xXYoF~ׯ[%ۢ(GN,9/i`0m Hr)eqQEcvV臆qm( +l+yk[GOME|5 |om荧4rrx<٫&wѴ!L +e|}sPE3O0LDQF1U5_&[.tE"i:m핼ވi6fbý&)$Rtjc6 ]Vd2|y[(2MłNONw[&ӷ D0xu'DpuANxId/攤Eo /Gyr['? dfFR Tu*0]&"sꍋoV}ݤ`<2fU`P&ߣBۓ׎8[VEBGLJF +)Pʲ фڴY +Cw@X9U4^i)yX2< joqn`h6u,T|C%@ / h +3 i5aekx<f9">}OrvMcIhHY\.+OFgPNSpig&Os+mKp78R$Zr"r2[JH+4ZfWYZq+*P2ytu@ +=Rn)|QяCXcE? ̯-1'`AZi 5fIQ8.-&tG,Iev.kfEZq[Prd_CivH6aS\pz>^LΏ_9kp]'x(#e:nx2B:npU*s5*IlN(BU~?PkO0$ pj{P۹[gb2(ԩagm. +bV ٥8v)V&2JKٸ컎;3$اd$4ߝDld9eP`S3fiJH/'%}i2 +,lW9BdEu`'rR3"; Bv##y$#AJ]WX\U9`pkA~{-kUOѕP5o0YdW|\d+&*h-:45C2t +Ԫ{7d)[{/e|И5|Ҫ+C"IShw#[Q#N;Y@VJ:x2. +%=,}N8ug︣@ +Il@U{sJY,P4%1[C@X6^"\mc`b;(SPD +qO#W\g;4.@ʆرB,@qR>>>ŀ> endobj +1604 0 obj << +/D [1602 0 R /XYZ 85.039 781.388 null] +>> endobj +594 0 obj << +/D [1602 0 R /XYZ 85.039 761.463 null] +>> endobj +1605 0 obj << +/D [1602 0 R /XYZ 85.039 741.337 null] +>> endobj +598 0 obj << +/D [1602 0 R /XYZ 85.039 707.744 null] +>> endobj +1606 0 obj << +/D [1602 0 R /XYZ 85.039 685.028 null] +>> endobj +602 0 obj << +/D [1602 0 R /XYZ 85.039 338.256 null] +>> endobj +1607 0 obj << +/D [1602 0 R /XYZ 85.039 314.938 null] +>> endobj +606 0 obj << +/D [1602 0 R /XYZ 85.039 273.465 null] +>> endobj +1608 0 obj << +/D [1602 0 R /XYZ 85.039 252.87 null] +>> endobj +610 0 obj << +/D [1602 0 R /XYZ 85.039 219.277 null] +>> endobj +1609 0 obj << +/D [1602 0 R /XYZ 85.039 196.561 null] +>> endobj +614 0 obj << +/D [1602 0 R /XYZ 85.039 119.598 null] +>> endobj +1610 0 obj << +/D [1602 0 R /XYZ 85.039 87.276 null] +>> endobj +1601 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F36 892 0 R /F43 1079 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1613 0 obj << +/Length 1314 +/Filter /FlateDecode +>> +stream +xYKS8W]i[{caf!#sb9ĐԒb-=bho4:}|-K"aθ휝`l|P"tCu0H%; +wy͊i :[E(ER4.ps^5Sejt9XF'BrogEUA#gK{$Fsgy8ڑ"RIˋڷПs@d|IIBS$J] 4'Δ8A)M#YdugL8wYNv1Sa +ԳNVIEj=B 8G< ֬ +8v>,JL4 *`Auu]֯hCDF~lڄ&)wCux|,|r~=Q=VU%~|뎣6S\0Zf.dWta?Tё㳛 ~^,b?m%,`Mh>xh mBUlS ͠=8u!Fg}tN^#:4n/O9k~7#2@4iZf){s1Zmh.F:EX5^Ɉ};f@$m76EI|c\]s桩$q3E3Ri# UNAB٢  ++.bgU4u05W;;է/R,'Y&\IgL}e] M *ں*ӕTiP^J>EU(()GPfYs[2{,eZ qܐ+KQwMǦTYYULQ.Xоؙf5d frTκ0$-uXg2uW g}u8*u8rGx,0X8vq>FHX_&j.wd޴35̟[,8!,+ʦ[$ Gendstream +endobj +1612 0 obj << +/Type /Page +/Contents 1613 0 R +/Resources 1611 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1581 0 R +>> endobj +1614 0 obj << +/D [1612 0 R /XYZ 85.039 781.388 null] +>> endobj +618 0 obj << +/D [1612 0 R /XYZ 85.039 761.463 null] +>> endobj +1615 0 obj << +/D [1612 0 R /XYZ 85.039 741.134 null] +>> endobj +622 0 obj << +/D [1612 0 R /XYZ 85.039 698.974 null] +>> endobj +1616 0 obj << +/D [1612 0 R /XYZ 85.039 678.379 null] +>> endobj +626 0 obj << +/D [1612 0 R /XYZ 85.039 482.122 null] +>> endobj +1617 0 obj << +/D [1612 0 R /XYZ 85.039 459.406 null] +>> endobj +630 0 obj << +/D [1612 0 R /XYZ 85.039 260.422 null] +>> endobj +1618 0 obj << +/D [1612 0 R /XYZ 85.039 239.831 null] +>> endobj +634 0 obj << +/D [1612 0 R /XYZ 85.039 170.573 null] +>> endobj +1619 0 obj << +/D [1612 0 R /XYZ 85.039 149.978 null] +>> endobj +1611 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F36 892 0 R /F15 895 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1622 0 obj << +/Length 1654 +/Filter /FlateDecode +>> +stream +xZMs6WVS$\2$Jj890"mqBQ*I9q~}wRDN-qX bv˰>*B!#" i/aU3h_+z1R}F?0SFs&3w'>{4z;$@?~ xӣDڔ0ӞT()7\Ŏɾ}'UH4y0]s +Xpt s"D暚PVdc")]9s3]&ife66z'aٽy(p$ k`lQ\:_OR /E1З6LSÌg`ٶ1d=7$ruכt w,d![:ɪbU-'?b,#+ו=֤e{0(.w^H]U9 +RJg1zK{(zYM9Yzi !$plb**kݼS8Ҭ 4+5ᐤvh?@N4hޞFAvSJ&y & N zΙˬ`/ e8a3GxV{$< ~ {=Om]\ N:؜D i4v#[^pM;S"CuYheRX[ѴFSPY񥬢 +×UaD[u ۸*'gUa- ?2";c HP_8M5C5}"hxleZI޲5`v %)M +4!guLI8!%W]ޝZ4k +Z4c)DYJN yuAEbU{/CW`4{£0iXdzeys_Z70M$;b}!QLMʴ ֐1AR913l5ZSML]jk +xzN9WTe ,J2lr'q^l˯i5U-阙vr?Say=4]o,Qo^+!SiV3ҼXae)g/)+sEk4:oERig^9T|dXq\3 TlsImZ8fЗᖧieXT|9/_fveb$n۸}m!l$w'G*r,WFGQo뜅e'k<9ύ;rq6 +weaX%p<šO|dE}SeR3E'sd*VT!MlȄ'PTlTV/l{DqRܷB:&XMތ-+W`xc۲ +5] ^޵>T᭰FCa +౐_}iݸîf ]eRjg;KrAl=LXMssլ YiڟnY7ӖWqe?dC/"W|/:S ^`%elg}4 Px7{)$u٪w*GJ;gMIdendstream +endobj +1621 0 obj << +/Type /Page +/Contents 1622 0 R +/Resources 1620 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1581 0 R +>> endobj +1623 0 obj << +/D [1621 0 R /XYZ 85.039 781.388 null] +>> endobj +638 0 obj << +/D [1621 0 R /XYZ 85.039 591.485 null] +>> endobj +1624 0 obj << +/D [1621 0 R /XYZ 85.039 568.769 null] +>> endobj +642 0 obj << +/D [1621 0 R /XYZ 85.039 411.417 null] +>> endobj +1625 0 obj << +/D [1621 0 R /XYZ 85.039 379.891 null] +>> endobj +646 0 obj << +/D [1621 0 R /XYZ 85.039 314.138 null] +>> endobj +1626 0 obj << +/D [1621 0 R /XYZ 85.039 293.145 null] +>> endobj +650 0 obj << +/D [1621 0 R /XYZ 85.039 235.379 null] +>> endobj +1627 0 obj << +/D [1621 0 R /XYZ 85.039 215.391 null] +>> endobj +1620 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1630 0 obj << +/Length 1888 +/Filter /FlateDecode +>> +stream +xZ[o6~ÀCđ"ˀ>ۦ4Bmɕ9$8t$D/ߡú~X70NڽfvЮ ԗr F2^87ƃa;A:c}s}=uԻ ,\Aϑ%NAJxvEEGHN~uZQk߲h;\ȓvm]NF+}=j7">1JIaRtdNEC0YŒDHv a> soħ&K="@hMI r zP8s` ۞:|؃0 GDU I߉7:'+ǩ]\S" }R%֧ʵF`kpM YgV +~W/$4A'~!L, 2z1l*I-!=b.`n4 QԖ!w?œ'^=r'ͮ KM~jI<;)&EX`ާXߟac9phx$nx?0)kv "Fkh08hV0ښ6ew)"hP4MjT'MWϳIkP=rE)+߶PT@ PL#Ux0$vtis"^҉PXio+ tNE }eƃPPԹTyF=MrL{G訐Ը֛&Yaჼήi1EL3%V,̳F[w4lbNl0A `i%Z$jk:l:;Ӹ)̘=yakF{w@|1hElP0T}òxe\0G[`Rr/9 }H%BӥKE umZb6mk_EUSW? +xNvkOE\LJW">U)&MahkA +:ҀLhn6+a ;Nt6ٝ o=C4E mJ)ZNQzmd8љa̴f + 6-FXhp}MۋBsOHj\m(?0(|ai+k+#Ch>s4ޅltޥ,U'6uzJo@Ȗ~hұo Ѝh=G=e>_\RBKo8 ͒/7,&& q VƹW@|tx&~a:5NF5sZN7DbmS<Zu[zٴVƘ:3I뒴B 'GCxL-kk"׀5tOj lRͱ2*Lc 68zCv{/1_endstream +endobj +1629 0 obj << +/Type /Page +/Contents 1630 0 R +/Resources 1628 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1638 0 R +>> endobj +1631 0 obj << +/D [1629 0 R /XYZ 85.039 781.388 null] +>> endobj +654 0 obj << +/D [1629 0 R /XYZ 85.039 761.463 null] +>> endobj +1632 0 obj << +/D [1629 0 R /XYZ 85.039 741.337 null] +>> endobj +658 0 obj << +/D [1629 0 R /XYZ 85.039 609.877 null] +>> endobj +1633 0 obj << +/D [1629 0 R /XYZ 85.039 588.884 null] +>> endobj +662 0 obj << +/D [1629 0 R /XYZ 85.039 557.961 null] +>> endobj +1634 0 obj << +/D [1629 0 R /XYZ 85.039 537.366 null] +>> endobj +666 0 obj << +/D [1629 0 R /XYZ 85.039 476.315 null] +>> endobj +1635 0 obj << +/D [1629 0 R /XYZ 85.039 453.599 null] +>> endobj +670 0 obj << +/D [1629 0 R /XYZ 85.039 343.455 null] +>> endobj +1636 0 obj << +/D [1629 0 R /XYZ 85.039 311.93 null] +>> endobj +674 0 obj << +/D [1629 0 R /XYZ 85.039 311.93 null] +>> endobj +1637 0 obj << +/D [1629 0 R /XYZ 85.039 293.727 null] +>> endobj +1628 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1641 0 obj << +/Length 1313 +/Filter /FlateDecode +>> +stream +xWo6_EFeUU`2Үg+CUblՒt㑶qawݏgŸןDsɤU==OKqG~KzG:%wYn>A``8OW?]^z>^,ɇ޻eb:(@zwn?7>\'']Nj~ @ޢ^ >dh$^~}>=Dxcg < ȵf 󬌗&Ax`h]]V?t4C3t?Vb)MaG3rB_fl%`B͚=⣠yb{l]ۗyifO,<RDaJGA=r+WEJf;b̈f6S!X#c';\tC!6CAQ ǮuzI$-r^Em Pe?$vEYҊo$Aa@GƳ $@9աUZ/B +bx*ء orN~s74A2hF>/pr!V1:=l2$N`m7!ԌB#gșX1|L$ymTeaʆr*II`_VDx!HRR.qe7ːn7ur̰uH@>H(F/JXUcJ2yډIQ1Vw̳S]4^%u﬙AL¹ ;B҄H2=$6i ѧO꫓c~&Vq2m{>Nx@*_9τt0w&EGJ_S Éu;n8UdU؀}vX1A[rՃ5IA6\c@ hhh*!\˔6bKpFT{k-d*<XPxo9X*@??׋R_ӟZ&)7Q1>ۉ v肭Rh)W\Г^I5N> endobj +1642 0 obj << +/D [1640 0 R /XYZ 85.039 781.388 null] +>> endobj +678 0 obj << +/D [1640 0 R /XYZ 85.039 761.463 null] +>> endobj +1643 0 obj << +/D [1640 0 R /XYZ 85.039 743.459 null] +>> endobj +682 0 obj << +/D [1640 0 R /XYZ 85.039 102.539 null] +>> endobj +1644 0 obj << +/D [1640 0 R /XYZ 85.039 81.546 null] +>> endobj +1639 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F37 900 0 R /F15 895 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1647 0 obj << +/Length 2019 +/Filter /FlateDecode +>> +stream +xڽY[w6~ׯ[K/}s^&rRO>mX"s)J윕w 73,qdqIh،#2Vk~$2_\ziUJ9a99~rwF?;GZ@_F퍗㷑'TfF+_fMFU"ݪ$̀J.2vU6: tvYďي`MˡF mS. K?^JPfY]uL&Pɗ7iZSnxg3L:DU,DJ2 \O&HJ6zW/vUUuKZR!hB1RSK[}(]7?*D| җ"1c>3B:2z|HEө;Cem]R@)!DvHvt}l_P{L;Q4tҢ.[s`TE]hvSrBA)CdO9!|qEKI5Naqb}xs)P +8Jce@4yMvS^aTH | sH8wX@9kZq~!J3-Wǰ0Q->[,\A { +tw F^s&}@&SE1 ~xWloJ?M@ ?W7obW\슛JdR6B+x+ ֹ˲EO{7 r'+ ?-++Pl^d#Οendstream +endobj +1646 0 obj << +/Type /Page +/Contents 1647 0 R +/Resources 1645 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1638 0 R +>> endobj +1648 0 obj << +/D [1646 0 R /XYZ 85.039 781.388 null] +>> endobj +686 0 obj << +/D [1646 0 R /XYZ 85.039 585.174 null] +>> endobj +1649 0 obj << +/D [1646 0 R /XYZ 85.039 556.439 null] +>> endobj +690 0 obj << +/D [1646 0 R /XYZ 85.039 440.216 null] +>> endobj +1650 0 obj << +/D [1646 0 R /XYZ 85.039 421.95 null] +>> endobj +694 0 obj << +/D [1646 0 R /XYZ 85.039 421.95 null] +>> endobj +1651 0 obj << +/D [1646 0 R /XYZ 85.039 401.356 null] +>> endobj +698 0 obj << +/D [1646 0 R /XYZ 85.039 203.603 null] +>> endobj +1652 0 obj << +/D [1646 0 R /XYZ 85.039 185.736 null] +>> endobj +1645 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1655 0 obj << +/Length 1530 +/Filter /FlateDecode +>> +stream +x[[sF}WVi&}W}K\R +xLj+ c8N޾ٳg%5)Ui,#U6/) +vz__*d4nMzo?ZN !168뽓Vؕ;twW$R S;ڼ3^5(m~2%,W QRFlW'ǓH*Kb%J_E!fr5ˆ],r<* +UQ>h z$Y6؅-ƂSE΄EbBc6gST#!rb(;=)PqAr8 9rjnI'HCĥ'.hUU|I[ĢP6 e +/]d0PP +Ъ~AEټlRS'86mI׈WN" |1R٬WwqAe9(Rb"C?&`ZOEtK0 R׻ЄMW_"8N<&5 `qx-n\,&Ř/n@dx+?ks~ra36cԢ +Xm9 gI=/ w=_%` ւQ6!+qz*z ?a~L@EͿ6wk}t'%w"$cS67~> endobj +1656 0 obj << +/D [1654 0 R /XYZ 85.039 781.388 null] +>> endobj +702 0 obj << +/D [1654 0 R /XYZ 85.039 619.934 null] +>> endobj +1657 0 obj << +/D [1654 0 R /XYZ 85.039 601.668 null] +>> endobj +706 0 obj << +/D [1654 0 R /XYZ 85.039 557.183 null] +>> endobj +1658 0 obj << +/D [1654 0 R /XYZ 85.039 538.71 null] +>> endobj +710 0 obj << +/D [1654 0 R /XYZ 85.039 494.225 null] +>> endobj +1659 0 obj << +/D [1654 0 R /XYZ 85.039 473.63 null] +>> endobj +714 0 obj << +/D [1654 0 R /XYZ 85.039 417.718 null] +>> endobj +1660 0 obj << +/D [1654 0 R /XYZ 85.039 399.244 null] +>> endobj +1653 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1663 0 obj << +/Length 2581 +/Filter /FlateDecode +>> +stream +xَF}B)`Űys8u8Ύ ERcIԕkc`ꮻR3,\/fI Mgƛm`7J (p0ŅY]ľ%oC7ho}o{n嚀ů([["cuW5Clp8/i/5nYNQ^#p$7S*t0>V|07 p6lϼlzr[~;Ci{ vrmEɢ6qr$w)9lvhwxH!GNzUg+7A|s z7+t@ ._|ZDj@{^MGaFu (GtK^OOF2U+SPdȾ$Zhю\ Lk@CW|3d9+Kǘ{A<UFnʋ*>Kka۩Wny{(A(T>QQdҟZNk3~^ES zEyV|W.cv5zݝۃьC&+kvedñ:t Fy" LxdD]uL V -gH)R2JQܘWU"kkקd4E -B#2`)0 }wq"Jz+IUUy~cDҔ\SJ(kȄ4 -T -/q'>%QE)mD`m5Il8$gHT3aHB)Fu}/kZ :;b1-@ݻPoƓ vjѼ#}(ꞕH^Ɔnfͫr4a3V>oۊt Q cǺM=ҙ.zGϚyM < ގD )U9E:ũ>@CJ] - -)zdz}\ ٜb`͜4hQZZfBi" -l5MvW]:)PL&tؾH~2 Pɨ꠽||x[m KJR*kQs 9kaoS#VT*x[!}'g?qXW\w}+ "^//߈LJendstream -endobj -638 0 obj<>/XObject<<>>>>>>endobj -639 0 obj<>stream -xVMo@+Vծm%"i9@`z UaKwA$-*d ̼_z ;@:~ ^m;np]S -b -8'xup="T,}2ז,gm=$ib"a0p Q\aeJ&rN 9?:=NV"~܈7iW˼gc .l(;u\#dez@ `Y[8h0g|0  kn &mv kCی9p ʤ(nB"EJrPzGSrפm۞m;یR5Ȩ9dfr.ֱa43p,2 -O r 1|T^5Ӛ#אJe7ax8ٟ[1;O i -',yìk(dD8'zLdArZ 5Y, cqU;04WeOjD`_)F}*s)W,1R%^>pQNFW0(\EVhaTZߩ01HLXз » -7q[7 y+endstream -endobj -640 0 obj<>/XObject<<>>>>>>endobj -641 0 obj<>stream -xo0+m$VXj%쥚P?w&Vx8 _M% Q }j>M&ﳟQ ^ņaZɶ g `MsBexک2OYޤ+3(˜@+GHrl88,i4"L0yn6>M>>DfC,\`)A9xsW.:AábU~ѝKQg;!oȓzMSj՜݈9Or;({;MFR:|rle ]rQ.ZGb[=M,Mt=854ϱ+ )oUѭ j}Aŵ%(6T sr N -jē4yo:R$uyǾnsDh<ƙc?J̮n![ZJKO۩c 3-Ma[i Ћ11ۅ޷?Pgmendstream -endobj -642 0 obj<>/XObject<<>>>>>>endobj -643 0 obj<>stream -xUMS0W:*9m$^qm`ɵe -]9a2gݷovP1lg=J(N@|p|a!ð L {&(0IT `7ncjFtfH 쓩s^ ڸO`l8:,NԼ(A+w) dԅn7i -.GJ}(9Xe6?Z([ -#NF)ЂCn'"4/!(oj\B=xa+^ ->gG|MHV9-;I1I-/x>>tm+&Tr-MM#vx1}{x- JYPDUQ`:9nSBV̀7ﷅ?&_轉%ݕJxsن<2L8 -'n.b*Jjc8z=6c -Z~Ddr( a0 ZH}RJZy:$6]FEpYs,rl$)k/B4gosl zMN'7Ue_+sb_[[ b]Np>CMwvT8sendstream -endobj -644 0 obj<>/XObject<<>>>>>>endobj -645 0 obj<>stream -xV[H~Wdd⾁ƴ mO6PScíNf]D8_}:UF6`fd -ik:L ]3gďpdj -䀏Lp>=b//fðؘ`-:ygd)TR4wURH \.LTHG -‘9Z1LeIx%*BctU=v.Y fjmk{ѣ%`&n|Db{"C5_dfȸUhW*lb<E+ -FWfET@_ӹ*L P`=-XR!; #ˎ͈g9(ŏ ]!0," y _DCNef[j )(׶)_ѴF,uY6no -\ffidA!R -9?hE1(Pr;58C7;F־Cn33ur&e -$;ъͲ6t8mQ ;1mմVdv6rE8 -7~Q!}aO^~RE7Ia-1 zOKV[5щ7+mv7W&: F[rf/ h|Faopkz&,-nN{ѪY=l]ߚ{,;1]_'w`jh - Etm.:&Iltv -2f6؞bwXRlwLE,ox9 b)Lւ-ךYljUV{z~\endstream -endobj -646 0 obj<>/XObject<<>>>>>>endobj -647 0 obj<>stream -xVRH}+[XlǗGqU Ԧ[X$د3uU톊 q}Nϯb$oSG|/b l%)/:hdY&9 4&~oNu=p.IjW)ii.2wIE`{M"NFӛ/GӋpz#p0i7󞘹PF4TڿDzZȊJQt:I9zYubi?oQYj~'b-etJ43@a*Vbu9K,XJE͔\"̥f>b4\RH[kRIh}K&'&4x_yjJ1PS)E1~֭tUu[GhWVCݡ`Q9APc"UbH 'N7heu":_]~$TB[:]%BHݏz3 X&P>"tx $k4䜚#VR:uK׾q?‹ -aa(tm? -cfV*〴h -IwB5k@xL)wdP~^b];EABp)E<PJYK\zg&z$S@Z{p 1aJB#Z50WKg'rI b -Nyph'~'[oZX -֡y'kmjnt3.@ -UͅWpYDJuG .G[BiJCpYN!cT0e,O2POY iC ^\4mg!ٖnr1\8>]\I[mqabeQxU~ KQek%A޸i;%ƻ nmkw'DjE֢ -:*õtLpA gzByiLq(?|,QX +Xͦ23&Ei|#`Xks V`cpӢ{_ܒ{E?A$ o.GGt"~{v3ly]qvݨ`#;]9}6endstream -endobj -648 0 obj<>/XObject<<>>>>>>endobj -649 0 obj<>stream -xVێ6}WL>8@ͷf8n>fV&C]҅N -AmXE̙3g );QDm/c?d<}T40p<4'lJThc_|m3%$\$ϬP-9YEvĭiSOvnwҚ7wF{2e@sP:7H*KYə,SفQ8n-9xNKNK,?3\l 56"|"iKe,]-fq_3<:x#++xO\rdhnTjA(~2rP(VUņ=B WVhiA;,A -LsZjE\P~_4tP;3K2 -DEAZRjӀ&h(iҢ%$hhʤg8݆:(xT1Ͷc# 㪳y«d* U[;xm%pI^w~Ϲ{(v[/ -QdM^õu\/TSbZXˡBuН* ӛ\sZ&M!x}@G;K <{@QsfWمS$VxNnȣjjxµ۝t)h,uNߐS<[^Q݇zZ2AM+uMI݈#X|dZ5f=V?ftc[7jo'ߞk=C7ȅȣy"+%1k۳HαyjNߩf;8ק[Y<\>YB>#fI;L ۸p4  z}EoP.;קFΥgn2Jpդmvendstream -endobj -650 0 obj<>/XObject<<>>>>>>endobj -651 0 obj<>stream -xUˎ0-؜f7C\lO,StHliu|A? -0ۀ5YxhRI??:i9Z.NHN:J.KlT4'N9V ^у40p;6rhY#“ -k!Q>@GuߙEclopE6ה/eK(gl>o]makx=PYw* r[5w[1K5㼽,/"]endstream -endobj -652 0 obj<>/XObject<<>>>>>>endobj -653 0 obj<>stream -xVMo6W ҤUR%T؉bxCSD+JN_RNFp޼y/# 8>Ոy @x"ƵVAn60$|{bt1H$bXdEzx{܃ oZW4V, $"}Re+U;_|8Ky!F:tBVhJ~`9ހ,[)we@jwx8clp`~!Fv -{s'/r5XOh) ksT`;R#,1VPvXR1~@AUU>6LvJ V6' ز_c# ,";|/ڇ"CPT#IG]OsXlmEXVպm^A3A|a{6Mݩ6z#F׽p4H!R*Kw(7[UaT UFZb!^CUnl|S`{mj`X\j,t)g^_ -Cv~(f4ܧsgƐ4Tt RÝ%S!&W,_&r>NH3}'+C3-⁕6uOuHb2D[}oTY=(a{%sB )ܜvA,sZI"zd'$q]X1uӗ8.SyaBg>>E=pV?GT-T1fdY @tD@lT[(.n193+WmoPL&@>Udj,M:ubq;_mh |Vc>k$,N#Q$+e)}/J| 4Φpl6F_z01㘡"fK ~5Bazq$Q>GQ-Gendstream -endobj -654 0 obj<>/XObject<<>>>>>>endobj -655 0 obj<>stream -xVN@+viiDRU{fwob BΛy3f{x4Ч(﹎K:c?lN'x /a< ~00&.eu٨6C}o0>gk+IdeaqcsŔRRW^#3cl -7gt}y""َ],sELRTB+5ߡ(K9 Nd&m$j4JR" SOj6igM8lOXKcn.~e|d1vbsf.$WPrlɥbeVuTGs Iԃ1$]T3C^jki)*Pt5JU}̸D<7,T-QUeFFv.V֤hD(49ppxyWQjNhGdd&vL&ƭZo(& eBc4f62\6FfhPmNw;8|TUdũΫ]H"dif,*_: {{oendstream -endobj -656 0 obj<>/XObject<<>>>>>>endobj -657 0 obj<>stream -xVr6}W/rbK))}حx&Q\3-Id{ vT硺(rgpR#GnzaR4MfS\ՒrpD/=OgWǽ7Mh88glJqF}AH拉LVda,Ȯ$UT_r)G@V\29%Qd^YQQoR'9oBs0Dσq0 -f]_׵4Ro"jVE<Xtwd?eclLXA壕%. È*-MZa ScOqSXL4쾖ƶ==T\e}Bo‡9_19.TCbߓ+GcޙLZnt"-_99d/T fz01܂Pt:^n/O>-3g+ ]xQ-a̯gEK[kP&WaysGoYzGL (c]GS --nO/[J˫$Y0Ear<'LrFKVC)>$J*5e%+e+]tq<ŢsHC9ŜHm;g'gmw%P X1.sʕ6`QgpP g$;c?w2gȧzyHWֳ,6W) kۭER'16 "丬QbZ -=#8Rr#qrܷ}M0F;)BܮVEo[ұI,q -[Jl~GBQܾč*&^32%B4=RJiFxi9D-t$O[5KlXƦ~qS阣e1L?ww @ M9 '88Q3UnZa~Wl3Lc"[L`pľ6򭋸{_pSendstream -endobj -658 0 obj<>/XObject<<>>>>>>endobj -659 0 obj<>stream -xUo0_qIBHߠ-[%d d;;҂4rw/ zz ^4@ݐ~{)Rp]: ?D0ׅ(3nQ8RD3!-4G13Xb%d&jZ8DOR}ЏBL(4,* -RhOÁf}n02!$\K:.Ϋ$Sa6C` bkojz ֕Y2A YMp 7 9Af nFUHU %)bj=fq c | 6<7S!"FҦs U1SP nc0֒N4IaFjJB0&EoK,P%8o~qAv -K~$,^Z[GVi_\[~{+ Kc%:\eko0*HegbF6]eZ[~wecar?8o^zm[: -'nE!*ɷH7rAƥZ&{Ҫfq(P]yU8tmm dҩܬf86ng&2F_*V#I4$b)+ȳJaw}=a~u\{>_eI߬W7CW3=e~0J]s54endstream -endobj -660 0 obj<>/XObject<<>>>>>>endobj -661 0 obj<>stream -xT[o0~WixqЗvcjwOHIH ^48u@(\}A/ȇA2oxăv;"!qgJ¤2, ^H.C@=2Pv7>wR,T4;$ P7go-aL6VE,r2 -E֣V[~zHKhAgIJFe|e93S0FG@.7SK#Expx%RgJ D:r~ u{(r- Ao]~%0y:6%M0/dy%]d@b޶%\RB?pUUݑ_sPy|*1&35Q-XAm 4NN9El=ZzPڕnGM1}E0QkER%j5K_[NmjՖד'?tШd -W*8^\%P"by޼^CHl0Or!1ս_]J_uPƂ?!]N:YP(9 -ɏsUm,|կ$dUo|[QRa#W\/pńu:sv/OгP 4|)%o+pdtJ.d0 -IbŽMy׍>endstream -endobj -662 0 obj<>/XObject<<>>>>>>endobj -663 0 obj<>stream -xTMo0 W=k1mkŻ4IA=8R*C_?ڲsmHy Ir;bRNæyL@Tt$~tV^.1(7Us(`GB)I'1 ٯ(ΰR?*8!E,6V;Tր!^t8t^{X&WWcgJ~;aTEJkcſ6@=*fn碮vߞvLҎٕQ ޝaø|8{,$+ -r|kÛ -;/ p+5aӱ -3뢜}7ޝendstream -endobj -664 0 obj<>/XObject<<>>>>>>endobj -665 0 obj<>stream -xՕn@sTk@9i-9v$aKX`?$&մReYB93=8´g[lסgNaY8L &i?]8{.=`6+zp!ze=s`2fd>?N03CSYȪtYYĨ ȱeJDPA*ThKI]{!7׸܅hv~MfJTS $Uek(qxxATƣ7"UɰJlA$Ӏ -GeZaA^cZ)^W?p nAiVA)~' rc ͮCԖVa⮻ڡLKL Lr]zF)5 X`paۇX wJ[ᶟĪ&*XG={A>U[ʄ -n[hG(UHQ`Y[&dA -CT ƠG)}t߿? |Of?ʎN\WQ<} ë!ccG`i8Em;h#޳:х N endstream -endobj -666 0 obj<>/XObject<<>>>>>>endobj -667 0 obj<>stream -x_oH)e&hlc`%c_7gƝ {g1)hToΜ{Lo{@@̆ ~.H<"E?>8{/^8 - c'/'?N/TExD4<iF^cX'MJHnU}l031diZ+-T;]%`GrS݂<)eU-&#PlҺv~ٌ1_gs\2BU  wۺ)|D"c,Ǚ{>IY(d)r'#՚L VdH.Ś:w۠Ϡkϱ׭l3C"(ZPH) -TԶG=R=373U -o0`^Tmwc@6^!(m3VPxN"^ -*B@"V0s !Obɒ [A AjM| #ɋyM%\2h-*7b(MLI0;x$#p5^9k]|2ϝ ,jA+jyQ"37?&o etPSgiuaYСURoib YQ@yG;L}*K)M &4{А95B}ϚU]/ޣ,ͽtԍ y|ڔPv0 qCyr[n?,(nSG3^h' N&rEs%7zp1w]p0fߺw:ǵƵ#[v<8|^F}KseeAAHWl#a1`wX -7 9_02Vhui{-鸠ʜ8CAD)4q޿flendstream -endobj -668 0 obj<>/XObject<<>>>>>>endobj -669 0 obj<>stream -xVQoH~Wt%'pmӷTHrWSY^.ofiSDxof/B`,A, RH9U (܃${dCflD$A>/XObject<<>>>>>>endobj -671 0 obj<>stream -xVMsF++, , 9VN(u5@Ah¿OHC -tOׯ_CDF R^F&p>'V:JtD2)T =j47Yaq YL#rZ2UUV`\aNJVoNƒx@wdy/_͉Ny)`$ A`U9)aʀ,`t d9?.$8-*6}TC>/XObject<<>>>>>>endobj -673 0 obj<>stream -xUMo@Wѩ–/c*竍:j{,VxYMZw[D=Ujd ̛o>r`@̆ X~8{C,x¡w2wh c ' Q mCgapk^VG7^-7Q6^?Ǘk؟x#d JiUkn"IfT(Ye^_yf-3k.+]\F |4;7gד\o1OyER *a@DP) xf0#MH0#roBdqn(Fl~\y gu>/XObject<<>>>>>>endobj -675 0 obj<>stream -xUQo0~Wc+Ai+ -|` JhMTz<=?~G=T݀:|œ]_`{m7G:ܚPX' Tyf㉼ϒ'YίGW\ 93Nr{|ir2?qvඩ?=; -ԕm"o<[)'^s,E3q b8cendstream -endobj -676 0 obj<>/XObject<<>>>>>>endobj -677 0 obj<>stream -xUo0⾵ -3c_VݦHm%S;M.8WSlm@hTiK*_޽{w~9@ρC8rm0బ;;Go?Dx/1Hq89MmX\\M }p:ߢϤ`Ò9lAXYme0V-xS; ggY e`{ 8Lnng -)N }5e3+sg -Tr*/Zuv*7!CLm -j)5?lz<Ŏ_{8^qmj! q(Xb&5@"\w)uqfE[(3t%*f+#WҎq/Λ ׭wdžW^v{$#m۝?#RGq.J4;l^f?N\ 'm?ӻk3 >"V@"ɏ^ف[ >}Wendstream -endobj -678 0 obj<>/XObject<<>>>>>>endobj -679 0 obj<>stream -xUMs0+H:ŵc\:.3 iɥt2Xr%9 ]Bca` +=vKo"!Eu\!#z:pĻA8t];|u]눓"σ$qIB?^Q$h<0a@ $Y̦SH& >3\G05RYr %~ ,ﰉ)Öρ] l'躀> -@&][U\\(ԥ-Pү`u80Mϒ@iLۄ'<׊c Sål 2/!)\&R%*kCֱqr}][I^>/XObject<<>>>>>>endobj -681 0 obj<>stream -xVQ8~ϯ>@XH*MU۴MhVqn],S7f#l80#{>qk2/.L ar `bۆ3 y [^yq%vr;}pnX˚y:haOUe6\դA')M{> ^mۭ{=g9TG\ sQ_Wh2,NvNqhdJ)/)m#(oV?^>|)3Qcj rZ|zplg@f )$ d;eoʺnRXJcӭWuS tI2Fk@5qNrôIwH@`^Z>VL3*K8#XȂM(j Iq oMlloA-.Eוk&Il1\RfP#*jʴU$#x]3F BP@ػظ5CL-,J4i254JwO wT@ߔtIԯ"a_gRċ4Ji1Rh%ce[.i|3h]q3`M#2&~g@p3Gݓ0gҡ"5N.W)>^"bUC{UhM#F [ifAD=v4T&slW}= $0{af0Y!@RFYҽoR`j0tf rɘ}>/XObject<<>>>>>>endobj -683 0 obj<>stream -xVMSH+1,lcljSEJ-*8a4F -F̌#墐x< iϐ#:FƧS~ƟQ:x]pL -G&x EwNQH7F;-uvjֽYq,I6P8@4违6ߎoFЂ)T6ҟaٻ, '߃eE/{3?ϝ\(X}Hek&S\ -JT0/pOn, a2nE_-y trjp4N~H{B\Y2hfBeΩt4DRgDkmbEu$u2e(wcbOU-xX9̨:Aw6(ImȬ&-eehrʬmXWۡ8q(ղn;M.MSB9tU@9fJ|Lr^-{h ]Z _.:; nrj"V[\ w;*LZ/l,ɢu/uyx osEc]ĥDYfHKe/-d"#Hd1 P:iO)>ӝ,W}Xor-IP8Op8SjhZbj[+Vۇ-Q ܤJ/{h#ZbIK~|,>r{F=!:wpHuQb5tL9)tUiX+,;.!3]/Ua~k۟pEin<i>?endstream -endobj -684 0 obj<>/XObject<<>>>>>>endobj -685 0 obj<>stream -xUQo0~ϯD= hUZ5L}A8 +ة;CI"Iwww~0 &=j8sQن8"|cЉ, l_G}V*%3hf ͚CՖ+dM!i\ȚB -O6-52/2Cdžq\"׋R=.z7gL T,!hxywЋ^B -<Ӫhv/i9,nQ:kɌBΏ\uz> 5DY?nlX¡EgyGg840;33."@~U2|p˴)3Scjz(YCԁFkaތ@NN}4 -ЇmBa0b7{|!Fnd(i#ܵX4IXWJ Xl$C^˾ۏӳO @&LYwƵpm9]v`֦f!rR 0nHgy2VěVcc\M>05[c02|ڒ.("R*(E2MRfZ?^]Cz9^eN7?ۋ|KW;fd0&5+]{m8No Bendstream -endobj -686 0 obj<>/XObject<<>>>>>>endobj -687 0 obj<>stream -xU]o@}WG8 l0!+MLc;~g*M1={ 4;*Vun[&nNaUtK橀f~/#`%Mۂ` AU!d "#֙:$"RlXpn)R~nXPl%,+8KS!cVf=< _2OEB Yr_ҷ;b q+L6I+sԝֈ} GT4M]2y* M82Io-I(-i6/&ŭ| $ r*cʍ˻w&sA4Ey˸(hppzUH8z;;-4߰,MgEyeه] /eNy^782묪,Zӯ*oV"ENYo:Pwb5Ν)d%y|gq>PQh.FN; ϮޑfOêZ<|Ւr$}ZrP[MЧjv9ecS>/XObject<<>>>>>>endobj -689 0 obj<>stream -x;o w;)pnd]uHiGKC$ =+|vz f+# LD(Ppv ,n" J'H` zGH z&ik eôYNf_A hخ+sw* %>y&q-RjkU8KǪގ mp^J(m\[tBKZwJvK-IRZYy5u^8szQ:\!@.]Y9| -WM'dqZbQd##W2Hͧi6[c97Q[p"C"΄U2v|={?+͋endstream -endobj -690 0 obj<>/XObject<<>>>>>>endobj -691 0 obj<>stream -xuAK0,&.9 -6ౌ5kge+x&>o;%`g 5Y!bf]@J)Y MC>/XObject<<>>>>>>endobj -693 0 obj<>stream -xWMo8W z[4v{jat(b+ -I1r']mP7o޼&4߄S:l٘^N)N< p<8zwJ1-KĚ/NhYD略8O]XzݮŅVk1Y3X#<4Uf4ۦlη-+E]o;|Fj=7Ys E4t¥Ww$XeJ i%A8'\:WȇJ: BT*{o0G֌jȖ=V,>*D:C -MLo"15 /:04HAVw1W&8QR\~,BΌRu僆 ԡdjGֈ!ю~Q r=γ@Uj>."U@p!|AsNwӏ" M#-~BsЯ&Қ&)ǘ?,3P}y]7sH OwpzMNoa0-ݰ$`nZ RVZI<{0xJcic7̍9SϿDnj|ŐO:%u L`.G]ahղ`zuj[bF -['iNa׍|>/L)-1evVqKN7gOZ{ST)dL=@=+n_< Ú]fCby%Jmpd)R5[{kXmFLVZ+#QׄedUP+u$FBnա~3}B -)H{xu؆i)yjWNC`KUkiLQgKc)ヺbC _0"ǬMrʩ -qU)0™$^EgܶwCҍ~Y+ʷGI ܅0/$j F -۽DrlKPg,/xvEl`NY -\Ttl&&q-tZ>x鼱yorĂ`uF*UbZC8E,D0w5X%c/lm, ŧ/JM -#\ᴊd`.n`7NKE s +U%҉)V;-|Rb/N,ĎQ!d7=?g0g{:.V81WB [U͎Y((⺄1pVH - e3u<;Շ߱bw'w^ZNK}1-fb~ǃhy@endstream -endobj -694 0 obj<>/XObject<<>>>>>>endobj -695 0 obj<>stream -xWnF}W ٰdIq$')ZZ%&ؐ -ݕd9$Ϝ9s׭ӡ~^()[{gmzC nKJVݦaҠ -=UwC6TM5cNͬ3sK;{[]`eF -.s.W|KU>Oan("!Sc]2u6]]{u*(S(hhe%B 귧iybx -e"L\Ur'Y -bx@C@LH :zVDv>쎕`L{AL2\&VBU`:c0_k]/]t"$'&]G'O/NNiTT6$]XCOdϬ*1!_7eTu筩Tf8ɓLi ǁWQ?h 0k>'Iw]־Z3}@dun}:VK P_><"F`c0CvX-Hm" [IJp \LmQ܃nXD?A3kIY qux%?q_Ηۀ\w>|s -1[~JT-<\xz+B]PKͥ5vfQ0+auR^K ?e@vќ]#7. bA3 ,ihQ؜T؉bzBt ij8Hyΰ>bNqi)#XLDyD~zbw6>/XObject<<>>>>>>endobj -697 0 obj<>stream -xWoGb 5b" -*U-rKv _7{)r~)|3o޼y3|=iS EI+iQ{/=_+i?x/ݦtX~Ҝբ4k }O)JNnT&% v2*(鳙9RK?ZJRmBc|j3iQ}tc+GfV -U ܚC8iJ.eHi%Y9WIG36HM_Sg<+v>6*咛%m˄KQ,;ENx *dt5M17v%Jeft9?WZ -P^G~M*ru4J;X42M&-75$C&y'eiլ*K(]b& -fP0{hR!e})r%*IKTnR{x nCM! (+1SƖK0О" es@F N{]0^hL$"* -,Yhc>=jrţT1ޜβ7+5Bʺ2Cy M_paKYiۣpFۏ2h堖 &rkY!>#MJ|pEgՃb=fNQBl(J L8tO x "A]̭x/` 3bIi>Y*l=q粁:= L饵)|sb_ZTnUϝz=-F?ӷ>{NxhJD6ѺT>]1h0kVFh -\.;PkIš=#D< ,LȣϵX~hre -ɜ6f$vr3J'Ffmz3UVVaK5p@3̻E'M,ۘ.!m8} &g|xzo/quO -_A|4[pXDOrT}ߪլk -wp{u{ :=bendstream -endobj -698 0 obj<>/XObject<<>>>>>>endobj -699 0 obj<>stream -xX]O9}WmT$I ,DZUU8{j{_ڞ$J2q telă?dt]6M;7] fyQRX$ݚqŸ1|no?onד/bzq=P""ϡ҂2QӑA1!.)f ?iK8?!A{劉Ir),jXCJF|hDj0*//-4QA)+R% ێzq'Vڐ m/5G1n+Y6IJfϻvݘQ`9bq#QZ-jJg+; RXU* -G4[ib%Y{O@ _و -(@0a1WBKb>/XObject<<>>>>>>endobj -701 0 obj<>stream -x5K0DjHa0;6E:jHӛ=dyqsQ"[lAͨ9G^y`Pڵj@tu6t\ m4xS`uʢoUĜ}r0 -"ҕYY6vͶc@D(X.HlS?%ꢺ8MHRYĐ9uZ1pPތHFL 'PWwGendstream -endobj -702 0 obj<>/XObject<<>>>>>>endobj -703 0 obj<>stream -xV[o"7~W6;B!YTHm&lT1vƞH~Ǟ )U\Č}.~t6t~?L48ṏ+iѹuN.ߥKse]?D饥^/;Q>Ơ03gK+r6`zn|0wVJ \8IqNy$J1W/ U~iMU:2I@8Hx/f7OӻѤMwlxQQ:h&?M~<'o=I",MskqL@^pKiH;8l/WmNȩ%g>!CAkZQ~lL~_W/INu\/!_9BiQ!n9lpBg$SKIQ>lz=Jho = QIk)lwэ,%bۄ> ,%ǂ ~*MMV ٰGіT.,N(jcvn89ܚ-v]m}^,q7}} %.S,ݖ=8%L0oʫ5,3^>P O7ZXSz 3r;Z|0<$vxLh=SdRc#E`])SPi~_Rb~a~ ta/* cobxG9Eyz%t0{UsD)rCz}v -[ԛV{O* -T(]yu.ؔs)hx+-nK.2[0dendstream -endobj -704 0 obj<>/XObject<<>>>>>>endobj -705 0 obj<>stream -xWO"I~Aۜ`Bz{`Ar1A`W_}Uh݌i“4/h8M޻ۨ:x@ sJ5nNߣM2q~y5HwFq8 X v]h ޓaxxkjg%Wv:lVKҞtRx&ofsrk\ErL{HC:]T++F3Z*})6ʓb/:nd<,TUK((Z(pmX@aľ",Ŀe'NƗ{mЎ5E+p >& 킽^9'PF jZil, bclz@o(We)I3@bdz9.yLx9wH;UBp\4 Ĉ](V3S}.V\: {uqlw-YH5ڄqE(Gg6E:!qcDwwOpqBgM9M7al9*FX #bxj< ^I= CI%< hj -o3a4!jʠ G0AC;Hx 0j|80}͹^ZWGvЊt6q!Lg -*S֥]`USy: --p, Z $VCZl+%0)C-@A AwL-U蕹x(@p& jwm[ʈi&u=V2K~0"ju;n>QbA%I[#C`3U-U(2TA9~ -cd -|ɪu}hnpG5,#0ЈUhJNѱ HkgG#IqXrSrv'tNPso Υ '-Y8ږ:ߋOc(Qh(zIنKtO&s@}mmq"V?m%/Iu4{TQ>6sx9@-rpMKy7 lXQF#88xK2"GF - cWie&)N?5Xը}m\кdeٗd,.>X=Aar"Hf>vYV!8m+r-]=-]mwtܦ&P[A}(q֮UQ Oi!{%.߀)mt΢ \<|X?}Jqus5,XnFm2?_9vendstream -endobj -706 0 obj<>/XObject<<>>>>>>endobj -707 0 obj<>stream -xVn8|W웒VlǰMs>D٬)RGRq7KNš-چrwvfv=4dh6^ 8Iu<ή78u0nJ1-k<>Ӳ"<<Ѳ/24j?V/vOe5 ;U=@:P:~[ѵ`\WWʗ F2`,UkSdP欅@4fsN MX+95ֺMN7I>b:)=Wzd#K+ڷSvmZBJ+YKHS W9 ,,BV}=Ge!-|f2 59D+ -W@I=a^d9Is`*c ̱ d -U%p/m%VR[V+aYhkU~$(Un<5[Pl#]BXn38z+NWGڷΚ pMm^)%EЂ`9cP)w|PHNߐ̞ Tx#nM6 O[>WVa5ēpH>,c$? -զHEXİG9ڜ`ɾ]M?;^k]rd[K?YnjFT> -RdQ{Ls ʚ ɥ%=.:B"^(< 3vWBwmS»G,+R%ˇWd3[;P Lfs@/9i~zz߿\/HxS` -輸g$d뇳] uTJ:h*ivX6Rz\_)mm Kᚫ@ -Z3\kNE4Ob'pkZZFi𷶅"j#X&KƞK`VS*꘳e\\E53ok+t>+옸:p˓N-endstream -endobj -708 0 obj<>/XObject<<>>>>>>endobj -709 0 obj<>stream -x}W]o8|ϯ7'+vron;hp=@_ D٬%RGRv|fIjдIj;;;;fDC|L0l2|0`2gӷ>=>z4ҲD~(CZ淣q6}]гҖ"w84(8t*Gˊz]V^XeZG[J}k뇏7ҿwғ5WZ:2oXWKv]`4_hgDnQZőV^Jy -d£sr}2TRw2p*N tP\YɂSd!R"i^Z;kS@46NpoK{ֶ mYoD%Xs7(؂!:z!\mP=aX>b󈤪4JIhÞ$%ҭ@,[/H@E ķBxqa12bGz@竻0݂1eq\wysY =ڧ]$N]!bzݎˈc`p2Je! pb7xO罕"sg]EA{#Cs*|ERZ;61ʐc2j$k#}Z`*I+v w1 -e0T}(I;z,PGb>[uQd( -18b<rc\VN`Q3^gX%zQIHOt+`-0?&JN?C1έiMX1aUcJ19dH-%@  b\Qh<8'sRafB4hP<u1W]_ue"knbd=-<=6$YB}|Y$KLD³%qB?\S4:礂89,4?`[X=uYnC` 4T@CjȨ"x+Uh2[v IUK>T:m%h/`A[(OUu§d*ǰ' -&S]| 7vP@8 /@/@Ы/]R7?dGdÂb9|4``>iyͿðendstream -endobj -710 0 obj<>/XObject<<>>>>>>endobj -711 0 obj<>stream -xVNF}+RB$&JB-1}m1l:ہb -!ʻ;s93u4>~4阢i4CM'Xkrcr*_G'# (LjH.ãߏendstream -endobj -712 0 obj<>/XObject<<>>>>>>endobj -713 0 obj<>stream -xW]o7|X% ˖c[S| 8i )1#/$ϊ}gtv Drggggy?ft%.^5,N_)-Vr9EIX~'JQ{~T-fAUKzo Fw9l6O:#M郍ޕ]]zNY^z6^ү&V+M~еkm#U[M` kZͲVӭjjB& d݆1` <{UREM]@Yl cITE[Pz$HBCd8Aivv VPxԁ*o?y6U; { JqN~*NE\0vѣ"k$ f7uu e*pڪ (|u.:G~ӭ|!/g+]?\)6J%$Y2vkLcj9/7=\*3u]*X7KQBKVMYJt" F]=uϕQ0ߚ9JL0#Z@)lfJlUYo,JeyWNx@G4q[׏X(_4jmͺ!9.lkSbBt>-ӤEerKMkp8n. -GF&4(.$ds9ħ/w| @,gePupԊG{8hL Sa^O4CIdѶE&?/~Ec]׆-?w/ic t)u:AJo4a7[J / {)2>D<ˊe[zAB -W58S!`ͻ17 ^lZ@/9|p}km|j[mK6YNkF[c^0ֽjŃ'D}BsuZ&gҬVp~%eMjԳWpy`{&н.; -#ıZgSF0_|1XЎ0q (O,_byaE?༬Y6< p(<|KᙖFԴƄ%r C:_M>< []/ߗZ{~5 5fƐt&"̛gM-zh'ym<SO2mj4Z\'L{>xz!:g?5Ƙyw$wwם\ -.ۣ,e ?o1GqT`Y{h]A->ϧ+l~/<oendstream -endobj -714 0 obj<>/XObject<<>>>>>>endobj -715 0 obj<>stream -xWnF}W |,4uaIZi\yX+ik..EI 'a@^̙3z0~4> |g$i6Ǒ,:YB80, OhA^ϖlv_k U*yyJa8;G#\M" ͵ r -aU!$}^$F;디y%|(ᥰKJ b@= =f 9 *-"}Õ9U}|u HpP],j׹)y鮣pPYZU6%ov[=&*wwd%cw܎uU sԐ LSz`,[2:|et-Vyy,@/N_K!'XD~ÔNUݰ~DCs4.R[qw\\zint?c# 3 U4ly4kS ^_姰2D'g G;![kSo9Q+(.TajNpJ)sYhxdM?Un̖5naD -_!%%iSEDEW >.? j|4j;bȏM ۏH٫uٺHv4JoBoPHdQt-j1_(б:`xx9-wG휽VrRt rjs΁']dk|'ڦh0zG^jTSP4 IR7Fa w -- B_]Qpe) UVn8eLEa8%n`tw@h&NCvɍT ?/o`3u:T|12R -YTX׋"_ȞS|}qQ[>øda[i;Eӣ6Щ{>nm}n sHajӺ&TV-r5WŜvDWc<꜐Zʿfvy3 Vo 5"vҰݚe-~9[Q//|t+e,tvCU\ F1'ʧBMv2L@kn@٬ ۵1 l:1z&19qp_ -{?2v#72'0ђFH{""lTR~U&RrsЛtiڻD`,cz]s.YȎKnw 2 IǕ -xS$,0obd󄨝OҿlW?ӛO|*mó vݸy^p|&f<}3}fJoJ5ڍ#|mv4$d{ĞO< uvendstream -endobj -716 0 obj<>/XObject<<>>>>>>endobj -717 0 obj<>stream -xm[oF+[i@)Y!e-`7IVQPdu,uqS p3g932Gğ9nbd$ -#,_a* 6br\]b>Ǧ?W 69zaom'MS&ՠ- Oʹ69 -9jtrpuO2m3Ρ} :yXKp<>?~K߭|>}3/E5i}YK{Jzy&4Õ|W`cTZ۾2; ')QdQ+UۛH7jŬjO?l~.$vxڊ pV-mQ=Ÿо;eD_AV*|uTezj6 I5drʷW!8XAp$8f!? X5Fݹ)M@.P^<+5WmɠN8B1c>QPyueN=]YģgW ~_vڦJe;dml!MlϐUj.#ʂO^hɧ -jazLQ:FNt{AĶP?9̋ ٟ{j±XN>X}Tr-\2d>/XObject<<>>>>>>endobj -719 0 obj<>stream -xuV]o6|ϯX\ bٲ=%mH{hG%Q6IԉT|FYb#QP߯B'&3Q00 i1~+I{1O܋x~|LWç{h"leBHkwg=H_Dn^򇌑$4%Gf&l#t 4Ҝ;^Χ|+= ꯫@r7endstream -endobj -720 0 obj<>/XObject<<>>>>>>endobj -721 0 obj<>stream -xVOF_1~H$_.܅ -WlZZۛdg7絁޷?lz-س3of޼o{#wDc:9l7 4>95'¾OxFuv>8')΂8< RTB.i Cc:q%yp-;iNj"yFgB,kEX<;󅐰k$<ؾy0 `6T݀S[Sj:plZ%dQ|~n ,b1镪@> --ugɗBW.C?\.%I%ूe\IdNDAC߾3.fMӤvߋ;dAE}'uyly:we4(x\gwW]t}W0Dcbw3K1LLNF!EE+FN -8F(PHeGHAN,+H{\rPۙzdP&70F SSi%a+L4W)zRCD/Z*K i -6{Eu<atkⲺ`1>q0{K?X/tY C ,02ayԉoM:yJUUn\&7Y=yL10;*Ck>/XObject<<>>>>>>endobj -723 0 obj<>stream -xVa6ίxʞ =tERO~Y 9!:vj;KNn[E3o޼SJ˜f `MnqhZ: -lͯ|~|B=mKwp] Kӻ~O=X}4e0ͳC1}aZi:ll+4T -ǭ,٣ -/3`xi,dC ĉY^I/xXNG戕(C)+U3=>J3.S>$"AM[G}UЉY:ޚ:6i -4QtN*EL9/śҖcϓХ6*o5h^Wִ p,P|pnpyF? --,S˓ORfG%41%J DiW(~2 +bJB{┆j*ֽ[酵 ߽m w3ht $>{0NQC__԰:S><&F}ࣄR.;1rR\eZ@Ap=C?g޺`{kwJBn|OT(H%:i-DG җ$O=g֕I.0ho,ԸYpg/IHRX"noN;!agA:nM]cap4AI3{jf1ܷ}`MV8Mo~Dw}P|F_zyrO K7G<|/wM6yV2ְBЅ[Ấ%]4:־LSeES٭Hu!RL~vtMkuz(ND&A#mվ;|#DB`ی#;dzuuU7Z+nst:3>/XObject<<>>>>>>endobj -725 0 obj<>stream -xTK0+UBBKjU^ 6]~d!i|=y2HAf$vb_3ǯEh} OeWf)=Վv(-8Oȍ}MAr_ayF%<΅dRd7~8<~kFs8 !aAYde7-_ ROYRs@uSm -Ii"YF)1a{a{JF KdžB,tFzԘwCWwhEVKd>>8(Ѫ(b^4٣sA% -̽7:Y?FP9wWpfNb~K{p@V`dM;L(7[+kE3&8@\kՀW<\P\s3-Բ1nNl0ԫ9ıG*3R j><ZEn(5/чuEy F֭8zI"\؞Βqm|lLc͚υ+),HOu- Yendstream -endobj -726 0 obj<>endobj -727 0 obj<>endobj -728 0 obj<>endobj -729 0 obj<>endobj -730 0 obj<>endobj -731 0 obj<>endobj -732 0 obj<>endobj -733 0 obj<>endobj -734 0 obj<>endobj -735 0 obj<>endobj -736 0 obj<>endobj -737 0 obj<>endobj -738 0 obj<>endobj -739 0 obj<>endobj -740 0 obj<>endobj -741 0 obj<>endobj -742 0 obj<>endobj -743 0 obj<>endobj -744 0 obj<>endobj -745 0 obj<>endobj -746 0 obj<>endobj -747 0 obj<>endobj -748 0 obj<>endobj -749 0 obj<>endobj -750 0 obj<>endobj -751 0 obj<>endobj -752 0 obj<>endobj -753 0 obj<>endobj -754 0 obj<>endobj -755 0 obj<>endobj -756 0 obj<>endobj -757 0 obj<>endobj -758 0 obj<>endobj -759 0 obj<>endobj -760 0 obj<>endobj -761 0 obj<>endobj -762 0 obj<>endobj -763 0 obj<>endobj -764 0 obj<>endobj -765 0 obj<>endobj -766 0 obj<>endobj -767 0 obj<>endobj -768 0 obj<>endobj -769 0 obj<>endobj -770 0 obj<>endobj -771 0 obj<>endobj -772 0 obj<>endobj -773 0 obj<>endobj -774 0 obj<>endobj -775 0 obj<>endobj -776 0 obj<>endobj -777 0 obj<>endobj -778 0 obj<>endobj -779 0 obj<>endobj -780 0 obj<>endobj -781 0 obj<>endobj -782 0 obj<>endobj -783 0 obj<>endobj -784 0 obj<>endobj -785 0 obj<>endobj -786 0 obj<>endobj -787 0 obj<>endobj -788 0 obj<>endobj -789 0 obj<>endobj -790 0 obj<>endobj -791 0 obj<>endobj -792 0 obj<>endobj -793 0 obj<>endobj -794 0 obj<>endobj -795 0 obj<>endobj -796 0 obj<>endobj -797 0 obj<>endobj -798 0 obj<>endobj -799 0 obj<>endobj -800 0 obj<>endobj -801 0 obj<>endobj -802 0 obj<>endobj -803 0 obj<>endobj -804 0 obj<>endobj -805 0 obj<>endobj -806 0 obj<>endobj -807 0 obj<>endobj -808 0 obj<>endobj -809 0 obj<>endobj -810 0 obj<>endobj -811 0 obj<>endobj -812 0 obj<>endobj -813 0 obj<>endobj -814 0 obj<>endobj -815 0 obj<>endobj -816 0 obj<>endobj -817 0 obj<>endobj -818 0 obj<>endobj -819 0 obj<>endobj -820 0 obj<>endobj -821 0 obj<>endobj -822 0 obj<>endobj -823 0 obj<>endobj -824 0 obj<>endobj -825 0 obj<>endobj -826 0 obj<>endobj -827 0 obj<>endobj -828 0 obj<>endobj -829 0 obj<>endobj -830 0 obj<>endobj -831 0 obj<>endobj -832 0 obj<>endobj -833 0 obj<>endobj -834 0 obj<>endobj -835 0 obj<>endobj -836 0 obj<>endobj -837 0 obj<>endobj -838 0 obj<>endobj -839 0 obj<>endobj -840 0 obj<>endobj -841 0 obj<>endobj -842 0 obj<>endobj -843 0 obj<>endobj -844 0 obj<>endobj -845 0 obj<>endobj -846 0 obj<>endobj -847 0 obj<>endobj -848 0 obj<>endobj -849 0 obj<>endobj -850 0 obj<>endobj -851 0 obj<>endobj -852 0 obj<>endobj -853 0 obj<>endobj -854 0 obj<>endobj -855 0 obj<>endobj -856 0 obj<The smbpasswd file)/Dest[714 0 R/XYZ 0 771 0]/Prev 855 0 R>>endobj -857 0 obj<>endobj -858 0 obj<>endobj -859 0 obj<>endobj -860 0 obj<>endobj -861 0 obj<>endobj -862 0 obj<>endobj -863 0 obj<>endobj -864 0 obj<>endobj -865 0 obj<>endobj -866 0 obj<>endobj -867 0 obj<>endobj -868 0 obj<>endobj -869 0 obj<>endobj -870 0 obj<>1<>5<>6<>10<>12<>14<>18<>20<>25<>28<>32<>34<>69<>74<>75<>79<>82<>84<>85<>]>>>>endobj +>@$g,ȍl7q5‰#nS 5^e k5p 0 kå6h,ܫ,ybmc\ڨ?7a>EQq!N|vDޘ$x ҧAB^MVbԅlBPA׷#p]RT`)G^XqBE^x%N`h.@\U8LNuНR0ݡ¨p5$lwJГv=W y\råb"؏dpϟ^)zkn#K33?YΥf0f*%~tmɴnxU2 2ZTaOj'b'“Ѿ塰l)+"QdgeP.;Md"jLE)H/&d{\_@$ŨIJ 36,Q:?`tnmTc<4`'G ZxMW}+-$=s({f+h)JAC/ 8\yor^ +B8"; 17}短DobDۜ38>6ixӐ' &s8kF⡄4Uj^ڄߚ\^E,=GG6hRqbZ3! *(IgrR\!%=HhcVS^D~#2&8;leiS`(HNJ\OEIHvͯ{Lw7`tv}UY6dyThOiyr?x6| tFT6Bf!j<$XN՗n7I/z[w)hG$):By[ϴHK#G;SL,طS];mnxB:FGen)d|#.rGQ=}9S$+#I'ʦ$VHWH8㠍ˆTI|ʏhӢDF*pע눼 -/gB +A*/,|LrGI7$p o0Ptq썓`w60Q\Ժ۔tH Di"Lr4=&A-oǒfѰ(r4i6|Opeh; 3:/|ء& +A2hI.O{󊜽fq)J9ɮ GSL/K?*G&)Żj"Rik|]湟`#ӌKw[.0+75䋉[cC +8#&k~"ǝ[> endobj +1664 0 obj << +/D [1662 0 R /XYZ 85.039 781.388 null] +>> endobj +718 0 obj << +/D [1662 0 R /XYZ 85.039 761.463 null] +>> endobj +1665 0 obj << +/D [1662 0 R /XYZ 85.039 667.044 null] +>> endobj +722 0 obj << +/D [1662 0 R /XYZ 85.039 667.044 null] +>> endobj +1666 0 obj << +/D [1662 0 R /XYZ 85.039 642.326 null] +>> endobj +726 0 obj << +/D [1662 0 R /XYZ 85.039 596.667 null] +>> endobj +1667 0 obj << +/D [1662 0 R /XYZ 85.039 567.263 null] +>> endobj +730 0 obj << +/D [1662 0 R /XYZ 85.039 276.116 null] +>> endobj +1668 0 obj << +/D [1662 0 R /XYZ 85.039 248.593 null] +>> endobj +1661 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1671 0 obj << +/Length 2359 +/Filter /FlateDecode +>> +stream +xڵks6~&_Je" Rss7v9v]:v24 YlPHʮ],H9jg,M-c5-3yLlbM) kꘖ"d99 2b\Ie˳ٜsnx611.;[]_.gsf_~O0?<|=9[v88kh'Ɩi6q\nWtr3OC`Δvh7sqި5IX4[EFMuߙk??BP\HUۨl& l$~7$KiYIԊHTMpGk-c4hzsUCP:lVlAnEyծN$UbQEe EXߍwqlmdBòƅQ5mjS)A6z[I䱑T[`v +YÃnމQk`\5:fcr2PKdB󯄖.v-"i)adDwámas䐘\Ah< =G4VMGw{)m7"%M(Z*uB;ۣ4iӦ} LGr1[=O"c׋+>Jӳ:{suz},"YpǼ[3Ծ?$;v +͹L-h[P|fF랑9`J ֚@YH1DpkԡmBTrZ^~~٦1B9ЀךoGENFD0lQ}Ķm(H* oYo|$q)g; +3}ՔsRd˷!X!#|$xGӹ ]')nx7 Ms-#9qW7-Ư)"&c[X߭['s&O3Q:8>k[ +_%)Q4BnEz.Pe\}PP\a!5-Jro&`RVaiߠ5'/hRi[{'H%7B?F2W`:gVٸF B1G dtaU4KYRI"2ZhR<l%?rm2)`Dxw;ki nJ!IB9&=kn` (<.9a7ytt~ՐY8Xհ@48RPd R:nU`I\w;8L_пִϭ)=Q&#OSM%@cUE/ ,T5UxTa;b iۢ!uV֩# LgElI^dcYI3JIS"XRGp?An)$a)PT1XG +5i+:zµ6}G2G8+`c*dêK([@k3KDfC&tt:hKӯ1!$mYܷpVoü,Lu6|;@&6e} +^$HN.#$]%֓_- lr ^tRHh EWEؽj0}TdsS X۔$'SW %04"0hriT`A-ٔ}VnrlKA+Nr96z#}w^GcΠqUGE?S͛rj{a=O7*B}1- 50=,/Jԝ`fH$ѪEYPaJNHE)bZ$'CFжѐ[2@aٽfQV7 bA-0"͛sԫ_nZSDv9U 2:6ҍHwo.hd+iR>׽/nkLD{strUIڤiOBt/μwq~L@x/Op"fG MC_~}`W1BLIā!>gؼ+RNS<ݰy~ Ia`\ }Yr{ymP9"P&l0-ǃ'>Aߊ8pfCH/(HxP1"m$a\~>L흴kxԹm> endobj +1672 0 obj << +/D [1670 0 R /XYZ 85.039 781.388 null] +>> endobj +1673 0 obj << +/D [1670 0 R /XYZ 85.039 366.469 null] +>> endobj +1674 0 obj << +/D [1670 0 R /XYZ 85.039 331.425 null] +>> endobj +1675 0 obj << +/D [1670 0 R /XYZ 85.039 298.502 null] +>> endobj +1676 0 obj << +/D [1670 0 R /XYZ 85.039 274.583 null] +>> endobj +1677 0 obj << +/D [1670 0 R /XYZ 85.039 252.785 null] +>> endobj +1678 0 obj << +/D [1670 0 R /XYZ 85.039 66.98 null] +>> endobj +1669 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1681 0 obj << +/Length 2714 +/Filter /FlateDecode +>> +stream +xrF`"ƄX U9ȔcQČ 5_?ok,$ē*\.FS3-'2 -7Gv)FiM=z8z}#e+Yğ?Ooq O|?0n8xsˮqbf>] +\G`*P r>7m߁_Au^w^cΈn8"/h9t#6["` 7LAg*zc^ͮuT$_HΦ. B04j*V|^,\$Nws<$n$9҄q(09~+ZѲE'K: s+DC;S 26!4ϻm@{6qf켬Po#3^\ +bGjhaQXӭ\Fƈ;`sH]"a +ÈwՁQ",M]sxYxPE>U˘\>%}@x+ӄwUj#rxLݸ&qIx BED). H.E _, RLIc0B[fhu1"=Mҥ`FMQ|.\25I~@4j}Y_V?˳v,Z`-ZCk8~LUQ򠫫~0"z+ٚK`<|9B0A#r-ivHH86b_pnx]#'YL;>Z=e\uy|YG2JU +P5]Q-e9fzd*v'6*$HL?`#@I( +g++7 e;/>Z:L!tX6 )_p0#Ʊ)-cri)g%?Cx]OHxYfXfǶQ`nl=4aW0K\3xm9a6!ω.G3{Zo5ڂCBH[+|:kRGEw,k$Q5VDck|"wIE$aА l2'lJ%8܄{C;\ MgV["ٰ욎;.EX GA Kar +hL}܄ө1c^R-Krw I.^Aay*xpV"l!VǕ~b8.bj(˺).Y`Th76{^Lx9kW6[n7,ȃIQ@-=_L?l9/NJT@%bI>wVTU8<lTIV(_HYjþ(zʗxẤ,!A"$X$A=ZFuiF"TZN~M08IINuՆؠ-z0X! n<9pk $Ktv`j'yHOrA +y+Oć+)G)ƨxVv(UčuT!Ȯq׶1r? *J\wȹ`auX(K:8)Ls.?'&Vxdv]@gCLS1mLHQujQ+!eIbStYqW,.!InCFmT^צ^-m#/;?ۈvzL"[ӧݘrO8 c9-%Cb?9BvMfYnYɴxZjKnUW-,Ofae 6AwOb[_ hŋ,-5CcQcHY%$T?D9J+ >o6_ ~?ܙ'_~7k# }9qdƒYV+ԣU3Lay*ri=d"MIŮN.7s)M7b{ wsjmK oKrR҉M:^շ#:A"RcQE:ƝZGi]7V+E8 }w4I N{tMǁ^P5}/֗gw6lWC)zIMRl6)QSn~TѨq-_Yґ\5~CTÿ.Yv˃%mNOێ| Yk icݒ#"VHQ~L9. x<m&%t%9 $Zw,ŌNc+y3XvAɏQ> +۝J|X`q!MO+ ThK6N3>7Pv# =OSy74x(q<(6t<;nRPi"rHjmlǢUQ[\_' ~Y1}+^Z/HTY)K7iTL{}="ͩP1xb{-p |%uoPT? +˰xHU Fe,m!v6\V#l7BuRm\..ч(K-n$˃">7mNh>;zo<\pNE?6Up Kendstream +endobj +1680 0 obj << +/Type /Page +/Contents 1681 0 R +/Resources 1679 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1687 0 R +>> endobj +1682 0 obj << +/D [1680 0 R /XYZ 85.039 781.388 null] +>> endobj +1683 0 obj << +/D [1680 0 R /XYZ 85.039 761.463 null] +>> endobj +1684 0 obj << +/D [1680 0 R /XYZ 85.039 743.967 null] +>> endobj +734 0 obj << +/D [1680 0 R /XYZ 85.039 548.428 null] +>> endobj +1685 0 obj << +/D [1680 0 R /XYZ 85.039 519.63 null] +>> endobj +738 0 obj << +/D [1680 0 R /XYZ 85.039 489.767 null] +>> endobj +1686 0 obj << +/D [1680 0 R /XYZ 85.039 460.172 null] +>> endobj +1679 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F43 1079 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1690 0 obj << +/Length 2655 +/Filter /FlateDecode +>> +stream +xZoBN:E_|HmPrA"W{a}˗('n"]73XY3L',p`/V~sūk/Xd-r~6wg +˳bLfo/qڝ.v5[ӛ_x/|0v >D40alVN ^s'z1 pc:c<{7}Y#- e/ǤI +u>{D50ؓRt'8CrFg +ck)|M*nU($fu}%U^vخ[J{ۻo%YUQU#VQl;P $JLmngLծQWDZ'ھš،>U4Dߨ.F"4X6@E/HuQ~ʴ(B{7w\.ϺFز wlzSKR6('SKzݐ}LDxWCi i,C=CJR+zN_Ǜ`.?Z#7jN2\p4n_LgNj1NKE(ĜvC|FUƭu7HJ 8y=}b`!HD dt>}32\u )m-1sMU~j^Kz:7w`xOIۮIP -ι4)+^EL{,  dt"Se}݇rdSΘigv8}Ĉ^EL4*7y [HDܩCq[h6W*?Q'X> S%);*DrDZ%zPah7Av_X+6twԳJN$X9q kľEK svZXghb[ { b%Kr05U@PBy u |xbӶ s/ IZK{ p AʆGF:7BW1i#6 Lb)H ]Ie/c}> Y6ZnH|WXꡓ>wjDiϮ_",JQO l{uHy볣= xݓ]٘ +C)X٨D'2XFhD):@:zfLU:am/_ }P#ItPP}ḓK^"u8~Ve8\pjMQGն(2]Q_!H'ΤX|d,ο"n}I}ԇp:@LT55Vx׀T&' &k +ӷ`͟RᲯpgs˃Z>\`fn]pܤ($^ #o,<xot1^nxU8UHY&k.G\%ITw.|]Z'M.%@*täml@Ci9m"ZjhrP,6ͦɨ tx>2mBHT `^; +Uُq7Q`0RBRYHQ<4\ZmpN 2 0DgȚ""}E*"/ŊJV sb +cC-ő$!ɟ=:$MӮo霃}8!VŮowY_I)0;-u+~!fWV U-dx($t +!hN̴va\$A8@_mUICꅙ+6t撤h[u_g\ZpC.C,̃ԗ(r,-wX.l1xFEMRn}`"Zm7c6t痆J3&3k5*K9ҿaendstream +endobj +1689 0 obj << +/Type /Page +/Contents 1690 0 R +/Resources 1688 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1687 0 R +>> endobj +1691 0 obj << +/D [1689 0 R /XYZ 85.039 781.388 null] +>> endobj +1688 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F15 895 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1694 0 obj << +/Length 1547 +/Filter /FlateDecode +>> +stream +xYKs6W(DAٛة3ꡓ@QDTbYN:ψ v~-F(@y?ñ<>L/ؚ.$ti !@Ga l>fn&S{ćW ;b;ǚ> &a<=Wfy:Hsâ;&@|vxUgHj#{N3]滴is0!}0]X xɥFkhSnҥt9~̋%)3ll!>RVbxfP-aI=1F|iK7;kzEx4: MHa0͂* rILBPCt3I @Ĝ0~ŏH 3KE!&{hgn}OfnL8a3RwO 7:^)~)Ⴓf=DW2U\'; +>ĤSY)2ꤘjTQynW' +Hh-0ysXfKLpBU\эmAbT~_ŭQCLr3 ?;]P!|Nϵw+LaԸC L%LA7H VӝJN3{*`fc-;D(,M-];+> endobj +1695 0 obj << +/D [1693 0 R /XYZ 85.039 781.388 null] +>> endobj +1692 0 obj << +/Font << /F58 956 0 R /F43 1079 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1698 0 obj << +/Length 2082 +/Filter /FlateDecode +>> +stream +xڵXKoHW k1l6)$LI%J""eWv`ݪWV$@g$UNr*l`+%Q8`~fqVgO0f0?bML'O,tsﶲyS~Y!IxAC Th>>Nw7)5y7Ձg +S 6T 6%qMW0,lt?Wii% nwi~eaQ K5x>6M}O;IV|zbZ͎7^\0%G&m-8V:j tC̡㻤ptCA,cP qcjHQgJ\'VL"T}"qݝcx@wJ;a~x`B5sf sm憱mOB'5TO!̜x.-RZ:i2, >X!U9%-UϺR ycJBViܠ D|7,984aY"1H {vGm(2!\q3G {F]mEWb`- /%A!N4Zv}(#\ʣygr*#|G8|)}Ky'q"M%,zj;t%q6ɾ1& yw`'@~207(h(n7CGT]#DhJI)$P0w{+kޝmOI +UJ]aYReR1 +qȚt9JFj +|/XL )KrEGYP+xz`4p@R +fC.|L$䉈Y}^9~u%Ro'L#ѕ1:%΢H|wڀbн>؋އ[Tfxu] -,J03]qaSU +ۼ|u$m$@eI!m\P 3׃rXq+QqF 7ٵL7 8=~;͋ǔ6e~ P!KIf$SQ¯~Q2%EA; +bP bűƚs$X憂_)]]Z8nhSAY\710};Gnaŗ/,ʃ=?{=R g|X2vͅGk 0p uy ϔb:98x0}RBk :s]s͍s% L(Ԕb*E +F\+ҩYT9&d-::]K R(-`4lh+<:qO=`sQRJ<GNq $|: ={G;bqx}a4E +G/x2a ci?ؼ;5R?JGǯaJE+<:jhqd?{Jendstream +endobj +1697 0 obj << +/Type /Page +/Contents 1698 0 R +/Resources 1696 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1687 0 R +>> endobj +1699 0 obj << +/D [1697 0 R /XYZ 85.039 781.388 null] +>> endobj +742 0 obj << +/D [1697 0 R /XYZ 85.039 761.463 null] +>> endobj +1700 0 obj << +/D [1697 0 R /XYZ 85.039 671.062 null] +>> endobj +746 0 obj << +/D [1697 0 R /XYZ 85.039 671.062 null] +>> endobj +1701 0 obj << +/D [1697 0 R /XYZ 85.039 642.326 null] +>> endobj +1696 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1704 0 obj << +/Length 3531 +/Filter /FlateDecode +>> +stream +xڽZs۸De,$>^sZݍh5I}N3&,b]* /b?P4 }e"ȟ/Bбc}fpfGgI:=G\"(?I⑈_08|:SI}zg譚jzE럱xϫ^.ƛi?_e$ka<2Ծ!~|][S`qϬ5soeR/syrOk,~ \aҜXOi( r(&Gǟ[le^uLR 4##WQCdR!N(i*Q/Z&QԐ:ӑW4᥈ϒװlHQ.-s9؛e츛sJ +UCSLpivz͝EIanIGiF? !w xbP 阢,&yڠTgο5Ț9QڃУ>M*)t%r%%īizۜO xm$Fbii^?="mG|BkmL%n_DDۛף}bm;©ffW[BaZvojZw6>HޝIe̪Q7s=T+&eEZ zQ +Ϡqzfʔ%iV&yHg̈́(ޑQQ+pX!\"<|vBQ䭼ǰ|O->Ȕ@RqPhI—bÏgDGWx#Ks걲Jգfnͣ$%ߖUN,I| MX'S5ޣ2jrl:*)3P[/XQuz\!B?ԦQ5 `B*>-n70_+~eS->NfNy=S^]Q* -\;n*Sǃ] ~'/w7n*ESqĂ\J͍%y_>}PSk0B ieYW jCIf=zMۿͿ>G΢f{3?#Xbh4c +RտHcAmMq9N.%mYwY7Q8޹ӨRkh +Fq 7 ޛ +[rqJǠzmQJ\{^XB`rfK㑟Z>DZ"N|p$PX OQxS2s ~eG7 @/xS6Mɽ{I hd@zIn\Qzh.F|\Z +`T8G뎟Mq*<.7aoQćʼ$ E5@y_z +X30&WQ(8`J Ty #Iaۈ193 vHY.=e'-eRk/$XZ#'d)+P βZBH0a5O.QL="$?NI8Alxt^@Ivi;^NxRMfGݲCՑ!%SNɕ7읝=%Rs) Lٴ*vEo*dӓK,)00gT"DXĬW5Eu}[*l7+1zw"ҼV{ +s-zUGnpT@g߱ ܥKn\ FCH` +!aOk`㝬GƊue/,c Q7Q*XŊ1X Ǹ2ԃ7"fߣ$ $u d0&T[CXVڹ8K.yle9-WX=\5#wx:b #\[˔K Zqel[3 !S)J# 9Rǥˎg< a>X-FDe~TkS)PJU*BsWء4:6RX_B׆+=wzNo:x˝ۼ o6ɑgsF +?GÝEM!huz^k!M1am@𲥒I*dEbjZ%P_G%"Jd=hVĨEJK>\ـIjgS:IFI:L^j>.a5D/6.8ԒI;Q+.~pfA¸+Ȃp;ǖsP?9I[\uJ]qbő7RL [7`5mnzcltl pc,0X&mqþ-}|$ׁF`T:ף\ܻKi̺~hBdp 8ucED~4,? +G*5cZ+pycN{Y!ۈt;0əs6XjَG,G`,`\9tq:#G. [-UM=|ˠ+^pA{P>xSt6/c+ЙF R?g?ɚ&x|S~żUfTGHJ. coȒGU{S` 2ollFGs41o$w[-NNip1dBRsuKL8Pß4U!Ij(h2>2 x9{xHV~Z1@9 *E{9 R>HaSʚNE&4*ٺ78pwõl*/j y Q{ybKC΁)gY*O#$#<|XMkE4F%1{)?,_g%%xf1Wh@5_ʓCoDj [$ -TnX\ዣX~ Ɏ HQ\j?h۲Mz߷EQ0ԒxH[? endstream +endobj +1703 0 obj << +/Type /Page +/Contents 1704 0 R +/Resources 1702 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1687 0 R +>> endobj +1705 0 obj << +/D [1703 0 R /XYZ 85.039 781.388 null] +>> endobj +750 0 obj << +/D [1703 0 R /XYZ 85.039 761.463 null] +>> endobj +1706 0 obj << +/D [1703 0 R /XYZ 85.039 669.62 null] +>> endobj +754 0 obj << +/D [1703 0 R /XYZ 85.039 669.62 null] +>> endobj +1707 0 obj << +/D [1703 0 R /XYZ 85.039 642.113 null] +>> endobj +1702 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1710 0 obj << +/Length 3398 +/Filter /FlateDecode +>> +stream +xZ[s6~ЛL-M֝:tw>@"-qM +I=7DۙNf,8CY^͒w4mWl #?^B͔}zC|ͼl#U\,0t],$uV?[λw~4߷7W?__v_*W!nϿY|a~W* +H]]^ӮcjƳ&4K?s eVt+7TXp`"Ϲu목 8d8wmVeq 9nv7?5,BNsQ;9=n[h=rw_Ժ^wq9wЬ&3I)STQ<9HsO{^9yX^[%R9x Ȋ*RDοwMˍ~{\ыY +[^, wy +rK1Gݽ?sˋ<4|Jt$pa$tit}GX ITZ$xY|O[O[<5Bc;idΚ(sSzTN|?OiYg]ߢ6.;N^CnMC_XAuWnqqڎnmPa7לD:MrBϚd +)Y[$(Pf KHlK]s/-i'Bd(Fui bKFqpzҳ3BU0TNG˶s9pseD*3ڱQ%b\(3~z|o{QOpw?x;6>5i$|{B+U"4ࢺ*$g0JA_Nv,hԢA!L"'OHט$>CN,s(~*dEn/COEQG1}e]!"l޼¯g^1 ܶI92}R""F_}1/ϸVxK+NsO)ŭ`Ӑ>P*+FV'۶A@LҴ7L%BCT*ZmmGGP +8-Odr>Le؍̘y>X&ExumEq}"3!}> +_L4 ~L~%=@ +&/IOmscZT /ڌMna.X''ԭ6""W50)=*Xr9o+s5=kxtK!Mn{ddr\ZrlMeVl01klfz-?423a'h8\.̝6+B4PwfuYYvX_X/ ql|ݯ:k8f{+Őۋbݏ\m0\ +PjAeFT!eQtFQiRp)S9@#R9!j/Xpmꊾg #G_%;fAtSek@-g 0CjӀ;Ѓ #R818O`JK8m[Hf8z3 mMZ#֖Kd"\i]!}RC~{ZhdXendstream +endobj +1709 0 obj << +/Type /Page +/Contents 1710 0 R +/Resources 1708 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1687 0 R +>> endobj +1711 0 obj << +/D [1709 0 R /XYZ 85.039 781.388 null] +>> endobj +758 0 obj << +/D [1709 0 R /XYZ 85.039 761.463 null] +>> endobj +1712 0 obj << +/D [1709 0 R /XYZ 85.039 739.701 null] +>> endobj +762 0 obj << +/D [1709 0 R /XYZ 85.039 626.296 null] +>> endobj +1713 0 obj << +/D [1709 0 R /XYZ 85.039 599.682 null] +>> endobj +766 0 obj << +/D [1709 0 R /XYZ 85.039 341.05 null] +>> endobj +1714 0 obj << +/D [1709 0 R /XYZ 85.039 309.525 null] +>> endobj +770 0 obj << +/D [1709 0 R /XYZ 85.039 309.525 null] +>> endobj +1715 0 obj << +/D [1709 0 R /XYZ 85.039 288.997 null] +>> endobj +774 0 obj << +/D [1709 0 R /XYZ 85.039 246.837 null] +>> endobj +1716 0 obj << +/D [1709 0 R /XYZ 85.039 227.965 null] +>> endobj +778 0 obj << +/D [1709 0 R /XYZ 85.039 104.306 null] +>> endobj +1717 0 obj << +/D [1709 0 R /XYZ 85.039 83.313 null] +>> endobj +1708 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F43 1079 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1720 0 obj << +/Length 3034 +/Filter /FlateDecode +>> +stream +xڥZ[s۶~ЛL~ɛj;ΩIϴEkTI*ϯ?{HITs:X,vcO,gO"ߴxFF$ݜYGxf 5L+;?ؖ[d@,wŇ寳뺆혳yFKaf糹mBG[\K}r9}^5@Ÿ,Ӎ3-ӎ]\gwgҫ0͛Cܵ(im [ofs۞N e>mhBos&̉Xբ/еI / L.nVa^tE]h;;0J .sB#ە!Z_`v9fH`zb:8;^?05 +G\A'dʙ^tSgJ8yACqwuZFFWN1GjjXRBƝd4M;tb7ǜ7?훑mkv`3]/68?%Ƶieױ y,{3mHPA`\   6ZU~@bYۤmmcu(,ӳ1]?t¯CUFu 7ji6b8]-v; b dB$Յ|q2+,)EBN£}:7E+19P+YH`_W0ߦ߸6dOV87GtN*~S%YNhHYɛl0jDZ1!2eS[ xɬLU1oXįDo'V3+4B/ ,(sEuCڰ".xWrp- aU1fc8v!H)ItP"nO0m =95;UdJFȸkuRɑJٺ{AʹB~SL=g'vl oDzR/B_/&7!^B"?N[" G%G03dG/ncd{fyS;{D'C`sz +73|.UQGV)7l~ u/ +poF۩Z۲x\H`s7=Bl\<)CGJǴdKV 8 +Bk*)(. ͊A8HsU$x6mX?>#-(YPpfbf$KáFeǾDQY c +"J'z)%. .l(HWu,R i@/UxQ^Yի0'?W'yP8Ʀ{nX~`&vb:7ߖ< +`wzxw˛J4o~+\{~MVrՅezWU_+u{׃QrM=7bXu=D|8Fm ҞNUT~-3p˄zt]~_Q:c}Q`.Kۣ̅z8]6D/9f$_MT )}I/D>&endstream +endobj +1719 0 obj << +/Type /Page +/Contents 1720 0 R +/Resources 1718 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1726 0 R +>> endobj +1721 0 obj << +/D [1719 0 R /XYZ 85.039 781.388 null] +>> endobj +782 0 obj << +/D [1719 0 R /XYZ 85.039 704.845 null] +>> endobj +1722 0 obj << +/D [1719 0 R /XYZ 85.039 678.231 null] +>> endobj +786 0 obj << +/D [1719 0 R /XYZ 85.039 678.231 null] +>> endobj +1723 0 obj << +/D [1719 0 R /XYZ 85.039 654.913 null] +>> endobj +790 0 obj << +/D [1719 0 R /XYZ 85.039 598.597 null] +>> endobj +1724 0 obj << +/D [1719 0 R /XYZ 85.039 580.332 null] +>> endobj +794 0 obj << +/D [1719 0 R /XYZ 85.039 466.321 null] +>> endobj +1725 0 obj << +/D [1719 0 R /XYZ 85.039 437.523 null] +>> endobj +1718 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F20 877 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1729 0 obj << +/Length 1589 +/Filter /FlateDecode +>> +stream +xڥWYoF~ׯCSE\y(8jⴶӈZ$"i0\9HQ€3;7ʞZϞih)pkz)&6sXS״|H^8-3i|,q8/Bv<B#38mZ/./>jq }*^^ξǟ&x}/@4~X^[Erz\b=H!;[GsWbVGW"Y,YՕk$uWYI]U'7guJ[b~6je_ZEֶkU?du\\.3oZ2:h)P8l B-:'2el@"oL.ghH }Ϗ+" Y F A j2BꏅH'}SF~;<ƀF=L<7y7lbe:EdZ˿.y~M"۷ggv䘶$7rQ`4zdP2A>^;pwJsi/.ޯd?:S@IPeȰ̓!%c`TFh6MZ<(n$P~..m,7:Lu1d4*Npɦ)jy$~I':! >F{M$KO> endobj +1730 0 obj << +/D [1728 0 R /XYZ 85.039 781.388 null] +>> endobj +798 0 obj << +/D [1728 0 R /XYZ 85.039 679.868 null] +>> endobj +1731 0 obj << +/D [1728 0 R /XYZ 85.039 648.343 null] +>> endobj +1727 0 obj << +/Font << /F58 956 0 R /F37 900 0 R /F20 877 0 R /F15 895 0 R /F61 1406 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1734 0 obj << +/Length 3176 +/Filter /FlateDecode +>> +stream +xڥZK۸WLTHKCTޭl٩l#1H,ϿOe'h4~|h Od*4S+e7Ëf 3?PBab.ht&YFfiËFMD<<C@2~PA^/:I[p[0; lZ7󱯚z񯇿xKaV*^T_TzV/2+m+x}X*m 'lo`FAym8r*>V=-&L~Wr(.,(q=nsE-4r -B5>?P8.|ӠLY<[=*]%E*E* Nh6( 4ȭ.-6Ud巜gϲMg~)!Gyy.ra{z+!;߂ֆ]W]z1_;Y&NKX9"ZGAG帛a*QڱĐ_qMQ62-+1i(oU\|^{nUĥS/gmoZ5opzà] kd; ݮNw.Du̱%9s鑩×n +UN{Lw@hHҗ*y5ͥ[n5 dЬ(TzkHKa7h%C_~pMaK/:YUo 3'Cpq&hÜ<€lOg@S\NB_It [6ΐTj<@F\~iF;0`/qYFe#TF{#>'סȴř~pۜN<7S6J&ò /;::VhUp>C$DTI),x=})w8AIn=\~gɻ Ehy ؓYm( d #e*QKyoɆ7s:q>+:zMf#~4{vHH'42 nJ6Ӏiiie<r-KBN/R>F-&ak=گAzYIGY% HjRHlGGQY"?/!C(Puq3RŹW`Mm=x4l\Z"z(‚,etR̄]/sp;}|ƩhsvwRĿn/@5^iÛ|m6ą ێ][']֘Ѽ i6 b!b>h JCe'—. +!cې5'0=tfhL209Y"f&/Lwq7@}U7P0GiqGA],%H3PhqԌ1 c^X|xϟq6&P9(ќ?݂ 5(RGZ&GUU:D53> L8r*cV"۵GNS( 佧q3M M/ofFmƾ# X4 +`l}t/ E| @=ș#'@@syؑ}tK(+C3:.n[eT X>ܰq5U擔Z_X4-endstream +endobj +1733 0 obj << +/Type /Page +/Contents 1734 0 R +/Resources 1732 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1726 0 R +>> endobj +1735 0 obj << +/D [1733 0 R /XYZ 85.039 781.388 null] +>> endobj +802 0 obj << +/D [1733 0 R /XYZ 85.039 761.463 null] +>> endobj +1736 0 obj << +/D [1733 0 R /XYZ 85.039 667.044 null] +>> endobj +806 0 obj << +/D [1733 0 R /XYZ 85.039 667.044 null] +>> endobj +1737 0 obj << +/D [1733 0 R /XYZ 85.039 642.326 null] +>> endobj +810 0 obj << +/D [1733 0 R /XYZ 85.039 542.47 null] +>> endobj +1738 0 obj << +/D [1733 0 R /XYZ 85.039 515.856 null] +>> endobj +1732 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1741 0 obj << +/Length 3475 +/Filter /FlateDecode +>> +stream +xڭko~0Q$wrb +\۵:ԑ#gY@|Ϯʀ;^x4@i*NWۓF~: eFp qً8; ?[r]~śoK*L{yлxp y«kYdʻ)WQ~+-Ʈ/_Z|R:Q'?% I<;}vy~=ѱc9:݅)XG<}H8}B@Xq]+eznws_Cɐ߃PoF~9< +8a<ÞיvpbYuܻmzWS0|h{nW5D[^ oXC[b^;}kتzCyqTS6O;e^`@$!s"ƺ< +8͎z=jsjȮ'`ǽ%ց |vM17L{Oq +9/.JnM^-[86).bK%H-۬ j9^,a8G 0p{&t0 Lj0 )id]ЊRxUevu=SɃ x#ϋ*pN?DVQthu_t*Kx<etK*M՚ SIpRoaYG0. ܠ൲5g"HfSmaP!_dt <,H @Fdlxb)Ci# BҲ3|={RH;ՙY;I +?ESa0<$ +e Pá|ۡ,ԛz`e%SA%jY,m?P;XP ̇(xJBwlkr %wOsg = $jUGn lJ;p\zBc0;v&~9|l\KxFˑC&5eN~I)ʽ;tVv3'A.dGmk_uJm)^~~ 2'~y[nb%7\s DI`;"-$g0yGeXMv.aR=ef"*{/CĩGvL9neM|f6Qɷuڜ=[yRژ`B6"л]j[b F7NC}V2PwQb V -xQ.cq(+mcD\!aLf4)̵&[x* @$#; g&? zOe9A|}M=˚Cm)ƔDFU E}_#7S+Έ +7t%Dι#4ayo*;;ځ! 3,*cP6鿉*2ZB3HX|ԗ&~A|#>=P 0ZHHQa2 +)r*Y1fd#aɣ(*]Nr=eS:B܌=PLzpddUWaޥgdWG&JPi,  k1WLW#cy]9zV绺<+_@DS?"W +_Vഁx}˿n~XEsW-z[}mx5#}˄{ZLqf[[ i*Қu))עJ?cR9#o$\mFR%5\3DZՙIT C]S$&f=c%Ќ +SYθZp/$WK9M]*Fi1~,4l2cuyHSExEޑۀіҺ^YZ]&Uİ'ԯO-PuYcyg6kT 2팷9lk8ōv&V4(9(H &{~5 |ϣKs)/`ՔH)֛ (,CL:A8ߏXQ +9C|, '蔲ީf x3SC^#댮<+L Q-7NRqmh\Gw3{R=aLň R^Ͷs~g3c^)hZ8M{s>_I_h)g j?|dOgٺF`+ w|[w쐑fQC:t5=pSA0e1Y 6[~:RwupgJhtLM`!( I:;y&Yd/M\}hE~(Ȼ;(@JHLib8XJ@Pe}#]?`ƛK GO-q'Gp֐xƱm# XkɳoF\ÂHpmhĹq!R-KQpi0I9M~Lmt|X$> endobj +1742 0 obj << +/D [1740 0 R /XYZ 85.039 781.388 null] +>> endobj +814 0 obj << +/D [1740 0 R /XYZ 85.039 761.463 null] +>> endobj +1743 0 obj << +/D [1740 0 R /XYZ 85.039 736.911 null] +>> endobj +1744 0 obj << +/D [1740 0 R /XYZ 85.039 736.911 null] +>> endobj +1739 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F61 1406 0 R /F40 1163 0 R /F36 892 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1747 0 obj << +/Length 831 +/Filter /FlateDecode +>> +stream +xڥUn8}WF +)R[Nҙu2b恶T{ʑ\J~ϓHr<{O|󐾉d}]$dT/RćfCjQfY.>%fs70 b._8wzmރnK;T!`:\)qQU׳ݲaU-/'#w+qAEͮqGwH( +;/WpNv#B>]E3.MzV}Ս(bFNiN(]ǜi7."KX\^˞5> endobj +1748 0 obj << +/D [1746 0 R /XYZ 85.039 781.388 null] +>> endobj +1745 0 obj << +/Font << /F58 956 0 R /F15 895 0 R /F36 892 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1751 0 obj << +/Length 2215 +/Filter /FlateDecode +>> +stream +xYY~ׯv ez;y8"y]-%)CC,`x 0`5ꪯkuKQ,}rGJ~=ӹP ׏ƸER织{宕+[?hC#6\ofNz)vw<.D~2I_x~8OHmYW>ft={(YL;`-]5p=wthG`\+b'rREQWGM:BqCa N/3 e2/=h2YrFMhUqNsuNwe@jΉ1 ޖ.N|nxڝQ +]UaG'wf +B̌QD{ȴ6('*[\,r.F&0Z2wiGhp,iأD;8FO uՏ.ťLe-Io}sn.k| jdgaLe -uin'3wf#/MYJ$Oᷩu h5vx6XhJY7Ea#BxYs>w5 +kbr2D4eS(b>': z+%*.!~YNVxmW$Y+|_~~c +G2zIAjun>0q"J rWɁbrӞ% (<9e(S ]*4l4Dk[ ¿ԩK fѥ5)8 4G0g.6[_XhaufT(;h d1R9EAtvrpX'X`u/o$k'ؼC}ykDEHy<=ޖmݸpAvS W:PӾ` +ae9/ٌg:MvY̖n(w#!$UhZb9@Y-SM78CjJMzEMXwRJN[>Π'(tvCnevsWy 4#-g|vkF@-'j7t˞L{ +j̡-.iv ~ȏ4sx) gX<ʼn`݌MC^eh@k@nѥ,R}^C{Lt +Rݴ/ÚEq%+/0=tJQ-Sq7; uI ؈#v-1Pv+:'K4 !9| +*k3-a~g,z*x ^ޟlVT_޿_?P݉P*돭e!Lۢy 0u $Qn̋l_tZJS&uR: |FS77 VxӱJ Pi0lWQBFFWՐfNC"8&į}q@Ƴkm$ zMk%m)*ܽe([e0aɓ?;of/Mknl +9?5yf~ zzNXk(̆R'RX%f2G ]Rs+$ß?nFp7%ؔg~<[?y o{,7q%lBO`{u,Bҧ'7/ +9{6mgg/ <]_}䢤{ zRφ4 +:ʯQy5rsY|ܻʽ"pIqbHwO%}5ٯWKTPdutTL c=M@>2P4^}ٜ> endobj +1752 0 obj << +/D [1750 0 R /XYZ 85.039 781.388 null] +>> endobj +818 0 obj << +/D [1750 0 R /XYZ 85.039 761.463 null] +>> endobj +1753 0 obj << +/D [1750 0 R /XYZ 85.039 671.912 null] +>> endobj +822 0 obj << +/D [1750 0 R /XYZ 85.039 671.912 null] +>> endobj +1754 0 obj << +/D [1750 0 R /XYZ 85.039 640.387 null] +>> endobj +826 0 obj << +/D [1750 0 R /XYZ 85.039 486.212 null] +>> endobj +1755 0 obj << +/D [1750 0 R /XYZ 85.039 457.414 null] +>> endobj +830 0 obj << +/D [1750 0 R /XYZ 85.039 328.278 null] +>> endobj +1756 0 obj << +/D [1750 0 R /XYZ 85.039 309.406 null] +>> endobj +834 0 obj << +/D [1750 0 R /XYZ 85.039 163.931 null] +>> endobj +1757 0 obj << +/D [1750 0 R /XYZ 85.039 145.06 null] +>> endobj +1749 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1760 0 obj << +/Length 2380 +/Filter /FlateDecode +>> +stream +xڽY[s~ׯg5[bɑg5v2ITv{.I4xd,.Ξ=oąrz$a8YoO Dp|qN+"7,i"yهLkH# ˩t׋'ә_'?NW(2&im:.|G`;{{HmٲmsOt A &b.w{௝/CWFëˋU + &~=S킨~ɔBjݴx"&벰ad*9DCP$ iuU$^t<6XhMZUXVmо((Z5.ުoC +ACgv/DNX{X) 'ղoNn绞sF*{!C a^1BRA#+*3m!e}u]P 7#ϱ%wD/'/sO-h1ݩN=u*J 煮Sſ?~~yjֶK ~N)RuB|wYK4P˘0zK@qI,bI#I0;;5po׀+mT Q~wq[Sq~\x>lKI~Z12Pj&Ns.~ROWS7 (y{ qoQ7p1:-P +v:b|nj1^xaK̏//@f6k=BWw8)ԇ =E#mW6c@މ]K( !ݣegZBb5K(X}T7"݅m_PP]j+ly}eі^ۆMlR!ރhuv9 `@CCGd#:F_91wZ}bchqhaL<`yػV +;;> endobj +1761 0 obj << +/D [1759 0 R /XYZ 85.039 781.388 null] +>> endobj +838 0 obj << +/D [1759 0 R /XYZ 85.039 761.463 null] +>> endobj +1762 0 obj << +/D [1759 0 R /XYZ 85.039 736.911 null] +>> endobj +842 0 obj << +/D [1759 0 R /XYZ 85.039 431.136 null] +>> endobj +1763 0 obj << +/D [1759 0 R /XYZ 85.039 407.154 null] +>> endobj +1758 0 obj << +/Font << /F58 956 0 R /F20 877 0 R /F15 895 0 R /F37 900 0 R /F61 1406 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1767 0 obj << +/Length 1953 +/Filter /FlateDecode +>> +stream +xڽY[D~ϯznB"Xu`;]ʯ\Ǝx-sssyrXt'R$gY8gү0V k '&2R"4ԚpTF!M~{3|¹ +E--YHXZ/-:r!ݝ[9|`}(fw7[hc"vH4BhLL7+BաhX[ 0HGliN7b LCw|(ц-Q^p=wڊ[Gsl0h7|$w~+x)%#( $k`u$vZC<֤XF=26pu[Т3\1ZvF+\h79/"] vGܪ(qű5xb*ЍVnXxXhQ;xYLte^ ҜE1+-U[>gk Kexc=/~UcG!EYe9reϹN5 +r푋xU8ڀ,up첶He1<7Z̦H7߳+ZFL8 +&9+u..IKT#]NA&Q+&drP@K4I4~J! _R-"_;S߉ +Rrk+74ΔŊ~{V^ݩuǖ]>##A)%)g"`bӨ_5e8_X~Bڡi:δ}]~O™C+ ̈́BjD~~_zFGGTدs'&T$PG<3[m{rv[]N;Z *sϛ79^OnflRp,8^477-=Q[^qWh,o'Pi$be{TЈOe@FtZV6iU(BAl 4+ :+[;`lȵ=FH6 +P`"dANR4mWv o{%0{%9`g`NFIay-rb l>UUuSўjgP*fo,3YrI:"&#/8u9Ƅ顚yK_L(yA竰ݧ.nb*7Vu7[3[JuŐd%^;ʚNesHXiRc)]Hz$c0ˤ:Ub\b%BO0cp_TT&Oģ(]ѰEקDh+R?YEIіIІ//Z# +51ۨ/2%̓5FѻӂbBSp-v-6 +3W5XVA4f<+w\o.،7,4m}|Wv[zj荦'HPb!#9UNXaXMYsSȪ6Pb>JAi橾*34v O ˏ2H{#0\3\=_a +yޣP37geѴc6 6kȩ ]ȯ9{_0_sfl&A ݑ'-4eRp~^OLç1a2#-K)$RO-apOe"ЊآLB*sE~Wv9P,};*@$DR1@\c[A%9C*B' z:';L+S\ AeDE +َ +C!vTH^Ѽq?Ë-0NbޚD038u{BO4. h> endobj +1768 0 obj << +/D [1766 0 R /XYZ 85.039 781.388 null] +>> endobj +846 0 obj << +/D [1766 0 R /XYZ 85.039 761.463 null] +>> endobj +1769 0 obj << +/D [1766 0 R /XYZ 85.039 667.044 null] +>> endobj +850 0 obj << +/D [1766 0 R /XYZ 85.039 667.044 null] +>> endobj +1770 0 obj << +/D [1766 0 R /XYZ 85.039 642.326 null] +>> endobj +854 0 obj << +/D [1766 0 R /XYZ 85.039 569.569 null] +>> endobj +1771 0 obj << +/D [1766 0 R /XYZ 85.039 542.954 null] +>> endobj +1765 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R /F40 1163 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1774 0 obj << +/Length 1029 +/Filter /FlateDecode +>> +stream +xڅVn6+P&Ej*MѦ@jMmɖYӐ4;P*ywGzR|fZ,/js/[Zد(E&T6]Q02Wq{&R2If"}IƱwSjQAhDL)0Zs9?_~ߦRiRR6m}mRsu_ *n+D22N5#$ +f |7Ҳ (Dߔn9ܣ\n ||ZYѢnHn`ŻMzSS2W6vp,wu{l=s@\YeUIvė98b= 12{#6 VOA x0 BWȞtMEu-@_ja۞zisŖZrCuǢy5Oz]p p)8x)3@<,)c[VBMV֛ul9F&z [-phx 2#m@P1VY> &fj+Gl)_0Q,"wF*难rcVdTj׮ qcoGD䍈y7 2gn+sM^P!`MjܠEϝO,GkwxA#YGB-$|1 0̕-o0{uc0oJLB˽A}DQ 8>xv\;.ԵkGJcu˫v%BDk*P1Hiij#<`p6T-cBҕs5mwMgFlE  ;B uH^_1d PA,gx+9_RFX4RW"2wQ%W;v>Cd/Tc冲/C>ƭjc9PITg~!ЩY ߇L$(cendstream +endobj +1773 0 obj << +/Type /Page +/Contents 1774 0 R +/Resources 1772 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1764 0 R +>> endobj +1775 0 obj << +/D [1773 0 R /XYZ 85.039 781.388 null] +>> endobj +858 0 obj << +/D [1773 0 R /XYZ 85.039 761.463 null] +>> endobj +1776 0 obj << +/D [1773 0 R /XYZ 85.039 667.044 null] +>> endobj +862 0 obj << +/D [1773 0 R /XYZ 85.039 667.044 null] +>> endobj +1777 0 obj << +/D [1773 0 R /XYZ 85.039 639.536 null] +>> endobj +866 0 obj << +/D [1773 0 R /XYZ 85.039 532.636 null] +>> endobj +1778 0 obj << +/D [1773 0 R /XYZ 85.039 503.901 null] +>> endobj +1772 0 obj << +/Font << /F20 877 0 R /F15 895 0 R /F37 900 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1779 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/omega/epsilon/theta1/pi1/rho1/sigma1/phi1/arrowlefttophalf/arrowleftbothalf/arrowrighttophalf/arrowrightbothalf/arrowhookleft/arrowhookright/triangleright/triangleleft/zerooldstyle/oneoldstyle/twooldstyle/threeoldstyle/fouroldstyle/fiveoldstyle/sixoldstyle/sevenoldstyle/eightoldstyle/nineoldstyle/period/comma/less/slash/greater/star/partialdiff/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/flat/natural/sharp/slurbelow/slurabove/lscript/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/dotlessi/dotlessj/weierstrass/vector/tie/psi 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/tie 197/.notdef] +>> endobj +1408 0 obj << +/Length1 777 +/Length2 1024 +/Length3 532 +/Length 1589 +/Filter /FlateDecode +>> +stream +xRiTWE9(Q(!A "HEEVP,bj-X,K1Z(X"Rʱbuz<՟}}EH'B@?l.x @aeMB!|uss + 88 ğ$oBD +X{&I.S +IT$A@)!b JbO ' !6*@ Eq).&2j%@RNS6Y68(fد$iozSOa+IQEJQ,/ +!)(H $&u |΋ޚ#*c1Nl:*C A)N!郎oʅ} TNuC(N' ༦OakLDJas8\Hޘ拋cIRĠF< PJe{6NP@ 1y>vr_"<`wjݤ㸺89LUE +85CtLP E[}{\O+R}^/.>]S.vg>y=fi0,YQeywz4o2j6:\6sT4AE0Wz0^{welG|ԛP7!+aj|Z۝n"IJ*0~2؛{_DwYid#f ;4(vۥ +Y!u̱|_K_m{@{2]׉ ڴ^ bfQPTF婚%~]yUcdѶw42Mo4/ΛS{IJ+Q ]8mϗ.yu R[R,<s`KsM1ے.0QNg Y;GGG[`|| uHGL$$[X樴BO$ Enɣ މ8n=3F&ͮe 6̤&ڃ?ib.5 \7lDؕQ CkZ:}~ҍO65ET%WS1;?-d^Neָdiye,k. YϯD694T(R] +g.2?`K|/xeǒU=6aT13m|q1eC5ΰL9_+2ёtEZز_f}W"Jc!Vtrr!m܃{>?weV$rKY}մOjeYNqjٕ;+W ե{6ܘҵh>3+Ч.SG5wuoFkΦ-9%/㨴Q7>5Y4mxjn~3XJ,AS̬B\cDk}?XB [Ic)"W̶ӉdYpq\ufx_KiL.? ..mҎ&x6zÓ]ᕷ ZP ^d}~yg,f5]Uoa޷&L'fc<8|_±Ӝ0O0($)B*$.BZendstream +endobj +1409 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1779 0 R +/FirstChar 62 +/LastChar 62 +/Widths 1780 0 R +/BaseFont /LIRIPZ+CMMIB10 +/FontDescriptor 1407 0 R +>> endobj +1407 0 obj << +/Ascent 694 +/CapHeight 686 +/Descent -194 +/FontName /LIRIPZ+CMMIB10 +/ItalicAngle -14 +/StemV 113 +/XHeight 444 +/FontBBox [-15 -250 1216 750] +/Flags 4 +/CharSet (/greater) +/FontFile 1408 0 R +>> endobj +1780 0 obj +[894 ] +endobj +1781 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +1405 0 obj << +/Length1 1358 +/Length2 7588 +/Length3 532 +/Length 8432 +/Filter /FlateDecode +>> +stream +xe\\!K`in]htӸ Np'hp\!x9qwϪU}kUզaX!."5W\n..iLzzbqD<y@0;[ $A:Ԁ. 0%xrڿg8A Ȋ`eg9brh +l + 7`&3n + YcrCj :_q 2 ` PX`j9i(,m@<@Vv.k38?-N9]-Y-ӿ5v.пaxw`vc.x{oCLbeha0'& sy@pǜ%k +8`(|?u8m= BNx,A' 8f~.?ppZ۹7ý9_8翶%O\ +?pG~e&A$7.'ϳj7|[䁯/ \Oׅp]ׅ;mpn ܆? VHKCA/] /6~SI_;~b\Fm՛ڲd3$A3 &?<qil7V~ύF{@(/o8{f*-2sD2еKIfc٥61"pd'kdxc $Ӹ[r BתDwk4hL`Ҹٺ#[*F~֎{'YҿϾL)ZwLjnG_IJpEg}8R3f*Z^',켮 qSTCtS?Hup*x0&qrڑ ]S@C ;V$G񽸲dm:g{N|NF=/_ x6Ib.N^3T/9w8?V!y3t"|?Ag,/9ec,Όs-M_)XS]J&?wZcρj=ժw!\} 0(CG:|mϊ:BY Iv[jo7Ώ7-<[w@; UJ n"af,5Wl~+dV?nhQiN1i2_)t-pX.Zn,Q-`@2eUO5: ˇ&(/z:4:sH\ڋ#jr%'S@\ a9K}4Z( $\RJŠs-!Xr7)UKtjXgNMn6sGLCW*C8j[3QOӱW]O-POZ^TozrTgR2ϴ{2ArPv3jĴo4͓ lMˡޗzL3Y>)+g5Do ,߳'Or8Ou񇫋L)*:+؁Cwf>/m=_Zƭ3?L=uyn䖚j<)#DMjr&~ +j)z 'K>V&J·)[Lz\a §ŢjIdwwr$˱)Cpչ3 ⍛ }{mA)7嘋bG8k4=UnٻQHn02LwH5)/ +i5rɤ|x. UlQxK+2ui +&?jFj"b$sB mmq7qI~63j49^k.23tUՙwbobXSTb c J;~miQyx\4e1zC|ƭbҶ^A}s)c`Xev) SF盝H,K ޾ C뺦Nfz`O,]Do*~&- ΂@  )Zx;Ilw^-CR:F0=Q + 0ﾥ-mh$'fP$fw]sVu}mLWЮ@fyػ$x)J 'Uw +IUd?{EbV9zEEx?Ga(jNdZpshgFd$}&aY-N=l7gՂ>SiC'fWiB.>͏< +{ +"4Ͽ' Vޝwv@A~q"ϔy9Aw絰rGF(IV|o_˖43;$_M lH +F~ٸ"]媇mrJIV!fcM>Ah3,Q|gAhs5^j4~BD.=eDݑ3]K 3qV4OV9*cF +glbԘtE} Z0xUd5Ve!uL$_W^Ԭ>ԴBYhJq6B_ß &pM|k;4쫺W&U+wPzktqG `R_M#JT)+MzmVE<`?1EE\dQls^A)/qzNP)W L ˾㴀Y::]YM{<+|ƥIvXgV3DD«~m06jL}=f^HUwU)*lu}fG"!,Z6HZx  &?a!"X3(iW}.~4EbԚz(2sCdC$2uL)l?݆XAcࣾvUC +ra9 !"m4+V7 mոĘDް 㔢咩f !TNh[QTTYI V'?~1CdQrLǨ:,o%0pY”8}UV^dn#[5lət3(DP>"TM" E(m"uxr_89靋H"G:ͧBuk/( +%l 䶄=a+"fnţ;H飸p5lDLm>?90ywk *f;P~SVglLl(1qrM (j +ea9؉y2BȢ]'cojD#`&KpDs70M赢 yHJ RN2K_wI?|* ]1 [Gg&FT=^HM}-+{4s&Ήz(;B&Am%RęiҶ-6X)CY[.vԿy{_r(~q1T8z4c/&32hv`{_&416!yYn$ [Fj.A1VZDWkwfbD3yBɘD{WFY,ۖ+^`Q. +תƼ]k~}{z$ShTZchϞ8&8`.)pLRڵǭ6ε- WıA;N:5) CKsQwp3 iR*/\S$0Kyۭ(wwc'ˌdŬ*Jݦh};>rC`$`] A\5.s8tJT+#/w`tŨs̵˫p>vx5TuZ=H.Prz)^ CQ<ټtڔo^|u(PqFta{%,|$Z>J$#tCjluɰi] a,O|.* +MytfAq8gܯu +))Ûd^D3L!C*I;]Ĥ]ß־1`v>"L)9N29PZ%s=47K!2v^\эt<%!Ԣ A]U˄,[4h^BTa+sɐ~J-j땼xIgFԁh2)Hq*9Z38~%lboe*P9# Y_F,k6fkQ?$X=X~0-\C2!3a!! W?IZiI-jTbc"[Uf$ۘϬ93 @SaM'V !-7l~n <㺴O>AzHƋw3jCEMq:5%{]UB$"bEf0SiVtaR/֫/jzt1R[Ž|5ua +ioX2:yo~H5X # +AwMW )D +D(x4s]r>0x8*ĥTFm]ŒJo!F-ʅK}j4DQx8k$l`?;xBtH^̳"07l'(o$VNV:T;HMŚ8\q{}@yi??FXPɾmF1t7FHIH(X>]+5<AC\BuIiozƗZLjdG-pZp蘯u!eW;@RF-lz\t<2q56V 1N)2x{J*TNqh}- fO_ZFYn9ԏ"B11T "g*k:OxNWCd)Tz}7 ]Q,c_Qػg7W(0&HnٕԫfU+"瑟Q"Va[F 牤q^iڱJm&MLߠ|vۧ7 y=8|SCQ͚ӵÈG[d ZDu?^]q+W`SA.$0mb*i= +NmZ0ZV;<{BϷm1JdOt!P@>FMPhQYNvZoDפxCmʵ3*;һE2^J +W,$_’[}p% ?k˪8)F;#Q 2%0QՖom`O-RNYUYaț+ﱔq-=.?Đ DArj?ʽ ZX:Xo3FlKT1wH,K*.6_[9v6VY \9 ޗiQ432/D՝&}R}nE6"?5B˅#Ãd^:h- oRb]åb?LVpWGr,jSl|!Z*֛~Cd.P+ߟҺQP:X[z\|hH.s1a`Kv֘L/}$~hχXYk[r +.$ۑkbj!~\hotG?Lȧ, @_My>V2LqWw})RW!pIc =; +4eza+5??8ELNWq:H^lة ;wREc;U?k{1bqJTYZߍy@YFּĔJO7l0f"@`G4ѲhQ<f[Ug4fx?REo¨ZClڷٝI8|p[x+c`g-|GT .=i~t]U< FcQ57]Ob췁9t@/GUqkZSMɡHg)Gab FgS$9Wt(:!_𬼋z:CG|cy8גg2F-gcQW<|zؙ}F +)3 leWBJ.Kcft| qۮ-P}$]~i,M."#L婡ӰF8ם'W55kg^#dʤSO:=pUVʨ%EZ,K=Lj-&FNG4 8!k/ҖLk2-FSL H\CVrV"ɄEۯ (ޛةceI.|R7G"8<םŠx\PҸllػ|̎~uw<ǎ>E)|ٌ̠,z!u>opn4) <0O9s"Y׷#Ӽ{hSV59nĂlS' Xf;ߐ'u6?7 tVMpLl3}#^~ ޮzYQW$H/(UN/0GV J_ /\Fffu8=y88靫uoQæȺETL}dw/M%(v-,Ootmzlf{:7fo>TfIuGs1ΰY#9A$eەr#8CD14sFYei<}ӧ*Q,+ E$2.h6A'T,&TGjϟLKP{Y `Ϲn7,ӡc$&mfS[Fk]hU~>,;Ty)4DM'ܰ*ѧ;]Ѿ׼ fGQ KulyjC`I+ ws2FzBHKkZОg.[X@*^:[k/1J%(cK<KH dk/_6O$ •s78[-L^]G R_E>1b-) 9mz%'4)%F +xø*|T6MB %db\A +4.#r<ΛSC~hzmN[̠RţՍ%բ-eqp.C #]gz}`nm&8gfn/)Uavs>?aOta.0{endstream +endobj +1406 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1781 0 R +/FirstChar 38 +/LastChar 121 +/Widths 1782 0 R +/BaseFont /ESTQDQ+CMBX10 +/FontDescriptor 1404 0 R +>> endobj +1404 0 obj << +/Ascent 694 +/CapHeight 686 +/Descent -194 +/FontName /ESTQDQ+CMBX10 +/ItalicAngle 0 +/StemV 114 +/XHeight 444 +/FontBBox [-301 -250 1164 946] +/Flags 4 +/CharSet (/ampersand/hyphen/period/slash/zero/one/two/three/five/six/seven/eight/semicolon/equal/D/I/P/a/b/c/d/e/f/h/i/k/l/m/n/o/p/r/s/t/u/v/w/y) +/FontFile 1405 0 R +>> endobj +1782 0 obj +[894 0 0 0 0 0 0 383 319 575 575 575 575 575 0 575 575 575 575 0 0 319 0 894 0 0 0 0 0 0 882 0 0 0 0 436 0 0 0 0 0 0 786 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 559 639 511 639 527 351 0 639 319 0 607 319 958 639 575 639 0 474 454 447 639 607 831 0 607 ] +endobj +1162 0 obj << +/Length1 793 +/Length2 1151 +/Length3 532 +/Length 1728 +/Filter /FlateDecode +>> +stream +xRiTS2j=,iF !D(rKr/^n i*ʲ.EEXp""<`|Hժ8 U_osl[! p #ARͦhA8,' poJ\/ y^BBAXGRUO@qD!GTN` YC!W@`B"0 CL + DA p*RX$0Mʄ RIHCzJ +k FvI- YӋh5rd)kI0tj,VfzVBՈBa`WőDCP\O0 +MWB7%GGyS9QtdOŜ?c$с6Dr;%Mk&Fr)8A!X`D1Hgr),51:9{{ߟ /.`pyd+ +sJFZX xlo +UhqF"m{+i +&پkrUl MGvu76ϐ%#߰ %zZm6Xz.YÉ3.~9e`z_ܟ_I)Ys'i:,v_CC%31[tuA(VY/Oz;I`,0æ΁ŖR*pB1&`)ο)\.`~$?$,V=Xf/j ׷k #;~Ŝƽ)h/9iҋ-7+3b=}dzxTk_媯^6OcR'r.p\c:o{:+A%Gb'?[fDK;^^],ǦŒ+[{h]҂=ҹ5N u8~Exow{q;oc8uu©.S8G- H lѩ-'* 캱kDq,W4Z@h?o/̺ϿK]$]r4r'%EO*bȉݼy O"WQkDiendstream +endobj +1163 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1779 0 R +/FirstChar 60 +/LastChar 62 +/Widths 1783 0 R +/BaseFont /EUEUQC+CMMI10 +/FontDescriptor 1161 0 R +>> endobj +1161 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /EUEUQC+CMMI10 +/ItalicAngle -14 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/less/greater) +/FontFile 1162 0 R +>> endobj +1783 0 obj +[778 0 778 ] +endobj +1784 0 obj << +/Type /Encoding +/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 161/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef] +>> endobj +1078 0 obj << +/Length1 795 +/Length2 667 +/Length3 532 +/Length 1237 +/Filter /FlateDecode +>> +stream +xSU uLOJu+53Rp 44P03RUu.JM,sI,IR04Tp,MW04U002225RUp/,L(Qp)2WpM-LNSM,HZRQZZTeh\ǥrg^Z9D8&UZT tБ +@'T*qJB7ܭ4'/1d<80s3s**s JKR|SRЕB盚Y.Y옗khg`l +,vˬHM ,IPHK)N楠;|`{8;zkC,WRY`P "P*ʬP6300*B+2׼̼t#S3ĢJ.` +L 2RR+R+./jQMBZ~(ZI? % qЩI9`aL99WTY*Z344S077EUYX`j```apriQQj^ 8aOwjjEj2k-Yӷs]|a>k_d?nvfJm@%>wX,iG /vRfǝ%ش9QDod;U? ^VNvK{~/t-798 mi"6=!y:I_K-,1{).o +*[mF%s_-j(ls~gغ|K~#ﵾӷ&g]p_!GrnM`v^Dl>Z`,&7{طeY/-pp3LXc:s٧Oy1#u,U)MPPQSiމ_]7`tlx~FqFI8>yj&/E텏Z [%IZҼ/y-ɝ#ߘU))wpxk>Wõ-T2~U]gXZjEO-Z_Ȭ?֌J +vMO7J]8f풻v_ք7xht*̀B5j0 9'5$?7( -endstream +endobj +1079 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1784 0 R +/FirstChar 15 +/LastChar 110 +/Widths 1785 0 R +/BaseFont /HCAMJO+CMSY10 +/FontDescriptor 1077 0 R +>> endobj +1077 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /HCAMJO+CMSY10 +/ItalicAngle -14 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/bullet/backslash) +/FontFile 1078 0 R +>> endobj +1785 0 obj +[500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 ] +endobj +955 0 obj << +/Length1 1351 +/Length2 8100 +/Length3 532 +/Length 8939 +/Filter /FlateDecode +>> +stream +xUXܶ)NqHBqww+@ 8Ŋwwww/V);Z9W9M1Ɯ7Ɯ3ԵX%- f@93+'@ +'^ +4uAeLBNAAN !P3Q_EI; dnjxkl an +hAA@g6$ k@-99 sg +d#E{Ka \P')#̢ZB`Z@ss90Xʛځ]spqBo!@~[?Φ``dG$rZͭ`'q oz +*TN익=꿙a3lB CLb] ^>)j0|-;1;=7EP0W!A 60l 9$`B!R=_`wv{r + +.%Y[ 61/@xۃl3H=X`=<!?g5#LF օ3T `zS ԟ L0g I`ݾ{&އg<LO_ bCYvCXoAš %q`] NN.n?/,|grt*n Qs(h-A  6u|ds&#qH*i If;\Ɵ֏kl@Ÿ Gʥu^؃d%kduإ-Ro;3/^!sg!=XfAnѬ|s/yHd1o qkuv+I0<-l=wQt[EogVgFd$;xGJbPk)^%ᶞSy0^%xqh㴉1miglHw-uCKxZQn; _Ky?J7 7n)a~B+P=\;u9n +k70[=e a9#p)XyBlOPJW 97j].S 7XӭI X.MhWԜÕFN`*g-B&AN.5Y/5f;ַKf}<]KX9啻=owDPFoe<]Yym@b wwaaiAHyphmK@tLYow>%wC Sw&ΙK%i}]-R?G!^sb%[ئh푗|mx<܅dMIBE"?y|-"XE'A27NjB,{hw J2'7Sw֛Aݚ[X%su=%arln(o9r\DXU}H8!+qE~riQCg賏~)gLS 7F&L&R/#~7g.yJVoY0aΌ_."_nCaZVä5ŧUZ$ +yٽEL)#Ѱ2Y~ؼ|g!|zB_4},s.9eZKӚW80>}`GAqVD5>ͤr ;7ꞵ[ݽ²?;(sXDp0; כ> _GQ950Tlbd6g\Q5G=Vw:II{YI*('\{HxD;AQvWaE; VizA`RE--Rsj=8Y4y&rѐO\mz$IW(qTQQYHBE +P53!TC[~,ʦ/,~^}Qz)3ajMԿ,SB#UŚH=GKIS&!8=;A#$pj ~0.R$ _4fTKZ^D-1ڬg<OB2g47=8'VӇ:AG^NU5Ik%KuYyBӠECH|G\7GҜdd]UN&n5,1D +?:-qRڎugOwfG2[#4v.ԚԨ~F~c]蔷'p/?Mv,_wQ=:\^uX{p\ZKm$JZFd-gS?86#/^)9*"rF ,^5K|AX*`$\̍ޛlhbEg:Ȼ~g)XYrq >tQ s@wબa*C_񋈚& \ۚ7MgޔYI\j9&M]@WXaXW.JtZY#S/rm+U b(4VrT.-E+TL%,[N"+boP?s`"謪/D9L-^tPw@C'gxH 4n[x)_tx +Vpf+UƸ Mx0-dlgpdh{}FǎfKˬ8/4~]iRYVM +5i۶iNjC/N!1KɃ.= Եz +)J^cŤZ=}3s7KR7V/h!2 gd5BQWN ,ڹwBs[3u iw<4;)h(w4Kb1Dv3) .MoN޷mzRl 櫘,E^кU3-ӁCi|^3vR՗NKT~t7㑘-&o0l/9:=2|ד.hZX8F4bwҫ J}ui7 +gsy\tɋwo42U2vLxǂJ aNft*ӾEᲀ}fO5ؐZK$z:`UPLn*-LQbjCu<;tŜdj|t0>;Suڱdx~5]g~=?HM*]{5Az2|=hgIٜ,AuYxLT$Q.T45RWif%01i"#~\ Ӛ9:5 uTx|)`${z_RA8iLt|7KH뱱*FWSnR ߀s"pxbPY668Yrپ>hn3~zsHƟ;G!>LzC&=κP] nisDuz ]#VepC"jw*|RZ9dv `Es},bZ"t z'R 7|06o5S`BAìJ _gX,D +%vktv/|~O>z>^"Dh|xPOSɆRʣLK:ܯqNP1t8WU|%/t֑3f= Y$x}S5+R60 }(eLQ ζ:%.\: r62ǐH`J;O{I#/h]BnNBZe5}[c)GmƂP~Q GzqϫOv#ou4?`%4{_#; QD,֌{)۹{k#7ͱ-Z6a +"`m\;D/zEDĸX\`Y] +/ҕNoY*}x^>.3.Ʉ~v~奔[$ֺFS: 7ҩו "V);I FDVDtezBH0SDXdNЦ#sy&SӐ'fQٚԚYIqf~}pG%JjCSIYC;L$1~Aq>1\wXcӛVՁE/!VB;oOS&Ota7sԭ%i\_.YIR$*eF'bDeV&k%yϝqȒz"'D5]P:^f"}=K_ZBOT\Lz(̆yON0,Rs0xLz؂FuhcPg).|?b2 ǴKc@bF˜Qal"6`-0}wxPjm[XAN|q[l)n/ ~2$rPdNA|7dM"Lc7MDBOsG"یh/TҔx2Y>Hʥơѹ'ґZ:. ^] $nT? 䧢] 3D"Zv~Cr;MW>x]8P|~>wZ,Qjwͺf0N1s[*k5iP.ϯ1c +>*BhOQT +.v^{ʻq*1*`Ł]Ox%EkP=O*,#=- ^U]O +&GgcsCFn\{R6т8EKc:N |K+*oub .LiA,ajw#*)L}$3:FZӏ/w:jf#* +'|sl?[M**F$]\"y/| +$oD t=.]G5[+b&[冱`+JQܥh#f>(M>b56[+1C{Ou%6-؄xVPjc.\#+PclM 9bD|j>5%NM J6[J.[qKrYȐ"+e6|R$31HP+XF]rҨckq"9i鵶fO +!eoqZTuR5Rw*ޙQPD]gWV֬S8Jbtm6:3luƂܺ=tP)Ii?r;%uKvUb09QUW@Té-%>I=sh!if r^6GQ娡(JP~$WɑŊc !*> +[ J@òq ƕ^c6,as>VVO`"Ybv,׮VȚwa]&}׭:=Ո}]lgZj==ï,E8Rv+rst& !iգ&w4޻{S++<܌{yG?Sn< MYIM\ H|fU8(KBfo?onq֦!{~)oy?/~3"44j PUfާ,'xlZsH#ȴ@řRl'OEˆ԰H.9aWNP}w]qu K>S(Ibvl?1eݣ<10_W]5q=Ǹ;cNkӁ=fţcg Ҝ[iIY嵖8ج4JdAg}YyҘ꣙. =lD;S up2ibNhBLT%k`̨L_"{D̫)b!Jozm=]qtut'_Ja~V> endobj +954 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /QZIHLU+CMSL10 +/ItalicAngle -9 +/StemV 79 +/XHeight 431 +/FontBBox [-62 -250 1123 750] +/Flags 4 +/CharSet (/dollar/quoteright/period/zero/one/two/three/four/five/six/seven/eight/nine/A/B/C/D/E/F/G/H/I/L/M/N/O/P/R/S/T/U/W/X/Y/e/n/o/s/t) +/FontFile 955 0 R +>> endobj +1786 0 obj +[500 0 0 278 0 0 0 0 0 0 278 0 500 500 500 500 500 500 500 500 500 500 0 0 0 0 0 0 0 750 708 722 764 681 653 785 750 361 0 0 625 917 750 778 681 0 736 556 722 750 0 1028 750 750 0 0 0 0 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 0 556 500 0 0 0 394 389 ] +endobj +1787 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef] +>> endobj +899 0 obj << +/Length1 2210 +/Length2 14292 +/Length3 532 +/Length 15508 +/Filter /FlateDecode +>> +stream +xUXͶp[pw8{`w ]5+Y<<15GլꁊLEQ tcdeb#W`e!eebaCw8%L|lN.l\,|l?*RqG'o+k7RZ$q:\lMn67o&RQ{{RJpx,XYI-lHV6@dpwGW)4?$-ޤKf%GP5 =?k6p!Utw66(@_!W)/5;_a;V_:ʚZb=T1ix;{Ŭ<.6^,e%~*& 4wZqrz#8I}YIm/RH  +)hMI-](;)'$e;f+0)˟7)t!e6uE]MAK(-?a.=(GW2hdpdڻ d`'5\8%nǐ4W{SW?L|.I8fN o7k_ eKG?+ ҵ+ +j$ +Xf,'Hh?swK `Q.=bq2by?AI!I!俉d$@:"@T]+!Pu?@ՕM<*TO!P4UCT]xA5s15fF^gk q..e<ZMB_Z$c/9 )dAG&3/Y9 +-\^dB_l +d|?Oc,+x66n6Ւse ed쬠]i@++:XXx5wwnA K ai#$ ˡŬ?+5tu|n_<*L^\OJ:!u9۾~O uC JSNpoٗ'*d`==Ya\:Rdje8"+Dz*"rAxGݬ'?t1[)sjvXCOS~zC%,F $6zpҡG|R踔7ؽD,RPt¥ 0RcEO暬()ꮤ 1"8D9 o#'2cZF@=Hca%-i^N{s<Hh.>fծUB?9eJS? aլioDd!xʢԕ2*29;0s?|n;]<\Ařm jKѡYzbpP_\aIm^ǠC@L(QHD)|.s#xw3lKukȻFSE<¸ ].'BWWdf ХIW}cw7{w8`J/?<9,=vg +PHs0߈15ŸUvC}Q&@ P|kB%t݆zds,ldd +yۆI=5RA[Sh@ہ g^&$FGl/<3cnҗB9ä;[R +y"NW!@6W_؀w0o:ȝ.@6ڇu,'E QPUd_g{>BܭK`b:_z(xB(^ j@| vtyhhs[PzL3= >|'mH7!6G݇2i3KI5r t[w@n2+Cz|˰v.qʹ+ 7Ljbp/д)&ԏsJdbe2 6=:d1r"[as#[F, +^φ ofN_bH}h?QoZ?;PL0qs^P-Y_ř6u𰱾|Gї5^^}qc$ެ@)r'G2r)o|u +2) 0RV6t#NrA&^ 6ԏ1HXmkWo"{_`$>GËiB$_hޫ_ +5J}N,/r"Ŋ3zT1BqO$-[  JN677"B7MN߄Qc?&o*J"ȌNZs?k%at_F"n3j7YF5] 6IHc8-qעoQ𒴿`]h@[5+x] lAYM ݮ]|ʭql +}1CertdYx<" ?8]hR:$>TI ~y0 :u/(DBս$鄎ba:E'V)If#"6uSYJꜴɆa1ipw9lTДQZ L :U}S_6 yܳ[}@{Ă݌}\@WAՀ>Ɠ8q榥ܦK/\ZBAr! +ܗ7 +5f!?jwQH{5#ɢ7Tب}" :iˋj!.RYR ?$xx<6%urP3i+ԭBcۿwv#B'Z x&3فW'mv?-& +}jy7]5uU6e5 hW^Nr/Z~@pbRt~ʷ>9eoی@A "ї\[Q)\s7+`xMV1*%Vhi`}\s +׸V)5؆ȐE{]Yw茍1g$Hx,phغy~AR4N(~KOn]ŖAPSNu*=b#SROjCYـgLNX+?hG2۞ [3%5>thߗ'-01><EiNӿ2pGm̰tP|sؓ/݄ۏ6;#X%&)0Qʸ4h"L O"qwBV>|ࡇU]]hdScg +` <5(pAyf rJ >!q#\vF!;1Iu(x#LC]ߍ8t> ,gL~r ϔd-Gp݊6??xh5[D+)}ID{3j~t̼e, +Žo\YS􌵾gT ?#|V,]X~D]O7%}O {QH p_hTJ1)~5M9y@kƪWIH#pVxcjZ&4.l 2&wFMqK,qAa ưƠa+鯬g+r3S.\1A|flƸub ƿ,^o1ۻaM'Q#{q&_Btf6?-UHܺVD ;r%҈]͛Л{ XWS"T~3aNdסw]U{ fdLBJq}5ܘ$/"IAHQ'ٔ'74IWo;`msȿaRۇ$jĘ>#ں%?qZK,NZϼtQŝFƋۼVbeq6md*0uB2ƂH '&kRS[7 _6Zd0h/"E`!mw^0h +`Z_zM>gȗydyeqC%~Q 2b@O[v,\9> սoIS{=m$);G󬙓òD:, $V*.Xw\LHw/GjDž*(1+*1J.ST1lG}ޙ'/i>1jmNyTխ0> *~ԲA@̙3Uj6 ~ E[X$lC/}AB3JK3 ]*)\**oSm! _]D]m~E֎(}dž'k-] M-%,g$isn(eFzkD{yL:I=ܒYRpK>Sll6 lu,s:M!.qRvxY!J16"* aJpڤgNO^\7Ƥ9xY9RJ YQ +͑8W*&Itk(_5=wYu!3gyVǐ6X~#<e +}ĒEvߋF +z/8;_``[c<>)iח!_@vR'!~q +a Tt>#wn%=Φ )9iI!43PػpbopXsZS!:=A'?m#2zA 3]Sg+3b3(hx/Q~9`5Vc^h7^`%-qJ5x\Wk +ol\-L ۲ShXUke[h|ᢃT.pXڋ0BƐ8Wn|%:ٸp*CEIcP^!;Yx1giM:9T5Nz]ŚmAnQ`{ t%7禬 _/yY`oZo_uV0,#ԎYKKd;) ϳ^ ++-+P$ӟz;g6`cb0spDJEЄgWؙǏJK虼 ,]&~)l 1YZӏyH]vËtR +R8@ޅt@kfr.Y,Sp7#` +3̎ee(j.?d5ѵ@rlRBOk!` `нREt/ɈE>, &e]`TF~?6kp.i33ٖkێ|azDKte"ޏvh ۺVzat`# +W[TEظ,c2,WWK !q*^YXfN'y ,L1KR3+jiDH3 07+M22*- pRa +Kq5!߫+Hw5~L秗Ӱ.sLl_QY zn '(lmu1Ql=WV06RpoqwJڷ#SUFn+sL>.1yԘH9JOc#IjƤ⢛ 1$HNՁeG¿fP`wm=}r wyJ?DAcwZ˷ʎ:j^ 21gV[q'd)__lRjcnzhS(WI^}xLә~ +\lm@h#;jz'q:`I0.jTf->~J.m_;kdkk7ɶEc^)~c]d +ѠI;zk ІQN"YQ@ +}Ea-aH/*Sz|^ʬ4s7-6 `'r.' Epm ɽ1Y↬@K}9tYxZMXUL:~9CE'79D>S/is \;nv}A@Ux B)Kb9"g>[C3t+i^P]FD/Dḣ̓ˏ@!bcwt,16e{zs4ot\멥J;mUvwΡ<Ѯ?,L'MCnаc {rg[,^bOu\>*JO {bqlxٽ/M9#L\o_Xd2 6FgM.=NFdE}y% {=@M.EuRVi2j/>Tu`K=68T?i,k:h塓I6"-jz37 󐣁sO?n3BtEwh\أjd3 ?3brUG{X*r]ÿ.C󸆐H 6jPP]M~FvϧfӴ_jT'{{X[A;&CLmtwP:.([] pE{0m'1AKg%UyDS$_fͨ`G{bN:W4:u=fCDQ8lTZ#QA5.,J yWpk_:9{3Sᬰ>#,:Ya|3ӝXbaS`m$=-ske$K_MMyBJIe4\{>};dF>ʀbpax5j=؃Mֈf3L/ ? ,|o]ցsUAz!SݟY(k*PYPi3Sx=1|<|OG|e;jkO,]a";WM_f{WYR]vM[eH{?CƉ;^D}+s֧6*?変eZ9[= +.?5C'`9֌@^P&k^NX}wfDѧF9x"#K$fjih@/y8QWR5]ԁWr+dJ kkG+꥖eDI$B*{m5qa!ᄔ 7̉{s6tdAht3lu3~b~8'%_ + yKl~^ gO7,"GD5)ϧ/5ksOMJ ,A21A=aLQ>nKbxٌ^}ƙС9@aT!MS + }mΪE?#k IpR},vyfSuqxiCQȢVh{HR`:fmtT;P }Vk׼_CV{N_9rW[)74#Β9>>Uatj̙\nݦpBK.+cH]߰M]I:Z}fSl>.k+t m]|v +/j틒:nq$~'Jp1臫` ru +^SVZ%I\M',y Α~|*<ۊ8dwVG)pP1(GJs ڔg 2Vk%=RMFRf!O2`p9 r2sb `OyhRK< 7I~z]U-  ||2uWۘț=~}REUY(29A\NsjESО3Έ %dLMO<lN;-틢^$ŪOq| ˣ dž/DjiUh -fC: 1Rq`fG;"G7 +'+<63Jއd-i[aVf^8>Zhw &B7~qOiC3)ϭUл'G4V*(CPI0{}7+OU\ptVЄO]z0O#nj##N'[Զ,Bȟ`;\Kuw6/;|beN" 4Nj89*i%|gkw$r*m}#c߀B$bF(B06Õ +Sdi9u_wB"m~: 9q$e;mGazu*'(."ԜՍN5hM-eu]B׵o-26$sD#1x +2|BA*` Ez;A㙇@˂ͮ8':BB\͝8¯Y$Xن# +EWА *)|5W8/02|O}$ڛxӥKF.}=96 ֨>ӀT =`G; +ȁOYkYNB9mMj`Gq~ 4q̕=I% +Cb#FA >!d9'81ƚ r0 +30X(cy.[;JQu5q2 [yxڥjTNDQQJX i h֠(Ւj%,^&>Zdub^\1Jܾ̃O$*sGǭ> >ɂ+#b_8|. e颷VV{ٺ+ |K_/D ɮ@%L4uڎ]P(cgƚUpwZ!4' +F!\s~6.?F#l6m`ڊ 9p= lIBB^vU&3"nh( B)ojLs/|UP.Z 6˰GgfB9&s FBIS&/d ^`yPe`ՔUڎ7JE6(O/jǩߙ2hKÝC.Xccp!NU7/-SԼ Q0t3Rs?6Y#Xhb? V #M<ɧ). O9b܃unW،pijƟPYrV ^Zgfm/3u0 qEo.|1.!;O}/†LWPTWkpL+ 7Ud7+atiBe|=掳5f&5Vv{*t!Ds=3%zŒ~ce?RN^υ9}bK`mڧtRVv,R +:Cg\n|"ѸKkAqn F640:S#R8lՌޞjQu}XcW"0]D~ l(PH6. Z5C[?[A~PX/T?L;b8ȷʔQrր9/7щk:A w#K +ft[z{k{h9~WDN/V(858GXpc$VC]/ȱrfw$<}]k$ud￪ÜVwY3yY;,eܖ\YBINz."ɫ_z(P]YBN0t!p_l7b6 +Q3 jafJ4]Tȣn;{[;oI.f6wɋ-D*/:gͷ5Ɗ O(+zQǨQäL4oqm<8-'kccϖ?&Gw8~Q<џ]ߖ^*UϽ:KB9V9_%3[{9$:My[H!}˺ @L8@ULi%c[dOx)!}NeU^]DOM ѝ\yg©Cqokp쿍 PX'ϗC([Cj IHvV.uX~@ot7Ct gUH"Cq>3R;l4,iw|Xx&tGX41*,[`aHWPZZ?pHΣhm!P"dQV8$w"'ީ`?1& +Wk?dJc_S V^\3Qŝ'91!ʇIjv!îd*.|ʎ>2Ekw[@XP~ G6fy6J]}6DG$Ʉ\dzG֊GSr-UQw=Vk+ [5.lDmBLed> SvTKT%rk Y,DssxTE*2;/'vM^n2Ih,lo*ǫ|ǡ1JaJN!@] pqwUa__w݆1Kzáhu^xkFr/Q7/$o"#;=xHE l|=|\<-\3v6jfn4lJnw;(.(Y> endobj +898 0 obj << +/Ascent 611 +/CapHeight 611 +/Descent -222 +/FontName /XOUGVB+CMTT10 +/ItalicAngle 0 +/StemV 69 +/XHeight 431 +/FontBBox [-4 -235 731 800] +/Flags 4 +/CharSet (/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/A/B/C/D/E/F/G/H/I/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/underscore/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde) +/FontFile 899 0 R +>> endobj +1788 0 obj +[525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 0 525 525 525 0 525 0 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 ] +endobj +894 0 obj << +/Length1 2181 +/Length2 16529 +/Length3 532 +/Length 17761 +/Filter /FlateDecode +>> +stream +xڬstݺF㤱mV4Xm6'm4nFz>gXc]9 *@֙XT^IB`lag+f !ff!xxY(E=-̝DI$8Z:l}Z[=Uy‰Xpt013X;,lQ5#w\N@)biR%Ml=Mp +v@?o. +6tB?͆6`gc p$38TM&.6UX@;D؜ 8JW_ + +:J*)Z:y:ĺLe&?K%nklgbakFAlh<=@b'b&5܁Œ vGkCljφ_# - + ?Y m).v#Z؉m]l9:fČ&vֆBČGc_OsO)0`k 0+? ?]8Y `o'ǚ_v&B@k'kC'?.bFOݟpv0;O;;W?agm ׿2N:\r F-;PolmCtccQ ϑ`g_NԨ?A8J#*!!NbI!.:I!!!(.J.*.j..Z!7})EQdLL_Q Ufs NV!P"Sp/Z@+_r V.!/ZUGV!/Zy@ ֎e""bE/v3m-WQZ XW8;OXM-5` dglZ+^8SI*b;j]2&@Y2)[yR2!>}agMǁ=crG9;xyv`Y: Hkc_V0DzXHgVtp 7D _0VڵkN߅0I_1P;XUvi0TˊP>FjT!¨I墇x^aO˻^ҵujQpmɬ3]%}||?%N})G鍜\Z͒ [g03kÓ.[O^0E(SOا b工<I.vn +##aHChT9y50 + T;M!*foSҘp4^LPeH +HP4;jǼ'd%ka^pRPNTG{?|pEA;1GO߾^Um5>}Y, a굺t>hbj;"b9w($NQe8}*'s.&cSbĞă$0|ēSt{a-tZ7K˃4Y,/cT;SX4f $ap;@#K +pUkJ<>+S 9Pn6-qn]1o]w3Zb +>> 1ݐ f^wj%VMXwbU;[Q6jmIK9EU!O1ĶPf.>1d?e;y3/X#㗧!^*:S iSgwhxp6@҂PqˤkkC&} K)iI)dz_eCY1swy40{ I/wk;Q]uO̅&jVB&he(@tVvb!Pp^HX H_I_J .f(?wa>ن1Gf"/$:H k\*suY[ivHF܄#-W}hrxgCv!fȤO0T'`ש~npψ9ۥVZT‡ǫ/6g/V\CmgAp\e? C_1N!k bP4SbœTNN腄h3+2 ijبFV$&A= I$r\#!L0@w( Fu$ql$_g4kg7~ˆҥ'E~)B]rRnXJo +9LXǻ~ѺlgFD wv}4j{~셎ޮTh'(R!2Lz/86a~zȕ*{:zc$CՔVfcPUHNnmfԗ]J[mjwY?06Ùa6 +-L_U?FwpwirG J)u]=5@&6oe{swo!esױM 9K|z +@M'Ua6PJ;p$ڛk%1*!EOĉLi],_?ibDMϟ(ЈUlJ??\ )2-,NЂU'p/_qq>wJʛvh=Z$+ =?B՗v[홦]j Pibu(ԛ !/GAmZv: ^:ka- +iqbrE$%Vr*#Xpz%o7D}dy[f6,0 FL\ +Sqch&˹;sI +;޻nui_ DG1-f}P`?X-\Al){ϡ52 v* fŭ_ .>o߸? +yH +u^ W9I#7ICEˏ)%tA7էEhlIzgfPƺN&abCV~aLr7I'^IKbHl 5 TȚ+b8`0S|]eP& LτIу"BU#-zn+DaFPa^dZcO(8 ;A +85=Aoޒu*0lv!&N?rՏ%͞;^3-px/OaExi}7Q(!>nd7,$E`= iqpٍBOQVCƍM {'8o( l!8Ѻu =j*'NPf” z,Jܞ+9"Z!e_ z3(S +;"Hbtؐ olP^)BŚ=1A -"J&ZΓuވ\wo hRivF$&~!Yz?/s1h6K^:IwƒGŨ73ҷ$_cAoRU%I>8 Vs7ʿ}J|J#5ިD 9D궊r D??rXw&BϾ+1<,ցxI^{D{ҩ3UIqd?AuLzwS(Jq_Fw';gP{~/y+ ϡd\ܰ ` "%8˫S慡F#UCDi#-?%1_"s,得WJkkԔNSeܟA:AkQ$x9,\2JW|u+·­~/ܺze[ޅ:31ْFxgB٢k$&e-{͏;#qå3"F_8)JT8C03wH8=V}1t0b8`Q=z-X l3YPcL`qcG"yuIm頄g8hL<3 40M_?LQսdf@Vr7u۞,1^ou{nyN5xކJ0*eQ7Ҫ4ptT"|lcAT ]ۆ.o!CE{cd@ަQs!BބR:t&5j󝸮E:_@(+*cʈ׍ڐX[̞9YqoyEU\o&Pi ?8qǑ ՛!$pQ,pZKT)XoΎ4n+P7lCtBys7 ?I\kSQl!&yPV+ޕ1/h=. >J[nBieBؽSz?jn0O4x\{?A?:jY3N < ZtfMQuVjZFwwE>}5&R q"t>ʑm_Vg۲/v/{W ְIщ#[ )Y_ mxZ\~S3,3jtrQN}E-D +'$#kMą u*QWo1FN?8@~2(dOgFF#~vQJX~oQ]`O'/YaOT09:SRqa_Q0(ө/064 v4!T}Ȟ8y;{7;S;#AXc*>IRiҷz/ωcHge ~V2`CgI0qx-9B$}3HҸ9La +9JHH$kDu`[v2ꋂFMQ UP$!sZCiֵެ$R'kQSHrP^)]M1}K(m&5ef?dCek6=s?Kc:v ߟ/tMR4D3l~"l7EgJnGؐEioÑR'B17aNCw,T>c:(TظLMPsLG,t "Rc3ZV 9]o>s;&x){oi +`?-byvJb{x!^,ǦuDHWB)t+{#ybp&&VJ39ǂTN`b!gR_jr'9S~M?}u_`80gڅpK޲QxiL4uR @ f<OcF z+hjӃċ$)|` 9.aw"z$\&#8GBT3!snc&%@V% YkQ~QnijR)VMa-a. +%!P/WBjt{/&1SOoj2{+ψfni:ك"(RԻxv,(^BND$[[M&qʸRX!Iͷi#hy#Dv|ba_΁mMj-( Uv**v!$qH_="Y +lBR.X(dz+MlqO04D9- -AӢ%ҧPFR&[Qh€^֟2IXfb{}e#e9sCX3.oW S9vp ;3DH @$1Z!/E(%Qxn{ SϡM TQsĚ Eqj +4.HRpa/+19UUl63WUdޯ0?Yq-[Hә&tɬhWH"rLU6If_&pYQeɗ͢ey<E5R %K$vj ?j=MzS+om"?01 <s uh=c.a LYigcԇ%.n] |K&;!#[0R-N:65\)"Emc>=e@?)6i3"=)S +HmlGݠ1$?FMLOsk Qo}^%iƴB'joJp?!Bƻ\䷄}x% PMjk~ Dr_kf08^c[Z ֚Cot"᳦oz!SDv=%(χxdO0:$DG-2B5Wr1 M.KcWdU}u>BW+(kWvZC>! +c+:Yj +;F"&8;e)/>ٮrV69t% +Uͱ,!٭#̋H+taATWCK`0;C/ŔXmպhrL*,5Y&dDLP~γ,!iF{ۃ,n:I Xƺ$$s8YҵЅ[(R( cipA+D![Ahh_"I-a97qWh<$}K Pޡ~^Evn@HsP-a}?XN9!bS-k+EԵgR> +B[~[v_-$Р&ҟnSq-YlJŃi<(U +I^--w'劼*,ꊏFކR`xJ U+½^;M s~;J28ڋ2/v"xݸR)Xm$흈5[2&o}R{/gb5<)/oD?O=8Ro6$});zH窍 .CI+\(jḃ:мSXx oGIv߸Qe#4HVyxNe=Vj|W7IY2&x!w4|q~=T*vn h18٭$aj+ 1R}NILK^EK= 'lW[ün37_Vb JK :x^Z(ӼOwZ]˷+}Fkxv^=:DTӇn+)>}4EY"'HcD;7r~k 0ErMT0 `&f݀s%P]jEMUnE6B|Dn3)O81Y5֯75JM9D)TO<jZ7y{pspdkOwgqՄ>SxWCfUb~ +gЯ In:vzXCYK!͎̺֤d2&H5g'e!b*(WyGMGI݈D+N /d4 +/6ebkJPq7)OrbP^B&݂80IM3qYZ RjrߟhQ7p#s]kj|UuMbi޳s-$]p۫: + m1J+yx쏬UAe*N7ި 4l[w.H`n1{Bn@E:Ⱇvז~DtԒ +g2hKwְZfR)ytMW Oz->k̍`bȒmpۂ=ًeá?J ʆlr7YꢩRv '1Ui + qD bа$-!wF+ֽmXxvYӅYK6hLYڸN$N)gŒIuEU`U2bVgY?f"f(hsgDZ$ڭ*JMS/o`nzjT3?? Z@(=)qUpOHk9w/QW)cUbIߴ xTPa(ce؀v֌}q̈^9!x__M;$F,v ;>d/ 3^d9Fȃ{-B_Sŧ'J4ɔEGx>tuz!Cӹ=<$I^9keоV˗1&+v-hJaJ tX ^'42e(lC<#9Jϧ!i8\&ԡV泑{8}'28[~.y`} 44sĸz_B&d$.ƲQ*+u/hyNK;uEE\e0 +nU@oK6a]zm.eV7eD9Xr`kA$*]Ŷ7Rb4kfk-osU`Z7Kc$/@,LiozjNIA}=^Ԯ++fSu@٧qiR`-xپAԖDޯ +ȭ<).aC'A~TޟzW|׸kb(lGok$0ⳗѺ5ΊSvPCBߠ&Q)'zwfGfӰ:V"!5->nJ6u7r(V3<wӌ*eG5a5gs&||!,=#'dqp:܃a“DM쐵hO3nN3n3勡Ye:ER*| A wTjPne`, Sɧ4wXS_x.rPA+6~i/zp fsۃÒ~C'S +6 Z3oSeNvՏ}2ұE +H(?oI$r٤$iEFWNôҸ~żqDP :7^8}LpvN(E]cލ7Zˑ,^ +IsӜܔ }'vA/F\&U + KwT5vau /߬yo\HY0/! mHoY@ (J$ ^ A`NB4Wdxhmq/qM3jS^4ɻ97&M:VPn"aZ~c;D@ ۧ(jo ѐ{)T=ʆvW0+,FSW-wզTdsPձ)3k|$ݰ+1}fߎ0 _8D`Z&¦V[b¬u4̗е]Ҋn`0` s]2]&d*>C/-Pޗ,'VӉF >N+Ptae ntQyvMPj +3"gTl[vg!$U6>}E,/!g9{IC$#BEr%*MP ›nQEoH ? YxI6WKiDMƛiI.0_`Sren҆pMR%Մ/br$z(21ܦ#DM~fS"џ$BLs߾qqL|G +-}dcC'KsDÇDA5mPBr2:0\sPD<@_Alc#P&mF2v,D¼A.9DT*"4mvRޗK +;~2W*խ1k%se4"]+qk皀0L0GaעK2V9/QEj2fg +QE J7/nl4YUW0䰭)GY1;v(\D}SsCr{"hG7)ɸK,.!ejDAo #4 [d!i&j%+4GM]a"<)Sm qyf B X;pʏHھ;daxu=o)7 0QqX'!=GJ zx.+hBt#iy[Dᐴ 2 u"z2O&?ؠLNr6}jL@D)/!{1BE8dNxh93@v.ڨL @3()%2X)%(겴vǦHPۃ%s#;x`m~T"Ѿ4 +<{{zoGԥFRFiע$oD~AtҽIuB!R^~!ފ IQ*w1el.n"+7؄cUÑ(MOKc +ւB_ {(cLj8 <Գ=/#,{(jw95;ЉR?GE~'|f֧e(ԓhI%%FSO%ž N6XUףQF3W< >oÁ,ϋUa)f)U5_ S~h/=%lu +]>CPsR}'9x)JH2hHP"p{Jf8%2AN{c} d4?MyBmu7귶%M% RAEڹq:Ho1m~S~ V^~8 `ߗ1HRsZ +^$>yX A"&-;߹k5:^\Aȟ2p6`]Xd5Kh[$bxa~+4@OM|c9Fs;r+j`h>'O:S`3q;d 4|>f"ϛ-15zU2cL%{ߟSDjWâUJq[o'7YuADbn:\oy'YSr>_ڹ}5󆦇Tro+9juhU`/y7x\buMїNՙrk98~%KKVԟݑ`i;ޓߏ%|o^A^C;,<xKFϺ;O,G]񋻾~.н1 __17oW%Q)Ey+r/օ% +: N˘4޲.ibgt|鮯I{8|w~UK1v;DzϛxeIi0%U_o9߿k/L3fӏb>j5K:83.sx-U(bU+[̻9,ayh,Q"sUUw7N4?r၀U\]vKsΩ{csL]Sr+gD\ *Ƅ{..KR^q \:1jZMgr_˕6 ]Xն7e 狾Wi|WF?mXI1Usڥ3eɻ9#,v\vMY7MsVV$8.c=UӶ~U:zE|S] 0q{!45> endobj +893 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /INZPWR+CMR10 +/ItalicAngle 0 +/StemV 69 +/XHeight 431 +/FontBBox [-251 -250 1009 969] +/Flags 4 +/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/emdash) +/FontFile 894 0 R +>> endobj +1789 0 obj +[583 556 556 833 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 500 833 500 833 0 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 778 750 708 722 764 681 653 785 750 361 514 778 625 917 750 778 681 778 736 556 722 750 750 1028 750 750 611 278 0 278 0 0 0 500 556 444 556 444 306 500 556 278 306 528 278 833 556 500 556 528 392 394 389 556 528 722 528 528 444 0 1000 ] +endobj +1790 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +891 0 obj << +/Length1 1836 +/Length2 14873 +/Length3 532 +/Length 15918 +/Filter /FlateDecode +>> +stream +xS|߶IǨضmض;VG۶mFV'Xokｺz/Ϲ:SUs7'&OtvΟ]9KOo!'ZAO72\M k} +u1g{ sw7p461+H`o'OS2 gOY;?!vOӯɿӨ۟vc'O,\isSG٘?GOs^sJBs6SF}J?'!>,>e%ЧTC +rSA>gɔЧ,>5Чv8?3 gџi/tjWӬ_i/ta~ڰw_i/a3O j+ӕ_/t~ߗ-e<2l>;SsK|*&E\?O~g>oaSfuΈ;2)W4 78h+!'7ʂc r0E9R҅t%)6V2} +0<en2љHPMf*}3ݖkx #{EXۭշUc$vDsq| ;U9 Tٲ ;0VY5 GtK ++rHxs1lYۣ* ntc3 ÿp wBu2ƱAA'c`LKU뙞Xr ̰sV~iBk@LPIoS:^MczESbȗP]Βn8?VҊN2'ޟL|x.!5Kia vBtC5';):Zhb * 4424xfqKEDZ[ +Vj + RF1YovcEYfXr3@ݰr1*8n;a( 6md_ZğY!5jgO$= ;~xJ +5>0ߌosa.:輪%"m7..R m<O&Ȯ3[1D9Q&2z0^I6$% "wO 黳܏389τf~fl5Uٲ P-< ݟ,,·cNŻ[|0tq#~;1! h:W{:Bfv _ 0?RGXg%Nt۾TN$L ;%[H5pU/zr>60=XeKT)KI '**gHuB:Osw=. cؕ7]]S2H1GBTֵr ۾2n ^}gc^D+2;N]Ȉzଡ଼z]3395+kQ/F@_h,\i8_0ݓ{ȿhțP~m=Ր>/\qKZɟPNV˥bp لlH^B_PU3jx| !s<wl\4JJI~HI~>@@ӠS0i\q/w4Y#mm5E=T/qhŨz#O*, ?,O~X NbV;7m:HL) ՗ m #ͪv>WX>0%{QANÂ@/6֌v3*kw>fP&͟O\x۩de+1L>|wB~{7ZxsADPU>DӀwkdCpv҄&lP8ބ^O(f)ܷ2QPPk}8ou~w +)|б5r~zB2Jɧa.vw C׻dk[n~SUـiqmyWv[B ZI3{;[iC;5a +IX˕m* 5X1_ +2-X@Y|P.)Qbǭđ)p619/#@ANÃyUlIS_<b!EPjܙ98_F2U 'O489QasLރ&X3Ru|uݬPR~qVe++KbA'r}AЈx`?( +dxc'_mo]89|̾>WV/bUKѵZj!}1Fy `^aW-L00ww㦹,'$-JP,;s,JsOf5A?ٰL~KuI;u`XHzArlK݁=jTg%6s0NDz_on), 硠_%G2g1IŸ~výsظGG)׆DOk(@ކ@Wtj1_A,weJZƲfHy_F }n(1R8,H ^`|IftoB)~ jBxEA[`Гva@jz}B{%EѸ?ԕMmoZ~oa@/yN)_ZsQACG<='l}Ns/$2N_??(=fI̎@á V ?Dc {_KU84y(C}pK]fGTYLlT皐jDˆPPItB> +'Zy~. {N>sTtbrս ezZ9PE4E`wpyd e^*}[:3^){R!eǚ`'v(ZS} Љ*)$90ޭzݸnO. +NC9&Zbfwwp \LZBmvSy.ئBNNd-$}G)KoBvJB+$3un |!fmrsH9mv';ٮ ΂9ü +.,$+_MS6sLI,Ҟ^nzUlex*UO4# [u2y{O;~5sϪ1riaӢ]zЋB43^ +)lfqn?0mΣ>M-{.I]ΐ@>|a[ w׾0 +[! 5t@eTWN3A6omNžt lUndŹ؃/U"@榱]/'W*4us"4bsD| +1WfhuzXxh1lLjؘ?7=˴FE-ɮݖ5tz<|W¶\7:ںsv#'Pgr1FXC;Hz&y.v&N)gԥ|4. $lw!qX@˜:h+uoRzNh Nb;SJb!Bf^joKOc1*櫟6L[SŨX+~MYy%e2WQYN*u~՞`7h_c4]X=cTKٱj 9B` 3h߽,(ђRd +LU5#"X̭&K,՚:5w`Lr`yݤ kȑʒ试|po 0D5i2Vkp0=xָgH5D+~%j#m 4+_le |x0a1F|]}PMޖ.V諰ҝw繇UFOU 7oJ_&e:^7O: *Wdt%;^j{.C0=ϵCLP\ӰQv>s#GoP9TVW0ird}Uo Bf<,#}%\x YG%S: EtW|^_F؝޽uվ(e]Ln˲Kr Ȓ1cU%я!jC{+t:Vs% @"w9 ;Սm1e ]$wD(d<[6P]"ocQXJK 2vJL/.>(0:21o_wHv4gV#^E7Wxsݵ~G3x ϳCso)%pÏi˴0-GC{!;j}`10#kxB,RwBYSHjRLMXY4O)FH&Mf;:Rq(0U,ߋ'!ؓKӅRQ< ɍ1Gؗ%aT-<J;{Cd;8~kgТ:Aߝrh }+/HM# m7e͢rJ2(! `%>V0V:c"8Id\evގn8kظ-WSzP\rH0!+P欓o3zsZfܡ<16ְ AJSɚ8cBTIB,*;6^N +VWmGx{JNkC~{:I]VFCٜt/5 D)ȫ`&k5#XS1`EGŦ˜ ~AT~NkGu'Gܾ?}z*&C:SvK[xk<d +v9Le +bt”zҀN>nCIk)q7Ck}Pޟ~}2vc4Nn-ҫ^N': +@0ORш'|IrNHb&E[lc +OVw[(cR}wvHD9xl' #t޴:a *xQP4V_AY/?s-khԌmuRe`+nADy1FOXM1Z$sYu9x`_[R+mUp0jILK٪ Vt/͒eWS:3C¬U2e?>o<}T`L{3%5#X,^L$0LGoG42MW=To5xw1dDo9:Wf`GYҁݝy1b&R]^~DBnB_'rjܼhO/p+0e&m3R=#sએ1Mf[X$zBH=A~ !ܑx2.%BaICOL?bGwUG3h[P Ɇ/.h_ i.䕈̷Kx?׮gu,WP"]XVDzb^RgO"=bu S1, _QΙIq*j 1 6i +wo9&EDD&Upg7dpr$d"D[ݞB﯑sHum5fv(G0w^CI' Hb5xK97}!J/-M +hY "2~AWy|i [SI/E{RqEu7]c{-9.pe%:>_9ٳIk++t)r jࣗ +vpxooʊEts7 2A1S:w Kbhb.*}ȳVlUE _PQIV` ҳ!!Q ihmNCu;ddp3)xmQ5-1l:Sqt!%5/}~Mγ8=&z1$»k7 s:wXw2K hƫS GfD˃} {2"7 j#x|&ߔTY4uݘ׵ڳȰpkq'y_ĵ +b3@o4;nmL0A7>Fo!0(Phܨus&|>ˏbyB^džUE%LD cM!P\c +&37s6bȾmLuOXG|y#L6u-qjTR1rg> +ogD#,Lĝbʬ+iESZX4٢Et!,mē(ݽ-Zܶ`MТp?źh#8^j8&S`һՙ#?ύV@/?L%GYP !wbhCZIT\GaJ$\uI4__FV!|9jT/ 㻸M O\Ưw`qr1lgQhI6@FEnR^wc0[ht t56~GYT}}H9g1 $m>)GDvaB;^:SK&{W.b\2eí3p*48|Q+vmk+-G\c; ^5̹+/(G=1 ?Uz 2Bhx}ߺJP'Lsx};;Idrl;$_$'uev5#Љ&w"$la%w8詝 $h+A5ɹREå9s,CQoK7oMTfO '}`X.raZ.&ՎrD ׹:#{H\,0m[^~1_)\` 4M;]@^ŵmB|GIy㛙ص>m\Vvr88|O_t'+AC]VPo\w#.m?zfez/]/Gޮ}khHԥ#i& e5#1]\Ar钒&:F> p 'Ed#d\P@my g>$z%EvtL6jYϨ$1{oTnL )4V͓jH:xDyoAc/?*wC"H @d8Lu>%Sª;cl4XDM:C [dUԠtd FR V!.21,LpԘ6:rLƭ2¤ͧ*\t`!.Hp@ILR2~Zc1h2̷ܝ'g`<%4B_% U5DOX~u0gsHͻ oq7"3w+qj#ʽ2I¬ـƇ}xY2֦^Y**/杖Sv2ve ߕ3F`E.tvg^a6qIM/5.H<=Y\]Hf+ cʐ?SDHBiEj^Fw.S2?`7WES.y ' +5G7ϖB!PW\?a&Ѽoܰ4j2HRcqIRZۺ3ɓB)f Q,v[DdyY13^ˁ DBdނݳ2%AT+ 8d1w!&f;h t¾yD_Yyi%L W|ϗjy1T;D٨R8'G";MEDywQ~cx}K\)ӧF~_ĝw?wCҗK.gYp6YFb˭Ԉы05KT^Fziӿc򈿲 ]jfvu +|82 |Z)E!8?/@N ÷*|`<,nM]=SjDD`q" +Q6yZ&ήiTr(Y趸+^-{,Z+ @Qte'r-;(Obߒ6Z;w(,>K~4}5 nW^v#$Qӌִ\"t\u@)&Q5wmRM;lRtttBF+߄P׶p.qiFIw]Y_]J' 6]td(C(2,6+M3xZ*MgJXRO)G*0jLHQzg%PI%~8'$I +׮pytMWO Dn j:dl氒''{]F[ sNKGMtob97K +>MyqVD"c8SwիM&X=_Tj5mẒW/|k;܍Pȋ޷^"'*b釰@!9 7f ݖE$1 +_S݊CSRLWQ[fh*f_tTE믦yp7*Adp%ElPY]*CT/i(n +<AEIk9saKa.UtgÄ`KYAK&RBKm:mG\;B$\jh>6S'D1~ cU( vbgñ@[[ptGrhU/X8ocHg\I_(-E\+V ,{sTW<{Qy +{X5=JYNw@A*v/sdq59DUkhE+(X`cU;df׼t`X$7sSCA@Ε^%xÂ{F)gWNc1̼ #$=ֵ.`>J(+e6/YVјUR*G!1Owl+/ )~#1q;+ׄhA.N>3;C؀rxlq[PEDNl;Ss^Z#:_ 9*ƯFo_Jٕ,5 f4Q7.IvMIXU2]b"rjeʩV>MpR/)朳؇.9xc!DvgB)@!r VsRO_%&Mߨ^!&"NEi|qt.<B#@P/$8:g#V &LSoCQ{wdDgTNF%(+%K *'!S uu@S\3kh4'ֆPi]LV/%&$;z}7]Xs"iEk=!k4fgsӗlʃ-!xNS$`soI)-O`JYU nLGH'֭l~uY5k%宱5zuRi"!wbE K\ DPU^>0 4LW\)rJ#嫨n|ics/Q1>7.!}r)p(L>eL?!Y#t9qtW D&6Q{Li۵egh09yյ| ++řhF@S^pJ]Ih~Vvw-Jީu ;,hhz&Dss9 XYUCSA +^ v/C7b<.z~U<ǻ!R& N^2]]a13ވEq$Z[%) ݠ v˻ Y![DESq괊҆o]r{ޒ{/c˭X/O `dmblgchuendstream +endobj +892 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1790 0 R +/FirstChar 11 +/LastChar 122 +/Widths 1791 0 R +/BaseFont /SNTQWX+CMTI10 +/FontDescriptor 890 0 R +>> endobj +890 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /SNTQWX+CMTI10 +/ItalicAngle -14 +/StemV 68 +/XHeight 431 +/FontBBox [-163 -250 1146 969] +/Flags 4 +/CharSet (/ff/fi/fl/quotedblright/numbersign/quoteright/parenleft/parenright/plus/comma/hyphen/period/slash/zero/one/two/four/five/six/colon/semicolon/question/A/B/C/D/E/F/G/I/L/M/N/O/P/Q/R/S/T/U/V/X/Y/a/b/c/d/e/f/g/h/i/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z) +/FontFile 891 0 R +>> endobj +1791 0 obj +[613 562 588 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 514 818 0 0 0 307 409 409 0 767 307 358 307 511 511 511 511 0 511 511 511 0 0 0 307 307 0 0 0 511 0 743 704 716 755 678 653 774 0 386 0 0 627 897 743 767 678 767 729 562 716 743 743 0 743 743 0 0 0 0 0 0 0 511 460 460 511 460 307 460 511 307 0 460 256 818 562 511 511 460 422 409 332 537 460 664 464 486 409 ] +endobj +1792 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +887 0 obj << +/Length1 850 +/Length2 2165 +/Length3 532 +/Length 2768 +/Filter /FlateDecode +>> +stream +xRy<N)5(Ecy%[eK)XQC1bwg*%!NGZ -[SP9}|y?eEk[ ,rM!:K@8<Fh +cDY>CX'h]}z0e1O/S_!XȤtOdy4Hl!d , +جL6 )$zR0%s~+ٌ-'0 LdN Ƞ i N~7eSDڊF (ԀQ "LT;;ֽ)3+{^ҫdsV$06rv8J-<OՋ¯J5 xɃ&&&ln->~rDMJ';U~s]Q=h־fK_t/8LeXH{Bqş@rTKrvOnٙARDT\M ,8 B$8jy 6G=sܘ:^j2ו˩=sl+ +M6\ɲ?b.ĩB M #IIa4W eiOY^pM/Ž2y2FGE04v^$I"[Dm +/Ktx}K4hD9nJ=y΍ԽvqXdYS5 nи \'0~..Kcĕxv;Md0q-楏'*FFdU&кf7O*&`.F)zs:{C|lniGns0FIe5})$X8otywE}6ӹUdR-IAKik79쨖ya{%bǯߊB6:35bxNMؓb/vvԚ]vj vrpErVٝ^6[A乴|Nne.(QCnbkNj];dKΗʈ9q۸/$o Iuf}E6O.Xo;d߆-He# WiU.Hrku)לG'5Oً7{z/(QvץӶ<<:zO٬jJDL-̅vݨ^)sRN1WO;UGy9h3nIyO}r\Ⱥ3/m斘2Jȶ̤Sge^A˄cV\H{PUnůUŃbtIO5~췛k]ٖ566@j\YWWm*4Cܨ #)sQ=ç^Q |JQnG1.%,[[ɏ] j{ʻ?$"_:T7%͢twݸdU)%_Ff\A+֎^0L&q>A\C]ME[ՎfZEӀO_yjq!B,+apUgcL7 ,Ԑmޕ[R1 wJ?Yz>:JEK >9p/}E/MZ??@Bӹ%n$d LiIR gk ,D){iWYKgc-3lk=uTJ +V@?R8r~3a\lK_BM/~yO& ˜)KRcUqw*?*|i"Ρˠ,asJSV—Xn/NҩduOUm<1;G+OOϩ_@q6 TpkZqRVtV]ZXy=a 2KO{մ“SLf +79/U.]h":.ƽanVt:}WzLvUn%;qmiȒlpQbry.`B=J!W-*h2d+;V#zEgftotӪhl`jT,-8߾QfyO#UPCweTM0ÿ>2>o<~e6MsknG͏-.ޓA!"Z(ɥǒoʶKϑ7nsڰ84 eSWJ:N}x3NK5eΨAP+-L8ݱ=;٧igI HrFE}p^>Öm$0v죴2Ys[5P +,Fd ^}endstream +endobj +888 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1792 0 R +/FirstChar 65 +/LastChar 116 +/Widths 1793 0 R +/BaseFont /TBPDHW+CMCSC10 +/FontDescriptor 886 0 R +>> endobj +886 0 obj << +/Ascent 514 +/CapHeight 683 +/Descent 0 +/FontName /TBPDHW+CMCSC10 +/ItalicAngle 0 +/StemV 72 +/XHeight 431 +/FontBBox [14 -250 1077 750] +/Flags 4 +/CharSet (/A/a/b/c/r/s/t) +/FontFile 887 0 R +>> endobj +1793 0 obj +[814 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 613 580 591 0 0 0 0 0 0 0 0 0 0 0 0 0 0 602 458 591 ] +endobj +879 0 obj << +/Length1 969 +/Length2 3492 +/Length3 532 +/Length 4169 +/Filter /FlateDecode +>> +stream +xy@.!^IC3>3U|VF=7b\[g?*?:%mS&B\|y\h )7tabBǒ#'|%Nv?T)9_K~p(#~vm_xꐂ{k2ꖮܩ[nTUlBze+bpHqCxW2ҙi'_Y5)`տ&pOB +Fd="nF7ܸKfD8,:r(&Iz-tw(ǩ#!v\>w}|L2~&C%C=^>8vs[yU9)$Hb%za8*G +H 8ihj3[(Z.UN\5w`˼떐鿺rh#~.ɲ*1(%{ou=_G?ׯQc^c^ΚxrqD 糁4H*0.gÛTx<s7b\9X/ǚQp3 +FI,IХp){ɑzZmާI6VPS?REf +Ot$/b\n3NYӖ*̲UG}̸2|\0/uhuNd0oe@^vqka֖|"UM>MhqjviRF|ҩɛx{⣭宵R/ı10Vmv31ZG b{IruP7?臻Y 8v^wuy4IsG~dFQ+{0k[ײ_<В2MuhT̔jkf3O쏮m/u>ׅXYYp0!h)&K 0@5H5_xbW4䏱$02 b%J>mz>6gPVZ4" Q]j>Ff]>R(rO|^w6T*ۭqѺ%Hҵx\!rjtňWuZa8Q\8'.>▴ 2}=D(%>} a]2Ƚl7I6#z D #=ZHۑ Sr}myZ1ZkDVU-;#k0pK~"~nTNH3ݮ6ydR`\sZ,zO˛%w~ 4yزb Ya"#D:S +^[r)4]jd%ɜ;^Ըu&XUo܁4FO,yڂ1\=x,:2hMbn B~s!U5 +.rޞx)O֌f"YZu"(w}'y.(Ad_)m7/E=ao Z~O&W.ګZo E +)~ߓ <P\C +z#!Yo[WEUKa8o>iNqGMڹwg)uY2s䊾Ӎѡ%wr:0<$z!{Zox(nJ$E9ɖ̾ʪr{P4$0sw?gb*` +][xj)ci^8@ֶیO,{|v<-!0^ˀ;B3k;|k,7po|͸p(`8kzپi38w}>v [۟[76WT[> endobj +878 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /PORZYW+CMR12 +/ItalicAngle 0 +/StemV 65 +/XHeight 431 +/FontBBox [-34 -251 988 750] +/Flags 4 +/CharSet (/zero/one/two/three/A/B/M/S/T/a/e/m/s/t/y) +/FontFile 879 0 R +>> endobj +1794 0 obj +[490 490 490 490 0 0 0 0 0 0 0 0 0 0 0 0 0 734 693 0 0 0 0 0 0 0 0 0 0 897 0 0 0 0 0 544 707 0 0 0 0 0 0 0 0 0 0 0 0 490 0 0 0 435 0 0 0 0 0 0 0 816 0 0 0 0 0 386 381 0 0 0 0 517 ] +endobj +876 0 obj << +/Length1 1972 +/Length2 11871 +/Length3 532 +/Length 12951 +/Filter /FlateDecode +>> +stream +xUX\]h; + \w` ݃Hp <;wwS:ϡns=sɦ&WRe6%@NLXy",,HԢ@C' #+@ `eB,̝tL, mN@pcCk* lm P G +4 +00v,lq5#ll_C.@G,I+l&@S$f]@R3?Ok9; z" "i'Ck ca[3k ?Bn@% 'cs#_qT7_2j ^ +Z:;?Ŭo @ +x"_}5X؂7' ; dXؚ@73[)S?K +^ufh`7sAN@#X|ϑ`0:mEY3?&mO +G -v0E8v@۷)p"[hmh0{@op [࿙l6 v2w5v4`]GR@\ oZ-O֠7--F"o)Fbo[ Z5K^7KHR7ȾE.ovQx#⿉F`7E.jovQ#]>E.Z&l`hlto|1mƏ Fo`vX+2 %:,,B_ V6omB/[llB_r V.!lBǿ_"" 7O&eb`p{OTi1!gaVr|Z?@iaddR#^0^KH^4\ִC3Ң#XĔsAثS9x./CPWwN_MVٖ]#"K;l>+w>qL󥏕r v +җVdjÑ$P_7ekej5cdFH9bRj2'j{6$϶A==4S[\q2!D.qPy̖޾wY>n-bm?q )UDY=̜%bZ٪ gDZ +oBU&VF_5Y.-SM'q:\fxSVpَ#:T[ +kUÕ"OjRd|d@s#'zrpOJ?|4TNKPK|`7`ϙRK(͸6ӷSeNQP5.krI*~/*(^&^f6&rf1y2S_pSC# ORQ}b=drJ:fyU_,b]I;-gHQJpn62 +SHOߩ&}|5&YG)#CE`eY)RCTdpQK/%_EQvSTJbgb.CN\ꣁv17> + kB}&qb |Tȷ-+Ѳ!2'(\wHxV?ijWd>g/mJ3g ]"f7@Ȳ$̟(_|{,C't +h&nf+mDŽv3ڪR?h7V0;tӪ$'J@%bڍq$)°6M"9=LC5t ]ԛu9P$ө}60d!"Gn,,:XzC4L DAۉxz+I-0a+AzdmRs훫eSc2Br2Z,mďJ~2vzhjO (fK'?oe+[W"rlƆ#[Jݞ@{hNBfg7dK} =dAܔ(ecl8{%'_3jHP9m?Omx(2͛} *c%̔$cXY_Ѯ<$$c $Шorrh2/2eLZXnkDBGE56!2"$-%vI +p/ O#jQQ>:?|K4|{"c|h3KWra3Ax8 +D-b|0E]WjB8C+F}rVpa!V SC!Ge1Ia_1zy:(+^@Ls׻֍3-~X/^FdQc,J8-ָR㊥y)ka`KNi`uQ!#:!z'xå2y*!m.wB>5ٵj͗. )0GAsxz .c;㖍-#j`TX[tinP9MZOCգ9H0e2ɯxAVaQ&mT4>SQ,6gP.l . P7@c#~Y{2ptӠ(\t-[ʽR3X,H` H*Fpˑ +4ܨVò%JfwSuC[r}ӵ k1j;rȮ]Q/g7$I@Ӧ R X_YM2c>R~h;cbE 9*Ete%״5aVJd5Q:_;2h:\`PX°|JXtV[xfŪ]sl!iK +Asj+geUgO3Uyu߅Vr$OgdiyD+|:YYIcZ<>ܩJs;Y#B?9-T/< q<bbc\]~L\u + -/S-"'L ;^osb<"|0Oh"jnA rP`_tEމ[A6ųc1.Y^i(e.810LVI0:ʔd5%8cE]}w\MXRF?\ +ac/Kּv΀ic?}jDmy_Ӧ0xF]z 8eb]g`WI~sj; ,E[ӻ(DKAB{֔ +;M +nGaVxqS_ۛĕGA6|p#$3~~☜93hō67SE{uڴR@ qQF EM(v3t +acIR;5aqApKov&cH.W:8G{*E"OkP6i:k6 +R|"h|q8$5ff灴3‘Ù[>]\fd)n}՞!_#${f+֒Ͽyol"Wfu)۹oƆ~Kp] _ PI]_ۙˆn_T{7rur<,P+8\e!$pc>5~(*ǼwjZNE ޙ 8-I%Iɮ<،7QC5OGéA73yN}&ND>:^*Ye_f"w*p͋ۨ[8MTc"l|8*։,p&S3l]k$p [/!#̇_dU&` ;B5u!8!dD_W:jh`"Puņ% WTFzįuNcbV+B-jf L_tK 94LT7PY4 |`&ۆ.;ի]J;Z색$Tj2qlomQ"IaA_=ğ>3<4x.7$b|tPa)PNB$'M|{ +₍(aqH6 ےAM7|Fi!Hx&cbgv5 K9w6jThork'm<# 4(8BmpXU% |g=@zhx'LJҎL q6ZwdyU@9FN;gX-z $/cBDv"rW>}9&V*k3#jDzHwC*Et/U(XfX>]`dKlYӈY1(K.)MI :9̓Q}}Cxi Z.=NTg ]XMF,5аn9,Tn*U(ժIZCCQ {]s׷{cjpvZZwu.N–6K>Th7}=4netnKϋ.+]S9Y Sf=r+)= /3^B~N{ }['.Om>i-&TU& qծU̜:&^?i"5 +SS<({e;<͟|3.ƍUg層|Klٟx>ˆ} tN˸T:74IF8(;iؽmYaB| mWcrz2/ 3s/.c|'~QGeci=yk;a9!B)WB.|h~u#gѭ%ra}#'=/IAޑ$ڈKu4|ZA:=.T[Avǯ&wl^˱KoY×rh / ax4'NCYQ쾅}6ۇEQŤ\ݷ#rn?N B긨S} ;e8d17'U0b_ԓվJvz_Pp?Mھ%rGU@1GNM 5]Ŕk xR~=ޠ{ϲ& +HvE QtYn]\#yɴ$a#N+]Nܵfܛ 6}=/o?f ;5gj*eCYtP~x9bta:,m~QSi\V=gBЦ[Y-VC~JQ|%q|Kr xCHO 9\碷EU'tgvy[΢'&+ 9cYWS縯Z> DL~`?aXϝ}$20^-VNҍ/p(BEp`T|Z _!q,@Ɠ텬蝦9j6̦QIRtmG9珘Q0h˓< AϡxI:nEU;I-r>Yy!w||ZLQn+/Z.F'Dvyy.@㚾%o+ noݩ:MLj)%ړGY 67n-v?鹢i·ϊua.\& x8ԙfGQ~ON81%Ԧ[˚4jH!:Bqx@wak|d@OE~ }*K"@aAc[B#`g6m󰘜dx0dھVPLIJR8Y.9c"px{i0Ue |2ʮԌ)щC y;W!U3c9Q}SoH-xtѐXh> K3pX+Hpd߭@RJn\Бf$d}W4"1*|O$I/lяdG\ld1zxҶ}Tj-'}KfҒ(<{pXg!Ln(-ǣvm +GKp3%ʉSVKv柶W -vE+J{?(C'3`j F8+p0TYY/䷺RnΏH1~!MLw z.Ώ4=g?p [+@l¡#$ѴAsͱ׫ၖ! cB> +R +mˤH[]Xc+98aa^Rv%{K6ѝ'jA'~d\Yc)15񠋮>Q1>Q}^r`|4vd]R@:}e^ /pZ&R@'S kj`t"Tn#I&<:9IK~\1F+7SDTv[aezb+`sũ:;r#Mu2 Ȭ?d=5n</^(֌Xh2p̂' + UX3 #=@6 ݄ϬM'[&,hz/,dpNq}?Ǵ #wY\.*˨}+vcï./~TlS›X2hNOejCOWT}O0<&Şui%Y~:n|a&!Nc^]e(i!Rw)М3"lNv&U~/B] ,Mκv{ mWpϕF/IYf-J&1/em[6W>zSLCΕ+}la yTB T]PU!t~9!XaVlְm,3cyl5[tChue%oI..xK+`D4JҴ*V5V`= `*Co_48It_V0δ`JG$Vo~Q5/&W@47~25ͭsoQ mr̵2?uQ^^bR:d~~=ݼvLmuS)Bښ{Ry)k+5|?zRb2xM;KK/_)yK*,˙{dͤ>tkh' 07irN5ϥ؞)0l^| F(:\xFx\]){@͐YMjzTxg з mݘCي/)z~j_~H3ocU'dv+%huUgԪ >T\grz)IH]_K4?1UPֶD3%&ܻb$ܶCɎW1L)&i0+C?!q#,cvҳQVϯơ6)uZvdc3 +q+dFBc5v|}ljJ5~J6Qf!0'E'+Iu "}Ltp +}M߄gyQcLoebt<&!4ܽ 1i=5:[RXmIݶ/xa GP@ ~b jUWuH ҟA#Y h^whʯ< 1 +rټ ̡nJvȆ:S1(-K#vStf- +}3<;b?=)!aJSA +b %Wql A"汗>Dk[H_D6QpL_pB#?nKL%| n\4gBQM=n'u,̈nNL).C+1 B Ee8O&sIo^Rn3ee8??:i5ca'Zo׍QUˑˊi"rRGQ{0ɚS@ O*PPcژ8(?]3 ~w%lgHn +Cvf ˷J03.(7/R44"Mam'B|cj$ ,U@N(DeNmnelrV& >)>e6a./n Cc89m]81Q\~02qC^&en}ZF魗.ڗU(K$gE0/V~v;׳8_h~7e-Afrc-I걡z`#=-ifգiC >C%Fcܗ_D=CvvN)"铮Pxq+>! T i%hf6*j;q|E9(obJp/9@ЄDlVaB=y +~X/uf}#k*?ADٯ̀r";2j2d @nSff/b +Yr%9y[sCbpz5+mdTI7c߅3zdtaTE*/f1{p8&E\X=yԦ_!Rf/F(ہRӉ'Vu#OwLM Nh59_^%"kYK gs~7^%ls.# # j-.)`!nй4i;@qc\`?MYo_@[sBbِVe,_+[ @6VHàendstream +endobj +877 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 1781 0 R +/FirstChar 11 +/LastChar 122 +/Widths 1795 0 R +/BaseFont /JXXTGO+CMSSBX10 +/FontDescriptor 875 0 R +>> endobj +875 0 obj << +/Ascent 694 +/CapHeight 694 +/Descent -194 +/FontName /JXXTGO+CMSSBX10 +/ItalicAngle 0 +/StemV 136 +/XHeight 458 +/FontBBox [-71 -250 1099 780] +/Flags 4 +/CharSet (/ff/fi/fl/quotedblright/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z) +/FontFile 876 0 R +>> endobj +1795 0 obj +[642 586 586 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 558 0 0 0 0 306 428 428 550 856 306 367 306 550 550 550 550 550 550 550 550 550 550 550 306 0 0 0 0 519 0 733 733 703 794 642 611 733 794 331 519 764 581 978 794 794 703 794 703 611 733 764 733 1039 733 733 0 343 0 0 0 0 0 525 561 489 561 511 336 550 561 256 286 531 256 867 561 550 561 561 372 422 404 561 500 744 500 500 476 ] +endobj +881 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [870 0 R 883 0 R 906 0 R 951 0 R 1007 0 R 1063 0 R] +>> endobj +1148 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [1120 0 R 1150 0 R 1157 0 R 1165 0 R 1180 0 R 1188 0 R] +>> endobj +1202 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [1198 0 R 1204 0 R 1210 0 R 1221 0 R 1236 0 R 1257 0 R] +>> endobj +1289 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [1272 0 R 1291 0 R 1310 0 R 1324 0 R 1339 0 R 1358 0 R] +>> endobj +1372 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [1363 0 R 1374 0 R 1382 0 R 1389 0 R 1396 0 R 1400 0 R] +>> endobj +1414 0 obj << +/Type /Pages +/Count 6 +/Parent 1796 0 R +/Kids [1411 0 R 1416 0 R 1434 0 R 1447 0 R 1459 0 R 1470 0 R] +>> endobj +1487 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1479 0 R 1489 0 R 1496 0 R 1502 0 R 1508 0 R 1514 0 R] +>> endobj +1525 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1520 0 R 1527 0 R 1536 0 R 1544 0 R 1550 0 R 1562 0 R] +>> endobj +1581 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1574 0 R 1583 0 R 1591 0 R 1602 0 R 1612 0 R 1621 0 R] +>> endobj +1638 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1629 0 R 1640 0 R 1646 0 R 1654 0 R 1662 0 R 1670 0 R] +>> endobj +1687 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1680 0 R 1689 0 R 1693 0 R 1697 0 R 1703 0 R 1709 0 R] +>> endobj +1726 0 obj << +/Type /Pages +/Count 6 +/Parent 1797 0 R +/Kids [1719 0 R 1728 0 R 1733 0 R 1740 0 R 1746 0 R 1750 0 R] +>> endobj +1764 0 obj << +/Type /Pages +/Count 3 +/Parent 1798 0 R +/Kids [1759 0 R 1766 0 R 1773 0 R] +>> endobj +1796 0 obj << +/Type /Pages +/Count 36 +/Parent 1799 0 R +/Kids [881 0 R 1148 0 R 1202 0 R 1289 0 R 1372 0 R 1414 0 R] +>> endobj +1797 0 obj << +/Type /Pages +/Count 36 +/Parent 1799 0 R +/Kids [1487 0 R 1525 0 R 1581 0 R 1638 0 R 1687 0 R 1726 0 R] +>> endobj +1798 0 obj << +/Type /Pages +/Count 3 +/Parent 1799 0 R +/Kids [1764 0 R] +>> endobj +1799 0 obj << +/Type /Pages +/Count 75 +/Kids [1796 0 R 1797 0 R 1798 0 R] +>> endobj +1800 0 obj << +/Type /Outlines +/First 7 0 R +/Last 859 0 R +/Count 16 +>> endobj +867 0 obj << +/Title 868 0 R +/A 865 0 R +/Parent 859 0 R +/Prev 863 0 R +>> endobj +863 0 obj << +/Title 864 0 R +/A 861 0 R +/Parent 859 0 R +/Next 867 0 R +>> endobj +859 0 obj << +/Title 860 0 R +/A 857 0 R +/Parent 1800 0 R +/Prev 847 0 R +/First 863 0 R +/Last 867 0 R +/Count -2 +>> endobj +855 0 obj << +/Title 856 0 R +/A 853 0 R +/Parent 847 0 R +/Prev 851 0 R +>> endobj +851 0 obj << +/Title 852 0 R +/A 849 0 R +/Parent 847 0 R +/Next 855 0 R +>> endobj +847 0 obj << +/Title 848 0 R +/A 845 0 R +/Parent 1800 0 R +/Prev 819 0 R +/Next 859 0 R +/First 851 0 R +/Last 855 0 R +/Count -2 +>> endobj +843 0 obj << +/Title 844 0 R +/A 841 0 R +/Parent 839 0 R +>> endobj +839 0 obj << +/Title 840 0 R +/A 837 0 R +/Parent 819 0 R +/Prev 827 0 R +/First 843 0 R +/Last 843 0 R +/Count -1 +>> endobj +835 0 obj << +/Title 836 0 R +/A 833 0 R +/Parent 827 0 R +/Prev 831 0 R +>> endobj +831 0 obj << +/Title 832 0 R +/A 829 0 R +/Parent 827 0 R +/Next 835 0 R +>> endobj +827 0 obj << +/Title 828 0 R +/A 825 0 R +/Parent 819 0 R +/Prev 823 0 R +/Next 839 0 R +/First 831 0 R +/Last 835 0 R +/Count -2 +>> endobj +823 0 obj << +/Title 824 0 R +/A 821 0 R +/Parent 819 0 R +/Next 827 0 R +>> endobj +819 0 obj << +/Title 820 0 R +/A 817 0 R +/Parent 1800 0 R +/Prev 803 0 R +/Next 847 0 R +/First 823 0 R +/Last 839 0 R +/Count -3 +>> endobj +815 0 obj << +/Title 816 0 R +/A 813 0 R +/Parent 803 0 R +/Prev 811 0 R +>> endobj +811 0 obj << +/Title 812 0 R +/A 809 0 R +/Parent 803 0 R +/Prev 807 0 R +/Next 815 0 R +>> endobj +807 0 obj << +/Title 808 0 R +/A 805 0 R +/Parent 803 0 R +/Next 811 0 R +>> endobj +803 0 obj << +/Title 804 0 R +/A 801 0 R +/Parent 1800 0 R +/Prev 751 0 R +/Next 819 0 R +/First 807 0 R +/Last 815 0 R +/Count -3 +>> endobj +799 0 obj << +/Title 800 0 R +/A 797 0 R +/Parent 751 0 R +/Prev 795 0 R +>> endobj +795 0 obj << +/Title 796 0 R +/A 793 0 R +/Parent 751 0 R +/Prev 783 0 R +/Next 799 0 R +>> endobj +791 0 obj << +/Title 792 0 R +/A 789 0 R +/Parent 783 0 R +/Prev 787 0 R +>> endobj +787 0 obj << +/Title 788 0 R +/A 785 0 R +/Parent 783 0 R +/Next 791 0 R +>> endobj +783 0 obj << +/Title 784 0 R +/A 781 0 R +/Parent 751 0 R +/Prev 767 0 R +/Next 795 0 R +/First 787 0 R +/Last 791 0 R +/Count -2 +>> endobj +779 0 obj << +/Title 780 0 R +/A 777 0 R +/Parent 767 0 R +/Prev 775 0 R +>> endobj +775 0 obj << +/Title 776 0 R +/A 773 0 R +/Parent 767 0 R +/Prev 771 0 R +/Next 779 0 R +>> endobj +771 0 obj << +/Title 772 0 R +/A 769 0 R +/Parent 767 0 R +/Next 775 0 R +>> endobj +767 0 obj << +/Title 768 0 R +/A 765 0 R +/Parent 751 0 R +/Prev 763 0 R +/Next 783 0 R +/First 771 0 R +/Last 779 0 R +/Count -3 +>> endobj +763 0 obj << +/Title 764 0 R +/A 761 0 R +/Parent 751 0 R +/Prev 759 0 R +/Next 767 0 R +>> endobj +759 0 obj << +/Title 760 0 R +/A 757 0 R +/Parent 751 0 R +/Prev 755 0 R +/Next 763 0 R +>> endobj +755 0 obj << +/Title 756 0 R +/A 753 0 R +/Parent 751 0 R +/Next 759 0 R +>> endobj +751 0 obj << +/Title 752 0 R +/A 749 0 R +/Parent 1800 0 R +/Prev 743 0 R +/Next 803 0 R +/First 755 0 R +/Last 799 0 R +/Count -7 +>> endobj +747 0 obj << +/Title 748 0 R +/A 745 0 R +/Parent 743 0 R +>> endobj +743 0 obj << +/Title 744 0 R +/A 741 0 R +/Parent 1800 0 R +/Prev 719 0 R +/Next 751 0 R +/First 747 0 R +/Last 747 0 R +/Count -1 +>> endobj +739 0 obj << +/Title 740 0 R +/A 737 0 R +/Parent 719 0 R +/Prev 735 0 R +>> endobj +735 0 obj << +/Title 736 0 R +/A 733 0 R +/Parent 719 0 R +/Prev 731 0 R +/Next 739 0 R +>> endobj +731 0 obj << +/Title 732 0 R +/A 729 0 R +/Parent 719 0 R +/Prev 727 0 R +/Next 735 0 R +>> endobj +727 0 obj << +/Title 728 0 R +/A 725 0 R +/Parent 719 0 R +/Prev 723 0 R +/Next 731 0 R +>> endobj +723 0 obj << +/Title 724 0 R +/A 721 0 R +/Parent 719 0 R +/Next 727 0 R +>> endobj +719 0 obj << +/Title 720 0 R +/A 717 0 R +/Parent 1800 0 R +/Prev 251 0 R +/Next 743 0 R +/First 723 0 R +/Last 739 0 R +/Count -5 +>> endobj +715 0 obj << +/Title 716 0 R +/A 713 0 R +/Parent 703 0 R +/Prev 711 0 R +>> endobj +711 0 obj << +/Title 712 0 R +/A 709 0 R +/Parent 703 0 R +/Prev 707 0 R +/Next 715 0 R +>> endobj +707 0 obj << +/Title 708 0 R +/A 705 0 R +/Parent 703 0 R +/Next 711 0 R +>> endobj +703 0 obj << +/Title 704 0 R +/A 701 0 R +/Parent 687 0 R +/Prev 691 0 R +/First 707 0 R +/Last 715 0 R +/Count -3 +>> endobj +699 0 obj << +/Title 700 0 R +/A 697 0 R +/Parent 691 0 R +/Prev 695 0 R +>> endobj +695 0 obj << +/Title 696 0 R +/A 693 0 R +/Parent 691 0 R +/Next 699 0 R +>> endobj +691 0 obj << +/Title 692 0 R +/A 689 0 R +/Parent 687 0 R +/Next 703 0 R +/First 695 0 R +/Last 699 0 R +/Count -2 +>> endobj +687 0 obj << +/Title 688 0 R +/A 685 0 R +/Parent 251 0 R +/Prev 671 0 R +/First 691 0 R +/Last 703 0 R +/Count -2 +>> endobj +683 0 obj << +/Title 684 0 R +/A 681 0 R +/Parent 671 0 R +/Prev 679 0 R +>> endobj +679 0 obj << +/Title 680 0 R +/A 677 0 R +/Parent 671 0 R +/Prev 675 0 R +/Next 683 0 R +>> endobj +675 0 obj << +/Title 676 0 R +/A 673 0 R +/Parent 671 0 R +/Next 679 0 R +>> endobj +671 0 obj << +/Title 672 0 R +/A 669 0 R +/Parent 251 0 R +/Prev 643 0 R +/Next 687 0 R +/First 675 0 R +/Last 683 0 R +/Count -3 +>> endobj +667 0 obj << +/Title 668 0 R +/A 665 0 R +/Parent 659 0 R +/Prev 663 0 R +>> endobj +663 0 obj << +/Title 664 0 R +/A 661 0 R +/Parent 659 0 R +/Next 667 0 R +>> endobj +659 0 obj << +/Title 660 0 R +/A 657 0 R +/Parent 643 0 R +/Prev 647 0 R +/First 663 0 R +/Last 667 0 R +/Count -2 +>> endobj +655 0 obj << +/Title 656 0 R +/A 653 0 R +/Parent 647 0 R +/Prev 651 0 R +>> endobj +651 0 obj << +/Title 652 0 R +/A 649 0 R +/Parent 647 0 R +/Next 655 0 R +>> endobj +647 0 obj << +/Title 648 0 R +/A 645 0 R +/Parent 643 0 R +/Next 659 0 R +/First 651 0 R +/Last 655 0 R +/Count -2 +>> endobj +643 0 obj << +/Title 644 0 R +/A 641 0 R +/Parent 251 0 R +/Prev 615 0 R +/Next 671 0 R +/First 647 0 R +/Last 659 0 R +/Count -2 +>> endobj +639 0 obj << +/Title 640 0 R +/A 637 0 R +/Parent 631 0 R +/Prev 635 0 R +>> endobj +635 0 obj << +/Title 636 0 R +/A 633 0 R +/Parent 631 0 R +/Next 639 0 R +>> endobj +631 0 obj << +/Title 632 0 R +/A 629 0 R +/Parent 615 0 R +/Prev 619 0 R +/First 635 0 R +/Last 639 0 R +/Count -2 +>> endobj +627 0 obj << +/Title 628 0 R +/A 625 0 R +/Parent 619 0 R +/Prev 623 0 R +>> endobj +623 0 obj << +/Title 624 0 R +/A 621 0 R +/Parent 619 0 R +/Next 627 0 R +>> endobj +619 0 obj << +/Title 620 0 R +/A 617 0 R +/Parent 615 0 R +/Next 631 0 R +/First 623 0 R +/Last 627 0 R +/Count -2 +>> endobj +615 0 obj << +/Title 616 0 R +/A 613 0 R +/Parent 251 0 R +/Prev 551 0 R +/Next 643 0 R +/First 619 0 R +/Last 631 0 R +/Count -2 +>> endobj +611 0 obj << +/Title 612 0 R +/A 609 0 R +/Parent 603 0 R +/Prev 607 0 R +>> endobj +607 0 obj << +/Title 608 0 R +/A 605 0 R +/Parent 603 0 R +/Next 611 0 R +>> endobj +603 0 obj << +/Title 604 0 R +/A 601 0 R +/Parent 551 0 R +/Prev 591 0 R +/First 607 0 R +/Last 611 0 R +/Count -2 +>> endobj +599 0 obj << +/Title 600 0 R +/A 597 0 R +/Parent 591 0 R +/Prev 595 0 R +>> endobj +595 0 obj << +/Title 596 0 R +/A 593 0 R +/Parent 591 0 R +/Next 599 0 R +>> endobj +591 0 obj << +/Title 592 0 R +/A 589 0 R +/Parent 551 0 R +/Prev 579 0 R +/Next 603 0 R +/First 595 0 R +/Last 599 0 R +/Count -2 +>> endobj +587 0 obj << +/Title 588 0 R +/A 585 0 R +/Parent 579 0 R +/Prev 583 0 R +>> endobj +583 0 obj << +/Title 584 0 R +/A 581 0 R +/Parent 579 0 R +/Next 587 0 R +>> endobj +579 0 obj << +/Title 580 0 R +/A 577 0 R +/Parent 551 0 R +/Prev 567 0 R +/Next 591 0 R +/First 583 0 R +/Last 587 0 R +/Count -2 +>> endobj +575 0 obj << +/Title 576 0 R +/A 573 0 R +/Parent 567 0 R +/Prev 571 0 R +>> endobj +571 0 obj << +/Title 572 0 R +/A 569 0 R +/Parent 567 0 R +/Next 575 0 R +>> endobj +567 0 obj << +/Title 568 0 R +/A 565 0 R +/Parent 551 0 R +/Prev 555 0 R +/Next 579 0 R +/First 571 0 R +/Last 575 0 R +/Count -2 +>> endobj +563 0 obj << +/Title 564 0 R +/A 561 0 R +/Parent 555 0 R +/Prev 559 0 R +>> endobj +559 0 obj << +/Title 560 0 R +/A 557 0 R +/Parent 555 0 R +/Next 563 0 R +>> endobj +555 0 obj << +/Title 556 0 R +/A 553 0 R +/Parent 551 0 R +/Next 567 0 R +/First 559 0 R +/Last 563 0 R +/Count -2 +>> endobj +551 0 obj << +/Title 552 0 R +/A 549 0 R +/Parent 251 0 R +/Prev 411 0 R +/Next 615 0 R +/First 555 0 R +/Last 603 0 R +/Count -5 +>> endobj +547 0 obj << +/Title 548 0 R +/A 545 0 R +/Parent 539 0 R +/Prev 543 0 R +>> endobj +543 0 obj << +/Title 544 0 R +/A 541 0 R +/Parent 539 0 R +/Next 547 0 R +>> endobj +539 0 obj << +/Title 540 0 R +/A 537 0 R +/Parent 411 0 R +/Prev 527 0 R +/First 543 0 R +/Last 547 0 R +/Count -2 +>> endobj +535 0 obj << +/Title 536 0 R +/A 533 0 R +/Parent 527 0 R +/Prev 531 0 R +>> endobj +531 0 obj << +/Title 532 0 R +/A 529 0 R +/Parent 527 0 R +/Next 535 0 R +>> endobj +527 0 obj << +/Title 528 0 R +/A 525 0 R +/Parent 411 0 R +/Prev 515 0 R +/Next 539 0 R +/First 531 0 R +/Last 535 0 R +/Count -2 +>> endobj +523 0 obj << +/Title 524 0 R +/A 521 0 R +/Parent 515 0 R +/Prev 519 0 R +>> endobj +519 0 obj << +/Title 520 0 R +/A 517 0 R +/Parent 515 0 R +/Next 523 0 R +>> endobj +515 0 obj << +/Title 516 0 R +/A 513 0 R +/Parent 411 0 R +/Prev 503 0 R +/Next 527 0 R +/First 519 0 R +/Last 523 0 R +/Count -2 +>> endobj +511 0 obj << +/Title 512 0 R +/A 509 0 R +/Parent 503 0 R +/Prev 507 0 R +>> endobj +507 0 obj << +/Title 508 0 R +/A 505 0 R +/Parent 503 0 R +/Next 511 0 R +>> endobj +503 0 obj << +/Title 504 0 R +/A 501 0 R +/Parent 411 0 R +/Prev 491 0 R +/Next 515 0 R +/First 507 0 R +/Last 511 0 R +/Count -2 +>> endobj +499 0 obj << +/Title 500 0 R +/A 497 0 R +/Parent 491 0 R +/Prev 495 0 R +>> endobj +495 0 obj << +/Title 496 0 R +/A 493 0 R +/Parent 491 0 R +/Next 499 0 R +>> endobj +491 0 obj << +/Title 492 0 R +/A 489 0 R +/Parent 411 0 R +/Prev 479 0 R +/Next 503 0 R +/First 495 0 R +/Last 499 0 R +/Count -2 +>> endobj +487 0 obj << +/Title 488 0 R +/A 485 0 R +/Parent 479 0 R +/Prev 483 0 R +>> endobj +483 0 obj << +/Title 484 0 R +/A 481 0 R +/Parent 479 0 R +/Next 487 0 R +>> endobj +479 0 obj << +/Title 480 0 R +/A 477 0 R +/Parent 411 0 R +/Prev 467 0 R +/Next 491 0 R +/First 483 0 R +/Last 487 0 R +/Count -2 +>> endobj +475 0 obj << +/Title 476 0 R +/A 473 0 R +/Parent 467 0 R +/Prev 471 0 R +>> endobj +471 0 obj << +/Title 472 0 R +/A 469 0 R +/Parent 467 0 R +/Next 475 0 R +>> endobj +467 0 obj << +/Title 468 0 R +/A 465 0 R +/Parent 411 0 R +/Prev 463 0 R +/Next 479 0 R +/First 471 0 R +/Last 475 0 R +/Count -2 +>> endobj +463 0 obj << +/Title 464 0 R +/A 461 0 R +/Parent 411 0 R +/Prev 459 0 R +/Next 467 0 R +>> endobj +459 0 obj << +/Title 460 0 R +/A 457 0 R +/Parent 411 0 R +/Prev 455 0 R +/Next 463 0 R +>> endobj +455 0 obj << +/Title 456 0 R +/A 453 0 R +/Parent 411 0 R +/Prev 419 0 R +/Next 459 0 R +>> endobj +451 0 obj << +/Title 452 0 R +/A 449 0 R +/Parent 419 0 R +/Prev 447 0 R +>> endobj +447 0 obj << +/Title 448 0 R +/A 445 0 R +/Parent 419 0 R +/Prev 443 0 R +/Next 451 0 R +>> endobj +443 0 obj << +/Title 444 0 R +/A 441 0 R +/Parent 419 0 R +/Prev 439 0 R +/Next 447 0 R +>> endobj +439 0 obj << +/Title 440 0 R +/A 437 0 R +/Parent 419 0 R +/Prev 435 0 R +/Next 443 0 R +>> endobj +435 0 obj << +/Title 436 0 R +/A 433 0 R +/Parent 419 0 R +/Prev 431 0 R +/Next 439 0 R +>> endobj +431 0 obj << +/Title 432 0 R +/A 429 0 R +/Parent 419 0 R +/Prev 427 0 R +/Next 435 0 R +>> endobj +427 0 obj << +/Title 428 0 R +/A 425 0 R +/Parent 419 0 R +/Prev 423 0 R +/Next 431 0 R +>> endobj +423 0 obj << +/Title 424 0 R +/A 421 0 R +/Parent 419 0 R +/Next 427 0 R +>> endobj +419 0 obj << +/Title 420 0 R +/A 417 0 R +/Parent 411 0 R +/Prev 415 0 R +/Next 455 0 R +/First 423 0 R +/Last 451 0 R +/Count -8 +>> endobj +415 0 obj << +/Title 416 0 R +/A 413 0 R +/Parent 411 0 R +/Next 419 0 R +>> endobj +411 0 obj << +/Title 412 0 R +/A 409 0 R +/Parent 251 0 R +/Prev 267 0 R +/Next 551 0 R +/First 415 0 R +/Last 539 0 R +/Count -12 +>> endobj +407 0 obj << +/Title 408 0 R +/A 405 0 R +/Parent 287 0 R +/Prev 403 0 R +>> endobj +403 0 obj << +/Title 404 0 R +/A 401 0 R +/Parent 287 0 R +/Prev 399 0 R +/Next 407 0 R +>> endobj +399 0 obj << +/Title 400 0 R +/A 397 0 R +/Parent 287 0 R +/Prev 395 0 R +/Next 403 0 R +>> endobj +395 0 obj << +/Title 396 0 R +/A 393 0 R +/Parent 287 0 R +/Prev 391 0 R +/Next 399 0 R +>> endobj +391 0 obj << +/Title 392 0 R +/A 389 0 R +/Parent 287 0 R +/Prev 387 0 R +/Next 395 0 R +>> endobj +387 0 obj << +/Title 388 0 R +/A 385 0 R +/Parent 287 0 R +/Prev 383 0 R +/Next 391 0 R +>> endobj +383 0 obj << +/Title 384 0 R +/A 381 0 R +/Parent 287 0 R +/Prev 379 0 R +/Next 387 0 R +>> endobj +379 0 obj << +/Title 380 0 R +/A 377 0 R +/Parent 287 0 R +/Prev 375 0 R +/Next 383 0 R +>> endobj +375 0 obj << +/Title 376 0 R +/A 373 0 R +/Parent 287 0 R +/Prev 371 0 R +/Next 379 0 R +>> endobj +371 0 obj << +/Title 372 0 R +/A 369 0 R +/Parent 287 0 R +/Prev 367 0 R +/Next 375 0 R +>> endobj +367 0 obj << +/Title 368 0 R +/A 365 0 R +/Parent 287 0 R +/Prev 363 0 R +/Next 371 0 R +>> endobj +363 0 obj << +/Title 364 0 R +/A 361 0 R +/Parent 287 0 R +/Prev 359 0 R +/Next 367 0 R +>> endobj +359 0 obj << +/Title 360 0 R +/A 357 0 R +/Parent 287 0 R +/Prev 355 0 R +/Next 363 0 R +>> endobj +355 0 obj << +/Title 356 0 R +/A 353 0 R +/Parent 287 0 R +/Prev 351 0 R +/Next 359 0 R +>> endobj +351 0 obj << +/Title 352 0 R +/A 349 0 R +/Parent 287 0 R +/Prev 347 0 R +/Next 355 0 R +>> endobj +347 0 obj << +/Title 348 0 R +/A 345 0 R +/Parent 287 0 R +/Prev 343 0 R +/Next 351 0 R +>> endobj +343 0 obj << +/Title 344 0 R +/A 341 0 R +/Parent 287 0 R +/Prev 339 0 R +/Next 347 0 R +>> endobj +339 0 obj << +/Title 340 0 R +/A 337 0 R +/Parent 287 0 R +/Prev 335 0 R +/Next 343 0 R +>> endobj +335 0 obj << +/Title 336 0 R +/A 333 0 R +/Parent 287 0 R +/Prev 331 0 R +/Next 339 0 R +>> endobj +331 0 obj << +/Title 332 0 R +/A 329 0 R +/Parent 287 0 R +/Prev 327 0 R +/Next 335 0 R +>> endobj +327 0 obj << +/Title 328 0 R +/A 325 0 R +/Parent 287 0 R +/Prev 323 0 R +/Next 331 0 R +>> endobj +323 0 obj << +/Title 324 0 R +/A 321 0 R +/Parent 287 0 R +/Prev 319 0 R +/Next 327 0 R +>> endobj +319 0 obj << +/Title 320 0 R +/A 317 0 R +/Parent 287 0 R +/Prev 315 0 R +/Next 323 0 R +>> endobj +315 0 obj << +/Title 316 0 R +/A 313 0 R +/Parent 287 0 R +/Prev 311 0 R +/Next 319 0 R +>> endobj +311 0 obj << +/Title 312 0 R +/A 309 0 R +/Parent 287 0 R +/Prev 307 0 R +/Next 315 0 R +>> endobj +307 0 obj << +/Title 308 0 R +/A 305 0 R +/Parent 287 0 R +/Prev 303 0 R +/Next 311 0 R +>> endobj +303 0 obj << +/Title 304 0 R +/A 301 0 R +/Parent 287 0 R +/Prev 299 0 R +/Next 307 0 R +>> endobj +299 0 obj << +/Title 300 0 R +/A 297 0 R +/Parent 287 0 R +/Prev 295 0 R +/Next 303 0 R +>> endobj +295 0 obj << +/Title 296 0 R +/A 293 0 R +/Parent 287 0 R +/Prev 291 0 R +/Next 299 0 R +>> endobj +291 0 obj << +/Title 292 0 R +/A 289 0 R +/Parent 287 0 R +/Next 295 0 R +>> endobj +287 0 obj << +/Title 288 0 R +/A 285 0 R +/Parent 267 0 R +/Prev 275 0 R +/First 291 0 R +/Last 407 0 R +/Count -30 +>> endobj +283 0 obj << +/Title 284 0 R +/A 281 0 R +/Parent 275 0 R +/Prev 279 0 R +>> endobj +279 0 obj << +/Title 280 0 R +/A 277 0 R +/Parent 275 0 R +/Next 283 0 R +>> endobj +275 0 obj << +/Title 276 0 R +/A 273 0 R +/Parent 267 0 R +/Prev 271 0 R +/Next 287 0 R +/First 279 0 R +/Last 283 0 R +/Count -2 +>> endobj +271 0 obj << +/Title 272 0 R +/A 269 0 R +/Parent 267 0 R +/Next 275 0 R +>> endobj +267 0 obj << +/Title 268 0 R +/A 265 0 R +/Parent 251 0 R +/Prev 255 0 R +/Next 411 0 R +/First 271 0 R +/Last 287 0 R +/Count -3 +>> endobj +263 0 obj << +/Title 264 0 R +/A 261 0 R +/Parent 255 0 R +/Prev 259 0 R +>> endobj +259 0 obj << +/Title 260 0 R +/A 257 0 R +/Parent 255 0 R +/Next 263 0 R +>> endobj +255 0 obj << +/Title 256 0 R +/A 253 0 R +/Parent 251 0 R +/Next 267 0 R +/First 259 0 R +/Last 263 0 R +/Count -2 +>> endobj +251 0 obj << +/Title 252 0 R +/A 249 0 R +/Parent 1800 0 R +/Prev 247 0 R +/Next 719 0 R +/First 255 0 R +/Last 687 0 R +/Count -8 +>> endobj +247 0 obj << +/Title 248 0 R +/A 245 0 R +/Parent 1800 0 R +/Prev 207 0 R +/Next 251 0 R +>> endobj +243 0 obj << +/Title 244 0 R +/A 241 0 R +/Parent 207 0 R +/Prev 239 0 R +>> endobj +239 0 obj << +/Title 240 0 R +/A 237 0 R +/Parent 207 0 R +/Prev 235 0 R +/Next 243 0 R +>> endobj +235 0 obj << +/Title 236 0 R +/A 233 0 R +/Parent 207 0 R +/Prev 231 0 R +/Next 239 0 R +>> endobj +231 0 obj << +/Title 232 0 R +/A 229 0 R +/Parent 207 0 R +/Prev 227 0 R +/Next 235 0 R +>> endobj +227 0 obj << +/Title 228 0 R +/A 225 0 R +/Parent 207 0 R +/Prev 223 0 R +/Next 231 0 R +>> endobj +223 0 obj << +/Title 224 0 R +/A 221 0 R +/Parent 207 0 R +/Prev 219 0 R +/Next 227 0 R +>> endobj +219 0 obj << +/Title 220 0 R +/A 217 0 R +/Parent 207 0 R +/Prev 215 0 R +/Next 223 0 R +>> endobj +215 0 obj << +/Title 216 0 R +/A 213 0 R +/Parent 207 0 R +/Prev 211 0 R +/Next 219 0 R +>> endobj +211 0 obj << +/Title 212 0 R +/A 209 0 R +/Parent 207 0 R +/Next 215 0 R +>> endobj +207 0 obj << +/Title 208 0 R +/A 205 0 R +/Parent 1800 0 R +/Prev 179 0 R +/Next 247 0 R +/First 211 0 R +/Last 243 0 R +/Count -9 +>> endobj +203 0 obj << +/Title 204 0 R +/A 201 0 R +/Parent 199 0 R +>> endobj +199 0 obj << +/Title 200 0 R +/A 197 0 R +/Parent 179 0 R +/Prev 183 0 R +/First 203 0 R +/Last 203 0 R +/Count -1 +>> endobj +195 0 obj << +/Title 196 0 R +/A 193 0 R +/Parent 183 0 R +/Prev 191 0 R +>> endobj +191 0 obj << +/Title 192 0 R +/A 189 0 R +/Parent 183 0 R +/Prev 187 0 R +/Next 195 0 R +>> endobj +187 0 obj << +/Title 188 0 R +/A 185 0 R +/Parent 183 0 R +/Next 191 0 R +>> endobj +183 0 obj << +/Title 184 0 R +/A 181 0 R +/Parent 179 0 R +/Next 199 0 R +/First 187 0 R +/Last 195 0 R +/Count -3 +>> endobj +179 0 obj << +/Title 180 0 R +/A 177 0 R +/Parent 1800 0 R +/Prev 87 0 R +/Next 207 0 R +/First 183 0 R +/Last 199 0 R +/Count -2 +>> endobj +175 0 obj << +/Title 176 0 R +/A 173 0 R +/Parent 87 0 R +/Prev 163 0 R +>> endobj +171 0 obj << +/Title 172 0 R +/A 169 0 R +/Parent 163 0 R +/Prev 167 0 R +>> endobj +167 0 obj << +/Title 168 0 R +/A 165 0 R +/Parent 163 0 R +/Next 171 0 R +>> endobj +163 0 obj << +/Title 164 0 R +/A 161 0 R +/Parent 87 0 R +/Prev 99 0 R +/Next 175 0 R +/First 167 0 R +/Last 171 0 R +/Count -2 +>> endobj +159 0 obj << +/Title 160 0 R +/A 157 0 R +/Parent 99 0 R +/Prev 155 0 R +>> endobj +155 0 obj << +/Title 156 0 R +/A 153 0 R +/Parent 99 0 R +/Prev 151 0 R +/Next 159 0 R +>> endobj +151 0 obj << +/Title 152 0 R +/A 149 0 R +/Parent 99 0 R +/Prev 147 0 R +/Next 155 0 R +>> endobj +147 0 obj << +/Title 148 0 R +/A 145 0 R +/Parent 99 0 R +/Prev 143 0 R +/Next 151 0 R +>> endobj +143 0 obj << +/Title 144 0 R +/A 141 0 R +/Parent 99 0 R +/Prev 139 0 R +/Next 147 0 R +>> endobj +139 0 obj << +/Title 140 0 R +/A 137 0 R +/Parent 99 0 R +/Prev 135 0 R +/Next 143 0 R +>> endobj +135 0 obj << +/Title 136 0 R +/A 133 0 R +/Parent 99 0 R +/Prev 131 0 R +/Next 139 0 R +>> endobj +131 0 obj << +/Title 132 0 R +/A 129 0 R +/Parent 99 0 R +/Prev 127 0 R +/Next 135 0 R +>> endobj +127 0 obj << +/Title 128 0 R +/A 125 0 R +/Parent 99 0 R +/Prev 123 0 R +/Next 131 0 R +>> endobj +123 0 obj << +/Title 124 0 R +/A 121 0 R +/Parent 99 0 R +/Prev 119 0 R +/Next 127 0 R +>> endobj +119 0 obj << +/Title 120 0 R +/A 117 0 R +/Parent 99 0 R +/Prev 115 0 R +/Next 123 0 R +>> endobj +115 0 obj << +/Title 116 0 R +/A 113 0 R +/Parent 99 0 R +/Prev 111 0 R +/Next 119 0 R +>> endobj +111 0 obj << +/Title 112 0 R +/A 109 0 R +/Parent 99 0 R +/Prev 107 0 R +/Next 115 0 R +>> endobj +107 0 obj << +/Title 108 0 R +/A 105 0 R +/Parent 99 0 R +/Prev 103 0 R +/Next 111 0 R +>> endobj +103 0 obj << +/Title 104 0 R +/A 101 0 R +/Parent 99 0 R +/Next 107 0 R +>> endobj +99 0 obj << +/Title 100 0 R +/A 97 0 R +/Parent 87 0 R +/Prev 95 0 R +/Next 163 0 R +/First 103 0 R +/Last 159 0 R +/Count -15 +>> endobj +95 0 obj << +/Title 96 0 R +/A 93 0 R +/Parent 87 0 R +/Prev 91 0 R +/Next 99 0 R +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 87 0 R +/Next 95 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 1800 0 R +/Prev 83 0 R +/Next 179 0 R +/First 91 0 R +/Last 175 0 R +/Count -5 +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 1800 0 R +/Prev 47 0 R +/Next 87 0 R +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 67 0 R +/Prev 75 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 67 0 R +/Prev 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 67 0 R +/Next 75 0 R +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 47 0 R +/Prev 63 0 R +/First 71 0 R +/Last 79 0 R +/Count -3 +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 47 0 R +/Prev 59 0 R +/Next 67 0 R +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 47 0 R +/Prev 55 0 R +/Next 63 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 47 0 R +/Prev 51 0 R +/Next 59 0 R +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 47 0 R +/Next 55 0 R +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 1800 0 R +/Prev 23 0 R +/Next 83 0 R +/First 51 0 R +/Last 67 0 R +/Count -5 +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 23 0 R +/Prev 39 0 R +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 23 0 R +/Prev 35 0 R +/Next 43 0 R +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 23 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 23 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 1800 0 R +/Prev 7 0 R +/Next 47 0 R +/First 27 0 R +/Last 43 0 R +/Count -5 +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 7 0 R +/Prev 15 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 7 0 R +/Prev 11 0 R +/Next 19 0 R +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 7 0 R +/Next 15 0 R +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 1800 0 R +/Next 23 0 R +/First 11 0 R +/Last 19 0 R +/Count -3 +>> endobj +1801 0 obj << +/Names [(CodingSuggestions) 1224 0 R (Doc-Start) 874 0 R (Item.1) 1170 0 R (Item.10) 1193 0 R (Item.100) 1441 0 R (Item.101) 1442 0 R (Item.102) 1443 0 R (Item.103) 1444 0 R (Item.104) 1445 0 R (Item.105) 1673 0 R (Item.106) 1674 0 R (Item.107) 1675 0 R (Item.108) 1676 0 R (Item.109) 1677 0 R (Item.11) 1194 0 R (Item.110) 1678 0 R (Item.111) 1683 0 R (Item.112) 1684 0 R (Item.12) 1195 0 R (Item.13) 1196 0 R (Item.14) 1213 0 R (Item.15) 1214 0 R (Item.16) 1215 0 R (Item.17) 1227 0 R (Item.18) 1228 0 R (Item.19) 1229 0 R (Item.2) 1171 0 R (Item.20) 1230 0 R (Item.21) 1231 0 R (Item.22) 1232 0 R (Item.23) 1233 0 R (Item.24) 1234 0 R (Item.25) 1239 0 R (Item.26) 1240 0 R (Item.27) 1241 0 R (Item.28) 1242 0 R (Item.29) 1243 0 R (Item.3) 1172 0 R (Item.30) 1244 0 R (Item.31) 1245 0 R (Item.32) 1246 0 R (Item.33) 1247 0 R (Item.34) 1248 0 R (Item.35) 1249 0 R (Item.36) 1250 0 R (Item.37) 1251 0 R (Item.38) 1252 0 R (Item.39) 1253 0 R (Item.4) 1175 0 R (Item.40) 1254 0 R (Item.41) 1255 0 R (Item.42) 1263 0 R (Item.43) 1264 0 R (Item.44) 1265 0 R (Item.45) 1266 0 R (Item.46) 1267 0 R (Item.47) 1268 0 R (Item.48) 1269 0 R (Item.49) 1270 0 R (Item.5) 1176 0 R (Item.50) 1275 0 R (Item.51) 1276 0 R (Item.52) 1277 0 R (Item.53) 1301 0 R (Item.54) 1302 0 R (Item.55) 1303 0 R (Item.56) 1304 0 R (Item.57) 1305 0 R (Item.58) 1306 0 R (Item.59) 1307 0 R (Item.6) 1177 0 R (Item.60) 1308 0 R (Item.61) 1313 0 R (Item.62) 1314 0 R (Item.63) 1315 0 R (Item.64) 1316 0 R (Item.65) 1317 0 R (Item.66) 1318 0 R (Item.67) 1320 0 R (Item.68) 1321 0 R (Item.69) 1322 0 R (Item.7) 1178 0 R (Item.70) 1328 0 R (Item.71) 1329 0 R (Item.72) 1330 0 R (Item.73) 1331 0 R (Item.74) 1332 0 R (Item.75) 1333 0 R (Item.76) 1334 0 R (Item.77) 1335 0 R (Item.78) 1336 0 R (Item.79) 1337 0 R (Item.8) 1183 0 R (Item.80) 1344 0 R (Item.81) 1345 0 R (Item.82) 1346 0 R (Item.83) 1347 0 R (Item.84) 1348 0 R (Item.85) 1349 0 R (Item.86) 1350 0 R (Item.87) 1352 0 R (Item.88) 1353 0 R (Item.89) 1354 0 R (Item.9) 1184 0 R (Item.90) 1355 0 R (Item.91) 1367 0 R (Item.92) 1368 0 R (Item.93) 1369 0 R (Item.94) 1370 0 R (Item.95) 1428 0 R (Item.96) 1429 0 R (Item.97) 1430 0 R (Item.98) 1431 0 R (Item.99) 1432 0 R (Packaging) 1776 0 R (SMBPASSWDFILEFORMAT) 1744 0 R (architecture) 1168 0 R (chapter*.4) 909 0 R (chapter.1) 6 0 R (chapter.10) 718 0 R (chapter.11) 742 0 R (chapter.12) 750 0 R (chapter.13) 802 0 R (chapter.14) 818 0 R (chapter.15) 846 0 R (chapter.16) 858 0 R (chapter.2) 22 0 R (chapter.3) 46 0 R (chapter.4) 82 0 R (chapter.5) 86 0 R (chapter.6) 178 0 R (chapter.7) 206 0 R (chapter.8) 246 0 R (chapter.9) 250 0 R (debug) 1191 0 R (id2733755) 1192 0 R (id2733820) 1154 0 R (id2733904) 1155 0 R (id2733935) 1160 0 R (id2733972) 1201 0 R (id2734187) 1185 0 R (id2734254) 1186 0 R (id2734448) 1207 0 R (id2734494) 1208 0 R (id2734600) 1216 0 R (id2734608) 1217 0 R (id2734627) 1218 0 R (id2734650) 1219 0 R (id2734703) 1169 0 R (id2786615) 1173 0 R (id2786652) 1174 0 R (id2800686) 1261 0 R (id2800712) 1262 0 R (id2800990) 1351 0 R (id2801045) 1343 0 R (id2801174) 1278 0 R (id2801187) 1279 0 R (id2801201) 1280 0 R (id2801215) 1281 0 R (id2801228) 1282 0 R (id2801244) 1283 0 R (id2801258) 1284 0 R (id2801273) 1285 0 R (id2801287) 1286 0 R (id2801302) 1287 0 R (id2801316) 1288 0 R (id2801330) 1294 0 R (id2801345) 1295 0 R (id2801359) 1296 0 R (id2801374) 1297 0 R (id2801389) 1298 0 R (id2801404) 1299 0 R (id2801439) 1300 0 R (id2801591) 1319 0 R (id2801677) 1327 0 R (id2801816) 1380 0 R (id2801840) 1385 0 R (id2801877) 1378 0 R (id2801899) 1379 0 R (id2801946) 1356 0 R (id2802010) 1361 0 R (id2802109) 1366 0 R (id2802179) 1371 0 R (id2802404) 1386 0 R (id2802466) 1387 0 R (id2802496) 1392 0 R (id2802521) 1393 0 R (id2802567) 1394 0 R (id2802753) 1420 0 R (id2802908) 1668 0 R (id2802951) 1666 0 R (id2802967) 1667 0 R (id2803176) 1437 0 R (id2803211) 1438 0 R (id2803249) 1439 0 R (id2803257) 1440 0 R (id2803333) 1450 0 R (id2803340) 1451 0 R (id2803415) 1452 0 R (id2803546) 1453 0 R (id2803553) 1454 0 R (id2803565) 1455 0 R (id2803576) 1456 0 R (id2803589) 1457 0 R (id2803602) 1462 0 R (id2803695) 1463 0 R (id2803709) 1464 0 R (id2803765) 1465 0 R (id2803808) 1466 0 R (id2803836) 1467 0 R (id2803878) 1468 0 R (id2803964) 1473 0 R (id2804058) 1474 0 R (id2804085) 1475 0 R (id2804172) 1476 0 R (id2804242) 1477 0 R (id2804342) 1482 0 R (id2804420) 1483 0 R (id2804461) 1484 0 R (id2804543) 1485 0 R (id2804596) 1486 0 R (id2804767) 1492 0 R (id2804871) 1493 0 R (id2804910) 1494 0 R (id2805054) 1499 0 R (id2805167) 1500 0 R (id2805730) 1505 0 R (id2805825) 1506 0 R (id2805868) 1511 0 R (id2806037) 1512 0 R (id2806504) 1517 0 R (id2806516) 1518 0 R (id2806618) 1523 0 R (id2806809) 1524 0 R (id2806942) 1530 0 R (id2806969) 1531 0 R (id2807008) 1532 0 R (id2807149) 1533 0 R (id2807189) 1534 0 R (id2807339) 1539 0 R (id2807412) 1540 0 R (id2807492) 1541 0 R (id2807538) 1542 0 R (id2807718) 1547 0 R (id2807884) 1548 0 R (id2807897) 1553 0 R (id2807967) 1554 0 R (id2808010) 1555 0 R (id2808024) 1556 0 R (id2808063) 1557 0 R (id2808117) 1558 0 R (id2808125) 1559 0 R (id2808137) 1560 0 R (id2808209) 1565 0 R (id2808216) 1566 0 R (id2808229) 1567 0 R (id2808319) 1568 0 R (id2808326) 1569 0 R (id2808353) 1570 0 R (id2808385) 1571 0 R (id2808399) 1572 0 R (id2808498) 1577 0 R (id2808595) 1578 0 R (id2808610) 1579 0 R (id2808723) 1580 0 R (id2808821) 1586 0 R (id2808983) 1587 0 R (id2809015) 1588 0 R (id2809085) 1589 0 R (id2809118) 1594 0 R (id2809149) 1595 0 R (id2809218) 1596 0 R (id2809265) 1597 0 R (id2809305) 1598 0 R (id2809347) 1599 0 R (id2809381) 1600 0 R (id2809396) 1605 0 R (id2809423) 1606 0 R (id2809495) 1607 0 R (id2809510) 1608 0 R (id2809537) 1609 0 R (id2809587) 1610 0 R (id2809604) 1615 0 R (id2809619) 1616 0 R (id2809745) 1617 0 R (id2809866) 1618 0 R (id2809894) 1619 0 R (id2810078) 1624 0 R (id2810192) 1625 0 R (id2810238) 1626 0 R (id2810259) 1627 0 R (id2810384) 1632 0 R (id2810458) 1633 0 R (id2810472) 1634 0 R (id2810513) 1635 0 R (id2810575) 1636 0 R (id2810583) 1637 0 R (id2810745) 1643 0 R (id2810826) 1644 0 R (id2810875) 1649 0 R (id2810915) 1650 0 R (id2810923) 1651 0 R (id2811049) 1652 0 R (id2811230) 1657 0 R (id2811245) 1658 0 R (id2811293) 1659 0 R (id2811353) 1660 0 R (id2811596) 1701 0 R (id2811836) 1685 0 R (id2811849) 1686 0 R (id2812158) 1738 0 R (id2812288) 1737 0 R (id2812322) 1707 0 R (id2812453) 1712 0 R (id2812488) 1713 0 R (id2812557) 1714 0 R (id2812564) 1715 0 R (id2812580) 1716 0 R (id2812608) 1717 0 R (id2812630) 1722 0 R (id2812637) 1723 0 R (id2812655) 1724 0 R (id2812694) 1725 0 R (id2812785) 1731 0 R (id2812874) 1743 0 R (id2813064) 1755 0 R (id2813097) 1756 0 R (id2813131) 1770 0 R (id2813150) 1771 0 R (id2813325) 1754 0 R (id2813533) 1757 0 R (id2813561) 1762 0 R (id2813621) 1763 0 R (id2813840) 1777 0 R (id2813873) 1778 0 R (internals) 1260 0 R (modules) 1753 0 R (netbios) 1153 0 R (ntdomain) 1419 0 R (page.1) 873 0 R (page.10) 1167 0 R (page.11) 1182 0 R (page.12) 1190 0 R (page.13) 1200 0 R (page.14) 1206 0 R (page.15) 1212 0 R (page.16) 1223 0 R (page.17) 1238 0 R (page.18) 1259 0 R (page.19) 1274 0 R (page.2) 885 0 R (page.20) 1293 0 R (page.21) 1312 0 R (page.22) 1326 0 R (page.23) 1341 0 R (page.24) 1360 0 R (page.25) 1365 0 R (page.26) 1376 0 R (page.27) 1384 0 R (page.28) 1391 0 R (page.29) 1398 0 R (page.3) 908 0 R (page.30) 1402 0 R (page.31) 1413 0 R (page.32) 1418 0 R (page.33) 1436 0 R (page.34) 1449 0 R (page.35) 1461 0 R (page.36) 1472 0 R (page.37) 1481 0 R (page.38) 1491 0 R (page.39) 1498 0 R (page.4) 953 0 R (page.40) 1504 0 R (page.41) 1510 0 R (page.42) 1516 0 R (page.43) 1522 0 R (page.44) 1529 0 R (page.45) 1538 0 R (page.46) 1546 0 R (page.47) 1552 0 R (page.48) 1564 0 R (page.49) 1576 0 R (page.5) 1009 0 R (page.50) 1585 0 R (page.51) 1593 0 R (page.52) 1604 0 R (page.53) 1614 0 R (page.54) 1623 0 R (page.55) 1631 0 R (page.56) 1642 0 R (page.57) 1648 0 R (page.58) 1656 0 R (page.59) 1664 0 R (page.6) 1065 0 R (page.60) 1672 0 R (page.61) 1682 0 R (page.62) 1691 0 R (page.63) 1695 0 R (page.64) 1699 0 R (page.65) 1705 0 R (page.66) 1711 0 R (page.67) 1721 0 R (page.68) 1730 0 R (page.69) 1735 0 R (page.7) 1122 0 R (page.70) 1742 0 R (page.71) 1748 0 R (page.72) 1752 0 R (page.73) 1761 0 R (page.74) 1768 0 R (page.75) 1775 0 R (page.8) 1152 0 R (page.9) 1159 0 R (parsing) 1342 0 R (printing) 1665 0 R (pwencrypt) 1736 0 R (rpc-plugin) 1769 0 R (sam) 1706 0 R (section*.1) 889 0 R (section*.2) 896 0 R (section*.3) 903 0 R (section.1.1) 10 0 R (section.1.2) 14 0 R (section.1.3) 18 0 R (section.10.1) 722 0 R (section.10.2) 726 0 R (section.10.3) 730 0 R (section.10.4) 734 0 R (section.10.5) 738 0 R (section.11.1) 746 0 R (section.12.1) 754 0 R (section.12.2) 758 0 R (section.12.3) 762 0 R (section.12.4) 766 0 R (section.12.5) 782 0 R (section.12.6) 794 0 R (section.12.7) 798 0 R (section.13.1) 806 0 R (section.13.2) 810 0 R (section.13.3) 814 0 R (section.14.1) 822 0 R (section.14.2) 826 0 R (section.14.3) 838 0 R (section.15.1) 850 0 R (section.15.2) 854 0 R (section.16.1) 862 0 R (section.16.2) 866 0 R (section.2.1) 26 0 R (section.2.2) 30 0 R (section.2.3) 34 0 R (section.2.4) 38 0 R (section.2.5) 42 0 R (section.3.1) 50 0 R (section.3.2) 54 0 R (section.3.3) 58 0 R (section.3.4) 62 0 R (section.3.5) 66 0 R (section.5.1) 90 0 R (section.5.2) 94 0 R (section.5.3) 98 0 R (section.5.4) 162 0 R (section.5.5) 174 0 R (section.6.1) 182 0 R (section.6.2) 198 0 R (section.7.1) 210 0 R (section.7.2) 214 0 R (section.7.3) 218 0 R (section.7.4) 222 0 R (section.7.5) 226 0 R (section.7.6) 230 0 R (section.7.7) 234 0 R (section.7.8) 238 0 R (section.7.9) 242 0 R (section.9.1) 254 0 R (section.9.2) 266 0 R (section.9.3) 410 0 R (section.9.4) 550 0 R (section.9.5) 614 0 R (section.9.6) 642 0 R (section.9.7) 670 0 R (section.9.8) 686 0 R (subsection.12.4.1) 770 0 R (subsection.12.4.2) 774 0 R (subsection.12.4.3) 778 0 R (subsection.12.5.1) 786 0 R (subsection.12.5.2) 790 0 R (subsection.14.2.1) 830 0 R (subsection.14.2.2) 834 0 R (subsection.14.3.1) 842 0 R (subsection.3.5.1) 70 0 R (subsection.3.5.2) 74 0 R (subsection.3.5.3) 78 0 R (subsection.5.3.1) 102 0 R (subsection.5.3.10) 138 0 R (subsection.5.3.11) 142 0 R (subsection.5.3.12) 146 0 R (subsection.5.3.13) 150 0 R (subsection.5.3.14) 154 0 R (subsection.5.3.15) 158 0 R (subsection.5.3.2) 106 0 R (subsection.5.3.3) 110 0 R (subsection.5.3.4) 114 0 R (subsection.5.3.5) 118 0 R (subsection.5.3.6) 122 0 R (subsection.5.3.7) 126 0 R (subsection.5.3.8) 130 0 R (subsection.5.3.9) 134 0 R (subsection.5.4.1) 166 0 R (subsection.5.4.2) 170 0 R (subsection.6.1.1) 186 0 R (subsection.6.1.2) 190 0 R (subsection.6.1.3) 194 0 R (subsection.6.2.1) 202 0 R (subsection.9.1.1) 258 0 R (subsection.9.1.2) 262 0 R (subsection.9.2.1) 270 0 R (subsection.9.2.2) 274 0 R (subsection.9.2.3) 286 0 R (subsection.9.3.1) 414 0 R (subsection.9.3.10) 514 0 R (subsection.9.3.11) 526 0 R (subsection.9.3.12) 538 0 R (subsection.9.3.2) 418 0 R (subsection.9.3.3) 454 0 R (subsection.9.3.4) 458 0 R (subsection.9.3.5) 462 0 R (subsection.9.3.6) 466 0 R (subsection.9.3.7) 478 0 R (subsection.9.3.8) 490 0 R (subsection.9.3.9) 502 0 R (subsection.9.4.1) 554 0 R (subsection.9.4.2) 566 0 R (subsection.9.4.3) 578 0 R (subsection.9.4.4) 590 0 R (subsection.9.4.5) 602 0 R (subsection.9.5.1) 618 0 R (subsection.9.5.2) 630 0 R (subsection.9.6.1) 646 0 R (subsection.9.6.2) 658 0 R (subsection.9.7.1) 674 0 R (subsection.9.7.2) 678 0 R (subsection.9.7.3) 682 0 R (subsection.9.8.1) 690 0 R (subsection.9.8.2) 702 0 R (subsubsection.9.2.2.1) 278 0 R (subsubsection.9.2.2.2) 282 0 R (subsubsection.9.2.3.1) 290 0 R (subsubsection.9.2.3.10) 326 0 R (subsubsection.9.2.3.11) 330 0 R (subsubsection.9.2.3.12) 334 0 R (subsubsection.9.2.3.13) 338 0 R (subsubsection.9.2.3.14) 342 0 R (subsubsection.9.2.3.15) 346 0 R (subsubsection.9.2.3.16) 350 0 R (subsubsection.9.2.3.17) 354 0 R (subsubsection.9.2.3.18) 358 0 R (subsubsection.9.2.3.19) 362 0 R (subsubsection.9.2.3.2) 294 0 R (subsubsection.9.2.3.20) 366 0 R (subsubsection.9.2.3.21) 370 0 R (subsubsection.9.2.3.22) 374 0 R (subsubsection.9.2.3.23) 378 0 R (subsubsection.9.2.3.24) 382 0 R (subsubsection.9.2.3.25) 386 0 R (subsubsection.9.2.3.26) 390 0 R (subsubsection.9.2.3.27) 394 0 R (subsubsection.9.2.3.28) 398 0 R (subsubsection.9.2.3.29) 402 0 R (subsubsection.9.2.3.3) 298 0 R (subsubsection.9.2.3.30) 406 0 R (subsubsection.9.2.3.4) 302 0 R (subsubsection.9.2.3.5) 306 0 R (subsubsection.9.2.3.6) 310 0 R (subsubsection.9.2.3.7) 314 0 R (subsubsection.9.2.3.8) 318 0 R (subsubsection.9.2.3.9) 322 0 R (subsubsection.9.3.10.1) 518 0 R (subsubsection.9.3.10.2) 522 0 R (subsubsection.9.3.11.1) 530 0 R (subsubsection.9.3.11.2) 534 0 R (subsubsection.9.3.12.1) 542 0 R (subsubsection.9.3.12.2) 546 0 R (subsubsection.9.3.2.1) 422 0 R (subsubsection.9.3.2.2) 426 0 R (subsubsection.9.3.2.3) 430 0 R (subsubsection.9.3.2.4) 434 0 R (subsubsection.9.3.2.5) 438 0 R (subsubsection.9.3.2.6) 442 0 R (subsubsection.9.3.2.7) 446 0 R (subsubsection.9.3.2.8) 450 0 R (subsubsection.9.3.6.1) 470 0 R (subsubsection.9.3.6.2) 474 0 R (subsubsection.9.3.7.1) 482 0 R (subsubsection.9.3.7.2) 486 0 R (subsubsection.9.3.8.1) 494 0 R (subsubsection.9.3.8.2) 498 0 R (subsubsection.9.3.9.1) 506 0 R (subsubsection.9.3.9.2) 510 0 R (subsubsection.9.4.1.1) 558 0 R (subsubsection.9.4.1.2) 562 0 R (subsubsection.9.4.2.1) 570 0 R (subsubsection.9.4.2.2) 574 0 R (subsubsection.9.4.3.1) 582 0 R (subsubsection.9.4.3.2) 586 0 R (subsubsection.9.4.4.1) 594 0 R (subsubsection.9.4.4.2) 598 0 R (subsubsection.9.4.5.1) 606 0 R (subsubsection.9.4.5.2) 610 0 R (subsubsection.9.5.1.1) 622 0 R (subsubsection.9.5.1.2) 626 0 R (subsubsection.9.5.2.1) 634 0 R (subsubsection.9.5.2.2) 638 0 R (subsubsection.9.6.1.1) 650 0 R (subsubsection.9.6.1.2) 654 0 R (subsubsection.9.6.2.1) 662 0 R (subsubsection.9.6.2.2) 666 0 R (subsubsection.9.8.1.1) 694 0 R (subsubsection.9.8.1.2) 698 0 R (subsubsection.9.8.2.1) 706 0 R (subsubsection.9.8.2.2) 710 0 R (subsubsection.9.8.2.3) 714 0 R (tracing) 1403 0 R (unix-smb) 1377 0 R (wins) 1700 0 R] +/Limits [(CodingSuggestions) (wins)] +>> endobj +1802 0 obj << +/Kids [1801 0 R] +>> endobj +1803 0 obj << +/Dests 1802 0 R +>> endobj +1804 0 obj << +/Type /Catalog +/Pages 1799 0 R +/Outlines 1800 0 R +/Names 1803 0 R +/PageMode /UseOutlines /URI<> /ViewerPreferences<<>> +/OpenAction 869 0 R +/PTEX.Fullbanner (This is pdfTeX, Version 3.14159-1.10a) +>> endobj +1805 0 obj << +/Producer (pdfTeX-1.10a) +/Author()/Title()/Subject()/Creator(LaTeX with hyperref package)/Producer(pdfTeX-1.10a)/Keywords() +/Creator (TeX) +/CreationDate (D:20030501010600) +>> endobj xref -0 871 -0000000000 65535 f -0000000015 00000 n -0000000242 00000 n -0000001808 00000 n -0000001882 00000 n -0000001961 00000 n -0000002039 00000 n -0000002116 00000 n -0000002195 00000 n -0000002278 00000 n -0000002354 00000 n -0000002436 00000 n -0000002521 00000 n -0000002580 00000 n -0000002681 00000 n -0000002783 00000 n -0000002884 00000 n -0000002985 00000 n -0000003087 00000 n -0000003189 00000 n -0000003291 00000 n -0000003392 00000 n -0000003494 00000 n -0000003596 00000 n -0000003698 00000 n -0000003800 00000 n -0000003902 00000 n -0000004003 00000 n -0000004105 00000 n -0000004207 00000 n -0000004309 00000 n -0000004411 00000 n -0000004513 00000 n -0000004615 00000 n -0000004717 00000 n -0000004819 00000 n +0 1806 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000074011 00000 n +0000409878 00000 n +0000000054 00000 n +0000000130 00000 n +0000074134 00000 n +0000409806 00000 n +0000000177 00000 n +0000000207 00000 n +0000074258 00000 n +0000409720 00000 n +0000000255 00000 n +0000000295 00000 n +0000077595 00000 n +0000409647 00000 n +0000000343 00000 n +0000000378 00000 n +0000080860 00000 n +0000409522 00000 n +0000000424 00000 n +0000000463 00000 n +0000080984 00000 n +0000409448 00000 n +0000000511 00000 n +0000000546 00000 n +0000081297 00000 n +0000409361 00000 n +0000000594 00000 n +0000000641 00000 n +0000081420 00000 n +0000409274 00000 n +0000000689 00000 n +0000000726 00000 n +0000085541 00000 n +0000409187 00000 n +0000000774 00000 n +0000000811 00000 n +0000085665 00000 n +0000409113 00000 n +0000000859 00000 n +0000000893 00000 n +0000087973 00000 n +0000408987 00000 n +0000000939 00000 n +0000000982 00000 n +0000088097 00000 n +0000408913 00000 n +0000001030 00000 n +0000001070 00000 n +0000090917 00000 n +0000408826 00000 n +0000001118 00000 n +0000001160 00000 n +0000093073 00000 n +0000408739 00000 n +0000001208 00000 n +0000001253 00000 n +0000093196 00000 n +0000408652 00000 n +0000001301 00000 n +0000001346 00000 n +0000096049 00000 n +0000408541 00000 n +0000001394 00000 n +0000001430 00000 n +0000096173 00000 n +0000408467 00000 n +0000001483 00000 n +0000001519 00000 n +0000096297 00000 n +0000408380 00000 n +0000001572 00000 n +0000001607 00000 n +0000096421 00000 n +0000408306 00000 n +0000001660 00000 n +0000001712 00000 n +0000100587 00000 n +0000408217 00000 n +0000001758 00000 n +0000001797 00000 n +0000109575 00000 n +0000408089 00000 n +0000001843 00000 n +0000001879 00000 n +0000109699 00000 n +0000408015 00000 n +0000001927 00000 n +0000001968 00000 n +0000109822 00000 n +0000407928 00000 n +0000002016 00000 n +0000002056 00000 n +0000113070 00000 n +0000407799 00000 n +0000002104 00000 n +0000002149 00000 n +0000113194 00000 n +0000407721 00000 n +0000002203 00000 n +0000002244 00000 n +0000113319 00000 n +0000407629 00000 n +0000002298 00000 n +0000002339 00000 n +0000113443 00000 n +0000407537 00000 n +0000002393 00000 n +0000002439 00000 n +0000113568 00000 n +0000407445 00000 n +0000002493 00000 n +0000002534 00000 n +0000113693 00000 n +0000407353 00000 n +0000002588 00000 n +0000002629 00000 n +0000113818 00000 n +0000407261 00000 n +0000002683 00000 n +0000002725 00000 n +0000113942 00000 n +0000407169 00000 n +0000002779 00000 n +0000002821 00000 n +0000114067 00000 n +0000407077 00000 n +0000002875 00000 n +0000002921 00000 n +0000114192 00000 n +0000406985 00000 n +0000002975 00000 n +0000003021 00000 n +0000114317 00000 n +0000406893 00000 n +0000003076 00000 n +0000003124 00000 n +0000116740 00000 n +0000406801 00000 n +0000003179 00000 n +0000003227 00000 n +0000116864 00000 n +0000406709 00000 n +0000003282 00000 n +0000003325 00000 n +0000116989 00000 n +0000406617 00000 n +0000003380 00000 n +0000003423 00000 n +0000117114 00000 n +0000406525 00000 n +0000003478 00000 n +0000003526 00000 n +0000117239 00000 n +0000406447 00000 n +0000003581 00000 n +0000003629 00000 n +0000117364 00000 n +0000406317 00000 n +0000003678 00000 n +0000003723 00000 n +0000117489 00000 n +0000406238 00000 n +0000003777 00000 n +0000003813 00000 n +0000121927 00000 n +0000406159 00000 n +0000003867 00000 n +0000003905 00000 n +0000123591 00000 n +0000406081 00000 n +0000003954 00000 n +0000003998 00000 n +0000126860 00000 n +0000405949 00000 n +0000004045 00000 n +0000004084 00000 n +0000126985 00000 n +0000405831 00000 n +0000004133 00000 n +0000004173 00000 n +0000127549 00000 n +0000405752 00000 n +0000004227 00000 n +0000004275 00000 n +0000127926 00000 n +0000405659 00000 n +0000004329 00000 n +0000004384 00000 n +0000129713 00000 n +0000405580 00000 n +0000004438 00000 n +0000004488 00000 n +0000131602 00000 n +0000405462 00000 n +0000004537 00000 n +0000004567 00000 n +0000131978 00000 n +0000405397 00000 n +0000004621 00000 n +0000004661 00000 n +0000135764 00000 n +0000405264 00000 n +0000004708 00000 n +0000004753 00000 n +0000135889 00000 n +0000405185 00000 n +0000004802 00000 n +0000004838 00000 n +0000136014 00000 n +0000405092 00000 n +0000004887 00000 n 0000004920 00000 n -0000005021 00000 n -0000005123 00000 n -0000005225 00000 n -0000005327 00000 n -0000005429 00000 n -0000005531 00000 n -0000005633 00000 n -0000005735 00000 n -0000005837 00000 n -0000005939 00000 n -0000006041 00000 n -0000006143 00000 n -0000006245 00000 n -0000006347 00000 n -0000006449 00000 n -0000006551 00000 n -0000006652 00000 n -0000006752 00000 n -0000006852 00000 n -0000007162 00000 n -0000007263 00000 n -0000007365 00000 n -0000007467 00000 n -0000007569 00000 n -0000007671 00000 n -0000007772 00000 n -0000007874 00000 n -0000007976 00000 n -0000008078 00000 n -0000008180 00000 n -0000008282 00000 n -0000008384 00000 n -0000008485 00000 n -0000008587 00000 n -0000008689 00000 n -0000008791 00000 n -0000008893 00000 n -0000008995 00000 n -0000009097 00000 n -0000009199 00000 n -0000009301 00000 n -0000009403 00000 n -0000009504 00000 n -0000009605 00000 n -0000009707 00000 n -0000009809 00000 n -0000009911 00000 n -0000010013 00000 n -0000010115 00000 n -0000010217 00000 n -0000010319 00000 n -0000010421 00000 n -0000010523 00000 n -0000010625 00000 n -0000010727 00000 n -0000010829 00000 n -0000010931 00000 n -0000011033 00000 n -0000011135 00000 n -0000011237 00000 n -0000011339 00000 n -0000011440 00000 n -0000011540 00000 n -0000011640 00000 n -0000011965 00000 n -0000012067 00000 n -0000012170 00000 n -0000012273 00000 n -0000012376 00000 n -0000012479 00000 n -0000012582 00000 n -0000012685 00000 n -0000012788 00000 n -0000012891 00000 n -0000012994 00000 n -0000013097 00000 n -0000013200 00000 n -0000013303 00000 n -0000013406 00000 n -0000013509 00000 n -0000013612 00000 n -0000013715 00000 n -0000013818 00000 n -0000013921 00000 n -0000014024 00000 n -0000014126 00000 n -0000014229 00000 n -0000014332 00000 n -0000014435 00000 n -0000014538 00000 n -0000014641 00000 n -0000014743 00000 n -0000014846 00000 n -0000014948 00000 n -0000015051 00000 n -0000015154 00000 n -0000015257 00000 n -0000015360 00000 n -0000015463 00000 n -0000015566 00000 n -0000015669 00000 n -0000015772 00000 n -0000015875 00000 n -0000015978 00000 n -0000016081 00000 n -0000016184 00000 n -0000016285 00000 n -0000016386 00000 n -0000016487 00000 n -0000016856 00000 n -0000016958 00000 n -0000017061 00000 n -0000017163 00000 n -0000017266 00000 n -0000017369 00000 n -0000017472 00000 n -0000017575 00000 n -0000017678 00000 n -0000017781 00000 n -0000017883 00000 n -0000017986 00000 n -0000018089 00000 n -0000018191 00000 n -0000018294 00000 n -0000018397 00000 n -0000018534 00000 n -0000018589 00000 n -0000018676 00000 n -0000018731 00000 n -0000018818 00000 n -0000018885 00000 n -0000018971 00000 n -0000019073 00000 n -0000019176 00000 n -0000019279 00000 n -0000019382 00000 n -0000019484 00000 n -0000019587 00000 n -0000019690 00000 n -0000019793 00000 n -0000019896 00000 n -0000019999 00000 n -0000020101 00000 n -0000020204 00000 n -0000020307 00000 n -0000020410 00000 n -0000020513 00000 n -0000020616 00000 n -0000020719 00000 n -0000020822 00000 n -0000020925 00000 n -0000021027 00000 n -0000021129 00000 n -0000021232 00000 n -0000021335 00000 n -0000021438 00000 n -0000021541 00000 n -0000021644 00000 n -0000021747 00000 n -0000021850 00000 n -0000021953 00000 n -0000022056 00000 n -0000022159 00000 n -0000022262 00000 n -0000022365 00000 n -0000022467 00000 n -0000022568 00000 n -0000022669 00000 n -0000022998 00000 n -0000023101 00000 n -0000023204 00000 n -0000023307 00000 n -0000023410 00000 n -0000023513 00000 n -0000023616 00000 n -0000023719 00000 n -0000023821 00000 n -0000023924 00000 n -0000024027 00000 n -0000024130 00000 n -0000024233 00000 n -0000024336 00000 n -0000024439 00000 n -0000024541 00000 n -0000024644 00000 n -0000024747 00000 n -0000024850 00000 n -0000024953 00000 n -0000025056 00000 n -0000025159 00000 n -0000025262 00000 n -0000025365 00000 n -0000025468 00000 n -0000025570 00000 n -0000025672 00000 n -0000025775 00000 n -0000025878 00000 n -0000025981 00000 n -0000026084 00000 n -0000026187 00000 n -0000026290 00000 n -0000026393 00000 n -0000026496 00000 n -0000026599 00000 n -0000026702 00000 n -0000026805 00000 n -0000026908 00000 n -0000027011 00000 n -0000027114 00000 n -0000027217 00000 n -0000027320 00000 n -0000027423 00000 n -0000027526 00000 n -0000027629 00000 n -0000027732 00000 n -0000027835 00000 n -0000027938 00000 n -0000028040 00000 n -0000028141 00000 n -0000028242 00000 n -0000028667 00000 n -0000028770 00000 n -0000028873 00000 n -0000028976 00000 n -0000029079 00000 n -0000029182 00000 n -0000029285 00000 n -0000029388 00000 n -0000029491 00000 n -0000029594 00000 n -0000029697 00000 n -0000029800 00000 n -0000029903 00000 n -0000030006 00000 n -0000030109 00000 n -0000030211 00000 n -0000030314 00000 n -0000030417 00000 n -0000030520 00000 n -0000030623 00000 n -0000030726 00000 n -0000030828 00000 n -0000030931 00000 n -0000031033 00000 n -0000031136 00000 n -0000031239 00000 n -0000031342 00000 n -0000031445 00000 n -0000031548 00000 n -0000031651 00000 n -0000031754 00000 n -0000031857 00000 n -0000031960 00000 n -0000032063 00000 n -0000032166 00000 n -0000032269 00000 n -0000032371 00000 n -0000032474 00000 n -0000032577 00000 n -0000032680 00000 n -0000032782 00000 n -0000032885 00000 n -0000032988 00000 n -0000033091 00000 n -0000033194 00000 n -0000033297 00000 n -0000033400 00000 n -0000033502 00000 n -0000033605 00000 n -0000033707 00000 n -0000033807 00000 n -0000033908 00000 n -0000034333 00000 n -0000034436 00000 n -0000034461 00000 n -0000034545 00000 n -0000034631 00000 n -0000034705 00000 n -0000034791 00000 n -0000034824 00000 n -0000034902 00000 n -0000034989 00000 n -0000035095 00000 n -0000035181 00000 n -0000035253 00000 n -0000035339 00000 n -0000035398 00000 n -0000035485 00000 n -0000035576 00000 n -0000035662 00000 n -0000035733 00000 n -0000035819 00000 n -0000035884 00000 n -0000035918 00000 n -0000035952 00000 n -0000039512 00000 n -0000039555 00000 n -0000039598 00000 n -0000039641 00000 n -0000039684 00000 n -0000039727 00000 n -0000039770 00000 n -0000039813 00000 n -0000039856 00000 n -0000039899 00000 n -0000039942 00000 n -0000039985 00000 n -0000040028 00000 n -0000040071 00000 n -0000040114 00000 n -0000040157 00000 n -0000040200 00000 n -0000040243 00000 n -0000040286 00000 n -0000040329 00000 n -0000040372 00000 n -0000040415 00000 n -0000040458 00000 n -0000040501 00000 n -0000040544 00000 n -0000040587 00000 n -0000040630 00000 n -0000040673 00000 n -0000040716 00000 n -0000040759 00000 n -0000040802 00000 n -0000040845 00000 n -0000040888 00000 n -0000040931 00000 n -0000040974 00000 n -0000041017 00000 n -0000041060 00000 n -0000041103 00000 n -0000041146 00000 n -0000041189 00000 n -0000041232 00000 n -0000041275 00000 n -0000041318 00000 n -0000041361 00000 n -0000041404 00000 n -0000041447 00000 n -0000041490 00000 n -0000041533 00000 n -0000041576 00000 n -0000041619 00000 n -0000041662 00000 n -0000041705 00000 n -0000041748 00000 n -0000041791 00000 n -0000041834 00000 n -0000041877 00000 n -0000041920 00000 n -0000041963 00000 n -0000042006 00000 n -0000042049 00000 n -0000042092 00000 n -0000042135 00000 n -0000042178 00000 n -0000042221 00000 n -0000042264 00000 n -0000042307 00000 n -0000042350 00000 n -0000042393 00000 n -0000042436 00000 n -0000042479 00000 n -0000042522 00000 n -0000042565 00000 n -0000042608 00000 n -0000042651 00000 n -0000042694 00000 n -0000042737 00000 n -0000042780 00000 n -0000042823 00000 n -0000042866 00000 n -0000042909 00000 n -0000042952 00000 n -0000042995 00000 n -0000043038 00000 n -0000043081 00000 n -0000043124 00000 n -0000043167 00000 n -0000043210 00000 n -0000043253 00000 n -0000043296 00000 n -0000043339 00000 n -0000043382 00000 n -0000043425 00000 n -0000043468 00000 n -0000043511 00000 n -0000043554 00000 n -0000043597 00000 n -0000043640 00000 n -0000043683 00000 n -0000043726 00000 n -0000043769 00000 n -0000043812 00000 n -0000043855 00000 n -0000043898 00000 n -0000043941 00000 n -0000043984 00000 n -0000044027 00000 n -0000044070 00000 n -0000044113 00000 n -0000044156 00000 n -0000044199 00000 n -0000044242 00000 n -0000044285 00000 n -0000044328 00000 n -0000044371 00000 n -0000044414 00000 n -0000044457 00000 n -0000044500 00000 n -0000044543 00000 n -0000044586 00000 n -0000044629 00000 n -0000044672 00000 n -0000044715 00000 n -0000044758 00000 n -0000044801 00000 n -0000044844 00000 n -0000044887 00000 n -0000044930 00000 n -0000044973 00000 n -0000045016 00000 n -0000045059 00000 n -0000045102 00000 n -0000045145 00000 n -0000045188 00000 n -0000045231 00000 n -0000045274 00000 n -0000045317 00000 n -0000045360 00000 n -0000045403 00000 n -0000045446 00000 n -0000045489 00000 n -0000045532 00000 n -0000045575 00000 n -0000045618 00000 n -0000045661 00000 n -0000045704 00000 n -0000045747 00000 n -0000045790 00000 n -0000045833 00000 n -0000045876 00000 n -0000045919 00000 n -0000045962 00000 n -0000046005 00000 n -0000046048 00000 n -0000046091 00000 n -0000046134 00000 n -0000046177 00000 n -0000046220 00000 n -0000046263 00000 n -0000046306 00000 n -0000046349 00000 n -0000046392 00000 n -0000046435 00000 n -0000046478 00000 n -0000046521 00000 n -0000046564 00000 n -0000046607 00000 n -0000046650 00000 n -0000046693 00000 n -0000046736 00000 n -0000046779 00000 n -0000046822 00000 n -0000046865 00000 n -0000046908 00000 n -0000046951 00000 n -0000046994 00000 n -0000047037 00000 n -0000047080 00000 n -0000047123 00000 n -0000047166 00000 n -0000047209 00000 n -0000047252 00000 n -0000047295 00000 n -0000047338 00000 n -0000047381 00000 n -0000047424 00000 n -0000047467 00000 n -0000047510 00000 n -0000047553 00000 n -0000047596 00000 n -0000047639 00000 n -0000047682 00000 n -0000047725 00000 n -0000047768 00000 n -0000047811 00000 n -0000047854 00000 n -0000047897 00000 n -0000047940 00000 n -0000047983 00000 n -0000048026 00000 n -0000048069 00000 n -0000048112 00000 n -0000048155 00000 n -0000048198 00000 n -0000048241 00000 n -0000048284 00000 n -0000048327 00000 n -0000048370 00000 n -0000048413 00000 n -0000048456 00000 n -0000048499 00000 n -0000048542 00000 n -0000048585 00000 n -0000048628 00000 n -0000048671 00000 n -0000048714 00000 n -0000048757 00000 n -0000048800 00000 n -0000048843 00000 n -0000048886 00000 n -0000048929 00000 n -0000048972 00000 n -0000049015 00000 n -0000049750 00000 n -0000049907 00000 n -0000050074 00000 n -0000050263 00000 n -0000052866 00000 n -0000053056 00000 n -0000056162 00000 n -0000056352 00000 n -0000059894 00000 n -0000060084 00000 n -0000061357 00000 n -0000061514 00000 n -0000061743 00000 n -0000061942 00000 n -0000063751 00000 n -0000063922 00000 n -0000066005 00000 n -0000066176 00000 n -0000068463 00000 n -0000068634 00000 n -0000068890 00000 n -0000069056 00000 n -0000070701 00000 n -0000070867 00000 n -0000072409 00000 n -0000072575 00000 n -0000074309 00000 n -0000074475 00000 n -0000076211 00000 n -0000076386 00000 n -0000077652 00000 n -0000077827 00000 n -0000079038 00000 n -0000079213 00000 n -0000080460 00000 n -0000080626 00000 n -0000081536 00000 n -0000081726 00000 n -0000083690 00000 n -0000083846 00000 n -0000085623 00000 n +0000136139 00000 n +0000404999 00000 n +0000004969 00000 n +0000005007 00000 n +0000140317 00000 n +0000404906 00000 n +0000005056 00000 n +0000005089 00000 n +0000140442 00000 n +0000404813 00000 n +0000005138 00000 n +0000005169 00000 n +0000140567 00000 n +0000404720 00000 n +0000005218 00000 n +0000005252 00000 n +0000145032 00000 n +0000404627 00000 n +0000005301 00000 n +0000005338 00000 n +0000145157 00000 n +0000404534 00000 n +0000005387 00000 n +0000005423 00000 n +0000145282 00000 n +0000404455 00000 n +0000005472 00000 n +0000005515 00000 n +0000149905 00000 n +0000404361 00000 n +0000005562 00000 n +0000005610 00000 n +0000156487 00000 n +0000404228 00000 n +0000005657 00000 n +0000005694 00000 n +0000156612 00000 n +0000404110 00000 n +0000005743 00000 n +0000005779 00000 n +0000159990 00000 n +0000404031 00000 n +0000005833 00000 n +0000005866 00000 n +0000160115 00000 n +0000403952 00000 n +0000005920 00000 n +0000005953 00000 n +0000160240 00000 n +0000403820 00000 n +0000006002 00000 n +0000006046 00000 n +0000160364 00000 n +0000403741 00000 n +0000006100 00000 n +0000006131 00000 n +0000162351 00000 n +0000403609 00000 n +0000006185 00000 n +0000006223 00000 n +0000162476 00000 n +0000403530 00000 n +0000006282 00000 n +0000006327 00000 n +0000162601 00000 n +0000403451 00000 n +0000006386 00000 n +0000006431 00000 n +0000162726 00000 n +0000403332 00000 n +0000006485 00000 n +0000006521 00000 n +0000162851 00000 n +0000403253 00000 n +0000006580 00000 n +0000006614 00000 n +0000162976 00000 n +0000403160 00000 n +0000006673 00000 n +0000006705 00000 n +0000163100 00000 n +0000403067 00000 n +0000006764 00000 n +0000006797 00000 n +0000163225 00000 n +0000402974 00000 n +0000006856 00000 n +0000006890 00000 n +0000165031 00000 n +0000402881 00000 n +0000006949 00000 n +0000007012 00000 n +0000165156 00000 n +0000402788 00000 n +0000007071 00000 n +0000007113 00000 n +0000165281 00000 n +0000402695 00000 n +0000007172 00000 n +0000007232 00000 n +0000165406 00000 n +0000402602 00000 n +0000007291 00000 n +0000007372 00000 n +0000165531 00000 n +0000402509 00000 n +0000007431 00000 n +0000007484 00000 n +0000165656 00000 n +0000402416 00000 n +0000007544 00000 n +0000007613 00000 n +0000165781 00000 n +0000402323 00000 n +0000007673 00000 n +0000007736 00000 n +0000168275 00000 n +0000402230 00000 n +0000007796 00000 n +0000007858 00000 n +0000168400 00000 n +0000402137 00000 n +0000007918 00000 n +0000007979 00000 n +0000168525 00000 n +0000402044 00000 n +0000008039 00000 n +0000008128 00000 n +0000168650 00000 n +0000401951 00000 n +0000008188 00000 n +0000008252 00000 n +0000168775 00000 n +0000401858 00000 n +0000008312 00000 n +0000008390 00000 n +0000171173 00000 n +0000401765 00000 n +0000008450 00000 n +0000008525 00000 n +0000171298 00000 n +0000401672 00000 n +0000008585 00000 n +0000008648 00000 n +0000171423 00000 n +0000401579 00000 n +0000008708 00000 n +0000008799 00000 n +0000171548 00000 n +0000401486 00000 n +0000008859 00000 n +0000008958 00000 n +0000171673 00000 n +0000401393 00000 n +0000009018 00000 n +0000009098 00000 n +0000173696 00000 n +0000401300 00000 n +0000009158 00000 n +0000009237 00000 n +0000173821 00000 n +0000401207 00000 n +0000009297 00000 n +0000009347 00000 n +0000173946 00000 n +0000401114 00000 n +0000009407 00000 n +0000009472 00000 n +0000175823 00000 n +0000401021 00000 n +0000009532 00000 n +0000009619 00000 n +0000175948 00000 n +0000400928 00000 n +0000009679 00000 n +0000009740 00000 n +0000178036 00000 n +0000400835 00000 n +0000009800 00000 n +0000009894 00000 n +0000178161 00000 n +0000400742 00000 n +0000009954 00000 n +0000010036 00000 n +0000180504 00000 n +0000400649 00000 n +0000010096 00000 n +0000010150 00000 n +0000180629 00000 n +0000400570 00000 n +0000010210 00000 n +0000010260 00000 n +0000184037 00000 n +0000400437 00000 n +0000010309 00000 n +0000010363 00000 n +0000184162 00000 n +0000400358 00000 n +0000010417 00000 n +0000010454 00000 n +0000187330 00000 n +0000400226 00000 n +0000010508 00000 n +0000010540 00000 n +0000187455 00000 n +0000400147 00000 n +0000010599 00000 n +0000010693 00000 n +0000189840 00000 n +0000400054 00000 n +0000010752 00000 n +0000010804 00000 n +0000189965 00000 n +0000399961 00000 n +0000010863 00000 n +0000010906 00000 n +0000190090 00000 n +0000399868 00000 n +0000010965 00000 n +0000011010 00000 n +0000190215 00000 n +0000399775 00000 n +0000011069 00000 n +0000011114 00000 n +0000190339 00000 n +0000399682 00000 n +0000011173 00000 n +0000011218 00000 n +0000193369 00000 n +0000399589 00000 n +0000011277 00000 n +0000011322 00000 n +0000193493 00000 n +0000399510 00000 n +0000011381 00000 n +0000011426 00000 n +0000193618 00000 n +0000399417 00000 n +0000011480 00000 n +0000011510 00000 n +0000193743 00000 n +0000399324 00000 n +0000011564 00000 n +0000011609 00000 n +0000195987 00000 n +0000399231 00000 n +0000011663 00000 n +0000011714 00000 n +0000196112 00000 n +0000399099 00000 n +0000011768 00000 n +0000011809 00000 n +0000197950 00000 n +0000399020 00000 n +0000011868 00000 n +0000011903 00000 n +0000198075 00000 n +0000398941 00000 n +0000011962 00000 n +0000011998 00000 n +0000198200 00000 n +0000398809 00000 n +0000012052 00000 n +0000012099 00000 n +0000198325 00000 n +0000398730 00000 n +0000012158 00000 n +0000012193 00000 n +0000198450 00000 n +0000398651 00000 n +0000012252 00000 n +0000012288 00000 n +0000198574 00000 n +0000398519 00000 n +0000012342 00000 n +0000012397 00000 n +0000198699 00000 n +0000398440 00000 n +0000012456 00000 n +0000012491 00000 n +0000198824 00000 n +0000398361 00000 n +0000012550 00000 n +0000012586 00000 n +0000200619 00000 n +0000398229 00000 n +0000012640 00000 n +0000012681 00000 n +0000200744 00000 n +0000398150 00000 n +0000012740 00000 n +0000012775 00000 n +0000200869 00000 n +0000398071 00000 n +0000012834 00000 n +0000012870 00000 n +0000200993 00000 n +0000397939 00000 n +0000012925 00000 n +0000012961 00000 n +0000201118 00000 n +0000397860 00000 n +0000013021 00000 n +0000013057 00000 n +0000201242 00000 n +0000397781 00000 n +0000013117 00000 n +0000013154 00000 n +0000201366 00000 n +0000397649 00000 n +0000013209 00000 n +0000013251 00000 n +0000201491 00000 n +0000397570 00000 n +0000013311 00000 n +0000013347 00000 n +0000203187 00000 n +0000397491 00000 n +0000013407 00000 n +0000013444 00000 n +0000203312 00000 n +0000397373 00000 n +0000013499 00000 n +0000013542 00000 n +0000203437 00000 n +0000397294 00000 n +0000013602 00000 n +0000013638 00000 n +0000203562 00000 n +0000397215 00000 n +0000013698 00000 n +0000013735 00000 n +0000206061 00000 n +0000397083 00000 n +0000013784 00000 n +0000013840 00000 n +0000206186 00000 n +0000396965 00000 n +0000013894 00000 n +0000013941 00000 n +0000206311 00000 n +0000396886 00000 n +0000014000 00000 n +0000014035 00000 n +0000206435 00000 n +0000396807 00000 n +0000014094 00000 n +0000014130 00000 n +0000208946 00000 n +0000396675 00000 n +0000014184 00000 n +0000014228 00000 n +0000209071 00000 n +0000396596 00000 n +0000014287 00000 n +0000014322 00000 n +0000209196 00000 n +0000396517 00000 n +0000014381 00000 n +0000014417 00000 n +0000209321 00000 n +0000396385 00000 n +0000014471 00000 n +0000014520 00000 n +0000209445 00000 n +0000396306 00000 n +0000014579 00000 n +0000014614 00000 n +0000209569 00000 n +0000396227 00000 n +0000014673 00000 n +0000014709 00000 n +0000209694 00000 n +0000396095 00000 n +0000014763 00000 n +0000014802 00000 n +0000211843 00000 n +0000396016 00000 n +0000014861 00000 n +0000014896 00000 n +0000211968 00000 n +0000395937 00000 n +0000014955 00000 n +0000014991 00000 n +0000212093 00000 n +0000395819 00000 n +0000015045 00000 n +0000015085 00000 n +0000212218 00000 n +0000395740 00000 n +0000015144 00000 n +0000015179 00000 n +0000212342 00000 n +0000395661 00000 n +0000015238 00000 n +0000015274 00000 n +0000212467 00000 n +0000395529 00000 n +0000015323 00000 n +0000015381 00000 n +0000214325 00000 n +0000395411 00000 n +0000015435 00000 n +0000015474 00000 n +0000214450 00000 n +0000395332 00000 n +0000015533 00000 n +0000015568 00000 n +0000214575 00000 n +0000395253 00000 n +0000015627 00000 n +0000015663 00000 n +0000214700 00000 n +0000395135 00000 n +0000015717 00000 n +0000015752 00000 n +0000214825 00000 n +0000395056 00000 n +0000015811 00000 n +0000015846 00000 n +0000216997 00000 n +0000394977 00000 n +0000015905 00000 n +0000015941 00000 n +0000217122 00000 n +0000394845 00000 n +0000015990 00000 n +0000016040 00000 n +0000217247 00000 n +0000394727 00000 n +0000016094 00000 n +0000016134 00000 n +0000217372 00000 n +0000394648 00000 n +0000016193 00000 n +0000016228 00000 n +0000219764 00000 n +0000394569 00000 n +0000016287 00000 n +0000016323 00000 n +0000219889 00000 n +0000394451 00000 n +0000016377 00000 n +0000016422 00000 n +0000220014 00000 n +0000394372 00000 n +0000016481 00000 n +0000016516 00000 n +0000220139 00000 n +0000394293 00000 n +0000016575 00000 n +0000016611 00000 n +0000220264 00000 n +0000394161 00000 n +0000016660 00000 n +0000016730 00000 n +0000220388 00000 n +0000394082 00000 n +0000016784 00000 n +0000016821 00000 n +0000222204 00000 n +0000393989 00000 n +0000016875 00000 n +0000016909 00000 n +0000222329 00000 n +0000393910 00000 n +0000016963 00000 n +0000016997 00000 n +0000224851 00000 n +0000393792 00000 n +0000017046 00000 n +0000017083 00000 n +0000224976 00000 n +0000393674 00000 n +0000017137 00000 n +0000017178 00000 n +0000225100 00000 n +0000393595 00000 n +0000017237 00000 n +0000017290 00000 n +0000225224 00000 n +0000393516 00000 n +0000017349 00000 n +0000017395 00000 n +0000227245 00000 n +0000393398 00000 n +0000017449 00000 n +0000017490 00000 n +0000227370 00000 n +0000393319 00000 n +0000017549 00000 n +0000017597 00000 n +0000227494 00000 n +0000393226 00000 n +0000017656 00000 n +0000017705 00000 n +0000227618 00000 n +0000393147 00000 n +0000017764 00000 n +0000017814 00000 n +0000230703 00000 n +0000393014 00000 n +0000017862 00000 n +0000017909 00000 n +0000230828 00000 n +0000392935 00000 n +0000017959 00000 n +0000017992 00000 n +0000230953 00000 n +0000392842 00000 n +0000018042 00000 n +0000018106 00000 n +0000231078 00000 n +0000392749 00000 n +0000018156 00000 n +0000018198 00000 n +0000237538 00000 n +0000392656 00000 n +0000018248 00000 n +0000018323 00000 n +0000237662 00000 n +0000392577 00000 n +0000018373 00000 n +0000018433 00000 n +0000245224 00000 n +0000392444 00000 n +0000018481 00000 n +0000018524 00000 n +0000245349 00000 n +0000392379 00000 n +0000018574 00000 n +0000018612 00000 n +0000249371 00000 n +0000392246 00000 n +0000018660 00000 n +0000018706 00000 n +0000249495 00000 n +0000392167 00000 n +0000018756 00000 n +0000018806 00000 n +0000253383 00000 n +0000392074 00000 n +0000018856 00000 n +0000018901 00000 n +0000253508 00000 n +0000391981 00000 n +0000018951 00000 n +0000019008 00000 n +0000253633 00000 n +0000391849 00000 n +0000019058 00000 n +0000019089 00000 n +0000253757 00000 n +0000391770 00000 n +0000019144 00000 n +0000019182 00000 n +0000253882 00000 n +0000391677 00000 n +0000019237 00000 n +0000019277 00000 n +0000254007 00000 n +0000391598 00000 n +0000019332 00000 n +0000019370 00000 n +0000257545 00000 n +0000391466 00000 n +0000019420 00000 n +0000019456 00000 n +0000257670 00000 n +0000391387 00000 n +0000019511 00000 n +0000019567 00000 n +0000257795 00000 n +0000391308 00000 n +0000019622 00000 n +0000019659 00000 n +0000257920 00000 n +0000391215 00000 n +0000019709 00000 n +0000019751 00000 n +0000260013 00000 n +0000391136 00000 n +0000019801 00000 n +0000019833 00000 n +0000263707 00000 n +0000391003 00000 n +0000019881 00000 n +0000019937 00000 n +0000263832 00000 n +0000390924 00000 n +0000019987 00000 n +0000020024 00000 n +0000263957 00000 n +0000390831 00000 n +0000020074 00000 n +0000020116 00000 n +0000267922 00000 n +0000390752 00000 n +0000020166 00000 n +0000020209 00000 n +0000271955 00000 n +0000390619 00000 n +0000020257 00000 n +0000020287 00000 n +0000272080 00000 n +0000390540 00000 n +0000020337 00000 n +0000020372 00000 n +0000272205 00000 n +0000390408 00000 n +0000020422 00000 n +0000020462 00000 n +0000272330 00000 n +0000390329 00000 n +0000020517 00000 n +0000020558 00000 n +0000272455 00000 n +0000390250 00000 n +0000020613 00000 n +0000020654 00000 n +0000275325 00000 n +0000390132 00000 n +0000020704 00000 n +0000020744 00000 n +0000275450 00000 n +0000390067 00000 n +0000020799 00000 n +0000020865 00000 n +0000277921 00000 n +0000389934 00000 n +0000020913 00000 n +0000020957 00000 n +0000278046 00000 n +0000389855 00000 n +0000021007 00000 n +0000021037 00000 n +0000278171 00000 n +0000389776 00000 n +0000021087 00000 n +0000021128 00000 n +0000279705 00000 n +0000389657 00000 n +0000021176 00000 n +0000021217 00000 n +0000279830 00000 n +0000389578 00000 n +0000021267 00000 n +0000021302 00000 n +0000279955 00000 n +0000389499 00000 n +0000021352 00000 n +0000021384 00000 n +0000021757 00000 n +0000021998 00000 n +0000021436 00000 n +0000021876 00000 n +0000021937 00000 n +0000386543 00000 n +0000373304 00000 n +0000386377 00000 n +0000372870 00000 n +0000368418 00000 n +0000372707 00000 n +0000387416 00000 n +0000024306 00000 n +0000023205 00000 n +0000022083 00000 n +0000024062 00000 n +0000368072 00000 n +0000365019 00000 n +0000367907 00000 n +0000024123 00000 n +0000363188 00000 n +0000346984 00000 n +0000363024 00000 n +0000345060 00000 n +0000327014 00000 n +0000344897 00000 n +0000024184 00000 n +0000023368 00000 n +0000326048 00000 n +0000310254 00000 n +0000325884 00000 n +0000023539 00000 n +0000023709 00000 n +0000024245 00000 n +0000023880 00000 n +0000032730 00000 n +0000025927 00000 n +0000024417 00000 n +0000032608 00000 n +0000032669 00000 n +0000026378 00000 n +0000026530 00000 n +0000026683 00000 n +0000026836 00000 n +0000026990 00000 n +0000027142 00000 n +0000027296 00000 n +0000027450 00000 n +0000027604 00000 n +0000027758 00000 n +0000027911 00000 n +0000028063 00000 n +0000028217 00000 n +0000028370 00000 n +0000028524 00000 n +0000028678 00000 n +0000028832 00000 n +0000028991 00000 n +0000029150 00000 n +0000029309 00000 n +0000029461 00000 n +0000029613 00000 n +0000029767 00000 n +0000029920 00000 n +0000030074 00000 n +0000030233 00000 n +0000030392 00000 n +0000030551 00000 n +0000030710 00000 n +0000030869 00000 n +0000031028 00000 n +0000031187 00000 n +0000031345 00000 n +0000031504 00000 n +0000031664 00000 n +0000031823 00000 n +0000031981 00000 n +0000032140 00000 n +0000032298 00000 n +0000032456 00000 n +0000043285 00000 n +0000034901 00000 n +0000032815 00000 n +0000043224 00000 n +0000308649 00000 n +0000299425 00000 n +0000308485 00000 n +0000035430 00000 n +0000035589 00000 n +0000035748 00000 n +0000035902 00000 n +0000036054 00000 n +0000036208 00000 n +0000036367 00000 n +0000036526 00000 n +0000036684 00000 n +0000036838 00000 n +0000036997 00000 n +0000037149 00000 n +0000037303 00000 n +0000037457 00000 n +0000037611 00000 n +0000037765 00000 n +0000037919 00000 n +0000038073 00000 n +0000038227 00000 n +0000038380 00000 n +0000038534 00000 n +0000038685 00000 n +0000038836 00000 n +0000038990 00000 n +0000039149 00000 n +0000039308 00000 n +0000039462 00000 n +0000039621 00000 n +0000039780 00000 n +0000039943 00000 n +0000040107 00000 n +0000040266 00000 n +0000040430 00000 n +0000040593 00000 n +0000040757 00000 n +0000040921 00000 n +0000041085 00000 n +0000041249 00000 n +0000041413 00000 n +0000041577 00000 n +0000041741 00000 n +0000041906 00000 n +0000042070 00000 n +0000042235 00000 n +0000042401 00000 n +0000042566 00000 n +0000042732 00000 n +0000042896 00000 n +0000043060 00000 n +0000054473 00000 n +0000045312 00000 n +0000043383 00000 n +0000054410 00000 n +0000045914 00000 n +0000046080 00000 n +0000046246 00000 n +0000046412 00000 n +0000046578 00000 n +0000046744 00000 n +0000046910 00000 n +0000047076 00000 n +0000047242 00000 n +0000047407 00000 n +0000047573 00000 n +0000047739 00000 n +0000047904 00000 n +0000048059 00000 n +0000048219 00000 n +0000048379 00000 n +0000048544 00000 n +0000048709 00000 n +0000048874 00000 n +0000049039 00000 n +0000049204 00000 n +0000049368 00000 n +0000049533 00000 n +0000049698 00000 n +0000049858 00000 n +0000050017 00000 n +0000050177 00000 n +0000050337 00000 n +0000050502 00000 n +0000050667 00000 n +0000050827 00000 n +0000050992 00000 n +0000051157 00000 n +0000051317 00000 n +0000051481 00000 n +0000051646 00000 n +0000051806 00000 n +0000051970 00000 n +0000052135 00000 n +0000052296 00000 n +0000052462 00000 n +0000052628 00000 n +0000052789 00000 n +0000052955 00000 n +0000053121 00000 n +0000053282 00000 n +0000053447 00000 n +0000053613 00000 n +0000053768 00000 n +0000053927 00000 n +0000054089 00000 n +0000054252 00000 n +0000065016 00000 n +0000056357 00000 n +0000054559 00000 n +0000064953 00000 n +0000056941 00000 n +0000057106 00000 n +0000057271 00000 n +0000057431 00000 n +0000057596 00000 n +0000057761 00000 n +0000057921 00000 n +0000058086 00000 n +0000058251 00000 n +0000058410 00000 n +0000058575 00000 n +0000298991 00000 n +0000297468 00000 n +0000298825 00000 n +0000058740 00000 n +0000058894 00000 n +0000059054 00000 n +0000059219 00000 n +0000059384 00000 n +0000059544 00000 n +0000059709 00000 n +0000059874 00000 n +0000060029 00000 n +0000060189 00000 n +0000060353 00000 n +0000060518 00000 n +0000060678 00000 n +0000060843 00000 n +0000061007 00000 n +0000061162 00000 n +0000061322 00000 n +0000061482 00000 n +0000061642 00000 n +0000061797 00000 n +0000061957 00000 n +0000062122 00000 n +0000062287 00000 n +0000062446 00000 n +0000062611 00000 n +0000062776 00000 n +0000062940 00000 n +0000063093 00000 n +0000063249 00000 n +0000063405 00000 n +0000063561 00000 n +0000063717 00000 n +0000063873 00000 n +0000064027 00000 n +0000064183 00000 n +0000064336 00000 n +0000064491 00000 n +0000064645 00000 n +0000064799 00000 n +0000070703 00000 n +0000066354 00000 n +0000065129 00000 n +0000070640 00000 n +0000066714 00000 n +0000066875 00000 n +0000067036 00000 n +0000067197 00000 n +0000067353 00000 n +0000067514 00000 n +0000067675 00000 n +0000067831 00000 n +0000067987 00000 n +0000068141 00000 n +0000068297 00000 n +0000068452 00000 n +0000068608 00000 n +0000068762 00000 n +0000068918 00000 n +0000069074 00000 n +0000069235 00000 n +0000069396 00000 n +0000069552 00000 n +0000069712 00000 n +0000069866 00000 n +0000070021 00000 n +0000070176 00000 n +0000070328 00000 n +0000070484 00000 n +0000387536 00000 n +0000074382 00000 n +0000073825 00000 n +0000070802 00000 n +0000073948 00000 n +0000074071 00000 n +0000074195 00000 n +0000074319 00000 n +0000077719 00000 n +0000077409 00000 n +0000074468 00000 n +0000077532 00000 n +0000077656 00000 n +0000295566 00000 n +0000293552 00000 n +0000295401 00000 n +0000081795 00000 n +0000080674 00000 n +0000077832 00000 n +0000080797 00000 n +0000080921 00000 n +0000081045 00000 n +0000081108 00000 n +0000081171 00000 n +0000081234 00000 n +0000081358 00000 n +0000081481 00000 n +0000081544 00000 n +0000081607 00000 n +0000081670 00000 n +0000081733 00000 n 0000085789 00000 n -0000087771 00000 n -0000087937 00000 n -0000088673 00000 n -0000088848 00000 n -0000089890 00000 n -0000090056 00000 n -0000091692 00000 n -0000091858 00000 n -0000092482 00000 n -0000092657 00000 n -0000093987 00000 n -0000094162 00000 n -0000095236 00000 n -0000095402 00000 n -0000096003 00000 n -0000096169 00000 n -0000097955 00000 n -0000098121 00000 n -0000099838 00000 n -0000100004 00000 n -0000101853 00000 n -0000102009 00000 n -0000103124 00000 n -0000103308 00000 n -0000104915 00000 n -0000105080 00000 n -0000105969 00000 n -0000106168 00000 n -0000107893 00000 n -0000108068 00000 n -0000109893 00000 n -0000110068 00000 n -0000110679 00000 n -0000110854 00000 n -0000111629 00000 n -0000111804 00000 n -0000112561 00000 n -0000112736 00000 n -0000113574 00000 n -0000113749 00000 n -0000114585 00000 n -0000114769 00000 n -0000115609 00000 n -0000115784 00000 n -0000116544 00000 n -0000116709 00000 n -0000117334 00000 n -0000117518 00000 n -0000118286 00000 n -0000118461 00000 n -0000119423 00000 n -0000119607 00000 n -0000120942 00000 n -0000121126 00000 n -0000122144 00000 n -0000122309 00000 n -0000122888 00000 n -0000123072 00000 n -0000124132 00000 n -0000124307 00000 n -0000125185 00000 n -0000125360 00000 n -0000126454 00000 n -0000126638 00000 n -0000127525 00000 n -0000127709 00000 n -0000128486 00000 n -0000128661 00000 n -0000129262 00000 n -0000129437 00000 n -0000130099 00000 n -0000130283 00000 n -0000131259 00000 n -0000131434 00000 n -0000132442 00000 n -0000132617 00000 n -0000133611 00000 n -0000133795 00000 n -0000134627 00000 n -0000134802 00000 n -0000135534 00000 n -0000135709 00000 n -0000136391 00000 n -0000136566 00000 n -0000137395 00000 n -0000137570 00000 n -0000138558 00000 n -0000138733 00000 n -0000140117 00000 n -0000140301 00000 n -0000141095 00000 n -0000141279 00000 n -0000141941 00000 n -0000142116 00000 n -0000142523 00000 n -0000142688 00000 n -0000142994 00000 n -0000143189 00000 n -0000144721 00000 n -0000144896 00000 n -0000146611 00000 n -0000146796 00000 n -0000148377 00000 n -0000148562 00000 n -0000150328 00000 n -0000150494 00000 n -0000150873 00000 n -0000151048 00000 n -0000152345 00000 n -0000152520 00000 n -0000154223 00000 n -0000154399 00000 n -0000156151 00000 n -0000156317 00000 n -0000158211 00000 n -0000158395 00000 n -0000159665 00000 n -0000159840 00000 n -0000161568 00000 n -0000161780 00000 n -0000163402 00000 n -0000163585 00000 n -0000164497 00000 n -0000164672 00000 n -0000165960 00000 n -0000166154 00000 n -0000167493 00000 n -0000167677 00000 n -0000168711 00000 n -0000168886 00000 n -0000169535 00000 n -0000169591 00000 n -0000169690 00000 n -0000169843 00000 n -0000169922 00000 n -0000170025 00000 n -0000170223 00000 n -0000170317 00000 n -0000170434 00000 n -0000170533 00000 n -0000170693 00000 n -0000170792 00000 n -0000170916 00000 n -0000171030 00000 n -0000171144 00000 n -0000171242 00000 n -0000171406 00000 n -0000171510 00000 n -0000171629 00000 n -0000171751 00000 n -0000171873 00000 n -0000172009 00000 n -0000172109 00000 n -0000172221 00000 n -0000172331 00000 n -0000172455 00000 n -0000172612 00000 n -0000172717 00000 n -0000172834 00000 n -0000172992 00000 n -0000173096 00000 n -0000173213 00000 n -0000173335 00000 n -0000173452 00000 n -0000173569 00000 n -0000173687 00000 n -0000173805 00000 n -0000173927 00000 n -0000174049 00000 n -0000174173 00000 n -0000174297 00000 n -0000174416 00000 n -0000174535 00000 n -0000174659 00000 n -0000174770 00000 n -0000174927 00000 n -0000175026 00000 n -0000175127 00000 n -0000175234 00000 n -0000175393 00000 n -0000175532 00000 n -0000175643 00000 n -0000175774 00000 n -0000175887 00000 n -0000176016 00000 n -0000176106 00000 n -0000176271 00000 n -0000176370 00000 n -0000176479 00000 n -0000176593 00000 n -0000176702 00000 n -0000176809 00000 n -0000176919 00000 n -0000177032 00000 n -0000177144 00000 n -0000177250 00000 n -0000177382 00000 n -0000177539 00000 n -0000177674 00000 n -0000177770 00000 n -0000177866 00000 n -0000178022 00000 n -0000178116 00000 n -0000178230 00000 n -0000178329 00000 n -0000178496 00000 n -0000178596 00000 n -0000178704 00000 n -0000178810 00000 n -0000178931 00000 n -0000179058 00000 n -0000179175 00000 n -0000179298 00000 n -0000179429 00000 n -0000179546 00000 n -0000179658 00000 n -0000179776 00000 n -0000179882 00000 n -0000180050 00000 n -0000180160 00000 n -0000180280 00000 n -0000180405 00000 n -0000180520 00000 n -0000180623 00000 n -0000180785 00000 n -0000180887 00000 n -0000180985 00000 n -0000181147 00000 n -0000181250 00000 n -0000181358 00000 n -0000181540 00000 n -0000181640 00000 n -0000181750 00000 n -0000181847 00000 n -0000181983 00000 n -0000182087 00000 n -0000182191 00000 n -0000182358 00000 n -0000182454 00000 n -0000182594 00000 n -0000182712 00000 n -0000182863 00000 n -0000182986 00000 n -0000183149 00000 n -0000183237 00000 n -0000183403 00000 n -0000183516 00000 n -0000183637 00000 n -0000183770 00000 n -0000183913 00000 n -0000184014 00000 n -0000184130 00000 n -0000184231 00000 n -0000184379 00000 n -0000184495 00000 n -0000184592 00000 n -0000184710 00000 n -0000184805 00000 n -0000184981 00000 n -0000185081 00000 n -0000185199 00000 n -0000185306 00000 n -0000185456 00000 n -0000185554 00000 n -0000185706 00000 n -0000185810 00000 n -0000185914 00000 n -0000186053 00000 n -0000186169 00000 n -0000186333 00000 n -0000186426 00000 n -0000186530 00000 n -0000186678 00000 n -0000186776 00000 n -0000186871 00000 n +0000085229 00000 n +0000081881 00000 n +0000085352 00000 n +0000085415 00000 n +0000085478 00000 n +0000085602 00000 n +0000085726 00000 n +0000088472 00000 n +0000087787 00000 n +0000085888 00000 n +0000087910 00000 n +0000088034 00000 n +0000088158 00000 n +0000088221 00000 n +0000088284 00000 n +0000088347 00000 n +0000088410 00000 n +0000091041 00000 n +0000090731 00000 n +0000088571 00000 n +0000090854 00000 n +0000090978 00000 n +0000387661 00000 n +0000093320 00000 n +0000092887 00000 n +0000091167 00000 n +0000093010 00000 n +0000093134 00000 n +0000093257 00000 n +0000096545 00000 n +0000095674 00000 n +0000093432 00000 n +0000095797 00000 n +0000095860 00000 n +0000095923 00000 n +0000095986 00000 n +0000096110 00000 n +0000096234 00000 n +0000096358 00000 n +0000096482 00000 n +0000101214 00000 n +0000099982 00000 n +0000096657 00000 n +0000100524 00000 n +0000100648 00000 n +0000100135 00000 n +0000100334 00000 n +0000100711 00000 n +0000100774 00000 n +0000100837 00000 n +0000100900 00000 n +0000100963 00000 n +0000101026 00000 n +0000101089 00000 n +0000101152 00000 n +0000106005 00000 n +0000104751 00000 n +0000101313 00000 n +0000104874 00000 n +0000104937 00000 n +0000105000 00000 n +0000105062 00000 n +0000105125 00000 n +0000105188 00000 n +0000105251 00000 n +0000105314 00000 n +0000105376 00000 n +0000105439 00000 n +0000105502 00000 n +0000105565 00000 n +0000105627 00000 n +0000105690 00000 n +0000105753 00000 n +0000105816 00000 n +0000105879 00000 n +0000105942 00000 n +0000110449 00000 n +0000109389 00000 n +0000106091 00000 n +0000109512 00000 n +0000109636 00000 n +0000109760 00000 n +0000109883 00000 n +0000109946 00000 n +0000110009 00000 n +0000110072 00000 n +0000110135 00000 n +0000110198 00000 n +0000110261 00000 n +0000110324 00000 n +0000110387 00000 n +0000114439 00000 n +0000112695 00000 n +0000110535 00000 n +0000112818 00000 n +0000112881 00000 n +0000112944 00000 n +0000113007 00000 n +0000113131 00000 n +0000113256 00000 n +0000113380 00000 n +0000113505 00000 n +0000113630 00000 n +0000113755 00000 n +0000113880 00000 n +0000114004 00000 n +0000114129 00000 n +0000114254 00000 n +0000114378 00000 n +0000387786 00000 n +0000118116 00000 n +0000116554 00000 n +0000114538 00000 n +0000116677 00000 n +0000116802 00000 n +0000116926 00000 n +0000117051 00000 n +0000117176 00000 n +0000117301 00000 n +0000117426 00000 n +0000117551 00000 n +0000117614 00000 n +0000117677 00000 n +0000117740 00000 n +0000117803 00000 n +0000117866 00000 n +0000117928 00000 n +0000117991 00000 n +0000118054 00000 n +0000122240 00000 n +0000121363 00000 n +0000118228 00000 n +0000121486 00000 n +0000121549 00000 n +0000121612 00000 n +0000121675 00000 n +0000121738 00000 n +0000121801 00000 n +0000121864 00000 n +0000121988 00000 n +0000122051 00000 n +0000122114 00000 n +0000122177 00000 n +0000124346 00000 n +0000123405 00000 n +0000122339 00000 n +0000123528 00000 n +0000123653 00000 n +0000123716 00000 n +0000123779 00000 n +0000123842 00000 n +0000123905 00000 n +0000123968 00000 n +0000124031 00000 n +0000124094 00000 n +0000124157 00000 n +0000124220 00000 n +0000124283 00000 n +0000128051 00000 n +0000126674 00000 n +0000124445 00000 n +0000126797 00000 n +0000126922 00000 n +0000127047 00000 n +0000127110 00000 n +0000127173 00000 n +0000127236 00000 n +0000127299 00000 n +0000127362 00000 n +0000127424 00000 n +0000127487 00000 n +0000127611 00000 n +0000127674 00000 n +0000127737 00000 n +0000127800 00000 n +0000127863 00000 n +0000127988 00000 n +0000129836 00000 n +0000129527 00000 n +0000128151 00000 n +0000129650 00000 n +0000129773 00000 n +0000132103 00000 n +0000131416 00000 n +0000129962 00000 n +0000131539 00000 n +0000131664 00000 n +0000131727 00000 n +0000131789 00000 n +0000131852 00000 n +0000131915 00000 n +0000132040 00000 n +0000387911 00000 n +0000136264 00000 n +0000135578 00000 n +0000132229 00000 n +0000135701 00000 n +0000135826 00000 n +0000135951 00000 n +0000136076 00000 n +0000136201 00000 n +0000140692 00000 n +0000140131 00000 n +0000136364 00000 n +0000140254 00000 n +0000140379 00000 n +0000140504 00000 n +0000140629 00000 n +0000145407 00000 n +0000144846 00000 n +0000140791 00000 n +0000144969 00000 n +0000145094 00000 n +0000145219 00000 n +0000145344 00000 n +0000146221 00000 n +0000146035 00000 n +0000145520 00000 n +0000146158 00000 n +0000150030 00000 n +0000149719 00000 n +0000146307 00000 n +0000149842 00000 n +0000149967 00000 n +0000292953 00000 n +0000284233 00000 n +0000292787 00000 n +0000283051 00000 n +0000281175 00000 n +0000282885 00000 n +0000151243 00000 n +0000151057 00000 n +0000150157 00000 n +0000151180 00000 n +0000388036 00000 n +0000157049 00000 n +0000154858 00000 n +0000151342 00000 n +0000156424 00000 n +0000156549 00000 n +0000156674 00000 n +0000155056 00000 n +0000155250 00000 n +0000155444 00000 n +0000155666 00000 n +0000155854 00000 n +0000156030 00000 n +0000156237 00000 n +0000156736 00000 n +0000156799 00000 n +0000156861 00000 n +0000156923 00000 n +0000156986 00000 n +0000160803 00000 n +0000159804 00000 n +0000157175 00000 n +0000159927 00000 n +0000160052 00000 n +0000160177 00000 n +0000160301 00000 n +0000160426 00000 n +0000160489 00000 n +0000160552 00000 n +0000160614 00000 n +0000160677 00000 n +0000160740 00000 n +0000163349 00000 n +0000162165 00000 n +0000160902 00000 n +0000162288 00000 n +0000162413 00000 n +0000162538 00000 n +0000162663 00000 n +0000162788 00000 n +0000162913 00000 n +0000163038 00000 n +0000163162 00000 n +0000163286 00000 n +0000165906 00000 n +0000164845 00000 n +0000163448 00000 n +0000164968 00000 n +0000165093 00000 n +0000165218 00000 n +0000165343 00000 n +0000165468 00000 n +0000165593 00000 n +0000165718 00000 n +0000165843 00000 n +0000168900 00000 n +0000168089 00000 n +0000166018 00000 n +0000168212 00000 n +0000168337 00000 n +0000168462 00000 n +0000168587 00000 n +0000168712 00000 n +0000168837 00000 n +0000171798 00000 n +0000170987 00000 n +0000169026 00000 n +0000171110 00000 n +0000171235 00000 n +0000171360 00000 n +0000171485 00000 n +0000171610 00000 n +0000171735 00000 n +0000388161 00000 n +0000174071 00000 n +0000173510 00000 n +0000171924 00000 n +0000173633 00000 n +0000173758 00000 n +0000173883 00000 n +0000174008 00000 n +0000176073 00000 n +0000175637 00000 n +0000174196 00000 n +0000175760 00000 n +0000175885 00000 n +0000176010 00000 n +0000178286 00000 n +0000177850 00000 n +0000176185 00000 n +0000177973 00000 n +0000178098 00000 n +0000178223 00000 n +0000180754 00000 n +0000180318 00000 n +0000178398 00000 n +0000180441 00000 n +0000180566 00000 n +0000180691 00000 n +0000184286 00000 n +0000183851 00000 n +0000180880 00000 n +0000183974 00000 n +0000184099 00000 n +0000184223 00000 n +0000187580 00000 n +0000187144 00000 n +0000184412 00000 n +0000187267 00000 n +0000187392 00000 n +0000187517 00000 n +0000388286 00000 n +0000190463 00000 n +0000189654 00000 n +0000187719 00000 n +0000189777 00000 n +0000189902 00000 n +0000190027 00000 n +0000190152 00000 n +0000190276 00000 n +0000190401 00000 n +0000193868 00000 n +0000193183 00000 n +0000190575 00000 n +0000193306 00000 n +0000193431 00000 n +0000193555 00000 n +0000193680 00000 n +0000193805 00000 n +0000196234 00000 n +0000195801 00000 n +0000193994 00000 n +0000195924 00000 n +0000196049 00000 n +0000196173 00000 n +0000198949 00000 n +0000197764 00000 n +0000196360 00000 n +0000197887 00000 n +0000198012 00000 n +0000198137 00000 n +0000198262 00000 n +0000198387 00000 n +0000198512 00000 n +0000198636 00000 n +0000198761 00000 n +0000198886 00000 n +0000201615 00000 n +0000200433 00000 n +0000199088 00000 n +0000200556 00000 n +0000200681 00000 n +0000200806 00000 n +0000200930 00000 n +0000201055 00000 n +0000201180 00000 n +0000201303 00000 n +0000201428 00000 n +0000201553 00000 n +0000203687 00000 n +0000203001 00000 n +0000201727 00000 n +0000203124 00000 n +0000203249 00000 n +0000203374 00000 n +0000203499 00000 n +0000203624 00000 n +0000388411 00000 n +0000206559 00000 n +0000205875 00000 n +0000203799 00000 n +0000205998 00000 n +0000206123 00000 n +0000206248 00000 n +0000206372 00000 n +0000206497 00000 n +0000209818 00000 n +0000208760 00000 n +0000206685 00000 n +0000208883 00000 n +0000209008 00000 n +0000209133 00000 n +0000209258 00000 n +0000209383 00000 n +0000209506 00000 n +0000209631 00000 n +0000209756 00000 n +0000212591 00000 n +0000211657 00000 n +0000209930 00000 n +0000211780 00000 n +0000211905 00000 n +0000212030 00000 n +0000212155 00000 n +0000212280 00000 n +0000212404 00000 n +0000212529 00000 n +0000214950 00000 n +0000214139 00000 n +0000212744 00000 n +0000214262 00000 n +0000214387 00000 n +0000214512 00000 n +0000214637 00000 n +0000214762 00000 n +0000214887 00000 n +0000217497 00000 n +0000216811 00000 n +0000215076 00000 n +0000216934 00000 n +0000217059 00000 n +0000217184 00000 n +0000217309 00000 n +0000217434 00000 n +0000220512 00000 n +0000219578 00000 n +0000217609 00000 n +0000219701 00000 n +0000219826 00000 n +0000219951 00000 n +0000220076 00000 n +0000220201 00000 n +0000220326 00000 n +0000220449 00000 n +0000388536 00000 n +0000222453 00000 n +0000222018 00000 n +0000220624 00000 n +0000222141 00000 n +0000222266 00000 n +0000222391 00000 n +0000225349 00000 n +0000224665 00000 n +0000222565 00000 n +0000224788 00000 n +0000224913 00000 n +0000225038 00000 n +0000225161 00000 n +0000225286 00000 n +0000227743 00000 n +0000227059 00000 n +0000225448 00000 n +0000227182 00000 n +0000227307 00000 n +0000227432 00000 n +0000227556 00000 n +0000227680 00000 n +0000231203 00000 n +0000230517 00000 n +0000227855 00000 n +0000230640 00000 n +0000230765 00000 n +0000230890 00000 n +0000231015 00000 n +0000231140 00000 n +0000234318 00000 n +0000233756 00000 n +0000231316 00000 n +0000233879 00000 n +0000233942 00000 n +0000234005 00000 n +0000234068 00000 n +0000234131 00000 n +0000234194 00000 n +0000234257 00000 n +0000237787 00000 n +0000237226 00000 n +0000234431 00000 n +0000237349 00000 n +0000237412 00000 n +0000237475 00000 n +0000237600 00000 n +0000237724 00000 n +0000388661 00000 n +0000240835 00000 n +0000240649 00000 n +0000237913 00000 n +0000240772 00000 n +0000242762 00000 n +0000242576 00000 n +0000240948 00000 n +0000242699 00000 n +0000245474 00000 n +0000245038 00000 n +0000242875 00000 n +0000245161 00000 n +0000245286 00000 n +0000245411 00000 n +0000249619 00000 n +0000249185 00000 n +0000245573 00000 n +0000249308 00000 n +0000249433 00000 n +0000249556 00000 n +0000254131 00000 n +0000253197 00000 n +0000249718 00000 n +0000253320 00000 n +0000253445 00000 n +0000253570 00000 n +0000253694 00000 n +0000253819 00000 n +0000253944 00000 n +0000254069 00000 n +0000258045 00000 n +0000257359 00000 n +0000254244 00000 n +0000257482 00000 n +0000257607 00000 n +0000257732 00000 n +0000257857 00000 n +0000257982 00000 n +0000388786 00000 n +0000260138 00000 n +0000259827 00000 n +0000258157 00000 n +0000259950 00000 n +0000260075 00000 n +0000264081 00000 n +0000263521 00000 n +0000260264 00000 n +0000263644 00000 n +0000263769 00000 n +0000263894 00000 n +0000264018 00000 n +0000268110 00000 n +0000267736 00000 n +0000264180 00000 n +0000267859 00000 n +0000267984 00000 n +0000268047 00000 n +0000269361 00000 n +0000269175 00000 n +0000268263 00000 n +0000269298 00000 n +0000272579 00000 n +0000271769 00000 n +0000269473 00000 n +0000271892 00000 n +0000272017 00000 n +0000272142 00000 n +0000272267 00000 n +0000272392 00000 n +0000272517 00000 n +0000275575 00000 n +0000275139 00000 n +0000272678 00000 n +0000275262 00000 n +0000275387 00000 n +0000275512 00000 n +0000388911 00000 n +0000278296 00000 n +0000277735 00000 n +0000275701 00000 n +0000277858 00000 n +0000277983 00000 n +0000278108 00000 n +0000278233 00000 n +0000280080 00000 n +0000279519 00000 n +0000278409 00000 n +0000279642 00000 n +0000279767 00000 n +0000279892 00000 n +0000280017 00000 n +0000280179 00000 n +0000283261 00000 n +0000283286 00000 n +0000293287 00000 n +0000295779 00000 n +0000295810 00000 n +0000299208 00000 n +0000308973 00000 n +0000309235 00000 n +0000326633 00000 n +0000345608 00000 n +0000346035 00000 n +0000363628 00000 n +0000364009 00000 n +0000368279 00000 n +0000373105 00000 n +0000387016 00000 n +0000389009 00000 n +0000389134 00000 n +0000389260 00000 n +0000389340 00000 n +0000389422 00000 n +0000409988 00000 n +0000424113 00000 n +0000424154 00000 n +0000424194 00000 n +0000424425 00000 n trailer -<]>> +<< +/Size 1806 +/Root 1804 0 R +/Info 1805 0 R +>> startxref -187413 +424621 %%EOF diff --git a/docs/Samba-HOWTO-Collection.pdf b/docs/Samba-HOWTO-Collection.pdf index a412abec6f..9798599637 100644 --- a/docs/Samba-HOWTO-Collection.pdf +++ b/docs/Samba-HOWTO-Collection.pdf @@ -1,6796 +1,24496 @@ -%PDF-1.3 -% -1 0 obj<>endobj -2 0 obj<>endobj -3 0 obj<>endobj -4 0 obj<>endobj -5 0 obj<>endobj -6 0 obj<>endobj -7 0 obj<>endobj -8 0 obj<>endobj -9 0 obj<>endobj -10 0 obj<>endobj -11 0 obj<>endobj -12 0 obj<>endobj -13 0 obj<>endobj -14 0 obj<>endobj -15 0 obj<>stream -xUQ+1ʑkGl;2"c#X$G`Iwف(qO%sN o$Q4F۾Qz'`/~L,vuGo ujc\߱XI3+cEdJk{Q[^XRo8z͑u(d*Gs(y xދYg({E䢡 {_3^Sd8<##~$:s0B39dendstream -endobj -16 0 obj<]/Interpolate true/Filter/FlateDecode/Width 24/Height 24/BitsPerComponent 8/Length 223 >>stream -xUQ0 58@4wo%wR+8C+N"]ׂ*W ,D1|Ši"%~0)܁1lN!31T4HԆ<<~Z>yn.H>LKb؎џ'4Y}-?f&tA{27L}On4KI" PBhïG]z$>.mcoendstream -endobj -17 0 obj<>endobj -18 0 obj<>endobj -19 0 obj<>endobj -20 0 obj<>endobj -21 0 obj<>endobj -22 0 obj<>endobj -23 0 obj<>endobj -24 0 obj<>endobj -25 0 obj<>endobj -26 0 obj<>endobj -27 0 obj<>endobj -28 0 obj<>endobj -29 0 obj<>endobj -30 0 obj<>endobj -31 0 obj<>endobj -32 0 obj<>endobj -33 0 obj<>endobj -34 0 obj<>endobj -35 0 obj<>endobj -36 0 obj<>endobj -37 0 obj<>endobj -38 0 obj<>endobj -39 0 obj<>endobj -40 0 obj<>endobj -41 0 obj<>endobj -42 0 obj<>endobj -43 0 obj<>endobj -44 0 obj<>endobj -45 0 obj<>endobj -46 0 obj<>endobj -47 0 obj<>endobj -48 0 obj<>endobj -49 0 obj<>endobj -50 0 obj<>endobj -51 0 obj<>endobj -52 0 obj<>endobj -53 0 obj<>endobj -54 0 obj<>endobj -55 0 obj<>endobj -56 0 obj<>endobj -57 0 obj<>endobj -58 0 obj<>endobj -59 0 obj[17 0 R -18 0 R -19 0 R -20 0 R -21 0 R -22 0 R -23 0 R -24 0 R -25 0 R -26 0 R -27 0 R -28 0 R -29 0 R -30 0 R -31 0 R -32 0 R -33 0 R -34 0 R -35 0 R -36 0 R -37 0 R -38 0 R -39 0 R -40 0 R -41 0 R -42 0 R -43 0 R -44 0 R -45 0 R -46 0 R -47 0 R -48 0 R -49 0 R -50 0 R -51 0 R -52 0 R -53 0 R -54 0 R -55 0 R -56 0 R -57 0 R -58 0 R]endobj -60 0 obj<>endobj -61 0 obj<>endobj -62 0 obj<>endobj -63 0 obj<>endobj -64 0 obj<>endobj -65 0 obj<>endobj -66 0 obj<>endobj -67 0 obj<>endobj -68 0 obj<>endobj -69 0 obj<>endobj -70 0 obj<>endobj -71 0 obj<>endobj -72 0 obj<>endobj -73 0 obj<>endobj -74 0 obj<>endobj -75 0 obj<>endobj -76 0 obj<>endobj -77 0 obj<>endobj -78 0 obj<>endobj -79 0 obj<>endobj -80 0 obj<>endobj -81 0 obj<>endobj -82 0 obj<>endobj -83 0 obj<>endobj -84 0 obj<>endobj -85 0 obj<>endobj -86 0 obj<>endobj -87 0 obj<>endobj -88 0 obj<>endobj -89 0 obj<>endobj -90 0 obj<>endobj -91 0 obj<>endobj -92 0 obj<>endobj -93 0 obj<>endobj -94 0 obj<>endobj -95 0 obj<>endobj -96 0 obj<>endobj -97 0 obj<>endobj -98 0 obj<>endobj -99 0 obj<>endobj -100 0 obj<>endobj -101 0 obj<>endobj -102 0 obj<>endobj -103 0 obj[60 0 R -61 0 R -62 0 R -63 0 R -64 0 R -65 0 R -66 0 R -67 0 R -68 0 R -69 0 R -70 0 R -71 0 R -72 0 R -73 0 R -74 0 R -75 0 R -76 0 R -77 0 R -78 0 R -79 0 R -80 0 R -81 0 R -82 0 R -83 0 R -84 0 R -85 0 R -86 0 R -87 0 R -88 0 R -89 0 R -90 0 R -91 0 R -92 0 R -93 0 R -94 0 R -95 0 R -96 0 R -97 0 R -98 0 R -99 0 R -100 0 R -101 0 R -102 0 R]endobj -104 0 obj<>endobj -105 0 obj<>endobj -106 0 obj<>endobj -107 0 obj<>endobj -108 0 obj<>endobj -109 0 obj<>endobj -110 0 obj<>endobj -111 0 obj<>endobj -112 0 obj<>endobj -113 0 obj<>endobj -114 0 obj<>endobj -115 0 obj<>endobj -116 0 obj<>endobj -117 0 obj<>endobj -118 0 obj<>endobj -119 0 obj<>endobj -120 0 obj<>endobj -121 0 obj<>endobj -122 0 obj<>endobj -123 0 obj<>endobj -124 0 obj<>endobj -125 0 obj<>endobj -126 0 obj<>endobj -127 0 obj<>endobj -128 0 obj<>endobj -129 0 obj<>endobj -130 0 obj<>endobj -131 0 obj<>endobj -132 0 obj<>endobj -133 0 obj<>endobj -134 0 obj<>endobj -135 0 obj<>endobj -136 0 obj<>endobj -137 0 obj<>endobj -138 0 obj<>endobj -139 0 obj<>endobj -140 0 obj<>endobj -141 0 obj<>endobj -142 0 obj<>endobj -143 0 obj<>endobj -144 0 obj<>endobj -145 0 obj<>endobj -146 0 obj[104 0 R -105 0 R -106 0 R -107 0 R -108 0 R -109 0 R -110 0 R -111 0 R -112 0 R -113 0 R -114 0 R -115 0 R -116 0 R -117 0 R -118 0 R -119 0 R -120 0 R -121 0 R -122 0 R -123 0 R -124 0 R -125 0 R -126 0 R -127 0 R -128 0 R -129 0 R -130 0 R -131 0 R -132 0 R -133 0 R -134 0 R -135 0 R -136 0 R -137 0 R -138 0 R -139 0 R -140 0 R -141 0 R -142 0 R -143 0 R -144 0 R -145 0 R]endobj -147 0 obj<>endobj -148 0 obj<>endobj -149 0 obj<>endobj -150 0 obj<>endobj -151 0 obj<>endobj -152 0 obj<>endobj -153 0 obj<>endobj -154 0 obj<>endobj -155 0 obj<>endobj -156 0 obj<>endobj -157 0 obj<>endobj -158 0 obj<>endobj -159 0 obj<>endobj -160 0 obj<>endobj -161 0 obj<>endobj -162 0 obj<>endobj -163 0 obj<>endobj -164 0 obj<>endobj -165 0 obj<>endobj -166 0 obj<>endobj -167 0 obj<>endobj -168 0 obj<>endobj -169 0 obj<>endobj -170 0 obj<>endobj -171 0 obj<>endobj -172 0 obj<>endobj -173 0 obj<>endobj -174 0 obj<>endobj -175 0 obj<>endobj -176 0 obj<>endobj -177 0 obj<>endobj -178 0 obj<>endobj -179 0 obj<>endobj -180 0 obj<>endobj -181 0 obj<>endobj -182 0 obj<>endobj -183 0 obj<>endobj -184 0 obj<>endobj -185 0 obj<>endobj -186 0 obj<>endobj -187 0 obj<>endobj -188 0 obj<>endobj -189 0 obj[147 0 R -148 0 R -149 0 R -150 0 R -151 0 R -152 0 R -153 0 R -154 0 R -155 0 R -156 0 R -157 0 R -158 0 R -159 0 R -160 0 R -161 0 R -162 0 R -163 0 R -164 0 R -165 0 R -166 0 R -167 0 R -168 0 R -169 0 R -170 0 R -171 0 R -172 0 R -173 0 R -174 0 R -175 0 R -176 0 R -177 0 R -178 0 R -179 0 R -180 0 R -181 0 R -182 0 R -183 0 R -184 0 R -185 0 R -186 0 R -187 0 R -188 0 R]endobj -190 0 obj<>endobj -191 0 obj<>endobj -192 0 obj<>endobj -193 0 obj<>endobj -194 0 obj<>endobj -195 0 obj<>endobj -196 0 obj<>endobj -197 0 obj<>endobj -198 0 obj<>endobj -199 0 obj<>endobj -200 0 obj<>endobj -201 0 obj<>endobj -202 0 obj<>endobj -203 0 obj<>endobj -204 0 obj<>endobj -205 0 obj<>endobj -206 0 obj<>endobj -207 0 obj<>endobj -208 0 obj<>endobj -209 0 obj<>endobj -210 0 obj<>endobj -211 0 obj<>endobj -212 0 obj<>endobj -213 0 obj<>endobj -214 0 obj<>endobj -215 0 obj<>endobj -216 0 obj<>endobj -217 0 obj<>endobj -218 0 obj<>endobj -219 0 obj<>endobj -220 0 obj<>endobj -221 0 obj<>endobj -222 0 obj<>endobj -223 0 obj<>endobj -224 0 obj<>endobj -225 0 obj<>endobj -226 0 obj<>endobj -227 0 obj<>endobj -228 0 obj<>endobj -229 0 obj<>endobj -230 0 obj<>endobj -231 0 obj<>endobj -232 0 obj<>endobj -233 0 obj<>endobj -234 0 obj[190 0 R -191 0 R -192 0 R -193 0 R -194 0 R -195 0 R -196 0 R -197 0 R -198 0 R -199 0 R -200 0 R -201 0 R -202 0 R -203 0 R -204 0 R -205 0 R -206 0 R -207 0 R -208 0 R -209 0 R -210 0 R -211 0 R -212 0 R -213 0 R -214 0 R -215 0 R -216 0 R -217 0 R -218 0 R -219 0 R -220 0 R -221 0 R -222 0 R -223 0 R -224 0 R -225 0 R -226 0 R -227 0 R -228 0 R -229 0 R -230 0 R -231 0 R -232 0 R -233 0 R]endobj -235 0 obj<>endobj -236 0 obj<>endobj -237 0 obj<>endobj -238 0 obj<>endobj -239 0 obj<>endobj -240 0 obj<>endobj -241 0 obj<>endobj -242 0 obj<>endobj -243 0 obj<>endobj -244 0 obj<>endobj -245 0 obj<>endobj -246 0 obj<>endobj -247 0 obj<>endobj -248 0 obj<>endobj -249 0 obj<>endobj -250 0 obj<>endobj -251 0 obj<>endobj -252 0 obj<>endobj -253 0 obj<>endobj -254 0 obj<>endobj -255 0 obj<>endobj -256 0 obj<>endobj -257 0 obj<>endobj -258 0 obj<>endobj -259 0 obj<>endobj -260 0 obj<>endobj -261 0 obj<>endobj -262 0 obj<>endobj -263 0 obj<>endobj -264 0 obj<>endobj -265 0 obj<>endobj -266 0 obj<>endobj -267 0 obj<>endobj -268 0 obj<>endobj -269 0 obj<>endobj -270 0 obj<>endobj -271 0 obj<>endobj -272 0 obj<>endobj -273 0 obj<>endobj -274 0 obj<>endobj -275 0 obj<>endobj -276 0 obj<>endobj -277 0 obj<>endobj -278 0 obj[235 0 R -236 0 R -237 0 R -238 0 R -239 0 R -240 0 R -241 0 R -242 0 R -243 0 R -244 0 R -245 0 R -246 0 R -247 0 R -248 0 R -249 0 R -250 0 R -251 0 R -252 0 R -253 0 R -254 0 R -255 0 R -256 0 R -257 0 R -258 0 R -259 0 R -260 0 R -261 0 R -262 0 R -263 0 R -264 0 R -265 0 R -266 0 R -267 0 R -268 0 R -269 0 R -270 0 R -271 0 R -272 0 R -273 0 R -274 0 R -275 0 R -276 0 R -277 0 R]endobj -279 0 obj<>endobj -280 0 obj<>endobj -281 0 obj<>endobj -282 0 obj<>endobj -283 0 obj<>endobj -284 0 obj<>endobj -285 0 obj<>endobj -286 0 obj<>endobj -287 0 obj<>endobj -288 0 obj<>endobj -289 0 obj<>endobj -290 0 obj<>endobj -291 0 obj<>endobj -292 0 obj<>endobj -293 0 obj<>endobj -294 0 obj<>endobj -295 0 obj<>endobj -296 0 obj<>endobj -297 0 obj<>endobj -298 0 obj<>endobj -299 0 obj<>endobj -300 0 obj<>endobj -301 0 obj<>endobj -302 0 obj<>endobj -303 0 obj<>endobj -304 0 obj<>endobj -305 0 obj<>endobj -306 0 obj<>endobj -307 0 obj<>endobj -308 0 obj<>endobj -309 0 obj<>endobj -310 0 obj<>endobj -311 0 obj<>endobj -312 0 obj<>endobj -313 0 obj<>endobj -314 0 obj<>endobj -315 0 obj<>endobj -316 0 obj<>endobj -317 0 obj<>endobj -318 0 obj<>endobj -319 0 obj<>endobj -320 0 obj<>endobj -321 0 obj[279 0 R -280 0 R -281 0 R -282 0 R -283 0 R -284 0 R -285 0 R -286 0 R -287 0 R -288 0 R -289 0 R -290 0 R -291 0 R -292 0 R -293 0 R -294 0 R -295 0 R -296 0 R -297 0 R -298 0 R -299 0 R -300 0 R -301 0 R -302 0 R -303 0 R -304 0 R -305 0 R -306 0 R -307 0 R -308 0 R -309 0 R -310 0 R -311 0 R -312 0 R -313 0 R -314 0 R -315 0 R -316 0 R -317 0 R -318 0 R -319 0 R -320 0 R]endobj -322 0 obj<>endobj -323 0 obj<>endobj -324 0 obj<>endobj -325 0 obj<>endobj -326 0 obj<>endobj -327 0 obj<>endobj -328 0 obj<>endobj -329 0 obj<>endobj -330 0 obj<>endobj -331 0 obj<>endobj -332 0 obj<>endobj -333 0 obj<>endobj -334 0 obj<>endobj -335 0 obj<>endobj -336 0 obj<>endobj -337 0 obj<>endobj -338 0 obj<>endobj -339 0 obj<>endobj -340 0 obj<>endobj -341 0 obj<>endobj -342 0 obj<>endobj -343 0 obj<>endobj -344 0 obj<>endobj -345 0 obj<>endobj -346 0 obj<>endobj -347 0 obj<>endobj -348 0 obj<>endobj -349 0 obj<>endobj -350 0 obj<>endobj -351 0 obj<>endobj -352 0 obj<>endobj -353 0 obj<>endobj -354 0 obj<>endobj -355 0 obj<>endobj -356 0 obj<>endobj -357 0 obj<>endobj -358 0 obj<>endobj -359 0 obj<>endobj -360 0 obj<>endobj -361 0 obj<>endobj -362 0 obj<>endobj -363 0 obj<>endobj -364 0 obj<>endobj -365 0 obj<>endobj -366 0 obj[322 0 R -323 0 R -324 0 R -325 0 R -326 0 R -327 0 R -328 0 R -329 0 R -330 0 R -331 0 R -332 0 R -333 0 R -334 0 R -335 0 R -336 0 R -337 0 R -338 0 R -339 0 R -340 0 R -341 0 R -342 0 R -343 0 R -344 0 R -345 0 R -346 0 R -347 0 R -348 0 R -349 0 R -350 0 R -351 0 R -352 0 R -353 0 R -354 0 R -355 0 R -356 0 R -357 0 R -358 0 R -359 0 R -360 0 R -361 0 R -362 0 R -363 0 R -364 0 R -365 0 R]endobj -367 0 obj<>endobj -368 0 obj<>endobj -369 0 obj<>endobj -370 0 obj<>endobj -371 0 obj<>endobj -372 0 obj<>endobj -373 0 obj<>endobj -374 0 obj<>endobj -375 0 obj<>endobj -376 0 obj<>endobj -377 0 obj<>endobj -378 0 obj<>endobj -379 0 obj<>endobj -380 0 obj<>endobj -381 0 obj<>endobj -382 0 obj[367 0 R -368 0 R -369 0 R -370 0 R -371 0 R -372 0 R -373 0 R -374 0 R -375 0 R -376 0 R -377 0 R -378 0 R -379 0 R -380 0 R -381 0 R]endobj -383 0 obj<>endobj -384 0 obj<>endobj -385 0 obj<>endobj -386 0 obj<>endobj -387 0 obj<>endobj -388 0 obj<>endobj -389 0 obj<>endobj -390 0 obj<>endobj -391 0 obj<>endobj -392 0 obj<>endobj -393 0 obj<>endobj -394 0 obj<>endobj -395 0 obj<>endobj -396 0 obj<>endobj -397 0 obj<>endobj -398 0 obj<>endobj -399 0 obj<>endobj -400 0 obj<>endobj -401 0 obj<>endobj -402 0 obj<>endobj -403 0 obj<>endobj -404 0 obj<>endobj -405 0 obj<>endobj -406 0 obj<>endobj -407 0 obj<>endobj -408 0 obj<>endobj -409 0 obj<>endobj -410 0 obj<>endobj -411 0 obj<>endobj -412 0 obj<>endobj -413 0 obj<>endobj -414 0 obj<>endobj -415 0 obj[384 0 R -386 0 R -388 0 R -390 0 R -392 0 R -393 0 R -394 0 R -395 0 R -396 0 R -397 0 R -398 0 R -399 0 R -400 0 R -401 0 R -402 0 R -403 0 R -404 0 R -405 0 R -406 0 R -407 0 R -408 0 R -409 0 R -410 0 R -411 0 R -412 0 R -413 0 R -414 0 R]endobj -416 0 obj<>endobj -417 0 obj<>endobj -418 0 obj<>endobj -419 0 obj<>endobj -420 0 obj<>endobj -421 0 obj<>endobj -422 0 obj<>endobj -423 0 obj<>endobj -424 0 obj<>endobj -425 0 obj<>endobj -426 0 obj<>endobj -427 0 obj<>endobj -428 0 obj<>endobj -429 0 obj<>endobj -430 0 obj<>endobj -431 0 obj<>endobj -432 0 obj<>endobj -433 0 obj<>endobj -434 0 obj<>endobj -435 0 obj<>endobj -436 0 obj<>endobj -437 0 obj<>endobj -438 0 obj<>endobj -439 0 obj<>endobj -440 0 obj<>endobj -441 0 obj<>endobj -442 0 obj<>endobj -443 0 obj<>endobj -444 0 obj<>endobj -445 0 obj<>endobj -446 0 obj<>endobj -447 0 obj<>endobj -448 0 obj<>endobj -449 0 obj<>endobj -450 0 obj<>endobj -451 0 obj<>endobj -452 0 obj<>endobj -453 0 obj<>endobj -454 0 obj<>endobj -455 0 obj<>endobj -456 0 obj<>endobj -457 0 obj<>endobj -458 0 obj<>endobj -459 0 obj<>endobj -460 0 obj<>endobj -461 0 obj<>endobj -462 0 obj<>endobj -463 0 obj<>endobj -464 0 obj<>endobj -465 0 obj<>endobj -466 0 obj<>endobj -467 0 obj<>endobj -468 0 obj<>endobj -469 0 obj[416 0 R -417 0 R -418 0 R -419 0 R -420 0 R -421 0 R -422 0 R -423 0 R -424 0 R -425 0 R -426 0 R -427 0 R -428 0 R -429 0 R -430 0 R -431 0 R -432 0 R -433 0 R -434 0 R -435 0 R -436 0 R -437 0 R -438 0 R -439 0 R -440 0 R -441 0 R -442 0 R -443 0 R -444 0 R -445 0 R -446 0 R -447 0 R -448 0 R -449 0 R -450 0 R -451 0 R -452 0 R -453 0 R -454 0 R -455 0 R -456 0 R -457 0 R -458 0 R -459 0 R -460 0 R -461 0 R -462 0 R -463 0 R -464 0 R -465 0 R -466 0 R -467 0 R -468 0 R]endobj -470 0 obj<>endobj -471 0 obj<>endobj -472 0 obj<>endobj -473 0 obj<>endobj -474 0 obj<>endobj -475 0 obj<>endobj -476 0 obj<>endobj -477 0 obj<>endobj -478 0 obj<>endobj -479 0 obj<>endobj -480 0 obj<>endobj -481 0 obj<>endobj -482 0 obj<>endobj -483 0 obj<>endobj -484 0 obj<>endobj -485 0 obj<>endobj -486 0 obj<>endobj -487 0 obj<>endobj -488 0 obj<>endobj -489 0 obj<>endobj -490 0 obj<>endobj -491 0 obj<>endobj -492 0 obj<>endobj -493 0 obj<>endobj -494 0 obj<>endobj -495 0 obj<>endobj -496 0 obj<>endobj -497 0 obj<>endobj -498 0 obj<>endobj -499 0 obj<>endobj -500 0 obj<>endobj -501 0 obj<>endobj -502 0 obj<>endobj -503 0 obj<>endobj -504 0 obj<>endobj -505 0 obj<>endobj -506 0 obj<>endobj -507 0 obj<>endobj -508 0 obj<>endobj -509 0 obj<>endobj -510 0 obj<>endobj -511 0 obj<>endobj -512 0 obj<>endobj -513 0 obj<>endobj -514 0 obj<>endobj -515 0 obj<>endobj -516 0 obj<>endobj -517 0 obj<>endobj -518 0 obj<>endobj -519 0 obj<>endobj -520 0 obj<>endobj -521 0 obj<>endobj -522 0 obj[470 0 R -471 0 R -472 0 R -473 0 R -474 0 R -475 0 R -476 0 R -477 0 R -478 0 R -479 0 R -480 0 R -481 0 R -482 0 R -483 0 R -484 0 R -485 0 R -486 0 R -487 0 R -488 0 R -489 0 R -490 0 R -491 0 R -492 0 R -493 0 R -494 0 R -495 0 R -496 0 R -497 0 R -498 0 R -499 0 R -500 0 R -501 0 R -502 0 R -503 0 R -504 0 R -505 0 R -506 0 R -507 0 R -508 0 R -509 0 R -510 0 R -511 0 R -512 0 R -513 0 R -514 0 R -515 0 R -516 0 R -517 0 R -518 0 R -519 0 R -520 0 R -521 0 R]endobj -523 0 obj<>endobj -524 0 obj<>endobj -525 0 obj<>endobj -526 0 obj<>endobj -527 0 obj<>endobj -528 0 obj<>endobj -529 0 obj<>endobj -530 0 obj<>endobj -531 0 obj<>endobj -532 0 obj<>endobj -533 0 obj<>endobj -534 0 obj<>endobj -535 0 obj<>endobj -536 0 obj<>endobj -537 0 obj<>endobj -538 0 obj<>endobj -539 0 obj<>endobj -540 0 obj<>endobj -541 0 obj<>endobj -542 0 obj<>endobj -543 0 obj<>endobj -544 0 obj<>endobj -545 0 obj<>endobj -546 0 obj<>endobj -547 0 obj<>endobj -548 0 obj<>endobj -549 0 obj<>endobj -550 0 obj<>endobj -551 0 obj<>endobj -552 0 obj<>endobj -553 0 obj<>endobj -554 0 obj<>endobj -555 0 obj<>endobj -556 0 obj<>endobj -557 0 obj<>endobj -558 0 obj<>endobj -559 0 obj<>endobj -560 0 obj<>endobj -561 0 obj<>endobj -562 0 obj<>endobj -563 0 obj<>endobj -564 0 obj<>endobj -565 0 obj<>endobj -566 0 obj<>endobj -567 0 obj<>endobj -568 0 obj<>endobj -569 0 obj<>endobj -570 0 obj<>endobj -571 0 obj<>endobj -572 0 obj<>endobj -573 0 obj<>endobj -574 0 obj[523 0 R -524 0 R -525 0 R -526 0 R -527 0 R -528 0 R -529 0 R -530 0 R -531 0 R -532 0 R -533 0 R -534 0 R -535 0 R -536 0 R -537 0 R -538 0 R -539 0 R -540 0 R -541 0 R -542 0 R -543 0 R -544 0 R -545 0 R -546 0 R -547 0 R -548 0 R -549 0 R -550 0 R -551 0 R -552 0 R -553 0 R -554 0 R -555 0 R -556 0 R -557 0 R -558 0 R -559 0 R -560 0 R -561 0 R -562 0 R -563 0 R -564 0 R -565 0 R -566 0 R -567 0 R -568 0 R -569 0 R -570 0 R -571 0 R -572 0 R -573 0 R]endobj -575 0 obj<>endobj -576 0 obj<>endobj -577 0 obj<>endobj -578 0 obj<>endobj -579 0 obj<>endobj -580 0 obj<>endobj -581 0 obj<>endobj -582 0 obj<>endobj -583 0 obj<>endobj -584 0 obj<>endobj -585 0 obj<>endobj -586 0 obj<>endobj -587 0 obj<>endobj -588 0 obj<>endobj -589 0 obj<>endobj -590 0 obj<>endobj -591 0 obj<>endobj -592 0 obj<>endobj -593 0 obj<>endobj -594 0 obj<>endobj -595 0 obj<>endobj -596 0 obj<>endobj -597 0 obj<>endobj -598 0 obj<>endobj -599 0 obj<>endobj -600 0 obj<>endobj -601 0 obj<>endobj -602 0 obj<>endobj -603 0 obj<>endobj -604 0 obj<>endobj -605 0 obj<>endobj -606 0 obj<>endobj -607 0 obj<>endobj -608 0 obj<>endobj -609 0 obj<>endobj -610 0 obj[575 0 R -576 0 R -577 0 R -578 0 R -579 0 R -580 0 R -581 0 R -582 0 R -583 0 R -584 0 R -585 0 R -586 0 R -587 0 R -588 0 R -589 0 R -590 0 R -591 0 R -592 0 R -593 0 R -594 0 R -595 0 R -596 0 R -597 0 R -598 0 R -599 0 R -600 0 R -601 0 R -602 0 R -603 0 R -604 0 R -605 0 R -606 0 R -607 0 R -608 0 R -609 0 R]endobj -611 0 obj<>endobj -612 0 obj<>endobj -613 0 obj<>endobj -614 0 obj<>endobj -615 0 obj<>endobj -616 0 obj[612 0 R -613 0 R -614 0 R -615 0 R]endobj -617 0 obj<>endobj -618 0 obj<>endobj -619 0 obj[617 0 R -618 0 R]endobj -620 0 obj<>endobj -621 0 obj<>endobj -622 0 obj<>endobj -623 0 obj<>endobj -624 0 obj<>endobj -625 0 obj<>endobj -626 0 obj<>endobj -627 0 obj<>endobj -628 0 obj<>endobj -629 0 obj<>endobj -630 0 obj<>endobj -631 0 obj<>endobj -632 0 obj<>endobj -633 0 obj<>endobj -634 0 obj<>endobj -635 0 obj<>endobj -636 0 obj[621 0 R -623 0 R -625 0 R -627 0 R -629 0 R -631 0 R -633 0 R -635 0 R]endobj -637 0 obj<>endobj -638 0 obj<>endobj -639 0 obj<>endobj -640 0 obj<>endobj -641 0 obj[638 0 R -640 0 R]endobj -642 0 obj<>endobj -643 0 obj<>endobj -644 0 obj<>endobj -645 0 obj<>endobj -646 0 obj<>endobj -647 0 obj<>endobj -648 0 obj<>endobj -649 0 obj<>endobj -650 0 obj<>endobj -651 0 obj<>endobj -652 0 obj<>endobj -653 0 obj<>endobj -654 0 obj<>endobj -655 0 obj<>endobj -656 0 obj[643 0 R -645 0 R -647 0 R -649 0 R -651 0 R -653 0 R -655 0 R]endobj -657 0 obj<>endobj -658 0 obj<>endobj -659 0 obj[657 0 R -658 0 R]endobj -660 0 obj<>endobj -661 0 obj<>endobj -662 0 obj[661 0 R]endobj -663 0 obj<>endobj -664 0 obj<>endobj -665 0 obj<>endobj -666 0 obj<>endobj -667 0 obj[664 0 R -666 0 R]endobj -668 0 obj<>endobj -669 0 obj<>endobj -670 0 obj<>endobj -671 0 obj<>endobj -672 0 obj[669 0 R -671 0 R]endobj -673 0 obj<>endobj -674 0 obj<>endobj -675 0 obj<>endobj -676 0 obj<>endobj -677 0 obj<>endobj -678 0 obj<>endobj -679 0 obj<>endobj -680 0 obj<>endobj -681 0 obj<>endobj -682 0 obj<>endobj -683 0 obj<>endobj -684 0 obj<>endobj -685 0 obj<>endobj -686 0 obj<>endobj -687 0 obj<>endobj -688 0 obj<>endobj -689 0 obj<>endobj -690 0 obj<>endobj -691 0 obj<>endobj -692 0 obj<>endobj -693 0 obj<>endobj -694 0 obj<>endobj -695 0 obj<>endobj -696 0 obj<>endobj -697 0 obj<>endobj -698 0 obj<>endobj -699 0 obj<>endobj -700 0 obj<>endobj -701 0 obj<>endobj -702 0 obj<>endobj -703 0 obj<>endobj -704 0 obj<>endobj -705 0 obj<>endobj -706 0 obj<>endobj -707 0 obj<>endobj -708 0 obj<>endobj -709 0 obj<>endobj -710 0 obj<>endobj -711 0 obj<>endobj -712 0 obj<>endobj -713 0 obj<>endobj -714 0 obj<>endobj -715 0 obj[674 0 R -676 0 R -678 0 R -680 0 R -682 0 R -684 0 R -686 0 R -688 0 R -690 0 R -692 0 R -694 0 R -696 0 R -698 0 R -700 0 R -702 0 R -704 0 R -706 0 R -708 0 R -710 0 R -712 0 R -713 0 R -714 0 R]endobj -716 0 obj<>endobj -717 0 obj[716 0 R]endobj -718 0 obj<>endobj -719 0 obj<>endobj -720 0 obj[719 0 R]endobj -721 0 obj<>endobj -722 0 obj<>endobj -723 0 obj<>endobj -724 0 obj[722 0 R -723 0 R]endobj -725 0 obj<>endobj -726 0 obj<>endobj -727 0 obj[726 0 R]endobj -728 0 obj<>endobj -729 0 obj<>endobj -730 0 obj<>endobj -731 0 obj[728 0 R -729 0 R -730 0 R]endobj -732 0 obj<>endobj -733 0 obj<>endobj -734 0 obj<>endobj -735 0 obj<>endobj -736 0 obj<>endobj -737 0 obj<>endobj -738 0 obj<>endobj -739 0 obj<>endobj -740 0 obj[733 0 R -735 0 R -737 0 R -739 0 R]endobj -741 0 obj<>endobj -742 0 obj<>endobj -743 0 obj<>endobj -744 0 obj<>endobj -745 0 obj<>endobj -746 0 obj<>endobj -747 0 obj<>endobj -748 0 obj<>endobj -749 0 obj<>endobj -750 0 obj<>endobj -751 0 obj[742 0 R -744 0 R -746 0 R -748 0 R -750 0 R]endobj -752 0 obj<>endobj -753 0 obj<>endobj -754 0 obj<>endobj -755 0 obj<>endobj -756 0 obj<>endobj -757 0 obj<>endobj -758 0 obj<>endobj -759 0 obj<>endobj -760 0 obj<>endobj -761 0 obj<>endobj -762 0 obj[753 0 R -755 0 R -757 0 R -759 0 R -761 0 R]endobj -763 0 obj<>endobj -764 0 obj<>endobj -765 0 obj<>endobj -766 0 obj<>endobj -767 0 obj<>endobj -768 0 obj<>endobj -769 0 obj[764 0 R -766 0 R -768 0 R]endobj -770 0 obj<>endobj -771 0 obj<>endobj -772 0 obj<>endobj -773 0 obj<>endobj -774 0 obj<>endobj -775 0 obj<>endobj -776 0 obj<>endobj -777 0 obj<>endobj -778 0 obj<>endobj -779 0 obj<>endobj -780 0 obj[771 0 R -773 0 R -775 0 R -777 0 R -779 0 R]endobj -781 0 obj<>endobj -782 0 obj<>endobj -783 0 obj<>endobj -784 0 obj<>endobj -785 0 obj[782 0 R -784 0 R]endobj -786 0 obj<>endobj -787 0 obj<>endobj -788 0 obj<>endobj -789 0 obj<>endobj -790 0 obj<>endobj -791 0 obj<>endobj -792 0 obj<>endobj -793 0 obj<>endobj -794 0 obj[787 0 R -789 0 R -791 0 R -793 0 R]endobj -795 0 obj<>endobj -796 0 obj<>endobj -797 0 obj[796 0 R]endobj -798 0 obj<>endobj -799 0 obj<>endobj -800 0 obj[799 0 R]endobj -801 0 obj<>endobj -802 0 obj<>endobj -803 0 obj[802 0 R]endobj -804 0 obj<>endobj -805 0 obj<>endobj -806 0 obj<>endobj -807 0 obj<>endobj -808 0 obj<>endobj -809 0 obj<>endobj -810 0 obj<>endobj -811 0 obj<>endobj -812 0 obj<>endobj -813 0 obj<>endobj -814 0 obj<>endobj -815 0 obj<>endobj -816 0 obj[805 0 R -807 0 R -809 0 R -811 0 R -813 0 R -815 0 R]endobj -817 0 obj<>endobj -818 0 obj<>endobj -819 0 obj[818 0 R]endobj -820 0 obj<>endobj -821 0 obj<>endobj -822 0 obj<>endobj -823 0 obj<>endobj -824 0 obj<>endobj -825 0 obj<>endobj -826 0 obj<>endobj -827 0 obj<>endobj -828 0 obj[821 0 R -823 0 R -825 0 R -827 0 R]endobj -829 0 obj<>endobj -830 0 obj<>endobj -831 0 obj<>endobj -832 0 obj<>endobj -833 0 obj<>endobj -834 0 obj<>endobj -835 0 obj[830 0 R -832 0 R -834 0 R]endobj -836 0 obj<>endobj -837 0 obj<>endobj -838 0 obj[837 0 R]endobj -839 0 obj<>endobj -840 0 obj<>endobj -841 0 obj[840 0 R]endobj -842 0 obj<>endobj -843 0 obj<>endobj -844 0 obj[843 0 R]endobj -845 0 obj<>endobj -846 0 obj<>endobj -847 0 obj<>endobj -848 0 obj<>endobj -849 0 obj<>endobj -850 0 obj<>endobj -851 0 obj[846 0 R -848 0 R -850 0 R]endobj -852 0 obj<>endobj -853 0 obj<>endobj -854 0 obj<>endobj -855 0 obj<>endobj -856 0 obj<>endobj -857 0 obj<>endobj -858 0 obj<>endobj -859 0 obj<>endobj -860 0 obj<>endobj -861 0 obj<>endobj -862 0 obj[853 0 R -855 0 R -857 0 R -859 0 R -861 0 R]endobj -863 0 obj<>endobj -864 0 obj<>endobj -865 0 obj<>endobj -866 0 obj<>endobj -867 0 obj<>endobj -868 0 obj<>endobj -869 0 obj<>endobj -870 0 obj<>endobj -871 0 obj[864 0 R -866 0 R -868 0 R -870 0 R]endobj -872 0 obj<>endobj -873 0 obj<>endobj -874 0 obj<>endobj -875 0 obj<>endobj -876 0 obj[873 0 R -875 0 R]endobj -877 0 obj<>endobj -878 0 obj<>endobj -879 0 obj<>endobj -880 0 obj<>endobj -881 0 obj[878 0 R -880 0 R]endobj -882 0 obj<>endobj -883 0 obj<>endobj -884 0 obj<>endobj -885 0 obj<>endobj -886 0 obj[883 0 R -885 0 R]endobj -887 0 obj<>endobj -888 0 obj<>endobj -889 0 obj[888 0 R]endobj -890 0 obj<>endobj -891 0 obj<>endobj -892 0 obj<>endobj -893 0 obj<>endobj -894 0 obj<>endobj -895 0 obj<>endobj -896 0 obj[891 0 R -893 0 R -895 0 R]endobj -897 0 obj<>endobj -898 0 obj<>endobj -899 0 obj[897 0 R -898 0 R]endobj -900 0 obj<>endobj -901 0 obj<>endobj -902 0 obj[901 0 R]endobj -903 0 obj<>endobj -904 0 obj<>endobj -905 0 obj[904 0 R]endobj -906 0 obj<>endobj -907 0 obj<>endobj -908 0 obj[907 0 R]endobj -909 0 obj<>endobj -910 0 obj<>endobj -911 0 obj<>endobj -912 0 obj<>endobj -913 0 obj<>endobj -914 0 obj<>endobj -915 0 obj<>endobj -916 0 obj<>endobj -917 0 obj[910 0 R -912 0 R -914 0 R -916 0 R]endobj -918 0 obj<>endobj -919 0 obj<>endobj -920 0 obj<>endobj -921 0 obj<>endobj -922 0 obj[919 0 R -921 0 R]endobj -923 0 obj<>endobj -924 0 obj<>endobj -925 0 obj<>endobj -926 0 obj<>endobj -927 0 obj<>endobj -928 0 obj<>endobj -929 0 obj<>endobj -930 0 obj<>endobj -931 0 obj<>endobj -932 0 obj<>endobj -933 0 obj[924 0 R -926 0 R -928 0 R -930 0 R -932 0 R]endobj -934 0 obj<>endobj -935 0 obj<>endobj -936 0 obj<>endobj -937 0 obj<>endobj -938 0 obj<>endobj -939 0 obj<>endobj -940 0 obj<>endobj -941 0 obj<>endobj -942 0 obj[935 0 R -937 0 R -939 0 R -941 0 R]endobj -943 0 obj<>endobj -944 0 obj<>endobj -945 0 obj[944 0 R]endobj -946 0 obj<>endobj -947 0 obj<>endobj -948 0 obj<>endobj -949 0 obj<>endobj -950 0 obj<>endobj -951 0 obj<>endobj -952 0 obj[947 0 R -949 0 R -951 0 R]endobj -953 0 obj<>endobj -954 0 obj[953 0 R]endobj -955 0 obj<>endobj -956 0 obj<>endobj -957 0 obj<>endobj -958 0 obj<>endobj -959 0 obj[956 0 R -958 0 R]endobj -960 0 obj<>endobj -961 0 obj<>endobj -962 0 obj<>endobj -963 0 obj<>endobj -964 0 obj<>endobj -965 0 obj<>endobj -966 0 obj<>endobj -967 0 obj<>endobj -968 0 obj<>endobj -969 0 obj<>endobj -970 0 obj<>endobj -971 0 obj<>endobj -972 0 obj<>endobj -973 0 obj<>endobj -974 0 obj<>endobj -975 0 obj<>endobj -976 0 obj[961 0 R -963 0 R -965 0 R -967 0 R -969 0 R -971 0 R -973 0 R -975 0 R]endobj -977 0 obj<>endobj -978 0 obj<>endobj -979 0 obj<>endobj -980 0 obj<>endobj -981 0 obj[978 0 R -980 0 R]endobj -982 0 obj<>endobj -983 0 obj<>endobj -984 0 obj<>endobj -985 0 obj<>endobj -986 0 obj<>endobj -987 0 obj<>endobj -988 0 obj<>endobj -989 0 obj[983 0 R -985 0 R -987 0 R -988 0 R]endobj -990 0 obj<>endobj -991 0 obj<>endobj -992 0 obj<>endobj -993 0 obj<>endobj -994 0 obj<>endobj -995 0 obj<>endobj -996 0 obj<>endobj -997 0 obj<>endobj -998 0 obj<>endobj -999 0 obj<>endobj -1000 0 obj<>endobj -1001 0 obj<>endobj -1002 0 obj<>endobj -1003 0 obj<>endobj -1004 0 obj<>endobj -1005 0 obj<>endobj -1006 0 obj<>endobj -1007 0 obj<>endobj -1008 0 obj<>endobj -1009 0 obj<>endobj -1010 0 obj<>endobj -1011 0 obj<>endobj -1012 0 obj<>endobj -1013 0 obj<>endobj -1014 0 obj<>endobj -1015 0 obj<>endobj -1016 0 obj<>endobj -1017 0 obj<>endobj -1018 0 obj<>endobj -1019 0 obj<>endobj -1020 0 obj<>endobj -1021 0 obj<>endobj -1022 0 obj<>endobj -1023 0 obj<>endobj -1024 0 obj<>endobj -1025 0 obj<>endobj -1026 0 obj<>endobj -1027 0 obj<>endobj -1028 0 obj<>endobj -1029 0 obj<>endobj -1030 0 obj<>endobj -1031 0 obj<>endobj -1032 0 obj<>endobj -1033 0 obj<>endobj -1034 0 obj<>endobj -1035 0 obj<>endobj -1036 0 obj<>endobj -1037 0 obj<>endobj -1038 0 obj<>endobj -1039 0 obj<>endobj -1040 0 obj<>endobj -1041 0 obj<>endobj -1042 0 obj<>endobj -1043 0 obj<>endobj -1044 0 obj<>endobj -1045 0 obj<>endobj -1046 0 obj<>endobj -1047 0 obj<>endobj -1048 0 obj<>endobj -1049 0 obj<>endobj -1050 0 obj<>endobj -1051 0 obj<>endobj -1052 0 obj<>endobj -1053 0 obj<>endobj -1054 0 obj<>endobj -1055 0 obj<>endobj -1056 0 obj<>endobj -1057 0 obj<>endobj -1058 0 obj<>endobj -1059 0 obj<>endobj -1060 0 obj<>endobj -1061 0 obj<>endobj -1062 0 obj<>endobj -1063 0 obj<>endobj -1064 0 obj<>endobj -1065 0 obj<>endobj -1066 0 obj<>endobj -1067 0 obj<>endobj -1068 0 obj<>endobj -1069 0 obj<>endobj -1070 0 obj<>endobj -1071 0 obj<>endobj -1072 0 obj<>endobj -1073 0 obj<>endobj -1074 0 obj<>endobj -1075 0 obj<>endobj -1076 0 obj<>endobj -1077 0 obj<>endobj -1078 0 obj<>endobj -1079 0 obj<>endobj -1080 0 obj<>endobj -1081 0 obj<>endobj -1082 0 obj<>endobj -1083 0 obj<>endobj -1084 0 obj<>endobj -1085 0 obj<>endobj -1086 0 obj<>endobj -1087 0 obj<>endobj -1088 0 obj<>endobj -1089 0 obj<>endobj -1090 0 obj<>endobj -1091 0 obj<>endobj -1092 0 obj<>endobj -1093 0 obj<>endobj -1094 0 obj<>endobj -1095 0 obj<>endobj -1096 0 obj<>endobj -1097 0 obj<>endobj -1098 0 obj<>endobj -1099 0 obj<>endobj -1100 0 obj<>endobj -1101 0 obj<>endobj -1102 0 obj<>endobj -1103 0 obj<>endobj -1104 0 obj<>endobj -1105 0 obj<>endobj -1106 0 obj<>endobj -1107 0 obj<>endobj -1108 0 obj<>endobj -1109 0 obj<>endobj -1110 0 obj<>endobj -1111 0 obj<>endobj -1112 0 obj<>endobj -1113 0 obj<>endobj -1114 0 obj<>endobj -1115 0 obj<>endobj -1116 0 obj<>endobj -1117 0 obj<>endobj -1118 0 obj<>endobj -1119 0 obj<>endobj -1120 0 obj<>endobj -1121 0 obj<>endobj -1122 0 obj<>endobj -1123 0 obj<>endobj -1124 0 obj<>endobj -1125 0 obj<>endobj -1126 0 obj<>endobj -1127 0 obj<>endobj -1128 0 obj<>endobj -1129 0 obj<>endobj -1130 0 obj<>endobj -1131 0 obj<>endobj -1132 0 obj<>endobj -1133 0 obj<>endobj -1134 0 obj<>endobj -1135 0 obj<>endobj -1136 0 obj<>endobj -1137 0 obj<>endobj -1138 0 obj<>endobj -1139 0 obj<>endobj -1140 0 obj<>endobj -1141 0 obj<>endobj -1142 0 obj<>endobj -1143 0 obj<>endobj -1144 0 obj<>endobj -1145 0 obj<>endobj -1146 0 obj<>endobj -1147 0 obj<>endobj -1148 0 obj<>endobj -1149 0 obj<>endobj -1150 0 obj<>endobj -1151 0 obj<>endobj -1152 0 obj<>endobj -1153 0 obj<>endobj -1154 0 obj<>endobj -1155 0 obj<>endobj -1156 0 obj<>endobj -1157 0 obj<>endobj -1158 0 obj<>endobj -1159 0 obj<>endobj -1160 0 obj<>endobj -1161 0 obj<>endobj -1162 0 obj<>endobj -1163 0 obj<>endobj -1164 0 obj<>endobj -1165 0 obj<>endobj -1166 0 obj<>endobj -1167 0 obj<>endobj -1168 0 obj<>endobj -1169 0 obj<>endobj -1170 0 obj<>endobj -1171 0 obj<>endobj -1172 0 obj<>endobj -1173 0 obj<>endobj -1174 0 obj<>endobj -1175 0 obj<>endobj -1176 0 obj<>endobj -1177 0 obj<>endobj -1178 0 obj<>endobj -1179 0 obj<>endobj -1180 0 obj<>endobj -1181 0 obj<>endobj -1182 0 obj<>endobj -1183 0 obj<>endobj -1184 0 obj<>endobj -1185 0 obj<>endobj -1186 0 obj<>endobj -1187 0 obj<>endobj -1188 0 obj<>endobj -1189 0 obj<>endobj -1190 0 obj<>endobj -1191 0 obj<>endobj -1192 0 obj<>endobj -1193 0 obj<>endobj -1194 0 obj<>endobj -1195 0 obj<>endobj -1196 0 obj<>endobj -1197 0 obj<>endobj -1198 0 obj<>endobj -1199 0 obj<>endobj -1200 0 obj<>endobj -1201 0 obj<>endobj -1202 0 obj<>endobj -1203 0 obj<>endobj -1204 0 obj<>endobj -1205 0 obj<>endobj -1206 0 obj<>endobj -1207 0 obj<>endobj -1208 0 obj<>endobj -1209 0 obj<>endobj -1210 0 obj<>endobj -1211 0 obj<>endobj -1212 0 obj<>endobj -1213 0 obj<>endobj -1214 0 obj<>endobj -1215 0 obj<>endobj -1216 0 obj<>endobj -1217 0 obj<>endobj -1218 0 obj<>endobj -1219 0 obj<>endobj -1220 0 obj<>endobj -1221 0 obj<>endobj -1222 0 obj<>endobj -1223 0 obj<>endobj -1224 0 obj<>endobj -1225 0 obj<>endobj -1226 0 obj<>endobj -1227 0 obj<>endobj -1228 0 obj<>endobj -1229 0 obj<>endobj -1230 0 obj<>endobj -1231 0 obj<>endobj -1232 0 obj<>endobj -1233 0 obj<>endobj -1234 0 obj<>endobj -1235 0 obj<>endobj -1236 0 obj<>endobj -1237 0 obj<>endobj -1238 0 obj<>endobj -1239 0 obj<>endobj -1240 0 obj<>endobj -1241 0 obj<>endobj -1242 0 obj<>endobj -1243 0 obj<>endobj -1244 0 obj<>endobj -1245 0 obj<>endobj -1246 0 obj<>endobj -1247 0 obj<>endobj -1248 0 obj<>endobj -1249 0 obj<>endobj -1250 0 obj<>endobj -1251 0 obj<>endobj -1252 0 obj<>endobj -1253 0 obj<>endobj -1254 0 obj<>endobj -1255 0 obj<>endobj -1256 0 obj<>endobj -1257 0 obj<>endobj -1258 0 obj<>endobj -1259 0 obj<>endobj -1260 0 obj<>endobj -1261 0 obj<>endobj -1262 0 obj<>endobj -1263 0 obj<>endobj -1264 0 obj<>endobj -1265 0 obj<>endobj -1266 0 obj<>endobj -1267 0 obj<>endobj -1268 0 obj<>endobj -1269 0 obj<>endobj -1270 0 obj<>endobj -1271 0 obj<>endobj -1272 0 obj<>endobj -1273 0 obj<>endobj -1274 0 obj<>endobj -1275 0 obj<>endobj -1276 0 obj<>endobj -1277 0 obj<>endobj -1278 0 obj<>endobj -1279 0 obj<>endobj -1280 0 obj<>endobj -1281 0 obj<>endobj -1282 0 obj<>endobj -1283 0 obj<>endobj -1284 0 obj<>endobj -1285 0 obj<>endobj -1286 0 obj<>endobj -1287 0 obj<>endobj -1288 0 obj<>endobj -1289 0 obj<>endobj -1290 0 obj<>endobj -1291 0 obj<>endobj -1292 0 obj<>endobj -1293 0 obj<>endobj -1294 0 obj<>endobj -1295 0 obj<>endobj -1296 0 obj<>endobj -1297 0 obj<>endobj -1298 0 obj<>endobj -1299 0 obj<>endobj -1300 0 obj<>endobj -1301 0 obj<>endobj -1302 0 obj<>endobj -1303 0 obj<>endobj -1304 0 obj<>endobj -1305 0 obj<>endobj -1306 0 obj<>endobj -1307 0 obj<>endobj -1308 0 obj<>endobj -1309 0 obj<>endobj -1310 0 obj<>endobj -1311 0 obj<>endobj -1312 0 obj<>endobj -1313 0 obj<>endobj -1314 0 obj<>endobj -1315 0 obj<>endobj -1316 0 obj<>endobj -1317 0 obj<>endobj -1318 0 obj<>endobj -1319 0 obj<>endobj -1320 0 obj<>endobj -1321 0 obj<>endobj -1322 0 obj<>endobj -1323 0 obj<>endobj -1324 0 obj<>endobj -1325 0 obj<>endobj -1326 0 obj<>endobj -1327 0 obj<>endobj -1328 0 obj<>endobj -1329 0 obj<>endobj -1330 0 obj<>endobj -1331 0 obj<>endobj -1332 0 obj<>endobj -1333 0 obj<>endobj -1334 0 obj<>endobj -1335 0 obj<>endobj -1336 0 obj<>endobj -1337 0 obj<>endobj -1338 0 obj<>endobj -1339 0 obj<>endobj -1340 0 obj<>endobj -1341 0 obj<>endobj -1342 0 obj<>endobj -1343 0 obj<>endobj -1344 0 obj<>endobj -1345 0 obj<>endobj -1346 0 obj<>endobj -1347 0 obj<>endobj -1348 0 obj<>endobj -1349 0 obj<>endobj -1350 0 obj<>endobj -1351 0 obj<>endobj -1352 0 obj<>endobj -1353 0 obj<>endobj -1354 0 obj<>endobj -1355 0 obj<>endobj -1356 0 obj<>endobj -1357 0 obj<>endobj -1358 0 obj<>endobj -1359 0 obj<>endobj -1360 0 obj<>endobj -1361 0 obj<>endobj -1362 0 obj<>endobj -1363 0 obj<>endobj -1364 0 obj<>endobj -1365 0 obj<>endobj -1366 0 obj<>endobj -1367 0 obj<>endobj -1368 0 obj<>endobj -1369 0 obj<>endobj -1370 0 obj<>endobj -1371 0 obj<>endobj -1372 0 obj<>endobj -1373 0 obj<>endobj -1374 0 obj<>endobj -1375 0 obj<>endobj -1376 0 obj<>endobj -1377 0 obj<>endobj -1378 0 obj<>endobj -1379 0 obj<>endobj -1380 0 obj<>endobj -1381 0 obj<>endobj -1382 0 obj<>endobj -1383 0 obj<>endobj -1384 0 obj<>endobj -1385 0 obj<>endobj -1386 0 obj<>endobj -1387 0 obj<>endobj -1388 0 obj<>/XObject<<>>>>>>endobj -1389 0 obj<>stream -x+2T0BCs#c3\..}7K#4K=3cS`g`NvurT(JM.QpO.M+I, r -endstream -endobj -1390 0 obj<>/XObject<<>>>>/Annots 59 0 R>>endobj -1391 0 obj<>stream -x[ے}W-rUn劤Xd_%H`9=3 lk/I3螾LO'..$+t2/~_2oM5ʃurMR#M -7)&͊IIb@4 \ -auŤ^Ni-[ʊB~r"C -IGV%y`Lix80p$]()JV^3ЁkrJʤeΎ!0I= #g &ͧ#R&EdR:($Ŵ+f.y@\Sq.@yιs$w4dhc PMRSt+g w TIeŃl$Y `%)3MN)S)˓մf~y \8~8@i?!lHZL9,a ۤieEʩ3*$FIDEn3i @HZLR1RbUFFՙ `[y/2P='", $!ezkU"g :J$- {â Y'IY0'Y%i@$k3Ѕh9!.f8z$-&Us2-5lM۟a 26xeEoq2DWƏtyIP`-8.5aQ`RYn{-یg_3[ fXJTXQL3c HVq  - DΧbdC-oXN)^Me$%55QbeeR -IN9K!m$iJyy@ {rqOB DZ  (Y69ό578Tb)dX53elIfXv?x҇E@pEERN!8 SrsꃟŠ i @L ,3ǧr -x)w計f)r9s⿣ 7G r,: 3"ajzHo 30|9 2#1 {1{{ldv0q'%l~n*ywmQG==sz_ƏɿvqX~`nwRdBNNˣzح -h|9Wz=f|CPuktVOz,0^iÄ~FrVy]߯~%},o_D-:?7F(*8ُHF{ 0' l&!W~hzmd!~yS; _~UI'Ӳ:;od#J^=2Ŀ8acM~h;R{`yEU:<&x(I3nEHyE|8+bF#zߢ*y'|́<s$ڳu@@N6E*/>^-w/W9uf -6(}[! --C=> --ڤF -Ynv n ->u=Nh3=tBqSVȡ52TqrEigwt^CâecU;/*ѽHP׷+о%@W}DDyU$MJ5y.Zl] (!.ݟ| ӏg'|Rĉ]$Z4VsI(5vˇ\nm-P@$JNonV5{/WfyeGXx[d\mq~27nظ {jUJp-^Q9<2hO[ޟ5B%WG -Gg{ -ߟ?KW 9kw KvwlEs4Б" l37f\T!6p -').&lW臏 P^"^}Fl!jvE˩7o^E(Nhj$۸/> [Q6\AD?WZ܉Uˡ߲FV<_v-;'bNj kh͋+OOKM[~ܸH3_WK2dO5g[è~~wUQiԁG?TBO#/I} Dv|H̩JtQ!t4-ue 2>6/(l5zfhex_Iy}~W}NF~ 7aVuWq7pQJ%2Cw<M -![0xj&r;wEqWw\D5pgGԷ_6`;-(zm~ 9D8iUF K|/'ͻs'iAWgx〠1Z BڠNU(l2FtG,΅mܳN+8BNx;ˠE R;{{~ƞ/bTBG%G!Zfh7yސc{;~ѯi -ˎo9>hg@DA66Jj΅ӹ?P~I3|o=xGwHż!k7ɂK5u&$kF/G{^l ~h7{\,G {*[Sc팳a0`ӝx(tpБ~ͥ-ޡP^/>̝To*bO:wDNJϗZå}Y=Qz-/!-sk3Q<ޭ]ߝZQvSqW/N2FIf)lA2}ZvZQ0VXC"$ᓮZrIZ+$\+X^Ϟq1endstream -endobj -1392 0 obj<>/XObject<<>>>>/Annots 103 0 R>>endobj -1393 0 obj<>stream -x[rG}WL*2sᐏegK1E[LxQH*> (gXUt7Fh(PtUQOA9.KK1if纨g8yhԍsp]i ũ[ ո8%qY9eQC欪$)&ITr6n86.rӆBG& rNsi ֲ80:p2@60rͤǐBf: vVS6M \/L&sӘn tؖ-#c=ۊXf846Vթ\:LȅpLzL/0Ց-6a$1flXt `P(TdQ=e:tO k\$`ss-d:;R zBՕ)jUqR) -<)Fz }0 cbHj,Gˉd'nʔf ,br"A0h.ؒCd -Ĥdd5sudd S,i=K -8j&٣)<SVA1XֱawV+qN9.pN8 9(q[ RҐ0%miMġgU*orhCdOs4S&! D8c -+C=lYK9VD b`Y1Xxeqբ[4rp`&= E2a?hJ-9v\UhzRA^4qzTӢwC=+{j.*󩶰E#P+P2ԔĆzLMӱeLw81|qr s0O|q!T=<6c ܱ6B#Wz g: x b$6嘑S6piNM92 R0#F.̤ǐ&<: eYXJv0/ g'2,ndp7jRACLmC.ytqpjg2gC8T:y=a8 R.\#˿L92 8499PqT6N@!w@d)"SBH489 9skqs3' -ht}W4c! -31w,ܼaaġYM_MZ=`qx{upu!փԫUd=,D"n򿪢h#8@jOA1jh䈚VU&WUy+Є'e_ǿ&8:7t D a=gOFk+5G\^\lwGkA$;ʙYN;j"vzWR9Vȼ[^NI7nh{BdJ|y.m~eT8KdE%̪"_?{P1@"fˍDTy MB=;mps'Gz%b9TX̗J7hpa\;EQDegAF2owK+9 - ͎T}__$Joŋ'ϟQ -S$ǥWϳש)o{93)gU ⏺.BdR凓^YnQ󻇍8ڽǻrPܴ%_j&;ė>Wv踘9_C) - k>ڛqcʜ.xI7slwgDH1$wpY: J7MC+cz|t;\ze0|CJ6fӡl7vup.6ruBMfk]Fl/5aNۅT.WF@9Tf8x'$me?5 Ixf,,7CU&ߟkez׫'Sk3kM׵N{ .7 oAm - pEV{2/7e< Mݎ/*o k>gR=6HTcԹrx['im+|Ao*T|k+1[s݉;n>|r"5|oˌ ,WK y!wGr㩤nv}=^IIg~̃wv*^~'11bg-@j2\җpuqX]TN#^o 0[? ~ |"(nk2Q?Z%53$_Q|1ؔJex]ê)np]꯻M{FG1r>~~ke{^އ+?u˿Mrp+S ^yS8՛;yCz/x_uyײQ!x|>է endstream -endobj -1394 0 obj<>/XObject<<>>>>/Annots 146 0 R>>endobj -1395 0 obj<>stream -x͜[Gr+zFCtG8lڒ^Ѧ/ i02뒧8E]Kfefeeh5Y;LG1˿/i7zQ?p7yJ;bv6Nf4SŰl&MvANJa瓳m?hvz`}g -ds8990 -,J\RRn׌.b #Lۘ~kSŦٰ`SD{k[:۸a-@Wagwz h)F]qnQuV̈́ -ތf:b=؁iJ J&HŰlJ(a'3:bX V0,s,ObX|=+L -ŴuVQ2bXW{NK0^E6L wn%`^ k0 `ة K[ 5*Pb[ItoA5状a!+*6ð+j6c`<JÞ7c\,񙥯*e ڳbX=Im뱯lԈlQUa}V- i+5AϊarwX{bXKglҶ9 T9R)}wNS9&P } hobSGڭbX\ K -V-ka1NuM:FRLR1ݲM9[?T1lkF*`5 KX^(+G􉰊a 謒l5 a8< r' TtZ*:ez)mV0̒i+Q x:%.)[L%[9q 3! d^ -RTXenH]QՅnnA%86]s Wa| P.tnM]sP *'NyBe֦aL0ŠiB|RPwYL &d9yaΆM-n|;āM(`l{bJ*A]u9nYkZ/xNS0FQȀ3!âZetU0[1Qهy3A:ŧB*!-G4$%jz2sڂm>4"EKLАQ1 { Dq d"֩b!V0,_daI$X`RZgIL$ *ә`n.;"\Q[9L+MA*eOdbX7D V1,ET*65O+E`KmdaEX(1Z*ؚ+ءDؚ98qڎX`R0J)`X{U(%o 8ѳ`Xf=r]uK[䓹]Ub.ci$j4:)rP+ U4TnP HP9fFX%M1r3[̗.lѯr!ػ3vga@:BٴpD%8nokfh'J Cd;pAB8 -:v.\@8:. j$Q)O%]'vB X?pK. \@&IROW #R. Yr9(S'/<ǣ촜?u0Ͽ~|}m/GO7a?ҊX֚}j7w\|=O4I?Zvo卷&iFm}Dv٫Mѝf~ޕ.m7˵upxNpjGs9߭.MzBo^WryV_pec#T-OMjycjyj:dﻫkUg֘vy ]j} arzn. 0ܪۛ"{EU{|}993:cɑkU?6{z j(;]o} [,%c,OCE5+'%tRmehJ\HRL21jul85Po7oos]Eq%Wiv0=̦u*kxɓ-wXkv0עAyٲ;ނUf g%#}b Z 1'b,B!{rn'>< - {׍$61?֝Ql^iKܻ̃î+HS$t<ڰ07mz{ÂB{͡^=h[s̀s:o]oyhI M}T&_=K,Q)$ؾsë{ݟ*p/!e8P :ˑ! fɑ$ebmՃ_gwʃ9vf{z6Ήޝ9~46dDeK|wHOomnd9~dw6z29RͫP"\ʗtL:l[z^$X#y=&%|aKmb'ک}iQjfAUOmVKe;{l5G{1nP8} -Um_)GpS{JZax'%آ>哓Qۿ! >6U=i<)Sz?rbk6[#]gv+"˴ZSθ߼~ߥMk̓cu'&^Qq9Gvr\bJ'뻚4WS2c'b97~*~U }K'H㮈okoP~k~,9hydGje[\cg_B}k{؉r*E/=ΰ;sUb)EQЗLo$吴^$E'=(<${y!&zrʇPn}Hw8bS  R/SpM -kdC $ˈv/˛|˵`ףṱ?BխLLd*(\*}竤SyY~885 ʒ^v5L~mz]&2b@ri9bwcY ȵH[+Bzc>HQ""gzC䰮$-~Zs .t`\]Zto]&Q nS%F dlhA54] D' -]R[Aʅ8(vW=H{^|vjf '+(>:nK)uAc(^~qgbbYM]UڗԽߠ=>սQFcևT[{y-p ?ny6X5T 5R uPdPNwۋ%>kr> 9un~pJLB-i;bxcrsG{ѥkqy~YE x-7+\'i-)7uDyˣ=^,Nx <m$mo7듇=p] {;^mSb+ endstream -endobj -1396 0 obj<>/XObject<<>>>>/Annots 189 0 R>>endobj -1397 0 obj<>stream -x[]s[}}Hf*XqƝ:Zʸ3M(?gw$OII;vbY T+ˋBqRM>!AZTp 'md:[kX? -H&1KY2,`b Z-cUcM`L \^䘝:J*E5vCLLXщKm#TΰTG2u:d }ӈo{[8/e nEg mkg cPjJmf@2E\_,aSZE!ހDpH -Gd +⦦fF/ZA[!py.{WHA% Z羨*>h,8XtiEԔ1ؑ$!)&,luaT -\ -Ic mey[T  \$V;H9Y.yJ*29YdH5bUR{ՆڧT 'k˜d Ev @jXG uVm[ -|#ۗB2ƠH䦦E$q{b b3,r -z61J.pl+t1-s)5e dX`D0qޖXXB"qk`77S.:aD2HEX¢l'm 9&;)pAD2N"9k"Ŷpx lX ytJ/J.Ra"[dY`1ڠC;X(A'`/dn5uV-@6r&EfΊ9FF!6 A2r\;GxN2Rѳ&*8P3q'!$NB7 \Wx'KCu ;"tI3]$k#0MΚ -.pF8GP9^jCN!1XFu'I3H%YJn%JLĐCD2VRXǢX¢deRό`m;oK,OLg`f=e +H)$t1XL6yjED+NLA](qXH$cB3gE:f V?Ϊ9O@ɦ!6˗B26AY;b(3Jޖ1X,1XD㚲Նhh)+NB/T4C89!"-a1D-a3k`NI $n9GPE -\e,KnƒˀXYY4pzGP0’qX OM4Y_P -\i'k'":@\g @KX -5n^ˑA$EB2ƠXwg X뿥WGha.Q94YJRD 8s(O&$G\%sA9U\kAqwR<0vKASn9v BL_ApQᮡv<^[+wR 09bԟ3uP%k%wv!0' 8jq.= 07K*4&Ssߤk9'!A~X?[P.GۅQx꽻}i\71n'of6fiq$*#J/rlJDC6ߨ* UnmʑjLI /n8B~TO:EPfr6,Wr|jA?H xRw_ ˷9OqGkg[xjwsx}X2b0LizNgEnlZG#{H%GȓJƹ*:bJ~a:e!gq13=l"}w< vg q;|z~,&/xf̉S#n]?mG`:AA`W. {ذ |zC -nU:!`NFE>u(/?:R[_zM,h iJ?:q{*bLpܹfq5-AMc4ר T琽L4&pyOmCm3%Y9]M֊]Ű8⹯x)wKg~"ʏ75^~ē{:El:X3m BQ{\, SZx5#ȫ޽pw|ڭqq:}7":.&$ɶ{׾9dwO.U?Ay ouZNJgG6Bp[ҼўG8YT=2i ^.0fq!\r -?51iE_wR-8]10n|lf;Kꕽ w:]Zc+S{fW>]}c,,SCnaVKx#{5P]rdk?4pBq~F`?Ƃ]VFkzZb)`&uI.RlWxxlxґlv;KO& ->wO{(!#LEL/j^ODp?<8})folVtRJ/&k|^t?.Ǔendstream -endobj -1398 0 obj<>/XObject<<>>>>/Annots 234 0 R>>endobj -1399 0 obj<>stream -x[]w7}ϯxtMs4'}UdQkI,$VN{N;w8@AgE"ʬjY>D>zY5Lng.sp դtˬ1خԮˬ,Q[VulN:eݤðCьl3naª0a+ \hWkj'E8%C|k) ,_R`#=vR65j|;eA4#= +4}%' -@5I\_B&,a`ᩍc&-H0M"GGgFtܚVжsjl JG`"E.:NsXY)Ҙ "4lI&U(1DXb}Щċԩ4rEUp0>NۆNN\0_u*1:-[m:jj`[: |o8 0#F(+SrF23W9t1v'gvRw8.+jF-Qj(F{8CdhRC0r̞gzt{: cP76ضĀ] 0F( - a0 - JR - #xl U8EUHb*uN[pH7bvqTMf촃Juf0Dz̰0"De"r%WIcrͷsjs Vyt+f rKe͑V .# -QsE4h+1Xɗ0b1V<ޣh%@d\pUD%CVcZc^;a`jðNc#v.B9 9bȌs"1XY֬6qɛ$=f' -/znl)-qt"Q>0>ۋ.:L]hEa -3+c=Л #h͸TG.D[#=H c -̬յu"a u[Yj)F+‘+!H# -$,p -jSq c:E~(`na_B݌P}D.CK0XLJSrc=;k1Ǯe)4 Wڊ;.DaM#pȅplPVrPc% n$ QQ)E23 ̃Jat&S9 zw2V(sZm 8ADםx$mQ-2!QA -Bw2 8gqz"3㤳ԮogZcQAPAнVA"zV$q"Hj˔K%yvy .dz.o:{^mݿ.C+LNb;{aq;.>r>>3,-/b~%ow͟7t2>~?9:G-VW?}]cvRt,ӫӕbI_E$buçH{t& obOG34l{;BBv.f*gﶛl+"v/N(ZZm7vL>x~ԠFPa*#t92Λj38#dG_Jټ!AXVNR_N77eH=p#5&CIp¤wgq'D}z{)L6m]>/UNďl[_ˀ!Ꙟov.KN9_ozP0ϧbϿ8}([hx()hb϶_Խ'CB|i1smB]pQ, ! Oӥ(R^D( &us}Ȁh -<0I/nw.L>ڛ& 2XS9~@MB|Km':VGI $4XdF62L>x~Winof+uPc7oÒc|:#&xIw $}xbOC͢^sv(;wh^/n7'^n(L#zKdIޡ5owl˴he̕Ef/w4!S, _)s+ZI~D0qw+4?-͙'󳝠h"Ãƹ f۹y? u;iNda^t FAWw{]3r\y^M>%tu#:?~[0>< @ q~b|? /Ӑ2[RUl0MGKYجCP)N(S -o⎾&d32xpNŲű|YUbEi<;$Lvcm9ϮՂE!GV 5Zj)_WB-݁]6 Oo3yS?ծ4g{Bu⯻|):NSC6L*ZQw߬oEܢa ͏4 Z*(JMV}\. I93QP*)3̆NiyPawGS*G%_i ==r#EP[8vnl b?~Z/kj_ŅdݠfEMpЮ)U!+y_1a=\$,7=ܜG8]cb5aW Kw=Ư@1;+҃2ӴOKe#T>j̔UX X] G}'V -E(V䡱EQ0OG0~J/SCs_!IXKUÙi9|*jՂWւt%4դ:s8됺/faX|iק\J娗r.(qm ^l߷kOWJDDX[an -J"n=Y"zQ?mQ)7/tfiIh>eRt j' Q@3rVz-eV)[IpV)QRŵ;zbA-ʎڇtu^`nx EPE( hpfOp'24a=MEB iX@YİFiG;A9 i/nl)4]oֲ!=ԋ -Iy拼5仩~hPcࢃe(4/M$T(Uߤ-Jx>ԧ=עcgS?뒄_lO?J;g/tjO -9BC"bi5J6R1:7_[+' ڪԎs<>nUn7IGVM36;4P`>|q&Oj덴K\N Wp V _Ɯ7\C^g<պo]`7>s|g9Bendstream -endobj -1400 0 obj<>/XObject<<>>>>/Annots 278 0 R>>endobj -1401 0 obj<>stream -x[ےG}+m 0˚3zf/h#3fu9YUْ»uɬUvGy6l\deMF~O5U.d\du=l"ql nNjK݁,ņV9Y[8d1,,1خv-eɢ iIdtRJ%=[Ԑ7ڳCCʰUgE-nXA(Anx#=-P|S=pV[(c۴Tmkøa8 e= 뮁P5&.H+jձ6:L5Pcu`&nc=kcۍ3; EU9lc=28UtZk%.+XCmձDQ -'E)1UAù7]{(17L3v`kzc8{0l*uÆ18x-6A%= 6OlX:4anX&^Mǒ `L8IIpUD4Hܫ@cPX\FYi+%" xVJc/{D8SAl^)1X\ٰ k%##N$1+UV/͏贉5qb1rGzcaI1/[1&T5mф~Ą'6c,1؂±s4"cj*9cڒ'Xv iQh于* })Ѥ*x1I%$C'eEU[ I ҁ%*2M9sRR|j60rys Tg88L@"RTnnj296qJg5d&IxZ* ڔ^ -UTѢ?Jxq.2cp2@c/tvFc=z  ::`ۦ+HF p6cFwzcYؔ#wM HMU?O -IG)p -В 4gV4 C -y894.q+"ﵞux0υіkuۚnHNA2 ÌlE3r`Q:LE: aJz aƊ8?-70kH*@8ؐ60L.)g:`aR^ɋ[eA*4q2iǫ#W00L -_0'g;S<EPIEx0Jthhm+"RA%N!2O=rb|9*T2e'4Ur163Yq]2Lg1 qH2 +5ܳGO^t`k,a\eW@˛Yz}Zng滋1 -==zr &z ?7o%f[_ fTtnkٯn&j.P 8~E8e4|6}^WBa\^@4Q[oHV,`E_3݌;D 8dzSuZs0Eg̷Q 07:0$zb/z8Ucq0ע#{lb|CIy4~NPgiP_#M3#d\ǖҏfbP8FL0oߥtq:Q:(-L!EնN@Jnt;lޭWQw襶=TV=*L>0AA|P뽣<loge\ -2WCgy;;COxi? Uul13<,W`-E@1 -̊\~"C]o{>8˓FxY)($ۺO(!^|ٮ痻xpGӌ~twR׀/}AqR=̵qVJ Pʢ(1ep -DǸ=!F1\I/ J-jS^D֩?/,dNx3N+! %^t 5=#qicu{/y4Ʃ<4J(/WB=w|b [JƝ -׹S)$޻;)a0] Y G=I4 -R}ay8F@n[Ϧ!$8l9_Tvܼ刓>yTixw{)]\w͜?Fw1 avCXk(! ɷ/Rzsd3 Fǩ`bq -6Ӊ$"j6[OcS\ej|(T #6_ͧfZB6CM*E}1XX~v=;Q-U;);o;bWg?S鋾]9?L8=Uƾ1|O"b/<^i+9 A0y"s994`GV"7{39|Qjvw9]\e9lѯ/0 XNiDY\>C zup^@oka]*o+T[h[=j*nqrF^܈/ISmyOΪ9Q@KQNd%xt=GVfw{Z%RwIj$:݇Qb*{ru~^vW}}&tMJ3M؟pf}ov(=0?[t ֟*]^+/S~X!5؅jo+"+Z7Z矾 O&;x xo6u -/Οz4>nn׼da7u|nέѿendstream -endobj -1402 0 obj<>/XObject<<>>>>/Annots 321 0 R>>endobj -1403 0 obj<>stream -x[r +f8 ~dVي%f;")7"Fc(*}M*Jt氻4@c9JM*2ϏQ'?Г<ʚQ}tud<*Qi8Qڐ-QcY5lSR36+IܬrV@8fg [*CZ 6Fe $Nl1*#C(+)Leuȧ*N\72)(c,YX`7 c Gi(+(Wee'+g*SƍtVXU2nlԤLvF*㹦@,#bY% k0X̲-Kk0ئL!cP08NW@L*(i1<%;`UEp$Xݲ"nI8, -yTW883K&si1آ7$P>X*J>" (aKlċ*KbOZЬZ=DZ4p"5c3!@^'X$qĉW8.IxLaXA9!ML',PD0(Ms,A ĤiIi1؊Z`eIFAXqrbrx]g Y u,XR:qF'+(g_P9YЍKRr0''o1d aL`_a i1-L03YĊWHs&4"jdDu\MIPbY 5` -[5b+3s8 *4!q \=+X(dMmf ,RbhW k0Y!`|+"UI@ (p@T ;"4sTdY!q<,1qƀ(vJ)N:&u8)r - ɢ`+ո1Vs`3 `͒Ȱ@ .j1Xج%9v(5(02bZܐ2P_2G }1` `:t,oLM%1E@ZEQ{ < XDHkxkT@Xgc²EX`%af1M q ?UbŢ0`RH8zlRA$!#3K"`R%- =Me@KUt(f$erD \R`>~%eyQxIsfӢN,khZ,D"QZL"C`eR*ri68Ί~D@Z i3b` VE-&;PɰRa vЙ-AC`R9D H?$@nQbR5'֤/Jy„:G/@x|pPa㒄a: A HR0_`fMk0 ++Kr`qi10wH"xf 3Ek0DB9+K~_eIrN Cx" _bt/^6 -jR/Lbe"[W)[9L봶1o>WRJJH{u}5Rg]$ Gʣ x⺽Fmt-z_1 -~Шc78a/Nzoh0&@ѳ:m|컇e6qw_Vg&Ss?b)Pa-doZz5< Z%$pL8.x/q5] -Yf,yj&O+fWZMQ:E*ntKBAe}Zq6m=zl$|?$)N^:Խz_#D2#?_q%|^wػ=TEop)8YQ7}lƮy17l7*P;UŖ'4CC\;p[9h.M_l>ކm)ʁBlnͻv6kðd$v2駫Ք؇*: -UˊlntKՋzgu-Mo޶cIjdi^CUrɨW+%q}4T].+l&:zXd3^Ϻ <@D -rW@t(G_ˠ45urV;ݴ+pdS2i=U9]`xEQ nߢ #9>Թi G=ĪV[Ϸh/=ikkh4<<i*mWEܵd3tvs+Z"ҭsN|DBOߦ8wL㴱NMB6b6&ӗèW- >H6̤zokk -'/tFU<.NQm>!i\ڿ) 郢AMPsuNJwi3PqT$6&8Zym ݜ㊭d{EYsfzn'NvÍ[lӕ~57bޔ{xV:Īᓡp L7U1%3MI\|9 d>:xuB6JJn$U;람q ;4M?f/kjCl4' f\YQvo+|c持8<,b{ --܎?5u]uėV}kcPzmv٢gP.7w C}O!^E]f$Ozw*G+$Tunun\mˮJ )WjR-OKE4w Cm]Dv!hѾAfﬓgz2w[ZZ IS_;=G*?x|e7tg5>q5n&t.=FB"M->.ߞ1 } CH$uM75;^yg$ r|g5YI| 2 }pv5v7=>M҉q -TzCj>8J*`*6HzC9 98E+ӫ>qg=OJQ~ x.ͻ&Z,V­_^wM4);!:[V.Q7ٚ.Z'HN#.6⫔ᆾ/rOzSJf-Nsķ7=4#>mzcVg6í9{w[voOkJlN>L'oB:lݱ?L7=M -v/_? - - -ߐ?%Ί.Ut֍7s|BK -*nMvgendstream -endobj -1404 0 obj<>/XObject<<>>>>/Annots 366 0 R>>endobj -1405 0 obj<>stream -x[MsWrUawO)lUE1c0tYKPr{-"J۷31==3ߞI%yWϦ)?HOh*I2=spr$5Hh^N-$UL'yx^2d :IHƳmSBB6*G+ `dȱsp`(Mx9q) ` =& 0ت ,NJ6' Uk\:iH&ClXeElY7%8Дl )DJD@BDiwlVY{a=[דڳl`s ->: =ۤ0k0B1{ 6/Fl1زcU:iݨ<TPkxJi1caL]\j%=V+m:7V\W+뱺Xzmqa-y0 3"\,?w`1M`k`_6ar};1YC\RY\fTcr}CX XٸpДlƆ2arn>1غi1U`k`adEy[y Vk0ضYRP= Y/pa*1/$f\ޱø ڨf9vmpAοQ`OCΥ1Wų4RXˤ/?x{:9ֻ~~+Za$4;ɨvorAsfzXO·ͮ{X.vA",hxԖQc-uiMm"|KK)$4HY:&nI-m𗾻b-/7)JBl{T -kHjٰ6 1%6*m^Bn .ng]Gpo5Z5M᰻@;{Ռ=8mr|[fNi0/^쫰=p^~ݰ j̓V?N턯ec~e)K%%F+ub~> -8Űlݚae1_̅y|X_/mz"p8NcX<{!Bj rGUCbc108ni/Z8,:8݌'i|ԗunOo `<.8Z?oqڷOOj|ToCzKo K8WkpO]Hhya]QfBONv+($qL۸{SM(%_U'}ptaխk`wƅ?zT73-(Ɩٰa_x>A|? r6Zʆ[d%˟r%sJ{( -.RPu…m ->ct|M0m}]N3fɞJ{¿|2:X{9S/endstream -endobj -1406 0 obj<>/XObject<<>>>>/Annots 382 0 R>>endobj -1407 0 obj<>stream -xX[oF~ϯ7=SPRQXij& vuΙqH H|3g}rת.TY$r?ӊLU`ޜxPfVY@t_.pi"%ƥ։mJNezNEV"n=/0Y - gyL%K,X9rWmjrEYbmdFBgb`+t`<˛6eB๖9B#j+xWez-)"' jDJ 5ǣEIm R7b^,$;cLɅ쒔A2s K`K:(BI, -U - ˆg%Y]sqr,qK -tRĸ,,7 ~Sѩ?*'O *ˌ֐ae} -W~ױ;u|ʼ~a;  i_1Ef*'%tcnVE}ŧC4;5yf㸏Y]јI=(W8,40X -G.t] qmXA "cMH{PDzVmXb8~Bii>pb`1~9y0guj`h ΫC-vaEG5oB֥_z[Ƽsl#>/XObject<<>>>>/Annots 415 0 R>>endobj -1409 0 obj<>stream -xXrF}Wt%JFLk"GD/~! XTT*tO@%!E ["H Utǫ)^,\okG6xpX20:P<"h7JlQDak(e4Lv3å 6 FAP0xqfޜ„drΤ vlEh5E:X*ȑ2%$$.bib߱A 1UIkMO K(*1LkM((TM˅Mu"&cV?@97)d9NA({9Rc!V -P -E-+/MDs& -9GX.X(n;i@l0؜2Ki|!0E@*DX1olF>!9j 68Vcp`|MY% -R,4BȎUuq`-X&ҝX9]>!DN 0 m0KVs >$1̃\ -Ms[@u'\* 6呢X|k8Vc2kec{tiWA" -c!;Vas0a4*Vay!O -!-|`"O?ωR\9ApYRAǓsPS܂Y9ȥzgSv*EKP8s#JX> e 8 Dq%*AΎSAp%Tp3 8 “q U 8\j%3.{i)xOW/.?4y2쌼1mViU{}jWvnGwFySUPRPw[\osB+FW Mvi ;cGC]?&Yj, ꂺ/sHM#rn)CU& uCc XWWgjD[܃Tϭ'aKqER[C$n~nL5Oú*sͧ_PQУ(ȅCVu^ \ѧ6]3q@発M}U*o in=T^M2{;{jD,K {T-B67iR]UtvN=5Yob>/XObject<<>>>>/Annots 469 0 R>>endobj -1411 0 obj<>stream -xZrF+8>C백yΆ%˖/ !G;JR^o8b"zWW5 ~1<YX5g~b1b6&dŨ8M9S 6[ -[,FQ<-LqAQCQc <%`*& vf - -nB >y,@@ -;[$/bȮbQD0)r!U L4OHf4k,DTh6E,8+yJb>N&P?È!d%94d^`˜>9+F١UlFCfvf YP)bq)"S9f([348L G%S>~G+afcn\M]ޣM}::? [paz.cMCFY5wP=t{۲P7jܔ]]4~~j\}>ݼy(PΰVsWEdm|u[c_uW7em7uWuzWlr]o? \}ܵ8zj{_Fn?`!7u${U(4.Q ~ׇ -]`N[>vSWoJZK\ PH^wݦj]v'{N+pPXcLeⷒ@MZlUhb§M}_c. -)ayUv_yRhۑ9S -:/\{kA >u>$CMr(L.@Ԏcc4oKw|xi7Z'2+Uz/-}60IVm1<ؽ4iwGL -mNBz|?[<ɶK`[hRsјB]43A&ېC^?=<U=b6 %8c쁋rX&[D/z -~S&ưn9Iݎ8& [WO7G -׃f1Yn(O!r~>.|Ӊ+ԇz#.bǹN}-mU{a` -5ºUbH/.u}OYt,UWڍ%6+]6-U<&Mw'XNn;˲GG8^*_9n..\p%`8Gyo<_/E? s~{ٟbendstream -endobj -1412 0 obj<>/XObject<<>>>>/Annots 522 0 R>>endobj -1413 0 obj<>stream -xZKsFWQZQēQYWE^E DBbВ\iLv+UvZ^$n7K]Vb:'O\IʪL%r h.fYcTdY - PR Ӓj9KY'%=*(ɼF'+ E2` . 7c ` jQq4D>Pd3rң9³!bI<$4L'+ yq)%*&"sa-E9 Ns#3 d9V0e +lUecb$.3cQֻ\ػlH\>kXDV0d:Lm -S8}Q`Y?bi`9kYQ*S 7.G/k60)T%\#Y33d+,ˑ4#Y`u^Pb;2Ab& -XU' Ր,(`8 ,VRY`14p9}Hdd# 9XP™1B Í`d,+(ndt1)"iB1 -7k1]Ni6rƀ"+fˑULǚEjȠ\q2#sY0]ΐ ae*V0].z܏ܐ/.׶4sWX`m+8 7)r^f[Ty2Aqȗ/bE +A"7.ì24rJAV1]>V0]dDYp㧚{ N;ΐ,&av:SÙ8 -f@\%OyZYP}pA` ŮDLyDV1ؤb;Y -`8 -+Y%`(N[#lۻbTֲ· `^%23< "csz{Sq4 -+,Fe -YzZҿ\!kp'*%>VTЦΚ"5dI QGh*fbb8KaSZ -CfV0(blw%pl-nv`_ ! ,z.GV0h~?Ŀ`N`]!\HtزXD2?,=b:^vKH pH=>ZŽ - !5dCSX`FW\ X~v%2ł -f#+V?a־DDV14[0#1pSa+,69d}vҎF6Ǔ Xs fMYW UC^qP1hdKa/3ULf#͊9܌Qwٶ̢H!sY0` %V1ؒ{FX`}UW~?=)[x2~P\R 84I. tZ֝9s|*D.Bp8Sή&Le^gbpL,BXÆDh\P~8rœuT:xcqoA!n)pU#g#vصր!Đ-ø#[\\"Jj+L>u%Ns}jv~uWwWj}|z>L2q[}mhXZ4nu}cwn?^9Z-gƮc-dD3~鞺!D}=DVͩ1zjmor׾Ӈ{wu嵮v[;>ru[ovͪ{Qh[ۿ۽[u߶^5+wnnb⾴[<5Mѡfw~x'-?URN [Yqp 3 vfﺧq8ufF޷A^v{ѹ6\oWykaG(_Mkap~TeY:e%R2} >{8hݛC]6\v=8?}ja#ziGS1?PGԟNa<].sGB|koa/6}^xΗb>u52||&Ȫw̻=O!S!Kd|9#ăykapK󸍙/; gu[u,=8G?d~Aw3/?Z}[GXlkKù9Q[4Dָp1X]qI2C"CnVD'-}>/XObject<<>>>>/Annots 574 0 R>>endobj -1415 0 obj<>stream -xY]s|ׯ؇T%yL|O)Yl%G$+HBH@CQUݹwfzfwgOB7?#gn93_NI0sYihN,'AnX5ͣi$M `|[7.J 5l2td[A<F5p)Br"dRxSTųCPPZL-,[Ab=q1b**`„欄 *1, `Q=k0,b5ggFdk1Xdbj>'%GIA"`8g85lSg ;A5PdHXfY0`qĬfMh!ܔ ОT{`&qs=k0bP,4YL}<&A\9r'{B1 ҭaі ʳff5ae&[ >QDZx db'2bp4쎬+s-G $> y I3YGE=k0۲r&b)a%x k0wg1v!q,8޳qS{`ʊVc -G 2:p =k0؂ ԰#[lUT:~,`.)HD Ҽ=+)NƏ(DTF:҇2{ł4YN=k0r2`e|1H6yVEx-l,HE+c|00L. gMeH⬡ʞ5aeLg5l Ұ\y`Ċc}zAHN5Dq̰F`dXVn6pм -@!JkE-k0X -bl0xbnjK -{Y#JY .rbA`8Fg L`eu0 4)BjBCi_c Z)*t6$ `|5UsHE%4Eʲ -2E9dCր?MvGBrļb]jWUW~V퇺Jw]/owQCW/v^prm͢7B -n9m"@U3T߻Rb^?ouj_{Tk޻zxE8@rSo;qu]W/MÿfzED(hywi2,\+Bm Ͷk_`蠟ynaAۗ{W>M&o&Tqmm7+pw]=8ұS*.;t2 C5춨췫Cz;O1dK헻c.nϮnhsp"wvKZ-*7[@c*}jt_$[&zmԸî,2OmQ(^~N}s})c]fЏuSv;ENz,V"$:\rw1qw,iLH7(ݺlip:z(0s4)q΁c2t܉#nsv].u==8P_w_#٭¤JD\PK2Y*dy+` 2ƇalAO0Eڄxl! -Uendstream -endobj -1416 0 obj<>/XObject<<>>>>/Annots 610 0 R>>endobj -1417 0 obj<>stream -xXrF+ `;(;vRe.!r(¢4CJUzz^D'<$u~Z&)+2n)J ڣM ׬-au18o,Hm|`2(Y'MT,bU2<0<#gf5f J:L ԁM ̳ -)D gL CWK< 6E"5kb뼭9*<Ҭ,"3s86 ɒl6c<0"e<0' Rź4[RClh41<뿮( "/o8 -~kZ=Yڇ-7mgjV}߰D}մHUm=01̉; %mzwVd g;QN^XjCc=M:0/tN"۟GjO+,\y^ϵ92?ԓl7\+ `U"3"i2=GC\Q~u'ː?i754/-Qr,Mv<%MuS,;v2.guGc߈2b~HzU T8UM#I_UGTb$c\Cv#9>﷟>ibOyз4@mU7\ :4蔩GnVfq项/ nvK9cU?Jqg1Oșx) ;d.iO=R=:hBv }&p>3/HUջ嗛%}v=ч~k1mRT߆,7F- - aw}k2^>endstream -endobj -1418 0 obj<>/XObject<<>>>>>>endobj -1419 0 obj<>stream -x+2T0BCs#c3\..}7K#4BHP$YSO=5/(1G!3$1''$3?O3$ BMr = !)f \CT&lendstream -endobj -1420 0 obj<>/XObject<<>>>>>>endobj -1421 0 obj<>stream -x]N <\Vݤ&&4-n Zh6Nfgt -B;1-=;vp0=YTa:\P=" )Lَ#,l~ di!<^ ]る'S^)EٍW:lG}|CVjeX׺/b^p_lendstream -endobj -1422 0 obj<>/XObject<<>>>>>>endobj -1423 0 obj<>stream -xXn9}W Ŏ-g˞H~TndKQ~OjGI V_rԩ<Ft9 0Wل'}N:EdpwE!-װuq9eN3vuPFLp6odPJ[/h4JǓl oOgkۆ+096"7(J%Ef6%;~56>y:?tiOֺTx?i+Ek6Jx,2Sr8=6*\Fpں{6XiˌRtZ zIa7u|9f0-ʈU5Ȯ~o8eG8-6^`;ayMG)ӦBR-rsacNh`R-5q4_ ""#V{Z)+|5]a(J8BbgCdxQ-*4Nڈ^6S;Z:Lea.4<;Oe`υ"-= Ha{Lt_wmCn ?N?>=N3ZnP4#n5WMS[M2>vT`,tV)cWZU&)؍Ε@C0xmY5:zHOo* oҵiE -%f8ōZv 8=xh~blKTrUYԙʐ_x1RCF(;~sF2pqow^(,*}oJj#&giG߸8~3ULry~u}>f5Izx.etf3΃@CK)ǥmUaضE}&Ue,ȷ {z+-LlwpϊE -\{x\RWx%i(+J5R >E3_#+-I [ H }⓳JiY!q@טqȩPqi3=M𤾠$3d:BrKYc^yS^)} fqN@#)D੸Wp0sc'L2,E##z6y['r?MJ*eQ.FwKV ,`wܥ( vؘܕ@'7Lw",N - ,q=r)@C9$2 _wql9CR]sawH1 I ŋ0KZ&o +]0LΓ\M'oendstream -endobj -1424 0 obj<>/XObject<<>>>>>>endobj -1425 0 obj<>stream -xXr۸+NDKJVWnE$@˚ARR'IO cD1M(.Άѐ& ~M4]ElpwISq5:!i_bSVh5Α$ߔJoƛ3?9/t"lBL#cVi{JM)JqR4Axb͞V{/_Hig6p([i3Dn{8(#)FTK_(BAL(U9M8巕?o+A5 sR{%rJ+s1S>NLe{'PveJ8o/HSӫ!0-ؗB^12quM%7.3U4˄'TK$j[J}DOkYƢˌr;<$v|iѿ#5+&3gcU+]JSI)R3vgrR?$~1f% Sm3IKz{Ubrm cOt)7(qFG'--9T{=#QPՐAz6iC0LM18qDƪAnuI03;@2lyށ=CA׉;@Wa=c(իg3 Vhf WE;fe*E`v*M -h94xqw<)Y:Ym$%IZn 1dM)i".np7ޟF]]1>ľ}y& -ei}3h>5sN ̦tb䘴^ sHM`xXޞШ S@QwI'8"e+J$GۥQ|O hP8=@I1\ yUm {D2 qX%>R@G+i_U,Bo2m=&cn[NO%_Ozm5\+ǩ)ԟ5PĐbh4y3aሟ'^6ֈ$λ>!MB=1qUup8BunfqQ!ACgnhwBa8」0O_O -!N}`L_{}OM ^\lBꖐ!yM!>OSf;Ȇ+QX Jh/ bE51v\giո(5bNUql͍dԋ.8f uEI  ,ɍ@>O@~Q+^ -lp9`5Īya -.Hrgͅ0Ip4a ^YmU`)CN7(-W0>J8WOR]&eD\ EWM}t˼&Nu{7 A%`cp| -p_UT퀳*p @S߹ xQ@K¹vЊ3"g#";bV6WJq1 -6c xA.9zS -:!jeFB送Ą;CFಣ,^;௝w+d6Q⺥om$C귬9F%6/Ƭ}endstream -endobj -1426 0 obj<>/XObject<<>>>>>>endobj -1427 0 obj<>stream -xXO޿ -=T"vBB+E (Ii5'{ y;wl' ]VJs_终ѰGwݠK`@!{g%-_wO߅#4]4iB4>~@s.5rakU^ 49Z(Y>˪R -cECJw~uBZJiU,X͕);}8zt7ǖq-Ҋ|d!7F[cXUwuYهhmf̃K\*2Vʥ$hiLBRBZ<2KLTڑYbP1-V82_ӏt;{Bj޻*Q V J7t% Ā,gLaXiM efŶM!:AgrZlqg%֔2ƛ7gș?ˀ /&~:1`Kgmto3iMp0FV1;:#-B کXpj/UUڵs;뛝uJl I/8e |YifuUН(K4i3;Bl8 > Rec{ #PfSg55YX-rGTY´@Oш:ǣm.'d* $raOdZ{x5uR^Z5d &u*hyé1مŸ$\OL.Ѓ!̪Jd(IT˔KNNlR,Z$X7ɶ;;Yp3,=sܯU['!$,hi47F.y piR,Be4m< ϕ;8@&UG,բ ܓz^eϻ0m_|.ttsúTZ%Tru<XXL^ n؍^\ޛ/{mUWyIv*gV)HThd5W?cp]JQtB]!oڢ M@l0y t^ DUCA -;UކkgH -dJmu/B,}VzԜ=S'Kh4u'?U-gϤKR[re~ut!!,)?:U0ooS/,ۋ8$6cQB=xLe8Šہ›e$g/ȧ~qn|s6(Y'x-2Y{qf)G}VLaA!-T!>a&qK*ttGD@`;¥_l ]&Wu'3>X+m&|. /O }?x_&g7g>/XObject<<>>>>>>endobj -1429 0 obj<>stream -xmUn6|W,eN_r) -8q[J\YL$%)+P. rwvvv bZNiL ?ъ%OLYbOEf0[P&CjII3&p\FFE4G6Ii$ӽJq&MMʟ;IfVxw!%r^Fmd2+} FcxMCلSQ92B{vGΤӁS8j*OF$PGIsM _Yv!c*^"L֖ @I -.V>G7< W%YSc*j!hle$ |2u@Ȧz0.r^LwRm/ \~6琇e0Ҝ]2 MO\7 -}A!%lPReӪ SBsw{@h`91ƃk۽E -ةTRB͙A$tӒrS2JRB8c˶Q2s`GC &!v h4RflP --Zu =DWd!bX[ƿ̐4~fˢ$AF=G -F%ӊQ$v -|ك\AQJvOЧT~'izݯgz Xi@\qݾUle1`JB͇ެf45,؃(RfMg{PXvn~н؉ꐞx)Z:^sUj,AI["귗+aGygq0B-:  emv*Qa`CԊc=k+9 9'[iFTc䕮 oX v/ _?}c.~i:6AkNsX8GKNpqj!eDlKZE-4a}*|wc,yi=0||3;L@*e0G^]% 4tK쫤P.$.n;mnN@ .B2ӿ::*2v7>tLAdlw.Ռf[<]\ӣ5Ϝw 9_Σb 81s!endstream -endobj -1430 0 obj<>/XObject<<>>>>/Annots 616 0 R>>endobj -1431 0 obj<>stream -xVn6}֮߯}$5mA}$JZURzgHI{iҋ ȹ3s?G!M*ْr4 2n ZN`J%MVݏN؝Ondl7͂9-V` zD݊mO%͢M0;=]cw9<-ri^H|ውy8E:tU/\ yn ŰX#0[=hvCє_ִM_DHFmeQ$6tͫ?p\o .nT;+=Ҋ2mBQ0E(riIgހSURLDTIU3iC*LQq(]I(&Kɱt|C($T!Gjv I\.ZdzATI] -<ʌ.5d'GQԵѵQAUϼ"ExLwo-2 e6x\ueʐCխmjU -g -OdL\98r "mNL -Qk~ xQTאLB8cXYdL| {ept%k`]rF;./۵G6ّ=I{_:0H@^4`Hfh=~09DܜX_b^k9/TM{)8!FB=r8ehNiK+8-/t,BPP|gcnt[w~NF,%~>o9gJ%[W?4y{"OiNuE0+p<3HVAoċM7 /Iu"l-AS/a̝LE56CtAU"ˑy w%.8 -"@K w:0M'}l1+(B#ÄF" 3cc9$K`ܓں4G,sbmw!BF]w1ylr|p1.w'eӸeʀB>q37P]KЂ9X`|h s*0xsp½ ; cu?vJ8Xz,Pxў btA|)oP~㏭9?g-:_̓ra>lG7endstream -endobj -1432 0 obj<>/XObject<<>>>>>>endobj -1433 0 obj<>stream -xV]o6|ϯXZIJe;C\quhHNYR%) (&ݝ׳i6l b4&4ea3]pfS(=16BR\Z -kwJj$A=|hi k9醫 BVdQGNU^b K?nqDjO{oQ|頂† "LJܬ,‚-Iccس>pÔb".}OhnM)1ng}Iqj)C6lJ'|jl2H G tɭ&l;處:{N L~RK+('{4ҪgkMX.ĉewQ[&dk ,WG@RC&3{{s˩_kiek ,_\ y8h:8t*X&.T:t5| (b{u[D6 _=iRؔeGl ?E`-AyW[>`I~(O] Y`<=$hD_5Oz Gb N2(U뿯f/l>ԧemZ|>raލA)@xhlmc;*zD<ӻ3smdЇϢ"~"=2-ݍ]yV)‰R_ӕ5 W oLȌU^cPa6rܞ*vOT]/lZ>@mA爩UDZtLZ4}[7aalX=ӗ蜤K(z"ǖ|dS0s0U$7W_nWCڔqhư9SzI+|_f gsa^m+t Jc'2o}~1MMn>C$u/X"\~:$M !_g}Aendstream -endobj -1434 0 obj<>/XObject<<>>>>/Annots 619 0 R>>endobj -1435 0 obj<>stream -xWko6_q/MXvtCR'C6icoA-Q5TEνG)h`}sCǿMt2<'}OɐF >֔`0'GxaoͣA?lt -{cG{_K$g{g{_K8wN)'v?IN'8~1~J/oڀ9O'>-ңw<<_n^Arv;쨪 B[U `+^|w2xv_@9-V~4sU{W?/vD{q *GQXMxtk:o<)?%o*) -mGn) -rWn?q} N3[Ul<sW|k,tw\*Z)OK IS}ņAYk̴P2 -Kҩɍ^){ .0wG%dgROYF -瀑{^J)},ҵNTk a,P#}[ &Om(^bt WHϔ:AusBo1t7,T h:pcD鲒(5F߭Xg;%;z9ZLjDT\~{#9]d <]au 1c-B$x64_|mŠs䃀J'78'M@56b&VD2bUQ:0j^EU];|>.,*DlGFD1]'Pig:(zhHqkye?¤F(1bN1cZ6@Cvt.3QC2sMpEPߕg,#̟k (OȆy=y{vaH ]5ĉiPF*]o<Ɏ, J30*ƒYr@ -Vh!{ CFo%A`}@ t![+#>-ǰ?Bɬ2be!' -Ra;(׉8C?KjKn!Rop;)+o`NA ժtono.I>]ڏw׋Knrp-y^p0r#ͥ)Lhנ!]Hʗ#?jھe x;stߵ.36Y|Л;h2J&i|_~-endstream -endobj -1436 0 obj<>/XObject<>>>>>endobj -1437 0 obj<>stream -xW]o6}ϯoMF8v4 `MC^BKņ"Us)Җ݆#s/4٤{?قf ~~<[K_.KM'GZ{Mxqf7G\j -KqQbut6 X髞9.w), *2,94`0BwNh@D&+Er:cZQ)u-+c5 !rr۽zQ *EéB2 -41ڋ]s{w&Vv/1gz!A -nuMKcTѮsA[n2a]GW/XmFqVcj]đÁqr K 9cLpa9Rp{V\ðE5td^4Sk9ÞY;Gvb}PKh6 \x-yz|q,AA RSxԛX5m r&6Tkg )xděUګȬC;OWWv~%?ӣK 9Of?Wda2rod<$K7=L pnsL@.Dr[U{Y|Gzl#e-v4Q$m#  B}Ջ8qM -Lo0v@bSh^h4fXJ#[9 G& SE4 4a|Upu50K  -7'"uSM2I~σ(qK*"l<Cw.t+* >(TؒQC,XBw165^[T7~FͪՃ$85yOF3;~V0>lN2PNGH@n0*: nd5-Ԭ76SJ7Bi\.h]$&;V018؍,wZc[HI|{*| ~PIe`gk\{4[k DPՑĐ БWݵ7*D\0{LpM@/6`I~e uƮ(]Tnq>fpowdzJp/_e.;q2ξ 5(endstream -endobj -1438 0 obj<>/XObject<<>>>>>>endobj -1439 0 obj<>stream -xXnF}ẈHŎ$JA"X+qcrWᒖ=h$;s bJ|Mi19$I2o%isq{E62*#Lh.YB֕͞[itZ+- QGL -s [u! f -x.ugn)ʵwW4sb4[$swcf-3k(aI_ "͕yleEu.UEe}{iIZxx?PL^x=HDtL٣գJ%Շ$d%8d4GS)~Hk*e*޵؛!x&W,D\ڥԩGZ(1'39"[Ki񯠯w|,Cyb?-WK*yhvl E.c5E;!4 ~gs;RHp\t%Q+ZK<(~#ђk^Nh-Qk{ӆ\s7 lֲR Ԋbmpag]w( !{VՍ%UQeGB< He>Kq@Z^J)H鐏# p^*YZvLzydH[$Grwxjt]|EY=N|0 l 2^]g+y?N\}N&iʔHpOi.tn! =)LJ^|DEq q9(zٶe u.%a|䧐rY8jGLS]L!쥏ۃw.CٸZt谬"6W\ͮV%<G= +SШ6)yZp]@Ucrm<@YD0F>%Ӗɥi0+[G -Va DX1%}0IljDFmi @R\܀1ڒeU ?pv<ş PHc;7 `'3)6 ߂6HWlp`:͍V֍Us{V2d0^8ڙz9rnrpO6A0\i*˘vNz=btX䏆I)/U* 74ҺRꁅ 6uNϹs(DPx#Ƒ չ75|Dԣ2(}s}C( PAƫ^'R-^2$$$t?/ϛendstream -endobj -1440 0 obj<>/XObject<<>>>>>>endobj -1441 0 obj<>stream -xWmOHίoMb T&:jco-nk'Ϳgf][(yygf tDiyOtk˃E2>钦s]`ߧiڣץ4)k]mSM7T84dIv|u2OIxqڣ$I'g4pbx8b\{u_&g{QcH#=j8t؎L m*#|wRUН ->nzMHe!ϼSYs1 guvYE[ܫd0Hɠ5J]]d4Ӵ0+mIׇ$XA+Ux&8=*U hfDqc8L݈HQR c]peV ; -W&}lOnچ{v8߶0`α|2I"B>WУZ4dz#7DR%N,[\",VnïfiK ab_q70u2ELw0Jg@Bz2L*$';>ZHGsTECh\Փ ʖʪ-UexB5kŢTx+HH+n3c` > )x;pi3l{֑@X%1wpN)bSiBER;LA J?NxPJJMהn' ʝG8_ -@t|Aƭ 6؏)`P"ЧiQg-ޜ[DXйD:b -[A0*P}( !f[Z+J k@VX8- A`ɖoH C> ʤȀfl`Ik5a[`0LަߠV(vmʫܤ=,uf*D+MhH„zq,RﰹH, I#齊,bچe+ -poBq_(rȋY8p5kCQ+䦽hn -&(3/"VZt5 @\%%eȢK j2aG;%q/{4`TzUJ pMᮍn p12FKx leXyJB]3=7Ȋ)唛Bš=prdcµb!<\)$u#Hh5303] Q3 L8&sh[>y ޹<^ Gz8[,.-0fG @endstream -endobj -1442 0 obj<>/XObject<<>>>>>>endobj -1443 0 obj<>stream -xls0([Rڤ5eib-J/ 80{L7ӧD|1BEA B I(4'$%QXQ )R0ȆU+N R2$*+RY5ڢrQcBB4Qr#?#@V=7Q$"a8diV)')!w) Ak5G+AJT<"Ao A2z߶ Y8R[$($!tT i[(~R0Q#GWbݲj7,9|Hg*z{Btl>%a)|ø6*Mo R,yu^wlŤiבkYv~΢·}$h46->PX"ΐVq8ٽI1 A|0g=]̾=zypDSYd"3Yւ8,Cmw6vm-aͻȷҾ7R9k|\9/wNKc V8슟_&r4['Hy;^t+tu}#[4uUhv񌘕\q/CH_>_}wU.N֪RkK8+s{]g @?΋Ƅw֐zlKWA8u1僩Fy5wB?Ǽ8-EGiLU4xx4c{ch:5& On- z}PcLc®Zh U=|+Q7GRܽfwR5j߸ Vn>_+;ZWk8FUo<moopnike+Z.VÓU=A&c8]-jt%c8~+̧it3TK!3n}-k |*t  6kaX<ϴ2:R@pIa:^raGUP^VAk -bVĶȲ5uIj@BPNC[s;LBp< -$Ηx.4K j 1`0DEq9. -y2T1Hh|8 -AO=2 (OTwQłJ1׶&[{ L{m7EMB%2~@'x\F0:z_'zhllb8u6 W,iىXm'STAsA[ha*ERg$ +%PDF-1.4 +5 0 obj +<< /S /GoTo /D (part.1) >> +endobj +8 0 obj +(I General Installation) +endobj +9 0 obj +<< /S /GoTo /D (chapter.1) >> +endobj +12 0 obj +(1 Introduction to Samba) +endobj +13 0 obj +<< /S /GoTo /D (section.1.1) >> +endobj +16 0 obj +(1.1 Background) +endobj +17 0 obj +<< /S /GoTo /D (section.1.2) >> +endobj +20 0 obj +(1.2 Terminology) +endobj +21 0 obj +<< /S /GoTo /D (section.1.3) >> +endobj +24 0 obj +(1.3 Related Projects) +endobj +25 0 obj +<< /S /GoTo /D (section.1.4) >> +endobj +28 0 obj +(1.4 SMB Methodology) +endobj +29 0 obj +<< /S /GoTo /D (section.1.5) >> +endobj +32 0 obj +(1.5 Additional Resources) +endobj +33 0 obj +<< /S /GoTo /D (section.1.6) >> +endobj +36 0 obj +(1.6 Epilogue) +endobj +37 0 obj +<< /S /GoTo /D (section.1.7) >> +endobj +40 0 obj +(1.7 Miscellaneous) +endobj +41 0 obj +<< /S /GoTo /D (chapter.2) >> +endobj +44 0 obj +(2 How to Install and Test SAMBA) +endobj +45 0 obj +<< /S /GoTo /D (section.2.1) >> +endobj +48 0 obj +(2.1 Obtaining and installing samba) +endobj +49 0 obj +<< /S /GoTo /D (section.2.2) >> +endobj +52 0 obj +(2.2 Configuring samba) +endobj +53 0 obj +<< /S /GoTo /D (subsection.2.2.1) >> +endobj +56 0 obj +(2.2.1 Editing the smb.conf file) +endobj +57 0 obj +<< /S /GoTo /D (subsubsection.2.2.1.1) >> +endobj +60 0 obj +(2.2.1.1 Test your config file with testparm) +endobj +61 0 obj +<< /S /GoTo /D (subsection.2.2.2) >> +endobj +64 0 obj +(2.2.2 SWAT) +endobj +65 0 obj +<< /S /GoTo /D (section.2.3) >> +endobj +68 0 obj +(2.3 Try listing the shares available on your server) +endobj +69 0 obj +<< /S /GoTo /D (section.2.4) >> +endobj +72 0 obj +(2.4 Try connecting with the unix client) +endobj +73 0 obj +<< /S /GoTo /D (section.2.5) >> +endobj +76 0 obj +(2.5 Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client) +endobj +77 0 obj +<< /S /GoTo /D (section.2.6) >> +endobj +80 0 obj +(2.6 What If Things Don't Work?) +endobj +81 0 obj +<< /S /GoTo /D (part.2) >> +endobj +84 0 obj +(II Server Configuration Basics) +endobj +85 0 obj +<< /S /GoTo /D (chapter.3) >> +endobj +88 0 obj +(3 Nomenclature of Server Types) +endobj +89 0 obj +<< /S /GoTo /D (section.3.1) >> +endobj +92 0 obj +(3.1 Stand Alone Server) +endobj +93 0 obj +<< /S /GoTo /D (section.3.2) >> +endobj +96 0 obj +(3.2 Domain Member Server) +endobj +97 0 obj +<< /S /GoTo /D (section.3.3) >> +endobj +100 0 obj +(3.3 Domain Controller) +endobj +101 0 obj +<< /S /GoTo /D (subsection.3.3.1) >> +endobj +104 0 obj +(3.3.1 Domain Controller Types) +endobj +105 0 obj +<< /S /GoTo /D (chapter.4) >> +endobj +108 0 obj +(4 Samba as Stand-Alone Server) +endobj +109 0 obj +<< /S /GoTo /D (section.4.1) >> +endobj +112 0 obj +(4.1 User and Share security level) +endobj +113 0 obj +<< /S /GoTo /D (subsection.4.1.1) >> +endobj +116 0 obj +(4.1.1 User Level Security) +endobj +117 0 obj +<< /S /GoTo /D (subsection.4.1.2) >> +endobj +120 0 obj +(4.1.2 Share Level Security) +endobj +121 0 obj +<< /S /GoTo /D (subsection.4.1.3) >> +endobj +124 0 obj +(4.1.3 Server Level Security) +endobj +125 0 obj +<< /S /GoTo /D (subsubsection.4.1.3.1) >> +endobj +128 0 obj +(4.1.3.1 Configuring Samba for Seemless Windows Network Integration) +endobj +129 0 obj +<< /S /GoTo /D (subsubsection.4.1.3.2) >> +endobj +132 0 obj +(4.1.3.2 Use MS Windows NT as an authentication server) +endobj +133 0 obj +<< /S /GoTo /D (subsection.4.1.4) >> +endobj +136 0 obj +(4.1.4 Domain Level Security) +endobj +137 0 obj +<< /S /GoTo /D (subsubsection.4.1.4.1) >> +endobj +140 0 obj +(4.1.4.1 Samba as a member of an MS Windows NT security domain) +endobj +141 0 obj +<< /S /GoTo /D (subsection.4.1.5) >> +endobj +144 0 obj +(4.1.5 ADS Level Security) +endobj +145 0 obj +<< /S /GoTo /D (chapter.5) >> +endobj +148 0 obj +(5 Samba as an NT4 or Win2k Primary Domain Controller) +endobj +149 0 obj +<< /S /GoTo /D (section.5.1) >> +endobj +152 0 obj +(5.1 Prerequisite Reading) +endobj +153 0 obj +<< /S /GoTo /D (section.5.2) >> +endobj +156 0 obj +(5.2 Background) +endobj +157 0 obj +<< /S /GoTo /D (section.5.3) >> +endobj +160 0 obj +(5.3 Configuring the Samba Domain Controller) +endobj +161 0 obj +<< /S /GoTo /D (section.5.4) >> +endobj +164 0 obj +(5.4 Creating Machine Trust Accounts and Joining Clients to the Domain) +endobj +165 0 obj +<< /S /GoTo /D (subsection.5.4.1) >> +endobj +168 0 obj +(5.4.1 Manual Creation of Machine Trust Accounts) +endobj +169 0 obj +<< /S /GoTo /D (subsection.5.4.2) >> +endobj +172 0 obj +(5.4.2 "On-the-Fly" Creation of Machine Trust Accounts) +endobj +173 0 obj +<< /S /GoTo /D (subsection.5.4.3) >> +endobj +176 0 obj +(5.4.3 Joining the Client to the Domain) +endobj +177 0 obj +<< /S /GoTo /D (section.5.5) >> +endobj +180 0 obj +(5.5 Common Problems and Errors) +endobj +181 0 obj +<< /S /GoTo /D (subsection.5.5.1) >> +endobj +184 0 obj +(5.5.1 I cannot include a '\044' in a machine name) +endobj +185 0 obj +<< /S /GoTo /D (subsection.5.5.2) >> +endobj +188 0 obj +(5.5.2 I get told "You already have a connection to the Domain...." or "Cannot join domain, the credentials supplied conflict with an existing set.." when creating a machine trust account.) +endobj +189 0 obj +<< /S /GoTo /D (subsection.5.5.3) >> +endobj +192 0 obj +(5.5.3 The system can not log you on \(C000019B\)....) +endobj +193 0 obj +<< /S /GoTo /D (subsection.5.5.4) >> +endobj +196 0 obj +(5.5.4 The machine trust account for this computer either does not exist or is not accessible.) +endobj +197 0 obj +<< /S /GoTo /D (subsection.5.5.5) >> +endobj +200 0 obj +(5.5.5 When I attempt to login to a Samba Domain from a NT4/W2K workstation, I get a message about my account being disabled.) +endobj +201 0 obj +<< /S /GoTo /D (section.5.6) >> +endobj +204 0 obj +(5.6 Domain Control for Windows 9x/ME) +endobj +205 0 obj +<< /S /GoTo /D (subsection.5.6.1) >> +endobj +208 0 obj +(5.6.1 Configuration Instructions: Network Logons) +endobj +209 0 obj +<< /S /GoTo /D (chapter.6) >> +endobj +212 0 obj +(6 Samba Backup Domain Controller to Samba Domain Control) +endobj +213 0 obj +<< /S /GoTo /D (section.6.1) >> +endobj +216 0 obj +(6.1 Prerequisite Reading) +endobj +217 0 obj +<< /S /GoTo /D (section.6.2) >> +endobj +220 0 obj +(6.2 Background) +endobj +221 0 obj +<< /S /GoTo /D (section.6.3) >> +endobj +224 0 obj +(6.3 What qualifies a Domain Controller on the network?) +endobj +225 0 obj +<< /S /GoTo /D (subsection.6.3.1) >> +endobj +228 0 obj +(6.3.1 How does a Workstation find its domain controller?) +endobj +229 0 obj +<< /S /GoTo /D (subsection.6.3.2) >> +endobj +232 0 obj +(6.3.2 When is the PDC needed?) +endobj +233 0 obj +<< /S /GoTo /D (section.6.4) >> +endobj +236 0 obj +(6.4 Can Samba be a Backup Domain Controller to an NT PDC?) +endobj +237 0 obj +<< /S /GoTo /D (section.6.5) >> +endobj +240 0 obj +(6.5 How do I set up a Samba BDC?) +endobj +241 0 obj +<< /S /GoTo /D (subsection.6.5.1) >> +endobj +244 0 obj +(6.5.1 How do I replicate the smbpasswd file?) +endobj +245 0 obj +<< /S /GoTo /D (subsection.6.5.2) >> +endobj +248 0 obj +(6.5.2 Can I do this all with LDAP?) +endobj +249 0 obj +<< /S /GoTo /D (chapter.7) >> +endobj +252 0 obj +(7 Samba as a ADS domain member) +endobj +253 0 obj +<< /S /GoTo /D (section.7.1) >> +endobj +256 0 obj +(7.1 Setup your smb.conf) +endobj +257 0 obj +<< /S /GoTo /D (section.7.2) >> +endobj +260 0 obj +(7.2 Setup your /etc/krb5.conf) +endobj +261 0 obj +<< /S /GoTo /D (section.7.3) >> +endobj +264 0 obj +(7.3 Create the computer account) +endobj +265 0 obj +<< /S /GoTo /D (subsection.7.3.1) >> +endobj +268 0 obj +(7.3.1 Possible errors) +endobj +269 0 obj +<< /S /GoTo /D (section.7.4) >> +endobj +272 0 obj +(7.4 Test your server setup) +endobj +273 0 obj +<< /S /GoTo /D (section.7.5) >> +endobj +276 0 obj +(7.5 Testing with smbclient) +endobj +277 0 obj +<< /S /GoTo /D (section.7.6) >> +endobj +280 0 obj +(7.6 Notes) +endobj +281 0 obj +<< /S /GoTo /D (chapter.8) >> +endobj +284 0 obj +(8 Samba as a NT4 or Win2k domain member) +endobj +285 0 obj +<< /S /GoTo /D (section.8.1) >> +endobj +288 0 obj +(8.1 Joining an NT Domain with Samba 3.0) +endobj +289 0 obj +<< /S /GoTo /D (section.8.2) >> +endobj +292 0 obj +(8.2 Why is this better than security = server?) +endobj +293 0 obj +<< /S /GoTo /D (part.3) >> +endobj +296 0 obj +(III Advanced Configuration) +endobj +297 0 obj +<< /S /GoTo /D (chapter.9) >> +endobj +300 0 obj +(9 Samba / MS Windows Network Browsing Guide) +endobj +301 0 obj +<< /S /GoTo /D (section.9.1) >> +endobj +304 0 obj +(9.1 What is Browsing?) +endobj +305 0 obj +<< /S /GoTo /D (section.9.2) >> +endobj +308 0 obj +(9.2 Discussion) +endobj +309 0 obj +<< /S /GoTo /D (section.9.3) >> +endobj +312 0 obj +(9.3 How Browsing Functions) +endobj +313 0 obj +<< /S /GoTo /D (subsection.9.3.1) >> +endobj +316 0 obj +(9.3.1 Setting up WORKGROUP Browsing) +endobj +317 0 obj +<< /S /GoTo /D (subsection.9.3.2) >> +endobj +320 0 obj +(9.3.2 Setting up DOMAIN Browsing) +endobj +321 0 obj +<< /S /GoTo /D (subsection.9.3.3) >> +endobj +324 0 obj +(9.3.3 Forcing samba to be the master) +endobj +325 0 obj +<< /S /GoTo /D (subsection.9.3.4) >> +endobj +328 0 obj +(9.3.4 Making samba the domain master) +endobj +329 0 obj +<< /S /GoTo /D (subsection.9.3.5) >> +endobj +332 0 obj +(9.3.5 Note about broadcast addresses) +endobj +333 0 obj +<< /S /GoTo /D (subsection.9.3.6) >> +endobj +336 0 obj +(9.3.6 Multiple interfaces) +endobj +337 0 obj +<< /S /GoTo /D (subsection.9.3.7) >> +endobj +340 0 obj +(9.3.7 Use of the Remote Announce parameter) +endobj +341 0 obj +<< /S /GoTo /D (subsection.9.3.8) >> +endobj +344 0 obj +(9.3.8 Use of the Remote Browse Sync parameter) +endobj +345 0 obj +<< /S /GoTo /D (section.9.4) >> +endobj +348 0 obj +(9.4 WINS - The Windows Internetworking Name Server) +endobj +349 0 obj +<< /S /GoTo /D (subsection.9.4.1) >> +endobj +352 0 obj +(9.4.1 Setting up a WINS server) +endobj +353 0 obj +<< /S /GoTo /D (subsection.9.4.2) >> +endobj +356 0 obj +(9.4.2 WINS Replication) +endobj +357 0 obj +<< /S /GoTo /D (subsection.9.4.3) >> +endobj +360 0 obj +(9.4.3 Static WINS Entries) +endobj +361 0 obj +<< /S /GoTo /D (section.9.5) >> +endobj +364 0 obj +(9.5 Helpful Hints) +endobj +365 0 obj +<< /S /GoTo /D (subsection.9.5.1) >> +endobj +368 0 obj +(9.5.1 Windows Networking Protocols) +endobj +369 0 obj +<< /S /GoTo /D (subsection.9.5.2) >> +endobj +372 0 obj +(9.5.2 Name Resolution Order) +endobj +373 0 obj +<< /S /GoTo /D (section.9.6) >> +endobj +376 0 obj +(9.6 Technical Overview of browsing) +endobj +377 0 obj +<< /S /GoTo /D (subsection.9.6.1) >> +endobj +380 0 obj +(9.6.1 Browsing support in samba) +endobj +381 0 obj +<< /S /GoTo /D (subsection.9.6.2) >> +endobj +384 0 obj +(9.6.2 Problem resolution) +endobj +385 0 obj +<< /S /GoTo /D (subsection.9.6.3) >> +endobj +388 0 obj +(9.6.3 Browsing across subnets) +endobj +389 0 obj +<< /S /GoTo /D (subsubsection.9.6.3.1) >> +endobj +392 0 obj +(9.6.3.1 How does cross subnet browsing work ?) +endobj +393 0 obj +<< /S /GoTo /D (chapter.10) >> +endobj +396 0 obj +(10 User information database) +endobj +397 0 obj +<< /S /GoTo /D (section.10.1) >> +endobj +400 0 obj +(10.1 Introduction) +endobj +401 0 obj +<< /S /GoTo /D (section.10.2) >> +endobj +404 0 obj +(10.2 Important Notes About Security) +endobj +405 0 obj +<< /S /GoTo /D (subsection.10.2.1) >> +endobj +408 0 obj +(10.2.1 Advantages of SMB Encryption) +endobj +409 0 obj +<< /S /GoTo /D (subsection.10.2.2) >> +endobj +412 0 obj +(10.2.2 Advantages of non-encrypted passwords) +endobj +413 0 obj +<< /S /GoTo /D (section.10.3) >> +endobj +416 0 obj +(10.3 The smbpasswd Command) +endobj +417 0 obj +<< /S /GoTo /D (section.10.4) >> +endobj +420 0 obj +(10.4 Plain text) +endobj +421 0 obj +<< /S /GoTo /D (section.10.5) >> +endobj +424 0 obj +(10.5 TDB) +endobj +425 0 obj +<< /S /GoTo /D (section.10.6) >> +endobj +428 0 obj +(10.6 LDAP) +endobj +429 0 obj +<< /S /GoTo /D (subsection.10.6.1) >> +endobj +432 0 obj +(10.6.1 Introduction) +endobj +433 0 obj +<< /S /GoTo /D (subsection.10.6.2) >> +endobj +436 0 obj +(10.6.2 Encrypted Password Database) +endobj +437 0 obj +<< /S /GoTo /D (subsection.10.6.3) >> +endobj +440 0 obj +(10.6.3 Supported LDAP Servers) +endobj +441 0 obj +<< /S /GoTo /D (subsection.10.6.4) >> +endobj +444 0 obj +(10.6.4 Schema and Relationship to the RFC 2307 posixAccount) +endobj +445 0 obj +<< /S /GoTo /D (subsection.10.6.5) >> +endobj +448 0 obj +(10.6.5 Configuring Samba with LDAP) +endobj +449 0 obj +<< /S /GoTo /D (subsubsection.10.6.5.1) >> +endobj +452 0 obj +(10.6.5.1 OpenLDAP configuration) +endobj +453 0 obj +<< /S /GoTo /D (subsubsection.10.6.5.2) >> +endobj +456 0 obj +(10.6.5.2 Configuring Samba) +endobj +457 0 obj +<< /S /GoTo /D (subsection.10.6.6) >> +endobj +460 0 obj +(10.6.6 Accounts and Groups management) +endobj +461 0 obj +<< /S /GoTo /D (subsection.10.6.7) >> +endobj +464 0 obj +(10.6.7 Security and sambaAccount) +endobj +465 0 obj +<< /S /GoTo /D (subsection.10.6.8) >> +endobj +468 0 obj +(10.6.8 LDAP specials attributes for sambaAccounts) +endobj +469 0 obj +<< /S /GoTo /D (subsection.10.6.9) >> +endobj +472 0 obj +(10.6.9 Example LDIF Entries for a sambaAccount) +endobj +473 0 obj +<< /S /GoTo /D (section.10.7) >> +endobj +476 0 obj +(10.7 MySQL) +endobj +477 0 obj +<< /S /GoTo /D (subsection.10.7.1) >> +endobj +480 0 obj +(10.7.1 Creating the database) +endobj +481 0 obj +<< /S /GoTo /D (subsection.10.7.2) >> +endobj +484 0 obj +(10.7.2 Configuring) +endobj +485 0 obj +<< /S /GoTo /D (subsection.10.7.3) >> +endobj +488 0 obj +(10.7.3 Using plaintext passwords or encrypted password) +endobj +489 0 obj +<< /S /GoTo /D (subsection.10.7.4) >> +endobj +492 0 obj +(10.7.4 Getting non-column data from the table) +endobj +493 0 obj +<< /S /GoTo /D (section.10.8) >> +endobj +496 0 obj +(10.8 XML) +endobj +497 0 obj +<< /S /GoTo /D (chapter.11) >> +endobj +500 0 obj +(11 UNIX Permission Bits and Windows NT Access Control Lists) +endobj +501 0 obj +<< /S /GoTo /D (section.11.1) >> +endobj +504 0 obj +(11.1 Viewing and changing UNIX permissions using the NT security dialogs) +endobj +505 0 obj +<< /S /GoTo /D (section.11.2) >> +endobj +508 0 obj +(11.2 How to view file security on a Samba share) +endobj +509 0 obj +<< /S /GoTo /D (section.11.3) >> +endobj +512 0 obj +(11.3 Viewing file ownership) +endobj +513 0 obj +<< /S /GoTo /D (section.11.4) >> +endobj +516 0 obj +(11.4 Viewing file or directory permissions) +endobj +517 0 obj +<< /S /GoTo /D (subsection.11.4.1) >> +endobj +520 0 obj +(11.4.1 File Permissions) +endobj +521 0 obj +<< /S /GoTo /D (subsection.11.4.2) >> +endobj +524 0 obj +(11.4.2 Directory Permissions) +endobj +525 0 obj +<< /S /GoTo /D (section.11.5) >> +endobj +528 0 obj +(11.5 Modifying file or directory permissions) +endobj +529 0 obj +<< /S /GoTo /D (section.11.6) >> +endobj +532 0 obj +(11.6 Interaction with the standard Samba create mask parameters) +endobj +533 0 obj +<< /S /GoTo /D (section.11.7) >> +endobj +536 0 obj +(11.7 Interaction with the standard Samba file attribute mapping) +endobj +537 0 obj +<< /S /GoTo /D (chapter.12) >> +endobj +540 0 obj +(12 Configuring Group Mapping) +endobj +541 0 obj +<< /S /GoTo /D (chapter.13) >> +endobj +544 0 obj +(13 Printing Support) +endobj +545 0 obj +<< /S /GoTo /D (section.13.1) >> +endobj +548 0 obj +(13.1 Introduction) +endobj +549 0 obj +<< /S /GoTo /D (section.13.2) >> +endobj +552 0 obj +(13.2 Configuration) +endobj +553 0 obj +<< /S /GoTo /D (subsection.13.2.1) >> +endobj +556 0 obj +(13.2.1 Creating [print\044]) +endobj +557 0 obj +<< /S /GoTo /D (subsection.13.2.2) >> +endobj +560 0 obj +(13.2.2 Setting Drivers for Existing Printers) +endobj +561 0 obj +<< /S /GoTo /D (subsection.13.2.3) >> +endobj +564 0 obj +(13.2.3 Support a large number of printers) +endobj +565 0 obj +<< /S /GoTo /D (subsection.13.2.4) >> +endobj +568 0 obj +(13.2.4 Adding New Printers via the Windows NT APW) +endobj +569 0 obj +<< /S /GoTo /D (subsection.13.2.5) >> +endobj +572 0 obj +(13.2.5 Samba and Printer Ports) +endobj +573 0 obj +<< /S /GoTo /D (section.13.3) >> +endobj +576 0 obj +(13.3 The Imprints Toolset) +endobj +577 0 obj +<< /S /GoTo /D (subsection.13.3.1) >> +endobj +580 0 obj +(13.3.1 What is Imprints?) +endobj +581 0 obj +<< /S /GoTo /D (subsection.13.3.2) >> +endobj +584 0 obj +(13.3.2 Creating Printer Driver Packages) +endobj +585 0 obj +<< /S /GoTo /D (subsection.13.3.3) >> +endobj +588 0 obj +(13.3.3 The Imprints server) +endobj +589 0 obj +<< /S /GoTo /D (subsection.13.3.4) >> +endobj +592 0 obj +(13.3.4 The Installation Client) +endobj +593 0 obj +<< /S /GoTo /D (section.13.4) >> +endobj +596 0 obj +(13.4 Diagnosis) +endobj +597 0 obj +<< /S /GoTo /D (subsection.13.4.1) >> +endobj +600 0 obj +(13.4.1 Introduction) +endobj +601 0 obj +<< /S /GoTo /D (subsection.13.4.2) >> +endobj +604 0 obj +(13.4.2 Debugging printer problems) +endobj +605 0 obj +<< /S /GoTo /D (subsection.13.4.3) >> +endobj +608 0 obj +(13.4.3 What printers do I have?) +endobj +609 0 obj +<< /S /GoTo /D (subsection.13.4.4) >> +endobj +612 0 obj +(13.4.4 Setting up printcap and print servers) +endobj +613 0 obj +<< /S /GoTo /D (subsection.13.4.5) >> +endobj +616 0 obj +(13.4.5 Job sent, no output) +endobj +617 0 obj +<< /S /GoTo /D (subsection.13.4.6) >> +endobj +620 0 obj +(13.4.6 Job sent, strange output) +endobj +621 0 obj +<< /S /GoTo /D (subsection.13.4.7) >> +endobj +624 0 obj +(13.4.7 Raw PostScript printed) +endobj +625 0 obj +<< /S /GoTo /D (subsection.13.4.8) >> +endobj +628 0 obj +(13.4.8 Advanced Printing) +endobj +629 0 obj +<< /S /GoTo /D (subsection.13.4.9) >> +endobj +632 0 obj +(13.4.9 Real debugging) +endobj +633 0 obj +<< /S /GoTo /D (chapter.14) >> +endobj +636 0 obj +(14 CUPS Printing Support) +endobj +637 0 obj +<< /S /GoTo /D (section.14.1) >> +endobj +640 0 obj +(14.1 Introduction) +endobj +641 0 obj +<< /S /GoTo /D (section.14.2) >> +endobj +644 0 obj +(14.2 Configuring smb.conf for CUPS) +endobj +645 0 obj +<< /S /GoTo /D (section.14.3) >> +endobj +648 0 obj +(14.3 CUPS - RAW Print Through Mode) +endobj +649 0 obj +<< /S /GoTo /D (section.14.4) >> +endobj +652 0 obj +(14.4 CUPS as a network PostScript RIP) +endobj +653 0 obj +<< /S /GoTo /D (section.14.5) >> +endobj +656 0 obj +(14.5 Windows Terminal Servers \(WTS\) as CUPS clients) +endobj +657 0 obj +<< /S /GoTo /D (section.14.6) >> +endobj +660 0 obj +(14.6 Setting up CUPS for driver download) +endobj +661 0 obj +<< /S /GoTo /D (section.14.7) >> +endobj +664 0 obj +(14.7 Sources of CUPS drivers / PPDs) +endobj +665 0 obj +<< /S /GoTo /D (subsection.14.7.1) >> +endobj +668 0 obj +(14.7.1 cupsaddsmb) +endobj +669 0 obj +<< /S /GoTo /D (section.14.8) >> +endobj +672 0 obj +(14.8 The CUPS Filter Chains) +endobj +673 0 obj +<< /S /GoTo /D (section.14.9) >> +endobj +676 0 obj +(14.9 CUPS Print Drivers and Devices) +endobj +677 0 obj +<< /S /GoTo /D (subsection.14.9.1) >> +endobj +680 0 obj +(14.9.1 Further printing steps) +endobj +681 0 obj +<< /S /GoTo /D (section.14.10) >> +endobj +684 0 obj +(14.10 Limiting the number of pages users can print) +endobj +685 0 obj +<< /S /GoTo /D (section.14.11) >> +endobj +688 0 obj +(14.11 Advanced Postscript Printing from MS Windows) +endobj +689 0 obj +<< /S /GoTo /D (section.14.12) >> +endobj +692 0 obj +(14.12 Auto-Deletion of CUPS spool files) +endobj +693 0 obj +<< /S /GoTo /D (chapter.15) >> +endobj +696 0 obj +(15 Unified Logons between Windows NT and UNIX using Winbind) +endobj +697 0 obj +<< /S /GoTo /D (section.15.1) >> +endobj +700 0 obj +(15.1 Abstract) +endobj +701 0 obj +<< /S /GoTo /D (section.15.2) >> +endobj +704 0 obj +(15.2 Introduction) +endobj +705 0 obj +<< /S /GoTo /D (section.15.3) >> +endobj +708 0 obj +(15.3 What Winbind Provides) +endobj +709 0 obj +<< /S /GoTo /D (subsection.15.3.1) >> +endobj +712 0 obj +(15.3.1 Target Uses) +endobj +713 0 obj +<< /S /GoTo /D (section.15.4) >> +endobj +716 0 obj +(15.4 How Winbind Works) +endobj +717 0 obj +<< /S /GoTo /D (subsection.15.4.1) >> +endobj +720 0 obj +(15.4.1 Microsoft Remote Procedure Calls) +endobj +721 0 obj +<< /S /GoTo /D (subsection.15.4.2) >> +endobj +724 0 obj +(15.4.2 Microsoft Active Directory Services) +endobj +725 0 obj +<< /S /GoTo /D (subsection.15.4.3) >> +endobj +728 0 obj +(15.4.3 Name Service Switch) +endobj +729 0 obj +<< /S /GoTo /D (subsection.15.4.4) >> +endobj +732 0 obj +(15.4.4 Pluggable Authentication Modules) +endobj +733 0 obj +<< /S /GoTo /D (subsection.15.4.5) >> +endobj +736 0 obj +(15.4.5 User and Group ID Allocation) +endobj +737 0 obj +<< /S /GoTo /D (subsection.15.4.6) >> +endobj +740 0 obj +(15.4.6 Result Caching) +endobj +741 0 obj +<< /S /GoTo /D (section.15.5) >> +endobj +744 0 obj +(15.5 Installation and Configuration) +endobj +745 0 obj +<< /S /GoTo /D (subsection.15.5.1) >> +endobj +748 0 obj +(15.5.1 Introduction) +endobj +749 0 obj +<< /S /GoTo /D (subsection.15.5.2) >> +endobj +752 0 obj +(15.5.2 Requirements) +endobj +753 0 obj +<< /S /GoTo /D (subsection.15.5.3) >> +endobj +756 0 obj +(15.5.3 Testing Things Out) +endobj +757 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.1) >> +endobj +760 0 obj +(15.5.3.1 Configure and compile SAMBA) +endobj +761 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.2) >> +endobj +764 0 obj +(15.5.3.2 Configure nsswitch.conf and the winbind libraries on Linux and Solaris) +endobj +765 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.3) >> +endobj +768 0 obj +(15.5.3.3 NSS Winbind on AIX) +endobj +769 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.4) >> +endobj +772 0 obj +(15.5.3.4 Configure smb.conf) +endobj +773 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.5) >> +endobj +776 0 obj +(15.5.3.5 Join the SAMBA server to the PDC domain) +endobj +777 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.6) >> +endobj +780 0 obj +(15.5.3.6 Start up the winbindd daemon and test it!) +endobj +781 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.7) >> +endobj +784 0 obj +(15.5.3.7 Fix the init.d startup scripts) +endobj +785 0 obj +<< /S /GoTo /D (subsubsection.15.5.3.8) >> +endobj +788 0 obj +(15.5.3.8 Configure Winbind and PAM) +endobj +789 0 obj +<< /S /GoTo /D (section.15.6) >> +endobj +792 0 obj +(15.6 Limitations) +endobj +793 0 obj +<< /S /GoTo /D (section.15.7) >> +endobj +796 0 obj +(15.7 Conclusion) +endobj +797 0 obj +<< /S /GoTo /D (chapter.16) >> +endobj +800 0 obj +(16 Advanced Network Manangement) +endobj +801 0 obj +<< /S /GoTo /D (section.16.1) >> +endobj +804 0 obj +(16.1 Configuring Samba Share Access Controls) +endobj +805 0 obj +<< /S /GoTo /D (subsection.16.1.1) >> +endobj +808 0 obj +(16.1.1 Share Permissions Management) +endobj +809 0 obj +<< /S /GoTo /D (subsubsection.16.1.1.1) >> +endobj +812 0 obj +(16.1.1.1 Windows NT4 Workstation/Server) +endobj +813 0 obj +<< /S /GoTo /D (subsubsection.16.1.1.2) >> +endobj +816 0 obj +(16.1.1.2 Windows 200x/XP) +endobj +817 0 obj +<< /S /GoTo /D (section.16.2) >> +endobj +820 0 obj +(16.2 Remote Server Administration) +endobj +821 0 obj +<< /S /GoTo /D (section.16.3) >> +endobj +824 0 obj +(16.3 Network Logon Script Magic) +endobj +825 0 obj +<< /S /GoTo /D (subsection.16.3.1) >> +endobj +828 0 obj +(16.3.1 Adding printers without user intervention) +endobj +829 0 obj +<< /S /GoTo /D (chapter.17) >> +endobj +832 0 obj +(17 System and Account Policies) +endobj +833 0 obj +<< /S /GoTo /D (section.17.1) >> +endobj +836 0 obj +(17.1 Creating and Managing System Policies) +endobj +837 0 obj +<< /S /GoTo /D (subsection.17.1.1) >> +endobj +840 0 obj +(17.1.1 Windows 9x/Me Policies) +endobj +841 0 obj +<< /S /GoTo /D (subsection.17.1.2) >> +endobj +844 0 obj +(17.1.2 Windows NT4 Style Policy Files) +endobj +845 0 obj +<< /S /GoTo /D (subsubsection.17.1.2.1) >> +endobj +848 0 obj +(17.1.2.1 Registry Tattoos) +endobj +849 0 obj +<< /S /GoTo /D (subsection.17.1.3) >> +endobj +852 0 obj +(17.1.3 MS Windows 200x / XP Professional Policies) +endobj +853 0 obj +<< /S /GoTo /D (subsubsection.17.1.3.1) >> +endobj +856 0 obj +(17.1.3.1 Administration of Win2K / XP PoliciesInstructions) +endobj +857 0 obj +<< /S /GoTo /D (section.17.2) >> +endobj +860 0 obj +(17.2 Managing Account/User Policies) +endobj +861 0 obj +<< /S /GoTo /D (subsection.17.2.1) >> +endobj +864 0 obj +(17.2.1 With Windows NT4/200x) +endobj +865 0 obj +<< /S /GoTo /D (subsection.17.2.2) >> +endobj +868 0 obj +(17.2.2 With a Samba PDC) +endobj +869 0 obj +<< /S /GoTo /D (section.17.3) >> +endobj +872 0 obj +(17.3 System Startup and Logon Processing Overview) +endobj +873 0 obj +<< /S /GoTo /D (chapter.18) >> +endobj +876 0 obj +(18 Desktop Profile Management) +endobj +877 0 obj +<< /S /GoTo /D (section.18.1) >> +endobj +880 0 obj +(18.1 Roaming Profiles) +endobj +881 0 obj +<< /S /GoTo /D (subsection.18.1.1) >> +endobj +884 0 obj +(18.1.1 Samba Configuration for Profile Handling) +endobj +885 0 obj +<< /S /GoTo /D (subsubsection.18.1.1.1) >> +endobj +888 0 obj +(18.1.1.1 NT4/200x User Profiles) +endobj +889 0 obj +<< /S /GoTo /D (subsubsection.18.1.1.2) >> +endobj +892 0 obj +(18.1.1.2 Windows 9x / Me User Profiles) +endobj +893 0 obj +<< /S /GoTo /D (subsubsection.18.1.1.3) >> +endobj +896 0 obj +(18.1.1.3 Mixed Windows 9x / Me and Windows NT4/200x User Profiles) +endobj +897 0 obj +<< /S /GoTo /D (subsubsection.18.1.1.4) >> +endobj +900 0 obj +(18.1.1.4 Disabling Roaming Profile Support) +endobj +901 0 obj +<< /S /GoTo /D (subsection.18.1.2) >> +endobj +904 0 obj +(18.1.2 Windows Client Profile Configuration Information) +endobj +905 0 obj +<< /S /GoTo /D (subsubsection.18.1.2.1) >> +endobj +908 0 obj +(18.1.2.1 Windows 9x / Me Profile Setup) +endobj +909 0 obj +<< /S /GoTo /D (subsubsection.18.1.2.2) >> +endobj +912 0 obj +(18.1.2.2 Windows NT4 Workstation) +endobj +913 0 obj +<< /S /GoTo /D (subsubsection.18.1.2.3) >> +endobj +916 0 obj +(18.1.2.3 Windows 2000/XP Professional) +endobj +917 0 obj +<< /S /GoTo /D (subsection.18.1.3) >> +endobj +920 0 obj +(18.1.3 Sharing Profiles between W9x/Me and NT4/200x/XP workstations) +endobj +921 0 obj +<< /S /GoTo /D (subsection.18.1.4) >> +endobj +924 0 obj +(18.1.4 Profile Migration from Windows NT4/200x Server to Samba) +endobj +925 0 obj +<< /S /GoTo /D (subsubsection.18.1.4.1) >> +endobj +928 0 obj +(18.1.4.1 Windows NT4 Profile Management Tools) +endobj +929 0 obj +<< /S /GoTo /D (subsubsection.18.1.4.2) >> +endobj +932 0 obj +(18.1.4.2 Side bar Notes) +endobj +933 0 obj +<< /S /GoTo /D (subsubsection.18.1.4.3) >> +endobj +936 0 obj +(18.1.4.3 moveuser.exe) +endobj +937 0 obj +<< /S /GoTo /D (subsubsection.18.1.4.4) >> +endobj +940 0 obj +(18.1.4.4 Get SID) +endobj +941 0 obj +<< /S /GoTo /D (section.18.2) >> +endobj +944 0 obj +(18.2 Mandatory profiles) +endobj +945 0 obj +<< /S /GoTo /D (section.18.3) >> +endobj +948 0 obj +(18.3 Creating/Managing Group Profiles) +endobj +949 0 obj +<< /S /GoTo /D (section.18.4) >> +endobj +952 0 obj +(18.4 Default Profile for Windows Users) +endobj +953 0 obj +<< /S /GoTo /D (subsection.18.4.1) >> +endobj +956 0 obj +(18.4.1 MS Windows 9x/Me) +endobj +957 0 obj +<< /S /GoTo /D (subsubsection.18.4.1.1) >> +endobj +960 0 obj +(18.4.1.1 How User Profiles Are Handled in Windows 9x / Me?) +endobj +961 0 obj +<< /S /GoTo /D (subsection.18.4.2) >> +endobj +964 0 obj +(18.4.2 MS Windows NT4 Workstation) +endobj +965 0 obj +<< /S /GoTo /D (subsection.18.4.3) >> +endobj +968 0 obj +(18.4.3 MS Windows 200x/XP) +endobj +969 0 obj +<< /S /GoTo /D (chapter.19) >> +endobj +972 0 obj +(19 Interdomain Trust Relationships) +endobj +973 0 obj +<< /S /GoTo /D (section.19.1) >> +endobj +976 0 obj +(19.1 Trust Relationship Background) +endobj +977 0 obj +<< /S /GoTo /D (section.19.2) >> +endobj +980 0 obj +(19.2 Native MS Windows NT4 Trusts Configuration) +endobj +981 0 obj +<< /S /GoTo /D (subsection.19.2.1) >> +endobj +984 0 obj +(19.2.1 NT4 as the Trusting Domain \(ie. creating the trusted account\)) +endobj +985 0 obj +<< /S /GoTo /D (subsection.19.2.2) >> +endobj +988 0 obj +(19.2.2 NT4 as the Trusted Domain \(ie. creating trusted account's password\)) +endobj +989 0 obj +<< /S /GoTo /D (section.19.3) >> +endobj +992 0 obj +(19.3 Configuring Samba NT-style Domain Trusts) +endobj +993 0 obj +<< /S /GoTo /D (subsection.19.3.1) >> +endobj +996 0 obj +(19.3.1 Samba-3 as the Trusting Domain) +endobj +997 0 obj +<< /S /GoTo /D (subsection.19.3.2) >> +endobj +1000 0 obj +(19.3.2 Samba-3 as the Trusted Domain) +endobj +1001 0 obj +<< /S /GoTo /D (chapter.20) >> +endobj +1004 0 obj +(20 PAM Configuration for Centrally Managed Authentication) +endobj +1005 0 obj +<< /S /GoTo /D (section.20.1) >> +endobj +1008 0 obj +(20.1 Samba and PAM) +endobj +1009 0 obj +<< /S /GoTo /D (subsection.20.1.1) >> +endobj +1012 0 obj +(20.1.1 PAM Configuration in smb.conf) +endobj +1013 0 obj +<< /S /GoTo /D (subsection.20.1.2) >> +endobj +1016 0 obj +(20.1.2 Password Synchronisation using pam\137smbpass.so) +endobj +1017 0 obj +<< /S /GoTo /D (subsubsection.20.1.2.1) >> +endobj +1020 0 obj +(20.1.2.1 Password Synchonisation Configuration) +endobj +1021 0 obj +<< /S /GoTo /D (subsubsection.20.1.2.2) >> +endobj +1024 0 obj +(20.1.2.2 Password Migration Configuration) +endobj +1025 0 obj +<< /S /GoTo /D (subsubsection.20.1.2.3) >> +endobj +1028 0 obj +(20.1.2.3 Mature Password Configuration) +endobj +1029 0 obj +<< /S /GoTo /D (subsubsection.20.1.2.4) >> +endobj +1032 0 obj +(20.1.2.4 Kerberos Password Integration Configuration) +endobj +1033 0 obj +<< /S /GoTo /D (section.20.2) >> +endobj +1036 0 obj +(20.2 Distributed Authentication) +endobj +1037 0 obj +<< /S /GoTo /D (chapter.21) >> +endobj +1040 0 obj +(21 Stackable VFS modules) +endobj +1041 0 obj +<< /S /GoTo /D (section.21.1) >> +endobj +1044 0 obj +(21.1 Introduction and configuration) +endobj +1045 0 obj +<< /S /GoTo /D (section.21.2) >> +endobj +1048 0 obj +(21.2 Included modules) +endobj +1049 0 obj +<< /S /GoTo /D (subsection.21.2.1) >> +endobj +1052 0 obj +(21.2.1 audit) +endobj +1053 0 obj +<< /S /GoTo /D (subsection.21.2.2) >> +endobj +1056 0 obj +(21.2.2 extd\137audit) +endobj +1057 0 obj +<< /S /GoTo /D (subsection.21.2.3) >> +endobj +1060 0 obj +(21.2.3 recycle) +endobj +1061 0 obj +<< /S /GoTo /D (subsection.21.2.4) >> +endobj +1064 0 obj +(21.2.4 netatalk) +endobj +1065 0 obj +<< /S /GoTo /D (section.21.3) >> +endobj +1068 0 obj +(21.3 VFS modules available elsewhere) +endobj +1069 0 obj +<< /S /GoTo /D (subsection.21.3.1) >> +endobj +1072 0 obj +(21.3.1 DatabaseFS) +endobj +1073 0 obj +<< /S /GoTo /D (subsection.21.3.2) >> +endobj +1076 0 obj +(21.3.2 vscan) +endobj +1077 0 obj +<< /S /GoTo /D (chapter.22) >> +endobj +1080 0 obj +(22 Hosting a Microsoft Distributed File System tree on Samba) +endobj +1081 0 obj +<< /S /GoTo /D (section.22.1) >> +endobj +1084 0 obj +(22.1 Instructions) +endobj +1085 0 obj +<< /S /GoTo /D (subsection.22.1.1) >> +endobj +1088 0 obj +(22.1.1 Notes) +endobj +1089 0 obj +<< /S /GoTo /D (chapter.23) >> +endobj +1092 0 obj +(23 Integrating MS Windows networks with Samba) +endobj +1093 0 obj +<< /S /GoTo /D (section.23.1) >> +endobj +1096 0 obj +(23.1 Name Resolution in a pure Unix/Linux world) +endobj +1097 0 obj +<< /S /GoTo /D (subsection.23.1.1) >> +endobj +1100 0 obj +(23.1.1 /etc/hosts) +endobj +1101 0 obj +<< /S /GoTo /D (subsection.23.1.2) >> +endobj +1104 0 obj +(23.1.2 /etc/resolv.conf) +endobj +1105 0 obj +<< /S /GoTo /D (subsection.23.1.3) >> +endobj +1108 0 obj +(23.1.3 /etc/host.conf) +endobj +1109 0 obj +<< /S /GoTo /D (subsection.23.1.4) >> +endobj +1112 0 obj +(23.1.4 /etc/nsswitch.conf) +endobj +1113 0 obj +<< /S /GoTo /D (section.23.2) >> +endobj +1116 0 obj +(23.2 Name resolution as used within MS Windows networking) +endobj +1117 0 obj +<< /S /GoTo /D (subsection.23.2.1) >> +endobj +1120 0 obj +(23.2.1 The NetBIOS Name Cache) +endobj +1121 0 obj +<< /S /GoTo /D (subsection.23.2.2) >> +endobj +1124 0 obj +(23.2.2 The LMHOSTS file) +endobj +1125 0 obj +<< /S /GoTo /D (subsection.23.2.3) >> +endobj +1128 0 obj +(23.2.3 HOSTS file) +endobj +1129 0 obj +<< /S /GoTo /D (subsection.23.2.4) >> +endobj +1132 0 obj +(23.2.4 DNS Lookup) +endobj +1133 0 obj +<< /S /GoTo /D (subsection.23.2.5) >> +endobj +1136 0 obj +(23.2.5 WINS Lookup) +endobj +1137 0 obj +<< /S /GoTo /D (chapter.24) >> +endobj +1140 0 obj +(24 Securing Samba) +endobj +1141 0 obj +<< /S /GoTo /D (section.24.1) >> +endobj +1144 0 obj +(24.1 Introduction) +endobj +1145 0 obj +<< /S /GoTo /D (section.24.2) >> +endobj +1148 0 obj +(24.2 Using host based protection) +endobj +1149 0 obj +<< /S /GoTo /D (section.24.3) >> +endobj +1152 0 obj +(24.3 Using interface protection) +endobj +1153 0 obj +<< /S /GoTo /D (section.24.4) >> +endobj +1156 0 obj +(24.4 Using a firewall) +endobj +1157 0 obj +<< /S /GoTo /D (section.24.5) >> +endobj +1160 0 obj +(24.5 Using a IPC\044 share deny) +endobj +1161 0 obj +<< /S /GoTo /D (section.24.6) >> +endobj +1164 0 obj +(24.6 NTLMv2 Security) +endobj +1165 0 obj +<< /S /GoTo /D (section.24.7) >> +endobj +1168 0 obj +(24.7 Upgrading Samba) +endobj +1169 0 obj +<< /S /GoTo /D (chapter.25) >> +endobj +1172 0 obj +(25 Unicode/Charsets) +endobj +1173 0 obj +<< /S /GoTo /D (section.25.1) >> +endobj +1176 0 obj +(25.1 What are charsets and unicode?) +endobj +1177 0 obj +<< /S /GoTo /D (section.25.2) >> +endobj +1180 0 obj +(25.2 Samba and charsets) +endobj +1181 0 obj +<< /S /GoTo /D (section.25.3) >> +endobj +1184 0 obj +(25.3 Conversion from old names) +endobj +1185 0 obj +<< /S /GoTo /D (section.25.4) >> +endobj +1188 0 obj +(25.4 Japanese charsets) +endobj +1189 0 obj +<< /S /GoTo /D (chapter.26) >> +endobj +1192 0 obj +(26 File and Record Locking) +endobj +1193 0 obj +<< /S /GoTo /D (section.26.1) >> +endobj +1196 0 obj +(26.1 Discussion) +endobj +1197 0 obj +<< /S /GoTo /D (section.26.2) >> +endobj +1200 0 obj +(26.2 Samba Opportunistic Locking Control) +endobj +1201 0 obj +<< /S /GoTo /D (section.26.3) >> +endobj +1204 0 obj +(26.3 MS Windows Opportunistic Locking and Caching Controls) +endobj +1205 0 obj +<< /S /GoTo /D (subsection.26.3.1) >> +endobj +1208 0 obj +(26.3.1 Workstation Service Entries) +endobj +1209 0 obj +<< /S /GoTo /D (subsection.26.3.2) >> +endobj +1212 0 obj +(26.3.2 Server Service Entries) +endobj +1213 0 obj +<< /S /GoTo /D (section.26.4) >> +endobj +1216 0 obj +(26.4 Persistent Data Corruption) +endobj +1217 0 obj +<< /S /GoTo /D (section.26.5) >> +endobj +1220 0 obj +(26.5 Additional Reading) +endobj +1221 0 obj +<< /S /GoTo /D (part.4) >> +endobj +1224 0 obj +(IV Troubleshooting) +endobj +1225 0 obj +<< /S /GoTo /D (chapter.27) >> +endobj +1228 0 obj +(27 The samba checklist) +endobj +1229 0 obj +<< /S /GoTo /D (section.27.1) >> +endobj +1232 0 obj +(27.1 Introduction) +endobj +1233 0 obj +<< /S /GoTo /D (section.27.2) >> +endobj +1236 0 obj +(27.2 Assumptions) +endobj +1237 0 obj +<< /S /GoTo /D (section.27.3) >> +endobj +1240 0 obj +(27.3 The tests) +endobj +1241 0 obj +<< /S /GoTo /D (section.27.4) >> +endobj +1244 0 obj +(27.4 Still having troubles?) +endobj +1245 0 obj +<< /S /GoTo /D (chapter.28) >> +endobj +1248 0 obj +(28 Analysing and solving samba problems) +endobj +1249 0 obj +<< /S /GoTo /D (section.28.1) >> +endobj +1252 0 obj +(28.1 Diagnostics tools) +endobj +1253 0 obj +<< /S /GoTo /D (section.28.2) >> +endobj +1256 0 obj +(28.2 Installing 'Network Monitor' on an NT Workstation or a Windows 9x box) +endobj +1257 0 obj +<< /S /GoTo /D (section.28.3) >> +endobj +1260 0 obj +(28.3 Useful URL's) +endobj +1261 0 obj +<< /S /GoTo /D (section.28.4) >> +endobj +1264 0 obj +(28.4 Getting help from the mailing lists) +endobj +1265 0 obj +<< /S /GoTo /D (section.28.5) >> +endobj +1268 0 obj +(28.5 How to get off the mailinglists) +endobj +1269 0 obj +<< /S /GoTo /D (chapter.29) >> +endobj +1272 0 obj +(29 Reporting Bugs) +endobj +1273 0 obj +<< /S /GoTo /D (section.29.1) >> +endobj +1276 0 obj +(29.1 Introduction) +endobj +1277 0 obj +<< /S /GoTo /D (section.29.2) >> +endobj +1280 0 obj +(29.2 General info) +endobj +1281 0 obj +<< /S /GoTo /D (section.29.3) >> +endobj +1284 0 obj +(29.3 Debug levels) +endobj +1285 0 obj +<< /S /GoTo /D (section.29.4) >> +endobj +1288 0 obj +(29.4 Internal errors) +endobj +1289 0 obj +<< /S /GoTo /D (section.29.5) >> +endobj +1292 0 obj +(29.5 Attaching to a running process) +endobj +1293 0 obj +<< /S /GoTo /D (section.29.6) >> +endobj +1296 0 obj +(29.6 Patches) +endobj +1297 0 obj +<< /S /GoTo /D (part.5) >> +endobj +1300 0 obj +(V Appendixes) +endobj +1301 0 obj +<< /S /GoTo /D (chapter.30) >> +endobj +1304 0 obj +(30 How to compile SAMBA) +endobj +1305 0 obj +<< /S /GoTo /D (section.30.1) >> +endobj +1308 0 obj +(30.1 Access Samba source code via CVS) +endobj +1309 0 obj +<< /S /GoTo /D (subsection.30.1.1) >> +endobj +1312 0 obj +(30.1.1 Introduction) +endobj +1313 0 obj +<< /S /GoTo /D (subsection.30.1.2) >> +endobj +1316 0 obj +(30.1.2 CVS Access to samba.org) +endobj +1317 0 obj +<< /S /GoTo /D (subsubsection.30.1.2.1) >> +endobj +1320 0 obj +(30.1.2.1 Access via CVSweb) +endobj +1321 0 obj +<< /S /GoTo /D (subsubsection.30.1.2.2) >> +endobj +1324 0 obj +(30.1.2.2 Access via cvs) +endobj +1325 0 obj +<< /S /GoTo /D (section.30.2) >> +endobj +1328 0 obj +(30.2 Accessing the samba sources via rsync and ftp) +endobj +1329 0 obj +<< /S /GoTo /D (section.30.3) >> +endobj +1332 0 obj +(30.3 Verifying Samba's PGP signature) +endobj +1333 0 obj +<< /S /GoTo /D (section.30.4) >> +endobj +1336 0 obj +(30.4 Building the Binaries) +endobj +1337 0 obj +<< /S /GoTo /D (subsection.30.4.1) >> +endobj +1340 0 obj +(30.4.1 Compiling samba with Active Directory support) +endobj +1341 0 obj +<< /S /GoTo /D (subsubsection.30.4.1.1) >> +endobj +1344 0 obj +(30.4.1.1 Installing the required packages for Debian) +endobj +1345 0 obj +<< /S /GoTo /D (subsubsection.30.4.1.2) >> +endobj +1348 0 obj +(30.4.1.2 Installing the required packages for RedHat) +endobj +1349 0 obj +<< /S /GoTo /D (section.30.5) >> +endobj +1352 0 obj +(30.5 Starting the smbd and nmbd) +endobj +1353 0 obj +<< /S /GoTo /D (subsection.30.5.1) >> +endobj +1356 0 obj +(30.5.1 Starting from inetd.conf) +endobj +1357 0 obj +<< /S /GoTo /D (subsection.30.5.2) >> +endobj +1360 0 obj +(30.5.2 Alternative: starting it as a daemon) +endobj +1361 0 obj +<< /S /GoTo /D (chapter.31) >> +endobj +1364 0 obj +(31 Migration from NT4 PDC to Samba-3 PDC) +endobj +1365 0 obj +<< /S /GoTo /D (section.31.1) >> +endobj +1368 0 obj +(31.1 Planning and Getting Started) +endobj +1369 0 obj +<< /S /GoTo /D (subsection.31.1.1) >> +endobj +1372 0 obj +(31.1.1 Objectives) +endobj +1373 0 obj +<< /S /GoTo /D (subsubsection.31.1.1.1) >> +endobj +1376 0 obj +(31.1.1.1 Domain Layout) +endobj +1377 0 obj +<< /S /GoTo /D (subsubsection.31.1.1.2) >> +endobj +1380 0 obj +(31.1.1.2 Server Share and Directory Layout) +endobj +1381 0 obj +<< /S /GoTo /D (subsubsection.31.1.1.3) >> +endobj +1384 0 obj +(31.1.1.3 Logon Scripts) +endobj +1385 0 obj +<< /S /GoTo /D (subsubsection.31.1.1.4) >> +endobj +1388 0 obj +(31.1.1.4 Profile Migration/Creation) +endobj +1389 0 obj +<< /S /GoTo /D (subsubsection.31.1.1.5) >> +endobj +1392 0 obj +(31.1.1.5 User and Group Accounts) +endobj +1393 0 obj +<< /S /GoTo /D (subsection.31.1.2) >> +endobj +1396 0 obj +(31.1.2 Steps In Migration Process) +endobj +1397 0 obj +<< /S /GoTo /D (section.31.2) >> +endobj +1400 0 obj +(31.2 Migration Options) +endobj +1401 0 obj +<< /S /GoTo /D (subsection.31.2.1) >> +endobj +1404 0 obj +(31.2.1 Planning for Success) +endobj +1405 0 obj +<< /S /GoTo /D (subsection.31.2.2) >> +endobj +1408 0 obj +(31.2.2 Samba Implementation Choices) +endobj +1409 0 obj +<< /S /GoTo /D (chapter.32) >> +endobj +1412 0 obj +(32 Portability) +endobj +1413 0 obj +<< /S /GoTo /D (section.32.1) >> +endobj +1416 0 obj +(32.1 HPUX) +endobj +1417 0 obj +<< /S /GoTo /D (section.32.2) >> +endobj +1420 0 obj +(32.2 SCO Unix) +endobj +1421 0 obj +<< /S /GoTo /D (section.32.3) >> +endobj +1424 0 obj +(32.3 DNIX) +endobj +1425 0 obj +<< /S /GoTo /D (section.32.4) >> +endobj +1428 0 obj +(32.4 RedHat Linux Rembrandt-II) +endobj +1429 0 obj +<< /S /GoTo /D (section.32.5) >> +endobj +1432 0 obj +(32.5 AIX) +endobj +1433 0 obj +<< /S /GoTo /D (subsection.32.5.1) >> +endobj +1436 0 obj +(32.5.1 Sequential Read Ahead) +endobj +1437 0 obj +<< /S /GoTo /D (section.32.6) >> +endobj +1440 0 obj +(32.6 Solaris) +endobj +1441 0 obj +<< /S /GoTo /D (subsection.32.6.1) >> +endobj +1444 0 obj +(32.6.1 Locking improvements) +endobj +1445 0 obj +<< /S /GoTo /D (subsection.32.6.2) >> +endobj +1448 0 obj +(32.6.2 Winbind on Solaris 9) +endobj +1449 0 obj +<< /S /GoTo /D (chapter.33) >> +endobj +1452 0 obj +(33 Samba and other CIFS clients) +endobj +1453 0 obj +<< /S /GoTo /D (section.33.1) >> +endobj +1456 0 obj +(33.1 Macintosh clients?) +endobj +1457 0 obj +<< /S /GoTo /D (section.33.2) >> +endobj +1460 0 obj +(33.2 OS2 Client) +endobj +1461 0 obj +<< /S /GoTo /D (subsection.33.2.1) >> +endobj +1464 0 obj +(33.2.1 How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?) +endobj +1465 0 obj +<< /S /GoTo /D (subsection.33.2.2) >> +endobj +1468 0 obj +(33.2.2 How can I configure OS/2 Warp 3 \(not Connect\), OS/2 1.2, 1.3 or 2.x for Samba?) +endobj +1469 0 obj +<< /S /GoTo /D (subsection.33.2.3) >> +endobj +1472 0 obj +(33.2.3 Are there any other issues when OS/2 \(any version\) is used as a client?) +endobj +1473 0 obj +<< /S /GoTo /D (subsection.33.2.4) >> +endobj +1476 0 obj +(33.2.4 How do I get printer driver download working for OS/2 clients?) +endobj +1477 0 obj +<< /S /GoTo /D (section.33.3) >> +endobj +1480 0 obj +(33.3 Windows for Workgroups) +endobj +1481 0 obj +<< /S /GoTo /D (subsection.33.3.1) >> +endobj +1484 0 obj +(33.3.1 Use latest TCP/IP stack from Microsoft) +endobj +1485 0 obj +<< /S /GoTo /D (subsection.33.3.2) >> +endobj +1488 0 obj +(33.3.2 Delete .pwl files after password change) +endobj +1489 0 obj +<< /S /GoTo /D (subsection.33.3.3) >> +endobj +1492 0 obj +(33.3.3 Configure WfW password handling) +endobj +1493 0 obj +<< /S /GoTo /D (subsection.33.3.4) >> +endobj +1496 0 obj +(33.3.4 Case handling of passwords) +endobj +1497 0 obj +<< /S /GoTo /D (subsection.33.3.5) >> +endobj +1500 0 obj +(33.3.5 Use TCP/IP as default protocol) +endobj +1501 0 obj +<< /S /GoTo /D (subsection.33.3.6) >> +endobj +1504 0 obj +(33.3.6 Speed improvement) +endobj +1505 0 obj +<< /S /GoTo /D (section.33.4) >> +endobj +1508 0 obj +(33.4 Windows '95/'98) +endobj +1509 0 obj +<< /S /GoTo /D (subsection.33.4.1) >> +endobj +1512 0 obj +(33.4.1 Speed improvement) +endobj +1513 0 obj +<< /S /GoTo /D (section.33.5) >> +endobj +1516 0 obj +(33.5 Windows 2000 Service Pack 2) +endobj +1517 0 obj +<< /S /GoTo /D (section.33.6) >> +endobj +1520 0 obj +(33.6 Windows NT 3.1) +endobj +1521 0 obj +<< /S /GoTo /D (chapter.34) >> +endobj +1524 0 obj +(34 SWAT - The Samba Web Admininistration Tool) +endobj +1525 0 obj +<< /S /GoTo /D (section.34.1) >> +endobj +1528 0 obj +(34.1 SWAT Features and Benefits) +endobj +1529 0 obj +<< /S /GoTo /D (subsection.34.1.1) >> +endobj +1532 0 obj +(34.1.1 Enabling SWAT for use) +endobj +1533 0 obj +<< /S /GoTo /D (subsection.34.1.2) >> +endobj +1536 0 obj +(34.1.2 Securing SWAT through SSL) +endobj +1537 0 obj +<< /S /GoTo /D (subsection.34.1.3) >> +endobj +1540 0 obj +(34.1.3 The SWAT Home Page) +endobj +1541 0 obj +<< /S /GoTo /D (subsection.34.1.4) >> +endobj +1544 0 obj +(34.1.4 Global Settings) +endobj +1545 0 obj +<< /S /GoTo /D (subsection.34.1.5) >> +endobj +1548 0 obj +(34.1.5 Share Settings) +endobj +1549 0 obj +<< /S /GoTo /D (subsection.34.1.6) >> +endobj +1552 0 obj +(34.1.6 Printers Settings) +endobj +1553 0 obj +<< /S /GoTo /D (subsection.34.1.7) >> +endobj +1556 0 obj +(34.1.7 The SWAT Wizard) +endobj +1557 0 obj +<< /S /GoTo /D (subsection.34.1.8) >> +endobj +1560 0 obj +(34.1.8 The Status Page) +endobj +1561 0 obj +<< /S /GoTo /D (subsection.34.1.9) >> +endobj +1564 0 obj +(34.1.9 The View Page) +endobj +1565 0 obj +<< /S /GoTo /D (subsection.34.1.10) >> +endobj +1568 0 obj +(34.1.10 The Password Change Page) +endobj +1569 0 obj +<< /S /GoTo /D (chapter.35) >> +endobj +1572 0 obj +(35 Samba performance issues) +endobj +1573 0 obj +<< /S /GoTo /D (section.35.1) >> +endobj +1576 0 obj +(35.1 Comparisons) +endobj +1577 0 obj +<< /S /GoTo /D (section.35.2) >> +endobj +1580 0 obj +(35.2 Socket options) +endobj +1581 0 obj +<< /S /GoTo /D (section.35.3) >> +endobj +1584 0 obj +(35.3 Read size) +endobj +1585 0 obj +<< /S /GoTo /D (section.35.4) >> +endobj +1588 0 obj +(35.4 Max xmit) +endobj +1589 0 obj +<< /S /GoTo /D (section.35.5) >> +endobj +1592 0 obj +(35.5 Log level) +endobj +1593 0 obj +<< /S /GoTo /D (section.35.6) >> +endobj +1596 0 obj +(35.6 Read raw) +endobj +1597 0 obj +<< /S /GoTo /D (section.35.7) >> +endobj +1600 0 obj +(35.7 Write raw) +endobj +1601 0 obj +<< /S /GoTo /D (section.35.8) >> +endobj +1604 0 obj +(35.8 Slow Logins) +endobj +1605 0 obj +<< /S /GoTo /D (section.35.9) >> +endobj +1608 0 obj +(35.9 Client tuning) +endobj +1609 0 obj +<< /S /GoTo /D [1610 0 R /Fit ] >> +endobj +1612 0 obj << +/Length 244 +/Filter /FlateDecode +>> +stream +xڍOK09&dw ]E[z;ݮh yyo24^scR+oչ!Y5RH$SSd֥:$oȃp흽]m֮Fr5؛yn'5hmc;> {w_r"OǼA0jB@ +A"e%j~l7qjҡ_9i%> u__8qeendstream +endobj +1610 0 obj << +/Type /Page +/Contents 1612 0 R +/Resources 1611 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1621 0 R +>> endobj +1613 0 obj << +/D [1610 0 R /XYZ 85.039 786.531 null] +>> endobj +1614 0 obj << +/D [1610 0 R /XYZ 85.039 766.606 null] +>> endobj +1611 0 obj << +/Font << /F20 1617 0 R /F21 1620 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1624 0 obj << +/Length 1386 +/Filter /FlateDecode +>> +stream +xڕWMs6 WxrYyfH"%Y3\zCVlmd#x(vA|d_2[dQYȣL%*mi*q:SQ5_X N\e0M( +J?,n~IYGe\Ζ,wu?UV0-K>@V~gmZ$jۊ;e'Ah V,hٝ M1̇iǠjq` +([OՉd؉%yMGhj=n:8x8/Ӑ '>:1\kNj~\joIЁi7㎲ +@u2o,й#D$  ,UHϿ.R%u{fyvBJ!+:igq'#TM3>e>"{]ށe.z^n0 .N>""Yɒie"Ua{pSnd pr$"M:rDBuJVz7 nnNSԛD\H(-iDEq^'n eqA.bZ f[$h~k*oTɑ2DMuigLo3g7 Lոu8_]" +Uۍe6,RGn<O-7U3f(k!!]owL?YL.ߍw$JdG եXEEHKųZ:zAuф$MI΄j$ـ\ +:hzav=^oiI)wlQ$O/8$; Swx: /EVgڲlwCZ.˧ 4ehܯ^1WwR݀Ɓ3ʥ5!)G.N_ysM ڎH@5pV?E:\a49P.~ENGu$l?>q'/vA,[?ĉ/RN\;Aʦzk-5ME蹋n3k<-^5<C/!D4599,t8z/a0ФȱϩX1q8+gϮSB_L|=CJ55,×HH%wLԲ$*8#TvV˝!c2=링ֹ!=8qM;p[:hFB_"9Mun/fc5 k{ Z2v_5 +`'E*Q Eendstream +endobj +1623 0 obj << +/Type /Page +/Contents 1624 0 R +/Resources 1622 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1621 0 R +/Annots [ 1629 0 R 1633 0 R 1634 0 R 1635 0 R ] +>> endobj +1629 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [210.406 523.32 332.67 535.312] +/Subtype/Link/A<> +>> endobj +1633 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.346 509.468 215.702 522.369] +/Subtype/Link/A<> +>> endobj +1634 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [220.377 509.468 289.612 522.369] +/Subtype/Link/A<> +>> endobj +1635 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [304.619 509.468 410.324 522.369] +/Subtype/Link/A<> +>> endobj +1625 0 obj << +/D [1623 0 R /XYZ 85.039 786.531 null] +>> endobj +1622 0 obj << +/Font << /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1638 0 obj << +/Length 554 +/Filter /FlateDecode +>> +stream +xڥT0>1ؽRi]zI`;clC 3ofޛOd:eJ +RNYbFpq&啓 +0wLCA$Sm|=W񱄜KݶTL+IδN.1X)_TJ 3$!ꅮmцԒ>6m:|[S&y%3wǂia|=|׌@#Nh +ڇQi9kdԅM!D3;լ'xZSy$:j|=˺7>xZãmJY0%)+ +,5NT%ƙނʘQ#@`?oK(Um %<7vfw +ȽN=V:6P~s㌢{~9Z5zS83g;5N7WNȱr#Wp2; ˫Cߖ~䝅Y{XG7WZf(d> endobj +1643 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [156.148 704.616 341.202 715.741] +/Subtype/Link/A<> +>> endobj +1639 0 obj << +/D [1637 0 R /XYZ 85.039 786.531 null] +>> endobj +1636 0 obj << +/Font << /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1646 0 obj << +/Length 1747 +/Filter /FlateDecode +>> +stream +xZ[sF~[LD,OISwj)ㇶD2@qs! ˮu/]w`V'N}W Nf>0B**)eW|z2h[ =Zq48x:s}_tr092Nˢߩ6 }녰RhWe9s5$;0J5Íy4;'iQ=s&Qd L 2`>OVE&nońKa1+닀-n=][bp@ p2͆tlEc~hY^I,Q$ jgXփQ8Q4q6KGݞ +/2 5Ϸm\v v.h,`6ujܢ6j4I3l|)Pom+Bt;B܄Q/ălJ.)tI4./=Q6! .D@) h$&ƌ,`\"T{~JEW ,gWFiC v``ay88sN~Goqe+;KۼoLG|׸l0H _m_dC<]MK"؍aؼqpI0.;do_ljs_a&ZπG h ѱq91DeʻjQT5tRVv!b vFXv,p<6R.lSr!aJ]fb@-T^v)"%<8MV/x, }u!6R(4G틔/A4^b}{碩Fi57BL u_֚IU!0r-b\"d+|j*N>52˩bg#*|凱e-ǐo̓ӯ~_ mg]HGf| +U &*̼!GzMc9 k6C"QJ I>D.W/%р[/ܩbpMV} 1E{6)}l2ͪ~-CL_[ktx>R<$oL.WFe߾FF_ +\Y1shEMjdp]؈쁋y"Ydc P +Zŭ'UmWy_R.endstream +endobj +1645 0 obj << +/Type /Page +/Contents 1646 0 R +/Resources 1644 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1621 0 R +/Annots [ 1649 0 R 1650 0 R 1651 0 R 1652 0 R 1653 0 R 1654 0 R 1655 0 R 1656 0 R 1657 0 R 1658 0 R 1659 0 R 1660 0 R 1661 0 R 1662 0 R 1663 0 R 1664 0 R 1665 0 R 1666 0 R 1667 0 R 1668 0 R 1669 0 R 1670 0 R 1671 0 R 1672 0 R 1673 0 R 1674 0 R 1675 0 R 1676 0 R 1677 0 R 1678 0 R 1679 0 R 1680 0 R 1681 0 R 1682 0 R ] +>> endobj +1649 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [497.163 617.124 512.306 627.419] +/Subtype /Link +/A << /S /GoTo /D (part.1) >> +>> endobj +1650 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 592.666 512.306 602.234] +/Subtype /Link +/A << /S /GoTo /D (chapter.1) >> +>> endobj +1651 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 579.116 512.306 588.139] +/Subtype /Link +/A << /S /GoTo /D (section.1.1) >> +>> endobj +1652 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 565.567 512.306 574.59] +/Subtype /Link +/A << /S /GoTo /D (section.1.2) >> +>> endobj +1653 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 552.018 512.306 561.041] +/Subtype /Link +/A << /S /GoTo /D (section.1.3) >> +>> endobj +1654 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 538.469 512.306 547.492] +/Subtype /Link +/A << /S /GoTo /D (section.1.4) >> +>> endobj +1655 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 524.92 512.306 533.942] +/Subtype /Link +/A << /S /GoTo /D (section.1.5) >> +>> endobj +1656 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 511.37 512.306 520.393] +/Subtype /Link +/A << /S /GoTo /D (section.1.6) >> +>> endobj +1657 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 497.821 512.306 506.844] +/Subtype /Link +/A << /S /GoTo /D (section.1.7) >> +>> endobj +1658 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 473.363 512.306 482.931] +/Subtype /Link +/A << /S /GoTo /D (chapter.2) >> +>> endobj +1659 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 459.814 512.306 468.837] +/Subtype /Link +/A << /S /GoTo /D (section.2.1) >> +>> endobj +1660 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 446.265 512.306 455.287] +/Subtype /Link +/A << /S /GoTo /D (section.2.2) >> +>> endobj +1661 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 432.715 512.306 441.738] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.2.1) >> +>> endobj +1662 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 419.166 512.306 428.189] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.2.2.1.1) >> +>> endobj +1663 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 405.617 512.306 414.64] +/Subtype /Link +/A << /S /GoTo /D (subsection.2.2.2) >> +>> endobj +1664 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 392.068 512.306 401.091] +/Subtype /Link +/A << /S /GoTo /D (section.2.3) >> +>> endobj +1665 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 378.519 512.306 387.541] +/Subtype /Link +/A << /S /GoTo /D (section.2.4) >> +>> endobj +1666 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 351.42 512.306 360.443] +/Subtype /Link +/A << /S /GoTo /D (section.2.5) >> +>> endobj +1667 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 337.871 512.306 346.894] +/Subtype /Link +/A << /S /GoTo /D (section.2.6) >> +>> endobj +1668 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [497.163 299.378 512.306 309.672] +/Subtype /Link +/A << /S /GoTo /D (part.2) >> +>> endobj +1669 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 274.919 512.306 284.488] +/Subtype /Link +/A << /S /GoTo /D (chapter.3) >> +>> endobj +1670 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 261.37 512.306 270.393] +/Subtype /Link +/A << /S /GoTo /D (section.3.1) >> +>> endobj +1671 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 247.821 512.306 256.844] +/Subtype /Link +/A << /S /GoTo /D (section.3.2) >> +>> endobj +1672 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 234.272 512.306 243.295] +/Subtype /Link +/A << /S /GoTo /D (section.3.3) >> +>> endobj +1673 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 220.723 512.306 229.745] +/Subtype /Link +/A << /S /GoTo /D (subsection.3.3.1) >> +>> endobj +1674 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 196.264 512.306 205.833] +/Subtype /Link +/A << /S /GoTo /D (chapter.4) >> +>> endobj +1675 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 182.715 512.306 191.738] +/Subtype /Link +/A << /S /GoTo /D (section.4.1) >> +>> endobj +1676 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 169.166 512.306 178.189] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1.1) >> +>> endobj +1677 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 155.617 512.306 164.64] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1.2) >> +>> endobj +1678 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 142.068 512.306 151.09] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1.3) >> +>> endobj +1679 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 114.969 512.306 123.992] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.4.1.3.1) >> +>> endobj +1680 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 101.42 512.306 110.443] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.4.1.3.2) >> +>> endobj +1681 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 87.871 512.306 96.894] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1.4) >> +>> endobj +1682 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 60.772 512.306 69.795] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.4.1.4.1) >> +>> endobj +1647 0 obj << +/D [1645 0 R /XYZ 85.039 786.531 null] +>> endobj +1648 0 obj << +/D [1645 0 R /XYZ 85.039 656.613 null] +>> endobj +1644 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1685 0 obj << +/Length 2278 +/Filter /FlateDecode +>> +stream +x[oFB(T4 6iCHKӏ<)hu)<ߊ +()%i2 Z‘/)U4Z_$_EiFK:_CdEI%4bD|oPEAޅ}56)"hlɃ9U?vkM ~OXтYsIn?R lwnb@W5^l}tp_XϞ_lU R!:L dRʅ2- +=MN$)#=#ZRHqȝ iX'Qq +7 tk Jblyƴc7nL27W=us;>_צ.ԧK&Eodg4 ç &H㟖jHJ<&>'65M: ϓK`&P7epk9o)3oKMhVuF/ *O__z/Óyp+ @Հ/5l +:֜ӧ_i>4&?yyA}_XGu9_t濣@īht QϭE5O]<˪䆶j?j3xj01( fmWtć6Ok5D]/t\\f~?f$J6Cx 4i~ zf(Si=ey2;-j +j#z^W}b$ Ol{5Gmy4 +ᐳrӕoǍ@(Jm5@0LN\q7OupW]3͐1^-;Q 9ՙz"-hD :-uv= +6@AW 2H㗃 AӐWO4i7N]e_ފd?LeGM%ȅ>R YI`:SIq50c}2-UT_A+֧EIrۮ@FgT@45%H߂V)tg^(bW[Iv6wnnˎ.7A9kկc߲$*M3_!vDE5ݏ0qS;:EL1)n43N.wE%QcUad2$N5>fa&"I4<!QzcR@-Jgha]h1_>X!)<5YB_S)(]DGQ'"(x '/ r^PrJl,2.Mj9(?q2q7Q؇&F0MP&G&S.tC|w"9/KUѝJVP/S:7Kck0_ćI-b;]fOkۨ Ҝs,|-_Ɨ)81ǮHfWx2K(&ۭ9-*ֹq_4=tK Oq#3շfr4;6LR0Z*udW/n䖏[Pcć2xJ~^x/ ^~wv+A5J'kc6{7|"l#%lW?A-/zZҺeYeg`,7W3U&KȖ2١-w4@Q6.F4ٶp@W*'Mw՝?> endobj +1690 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 754.651 512.306 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsection.4.1.5) >> +>> endobj +1691 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 730.193 512.306 739.761] +/Subtype /Link +/A << /S /GoTo /D (chapter.5) >> +>> endobj +1692 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 716.643 512.306 725.666] +/Subtype /Link +/A << /S /GoTo /D (section.5.1) >> +>> endobj +1693 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 703.094 512.306 712.117] +/Subtype /Link +/A << /S /GoTo /D (section.5.2) >> +>> endobj +1694 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 689.545 512.306 698.568] +/Subtype /Link +/A << /S /GoTo /D (section.5.3) >> +>> endobj +1695 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 675.996 512.306 685.019] +/Subtype /Link +/A << /S /GoTo /D (section.5.4) >> +>> endobj +1696 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 662.447 512.306 671.469] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.4.1) >> +>> endobj +1697 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 648.897 512.306 657.92] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.4.2) >> +>> endobj +1698 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 635.348 512.306 644.371] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.4.3) >> +>> endobj +1699 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 621.799 512.306 630.822] +/Subtype /Link +/A << /S /GoTo /D (section.5.5) >> +>> endobj +1700 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 608.25 512.306 617.273] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.5.1) >> +>> endobj +1701 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 567.602 512.306 576.625] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.5.2) >> +>> endobj +1702 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 554.053 512.306 563.076] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.5.3) >> +>> endobj +1703 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 526.955 512.306 535.978] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.5.4) >> +>> endobj +1704 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 499.856 512.306 508.879] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.5.5) >> +>> endobj +1705 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 486.307 512.306 495.33] +/Subtype /Link +/A << /S /GoTo /D (section.5.6) >> +>> endobj +1706 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 472.758 512.306 481.781] +/Subtype /Link +/A << /S /GoTo /D (subsection.5.6.1) >> +>> endobj +1707 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 448.3 512.306 457.868] +/Subtype /Link +/A << /S /GoTo /D (chapter.6) >> +>> endobj +1708 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 434.75 512.306 443.773] +/Subtype /Link +/A << /S /GoTo /D (section.6.1) >> +>> endobj +1709 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 421.201 512.306 430.224] +/Subtype /Link +/A << /S /GoTo /D (section.6.2) >> +>> endobj +1710 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 407.652 512.306 416.675] +/Subtype /Link +/A << /S /GoTo /D (section.6.3) >> +>> endobj +1711 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 394.103 512.306 403.126] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.3.1) >> +>> endobj +1712 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 380.554 512.306 389.576] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.3.2) >> +>> endobj +1713 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 367.004 512.306 376.027] +/Subtype /Link +/A << /S /GoTo /D (section.6.4) >> +>> endobj +1714 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 353.455 512.306 362.478] +/Subtype /Link +/A << /S /GoTo /D (section.6.5) >> +>> endobj +1715 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 339.906 512.306 348.929] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.5.1) >> +>> endobj +1716 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 326.357 512.306 335.38] +/Subtype /Link +/A << /S /GoTo /D (subsection.6.5.2) >> +>> endobj +1717 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 301.899 512.306 311.467] +/Subtype /Link +/A << /S /GoTo /D (chapter.7) >> +>> endobj +1718 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 288.349 512.306 297.372] +/Subtype /Link +/A << /S /GoTo /D (section.7.1) >> +>> endobj +1719 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 274.8 512.306 283.823] +/Subtype /Link +/A << /S /GoTo /D (section.7.2) >> +>> endobj +1720 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 261.251 512.306 270.274] +/Subtype /Link +/A << /S /GoTo /D (section.7.3) >> +>> endobj +1721 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 247.702 512.306 256.725] +/Subtype /Link +/A << /S /GoTo /D (subsection.7.3.1) >> +>> endobj +1722 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 234.153 512.306 243.175] +/Subtype /Link +/A << /S /GoTo /D (section.7.4) >> +>> endobj +1723 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 220.603 512.306 229.626] +/Subtype /Link +/A << /S /GoTo /D (section.7.5) >> +>> endobj +1724 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 207.054 512.306 216.077] +/Subtype /Link +/A << /S /GoTo /D (section.7.6) >> +>> endobj +1725 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 182.596 512.306 192.164] +/Subtype /Link +/A << /S /GoTo /D (chapter.8) >> +>> endobj +1726 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 169.047 512.306 178.069] +/Subtype /Link +/A << /S /GoTo /D (section.8.1) >> +>> endobj +1727 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 155.497 512.306 164.52] +/Subtype /Link +/A << /S /GoTo /D (section.8.2) >> +>> endobj +1728 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [497.163 117.004 512.306 127.299] +/Subtype /Link +/A << /S /GoTo /D (part.3) >> +>> endobj +1686 0 obj << +/D [1684 0 R /XYZ 85.039 786.531 null] +>> endobj +1683 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1731 0 obj << +/Length 2156 +/Filter /FlateDecode +>> +stream +x\RV}WQ~*\!дRL&I dؖ+%}>7F $]@k}9ko9v%w>#a7t9挠K3<;u{~N9~i/^MMԧ]|' | ~I23JqgE]}UڧA IKI O8=Q4S{쑗R(B5FD,DFtX k2UR)?{y+ 6$߬yՍMQ<zBw=IӴ6QEbB.E)| *5+~BNTjfT(W3pǛˈj'l +< P//U7N&J`ׇL3R5fp(Ý7rC 7Gr=J4G[2_ +Aďgye'=<vd"+`fQ+AiϸpcxI^eI]&9/xyiC0_35't9VqŜ7KdY*^Z R>d4m\|P^o1Fx!9Bts0~RcVLmS%ʋ/zI!|~ -Fژ+-&7I΂*= "ȷ"0u˰gl;J#rU5zbd +᫤/@5l]/h'x3'LS ǂlயO1Lu4TfmmHY$Bga9:8XbXv7 +YBqd'Qvje@8,BƝZָkq9X9l6|w>LDŽq6L.Bg:3D9Knr$i5R]gDBY1 0@He\Ƹbi3!Z\5GE; _O7?Bn#So#?EO +KTL[ P\$2lڝMw0`g^D6W97[Y$6oAȲ87Tۻ͹n=[PMiMxH."ciXBkȽ==KPZ-D`[kdSUZbk,Iz$rzZܴU> endobj +1733 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 754.651 512.306 764.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.9) >> +>> endobj +1734 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.9.1) >> +>> endobj +1735 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (section.9.2) >> +>> endobj +1736 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (section.9.3) >> +>> endobj +1737 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.1) >> +>> endobj +1738 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 686.905 512.306 695.928] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.2) >> +>> endobj +1739 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 673.356 512.306 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.3) >> +>> endobj +1740 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 659.807 512.306 668.829] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.4) >> +>> endobj +1741 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 646.257 512.306 655.28] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.5) >> +>> endobj +1742 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 632.708 512.306 641.731] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.6) >> +>> endobj +1743 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 619.159 512.306 628.182] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.7) >> +>> endobj +1744 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 605.61 512.306 614.633] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.3.8) >> +>> endobj +1745 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 592.061 512.306 601.083] +/Subtype /Link +/A << /S /GoTo /D (section.9.4) >> +>> endobj +1746 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 578.511 512.306 587.534] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.1) >> +>> endobj +1747 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 564.962 512.306 573.985] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.2) >> +>> endobj +1748 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 551.413 512.306 560.436] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.4.3) >> +>> endobj +1749 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 537.864 512.306 546.887] +/Subtype /Link +/A << /S /GoTo /D (section.9.5) >> +>> endobj +1750 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 524.315 512.306 533.337] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.5.1) >> +>> endobj +1751 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 510.765 512.306 519.788] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.5.2) >> +>> endobj +1752 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 497.216 512.306 506.239] +/Subtype /Link +/A << /S /GoTo /D (section.9.6) >> +>> endobj +1753 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 483.667 512.306 492.69] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.6.1) >> +>> endobj +1754 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 470.118 512.306 479.141] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.6.2) >> +>> endobj +1755 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 456.569 512.306 465.591] +/Subtype /Link +/A << /S /GoTo /D (subsection.9.6.3) >> +>> endobj +1756 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 443.019 512.306 452.042] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.9.6.3.1) >> +>> endobj +1757 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 418.561 512.306 428.129] +/Subtype /Link +/A << /S /GoTo /D (chapter.10) >> +>> endobj +1758 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 405.012 512.306 414.035] +/Subtype /Link +/A << /S /GoTo /D (section.10.1) >> +>> endobj +1759 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 391.463 512.306 400.486] +/Subtype /Link +/A << /S /GoTo /D (section.10.2) >> +>> endobj +1760 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 377.914 512.306 386.936] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.2.1) >> +>> endobj +1761 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 364.364 512.306 373.387] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.2.2) >> +>> endobj +1762 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 350.815 512.306 359.838] +/Subtype /Link +/A << /S /GoTo /D (section.10.3) >> +>> endobj +1763 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 337.266 512.306 346.289] +/Subtype /Link +/A << /S /GoTo /D (section.10.4) >> +>> endobj +1764 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 323.717 512.306 332.74] +/Subtype /Link +/A << /S /GoTo /D (section.10.5) >> +>> endobj +1765 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 310.168 512.306 319.19] +/Subtype /Link +/A << /S /GoTo /D (section.10.6) >> +>> endobj +1766 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 296.618 512.306 305.641] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.1) >> +>> endobj +1767 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 283.069 512.306 292.092] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.2) >> +>> endobj +1768 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 269.52 512.306 278.543] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.3) >> +>> endobj +1769 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 255.971 512.306 264.994] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.4) >> +>> endobj +1770 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 242.422 512.306 251.444] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.5) >> +>> endobj +1771 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 228.872 512.306 237.895] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.10.6.5.1) >> +>> endobj +1772 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 215.323 512.306 224.346] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.10.6.5.2) >> +>> endobj +1773 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 201.774 512.306 210.797] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.6) >> +>> endobj +1774 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 188.225 512.306 197.248] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.7) >> +>> endobj +1775 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 174.676 512.306 183.698] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.8) >> +>> endobj +1776 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 161.126 512.306 170.149] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.6.9) >> +>> endobj +1777 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 147.577 512.306 156.6] +/Subtype /Link +/A << /S /GoTo /D (section.10.7) >> +>> endobj +1778 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 134.028 512.306 143.051] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.7.1) >> +>> endobj +1779 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 120.479 512.306 129.502] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.7.2) >> +>> endobj +1780 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 106.93 512.306 115.952] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.7.3) >> +>> endobj +1781 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 93.38 512.306 102.403] +/Subtype /Link +/A << /S /GoTo /D (subsection.10.7.4) >> +>> endobj +1782 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 79.831 512.306 88.854] +/Subtype /Link +/A << /S /GoTo /D (section.10.8) >> +>> endobj +1732 0 obj << +/D [1730 0 R /XYZ 85.039 786.531 null] +>> endobj +1729 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1785 0 obj << +/Length 2200 +/Filter /FlateDecode +>> +stream +x\KoFWT,$wOEj7&p#.@KLDU>wf_$&~HmY0`Q$mη3cI>\~C7?Y f^>3 ee +Oǟ)$[|(ǯ{72OG??T5{.豀7aX_]'_C깜sHnbZw0ys>I8q~)<8̆/8PSu,ـzuގ `ׁ8ml~mRM,è|W^}`VWwٖ~DguC +&"%AHQ>cΟir.gpj)UgY e +~eD Ua(`8QRY$RUȕwS'Oxcl[q#?h{->o9kwܒ7>ȔZo>ֵz2SF'7D.hDE7x1_⑾*Εy5>ۃ?mbC;"1h½^y85zvO?؂QcA-7#7M,JMsa5\pF NjŤ#A2m`rf??|%54Qc$AEؿ +){I4M?[3j RP5̓ "%7P&NJE`jltǓ25:Eg2\Sr3\ƆAk#..5,O\|IX&et١G2GzP}+҅4M>%U@ -nV +A*Ϫ:|V88{wsK|`] +;Ȃ*Y J4p̔,ZX+2cn7h!B9蕸30!J/zlZ-ݔRmj*"F肀1݉#h&^:пI}>'1X#\L4JJePS ,'RwצQ(ҝHdvh o i-ob'AG@0 ċTI[>oX- ]맒f̸u^_QHx Vat5!&s#P%0Cw]͚=[4 ^g*gsUAďtjOHQK.0c +F-TWkt?9[SVc1)nˊ8x(P`Hշ[k"|*l %d3<'T7wE5bͧi2*Y<ޖ`vĶZ q'8kشOژ٧{1|N?D{oD{(ST"-v SQXD $@Duo4e:%85o@!u$@lѳf;)iS9%2KLjtcDA{'lYuB WzK2 /8wp08|"]2˲~wc_6m/]ߺw +Q|=s#KI*M'M> endobj +1787 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 754.651 512.306 764.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.11) >> +>> endobj +1788 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.11.1) >> +>> endobj +1789 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (section.11.2) >> +>> endobj +1790 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (section.11.3) >> +>> endobj +1791 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (section.11.4) >> +>> endobj +1792 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 686.905 512.306 695.928] +/Subtype /Link +/A << /S /GoTo /D (subsection.11.4.1) >> +>> endobj +1793 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 673.356 512.306 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsection.11.4.2) >> +>> endobj +1794 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 659.807 512.306 668.829] +/Subtype /Link +/A << /S /GoTo /D (section.11.5) >> +>> endobj +1795 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 646.257 512.306 655.28] +/Subtype /Link +/A << /S /GoTo /D (section.11.6) >> +>> endobj +1796 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 632.708 512.306 641.731] +/Subtype /Link +/A << /S /GoTo /D (section.11.7) >> +>> endobj +1797 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 608.25 512.306 617.818] +/Subtype /Link +/A << /S /GoTo /D (chapter.12) >> +>> endobj +1798 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 583.792 512.306 593.36] +/Subtype /Link +/A << /S /GoTo /D (chapter.13) >> +>> endobj +1799 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 570.242 512.306 579.265] +/Subtype /Link +/A << /S /GoTo /D (section.13.1) >> +>> endobj +1800 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 556.693 512.306 565.716] +/Subtype /Link +/A << /S /GoTo /D (section.13.2) >> +>> endobj +1801 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 543.144 512.306 552.167] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.2.1) >> +>> endobj +1802 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 529.595 512.306 538.618] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.2.2) >> +>> endobj +1803 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 516.046 512.306 525.068] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.2.3) >> +>> endobj +1804 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 502.496 512.306 511.519] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.2.4) >> +>> endobj +1805 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 488.947 512.306 497.97] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.2.5) >> +>> endobj +1806 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 475.398 512.306 484.421] +/Subtype /Link +/A << /S /GoTo /D (section.13.3) >> +>> endobj +1807 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 461.849 512.306 470.872] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.3.1) >> +>> endobj +1808 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 448.3 512.306 457.322] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.3.2) >> +>> endobj +1809 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 434.75 512.306 443.773] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.3.3) >> +>> endobj +1810 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 421.201 512.306 430.224] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.3.4) >> +>> endobj +1811 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 407.652 512.306 416.675] +/Subtype /Link +/A << /S /GoTo /D (section.13.4) >> +>> endobj +1812 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 394.103 512.306 403.126] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.1) >> +>> endobj +1813 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 380.554 512.306 389.576] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.2) >> +>> endobj +1814 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 367.004 512.306 376.027] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.3) >> +>> endobj +1815 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 353.455 512.306 362.478] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.4) >> +>> endobj +1816 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 339.906 512.306 348.929] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.5) >> +>> endobj +1817 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 326.357 512.306 335.38] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.6) >> +>> endobj +1818 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 312.808 512.306 321.83] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.7) >> +>> endobj +1819 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 299.258 512.306 308.281] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.8) >> +>> endobj +1820 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 285.709 512.306 294.732] +/Subtype /Link +/A << /S /GoTo /D (subsection.13.4.9) >> +>> endobj +1821 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [498.314 261.251 512.306 270.819] +/Subtype /Link +/A << /S /GoTo /D (chapter.14) >> +>> endobj +1822 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 247.702 512.306 256.725] +/Subtype /Link +/A << /S /GoTo /D (section.14.1) >> +>> endobj +1823 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 234.153 512.306 243.175] +/Subtype /Link +/A << /S /GoTo /D (section.14.2) >> +>> endobj +1824 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 220.603 512.306 229.626] +/Subtype /Link +/A << /S /GoTo /D (section.14.3) >> +>> endobj +1825 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 207.054 512.306 216.077] +/Subtype /Link +/A << /S /GoTo /D (section.14.4) >> +>> endobj +1826 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 193.505 512.306 202.528] +/Subtype /Link +/A << /S /GoTo /D (section.14.5) >> +>> endobj +1827 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [499.405 179.956 512.306 188.979] +/Subtype /Link +/A << /S /GoTo /D (section.14.6) >> +>> endobj +1828 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 166.407 512.306 175.429] +/Subtype /Link +/A << /S /GoTo /D (section.14.7) >> +>> endobj +1829 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 152.857 512.306 161.88] +/Subtype /Link +/A << /S /GoTo /D (subsection.14.7.1) >> +>> endobj +1830 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 139.308 512.306 148.331] +/Subtype /Link +/A << /S /GoTo /D (section.14.8) >> +>> endobj +1831 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 125.759 512.306 134.782] +/Subtype /Link +/A << /S /GoTo /D (section.14.9) >> +>> endobj +1832 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 112.21 512.306 121.233] +/Subtype /Link +/A << /S /GoTo /D (subsection.14.9.1) >> +>> endobj +1833 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 98.661 512.306 107.683] +/Subtype /Link +/A << /S /GoTo /D (section.14.10) >> +>> endobj +1834 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 85.111 512.306 94.134] +/Subtype /Link +/A << /S /GoTo /D (section.14.11) >> +>> endobj +1835 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 71.562 512.306 80.585] +/Subtype /Link +/A << /S /GoTo /D (section.14.12) >> +>> endobj +1786 0 obj << +/D [1784 0 R /XYZ 85.039 786.531 null] +>> endobj +1783 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1839 0 obj << +/Length 2113 +/Filter /FlateDecode +>> +stream +x\rH}+7`YI:oTe K2LE $|힋;`*UA8gtO+vۂ?vwLmwMhܲCeV7{m =S7m6(Qt>rLR|o߭v ǖeo±eACMQuk-Z]WG2}c&u!/"֊_d;f(`k,;GOȆ٤aIفoW.8̄cۈ*\t Y.Jz3^9kSwP/MyY+Iz3 ono%I5bEԫ/3 N_t =p}c^5<BY3>OBUaF6FW1vm%PVX,ڐ 'd(Rv&z){C=sN?Z;T3JowH^N,s+E+n)*CՐ8~)H/[܍cYhEsOtϭr$aTTGDYu4?y&2 +vv?{[&ݓ_(v׆BG餔o M3<>T7Sy[Kw1DD2<)0U{؃|\EЀj} {rB;[}V'QAPQp>Yȋj~S$'5Ϭ߼S&=ߑ +{ Ӧ,eCVVtbۖjtNon:f-ݒ^7ۮTU~0*wc앮=[x,w&6uг:"X7iTJ^0V&^D'@hJBJK||>WpMH#^4 Q?{OE;>k/YB8S1Xnlm`˅gC,-]W~Y'TB\T-zz\#ciQ9Ϫr|Ó[lw+U"ʌ 曖<ޥ^ d`s?_Dendstream +endobj +1838 0 obj << +/Type /Page +/Contents 1839 0 R +/Resources 1837 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1836 0 R +/Annots [ 1841 0 R 1842 0 R 1843 0 R 1844 0 R 1845 0 R 1846 0 R 1847 0 R 1848 0 R 1849 0 R 1850 0 R 1851 0 R 1852 0 R 1853 0 R 1854 0 R 1855 0 R 1856 0 R 1857 0 R 1858 0 R 1859 0 R 1860 0 R 1861 0 R 1862 0 R 1863 0 R 1864 0 R 1865 0 R 1866 0 R 1867 0 R 1868 0 R 1869 0 R 1870 0 R 1871 0 R 1872 0 R 1873 0 R 1874 0 R 1875 0 R 1876 0 R 1877 0 R 1878 0 R 1879 0 R 1880 0 R 1881 0 R 1882 0 R 1883 0 R 1884 0 R 1885 0 R ] +>> endobj +1841 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 754.651 512.306 764.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.15) >> +>> endobj +1842 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.15.1) >> +>> endobj +1843 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (section.15.2) >> +>> endobj +1844 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (section.15.3) >> +>> endobj +1845 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.3.1) >> +>> endobj +1846 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 686.905 512.306 695.928] +/Subtype /Link +/A << /S /GoTo /D (section.15.4) >> +>> endobj +1847 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 673.356 512.306 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.1) >> +>> endobj +1848 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 659.807 512.306 668.829] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.2) >> +>> endobj +1849 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 646.257 512.306 655.28] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.3) >> +>> endobj +1850 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 632.708 512.306 641.731] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.4) >> +>> endobj +1851 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 619.159 512.306 628.182] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.5) >> +>> endobj +1852 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 605.61 512.306 614.633] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.4.6) >> +>> endobj +1853 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 592.061 512.306 601.083] +/Subtype /Link +/A << /S /GoTo /D (section.15.5) >> +>> endobj +1854 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 578.511 512.306 587.534] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.5.1) >> +>> endobj +1855 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 564.962 512.306 573.985] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.5.2) >> +>> endobj +1856 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 551.413 512.306 560.436] +/Subtype /Link +/A << /S /GoTo /D (subsection.15.5.3) >> +>> endobj +1857 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 537.864 512.306 546.887] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.1) >> +>> endobj +1858 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 510.765 512.306 519.788] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.2) >> +>> endobj +1859 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 497.216 512.306 506.239] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.3) >> +>> endobj +1860 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 483.667 512.306 492.69] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.4) >> +>> endobj +1861 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 470.118 512.306 479.141] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.5) >> +>> endobj +1862 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 456.569 512.306 465.591] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.6) >> +>> endobj +1863 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 443.019 512.306 452.042] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.7) >> +>> endobj +1864 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 429.47 512.306 438.493] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.15.5.3.8) >> +>> endobj +1865 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 415.921 512.306 424.944] +/Subtype /Link +/A << /S /GoTo /D (section.15.6) >> +>> endobj +1866 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 402.372 512.306 411.395] +/Subtype /Link +/A << /S /GoTo /D (section.15.7) >> +>> endobj +1867 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 377.914 512.306 387.482] +/Subtype /Link +/A << /S /GoTo /D (chapter.16) >> +>> endobj +1868 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 364.364 512.306 373.387] +/Subtype /Link +/A << /S /GoTo /D (section.16.1) >> +>> endobj +1869 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 350.815 512.306 359.838] +/Subtype /Link +/A << /S /GoTo /D (subsection.16.1.1) >> +>> endobj +1870 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 337.266 512.306 346.289] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.16.1.1.1) >> +>> endobj +1871 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 323.717 512.306 332.74] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.16.1.1.2) >> +>> endobj +1872 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 310.168 512.306 319.19] +/Subtype /Link +/A << /S /GoTo /D (section.16.2) >> +>> endobj +1873 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 296.618 512.306 305.641] +/Subtype /Link +/A << /S /GoTo /D (section.16.3) >> +>> endobj +1874 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 283.069 512.306 292.092] +/Subtype /Link +/A << /S /GoTo /D (subsection.16.3.1) >> +>> endobj +1875 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 258.611 512.306 268.179] +/Subtype /Link +/A << /S /GoTo /D (chapter.17) >> +>> endobj +1876 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 245.062 512.306 254.084] +/Subtype /Link +/A << /S /GoTo /D (section.17.1) >> +>> endobj +1877 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 231.512 512.306 240.535] +/Subtype /Link +/A << /S /GoTo /D (subsection.17.1.1) >> +>> endobj +1878 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 217.963 512.306 226.986] +/Subtype /Link +/A << /S /GoTo /D (subsection.17.1.2) >> +>> endobj +1879 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 204.414 512.306 213.437] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.17.1.2.1) >> +>> endobj +1880 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 190.865 512.306 199.888] +/Subtype /Link +/A << /S /GoTo /D (subsection.17.1.3) >> +>> endobj +1881 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 177.316 512.306 186.338] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.17.1.3.1) >> +>> endobj +1882 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 163.766 512.306 172.789] +/Subtype /Link +/A << /S /GoTo /D (section.17.2) >> +>> endobj +1883 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 150.217 512.306 159.24] +/Subtype /Link +/A << /S /GoTo /D (subsection.17.2.1) >> +>> endobj +1884 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 136.668 512.306 145.691] +/Subtype /Link +/A << /S /GoTo /D (subsection.17.2.2) >> +>> endobj +1885 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 123.119 512.306 132.142] +/Subtype /Link +/A << /S /GoTo /D (section.17.3) >> +>> endobj +1840 0 obj << +/D [1838 0 R /XYZ 85.039 786.531 null] +>> endobj +1837 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1888 0 obj << +/Length 2242 +/Filter /FlateDecode +>> +stream +x\[sH~WY}i*d<[NeyAƔy~26,IݒP߹I;ND1Վ +Fڃi+j`C36#)p~I$ +Uk}Jg>uh(:k_I\2[E(՞`=iZw1smy.t<"eÂʳӅpW +?D<5)xy*sAC|zkLZ]mO)UjDbcdofJ3lM3I3XsXE6|;IDF7ڊAkpE Q]Ae@2]Yl2(т8QFF|\Z1FKޥ +ڢIf7FX#Xsg!5]F\cڜ10;jR/N@ q^Mk:VrF{p_-92XB,ȷ`[hj]t){?۸y]9^#4pΓ_ K"~`G,ꇷO/+Ad*GdC>/ve_ƚ\ s&QfO 2:S54X[tr[EtkK\2t]ÉuW&(+pUq,J0I/ +3&āqh~p@_ + MQj3 SǙNbk$ⳉWVzV}0.z{ϙZ#Xo!+a/O m|/ah3!_ +6?白XSHLYi >AF ԊԨ5 s=C+Q5I)eH;P@yijyV[rIP5 +sJ^1XH#ciS{cjc, gFg6fȅHM$ +vRn98ϮSL*hWZ^WF5Gch;SBY1w՚M8tyF`W'y[\5yzp=uSrM7kBGf]]/|nec0Uwft|;J'j jT>$zJqgˎ -2 ă2z}㍘p#ڰu ]%݀Lua'R4&[u~ u80޲I.Y1ܺ{ ExɖF7B0<5VP>fF' U9$oy^kmKU5 pffR/W=OYY%4i+]K+Lo~ 9U&廰+^Ցoư%fFtSv {ز%Y</o{K`hֿK |MbZwL`R8|!&u]0wBCH_wuG+/>?'gz>.J]7Z"qk[.`^z% Yw Ixq1LkY'"V8?R oTT6x4ƽ(3N1fW +rHrъHzBIbLr,bp6L{up'm~YSò Ų-5}ē0Jffcm-"Pp)Y|endstream +endobj +1887 0 obj << +/Type /Page +/Contents 1888 0 R +/Resources 1886 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1836 0 R +/Annots [ 1890 0 R 1891 0 R 1892 0 R 1893 0 R 1894 0 R 1895 0 R 1896 0 R 1897 0 R 1898 0 R 1899 0 R 1900 0 R 1901 0 R 1902 0 R 1903 0 R 1904 0 R 1905 0 R 1906 0 R 1907 0 R 1908 0 R 1909 0 R 1910 0 R 1911 0 R 1912 0 R 1913 0 R 1914 0 R 1915 0 R 1916 0 R 1917 0 R 1918 0 R 1919 0 R 1920 0 R 1921 0 R 1922 0 R 1923 0 R 1924 0 R 1925 0 R 1926 0 R 1927 0 R 1928 0 R 1929 0 R 1930 0 R 1931 0 R 1932 0 R 1933 0 R 1934 0 R 1935 0 R 1936 0 R ] +>> endobj +1890 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 754.651 512.306 764.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.18) >> +>> endobj +1891 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.18.1) >> +>> endobj +1892 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.1.1) >> +>> endobj +1893 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.1.1) >> +>> endobj +1894 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.1.2) >> +>> endobj +1895 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 673.356 512.306 682.379] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.1.3) >> +>> endobj +1896 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 659.807 512.306 668.829] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.1.4) >> +>> endobj +1897 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 646.257 512.306 655.28] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.1.2) >> +>> endobj +1898 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 632.708 512.306 641.731] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.2.1) >> +>> endobj +1899 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 619.159 512.306 628.182] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.2.2) >> +>> endobj +1900 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 605.61 512.306 614.633] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.2.3) >> +>> endobj +1901 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 578.511 512.306 587.534] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.1.3) >> +>> endobj +1902 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 564.962 512.306 573.985] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.1.4) >> +>> endobj +1903 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 551.413 512.306 560.436] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.4.1) >> +>> endobj +1904 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 537.864 512.306 546.887] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.4.2) >> +>> endobj +1905 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 524.315 512.306 533.337] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.4.3) >> +>> endobj +1906 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 510.765 512.306 519.788] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.1.4.4) >> +>> endobj +1907 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 497.216 512.306 506.239] +/Subtype /Link +/A << /S /GoTo /D (section.18.2) >> +>> endobj +1908 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 483.667 512.306 492.69] +/Subtype /Link +/A << /S /GoTo /D (section.18.3) >> +>> endobj +1909 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 470.118 512.306 479.141] +/Subtype /Link +/A << /S /GoTo /D (section.18.4) >> +>> endobj +1910 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 456.569 512.306 465.591] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.4.1) >> +>> endobj +1911 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 443.019 512.306 452.042] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.18.4.1.1) >> +>> endobj +1912 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 429.47 512.306 438.493] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.4.2) >> +>> endobj +1913 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 415.921 512.306 424.944] +/Subtype /Link +/A << /S /GoTo /D (subsection.18.4.3) >> +>> endobj +1914 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 391.463 512.306 401.031] +/Subtype /Link +/A << /S /GoTo /D (chapter.19) >> +>> endobj +1915 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 377.914 512.306 386.936] +/Subtype /Link +/A << /S /GoTo /D (section.19.1) >> +>> endobj +1916 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 364.364 512.306 373.387] +/Subtype /Link +/A << /S /GoTo /D (section.19.2) >> +>> endobj +1917 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 350.815 512.306 359.838] +/Subtype /Link +/A << /S /GoTo /D (subsection.19.2.1) >> +>> endobj +1918 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 323.717 512.306 332.74] +/Subtype /Link +/A << /S /GoTo /D (subsection.19.2.2) >> +>> endobj +1919 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 310.168 512.306 319.19] +/Subtype /Link +/A << /S /GoTo /D (section.19.3) >> +>> endobj +1920 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 296.618 512.306 305.641] +/Subtype /Link +/A << /S /GoTo /D (subsection.19.3.1) >> +>> endobj +1921 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 283.069 512.306 292.092] +/Subtype /Link +/A << /S /GoTo /D (subsection.19.3.2) >> +>> endobj +1922 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 258.611 512.306 268.179] +/Subtype /Link +/A << /S /GoTo /D (chapter.20) >> +>> endobj +1923 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 245.062 512.306 254.084] +/Subtype /Link +/A << /S /GoTo /D (section.20.1) >> +>> endobj +1924 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 231.512 512.306 240.535] +/Subtype /Link +/A << /S /GoTo /D (subsection.20.1.1) >> +>> endobj +1925 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 217.963 512.306 226.986] +/Subtype /Link +/A << /S /GoTo /D (subsection.20.1.2) >> +>> endobj +1926 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 204.414 512.306 213.437] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.20.1.2.1) >> +>> endobj +1927 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 190.865 512.306 199.888] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.20.1.2.2) >> +>> endobj +1928 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 177.316 512.306 186.338] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.20.1.2.3) >> +>> endobj +1929 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 163.766 512.306 172.789] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.20.1.2.4) >> +>> endobj +1930 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 150.217 512.306 159.24] +/Subtype /Link +/A << /S /GoTo /D (section.20.2) >> +>> endobj +1931 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 125.759 512.306 135.327] +/Subtype /Link +/A << /S /GoTo /D (chapter.21) >> +>> endobj +1932 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 112.21 512.306 121.233] +/Subtype /Link +/A << /S /GoTo /D (section.21.1) >> +>> endobj +1933 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 98.661 512.306 107.683] +/Subtype /Link +/A << /S /GoTo /D (section.21.2) >> +>> endobj +1934 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 85.111 512.306 94.134] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.2.1) >> +>> endobj +1935 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 71.562 512.306 80.585] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.2.2) >> +>> endobj +1936 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 58.013 512.306 67.036] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.2.3) >> +>> endobj +1889 0 obj << +/D [1887 0 R /XYZ 85.039 786.531 null] +>> endobj +1886 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1939 0 obj << +/Length 1980 +/Filter /FlateDecode +>> +stream +x\rJ,B,ՃիTĉSyY A򓄝}n OX8Uֈ=AT[i&-}G޷=ks>zo &<} KjOZgϙzcm>^,n@xnꦉ)qN $Q}߁+5us? ^q`}i Y~IyQW0DS݉';_zc$3g:rɝ'UN1Xs\GQd/!\*/bM-)sh,hg5<ҫ jKtj, m(8?_Xw@U@";ҼsTi\A`w){VXcčYiphN+#;~yȢ|#xy셓pimQnޕG$Y`Z0\"+ +u ]W8104>&/. ]IÒ&@d_ʴ~F۴Y +}QZCp ) 'Et3r;`Odvq.Jw>)cOu\*B$[DZ}2[‰U5SxZsƚA#v%2[f?%3IT9kTڇd}+<9ى +/vF/=zxMHE2jrir'vh#y6_>|L_*DS<5νrb%E\ӢanӼ +ӣ:"FRQ-t :R[p`mAv?ym^br죨xl3 vCc?x˚Ɲ.!̽ǽ 16rTM(>푵S,IҍAgSiQɰl.9Mr ULPm8l-rzZX⸆ѓMN9 5y|M.XfY; oLh/TϳÖmLvs U7*";zk!S8:C1 [G;c ,٬Uhh~! \5%lVzt*.,(Jxam)Y9ZM81{niQ7$ Em;M%F3І(zG˭OqcBI!fUsﰰ=s_3Hl,)nTW68^RȿdƯlۀ1>~;L,k|2E l2W/2WRβtbұ21!ľ-4(=Je,1x2LLpF|ڢ,*D2,ދW#X$|/ncf07ŶҖo +L{Βp.^淨myҔFFxUr` FiV%ѲtJ6<ұBՉ]"k+'JP`E<B99WL܆6hƺں{plɋp++}T9f:5iR(rHeWqYNxA\b*ʫJɆ!#o0hỈ%d˪d@*﯇-bc+% B8ߧ[ #\R 6+RSJ=q }QX|dTR;o"j9{\I݁@_c)Q4QiA #=1qz16oZn.R[R5McM +^yDUJjA^peU58~,os΍a8endstream +endobj +1938 0 obj << +/Type /Page +/Contents 1939 0 R +/Resources 1937 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1836 0 R +/Annots [ 1941 0 R 1942 0 R 1943 0 R 1944 0 R 1945 0 R 1946 0 R 1947 0 R 1948 0 R 1949 0 R 1950 0 R 1951 0 R 1952 0 R 1953 0 R 1954 0 R 1955 0 R 1956 0 R 1957 0 R 1958 0 R 1959 0 R 1960 0 R 1961 0 R 1962 0 R 1963 0 R 1964 0 R 1965 0 R 1966 0 R 1967 0 R 1968 0 R 1969 0 R 1970 0 R 1971 0 R 1972 0 R 1973 0 R 1974 0 R 1975 0 R 1976 0 R 1977 0 R 1978 0 R 1979 0 R 1980 0 R 1981 0 R 1982 0 R 1983 0 R 1984 0 R 1985 0 R 1986 0 R ] +>> endobj +1941 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 754.651 512.306 763.674] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.2.4) >> +>> endobj +1942 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.21.3) >> +>> endobj +1943 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.3.1) >> +>> endobj +1944 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (subsection.21.3.2) >> +>> endobj +1945 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 689.545 512.306 699.113] +/Subtype /Link +/A << /S /GoTo /D (chapter.22) >> +>> endobj +1946 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 675.996 512.306 685.019] +/Subtype /Link +/A << /S /GoTo /D (section.22.1) >> +>> endobj +1947 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 662.447 512.306 671.469] +/Subtype /Link +/A << /S /GoTo /D (subsection.22.1.1) >> +>> endobj +1948 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 637.988 512.306 647.557] +/Subtype /Link +/A << /S /GoTo /D (chapter.23) >> +>> endobj +1949 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 624.439 512.306 633.462] +/Subtype /Link +/A << /S /GoTo /D (section.23.1) >> +>> endobj +1950 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 610.89 512.306 619.913] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.1.1) >> +>> endobj +1951 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 597.341 512.306 606.364] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.1.2) >> +>> endobj +1952 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 583.792 512.306 592.814] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.1.3) >> +>> endobj +1953 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 570.242 512.306 579.265] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.1.4) >> +>> endobj +1954 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 556.693 512.306 565.716] +/Subtype /Link +/A << /S /GoTo /D (section.23.2) >> +>> endobj +1955 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 543.144 512.306 552.167] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.2.1) >> +>> endobj +1956 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 529.595 512.306 538.618] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.2.2) >> +>> endobj +1957 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 516.046 512.306 525.068] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.2.3) >> +>> endobj +1958 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 502.496 512.306 511.519] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.2.4) >> +>> endobj +1959 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 488.947 512.306 497.97] +/Subtype /Link +/A << /S /GoTo /D (subsection.23.2.5) >> +>> endobj +1960 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 464.489 512.306 474.057] +/Subtype /Link +/A << /S /GoTo /D (chapter.24) >> +>> endobj +1961 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 450.94 512.306 459.963] +/Subtype /Link +/A << /S /GoTo /D (section.24.1) >> +>> endobj +1962 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 437.39 512.306 446.413] +/Subtype /Link +/A << /S /GoTo /D (section.24.2) >> +>> endobj +1963 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 423.841 512.306 432.864] +/Subtype /Link +/A << /S /GoTo /D (section.24.3) >> +>> endobj +1964 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 410.292 512.306 419.315] +/Subtype /Link +/A << /S /GoTo /D (section.24.4) >> +>> endobj +1965 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 396.743 512.306 405.766] +/Subtype /Link +/A << /S /GoTo /D (section.24.5) >> +>> endobj +1966 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 383.194 512.306 392.217] +/Subtype /Link +/A << /S /GoTo /D (section.24.6) >> +>> endobj +1967 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 369.645 512.306 378.667] +/Subtype /Link +/A << /S /GoTo /D (section.24.7) >> +>> endobj +1968 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 345.186 512.306 354.754] +/Subtype /Link +/A << /S /GoTo /D (chapter.25) >> +>> endobj +1969 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 331.637 512.306 340.66] +/Subtype /Link +/A << /S /GoTo /D (section.25.1) >> +>> endobj +1970 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 318.088 512.306 327.111] +/Subtype /Link +/A << /S /GoTo /D (section.25.2) >> +>> endobj +1971 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 304.539 512.306 313.561] +/Subtype /Link +/A << /S /GoTo /D (section.25.3) >> +>> endobj +1972 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 290.989 512.306 300.012] +/Subtype /Link +/A << /S /GoTo /D (section.25.4) >> +>> endobj +1973 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 266.531 512.306 276.099] +/Subtype /Link +/A << /S /GoTo /D (chapter.26) >> +>> endobj +1974 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 252.982 512.306 262.005] +/Subtype /Link +/A << /S /GoTo /D (section.26.1) >> +>> endobj +1975 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 239.433 512.306 248.456] +/Subtype /Link +/A << /S /GoTo /D (section.26.2) >> +>> endobj +1976 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 225.883 512.306 234.906] +/Subtype /Link +/A << /S /GoTo /D (section.26.3) >> +>> endobj +1977 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 212.334 512.306 221.357] +/Subtype /Link +/A << /S /GoTo /D (subsection.26.3.1) >> +>> endobj +1978 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 198.785 512.306 207.808] +/Subtype /Link +/A << /S /GoTo /D (subsection.26.3.2) >> +>> endobj +1979 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 185.236 512.306 194.259] +/Subtype /Link +/A << /S /GoTo /D (section.26.4) >> +>> endobj +1980 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 171.687 512.306 180.71] +/Subtype /Link +/A << /S /GoTo /D (section.26.5) >> +>> endobj +1981 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [490.587 133.194 512.306 143.488] +/Subtype /Link +/A << /S /GoTo /D (part.4) >> +>> endobj +1982 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 108.735 512.306 118.303] +/Subtype /Link +/A << /S /GoTo /D (chapter.27) >> +>> endobj +1983 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 95.186 512.306 104.209] +/Subtype /Link +/A << /S /GoTo /D (section.27.1) >> +>> endobj +1984 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 81.637 512.306 90.66] +/Subtype /Link +/A << /S /GoTo /D (section.27.2) >> +>> endobj +1985 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 68.088 512.306 77.11] +/Subtype /Link +/A << /S /GoTo /D (section.27.3) >> +>> endobj +1986 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 54.538 512.306 63.561] +/Subtype /Link +/A << /S /GoTo /D (section.27.4) >> +>> endobj +1940 0 obj << +/D [1938 0 R /XYZ 85.039 786.531 null] +>> endobj +1937 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +1989 0 obj << +/Length 2082 +/Filter /FlateDecode +>> +stream +x\YsH~Wf9twrΦ*Ƀk+s/lqJU4F鯏HݳMusLzoTsR#jUx/։e_?Sߍ$nPBy4~y^xIajZ>|Їe2߫2G5n3Lk[=^O|&|jn,x́+VɊg6>7Zq0D băF9}9$C|8 F@iIђT +_E^Lu98;ˁhEkEB0&sf: dFɩb! ʹqLp#8eY\#¹{<}e-)xٽE qKxJ ςW.a< +q :;'Y0Z k:f  8Iɫ8ʒ8\ixL<)T4":+cjvfwnu%Q|/ W~[KѥWQłFM!)}!f\}<p1mU +0"0!4QvN I]lH% +ڵ`RaspcȐ ҉+hE(P][{{hC$Jf9<^KRK9H>Z|iRa(xSl7d#Ff3G1:xY֯VOd 7E7E~t]ɋd|E%=4+Q WfWWcyvl(_,PBPήy9,׌Ih=Kӛ*p&ʴSpV6H#A]4@_ +5N/ @p,{$oQ=O]#fM{42YyFWElq)66 .iI,~;@N_ov:P҆&A&\8uw=E]P:&]JT8@Fa{v2 +s2|d +vxh'6nt"Yگ8Jug%zt<{2 "mor+ B36WefTAE_ 1AX ˉa7M7\@2V{UV(31!vI];hAοOTE#W"a^%u;wep]H KKX뾕bWEbFklY( +UU)QGE~P*Vk,ÈWBĆS`;U%c<9'Mx˕ YWI%6 ܥͩo'$?ӑ{MyB*P!3]p2C{WJυ>~ǓFl' | ;~ +XWߍJduv SiwG +qĆu! -RLc2H:wz)F1nUvFmZs%cAL;J@v5]bUVb/&I*d2 +dWD_h1M uRmqr:eFPr^xhb=/XnHYF] O^p=pCW.мp} $VxmpUZh;G_we{6QO,{o}[ȲO$"VwFi 4E<I {ByMYL ͐[qTqjPR s?endstream +endobj +1988 0 obj << +/Type /Page +/Contents 1989 0 R +/Resources 1987 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 1836 0 R +/Annots [ 1991 0 R 1992 0 R 1993 0 R 1994 0 R 1995 0 R 1996 0 R 1997 0 R 1998 0 R 1999 0 R 2000 0 R 2001 0 R 2002 0 R 2003 0 R 2004 0 R 2005 0 R 2006 0 R 2007 0 R 2008 0 R 2009 0 R 2010 0 R 2011 0 R 2012 0 R 2013 0 R 2014 0 R 2015 0 R 2016 0 R 2017 0 R 2018 0 R 2019 0 R 2020 0 R 2021 0 R 2022 0 R 2023 0 R 2024 0 R 2025 0 R 2026 0 R 2027 0 R 2028 0 R 2029 0 R 2030 0 R 2031 0 R 2032 0 R 2033 0 R 2034 0 R 2035 0 R 2036 0 R ] +>> endobj +1991 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 754.651 512.306 764.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.28) >> +>> endobj +1992 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (section.28.1) >> +>> endobj +1993 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (section.28.2) >> +>> endobj +1994 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (section.28.3) >> +>> endobj +1995 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 686.905 512.306 695.928] +/Subtype /Link +/A << /S /GoTo /D (section.28.4) >> +>> endobj +1996 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 673.356 512.306 682.379] +/Subtype /Link +/A << /S /GoTo /D (section.28.5) >> +>> endobj +1997 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 648.897 512.306 658.466] +/Subtype /Link +/A << /S /GoTo /D (chapter.29) >> +>> endobj +1998 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 635.348 512.306 644.371] +/Subtype /Link +/A << /S /GoTo /D (section.29.1) >> +>> endobj +1999 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 621.799 512.306 630.822] +/Subtype /Link +/A << /S /GoTo /D (section.29.2) >> +>> endobj +2000 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 608.25 512.306 617.273] +/Subtype /Link +/A << /S /GoTo /D (section.29.3) >> +>> endobj +2001 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 594.701 512.306 603.724] +/Subtype /Link +/A << /S /GoTo /D (section.29.4) >> +>> endobj +2002 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 581.151 512.306 590.174] +/Subtype /Link +/A << /S /GoTo /D (section.29.5) >> +>> endobj +2003 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 567.602 512.306 576.625] +/Subtype /Link +/A << /S /GoTo /D (section.29.6) >> +>> endobj +2004 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [490.587 529.109 512.306 539.404] +/Subtype /Link +/A << /S /GoTo /D (part.5) >> +>> endobj +2005 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 504.651 512.306 514.219] +/Subtype /Link +/A << /S /GoTo /D (chapter.30) >> +>> endobj +2006 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 491.102 512.306 500.124] +/Subtype /Link +/A << /S /GoTo /D (section.30.1) >> +>> endobj +2007 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 477.552 512.306 486.575] +/Subtype /Link +/A << /S /GoTo /D (subsection.30.1.1) >> +>> endobj +2008 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 464.003 512.306 473.026] +/Subtype /Link +/A << /S /GoTo /D (subsection.30.1.2) >> +>> endobj +2009 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 450.454 512.306 459.477] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.30.1.2.1) >> +>> endobj +2010 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 436.905 512.306 445.928] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.30.1.2.2) >> +>> endobj +2011 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 423.356 512.306 432.378] +/Subtype /Link +/A << /S /GoTo /D (section.30.2) >> +>> endobj +2012 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 409.806 512.306 418.829] +/Subtype /Link +/A << /S /GoTo /D (section.30.3) >> +>> endobj +2013 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 396.257 512.306 405.28] +/Subtype /Link +/A << /S /GoTo /D (section.30.4) >> +>> endobj +2014 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 382.708 512.306 391.731] +/Subtype /Link +/A << /S /GoTo /D (subsection.30.4.1) >> +>> endobj +2015 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 369.159 512.306 378.182] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.30.4.1.1) >> +>> endobj +2016 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 355.61 512.306 364.632] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.30.4.1.2) >> +>> endobj +2017 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 342.06 512.306 351.083] +/Subtype /Link +/A << /S /GoTo /D (section.30.5) >> +>> endobj +2018 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 328.511 512.306 337.534] +/Subtype /Link +/A << /S /GoTo /D (subsection.30.5.1) >> +>> endobj +2019 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 314.962 512.306 323.985] +/Subtype /Link +/A << /S /GoTo /D (subsection.30.5.2) >> +>> endobj +2020 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 290.504 512.306 300.072] +/Subtype /Link +/A << /S /GoTo /D (chapter.31) >> +>> endobj +2021 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 276.955 512.306 285.977] +/Subtype /Link +/A << /S /GoTo /D (section.31.1) >> +>> endobj +2022 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 263.405 512.306 272.428] +/Subtype /Link +/A << /S /GoTo /D (subsection.31.1.1) >> +>> endobj +2023 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 249.856 512.306 258.879] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.31.1.1.1) >> +>> endobj +2024 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 236.307 512.306 245.33] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.31.1.1.2) >> +>> endobj +2025 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 222.758 512.306 231.781] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.31.1.1.3) >> +>> endobj +2026 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 209.209 512.306 218.231] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.31.1.1.4) >> +>> endobj +2027 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 195.659 512.306 204.682] +/Subtype /Link +/A << /S /GoTo /D (subsubsection.31.1.1.5) >> +>> endobj +2028 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 182.11 512.306 191.133] +/Subtype /Link +/A << /S /GoTo /D (subsection.31.1.2) >> +>> endobj +2029 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 168.561 512.306 177.584] +/Subtype /Link +/A << /S /GoTo /D (section.31.2) >> +>> endobj +2030 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 155.012 512.306 164.035] +/Subtype /Link +/A << /S /GoTo /D (subsection.31.2.1) >> +>> endobj +2031 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 141.463 512.306 150.485] +/Subtype /Link +/A << /S /GoTo /D (subsection.31.2.2) >> +>> endobj +2032 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 117.004 512.306 126.573] +/Subtype /Link +/A << /S /GoTo /D (chapter.32) >> +>> endobj +2033 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 103.455 512.306 112.478] +/Subtype /Link +/A << /S /GoTo /D (section.32.1) >> +>> endobj +2034 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 89.906 512.306 98.929] +/Subtype /Link +/A << /S /GoTo /D (section.32.2) >> +>> endobj +2035 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 76.357 512.306 85.379] +/Subtype /Link +/A << /S /GoTo /D (section.32.3) >> +>> endobj +2036 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 62.807 512.306 71.83] +/Subtype /Link +/A << /S /GoTo /D (section.32.4) >> +>> endobj +1990 0 obj << +/D [1988 0 R /XYZ 85.039 786.531 null] +>> endobj +1987 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2039 0 obj << +/Length 2007 +/Filter /FlateDecode +>> +stream +x\[oH~WV#wJjwݬ'XLi=g.!4MHJ=6c|߹Cf$}U3_ryg^74O^t^Ijv%G0XL[o/ /|m|L}񹊚O|TsRp{4k3_6;8Վ(XJn|ݹ%x,QM3Fqy 5V[HiNu֢^jSPxg9>p]#ߕPoA}{%b~֠V:HZJRegPsDhY7<.+h"6r h$q+6Գ . l$1acq")04FB/NV b:7LMWc* 7Bk1"h\1bh`-m ז=Me9c`Pj˿%z6._3АqU޻2 {#{ 4`StЋBޑƟ>?cq#021=[aƲLlbm'^IjYaycNJ^gS8Ȝvx[S0ɒ-JZ!.1Krɠy32-!]t0+9s3L%SA26'KԲSR3nT߫o[c,6-Ոfp'`Xu^w sup0AGiڌ>2)՝.p ˿ A\]Z9W Q;HX%q$qN8l2:wX~ lb/ +c1 AKh ".{HΣc3dOo졗bA#3g {S'J.z#&NVD-\c4LĨ5E)@(|^ؠhD j+BÅ&B;4HzQbmЁaRwW}y}`RKi"u(7Qu,eM+;/JT8Vlk(쉊Z퐱J% jNP@n)F$w:kbӔ"|\X\]v Sa>|vn$}F&ZK8ե:`20 .!NpbCl0Օ`5ݗ+ D]:Zxܳ-O//,̧m,KAk*˲aV65l*e*>L7r*@vDgBJjv > endobj +2041 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 754.651 512.306 763.674] +/Subtype /Link +/A << /S /GoTo /D (section.32.5) >> +>> endobj +2042 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 741.102 512.306 750.125] +/Subtype /Link +/A << /S /GoTo /D (subsection.32.5.1) >> +>> endobj +2043 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 727.553 512.306 736.575] +/Subtype /Link +/A << /S /GoTo /D (section.32.6) >> +>> endobj +2044 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 714.003 512.306 723.026] +/Subtype /Link +/A << /S /GoTo /D (subsection.32.6.1) >> +>> endobj +2045 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 700.454 512.306 709.477] +/Subtype /Link +/A << /S /GoTo /D (subsection.32.6.2) >> +>> endobj +2046 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 675.996 512.306 685.564] +/Subtype /Link +/A << /S /GoTo /D (chapter.33) >> +>> endobj +2047 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 662.447 512.306 671.469] +/Subtype /Link +/A << /S /GoTo /D (section.33.1) >> +>> endobj +2048 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 648.897 512.306 657.92] +/Subtype /Link +/A << /S /GoTo /D (section.33.2) >> +>> endobj +2049 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 621.799 512.306 630.822] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.2.1) >> +>> endobj +2050 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 594.701 512.306 603.724] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.2.2) >> +>> endobj +2051 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 567.602 512.306 576.625] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.2.3) >> +>> endobj +2052 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 554.053 512.306 563.076] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.2.4) >> +>> endobj +2053 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 540.504 512.306 549.527] +/Subtype /Link +/A << /S /GoTo /D (section.33.3) >> +>> endobj +2054 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 526.955 512.306 535.978] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.1) >> +>> endobj +2055 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 513.406 512.306 522.428] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.2) >> +>> endobj +2056 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 499.856 512.306 508.879] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.3) >> +>> endobj +2057 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 486.307 512.306 495.33] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.4) >> +>> endobj +2058 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 472.758 512.306 481.781] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.5) >> +>> endobj +2059 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 459.209 512.306 468.232] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.3.6) >> +>> endobj +2060 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 445.66 512.306 454.682] +/Subtype /Link +/A << /S /GoTo /D (section.33.4) >> +>> endobj +2061 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 432.11 512.306 441.133] +/Subtype /Link +/A << /S /GoTo /D (subsection.33.4.1) >> +>> endobj +2062 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 418.561 512.306 427.584] +/Subtype /Link +/A << /S /GoTo /D (section.33.5) >> +>> endobj +2063 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 405.012 512.306 414.035] +/Subtype /Link +/A << /S /GoTo /D (section.33.6) >> +>> endobj +2064 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 380.554 512.306 390.122] +/Subtype /Link +/A << /S /GoTo /D (chapter.34) >> +>> endobj +2065 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 367.004 512.306 376.027] +/Subtype /Link +/A << /S /GoTo /D (section.34.1) >> +>> endobj +2066 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 353.455 512.306 362.478] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.1) >> +>> endobj +2067 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 339.906 512.306 348.929] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.2) >> +>> endobj +2068 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 326.357 512.306 335.38] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.3) >> +>> endobj +2069 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 312.808 512.306 321.83] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.4) >> +>> endobj +2070 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 299.258 512.306 308.281] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.5) >> +>> endobj +2071 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 285.709 512.306 294.732] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.6) >> +>> endobj +2072 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 272.16 512.306 281.183] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.7) >> +>> endobj +2073 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 258.611 512.306 267.634] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.8) >> +>> endobj +2074 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 245.062 512.306 254.084] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.9) >> +>> endobj +2075 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 231.512 512.306 240.535] +/Subtype /Link +/A << /S /GoTo /D (subsection.34.1.10) >> +>> endobj +2076 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [492.314 207.054 512.306 216.622] +/Subtype /Link +/A << /S /GoTo /D (chapter.35) >> +>> endobj +2077 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 193.505 512.306 202.528] +/Subtype /Link +/A << /S /GoTo /D (section.35.1) >> +>> endobj +2078 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 179.956 512.306 188.979] +/Subtype /Link +/A << /S /GoTo /D (section.35.2) >> +>> endobj +2079 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 166.407 512.306 175.429] +/Subtype /Link +/A << /S /GoTo /D (section.35.3) >> +>> endobj +2080 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 152.857 512.306 161.88] +/Subtype /Link +/A << /S /GoTo /D (section.35.4) >> +>> endobj +2081 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 139.308 512.306 148.331] +/Subtype /Link +/A << /S /GoTo /D (section.35.5) >> +>> endobj +2082 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 125.759 512.306 134.782] +/Subtype /Link +/A << /S /GoTo /D (section.35.6) >> +>> endobj +2083 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 112.21 512.306 121.233] +/Subtype /Link +/A << /S /GoTo /D (section.35.7) >> +>> endobj +2084 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 98.661 512.306 107.683] +/Subtype /Link +/A << /S /GoTo /D (section.35.8) >> +>> endobj +2085 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [493.95 85.111 512.306 94.134] +/Subtype /Link +/A << /S /GoTo /D (section.35.9) >> +>> endobj +2040 0 obj << +/D [2038 0 R /XYZ 85.039 786.531 null] +>> endobj +2037 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2088 0 obj << +/Length 226 +/Filter /FlateDecode +>> +stream +xmP;O1 WdL?\*C6p!C*s@SGg2LRM. yм)G@ A+?@ eMD5HQ B %mg4$i{}NȎNg%eud=#@.;|P,nr87 +=Lp. \ײ쵊@(ndhbz MlYendstream +endobj +2087 0 obj << +/Type /Page +/Contents 2088 0 R +/Resources 2086 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2090 0 R +>> endobj +2089 0 obj << +/D [2087 0 R /XYZ 85.039 786.531 null] +>> endobj +6 0 obj << +/D [2087 0 R /XYZ 85.039 547.583 null] +>> endobj +2086 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2093 0 obj << +/Length 3344 +/Filter /FlateDecode +>> +stream +x]o=0 +:X4)^ +ˎTĊ>$Zb-*OwKʢ>X;/FE:J8/wV~z FnE0Ya^0#}]$09;ƱLSz0j0 =guX*aFX83\W;]aLu0q?WJ ߃Kf+]N8up8r׍V%VQ8Ӳ: A(Wg+`SVBa^U!< K;nA KA\]d42bq2 F(av0sG-1,aX%;)nvkzj^R +_sPMnDKo (P-aJTL{~G\O՛%̞3}pRfԩj`(HR.cͤ3y:QlG 15͊ Nî" ݏD`^MhMWK:h&Tt(j&+\S:g`] >_៰{mZ W]F1h+d\]9]竜IQ*V|ń(#Z-O܀ +HV94/Pwy=ʧZjc߀ ֏!H*.p"̥sÕb8C +7Dj cZƊ[cen!͏0JNC(sp |yn7CI`a)p^W"4g#$⾠kp-(D5WPOy]w)F#Kgt]^oL v>$<j?`pW2Q4]^&j?hk@~+?Ӯ]E 1\?;~!B0F5 a/G,`Pe=2R_ Hc&0A`I;ԂC `]|#v3"opc38شV??|^Ms^B*6 P&~7uuA__!UiIg)?q|5=Fj|ٴ@cT)sq[՞(;!{4\ ЊL+ +e;;ly,׋|. +2<*Pzz{|7&|ExZ8glA+CoIzI8?QH8 I `l3!OYN>g!dRrgL ??޺P,목4OOɩmjVj0lG(JeCIiT/%̂ caʱ<-6') M#ܚRYm5cBcua^s/S뾣(̚66 +0 +S88;qQ9Qqԅ +BNz8tBhK4K`^ջ3rfcf]pbʈl6j-Q`WL\ǗnHK.ٽ!} 'hF}Ɗi-{씯?^R0K86l;| g2s@ܜ̼n(. +*PQyغeH9<7 }矨TD@Ƌq2:nκח(k'm;PGc0kL*!y)뺰+b7ڢS"4r,vmYU0 >+p]Fm ᪅QU[@A2:k.x#J8 'mz[84r1u{Nd^L=7 TBh,S +-6LK9kFƔLH.EVnSKC:i|={ /hUHR-@hLa9pN#FZwۛScZɖ+Lԟ}DW,Kjmѷ==v ש9Gvd8K* +]"{|Xhe}{{zלV4Z-IEY`iʮj܆Tˊ4uS|1k +ha +} R{@9' k W6"4ozs09XX3[БdBM.oLS-1$_x<(^fq,5>Nu|ǾTuҶa.#2 gUZ( +$yy̌AZ{"&q'M砚wH)'B񢏯5U'!4t MЛB {5%Dzr xHGQG+ξ"Z7&eSmmeAJzQ,~ /4xQG6/HH_?&2jS^m$o/h*kyӖ<^ZZ#P=RgԵ^M1c>]ĒGMBT[wI "ҹZk_&Y#MFi}$WgaAzendstream +endobj +2092 0 obj << +/Type /Page +/Contents 2093 0 R +/Resources 2091 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2090 0 R +>> endobj +2094 0 obj << +/D [2092 0 R /XYZ 85.039 786.531 null] +>> endobj +2095 0 obj << +/D [2092 0 R /XYZ 85.039 766.606 null] +>> endobj +10 0 obj << +/D [2092 0 R /XYZ 85.039 766.606 null] +>> endobj +2096 0 obj << +/D [2092 0 R /XYZ 85.039 676.914 null] +>> endobj +14 0 obj << +/D [2092 0 R /XYZ 85.039 563.765 null] +>> endobj +2100 0 obj << +/D [2092 0 R /XYZ 85.039 534.36 null] +>> endobj +18 0 obj << +/D [2092 0 R /XYZ 85.039 193.665 null] +>> endobj +2101 0 obj << +/D [2092 0 R /XYZ 85.039 164.26 null] +>> endobj +2091 0 obj << +/Font << /F20 1617 0 R /F65 2099 0 R /F15 1628 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2107 0 obj << +/Length 3436 +/Filter /FlateDecode +>> +stream +xZWHWqY^,iY)@`69[Ȓ#v_wKa.<ȡ?w4 mǏGtb;oNъvy*g$䭋;h7_f?}߷\lESv̛Z><\ήƮ̵n(f|/x_N>:W;|pF "Ǝhs''1Xpj^D߱`Ɲp6~wh>R +;8p۳7!̫`6YKOeI]<ڴYn6g^d +I)+⿠٤GXMya\DyҤf˜z+(Rx!/ +` @oxyfZӔd׳U⃉}vd,C{DK7 ^3k~C +V$?$_xq_Kl* bߝE[mDž] +A)EZ@. Og1"i#+Id;F(-LD2hDlE!d˝K%KP}Þ(V0uS+#Sm$| 1̳oяXxDJJQ26[(]wC03:dCUAX" +wT?@,w f!1AAPgxCh!% <- @C XF<7ͳd4]No.e:v_+KcJJ')1~pA[7@&`I) +>$Mb>. y2]!СS Ul@m{B{=a@&{߷^0՝Dmxz<ͧ 5GÇ_eHS׏I&T,J N/GʆasJקi*#Q|eC{)MQWkSL'/.TSW8 +~b\b.Aj80#1_u,wM:Āo6 ~=.q?I!vu_ŋ?s9;IiJP'Nʾ9~&}fhaB_Z]=' c/4=ޠItz'_3i&)e`zCfuFvRzG]d)=*X<){ =?~~bUmq+ΩmB-n~AGƏ]VJ{J]THkk~mJvH8*{[+8r6'-6j2G=kf{hG{َ6!ڬi4RDN"*>nv4k&4( B,Jv "oXLJ+`Ugm+#[2L6U}VRJEA402lY7}(J8pkLG:J?\qDub;,W* ٢xĩn˵ 쌢4#VQ{o?| HUO5#K!(uyuG:⦟&&ݧ\7H ,Wa65* 7̢ōSc҂øׅJ|É iD+|ɍ%QDD!^R thx|IAܫ0*_n-UlZ#@߷(:ؿngOHc-t*reendstream +endobj +2106 0 obj << +/Type /Page +/Contents 2107 0 R +/Resources 2105 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2090 0 R +>> endobj +2108 0 obj << +/D [2106 0 R /XYZ 85.039 786.531 null] +>> endobj +22 0 obj << +/D [2106 0 R /XYZ 85.039 159.815 null] +>> endobj +2109 0 obj << +/D [2106 0 R /XYZ 85.039 131.017 null] +>> endobj +2105 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2112 0 obj << +/Length 3359 +/Filter /FlateDecode +>> +stream +xrF`j*0x:'Y,Yk2!"A0( ARv7uJU<==݁ lG%(@,`3W o;a[&gס7p;qdN /Տ?GJ)˵([t5\еȷ&x|y pr#Cg~o`}8slă-MJ_ ~ 썔cDZoXuVu\3$ĵf<^ðˡX-CW zBd58VQ3i"UcG9V:E)S"Glţ>qY#m;!]ꃅE&$Yftv[!wa,0 "X PqX. 82MhBBcKVڊ+V!.S|qɋ|%nvI@$(nʚ3Ml4sӒ]ҌQj/,r]cθ/hݔb:-PfFh#:e9 fsF]_f9xKZ O-f@!-*>$L75BZ} +8ҞK5Y;`!3+}(f^Q_N" [̛Pt-){Ha G]됄B^l\F&_ DF^rrōe HE%\Ek:s(֢D]|vxBO} ixMU6$r$-Д.j sH\PHˏ+ +Cܧ7J"S2ؖRBJXӴ'C*s_E%pR $эTp.A!y+\deqZ#{RQ1کqdnl`OorCxMXYsbz7XE6ZZw-s7)y9me۞Ln|[E9١DdTJ<>~y;^ܪ5T]JR I(d{eptݣ!dpG ˽k8pJATMִ<1E)(Ntϯ 3-V51iJz%F9r %u8ᆭxCSa5dƫ8!x$öў-CJN ߡkB*z9ϞjSG EiKZuuM6 +r#egyUt-<2 PB[ީg:6$xŨܘ݈YSJ[#iυS5|u3.^Ee:{LLj@i_ø[jNM)cxp~ U<{Ķ69.a_!P0@{OR= +rŏFш1/xrK{qGϿqveX(\dyWZ&OrOݤF2=W7xS#RCLn)H}Z +1+ <ՒɘX(4 3x+v}Azz"XSL.Ew'vߖ56o'EJY6{Ϟ3'鎱 $YMt +; ]{'|MZg<& H)\JL&ܧg.߀ "ߺ_SS]K֝mK!CHisZ9VPWz.Hwؚ[%a2]UeFeW~Z 0!g6K"41BPyĬ=W+K9]FN_)@Hu栳OZ4ċcM?L ȌWMv0%R7ouM +uozoBDE[6J=:^BVJ1""Qה/0o7M˃1+R7mƎZMĤj>"ybK|I|ϣn>>0^\l[e:_q9;g" ?Vd==.U:1-fplʉ0Yw?3Y'嶗ԹYi?(#iEUl{wt>, 3L$fQs@A:ASbhDwƪl3gk < `~~t K +/:0/^ 565 !y# #\B?OL_bN5a?q w\@,p@-]J;iir=<''w +U!oϏYBlg[vl uiGRg`KP"M/6}aԏlzI?&)ro'f=ath&v~{v^unx̄(:*sendstream +endobj +2111 0 obj << +/Type /Page +/Contents 2112 0 R +/Resources 2110 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2090 0 R +/Annots [ 2116 0 R 2117 0 R ] +>> endobj +2116 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 74.246 402.992 85.935] +/Subtype/Link/A<> +>> endobj +2117 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 52.241 385.241 63.93] +/Subtype/Link/A<> +>> endobj +2113 0 obj << +/D [2111 0 R /XYZ 85.039 786.531 null] +>> endobj +26 0 obj << +/D [2111 0 R /XYZ 85.039 541.704 null] +>> endobj +2114 0 obj << +/D [2111 0 R /XYZ 85.039 512.906 null] +>> endobj +30 0 obj << +/D [2111 0 R /XYZ 85.039 116.921 null] +>> endobj +2115 0 obj << +/D [2111 0 R /XYZ 85.039 90.912 null] +>> endobj +2110 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2120 0 obj << +/Length 3225 +/Filter /FlateDecode +>> +stream +xZ[o8~ϯRQw MhnnRlMl#q(+X`5yxD|J2ԁ4lKN8OV'F>(pN} z;99ʱ'9$պt}z4B۱UNߓ,'2|* +0 _|g&S%"c5ZqI5CBQCjys!&LBۏbTэI%w5j#3~U !#fvb-?PԢU>͢Zh4k9,WՏ 9 +™fhUuCi.UYQa2T|AZ(Eنt@d%?VIxMCQ:8q-efX2x1DU᭮%P֦qkȃ0 NرR-.AîA߁X9noz5Q܊`熐~u o^sʺH5:2p8rÎQAk%V#*{lKN]g]Zĕ2Ȅ-S+_c#DxTxKH0gպyE,z)TR ]ق;y@Y9 {q8F F$ONx $]^y'Tri̪PWz_y~@ȅ՚D*k-8" 1RpkBR‘*ΚC9Wp'NUU,jrAM[lRi.ՄLS5[bq;oP?~d] |G6 x;Ek $ * WH౥E"B=rdzYdfyWҀ]qf6UZKkZ[HpUY@<\/BS^ +G(C/ܻ-H[I4Q}^Ŏv6I|2 #jI0 _hsڰd ]xC> l!H>*&Oq;t @2|™\xKqlԷ&uؘ^qlNb 1-7羠-8f97[f!wyZڤ|]t>i8W7(&q.sӇr%~wA^)߻< E. RY2qkܬUn(n [Ncf Z짖:hq|i62S=`Ukam`YUQ*ǦK ls[I- iN+v1!3sl-ꉪINճś6i< 8V/m `Zmou$ICx( +2(Xu!N*nA1U\rOIN2Fp܎Sr +rU`RѤD8>2 ?$L%OE4۬dU,g]O4[nH]78in,wU̹,[A:ͤςD'd\QYM*}hUEIM;(6K@P>_ժ{.@Ac/D1T;*Yg\z@f$|)2@5$7h1`N ֻ \`Ds^e;pً ㇁i֗)8Pe,>^Ǘ,t\;٣98\H4$ S $jt^,w$/:d<<<3EkZ%+nI:4$.VXbZ;Kٻq7QSC<_sHgy|5h0 +$12'ò*WMZ< @rsU G*u1dTIo5}; +ck;۷^?|[4˖VLAcJA.g/`` {F hZ%s19$.0`+b}d){w(a6hx> endobj +2122 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 752.53 357.484 764.219] +/Subtype/Link/A<> +>> endobj +2123 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 730.014 328.405 741.704] +/Subtype/Link/A<> +>> endobj +2124 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 707.499 370.677 719.188] +/Subtype/Link/A<> +>> endobj +2125 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 684.983 289.975 696.673] +/Subtype/Link/A<> +>> endobj +2126 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 661.861 309.786 674.763] +/Subtype/Link/A<> +>> endobj +2127 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 639.952 358.538 651.641] +/Subtype/Link/A<> +>> endobj +2128 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 617.436 379.598 629.126] +/Subtype/Link/A<> +>> endobj +2129 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 594.921 460.925 606.61] +/Subtype/Link/A<> +>> endobj +2130 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 572.405 350.768 584.095] +/Subtype/Link/A<> +>> endobj +2132 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [131.316 229.148 458.066 240.837] +/Subtype/Link/A<> +>> endobj +2121 0 obj << +/D [2119 0 R /XYZ 85.039 786.531 null] +>> endobj +34 0 obj << +/D [2119 0 R /XYZ 85.039 556.962 null] +>> endobj +2131 0 obj << +/D [2119 0 R /XYZ 85.039 527.558 null] +>> endobj +38 0 obj << +/D [2119 0 R /XYZ 85.039 213.705 null] +>> endobj +2133 0 obj << +/D [2119 0 R /XYZ 85.039 187.09 null] +>> endobj +2118 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F65 2099 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2136 0 obj << +/Length 2385 +/Filter /FlateDecode +>> +stream +xڥX۸½/'V$,IqI-{(|mV I}EYk/-XCj8of&I&IQM0Y7Jv0ř[:1,}D~ӊv>-?EQNәΔgq{uTycOM<槧"śl|[WP3 +}+(Dy(K1 #_maw| y~*3'ivSʏ* E~_yLg6by^.Xݩatq^ .4k Kt# |-vhSOtaEt+j{0p$%Իa-vW6p +Caq +- ]Ƣr-#}˥gg9hsvM@?ҡry ˃w;yWAHxb Бmxs.6)͏oCB +qnOJ>ZO9E?)7<:qJС!,!ekvAЂ0WWːH, ׸orYp6hπ [9\m+6ҖX6!%_:n6w]Zs: +{>BȓOSCm€-L9 +D^$Pɒ<6%+τh `4NEb|) U<a$K}[h,l"l|uC)A% xT6@ +I'.!1A{%#>)%[ނԣ(]全~p,1X ==S)ي-³,iקxOk!Cq 򱐚[B5#Z+(ڷ ƑlmYW'%g%xR"R` +<J"}WJ`-UDr +6+;ϫ/|W`ucP"E:?~1 8(Έ+9ӈV{Ӑ}˳}l b [@@m + Xu!ֻ/СV,b^v~Ss#Hd-:vvt'j֢SFRrv2 ' !Vves $ZYţ1pg0%s^P4s~`n.Y9.(L Q +%%A ʩ +K4 +[4v_2 0عAPp,8ee.uMa#0,' g<G&g 'm6} \~4 +eS*: Ԋ7켗*'>:+p+b}ryPagɭbR3k?Rߘ1\!˒A#BL~Pm$d 9Xts.\5>.vQ9fhh:dV_.Z\*n$5Ū@ol±Q$0OXLY b6Jzsze5PIABפ+}QEv@_ѻc bsG3W4`RzܑQQ+^䕗Gvq˪cԿ XJ!7̤D27U) zj# Pce%FӌA@y$gEK5xZ ,ʪbJU\{UA_+y$R ++ +@C%ӅE8|A> endobj +2140 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [313.377 617.253 415.127 628.943] +/Subtype/Link/A<> +>> endobj +2141 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [367.537 603.704 509.276 615.394] +/Subtype /Link +/A << /S /GoTo /D (compiling) >> +>> endobj +2144 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [182.558 186.729 260.642 198.418] +/Subtype /Link +/A << /S /GoTo /D (securing-samba) >> +>> endobj +2137 0 obj << +/D [2135 0 R /XYZ 85.039 786.531 null] +>> endobj +42 0 obj << +/D [2135 0 R /XYZ 85.039 766.606 null] +>> endobj +2138 0 obj << +/D [2135 0 R /XYZ 85.039 676.205 null] +>> endobj +46 0 obj << +/D [2135 0 R /XYZ 85.039 676.205 null] +>> endobj +2139 0 obj << +/D [2135 0 R /XYZ 85.039 644.68 null] +>> endobj +50 0 obj << +/D [2135 0 R /XYZ 85.039 588.261 null] +>> endobj +2142 0 obj << +/D [2135 0 R /XYZ 85.039 558.857 null] +>> endobj +54 0 obj << +/D [2135 0 R /XYZ 85.039 490.063 null] +>> endobj +2143 0 obj << +/D [2135 0 R /XYZ 85.039 468.867 null] +>> endobj +58 0 obj << +/D [2135 0 R /XYZ 85.039 172.46 null] +>> endobj +2145 0 obj << +/D [2135 0 R /XYZ 85.039 151.866 null] +>> endobj +2134 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2150 0 obj << +/Length 2895 +/Filter /FlateDecode +>> +stream +xk +!h +x\rN.plǧB($JbM +I|>Z>$E- 3Z$mNj'aؾ&3WJ0ǩWׯw;v|C(o_<ϳ\{: ԍo|y yB03e* pw3|}OW/=fցlv3Y?]9G{;JkO󫻫_Z*<'j31SnHŏ[90 E}Ǻ[Lc+8 gBylOױX{*D7RKD2vʀOhOJ%$5<]w*IMJ쒆WБ{@SQfJ}@ +ڍgɄRKRt?OJ#7)'ix%/]V%YB 7ohyIVI+yoX 9'ظyoTXS8 ,Fh)d/kp KS"TZ +/.CȦ7 I[.@e ՄG;=UdtI!dX"[ʮMIv(ss-4 {O8p;BK8LYz'ˢHW qfoވ$)-i*,%s_2 Y!ERڧjʉ\L4rf<==$5;ZL]-h-"zϷ}]X}UƁSVUΧ *Ӷ&6~x)*Za_ +3j;GsЎ)`SxN o#+&rY['zL=R FHsB`F.G?\V̗ahƢlRHs"o,c R?f|;tCc1Ƽ5g=VX*rO +LpɵȈBmcE$ ϳ621BNf\@&7 Np]ވ +-@+v3@uY|;.:FIyw5;Ӵٵ9M-˪ς>HCtӁG|'_`(4hp\*1SnX2wicZcL߷BnF? M,p݃6w :)~6,e :cr1 m(8 -9j^##KD#hisV +r<>yv +8%)}6K((n ֿͨFڂsTkK<iT +=N*) 'j~8=e IqO>Ci6X [hC6b% QpM 5Ku#P4h-QFb8 Q%?(F#t)BuEj%ahQr;˳6@i.E| 9:hD@~Ue1n^ :S!]t%%zaNh D~܆ +h$Ed Cu &k*%γ3|{8:e![db|#d]HBg$`_k$`q9(2!C#7Θ?FH^9[ANFS&P97(\kތuM޻tTL*I;~A"C >lUѶc7=)k(a ^daN2;o;kD/8HE+ۑOz nA lo[d0)'|d)'|QK Vpj4ЌgLb^nnp6m1$͏͡HwdݟQJחؚˣGT&~l(S6-B1pYl0+/YJŝ" +' :v3ža;&6Aq腇w^8铖GPUl5msݦj'Hۯ4O>5!f`n0e~qNNDmz#[G-' ec*?4n(FʨLtR`zZKlg*vm8E4|.(٨tT&9QcS8N4B_s݆oj@o0jN:ǣB QavkV/[\Pp +iVpOS}B^i06O ('^|i{ɡ9o\B`k'gVV /d[YڐA2q=ἒg/6ng%s4j+iүSv .L`oӸߘ;y/g2;a"]7|SPMJc5Eټ)!]U.Kl yG鑝B500).v7^=ێ;]q2-y`{C'neA aN'أi׌("Ƴk>k:L@*k><7s[vh84בFl]](Z>Zw*2elVw Cۍ!Յҙ%|6fT|L1;qr|3endstream +endobj +2149 0 obj << +/Type /Page +/Contents 2150 0 R +/Resources 2148 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2162 0 R +/Annots [ 2160 0 R 2161 0 R ] +>> endobj +2160 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [293.723 140.375 341.14 152.065] +/Subtype /Link +/A << /S /GoTo /D (diagnosis) >> +>> endobj +2161 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [225.07 126.826 427.223 138.516] +/Subtype /Link +/A << /S /GoTo /D (problems) >> +>> endobj +2151 0 obj << +/D [2149 0 R /XYZ 85.039 786.531 null] +>> endobj +62 0 obj << +/D [2149 0 R /XYZ 85.039 766.606 null] +>> endobj +2152 0 obj << +/D [2149 0 R /XYZ 85.039 748.602 null] +>> endobj +66 0 obj << +/D [2149 0 R /XYZ 85.039 610.22 null] +>> endobj +2153 0 obj << +/D [2149 0 R /XYZ 85.039 578.694 null] +>> endobj +70 0 obj << +/D [2149 0 R /XYZ 85.039 453.924 null] +>> endobj +2154 0 obj << +/D [2149 0 R /XYZ 85.039 425.126 null] +>> endobj +74 0 obj << +/D [2149 0 R /XYZ 85.039 313.904 null] +>> endobj +2155 0 obj << +/D [2149 0 R /XYZ 85.039 266.376 null] +>> endobj +78 0 obj << +/D [2149 0 R /XYZ 85.039 183.05 null] +>> endobj +2159 0 obj << +/D [2149 0 R /XYZ 85.039 154.252 null] +>> endobj +2148 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2167 0 obj << +/Length 238 +/Filter /FlateDecode +>> +stream +xmPN1+\- JTHSQ +~dk̎g !r d "w 0|{lh˒Ͳ52T没+ /k3Pv8f``6s\~]endstream +endobj +2166 0 obj << +/Type /Page +/Contents 2167 0 R +/Resources 2165 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2162 0 R +>> endobj +2168 0 obj << +/D [2166 0 R /XYZ 85.039 786.531 null] +>> endobj +82 0 obj << +/D [2166 0 R /XYZ 85.039 547.583 null] +>> endobj +2165 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2171 0 obj << +/Length 2514 +/Filter /FlateDecode +>> +stream +xYK6ϯ0$mY n ضl GC?^=bXH ~"lOQځ.;gqsC(]hNjl/+OىC7֟(jR&<ys ɺ+F?;A#,l1vS`a*S]U#D grV>(vZqްqQ1b9@Uw1wƃQY9soV~_͑< ҝ[ +*9MREYYh6)Udı=R+Gve:[V0 0 R$d~n^Qղ¦OhQ*l 6cޏmr@YzkLA2ĴܹPjP!֝,"s2IZ~MRWWsf+bǒe)#i!L19( hͱS*<%V*0U5ӆv$\?jQ8ZTu->[tő`fd +-#BѸ zsf* 5qoPpc$8Zi6͔JI*׵TD=ܤc<s0?n~dRzx$b7r{R@#ǎ' dKe.g%0"<..%k> endobj +2172 0 obj << +/D [2170 0 R /XYZ 85.039 786.531 null] +>> endobj +2173 0 obj << +/D [2170 0 R /XYZ 85.039 766.606 null] +>> endobj +86 0 obj << +/D [2170 0 R /XYZ 85.039 766.606 null] +>> endobj +2174 0 obj << +/D [2170 0 R /XYZ 85.039 672.773 null] +>> endobj +90 0 obj << +/D [2170 0 R /XYZ 85.039 454.238 null] +>> endobj +2175 0 obj << +/D [2170 0 R /XYZ 85.039 425.503 null] +>> endobj +94 0 obj << +/D [2170 0 R /XYZ 85.039 111.192 null] +>> endobj +2176 0 obj << +/D [2170 0 R /XYZ 85.039 82.457 null] +>> endobj +2169 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F56 1642 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2179 0 obj << +/Length 3161 +/Filter /FlateDecode +>> +stream +xڵr6_ᚗFǞl$IY\So_ )rt7K~eZ\IʿL#R^Ň܅\ d\ulr;q|˧WD9˟wa?>Akg{=~_xi9d])Dů{`Ermj%.-s왆lf(m$QFXކMMĽph-^b>&RbhXJD@6'+h w@l +:p}# \ Lw m`V Ќ!=К-lՀr 3@˨a;{0",{ YzFaW9W=&R.Qa2_Z=oTyXb4ysZQ<*R\ +uk\`ud͵{V0Z[uf,~0[[^dZ=B[CkԠ}]W5dܲ܏@f3nkClZLNchhmynDsHo䦓 edn 瘜JQv 76ɖb~:CskD+ֹ QC`*@@*9*)bsnH29Q\)90 0x;eLu8avȴU)rtCB&h%u,q@F.&k"hFz4p}i1XɑSA1:ؠtJwh{ ʉ\nߣ) 9hT΋_l Q18颷 +5bkq5uL + ͠N͞S\SҰ8!.>CV[O˭,9H5>H͸XleU[Cm*)H>I6H=QZp`-1Ds_Ǯghey5nR:dylWi1HihOd#+R*lDAV~+kUoQ;eI t iH9?T]jIU弗u՝4TU1{:S ++tҤ|Xx!±J~`NvR!*z{G/ @i $QrBҭu1/-L 5yz}uTd eaSHSS N7= ++w 9~9b߇I_GGZ=T☸' +@!/vwRSǁTO Otcߍc#a W YR w`_b) a'L 6lrU2-(܀1SY%yU3q++k[ˎ\=]b&$-1\OOܺ56%PѣS荬l" eѾYv~( RYs@`Jeg3 9S @;gn _G9)BZ`xm&+=h(zhxʬhA`Ӳ6p(*'@':j"r.k>&IRIR(L a_n`$G U?OhK`1壅L+`(lp\f,d0ۺ;gf87X]Y>> endobj +2180 0 obj << +/D [2178 0 R /XYZ 85.039 786.531 null] +>> endobj +98 0 obj << +/D [2178 0 R /XYZ 85.039 601.595 null] +>> endobj +2181 0 obj << +/D [2178 0 R /XYZ 85.039 574.98 null] +>> endobj +102 0 obj << +/D [2178 0 R /XYZ 85.039 516.946 null] +>> endobj +2182 0 obj << +/D [2178 0 R /XYZ 85.039 495.75 null] +>> endobj +2177 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2185 0 obj << +/Length 2830 +/Filter /FlateDecode +>> +stream +xڵ˒_1RU#7sqjSsq瀑8ߧ_ASh[SwyQq婟DnJ($8rg48[ 3?̢]E@=}x! O(bK{v{Sqy )<ߞF6=ԏ;Džߧ"o8^_j]lȗ+x~Adw^.}aG(=-Lr$ m\ oL?K E&ϽC)w]'6gb"|na 7W lm瞐2! D!3bnXNϊձx~$_0'h}] "hdUc}/ǼV{=ȆJW J)OɦKٲi&jҽ¥ y +oGU?+2,VNp>7̍cM+ GG$sC!*VAVdxhw9 y!(PlV0 c24.ƼVpuZ1{M4{HFA>|j\ ќowo٩^.G;MXoY^ +yگX=w0ԳaauMDpzbe](/fEGE! vr.E[D^hkHD#' R~/uD$߲O +Iq1C!t=n+yOr;1@LMNoL;iY^pj ahǓ cc1N/\+kE)29t@Cn"| vYlpߞxfq;ye0t-m\OTKAMQ8$ԨRp z7M9@R3wE:և W,܇Njb=}^k#TW&roZ^ n.#2I!;#.Vr\$=iY״ iX/6w݄hvݕ[ˊkC>3WM~MC=t歳5 §$Idn> +ݳ-2h.CgxLfEjw"{ +m˭} }hE‰ufQ!UrGqPM3f&d~^kV/u j+嵦i+wA-ZElG~{&q=vBX.hJMWVK\/ZԡmwYՓ{I RXKl0]eh:Fb]9 ՟[T3 澦&8[Nq zc5kETN*BL`4IĈu|smR;XF(:lQƭCEUQV5r"[ +0"&n qK>zґ4eKc:CS qL' 5r(Cqa]BA[#@` +@Zg'XWD™T5F} (Y(@By[Pso"1,=6Dnz>d@;~੻rFgM$1θaOH&!SI<Ή"'ߘKVstim0 J5=\ĜV#7bQܞ}^"`K{o!"G 276DU6'hb0rԖ۳RفZԼ#VhB+U~GwQzF_H)dCՍMNL<??ο+8{L Y~?k>d^ a+L||31H<@PmB rT.՝wsh'+j='2$5WofJPQAo\ݺR-80|buSvmѲ1Uf7xvYOvٝwUөC\Caq7Q +aq@Kg"&5" ]u%&M!+m pBf I|(WqFTt{Hgޔ-]Eendstream +endobj +2184 0 obj << +/Type /Page +/Contents 2185 0 R +/Resources 2183 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2162 0 R +>> endobj +2186 0 obj << +/D [2184 0 R /XYZ 85.039 786.531 null] +>> endobj +106 0 obj << +/D [2184 0 R /XYZ 85.039 766.606 null] +>> endobj +2187 0 obj << +/D [2184 0 R /XYZ 85.039 676.735 null] +>> endobj +110 0 obj << +/D [2184 0 R /XYZ 85.039 644.816 null] +>> endobj +2188 0 obj << +/D [2184 0 R /XYZ 85.039 615.412 null] +>> endobj +114 0 obj << +/D [2184 0 R /XYZ 85.039 508.283 null] +>> endobj +2189 0 obj << +/D [2184 0 R /XYZ 85.039 484.966 null] +>> endobj +2190 0 obj << +/D [2184 0 R /XYZ 85.039 397.416 null] +>> endobj +2191 0 obj << +/D [2184 0 R /XYZ 85.039 374.7 null] +>> endobj +118 0 obj << +/D [2184 0 R /XYZ 85.039 222.665 null] +>> endobj +2192 0 obj << +/D [2184 0 R /XYZ 85.039 202.075 null] +>> endobj +2183 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2196 0 obj << +/Length 3291 +/Filter /FlateDecode +>> +stream +xڥ]}'D*Mnm"ɃɒOo/R-][Cr87VS,(_YǑZm7j#Q2#Xi?HbwIR<~ssEmfFywCz,>x NJ)w I4|`2 (V/|㍎#?֑뛇X,g7V*42LR>%OvrJN6LsᄁMzv|?|Z7)Eʞo CKg9yjVw,!x8fPؽtr)]EFg׃(̽9;,zB:_<0hu`9sefqN +aL9;++иāPvK$~(?*I`:,6QD^GaE2~ْ~GbY5jTJħc`]~Tb= pLl'p̲\1!ugoI:gh͠Gpە"hG;cy b &CHIF"Ve=/B}!A$ ;b +lGn&BI#kfѽDf //vӸ*)r1 ׂ݅mm؈9y|4"ɡ#ȻB\Y^)>4Mħ1i04\4xUhg6LϚOFa]_6=ߊ@;s[9]1'`ﾕs'8 +8:rOw4&KE큘- u`_Jg?B l!$7ul==10F D C#F&dgm8AH 8?x#T[NU-cۢ1D=F',+?2֚zeGfFI@<(QD зncRQyTl9`u["x%P)HXBճw;AMIdq.vD|v( PH }lsFc~{JNAÐu$ +{ ,0ܵIH e' [*K脄:<\4WVjq\Ǣ)q!$SF$?|B =T&%(#u2`۞ɝElyN&mx +]ګ΢\['! 90S +$x,޹9 6AX{(Hz-2 *_iH4k +ܥbW1'b7 =[ @-t-\48ƛ~k$I e?<>> .л҇{…삤pgR˫Dk'lr0d!h&@B C_y#o:DW\[]dQH+k+_ +GΛ ҍipt[`Ր]^&Lxpa!t7G:{TgO$ 0q4&_t7$n„P:Y?};ZpL׷8TF5Lrq̖ Zn)؏UYbV:Wir yʼnЏ1>=D<괉qm Fa0R3%6)q}8sʏԇ϶6D BA TDFN>66 .zjBv% Yjn~5\P~n1(:"Uo[ q4j 6/c%xD\ic +\ +B;f62 2c'{ ׬ MTl8X*3Rg@'ex ;G/`hz%Th{l \ ?3bQa5f)|_JMIgx /5E /d~3 +Cos=J¬=?{Z4M .{Oj;‹>xGgGYw^TA"K%3/6h 0V&XGgȲC!8ȺR^MTDeS4mÙ^Fs̅*v̚Z1*@2@xϊBq +*\IB e2BfoLt {6!:f B{*z,De87&566lvV%P,d<نTXDi.K5X[f*$3-`ȋV0f%dNrw΄ȼ[|~b֝Dc|HOu1Û:] !BD?R:h P_)s&W_`endstream +endobj +2195 0 obj << +/Type /Page +/Contents 2196 0 R +/Resources 2194 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2162 0 R +>> endobj +2193 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (./xslt/figures/note.pdf) +/PTEX.PageNumber 1 +/PTEX.InfoDict 2209 0 R +/Matrix [1 0 0 1 0 0] +/BBox [0 0 27 27] +/Resources << +/ProcSet [ /PDF ] +/ExtGState << +/R4 2210 0 R +>>>> +/Length 2211 0 R +/Filter /FlateDecode +>> +stream +xeU9,Ge@@Q !%bd(dʤ( +$T)_acڿG=1Fl]tquݦ5<8Ǘ:\;&Ї h:X=&02oC eD3PMt1CrZb7}tmAd'W!KO(ԤtKb^ *BFmY`UՐ -nܞ `*Tޣjg=sAR? =}ځl +ϒig٥C6u&\ GTMKlFyu|?%iȥKNq{v*JE]8hp0R$(+ nN +qѫ^>> .13ׅӃ!3SAՔihŨ^(<m䦽lL7aƴd 6(WںK +г2"E9~ +n*1xƈp&XîÜ\D0}#X>#^V|2i9΁r)`Xh&hbHe"ʱ~ϓatZD!#Zk!e'j=_ts٬&N@i3t%kЁE\HYZx/U@iW H +rGX58ժOt$yBқ5/vpo`kAr 4N.4&FTG%V'R5Bԋ`qUv-U=Qv2_ qq~r5JhPkڏ>D oiCrT]MJֹ;Z [-Bxp|endstream +endobj +2209 0 obj +<< +/Producer (AFPL Ghostscript 6.50) +>> +endobj +2210 0 obj +<< +/Type /ExtGState +/Name /R4 +/TR /Identity +/OPM 1 +/SM 0.02 +/SA true +>> +endobj +2211 0 obj +1049 +endobj +2197 0 obj << +/D [2195 0 R /XYZ 85.039 786.531 null] +>> endobj +122 0 obj << +/D [2195 0 R /XYZ 85.039 686.185 null] +>> endobj +2198 0 obj << +/D [2195 0 R /XYZ 85.039 662.868 null] +>> endobj +126 0 obj << +/D [2195 0 R /XYZ 85.039 231.018 null] +>> endobj +2208 0 obj << +/D [2195 0 R /XYZ 85.039 213.279 null] +>> endobj +2194 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F71 2204 0 R /F18 2207 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2214 0 obj << +/Length 2999 +/Filter /FlateDecode +>> +stream +xڥnF_!+>ؙ&ؓ=]$-QaTxߺlJ°٬iH# En[+_(r8Bw?["y~[0t\%I/}ʹg?,й{~OAR;'uQ{]bOZy1EDKoHZ3i>u&_6_ +i|b0뉉}4i?y o< 4>{$7%!aF]-}aBvaF" dǶ1U˫|= R$!8x.ʒGٖkàCM +pbꡩ-a# 8/abW3`Q M]6U % +;7:ԃӝQKG3ei(~9C, gI[Z1d BK]T3^/y]<l?s^g[Rdٱ`YyVNDqʦ\FV> +4nh=RtE575I>PWP'HޱD^ q?dl-@T9TʞˆRt<"Vr>QG&oQ<1PNb4F$@ m% $"){x;,xًYDjJ5(t6h+\ ”a_8w]wƴQ>j(`ݜS֊Ud6fP\ +{ Ƅ10ޛ`?*NΝ@XڏFRQnklA`sx}[lp]!1 HhLZA::熱aP=LdvQm/n$9dGH.&լ{Ӗt0l\A +D7#֮)&l2 kt0f@tah25ZM 8w?~, ^r*hI(%ɏ\7oNgtaqlI}p̲A}#qmfk=zBXۥ8 Lnyє ʒ yςAqi;LÜ9V& uhWG§̻n[;+xuM@.K0/I$n 6˛We:H)՝s,eȔx>LYKuDleX*MAuK3\xͷn7PO/$Ә;Ԉl)?LʌV2,f٦D ͫ4 !p>1o).|R|=[Qn . ]̀(}RȈe~zႼœs=>>)\5:ͭH_Q+;-"\M3ΫSwNE/|Yh^+qq]ic"N}%trRw2\47DCL.*[2=-z{ Z;vڎB VM:x=Ԁ +]WGoinr̅gbeR8[23T:m~{M34ʴm[<eE".xZKscDXad*R0!gq2 2uB!7| / Pg*s>R7̷Pphi DŽߙ>ޙwri5(D8ٺ5ύ[xMj +gXxcn0_E{> endobj +2215 0 obj << +/D [2213 0 R /XYZ 85.039 786.531 null] +>> endobj +130 0 obj << +/D [2213 0 R /XYZ 85.039 173.977 null] +>> endobj +2216 0 obj << +/D [2213 0 R /XYZ 85.039 155.503 null] +>> endobj +2212 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2220 0 obj << +/Length 2987 +/Filter /FlateDecode +>> +stream +xZmoF_!8**k~PM۽Z9-QTIʎ}mɕE98p]˳#$ ]O8PrwM60Ӆ +o^?FDyn꥓ŚHߝ~xtvw:Ĺ*g~Gg~.vח뷼IaR.~xDniᯋ&+ i2y4.Pa廼gυ 9,P|3IGVȑۼɧ3_+'k@|wS?qc7pE=x=f`菖Һs4lϏ4G4(Vh9,!M"!08sGFxI[t20,GK}DG"&-4#,ϛ.+*Ίt:6!\5d[I-h`cݾkM*Gؖԑ|*{##bki2#P?"/m0 +[{⩺cKt7r\y8ٴ#, l,7ӉX*8ǀ~m$= aN)ya\ +1gze#GAb}mGsqs0]FA +*x:^0exgi0thGr2v8k +*T&bū/:7+T82hsq@vyVI39RNEm?2X%<S5i,a|iS3 ad_'Nx'ܙ19і0w.x8,RdE 2#ϦW  |8Rl F I<% + /6[͸ɝsy.Ҙ5]I+7zUbwM;G(cT< +(nje ZT"OIsDMG/D K$\2 +3,\D]k1dB.KK 6?fGEm Mݽ Ƴ Aa tJcoFcU!BMj-MYIժJc&9E?1ݷ= ig*#St}orF )RFG&83kGa'y@!yq$`[#73(eC <WdPnBϤT1Y[}=~zAEC$Л}mWv(ZJSAex)K7lDcδTRx *>bgTbWSb3t'kʱghqL/Z +s^x4[_*v!)*FiREmIUy(lgh[?ʟ65F'?qqwXZ˛SBw#7>fj6KUł6/L] +vv 3(D$P)3?M [ܘ<(~eιD5:oUC=K_Ŝxٶ}}+HQZnV*rv~y˝K>r^"RadU׽":h`wG' 4nJendstream +endobj +2219 0 obj << +/Type /Page +/Contents 2220 0 R +/Resources 2218 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2217 0 R +/Annots [ 2224 0 R ] +>> endobj +2224 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [191.71 117.821 283.127 129.511] +/Subtype /Link +/A << /S /GoTo /D (winbind) >> +>> endobj +2221 0 obj << +/D [2219 0 R /XYZ 85.039 786.531 null] +>> endobj +134 0 obj << +/D [2219 0 R /XYZ 85.039 604.89 null] +>> endobj +2222 0 obj << +/D [2219 0 R /XYZ 85.039 581.572 null] +>> endobj +138 0 obj << +/D [2219 0 R /XYZ 85.039 525.863 null] +>> endobj +2223 0 obj << +/D [2219 0 R /XYZ 85.039 505.269 null] +>> endobj +142 0 obj << +/D [2219 0 R /XYZ 85.039 103.552 null] +>> endobj +2225 0 obj << +/D [2219 0 R /XYZ 85.039 82.356 null] +>> endobj +2218 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F65 2099 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2229 0 obj << +/Length 1834 +/Filter /FlateDecode +>> +stream +xXIo8W(cF$e:hd:@ۃ"+-$;ͿsHaɷ|oO:q <8Q@K'&?&PC̮B%΂soj*ݻt:a<Τ;yjmySjHU:0|~˘.j˦iOS¦2o~|'81t-4 D6/kC>Ľis*AaYƏ0q%](y &zy?NbIT EMf\Nn'S <1ɃcgO */D`AH.HQ|s$:DO|6ٻJ:W p옂v M4GY_T# +h1:fϦ>kg"2}@ +hxin-i H mIJ%Ecb]r=bF +[Wzxsf{P#Q.q/.S|ž[7;2TÃ?Ji,rg~?^&3m?&23SᏊ|W5e[\fE +[_ܱh->b-ڜs}u훃bQW?.XkGRV%o5rvV8_,B^)R=V޶f> endobj +2230 0 obj << +/D [2228 0 R /XYZ 85.039 786.531 null] +>> endobj +146 0 obj << +/D [2228 0 R /XYZ 85.039 766.606 null] +>> endobj +2231 0 obj << +/D [2228 0 R /XYZ 85.039 651.298 null] +>> endobj +150 0 obj << +/D [2228 0 R /XYZ 85.039 651.298 null] +>> endobj +2232 0 obj << +/D [2228 0 R /XYZ 85.039 619.773 null] +>> endobj +154 0 obj << +/D [2228 0 R /XYZ 85.039 549.805 null] +>> endobj +2233 0 obj << +/D [2228 0 R /XYZ 85.039 520.401 null] +>> endobj +2227 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2236 0 obj << +/Length 1982 +/Filter /FlateDecode +>> +stream +xڭio~-E8mC+rm! +8eQ 3+w?w<m_g}w#g;?\pƁD!nZ^~ycױb'uκ\ޮL}߷B{2ۉk-_-X˷׫u7wȯ&SZy?-`woqoW+/nV뻉7n7=٧D> +i3N@7##.|;.Ԁ>f;|tr[f FEUt+L-PMUE jX1zr%cٌTonDnW6un&SK:Xm=zSM d &عuoJJ*43#3 # m +*qȠ&F±[]jF CLm@,vD`&5#AD=1hVM0LI{ 7+y0Ep*I:uj$I;Z.Ѿ\җfɼэN/=R'dJ +iHI*AJPr̀QrGdE§59im +M?yqXO\BbIJ^JOB>S&wuF &#(;~oH8"N1Ig7UDܥ1'wŠl~8*ጯgO|Esv 4( +b7`VnrX7JӻjDI4T̉TI/ jc}XGE @-v#PS֡@\9CqO^?@C6%ʼn'&=١}5]M(/[bg5[}T4ރB\M䚞\-atmY[ߖmet?."CgST&54{:\:EbX-t Ij$,k8VftTh;/fH؆"W51΅nu.D(bĶ >qZL)/W +R2ݯIJ)V7 0ũ$}̬0@I#K(U|(Gɛn;֎`ZKm(\yO&[t_n.c3Rmw̵(JXu\`/a.S-PEbE3UF1teX4Yaw @xNZϵC~05 NdeU[ MXvj4? jo,rՐ5HCQJhYVQaωAPe>XE׍8LEF.uOO_p`i>jI]|K~46GϩaL,)CpoPJr O~߾K-^,#]NF;,$O裻/u) ,"&} JȟEM!꣖S}d_ +iB/lx"w٨iiZp>dgl 8G aIMtyos{GȟOZޭ]HVJUM sRu ,.&H5CuTh ;UUu&KBV}숃Rб});޸(Ba +~dcQYmM C^Th8Gn <2 Mi+O6ӟuv$z [{]:9Cu/:SSV:EEzNN7k3; Y#}t]ݚؔ!O?5isݦU-Zxj;o8c#)$f:gll#ԦE+} +CqBO{TVB g +JSitTPqTendstream +endobj +2235 0 obj << +/Type /Page +/Contents 2236 0 R +/Resources 2234 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2217 0 R +>> endobj +2237 0 obj << +/D [2235 0 R /XYZ 85.039 786.531 null] +>> endobj +2238 0 obj << +/D [2235 0 R /XYZ 85.039 664.759 null] +>> endobj +2239 0 obj << +/D [2235 0 R /XYZ 85.039 642.243 null] +>> endobj +2240 0 obj << +/D [2235 0 R /XYZ 85.039 619.728 null] +>> endobj +158 0 obj << +/D [2235 0 R /XYZ 85.039 532.653 null] +>> endobj +2241 0 obj << +/D [2235 0 R /XYZ 85.039 503.249 null] +>> endobj +2234 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2244 0 obj << +/Length 1910 +/Filter /FlateDecode +>> +stream +xXo6_E>PmvċE$Jl+)z})@$gf ̊špfe̵v@a4kHz]}zsMXGՏw7"bnۗK\~={RW7j_^y?+;X~Uy^vE 0 yzw_g?Vi:<Kwy5E|KIM@]pfqX`BjXꛪϱ-?^Ԛ)/euB>j&ا݋cN}7VcvFwKHJDN}~Z>#.t_H}s4x&Pd]dt\򠯸RTՀ`;>ϐEv_x}s⅚nE}lTl̐EEkw9Yo&`jh8:\iDIQUPi:͡#Zϫc+*U֛*7Wf#djMxc1eYvBUٞti^A4I S6A]ؖդ" OS~jkFLg `@ˉX& |q))q!n0?Ƀ p2ob3ω}Hʅ}Ȱ8qB*'I g̋O.T&JP[s=/\]5xHȳŁ(]+!_ Ҍx#[t\{K]{ɠtm+JiIM﬈3+>8ҕ_vR'ѵZޮSR3DLixߪ~sK{ #;ES%Vj0gNLn%zhp5KU 슋*3) jp:/p^|p|m">~SJ#;g.q1;c澔dcu˦sSgHN䲿"YYS64t!`2PcH^=B&5^ 1(#[Q!; )jqrhJ7j#4սI]tlcw=$ZMͅsdyk Y+0 lPHE)s0ʖ 8`$j! 5ʋ.-VMįMȖjf#fEEv::q1=?(r+{] S.M@<׃A3=}W%aGn˭&t< 98#1:\&cՏ ǹIIʝx)(֜[納/oϠ@Ɓc7z e;ޚ*Bn0[0n1YU .LH +rfLJ80M]R5TyWs%H!07O*58jmJ(K߱o.0όMX\l꘏21V7(!"rM$7G݁B]ZąTuS)P]Jn<㪁/vhk&u[H(5)Ƥ5<O\R=;JJPVa,~L{}>M>VkI<8yh +fsߟ`X(qh )C,Jʺ r&SH*rҌeCk_zا\FsCendstream +endobj +2243 0 obj << +/Type /Page +/Contents 2244 0 R +/Resources 2242 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2217 0 R +/Annots [ 2246 0 R ] +>> endobj +2246 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [177.134 169.832 306.43 181.522] +/Subtype /Link +/A << /S /GoTo /D (passdb) >> +>> endobj +2245 0 obj << +/D [2243 0 R /XYZ 85.039 786.531 null] +>> endobj +2242 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2250 0 obj << +/Length 3101 +/Filter /FlateDecode +>> +stream +xZ[s~IbeFWތ!N'$av% +"i9>}4Z@r*v.=3=_wS$t=.$rC퉷_NPxN 幩.VD>8/߮_.N.8qޝ*s w;ܿ\Lӥr.[z4?yٛ//}ruu | +}A'>z su,*Mۓ nh'NsWͨhQ,U~8GǮk݅iMW @a:unbwFln usu*>4-w7k]ƍ_bGd:E.ԑTk:3U[SBX3&x7S?qnL8482lWehx;ɵV"Tҩ0GM*vģ@+|63m>:qSB+M#%1([ w^m^P 7xtSD͊1K^"w +9_ FvmTqBUUHioc?5?Cl#S4y>R.bB ٛUwkh֬`e=8W;vw:MSsສ͡I-UHBm*bnlbaxCOS简 V9)_T,uUy]!25گy3\! 1X7B+HY_2PIUF( OκjRNMjJqN 9fskel@7S| `Zwsl)A;o]HNUqěBDj>%A{' ]MѴ5qgS1@Đ@,5!6%qYq/h2RTraҌ.!6syZq#LAvפ-D? }<& +.3X?Y1!i w`7GVL`2DH4cZ;gh-fd|Z滬aj}~b) +22'3)7c&W#([;P3$ǛThv? >;GyU\/ѫ= ؗ)FQ J"T|uO L֒`;75o/!%d6#-,<[hQ!{e0|s,wE׭Q /5<e-g + kVm,?BβϱZz1V@!Q]RO S +]8g:<@>"9PsD2PYsW%%tm>!:%"3n1=_ +thu 6 |3-`e]Bӆ(i24s+w8)Ϛrg{XGYUqer/-](bg|4=|̘Z bĤeAvad3!?e +͙`00L 5uı<=Tۃt"N(aVV{ +\zrE5LXw(hR*aѮۛ{IP#ȯKBe"5eƌ)!oLj.OMv`V]MY.z<% }!\Ǩ_l}1x` L?]ϏH*?kPj(5dMgݖ!Sʸ#_C]_'HΛE!? K8 nȥY< k\%l*,ˁ)1:p5z,g&X_!\L 29[&UlF&7pHVR%x}^e|)sIv+ ɉkTzR:6 o ¶ iXǂUbfLtKM[!¤ H=&@aY_ /~tEWjۄ7I:SҼ(44}aSk@@q'9)lpJɻfq }vXpyvH쿃DKhxӯ0lE-/GA ? '!|e}$z72z*{6<}Ro{o&_Tl{/%(~>qKZOϹ\hE7L\K N5mW7eE!l>H#A&~(| 7\( IT YXdo6efiUU[iU8ı9Ǒ>q@uV[‰z[xeضWcAo! +` CrW'6QM]_W!+KLB ;!w%W=]$yҨO'( 3n;FQ0C'ۋI4ػzX'1Rbf.N#4ߧ$$hnqph2`BchGfn@MQ6bW>aQ8b?jBC{_af j=Iendstream +endobj +2249 0 obj << +/Type /Page +/Contents 2250 0 R +/Resources 2248 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2217 0 R +/Annots [ 2253 0 R ] +>> endobj +2253 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [258.165 167.281 329.551 178.97] +/Subtype /Link +/A << /S /GoTo /D (passdb) >> +>> endobj +2251 0 obj << +/D [2249 0 R /XYZ 85.039 786.531 null] +>> endobj +162 0 obj << +/D [2249 0 R /XYZ 85.039 766.606 null] +>> endobj +2252 0 obj << +/D [2249 0 R /XYZ 85.039 726.911 null] +>> endobj +2248 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2256 0 obj << +/Length 3364 +/Filter /FlateDecode +>> +stream +xZYoV~<B!ͻq񛓴t(m1%b-*I9˽\$:uTw9w;wZBO*I%fQ8g:#SNLA"ZOW}J)s?r.pT{g+s_i&۹/s/ F>}a(?N"S6:@'V_ Jv]c+S%w 2'+3RD`*3XT "N0,o<2  ?|~{ +Ӡ- .󗌓kԱnrU.#iWv \ t?6A&xprЇ 2L@y0~P95 y%wVXSY9*^-pBmyԫšR5wM˻g=ԀjAR#Nx`^ kxZGb9ݗ#e`D4DH3 +Ӵ`b9( 7)3)A( i|2 +Gs2rЊsv 45mW9$:2v쭑[MK'4k:́me{ DTcίx`5t?4,YhhWCB u\?N J%{: FN\НQyWhaF +oWq䊽ߟ2To+EA#TAE ޾"aֈ7hJAX_h„Vetgf;{ma !ђ` GC&F'y8yR"ePuBEz<:gCSCEL jkj3lTuڧyOH9j .&@K6i;V浽%aEسwvFi8Obonkr +Ġ*:Gץ3R]S,Yk'EW%({U+&k]yY pʆQY%hp_`%6Y,Ư˧GE.z$q|uȇ 1V= b!D.]ف$_% 6/$&PmzX9\* OZuvqm,Ew3*͢ˑ`aKxIaɰGʪEwx&M qЂ i$I͊@4t*j~d#):GP.>ȇZ EAt@|_&"y*R%HMtI8٪A2T ,02&DP#@SQv=` R̸X1CjJ`mb(qb5m:Dol`? z'=F:#Ɖ4?{UO +8֤ʟ*hpp2lq:}^l!4M Rd!zJ%PhtInvٚ!au q_lJBqxqQiIa(޻J|5xIND8NG7 \rj$՗zcވA^UF¦aa}8x",BwƤji1olI%IG1l6qȓϻHr hC7 ];[18.Wj9uULqɮA4E ^VrZJa vdߟ<;ih0 ge»+<=?g\OzpWaXo(o6"@*1gRrNeɿFͳDC+K~"ݓ,Okjl63>8_B/|UǮ +Cq5)mCykWeUYԮ)Iv/:/*/†b]PuH69bc1*zd/Sҷ";?Fx2O W8vkuW!t(5-axJwU !] Ժ:| B<J(TH#*.B +mD)?)P`28"˗XqseEkmLG8ְ!& V k\ Qk^%-e]u*K/>iF'#zvYbY[Y^txn=,2jà ϭ1obTwLR ¯%lC\>~sԄ }GŶvM]|'D_{fvK)ڣ2n`h3\x)2ʸCDG4d%":?$ k c\tQ_6%m,~orlgO3 #v8pK&J0bנr9q +񕥯UR?' +[\:5 yP6Gz@%,&H).Ú'XE2-mSJ\4Qn\K[5V ˾N>΅t.o>1^W;7UAŌ'My /"_@|dWVt G>J ^2 4鋛d`<2h"WG(OԷm v#BKq1faW e* D Yu'/L +b=|45 =Tn@4# Ûendstream +endobj +2255 0 obj << +/Type /Page +/Contents 2256 0 R +/Resources 2254 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +/Annots [ 2259 0 R ] +>> endobj +2259 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [369.053 65.818 448.095 78.72] +/Subtype/Link/A<> +>> endobj +2257 0 obj << +/D [2255 0 R /XYZ 85.039 786.531 null] +>> endobj +166 0 obj << +/D [2255 0 R /XYZ 85.039 410.406 null] +>> endobj +2258 0 obj << +/D [2255 0 R /XYZ 85.039 391.534 null] +>> endobj +2254 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2264 0 obj << +/Length 3104 +/Filter /FlateDecode +>> +stream +xowZaҼni6Ng4?-qH:h؆a0{}wGj80P̟,a3%x~ҫHO~:lѹw7S7'n'T9^]q.n5gʹ?0ssfίqU{ajKiu V&qmMx - :µ2@\({ޱvJr00 n5Vܶ|r%eV3>0 jWNuH$0- YkQ0+Qb _S LeLCUumOjSqiP * 4"SPhT`* +( 6Qx:]1ЁH` \#hǑvȹ;Et':G'eW[WBҏSbR4ysڵA^Φ:u,/e[{n;|I6(;mzB)w*AjND*{.|hqƖOǡbn4t&Bq[?)޹q,[9kQF"[ʱ 'A=2qm6 5.D>e|JUf{.,ěgCNy >^9D)=#lp&pnSsp3C1"P)O{1j⼜. Gi͒;+ c&\at{P7S?۵=Ԝ,0{8l/凐춤EoW)i_X7_% \t?!m {^RPոQ&bRnƟd_k05D޼F,mQ%?ż8Q_̫-RA*J~79xW1o=aIKnD#px=4wyw7(0m# +R0x6u|(|-Vt]VL|XuX\r(%%M<5' ٖ|#IlΤ笃;[\@a֚ m6im)bm#zK؅Sp Y]pKъnWGGp4Ar\Bbx#C:X"/5=/Ό$T&AO}4ZO;V}nP (_sǔA 2^}BÍ7IA~asw֝13 +#IFlcOo +uFʒ&x(֖i܂Wl`~$J$coæҴ}Xe b$9y6 +Όsgt4`5ܩ+2 יXS[>,/|@u R(|i/z-y3A}Aml zY!^^j9IG>6e:.pFa}0~8x۪Q]'v8wsNralgZviI 0 }Ng0e9ەMM4Ģ$&ʀq\y;? #.+ҩyfBRHG[[KÂ<6U)O9S/ R}@3~138;*MF*`PٔtDhuLk/R*miG]2<sJ;^R4X>6SF-L5 =*%ksLMgG91zkO~K- "!~~ :z񩼇 +Ys;T~ܚ%g[cԁޅhU2Q1O>-~]=gpoendstream +endobj +2263 0 obj << +/Type /Page +/Contents 2264 0 R +/Resources 2262 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +/Annots [ 2267 0 R ] +>> endobj +2261 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (./xslt/figures/warning.pdf) +/PTEX.PageNumber 1 +/Matrix [1 0 0 1 0 0] +/BBox [0 0 31 31] +/Resources << +/ProcSet [ /PDF ] +>> +/Length 557 +/Filter [/FlateDecode] +>> +stream +xmIn1 EOPwu$Ig0ľ6V5 oʯsO #h8:5?Ơ[IL~F PYdzZ8򑖌f(E#@xoL ۹[ + +6\>RgbWj[ +WϢ{6;F])/ԬMu;pk;̩dh> +>> endobj +2265 0 obj << +/D [2263 0 R /XYZ 85.039 786.531 null] +>> endobj +170 0 obj << +/D [2263 0 R /XYZ 85.039 513.624 null] +>> endobj +2266 0 obj << +/D [2263 0 R /XYZ 85.039 494.956 null] +>> endobj +174 0 obj << +/D [2263 0 R /XYZ 85.039 296.432 null] +>> endobj +2268 0 obj << +/D [2263 0 R /XYZ 85.039 273.114 null] +>> endobj +2262 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F41 2104 0 R /F65 2099 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2271 0 obj << +/Length 3087 +/Filter /FlateDecode +>> +stream +xڭkoF`1\yiOvmEÚ$6TT(] ݝJL8/DqhՅ3YBA8v/.}؉LKYdX7~X|x<ϳ{:z +k'>?O>΄ug`qq{hRc.+IXեKE vOȢfv41}t[ &]رͬ[3G{ 'u<˙q@M)֢[#1[m8BԚ Qa53\)34JK MV3DFVg#77ؑ!V/(H]ތHɘ{ Rc'sK4g["UIzJë5 qnj2=Lm,%F|E5D-+6t.eF::Sؚ6I4! Rѝv8{y2fcTi6.m3Ըr7#4Wx|g,la.ԉm7njm/#j/F#(Jt{`Zx)N=1 Lz +(ǁA\jh#iY& U(-fJ¶aCھhX nخHf5xJsEٺX؁3|EŽ`VKɫΘTl >`v,9ͅ9`nb;zh2PÐ h@=xEgd@^ٳ?>Y #%ͦbhQ?W0J fz B#:v؉'ՠձws`$ 3ءѸ,=ZTox[wy{mF:l/hLD7;l#H|/3239::sgp>\wطf?:5~MoRT8&~;aS o!/Ò?[Gg +$VD 6\=xp̷q.b8 +"PPO='BDܵYjZmMH&h%(7=XYf\~C\0*\*:b6_8֝4`Dpӎ]ٟ[7G |n+wW] | I$k2Dk7nbcybPěP1.0HLg#J7A= 81D"uBW7PmŒ}ܪВAa3mx%KZc+;kh!ZZan\{2V]]fSdKᫎhײm1-MᄁaqJ-LܰP*4uYRv3ΊKCVWC&*RۆMY9Õ|UcܩGQp!?N(Hg8n1ۡmm爃-\7 S ^z<@@wendstream +endobj +2270 0 obj << +/Type /Page +/Contents 2271 0 R +/Resources 2269 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +/Annots [ 2273 0 R ] +>> endobj +2273 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [428.788 626.203 512.306 637.893] +/Subtype /Link +/A << /S /GoTo /D (domain-member) >> +>> endobj +2272 0 obj << +/D [2270 0 R /XYZ 85.039 786.531 null] +>> endobj +178 0 obj << +/D [2270 0 R /XYZ 85.039 597.211 null] +>> endobj +2274 0 obj << +/D [2270 0 R /XYZ 85.039 570.597 null] +>> endobj +182 0 obj << +/D [2270 0 R /XYZ 85.039 570.597 null] +>> endobj +2275 0 obj << +/D [2270 0 R /XYZ 85.039 548.939 null] +>> endobj +186 0 obj << +/D [2270 0 R /XYZ 85.039 450.922 null] +>> endobj +2276 0 obj << +/D [2270 0 R /XYZ 85.039 401.83 null] +>> endobj +190 0 obj << +/D [2270 0 R /XYZ 85.039 278.375 null] +>> endobj +2277 0 obj << +/D [2270 0 R /XYZ 85.039 256.514 null] +>> endobj +2269 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F20 1617 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2281 0 obj << +/Length 3613 +/Filter /FlateDecode +>> +stream +xڥZo4IK*EDI%R!ffN€;;;;;џ=]/LǓčCzW4+_1CoWMksS/.ey>n0tbwt3O=4r G?N#AI ~t;23A>?}MB{Q>>N?uՇiȍ~˯Õ@mz{šG7WOWXt-ΰ`9`0wqjИO%ND|cϙs:o8l.h~[]@@ڗYVsj] Z3}+I>hY)jq陊-qA[$|u⡮J􉞲QjDa+} 379/hO;i`SЌ:ꗂ P&f_9rsR6`$AFA8Z9o/Xn8OX7E`BX=u-!1V@[>Lչm%_a?ku! e6'f= +]evsD" " +#j2Xd|4+61B{Qm3+K'ԔP} ׼4-C 7nCU/L)HޭX;7復q|LJh>tJ)Cm6/xbdb($0DpΣs&^g"uWm&IOJce-V 8uqVK6h`KBKSI>w9aJ!Kb5]  G0/۞`O wt2 u> sBkB1r?X|Qa|2q%+ӭT0ri4Xl*N -fwp@fX@eslxR&*1t,y]/գ'JEi:7#hqWm*>Trug8k"u1,Ku| bE}x3evq&sqE?hRksm#jDGoXYfrskKj+N,1ijiy8F*`^F%ty>(.}"_O$Q΃nMa|=|DF-1 ~Ħ8DA;=H+ͺ7eq1#'?V4C#yɒʹy>~eqzQ,quy+&ģ|lrgs4ޛසaendstream -endobj -1444 0 obj<>/XObject<<>>>>>>endobj -1445 0 obj<>stream -xVN#9}+jyHIJ.H;;$JHv{pYM)w!a4$v9Uſ']K'Cg1?{xYIY8莺ۃ}=n )OCqVԬMΚ4&Jpke&)yCK-ԆKDq.I=8o;:7OIJLYM+kIr >qMu|uiL( iҢTxrTJ 81K]89M\+iQ5iHrυ䋗FsL)1—BYRZd@GjD3kJPxD'5iÎ9iHGYLZN#c\RԳCHg]( XǑv.`Vo :IVJɈef2k煣ϯh6+:gn~=O qZA"RW錪<@M=Nf 9WT/9i@UijsxM^zwAG(72e:?g @QV0 _y{yxL"saC+u`xiH9D ĵs 0tY#%kÇ W.K(@( =c?ӚB'J{I;7λW5mYP,zr!/tуz?3IҘ;6gh_Q@[7 -B3;\HPyV MoEI=O]AİOi%,k /tɥZaem >f%{nh_whm޶~V!rUf hc}SzhHU 1G}A\GD0k}X!6(=oK A?m)[Fzh}K!m5l/x!q ER[,.y80NVY0Jx2~4ޯὤTn@Np-;ѤnkօO,X6 jg(F/ɸOg+^, >3I 9A1k֨  X0ڝuנendstream -endobj -1446 0 obj<>/XObject<>>>>>endobj -1447 0 obj<>stream -xWn8}W pjE/liBKŵD*$WgHɱU/(93gΌ.&4ƿ -4[PZ]1ͧdA%~OJ/hL8$7xGpdA }}G1s^,oh$XKK;U:7^Mb#|'ؘ,<$Y{k&+&tqhtfRI93K4yS-92ψWLATAД2'oZJm[{& NV$&5U-,劼 -rX!'5D}ٜ.9{=!X{ǥ3W(K<"t,8՚ػt?ޜ;B$K R1YZ'? WeIFm\X92e0>$3F9FJY*mK -ORd6 -E|i#Q"{tRҙX S_Oi/C<6O9 -賁B<ܹCTr_HVL\d (SyS3I5Bi#Ai~dM ܔ\h%Z*[SB֥Ic, 宑. -AC`ا}}ִ[%Ӫ҉4O+SHwW }4U**nhq3p#k} hq ъ{j#=;3iS`1{1 Jt}Ӱf{ϯo{VTb=V OfU^{Z2mU0QnPsAhzαn{Z=50\+r - -u/Qa( bcJYGщ] Ig[+8KֵO4qP:F47"9᮷8O}k8HXdz}Ea{Zy c 3&2tFϢdD7SnסB?VItwW(/Gc ȤU,XL yi0rkpK{ -0*R»8Yж,K"Mڳ'`cE2r_hH>pv1m /DCr>{LYHk㜂D$\A A;DC*3cgs -(#e&U{*1S4ۂقx0NxdfVUVYlXCͱ,?*uͰa -*\4T$#ѡqΆ0OT0ˮoċc@U5~9S6a3G wE fWG;سJg~Y?^jx,Jd=TŬh̐ҝJq&(F5S"8YMHYid2On}0FB=rG8ajjД7hT0C7Ԕ-X(aEV~Vh^=畖u(ҟX=Zݯuu5&$#;|U7f;UpT - @am䯕>E2^贃3+ב[|o«,Yt5_|Of t' aqi:X_|Kendstream -endobj -1448 0 obj<>/XObject<>>>>>endobj -1449 0 obj<>stream -xW]S8}WܷvH#QYADŶ\I{awZے9犟!/iD' jCh|r',/c:`(1gS6_ +k蔥6yo0h sY[p f1`+Y^}:: glqo 0q00# -|yڥNendstream -endobj -1450 0 obj<>/XObject<<>>>>>>endobj -1451 0 obj<>stream -xVoGbTUHg;vRU)R i1e}w^}3{wM!̼yǗF|L۳Q6dӫ9~kZɇt͞Ϯ׋7X!jN`4E1N/_.>}8 -7 -SKSPtTl]k@'cKtqcc@ÌhO1p R CpPf|C7n?UdVԸ8ƮIYiր" _fm ‘-rUdߪؚ>1(Ok_%P^㮝>{lu|]$5m4r1ˆL Ç=[G=]8Ft ca?Efa N|;V~`gyCɾ`wBqٷdN3*{V[b3DuI+7@8grYqzWZFsg%8gKQ{_\ڛeZ]ȍ}tlXѠX$*-NTUoO)m]@no.U♈Ʃz]/`poA ]4΢C_[wNa jك[7.h ?&PE%i e/λ.JPb(}P7WF3 \Eб'*[N'0|u~bL5z8d{1E;yW`Fl(xWB@XUo,d伛웁PI[y·hd dGNLM6xJB;1ڒaR?+A*_mepNJsM.ӴM,Ӽxs^ 7ՄfQP^{ -(ZS%EY:nd0 |gW?g;9+endstream -endobj -1452 0 obj<>/XObject<<>>>>/Annots 636 0 R>>endobj -1453 0 obj<>stream -xX]s۶}Kܙm꩓F>"A 5IhYgRe3d:"^4ğ#()oN}xu34[̢!4M*<E W'hF,`q1Fu 0Y77Sxyi:흫~ C6OEi_3^? P^d/JTé_s9+bgJS1PO〃t7o1oEX048"}R UܞH0;τge]lZ`aئvumݼQu,^HDSc]Y*j,4ti埵,WLj>'@oCZ| -%wlǡzBmzDcB܂Jqs2׀iܣ1F 6HX2R 'V uH3g K j%LڃrKc e])(lqҘ,_ =yLi$EL9C:f\`$,C;Vdi \b+tҙ2lzO -ˏ͞%@s ۙUwBdFVS9#e+ˈM7iŔ2yJ f4Ilu.tm !_h0=[W6ES^B=$S#ov幘FHש!/'&4T,ϋCZBMYKvz؄H [wJԊ0t)y(;Y[6ϫ8=vr (+)dqm3L>,oi3wb\q*~ӯGTh5*+,0+<#7FME>ӠLvq9h|OiE aY`eqlG\87v_,>ݐP[27ᦣ5 #)IrtJ}@a',zNy枇 w9{uۥJLgA0!lB C3A;lŸq<]Tz/?%SϸdtuV5 qB >X5(z@!V F߼K6{v, Z c\=WO?-?0!o?χ7s'|ј_Y uendstream -endobj -1454 0 obj<>/XObject<<>>>>/Annots 641 0 R>>endobj -1455 0 obj<>stream -xW]SF}Wܙd3'6BB'ʹe- V]]v8s>M4Sl}'4>gFq4>4 ³N&80럞 :§ڰ7kf{4[ ɄfGMՊl."mΟR 3K:0"+ yBw2NܮTAN[I<7B[,u`9ЙS"?iHM2 -!|-T̿\zLTN.u]> )t|=:(!p] -kIYZ'JKBg0 -4o8fu ]CN1Le޿fIbѣ|%%l>^m?8vXڟO-RlYυAilT<܊ -~8证ӸUZiѺroHe '  `lx[Q+ai.A*:#bZ~ط$ z|{$`&EƝXTm\{stCE9O]$mtIΈܢ7] -(HgcQHLXrkyD-6sFX -t5`-+XRP XU&E6FDz`ޖ"d%V,`7խò>"?}j6lWv@]uxfZgG& >'D=)r2P8m6}k$!?5@0Ml AT)l;ҥ80+xT0ё9hAkpI#7qyyFFA&|6( m{o%7*$FBO=w,UgiH%gI  'z}N1@Hޗg)]Ey88$"ipPl_[kPU|'J@Y9`?oӭc#4EUEǼ| 0 ,|U/ZN]G1uP ?wHU@>{і7L\Ma.>2YP:7$, AiؕF|:\ , 2˦8JU+[.W6<­Z u aꤍsۡvXaCv -D qQ0X~ wFڐ@wmHPFFk._myhr=C".B;/~%݅(\bs#8HACKϮN5^>ۈsm]xsfak9@`09PYp!b6؇8?b&rQn+z.+[!~ܘEm? G:B7\rJp B -aUjo>/XObject<<>>>>/Annots 656 0 R>>endobj -1457 0 obj<>stream -xV[s8~W %3`C-;;-m¿OoLwBb}I?>M2ق|04C/ys3?_f fު^dt?-sZYOSon_- 瀞2oo=ղ*V[ -b9"1ݢld v2/za.}l| -Z۷Xv9 W˖^+}`oP|LMiEZMi"ΪS3:Yʉdf( A qz+#iz&*'jf;^ -tQ%Bh8LcKq(1Ƞm9r6 &Xp#g $& iR)9D2wDN44jF{e3x'1~XE,O%QDAĭsPmϪ\GPrڬ?l޾a }C_n׵!q<)&y҂͝9>mgܥA|M4 hdx Np-4~M;Jw=Ԥ#`ARj[O+Qݔ\[P`"f_45N-5߯?^)̅ވN3 -˃fx957ґ;~>܈4˹\ƒkf?3endstream -endobj -1458 0 obj<>/XObject<<>>>>/Annots 659 0 R>>endobj -1459 0 obj<>stream -xW]s6|q]&фƳ)^k$h8G.`_]`vsOe._h0uq(K/Nzw}E -T^$~>-"[X6ooJF[W\ҲTT4e:|iy~tҧͰtX1KDY/A$6bYDͺ8oV~t.hź(dTa >oLY'#Yцtqr  BХ4UV*yO g;4(4]xX֕Jagh 4U_A̩KL^$-@yO#YBeAb TeNRau٩TrKRvDg&uU@swowZEBoJK(Zp w7auS~r  -LK Syxn =FWYBN},k`c7#1֙a"EF;6j#QI5D8{y\p~%ث^TYG,[ǏI)> d=x;M䌔S$![XvڈȚ,3O @Pi.:?/p)u s/P?k+X -1ѓ.#^ί y sdm=^mH%lUEp8|D RFz\|nZYkx5R;T`BՈ^N֙^AǨDUn3Yej64+ܳP¼/6iR9穀J " _!|^&[FQv(qLڻɂ0]Fz j% I5nno}ڊ@U,b\:Ƞ70FwxAV,) H;S(L[PC ~ -Z,\peFX|5H~xBp A6䓗"^>nu(Fmk-jZ= -፛m0I S*`Fw{Z 2v\P@ZSj ~cԉzhdZJ#ȣeX?`OD&anjg>Vf=.D1isq?dp䖘||׮%I;#zC, [Z KoA/)Mo8mQ{ţ! =P*v:38lpȥb7oGg["^F߼WS -+#37ߪU xl:0Mke$t*@n'D쭍a`j-&6ro~'yܤ[W<$Mxn@wZ??cdw8\}pendstream -endobj -1460 0 obj<>/XObject<<>>>>/Annots 662 0 R>>endobj -1461 0 obj<>stream -xX[oH~ϯ8JBT M)I U#-0cpb{gʿؘ[ETMws׃5E6uO^ͮץNm$|GW>G[סZ͎#-WgjhBAߣQ`oȯfU<̒En"R( SCJ"H4&&zki -3LdR(\hPYkz&&5ZG^ 4-=͠)MpY,PűZE)WgTӱ\ݍڛ"~˴@ɺEAzHu. gK6IZ^4>Kr#aLOp3?%ɍH& k]'s汬<QzgMilP -co:;h7QPx]ppMz.HIHWyj&f8#5C>3U|̕p+rS -hw]X*6XiUŭV1Yi9F4bod|u5 0K(h8ߢ$" ,rW[Tvg|،zyW~ *xf/"H.Qj(/EЄd%{MZdj@:k-$ -#Hh`!Y,[)9tC`bp=2$M!\ x/H% 9(,uys L:}PHc0_RokJ&C9ׂHI,_C#VS2Dxq. #CKSX)v͟2Xc>ȿnHSD:}>l2晵T"fVFh@v3KÅ u1=WlY9ue`]ny(U\X8Z`Boeg\MnAEGsœQ}6ԲC;N!D"ٳBN&vd^_G Jp-y7˞hBcrDi?ElF)OeB^UM5h!~}W'mE{;QŒG<-f1*㽙q4pL1?N-m:Պa\CmI>jN-!' bø^_[Vc)8!p_ŮQJb<^6sqNg*+ң%u-U/гÆUC޺)$%m)ݽd㪆aHMFat>|d{I ;J|Ys~>GqIB -MYLyfD{jqLĝo\вyT!ovCpk/r -ysQ,-+Z,ÿc+G>~} H#",Xf+iMs4 ځICT&[ Dr2[9Vo b}& [RbKV O d(ؐlsBUu$›2l Ϙaw5~_Dؽ[G}|DnU]g_; z~={huD^|~G7h>^@Bǂߍ:K endstream -endobj -1462 0 obj<>/XObject<<>>>>>>endobj -1463 0 obj<>stream -xV]oF}W\EJ dd7[ڪ`f3ΌЪw<8!NvmA x=ss>&Ǐ޺>Z<+ %1,20 XSEh-ٲTh{PZH55E6K2LSQr kVfoGRb8ZL/?š(bKJ9X^xd gh;jC!ra-0k6j@AcƁiv2^Vc`4XAu( JdQΖ4}؟Y8 -Ć0~n~@B"<LHК*($-GDY)hrV -s.ʋ-F,7?LLYu)?sJ*ϭ'sL9@ B:M["y -Jn FsZ4qQXW$Ӵ"lj˘)6¾v<3*@^H,uܵ;R7GT{1;Ϭ:w`j{'g0vcJH4q'0QKik(Κw|0O]xZaXa+{\,>L.xor</*0~/*yjv]'1(,@'ȍƓߏx zl7nwM|/$WI!r)E}?^#TyF}wo4L}8 Fa VDqMS]|}7UgӂmX+~_j@;Kp#KjezV\ _~g#AX`5v#ckER'OǏv>]bGUvlj|͢DaC.~S<pI%)2W}/ltNŋimw]{nSF'??fjĵ6^PnTϘo+rkZ..Z72de5 z3=5Qs>/XObject<>>>>>endobj -1465 0 obj<>stream -xXko6_q˖IaH3-bb%L(5Ϳ߹ȎMVy}NBOH1Mf'`D,b1~sI`C\,5\31d)-]!&F`ͥ(Tb+)X +OAvJae9d"{z0eN>#jI"e(cD*-iZSbrw82L3V?A8sPdW3PR^e@K؞((#.ҽvCe?tO -2X 乌#KJ+GqT56ϕISǕWu^E>ҿ_]ln-ZVN="&Y:mVA k{QlZ1}"`!m ,Q2K8*K{]nTFZD;K֤6L%T(Ѻ,\ wnM^"3:Ix: 9~qkX5TMʱ9{GtGɡs#i:F5_=ST *)?>pyhq4|63 -XڬWZQ.nOhLB*Ox QL" $ ?E]"E%+i5]!ҽ0Μ8IyLn4nJ#!glB1&:bQ$Z6/ub}M$lY 0bgy,Lm?rqaQ컜=m"^>r qi]PkS!ڞ+m2ͺR{73sWCKc}F.5Qa;qVN,vAUsUbPbئXb5ݨ]+2Ƥu kDAy .x ,v,p6ǔWZsHwwjm#\P/zpP{PVpr[N;{el )do&y[UruZy0BķCa]7k1qIjnVdW#%lhx U[&#?>?72SQY;CI~Xbz9Mĸa̳9 0^0v-OJ;"z̍ -۷[s g5Kq|"1Z.7Xx#Jpyrw{'MMaވ"6F(H+~QθgNszY[Tdxy">/XObject<<>>>>>>endobj -1467 0 obj<>stream -xV]o8|7;N^i9H+-QItH*}gi+\rD.S}h8(oWF)3b8c/>0o] bLfx ͣeTDZtV5~z&JYtEdk'cjlh_z{ 1 -w -CQmݜA_gBLˎy"t)١>-:W^P-4 'NkQ48\(1:о QYFؼ|)+Rqo.o?1a@pNaH-=l -K4'D+o2gbmaHSb%=O4kz$@RҼV#g0qn|2UZ}vȵI@暷C'|k3`{*My5^7Mϕx`U> }$C_S=uX\vp|蕥 \\|XGeQ)AUG"2rsLQ=?f!}$7\%jeSA/y6aH)EݘjXzO숗?@[6BRab8SvkmwAg5u@ЮC9_Mpz*V-g~ǹRYJG+?JcP)ۡNstEbwG2?t61ypCS{S87_@lj3ⴚ`? {ixxendstream -endobj -1468 0 obj<>/XObject<<>>>>>>endobj -1469 0 obj<>stream -x+2T0BCs#c3\..}7K#4BHP$YSO! U!?M!3$1''$3?O3$ BOzs=s3 -!)Ɔ #\C&endstream -endobj -1470 0 obj<>/XObject<<>>>>>>endobj -1471 0 obj<>stream -x]N0 y8 IZphyХ#:#IR!$d[O4b -I 10 -~;8W\wOJ>-cKn;=ؽq0;5` |%DRq|>bJTq aB `KItFYmÑd#*7yOOC/]nvf|E|ȇZTendstream -endobj -1472 0 obj<>/XObject<<>>>>>>endobj -1473 0 obj<>stream -xW]o9}ϯ;Tmm&bf x3cʿsmIZi?D -sιG]hܧfоg%-Ao4~y~vֹ~fKitM/-]Rg,%MdHw1fE3vZTy+W5,=iw>^j5oȯ%,+o\-q&'gl-EQ{^&2#Rd WјNA ֔BilF{kBfV)=ع;d뵻AUC:>d^dO:;~{<UT|N.7B5SH0Tbֆ(Uk&Ɩ -|iejj&ܐTT ExtP`zf+LRHhߎ8`yg =q{ĵc&(QE.\F7j-p:uKȒ6lU.0(HTJ{ RADI爳QiBձҙbt"аb+T!ƚo'M+#Ta;:%Kb! ϗ2^fkaa~WǖCCBȎJ 8 |g)Pd:>J7mk8r<{&^TT.CTo%lk$y~0E,ZU2VHhНPҳwL{΁;rk{j8 -hfxH4=!mc+I` E#@ -~'?XD9UdsFעm5 RvD_x>/XObject<<>>>>>>endobj -1475 0 obj<>stream -xVNH|+x -1}aG*^ ҪmNo r.Uuϓ)M3ՌKJ˓I4th^<ܸMG7E޸O..i:8GzEqFH0P!VYzcHOo/^ϖgB -'QS.-yC~'!29bjt5oD[U -5P) -:X*xB ҸQʭ[ڙN^"tֆ,ESڇ7e MrEY8")dv݆K@u]2<%.'`.fyQҐW4gLxhG=[hɏF -먪BTIʊ1udr:5rD^<@$8OeJEAZx*>FV )B;R |S2'J>ˎ \yJZռ˓6[ `-vWG1G!^h<[Ogy\F%c~#ҧ -{vS>*Z -Čwa0^y8mdD/TjRee1otfyɻxח e7$,c!sJjO>`)⃸!|mH>Wx:"jrRf-oM2E$~ H_1A9oP}$ \']~{ukF 3SZ\=J pxg$pE'lZ:9f7a{0E`<&$$)]?Cef2Tde2:) -6:5 _Yl97޿*eO'og-w}% -@ka8{onpMqr[b;D2&̤ eONXzz؊Aۆ|W wU }`" q׫782ԮvVEs{o'P>= $:$7ĀDNF?nX=٣SYWv.Ds8xcPQ ~kΆBVv=pI $ 'xt_I/$%9]*07؞-Y/?_&W>q-Vh\x =_0'5endstream -endobj -1476 0 obj<>/XObject<<>>>>>>endobj -1477 0 obj<>stream -xWMo8W |N$v(b/zɅhD$o,+>m&͛73-t=Ǐ״/w/7g.|X]\z 6pX>*'8'ғ*׊Tl>y_8IW/Wafde2@h|Rܙ@Ag8~@MBU+4M.$[֘é1.ׁ7kOәG-8nwb:ӧ_k S_uqj&tWӗ8yRE$0FRBT>wxZ}m)v};rpK"@F nS3َ 1MD^gڼ24 POաQ op*:R5?GM LsuXDV_Ѻ6^F׍iUUީVʇ -<-WX ͅ ѻZXsJs*S ̉^(^)Ժ@QN2T?) -d.Ύm wpeΣ!!H#7Ƈl -sr(yACf,9SXC] -z0]0ʠmUT{sij02]ErB+-ԕ{#k%xO N+"4 ! .y*gsno @@ b8YV4GHh(dcDsS:<H7c?~,byUUJB0ϗw9i- -ݾ{EI+zy ~ I4JaR4< -Ԓ;yJ#F贻L8eiCuTiDȚPj  q0L5@{eA~qGA#Z^@>2< -8#l#/n)QDuų==V`තc8NGH>Hœe[@Iĉjk~6d;]+NkiPz͹ ͊QKVҾR'nK dN&A,Υ,rw_mlL!bܾ`_h]w~&F߇QO[Sb MxSqV^Wt8wL,n-͌6uj1cJ.[H޺ė?wU|LSxo[,IGڗ1rhqfB `]x囓fu-oy_::0K" -7X䁱k_05 fz^z8.y ٻtxHXs..)endstream -endobj -1478 0 obj<>/XObject<<>>>>>>endobj -1479 0 obj<>stream -xXMo8W |JXv!mZ`(腖hD$ Iɶܢh89o޼ŘF7nfWlD"t1 ~[Oiƕ -ш,g7=I"-=Y◼,xw8'EYi⥒/ ȥ[KuOo%9QDXț,/'8 7ل#85vRSa#: Gz@Q!]nJ$7/3#֞WDJ^¹E JΝ낄cf ⠻!jt==e@'񴶦)aL8Iŀ\xm@';GZx3]@P«EKOzx\bY:7eMCnkʘ9hl`dUvp'AHW/2:M1[b'1{*}ń ό5?sM.unu %£@Ws iog fz=v*Bm!CW(kcĭxjUC -$Xk).W\#P8Y +P,WBpGEϫ{<<HVATUH" ]C4ZGFY+o\*=(2}@"gУk,:3VBX\Cx"]IzFRLn>!lQ]* zH[#SiYraF)$Ĩs`Dl^XBazTƬHcñÒ2aeaZE؂(PI`9N}n 6za_m6;L_ypt % `08^sP0a'8Fe%FbX˪Ĝ;#*)%zLNyǧZˑJAA$hTb-ze#9DfkJ-?==¥![DONo'ق?ҁ۷h9dT9?NkG7kH?}ASv]e_xL2vM l_^50Ԇ +vO9jsυ\ `o#VI\hUXS\V)*p(hXjJW+Uy6Qteo1q ͂1<-,gREQiE11x`Ӈ95F*SI@zKʭqfgP~ox (,j!/k '3Pe}]/涒"lQy(4}͠qe12Ww.@x!.`M9ye -^Uc, Ⱦ6MZH&QATαS@)>w*T~cLB -١4ڶ-a쾩]?-@ ft;^, J3l/ [1c:f"Μqy5$0endstream -endobj -1480 0 obj<>/XObject<<>>>>/Annots 667 0 R>>endobj -1481 0 obj<>stream -xW]o6}ϯԊx3lִtDl$%)'=d[mR[ǹ{lHtDʫA6ןg٘* /%i6Oo4ƗlDc%3Oܸf׋1 X!lJ"8E[aՔyV6ŠJziBRRdAгO$5\-ɬ҅yvtByTo6yհ_^"En?+U{~N*v v0FD^JaO1U.2:c_9Gc0z,V|Go(xOi/-l4 5Ǿ?r%\TKAϪ, ܺIe6O=HJυb)\Kir2<sѻe.պD2Fܑk^AtA12ך1Y"+C-e!PK<>-y‹}J<zHIm~Jt_xFlDN"î ƃG3cE*kb쿐$vMgt8]U;ϝdċt]-h{R7ױf=dQEжGFVE=;㙩 [99.T$ݼ@1/=4rA5>0]dB%vR;m"H!XfeM֖ۯaHhOQ:nFC# z -vb; >28}*k@yU%7"(,QJ|EFCXBvMT:Z U>w{j,%Xd 0(sgReCzn\ -&l L8iXptu'4iJ=6HZU N92pZ$f6ݣ?-TnC#16k 8ޖ3 jǼMDɒ6ooFP[Q"#w@&QXPAo07lzccu -u}ǚ_ ag_Yb!;7>/XObject<<>>>>/Annots 672 0 R>>endobj -1483 0 obj<>stream -x}UMsF+|"[A ! HU$Z&k/J fXmdׯ_B7IDㄲ7 -Fxr[/ALqZR<+)fAgc6t7pϦETgO7\hF)̈ҬO폕YSLRnJOKoDpi~;2wZ̖?Zxdeu|߱pSz`(<^Rc]_ݑvM)uMNSn^IeYQn"Pa2QKPʌ+S4 :sW-(Eav=ar@Vꉾ('K&)jȽ8*TA$JL$ybk*䜓Yw\-ZAz1I춧 \"oQ/| ݢ!G]cy+жC="j)20$IdiL_}}2k=C -ۖ%b7 GZLctJlkY|/tuob)AE~>א0Gyx4go<>whJ;mӵ&FZFaqWɀ?[ гV,8zAlڱkH742 k\Ni00Zuޙc1P#O/OF3 `B,,&YY׬-+}j{=6IWPзZ)}B|;s0PԲh18ZGnY^fKYnPU;h1Hᆩ5Qe{q@ro _5ShaF!{@{IO \5u&%ҫNlL^cnծssp<R@rDa,Qlg·u!]merϞEC+\[޴ ݦcߏzse^&s:do'%$DXcTendstream -endobj -1484 0 obj<>/XObject<>>>>>endobj -1485 0 obj<>stream -xVr6+譊(z:7?+eGk+|@Hš$$~{Rdoe˶̠{zvR'IF1ɲO4w8o_hJ$"M82+ݦ#6s9n)|Ǔ)sB>>gWkQ{eiУ(#Q|Hߺʞifu)KOlgצ+SykBY;R$IPV}h%r]!is"$c>qWܙ IF !_kG2 ՅNQ) iJbQ(z~zO lnbK](GN٭xt\$| -6/ *DOD^J;ưνkiwצׄkѿDt'c[[*cp+Ϗ[z$t)ʚM6Yal|+x dU -8PܡUBy`[Es|dnavj]b -BMM%ZQh wP89eaVrLp87/!ӃXiPFezwLYS64-iI_bVɕ9H#sW7"j -pL>Ȫw_=(orJA8Hf2sfiKkJ|fi=FfAw)춛?D҃P*4^^APEKBKQr>=*:-/3T7:ߊJBU,g?S ->hUT-p@8 eIO+Pɋ¼0J" SW.P=-/X+FG.r /Z!:Ɩ *~4lܷFs 9ZؽNj;XN 28D @GOg:QɑڂGw??%anC}N<}zO ? Fh>);նBYgǘVIoj~$ӎ̢7WlEa -nzU5ґˀXT0qq`HS޹M]cAcuװ18 QPgKtOF-N=Ha@{JUJP|S7tek-hXYQ:.p;P=(_ Ӂa-5,&ލvǫBКEb{ UQoB)ZX#O1olu`.@<o{FޗB0}`BJ;>RQ`inj8GQ,K !a+ ,tgn2;ʒt0aÙa2O#,sys;Bendstream -endobj -1486 0 obj<>/XObject<<>>>>/Annots 715 0 R>>endobj -1487 0 obj<>stream -xWsF~_/ %K2L'}hĝ>9H:;cҿI&G۟D7lLqJE}!i$9_i n?޿>GAJ`L5itDE/J,ȅ[^$aE3 -sNi(J'b%91LzBlyq^E1t{j`^oB 卑?q&'^A97bX-/xbe>xv$K^$COSqbN!^H9 Mؿ&ryfN<ɃP4&Pv ID;vxqFXf/'%OspHtԀŸqxlLKsTYYbIڂj͢}J:]TeQ 诺}JPe8jtUmY=<~: ÍSE( rݪzK6YwAku_e37K7Sv~.{*LS蕳]O(BysY4~(^Z 3]kJ^ɐs.LqfQ"*ZS2RZx5Jy`McT, y_9֨*@[*'* *tu">Tppڏj{-9D<4ClMիJԸTӃ\_>>+3SG3JE`^( ,)w+ @J"=睫黷zЛݷf:~o{ϽyR٥YWsU{1*S -Z~(B?U/iO;Yz[W >hI̎dgv:Pv4N 4{փN5ZCƖ\'r?^75ÊgJYR(^_ek81[ {]ŽZʴ/_eMsw]6Gz72y7b}(n;}n jͼQxkbgKKSZ[:iͺ+]mujowfc~3[^^7E{uhKA)uUIDC-D-۳3I%Rn#^>9H֟ vQ)v 2;xnGkێYG*g>>iNw;"85 =@38p^}Q+~(E=aa:(HȆB {nQ})/C6YjT6N6?oO /+r 4mcn_t2WёQJfyt5Ӡ79úLD?qt)+gt7b0YTt,#eiҼp''1*鸽%k'2ŚD> 1g!%Ydi['RWӓ?Nendstream -endobj -1488 0 obj<>/XObject<<>>>>/Annots 717 0 R>>endobj -1489 0 obj<>stream -xXrF}Wt"kHole'ZM*Jm !9AQܯs),]q%[)Lw>}_MiSZh$zŚ?go$mvv59ɚJ.&+MٲzE=M6%524kn#0tY+}Qoigt[S)CHU'J=|v70p"F#EQVѓuQM-2:|MSq F *Y$t]-Ad{UIM鶲޹kU[߉sw4*Y2t7΀q Kv/,_ohe]Za`C{)c$9x^&) x*:=`E[.L*Bسh6;Lte"cP!ֻ!l!HHnV0=ZՕ5(Ihåu){-[#O\TmqtӈRr OTe)8Z;dʆor^ƾ$B4L=ų]=>/m~1}iDw5U&29D#=6`+i$T27G*3IKזj41YfDe*cL`0;Q!  ((p^#&Ѝќx#Q4ڹ)B6&+>QɁDAi!)H"\X\f/"xW0 -<`-04xZo<5e=~ET^]E)E[_wר, dmPgv- -Kz^պwN n j9\S,.w|B9#Zo(2W KAZ@/ο* -<%dȈzB )cwrHɸm̘7,ƐT $z~A -X?u&f7g"Z73NL=Kg t?\`Cgd%R5L#ڦFuv^Ueوj'_ŧвg8]/?QQ*v^z|LSϓJ(\) ׽Pa^.W B:N'׵\~GD%q+$u:yru: X},50AKk(+ϘT#IjPaxUT?o:yu0e> p`I@,1gM"Jw4zB%Q0Q@D?>чS O+S'?S!C -6))gOxt; KLjC+rQ_ܣx/1 -J _@뮂1eo2/؅(1y`uCiE2Oܭr>?90z5>9Y_s J {wbn~/P4TqN@Wb8^=_zb]ě>v|x{Q4/ss&׼/l]JNGjke1ek6W/_endstream -endobj -1490 0 obj<>/XObject<>>>/Annots 720 0 R>>endobj -1491 0 obj<>stream -xXrH}WtySedxդ⪭A Ř=='e 9}z(~" lLI~4t~> G4'x?ī/hϧ?QCi<E|nm() jR`L!SR\H>^_VI`!n̤*\ HK %'~I]JKw&i@ &an84F=0 -.$ YU Ŧēd4*@Sv oEPFte%Dx|tjfbI{R)l -`RPOuerQ55Љɢ vTn$S|5̲0(IHPR&u mG21y.uc&\ t3bCsQ -疢lsXc @r~L0 -a5-'GVfV.]:}!!>W-T*+F69>;P~4|wͽ!gLU"4C]bxGZf#NΪ#WRrѦ( ZwUFdY(CP>|[x1ҦKY<6v$3+M'Tg֯ˢ_ΕYp&=E ~*Ɯ wn"r*y"lw!{f{97;pl?ŸVn{MnܠvivId'TW*CGi -5е<4Dx ~⡬lܼR>/XObject<<>>>>/Annots 724 0 R>>endobj -1493 0 obj<>stream -xWao6_q0bYmAml)vk<òHl%%8{GJ0A+xw{G%'iJG1eY%4M9ůUlko4aq2ES*zeSA׽gsIdrIMHg)6Ni4xouSf0>u-Y̊Avq?NNTr$ȉyV]lB-}1ns[cUgc.*(?;\U'u"Vr O_ onk }D%*ԐijE ߀;^~J,.H/(PW;BKծ|ŒUpc֦)$gT^. %쏃9gr-jZYI|^O>Wjw>LzTVۖ&SΓcyKgr ^o3_PdJ訖=D`9yO.Y~oj跟ŚYl ՘;X׉+o5F0olb݉/$\:tv׊gJ|v1`Ũ R}zy^`M0cwl*|G:9Uc0wtPC 3pE't x.N|]~Qx;< N}=M}#p+f~/?2 bZ! ;wwtz#'%ʡ/Y0u , {C~9|h'yH_Wendstream -endobj -1494 0 obj<>/XObject<<>>>>>>endobj -1495 0 obj<>stream -xW]o8|ϯ -=$Ӈ+yh/PZm6T|7KJ(XrvvvvhL#9]L)/FوMٔ&K|N*>\<_ͲƗ4_lLsI`4y>etkztvYғ0>:g;O@e<7ra M^R7' ?"hȈR8vqvHjJa=YoLbT>/XObject<<>>>>>>endobj -1497 0 obj<>stream -xX]oF|ׯ-J; %6 $R|Yr;ɡgZ￿ኢζUM;~ObF%YvF<[i*ݸY~ZtJg-//hU9;U~&ku4R )ux=~Vy+ 2aBz)0<MlUk2^U5{nn} 3aK޿{Omu#)Z2d:m??dBZ6 -?!?M&RRi*xHն4mճحuAB}m׍?Qȵ;AkE^g ǽ_Q^>Eή+]gt[Q Һqh.5b:tEEd>Иޒ -A-i (%dk+5ݯ_f?ї%mNp(j׶^֚iWPqr|d=T[H6NK0sɞG$q'~OpǟƺZU՞ -1.M_gs -¸`›=ˌv?ZVvE⑇νTnZ!TE,0@m՞lI`(CkX)e 4y$F+uf!FL.Bh=H^L -TJet]y{&xiWl7N5I w}+=$)7p3:w>;6Cu J>͎% N1go^ -UmEY[^[G5*|{`ʁ3qˈ"9<_ߤ|hN9͈*o+RGWzY |±r6z qݷ|G>q!lt_87 /#Wv#7"'cZQZr #XKlx iy\;l[r; -}4A4Of圖˳p}wsM -:bX1]&gW<=Ӈb],/eO9'quWԞhendstream -endobj -1498 0 obj<>/XObject<>>>>>endobj -1499 0 obj<>stream -xWko_1pQ,Ze= -۷Xm}YKscq{fvIL.ֱ<ф7ŔVGdLdIs4Y$:+s|©ɜ-&'y2Zh2uξ3ɺДF 5:A7v-bjw,7NM⩰)ӧRxr4q of|k҂rhlnJz4u :w jOm(uLMUʢO\KzXOHқL wBq:m'UΓx*ԈiC\,q:q 9KOi]ɶ{R؝NM?4&RsX;vSM-ڕ?Mt$}wl_X`uzO|mj{2V?OTA~OaK•>p{KïV7J=cj;,?DgAB#bxaiLoUb - hì7޷xC5ADuұlRk+(g'7ƱEv*Ɖ< 2N>?|zˇIl]Z Sm0*C\IUɄs;]=4lgK˻ nͧWGg>/XObject<<>>>>/Annots 727 0 R>>endobj -1501 0 obj<>stream -xWn8}W Зql@Q x$DH"Rq{lGIX *˙3g&O3ɐƔ~ǛtgdDiҧdry:O!0'>L0Һp5^аObO4|(x\oDdEӄfX -c]ҍ)tmL3t`$~y$8띍OAB?*YɧZY$"Sznh07WreԔ"k B\n,!.VR!%F8W!5l9%m۰ZI B!7$,eҦZ,OJأ%uej6Tk?їFL!hTK,*ST |;ͅҙZ6Zlϰ',_e?tt|q΀2E|K0΀򣥍B kL- -OZ_P怩*xLh{E+YJr= -5{% -0̿-s"e9RKeeV -'m$NsskBx9} Z4`ؚ^*Тe=/zrˎ5*)#H`ץa09F=%aʅc -Q^_l^h`Yp[Nd,ݟ\POnC~((²XqjvȲI|6e0z(%a ߙ(idC4WCKIi%&dm_4+mQx^% VHq-UV#>hi* s4B< $ttQh:T7zais, $cI6h>9Xbo}4zf8jR; h҇qACZC\5C;E?y̯ktrǸgLNĂ1.q޿ڋ|@QBTn-гun"Y(#[˄gh0z7VlO `eU[㾏5jSMvrO'"A<0- -]yڇ0/NK >0Dn a@"< v? MT&8!pcfUL6.Bn 8zRELj_{S-rior> -פ`[ ka#Y% +CM/g*l対bm+À%QA]0d2sbNkBrXkf1A -n ʆ1m_IlրHcP%&D H;ޅw!YTإe\02֬\M";),&~sF/:bmy}jxeNob@i\h2J&)΀<&W_4endstream -endobj -1502 0 obj<>/XObject<<>>>>>>endobj -1503 0 obj<>stream -xWnH+C$ >eD$Y~V͐2Mۻ"0"in:H2h"iyOr:'CϦ<_eg/g2| '>dd jwYD[;|n,sIJI- -]}0 c p -f. <׺1p{9~P^v¦ӕx+ -jSu&k{7!ax}K%ksb/YnŨR˯)Z_Uvov:s` $Tol@=L^mfu Fdv6$am sدR`ɣeL9Io?k8degty~?־endstream -endobj -1504 0 obj<>/XObject<<>>>>>>endobj -1505 0 obj<>stream -xV]o6|Xb8p(hӴ6PMQPeN"7KIN( N3{-GTj^.knAJRe%$꩕&| 2pU[~eV7s!ޠӸ":~2^.9 -U[(8VAIWϠοB睫CpC # =ʆ`K-(8rll z} ``Ψ"`C)\]Ka!8.:!i<5Fo8c7/`v=IoGA|(zU)7szFN=Yvz={+kQNV=&Y&O9-7E,رLXo@o7$]wB{;~xYꦒPNyhɉ\4{ۆ p*wpq>NZ7 - D5Yްb=l/ 4U`TKr(jmrUfp*^g;!tB,e,k-]OQOY4 }H>dG5P(|0?5Ol|j+kTendstream -endobj -1506 0 obj<>/XObject<>>>/Annots 731 0 R>>endobj -1507 0 obj<>stream -xV]o6}ܢQ$Y6tmP{%V#*E3KJyι2(oDiL ʪQt13o$F_(J/Q0$Iw&ҕ~A_Ǔ0ף(_FICYREFTJ.K&ki*-M4ED(+>p}y}. _ -, -x')kMaw8?ؖ*3R-fMN6q(h\3*-x[ $`+:6+YJp@i1 8~c$xE;D o1: |Ǧ8È4H&\ssRR@pQ -.s"+ <˒@Lwq9O/xͽj Jq),m5 0 E0Ζ_%:%w4LM02c].5- q6B mACJZK-l9.fV|[6'|r -UT(Әb{pMjKzߏ$@=R`e n'`Z[Ұj9L HkDB^:z`z{{  ڕ4WQWYXuUbˆ+i[iJʲ>/XObject<<>>>>>>endobj -1509 0 obj<>stream -xU]oH}W\eiUTIh>UXVBOg˿3H!ܹsν5JhWB)2hO(KqFrS=4[[UO:ިq}dAeBi2 YLwF0'ȕ!ƹʽ<~J t>6#oJdF"K#L-ZCV5F>*4;mN{YUhxI_q#[zRuGh&P0$uw a6 αw7iqk{IwB(m\뺨uЏkUȽ7Q^-挗0uӦߎkv@P%"z3DsGyzf'TGR\|"_iuY:ƴ}${F-+o.=Sw4xWR(Gu.mץg 1=R*$Vzoit% [g3!T{rJac^XᏴ@\@76 1EFƤV@Rkd*A?BĕYL?WRN,/C -0 >5jgq}7L4r_K[n֍qzP! Cϛ*gMxAi(󕳴5{vvn&%,Av[$=ynooOXp25Xo9iBOtƋl< ynF"endstream -endobj -1510 0 obj<>/XObject<<>>>>/Annots 740 0 R>>endobj -1511 0 obj<>stream -xWo6a;$eq2`2V{+ehHGRqIŊb)04HKw|w 4j0JFσ,hUN$JkfYrٝɔY2f49+oYYww -49==KҸuEcm8wӌm$c[5vfɬYhۋ>bNiQtK>܈QBsQ- KniCT=BWBo#:gVZJßy: Ώ'6 U5{rx$i0%'ڦ mă6dyd P0Z^Qp xOQAH|@O#t S.R}Wn `s"|%Px34-E~lc)(׵3xIľŔSD89CJVƺrU5֑,me쫾˕*%9MN໧!<؍nʂj6v+(뵤!*)Gn-`M?1jrIK|)]3%b(~ wL;9;tn#ē<hxvܯ5-DqLH:n,3v!;6{~D{҈l e,7!sC1#A I4P; Ǽd_A`|4tk?kUC% - ``b ڃH@+gs*N߽vh:Q0{G_բغ;. -uB6YDB{WFޗ?R@^ёaG('UbO;Q{Fc>x -*EvK-jakA'*֎q^õpA2/ב bXDa42@*k_"8<;ϖ o/p,#1U|) -??Q n/K -#8$K> Thix"si\XuZ$짛9‰@FںrV -yb=.xXׯMk|# ~;s4\亪ƈmE\Fk]g)^h5$lsI膕Q6>USzeoYȐ a2G?Lc>/XObject<>>>/Annots 751 0 R>>endobj -1513 0 obj<>stream -xWr6}Wl֙Nlj;qJ"! (hYH>t2 ={o>O '^ÛohLi2'*?V9yM;wVҪ3 oAQ⊯5׼;o؝Γa.}zɈqłk쎦ɸ:˻߀xOf3{ӥOx8c6Q`  sw@<W@4Vc {v^!8}Zy2" "=(-3L!?n7/1n_B;'쟐7 :Ň"zt>͋*-9.{)o$iOgob @a@Lzr5D.6֚T:G_` O *voLi#^^ ->j.D+yijJ }f",YJJM 2Zx)כ VS+ -vfB̅%ޤ&?ӚvV ]S x|ӂC>.RPa%!&y' -XYzcvQW,,\hiޙ2h &6y#j4-&yz :xl/%&z=6)CretbQ7 - Yt\H[ ^L&D/C,X奡gܨgVܐ@a Ԗt3F/F3ژ042nihv"HpQkxY ?c8 0.Mqx -;匣uP- q@Wd6߭xĬQEz7Wc*MW<%! 7#h<0'֘;b3n`5+y,nr.gV-ׁG/QጤOC*ɠǷ4 7 +&2LZк-ЎOڣr ?QAXx "|RǗ~|xP׽U?%ـ&I2y޻y{A|AJCJ -(k:ߤ!O{s>tL'3|Bxr/::t=zendstream -endobj -1514 0 obj<>/XObject<<>>>>>>endobj -1515 0 obj<>stream -x+2T0BCs#c3\..}7K#4BHP$YSO1,1/95E9?/-3($3?O3$ BUs=s3 ]!)& S\CQ)endstream -endobj -1516 0 obj<>/XObject<<>>>>>>endobj -1517 0 obj<>stream -x]OAN0 s\Ҵ+H@Ȧ$+${\u,{:Df&'1jIY<&voHF s!ZյӍw@ܣ\bW`+žcW`9/rv)_Va viTDX po.]ɣ.)߳|w^qY0|T>  {f?]endstream -endobj -1518 0 obj<>/XObject<>>>>>endobj -1519 0 obj<>stream -xWMSH+rr@ LFXKU|5Fɒ8lQlin<ZLivIiy&dIrEd7&'c\%3\NZnLɻ˓h:/WvƸnrUh2IzЮ4[{<*1M02NS=*8[Gofsdpߌޙj#V\U!~_O[ϗC{lj::UMoEr)-J*l8T0Ϛn}cVKψX-mf{j[e{nbL ^|`2炯rz-g)e, -!vAڵ ~r=r؀VfS SJ(:a>F*+M:$5&LX$W3)5̪$2?j]{6i9 ",AYFjss:[ 红( l݆踱PW.==4P.J7Җ:@"@[UTkvZ[ @)#ƔВ\iTt)Ӑ$5X0̘-źCbKM:ݝ] mwRK Cmi|2/" ]CSb K d&TZj\ja2t -0Pq4sbx *-M-ٶ> e-FqAhZ,._;kJrHݫzm%^Ljc压0aBl^sspc3=2#w2XI|q08(ATfY(ܔ{m|G^ -ƩQ* 䪈b<x$7Ԙы ϢHN8ݘhXvQA.z-DF -+ ՠfl2ѽf Ҳ/+A_m#zs:Ah [. -6+J-!jvTQHkJ#y4[Û/n<= cF-{aM\]44̖9ݧGF ]*:k+$RIIQ6~\W^Qί̴ORS;;gWnk̔G >OV(Sʣ\endstream -endobj -1520 0 obj<>/XObject<<>>>>>>endobj -1521 0 obj<>stream -xXMsHWtqTa ^c&{eF0kI_g$I%qGׯ_䟓 gDsS Cs9I?FlvI-8_Mh zJ%9Mn-)#sG+ z1<_P*>vkeiҔrh35E$!"-Ym[mN20W#8i$Bl4T3iCQ/He%K s9dA 0q~?pUb.jp|Arpu,Ï[>fjX[plmVI< [ua îE:yX[9nVVqW8&*"l8?ˋ1,y奿xp^؆+%+r4#\]x|>e>|=Gp: МV/N[_.' -WCz?a?NuPpendstream -endobj -1522 0 obj<>/XObject<<>>>>>>endobj -1523 0 obj<>stream -xWMs6Wز$;қSLmi@$(!&  M-RPf۷ gA%ݬ(.97[ݬįf &ڬi納ۃ$+#WN(VFF6G*ɔJRqH)"WTN%Z4&FFZŜ7%Οb~xMi4j@O{˃(aHJ%ET(qaBv1쌕rhC[SY?B"r~{o"A=>; {H U:>9d^z_}ѱJ >~tae8"UY):|2beT \Hv2a*z v<=>qOiWg4|:BaKUJQ:zPeAespB]o涊^eVo -,^E>/XObject<<>>>>/Annots 762 0 R>>endobj -1525 0 obj<>stream -xWn6}W %.(-_RYtS,It -;1"93g.>ic(-h/퟿$",E Loql23>5^ĸ2&8R$_nnnDSƉS:[&p7\c7Y:ԙ<-+'9XUc v5v(vb;o%)|\1-3=[irh3]V՞L{*JI{ -'>Z⒠J?:?^$6|Ov-i#Bti^ -1nQ=*wXz| -Ft3`Uu~![M.ሽ$QXbI;甮e4kQ>Ձ ](Ti;aaJ^{<-^=S -aoD% -iem''خDN/Ժ{-]Gs^/N>>&%/.o&y`eGJ [GDq68H39֭aSBPPz$W#Z -לdN["/ty GQpsu]tGekd0AOk()0AY^O/J? *T)n5>-|u]AW+^޹&յk9]wC”P_YIVꁫ~dе;ʍEafX3eT@_[\u_X{Ľ`.h%wR?'sʲ3adb#msn1Szk~{Yy<{ZasC {,xͺ.vX"*TP;_JEn>9Zƍ(uqdږ2dߵWnB5ȫz J7vpAnxbk0n;Vmyեt%@#gUiEW]J]Zii U'`U6U=ڡ%PL4ꩈW`@iyS$8k.y^ōE5#'Jj -LgD:[(3<x3~~xKVܣ_u-0F]5ǯ>4/nzdݛwtsx2Ol!nOoX??E*endstream -endobj -1526 0 obj<>/XObject<<>>>>>>endobj -1527 0 obj<>stream -xMo0 DN)8v]n -+Z[,AHW{Pm|%"/d -D5,X|)Vt0Y^A@+"4:QIwSFV\!:99m@CS%9X0<+ʿAyF,tfo`)l5j?K }ZYhj™#T}ڹ԰ -c8D2档I$˴t-l[G&y_oﱵ/ڱWWn1c\_&{4ghh&2'7аY(Gw˯,F \RۆVHBj݉Mֵs'E(Et6okYIֈ4XqaWwۉΓy 0շtk| endstream -endobj -1528 0 obj<>/XObject<<>>>>>>endobj -1529 0 obj<>stream -xW]o6}ϯVlh^-i]y%Zb"I߹XBuby?9#,i%]t~IY}HuHRZ]_F.hŕ˫kZ <ɦh4LVQMAݵh[|;]?Ȋ`d^:~q8>S/:gQtF1vMnHYBUbSɄ֥3F6jJôROړ‚8+ESȇSZ4p;ްwosDUɜl'd\[L/XGq@8 Eفx v])Rkp09% O`8扈 _n(kK(tT[g;}}]}z&]vx8Q%)nu<3102+Ҫ;s &qC_EquaR pc@ J'n".ycڤ0C7/7&3@•0(W%ソ_2.`[ -@ "6jߜξEiq%~XfvpˠyFGUmѼ{pIE!yz҄W)`2Ĝy1`ʗ ^ zq Md؀a6 - y9*g:@DeCQ>çc' wc;}"8 J/T;N5\dNwUO~?e80WFf~)p2b7T") $-1L9ƁJ^u]Ρŕo^}Fg_t `, Dj\b YCj\]^wd{'mD(iendstream -endobj -1530 0 obj<>/XObject<>>>/Annots 769 0 R>>endobj -1531 0 obj<>stream -xWRH}WUkdK !SyXa,$h${ӣc\XӭND}D4i0>>>E.`Hq0prv!Aw r.P<|g&xl9UE#Xq?Q087ѐihm4{Y'>24KmFtbUˊA@*kU>ҴYtUξgQlopQ@7e]Ij9E; ,FKRyFSQ,֥'JQ/LV>B&KQ*SR*,k>oM{hU Ç))JO9iV1A&tbe[QމrʁD x#i"S֔-z CzR^l۬|Re74o0](2"e-PgZ2K`wXN.8qNr 5+]R* Q6:q썂17q/G_xQ^Q/Ӵ~*E.O Yš tNFZJzޭdಮWo`J$yA)k eb1v oQԱd- dIдUN'}녙wg$$ѮI"+ӭ2 j{u˵u=7F9&^|p?jS#I Z5yFtPc$:ZV4X@Ҭ^|,v_#bhzR`Ke!eIF\>It5I$iD!3(2THBDfEI70=UYtAjjĂ]({u:&KO^`hUu.9 -;p wjQs5>}D(-mQrUߖ lj͂ܭ˞0\o[XU#pŖg)S =۾ZNR д^g1he%2`r e 99t:P -w5]&'a/Ckvyہ3Tڳ.ӽQЏ4iYr&NǢ>VɕAyn7;(dcs}!\|GYg~on8*TR``y'%:Aimb8p)r0۠L=Y* #4H{v!<-˜ XC [|>/XObject<>>>/Annots 780 0 R>>endobj -1533 0 obj<>stream -xWo8ߟb8 )P/پbKt/5^6-1[ITI)d(Ù7oF_c -;ń B=</1xG9ͦd9W7 -MWQľ,¤21fWxpڻt!5m\6q$ i_V&;oHÖJ4/X4^HuYjSѳ6~4eEE:x<i86ɦuT0_Y.uL*|HbȨFbODMRXyYػ)TIOb]+ߐչ$yog^DVK:NIX*E^f*#ބddT+J IovdU%^w>w2VZ A?DByKw CQ$W퍮a&v_GʪHvZJI{qѺ"eIebUeH1UpΕ [@?1R|8e:Ȋ|'FKq/v΀꒑,!] y,b&"`dsYknJ7̹ -) @e8L* Mesm%s%Z r-|GFǢ{%2sZKp{U@3::44Ȭ& a\?sW VamShN6s!9XD<2"3^r{b"! -&2X˄Q#]t< h#t=zM9.{59ޯ7gKga^4^ߞ]4[R-O=ly =}=?o6xaO;= B ǽ)"P>*fYFc`JejٴNƳY\N($r=||wCk?k=W8ZrJEm*Jn]h96ˊ7ThʯO=Tendstream -endobj -1534 0 obj<>/XObject<<>>>>/Annots 785 0 R>>endobj -1535 0 obj<>stream -xX]oF|X/KJ_ -'N -É=^f4/Hj}zKo:bu],VN$1zIűj,6u\oUQƏz3TH M#|RZ[5=hu2.Weq$ie:蒃BRQªJ2>Ը*z*&'q_hUD@.>YPtIS*s9^_@\% mMw&1%aK։ws=)WDt+TgnĞANKiZyz|F#%z'?NA)(l*I屦}c<[1Y_ֈ/ic*Gͧ3Y);DZ/Gw e_=oߖ66<GkG{S*ip-{\koPݽɀlIG -MPƁ$);d[G,SXT{pO#粋hD⸽`2*%&5ca\̎LU񞙆}x"9Lۜ9PvUxI9; 9cӄ X1[]WA [v.y5,Lf XgYYGj"1E͎l/mEK?OBv4q%"Vx~1x9q/Jg]<7o.J[貂M7rEc~rw/o]mGR;"8)f+|EQ^WFF б d`I -s%rw/weŦ - -8!~o!ש~;А#`Tli`i 60k<uhp"v#k=Z|PՁf1M]UkE9ni?ҦouSB `a-E ɹyc OٟZD'[ MmhnJPGG,'%rsG9 6:j18$@uғdܢBԦq&;<htƤľ ՉJβ}?C>OxKq=fp=I7a.^i ũ,D<m@Nf ñ'}Y•ika \  ی8XɉǙ±qJw #z%t!硩R" ݱ:]aaY&y`ޜe[eߞz;ԑV\;3.=-C|(~C|L7!wGTV4+oё:G˄҇ѧסp'1F gq |>{*S w˫3+҂U˧xڲʚDu"BnB^ldDs3Y춐߮v ?ȼf!zLp))I 2g3><^ޱj^'aT[D& a5{4Z-.xhp뾲1DW}Vd=j-/h/cfsog@vendstream -endobj -1536 0 obj<>/XObject<<>>>>/Annots 794 0 R>>endobj -1537 0 obj<>stream -xWnF}WLQ& ADE"&W%{f/2%8H46,k13gΜ%7~HEّ:=_!il}ܾ>je ]49-3f-3 -׮kXVDְ 3Rʾr˨^׮Z_YW[kkX'A8Ow+m*W[5Jw6lzְq,_4n5eFa;tNjt}ƺ>Mo/!NvqXEQȼWzOR樓 -YQ+cHdQ/>rtӥDh'yDYl";A}- -1ڔ4vsM,RáQPYn1<ٛz+JY %gGLeP/}+T`WWr-Rq_}W=9r6|jineɪJT~635ty;puK+zu}K7 ܎ӫ#eh2F.EϏ5̪xA{T-c"Yu>>Yxz3S3 VS+np^ǣa'=l;jax8^+׸xX.:dfZ,0H)YaSF6&)xs3Qfw^~d$yǴPi, `OKEr| -Uˤ{ 3c1[M&AwՆT <ԗP. -i18K%8err+u%ItMj;op$%VKqHNU >$FIO" -CjʈVƲꞇ5+o (˃X[|# kaZ N(gQ5R0(*հ䃇S $x?ZAu@Hר dUBdT {HL#xY>lMh-'NH6.DSBbH_߂mLQ'uCB6d{4Vgr4.ä][eXu!=Jn+FOKy)`QyuR⭈%eT-5Djos -#GNGFa <|[joB!Bphy"B+} V8^o{2WOE7Y|\xEPm0)n_.ދK؜DKo]fpA5<t U|}9`x~.OʥIk`[:MxЦ^db X}I*Z3$lw~o`޾z]|5=['endstream -endobj -1538 0 obj<>/XObject<<>>>>/Annots 797 0 R>>endobj -1539 0 obj<>stream -xWkO8_qUʊՖIK[̠ V#1K=; c)U;,3<{þ[/QH!Yq?4woifuc?b[ (A?FCJ7G@qqzO R8EZ4\HZȂkЏXº{KU_=o ĝ3u -Ew4UdL*p4+yrN$l;}}y1yMttMh%4OӦ`h7#9o8qN_^ǒklݢ$Yqc3m_@v:z;D&L&W*M-äwa/iz hOhoXvsl~g˵3VELWo:' ̭g n5YM4QĚȗ)N y -fHv@2X/d.H -Y5K8.E6h~ -GB޵Z:JXŜ0Su'2m:ƈ; ϐfCe@]TnYd H ͘HICPu>Ge2зV΄kUQPHڱ:w֏SU -/*XeOafK $HC  S=4nW;.9 -o=Sr{y*%`O-> a!'[}qA'*.m8m-wkQHt+ Fo4NœF?[mqendstream -endobj -1540 0 obj<>/XObject<<>>>>/Annots 800 0 R>>endobj -1541 0 obj<>stream -xWMsHWѩŊ8e.! C.cilH3BkU ) z_~v2~4dhL4]kI+~'Ed -/p*裻W,\DQt>_$c'&/ӓK)]!BXP0GfyrPtSVҶԘ4Sd|glaL6* t{7ozԖ̊,|V:7ۆnSztdE'tejLYJ=!GW.UF?#F[b%5J6VT+iL[g7e=#V|&kKD２Y22^KZUckl9HT5%O8'F0ZJ\?2[IaĘeKNCi r'yA_}SU^h9(ґx႕*d 597W1QY) -,L˝ǔ\ʿg~7O&P@Š%sxgYJC[+!z9=(A!6M﨔FhՔMBoD9Tdk -K|iL^> -<mC<0Iks{<3Zq0W:ۻЪ#;6:KH<7p!Gaq'ya -͂H=@Y0P1Ę. R[+l#;(/”iX{T ;us2; ԃP^ō$Uh}9}T</^'Ȍ@8ҟ 1l[+ܡ0̅Ғd%*Uea NrZע$(]瞣ܞàα2cy?e͏b)vҰ"> iK0Uջ9Y\ H"Q,kqoxnqR7`Y:ÂBuT`E|<װ9|_{/"'p>Bak~;t>M泅4gsMznendstream -endobj -1542 0 obj<>/XObject<<>>>>>>endobj -1543 0 obj<>stream -xWn7}W IP#Fĭ@jhsk+Y!wmis;sptҧ4pLi~Kz4^$#M'x=|{=~?_ IfY4 -sGHM5ȌkYK<HX7yꐅ@V "H%BE0pa,$aӵY6*2ueFHu1T7#gtzYh+g|pkm?[J#NH =9oZ-wZژ;`*,Qh%JuBS l֭:x/snb5/ΚRZ]6+2޽ QAF.OJI7#L9/sdR x>Wݕ)5^z|_硠cQL)c)tfbr!lŁ?Z %]?`%>-Ҷt/n0>0h^@pfCTL!U;SqGj& EJhf.Så~#@8,\r; Bg 4(JpPGB5*`/v/- -Lȣ5FR/A ^_PRp&J -T9=Ja/ -z8OYU)WY,82K*^L.U-m-[D=jF@۷lvhPgKkrq(hjūƢYaZ#i|^B3y +߱s+mBոq -6had+_1a'jdb)XS%+ ı:i.m~rAЃYMG,TbT̺oؾJU4Z-wRa SAb`BL)QM4axX=Ya|Ů$|uƓA"=@IἈ7gi :qv2MFd>/XObject<<>>>>>>endobj -1545 0 obj<>stream -xWkOFί%%RfЂDDRZ*lYU=w6mcsϝۙ?ZL`Nq3i6 4;\#)y}dB&-Ϣryjyscz j*ź(D1jkF*Gyeh,`2n[]gK8Yq좳y&]-kYG†:]o¸霡E$fҡ;RDDΝTrDdrE ٍu kjG -]Ʌ2z#J7.8'.yp2#e^R6a9\"V.퐖YmKZllpyikJ*U2JIXCH"*Ćlt/Zat:l=  -WœH'L^34b%hgo}~rٞB^E["; / zJ]'" vWZ&t˫h'02H]@_AJ-3[ʶfErwu hw4{Y6;?gӿhdiTLQ|Q+PF#3m(_z&"I|PI:ƍfº* aol>=wP5p8g< ?{|s xO~wJFL^{85,֑r-f[ &s/; endstream -endobj -1546 0 obj<>/XObject<<>>>>>>endobj -1547 0 obj<>stream -xWkoF_ 6*y&yiEE~|gHaM$۝]=icZLh:8#OfW \O4e2z(><h4&^آeMU~`<)Z -sRSɖxlD9.lC*ɮvOZq\UdjjKPEnI ⟸rf&zK^kv;훼F>Ncc|aO2Q9ulMmV\Z1HҶu*dnIC]'C*mZ;-=;c޼,`:qY@ʕ>2NhCm0׎JUh34ĮKN_TRߠdUB0 uHuDo'P"_^W"A9) zMYWSl -[{Sg6m9>9lZ;Ԁ`v^/b(5ѷʔCh< -X1,/ꗈ9H Zu9= -RV8ނ)NT8'~V\ΖkhfrD8wvGL%&7} /iM6sqcUQ<1$4BpZ^= K? - #\:T?nـ_ІMFq3VwO*o5 4dD΃|̔@8w-'cUΣAtVyLb<| g*js Pz>'W+h])笠MJۋHСㆶf'8 -C ;ٟܔ{-Eߞ!x\n7);?jf,zk%`B!֕{>JɿuvNrCzLL|۾}W.phIyq} G$ނ~y>~s |QINZSYnE½2L.wΡRD 8CÀf" ATk9}XӒK9P7i*^7gLm| A-s,6 mRA|@.J`3-ɵs"34%vX Y1~5lgg -<Tߏ\d~!jd2y(ah~c>/XObject<<>>>>>>endobj -1549 0 obj<>stream -xW]OJ}WLiByHj)z++m5b{4?k^UǙ3g&;3wFC:ZPZL)^I4?^!9Mλ4M+cǧSIfG~1A`Yș"D,խNcN `wgd(OW 'Hn"7SUSUcrܐ?RSO|SW lhFktD%K'||Jo{2#FDee`8/캋Y(I -]Me󰵶#gMl5?Fq^ }&juBn3f~w{\ W9V>kP';T=pjN%IfB!(Nuo<0Keq8k\y2-5)ps7v@GU5;[۶HltSF&}ժI%G漿^|v9]jS7Avh9Tih8@S4G&;IK*ve!6*&13SzWJ\SAt:U:g~[i./ݑA6r_yR@M z%*8;ݍPQ "ےIm -b -av7UG/y4:"h1D4}7xC{$y"un#^M͸o@UvE+τX ~|k 5%g;! Cx>!N!Cc3@>X]\xHyႫm592Hq[:lZ#+lVzw_nf |g:>rw0alVZkb!k|9Oc|M|{?xCendstream -endobj -1550 0 obj<>/XObject<<>>>>>>endobj -1551 0 obj<>stream -xTn@|W*UIM?:J#UЇ>am喤;wrV%ݏYD!> Z&T40)VALqi;8H^*\˅xy |fEQLI%; )/Σei@_+wEWBmWi]~1EѸHy^ď0ft* C˘&2`ɯ"_,7^_uhS0K?pXwp>n81<.&Zm/am;8,뵽8,Tz@w'SIp vdSVtW6(-iLnj4Xa-~aa f?]876endstream -endobj -1552 0 obj<>/XObject<<>>>>/Annots 803 0 R>>endobj -1553 0 obj<>stream -xWr}WnBUIeWmd'UUVL:v ȱ vf =Erd>}Ɍ;..)-O)N|Oh1[T|9~RJ]\4 ߯O&7oi>u+Zg'NA;-݊jںp&fhbot[g& Vf*b띦,mE_*}j.i3bS)ONmA=նn -(iKdO*(aS[g1>80ry -iܴ95U]PHse$ve/u~LӾ)į׺"S?j2x6-Q$`2Q|X<v=)<|\WSeTs9Cu -&U#Q;Uփ2/b%Hڌ؀B8sE*T3bX .ՀENiq7\$APFy8Q+~~"]:>MR#2{F{I~[$ۻ;iMmnGrF3ԱA{z0 -:dT3Drd9]u|VGzP#u0Sf\|̓F?Qn -u%RC+_ @_}<VsAYLm8gcBƎQSnT#5&v) X>pZ%qj Y`EesS"6329mC -課gM ܪkh@D4O C6ȄҡKZ-ZDerJ#iܷUn N%[3p)}N>ʹ0 :Ň&*ݲ9R]!vgҝ @XZ[ 55JF @Tem|V@ -h1En =B6yDΖd(w*CmB =+`x  9Ýf Ywudeǽ0/̗~fI"BL&at8덎\&Ũsv.Fw~wՁԼ*:WGccy\Tkzeי,9dQeG?uUh~-g،b -3!_sDFC o6_}'-bQ@MM3d~ZsLDHп)D"gsa'-U01T>rsx tz i#dxv:dRs1bfӆ'Dv?knsZ]|͡TD[l3 za.Tz($A3-;*E 3@Mu"ϊ/X>Ln7 LJҩ@GexաέSm<|be,Zy%)NȑSF::">d rlbߌ^-^X5y3iE5j(KXM=8bF-TRYLlfPb$er]Io _bs,cD9 Fk0u6Ğ`I0Tt@uM&#'fƋTB:FPKYk!/̝^K^GYeS\j֨B/^IQD9N刽m)&7WO_ԋel}\WG//?':/rIendstream -endobj -1554 0 obj<>/XObject<>>>>>endobj -1555 0 obj<>stream -xWMs6W(%93=8N]{~ٙ^kga#=@'@hՐ\ bOMX{'8ݙv7?8\A\_*iÔ3dTcz7BӅvL8DSǍԼ 0-uI - dOʣp\Y!wϽ竦_8%7'$:N!+p.huX"]PW"%U(0bgqxn/\jp#PmP`vǟ={Wu` /m/̲ǖv, -qiV{{+$Tv5)K~4CXP5t7$;(}2PSgq=lEGH&qECÅVb?kӡnB+zÚZ:t<7+Ѣx  n[7_=Ɏ89F5GZFwJ|'%5]~@CrPP[F#|י4հ7yj B7df3;dϯ'4 zyx}pUxc1R4|Blx2M%z<{7> endstream -endobj -1556 0 obj<>/XObject<>>>>>endobj -1557 0 obj<>stream -xXko_1] cxW?mM+PxEnH3õ$opfΙ3C#Mqߌ3:>9)pp1:?䲣Wӽch:ӳ M+ᐦ~6AB 7Mhn|p:P\4eM R{-TFclE|V{CGGiZ7*󂦰X{S49]^\np쮏w*ʶ FrskUq mLsVؠ} }>o35@F#Wג+Ά.!նԇsrx gq3״TwPkXt=-Egg|Zsed')&.XVC(#/a |nt4c?3\*J %D@;+`e~Ng} -xLFe;+{߾W $tfVV7rET1Qoy|I)јfa"r#'cdB۠t>̥th|Lѫ_2.jz}H+0+B[Y+ RzkGOaJ E}6 e({ -0:5P%V&*xeLq͝Y:sppdT|}|@ uT WOLI]˫&zr8󎕉u_F*q\i@xV=0an-"!*W"Zֲaheq1(O#ѿsz0hYP0b\ $33*>)t]^Ppl\ s5$FtX՝)bDu9jT*k5C -4.4*eպ*(HH?Ǿf/^v$+%z J^nL,50S-0А2;kꆍRQ1wܼG2;Ⱥ>}Ⱥ(@|Mr08$`{czɫiy]Ƙ4ݺK^keq cH[ءKD'Fdz&hjj4M"Rł$+#WUΥ,ډDzolU( -"C[.;/E3ohy9^qIr[AF>X(LV˕vXgؒ2\RX;$(>]a -_8LU?~?@BoNwu5N<@3R+)Xl3 -4!-"ğ! ~%Pn 4e^g.;2C~x65؂ 95F b5US"A`"iF/ѢQ'P zL +޷[o74@H;unֆdp}K@cܣ(gn+yY'ObG|3)k +.Z*SkP隓?GPHd (,5\ܪ#K%[99Q@(0FJ0>92;Pm HƬH(_L[۾H-;+!7 ~^ E~%/\^^ۜ +|'$X溃(WeSK%X8+ 6ki*XU8κ$Sg2Cj3sM[ bLTw! #@罻:Opf6TΌobݥNR W&&$t'MRJ"W:aVkV}8ң{qJY۝LlQ Zrd_ҕ{#Q{Y  3 n,4w9ӣ**J*o{D)*E)YgDV{EJȤyf 4sM(H d1kw2Sը`"TtTTkcd2@cS8pHGk"@' HB<#72r;7m8q] 7qw܀ ~tᚃ@t;$(0D,0JBp*Y5uo4QV@G1&Kb*1? d ǰo"k4K!m]mD +!| AF`[v:IGi 6>$^~'PYHοfK14Kv#v&7#6^Q*l5m*{eYazwo/bOP'/:ADbF P25H&ژ(皕2y&;U oMTT]vt141KJ΀1 sVeo"{|Lk@xxN(hn³jrC :3)HdZŌ0cÓ|ҍ?+n\9p|x+~L"cRQbEBmSaImXk)Hţ2aw(;C[Q4qs6j al!״0È9G[G+4&ޑuU06"p%~JYf= r1Y7v۱rΛ˚l642X} /=2%*ȝmN0rXb#Nm.Q +j5kX7njKKkڋ)3Ά4kŚr$"ĹoecA|R|tk0vmfJ]PIA%*,~F†Zj^ H a~ +S "sWc }+2oLnqod5 /;767Z~htKӉ,ZZL@~iZT-zC]2c5/lKŮ5ӭIޮ!pDLZ&f9,vxWT,K+ss _j23rX!]6,Q#R޵^\z8PoT17[Q|11M>QP4k.QWE+8[̳Ɩ`( +WqWa \.WQtNMSF>UP!Lt^e![+L4e'p  +$laLMkB)^<8de1u_~TqT b[t\mϸ 5(l2JVk4[E ZkkPi_zM˶M!:\ԓ }N%yR$k ^Y x}AYguŝ[\=(c EaE*r4/Dpz׹$+a1\΄20 8SihlXleFQLq&͋<+E$>iR9v [mݽiڄ&b6n-9pJLj)cW5GEl)զcȑ6pS?1Rwgf9f&cՊ?XF%Xj44 z rum4O C=30Q).zGeqbSԊ# #{XXx\ϗ\[qnN9[5iBzO pBNU_Tz,-YPc:ъ˩F0[QTYwF~)S Lb ݫ5Fwԡ'yT>~VpRqP^ juN6Lt^8&GnQ&adj1 /oJendstream +endobj +2280 0 obj << +/Type /Page +/Contents 2281 0 R +/Resources 2279 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +>> endobj +2282 0 obj << +/D [2280 0 R /XYZ 85.039 786.531 null] +>> endobj +194 0 obj << +/D [2280 0 R /XYZ 85.039 766.606 null] +>> endobj +2283 0 obj << +/D [2280 0 R /XYZ 85.039 734.654 null] +>> endobj +198 0 obj << +/D [2280 0 R /XYZ 85.039 529.7 null] +>> endobj +2284 0 obj << +/D [2280 0 R /XYZ 85.039 492.435 null] +>> endobj +202 0 obj << +/D [2280 0 R /XYZ 85.039 449.1 null] +>> endobj +2285 0 obj << +/D [2280 0 R /XYZ 85.039 418.899 null] +>> endobj +2279 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2288 0 obj << +/Length 2244 +/Filter /FlateDecode +>> +stream +xY[o~ׯJzppqrƗIDD$!8ے+v +^fggJM=S$t=N$rCě~7%4p(ĩȟ*MtrslvBw6Ĺ)GsteW<rxFgGWD;ث9O.ΗW3?v.[叓ӥ%E)^=P#*ÿN +Ue+,Ĭy"ZAnLS,#c!8!ũL` k-BPYB:<Ytйx$_LduE()Ʉ=&ܳărHAG&=*=Vgl.2d{i_$DMP $OvZ_9wأ$`fHۺ0<"φvھ01ւU](s=g25o; U 9UBwz,sjsa 8eIA^ iVEE,jL.S[).0i>ږrt'76Ģ +G輧&BҨBL\ξN"h_XWeKLf%x"(r6-%.t| ajMjzowuFF] u#+|& k+b%B +j6@ԛ]4Ć+a,$]bPWBuUf^t0)N(`M.78N9Y5OHP!X(n#5%O\9"HYZAY'*:+(+lUwJ({8X|)m$U0Zaim?4;j#VAdDaIU$Vpl?b [yHl\bo\^}18ҵr`W@`AIM[F7^_Kku".`U[prYBN$0'^F8RnG;0k/> +==VoIwYxQyoي~o"0Zz :A\D~ug+Ked̼gp3ԟ?=<~A_'%6w#vg8,42endstream +endobj +2287 0 obj << +/Type /Page +/Contents 2288 0 R +/Resources 2286 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +>> endobj +2289 0 obj << +/D [2287 0 R /XYZ 85.039 786.531 null] +>> endobj +2290 0 obj << +/D [2287 0 R /XYZ 85.039 766.606 null] +>> endobj +2291 0 obj << +/D [2287 0 R /XYZ 85.039 707.789 null] +>> endobj +2292 0 obj << +/D [2287 0 R /XYZ 85.039 671.724 null] +>> endobj +2293 0 obj << +/D [2287 0 R /XYZ 85.039 636.266 null] +>> endobj +2294 0 obj << +/D [2287 0 R /XYZ 85.039 586.652 null] +>> endobj +2295 0 obj << +/D [2287 0 R /XYZ 85.039 523.489 null] +>> endobj +2296 0 obj << +/D [2287 0 R /XYZ 85.039 460.325 null] +>> endobj +206 0 obj << +/D [2287 0 R /XYZ 85.039 399.93 null] +>> endobj +2297 0 obj << +/D [2287 0 R /XYZ 85.039 378.733 null] +>> endobj +2286 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F41 2104 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2300 0 obj << +/Length 2322 +/Filter /FlateDecode +>> +stream +xڥnF_!b +q 1qY[AM9ZMR0CwWUw]ՔXJQFE? LX` 4X}ʅ$H'"Y{?x\)-+Ⲯ&,#GW3^gTg;ܣԀ)6} uF:ܿ8 G)a[tIT+/XwSfecӂ%ʶՐGFO ++`^j-Qh2Y}Z̩^;Q$ `DmG jloq78-w@wSxEhHÔ[4p87Bic\)݈jH00]| D~.|*d8غ;a6t%.L0@5 lYee!՝mWAҊؓEê `rBͅϠOc>s4}$:ja +n;&t^g7Q Clˎ\|x|-uCZ(b֬;i3|Iw +\ SwI Ry ~+bsr: 3,ofU͝:>۴P޻霃w\,ƻ~bTD.@a'fz>HXƘݤ8 Ml^,0)3v>>SW[. +j\|8[ͰMvM/ZzzE'dB9H3`C Zg۲rOvMO1XW`(, !Iϔ%[TX\ 7qc.u1hzx 2NsM/B + ٶfuW&xIw+ +>7t%4Dl5 Gy8+-^t4j9O΢1bGXR#'( '̧/}:yzƻ#` +EC!b9iz]ql}$&f/6.(](iYi֜(ö~ җ\]vͶ\B|^.:0RxUh%'W6vP eHcqxj oz]Q6ͱL2Aȝ`zUg2~|AvVwBp&6_IAAm [O:sS^)a.3f) 2虂Ra2!*7uG[]sA$2LgѶ"O1}Zׁ¨n@GKS5d0_F +??N>OZ? _}W_U tendstream +endobj +2299 0 obj << +/Type /Page +/Contents 2300 0 R +/Resources 2298 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2260 0 R +>> endobj +2301 0 obj << +/D [2299 0 R /XYZ 85.039 786.531 null] +>> endobj +2298 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2304 0 obj << +/Length 2491 +/Filter /FlateDecode +>> +stream +xڵYoH_^d Vч$ 6r@[ؒ+ɛ?H>b;}8DCs^^dD"K$ +/wŚf~{*ED~yj ^1 ,<`w5 4.~Kn\(^n(zazh +a@iG@%Íߕvٔ3#BMFM |hJoo!\No?>7wO=zY䋋g_D !mFG$~#zĵKyԇjg?lp0(V|{`m:"QkI%>s )^8G+u,a=_Z +ߜd\s/'g9%{f;dp,\V؆1 'h?aw{*9L+!K4/ػbMcUo!~we>14  NPC)# +q1Uג~PRO7͆la?`sV( "_ ]hfww;NeaxqIFhXAfAtfGZ:6\pS sa^D{7s9z%\ l&[y+լTz,V9cu**II2_W2y͖K-zk|=0%!!Jf(k2WUSp\2 u;<0!҇ 8xᓷ3nx\Pi 4$#4g]}Ä:]ӑ8paհGZe`;mtz-xa(=}JQZmz1 +щ)08;4u8zh$9h(rUWC71lB*YL,/rtE{+h+p &[Cd;%'Wך2yQzFFY#)_ڭ4}{iVxTZ)XR +3 Sl]M/=SO|-ui{ b2rIpDLh,`_T) 8 ֻpT\0>);c4RA#/lQ +9D +k-d`(} c;2ieHt)V;]f)vNc3J2ȳͷbp qqO% HomJ¢ {pᇙG$y,71O^_o)4Tp1Zhjfի}5(M7ٯ,ԇw c҇kY—ZOx% xVNR@yԨ F, #nEI\/-ץ!WqӀPs[ȅY.x7i xǝ@+Ꭶ$uB`zU_̶Lp-;U Dl%}< Fs!yM7ȡA'3Pz0g>nb,ǖ{ddTyG?D7˼529endstream +endobj +2303 0 obj << +/Type /Page +/Contents 2304 0 R +/Resources 2302 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2311 0 R +/Annots [ 2308 0 R ] +>> endobj +2308 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [380.589 592.347 489.248 604.036] +/Subtype/Link/A<> +>> endobj +2305 0 obj << +/D [2303 0 R /XYZ 85.039 786.531 null] +>> endobj +210 0 obj << +/D [2303 0 R /XYZ 85.039 766.606 null] +>> endobj +2306 0 obj << +/D [2303 0 R /XYZ 85.039 651.298 null] +>> endobj +214 0 obj << +/D [2303 0 R /XYZ 85.039 651.298 null] +>> endobj +2307 0 obj << +/D [2303 0 R /XYZ 85.039 619.773 null] +>> endobj +218 0 obj << +/D [2303 0 R /XYZ 85.039 576.904 null] +>> endobj +2309 0 obj << +/D [2303 0 R /XYZ 85.039 547.5 null] +>> endobj +222 0 obj << +/D [2303 0 R /XYZ 85.039 130.562 null] +>> endobj +2310 0 obj << +/D [2303 0 R /XYZ 85.039 99.037 null] +>> endobj +2302 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2314 0 obj << +/Length 3243 +/Filter /FlateDecode +>> +stream +xZYoH~0c^[n<ّbf(HBRq~fK ,uWW_u|Ut8 +pi?Q%r{`pW)]/-FaA>|7}i$c/Ǔ4ͼ8.?^]"Uye?1GOBIӻouYl~ӏ˛__ 0,Jdx7w3 3?#׋? +F+/ځh{4.Ks1]H6QQG IYB= n g-nI}aK{mi`J@Z|-3v@+i?Swu-6')6[1}<+h[*qfYtK?o&+G{M=e]tL^-ugc]Ct"n>VpT,v$I89%p׵ԃ/5rtUg​J+=j-.P ȼz S7fímnҔ_xwy3^(Vz{'9 84lzV` +kǫ>?5K%Ms6S2p\e֞" \kמ?a-Ezwq7A  +Q uዑkn@6^ЃW-M2g/6D$u%L7Ҋ^pے6C{iHhs\ 9dELQbqϵy9l ,JImMQ^lj,jy`' FY*(H +v5-rz8b-[DTtH!@vP6GۭL1ץŘxgMv:IX5!V;Ls MwTlF=ϲ!> |uݭTV2jKѓUR*2D$z)ǕJԢ7lߨɵT8~ +㢏&J'O(pT쵺B*?D яЂu<7ZX (f\΄. i ||I\:uaX$IyG}%*: + !=]VJl 3y96b-m:vCꬣ~!r>M6dHVvげVu|Jeֹǀ30yn@u#}S7w>g9fIF6frDkv! 7-{i&͌1#IUSGʢ0~T V|&+OTc=\Ҩ +,^q)RR@>#LaEKܔ]wE_h#'.-%ؒORzb| ,foS2TZKs-,W5zu=`L3%VtK\a#"<#|,CYv#gd@1y=+.{<ڵZ8_! FY璓\_ERqXR|.u瀉s@-2=a)wHgԮ9~j;WS>>8Tu;NÞ}{IaߥIy3ٛo6[E^1A ` (0^ ~U߹u s.% K{Rniǘ!TX87䴊5DOǵg~VP,vI g,<"7e|cE+e%3} F +q nW`C39,լ>Z+)>GmOTsǣT\m+lQN6PXRB5av]4Cm[JLC0!b ,ǎ|f!̸?(-wS;_'+GfeYisƧ\3Mϲ0bQw"?Y;s"Ox endstream +endobj +2313 0 obj << +/Type /Page +/Contents 2314 0 R +/Resources 2312 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2311 0 R +>> endobj +2315 0 obj << +/D [2313 0 R /XYZ 85.039 786.531 null] +>> endobj +226 0 obj << +/D [2313 0 R /XYZ 85.039 699.735 null] +>> endobj +2316 0 obj << +/D [2313 0 R /XYZ 85.039 678.741 null] +>> endobj +230 0 obj << +/D [2313 0 R /XYZ 85.039 552.962 null] +>> endobj +2317 0 obj << +/D [2313 0 R /XYZ 85.039 534.09 null] +>> endobj +234 0 obj << +/D [2313 0 R /XYZ 85.039 461.332 null] +>> endobj +2318 0 obj << +/D [2313 0 R /XYZ 85.039 416.785 null] +>> endobj +238 0 obj << +/D [2313 0 R /XYZ 85.039 289.831 null] +>> endobj +2319 0 obj << +/D [2313 0 R /XYZ 85.039 260.427 null] +>> endobj +2312 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2322 0 obj << +/Length 2480 +/Filter /FlateDecode +>> +stream +xY[o~ЇPpEIvcE恒(/ +IW=!)S8˙3gyOt2b8 o\( ˋwC<7rK4W/ "ba/q8cg83_(疇n_'lyϙ]CWaea.sDrt]Ox_y  I<{$&@Zz6GixL[٘?,v).)\ݧ~qHC )PCppy*z,Z Ѹ~60̓I.skh/ĴeiHݸ},?4 +PŲжG14#+WR>gW2<͉Wć]79:&BF:r D6FAj&ցI(TLKؠ3:.X`{aH|~ǖ3V6#>agiHayol ?pϐ*ÏarܱYh`CCa]B:Ɋ-+K1l5@*.fvmt;{41| Ώ 敤7<5 '#(YΤM֤s +>{Tg279|(? G k8:7 ¥bT!jZ2#?|Ws}}a5ן4*"_f$e\ =j|:ڼ*w7l4GEzvX_ aSk߬&BnC&ԁM<(P7mia4}$yb?ʭd2`v n#3TC,Í(`%BHԙ=zMgVj/\T 51ړbE*ރc +8_Eب=]VqsWٚݎD9gEӧ0Ҩ֒\  +N@˙wF4M"'vُ#* @K\̶E#'դc+=N%ЎXBTYnNb!}Gp!g@rz1\03>eŖ5L.Za]|hOQ!lqE [r P똮GX^v^;ROQ5-)kxxK]ZkUޗ*E*}3.!d-LP<9?]#^{{n˾ XOc1\i.7-Ӳb[==)1jgxփ^>ch]H{`ru,Ҷ~!9=r4l_3V[%F=y˃\ E!CE[sk[[H*~&hkȉ-O z2ڿ5Ƿ $˷SHegy>$+Jb/ \-r#@ݏCإKA@xuSO=Entr X-ϵrY V@Mϱ^5 &Vns[c|7A/ᡓ +Yrv"endstream +endobj +2321 0 obj << +/Type /Page +/Contents 2322 0 R +/Resources 2320 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2311 0 R +>> endobj +2323 0 obj << +/D [2321 0 R /XYZ 85.039 781.388 null] +>> endobj +242 0 obj << +/D [2321 0 R /XYZ 85.039 437.555 null] +>> endobj +2324 0 obj << +/D [2321 0 R /XYZ 85.039 414.237 null] +>> endobj +246 0 obj << +/D [2321 0 R /XYZ 85.039 277.233 null] +>> endobj +2325 0 obj << +/D [2321 0 R /XYZ 85.039 258.361 null] +>> endobj +2320 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2328 0 obj << +/Length 1614 +/Filter /FlateDecode +>> +stream +xڥX[o6~bHQԥ@K:][,qQ]h[R*Ɍa}B^""ys?$)/5BKR%tzHz >R#2Z( bS82JNa$2I/&B)X{91]?@ljo[ƾ^^f^#-*&_Oafezt=uX9:Yq*) ȳ!ɲ@L/bB7%/sw5w@j;aj%yPtN +YHH&mӫq+3uŗ,vh$P *ab}͟ƩgYG :Rȷ$۞-+`˒MJ]0A3c}aU:򟡶/*U!Dm&фm3ΟO?܈77/oߊ?@6Mmn^^9Xjl:fmP7v6oa+7̔?qλS!T`b *Zl`8z([WM$>枲{ D@J9F_I#+CiO$P@K=Ru"LBU m8R1Bq3A3'7Dhq\w]@pdDzS(D;^ha*oXc8HWyD*cLo_7}=Bgk)Ty60YvPrR]9tK^r tAYAS4! +ڕw5ǣsR5oHpD \Z+H<׵)cJOW*VK}R^V9v&ê-#rg +fZqAx[WP4|2+Z((teؠA~T&%t*5\ 9\bxT=M}J"6֘{ g \~/Nw-&耤EKԼ$m9U{ٽؒ5Z?Ĵ>q_h#~>\?% Z8y^`[!!KwDqSW(ι3R9)Měq QCPE]]1Nܓij:5!:WyY"︛NwػW,++%m_V|ѐhPHL 81"J՟/{?UfL7?2]bL | Eٻ˟A8Gf)8;pWx6څ)0gOVwu m$ش0Ζ%=Ʀ> I?)-yFâA $ٜDĺo{?01t}+}>q}>"4S_H0> endobj +2329 0 obj << +/D [2327 0 R /XYZ 85.039 781.388 null] +>> endobj +250 0 obj << +/D [2327 0 R /XYZ 85.039 761.463 null] +>> endobj +2330 0 obj << +/D [2327 0 R /XYZ 85.039 671.062 null] +>> endobj +254 0 obj << +/D [2327 0 R /XYZ 85.039 627.524 null] +>> endobj +2331 0 obj << +/D [2327 0 R /XYZ 85.039 595.999 null] +>> endobj +258 0 obj << +/D [2327 0 R /XYZ 85.039 236.956 null] +>> endobj +2332 0 obj << +/D [2327 0 R /XYZ 85.039 210.81 null] +>> endobj +2326 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2335 0 obj << +/Length 2615 +/Filter /FlateDecode +>> +stream +xYKs6W\ZjrZdY;sJr%bF"=$5*hOaU&n4K$ 8T$ĝ<p(w?\Y8twa: tljs;9F3wlV/Սt/it90˻:3t@'N' +d4lNtP>="4=Y#Vϴ)?F#T|} LUFˑq('$FZ{_JHG4"^w1<4n*ڹ[m_b1hy)Wi A'ƛ\TѤW*HO{J"SKF@rBYNg @-4ZD}znĹ@#S W5%ZS]m+ki=%NϳDz\Jϱ{2;L6FؘF"x*?Ri3ZosGxmWi8~A'c˅!|7fQRbW_ ac6gԋASb 7y4>H? GaJ +-OylMnhк9MJ,L>] h# UͭVO"*ЮڹK{-0vf.PB)qޡJZs_wO? "axV!{:lnRj{qOXI쩗9`0/] YoʼST$BSf\ZM٣0.ΥQسBIcS{U5m/jG*.U\V(m%j|-pFbغk>,7pk{l.64IC^W]4SXr_7&#7ս). ᐟ1JXܥ=xv~>9aF! 떀Ӱ } &*<%vqou/Dp%X? Fg Tz,4ڧ<ԍW|YP2(Z3+g2PR,+lZAu !;˴f&8H'Z""3 ]䨫;^G +2+ifQKsC0l) ֢QjiT~Ý G5{:Iymm8ɔźȇeK(HQR0 +m'Ba֎b4,^sq(%_!_ZHlj}pAhCVa!P?lRy7B_ szxU!_0qbgj+>c1lrpԋ` ;S9}[V?UT,dk⽠p4R4bn5Ȑ$w4ZR1 E tOrⱛM3bB8툠+Pt*[.Dp屳E})E +1c'8M\#}&Epz2r i0fگ͙s+ OV @RHyTݨ*E[!Ec^+ 6uxqNٻ)Xy N"~4u(:sjBkQ冮ޤ7OYzaQU 7xCG!Х#@k"0huwSj 50p!T:F(z9V]BrowKqJQ3UC pD;= +Tޅ/X%qpuI@ۂKt6`^U6u5D㐻-1yT@_0JP~DMT7'뗍#yWiTD4^t%y!.R ц/T;IH/tt)": +%GH9c̋!\Zt"OepWgh=^ +t\2TLh nZnqM +T*βhUYR +c_.T{7>d/}im+BAo‡a6Ɋ>U_ !%#(K]E1dɫ!N7IwӔN* pkpmT)/M|^&,ǣ> endobj +2337 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [489.95 435.981 512.306 447.67] +/Subtype /Link +/A << /S /GoTo /D (ads-test-smbclient) >> +>> endobj +2338 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [111.316 422.432 183.828 434.121] +/Subtype /Link +/A << /S /GoTo /D (ads-test-smbclient) >> +>> endobj +2339 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [214.276 422.432 356.796 434.121] +/Subtype /Link +/A << /S /GoTo /D (ads-create-machine-account) >> +>> endobj +2340 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [380.57 422.432 476.48 434.121] +/Subtype /Link +/A << /S /GoTo /D (ads-test-server) >> +>> endobj +2336 0 obj << +/D [2334 0 R /XYZ 85.039 781.388 null] +>> endobj +262 0 obj << +/D [2334 0 R /XYZ 85.039 393.439 null] +>> endobj +2341 0 obj << +/D [2334 0 R /XYZ 85.039 364.035 null] +>> endobj +266 0 obj << +/D [2334 0 R /XYZ 85.039 274.847 null] +>> endobj +2342 0 obj << +/D [2334 0 R /XYZ 85.039 253.854 null] +>> endobj +270 0 obj << +/D [2334 0 R /XYZ 85.039 135.198 null] +>> endobj +2343 0 obj << +/D [2334 0 R /XYZ 85.039 103.673 null] +>> endobj +2333 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2347 0 obj << +/Length 1224 +/Filter /FlateDecode +>> +stream +xڽWKoFWUQn)-M;m(hKJRq;)-t<]@OBAH$oG"XǑ;D`,.g7"HS2[|fW?]<4,06Kvqsy\.U[N{>\ 0.ǡd@|}]zH?>\0\I2MXͭ~MGtj H5j×v %8o4[Qj 0% j)E-n6fx(`t{L›wFLr'yv4Nq>tTYn4: +ذljf՞mb wMR ȯV+狗^*+:%V&uv ǣݓߨ,ը +v< ]]C.*4_i$KGcg<RLl%n/6~DnI{ݽ7g+41FQ w)' k9*2Z;EWt4`ٲq&Rp +Zx w}zŒ$>JHTB\CpxJjIg' +O^^~A\$P!Tc +Mo[(/d)iH%Ġ=t%3l<+'K*mIWVl뻌%E^ +;x}jUx}JˏgUc߁ރT5Ce&\YC'SvlRnxTio};T/ov  6B +F[T%yJug sjb1]eJ, ɫ=^ȭ3ŋp#5s%&2)S,@b[Xn!wpxNume{+(6  +ywMvޏ82.VJ;в8"T~:L1Rwry*gqӠ%0rvv? WV zF"~l3#ԅ_@vIOP\c~dD@T~5ڹ^)>E113ɽۆp7 9sݰ9QĂ:u mTZ@/f}!nt  Q?Go7X=Fb:so(endstream +endobj +2346 0 obj << +/Type /Page +/Contents 2347 0 R +/Resources 2345 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2311 0 R +>> endobj +2348 0 obj << +/D [2346 0 R /XYZ 85.039 781.388 null] +>> endobj +274 0 obj << +/D [2346 0 R /XYZ 85.039 693.417 null] +>> endobj +2344 0 obj << +/D [2346 0 R /XYZ 85.039 661.892 null] +>> endobj +278 0 obj << +/D [2346 0 R /XYZ 85.039 607.594 null] +>> endobj +2349 0 obj << +/D [2346 0 R /XYZ 85.039 578.859 null] +>> endobj +2345 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2352 0 obj << +/Length 2458 +/Filter /FlateDecode +>> +stream +xYIoFWf4U Gv`X ,A&R7͘@ۊmɘˠU[ZSgi:;KR4=T/B ɵ]ǡd&L0gY@o_zgaDZ>%o^QxWZ)Ʈ:N<7{yZ+Xҁ"Uآ^~`&b: V^"ףd3%p;k *3R+kϥV(ɼ3Q;fy.q. +{%=6yXi0{'p8q!1ݢ`DӳȀ!e"?p ɧ8ZR<:È׏Oċ,yQeQ@$F q]ܠy!CYk>Ǿ gT9'"45iuWۭJOO:6mBI cؓp^`h_Z{4g4*/?YAFKw{heגGY֤)_u|_12a_IqTun{. 2{E! fV9ⶅt4P3t 9Hmҹ4@鋚R_H"[Lzi8;>CAYmx1a"~;}us=3b=>՜( .* C(! Ua9pr﶑=@iY:GCwq l?\ dfyGeӶ[n lS}sz(PZFT7щPel jBD&H®#ldpEay?kB Fzm -&KSAN;JNmfM r8dGNڰǶMYc#ޖXma@rD2ďdTv#lҐ_p 62&}: hp9i%"x/໔IAcQK"(bc ++e.'Wtw^Pcj= 9KHj}r :k+ބ#*.F<,zWQB!R*My9/qz^+O h!2;:uHrb:^ +)ؠx[ܢ "a~!H2&N8xة\Fv{l T=6\; E;m6fK:ȍ-go,W[r )#+}{|;ڐ[^i("/HAaį54P6;'4g/H4 &ŒF;A6 \:V$ =8s gXX:Y dhRB$|d Ԭ>0&TLtCH[ȗ8=8П::ta R٨d&v.|{8*$t,>bj___//e%_.s]2>4sNZ(_m)V&d6Z:?TFc0~ͷ>'@.C0J)f  *+ +Յ?gfPD:gn*_'3HdaevaMpendstream +endobj +2351 0 obj << +/Type /Page +/Contents 2352 0 R +/Resources 2350 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2360 0 R +/Annots [ 2355 0 R 2356 0 R 2357 0 R 2358 0 R 2359 0 R ] +>> endobj +2355 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [230.917 454.294 282.431 467.195] +/Subtype/Link/A<> +>> endobj +2356 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [203.74 413.646 268.218 426.548] +/Subtype/Link/A<> +>> endobj +2357 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [289.289 373.301 378.732 385.294] +/Subtype/Link/A<> +>> endobj +2358 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [250.286 345.9 339.521 358.802] +/Subtype/Link/A<> +>> endobj +2359 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [285.619 61.367 316.703 74.268] +/Subtype/Link/A<> +>> endobj +2353 0 obj << +/D [2351 0 R /XYZ 85.039 781.388 null] +>> endobj +282 0 obj << +/D [2351 0 R /XYZ 85.039 761.463 null] +>> endobj +2278 0 obj << +/D [2351 0 R /XYZ 85.039 646.155 null] +>> endobj +286 0 obj << +/D [2351 0 R /XYZ 85.039 646.155 null] +>> endobj +2354 0 obj << +/D [2351 0 R /XYZ 85.039 614.63 null] +>> endobj +2350 0 obj << +/Font << /F20 1617 0 R /F65 2099 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2363 0 obj << +/Length 3269 +/Filter /FlateDecode +>> +stream +xڥZoBThr*p(8w].pw(JBRqܿ%)R Zwfgg~̇j8Q^$Ÿa %x~һ#=SH_Çϗ wd~oo߽Y3{z.w?~G\W?ۛ;~p  >_Ň (@I\?0?^^&gJ„@s[Xzha^N(aS6 燺\x O+p ])x)ů:TpWl7^ky_aY׼}e9Y[V (} +- zJmH-UI=jϿ` ʁC>UNsNpe4cTPĚU]q$zcNSw-x=MWъ as+h*ۯe_$w {TH!.[@ZA2僄<5+ -hb9w-p&YCGzƃVusZ&IɈ>!2Gz>+?lـ% XMFG'<[Y_־L&dfKXuyX-]lc' 0-daSEUMfVF{ulmʶWpevu˯xWM|; s;==++]Z ͊jD u*{+b,^n3gp5D07YAEV*K| XabKonvuKM pBށDl-ۘEDg\ B催V0* ط<$Llvщzyl9(΂l  je5mV$ CNL=̤ E3^x\)ɲeβ]fek |ՙDsVb)IA K? T +!S +AǞ$\ʠax)Cit7xQ.Ӑ"!&h8T3Vb8\BW,BLy{qðy-7E]~h%6G 6ځRMLk;bq#v95e%%kpi̾/vS1IƏdR9gb wbCkp c&ɬa"=-;B~:64GK4&D` l6eluy $KfIl4$+ d {IW}ZlYڴ8Q.xң3ڪkxZy\8و+u̍zgq=SA^zZQ]x'X|ϔ +e2Jt}-;4§9ҬuT4dH3)0M*Ъ 0,39xFb"6O%a~oő|s (ǦWue$.5酎#uMp DbQLDyy.M +b#{Xd$q/ؤE,y0.- L5M+ʰX 7~]\Sg  +$qQwqм(Mlgx>\J+Xb3CV/2>kv%4Ůr#Q:u')8wx)ynR ] +aDl¨kQq`͸RjY[ Vz1'SSjBB:hFdJ6YïsCHJw f)} 3z<)(ʑBGw"m +XD# 6@ExŪ-+)ik_}995Clwë`L)M;_|z +Yn΃L& +A\vtl劫BP%][d3lc5%m0^VI{kӬ3\}䓍@ I@F(ig+ 5$ۚa|P䮶;qm錟|r&p3,3ʂ,HSNGA/~T YH6s2/JԫmZ7]8OgIAomI`=0U ޑSX[sYU/ L0&F~Dg|؆GDBEWİͱ*Q`4f_fMK4quS +$uB2zڐLFB[ -}~_wm 산 Zomc Vv儹uO4C:h_LioԜCjjrta2ň\Npg;:Y?u8S#$_}fiU^Tssp?:%]@mkY +ҙw9^47cFg @)endstream +endobj +2362 0 obj << +/Type /Page +/Contents 2363 0 R +/Resources 2361 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2360 0 R +/Annots [ 2366 0 R 2367 0 R 2368 0 R 2369 0 R ] +>> endobj +2366 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [262.823 498.973 345.582 510.663] +/Subtype/Link/A<> +>> endobj +2367 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [215.436 458.326 289.861 470.015] +/Subtype/Link/A<> +>> endobj +2368 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [201.985 140.627 255.917 153.528] +/Subtype/Link/A<> +>> endobj +2369 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [319.668 140.627 442.172 153.528] +/Subtype/Link/A<> +>> endobj +2364 0 obj << +/D [2362 0 R /XYZ 85.039 781.388 null] +>> endobj +290 0 obj << +/D [2362 0 R /XYZ 85.039 596.451 null] +>> endobj +2365 0 obj << +/D [2362 0 R /XYZ 85.039 567.047 null] +>> endobj +2361 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2372 0 obj << +/Length 234 +/Filter /FlateDecode +>> +stream +xmPN1 +2&C$g&lpꕊTJ NbdPI,AĬ>;4E:e Ũ菨 P^9QnjwuhZQ~ӡ;Bܺ}\tBaVy+mZdlNHqjavj]vZ;Y2:/0$>C/Yz[ʇ)B(XrVm|~cސ\endstream +endobj +2371 0 obj << +/Type /Page +/Contents 2372 0 R +/Resources 2370 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2360 0 R +>> endobj +2373 0 obj << +/D [2371 0 R /XYZ 85.039 781.388 null] +>> endobj +294 0 obj << +/D [2371 0 R /XYZ 85.039 542.44 null] +>> endobj +2370 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2376 0 obj << +/Length 2209 +/Filter /FlateDecode +>> +stream +xYo6_ZI}Kq۽)b mh[H+Iw>HI EKh8$7B^ʽ42o[/Bo=?,*Ε]%2tnL*o% i{z2 DyGrǡ7zRI'`3P6;TY!3 +lVOZ=-]KZ#l,dJXiW֣&Y-]uAW{"N>u}(qQ* ڰtD,eЈ.%%ChW&w<<ֺ/a]e Uuyԝ]oG>a3rຽKa@Izgi ^:RGmkcӸ5zۥcY72-75ٰE;iy_8t3w+G+f[GECĆƤ>>^Sqo ZˠO|T6=3FȦ}aZsYw j1wVTz&{ᾈK)>/&α`^U ?@~*[w\ +ߎ,e2M'+ Dk!~;nq_|3Չ4eIH`|A$g a ܫ*΃8OlZ/;2ʡY!a ?CԐ1RA2f;FCuJ!$Ev:N"m-O䍻Ry a(aL"Id?c L98F$/0dE.ҕFe +WOٿD·é_BOmQ=q͑Nv$0wer3#M)pejݗ%WyF|t{7UWa;,-1Xh +ڐ;tDp8֐{lpޏlTt:D4 M; 7\t +] f!ம9lZt e WH>G)7 `󭗄V<Bysz{(݃F7Q9|. +'̲HwLh߾|>CBBñe 5RAxss5 +aC|Ajg({@sݥ9`R)]IQ +5q)Y3lw'R")q"aF-Cwp^Do?Lq>ź`sK#yA7߫eyJ{MCΎXJx V"cbj}ГN^t_< A2 _V \%d3dÌD +_a(-bvf*b(\CctzW!1D^ER@> endobj +2377 0 obj << +/D [2375 0 R /XYZ 85.039 781.388 null] +>> endobj +2378 0 obj << +/D [2375 0 R /XYZ 85.039 761.463 null] +>> endobj +298 0 obj << +/D [2375 0 R /XYZ 85.039 761.463 null] +>> endobj +2379 0 obj << +/D [2375 0 R /XYZ 85.039 642.137 null] +>> endobj +302 0 obj << +/D [2375 0 R /XYZ 85.039 399.889 null] +>> endobj +2380 0 obj << +/D [2375 0 R /XYZ 85.039 375.338 null] +>> endobj +2374 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2383 0 obj << +/Length 2630 +/Filter /FlateDecode +>> +stream +xڥr6_Rxaskiʵ䁖h1-IYoMFõ1SzUq<[Wl +_f.] LxlL(o~_}~/Rv(\8n? wym.cq wW8+h87w_ͧ?V\}^ x\*d?W6p_unxZ$ l kj $*<ÝS]5ʹ%p_%m-MnBF.) CU۴ULc#WbewR'IUo}v=0#kEHzzr1:0wy﫺=np^1i^zHE>pj* =j~"w1&5SR#9#rC٣LH8 @ +Yx))scη+X(9~zguʃvgUI\h̋ +$`=Z^;TEADo?c7OpGC@b|i0lL'|  |;YP%oʞPV-db'(_=3 nО4йi|=FuDWz,yԴpS7k')b +v2KWT|O;n,d%at׮Dk o!CӠHA ޏpH+ʗڢEc 7<$XyZ@ K58'7z!-/e)i:CdN{{߽[B,!3vgME ߹ֈ[)8TJC- +܂8ۓ=/C +:*'Yϭ1\jwE+_>w^|[2^vnvY&"[iO G"\ iN!OZ(B/*{˭=2y>Z~b $ k^X\tosa0J:©x{Bs+zKCh`-.ϖY$Έ0';ԉΤ]P_V6[P0ȑTLlxu)uU>O +LEt_q \s*55e7JGVz` pxte +  ` u䄩>R.Y S(IqU6.-z@P3 8#xG^W7uܥb城I1Oe2tq-iCIHqFS9 HD/Eu4C,Aա +\<r4;ȱ]AN yQ{'Bݰf7o!vo LE^M-6eh:-y?s}aW`7O{X GUtRmi:NĂ\}[Ntu{ (Lͫ~+\9}t ?ƾ`T[]bC-hmLGK-UCSӿ] ҅p Z?:eZJ7endstream +endobj +2382 0 obj << +/Type /Page +/Contents 2383 0 R +/Resources 2381 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2360 0 R +>> endobj +2384 0 obj << +/D [2382 0 R /XYZ 85.039 781.388 null] +>> endobj +306 0 obj << +/D [2382 0 R /XYZ 85.039 408.357 null] +>> endobj +2385 0 obj << +/D [2382 0 R /XYZ 85.039 381.742 null] +>> endobj +2381 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2388 0 obj << +/Length 3839 +/Filter /FlateDecode +>> +stream +xڥZKsFWʂ {c'Q6R>$9 I +UR0~}p_?P"C_b} ;&"47oHEEP,4qO~}V)6raz>;?=7rw|ϿFUsw#݇˿xqȿo+Xl?*3?,&NJ*/xUQGTyl$Lfdv@ry]9U4 * J^_v_P =y\F٤27J!j؃ +þltiIdەvqy]aҬya0Ul/U ]q-nCbRLkS.g/R?$-Gy Tt-+h{f$몗klnkV롂{kZ袋eB_ K=v=Q Xd_xŭP@j[וY +Imteg0R5݈2L2~Y*rfa tb@rxHQ6p1 ٝ:#b2'Lpo/hȋ8P^;v'GȗvBe&tRF"ae kvP.4(])[Y gz֑hdS+:^\pwrPvyCY#11rLO\_$5dYy26{ܹ5[cCUֲڌKaqh*/~gԸ 6n2-iePn 32+"轗ŶDX֗$`ySTbKw99r'nH-zF%ܻd(CmXȱك)t@pL>E)2]G7`RUr<^9ʄ +DjS7ï<ݻuQǸb&56Zr03#XMI$1PTΦ0&X[3GQ 16O 2f +NEL8r6B-JƣkGE"nC >he''}| bhki*kiٚpu)D{jg'ҋ.Z6Ƽʹ%bm~ DAjW@5t!Xk1ÁN=HeFY*Hk[3 +z5 rn !t7[#Y#J|@*τcIV_зI"R d\`Ꮶ E3ѩ c5F$ D b0QBudTH c^'CKxr1f@r.!}#3.Z9Pw{j̥MgETTaSU>a:#1h ,B);r0H6DL^,v՟t@pZsɉaCZv$^ ډ{]OH5o9cWH̒ 9rE jnBRXuW Wo EzS3Qe[Q,Bk]<'dL"D6R, d "I/BB o"hYaAWy`@6%RIdԻ @g)ΧD.~mL8 ȗLE2`el  DCd,bIJ3V=(w3 q:}蹍8N&cJjn愞8˖v8H;:m+12(*k"钓_Ohn;̴b0#6ic$\5͎&NMqc%eM.WRyÑMɝ37foAe\阐j o"Q[(VNG3fgׁU iFPq3WAmd)/S&8(j3hWZܽ k #ce(X5 9 >ۤ8"(VAsռ!%_r9}L}?y̝ +(%i:dU^Xt6H +G{0f{185|A4th]B}!6?k(EzEjg2^,gú%g]KBVXO6aGk2g`ϚI +2U.klv3x;/KXY(FҞ\)%ZS)^PwM{DS7kAj iL +P L +h\2/a ;^G`"ɔ+4E(g(G~Lx.F7i]Jv*wߌa%x9amY3&U8 avc`,P@%H !"t׎|G,2%f,%yN tJf2#>B˚<%γ*"=lIQ2yel~qֿ 'h#fTLʎa81φ4φg!?Pј2`:SLPBoS6Kο%2򨦿Qe[u5*(gPq&Ø9QլP&(ɘZh+UdV WǤE@) + `r: -H䇯uO3fykPؤd;nH ̂cVZu&#?yce|Ja&m&h >NB Γ^nMZnZQ&]O F!Q78Sp +bʘ%<.endstream +endobj +2387 0 obj << +/Type /Page +/Contents 2388 0 R +/Resources 2386 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2360 0 R +>> endobj +2389 0 obj << +/D [2387 0 R /XYZ 85.039 781.388 null] +>> endobj +310 0 obj << +/D [2387 0 R /XYZ 85.039 610.001 null] +>> endobj +2390 0 obj << +/D [2387 0 R /XYZ 85.039 580.597 null] +>> endobj +2386 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2393 0 obj << +/Length 2682 +/Filter /FlateDecode +>> +stream +x]o6=o'"Q> +nK%.rvd[T|by +Dp8|,pi?Y~e,Y(,D#Dσ|b_o>-ϣ(r~w;7޾Ah]0-~wwu}q2w8x Дi3W_?[ d<8P> fk8g Ɓlwq$ߎ X%Ja~NB=q'ASos{د2MSՀzFhU0a{En #hG rd^̺)[a #25K-W׶@f+ +t܇h .{l cou= +X cVWfMhX<)^RB%~QviIG)h/kM[__׹Ⅸ8LR\Z ##ixeU{=IQH~b [5U~oʙ1'w16`XylOHFCGG;ZŐ R"E$[o=p?!Aue :m+UR+!"v"oQ0VB|sb2{{zKC͢2,,VH<_盪YdCK37:M7Cz||-":߈lAʒه雽r !B/c][{yZ{(R0o17%41n)@쿜d3R'mQdA>&0$&rsLڑ.w#5eziǕf0%2Kih6ƠȄ-t1kok < tl!7=TH(vn,O/g?FbxvD>|uNW}Ƭ. - GaG>B qq)rNVl_"~w<9.&g`LNӽ?|endstream -endobj -1558 0 obj<>/XObject<<>>>>>>endobj -1559 0 obj<>stream -xW]o9|h@o^z -0P3ŘNH"9w6A["旣g!'L|:ӳ驜^ZG?-fWXr-g粬sYVǪe:[^u͓{ V־:Ht7ZVzW;7<>zWL0}|4RYTv?Jq6IZM9ˏ9i>BDTZSh\3{jiյaҺCMʲLJO!bmxp}w93 ӝVk^|MԢdsFrⲰ_*J| @I}kfz^oSY5;DdԧܘPԧUfx{BRR`U!^WUVU!1Vcw@% [ML=.$h]Z8oײ6!q` -,}Ivj*1_a&D U'ꪋje-8uϬYXYmRT/SCV Y`K!A뛟%[-hHyX$9zp4^ ->jfZ+A;XJH@JrkcNYj z)"Η蠐/Ѡ9&2t\w ,FcA$Zq n-Ϥ~h$-r5PmL67´Y>jܠ*d_jm+Y) p7Ti ܲFZ,Ӂ[u},:VSP'ή~L;yS^hX*v \pR(R|0j2=ߠ՛3)S{֫r[ȏ_ܳW^)Kss'xLˍ; {Pim!/]_8 *&?A˶ͥ7 -Xn}`.,pZ{BG4X.)u,FYW 0o 0 >~|ňb?HwB:5hi$k$1 't6Fn,񁟲nޱ.Kz (`5Af]:O%9NdQzh D 61og36 ޞYJM,u@z$Jl`@`#ɠ3lH,޿g0fsnL*pvC#ibr]n8 ^rtݶ?kQ_t[ۅ-jSp ITi?zovSm04 0(wORrȾRo0[%cjamEbhOv9f50?gAi9ykth%D -Liͣol2vܤ i=/WFo @,n#tqĨʩ -|vD4ZFx6;Piڅv+-@TCV`믵cJ>4CiFdAp -R )`7aR>=T]L/4}rnzVEtl9NAxȃ{vB!:\fi:aߣcXHύٕz~ N37^Edt^iÊԊ'MB+6`@(}WyPzс vP]OH X Vzaaɻa< +Gǔq!?H| }P>p[\\Lrr 26e(%[?x#g?Ky:N V>7LxV'2ilyz~:=?PϘˣߏ endstream -endobj -1560 0 obj<>/XObject<<>>>>>>endobj -1561 0 obj<>stream -xWr6}Wl3~h21Q?ӫ(h:k%‹A?_F4| 39>uw6{(D -%UNfd4}V:3[׽̕ޝ3oJ2+43_V2E+G~#"3Ky<9SwpYh8Nq2 v2Z,sÕܸ[V!-ҘrygTPz{[coAG >&( iJ:*_AdpFQT`JQ\BiP:pA ׋cN0u8:A7 ¡ pHȦD #IA5yT .5"_pGUp6B!Vf![z*E4t'qKۺ0UH;Ơ8xsIQܛZ)Xq!S]Bu7+P=\V' $2 ; z÷|+jp*bCϣOV }#Q>wj).˲5 y=6)عuɔC s΂}c?xa*OF -[|@*­,3EMfyCtlkvҷ*8 3@7M$`q -<@F.W -L4Z%x6 -O] }1-86 <Z!tAP7VYZ`gV11 b>Qڙ -${,2l -l`9Hqt'_ֹY&~2N_\ANG[B9g=۟.OEIZ MP_=v@8p<(<wN=^{NKT/29eUu D[`pgEW?Uy$֘ӯ z>񞍓iDɍ]M믂_S|ּ?n$f&xf+endstream -endobj -1562 0 obj<>/XObject<<>>>>/Annots 816 0 R>>endobj -1563 0 obj<>stream -xXmSH* nQёܗ*Iw;?v'q/soA@]4QHQv4w #_-h qyb!A1x̨ {4{ݞ4V?~ß{G ݢ;Zc>h`qc x#[n]F=>(8: -pnlqЙv+Tn8/KQKa -RO;Iuz%ΌqZ1)`0?۾I!(M`wJ|3P8l Ld$H<:`M@ $*e]RZ[P8{FqXVi0E%^Fw&ԢMyȧs4py-9{y.O62̄isbMbV*MZ;S1Adze1o0w:;n}n?ևL.}ϟ&?qYm0σt" |*2jUl -&@ tH02SyseN&*Z8: -F5u9cB :wGh) -e*1, gU.eT2Qqy% ś=!\ҏ$w{ ʺ4[01]#~{1WsvD[⥀|2v]}w>/XObject<<>>>>>>endobj -1565 0 obj<>stream -xXmoH_1*T@JhsJ phx]{~=ADN*"wy晙u~dM *urGaQau6Oizt1<2;UmNql#l,dH>/|Hd~$ɂI_391 X(J0b> 3?OC6 Eeb80_*ZZ8QFlMq_[e 1tg$}HE(ՈO쑏?E88A|p{Bh99(spX0"=ĦDbB,Xb[=:1bxTHM᤹"hVOc[:u.XhY$9TiU@X0+BV1Qsz zLx Ȳz͊OhUԔ d`- -B ÉEDÚZ&Βy^2(/-'3A+660aQ#&֋}@ SD!uny} G`&>/XObject<<>>>>>>endobj -1567 0 obj<>stream -xXmoF_1I $*HsR"^.>l/ٵM kNתz晷gfrd65bi䴌&5;m<ĜGӣzߤS.G8l4eUŸy#?Jxp'unmr 4 ̕Iyn( -]<ǓQ|G&,@GӻFHaspm*ٴ۴[E>9>Mitiؽz]_&ѐBwG`{(Nsf*M8_ܸ.WBud= W,vI,dh%i01hV2Z \~R pn3p^Cw{p:1n7exYղe8UqYVDzÇ߉ktq54J@8MȚNh[~Eֵ:#; |ֻoΦRmϪftc96 F2uj۠êra9Fwk< wQ-SqA18Ve3mE,C7(^1}F(Y0u_ p .DFȑI nblÜ6i'Ne =%pO17"(K0ɥv]&7EOXu=1MX쯒pF"DZD|"1<@b++cUL,SdX30 Ҽ,X4S*iH]~' o 9 uiEO7]*`iQXӇ2VPkꇇ4ȇjttjz_mendstream -endobj -1568 0 obj<>/XObject<<>>>>>>endobj -1569 0 obj<>stream -xV[o0~W/TjB2@i"H'^Lb$lStjIdɎ;5|]h_e v+pOBc;Q\wvdž(gz)a< .hZmx%+02$ 3%|iH2*Pȧ6,ZslMXݩnf 4AJ$I素d30b u?p̨B$A{V4t?@J*ρշ c-*7%bQ˵ջ} (Bo/ POήރ>hE= Μxni=;?:~{ۈ\+"yNbnך(^tAp?6QD{5=[뫌Dp -N2eeIX2VAzHhIqr0<$\]ʥ1++'YHE( s +B§:4B7&q`ʧ_D| Yfǧ?v?)C^np6q5PY%|%J#VIz\T4{ߴЇ f~ðԏs0 W"9{E-<=hBr~\s/d8:AZD0p89UyӦ sµ_~_c vB /endstream +endobj +2392 0 obj << +/Type /Page +/Contents 2393 0 R +/Resources 2391 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +>> endobj +2394 0 obj << +/D [2392 0 R /XYZ 85.039 781.388 null] +>> endobj +314 0 obj << +/D [2392 0 R /XYZ 85.039 720.013 null] +>> endobj +2395 0 obj << +/D [2392 0 R /XYZ 85.039 698.816 null] +>> endobj +2391 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2399 0 obj << +/Length 2431 +/Filter /FlateDecode +>> +stream +xY[sۺ~#51$.t'NӉ!'Dj(%x7@DgL`w,vx_~=BgGhGa͙:FK:>yf£FL13 5`0ˌIlGlrs<vtp_`'+bf 7bKEvsֱz6E 2`! +0ɢE-[d&hv;oiREKv%oa㼰enYB]z SU"9&)6hy+͆٢5u ;4" HwMAN?{j{:M#V@ Dc7_5UŖHG2hoM{EҺf06RMD8Է:/,<;8EhfuO0ѩ^--MF#H424yHl6*txr,j?u3b!ol <>F\x?^UF=8”aWfan, ^NeaIUYQF28܅2˞`,u:3K숑f 1 Rbm/6(R͒⧟cF1'Lnin +a1ņt_y l Bf~&$zܮ/z(Q:LSt$ +((ʟS(jaRQVl+ъFp,8pUU Q}.j/cRM|_o&xՠ +b#ފLP3 +!ȴ:bw8FKRYdr +S}bb[M&K]$!IP"K*A\ DF3*)jTi`In)2D{ `9;~dm@tٚ\+ruTDEI&)4TX?[@|D_FUCRI/UQ=s,΃KbɏH8)Up^4mEYA< }mZ*niSr۽9[wRȤf;)_-IQzā ls7`$0}FGdJ8#U8_Ws_)-w$T˪_|bF0;cSz"Wz4ia҈\(_2+٪ժ}dHkPl,Oc: +UGx{1;~C) OT4ir5S GC2J:?@$ #IkDJW=Lv{/#JL!s+}KE%[6L+HD_`$5Cv\5c N63v0 S;cbʗTJIr? ~[f yrxg77Aw1@n鍅Dfxlgeq*rYqE65pdYš$,L܂ͮZ +sXƀa_f'(lGpYGsW/?x}0)-kR.z!Jirj1hWMoIRR<ov/oP=4):$@@]aOa(iGH21NYBendstream +endobj +2398 0 obj << +/Type /Page +/Contents 2399 0 R +/Resources 2397 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +/Annots [ 2402 0 R 2403 0 R ] +>> endobj +2402 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [354.867 309.434 512.306 321.124] +/Subtype /Link +/A << /S /GoTo /D (browse-force-master) >> +>> endobj +2403 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [111.316 298.006 150.096 307.575] +/Subtype /Link +/A << /S /GoTo /D (browse-force-master) >> +>> endobj +2400 0 obj << +/D [2398 0 R /XYZ 85.039 781.388 null] +>> endobj +318 0 obj << +/D [2398 0 R /XYZ 85.039 614.89 null] +>> endobj +2401 0 obj << +/D [2398 0 R /XYZ 85.039 591.572 null] +>> endobj +322 0 obj << +/D [2398 0 R /XYZ 85.039 136.291 null] +>> endobj +2404 0 obj << +/D [2398 0 R /XYZ 85.039 112.973 null] +>> endobj +2397 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2407 0 obj << +/Length 3603 +/Filter /FlateDecode +>> +stream +xZ[s~pRzxL&u2NZ%v)!u{nAr;M:1w.P|_|'a,C痫Et.b.M 6,/}8 +\>rS?W uPW,˃8x=RM?Ww|Ryp wXßpU;~7~^~aqaBj\/?]a_D.(Ga\ 01Z(f.׌(&NB X(sd'32}ZeWA{ V=r_Xruh-"j֛j5m%<c2h_yC6Ie>Ŷ8f _t{L6fw4#LZ6, +U19Ż;%u_uc +yLA@9f7!tqCB)T:Vxۦq`8Zǣ6L*<9]ִ+HY;&Yz㩧 Yl*Ihh2*bՈXb#RrM[kVנuKEpn@MzP +`9* hiY=}#@J@FpsփP ;sG! t",Љ~ +T3)&YidQlc-}`ҹ Oˡa\JRwt86RMiS(3z;T1͠[ <u,,T<Ma(èG70aSEG7 1*I6[A;_$C=+K<#*yeAuMt)c_ɷ}Q]d@wPTMv%{J=vŽgArAs54[R2yy@v>u`xnw`iH 0NX eU6t=`jq#aih/ޱO"HT)̗$fnc zn9;w'<^ tZ" ž*3U +ۜf~W7$bE435 jqGGmK͜S+ N$ l"i;.2x1B7{[!MJ?&!G/=+qapפ[$Rp@+N#\*f)֛`%n Cl;w"K?,3(wσ; c͋V˾-h>mP[:J02:F.yڜdc3KÛ,9E_ԵYD3g6;Q8!^\ȁ{ |9LCMF9ęg 8*`q +rco0<(8X"3~_$(eR6'LY"p +I;=`)GoO(4 5&i\ ]:q;OYA`sDSIDž;/q@fR;[& au +|3xh;HXm[Y*PlIt#D5ac>f.iPe&w)Cm1XOa(3v4t}(NK&P{ڥ7 +<{;I2NcGT܅ i@=kÔzrR ZiZ]̆v +/l0g4 +NItsE,|dLn%=BĐ$. sPuXHJXy ֨a,8dŏ3Na:wi*?g9z.+03IV$ sRnn^ysꩤur(%댲4LN9"Mv7CvWo6%DziL.{4[ +RyHy. +d0vp'7] n9h(h˔Ζtb)[2^4e*"TnmB[>dL( KMr˜=)aoj'G(~vZGR,,GոY^r= `e~HϹ˴゙,K%֛-?O9r5X.~BŽ+T--[NC$)H9q6Eo0Tx9pХFA9iF + yq+=Nc"m--l:9ZNz|bMZ\;߳9{M1Xٓ$L[]I6ƹD,O `铞 (?Os-zI,ڊ22ҘTr&FSg^'Y>`6GՈ{\3ʃYJn[l? 1>Oe9^:4iU Iɳ{\ŜL +Ozƺd1BGX\lYVV~ +]5x n?KQY 0NZK{N3P #UE5zMM|vOE$u:"I̹b˃"7s$a)-k>{ JþDh+,dL,jf"W7 T@@hNs' %g,4҄ڈ'{]W%#r|ă!k7VHZ@z'\.}5A hj|}]g;zLFxK6HaX>*΅s~K78'f"U 0No^)N䉧_endstream +endobj +2406 0 obj << +/Type /Page +/Contents 2407 0 R +/Resources 2405 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +>> endobj +2408 0 obj << +/D [2406 0 R /XYZ 85.039 781.388 null] +>> endobj +326 0 obj << +/D [2406 0 R /XYZ 85.039 437.34 null] +>> endobj +2409 0 obj << +/D [2406 0 R /XYZ 85.039 414.022 null] +>> endobj +2410 0 obj << +/D [2406 0 R /XYZ 85.039 204.486 null] +>> endobj +2411 0 obj << +/D [2406 0 R /XYZ 85.039 168.809 null] +>> endobj +2412 0 obj << +/D [2406 0 R /XYZ 85.039 93.031 null] +>> endobj +2405 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2415 0 obj << +/Length 2742 +/Filter /FlateDecode +>> +stream +xڵko8{~_*5+X>4^MKRn?(b %$_ eٖ.E*r!O+BD +$$at;‘adqݯPa:-7o?͇Dkb<${/_Wg\U^Ň[_^}bMyG~zˇN>ha"Dp4wv +&GBhubh7_\;̈X11**E=R x- =OHIVk_:q㉊ tYΧ &N ξ&8Vc-&]fcʃaK! ;~wCTHsU1z{_*p f*!DH!CjO@?Qh}GS%bb +yܵ}JבqX۫ "m!Sxˉ>h\i\͝derW,*"w]%~M"iȨ)gA~U6BtGj5QDWXu +D;Hgzb7t[5mW{Q !Pr U4O<̺O}v.})*9,3n U.pl>)8/VWW#+m\/7\ 0K>̦e 8P"M_v*Dr> N1_o-ǝ|z9\g]υ%O:^x #nLB(ysY9ۺm"0qGK,B`Z^qo#;?8t"a^Ҍxx7#юZW%hl/S>̍T"xUdңrTTϽ[GJ^3Uܸ@MY +]at.v\Sóh+7 -cwl;/wcZ>ls(//>܏o(SI?fDWf`fSsoWpDeuεXKm $dƅsK<@sӼE?g +S~ &$aѼI MA!=ȎJm:=늬r7w*endstream +endobj +2414 0 obj << +/Type /Page +/Contents 2415 0 R +/Resources 2413 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +>> endobj +2416 0 obj << +/D [2414 0 R /XYZ 85.039 781.388 null] +>> endobj +2417 0 obj << +/D [2414 0 R /XYZ 85.039 761.463 null] +>> endobj +330 0 obj << +/D [2414 0 R /XYZ 85.039 692.86 null] +>> endobj +2418 0 obj << +/D [2414 0 R /XYZ 85.039 673.988 null] +>> endobj +334 0 obj << +/D [2414 0 R /XYZ 85.039 604.917 null] +>> endobj +2419 0 obj << +/D [2414 0 R /XYZ 85.039 581.599 null] +>> endobj +338 0 obj << +/D [2414 0 R /XYZ 85.039 528.401 null] +>> endobj +2420 0 obj << +/D [2414 0 R /XYZ 85.039 505.084 null] +>> endobj +342 0 obj << +/D [2414 0 R /XYZ 85.039 136.833 null] +>> endobj +2421 0 obj << +/D [2414 0 R /XYZ 85.039 115.636 null] +>> endobj +2413 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2425 0 obj << +/Length 3528 +/Filter /FlateDecode +>> +stream +xZYsF~ׯ`VDXZJ\[ &o=8HImjR8s=0 "\/Ij M7gFgxCgϿ׷ R3uk&V`ZBYc2 (n ò;n(^+U021=F6y&1;xs%}buKKhZ{Jdm1Rtċ[Tc^-MlS$uT Yij>-w\K[0va)GXX4Ng v1,BN~A\'8U*w +=i@8inϴ5f%MmSfANFFJ? +>2 "F:Y&~Q |LǶ;F^Sl˶噏NЩĬ[YWn"pӪMdϙ>-Gκ] +$n׀'3׹ 䮖}AueW ++@\7U))%1Fb2wZ0eFn>GɾR@KbGbA WN®@ERsYtyο]J  O IyFHjxHG8,p;wzΑNM{!'nBǟk;!M[aj ),‰-M]*/5vFOٰ(848!U9X7iR\X~gYx R-.8мǜ xFXUx ]q!h.nPy(IO䙻zYDiBzg`TI1JaMH%kLd @&~kS/5x ;:`'@VSD^ɻS/*dž^ve4u%}@و3?'qW?8ȟYCf'e +^m'%)#+T`i2Fa\5-y ӵ՝gɅN;SdpXEuXi;',]d4(Ov3܅W҂o5|*sY1_LOeXl. +MF80AԼ#BScbB1Z(smiՈn|p|gq9-'EhT"cc} ZTM+rhikk@a8F`>YkYڽ5W(T< d,YRRMwu4Z4N %8ߺjW_sZa}SꝌ P'صzb;*䐍+A=2 reiyu+ ZK'7E ׎/JugY̸)ru2ᩀ%mP +:~|Zua3Q{*d[O<ݞ8L,y곯F}iǷFdD۾$>#%= ]B~jqNkuUoS NdբJɫzǘ2Lρ)X +3_ʰh_蘧2e FDnʍ7JlPV-)>j +m@_dX% n:afBv!nr 4j]~|AJE8nSg*_2DP5% B%-`_WcEG샾û;[[S}ژ^78ѷ5WA{Y̍x6G}҈/hi.% B'/0n* I@A1&:WgClHhg&Aa_˚P[J t EOVeY${/lI_O5zyIKJ-XhfPtqRQ>ѐ)&)NoUHbGo`燽_@hYb|tRر7Z +XC&jZ>\pH@*oh 93)a +'(I(;)n1%P0UZ5~w @(諦ۥq5vߎ90!C0CZ7&U9IA&q2㳟3@dօendstream +endobj +2424 0 obj << +/Type /Page +/Contents 2425 0 R +/Resources 2423 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +>> endobj +2422 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (./xslt/figures/important.pdf) +/PTEX.PageNumber 1 +/Matrix [1 0 0 1 0 0] +/BBox [0 0 31 31] +/Resources << +/ProcSet [ /PDF ] +>> +/Length 557 +/Filter [/FlateDecode] +>> +stream +xmIn1 EOPwu$Ig0ľ6V5 oʯsO #h8:5?Ơ[IL~F PYdzZ8򑖌f(E#@xoL ۹[ -'pR T דǻ;xa8F%23pҪk -l1aAATX9 ch*?nYa<$~8Mzh.FO>䙓W?`$Z2% -Х?kɺkUm GwTVu)+ B,3膕' -BLyJ%(luocH[P؟ hiG&.>Fi;/sjNZ햙ঋ?X-9ЪjZkX;5M@;E⏌mendstream -endobj -1570 0 obj<>/XObject<<>>>>>>endobj -1571 0 obj<>stream -xW]s:}W/df&ĤIM~I,g z4-N}6Ȏ˃l&wi|Bo#Mwd8 "(]@x#8έ=dv&3w6Ο[mR3kATI?uTI =j5nqAM\/L,|O/`޼-\p?ʄZ2FWwALBljqZǶ?yGXF1E $R|ǹH`ZӪ05_[кZ y>\!|{ql쵎$t=,E/&_P;,zB?О eQg~W){|g5GK+Jݪr\٬á&q+i~csmSAZ(eȦqM\PbyK(|EUjԮ:\x+;2^%wR[U%pԋ[XNM'ia@ cM[(9c<%MJ\̼s1 ӧ.IR Wwq1x Xf01s>Vpa Mzϔ׭fxrLazwa5^ɂfƿ.Bendstream -endobj -1572 0 obj<>/XObject<<>>>>>>endobj -1573 0 obj<>stream -xV͏@WϠqyl_QE0GЕԕ5 daQ@fv1"KUPX!*0,Ծ3lG |\8gai\VPa8"1r!S 40PAǪroNu@|`OPDM,"O `m.2AcJx:Scz0&H::H anc<w2G7Pntf4] C.FFf#Ck -G WB#}m74YJ;˅J1:YҢ"{&~^wz5q×Ͷڷo}@endstream -endobj -1574 0 obj<>/XObject<<>>>>>>endobj -1575 0 obj<>stream -xWmo0ί8/tUL2`:@#O| IfU]м0͉"9?=e@Ns%hw8m_YkGM{Nbf褋(WMOˤcx,~۔ێ \;P#3vgdJ0_ǒb~57RxOYTb+ >2\Xc.YEXP|gۛWЋh%}! -Ԋ’;3ܧR+W`㚓25뚼0VmLb3l)M5@xol=F 3tX凊). C{bc],5[ sr" SgNB= 0q$wn)k1,5$G_ -i:6ҶEp;Px]F2  %|P{=n͏I+~,Ko K.2. x}>-,?{U/Ϗ!Y١ +s0\^ٖS$ 7ݦ+k'MKf225% -ŭ. FC 9N]+:ڑGsZGO~Ft X_|1WiN(m%[V endstream -endobj -1576 0 obj<>/XObject<<>>>>>>endobj -1577 0 obj<>stream -xWQo8~W҇cwnԓX -S_Lb!NR\Br RU;7|3j_:gp~ =h>o\v|} ]_ܽyogg˧.W(RPL홬x9(Xsy^A5SڝPW^UgҹT W8-@Wd&m:k,UTd2`˜~V+@SǸ Inrmo nϢjB]e"1y뛭!M)vW]40 lPi f6 Ɠk ĝp? -`s:Q >4*xk i0!]2BWЩJ\4r@2xLJ 6rCz0i)> %*iW1IjSe -ALM0vc1YX8n $:؁WZ2k3 }f!#6R|`$IPhH#1;;JRCd4]TG@pT$P+pDB04k3:falYX o+cAmM1utjLN8C -5p:)W wk MN1 -^͗V{%%TF hMX@Ee\ZhjV<8kIs@A4Lդ>#Q/^.*{V;ӤQp."wFڸC,}l {b鵵mT!ugC.F R bR4zӵw]Ww=)'ʹ'tXf_$,Ŷ|Uta\궥6lI;]eNö?M/;o:yxٮD~SL~ 헟tgvFˎwi}{7{X -yifz`w6n{cR͋΅׹>1A?TFendstream -endobj -1578 0 obj<>/XObject<<>>>>/Annots 819 0 R>>endobj -1579 0 obj<>stream -xWmo8ίn7J{Bn+J'!L06sc'iy Ӧ*$yf<]tlCWz}%}}3/P7vk# }$M+;C9mwffew`Rǫ./outFW9;8ߌ1Tn\:w>V;OGK -%Oui,R k! ^f>LLjkPuvt>H-1@[ ;yk%ɗ -ԪPJkyǕNj4MfTάq_T0y>B>A5}" O4d|}k+Am}?lpwӛJ_7q0_qOLz yP329V[iΘmEJl36*cn_ -Hlh+Hf3{m[܇rÓlk 0܅%`+2 -F;%OY`!=KS!5̅/>|ߘI&; BO"<Tp:3qtmbY1wR;[ -R*Q[Qa?n$ij!]3I݁]NKޓI-@N\p%FxEP-2ƪ0"I|Zȍ 04Q`HSB}0V4qFKl1T0QDbNTsuz2E\i.xRMD$CM-0V/źjkDCU3S$!pM &fQZk@n!2x/>gNdS ò1Ex*s..Sh24UB |,`-ac NQ}lBfRLR£[["v7ݶ5*Wendstream -endobj -1580 0 obj<>/XObject<>>>/Annots 828 0 R>>endobj -1581 0 obj<>stream -xWOH_1Tl'!$SujеWzIu鴱7ɂuw7vJM?\ 쏙ylL'Sʃa27?^74==OTx6yXN3^;=Ki?uk'?7:b-|q2l(|ⵯ4%?phv^z=: M. Vhٌ|Hlâ aF:Z )Oavկt%ڨʩjhIVHdYՔgwb+ ˺,e˜r6iHY[&QB׎’ X#L-6~gwiscͅ;qL-ZkUZ'*Gr*֚J7E8J%\N - tc[ۣ{\%V$[k]HcDEYI#F77>btLWH+c-u.B RtebN;Ѐ+yBІCLWX$ Vk+{֍h1qڪ$I%6N*^ k'!JzCW[d!0J&IR?I?SY86yxS1Lh. 9ސǵ-*˨'8:k++>LV8Zc1:teQָE!"jU '6rXubeGǴ\@ ~hB[CQ{`S(i-6Uʸ}N~qⓖq%JcX&2ցoʏ-ZR60;큡 JzIᢍŠqL[U -́x0=1`VPm]-|Hb"3ș9h֢YHu$c7}S,/ ū]wrޯ'g0qHz5GY2<;oRS7޾oyܺG#lq &yBްt_Bs!U&=[ /L8t6-> ڐendstream -endobj -1582 0 obj<>/XObject<>>>/Annots 835 0 R>>endobj -1583 0 obj<>stream -xWmOJί8$R6a+!&$j{\8)}̄p[*sрxH#Jˣ~Ǖ_>MF]wz qoxqȝ4ㆳ ϓJף9# g" 4_h2yAr?8|7~SBaT8(ՓB,]ۡρVK\9!r`We|i !Ba~Y(TFrK(i"cjkpE-03wӧ ϳ$Oqzο>^q2|]Slu=&p1$?dws!|@XəWC8jBzi 'b8; ǃѡUM]=~m;Sm>ﶪ[;+}A Z\2/= E-%,H|ǧLtWN :F?%Q q=?z_Qendstream -endobj -1584 0 obj<>/XObject<<>>>>>>endobj -1585 0 obj<>stream -xWao6_qӗ&A$[8ikm@hD$߾wfBeM&2ɻ{ANc|t>8lg3`t5< -[fsZ1-n#KzGfE[ZCt.5V^55Vi,ˣ׃3l.@U<\t[e;^`cF^p:*z;{B8o:2Dw wl1z ]҆)d%rga'l%uI*)و>Q?D- -\A+kEG.LnXwGY\ڦ1-|k.s!е5K7 sgd33,ߜXۮZs"BoC{HL'|XقP|u6(PXtdܜ$zYjX;1*NQ3--jY*pЂ:FWc^N>%NBah,%sW}ZqӼǓ)gs?Z1/o"d5@&da)G9P%7l)؃vƚAYt#vS aӌ t~R:C`\c+iXhX' &HZJƹYؘ4Λm+ Ahv -̈́FD %e[dn zE?o~c0tw(/Iՠ pXvc$ ±k:eXc[@0XƒD RhwH/@V2:1aאNUw[t'iqUpQ?Jkk 3؆KPdFÚVM[ldyBON "XEf)`xo/!g` yl9 pdač0|} T i`Eț (ÊCփu$ZmJYe^ʒ?% ďAp+ŝVn9G%yqѢw4 ;S5oD&\x1fiv> g/8nydendstream -endobj -1586 0 obj<>/XObject<<>>>>>>endobj -1587 0 obj<>stream -xWnF}W ؇nHSw/E4hPkEQŒ\Ik\YR}( "wr朙їh1ɜF#ZiL'cϒVIʏMZU{yKΛVT]ƶ.?~m㍭ժVSњ;rvoxGvWSUNV7GqJh? kSjXSo`h8oK6JU"[eeR6:mW{mܗ{qѴ[b Er矶\ʶTf;/W]Cv/lZ14&/mKQ5Nm MFD ؐ$"8u|!<ɉQ$鯏ɔ^ma+.v"<P=98w]g,;0go>ڌ> 92fR$"]}>b3m= fz\GZ'ٳd@uWߪܳjp <|$>4bNҕ+SeW>{X䊘br^|v4_8MǗ2(MFwjodOcp'/mpg/mp}{~PrB4^U,h/FcE U4E("ЏeAd=5@7Q<,luvh--:8ev3:m ]h)m ~ %$Gf6͵s.L g~et}BP-DOUSlq Vw# =Ѝhiv8fbx~Tg9[n5E(n_i9LmTd'fӡ Qb;@g - -C>/XObject<>>>/Annots 838 0 R>>endobj -1589 0 obj<>stream -xSA!5?_vc~f1h՘Lmxɳ|*FȖsf-/r -Wr۶}Wt&%Y%viӸc険 I@wmTh:mϙ8/k}4s_c&Vt>Kʪ5]Kfk8[Qzٌ[rE뜦b::;nM'_(h˒6\4zKS֑7[K-%2L[{d$L;dk8_;S)2NLHZFFglusr'9"ZkUy{??QTi -grSXzyJ7d ]s:p˜2S;++S2D]]Y(ʭ~Bv[]*G[k**oޤnY8aCUU)'/ɩFZ52{ԂRH<$\ [']#JG߯c-Z]{yՅ ~xϳ$F]-A%r$j#!{~ccjmn&H(D d$4$|(t =@ӃOT }DKenE}  X/B%-GNzJyϔ%׷:@OKTéCT0qjJ_(2=8 ZK9ǐuϵ$;6+ HNMXq,{2jo^?J$mM]S,wsȎYN16OV>)yb> 846TҦ} S+ -aUrB Ԏ9֏ -㻃&oy(M/kC;cM 454j!Ҷm]3̮+/D[Ƅ 2Ԕ2SW/aC_rx*º8M<jn ԍOL]@7U -G6C\q|B+Q{OB;ЪpPinQM?>n}_l| 3WW2LՀg3?i.η6'*2Șhਛ:}x: ==x,r6@=8"oл~l709S}~T/6za6?_~wxRoLVC%=q=$@cv%&4;tÆS*TXjx Jl04IUP,\qC;HɠRUCrH<*2CNJ]+G4<ſi[=H(d+$U>KÄ>$}nnrl})$|zbn}:Zb7<1 $,Apx+\\ '35>#ff4ҹ]Q%#"tr$ee֐ qk])+8FNWxqcteCB aQuJ<6e|oGtG"\%8Lk!,"0ycgAB@wקYX`ӦueLqVaqCNw$н#51F__Y{,CH4qsE/$zS_3q +6\>RgbWj[ +WϢ{6;F])/ԬMu;pk;̩dh> endobj +346 0 obj << +/D [2424 0 R /XYZ 85.039 665.791 null] +>> endobj +2427 0 obj << +/D [2424 0 R /XYZ 85.039 636.387 null] +>> endobj +2423 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im3 2422 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2430 0 obj << +/Length 3395 +/Filter /FlateDecode +>> +stream +xڥZo6_ +PE}mn۸zrbT|\Pm9@p8/^ /2B?ʲ"|/B.$1/[b.σrbw刺0x5YfU@ zx7_̻=?Co?rWpnnϿݼ4z>qf}D` +._.?ʳg0/76Fگ..S1{)&D1s0sO7iD$8fh,$HtQI$  +q9_(4KC7"3CxI'SDit +c" ^:teEDT+T58yf>Nlu[y\B ߢ$TY̓+:'s _xL\9}Xt,щ-f$ځWX| +UI R\uYR ,HYdRʝJ L03(r@&ْbPꦓҼ턈fX%̿he-Liv1f { ++AC8SBRQ0hL8h-UtYJ(nA/+UU_{,b8ϽZDm #X92XlZ{_ê O]w>V\|}wp!Ǧ-Иk{'cDCv@(5= +'WeѪC2x;>?@XZ:'/[U;g>o|="sL!H $5~bS!baQ*yrbҢ4S!AYSmɽ 74E^ɦq7VdjO|\3U3fK4ɉuE0^ TOtqXzjp~}\*J&:S:N. +gFsnJ83W +=IhglO1l<uXs &MaέwS%GNNYMz +;.=q5\K3Uwk'{i(S+`IpzꂏqQEW\ԖΥR\2oɌݎdO gX-gܕ(Wƹrr"THL|כ]UoEqWH,o>>Ԇy،9ԫ+g{W.v[us7qΉEG]S=森ک,8~(a1fmnbltՋHխ]IqH5g8maލƵW>0XT'ԇW{,oʉ zsTAsfgi<5mH66Ք +6)bգr:tta$50ݛ9|UXLD秵 ҕE[PӜBˡR&j[Q'X1{r#K3SX;d@"^#7irIK $u&Ģ-Qd9&)EE&%we':2PEfBx'@~&rG2[Ze'wF`oVF"9 + 2AW邬|>̢vxtz>v+ p +*SOK$yv㑈q& gzyJGW9x>Zshh8PGaw)c֟KҲWS80`%-( +kYM(UQשBP-r\ը0(dƖ:upd*\nkDt_}כYIhίl0IOŶ/LME_ nqOui#?IϐtK(F8If a])f9Rz6&8_S2!uQՏYdq%y,c|;s;edwןi%oNvx&;jmQ;PvvnEe7 aTU=cruBQk.\#,0JqYNkuPOA̭qoҳFy>k3 BrB#rQwa@P ̠=Kd+F~8Rhv,u AJvHq'ӘTXn0,diՆChaRZ^_ 9pCЩ=:]v7{[Tj]05=((1'_VGD#)YEes I޲dly\g3yA+?$Ɉ'\]iU;Ԫ%WSsK[Wũoz(40IM*P҉O¾Um0N3tLW̄n`OtNi+QnO6ʤۡȩquUתXp3j0 v m}^p +}6_4k80"܅n(Z_ES غ*SdNnzhjq,;1q aa#"ݩZkϞǨ%yL<@IdRkoea +P[@*B&=-ݸt#50u,nҞwFDVt_~c=֍=ujcdb%,̦gJo+2F[9!oHMʃ1;FiqC[lN^\ŗs/H+Ȓ7#j.W?F2oC㭎LҨg7EuYyII)ʻJR*5Ԕ,*a-]ʽ5J#ͤ/Ҩ]bnuy׀J1/d|Y97vQ} 7ݓUl|? 'gkF2nM{xPDG]E[ d'X Z˝8•N+0I$l8TO7gN)Wj֫,!-GAF՟@eP<#8gfgއ;&?N?̩ڟѬh^)=Sq12Dendstream +endobj +2429 0 obj << +/Type /Page +/Contents 2430 0 R +/Resources 2428 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2396 0 R +>> endobj +2431 0 obj << +/D [2429 0 R /XYZ 85.039 781.388 null] +>> endobj +350 0 obj << +/D [2429 0 R /XYZ 85.039 761.463 null] +>> endobj +2432 0 obj << +/D [2429 0 R /XYZ 85.039 741.134 null] +>> endobj +354 0 obj << +/D [2429 0 R /XYZ 85.039 125.405 null] +>> endobj +2436 0 obj << +/D [2429 0 R /XYZ 85.039 102.087 null] +>> endobj +2428 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R /F72 2435 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2439 0 obj << +/Length 3067 +/Filter /FlateDecode +>> +stream +xڵrF]_e`pͲ[-i-8#Q-﷯!rjR*{`5O͒t:$'0NPxQ˓WDLynꥳHΛg E'\9?Fhbk|˹87׌8[p^C~lדEF&:Oo9~=\&G{J$Z˓w0. Q,,BnS4~ +QvR 2 0ִ +E(K;gU+i:N"/:mOTع5 )ƙR]3/zZvz,&ϊ Ḡ @ 2N[<>k70PN(˼A<@+FXa{QQҔv+46BY&hF|[ hdF/!|]p)8B`S6x-/{'u17ʑh |䢂؉_y:8.* Nb'˿"CD]0}Kcfi5>\vYk&TCq#*4"1VHBhIT- ~hՊKeUYca5-&\x07EO<%SqE9-nQ@AVbV=IFj]=7F!,tF!,7!,{./a5%GE^ ߍ#rC8/F0w֨Q<ؐ$I CMR #5pK̎d@SZWϊJ,G O0zJK~ܖdw~`Mh7䐎5D&fQL%Ok˶$M5-D{n-D/Ʌ$:cVϵ<6.^ %9W%:|ɖ9YkWi4Y$$PW ښEꠓ^<%R +w\u7UcI TX`L|֬L,@v ^*𻷘s}.89%#xڍ!&/(?9 r~bytɄ\D[m감0@&ucS-G] [Z8dNǔ ,I[JrNJT\ Oy@Uַemi +Dȅ-T] B8C8yQ`41հ}xs459 G˚tA_K05iZqpGՔ`H,1$}x%W4m'va#[}xÉ?p~<%9&AuF +SGU=grȐ-?x+-犅ծhp*ٗ7=f8%6[1J YPWŔ{gy +$mRɅ@ՇCqՓRj7*j|fRtw(ӊm% *-{7HH+1 +eMmw'skxn6\<$-˭Ht+Av;vOd(4,8޷? +קlڼYJ> ΡUnQs9sʕ+aN\ބO$*`ap*kSs#j%r]ƄZzu~cϡs +&}MmjJi8vkDHs~ k啹BL 0ݧ簯U&KL bƖ0Pٷ١;ڋP:`Rip_ԥ <}VO] soȹGGT7˕'zQ׋;׆[].<G/QҁW〜\Fއr]DFow&eѴ}xE48K)AmLXTtJ4ݝ? PpV&ܠ4 G(o_xw 9&rϻw xrG n Nzξэ/2HEQdq4ܮ?a9><ϓϔV4M}ؒl%x*AH Ga 72,(D;A@ӄO |4Faumrξya8Ggľ7]VJ:.w˔rfxc&$B?Lum{D|U1KE*÷ʶ8o1fnK** m;C%ʥ uz +2WxA}4?@!A +Y7qR7E +wAc 3$a_}&*6 %}ĽYPMjo{jQʗ:v0a#m!u~ Ns ߍ > 4j,*L(endstream +endobj +2438 0 obj << +/Type /Page +/Contents 2439 0 R +/Resources 2437 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2445 0 R +>> endobj +2440 0 obj << +/D [2438 0 R /XYZ 85.039 781.388 null] +>> endobj +358 0 obj << +/D [2438 0 R /XYZ 85.039 761.463 null] +>> endobj +2441 0 obj << +/D [2438 0 R /XYZ 85.039 743.459 null] +>> endobj +362 0 obj << +/D [2438 0 R /XYZ 85.039 657.234 null] +>> endobj +2442 0 obj << +/D [2438 0 R /XYZ 85.039 627.83 null] +>> endobj +366 0 obj << +/D [2438 0 R /XYZ 85.039 586.218 null] +>> endobj +2443 0 obj << +/D [2438 0 R /XYZ 85.039 565.021 null] +>> endobj +370 0 obj << +/D [2438 0 R /XYZ 85.039 145.627 null] +>> endobj +2444 0 obj << +/D [2438 0 R /XYZ 85.039 124.634 null] +>> endobj +2437 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F65 2099 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2448 0 obj << +/Length 2464 +/Filter /FlateDecode +>> +stream +xYYoH~2Qn3YϬaf(HߺE]€GuuuUK S4 T&M,aә`Als* Ld2ϋÑ1(IRa  1O+{?a佀HyeˊruϪ05v0@]6%P%U./vSvKDs]uuGF*MF: _,3]0V(H"CjaD^3i$%MX0 X FP쏰и st-Y+*@ ; ]ވD%uyw֦B5P'WaW֞:`; ۲wx!ڌ,TZ"3~fЀé臘Ad`9+q)pt\USr5nl9ZU<}sЏj SZ4E79+Ыk;g9q$agIY KQWxynys S9-J `o'-\jQm$HZ)D$cG`q]S,J>`KIfḱAޔyNjYZퟅ${eEh:;&}jwz3!\ڂ-gk#S +Vd+6ϦZZuIgW7q5Bq2C% hL/z14@d~wsߣS%GZU뜂yOV@;QDy˲{]F;LO@oO$ܗ[,ʦDPsdum+ Eiq+_8YSenoYD/@]Wd뚿x`.Jn Aޜ#@@!G bTƋ˯:ܛSeW⥸D + +{JnVr*j>lS/3s9FE~&,kvwH',8Q])*D;.ZaٵO̔?肣#I@o!E\a܇̏^ 7fb]ıw NyВX;zhژSz:?y`'[=Eyn`Kb JJj(cL'*ւcaP@'1z8WKrZ`qb.*!bZΕEeQA"6)B QZgY!\a U΄d-(-V$r~@kpk!c@Q_0| C;/CuLԏu\Užj.R;9Prgj] eGɛ-jA4j$\z'Tθ  P`ƠA02T.Mlm +W eh9iKZbw $rBȭUSlO(R#u%F|w*CJ )9)P9{geySdI4Qlh;+jfUR×e#4y "Q)p0oZWB N ]  =Lm_IfƆ;!L%F<}SsGΕD$"Sp +ykA z"r.Lrk=M 96yJm 9GCrJ"yi+(õ⑌)|g[Qqx:&BOsܹz'E,KÂII\!T] 2#,ƹ+{q@Jaµ&Pm]^=`'jWS~Irͭ0BT8z HJ襣H-rYL%S=g \0|a 2pq?z bS Ga7hN16Nh[E}J8Rlo[ ԝmSa|Q)RNFzo@D1Nw!Oyi6j1~s"Z[.PH`RnN M\G&X]68ENP"rCݺC+cK +XN +/59GC]QWTV18xI#$`,ζ $D?h+o'NUqth,ƷyN %4tŲ,$Ȧ]N c9|L?P$opj$f[~L`L晴aBv\51|bSeہ>[܋Ӈ 0 Խo"j=9#aHJendstream +endobj +2447 0 obj << +/Type /Page +/Contents 2448 0 R +/Resources 2446 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2445 0 R +>> endobj +2449 0 obj << +/D [2447 0 R /XYZ 85.039 781.388 null] +>> endobj +374 0 obj << +/D [2447 0 R /XYZ 85.039 351.586 null] +>> endobj +2450 0 obj << +/D [2447 0 R /XYZ 85.039 320.97 null] +>> endobj +2446 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2453 0 obj << +/Length 3684 +/Filter /FlateDecode +>> +stream +xڥio6{~QH4"%跹:.&xw + ۊ#,y$y})H:@ H>=Z"S܄Q\̲\qVۋhJ YF׋?z@߃7zq*WYs&Kp_|y\[y_?^.\߼~n○w ǫ$Lzl " +"=@; +UQ̶Co.n/vdƫΐB\",9Pg1@LᨦaNVi4R@/cu(xjlW*4T*qf䙺o .c\Ytt 9|ʜamEf)WZ\M=c5@, \)`q_ٹ93jY8"xvL-6R6L6IsŵcLS]qPp\Z(qFZw/}"*J 2#F JB(Ur\t%w>+*m9tR w4Hj utMXv͍Ɛè:(BB{<%0&d?a[ûQlYdMuCH5UH7& 0Ik%FAI;/ےxvoQd8n{D;4I Sq[\^@f={4H:x[iJd>N7U"%[>(2 =Ybۅ’5K:vʾ֊[p^LW7y +kM=hj4F1Jdi=uqy. m $؎ !rh嶲G^-"@5&dC-i!.aqጝ+½nsURMeg$œ={bX]g81,t$in0Nͯ *5޽`8j=˞"mgtY쳼,$m;40/j@9V<ܺDYp[B' ky +`tϽIp=+}Td^.%kİY0EDM#j!܋$VAZ+сgIDy|_rmJR5tuݝ]c!QxjHj%K\H;<\73zq ގxHX-R;Gop +ԚCd*"7)ǦMqZOC"؇[ c 阩B,ugv.THKeDtE̳^0뭚لU\NM4E*?}-٫ ɮEwA+YF@B+NzյPL#Eʴym$+n; Q֣h#U4<ԃ|$ [_ +7Ij)A GyatH.Oum05Jab(NWh-wM3 3Or +SҞ)mppCÑ` zyY&a'Y4ɪV]Z yF‡$N_)£)̑9A( +qZ֮}*'v}?a y \e#Xd#Lwo M] H|m8L#"8IwY=q5]d&\8wD|Do22%deꌦt)PB '=Џ68:Kbbr2/"]1%ayND!Iظ:6ն&l9cQ1&N[Y9tX!fJl.$bʞ ( aR1b@c#b:ԑu;MM+=e$ $ILLszSJ۰C>a(Q/O2A'ϮGMfGe* Yd Ѓ gϊFjE(jKƁ\eSX p@?kas唓`y#|o8DZkKw }tAe +]`^m:/<)X1pڒHM!mEl)$Ng[Q!V`Unw~0rB,m-'ۉAUuFÊ4̳Bְ0̷rSUVy]R]9WPkE~~3۵?uf?"wjz":Ke%טb,8`t*pys$Л A}'ݞ +ݏpI:J]b%'fL wG# QnNߊ"cw#9כ೮ 7j*45OUDQ 6+F›\Jiu_2&Q P )X ++`M.o rf бos_gkrL0dhD-%WU9EcOXr C/=wYhOc< _ +Qq`6>8~duaӈ +=ʵA`hhB< +c._xNOZ=`z~} + 2&C1.jqr~(+JGaZ|Ou΄ݯ>;@x +eMMv =l> endobj +2454 0 obj << +/D [2452 0 R /XYZ 85.039 781.388 null] +>> endobj +378 0 obj << +/D [2452 0 R /XYZ 85.039 761.463 null] +>> endobj +2455 0 obj << +/D [2452 0 R /XYZ 85.039 741.134 null] +>> endobj +382 0 obj << +/D [2452 0 R /XYZ 85.039 298.591 null] +>> endobj +2456 0 obj << +/D [2452 0 R /XYZ 85.039 279.719 null] +>> endobj +2451 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F56 1642 0 R /F41 2104 0 R /F65 2099 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2459 0 obj << +/Length 2905 +/Filter /FlateDecode +>> +stream +xڥYoF_Иry/NU-$D$%ffWD'k 3;=+3L4l9 ڢ'0NRD$xbIf_nfoڠ y^wS:{hq4.w~?۟pvS \^>lp$L2CqdA$ +mYL^h,'$aXNNw\2U#8u 80-QK-&!H:Zf!Ȓ4 +fj५ eA5oq,C):qhsl&bNle+ꔠy26 +:G[9ĩr{,DK ( ܺmIFY3c3E .o {rWυ[+hx.?)bSPȽV+:Bk3 v%lj!BB\EPlF6C cʖQeǍ;-,]>r{ut=g '\/fHb]]a|t˅"v=t_q/xHGb3 B@t.rbk[9.qW#6 eZC:5% ?6,G;"^l'8}<0jH-lĜyFH8\(ǂ,1m+b|6}eZ**yW:2$1b R/Zв:-wZos̆IrW)_`od,(SxhfF׳72`ZuAƵ:A#_i{K7,S݊8#Ց&\kౖFbVZ&>@A% *᝻`E:9@_\|L )\ǜRz*]4&:mF`3o$ 70K I+/HUʒMN>9k_ _z6I&EhAԤ 4Q:7MqYdˑ=Q_{vtAbT'@9˟cp)]8bc*~8YEV_|l!U]jh]āq۲Ze#ǥ2g W!*%vٻ(D;0ɋB] Tn*M +t$/ˁjy^|PH*fzz?.>{.{{=A\CXG+)PH,朳 )AҪIJ>)$7hOy& TǂBWK#A%?IRjLK3RiXޝj !IJʯ4|x(Ŵ9-: +9 Eto;ǘ_8{xLN1"+KZ+cȆ$' ϣLhӆ)nQ +q29m\f^X~>g0DvFG߼a7W,c-_gJǵ-3w Z1lKEX|p#Ώ1aF8t=]/A}->f:$Z2f{j(DͿt[6<-4.#Cm$_$ ]tx2;"0IT69jn亘h^[30I۹g%z?==-HNDa/;II[<,vQpݬ5c ~,azͬ\\P2۽"E ,B$뱠"> ~C)`,ڻ^27#bT Qi{(7kbSIqԨиZe( "I"yMLpшjԕq.{?_Ns*F߄@8oV+~صoP7 yγ7* 1e&~$Q~k J&`ڊV4 +k/Xq!p40 Z5Fv/U[}>m}#%"w&CG3i@~PRu֡x_`Q1emJE:-SkϙjZSi endstream +endobj +2458 0 obj << +/Type /Page +/Contents 2459 0 R +/Resources 2457 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2445 0 R +>> endobj +2460 0 obj << +/D [2458 0 R /XYZ 85.039 781.388 null] +>> endobj +386 0 obj << +/D [2458 0 R /XYZ 85.039 761.463 null] +>> endobj +2461 0 obj << +/D [2458 0 R /XYZ 85.039 741.134 null] +>> endobj +390 0 obj << +/D [2458 0 R /XYZ 85.039 484.308 null] +>> endobj +2462 0 obj << +/D [2458 0 R /XYZ 85.039 461.592 null] +>> endobj +2457 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2465 0 obj << +/Length 3030 +/Filter /FlateDecode +>> +stream +x]oܸݿb"YE")*v6N;!-dWr$m\߯|v$@sA "p8on_I|8.6F^2#Z0J:8x2U8 +(_\\Ӕկxppe68?G53|}_|8=;ysl^\|wd;ӳW }Ѹ4I5ߣ +A.q/6&abXx,x +&NB X(x O:XXVA[v%7աʂ +Fm'.06hrw0) ND17;uݴ؈ ]_خ׻2q?'}ШqI{=15[z9Xi*N!gBw;d!V\[Gc!UF>61L+ +nƇӳsnh[BWw8+Lqfʈu ]LiN ++.;qGī*a+`9^:rZT;}<,y=R,C|^3b&IAmƦD9:G0qipQNѶ|yJB9P*3mvJ3PGۯM/sqן^fCF | * +K i3J1hx1g|R^ci0v+7afj_ћHwB'@q9P8'Dp\5]G!S*y6H0xzpEJ85/ƽBc8J@`p߾ g.FxDͶ*7H38 ]+<b[nH2tX[4|(3RuŌ<e5"W7[V z~, '9Wyash/\ݨaʉec\ H\{i=? )~ГΙ 9ѡ^TOEU9}ʝ.M Hxo YP+`{|uTcZڍ0I{XpO#Q?鲕Wr]^a)~BI8zK1~Ui5*:KT1*Ym!<;w5[/[jGJM3p>wѣ2@֕e ,u?,~ʹa.n|̙1 :Q<{>;0?4_pk,W0zZ+(T'hqW?#9ј,6endstream +endobj +2464 0 obj << +/Type /Page +/Contents 2465 0 R +/Resources 2463 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2445 0 R +>> endobj +2466 0 obj << +/D [2464 0 R /XYZ 85.039 781.388 null] +>> endobj +2463 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2469 0 obj << +/Length 1658 +/Filter /FlateDecode +>> +stream +xYr6}W./}l'MZ+mLhlH뻋/n;gw`8?Dq;a$"gq4/FZpg<ШGϞ~?5:|| +4z;Kǫg*9qlFVL~GYH;4j +OP9,0w\8{ZjMdy+CODWOC^nVf wg 7I30]1MwiY.WK<"MԭW +˔:y{ɶ^eV'uv׈MZ1\sч<3fPC,4]e}1"[n+8#c`lZؓpP$AWQ~4]䚖,q^]agp-\wV\aW`gl1@P)RnB1"NB:h K0Hn<Cx:iq:bYmAEdb6ԗZWƽq$"SLTrJ ChrّstB li +)nnڹi&*Ɉ|h(%)nX3pS,dLZkrESr:7 +G;\ys(7hgtTxMJ_H=KZX7a>]l{!J1CYہ6cȂp|Ԕ/Y6CDI 졙n™"g ?TiX>Bk&a5Ѣyv8]Cp]d5&B}H(#|꠻AÊI%LF$2\)rLphהuo Xu,5θO@G)!_3RIh݀ʏpp$PBp3ቒR 7fO/Yt??Ɇ "1endstream +endobj +2468 0 obj << +/Type /Page +/Contents 2469 0 R +/Resources 2467 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2445 0 R +>> endobj +2470 0 obj << +/D [2468 0 R /XYZ 85.039 781.388 null] +>> endobj +2467 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2473 0 obj << +/Length 1215 +/Filter /FlateDecode +>> +stream +xڭW_s6 УRlioIf{m:U:v.Jmk{3A@P?%12`2IU1HnGip/b|j1x7 =YSo*Go,nƁO8N>凫KF ?q ǻ8L9 f7G?N%-qo^,z1&g3p#dx@s&+FQ,YIGџEHE) $gIu9@NfOq!Pέ-E|͉r>+qn#_hs(8,YD~{Gxk:ohFc7}J׾ lڗe z^9E]g53eqw@cPD8}xZlPaQ\7IJ_dH4yV9L[Bwe݈NlSX1- G:U __M>8{q&4Psԋf:*endstream +endobj +2472 0 obj << +/Type /Page +/Contents 2473 0 R +/Resources 2471 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2478 0 R +>> endobj +2474 0 obj << +/D [2472 0 R /XYZ 85.039 781.388 null] +>> endobj +2475 0 obj << +/D [2472 0 R /XYZ 85.039 634.111 null] +>> endobj +2476 0 obj << +/D [2472 0 R /XYZ 85.039 598.046 null] +>> endobj +2477 0 obj << +/D [2472 0 R /XYZ 85.039 561.982 null] +>> endobj +2471 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2481 0 obj << +/Length 2581 +/Filter /FlateDecode +>> +stream +xڕYKW 0IvSAāI`-A6ȑHѿOU}$5:_Z]@nJunw|iBKcZS{frft2G%~e4ͻ. +Jmr uzm,jxET/T5Gutfk|e3d7i$aJM ꍠ!Sc55zY&Qq4lwEM^feFKQ~zǴ+NG+D JC>Er44h_6p'-g$=Pb:bssEmY~L˺BaAEl:6e.4)8%j^]YE@^-g0Mg:EŃbAi5zގ):7-LKր(bӊl֒zux7Eh`b1O#! Lͳ(53`lJ -wis-ے[%u5¨h0h+:8|Gװˋan(NVރzܙcH'P=K,gѹ<)5p)n;#vo)'%bH<%tY`u%LQݦusΚ‘Rj-(0r-f<=!9pn[*Z0) 62CQZv3PXKf/rSLd37A#! +ׁ1ĭ ڎue|g4 е%nKo@</^y9<9iXe;PwAz, '45\Õf:>?9wST$(#h=L@_[yu%!|c2kg<9U./ 1=?bfR1 ++rvM8C4OL~=VvO|}ـ([3Xm7--KlޭøV}gg]j.yC'rTaUD~>|] r+w _ :GNҡr,E/{BZylAoo L~B +x +Ir;M.h_y| [aY`X n[/OGlsW@0s\ɪuhpJgdܿv{Rq) ąxzL&ydyWT+ϰJ 6';lVd3 О?A&fTK.AN/d{]f.D[q $1E  +-A{SyJ p1:fh`k2 +rpbq͑K.# ' ߪ,tB3䬶k\+e/hcxg,#~Qr.rɊBp5srMg\b(SsX!#f:&Y$tg2?*`v0>p`YD)ɜw%c̔68tV̿aC +-(rHd~2%-rxp8'-VxAeP"6٩z@&NFkWVIu'K٣_`:/GxfI1 ѥۜs1 B!/~V2{Hev;dc!TfnmIVR94ٗUpȺo ¥ODW{hlˑ*8*|GuW$$Z[6DO\0]7g]"bVm[lKy$y2A]̎0F[]Mh9f*NJTo|H>X!e3Mym2 Y!G 3_k-xKbjd{Rt. &_ĺQRpvC5®UQ) /m|*1??ۙx&j4#'̾3(e,1'7t@G}OCeӹg+"^C6AQE'S~c$s|9 S⼞'31=9GLFAV]A_ꋒM{E6ʱFq~w&Kl(ߟƔWZq0NȈE&i47D(mXG_ ؎^Or= ON3?3L!?2v(~c葝e4F>`]8UEՖ +guZEo7TGQrgRendstream +endobj +2480 0 obj << +/Type /Page +/Contents 2481 0 R +/Resources 2479 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2478 0 R +>> endobj +2482 0 obj << +/D [2480 0 R /XYZ 85.039 781.388 null] +>> endobj +394 0 obj << +/D [2480 0 R /XYZ 85.039 761.463 null] +>> endobj +2247 0 obj << +/D [2480 0 R /XYZ 85.039 671.062 null] +>> endobj +398 0 obj << +/D [2480 0 R /XYZ 85.039 671.062 null] +>> endobj +2483 0 obj << +/D [2480 0 R /XYZ 85.039 642.326 null] +>> endobj +402 0 obj << +/D [2480 0 R /XYZ 85.039 406.978 null] +>> endobj +2484 0 obj << +/D [2480 0 R /XYZ 85.039 377.574 null] +>> endobj +2479 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2487 0 obj << +/Length 2038 +/Filter /FlateDecode +>> +stream +xnJ_#>fn{HN;+v@N~ sVjE +MuuQ* ˃?a%Ԋ$³` 1<+p(ĭ7Շȷ^j6ZyyґRڰt8u~˧e"x`7wW-ޯ&L8Dݳ_ ϕiba"M"RW?*X|jFV'#׏ada~e&Qt )Lc"Îp0RzfǞ'dN'5;"ǭok1kM<0w"qGv_sd=|-56K?nVlp?7)Pb @$7:歾Їֆ9W_i'[TLۤ$4۲HpX ">>aȞY" )>:'Fƛj"2ZYY ȱ^B~NH}SMlP끴1ړ(,GVmI <CL$0pO=dTxg=yʋj?dnFՐ0 Cڇ!{qh4njj<Ҳn4Dm;֐f np4fS}˚fRlz2MV%/Ca[{pLMM>!pZkUʖ`۷)Tr[WOBu¥鶃kc$p5>T8?[VP ؤtʙIGŜϩDQ9M\A\R{‹ڱ@ C؟=c>f=ȪW8`SX]]ԭ如';UgdpQL9~,&)$ +AB6L0^44|1yn$!Ar$1տ)Bߍ~Z4t}a!.N7b.5ס9=!{8*Q? +] hț(|A Oo~p?Yw wg +*ҘߗysC;DO3- '@N-ih򵨛.2ݱm~,3ޣ0՜6OnRD(!ޱg; y_y;o p3FDK|YeCG z8ڄD~IdX(ӀkĀu(NgE0Οf˹$84ցS)1Ux԰ hf=7X + Ke_SE 7elDOE3 +endstream +endobj +2486 0 obj << +/Type /Page +/Contents 2487 0 R +/Resources 2485 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2478 0 R +>> endobj +2488 0 obj << +/D [2486 0 R /XYZ 85.039 781.388 null] +>> endobj +2485 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F71 2204 0 R /F15 1628 0 R >> +/XObject << /Im2 2261 0 R /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2491 0 obj << +/Length 3153 +/Filter /FlateDecode +>> +stream +xko>D,gQRz5-|%JfM +Iy-hs9;;;Jp5#q ?v|z3p] .zM +xS GݣYe9P*9Ұ(;' ݀C8qY";֍9e#,WȮ*tvZtD49ѮeCg 'fcgOia d8tϙݘQprNYV82nQwS7?]7x$Q g|eI4JX5\V&76gh7҉(!x-?ov|Ǒ/|}+xC\:tِG}xtu8_~C"oB?no޸ ҳESg0,ivÜrS<`w +߅BzSVuxlȩQ=عn߈BXIY}Wţ&DPnP>seˎ=>+A >oP2ҷ(\3Y 7550VMv&+I08C8y41EYs`5WNl0aBUn{BA^ͬ¡!}v +~˨u,eHI`ƅ0o/kLpݵGb#=lc^Or\|Hk~fL5g7LHzF SOZAbBzE{zjAA; ڐQ€nHh5R+ppVl47Jֲ+! ];QD&T3WU,:Ύс;2Aɘ0Hbl 5"1Ē2#q˰uFJVnjp'~Q>>/+cI|8GܼlBkjή'jy9ST[쑳"5i^BziOu>XE$*H >~[cȭ(Uj!7䓚x(q-_vw A! \ kR RgIN>g5;TP~/@Kȿ$wv(;ySEZPBgEa)Pd̉#ֱe͘UI 細e=ΉNġ6َr CF^0rld&$1U2s{ca[-)ҔZ3[R[?ZM1xd%hn/1, +H1z,W\,1-IEG_L72,:,Q2Ό;_løWc($ RO YY+=8ԙp_tHE s,У✸nvaQ' 8bd7>pE􏸣OL}0vX>pAii)_ +q+v|2I#'M-]ϏaB?c+՘JuSR=9y87piu=­D}]<3Mf_LAZ)o>23 +idи m+q} @4ڣf%nvYyrvkT'^=|60 w1DƦ ~mQuTE ]iJ 1P4Cd+A_Ȫ{Kd$gj*̊_tȐR?ʸ7%0lQMp2sSmӻˏ'L՘!+*.]%X!)KwRBޫ8{&Euv\nqӁ%ȰVkT4dﲮm+Ƹ ڮnrٛ" ꀈ8Vi5yPubg[=o\Bw2}l"V>M[= +<92UpXE峑kS{Dc"i| F+RM| @P`1E gcE.ž|UHf[ Qͩ`: kf™Z6*EOd$'NE3 q;GTdIbͷzM:tXH+?2HȐ7CQ՝BzBDADdL Vd1yaZwHjpf0˕$k/zPKJ/KF),.|Tog[&>sӱgq*޾AcL /i>X5#7S-xw,pGrFQ[l+HK}Ao8;,m3`ǁLu,o9ⷩyxܴE/(f̋, |73͘!l3}A]P#L.' )7C'SXRS Avԣe0:>qx?qEGD)ֆdR5Dxrm[œmRn}%yCLڿZ>?cco #Tb3 +Nω8jܡ}endstream +endobj +2490 0 obj << +/Type /Page +/Contents 2491 0 R +/Resources 2489 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2478 0 R +>> endobj +2492 0 obj << +/D [2490 0 R /XYZ 85.039 781.388 null] +>> endobj +406 0 obj << +/D [2490 0 R /XYZ 85.039 694.591 null] +>> endobj +2493 0 obj << +/D [2490 0 R /XYZ 85.039 671.274 null] +>> endobj +410 0 obj << +/D [2490 0 R /XYZ 85.039 529.279 null] +>> endobj +2494 0 obj << +/D [2490 0 R /XYZ 85.039 508.689 null] +>> endobj +414 0 obj << +/D [2490 0 R /XYZ 85.039 420.324 null] +>> endobj +2495 0 obj << +/D [2490 0 R /XYZ 85.039 390.919 null] +>> endobj +2489 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2498 0 obj << +/Length 3201 +/Filter /FlateDecode +>> +stream +xZ[oF~ +he}p$u&^GEh0iD*$E23$%t #I}|;??It'+d^xԼu o^$]L|Mt2&wOWwә,OS17Mx4b.?W>9Y膑U|OoB\&{E(+C7.eGp½F:3-f~ꦁkn hBKu+¨/h,d:U4Js;m=L=6ksˑ`|:8,UTeSsQ[lP\U1Z|+ɸϾOQ8pUmQ\v=-׮s~ٗ8A2ժ*Zn EtRdkv%{ !k~Ü`z; j _g|'ԕq~Fm.viwGnSU>2` OLk4dI$|^,YvVaĸɸN%w-c:(‚q 1eAYK0ʂK +M@j~j)TKr~?ORq,U/jT!gA{*|Z/ׯ_NpPàH)Wܮ]ÉkB-q;_zGgLTܔ/[.󯸇7p sJe-d \ -R+j_^ +kqNa^Q892YWiuЈ/!OZt6͌`J vԃ_NH?s\G"4 0BMJϹAC Wx / -eN8GP%c5q y2`![! ++ށl+.Yew<=k%>|iSA +9$fYAZ2Scqm2*+yHG!im$0 K$`KgNg0CGH(Ĭ7jGl"<5$ nUv^'R\ԑbH, cH;g! 5wmL-ʔݫaėpK^hLoۊD7LyF:b zO@xJNu~Oї.|egvNuaۡyitGHD(- ]h"s4I < 1&ND!q4; PtX271]OfEKꕮ{ӈimpp]^n2szuy:/bX|= &`1foHE`20FzO}=VKRrwYm/3k1Nf zR4w>UKQdd4}tW|yHMax|ru:_* G Eq6<_|J^xQ͌*~ ؐ;ќ \e[g1/AD3_>?U蹱LRiE۪NUt=b$NvjiHv#z~gHɪs~nVu/!F + D8GRW۳31psQw&q &OmxnW[9MN-0ìɀ%WIRgNN2t+)X[ap >Ѭ 7  ,Lt-dJrf)G(vn§x BW֕תĜjFͮx"͐ SI 0+aJi6&tbu/\^>dt`+ŚHڼ8wg xFV?GCD&V7-#WtB/|V_kuMr5ڑjK|<0|!sa`0}(OֲT !WMUxe/a"`p &5et Ǫүԫ0 +EeD7\izc,V%D;,4CԿă-#ܐp!.,وcV5Q^֚dX-r%!(pvچeY !-.mUYkd?:<<}wL`u܆7s$ 553W'7iE\aؿ!^}٤{Yo8"[u> endobj +2504 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [205.71 454.02 345.156 466.012] +/Subtype/Link/A<> +>> endobj +2505 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [265.68 432.424 479.579 444.417] +/Subtype/Link/A<> +>> endobj +2506 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [171.824 409.983 267.01 421.673] +/Subtype/Link/A<> +>> endobj +2507 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [161.013 360.141 303.763 371.83] +/Subtype/Link/A<> +>> endobj +2508 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [290.138 338.546 335.01 350.235] +/Subtype/Link/A<> +>> endobj +2510 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [268.283 275.623 403.2 287.312] +/Subtype/Link/A<> +>> endobj +2499 0 obj << +/D [2497 0 R /XYZ 85.039 781.388 null] +>> endobj +418 0 obj << +/D [2497 0 R /XYZ 85.039 761.463 null] +>> endobj +2500 0 obj << +/D [2497 0 R /XYZ 85.039 739.701 null] +>> endobj +422 0 obj << +/D [2497 0 R /XYZ 85.039 680.927 null] +>> endobj +2501 0 obj << +/D [2497 0 R /XYZ 85.039 654.312 null] +>> endobj +426 0 obj << +/D [2497 0 R /XYZ 85.039 595.538 null] +>> endobj +2502 0 obj << +/D [2497 0 R /XYZ 85.039 568.923 null] +>> endobj +430 0 obj << +/D [2497 0 R /XYZ 85.039 568.923 null] +>> endobj +2503 0 obj << +/D [2497 0 R /XYZ 85.039 547.93 null] +>> endobj +434 0 obj << +/D [2497 0 R /XYZ 85.039 311.161 null] +>> endobj +2509 0 obj << +/D [2497 0 R /XYZ 85.039 289.965 null] +>> endobj +2496 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2513 0 obj << +/Length 3342 +/Filter /FlateDecode +>> +stream +xioX +X$g%S׵&AHIRJRfHIv@Xq7o;r;Q(][hpF+yw +3m' p8h$yu~z?0(,O(gcң7wo^l}|0ʚ|k181ͼwoS?Q±Uvl7IF ?Pv+,Җ>X7Lj+~5cI vQxV 9|Qw7 +9"kdE(_MɞxC2]N2.e[BU49 WR=iYeѦ8CЀ55_16m|PPSByx_+@]c&>(um:ƀ6'zTF8K̇oFh1+(Pԭtd2KwHU>VU)>F=ACZtn + [;nyΗy]%l^5Q%t ga1,t%Mz(O -Q X7 6VpS܁)N=pk#d]2uSGfĦ0xmū_"Ɩd7pߟQ [ gUSڠ-8(花:{\"-K0@IsAC+EA yK|ٰCfb&^`Xt`/K(V 6`+()z^}E3 %F[ +`ww7aMjƍ{ +w>phloLwc[ Vwt. (`#ߥ'5 .v %s^M^o!kZǘMZ?h*6%Њpri!c7>8Hm]nu:~/Wѿ'[ZҊas `0Uw7ׯd'^R"@Hgr]"!2b,k.h g?TRy-$c` HTGk +USy){^ uMs\jDCHw3α3E4{he_'#kӥ*\ωJt] VM$V"$q+ +÷l`"W^SVR)-@[͡v)Gۤ&WM.?I}dC }RB9.VdR&ZWP f +XDـ C;=rIKIJ %JDuP:prjh+POw '"詺ۏw7soxN C8N |uc2e#S? +*Y<5\!yvم~ژ"@sJ"Rl?>b +|=6YQ3=+>#!TL3Z֑s.PçGp!e?gu* 8Cť,D'`ʬwsm8V\xS*GM]f%h9^n]E!2 qLڳ> endobj +2515 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [470.223 578.412 512.306 591.313] +/Subtype/Link/A<> +>> endobj +2516 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 564.863 187.762 577.764] +/Subtype/Link/A<> +>> endobj +2518 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [476.617 434.366 512.306 446.056] +/Subtype/Link/A<> +>> endobj +2519 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 420.817 205.581 432.506] +/Subtype/Link/A<> +>> endobj +2520 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [228.437 420.817 309.672 432.506] +/Subtype/Link/A<> +>> endobj +2522 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [194.71 157.41 275.945 169.1] +/Subtype/Link/A<> +>> endobj +2514 0 obj << +/D [2512 0 R /XYZ 85.039 781.388 null] +>> endobj +438 0 obj << +/D [2512 0 R /XYZ 85.039 524.101 null] +>> endobj +2517 0 obj << +/D [2512 0 R /XYZ 85.039 502.905 null] +>> endobj +442 0 obj << +/D [2512 0 R /XYZ 85.039 406.548 null] +>> endobj +2521 0 obj << +/D [2512 0 R /XYZ 85.039 385.351 null] +>> endobj +2511 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2525 0 obj << +/Length 2074 +/Filter /FlateDecode +>> +stream +xڥX[8~ϯԇa TLJjEɰ%rLM@"Uj8Tg4[4Mt +&S ^&Wov$jC,՛ϳ҂<Ḇ fv翮gV7K^xd77s5CLSPD2 +0E{R^kֹ.l7vzю?b5~PU/fszkkV +2HڪfO^)ސioaŹKp޸GL/)uܰ^.ޡuӣ%kf8KpGZ$Cf#?r~:咃pu>R)OB6-p LNPOHCx sb췞'`zmJAJ@$ѻҵ2t,SttM!s4%sMYiR:)fHɤ^n"ѨEc ЫyIktX +JxP סR>Bpysǃ,TAsȅj:(fL;g( 1,ىvnzLҎ mҴLWG!or:]@3o  hya.9vyuD@ą |,b_Xpm[QfE@ +3I UER,:kK-< ?^dݢP +yFO:DH \3@^mrptR6ͩb2e`5=Me@YDS1ֿ֚N0 s/ǡ`"W%s>vTEH'mUx|adL=N +u!AB; 3Gx0U5}fh\L3|LODּjB;Ad+;#&B7U +@`WU]-t`: \eIנG}㎽E\Am@i/HIC34Y#]R*E27y(pg Ϟqyjp#d;L]SD 7YC|$`_b~YiSۼɰT24X…RM3Y>]3RsTYq.WğPd'y NAvDZ6^aEzJ>:]E̺mЇ1v!c'NAKȄo5ʳa[(Ǚk14IգiIԯ U==-p_U hw%+U8 +TXjCcUfEpkSf>  L PIC\"f"`c&y̤i^(WT8ݭ2诓 ۋD$qf}!<;|ﻞ miy=*yD_*7endstream +endobj +2524 0 obj << +/Type /Page +/Contents 2525 0 R +/Resources 2523 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2529 0 R +>> endobj +2526 0 obj << +/D [2524 0 R /XYZ 85.039 781.388 null] +>> endobj +446 0 obj << +/D [2524 0 R /XYZ 85.039 667.6 null] +>> endobj +2527 0 obj << +/D [2524 0 R /XYZ 85.039 644.282 null] +>> endobj +450 0 obj << +/D [2524 0 R /XYZ 85.039 644.282 null] +>> endobj +2528 0 obj << +/D [2524 0 R /XYZ 85.039 623.891 null] +>> endobj +2523 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2532 0 obj << +/Length 1594 +/Filter /FlateDecode +>> +stream +xXKo8W!23z? +6iM{Js%JK*%5v.v/k)r8f8:]nKQ/cw'rq4nع]&tcI2̞oz},X( zef>z|r݋=kxnpZw׃Sv!D'~?;/v7A?ul%qwc8Iҝu#otXqQk~Wjѵ!q#x6c(M^dW5cwCf?Q܍ أ1k)kNՀg> D>by'yupOvey]q|3/ԾMQ7$$A!'\6 8F@\ ޗw'sY90t6qGʼny+q6+ܒq~[0Og(k1LӞY hΑr5?"q HZc5[@caTG?y3 yV5 +Lx[- )rseQxSV\,g%9@iG8"-KmX;!BS+}eo6 ڸbWزuR3TuְIc Lp$>v#om~ H=}D!Cz;EYOlMee*st=O08hy]]v#$:A8Ԍ~td'5nUGVT,㡃)2hT*L$ت.Bxv(v +&)Ie;ƾ'vf ߝHxĎߕL3Z(DUj*9WT(Z٨ +L.FMd RqF[GG uU .t@՟(77!bUfd qoTL}~@T|z[2]85fεG~x f7-:bF34?cIk6FR5\@TPQj_;U WΙQ~C}-H;g9KNi1aض"X(Œ-IKrYZ\E9XYqvW2D-RjPVM^>T[?$r<>0Pᵙ6^pY7L;b]- s- ut )w*N}"rךxP4[oI1!endstream +endobj +2531 0 obj << +/Type /Page +/Contents 2532 0 R +/Resources 2530 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2529 0 R +/Annots [ 2535 0 R 2536 0 R 2537 0 R 2538 0 R 2539 0 R 2540 0 R 2541 0 R 2542 0 R 2543 0 R 2544 0 R ] +>> endobj +2535 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 577.023 352.054 589.924] +/Subtype/Link/A<> +>> endobj +2536 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 555.113 176.46 566.803] +/Subtype/Link/A<> +>> endobj +2537 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 532.598 210.278 544.287] +/Subtype/Link/A<> +>> endobj +2538 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 510.082 190.036 521.772] +/Subtype/Link/A<> +>> endobj +2539 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 487.567 187.278 499.256] +/Subtype/Link/A<> +>> endobj +2540 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 465.051 185.157 476.74] +/Subtype/Link/A<> +>> endobj +2541 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 442.535 232.763 454.225] +/Subtype/Link/A<> +>> endobj +2542 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 420.02 213.157 431.709] +/Subtype/Link/A<> +>> endobj +2543 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 397.504 208.46 409.194] +/Subtype/Link/A<> +>> endobj +2544 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [249.04 371.394 306.851 384.295] +/Subtype/Link/A<> +>> endobj +2533 0 obj << +/D [2531 0 R /XYZ 85.039 781.388 null] +>> endobj +454 0 obj << +/D [2531 0 R /XYZ 85.039 653.944 null] +>> endobj +2534 0 obj << +/D [2531 0 R /XYZ 85.039 631.228 null] +>> endobj +2530 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2547 0 obj << +/Length 2685 +/Filter /FlateDecode +>> +stream +xnH=_aeX P O:׍q.qZL`Z=.pb$IZ?EyM\gL֕о{|̄$M4ER=SUk'woo]t-<] ҉f Nz6/ wO8Hfu7iI-VZ۲j3ˊB묔?)B׺8Ϻ*t;䐊=)]Vo2{|>i4Nx +ձ:@,rM9oK6p.ȏq|~Z+]*CVAqO41o!AC;oWءpV.09z,wE#a?`ճC/ o؟Ӄ=׎.vB4 m!:rXr?)V7JDhH5txB#tC1.W} bSzV#p e$Yjכhُ@֮{#aK`}5pT_g.7 r~S"NL?{gĂȝp1I7y\۪ [;e*S>q=IΣ'`}Cz_= RA +HP_|-~]V [#[z>5ւ"7gY͈2:JK8btw҂|'(rR8~px&)O;Y3jk.R+l8!(]6r@,DVC4FbUc4qrQhpMUtT9ʤ͆?]>eZWx9 n6z8bU%DЀʡp3i$bԆBz#dkŏ -jBSɸr'|X3  Tnendstream +endobj +2546 0 obj << +/Type /Page +/Contents 2547 0 R +/Resources 2545 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2529 0 R +/Annots [ 2551 0 R ] +>> endobj +2551 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [367.79 127.787 439.883 140.688] +/Subtype /Link +/A << /S /GoTo /D (passdb) >> +>> endobj +2548 0 obj << +/D [2546 0 R /XYZ 85.039 781.388 null] +>> endobj +458 0 obj << +/D [2546 0 R /XYZ 85.039 477.879 null] +>> endobj +2549 0 obj << +/D [2546 0 R /XYZ 85.039 454.562 null] +>> endobj +462 0 obj << +/D [2546 0 R /XYZ 85.039 303.477 null] +>> endobj +2550 0 obj << +/D [2546 0 R /XYZ 85.039 282.887 null] +>> endobj +2545 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2554 0 obj << +/Length 2542 +/Filter /FlateDecode +>> +stream +xn8=_adF^QZ*7Mw:Hnb t K,i$:n~υeGN,6Esȁ?1 +4dsV03!o;2W_Hw$;r|I uxytZn2ooތzlzxQd0TO`4 +afMĈWX)/K.q;ghЮwݪY5G׷(D3(ʾ%nKڬU^ (} +iNʚ \dؘZqx|=*т{,1\r! $/I8@*Yͪ05l(]nR'·dj$n cD" O!ezPR"bK<ߊ˴7|ɺa8We@,Ih/R^ q3sIp|VFE *b/[x0]gkp}6'Hk`Pu2PRkX/E5ZShY#i:C>/, + ~yڑR[uj'UdLmwj&]/'~O7⢨v$yƵN7z,IbtVs+˚{v]޸҈jڗCܶI/Je m4{C|yo1̐jΪ.e]yGEYivvM(4Ɵ9::&#`$,v<aw0'={ʤ a|h{X FW)TClq /tTb{%V,ImJ]sGY )ʡ +LDGX(b&@@^?8]>rQl7EC 2b Cq;p!q Yz/$#hc8pzCݻȏė^g7fɨsBNpbWz[CF/[OהĤ=5 4}lX-pP >t̟5!17'U\3MڷO'MV|}llߺ׳%Q8LyHnO;AÙ^ĪY,6NT|sVR}km{N+u)wzwuܪ[H#WsLvȲYAQ2sq2":ڭ3R'G HO Cұ]?А%^?L5w M7KRL~`',C2r zf}EFSr)7PLYݵe.Mn8瀆sF! 9(WA@0Y]s:W2M +J9@y@t[~N.$p"t4*s A|FbDJ˾t81ϵ^#4oE?6yi#[疇Tcyi‘8jSލH]>aKL i 5N`];j<%h-oykGQo+f_q\ *JcE%m[uRVS_o_gfYjn򻧅"@Q2&K +{%O-2wA@ݭss7Xr/O7#4FQ|Ӧsadw|fw*pe^d'8 tCK %UB_(憽3ڽ+-ELk( +.{# u~&/.. +N?jV=t`#w%ds x 9R(Pg?p3Fsn *O3U?.ϣc#wn]&h$"k][z їsL9p;;?endstream +endobj +2553 0 obj << +/Type /Page +/Contents 2554 0 R +/Resources 2552 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2529 0 R +>> endobj +2555 0 obj << +/D [2553 0 R /XYZ 85.039 781.388 null] +>> endobj +466 0 obj << +/D [2553 0 R /XYZ 85.039 574.243 null] +>> endobj +2556 0 obj << +/D [2553 0 R /XYZ 85.039 550.925 null] +>> endobj +2552 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2559 0 obj << +/Length 2684 +/Filter /FlateDecode +>> +stream +xY[o:~ϯ0,VjRnIɦ.>(l%$4~Bʒ؇@M p"GQBţ0|s"F+ys" +1Ү|vx#)Xģْ_˷wD)xX:zzEq"iǫ'W@>U 'Uq4zpe6'WO>szĻ:^z! pH*D!dxx վxO7oMlZ0U-r"5?O pָHӬbtMY=lXn#rҪA<ِtZL67iQ.c;2n dU:GH_x%P>b"H1e n]M./E:uSeUx<)x` +asZ=ٟA94p)k $/_Yxkѻp6MZ*ML5(߹|8RjyH[)-pukB\!͞kZ1Gr=vUdOu <@S/Rm׽$') bfd^[ 0"k}iT'y,1UExf9%h]8U՚u0U3YŕIQ`$Һ|^1<C`pI"NyY%L2ebcB< N%ʷC‡$o$m2ǹz'tOXIxt\&Q '/V}.Ǻaqq9Qǥk ]Ysk֌IS#;;cwU B!ݻ):&<$)ygN",)7a\+WGa׃qP@l,7Y!h4ڠČ#&,h +iȍEd(tel$YK.K+V6.ni uw"U`%7{pđ=tOtHm{%:NR]z({{7C${7VzҍM+Em,R\!(QYS3^6uc[o.P/\gs{IUfe>5[ +N cʩϧlT +L4vv`;JIj-m \LKkd oU(#(q#`> +Fon kγ#2|~L?_A`7Dqz>*!{f+?@Z=2N8۠ZMW4Kt9Ɛc8;Vho:޴T,wޖm/5WB3]蟐4C~Z +N*XgQUHxOZ,xX^)Xeo ~[Ns n)^E ,Zp_e00^nTRl$x_N_AP̣' l^Z.0 ;܇ٺ8#5B 6j6M@75ױ /iNL^ە_CB|-@~঴~m{*[0-x( ٟ6`bbh0 G Z)ta(Gn`pʹBU`bY$L@T+sS`G\ +J%j_l7RpGB j;'zlVwӛk35#lK|WsԀ~cI#\Ym _ʼm7V.:[EA}5&|g+H2G|KeE ? V2 VKc\vΓ˧b~/'xm  +2)z/?m~]0=p~~+D(rƇw|wendstream +endobj +2558 0 obj << +/Type /Page +/Contents 2559 0 R +/Resources 2557 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2529 0 R +/Annots [ 2561 0 R ] +>> endobj +2561 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [220.025 574.596 328.684 587.497] +/Subtype/Link/A<> +>> endobj +2560 0 obj << +/D [2558 0 R /XYZ 85.039 781.388 null] +>> endobj +470 0 obj << +/D [2558 0 R /XYZ 85.039 309.692 null] +>> endobj +2565 0 obj << +/D [2558 0 R /XYZ 85.039 289.101 null] +>> endobj +2557 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R /F73 2564 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2568 0 obj << +/Length 1980 +/Filter /FlateDecode +>> +stream +xXo82PɢHQ8^mwq;tA[,zl{f8b'J! |cXz>OfQ<dzlw6 +&u |v5O\VSUe^n pno0"<җKFݕݟӮ.Q(EI\юNe8kvy&TE.苍ZLǃ2gi}MUGd/X Gy32H(Z +wq/Ϣb a@L þp>FքEx!"E@?g Wi^L'B_ԆyLG0/AG>ֆ9 Usi_ybff>(/(B1/`څ<T1205PܡFkUAi\LFŘҠ `r`g&UR2׏!{ [.pb:yN*_= 2,=PdG xXOy s.L kmzؐєNdsS|`UoS )J0*=|(orxhbUݖ(Kcpc#6ST x TPEi Ҷ=˫5V$a-4?֜!G10`gaM5i˘9K2<0{͡jC'aqX+quЀzn#6rQEj-âcJuYYEEY| /a~8~MHD8cyMJ)ȣl n N%M\.28z IhG`ڡoM0LwC")SUBx6:񶴐 zFf8 {ZшTANTZ;I!c'툦RΔ=9y:Wf-viRjr_ BrLz㋻$K!T-roi3 |-OQiIg܃^6IHd%Az/ s0>r\G(4[bᆳ;$B͆o@>:knJfi6뮢dnC[qx՘tv`M `_> endobj +2569 0 obj << +/D [2567 0 R /XYZ 85.039 781.388 null] +>> endobj +474 0 obj << +/D [2567 0 R /XYZ 85.039 383.38 null] +>> endobj +2570 0 obj << +/D [2567 0 R /XYZ 85.039 351.854 null] +>> endobj +478 0 obj << +/D [2567 0 R /XYZ 85.039 351.854 null] +>> endobj +2571 0 obj << +/D [2567 0 R /XYZ 85.039 331.326 null] +>> endobj +482 0 obj << +/D [2567 0 R /XYZ 85.039 234.666 null] +>> endobj +2572 0 obj << +/D [2567 0 R /XYZ 85.039 213.773 null] +>> endobj +2566 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F72 2435 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2575 0 obj << +/Length 1515 +/Filter /FlateDecode +>> +stream +xڭXKsHWp3T-a8(uR9$9 @e2+=)֖ffwOQLeI=qA]W SYR00 ,&O-gzbŏ,7_j:TmMwW6׈*Wgw5U?Fs},͛;ݢnL%E?NLz4)ۉͨlZ?'EيUa9H8J)0:Wq_oDәMVN ]B*_ _%e!LJO +}Tba(?2]+H]eyyҔqTP2 2SbA`jMPG2ҏ8],rXp Nf+e`@ιGa8 0QԵچ& IfwG<}4 s0 +2WfjF=h];PhHbۜ abYa3RMēdjvGBXInYKYƅ8W! +ũ8cۥyȹ&w""e2QdUA-uь{ +⛣a?A Z((5Fzp}u1ug<ޘ܃=fxA*a(##8rj}t݌/ݦgKg׍Yf|)"? }l֯l\x/J(Ь=VYY}ۧOu%?I']iy\MHl:_a+B_=髫)w~gyVI>?)ɉneu?wmӮa:=mE6R%x4ܳc] Yr> endobj +2576 0 obj << +/D [2574 0 R /XYZ 85.039 781.388 null] +>> endobj +2573 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2580 0 obj << +/Length 1873 +/Filter /FlateDecode +>> +stream +xڽXn8}W2Ivn46.vmKRbKu;R1=33g.yw\sdˑ;#Okc币Sog7{xvG*?f_҂fYFb*"˧i$ه+ ,gonΧ?fG糞rT ъѷ8C?\Gxcx)_:{1}nw95U{|@Niq:Oluڔe)/|+yU4Kw-eyYw}7K~sO#[Ǝ+:'Bn(^NQ_Z/8Q5E|jB_"뱩YɪJ]l ++a X^)Uw3i&K`V-qX@Ysq;qw"EƶFi^P,2-$U&V,_Z S0Hn bZcʼn[\GӘhFU/r'݁:48/SKJm}ΰo k߭w=e֢#(XPV5Zqust ؎Q7909$t wC,~]Rp}2Gt#˞k-ITBN%uf1qVW/@*,taA#:VƗ^a$Lsc>37JL- W6\X|QtL5+=1 |'֑`򔂹>@Vt[D>>XOEkOкgZ- P`raLZwqjIiH\tIOiP5.-H<O 7L6LO^^Nxlk&M#zaSA*XC, 9ȅ.#iwgwʐ6dB?k¨bBNߎ[15_tv"1v =>+eݝs8c8ʲj <Ɲa:V{+1!(4c[)ߚQ=Wi>e5U<.įѸ4>kSv UiB7G4WxV#-r6LE0& 52L<+M'hmĎ#OHvK%>Nl/vH^F.J໡G$wU5b[bӢ 0~²}n^reÞǟ^IRwc[f#uXz,mⷮWXw߶?εyCUTFȳ Od G$9[aA_Q0h|6]]o=r@ Lk k]ܾo1#&E/",&:eTB}ſdɞuZ*/d y; +ғ~ީ[^Ѷ> endobj +2581 0 obj << +/D [2579 0 R /XYZ 85.039 781.388 null] +>> endobj +486 0 obj << +/D [2579 0 R /XYZ 85.039 666.966 null] +>> endobj +2582 0 obj << +/D [2579 0 R /XYZ 85.039 645.769 null] +>> endobj +490 0 obj << +/D [2579 0 R /XYZ 85.039 548.806 null] +>> endobj +2583 0 obj << +/D [2579 0 R /XYZ 85.039 528.216 null] +>> endobj +494 0 obj << +/D [2579 0 R /XYZ 85.039 444.234 null] +>> endobj +2584 0 obj << +/D [2579 0 R /XYZ 85.039 417.619 null] +>> endobj +2578 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2587 0 obj << +/Length 2773 +/Filter /FlateDecode +>> +stream +xڵYYoH~Dfط$f8ٱ3 0;DKRCRV燐!v fU_R"~`E($b +[J Eho3+7}J~ś۫WuЁEfq{O?/M;E]̛kyYᡯHKcW8[&~d5ȱ{<uhS|Gb ˜4o|DJ~jXP*M D]֊4lwY|(=Iv!a8`MѡO,M(3 XgH6dB t,ElNWaKw|#]ZC U୳ +k#ᵸkoC-o +sRxY܂'X +{\N^u)wO,Jwlb_ +Ki4" nJa |ژ*hQٓjmd]ݰN`CT?V$~h߯3Xl^ +|&#_bel4~yus6 +:6}hUpó},8IB 3OuMZBty(;-/845<;j"xaI} T2WI @G[h5TŏWjOk;0XdܸI]Ff40%W!E9P ـRtx"?d -;;buxip%x xB9`M|&7+XtI7n_ɱ~tW]p=bb6`, pngÁC+Bt"/c3q?*@@%]VMޔ485B5 8oPxp1oe4r#^}΂;ݠB7ɜch$+kqx%r\@A4aBTiX UW@)IgL@"4fc9#_ _V^> 8<gqꆴ Џӟ2 YA \߆t}=!D+mrn߼X`p[PSlwhhwXBpwH# !7O^j39nMN\vusQ]bsB U.8x6ܡ_rぼ%cXx#n{)'%@8 +[(ōJloG6Nfi+WLƂTV0]#8umc  DA*,b (cjD] #?cx8fT{1<62& f2cϊk^C)4E0yܑGO]uBo+jHç0;\sU^&Sy583_ܼտ-xZ#?5]#R?Cqr" >\!k{Ud|}?dׄzR +&a/%k. إg{^)1}FiypIT\ 2!Ul0 c*3S S+il 1T Ş.E@ 2Ӥrǵ =)i{pQm [Wt&%RQ)fG \];g| +)/$=m>c+ʚy\VEJ҉>UwG"0N~p)!hY/Rendstream +endobj +2586 0 obj << +/Type /Page +/Contents 2587 0 R +/Resources 2585 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2577 0 R +>> endobj +2588 0 obj << +/D [2586 0 R /XYZ 85.039 781.388 null] +>> endobj +498 0 obj << +/D [2586 0 R /XYZ 85.039 761.463 null] +>> endobj +2589 0 obj << +/D [2586 0 R /XYZ 85.039 646.155 null] +>> endobj +502 0 obj << +/D [2586 0 R /XYZ 85.039 646.155 null] +>> endobj +2590 0 obj << +/D [2586 0 R /XYZ 85.039 596.697 null] +>> endobj +506 0 obj << +/D [2586 0 R /XYZ 85.039 353.221 null] +>> endobj +2591 0 obj << +/D [2586 0 R /XYZ 85.039 328.669 null] +>> endobj +510 0 obj << +/D [2586 0 R /XYZ 85.039 177.406 null] +>> endobj +2592 0 obj << +/D [2586 0 R /XYZ 85.039 148.002 null] +>> endobj +2585 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F65 2099 0 R /F56 1642 0 R /F73 2564 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2595 0 obj << +/Length 3914 +/Filter /FlateDecode +>> +stream +xڥZYsF~ׯP` c\3T"{-mUI Q -k5lmd===}|Cu?uad4Sɲ,:Δ4Lž77g>$\Ea7s-xןn^,1RbYsӧ |b kzDž_/}\,UzndB۷qz36- ce?]^~;Rea4ϳpϢPƸz}v}ab9Dxj\ ]M;u>F3Faë+y Y8veߣ8Z0m=鶁Mkn"1*̰d, +#K^Ϋ|$cPy QyҾ1/!l*7y;{%8hb5UeH9X|О|h,2|+ B;4M۠üp @Oqp9,4PH2k;$lh NنHbupEZYf㎗\5< +(0@g9e<}HZ L 11v<*B)<UVg +3N +scιEʥ~ZL,9ѳ5 +Ԫ3xY"<|uג@I̶=ZVX5m[vzo!gmY/^r‹Jh|V(1<;@?"=f9t =Ȝv-yGD!dۇ~jpy-\.t@\-k΢yHN +_Ͻ;I(I`%Y}!h%M/ |!ߠ˷&y+˔2bo6A*J-%SN#E$&#{8: s'PeXs6mML2i]&JGfc"FC^<3':o`2d"؄9i$( Dp7Jph2rY! 3&pub6G9ѨXEq˙"/h#LzP.9ߙQ +w&P!.='0.V~XX6sMRRw5d@~̾ +4lXrWc¯ ,4`;y84ss,LPa27a2~>׻ +J9ii!v?dǠ9@y0W͇EQX:k:Ƌ۝ɀu6.|[谀ɒ݁>xcaSPjz=UM +š&K&$ +=-[7s3@/EP"!`i8}ϣ~Q10rD-!9J%o$eFpUSn={u*XrMoנi5؁$(ps{_A/ ! ^>1c?64n}B)6Ɂ=@y;#ENi[qU_4 ֏Gˌ-p#~š<*I),L}XU7dH:m~Q ~G$I2ɜ<(ÜC|ƞ1?g +Ll)tN'Xd#[gNiamD6D,^g"xqoാ| s2S60F_B=sנ0rᶒg2Ϙ}r?fESHe| $fɅwQ @q#CO/RA7 6g& ĂŝFAM[t|QՂcs< ]U;D6jK45v:کɅ%$޹(7M?ŀ\T gMT(edb-/$6h5% 㐦Vjrf'R~)Štt!sutkT!K8B*͆0q;at%fa.k\iJ=޼87=tNce-?ÂScLhS{'̲ǴV iALc:q endstream +endobj +2594 0 obj << +/Type /Page +/Contents 2595 0 R +/Resources 2593 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2577 0 R +>> endobj +2596 0 obj << +/D [2594 0 R /XYZ 85.039 781.388 null] +>> endobj +514 0 obj << +/D [2594 0 R /XYZ 85.039 555.81 null] +>> endobj +2597 0 obj << +/D [2594 0 R /XYZ 85.039 526.406 null] +>> endobj +518 0 obj << +/D [2594 0 R /XYZ 85.039 349.225 null] +>> endobj +2598 0 obj << +/D [2594 0 R /XYZ 85.039 330.353 null] +>> endobj +522 0 obj << +/D [2594 0 R /XYZ 85.039 96.185 null] +>> endobj +2599 0 obj << +/D [2594 0 R /XYZ 85.039 74.989 null] +>> endobj +2593 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F65 2099 0 R /F20 1617 0 R /F73 2564 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2602 0 obj << +/Length 3356 +/Filter /FlateDecode +>> +stream +xڥr6_5f}Kt6vҙD[SJRu=7D!u?u'ad,W*~])Y[\>* +^b[׿,}cM>CϷ>~7^xˍϷu| ,x"7wqX(&qAջwx?~#^BSOЎBUכ8A\Fէ;4<_ : u y>2Q%L87G*cuBIg@l=v/`ݶ, L g^}9Z'aB\3< a%^sSE,5lG$NdDx7:\e׸%fSwiA'aP~ J͗gI8S}-C#`!ӰM,-7{µyKȍ<saN%.,+eWaD+/- ʭ@wC!ÚgLzO. BS$MKً]D2Ec=WcUtmq1MÜ2* NByfLvmk1.56}37,qnDu!2v ,Zq_PډnnDrNPi̪a]W] 83 $gE M~MvW {<W`)y!_7ϊC"pZɂ=Ď{J;p Y7uT<4MT&6Lbt[Ɇ)ʙ [zҶCE_hЗu# 0Sq6{\ذ@0N»"sb1ݱ.u™0g`R. k'&|`RijN׫47=zdA NqOSSrwoz >&" %QMQd`硶V{yt 뱷 +F\6MwSTv]'Jew2,$+5=5)g +nZ PsUKXk(. B9cR Hcv`$A|ٌ g4B-1H m}{Б ܽ8k&ĆZq5 +\]/s3%IkɦSlOh!iO 4T<|@7xl6`}CA2RphR]Lg)!pj]L +-24P;&QU^fFP!#%et$g(y-#+ 7o`˖&}[*41+2;OxɵaCoZ] +&X`E&瑙Dj㓃V7>.^4jGAEDlk#;=ŝ1 OU zUze7e!8xVV ƿO[e@kN"8tˍ1ЫbCSayʎC 7!8iYə&5|i*DeI[4BRNJ6`Hۏ6iVs`5.-W+n|C,TlDE-EjIq>aA n })gy1Ng1$EAl?Uv6 `#z!=xs[s,vaCc`<=8*Qaج(8h]]; K+?Lϝd1 1Y10s%^ak#'ѫ_[ M04LGPJ쟼dx6_2 Nic)ޡ udWY"\S)rɥ$QSX*Oa[*̕44~.r%'AqVKޔs<:GwRңZM?1}}l!(FB2lܓl.rJ,]H=a|\%C/m`/yO^QcV9G QMnua+Ib;#SlnKF{yҕlyZf9Ģ3q;a#}#]SZwRk'Ųˆn'rLcXC.],;a7瓹endstream +endobj +2601 0 obj << +/Type /Page +/Contents 2602 0 R +/Resources 2600 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2577 0 R +>> endobj +2603 0 obj << +/D [2601 0 R /XYZ 85.039 781.388 null] +>> endobj +526 0 obj << +/D [2601 0 R /XYZ 85.039 625.671 null] +>> endobj +2604 0 obj << +/D [2601 0 R /XYZ 85.039 594.146 null] +>> endobj +530 0 obj << +/D [2601 0 R /XYZ 85.039 184.842 null] +>> endobj +2605 0 obj << +/D [2601 0 R /XYZ 85.039 138.111 null] +>> endobj +2600 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2608 0 obj << +/Length 3479 +/Filter /FlateDecode +>> +stream +xڥZYo6~0eiYk}H&dvvA´%GR#b,V}Ulu?u^QP.Y|ΔP_e`gfɹ2.ϯwDse_xr^(-Wy^,~nR->xuɭ_/WP̵./Z&g鹼e/޿L'l^RSd?| @ه`Q+UDJpUk|G,G,Lgp9Q2*4JQQ ҉Ma kܓG.,[7K6Veq!\ ӌYT\hF\o"D_`{]ա]ՠw~w(ˍHzg;Aְ~GmUQJ8R3:)UPhmr#+x@ha.mE2W߿Z/l-.E Gqene<yrEc3Ov UKb j\jXV@Qw=׽Pb Y!sj +$꠱IN ah}lQ%ݗSei'&7Yڷmm\|UA7IMq*QoIk|]﷨ :JLP e* ۦhN:)n$J|4@B1`rQg. +{'»<`(qɞLAGxb*ˣd5x$"IM] +̋bԭ=D%ZJ5yF wIpPլZK};xpG? rIo'+/ tm#F 4*Rcg A,=y8CUlاy1ռ8 0y7;9#UxhB*g|JacQMZ:(u6m#Ps=TznRxw[ѱc֩V 醻BZ#qgԎC̢4KZo壭:PgQeFzzH'FT?uRs<(ft8:4hu`A%]Q Ɋ# ̹l_^I<,F8_Fs̚ Y8:>x ×Cĭu@XE&-XS#x虓xA%tFo,grC`L^&A\,(-V KT {j  [;s-&$cC9HL/n\Cm5q7;rx@xtnfے7ǃ kZ +4G蜛l|Pvw5~_D a & f\Q Kirܳ6` N.I'[yfI j9㰫aFZҦ -U'>JD+j (佼!MRAM/nu3஍A~ +GKeQ2g&:4l6q#32-Gv[ݶ_8`^u1CX)СfT ^J 4kqE%+ϔ{kgֺW*Z>5:;8X[&ql8f̌A7lwsF9DI6 aa?3໾*}2$&Hl[hԴF$sjGN +[8bqZZy#̙A >\?9HÞPI[4WTH 'u( {4yS?(+ д(SKqyf3^"h?-λMד NJd"nt\%H grt2Z$⓪о`f\X[g( ©#W(}q iswk35`Ž{L.)bms`eÝE{t S\ͪX-" (kR[ jL'8 (e1ZO<~U6%Ll?@!cKl2E7h²10:nk)2:[e(!Xb\$|v{yp,{w"WQt#T?7-kL<|Fyx׿E:s[yTP=ߎendstream +endobj +2607 0 obj << +/Type /Page +/Contents 2608 0 R +/Resources 2606 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2577 0 R +/Annots [ 2610 0 R 2611 0 R 2612 0 R 2613 0 R ] +>> endobj +2610 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [342.345 720.288 409.913 731.978] +/Subtype/Link/A<> +>> endobj +2611 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [452.526 652.542 512.306 664.232] +/Subtype/Link/A<> +>> endobj +2612 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 598.345 206.209 610.035] +/Subtype/Link/A<> +>> endobj +2613 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [427.522 544.149 512.306 555.838] +/Subtype/Link/A<> +>> endobj +2609 0 obj << +/D [2607 0 R /XYZ 85.039 781.388 null] +>> endobj +534 0 obj << +/D [2607 0 R /XYZ 85.039 244.172 null] +>> endobj +2614 0 obj << +/D [2607 0 R /XYZ 85.039 196.836 null] +>> endobj +2606 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F65 2099 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2617 0 obj << +/Length 479 +/Filter /FlateDecode +>> +stream +xڥSMo0+1!4tJ(ll`gP/<3 .ALĸJ6)cdOp5E;%%> endobj +2618 0 obj << +/D [2616 0 R /XYZ 85.039 781.388 null] +>> endobj +2615 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2622 0 obj << +/Length 2838 +/Filter /FlateDecode +>> +stream +xڭ]۸=b> ,)@P5]phH^V"K>In}e˹Xp8&_|a,CWj +?="Iu& gvuRads0* U* ~}썊TV o7 b.iq6Eq=.qU0lKʂ:j +~1CkǓoGI_L0O GY^Z U_#Td aÎ'#~a*Ⱪ;_q4N`-RI{m0u?"C6a5,T|Ūϋt +]]"J]IgKh'/niDҳ`)J:+ I@$oZZ߾i6 woS/t,@8ލD9!,r/||$f]7 +50iW"goҕ^E& d+*NdhEmצ1邏$Z^zVpzW5efV> Pb5QB!,,{L6 7/M"a$'+W󆱠&# WbF7~$6$cUX}&^e}JI.2wmgd*V3=#v,`$ړ-|?٠IT*|āa e8X2jmeDGcyrcc"pU u5@>}]xٓΧBWrBQuksGa@_&/ۮq![hdBy:x 'יbEB("t惊bU0m Wku넯(5RMvoC*gȭ lM}G +{ڡ"WP-un-J, +#R81!,9YsCs$O\35rdGB-%gza D0fU`8!6QS%[rs<8_gB+Få̑WήIk Y@&+g)+;I!HΘr81̂/S^+(wMnkk5Es>v=DQM/[|Cwo[>RENEoF!> r+~M͓댜,~8/P5%3avd# Wɒ⑗^<#)3G/9n22id8fgp9(D~rjO%P*ܞˎjT)sv+$~_{9$zh5Jn+;S'N1 G#ɜ(=6R^+%ee~ 2MZۚpK4HRiŁF q?7.^lcp^eYH^FIe%*Bh'bgI{#@*WaWsr 95j%oΤaG( EpM$qZ`L]og~ e)vele ȍ(p9\o\]fDE];ѕ.u~BRH ש3aEkSZc9Ef3(,TrGnerzuD!GqAV8Ce5朹$E%J+%ϜT: u "">|Fǖ-/)gWNݕE+O)!:SH:C^1&$.j +E9PWg[dPr e $a3`׶_xy=6&n}o /\bĤ\z/F?тiR)Jߑve.N +k3-)Zp_X87Xz8ۖY>19lGj8U\A]M\}xMN&Ť'BAH5a0:!Z% hˮz /~gBJ@`.޹T|W^(:P9pb6n,rHhjb3q/3z;H}Α +~*pD$7q)P翻.$_B1]=Ke+DW^]+檫Fl5fފzZ[l%zƏ$86bZ ^HKcuiyU|E<y"hQ!8S|@HEE%W{d {9Z]<ΰΟH:d:$0K?8.&'< 5]ܮjZ1(;:>|{;PuUN(ɻA~AF!v3N7+yA*y<nZA1WMb7(~MO}-T=:WT;ylGa rtb^U85NQZJeӜ~hendstream +endobj +2621 0 obj << +/Type /Page +/Contents 2622 0 R +/Resources 2620 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2619 0 R +>> endobj +2623 0 obj << +/D [2621 0 R /XYZ 85.039 781.388 null] +>> endobj +538 0 obj << +/D [2621 0 R /XYZ 85.039 761.463 null] +>> endobj +2624 0 obj << +/D [2621 0 R /XYZ 85.039 667.089 null] +>> endobj +2625 0 obj << +/D [2621 0 R /XYZ 85.039 390.616 null] +>> endobj +2626 0 obj << +/D [2621 0 R /XYZ 85.039 367.529 null] +>> endobj +2627 0 obj << +/D [2621 0 R /XYZ 85.039 278.703 null] +>> endobj +2620 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2630 0 obj << +/Length 893 +/Filter /FlateDecode +>> +stream +xڥU[<}ϯċ#k.< -]@݂MK%όMKҢJm̙ ~<4e2ӌSe X{ *GOWDќjgMV˳Ջ(R.hiF{{q*9ɇ+;}{p*)ygn%HJ$2?[ :`TY<@iI~]ŝy-+PD2ejN?F$Pjy0M LU#.q&-JiqY(CF"#F=T*[&@ͷ#tbDqvkڠa\u[c]:(\n>2E&3EyJ[TX41g;#?3ͨMS!l]lrK6LzS>}ָB3_-[W;?hȉ˗E ,'^ﻲWeM\!$d!أvՏμjwk`g$JiLƻAurRRH +RoKd x BQ2*N+[A%4O=2<J)r_`,ϢÓxT3ea3X [Օ#w )grm̆t0ͮcXpRS2s'BÁ*՜1ß|'ncЧ]> endobj +2631 0 obj << +/D [2629 0 R /XYZ 85.039 781.388 null] +>> endobj +2628 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2634 0 obj << +/Length 2762 +/Filter /FlateDecode +>> +stream +xYs۶!j9I|;>9"eD/PD'oK3&XoWzß$m:lL+3?]iB " 12LR8^]4*nEwO[5NWOg+aktf[{i¿~ꇻ@n@zTx|ɗd9ReՁAt&FiԻٵuEbe[V nS_XP-TLxGvxjqar]lA;Ti-/NM=وnY[>MMH$T>E wGaZ:# +ёR:DuF$qV)H`Cۂ,rd 2[`Y~}ů_*>zzoP# &X9.Y7-Y),e!rZ">!SuhFʪgjDzWiG쁓(3s72:n/qlqU$[_; Isr0lcۼBS;z +6s5lTI0400f hBB.fI eE[ +sIːZf:. )헲7LҹPq]k~qqh2UT=%>cߓ:\ BP`/\8ȿdəNEUaid$Xde1`b]5=bi^#.CvqbPk +A3 +H8,4%l e@Tr{/q'2ړE:rAz0'8tse8zR+)MF]ɑ \Mꗢ\tIEF7 +eP)&g})FNr)lYH wh*DąO%`BMr`)J0qsf"Z(檶^ywTRĦ_V]sDǨ?J4$(};@S#>;X2]|[(nHTOQxRxY3ou!l=D3D(s/t~@U>&M8<10eB?jH޲C=Ϣ'闶lOmOW>8tNW*L#y\-~6h +@֡|XG}Nl2 %0UN~R(4ɵ[f{L6T톜/aJGL#jqJCCWeˏeKV*'mtLJ=}EL^WI6U6eɥt2rn6Bg6ҖZ0s!.^:UB3~4k +2p]> aN!zA3Ɏf dv*;#[f;w ۍ8ORXlD䌛o,./in@fQ}<,ZuP!qy +q`i~lB[&-`ic5W+dr~Qs 7qר'I^Sѧ5+zA}؏ٓ#h ~Sȍuj#qlV|aȗ|sg\n:nHb")c>?$ uK0TzgհA9ܕX}fgb"axwn  dMӃd?8h!c +nx9ʵ/РΒ43ֱbd%!!%/X#?SŎx."ezH=k-@P9w{"6F+o*B,d+CЌ2@F+sѵFsUendstream +endobj +2633 0 obj << +/Type /Page +/Contents 2634 0 R +/Resources 2632 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2619 0 R +/Annots [ 2638 0 R 2639 0 R 2640 0 R ] +>> endobj +2638 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [297.013 519.753 476.549 532.655] +/Subtype/Link/A<> +>> endobj +2639 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [343.406 485.661 494.306 498.563] +/Subtype/Link/A<> +>> endobj +2640 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 316.898 479.305 328.89] +/Subtype/Link/A<> +>> endobj +2635 0 obj << +/D [2633 0 R /XYZ 85.039 781.388 null] +>> endobj +542 0 obj << +/D [2633 0 R /XYZ 85.039 761.463 null] +>> endobj +2636 0 obj << +/D [2633 0 R /XYZ 85.039 669.619 null] +>> endobj +546 0 obj << +/D [2633 0 R /XYZ 85.039 669.619 null] +>> endobj +2637 0 obj << +/D [2633 0 R /XYZ 85.039 644.901 null] +>> endobj +550 0 obj << +/D [2633 0 R /XYZ 85.039 302.385 null] +>> endobj +2641 0 obj << +/D [2633 0 R /XYZ 85.039 273.284 null] +>> endobj +2632 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F65 2099 0 R /F70 2201 0 R /F21 1620 0 R /F18 2207 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2644 0 obj << +/Length 2829 +/Filter /FlateDecode +>> +stream +xڥ]~ +x$-4qAaERcIW!>KJ٨ =h9;ܙ+~*\Oe$]pv o^w7?V[By(9oJ)W:IRyn;/_ݷ_p.Uo~x\n+{oUS?x#=ϲ&J뛷7^6k?s Z 7H`̊ = TpKp(]ywSU^2gH؋-~:#튲e Vuq ` >K8anuQ?vXUs`N/UƠú$ZϐLq=(#1tݝpXL=DQPU9>/Q`>s@ 0W>]V)@e{>U(.IwB#G1$QI@5~۞V BkC]L1fY`OqƍԩG+ ;{w!9)>U:@`' +*dh(` tot^z):=~" %f +7qKx2 chJ%l(TS0E=3UY`ʐy>[ ZdlGRGŜήnj:A ({Ҥ=yMp=tDw;bS╉oIzk% ZF'4D3\#D(,Pq SGFre_BTpq˞S`;9rg,hON]G-`-۠ &?C/+vf(jr)PɸLj7w*{~nBj8%zh{.Z%n%ߡr*f6HrD!S*E3‱v] J~2Fp2GS2hքT[$KW7ˁGL|~he7TRp]ʫ +!jBn/-?dȻx!{Pc$~2\>lpe˶.9/hӵ}I22=1 jҘсZ"VP BE 3k"Gc%$FǏ]5 uP*t2peȥ?Cy+CU|6d=5\7F Hgxu>a۬GwfCe#G~FܕqNx^D?ªJWД @qN0޼LY.܅*fN &Q[OǺ,T;j +hE@HG9ŖB[T_I9ָCpM% F<:'viazQs~0T2SBm ΁[B@qcRF^29%kymYܙ8v$Z_.ݰԉ$-w=ݜ/6Y )epaNtԍB TVTLxGQs/ƭ- M:1,' +f"ю*6&3F9FRIOk#$!/&3_%BS%)w)ѧq%є|N=_\L wĽ-8*y]!+UzR55F0819H '%LE)nVl|8'*%&ļ3[cfNj伒=O Hr*ݙ Y!EeL*1^2!m0J<^sS5'-Y2} ?TQq̍b:Zgjr^Ǖza)ޝ +KyW߷jdWenlߜ= ] P7҃rJܼp@ZLSӌ|'  R7;ibyNn@}bfų=T*m +G𼽜(m|IK]DiC ?P9)>=5 vngNXZ6"ř1 +G#*cY1'kR?mG2&3%͏h::uk3 ]Md%l̓U]ʆFw/iKM6Q(xDue&q(eJE#V5$T +.tw&$*D:}|!e+`qK@rиK~j]ägKaC ռd*$'$il'-aSiIքcR̚abDT6xM^CRXQP qC& |?SyǑY8#V.2z\~9saJ!7F_!ϳy ,xS:m)KCЏxE/@1$kBοp냩`߆N>AD \kol@6|M_ف⩷%}50Hl' +?(;|| M0?}}1Fpv>iO,@}2}cg?opLi! +a!Dq'g'> endobj +2647 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [145.77 354.89 191.399 364.458] +/Subtype/Link/A<> +>> endobj +2648 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [361.036 338.614 468.425 351.515] +/Subtype/Link/A<> +>> endobj +2649 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [222.711 312.121 306.494 323.811] +/Subtype/Link/A<> +>> endobj +2650 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [349.617 123.446 454.872 135.136] +/Subtype/Link/A<> +>> endobj +2651 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [155.951 109.291 180.514 122.192] +/Subtype/Link/A<> +>> endobj +2645 0 obj << +/D [2643 0 R /XYZ 85.039 781.388 null] +>> endobj +554 0 obj << +/D [2643 0 R /XYZ 85.039 761.463 null] +>> endobj +2646 0 obj << +/D [2643 0 R /XYZ 85.039 740.47 null] +>> endobj +2642 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2654 0 obj << +/Length 2984 +/Filter /FlateDecode +>> +stream +xkoFN(P +hGDV-!Z-(R!)+.}vF  Q8:ر(m/Bˋ_Z*<'Gj^S@8v`%G8u!{2xAH`˪JkD "ቦ'QaIhc^\5Wh*wo2U3(_CΏǬHCohmvl.D2 +ǽ--~:>؋^M|jҮʑ؁m–k `dU Yկu?[8NblTHG|9(ix=>G\z#?YB=KV9@G0v7׎P{En}u =_nu{ ?xv{o%np4_T+/pȕ7vp9z7%\jS!D|88|b"jmy*-gcxO3&8\=raZB/4MY7x,R=r1`󡃖x$kOӣe9CQY١7K]YtdZS8է9(FfWr_\ak<]b̬ˢH /m4cz0nR<v_8`υ3S51a(' 1NKiU%'  g> &_ Sb$)I“F. +y#B.,JЀxtl >ֹ7;N+'l + t`IBxn߾9T<`|d7ߵ=ReY؇xD|JT/rL8 F>.´:!r]3B#2)O{.(YHӋ|9 +ym2y1 SłZ۔4*&0͘))mڽȢ\ȴM$bPlJ?};$$csQF\'4tl_?8L1;qQ}jfڄS +  nĮKcYJګ@)02+5 s_uYի+."T^ScBuv7}R'6YC۫gS:r e[B8)LB?M5kHsHRxM2GEm`^7O+01^-XL9p,̪r;Nta8'm7צDvm1Bu6[)Lm:1)=L47nB@I ^!4ؐNq'~?{#f Aojpδ.Dr +`ػ<*юƋ^8xiEa)sᗮCW5v@{1KB>;C,w0i60@cwarjS˹L ?!uJJUG]w%:⹺ nhI!I(YG5ORL2jx@bO)B)= +bR#^;xÓZP\VYsxg:YQ7͊sdCO +Z)+E0mҮ1`"(p#Rġ(MX8Aiqt!٘-ZFQ:~C'^!S:B@+'B)WͯDDzgzCS%ɊNMQ ?ĩ&7 UH؛?DJql= +ˤ_OǠ]cT0 aAve`KG]R*>:k ,('b'iۘ8{Vk|ZAciwY 6+VktW]*FqqtOckZ0%돩󈾾“B31}m?F쬍@b;kHǑ\5n@d/4Ҷo iu$ [9gm\Oֺ nj̳D1usd8> 4|$n3gDjQvcDFcJ/m羫W>W> Q:aQk7a@MxMT7z0^nbT|VƝu;qX\`T9ݔ,4OXk= c?o> endobj +2656 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [254.042 503.917 317.277 515.606] +/Subtype/Link/A<> +>> endobj +2655 0 obj << +/D [2653 0 R /XYZ 85.039 781.388 null] +>> endobj +558 0 obj << +/D [2653 0 R /XYZ 85.039 326.218 null] +>> endobj +2657 0 obj << +/D [2653 0 R /XYZ 85.039 305.021 null] +>> endobj +2652 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F20 1617 0 R /F65 2099 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2660 0 obj << +/Length 2270 +/Filter /FlateDecode +>> +stream +xڽmoH{~=RMYX0DO^OlP1eMOϽJٝY_|״`4(^X 켻I\zxֳG2+-DWƛaǽwDs.V(>\X)`cQbqޓ#k"k:ıLߗPpVר"m@#2m(F +_WR$7I䇬I +Q (,GہѼl oC%u󀽐nُN.,y m #?<ߘ^>U9aTxkҤ!]׮uU^SP(BqѭoW}r͵is-&l&JBcrU,fNӹ˦K:&pؑ$U6O(X8E{o'ŐLtx -:a5^\H+./^Bvwe f=6 ^': BHܠeYbӛUn\,jBX"7m*`0-/tuN%ߟ-l*;]imTͻu/L~6vx*?]~8 endstream -endobj -1590 0 obj<>/XObject<>>>>>endobj -1591 0 obj<>stream -xXkO#ί;R$X1H7eG8|@3mK~}NØ^E𸧫ԩSU~8Ft6)ۃ3NFń\t׃a1yqF'39#iup8xB-V4Ngbz:EExm8Ey6*ZT$TcknH464uT( Ϫ~Y VB$A>|4Apu?iq)Kv$ݭ74e5q0ww(̫Z`:t/+k%g}dF杕p'uG ٻ%ytdT41l1V'=V[eNGy_ΩfmqF4MwGpnq9[(FwH<'4ܹ)i.< *%jy6@,N,du/n$ IΤVJ8`A/d56R橆]/8 1H^MyBpmg41c1נ~Ɠi_./ZO>7fg~uTqX[':sCQaKE(zg}4Sh'(Ohe$ BknǨ:PTm-cdiT)cR 3bZ -wr3Oן>Ѷh8~l9eNy{0 r/|uSٵxl|JnqA(hV[V,ۼgv(lF||" i`WK~)|[$m^TLQSl$ ,Rq>3j1'ǫir[ Oll^f֝^y҅wG R0*U@O̠=HH1 -̵jq,d)+L\3E})]#(| W)M'/6tX,IniM%`6 O~2dpg_=5,V<#V"}(<1{U1<8,Rq_i JT۵-YgEsAz\^7c,Dl !,~= &endstream -endobj -1592 0 obj<>/XObject<>>>>>endobj -1593 0 obj<>stream -xWnF}W >؅EY";±h* >ȕ1evV=3K -!ڝ˙3g_tc:r+OI|_)O ?.3q(1OOO}?ino5VfcǏ.O8IUhn}3u3U0ՊΖtuKLٵ?SNNЁBst^]Oפm9K.km/ʅ _x@yjÁ`jut_osZۦHJ^x]e,+_h,]unҜn%^6V;bԖ|w')4NKl*LҺRK[j F;Xb Md -UEλ/Y)@r --xya_Еv&u7UL⋵\yl/[Sօ6h(tuTYԆܚTҢ \UEGjQL\@Mݢ -CZE;t‹7 x̿q2=O Z\[o7W< p _[[M#1Cf,9o["b6յu)-6t~? -:ŀ\47(Q> g A=9OE/EΣL?e $ _]DH8Ҭ{TV:~ge>7a$ SMׂY+Ht}75<8H -_w$`Uƌ-gkpznצ(D7өFKfbN"~Czw{>Y3>tboz3AUk9!l˱ZpiDj`AÅ]|T*[Iv[{ТBCkc> wc\XJ[iޚI[|bcTU4K@=b@GZr0N.:u2&_9tQsΈNleș >|@m%O&hXC}Z6Q!4pi>ၼkV`y[ b>|~Y <3|lk`!OZy1y0q4iMI.zhdƌd,v> --Yzt(ӮĐq#]h5TC\-,&XLD - -/2j1^RT ]c4pYRbܗ:/EHnۇ~4%N4`JV^;qSUrv[)\HFaptYrϝB{'C\`2A.1O3p]LSB&?Kʡ,ml -ŧm6Gqc$ -+c e]1+t;< Wax {9'å5R;9Zy@PX[>t: s[Rtn\&>Dy+ѫ78+l^>+b}m8!JT= (!^ë]Ycvk?"͊l0,|}ՀB{p_twM?ɉ}4bxi&>s=`z/Apt t uykϚ˫ 4Q2*y8ls/ZXb&=""ޟuJwzi -gWoX xL *## O^7=&'Sc6n3Ɂendstream -endobj -1594 0 obj<>/XObject<>>>>>endobj -1595 0 obj<>stream -xWko6_qhDWǂuE\ Hj$R)w.%ʼn0lsϽ2i4SZ P|UG f×^z7E#s|S) )168;iEVpj4Uzu|<&Xx>Vev\fσ<gϬ3?x-µw69h\{UT㶊r.זi%JTt0uE/H -U}Fmn)5u.)WB3Ur8$TIG. .n;vy<M>(PҍR%k -rKfî,eҺ"Ӓ'{甹x2gHy@ʥQ5-IfJ.uiH͊,WX2͌Ϯ^/z.S]iDm$r dSAL7ݿ9C?^~V;O!%_i(^noL@-V ~aZFc\CS ǰ_.HE[Zp7tzVw/19nڝu7ڙB k=XP!nTqe ]i'')Άo\exV*-Q\"u 6e3L=K3dGī住GD9V$\MhgQN4zW;#r2ktp|85* nU*}rvy!6H{ɳ[C\kYlUǛѓZJImIdubOynZ0px((;L8~۶ÁKxPHN1jiIP:R_3*1zLڵF*Brw2| jQhajȚI/P7A/s"?y4||~'mnFQdQI0wKh .ӔLJUE4!?k3EU1e9@{r:`ABz=+^.w9CO0l| qP0pA}9.x<8r'7C=0Yv'OLf_Sl\Lo?67endstream -endobj -1596 0 obj<>/XObject<<>>>>>>endobj -1597 0 obj<>stream -xWMoFW rrP[drzK08n =".%(M-6l͛ד\k.\^KR\.j~5[fdb1x>y,.dF֩$rU5ؔOdF:eNk+M]nrɅ/0ql*n Wrq87Jxl)ylB8vkUcE$.kFH׮梤C/#yTHJɋ{qS3_ hjz\,a^Llm%s5 S|ReT1CgN -lr-ܨID5 -Aժ􂜔xW ,ظpi8)tsFV()+܉#¿߿D?nʛ$ IܩzgL f\7iJg -è4xwO3A}>JrcQunT -%>I3Q ڡ~]VpڄȪ4{1 ߁;H1Gx/Sf-t~b@,iA,f/GN;]h]NKj J"=O/&ƓblMXeG&֡ @f;h dЈJ5cX&iu8&rlz*tNb)I`HF"?rӅt ]un`IlA r;8QG36(God+DHTv]b07}?*v4ˆU?Й]R6,* uv]?j}D -Y[K]n"SY%3h4b;F;FyԷ- >2jX{0Z1.H܉іr -sbOLrȕ-%RkTq>Ĉyr]=wSlNd*g0,%Gݓ]59X 1I@x>{ -})JA"tV0LD!esDVG?K -s0v/;Bwa[ae|0.,+#x'Ԫy;#dXi1G٬X_aڦ͛㧧Ռݧ@oRf\-g8^_/Nendstream -endobj -1598 0 obj<>/XObject<<>>>>>>endobj -1599 0 obj<>stream -xWrH+8ı1GCZ Yb -4D13ޯ3(Țn>ftsIW JdJW3/oMj9\z2듋shA!tJWΓ5TI6R 5^Zr&fK+剽Sk2 o3\z/ oMޯL|vZNia[C]&oq:He%vf+!I֑)Cs%KטQX)#REoƫDLJAtIUއ\|@3^0\Mf]jHǾr~)rz$:,ԐlΨ.Qǣw(Ő[Z pzcZuC;?Fڃb೯ pN7xj$#݀ōrlK׍_꺰 $!^U_1B3\4QqUsx]J2 - p,)gŸD]{-08{\+E ,{hީؖB|Я-,d&j0`)$X8M)RaO"=z9p.u*Yөn7jPh- -vaG`y!Xd(ًT# Q$A2`||Bb!Il&~ȴL  -ԹA̅2xY]PȄV98g꺛@%Le -Pj j)<*Ma-úKS%9"1\%R3] | zMʘ1/q0 d^90V=τ$(UX_?0CON -)ɺ1> }}nP$E}BfouXr \*iQ-;Fj ^DVNdg.\%Lkp*U%L6SK#ًP.EOޘw> 3ʢNlNv+3 2 SM&)n.-~)Z5AT"UL?to擛O:Mdžendstream -endobj -1600 0 obj<>/XObject<<>>>>>>endobj -1601 0 obj<>stream -xX]o6}ϯK3 QlǵӾ -[lv Dl(Q%xޯ߹$rv($x?=~=4lh6e3?VR^goǷ4Ҫ ~)vF#Zc&ݫgJOWO7vOKiT.O/058a|\^d4_RTkA[h#T- [Ib{T۞?U]c+#j7 ] {7|M5F n,|:8\r)>> EڵD$0BJVxDkxxܩz)Yr@-`ocM8dGd+v{rdM xMrQzEO~T*j˲Ty0g -%"TUeY3.Ǡ 0 h1*Uɷߨ -KgYJ[ĉZx~X8aFX{"r}$p4 -9c08_#|T8 \CZ]OeiME| }ւ}Dj((CLq mjg 4"wSRG?XV!BSR-;C0&›TFTKϞ0RY= m<[HMDPSnjjŧ%‹5`Qx&n -G]{ ,EOfi%*6VTUPR@y"eGy'u;υz2MߎvqD=2zq;I[RA884k1-VnQ,b NZLRNJib0u}S(ii죋cycHx)J[HwUPScjIp[^m! El%C&Ǩ/񪱪 -Y[[+zƮ>bAw~%}~U;1C+nLIxd1m 6mB$0LMF.!聡Gq7jx:pR;7I_U#BC DARDŽRh}( !Fb( J'tE7Lw<ё!@Ɋ^%Sb@l@nySn4 10evkKPGIJ;AXn[6>ݷ2;?f=ާ7Lv7YBN\<`C(L`͋mtv`Pkb+'yj5 -  g' ozφrPwo܌z'7i،g\<^po/ѝqL7:q.s?~Χ|vEM:?_iendstream -endobj -1602 0 obj<>/XObject<<>>>>/Annots 841 0 R>>endobj -1603 0 obj<>stream -xXMs6W-LL[,+:vm>(2ӁHBL -@Zѿ)13xX$}"ߎFt]|Je}tV%> ⼘=b<'^h4(^h:5gŨV'0Mi~Ы F4_ZN>yy|g:Mm4!5TjxB -6*ƭz[1aJC/|NFoٖHl.D^IwS6*^hW~}lXrm{ IuPlm*xG5W 쉉TNEOZ\ha`ꁗ!~7dKS6m?Վ0s/Sb -8һ]1-v jVݧN 'cAaAY!iӍ }49d,t=R(,`'cNAwɞ I2҆EMsNJ]י.>R۵je`FJ -/ x¬/צFH?TE! _{Dv)=lmvxEvHϐl`LR0yP=yXn4A,K=XE}H^eJ} WE +eu\HjJ gO550wT<*^29$')8ơRf3OS(զajgڞ-iO ӷ`iÞ0Ln)l™.;PAqWhGroh^aUJpLB4<8+4j |HxUUb& ˥^ڛ1u7=Nz2CSE^:)s3!Nܑڮ k¸& ɮ9:Zn 1MgSHOn9Q?/*U\lhm\5~*aVZnfPl׸_Z}*g\$פzڋuQPwMk4tuNB6 +Rc=$;b]2$ #gz};W R}@JZ*%JQ¨I/ l ^_NS +~HTfIa!m|u{6(2ќ?WTendstream +endobj +2659 0 obj << +/Type /Page +/Contents 2660 0 R +/Resources 2658 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2664 0 R +/Annots [ 2663 0 R ] +>> endobj +2663 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [129.868 508.057 297.154 519.746] +/Subtype/Link/A<> +>> endobj +2661 0 obj << +/D [2659 0 R /XYZ 85.039 781.388 null] +>> endobj +562 0 obj << +/D [2659 0 R /XYZ 85.039 584.243 null] +>> endobj +2662 0 obj << +/D [2659 0 R /XYZ 85.039 563.046 null] +>> endobj +2658 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2667 0 obj << +/Length 2459 +/Filter /FlateDecode +>> +stream +xYkoF_umF#g +n&鶩X4JE"U1CQ'"<3EpU< +#)Twt3OYᎴpLtEƣق_\^^]'J)G*1a\slRu#IQpc]簯d25t Iu) Fc_:)%8AHDJ5խWXcʬQ$];bzB<S5(7$IȢBGY ֞v. 2畓=MK_:0o132 ./1lq +EBbqcWLj3g3v;aQM>Miw,ث0Do{•P@;-  훍Bq97Μ…6 ] i(jQ"H[4ln+R70A͂]kGoZN7V_ֿX!a[&t^=~p}zOʋڴ.ˁ7-S ,g5&U,tq:!G&+HA^I ^}]W0J"äکcNdU۽[\WyIIG6[*eF 7N_YBW`a'JvNw.> deIL鹐P0KSױ!kbZE} ezj@eV5 DS;/V8OUw51ߚ mB((,*/ѝ+EtSwjن'KY;͓:pYK'kRb6 +z;NA !&(Ǟj:Pݟŕ+-XdGǬ Ax7b7KaBFPDzE]g^FOӾ/[P?5KLP6`A5;Go1vN:M(j +r :5A#R#PS%(阆GVZ7%\/~B݅KT 0ˬȤS[';iA5|ʞ71)尬4Uk +gft;o1_]cb@-CPcGP4GjQCO/dHYg)Oun{GKf8I`$`uλU.i._n-(ws QЪMi_2zhXM!{oaWm !?`qtY"yLL0Y$M8Vfu&6@. +q]d^P!*c|DkRKAYk6; w!Fq5XT搮Vkst+>{Աe`\v~|pj~ʁ꽴B҂ w$45 v@zqq8%7O6 5$N]#*mVCo9:wh69b*VQTzJj##+2sE5I-居K Rp0= _OE8^۽CP6iMx{~^x~j3.dlcw~?9/N)Uf3i֐)}6x:)|Aq?+kce}lHk-ق!h<Ӷ|nm hs`q`59=d!{zug:K6j=k-)˫#(.g.~ObI}:O'o>(_]^.N0a*&uhO?lSj4pܬ:ut4j~A6_U$ 7_ϙ|A*@J &'YWU1Oϼlxe٫ 媀5˾L?|N_b}14Rr$ۄԧ8L|˗ړ^#ZKWb(:hX=]6 +;{K_{ +mendstream +endobj +2666 0 obj << +/Type /Page +/Contents 2667 0 R +/Resources 2665 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2664 0 R +/Annots [ 2670 0 R 2671 0 R 2672 0 R 2673 0 R ] +>> endobj +2670 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 638.298 286.854 651.2] +/Subtype/Link/A<> +>> endobj +2671 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [167.627 600.436 275.552 612.125] +/Subtype/Link/A<> +>> endobj +2672 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [251.271 492.042 367.484 503.732] +/Subtype/Link/A<> +>> endobj +2673 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [258.568 464.944 363.558 476.633] +/Subtype/Link/A<> +>> endobj +2668 0 obj << +/D [2666 0 R /XYZ 85.039 781.388 null] +>> endobj +566 0 obj << +/D [2666 0 R /XYZ 85.039 761.463 null] +>> endobj +2669 0 obj << +/D [2666 0 R /XYZ 85.039 741.134 null] +>> endobj +2665 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2676 0 obj << +/Length 2310 +/Filter /FlateDecode +>> +stream +xY[oF~\cA1,nȺZ[Ev-$"(${nCQh؅a̹ohw;IǓeyLְ•DNҷЛ8d-g_o׾[oO(S׺]L]O6}k1eśke?]3ɀ.O#MIy/=^S>5"׵Bۋ;v^@?w:rkYQ/b֦C:6mW*Mu_v֕[^O̾Y_\uׄ.ZnNJw\n"Ic7rۺ.f6]y u##Nsh8)C1D/T_` _ݛ0;Fs/_qmVft6 Ox)Y[>˺ZhtHDvI؉T7B>nR˥-uZJ(Zj;)ӋB}h,-@0QQ}=Xsg_P0(,AXh('ahUȚ[FSߵXMמy-ϱd_ܱ!zC{yElaؚzL60O#98тaN<6ǼNSh6fОRPq7ЧVWDĩ(4 GawPH)q!#|]ǿ/a ޼ctmd Wda X⭻QZj;H-GA|.I- +V9*z)u˷}FW*d PkJC> + ja^+;G!8!Qu@WT-Ğ %:jh?΢ЬC-(a!F=a.a2-&L$4t#mҮwh.~+MiO}(Nr T"bDyLoINB(LJ1`CM i;c~C][eiޠ L֗|d&T$r="=NGX}p'PtŽ^P{ypeJڶ&V"s娱B턅Hc#WlxHQZ՚=[T!phN#n@KOdSB_7Ɉ;RN=ز;"!:mمwAuEAwjvH$URa>1@k*NӑXP>Wrkֲxʭwv^(QQ%˒%9X 8&_Ҋ#M[q gB݆!mzH3Qk-Cn^v{)ra Hq=^ۧɗ ,sVkGy@}FL[ OYx&! +=n֎Y8 +e$t&rao$I5|3=Pt{OO fO0Q2eO,l_gEp4}6M&o#,V$Vht-RMv9&@RֶЌ4nJ RCW1 /=.xx^Ɇ.PY~ȊֻfCYk7!I0ׁؐ*WP<1 +):̢ߣ +J;4ف]fG,yqt@:7X@ #y$B +2 )I*nA3SDcI[)=E!֘b}ҍZvFns'B%CxsԁҝK9>h#fp fc&(88 'D3'OEkk!*nqǪ}X[#/zz_<Ie?|=t)}E*y|a}:=Z[VF eL,leeə͞(.;ʟ7W_{?=i endstream +endobj +2675 0 obj << +/Type /Page +/Contents 2676 0 R +/Resources 2674 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2664 0 R +/Annots [ 2679 0 R 2681 0 R ] +>> endobj +2679 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 305.015 212.606 316.704] +/Subtype/Link/A<> +>> endobj +2681 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [457.73 218.948 613.572 231.85] +/Subtype/Link/A<> +>> endobj +2677 0 obj << +/D [2675 0 R /XYZ 85.039 781.388 null] +>> endobj +570 0 obj << +/D [2675 0 R /XYZ 85.039 464.617 null] +>> endobj +2678 0 obj << +/D [2675 0 R /XYZ 85.039 443.624 null] +>> endobj +574 0 obj << +/D [2675 0 R /XYZ 85.039 276.385 null] +>> endobj +2680 0 obj << +/D [2675 0 R /XYZ 85.039 246.981 null] +>> endobj +578 0 obj << +/D [2675 0 R /XYZ 85.039 178.549 null] +>> endobj +2682 0 obj << +/D [2675 0 R /XYZ 85.039 157.353 null] +>> endobj +2674 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2685 0 obj << +/Length 2940 +/Filter /FlateDecode +>> +stream +xr`VWn֖bѥTm0"  @dn*~$ 9!==3=?Ff$0Mg7[Յ/L^_~3s3/-e\{}|yCwHԹw?^-|¹y:˟.,.Oz˯,~0KgO0\?f nBy.n/fw95U|- ,p 0("`H4p |NG\z \DZsӖu_8?@ѼCѫ.s, ~N?妘/,tv@l8uVRu<<3pVD&`,0Cv-aq_09qB@;<;:=<>ါvyeoH툔fgpTDv˅`PQ>uFym@O#@yxcH.,}g4]uDbjd9ß~#Ա4&[=5/=7KhmC;D^L0I;ȫع6Mc,w010'_0Lu"0u jF[kJdncV /6Dc2UeL[T2gǷ<@tNu-hFP9uQ]y1 zmw%EAnpa%nhﾛ Ec"n/'PQuEr~? ;V6BTYԪ:0L3-F گ-bq<`tu0"-7(=1Ȃnda0{@ *k~Z_l#`;҂Nb90s|Ɨ::eZLߓ2(' ?1͠܍έ,%zm`潑U*T=s +lgI7xՠ'6Kǧ48u_X+0iI>4Me[19t&8RÑWcX? +ʨ3i9#t7gfWP'%yf/+/zȶGpŰbw +vB4wdo穢(Kho6Nhwmm$v(H[%Jp'EUm+ǜ~-Q9#zML o(I2׆ɾ|;Ҝc|/y8~%1&–z1IWAoxwb?RP32/ܫQPV]^vbeN)(vޞjyRT|7Z}vR`iK>֙3[@ökN"ׇ;R +H5$$4m;`﬚Kc8ap ֘t/VK%f u9Mz?fBξfgD f2WWqkY疅0>M8&㰑` B+-4OdO󤠕'ݿL*br}B ljDs[f!4qGyÔ8KhyS?mSoz*]z*cZ|_A]i~Q_(Q#^M-`+]6enPC'ȡ?Xo)Ds,\<_6XhB3EgBPd> endobj +2686 0 obj << +/D [2684 0 R /XYZ 85.039 781.388 null] +>> endobj +582 0 obj << +/D [2684 0 R /XYZ 85.039 761.463 null] +>> endobj +2687 0 obj << +/D [2684 0 R /XYZ 85.039 741.134 null] +>> endobj +586 0 obj << +/D [2684 0 R /XYZ 85.039 672.049 null] +>> endobj +2688 0 obj << +/D [2684 0 R /XYZ 85.039 650.852 null] +>> endobj +590 0 obj << +/D [2684 0 R /XYZ 85.039 568.218 null] +>> endobj +2689 0 obj << +/D [2684 0 R /XYZ 85.039 549.346 null] +>> endobj +2683 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F41 2104 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2692 0 obj << +/Length 2286 +/Filter /FlateDecode +>> +stream +xڭkoFP8 +hE8\Ҹ@[_"|DbBr.G%)JN;0wgggg=+wC:vm?Y<7`8v~ܾ؉,6{Bd7?o^\o\ױut?~,Wuϼkط6_n^mF;|<{gS8ċ';$&}; |7oocZ] +0;sA7pB/ac; i_/jN`QK/?Pp xt-d+ĕj@(ۓB`{ `M^,pIH,O8G= T@}\`B?H;DNkpAu<适՜& +Ƣ!pb6{jO1Ұf0:1xQ).gv$YxaʋQ1C7tt?c?2*YIYTE +fR;eҖ%t5JXP͜\"Yӹ $U%&K2ۻ>-Lײaj48g$\7Cv.kBl%叱9 'UsIz%BDx0>0"0K+r:18G[(`ɡi-8V%$RB⧻KQ_8Qܿ@K]L%$C?YfB)gη*Ql2 iót?kd 悡BbEC%j.Bqp StOхKVPK5jկm*fQSwg^x;UxU-XP T,VZW8JRl_;Akvq8|Ilg4()Z3D́zO tE)k$^|jh %/'t,Au 璝]}z mQσn;UKPmʑ**pI$ٿ}3>W~b;a@wyx,6-߳];,VFHhي:GR )PF T)㧳hmNx~NNEMuNօbOBO>?@:AR?s9mnڦI1A-lM^RZ\6z,v}XS2C6 +Rb{(Ώ'S +ݪD|"!f+m(7qΠ/sO\cIdYѻ9?1>qdD/"gý>}ts6g_rLendstream +endobj +2691 0 obj << +/Type /Page +/Contents 2692 0 R +/Resources 2690 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2664 0 R +>> endobj +2693 0 obj << +/D [2691 0 R /XYZ 85.039 781.388 null] +>> endobj +594 0 obj << +/D [2691 0 R /XYZ 85.039 679.868 null] +>> endobj +2694 0 obj << +/D [2691 0 R /XYZ 85.039 648.343 null] +>> endobj +598 0 obj << +/D [2691 0 R /XYZ 85.039 648.343 null] +>> endobj +2695 0 obj << +/D [2691 0 R /XYZ 85.039 630.139 null] +>> endobj +2690 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2698 0 obj << +/Length 2253 +/Filter /FlateDecode +>> +stream +xڭks; 8Sx[im#Ñ<в&}$!OfPם?8I}7Ly-`~B#כLjb4i}ͼlb}߯oo>La:~NI:7d;o=&i,&Fo CatAw# tcl\8t(y1ra\4UzM` BM* + +Z +ĦI=>t}4q;P)lx2$h)?z~\Л'js$*Wf+\`UW7O4rb{!ךȻm]}(D0#dc& JW(vZUZ[GunUZ,uP] +Ǵ.KifEkc 2azZƤ%cU% _9̆gmB-덮@| ݸ$[l8y´84$lS7Jcg?= p}7 jD|>n_0DBF[- +$@y*њJ!N&\g֕Y&4r6ۃy~2z.mx-սC##.w}*uDɠՅKsٖmCT&ACu>#MʊU[>G^OuelcQ犎+^Rkb/S^,[MSo[Pcߎ}!?WBq' +FV t}٨T*1&vΚP<^NL[pbq=%OM7[-)[fIW){36X}g(mā;BRfb- +~L ~<(٥؄lr*rmlV궛+^k pCll+P",W ,cVj`ꚟ7͍jǺYX*^.^X|bo~2\A3$H|L[`G?yKϛ%.yOph)M$4~9kQvt}HKbߋ2 ( 'yyG 땪V1cfZz[FL]ȺwHҖk>M:xw psd&߈zlsŽ^-2@nXӆē(J-mH ^\ƞ+ȸgw<(jmK y Wc1kMȵ;_y_IǙƨ dID~.DӷʢZ|JhD0s2&m{Zڔ^\5Y ?'h ֡:oAq1Wh\O/|c/T5Ru71"o6T +p'_"/=7՛I@w]yIR5E@ߛ`9xwY!1\Oxoid+~(mۼU7cpa~"o|3=8s8x ˱UGf_3\Puendstream +endobj +2697 0 obj << +/Type /Page +/Contents 2698 0 R +/Resources 2696 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2664 0 R +>> endobj +2699 0 obj << +/D [2697 0 R /XYZ 85.039 781.388 null] +>> endobj +602 0 obj << +/D [2697 0 R /XYZ 85.039 638.273 null] +>> endobj +2700 0 obj << +/D [2697 0 R /XYZ 85.039 617.077 null] +>> endobj +2696 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2703 0 obj << +/Length 2252 +/Filter /FlateDecode +>> +stream +xYY~ׯЛ(h^xwǰɮ (YZ#O]M5%jfxcauW-w;iU9q[y?q™* rr.c'N2]ndۇon~/|߷\ߞ/(n|Z7?O0qnrɷKcÅU_&?L wxmvdZNTہ_L>Ms95U#z-4M h"(@ M #iZ٠*]ځadk5ye ZZ<{]z -g/H÷ F|/v}Z$i:I*ʸ12@T팇 tmB0bk'>Sm3rX[abWȄLUZkFF{akmр@.6!s7rUPDk;$ +zA.O*wd'ǴWqU>`.5y@BX\Vp(hYiv9gM{PtFdE($f1.Vh? fQM|Գۉ_JSu99?IԏFjmNTm^s8 28V@fBIAuClh[n^0Ezڎ6)( vAK5uŃde@6x]u\~*Ny13SJc$?y1`9yyGZ)#8Ĺ|@$$#AoHHIk>qkl yq`5XqcW@/AB~9Ս1)YQs5_p~.:arQ51 +Vc&`A%` + Xyںl۾iqȮa`,I: w`Ș*n;. RD@CVjA@DBAxRƃRwE䞣ՈS|œt6]8D9hg$J8V} 5n$K% +Ol/'+ey(T_RLA6vgP%\]Ѐ]<mc̀!<+Z bWS<N`Ŝ% +: PiH8MY^ +>Ha# {,6TrRC<2Ο@X锅R(A]*# hͭTFRVU!ˇw xSE1S&aKӒ +8XpEQATWda<1$jzI 9kD-h [4uH8)VqNYW8oLm4 ]zu(t^[Z=%ΏuR:{y+78ޞ5Nj J>'ILU[IzP;3@}ԕOAkiʯ MsIб=(K9dRVذ,0Pc{P#5K_tӻ,>@m-쩴렵fÕ g]!)ר m&#I^LR4`C +~窚C?p__ Mw3ƣս +ƃ vW/zqŒvJI. GTMz^H9PXrНwg$>>Gc݋Y~ӁM)弦oO +g ge(L~kbTyReky༵/lOU/',@_S 5W:fПL@/!e_)ʦ.\vVرAĽ J'Z +y{}yO޶pt+oqĜc$w[-c 02XǓ|c^ MH^ pXAQhY&[ b*endstream +endobj +2702 0 obj << +/Type /Page +/Contents 2703 0 R +/Resources 2701 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +>> endobj +2704 0 obj << +/D [2702 0 R /XYZ 85.039 781.388 null] +>> endobj +606 0 obj << +/D [2702 0 R /XYZ 85.039 761.463 null] +>> endobj +2705 0 obj << +/D [2702 0 R /XYZ 85.039 741.134 null] +>> endobj +610 0 obj << +/D [2702 0 R /XYZ 85.039 536.885 null] +>> endobj +2706 0 obj << +/D [2702 0 R /XYZ 85.039 513.567 null] +>> endobj +2707 0 obj << +/D [2702 0 R /XYZ 85.039 299.114 null] +>> endobj +2708 0 obj << +/D [2702 0 R /XYZ 85.039 277.353 null] +>> endobj +2709 0 obj << +/D [2702 0 R /XYZ 85.039 255.592 null] +>> endobj +2710 0 obj << +/D [2702 0 R /XYZ 85.039 233.831 null] +>> endobj +2711 0 obj << +/D [2702 0 R /XYZ 85.039 211.464 null] +>> endobj +2712 0 obj << +/D [2702 0 R /XYZ 85.039 152.04 null] +>> endobj +2713 0 obj << +/D [2702 0 R /XYZ 85.039 116.73 null] +>> endobj +2714 0 obj << +/D [2702 0 R /XYZ 85.039 81.419 null] +>> endobj +2701 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2718 0 obj << +/Length 2637 +/Filter /FlateDecode +>> +stream +xڥYKsFWjLOٵv9֖+I%9@$(& +-o=CJULOO{M Mu+mAuYD(z-_9Fez[Ĺ{l)MB z'&o+q|4oJp)q n%}.ƀY{h +]@2ů?~U{QZoQF7@ߨkϠš%g‌v1ə8dai?2'OP,- asAukD<$Xd,x1NLnrtY`^Qp 6..,/f D7-ŀ(910"p$>{+;橰!]u\ c bX"狄MhGM +q63׋Cp_R0bg~C&RuE#2c +;:J!b +j^3p'ޑ Hٴ14`LW2: P`Vt S!n^)랸z'KթT$5\vsp06%='xad,Lt0}PF>D#vZ{Rﻒr}.xdFȀvZ#>Uu Kkm 5zJh@i-)L5= v#Ӌ=+O\ڈo|&Z +J +%2"[+m\k ?um +gĔ0=)kgjERR1BH +N׊(0&=5zvXYMz 6n +L\LEAKj^/3yB?«)f|?7=CRs$8 =JIpұ(g>*:&D>"CWSIP.r=]o%r/(pFӣ'O|7" /*N0{>:Ljt]~ؿb\y?C7 Ck,FN 'uڢ3Ry#0fApV6;ٶT{!-ES#)~y6oՍI +_#v?25VD&H$(IZ66}wAߦJ0hhG_Wndf)_/rZo|9td)$هK%"SQk,ԟLYL +c|y}N9Wv,>TM&7zy^On?*(p_Tq<yYendstream +endobj +2717 0 obj << +/Type /Page +/Contents 2718 0 R +/Resources 2716 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +>> endobj +2719 0 obj << +/D [2717 0 R /XYZ 85.039 781.388 null] +>> endobj +614 0 obj << +/D [2717 0 R /XYZ 85.039 761.463 null] +>> endobj +2720 0 obj << +/D [2717 0 R /XYZ 85.039 741.134 null] +>> endobj +618 0 obj << +/D [2717 0 R /XYZ 85.039 339.522 null] +>> endobj +2721 0 obj << +/D [2717 0 R /XYZ 85.039 318.325 null] +>> endobj +2716 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2724 0 obj << +/Length 1502 +/Filter /FlateDecode +>> +stream +xڵَ6_!(B":l[wy(%WuTq9(YuM` s8>'=_N2hʛE`9|'$FI!u^j]J)E =wXz{vx{׀|Z47b~\x](xߋ}~]3` iQ,8v[\/~0-rQyYI9(35ՠ-.0?Uoo ^` +ub{sڢ*篃eKTdqD[2I:7ĝ770# 7L=uLԀrK3BN°/)|Ez0WkX[>$k80fJ4YZ˗*?[[ yp$f\ijx{4v5mAAŋ p'`ũ~bjK>? h3T/%3(˰ks=<@@" [ ں3uœ- Q(B^ +5ykՎZ>ޠN=,̼4̜ez^JxYL%-8(\ypOJɸBEUȸޕ>;5謪|x0~b+c\m6}8^ORtlm0Y({jt-6D3  Tgoeyu"tCԵ('{p% 5X /&D<9רO]4nqd13糤'sOmDi36~h7(ZSD~r )ϒ(̘cVSMHDsW'=3f.f?6X_=Mri2'Əp3N>>K*e_eo?ۼE9w*0;o|#~ +.G[{O9qj<5 ,T-8L rڊ/1yc +u;ZQ1ُe-U~v& c(Y<庪amP/vvqŠި;hS +*KwU}FpLQS#Eg rendstream +endobj +2723 0 obj << +/Type /Page +/Contents 2724 0 R +/Resources 2722 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +>> endobj +2725 0 obj << +/D [2723 0 R /XYZ 85.039 781.388 null] +>> endobj +622 0 obj << +/D [2723 0 R /XYZ 85.039 639.867 null] +>> endobj +2726 0 obj << +/D [2723 0 R /XYZ 85.039 618.671 null] +>> endobj +626 0 obj << +/D [2723 0 R /XYZ 85.039 549.412 null] +>> endobj +2727 0 obj << +/D [2723 0 R /XYZ 85.039 528.216 null] +>> endobj +630 0 obj << +/D [2723 0 R /XYZ 85.039 445.408 null] +>> endobj +2728 0 obj << +/D [2723 0 R /XYZ 85.039 424.212 null] +>> endobj +2722 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2731 0 obj << +/Length 2950 +/Filter /FlateDecode +>> +stream +xڍkoܸ{~P-%RW I;ň^iڵ.z"%Z `Cr8/tz'"_yGX/;PaxeqkVr ^ۣbWb7hǻWw<7vنΗVGs nP6Gߌ|nv;Qg\_̓=հ}~8'ApIRڏP9pK^ +/_z{Wl9m]]4 xr6*q<3CQ#(u/.yN'Ə\  =d2\x `7XhZR8BS)=j;O݋zwv~ll_0Wڼ`Vؘ=ЄW;IE0k9CR+$W~h2 a[_zd9iX5b<=:SqtMkG[51% !XK`188t]e/jBC^Jkj?)"dWBE6EW31g;hv!"ӂ>JPt-ȊZl\RJ=8ij8V^(,PEk[A=-WB3=c.^JY*Et8`@u?|Fnvx`NjɘM˔:03\utd; Ӈkk\T-YcUNfX NofsA$o1.ȌAHc5F'08Y f#BtB!W9C"dvK_Cb9N -^cOH&9p)⟌PT /ZLl]7a~y04Ԧ'6&}aRÖWYFs0±=(]#pO x˕-ǀ!E?2 1ɠ@L|mw%BGʍj#8a dwc.nqffӞ\hj+)/ P C1𡮛 FH[.R6?f4R%ǛN.^r2;fclz9~u/<@|endstream -endobj -1604 0 obj<>/XObject<<>>>>/Annots 844 0 R>>endobj -1605 0 obj<>stream -xXMs8WTIԗÖwR)D[1 hZ} iqf*2FׯjN3zA%,:Zf_jv_j\4-m)WXgVѦ,ZV_z5#fMTB.2ʔXkKTKWwt&Uiwtԥ?2/zLޑդT=tI8וqv~Ռ&%ۥ#>Q3n}T9*\jg92jw~Ox6p//+}LVMHd*Gv&:O3[W|swrXJUd#lQ5INN2ͅo7|M2񷏴gsm`)u2l{D`d:eQ -Njj҃]%mչ‚]6% vuzO՚.ju-**e"0 7X~"ğ}>+Lq5 C8_,D > zt2>cF{eJP+o{i:\BǙsV48Eȁ|D;&W&d~Voq= - -keo'֨֒Oq >qi*S+$Rh`Lh( X0nED)vH/!Q"aBE(qvo5 @|$uY"HI yDn?~;?.5xL,<BxFWU'Fah`4U2="JB+.#\ t#dV^IQw/ES\2?_> |>\~ -wT 7NDAP3l(?t)aI9'yX) <)+*W OEU[Wyv]jDu8z2ђ.o.d \iƪ|E_qh:AWhv:tO - cDOp'khKWmaURtDOs= 6Kt 1YCT8P5,Yq PbhM殕y>] *il}Ёq#B+ sbU+qgP :H1vyߏ+$:/e/hQ6ҽ q!`p,"4: ^0h pOY3_n0]| 48Qf<ۗ\3eE0p &.UiPAD2;Q~.& (*\hÙu%'h}=Y,JWsᚘ B(3LCΥ%<.bC8Ssw &Ϡ| +Wkya-\p cC]]F**mJ| $gЀ 3%@.̃ЁZZɗP}i=X릕U%}1kB&w0i9‘ݦhE6KZ6]HX?0 ÇMlς_ z(i峟vW?.qendstream -endobj -1606 0 obj<>/XObject<<>>>>/Annots 851 0 R>>endobj -1607 0 obj<>stream -xW[o6~8@1u%J H׵Cm2 Dl(w/lqlwnߡ%o)LPԣ0:.5ſV@e,yr1X_~0J36$MY5W O -nG)Zd~-Ml{ZyEce|)Ÿպ{j$n4ӸVyB7[>Ib{|Jm D@Xx. J>|yy٘+00 3]P(ki`+JQ^uǷ  1zFJ\E9?0fp+tk5E_ -uOb$S!dM>2ot-ke- n:2^Қ&MY*[Jacyv &s6gȁ63q7c+l_hl͐a\"FRھ!gܹy0C1\n~@\7a#lah hxJ%\ʌ-A`UAdt" -4" =ˇaѡJ6١0-h -rXZ#ܿ>ڪtΰ<}ҳ̯a]-hgOkXr)v_:m}26th=Og [p'cSfGg^7@1 ٵ(6DWxABT(z PHj|=H#IVקm=迠]ތob%ѲgbGJϫ?czΜ8pDh4)Mbqoּ3m>84UKWCRHd5j(Hi`WUa}{f iZP)(D5^r.мH0Ǖ4Jݼ$eroOܽW\͛h828 -LXb3Qp0B8:Ke,F5mQ/Qߜ 6uD &ƭx-W-FKg^-5⁹Zl^sRνd = V2\dɣ\ Dhenkjmt0Eq>slrCRSRVF Bj0?VJ\ FtGUlP~` ulXIB`F5|‰ػo>^-@j{ÏvN[f C$:*$o*, O,H19 |2d&8=g;W6}q_[ -cK6Y/<0SRo,%|5𹷲4[dl1I/oA|Wendstream -endobj -1608 0 obj<>/XObject<<>>>>/Annots 862 0 R>>endobj -1609 0 obj<>stream -xVko6_qעŲ؎`&)2M( -ѶRTI)KR$.8`H1~t b~ 9bD 4DP]X ֆ{&i8ESxM[Lͺ0K>x$>hʡ%7na`p)Hv2ŗ,JZ晥?TkJܗ6R䊖F7}=Gp7z\s^oDߝW( -&RQZ^Pk -K~% =o?ݙTxAvԢ EA{ZRRf2|AJnh%p54~~݅eUZJ2Mـ@@ՃWWya/9̅]) \jR3G"N;wqNA.4p&[K aWؼ\\-)euR|A]ӝ#Zޏ~zty{[gS`@qэO ^ۖk<+sDus ڳL%QHowP!/RZ0p|D7ta=uү9kNE1`߹?w2s10VZCy:ٕn^0@^.ۓyuvkjyL=oT. eBP G>ik_|mizn 9# -vYx.rNMM^!u2s;t}i@lY*ڏѼЙ敶6d}/\ -SEnlLxO{enRt}w&虇ۂl5>2J"[@Vi7a:-u& -9\!'LwYiyQ[ke -p1HW07Uuȁ '_STSe[KG'`и{L"4)RsNqnH+Iߺ8gL.4,('+,1nKpa-6hayR+rp2A hLB!(A,1lȪmp>/XObject<<>>>>>>endobj -1611 0 obj<>stream -xV[oF~WHZ1BVZUIQ7.nJ2cĞagaQ|@E6({ΜZpՅ:WBR k&xc01taԼm kho>rT4ALa2e"W$8h bơ@y甐BI֌("hQu^S@/)(JH "/@ XP )0D^>8wYkcb~)..`*㦟+""v5~%ڋ7֛d\NnqUDFqn~SN>s~'UНZ4=.tG1|2<.14#p2{CddљE&k^X<¶NrY(0ar+9K>bZj̅^`䥲O*ʃPn ?Jlz^נ`u2$;{p@-ѝ"JmVZ-EƖĺn/6"P͙oTG1Mɘtcf8]W"YZK3I#DQ&$O5 STUK fեZ)D]ֱ8쾍VY{y\ݼkSCһz1a;L{{4$[e'/?Eބ [4V@WHS4l~X5ȏ9c s\F 2ze - m(xziY/YHTɜ)1MQf}I7֞9C;Wq1x193 -3j1&Әu^q9 KdGX)玢s#B$NY[U#LUSڎ9wa#ˉLvY8mͧ)4,]'.R*hU>/XObject<<>>>>>>endobj -1613 0 obj<>stream -xVmoH_D4=կI݀ZAhtcoR{7x Օ.i.!Ż3wI]a4v'L ɼx4)IAҾy2BbI&z>w$su> 'nxZVI*.\&ZyXE?BT%U)Z;Bͳw:A!;ad9[ZV*OKFPV.\)@Z9ҘR);8!጑`|:RF٫:=#^!7^اX R^1B?)Ys :9SZD9%#b$,ZKrLdQeF*75~+0h)/UHh0UճYICT0944hA=E%u)P}>ޱ@_[ُO,]Ii*pR}@~^zJPՓ -CwFn\qɕ}P%7Xj5kM GӉnZk:wt\j |]iT1e-,s:c74h:v)A,TfVMld,&4IL.-?N6'M,D -uJXtf``n`PڝF< \;s -x'L3ow,vo -tЬ'wljd -dJ-FL-w춊k޵ykEC7VV=S8 TP)_7kwN/>ͨ5ao#6NjtiADѴ~/Og)?DL]ltZ7WQӭ3eԖʞ$aH&#ꏍ_/Еendstream -endobj -1614 0 obj<>/XObject<<>>>>>>endobj -1615 0 obj<>stream -xV]o6}HlJmdn=dÀ-6cTIFlζt8"׹ܫϝb$4pLiщYLGӉdFNt[/j<ŗ&iv?tb6AUTtIѩVX\K#2ZjC NV0').K.H9~}yl#O2YQpK&[٣ QJjEݒWkۣ6u٣FZRZ$ "jk\<|B3[?30bV~ $~~yM"$UrU -d4m{6>Wks޿? 9Ay#ܑ\Ǯ9r | u+"QTbY 3_yF[婻݌(ITȫGryYlSUF(yN :=y*FKZLBqM,+ C`RM%dC6Ƈ~Up)d=bxڥ;-WU16[nIKٵBܷ#A7u.&q2dם)K)@(CmC` pjP4 }o`03IjXFmQB܄27JPh1r54F^ t0jX {Ɠ -c`+װUL"p{I;o~/Im(!98[v57v2ǂQ y^ K'Vd:3t(<ԥ%و\IaD˽~z 0}.&J9'paOqn:`NbcT~8:SJec潁.J$ՠ'{^e,ЩҨK!JGZ<ӭD@gˬEɽ4WA6V4l¬w /K!^+dLu6yN8~kПh/I,}}oF)_~#üK+==endstream -endobj -1616 0 obj<>/XObject<<>>>>>>endobj -1617 0 obj<>stream -xXn8}W /.v.N@Zt E[?(hPKRu{mYQAvΙٔ&%]ͨ&ńfW5]K:I˳kNiđ-+ ٚJҋ<QQm\)*d4~l-eTK%mtE I]+YQ1mK5dk˱ ]LK=}l -[mh zo_][d}FZ-N?N0jg{P6Aѽ$)ӯg~GFI_'vֆ_ҧ7*z!Z -j| x}I/vN7MqUӂP>~|ͅ_R-UI^ff:\X*EfTVz26̑0*聾4>ː#@W\]Zשv +ɯ [:I,|i/M>-ufᤸEYƄJPE@S 8&r%ӪPa&VRmJ Ldc]-tN-Oho!O#HPVFh=T!A T 6 1WI -F,` n?S-`ԙ1(H2.&wxJdCz3kgN|zQ~Ej{* ek8yS -$I h"T^p\l:2敃o @?M? 9jB;)-PpKv&tkpa,;н^k@b A@L23xy_IÝKX=1ŤsA-d-I;7KXŤNKհ#ѕڷ^7vD&Gw;1k\IqNhY  DL|?)+C yDcw^q~׿ t;qNAԞG&N=: cԮƯML[dYα7ye2빯CF o7 oф.;(_׉XX^wvmMħM<-=|yRܛR"}l'wr:÷wW~ ^9?z}p .ƖMɴ]/n'X Q{{7 -=oK|Nng 9;lendstream -endobj -1618 0 obj<>/XObject<<>>>>>>endobj -1619 0 obj<>stream -xWێH}+J!4[FBQfZi%QnCGvӗLo1dFca}ԩtB/ЬxDW U00U[V1 )Q9ɞ<-jpSN[}FQӃ $1Lٱï>/XObject<<>>>>>>endobj -1621 0 obj<>stream -xVn6|W`,_b;}& ``@@K]ԒTCIquj̙`L1ǴtNI9.&hB'0/婅I<`t%m2/"%ďc$g~|4I>JLѢ QPۑIm?~YF(EL4&oO?U¹~&{DN}j7~'Dמ$tWOsOɱ76Nkt;!p2gHΐHS蝡BiI"%J{J o ғU(-#9(Sjm!)䆤]C.j/ܛ=d뼰V rʕQb~gM] -D8˛3}A\>!Ƌ?}R!Z[Q - t]n@(g9Bп)];)~vM[wp^rev\pPIziP\Be T-JpuG-oQ@sV~N{M 2/$L~v3m}V GzecZLZuD4l%Fh5e urK#=?ԩFI"Zq5?8đa}8l*@=RG1z\C*ڵ؞BEnp9J[0[L*+0A4B95gkNƛCXLנg=Se* ` 3%6ln%Ր!S`8͔k쁧MuQ-L2dښ[;]+m:dٗ8B -tA/`_<\ *x5Z43ek2j`~96UVPr7R2R<Ÿ+,:NaN-a4i72_;"GPw'=?N֥@Tk*tk<=>\sɟY>3,8 'E `FyKb>1^Ԕl> M+#Tqgaʬ4C#5Ledk.Td \@K,kl=f<dzrJp>^у5qҍIN宆"ⳓl<:x' |tIendstream -endobj -1622 0 obj<>/XObject<<>>>>>>endobj -1623 0 obj<>stream -xW[o6~ϯ8oN[If P`I@7@KE5+.(X"{R^՚b,h.5npu{\?щwZ.hC mrB>. -8i(]'t:9=JwD-꽬d^m=+Jply,qP̜5 d8KNSOR#j -iDIVi! Tw7qt>Z"T3ic9ҫPh:܏8n<42eZt.hCBRkQ_5';%QV%ʌ–*s$)& yCul*Yq{4;]Ծ5ӓ -6ǜpkLz\A -}dQ^q>~ T~V6wGN#듲!ov,w }]{ DM[?<U`q/o??H+"͑nxüR"Q㹟uH4!m1FfjQA\C9 *Kn=KHȑKzZ;\}[ 9}TmCqg)<:`2 : }!qF6'p5#|`@8n|B`܋L4"SĂS?NirJ]f -|6 eƓy'iy^{DÍ|/tմ,uA |rIֳCPB)C@P^=/=VN'.߆'x0%:^RUj9t̑=Z.e#`xh}Up{SƅyO= -9U3oM_1 ->pr|jF) -$)jB[ p?^7+( U7s{|K1°9<z;J{,$MK؆3a l[ְHZn9Дa`U6<Sh -6<rr - 89CO1a=W tf7yJ7#"أ9n-T ~Q ya,9e_U_(2NgS2~igtE*3ꝣѷh~ g GeΊX -*{,zuYNu{4ؘF>o6j6%춝@2xSo;(v;!ɩG2/H [YY\OFp:QU}@B6CCKoQA~qj>/XObject<>>>/Annots 871 0 R>>endobj -1625 0 obj<>stream -xW]sF}o8S#Ўح[;I3SaZ*sW&t #<[HZ4|,^ZӠWOgq04??![ ^0<2!]/6էFl2 -BA7i@xD{ۥYrXp XʵԎ&|p.JYrdI)wd*yQzIFӻ?罥sp.>3KϯҵʺB84n[0K'w*MAy݋W&Nc!yj3QdŮ$I[Vw\ EVe1$$ZWl$L+38j!! d JH[-hgJ&"%6f-*h.)/ %p{!hhiN8S :ŕ\X5EZW%\5.8ʇQ>HY!Ek]Qq\Pt)d̹8nX@Q F'Au \x\+ +-ve`K:7|].[Z%{ 't!t#YJ)/Qĩw_?MZ"]W}ު]I5[ -=ҭRYVo&לU[cu: -\Ւ(j9dch^Ar$֢c+HX+kf#N̩ -D]U-H<=dEnEZ4- Wax梣еE Dq+.wGiXRΓHHVݾMU-ڽ`4P;ܽ%%37"'^Gfxo;eg)|]McCACmd &U6>51@[fPyĻ0O,Lnw"7q  Džy6()dY2k819k%0?S]ScNk\"rM5ǼR^un'<(۽^p`\- n+9bcs QE`;~l}f:mdܪ5/8~x -Y@mi:Ԏ]H$',1`ƒVlV!omQHyl94wOQ,9ø˚T:5[KWZlrRJ#TKq8ԏҗԅh1|s/ՋJOZrX$h~lT_V_8My"?iAHΌҊ^(0嗝f ktb,ywۻ39nn,͠tF,E^n;Fl<0&m6JpYC?}=>y2:?C<[ ݛ%0N -3,URո n~̟`Yb}1Y p#1XG[!L -J]X -KV0X)V-?~7):E+',Bpׂ -sSRWSѝ`9 :]Gj>/Բ qIQѼ{sV(gM [Zh?2Y^ *Zr>/XObject<<>>>>>>endobj -1627 0 obj<>stream -xWmSF_uajf7lN2%`CN?TpNSNOݓ@t2aO>k iB.q;l4i?qN}pLLs!0e#d"w2Dj,R xʾS2K#<3\M+ԛ]=A`9EXq}`IcfO>Dd7rtzU_qf8yi#cB$"= $@(wp#e:4.')c#zNyD)fC-3s/@08ere"ˤΙ WusLNrEdqnSY@(VwH@ o(fI߿wl^` Z]SD(KA$(AM\V44PDp /а~iEbMFh8T޵ͮ]=e0F@X rV7nm=Sxa:%U"5풗&L09 I |8F E̱X Is/YXgpxikRX :'%K+) 2B:͋ X(" -H07ujKBj:֊ռuv)j67y'9TJ$Јj-\${,WW[.Er|mVx vaeBxGO.*CfG`2E1޽w2-dkIpm`i9%N+ -gj|#"׋Ϟba?LX3ShܰGΘPBsXp8lT-u̔穪68h8<sqf -&24K:/##xR@D - +T'b -߾mi/4C;*wzq$&~n07nOx*()vIRІeG ~rs?I ?? `Vp`O[zaxF0mNBt!jϞz%|o8E5|&I~mn鞴p[ ZL+TrQͱendstream -endobj -1628 0 obj<>/XObject<<>>>>>>endobj -1629 0 obj<>stream -xUmS1ίbgЙr '2S &Adj{7zvMgsWM:.i@=jاBR>c#]b x ݷˣO_k;(ώex|^fýxZrND?q?ř+ 7:myán=;G/='%pe l9!a(E. D!B 0H1)#1̤wp! -% 8΍)3ay!l6Ao{-KS*& })FQ'h9 aS^"Ԛ9U --;{\LvRN:q'NAl\ĶrT딖66u$3|Rȅ/ EEqgQ=犎:Ēߪm&IiA`T b$G^i3Љ\# [YLS̭AݲzCo:SLjrpĄD#դQըذֽjmax0LfjhS6ADߴnW6u-9PŌ %twDT'v)%$mU.xh@hCqz.g:q7Vendstream -endobj -1630 0 obj<>/XObject<<>>>>/Annots 876 0 R>>endobj -1631 0 obj<>stream -xXoFb/qdYԉsUNZ.=\uwiE%%mAbSo޼揳1]Ϙn't=#]]eWϧgsicC(I׭5`B2HSnEWUXyi8%]# jKh f.|m[6YbSC'۸6AGݜzXt3kL:&4]N\fsRsKؿbV%z,i׆0XZ/)b5#o³#(LHrs9bJPkMZ87y>d*Hq(J[QǍyN=^e ϯ(Ր9agKoӦ5|t O{2^5K|m+E& 09$GY~Rwg|d2}wA1sk{ Xt \iu%0 V^`.dÚH/b@شݭ&\f[ #ˍ!txWzA׾ 9x|S! -}!u^I<Խf^wL;0gnOendstream -endobj -1632 0 obj<>/XObject<<>>>>>>endobj -1633 0 obj<>stream -xXr6}W5[6uvޜ;3vITHHBL -ZtvDO>_Gcߘ'4QZ}&tvq'_jZӳQ2tz+~ oh< -Af4F#+ڻ2G -YSh*z'%=yGnc/_wv&)Y4aNzm|ReO?Ft:&$1l&{:cמV+dRϧՖR}ؓC*tiX7mS}ҋG.M7Ϊ<3&K -F5~#Nt1x4w̒3>w6ץC[tO-uI+W,y˭xI}B=}Jr REr~&,V.3҆D߆株/͍{Z/@Ӑ01v.[+DY+ñR`ka)PI~kaU1_ dCeU(%jjyyq [4*P-R%Q]8z|IIfn~~FOa<Ƃߘ\(`o0w塷lH]u41~-*/ -CKg;RH?\eLX~=wfƦy61в5kwg@&?\h^͝"4pg"nj0fxzq4ŀ2OTiqRp3'^?X*Y#L(Š[D8`f/+a#w*]lV `y4;J^<ӥ+lBmԋ29 $%Τ0rBo\o -p=V[Qx ͺ>* SrVG[l͟`TUÓI;J.ΰ =aE'*K00>(lt| B/j{FE vc^4==}?n\qwkCn5²ɪl09Щ ء9mlllAABN(DUmbav,Ѫ*bDRxYpMjWKq*2?%\Q>4VӄZo5^iH=cVhq0ؙb8=2E$!46gVזrJ[40 ڊ=.# HԜ9_[!ى@ ͔g -B{bdbX -fn8:A FV0i84]HֵJU)7,®Nc6(*T>C(K+UHa(aryX0w}B|a%k fY!::"-اnYq銉"pk(KY9 ;vL96J۴%0@;h2/r|3a',4YQ3>/*ji%WuYWqzRiڗX5d -%?]K34@ņAFH41eE1MT'ivEu(=}uiŕ|a47Ak@8'ޤQبEVBVKOA]k+2XH++*Pd;OW.l0*x"4%C(N{vFf]׮ ]L|tu$6._bf7`^6r ( endstream -endobj -1634 0 obj<>/XObject<>>>>>endobj -1635 0 obj<>stream -xXNJ}+Rbr>T%ВJLI23cBן\ -!ok_G}OSh@>4͏~QOe;Gc:?Et>nztz=~sq>iB04>.vTZG gG'ӟG=acՙfڽtDMMI5\e:!>szdzeYDwƅc6&}'MNaY݄jwCwl?4E]_&Oʋ!@VR>6M[2z\h:?{Cfw $.98{{k]ѪK&㍴;bt> ??L Ҁiendstream -endobj -1636 0 obj<>/XObject<<>>>>>>endobj -1637 0 obj<>stream -xWn8}W .(8in\t -Q6[TI*~ %QEıȹ9sf`JLtF I6$;)ƯTʃYv:nyp MOiYlJ˂`2e>f.Ukct箵kОn\erwؘW4[ʨ?@TXMBsSZ-P1v )n%Pmȕru-^|]tM4rdǴ\׮0?XJc*׹deځ Na<ʶlTd7cuHF.|4ۑ G&xnW?0a= K}-sNQPI9F¥ڨ@&}ll#6$JMpg{j0C;`$ݫ9<"oM̐>H({Er(zh6:R0(Zٜ|r†82ŹԃZ5P ms)Ŏ" տ@b!{l1s,jqH'o{=C ]a"7J{gu{au[o"4wݤ -?[\iS⸁7I;+u{B$iOp!8beuU&= ńR;@|Kn\`u㢛>#8q*H%Om7(w-B{'^dAsYW]-$-.w' K%`0GP^lQ:o׽ GxF8B,;+[ 8 Lvj78Q?h Vo{ x!LхkĻdWdZ^l4 -晓y: l~}}mbdEfm=/ ̱Uvܙ6*Fܣ*Rξ2g4M6/loXJr:e]NM3 ;` qKT=R]4ZFf#{%w=g *8v-$ɮ ygJ\'IDL屵7 Z -E,{wd(~Иz (3q_ܻʘbiLw (;x|;|jz1洇6.I N/ Vu^V+E7/ OOvb -ꇎ-\/LzO!6h.X$on8"vI) (ԫ;aScw"{?, cMf@F2JCv5LvN~ jsZե)8j }[wuϺ k3s*wy$AIWO'ovu/aY8==a?,8E`endstream -endobj -1638 0 obj<>/XObject<<>>>>>>endobj -1639 0 obj<>stream -xVr8+(WIHzI6E-%@)گ!EӖe[Ӄb+yBeq4&4]w|Wwi]l:'i y4ѓK&/zl&S慾eWpS#y4Cz|Vk{#byK4<*قSl8upZeJ!yIpJPpTΩB ͍ 5Jfє/=H+9n rglkw'3Iǻu^ZҳQ }Q݃1w쁀j0+`386]WqD>kiyd{UHʑ2{2`V. <ҷ'9!9n`/jg2DYj%r'd%q`'|8$b@yGVm&`g'2`W^h<9Q̐NG[ 0/[(Xgꥮ.%4X4}e"UZm(N)/d'a?T$}5d]vKm(O/B@3K 耈H-ݵPx-AIq<dVw!@*ųlU#23&VQzD?0Ͳ딸WyL hPQQ#]3LJVڏ=}G=$jJhG - rX -L';88űe֛YWo$$ -jFz!$1,螋Dn!g\:`iu)[|vXD:]*+v$08j-Nإ2+I#R-s6ZNd ,5D"d=a^ś1 ,mވ07g  ;ʉ0ue$aO͒e +Eݽk=I9fK~YƖfYvS <0s?I 4\5l离֚V -mwYplA)qjFKE"6/r[v;EHN'L&s A DlD`Utc[dGg^Obñh -mc6Ѽ*Q0evVӽ:%cM>.P<Żk1!h|3a%>_.Jl^Ba4Ṇ+8(=ȦE4IC8q뫿;^endstream -endobj -1640 0 obj<>/XObject<>>>>>endobj -1641 0 obj<>stream -xWo6V ز%;3`v]6^ں؀z(hH*Ru)ʮbR%ޯw1/B_Hs.=adؗW᜞+z{1 &4σ+--)u/p>p> f}1~qMф)қ/NyL$<ۉȚe@ϥ~0ZY.V^4O[/yMgq `N"+｡vg|f>7SOX޳}uJzw<.w<4Fdȴ1.e7 g$zcdQqW|HmL#TatXfEaQKP$GB_ӏ Mr 0 hr093\fqn"}w(f 54ƨrol}d؅xvhdA :%;m%'6GwDِ$lEUX6|7k87>J)r5$i/BaKqaEt+DVq[yrD(]"UYrV?axյf/e kΛ+a~<~vU@@ks(j(⻇21bW}`ٶ-t -o̮n=VIIb;褎WKOܤpO78v(egˀ٣Lz(PKs~ý -\bp4YUvv=&oNM˜ֱZdz+BJ;#_ɄtڋC8.,c~:}8_5nABk_9޷z%G+\'ˈwY.8ү닷E Cendstream -endobj -1642 0 obj<>/XObject<<>>>>>>endobj -1643 0 obj<>stream -xWkoF_P$ZmE.y4hIamQʼn 'zm6D䩪L9mز?eG=yF*{NC\ȽSN:hz*wykI1;$ 9A -3Ja%c), -R>V^*7)u);s<=07r֗uw_[w#lws}$#i59z)EHYVm4 -U=J ^in0bܠn~ $\鰵6pki(@a#q , -{\k*ۀ.,-쁨XH0am4xW%"SCTZ ۹%inBWne$ʿ6]#ؠpk m}_lP^WWv t />3ATUh$C@SRBH5k¨=4D*72P7Y(3Ȟjm#,E -2dHq@W%#'׭3Sx[\!I ft#*kvD(6xrg z*]G|C,ご!Y }@Z-(ў2_`H8JVD4 ߕ 3V U!Ā= f ჸ2>Hd]@y3&и4qٞ!CZPocʼLᡈD5m;ك^kI^M!I\Dq[7%*{g|r G〪a -&/T[R2~ |uKfnNz2$>8,'-zhPm dZy -5 #ק-=Lvy~lGZ/e7tZCPJyoKOXd %͓׋5`:"/_: 跣endstream -endobj -1644 0 obj<>/XObject<<>>>>>>endobj -1645 0 obj<>stream -xX]sF|ׯK*")&uJXkXf =@P|WNʔ t꯳MgFs\PVM8%7tusso$/.>]lF5^Y\2'<>2;$[IO3]ЃP)ӥ{0vWN!MJXI>RU>fA,)Mf229LIUQ7#~܊r%JsDVl4/05ʨxp#J;rQFjh\K[qHV)j'!|\q˭6<~TEd"ۢBg(N1ksG-bsI hMZ;P9꧚JAxD_E>YqJ$RYkOXZ7fz5~8Hfۻ7z PUhd#]/&u_\P0?]-vڸ*yn`Bt$:}`vx5? -= podM 0Pxȍ=׹ %UkY1=t?͇YZR5*ǿ1qۢ:lܣgRLUlOFT*]YRpӴU{2jeMHq|?y)Tfp%gL˞) e~tб4VA yl*\VrPCצ 1ڻ$!r5V,U)G@$ꌪlɀ8_m*{wNd M>\BU@Y7ےK}糄]dxRz߅>,?o~w<~L4o -&&iKWeAv~gx͜p ,Bo0 d$Uoѥa+D˘ S0!%ĉ9uzJ"˯t-1/K/Zl~l9LWR`q* 'L^cڇ(/y[p{BJGݲ7)۪% xKꃏxa-B%g|NC"Cō' b|{ڪԄ$ݭ=&(.8;<"~c_g^x:DrCDxy%X)Œ -T3VXt0 7PbcGoŭ<=Z>^lr" _d&ɂQBpEU6ϢA\5*Oz_u6p쉝BَM [ f'28WGtD',:֊6hu&} VC˫tnAc&nKnie'yՠЃ -,10%?%AEypx1ʓ+h - x ݺ!Q /SMԋOonY2ǟ~Pú9tzqk;GHCL?ph;h];x%c7rvJ{wzkt3efH.) $&poqF!{]ygLu>/XObject<>>>>>endobj -1647 0 obj<>stream -xW]oH}ﯸK)/д-d MIbj{gLȿsgl'1 -TH{9z|:tBq~0F41o%iqs/psoJk'7}9w?;O{\)\ dzNaBHr40> -Wda -TE?݇c*+H3I&AQ37G}H+M9KUq৻qܫS&G"ӊJ -#Zfǽ#F0Ր+)SeZ,)-J|R#Uj~L{-jQgY/v[c)6:ETY"+ c?KJKҩ+tpj(O+COɋ^5Q oNmwiw-A+#fdYtO]|nLL`VYۤz΅WzHBZf?KlT9^R |42QC !5Zf ƊHd  bPћBOQS6wFkd[!N'q]U[B UM(ymdN - P=Bf9 L"f~Ee 0,xckdˉd.J Tqf+Y2]7^uD)Xr^}Rg"ۑpOw{2uc Ee gd"]q<-}-" ;(Н+mثl`XO= SO;灀酴!@jqKZĪ^J? %Q[4Ow]*kU=kcY 63k5KҭZ肽|-`6OiL4( -&go_v -*Z YyxnemduH7th'4ؤRS$^O_O~Ks^``*bt<Ơ0zAM2xgxn=C*#\b)Ʌgs3T -;:\ĐxI[,XMb\A 4$=V,ɣ P4|A-Zaqڒ F>HZ̶)5q.,.MP#C<_0cNw7mUJ!Bk3yMܟ&l._Rs23fo n$rѨ @;^A/@wNYt{saW&@`Sh+toÿت휷1X*ܮF {vd2qT53vk.?jFf%GLe맂}x%Zn >s=B`X6a r!YRS b/PAoV޸ -۞s +Q5uX|.6h*W|xgswSMÓfзT RБRal>bv0oo0sm.A.e DGlNPeT(r,T&w%W;;L4V|9u\6E&Ruj3aF -J>W`!3OrX˿o!i8qE`լ0%+rJ >pŵ7lzMF?|af3r S:>]؟,ɻ_` ->Kendstream -endobj -1648 0 obj<>/XObject<<>>>>>>endobj -1649 0 obj<>stream -xW]OH}W\T"NoYU.q]=N3gLȿc;/ծHUUs9w~?N(^ϧl_H݁9/޴}p#} -bϼAߧl'3 -"~cL{]R(Җ.tS$LDJ\H>ĞV*dʞR4ݓV$Ey|?Sz8>DIj;,Su]t~]EZUzӂLٍܦ]{r-leG߾kEbC - T.,QJ.Ro]NULT6=r2G勉 ܕzs>e F>:-FǖB$&VFcFiD"ϥ(Ni -6ahpe%:җ֢"D1TP`s_qA 1Ȳa!2"_5KLk\RחFLq^ɫ?|or# 2ko[Etz~\LBK(`5&14[$x b{0t9 Dȣm UwN!ڡqQ|3j'omoua@ZQDΫ/0Úlu1@W.2E2:<%ϩB]v.>겒f>JjL2Bx"cǦjߴ㌜]fV5o`v,_./[_oc_c==Bzs*\uw'eQ,<}p3d+@zN\%%'zxGErNu@7@F_Q?^ᇺ,m?B 9z+\wW'6 -uF ;ޅԛ7O~EzFHlw P-ea]yB+05oMaP{WjJ0Mz{h6搓7o:Ȼ2-TY?~>/XObject<>>>>>endobj -1651 0 obj<>stream -xWkoJ_1R 0Hyܢ4zJH^6]C%ꕪ(cq̙3O1/L<É7qK<= ӥ/G}O h4ǯr7yvqqtz=+D4Nh<O>I8T U֥wGH珽gեBet3ktH%ֱ0a:ӼtdcQ!Z&+JD nDo4Oۃ+Ȣ밎ԜZ U]ʥ.(rBєVȢ}: ѡ kF"-4I6qL.֣pBokB#7Z]I3^.ճ4[Nv>\%u ˅_>I# -eUBMWdϴELW$8^˰5eaADX"V9my8,#QŜ'^r炡]:;hvG'omH4ݢ3P*Ln(6\ɇwu~X.Lru RE'qUb4!??~U5AcB: b -܂߮7-q!@x\0Ƶ-JWkj= -v -O҆$ԋjnų|YFI(7i+6i$euD -ʱgTJ\ۋIE(6u=UxU -WJ5XKk#7᜻7x҈$4:{*͵A'^wC]fh ^&-AmBleM7ekBC1r F8D}Q0z|~o\eQ@D*6IYma -]U.dXeNwY B+͆ -g(AzSYm|uyH1f?(&,LEP nfjcb 0'<,4C#kM=7_0p-VCTaЌVEsYO u0O'uJ O7W|8j_/ϿVFze}Ei WrYKgxK4]3nAmWw15Q;,7MQy k:GYy+ zhyдBcMk\C:٢a 7[,-u\Groekq*Agxw4 -:Wan=LNQ#uP+$$0(A")ee ,=` -oh'͐[v4O1o õj%nв34X|wǷE -KLH.!X~% C)4ɱC idRpk+.*`b[@-qm==7|(SSqa'Y+6 VS^ '-JG63-y ->F>+]bEz8Cި ɟ:,&){y7qoݺO.LN~w#yls4z|]-Tendstream -endobj -1652 0 obj<>/XObject<>>>>>endobj -1653 0 obj<>stream -xWnF}W R(QuCŖ۠ -6&w.iI3KR&(45;3g,?}(H~?[~ So?v?WtcYhi8㹏?={~0yyvܿO<iQ{>&WhBːpףepE2 -T-%1eR&RP2(LՅIY -..%"(W= YGE.]cV9:NM-.ҡZ_^oѥ))bcB -J+QIɒHh _d^Gƹ)JÛx눬J3q]/VlI>d -I5"# E*h+4BN{ -9 Bc.- q؈ K!QQJNڥҽb$\Hj0'kF[鸻Zx?,{}&4F\ ?B+ F?B͡LEʬC6XVDqZA`>*pd(E]"GAiX(A|6>&#eB4F"{Si[xSC~f!?2Q 8fo.!h?~CBLՅ [ӒNSQvУ vZ1;gp7N հКc\`23؇ڴY$$wʂS<]= c7[Q F;2Y- M[?c\?tQ͈ܣs ̧(G5Orq#3#0H -xw}m1UkZ*UI/X#tlk0U%E"6"MXgrK]w\ /!]PK5M-/! r!1p9z0zңvp 3Xqlx9(.Xޕk^?4URIRTQ 7Ax{ m\>熰w$tmҬ,5o`l@7n?&axM,X VV49zk jh'wC wSs{w>jvp=]~ZKHbZݙ8i}Gbmׇ7T3s]) Gtw6'ja5xIM>zjpwJOWݤ.No2?Ìtc% /fT9l/]|y_[ +cR!6uz6 EzF7ic+fI`BnuJQaN"})};X|vivw- ?v:4BDfjRҹ|QT|;rv( Y~p3 ˎ|K!=3{ :c+y/,0Pt.ooyRJPĔV _QM+s Lg%l떙X#~nʌ_>hNl[Z#K<&=o.D ^-DpZkXs*٤xԓ$堖&pw~}Ka,l1x_>K+]CG b ! ZalK" _HǷ72u/5KtO|H[{pA㼥+7y~d\b0<=Wǹ(:Ax[sGilFF-toղ.1:adh+QbP/0%w0xV$9 ӲPe^Ѳx&81>Ry!Dw'1meA8NTر> 4a:raMHkgA;*5 +A*a-1)Kùf"$4C2SmEfMZ]vQTZyoM U]ؓIh9Ts +6$8[ܧ1ӮRMBwz1 J=zSt))HB>1o#g *_й 4fpҦhPB*KJxnD$7YB7mO:N:PRs5QaӜ>X,lrsOсu)H~%=B$T d t(l58-ˋ}4ArdryhFZKNȏic/B7w J :"k\аɚurE"~ԮX6Y MpX0ĘZzP 'Jky0m\nf1o(\gVRYyfȓ,CK}fNHj FsB= @f%{`V$?\xWDn +i-^&|+dt<*]xY) lvÔ hh^h2%N syn"s$x5‰0R@B9@} ?Hʘآw`m5Q2Yz!U Y $lD;t X0[itmp>ۏS`9,bNS5];V\^`z]8 \+d, ] ̚)Cxt,(LK!`+2 [!ص2эБ<˵_|x&SCVV=8 6`T`v`&XqRJ:)2 rh`4.McR^#woq-ΞCSZ옕,#BXUrՐfzjTi,L@DZ(jvg(AW34 ҌoBZ6YgL+tKBvLTkmJvA6-RHΧa3/{ r`jj[`34f]7\'MK*hn*dm)k(E2:D8 SS^1J瓹K/Νma>O5.l c_0"굨w~Ey@Dܪ*i_74 /[+n^G8XG XZXXY羰FbO9dˀUѯ e/a/ .Lo=/gOgFqA +uZ/s-r貦5kA?ā0:roĘKɏ*ܾuN7?c]Ž](!<<.OC\f+xR~ ~}Wp.-"ycìQ.W'8OYM[ǹ\58Qpx&Z8_ΊUٌg|݊ܫŨR79+GP^' r %mjoendstream +endobj +2730 0 obj << +/Type /Page +/Contents 2731 0 R +/Resources 2729 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +/Annots [ 2735 0 R ] +>> endobj +2735 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 422.421 153.763 434.111] +/Subtype/Link/A<> +>> endobj +2732 0 obj << +/D [2730 0 R /XYZ 85.039 781.388 null] +>> endobj +634 0 obj << +/D [2730 0 R /XYZ 85.039 761.463 null] +>> endobj +2733 0 obj << +/D [2730 0 R /XYZ 85.039 667.044 null] +>> endobj +638 0 obj << +/D [2730 0 R /XYZ 85.039 667.044 null] +>> endobj +2734 0 obj << +/D [2730 0 R /XYZ 85.039 642.326 null] +>> endobj +642 0 obj << +/D [2730 0 R /XYZ 85.039 379.88 null] +>> endobj +2736 0 obj << +/D [2730 0 R /XYZ 85.039 350.476 null] +>> endobj +2729 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2739 0 obj << +/Length 2934 +/Filter /FlateDecode +>> +stream +xێ6}Vb )iڴt<}X[[r$9{.$%y4I/~y~b +$I]/dW^^]ge5nyHUZzujpR:VxNjH{u!B;Pfp +VvxwOOMp҄ +xZ*lJ3jW,QQKcuKI)L[guvr_/^-^:wa2RB9ozZ78UT*LLcFnr_lxYC8|s[/[E @~ űc qP28P8X$)LڰXM<`X QEAW +8a=X! vB_Q.c-AQ@ +]aЖ1@(j$?bup@ vƄ>Ȓnu]m'8)X>cE)M ϽuPEڄ1b@Hp=ӄ"ӡpbG{{}ϋ 7VEPnw0>%MZGK*H,TGCB@JgqYEDc{]:j$@88Yxw0&:Cpyukh0AҸרL'"]n~{gMVB/q6N(m8f5Vq)n8!*!rg Rۖl"})`b0U]pz!5iZސ~*;'n@wta XY&AސF Bj ơ0m04F))rq ]RHv Li}ixokc|h:JUF,&Ѫ-opb@~0!5l-ˈ+7NLf [2ΚdA>\ԡ7xÐXX9R8ЃL/g~S7Hh )r). \X!C,P,AYલ)7.J1΅v LVV۰)@ 0u:p +NBmFPP&rR]Qym +V\4/4'5ikÈv_PD/mmb%={Jo4:rINre矡q|al'LXl_.hD[Y28M~(% wX;]gQv[nD1KP3}nbO0'&*0"h=Ty,0M?bP|DcoVt|嵐M_N-Bߓ!:,:Ц<+"4(Wm.YL!aI”"MG΂vG5X4TM}pMMJw%5O5y$r{Vg!"6 0\QY~()-.Md[*]qAuKY<jFx\iY3X(Su+BoX#<Ƨkθ8DzJ<:A?:}R_'܀KN}zHhb lxdÇɗ7:1#Fz/)0 /lZwh\#Vx'X#-}.\r*`XWE7L#1_.RsA9\ta_/__ןLO92SznTW3d旉3&l!fMJō(r,(xnXFA)ˊZ**'m#uvMy(:~zQT*`썕JD0GJҜYH`EnKpĤ1@șa?mƏX/Άyɠ(N7_|ʅmOE{DI&,Vy{Gi&_>!g))J}ɑ_r^AV@OiTu_hcV Ҝȼ7<Rt~ЭZ9J7c`oԻ(O_Uޜ8S-ǾNՕ+ΞPb,"F;oVaB4tƪ7̜Ā3 endstream endobj -1654 0 obj<>/XObject<<>>>>>>endobj -1655 0 obj<>stream -xX]OH}WT"&_ЗUJӥZ]0[d28vq4+%GxrN~Lx#?'㇮(k),0pq.b -(xS6wl, E -eaf8! -9sZ:=g|?Dp׷7˫/YDoRMRcTr]Re*L<:kj_(@HdIaAbA0X: I[iŗ$gHCeST] Lƽ-L E! 4~*&B3JT;E\ -RDZ"% -TZ(K2x9;ץB26' (7ȁ+<jaMb>"'eiS Ȥ:3Jo$ap[HK:z\k%_Hm_q1[UrD h"a Po$ Զʘqy"zsۧ\'\o(2SOW& '\LJ4AҺ7mrSDl1:1kKjl4I,\ TӅ7Es8wjfvl1na@᠔6; mHk__N6~gtLx6lMqWaxAs;:]a;+:D;_U@N_s87;P/oh{b,>TMx8 ^̿vNN5Fgt#kҀVY\бQ\HlZr:Vyah+-T-0c`7F}n6ss ('Gnt{x6c̵>!{ @+] ۫*+[t +nv17rrBe/a,kK)jū˴p5%Rq0V5`v;< Qx6kɹF"Iɟ ?3VmQ|˰;Ki*HV0oG&'͙ i>/XObject<<>>>>>>endobj -1657 0 obj<>stream -xWmOHίUBJ%&!}H$pӪ%؛kB|ɱwg?ÿ>xAz;p1~O z=8lX wZ@XbmL~Qi!lmߗ6:=wTw0rh3]8 VlZ,i!悥/ IJ C3 0Y29A Ni΅Їk|pp=l:fuh0KSqiR[;~]'?˥ʥ}=IĚ~Yr)ow<9cAn ?!'< QD0ŏLف액ڪy -Bf" -(er ؆|DHt0MQJ2 -Mtws)裪_6@a,xX *’Rƫ*ʴD,[s〙džxn4knE;pCwBkR&F dO Hdn+'3B91nBЄ~ԌxGT7%)ud{y T&{hVf^bpX*m}1-&ߴ\Ae &kZc%#9S(3SŵFk.C }?rF-{ BM0Y4Hi 2-R0 "Q GC$r>wgQciA%-TZb7JԒE,(WTSs6 -c-)*^qPt\T g^ dE -; Br-Rbȶ -!=*!z$3hϮ_YWldw=LiVyalf~krՃ6-r{2gjP-ϸ"l],8{.ް]-di94hʳMs t rg'Zerlɯ#|ZZr7r'GD]w3_5&QߋT 7 %2ͅm2w_X e.//`BE;͎o鍏a4:_,K}'LCid[ -tO{vcgGۏO3:gm;_<*endstream -endobj -1658 0 obj<>/XObject<>>>>>endobj -1659 0 obj<>stream -xXrH}WKP+ŹjɅ\[XhF1==%@Z cOt>};joPﴣ6 K#⧔|uE':Ó>!]hza;:|xxM'4Nrp vu.f"K;Z+;dr[TeL&gYF,y9ӦVhI1,g3_{YQZEU~3|߀vx͐d.| u^GՈ>"KCv[oЧΥFvZ]ur-ѹaB)- UFR"SQeKZUܧie)FBh댌R*3҅/ンp yeZ82lEisR,W~plB8cT )\Nt4'Δ,`du#Ɲ>vBnh)Kы$W2VR2pflàI.clWy9!xgA:Sn_e&{oo䥃&Qt i. DQȥuJc9˴IM1EjUWp.4#!*UxԯZ]d5 -  FEjtǚ]&P}ϑȧСTL> 5Q%HF f,@bS(UFWhӏd=P44MR:纘hXճ7 7ȯC2 T-037+U8ĄQIvӂ4 T"u?h܅[Sww酙})9Kwu&/T#{a;`,[@ѷ- -`>?3p)NI(-Ke0e0Aݦ0*]aJaj%ەr$1|%W~ι. &Wq&M4fLKŢ4OuS~xD S -'7W*.o\dRv,G=vspy\7eg{x?z=.aS>[,ٴ,ZGm~7Oq48o(hw.;=eendstream -endobj -1660 0 obj<>/XObject<<>>>>>>endobj -1661 0 obj<>stream -xWmOHί!UG}H!)HkO$[t&3~#1u.I;3<3%]:qdlh4c/yh/ >bc};aA/+ TZ2idH4X脺^/-%{(iAn(4 SԑȜIS %Bh^+\d#UV/:tN=DVVE㓈3ق"-Յp6͝?ތo1vhs-ZE WC˵rK^ 3vCWIeڦݘƴZ vLYU.[GXv%j5ě[] ve MU2[԰ &buEDKc -Ivn4\?MUzۀi*nV$u6}'YLmqEӭ Yȋ-̴m|?Z+GA4[dˆEk,$^SCB< K'"%miR^2U1JWwPC&Nt0\t/ÕCyBlƢsخCIΰ~JW6Q F%kDŸ75s&SRh\IUDLI,fHF،A9)?}QZF'RGx)Gk&7384evkO\ ?#6 -sU7͍%XPAM &\HrD0 =[1zzG O~ wl |H,ڪ\|5~ޢ-%1EV]5^`5hunFNr`9|4 "ee7L {~j٧/ |W | ?uNK$ζ-NRKU u5R'ȑ2 KNj"y(*TA퀶ٽ-eRޕiL-Gj^\GK>tdiQk TJMul_+=i,O7I3dA.uNڥDZW$_Ne}Su((UUJ3vJ!IKG-o{tyL.ؠw>|\h[z4zmWLVٞ -%%3ei2 ,m+ <ӣJ _-˿_^ߜW!J?inX֤UBLfApYP -|c_rK'K@1zlnYYi;;W 0057KVt:'v*'Nh g{Wendstream -endobj -1662 0 obj<>/XObject<<>>>>>>endobj -1663 0 obj<>stream -x5OK1XIvc - -fSwKOwa`f3TFG&6+Ь/{vlBJ=I5p=a|w (C@̾{}>bcW@b(GN|[@]jJ nYCߎ!9UNύx f1yB VՖ륢*l8xFendstream -endobj -1664 0 obj<>/XObject<<>>>>>>endobj -1665 0 obj<>stream -xWMs6WLX"۽934qX\|HHDC Jֿ)QN${gğ ]OjNYuv9w7f7=?i%/&xڋgo?+_"'ؿēlPuԞ&cd+w2 REl(LԌ&dbzIUKuqEkcŌBܕZkQ1- -WZBEQ0Qښ&h2+|w%]Lʬ8 d]E槁e:]Fӽ:yXw-U9h2*NmVF闺|A ƮYƮI`;M*ܖ>s>剾-Sjv] 6]K@K#EaW>+Pi@34 -1V+?0`]-MaH/X\BHT~&$\w; -ftrF\J/gBP'ס)[u0k Y!y -Gڐs]\BE8Wye`x^CF4> >QVBpe:Ob2[EFNNtPytwKzX~~a@HZ*NόϚj"dW ď\u[#1=HO4~EzĪі% - FQ;8=i{ʫܬ+vA# ,՗V 5e}&zm-zAP-,uK;C9~тZʂB+ٶNkm˛ lM,x\hzYG 4(͑Q -f1+8VgMvԴc-,5`&l Tcڶ"b0bl%̼YJq.9k(Piqy;3G/&hLODz09 aCG :dMfi&[t΢Sq(V!h!1WiLIcRRBR]kSQ$/<}cSN@2fV "ΦFݪ Q/n 5`%YƄksy-[4,XdUhL0CDL(G B:'IHeآ?Aa ꊦ!QˀŐhND'$Vh2^=<*unׇ7O`?dRoK#4c:YY!5(0.c:wbL4Zbk|/8tnx2&=Zda c( VeS^1v8Ԇ[ah9]S%v*R,:t]\bZ찕 ыqaCvАZXfHJ.p栰|7D{ !7,5+ CK"U÷b︒/Ǖt)lX&NdyqўJ>ړsPgWf.,{|kBt&\>!^mpLyowS\h1g & endstream -endobj -1666 0 obj<>/XObject<<>>>>>>endobj -1667 0 obj<>stream -xW]O9}W\B%}VC+R>8=k{HkO Th~sO&4.4[PQGch~uߧ5Ѽki~) cZgt4їTѴm>W+c^+yG"%p_/͜&f8{m;9'UUT&bUlؘ&BkzxhG>s4_Meգ#Z:ӛc[靮ݓ>J<L\5n zf.[\ٞ͠_U D'%stхY"yT!̓z]nM1DRB#xHOsvAcBB]ؿԁ2N-Fjv9>/XObject<>>>>>endobj -1669 0 obj<>stream -xW]o9}WծD*BѤ]Em! *Ě7MmO(~|@GyX5UPlsν44P ]ѐk|⿕ CM)^Ec~uy_ѭo}cm&Rgl©^MaC4OPrb:b'@ zxaWZpRC?CI@65ZY쎕? e%؀ CC"Cu'5(Kߕ'Gpm@mG_Dmȩ)3XcM&Џi V^A`(|DάC->]Kl9m&ial$8o^|fW[a5'w#RR#˩!de9P0D: EfX+Vr̩410Z3(EQa([y=oV  Fye+AVl6@5 +2738 0 obj << +/Type /Page +/Contents 2739 0 R +/Resources 2737 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +>> endobj +2740 0 obj << +/D [2738 0 R /XYZ 85.039 781.388 null] +>> endobj +646 0 obj << +/D [2738 0 R /XYZ 85.039 704.845 null] +>> endobj +2741 0 obj << +/D [2738 0 R /XYZ 85.039 675.441 null] +>> endobj +2737 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F38 2158 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F65 2099 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2744 0 obj << +/Length 2702 +/Filter /FlateDecode +>> +stream +xYmo_8 +"%)2h :T[Z%6un|mɥD'W!@ݝgfj?5J"h(O'hpV0L ? +=?p8)Kt4'gDkOĽ{wQ3zhw>evzaqg?⏖pgdt4=P GjvPE;M%I^SEלUpb;O8up1f 9X3IwU>0D"9Ad]BQ3wA%9}CѬMTeSO ^0a*={Չ'Q:3sM0ˊ]K +cvJnKĔ +aYHRd#oܣr,/٢ᬄvrk\fitws`EA$]|'uc$ Z)Ho*;Ԭ=|I@rvuSjKΦ"^X0@kaV"4P$29-Cnݢ@/E؜MORSAПBr,JJB8P݂6L{JB?B0#sSC!LqAGױ1_@/[ܚΔt⬯c׭c)z@h[E,~lbI'zo5z,M#q':[.*9q(#%~^uG7ښ@_kp8"Ap0pEFAϬ3ҁf=Z>+^ڞ 2lWTN , )5ZH {ل U9L %>+{ebH\_*ԏM}_30`m-/(B/㯿(4|+3FY99<2}9OŒROXrN+ +%>iyIED8zP%iԝJ^?(*Ӯ}O FZ 1Xɯ&d0HŶ|!!p fFd""'ڂk0՜5%>6FeeVtUzKq1Ǧ:C9H׃'3Kſ*y9A/W8E'^w4,++!%؍hxZ_bqԻlmy&;t>>IXhp@^lݦːh$eO-vٖNY8@Xu3Ǒ?]֔k,0p$!qQYW۲an_3׆o|u~I9I\7ku +ciK}G<%_ZnzPd|7 U0YG׼g!x9:B{c3i[`SoOp]mY{^"}ߪ!e:j'4>aB`endstream +endobj +2743 0 obj << +/Type /Page +/Contents 2744 0 R +/Resources 2742 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2715 0 R +>> endobj +2745 0 obj << +/D [2743 0 R /XYZ 85.039 781.388 null] +>> endobj +2742 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F56 1642 0 R /F38 2158 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2748 0 obj << +/Length 2489 +/Filter /FlateDecode +>> +stream +xڵY[o~PR0)/fFuEhSBRV;9eq7i"@t.s̙F;398l/Ecyq<6lE;o.Ea|lb:tgm%v2{`W_޽0=3ZQ/?.㣬~~w f>-:Ƨ[la{WwkMC~w{h7%lOcrd +|OͫȞ?S3}7܈.Ѹ +p: h|M|d$3>cѠv+ 7~a:F1A'-02s,OOvGcxgsC"͎RyNHXA.'rR,bVk]xhIi ˘fb#i#R-GLCb'@N<0+Ӿȅ#De_wt 锗&DYJNx#:)?YNRD3K%yIf*uTH-mr^ft OF^)R82ՊCJB c,5Vxq}&Q̻W*oNpZcJÙ*Z|I|ͬ)X + +s ]{ȹ@d$`%s>WGxӅ@}3)OKٹsJ#-10 +(< Ce.R1B^ 0.EY`e0 rSX(x>BR z0xԸ%zzD3kT0IB G0ՋQhߗTrdL"){Rt ky,`р[)R-Vis[ NuF,H6wa&R۰i_sj8 `rfR# Q8UUNZ荫WINq~:N-%uxq̮Aַ%WTTՎgYʋ($2I"9'UU:T|f0lcw;ndZ,ZV $Z=_|$ jS}#JhZ6b RE}-DDy[N\^mɵV.ٰ&nry$!oh%\޼LWR_;V}6jmTlwϞs6AUR/}d؋aJ5 m?g P39|r)OLWRzk0QNq9Tu#8oӡ%-Tx'9.LJr(EfC(xWX2bkbULX@+'13)%mtТF-GߏZ~9k[#?A9c ?endstream +endobj +2747 0 obj << +/Type /Page +/Contents 2748 0 R +/Resources 2746 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2750 0 R +>> endobj +2749 0 obj << +/D [2747 0 R /XYZ 85.039 781.388 null] +>> endobj +2746 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2753 0 obj << +/Length 3836 +/Filter /FlateDecode +>> +stream +xZY~_1K>YG%Q#A|fS< ꪯ:&m$Ӎs-o\pnۉBl]ݺ:@,߬7o?-W[n`/WqXKzdX Ze[ooniWD>ͯ9{Xڏ73MMvR/ooG{nxP;IM7f_/C8n,_}rmw˕kOj SVT_N_=6u%VfȶrŌ(Mb s[X\0"lo +%TRR&]khI828ֿ-/sM[-͍VP71)pw[yU-KZzcrE:R$ꒂփCf~%v}V)\rumxSK߮>OL=e. +z1oeU}1. + +#,.¸U r)E/h'"}bʨcGСxQ:zՇ>XZ.LQp(Wdj|a/u|P[:$$P[8>}N){SֲJ=8UJ^+1= FG -]G3PGDx~@(@BBUFt۱Z1Xyx^-Ru?Z,}}u'\!MW +H4z"WFrHVY+e EEFMdJWYyq$^}5ͽxG 5dܿ.*\=60]AsEq~+ <;8, 2x1*/1-dqxh[j2 Z5;D%`_pU ?EFW;8yK&t0&. +ͧC !Ɇ0M]YMI}ڜ C.|1Z1CȧlNrb<b[>#~R(?LJ}j +@\1B!uc$FdJJrt^W'AQsrY#_ٝSAs@QAZ _۞ݳ2˛}"~D>/K$7q)Q$UJ7$B@̻7±rYb@KhPE}/2XL6.a;%v 2-; 'YwAE#)<=hԢ$sV}x J&R2 +CVp Ɵ$nv@#@:[7H-N% /\1,)uT23b 4,+W<<1Y7'{ */&lq*jQ^[9&FF'&3,u{L.k q+[ix0Ll8_(MVi[( m& +;+kE%,P|Dw>!^U~y&ڤ;!kX 1o!Pd61%أB1sPWiKZ`%SY&bǖQwadhؘO**[_()=A+n +/22j܀<"3\\پ/k+c^rrr~d^($Yc2H`O +q39ܡ3x)0BpލDtx f?}:yX7#'S?>~:dJ Mk: +Z\ʋ!ՍdR:n#Gˈ4#1Xh/]TnO~xa)D3`V3]}R6HuB ZgBl3l7q?f tQ(U8\[ sPj1=vp Y?f3;uw깎'Ok sXQ{xIhmN/d&/P1{b<%`]Nq8'/r2nMsh0pB6&~2kWӂFlJN4ɽbpo(|ט 5t鹭汮K?e$\BO9ݓDv$A':z|_#&vBɺL$ f[aA܏vv^]fmLo z&Ya>z||(C!Y׫YDٵoc&CL<}8a`Ϡ2$LɹaCBƟ99gk Ei +Ff//L DTb]@6\:!hk-6_3{qLJˤ=K,M%]*Ưz?khDž. U=S|Bx>(6ƘKt=/`#q$U}0=gE?}8ދ r0|M-7>Hِ׺:lv2-Y)|}Y?.^PJЫj!,arwٹSn4@ Oot s[B>Xx6,UvQJw +.;fm6978704s?Wf '['8 !2@dߋc6Vk5xN`]K]Wo,mgW(-Zi9}̈ʍm7E>؍srmGod+pLUsn K> endobj +2754 0 obj << +/D [2752 0 R /XYZ 85.039 781.388 null] +>> endobj +650 0 obj << +/D [2752 0 R /XYZ 85.039 609.395 null] +>> endobj +2755 0 obj << +/D [2752 0 R /XYZ 85.039 580.597 null] +>> endobj +2751 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F41 2104 0 R /F35 1632 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2758 0 obj << +/Length 2415 +/Filter /FlateDecode +>> +stream +xڥYoݿB]X +hk>+v +HВ#{~PM;)}..bb\t +DP~&xifO 8PUޛe_7o w +Cnfi ەU#?>~ +%UEuEhTe__\{wjX3ڭTQ8\@c4 +gL[fH|cxLh ͪlT-W{S]Fg~3ZhUX + oi=L fכ#[YH/q +γ7|2yʼ_yб!: U_(?T>[eN+W)x1pQnw AfN1N' 0}0m-лGo,d}~[67 Z.Ω>#'UeǺ9jynQgL ͭ"NdeOG6Z-|QVx^33qP_A˧=2(QB7U(X%;c$!4amρ/| ^L+A N6.k@YTJ^u{KkXcO%khB&+I6t"FpQ V׵{%#-@2 +s-,w,$-c-NC-NicMj #5ThȝeUK%ؘa׳*Hۊr"CpqôL>cJh5Ɛ+2޶Nzhɲz eW#EjҖѸ+.P8#@,0,϶W39u٘ זd[\WRg ]o) R*z͝,Hd=j(<`_ߒYaR)%9B šjHx~t[28ӼDcIZRxfD u?‰|6(mgB>9P̥w&HF#9ǔ 7fwGtZ!-6v5oOx!% I tD1X':®~g6Bt0djkDVHA9l1t_58#=FB5Ƞ𲺣z)vTKޕ2[ƞgW`gA:TW[bFsݽB/$*-4,^^[g<$kQ7.2SP0 c.ހ+%O7+\Rw""d6iQQR ,XqzQ"÷JP2FK3\-c(r5vh˳uC%\GK<<GnjតM!iQ܎ +C)JX(urESne \N t*hGtMYPaF@eˈk۳%p\ ȣ +w2h48pqP 2[ 9Db!Q_E49Rf"$~Rvr([= +2D\;_Ǯl ζJoK ڹG)=S5Xhد?"qw2?OZO}OT|7k/+,]M%bfV9| eTP>Vgbx,\U?wendstream +endobj +2757 0 obj << +/Type /Page +/Contents 2758 0 R +/Resources 2756 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2750 0 R +>> endobj +2759 0 obj << +/D [2757 0 R /XYZ 85.039 781.388 null] +>> endobj +654 0 obj << +/D [2757 0 R /XYZ 85.039 718.394 null] +>> endobj +2760 0 obj << +/D [2757 0 R /XYZ 85.039 688.193 null] +>> endobj +658 0 obj << +/D [2757 0 R /XYZ 85.039 442.883 null] +>> endobj +2761 0 obj << +/D [2757 0 R /XYZ 85.039 413.479 null] +>> endobj +2756 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2764 0 obj << +/Length 2971 +/Filter /FlateDecode +>> +stream +xZrJ}W2ʴin8f[cs3KX(~=:sRe5M_^{MܑQ NjGa +/F3ZAő{8#%Ǧ<#e|i:?۞Yc; #tZ3]̯n.IAkOny|ټ3 +-|2|k:rY74Ң6Уeǘ;^")+u_3&[]<>aаKA.Rj3_gc ՟ CEp?;ISyv5wyVfi PSkڪd{EQkO&EAlirE.9cդϑ&^lR:"ܲ~UzTJ酗S1wkCӋq2im(Og8l I "zym]MꧤJ' &vEpąS c}.7x4{x}92WAeN\s]RNJ ܍%љ>t(( dٍ`f>DhHjX8pSNS,ߣ|:=]l:Son/o7<>*e<g2ڀ1tWз~Z(k 4Pǔ! f_Jh/&Dv=ϐAw w f`؎&R,Ԭ+ +[&iu`nۗ!1LҪ0gpv)ܝ:"I`%w,=:)4]]B2&9tu=ΩMä۪[SxI#73kD=F`+sKǚ| \'ŊJ#VI7{MZ)q$aR2jgQ:m&\sĀo9n`Fc _G9CboZ閻wi "Xf 1D`m4>N&ny s IBɦCrWz+Rs@KǕija1,/z2rLra[ʞp!DȎ!AoQH0i"[oJ -.c#l6dTn 8U,Wѵy!2&/c[1!B;tɰ8\} 뙑ڨb#i}/5Zj"l&n:ZȕB”]t鬞>#TjЙ5[Y-$IڝXg杼AѢ&!lWQ L.ۯERz}LAdBbz#s ]xj㏮6"4/F6>)YEN8')ɋFw^ d!b .@UqԺpZ3e"7 +9Ja +eʽĞ*ķGX9th ;Ze֛XHP9W`´nRbڙ CkmPNOi5I/ Mp\E~HnKnZ)@n ݪ6L`Izg]w@e܂t\9|\\ Il(樒n@ʇxBq(> endobj +2767 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 394.756 387.717 407.658] +/Subtype/Link/A<> +>> endobj +2768 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [157.067 304.494 429.341 317.396] +/Subtype/Link/A<> +>> endobj +2769 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 254.88 347.128 267.782] +/Subtype/Link/A<> +>> endobj +2770 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 218.816 508.187 231.717] +/Subtype/Link/A<> +>> endobj +2771 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 155.652 336.156 168.554] +/Subtype/Link/A<> +>> endobj +2772 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 119.588 400.551 132.489] +/Subtype/Link/A<> +>> endobj +2765 0 obj << +/D [2763 0 R /XYZ 85.039 781.388 null] +>> endobj +662 0 obj << +/D [2763 0 R /XYZ 85.039 491.246 null] +>> endobj +2766 0 obj << +/D [2763 0 R /XYZ 85.039 461.045 null] +>> endobj +2762 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2775 0 obj << +/Length 2593 +/Filter /FlateDecode +>> +stream +xY[oF~]*wR]Iǁkp`DɒUw|ύeNž,Ds9sn0? puÞ #c#S(㏞50 }bL;"G7O'pd۶f:p~1ڌW39hj)n_][o矏N#Gw<~tsk "Pۓ``s丶:ӣ/-s|Ǻcy6 pZ3M?@e<)`LK*%NDy 98BpM#qBL,-Pȶ} +)1Yz]%B(3kC(V*۶H +FPkNKՓLlIm.fڔʘ :WKN\VFx:nپCMM, fUFsЕЧt]'Rܯ:9@H[xGI8= (ׅkdʦzx,y3ըǦ +`ȱ}^B2oh0v)60]%X`W10x=w7E.ݴvk]QtkCHG-!OAA;mB M,QtN3hi !*QTmP|} jmUV=9M9υx0SX*O5騆WT tǷ(achQyMq.MI/\$iI^4WQ(֖*EA*LeeˏSB2*}8)`O4ʦ>Zցg  pe}o4{>KڿH +}|Yn[Ϋ#-4_eVMt.# ̋g2qm/$;$o(G|'d tH+_7¦OF:_z0K/:b)'}W\@E-DV2Bť S`_Iq%nH9D$DLVRײgM?pj%&WnJH^'R~$"JH|G" +$ >dc] &5Tj>hA2F$F qhIβh Iy^oujq=E[chسi;?ŗǨ?%Kb(ss%bӯ['AkX)vayFпte}hx[[Wcf dqɇwә8 18 CdbڧmKv|+2 E¦o!(M+anmw]6 S:n|yUj:/ɃFG_#_2')CQIfmty:W7,C{{٥$إ +%Zcy\7|n{$\ο'ջϧ_/O~>|v~%Qm&[ehyAX] +R,̞@ =qt/ن,_7F\@Z'oztu"M}Y: (:wgcD5 j$|X endstream +endobj +2774 0 obj << +/Type /Page +/Contents 2775 0 R +/Resources 2773 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2750 0 R +>> endobj +2776 0 obj << +/D [2774 0 R /XYZ 85.039 781.388 null] +>> endobj +666 0 obj << +/D [2774 0 R /XYZ 85.039 543.429 null] +>> endobj +2777 0 obj << +/D [2774 0 R /XYZ 85.039 522.232 null] +>> endobj +2773 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2780 0 obj << +/Length 1210 +/Filter /FlateDecode +>> +stream +xڵXmo8ί;[BwhHԭ4]T\8@x ]*byf3 R 1#@8W\P2-^+5 +b?'[}EnjuBHQP:^ 5T$?vϨ /5Nv:Xj7b 2 ůPt>X2.r*tub  &Ѷ#gEw[huwA* Oj(hyI{:BjTx<l`ڏ}aM~4/nۏWncuziz,W/,f8ƑR])\9wUFToTb?n$2 +a+@p D.n mJ01&yIL lQksYPDU ⩤+¤uBؠpFP*Jd`Jv fZ9iq$cVt,VP|ۚ5;5xY* +ݍPL[>qvׄFUQKMC@:kL s(v.Ӧ(Tyh'B˂J1]HʡY,\ d{+>ގNfQ&ѕԴm>Hz ntD ɟrT}w]a%*$'צ:MaJ]ǢGtƟ}"qf&Y~nB>7!7Q1)?-endstream +endobj +2779 0 obj << +/Type /Page +/Contents 2780 0 R +/Resources 2778 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2750 0 R +>> endobj +2781 0 obj << +/D [2779 0 R /XYZ 85.039 781.388 null] +>> endobj +2778 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2784 0 obj << +/Length 2269 +/Filter /FlateDecode +>> +stream +xYoBuZBtS:i +AAS+5EH*7C&M`;;;؄8p Sc? d72wnd) +sOͥg-pm$Zf?ODBhcLtVY&1*C5,eR}>XE0EgELL*Mb AaØ})G7&k;hҼ,ky{ ]8r4|8gIv&$׸>s-]b@ HMC2E$WPaal +52PRXem0G3SXRLv]bD;M`C{1@-Yx.=W?>*eR5fT}<95پ-Tt,ݖuP%dgEsZ1=Eag~$taYu֜ld V -c٬ȩsjx g $9?#'Z]SM8X͆@ ju<~Tj[288UCz}?l>j*r 8U+I]%L)t]5ٻIr9OCJʶTݼתuZ}U=%P̗;yR S|0nlp[\6mGo Gd;p]3lCz":|INw헫IU .ό]T }ukp*@(]JLj jgq[7S} $7W?f:YT0Jf}}ۦ ;2ΨMNov6]Σ"enXI_.W͇i.sP{YVRHCà9/:c*}[<&r[to-}Zp^@ϋw:ډ4x_ux;j`*R=u.W4_/,Wj ~{^#TPO8"~ozj-S< 9('Yendstream +endobj +2783 0 obj << +/Type /Page +/Contents 2784 0 R +/Resources 2782 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2787 0 R +>> endobj +2785 0 obj << +/D [2783 0 R /XYZ 85.039 781.388 null] +>> endobj +670 0 obj << +/D [2783 0 R /XYZ 85.039 421.906 null] +>> endobj +2786 0 obj << +/D [2783 0 R /XYZ 85.039 395.291 null] +>> endobj +2782 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2790 0 obj << +/Length 823 +/Filter /FlateDecode +>> +stream +xڽVKo@+{R<#:8!Jlj/i&< +$.삉7ucK찏o+btYy@U)Hx };ax9]s1A_4]}$8t֞Zc_o2D­].O} n޽Lu(Y?{/+l #NV0Pdޗ}o5:eIF ˍX0K_T$E5d|2b#uSˮL)n>_)of$I"ɼ𳾈MAz9 LSA_VaPaSNg.Ji1"hd]f~^B +M4IZe> endobj +2791 0 obj << +/D [2789 0 R /XYZ 85.039 781.388 null] +>> endobj +2788 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2794 0 obj << +/Length 1130 +/Filter /FlateDecode +>> +stream +xڵW]s8}WxDl2ӝa)I7/>8ؖkǯd#tי uuѽGGt4׆Au0mڂܶ5 =[ 鷮nztTnYAq;/^u7OV,uxbx:f~?FVX`Ag[_Zġ}jښu}-mY mT5oU{c&gX40uVL>8xdWV@D}gm؝ݏ<\=L>B9s>=_b۟~Omp40rJҀakz'e|<@H2ʊUȨ\HH<À8<+vN(a3ُ3)/0f z&Gq,͊ڎL,J YRFle)NT !/SNz;0-$ҡwڀ~=%l,^$2Gg9K'U@RN̖q $:Ql \eC}Ö@I̓e޸D&j#eso4ߌ]`9|V+ZN1qh89^#zW.|2=ޮڄ0|YAŐ-M|},i{O7+F<¤)cǂ(qU*k+jlX.f$jtGa\tR<ӫZnD U Dԛ 1f#A#Z˽.yŐ*T9 Di~ukd_B|%AB +nFTҠ*_u؃t)]wAVU<9lj3vX?-vsQnl*jʝ]61ɫ>$mzgUHbO%cz"b•h%Nrdivڧj1kU4(5"ܲir $~Vx$Ky V˞]:h)~*KZXj-6wN=lWOþ?{*<7t75KUbij=kFIeA9?l_-7tyf ߘL 8 d4*׿v{3fu5Cfy(A~/endstream +endobj +2793 0 obj << +/Type /Page +/Contents 2794 0 R +/Resources 2792 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2787 0 R +>> endobj +2795 0 obj << +/D [2793 0 R /XYZ 85.039 781.388 null] +>> endobj +2792 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2798 0 obj << +/Length 694 +/Filter /FlateDecode +>> +stream +xڽVMs0+R$L. ĦF%1fb +W $gbM +dĐ<[IHsϥH iʤӁA Y2{*^s=@Q{0LžzXSo;,,?ʝWGI{`גZ j:)!? 9Ю%e[>G[4J He/%_D>Moud4U'AԚ4 H )R~h o훴}vJ,^"Z81[(ߺy7ghx|ccPL?&oz' [Y% 0w~;O8˳YŽy&i'|>P~qZiƳдC(^Fx)%+j"&f>b\ia-}Ì' ~v0r []*p&slwڇ/ݛ9\+vbsMt]P+fq Jx46EsmǸ Y|;R9}q4~ +-",T[yw:U,hqbfim^iNƛeQ!>(_l?y-?Ʒݶ&!20TUuwtUϵVĀlP}0:$:oQQrIendstream +endobj +2797 0 obj << +/Type /Page +/Contents 2798 0 R +/Resources 2796 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2787 0 R +>> endobj +2799 0 obj << +/D [2797 0 R /XYZ 85.039 781.388 null] +>> endobj +2796 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2802 0 obj << +/Length 874 +/Filter /FlateDecode +>> +stream +xڵVs8~`|ggr3>'tZ^&1l(t8.6vz'IZ}i%Q11aj;3QB{\+Tj2Hy;tWZhU ț cL vї`@P3k>2`j_.ӢE;"~W~#}Pf>A`J1LMq!3T;dm0غ7xjmrw72*m)ʺ[<,[v`kS7a|GȟN0 +G3?Np:cޗ9n!ww{>yu!UB{( T Q'%"nH*+O I1ijDR> endobj +2803 0 obj << +/D [2801 0 R /XYZ 85.039 781.388 null] +>> endobj +2800 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2806 0 obj << +/Length 977 +/Filter /FlateDecode +>> +stream +xڵW[s6~W0CMPwΤ^o֦e.d2?~68@6gtsSEh@VmѴ P-K w,ӕЫ}꽡PlG׮X$UUP34֝fݵMI8uzfS(,YIVv +>bD}dږH2-MW;<ᯃL)PL:Pe`YځlN-_wV+w|vWaS3i-t/UE85`QҳA}.F}co⌔$,p^K%{?f@%i:-ˏiy| =4`FQ00H89i%wys ݮNQM4'4.m%$lD2 0(i*_=($F}rc-֛੓Mm:!hѳi[7JtRjnQ8~!Mo:L`x/.;|k4l{ +znq.2 g<B뱻> endobj +2807 0 obj << +/D [2805 0 R /XYZ 85.039 781.388 null] +>> endobj +2804 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2810 0 obj << +/Length 873 +/Filter /FlateDecode +>> +stream +xڵWn0}WDݗ];sԕX(U YHyPaZ_'vu$ḏ=`&XabHLSL$$5t.tA Y;D\QTT!D0ڃSJ:fmHcXypvbŭ!cn%eKG[<4J Ոki2;:T !v71A_z~P*0NA̒|yN8ᐿq c>,tǐ4.i0p%Peڮ})p`*$0DK"8( 8OFW!Σ0Sp#DC߄忻e:qf ȣdŨ30IbNFE[jn͂jݛܙjUmdFRL/U C"?(졂  g,$]FwEc;۾ݛVԛwvݹ)r=zk.WF$ꧧ8wZm[Nvk~=y??!׺)ARww4fk ѶzwMTKsscfP1B{Jdv 6ű^3_۽f;bcàǨ/4fu€03T96*P] :Z:G^|q®~qYp`\*X{!qSW"$- +kҏf~E爞01> endobj +2811 0 obj << +/D [2809 0 R /XYZ 85.039 781.388 null] +>> endobj +2808 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2815 0 obj << +/Length 2725 +/Filter /FlateDecode +>> +stream +xڵYoBP?JK.|hԳHh1)2ʊ)J M}i9Ł(]KhQ9>s8>FcMh~O$凷՗2\ߚQ&qˣ/77àk|;_&2ϮcMCrh }SDbz?p+Դk1H}`l ̊ǶYsNu̱p('aƘ2}J6:A#Z&RNlOn2];[B0t \%adN"ڻw5E`9{p Ox?QЫr 2h qX= g)/x~_FÚh0gNޔZfkDX&:C33iɜ6EmP5hԨS2(h L'8] =BxC< g{FswӆtɤIF46Ih4ⴹ/BLwuuaʳ5$HѦNZg^Y GmE9kSTDPdq:u=R]N漊ۋ]\6]q-0 ]qNHܥF"S)!ƒ!PfDRI2Ojw15*wSMtp2 i:B 3=Ǐ\guVrJqWq)uJHy웁W{ 'tRnu: A zekЫz53EeH&M 9 ^h+'8D&yb|>(ݎw6$~%W a:o@NJRRtI+h7k]WQ&]=f0/b@E"{4;q/@>j IJ "U]tG_+1A]=o@t;.i[z)Ӥn}5x_.qaJ/Sb70D? +B-\4^v2Yȕ%KzVdĨzS=SivvGJjU$V=$w$X7#0# ]Q,Dq4i,3):ܭg0zG8@.@v.x=FB9:#kv~UB(ck,m5ƒwƾ":[AiRаyOrAQa_kw/«Ej}brŲ+yfo̊XcXTBR1q|K|VAu*H`}V$~;s D9 +bI<%rc  yܗ'@A+_\9yF齨 .endstream +endobj +2814 0 obj << +/Type /Page +/Contents 2815 0 R +/Resources 2813 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2812 0 R +/Annots [ 2819 0 R 2820 0 R 2821 0 R ] +>> endobj +2819 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 376.733 381.942 388.726] +/Subtype/Link/A<> +>> endobj +2820 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 322.537 456.396 334.529] +/Subtype/Link/A<> +>> endobj +2821 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 281.889 450.669 293.882] +/Subtype/Link/A<> +>> endobj +2816 0 obj << +/D [2814 0 R /XYZ 85.039 781.388 null] +>> endobj +674 0 obj << +/D [2814 0 R /XYZ 85.039 585.023 null] +>> endobj +2817 0 obj << +/D [2814 0 R /XYZ 85.039 556.288 null] +>> endobj +678 0 obj << +/D [2814 0 R /XYZ 85.039 439.067 null] +>> endobj +2818 0 obj << +/D [2814 0 R /XYZ 85.039 418.477 null] +>> endobj +2813 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2824 0 obj << +/Length 2935 +/Filter /FlateDecode +>> +stream +xrF]_C +MrUj+k;Z%W䇭$ A@گ߾f8*aȁ?w'(vm?G3Z+HNf߇uIF+_bwoO['(Wn'uǣo߼ƞAp|?}~Wo{NBߜPʱ$nW*@/~6 lhʐdV:Qh](n2nG +ԋjbz{4khUW[n @oZkׄB`=p6#`-e +y; +9SY=͎#A{YqUݖE G[si0$iq`Ľ7)6kZn? IYUɀDsD +qCء1z-sKߴlv8"/p'y A71YSط:@0@.LH"`mPJePƢe ĕŪӕ45G +G,,2hQa.ۭl+ʶ@إD堕Q-DuB;h%z; vs Z:iqcȹ S.z=_lv+cF  Bc뙋"հ+ ,"_AXoyshy<gj,i=qGn+0ICf3 o>k2kӼh/D(x)=}="M?f-Nx[T}|<Ѐ4|" ߡ(T834&  +A֔cM-~I +yb@Gqv:ډ;^xbm l A/ +\G}c_m~{vυ_dA`q? +8A +2Гy%1sfaX]~S%g'TK nVz߬>!|9}&%ޢSx-Yo@uzX04~`DhliV4#s1p<ʍz!vK3O Y[I7V쿭q% 8C숀DC!fnΦ5uL.o~q4ڪb :v"l'W̴Ӕc)W)>T=$s8X2 -r`ntt d|(>E0=z?2NvPb<}ڎJg{m³[D;z]F)?=8n=5ܘTϷ~L]r@y:O(0 )]VN̒6Q}&EV +4:j㋲"D9T$|ܗڑ|3us@ KQyسL =o#ESȜ/~u!KJ-V6+)v,85gAvt+ZUklSyI;Kc'?%Uv +\u`j&h˒?TC_"FDR1T"7KJp%6YpvxWд\=d5wOopg؇kչT5ΊVzMny"oJƽ ^}ㄗ}kT 6ƿK*S2DžiYiEXZ/~WxqV!˕ئ=.Q,<d0_v,_-NXUM97'Zbvf^"_U*^H)zZϸ9%4ʣ^ˋnn i1uZ +yZE_y%p~?f(zdym*#{ X&7 Bt#&iՇ;n2H99X*gr۾@ƅwe1/SLS{E>P?W}uKz_#mҐVzk5@r eA'Ќ(7L<;pÿ {Q7&3ڷktzO$%Mi!3E^6#o}>6AQkN5.8b۔^ρ!-䰪WluB m/V;7&~6Yν2~C;XCA'>?xN4{I4ݦ/y. `p2;fo#.ܹ83lWھ/'ƝѾpxSknڞi ++Ml彖_w;yy&b֋ܽ\@G__m1=~-N`xH,m r#yp51DA8#e؋e +Hkoʣ`@L2I$+X;!u;-kV~Y+Y@)g"=]gQ ,+E4 fҥ~r= "Dl:}hendstream +endobj +2823 0 obj << +/Type /Page +/Contents 2824 0 R +/Resources 2822 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2812 0 R +/Annots [ 2826 0 R 2827 0 R 2828 0 R 2829 0 R 2830 0 R ] +>> endobj +2826 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 706.436 347.579 718.428] +/Subtype/Link/A<> +>> endobj +2827 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 570.944 512.306 582.936] +/Subtype/Link/A<> +>> endobj +2828 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 559.819 279.398 568.478] +/Subtype/Link/A<> +>> endobj +2829 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 346.095 365.259 358.087] +/Subtype/Link/A<> +>> endobj +2830 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [122.225 318.996 496.486 330.989] +/Subtype/Link/A<> +>> endobj +2825 0 obj << +/D [2823 0 R /XYZ 85.039 781.388 null] +>> endobj +2822 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2833 0 obj << +/Length 3056 +/Filter /FlateDecode +>> +stream +xZoH~_a^-E&i6{M>(b%Wo?~$JpEq(pf8Y}r'plxܛޒFΏl5yz}}4z8=2'֤w}S'O> ga86Nnۘ u=q3k\캵3ž_-Hߎ,ӝ{ԶL{2魏<5}Uhv"c^OVunf֧tS.w|cU.^_;W.Ngo +!8֝wٙꖧg89{|&n'.}hC o>,/> Fx;O4R~x/t0jx[ŇmeHi^& 6jރD)wۊoNϸWMKP1طгLkB]bؼĴCë,#-=}OWg;iN!jk*'&F!}٦M&,i ;I^#A L7ku*bw7UTI!V:!ɧ3DuzrF`WD$?%Z`茍|Uɼ/pdֆnӁqvqcݔDPh2G28[, F^NJGoG_h$c%|"B)^}T\geyc#;Mp"N .@*opJTbVH16Z,_ZBαiKe[m\l6}&Eo._ HG,F4UP8ƴH`jZB`w|1HL!90gpR>`.W0| FD՗L1ھ/b9V-b|[,sqbr[!Cʈ<7H ve"-[j3\8`&Yq?:+f[}w}tr)FmY^$ 0B! /:gF}X3 Sy˪kwJ6U_pT|W([B~C2gVmK-z>bƏ28ۿ@˰>zciQ:c6h3>B݊.z.(I}f `*Ћ;YԪ6/ForTw)M8gcoWjH" ^CZtoȀ .Tj‚eD[޷Dw|YiiG AX2c (jO)cc0%L,yҔs3>yŨ{Oyp[*Z}8jRK@J9~hlO} 8E\//lq +iZLol[ݤE~$@{uӁPRat +M˗VηQ:+ޖ(!IV ) gzVGT åZu +Z +&҂枉%*ֶ fBWIB-Iو$ )Uvy^DDmC.VM6H[Y'vA)i!=Satm)| + = 'Q&4ZT_* E^es~(=ԈINC ]O9qe5*V'@-'5Zd׏xՀ룣< B&BV"%GT`xk5Fj0eϽ |`fe\'~왶9L/dkqw-4v̷ړo۸[*R/˒L̶u(#mgaRx밸n:rI=a(:qPq!`!Q" %KH:Ķ}t]G= +>K:.8(| OՋ3"Iӡ2RnfS*V@W+qJ1רoPFȋdZW!W;8S fz? <^gـ h[ÊS 5IL+^l)Vq\E +eťg2QX˦v=AGeNn:QEiTLa%3\F] F d- `K<~ puAtyxUݴCCRI}M٪jwVYdNy-Z泦T koK-K]r_g:o@F%xOU\>t!u1UN'\֛ &SghҬn،k-w`+6o>HBfT +C<+hq'*yjڕvJ[ ZUo P@fkTWs6NRZDY6З^zd` nE ͯd>e74b۶/*v-endstream +endobj +2832 0 obj << +/Type /Page +/Contents 2833 0 R +/Resources 2831 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2812 0 R +/Annots [ 2835 0 R 2836 0 R ] +>> endobj +2835 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [351.165 473.426 512.306 485.419] +/Subtype/Link/A<> +>> endobj +2836 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 459.574 136.217 472.476] +/Subtype/Link/A<> +>> endobj +2834 0 obj << +/D [2832 0 R /XYZ 85.039 781.388 null] +>> endobj +682 0 obj << +/D [2832 0 R /XYZ 85.039 171.068 null] +>> endobj +2837 0 obj << +/D [2832 0 R /XYZ 85.039 142.27 null] +>> endobj +2831 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F65 2099 0 R /F20 1617 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2840 0 obj << +/Length 2772 +/Filter /FlateDecode +>> +stream +xYݏBK)âH.? !J'#-<1%$"{kr +7ݙ̬ܙ,lG%(vmdzʙʕ̷0@ֳU\Nd!'_^|X*,׷(uw߮_{>]5x^~sr=Xv~pOW?2P͕c$nvW~Wүnf0ϟ-}7i;}M7z[9{/9`GU<Իake<~ z։M ت;U~BK;^%eڡ~DZ2v/E)?ڶ( +GZ%UgKEs%W[lr_pot0mOGR8iZRCú?UӺ!v 偿,dҢĩK}$7e= ?vAU+L*v3ibK/mC\L#8St)x({d_ѢysϤ썃Б7G +*,P5 +,92{&;d)p>8sږ vjosQ좛f-7Z۲ԥNSGgzD^ pXSA͡G\&'~}2r<9N0(,~7ȠC&vWݣȆQۜǁhJ4qY@(4Ц L69hwqZKq P?FA>G/x] OH|J'9?z' E+2?,pi;`k= H"9x 8nq?{ojIiܡ{&Dҵa +me2m3&;0MD4jkY$7AVz7cBڐh\ )&!0$Q {-M`*MU;G)GIZݤ;{vc9a{ O)BÉahyҖGϛT15лJ[ +|b:ubuz@1XE0t%Ԝܙ\:~5a[ HGSιKiܧ(OgP`tT h6|[9$XpM9 _MS P' 2!GqcIGt#d!{hLTrT<_ u c\x5N C9w ^#zHB 9ObJ>I*$e9 9laҵtm ]k4u&%r< `?u䌦GglQ8&ˈ#5.a^LJjǒēl_%B8@ +0Hu&N|**R먂dR_`#9ԵqYID<W|R1#- `bybg#9>u<ԘsHE1 }1o &]VH2)47L+]@IKZ}Z\1 `GQ|X*$̇m(*ᐓ9XiŊ%SW`%%!K"UPco@:Z;QR>1 ?b<ɜ@GxɴQ83*YRs~:=׎/?~q35up4ΐvRED7_{"ۋ|=گEő\)Fm4# +ऄB(nwbJ& @GGtg6* (584nHNM$SG@vW;/q/y=v( +T7N lֳ6D'ف/{? +oLo=ؚC^'->{IƯ ]}hU֎`4]^8ߡ1$XMʮer?/k?h:vFVrX^meYvΖXV5]Z)]% ҡ4Mp[Q/쾘@b@=Bm9@t2ܡ.ZDoo`;1nQ#(8MnOUsV24VԾd7'Jacp}'?"oMZp5$hޢ@/[˝(9˃SY^wL {P"ve]ވ몳˸?2\endstream +endobj +2839 0 obj << +/Type /Page +/Contents 2840 0 R +/Resources 2838 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2812 0 R +>> endobj +2841 0 obj << +/D [2839 0 R /XYZ 85.039 781.388 null] +>> endobj +2838 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2844 0 obj << +/Length 2785 +/Filter /FlateDecode +>> +stream +xZ[F~_rXݺ U!,n4cKFq=elC݁-Q#(\%(֮ǣLL  +\z<;;)4#D%قHfo'??z1dy}w2yD;xOqäv^__NbϙMΞ8;]?goު5L^WN<7=^݅uvS߄)7c4F{d-p %HY=36]Jm&&v&S? +aj"`΃ָIXp^;?`v^nUyq^pQFU-L5yY-hhC }wk?tC15RCQO_f+ıqlSxγg/vC& ᙆb,15n"!)$Ycf +*/ (4؆a%p86 +L'<öҼ'Ow#%Dy BHpvf4qf^(x bcu#7(0%q=AU4N,ސFK++5>{ 0&#Z.9 O}OVu=Ta6hUddf;+5P)˭+gdsL{vfz@VduNC@D*cծ ;Jny5RVDo佖G.v}0?^pkŒ +hsbwhZW#nvdÓqYóv# J'c2#J=lZ y>3p-MbrGwhe׺$ƜVw}yiʃrD⪈)`-qJ&P,%{M_;9OƍG. [~ЯSr@Je]ݪlF]!u򊤞7qvٕŋ +Yc~#DIƑΙs&۪֍%H)reV6-5 )uQ|/ZOgZH8zm͏٨qUmU-X"NHi1r45Yׯi+1'ʰd=~?;>ᷩLA6Vٕ en` B ӥ1STs,􄈃J=8d0$Zv{Gc}=*9r|Tp;*@s)1^NM E-)&~OR"lQݖ)z~-A4KRӂ9^}_$*\6FZ͆S!C.&n`¤iQ6-ί=YY}L@E| +!K P} T}[sq9iyT|;1&$E 8چ3 X]Yϴ|#,DgGʵYrVn7}OO$l0hq+H`2eɭ.hW%9aqm r̤;Qox*#n88TrҟZpCD˝08dHso7+ި,e^wNpLm@h%CjS\Sav7Hvиݱ$?Foԥ^żHS7#ɹ|&f[!g7z(5T+" 6Bn\*6:^ZߔSL`Y s"<@AB- G~qޭ'sX*lɯd_qCnw˶̈Kt谒DeBxP|Oa P-OWM8?DuhKUYnDCk:m:Ӽ$p0.0\o6-)<;77|#JUhʃ:&\ۀ%ˣ_?̠C;:17.OwfT< Ƒ\HD@wܺmMeʡA4]jQ'tADsɻ#c`XQK9>/E] If߉+9TÛL)`B\^3]m?O?}qgӆ;"Wendstream +endobj +2843 0 obj << +/Type /Page +/Contents 2844 0 R +/Resources 2842 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2812 0 R +/Annots [ 2846 0 R ] +>> endobj +2846 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [318.285 100.991 509.276 112.984] +/Subtype/Link/A<> +>> endobj +2845 0 obj << +/D [2843 0 R /XYZ 85.039 781.388 null] +>> endobj +2842 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2850 0 obj << +/Length 2574 +/Filter /FlateDecode +>> +stream +xYmo8_aT.֔(vkkz [J,T\ )˶]  "pH<3, YHd]x;hyw!Mo/ +Յ6gVeq^ͧR)@,q8^H熥ן>>ZBv?-_W\Y]"ŗ,~J=!tB%@zuqsA 35e C`MK$ epb~:ۭ3Qֺ˪j p,MQLY?[mNO'{oذ!mK\~ -lq>P)jz>,#'+r>w[t[3 5 wEt3)B-wm<࿬5% +MgK^KHk4[9_vA ή9Z34ǓA[)Xv++J-~iK\YcL)=s;Tf n`5&rvZ^xp" q{ݺz y[vWB D/|*Nq@4'S!(y"+_MD}+qhq]l)^KEP}Ra*4-:@)=4=\ݏ%3m1Hb,@wʆTD^fݩ woT&H^eƩT`DQz^x'w wԶk/zd&NKNPYplPfă69uãHđ벞0As/cߊWwUԇṈU(wCY !@W! am%l^DhS0Ƙ=#Q3sM7[c]0q="f]w\ͅ) k, BYj^Us7 o߱htǨ]qg9@mykClCVJ|f_3YzkZj=Нw@쇨0lC>s +H[4(DC%BLǥφBį4|~_]>~ + ~h @ cK4eRJ> HbbX##5:P@rho(tmz;. C}\65Fysp-*&NIƒmⰹ ݓ7entף03"3nb8(njn!tH'hkT"1,T7̑D_#x`AİHF)Yr6ħ۔ɐ!Ѭd+xa9l1 R syp"Ual<$V UsNj'MǠjwwࡆcn]T&S!F 2#~j ho$?ZN3q L 175Kg}WG|d!ۆ˩ +SoA)Kc[4 +cj7G-^n33k Ix=M.13HUR{ +֘Μ6 94Ȏ@! H(3@Ozh;D`6GSq$ȗ] +>=^y +cތkhAQ\RP2R*+67A>;flKKn-p$cM; BP B9#`b! 7ao%[vGjApBW|teЌG'%CjoAs;t Nnʥp|Y0yZ'}o0fO%t|ya#7qn?$rN[B w/N$Nz$qF4(T[{lsǰPp /|: $bњ,ڌ,6wz;7_uvquA_ƌT>Qڮy_sYaE + |K"{-! B;>!냟Am8L^;'IEpbl*i`Rt)[jz?~FPʹ:@ VH"d^D +i_;h+["ovE^ 8[S849f pG3=(Qԫ$qu4'-Ig܌vȶAឌ9'j+f:^&sp57eYܲJZ> endobj +2847 0 obj << +/Type /XObject +/Subtype /Form +/FormType 1 +/PTEX.FileName (./xslt/figures/caution.pdf) +/PTEX.PageNumber 1 +/Matrix [1 0 0 1 0 0] +/BBox [0 0 31 31] +/Resources << +/ProcSet [ /PDF ] +>> +/Length 557 +/Filter [/FlateDecode] +>> +stream +xmIn1 EOPwu$Ig0ľ6V5 oʯsO #h8:5?Ơ[IL~F PYdzZ8򑖌f(E#@xoL ۹[ + +6\>RgbWj[ +WϢ{6;F])/ԬMu;pk;̩dh> endobj +2848 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im4 2847 0 R /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2855 0 obj << +/Length 2865 +/Filter /FlateDecode +>> +stream +xZm6' 8oPˤDm7hnA +AkɶXm6ax8Cr*r$O~2bq5Q(/tdK>.p r = m%.y[<^6fu}=61O84ev.nwŗE RB3=YmO Ys<n |N1[3QFoqڗeV}K(P7Mq;"o[hKU~ WJX1a^ mԎ] xڢZ'dp)@=Zs=|*.ꪥĥghEyt0Tqbe!&jN8#A)F9 v|LҋK.5 }-+BkB'algiײ5H }l`YP"-vEX|W;;o98l;[Z$f@Eӛ?te-``MŒ405 粻DZ:oFQn(#r9֔'Ք2? =g&TAp}56hetQ˖$Js=Jm-J$SH!3I?q8L"3b;0%$T +uĉwT\h2F1ɂҺTO=VMx*r;1~2/b,i9٦hݞfڃ]Crf/TR2,fG<2&X٭+&-Iy\@H؃Y)g쮜'XbO?]v(Oq[(SM3Z_ΝoWZa>(ԆNS)>DQ N5z0 TC݌j܌/Cr<銑1adlWX.>+,QHKJ{Ɓl5 p+HGz˜c0ʭ}%~G?nqPҍp4IQ) %8/w|syi@! +@=H\B;'\ETQBe)endstream +endobj +2854 0 obj << +/Type /Page +/Contents 2855 0 R +/Resources 2853 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2852 0 R +>> endobj +2856 0 obj << +/D [2854 0 R /XYZ 85.039 781.388 null] +>> endobj +2853 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F38 2158 0 R /F15 1628 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2859 0 obj << +/Length 3166 +/Filter /FlateDecode +>> +stream +xڵr8PD"Sd3$oTjf4IKL(R!(ٯ~$%9l\6F4 3~Y؎Ekq,\떡7^߽~=@t|\ľuKeu]3`k._ų]f v|6TxLxW0;9Ls8RqIa׷ /0LJwi'bڎI8ld -)h: c+?ZlΙJTZnzgn䱋Yኊ/*O%.4hq7'NZ`vМ l< zՆ^ZYЌG0HZAw]QWjϷEi] +0u9# wqmwQy7I7{Ut:eU6JhvEcUШRӡu(;f;[0sP; QiKaJQA6Ȼ|Ðޗ"wp} El@ݐ {i٩,JDC.[dxكIDW +SrbL.w50mjVu$掇W[+*`@nbns[vmW9X{ (NijZ7M2I[*)拏!ڑo:(GZF{]ʱCS~^F0`oX$°iF5][ +'f8ف>Kt+܆^Lڎ NoLRZ`C E)G䕲CQWIyFm}G]m&TKK˖ +u}w} *Ro~3lɱ": ŧh䡢 0Grmt$f}vjP!A$7R'1^Kae ~ҝYZ0}xZֿ*kCt'N7JŮvpM-2 sF$+ y i'xK#+;#ψĸ8LFLxet`PSbx! Y-ą|וt]S`prLa"J1|CPZوgؠOk<y'"[ +{Gȳf`D蔙H6](ū.,O6C#̟]F;'jX ^SMNH +%j:a\kMB:e d(e"V8FZi!}A2n=NS|| 6e - f0035Pty +|[ p"˟sdqJAB"_>q0I=GGr=Lve&8`&_;vэ'$1%HcYlwMk:^4U< +T}2ꌖkcy7v;Eaf!6ꪯ@1@<[?P:f7-h^ BPxJUbj eV+itQw Y'p$PV/Y]Dti4%559{>tܧ߮MKXp~Nd"$2EFƔ܁0ąEzAT)b|%r]mcdwjPmQ`:|Nk<;Z=v"Н Wy'q fe .jO}_CHd U ?yޗbq1)QE6= RL'Sf@p@]Lt-JpևD3@ET|n 9mcp)Щ SMؽ]ﴧbrm3iG~xiϜoMpHjaӖa,@D{>{>M*gNj@!$JueΛV#2(ש(\TW~IܡR6R3DH=fI b5Sy + Ҕ/ +x@IqNrk|V@ +mr1VR"<{Qε1GFq)HI*8mH(_55q+W@'Rb3/P{j%Rld&(mbZ PpZsTzLVUЗWDg 1$ ;%z ׂgGpA:7l|GcgF9ȑc9V*~tma^)LߛJcTʾx)hܷgJ:L<ֽwl-w1Q +`*yVh)-񦶪}К9-PQċTD)@ôy${_OY(x ՞x  =w<^)A,6BKmbC@`;a4*f7mjٜH8o4KSZ؉cZ Q8lj@ϼ?lnʲ* f Li% jL^6#'0&cMl /z@:U3dLx˚%jy~] FYB91(OG]TMm_jjK[)CޘR^ZqIXIXYd1JSUcXmMHB)cU&Hp- i!sKDȀMV`t,kȍV;x< 8ՙ 瀶:Pu?^pUl4eG68eOvٕȯ1endstream +endobj +2858 0 obj << +/Type /Page +/Contents 2859 0 R +/Resources 2857 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2852 0 R +>> endobj +2860 0 obj << +/D [2858 0 R /XYZ 85.039 781.388 null] +>> endobj +686 0 obj << +/D [2858 0 R /XYZ 85.039 388.423 null] +>> endobj +2861 0 obj << +/D [2858 0 R /XYZ 85.039 359.625 null] +>> endobj +2857 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2864 0 obj << +/Length 3193 +/Filter /FlateDecode +>> +stream +xZY~_!(B͛zw;NG䌸!MJfKX]]V3,lKfQl/g̙=̏gJV83v^ޜ ݙrIf7&hWy2bBY@N -YO,(.D0$aJ[IÔv䒩ξˉѴo&fhrg`k6p% ,Dx´?S/R8N\w`'݂17п"1(CgTI4[LX=@=}7( :" B'^ng Dk^kl*Ns=F+l/bEDza*dkXo$İx8pV= GbGQRldÞ)7 GJpcGw)|c +] Z%(պXSkAd-/BF(k3='Or9Vir1ōnWԁXzОgm/cJ+V f5U[.<+]y #LOsdy*0\[{ &B$ND>63s*5u .-)%.nWdM- ,5 A6ta` ˶09%\huyC +q;nkh8ta1R{H8+Eiyj۶C|+q7Qn7SRuMuT`ε0F @`B6R\`YY0I)B+,]m.H˺u-ӱ!7FqlŶ]$ ʘbDvy&fpaη=? 0\-M@@<]9eOfΩG'Li2#` =Ao3ƅ;dqms 4Gs_0> ;q&G'V&E?%""ق]w< h]սR>h AK[hhBDcqL>q(FyT8Ɯ%;0Uw6@CJdž>仼Q#0r.ēIJ^n]BC qm*zEAI=G@2jsB(!R&(%`9՟V躿l쯄=I'.a_9H'B :p@(fi8Sï11BOثȇ$V;PtƋ[u9Ԃ=9ymKp_OKUT]>W'w, KvkJ4AJA7riݶO7m.9'%001>p<քY=dBx ϡzU6l*t9[JS~ץbp?&oݓRBKI,}ۉqǏWqK[ߛncLT Ǝ$jCM (fjþ锲E˹[;Y(hcsd]r\JGb"#0xN!;G @u*#tơΔ=$2EN_i"o E xƖ<N'ܱ[`ByhP19/ `g3Q N;|*_%LLhY3NZ" tpDL0GѽI'bl^^^S -j㢖: +{)|_pH:%dSO&w > +x0190:IJ1LxP22{@\"ij<q?Rz|T ͌wQ=} +i5B%XDhuʎQm{at~ ̒ 9b^y"9QH R AA~^'7,|i3Xm\9,Jn+Z$_)2jZ\*= ti Z])K_弌f7:` P  ci+ȕEUc";YnŰ\fp_0!{!y@j0!NU\AM +ms=)\:u܁R?JfS{t'o],bIF+-t! ]_0̈́,~f\GVc-X|;&( q|}Ǻ6؄um b%KJŹ;|n><+F/ǴF#48,|- ZXv eĸaGVT gp7DK~\v +7hu9*?@=d +!<;O#E6ˁrCF%3KU L{ endstream +endobj +2863 0 obj << +/Type /Page +/Contents 2864 0 R +/Resources 2862 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2852 0 R +>> endobj +2865 0 obj << +/D [2863 0 R /XYZ 85.039 781.388 null] +>> endobj +690 0 obj << +/D [2863 0 R /XYZ 85.039 469.263 null] +>> endobj +2866 0 obj << +/D [2863 0 R /XYZ 85.039 437.737 null] +>> endobj +2862 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2869 0 obj << +/Length 1879 +/Filter /FlateDecode +>> +stream +xڵXm6 _ad[ֵ֦ؗMlvvC\XQ$(|HY%F+ۋcc8ƒfMp vS'gOCP81fy|ǯ'/gyELzb~~ #|}/ggg'Om-C~y|^wl$f'& Rd7dՑY +ldypL9YU#g2ofnl]RJۙ_r,Xm񿀜f_lA{p߶>v*;V1u2uTr|nUj*2̄vU,@\ɰheTX'cLiQpMׅc-T:x/pTYcMj&dy7|)%,a9"7 +\lƺFc|p:nDž}`}CSo^nEU^ ߞL?ĽdJ +vXYU7GtEHqD]ط@ʭp #עknaVv,FN!`m2"tG<@Ңb)fT&qwL]f mina9Hp(\&*7쓷=ot +<.ga@TʠX"VfyštwrLui| :pY.WhQ6q1bwJ;I0g# !B0La:ibG[yE%aa]mxԗ-_kHSbr +m۾k1:5g!p^sn ҟ¡UTYt\B#iS^A'E?aqgC693lJv@U|Bgndԟ!pE`/Tm25i\,KpzTg-Y0 .m(v~3J /ĄG<%K"h?]OP:4Q7 }*tD"6JC_@x0k`C:rAFیq̓"tcrxEjdf3ưW"};0qݝDž͈+.TzedqEBNۓ-JaR9s(-;RKrd9ѨTx2A`!AxRkYLL`|[CIr@#J"%8V qRi +\@GR|2tr LPMr992ZwPBXEM1Zp,W'^x~h%jn*կZ.g殶]E|;zFX>8Ǵn}gѻrϤGr3?˒#~<9(ڦcgq6zE}!PmOg9މz|>Ag1rVjS7 +O i1L(\Z)?MJCxq!EDC*\}fE͞ﭓ Q;'# jb?eu1|Yg͘9EOO#TAMP=-Sγ7pu۹n J5»rr;UcNX)WT6UoRe٠endstream +endobj +2868 0 obj << +/Type /Page +/Contents 2869 0 R +/Resources 2867 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2852 0 R +>> endobj +2870 0 obj << +/D [2868 0 R /XYZ 85.039 781.388 null] +>> endobj +2867 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2873 0 obj << +/Length 2539 +/Filter /FlateDecode +>> +stream +xɎ>_F4Y57' 2 2m;$b($5mU,IT$@WUo>>d!B_gCٽ 7@D(nQR_a"?ϏoQ*D?< cizfz ~ ¨6[?O8N|B7y{zjjeC?ߨ̛X ˀ}S4g+ gD8p>y^mgdxBA$-ʞG*&5k썈C˜(AaITLϨ8/<;7=L7\E|]%p{w'p4xŚ91a[|ᄋЛh5A%@E;9;xfA@cMQL nN[:oG2f~X9# uGi&3FaU*vh2$ \`Qӝ"QBV-??eѶ[W1a>|[Nv#SK2}1 $,'A'H<EGlڔs3Ƈ>[ -3Enƭ'HRa8MHغ_'i/PtZQy< +&FYThJUCxԱMP#QhTBgg#-C>&{7_ +$fƛ_x{I>_=-,fMbX󸘗FpV-Hh _ZoxA'ߍ! 150fLUSH +DETE +L<$m3zb3{xi=z "M92c.qCZ/V@,rsg7MVu+{ 6'{\CJE5|m0R=,H7x=|] /Jbcѽĕc?pxhjI(7lWL*0}1f85 j):0~Lht,d+G K=I|q49/a$xx SɻE +ix(J㡆񅍚Eғ9cwo(C(9a0iq/i`cM>wK8*ӰPfT͖1A%qV9(YJ]6SQBT(uALE&r!Qn_X u9&=?3/=7R>HB9ӭSCL%TFʓъ"p,Fgޚvyf62R-a2`;&О^9쑺'r:C%$p\ &ؿ*##|+niź36Rڍr}fᔙ6=~dGFCP2|n_esJ&\L`F$EkX0t+>j/L9UR<M8. ?\|)VLC+ٞ-$YTm&[kQy( Vf`?wv2,lomBr'ݽMM\ 5Js kQ!sde|"]UMȃTn͋NV<0VXeFd- _'t. +W9Lz}oG~nΝ)Gd >9 jAI|_h`9I~/R~yl[ +4^^vJWX~BRal4n2'+ݬķBV~D\T)Ű33%'zY|۽#dْ_vaeL/3m7OlTwC!dPG*Pf#T Hhs +5X_'] +d*cv81^r#*B!jdT"^9h _dySXqX21-}`lQ3ѣe7%J>yhљ1(&_(xJo1B&y9> endobj +2874 0 obj << +/D [2872 0 R /XYZ 85.039 781.388 null] +>> endobj +694 0 obj << +/D [2872 0 R /XYZ 85.039 761.463 null] +>> endobj +2226 0 obj << +/D [2872 0 R /XYZ 85.039 642.137 null] +>> endobj +698 0 obj << +/D [2872 0 R /XYZ 85.039 642.137 null] +>> endobj +2875 0 obj << +/D [2872 0 R /XYZ 85.039 617.419 null] +>> endobj +702 0 obj << +/D [2872 0 R /XYZ 85.039 490.465 null] +>> endobj +2876 0 obj << +/D [2872 0 R /XYZ 85.039 463.851 null] +>> endobj +706 0 obj << +/D [2872 0 R /XYZ 85.039 132.463 null] +>> endobj +2877 0 obj << +/D [2872 0 R /XYZ 85.039 105.849 null] +>> endobj +2871 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2880 0 obj << +/Length 3544 +/Filter /FlateDecode +>> +stream +xڥZYsF~ׯP eIZ^K)*ÐHABA+_u K-9zaxп:O .gyy~X_K*T +Y?fuEP\?>1cww&80',~w{+Ӈ)y](>+|ou4J |_h0Ӥ4oh&\{b~F8_W\t_?.*~X$l֛i/Qg5M̏fT?+:G5&YM+۵7R[|co>F3!N4tzBtظ)V:lk ش4{j};nּ87vb'QFgzcHU=y]#&'+-/jS}jxѽTy7v#nD17Yؼb+~qW|)}fIR:~sZ|m9E>Kp!4 e1{*swio5(FxXZ 7qO_feE+Wߵ8cc'* + 8clV„G2j<9 +0~lȇDX%,.Л@$h 65$ P0QaɀM5\8? e ,ˣ݆qb I_*0қ4{Y\|hQxV(Ym[:F#;2Nw~X~xZ^|g͎Cbܡ.#xss'~ +E}pS*]oYkdq:B!FX*N('#7d <#qe5ts놥ŭ[.Rk玏kin7Kao(N|6bJlyuaɭ設ӝu\ ~k`FZGݝmcMg2ѼlιmH3 [FJp4: ,o\RE3Dd3]6G[VlWw{y~%"Ɏ)E6g$^VxDvK#2%.Ha ?`K̓N9rh9s0>uzzb!b+>zbq~mWaȍ}f䑲<;QC~6El +TȢOPќQ<:6[1`蝩iHiG0vFCeMR3ڝznyK+X +%G[BӳBv7q*ngĠGqwj̏.UdXP\RHz3H.m 9!'v,LyG9f( "sKfۀĦnƹJefӊ>2<- KP}֘ 1}SQ=Voe*pbd2c(d. 48o)`=;q\V#&5/7ȳ$nۅ\r*I|,t:׎ +P LsT]mXgU+J2'9Ef=Ј'I vO Y3eɚc۱̅UAхstэ*QIN\@q + ܄~fpG 혫1 , 7pW6F;ѓÑqu0-RH!YϢUYFMRuxZϼ!oZmP6j8O.0-Ȕ?RXDRqDu&j$r~qf1AQ$0.l{EyxDԆ O(#v^'Ȫ2*)/M]ʘu(Fwgijb:\]̱NF9T _A{ƱM)Iqrh19jĔ'sFF #/l@_06Q i :!* ʿQh&G3b\aN}wa}$JRաpJDOu0G*S T]{_>3UWo=lo*7#A`{<)W#:<͊h-΄ {"MC[-JyodIBwʮj@hQ|v;(}#ᴮz ޠ$:>hܯQbm2ŋLh+Ϡ5z0JLH;_3}~M#t%0~'ow'L IQ߮=J/I;||1T%r4),u|9Ny΂{%e~'L~0w }՟ xaYr*Yendstream +endobj +2879 0 obj << +/Type /Page +/Contents 2880 0 R +/Resources 2878 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2885 0 R +>> endobj +2881 0 obj << +/D [2879 0 R /XYZ 85.039 781.388 null] +>> endobj +710 0 obj << +/D [2879 0 R /XYZ 85.039 461.534 null] +>> endobj +2882 0 obj << +/D [2879 0 R /XYZ 85.039 440.943 null] +>> endobj +714 0 obj << +/D [2879 0 R /XYZ 85.039 302.771 null] +>> endobj +2883 0 obj << +/D [2879 0 R /XYZ 85.039 276.156 null] +>> endobj +718 0 obj << +/D [2879 0 R /XYZ 85.039 204.579 null] +>> endobj +2884 0 obj << +/D [2879 0 R /XYZ 85.039 185.707 null] +>> endobj +2878 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2888 0 obj << +/Length 3665 +/Filter /FlateDecode +>> +stream +xڵkoF/r7Izk\"z)%*$o^$%ڽ- e2@i|eEp.OTs?\~* |XњWtZ{*iy?ݾ}{7<>sp?޽pf'Yp; ~V|o~ៀBi?rB|p +_.~-,|gGhE#4- EkZ(L0,ܣ-W "RPO8[@|v0X4Hcci{;Yʀ^ G qxp{:8FࡏXR2gtA:j-x0.kЕ垽;aogO`Mu2?B)? ǽ攟{  qxR˶0Ie_}-F͕ Z2ѐmϡ:_8vO\"BjS+ P aUz鸱6ծ,8 .G=ɼ3l K:A-c- a %ߑD@ +6 <"޷w,_LcCkQ~mlݽB,r5,/1;Xjлx y_*$Ck=s QfA#Zཀtr`Qn %u@>B Ȍ{2Bn [TuPg/f.g..b"FpЍ8oJ^W;" + gê3̽e]N͡F"-BtE`A|E*J{erhlX]m]?J#Iݑ "M /VAYAQ9 +.(c8zԢH/ܓ+GJXs/a~/<(@k@;x٧֗[{8O۞z}L! K^HB FռQ3 +W7F9-e?eguJmZß{^Z5ӉYpvpw-?_ڇ WyƆO5a1Ā8y'8x-JGمXBRBpMEe!>ke,naͬ +§@0=JG  J#.7~;IiB:({6]`$3^7{tG 䛙W%ObASlC]yײ$ |t% +0ʁNLlBkJqs[ 3qU\츩8Fω3RElGA57$$J;eުѫQٴEk(g-yҴ8 G'{Y uB"5Pjg['%g's!h|, }3p>Ϊ+ȇRBl-) Xu~A On]V2ٲ_*ZS,ZafUkO4gϲiZqENf-2r;z. PfQ@CAP8PEO܏pњh5R*!)sZ HJc?wJoX1`_\?2+{*8l@ DE"J}APZ HJ&NvѭDaA_%yw:OI܋WM.m]j;hSSl +TӅs4_L(GG:E :Jlr| Ҏ'yBᡉ+-dnrl4Ap1{p@2ԉd8 +j*1/8bIKi*tSߍGFP&9Fl}6dӻ4E( ŕe![*`H.lu#_36@)PW1i +%$(UwͫD՜B?C@:ES 2ŕMygQ<$ߜxRnIŌ\E.JH)ukAۆ6&J H$!(胪*ҚiKٔDbq\?bPRS8>qgU))E)N1xQGYWU"p}86Tށ_"k،4RB + $a`}!IM|Ww)C5Pxr\&K02JS߅wyP~6cTױQd #VkX.';f́L1lm6 _TWVIuU`O5 a[u ͳ"G9;> +`OUCmZNrV*| QIaq"ſ5Ãg ٓRu=8 KH\Ur 1븮vKŁOD RN2 n&4&LSM9u|[tJ> LQBtgɆVƨxg x^G?Ny^\|^} +R3??S_M"- +3$46w> endobj +2889 0 obj << +/D [2887 0 R /XYZ 85.039 781.388 null] +>> endobj +722 0 obj << +/D [2887 0 R /XYZ 85.039 719.568 null] +>> endobj +2890 0 obj << +/D [2887 0 R /XYZ 85.039 698.372 null] +>> endobj +726 0 obj << +/D [2887 0 R /XYZ 85.039 615.564 null] +>> endobj +2891 0 obj << +/D [2887 0 R /XYZ 85.039 596.692 null] +>> endobj +730 0 obj << +/D [2887 0 R /XYZ 85.039 172.83 null] +>> endobj +2892 0 obj << +/D [2887 0 R /XYZ 85.039 151.634 null] +>> endobj +2886 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2895 0 obj << +/Length 3513 +/Filter /FlateDecode +>> +stream +xڥZYoF~R@D3/-3"8[W7I 00nY]]W=Tz'z]]yyjuu. +}MzDcVo?~Z,Re'w.| w\v]o͇E82~̆5&ݿ_X uJ2`%zb'xӻᨿ\yJg{Օq5%߻WpY3Zj8-&5?CY/ywR9tb;~N둓oԗƑY_65ϭ:-=e}uϋ v6<"oP>s):i=< #4j⨾>v =wF%n&"нtGAFVRff;Xlkq.lCǸTxG` R@%N@EqTbR˺AXB8۷W΋w6YYwdgb|NؠCMSeH:_7Of+$*_3Y/u tԍW5-(U!Phi2ee\c`F*ؘ"jt`pqyfo/1m5W8Ӑ\{DCu/ۏm0le E0Y-5(#Gp2hϲ7 ҏd䠜Di˜mx9E*r 2!F'9,GӬk2a8!ֿp,8,Q>P>Ә1z[sD6aL}$xP-KgyNce2g2H̃hlFQHpIvŮџsǎ- G i eȟ9g + kqq#iX.GksaVe|0s}m kTU]&)r PsFAGLub%/>MQv iwDX3h{ #8zАؒ8>/R@0iⅣpnLrcr+tleH-4D4ny!evz?|=hm=@C 1 Ƥyt6 +Owo]nabJ3UnG"Dp_$ L`Z%-n3Y>154;=66aM8d!%]Ǧ!%nG |zGu2UF]VI_ hùU +$tm@{Xu a;:^BؾK:Bz݀#++Tp<0f*ޔj+bx7j=q=TIħI( ڑИ^J9EY+cci Z[I Db@V&5*m&sE ;=vͽdK#P0Bs6J@y-|Yw;9A6";"AB٧kػ_Qث'-x-"/41H5]fWMM2 7?2N͖5չ36P; L󬒯=-1;qP`p0B_}U܋;pzt'jao!sg؍t߂$+?*aؗTvZo/&^*p?J^wab3kU q/n)U4|gɗ&ng4Tb?ZIKz#Y=|Uq6O-vHPKtBN=rQmu"ĿØ;*m>aQz͊&.&ӣ&+'ЌuK +ܳ`P흅E0 T =zƪVd*?JoG x0d1`Q6]kzGS%c̹2]l9#pD9+ ZOnLJ`&Ol-aQnS!>%{N_&K[Fn4O,-1b䝣ȲzƳ\g/T},n2K0z2_TАb=T.wH j;;@igQommp.8¿-bQVN2 E@|ԴI9ı؄vd|pc{zcqxϞ9$19P'BR(ʥrzB8HVmŚ eūC46ԑb˼$j>3pUsʥ.P{0 KZRټ8e< k{e;-%;r|KJT=5$~4VznGV3}u'2ĕЌE3AD'hFJGGhr建ڨp ٹQc8=>yh |77c`ULSdφ_%>a;EQw*ua_iÖv#]_寞B5쿻:H",wݜ}yGf#nQ~vku1Z< JXKo<8 AGqٺ,!\DV3"R ) c5ui@`G#$c=6$3lДF Jf##I*o\ s+'p?K⎴:y`KF$VV͏3 +ؾ \Deґx퀛p/Io{uUz3V(0RWA1/12h?!Xx-7~%rxS6qp oىA1<~l +!= +7g<⼩cM80CL/P]+`js %Q$F"2og>F'vJ2)Q+ +O#.x /`?sQ@EObendstream +endobj +2894 0 obj << +/Type /Page +/Contents 2895 0 R +/Resources 2893 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2885 0 R +/Annots [ 2900 0 R ] +>> endobj +2900 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [250.936 169.022 367.444 180.712] +/Subtype/Link/A<> +>> endobj +2896 0 obj << +/D [2894 0 R /XYZ 85.039 781.388 null] +>> endobj +734 0 obj << +/D [2894 0 R /XYZ 85.039 572.649 null] +>> endobj +2897 0 obj << +/D [2894 0 R /XYZ 85.039 549.331 null] +>> endobj +738 0 obj << +/D [2894 0 R /XYZ 85.039 371.679 null] +>> endobj +2898 0 obj << +/D [2894 0 R /XYZ 85.039 350.482 null] +>> endobj +742 0 obj << +/D [2894 0 R /XYZ 85.039 212.304 null] +>> endobj +2899 0 obj << +/D [2894 0 R /XYZ 85.039 182.899 null] +>> endobj +746 0 obj << +/D [2894 0 R /XYZ 85.039 102.678 null] +>> endobj +2901 0 obj << +/D [2894 0 R /XYZ 85.039 81.685 null] +>> endobj +2893 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2904 0 obj << +/Length 3660 +/Filter /FlateDecode +>> +stream +xZYoF~> 8n؇\8ٱ3 +f>"-HߺII / >(u2dI|EpOJ(ďUsVo~ +,.WD*~vbiT/Iz\_pq<ϛO7_N}7 z߄z^jol/_aW?QA;3W[,UJ5~eW"M^>B;U]._/\xɫf u&tfnеbێߪX8XK0Kdq(ɼa!ae\(Q8d73~xrW]992{5#]eM_5zo<:uS2CtAy}6u-dx_~~"LY_-B}p ~d[pwb{ p/^wʆ;yt+{,~̇%DIohnwFi(-{^4;yW=ӋFtCOJ= ñ+~;=mnH˱ĝmc"忤-ݬd~+tza=Tm\ϊ]>n0>- <kHIԥ'\'4݃=?8O5g*M Yyfn0Lq*<Ƿ-^3J~j4(x%!_h4GNFGŮj52qǿ]Y?q M39.P j ^ey|v4qaz=(98d vpH[!0@ւх:Wc c;zǧ+mBX-Om);n7P˂!;Y 2aBsx)sr*yͮO7< 0ttr Ae}}H"v6 ElF_Zv r/YPil.88oARJZFsOPbPAD `vZy$̃";$C:&uX B)aۏUj<>p̝L'WvЅ=;k[93,߳j=j`3ʝ"M04x[G>fyn'wH:STrCK&`$,v_\^SX[9^pI3S'СQ>KBaeXv R.)1T +>Y9HCHw' Lv'JBR؎*%^=9*'&$SƑ@ !<- %`@^ +wMB=%?,1wGlZiP EL$lt ՛IkÀ4{aGs&[u"5FiR]I+!mbp +۝-aUuBW1&zfq8>x+Ax'lAg[K:0!ׯa|NhFAJĺȓ&s΁ 7sȼQt1/O 8=['ԻǠ0}Kԃ6BZhʼg0kCKaB&sHY )x$H̒#aL)1jF)r6Vt{.gǹVQުf +9-~y4)I K[߹ XW0"bTp'׹3M!JpIx[F4y=$ +H9ؒq&^.VPxȁc|Y :J, [jI8g8HcUC g(ݚ Ϣ$*wSj9 lTfUM8D. MѮgDBX>ҁ7Bj7їጆa|L(2RL@ s$xiJ1/[yץ$)*"懐5lIz$eW T/JE0&ya`Q-^.Mm&_IO5cީܩ.Z!xv^YlpoZYkti03H,>EG V0 f439*&g1<Ŭ.9X* 8_T@1`Mb4=M&ϩendstream +endobj +2903 0 obj << +/Type /Page +/Contents 2904 0 R +/Resources 2902 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2885 0 R +/Annots [ 2910 0 R ] +>> endobj +2910 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [348.805 356.06 464.335 367.749] +/Subtype/Link/A<> +>> endobj +2905 0 obj << +/D [2903 0 R /XYZ 85.039 781.388 null] +>> endobj +750 0 obj << +/D [2903 0 R /XYZ 85.039 499.992 null] +>> endobj +2906 0 obj << +/D [2903 0 R /XYZ 85.039 478.795 null] +>> endobj +754 0 obj << +/D [2903 0 R /XYZ 85.039 235.518 null] +>> endobj +2911 0 obj << +/D [2903 0 R /XYZ 85.039 212.201 null] +>> endobj +2902 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F20 1617 0 R /F68 2909 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2914 0 obj << +/Length 2607 +/Filter /FlateDecode +>> +stream +xnF_!`"3kޜɺhv">P"%D/Iu6iQjrf̹3VII&Q\Ǔ›aqC's/ܭ._?]{:38*p(_n?\_M'~-]}ƩyicFVn_;뛏fʸ"; g.zk߽IWsMO*I& ?݌ˋۋmxΟj,L%n1:2T +*)\)3@0tv2,CQNe2rn/|ӗω2hWiu`ջ (gU;@"-`S"e9ՊuihPӶ(5O<ܴuZ7S8q*3*Xj vSPX6nnS9;x>]ˉyMZvB)ZE)c#%q2_X%\Ά?ʁV_ + PBF7ZV:{8m])O-.}P.ήk]U?@uZV=mzskY 3g뭀¶]K`au+-["vT !w9:M!@:Z}ڵ@h%t}aQXKMxx |$n[#, |=NX5'j 1fD K-v͘,iJH$PѸQ2I"1]1'_k^#1FE4f"ފc'$`6'}6L%5"FwTkK9 WUK^SY߷·J@$YcIƼ_B9JxmG=@o](S1<zw#P, + Աqy))ѐ}) eYs;ż3#1d+ɖr#C:oe$) r;eBAZT{q?8zhmNtgJtG9E_qP^c֚4&3VUp$\N OxWBPC5_RnvÎ]2ʹԮЎj=|s(0\#E;A>Ȧyw醭eҁa4rLj\aa{C;N%)3@"xH +=E1 D*l>+ih*>Ĥjc) ҵ3rM"$FLvxgĘs&O5:LmWmrEpVܼ\UIR>{K8k-@51ffpQ` Nl< 9pF;6[ĉ^f᡾63E%X' OHl$5+F(aR?*"l?Z›nmĢ$lme .Jr!yҙpFv/w0IE4٭߼;ԣ^ 0('ׇgr>5 dC%Ŀ!(yW/^8;<{7 =R2Z1˟uKݳWcj"$$Z]&"wcHcy/ OO9?O7QWe o(S+CLU!Xy %` q Qd VcOzr}hxw嗧σZ`$Eȹ/Jy9 )|̃Z 2'jIJ1du*<"E/lդeUc-{z/h'F&?9cotpȤ^'. _`žMypp2z2Չ8|Qe;3 HYŽr(8>G7zX1D Q1R> +@@ [JY7W\4*%S e'tj!ϘOO> endobj +2915 0 obj << +/D [2913 0 R /XYZ 85.039 781.388 null] +>> endobj +758 0 obj << +/D [2913 0 R /XYZ 85.039 761.463 null] +>> endobj +2916 0 obj << +/D [2913 0 R /XYZ 85.039 741.337 null] +>> endobj +762 0 obj << +/D [2913 0 R /XYZ 85.039 514.594 null] +>> endobj +2917 0 obj << +/D [2913 0 R /XYZ 85.039 491.879 null] +>> endobj +766 0 obj << +/D [2913 0 R /XYZ 85.039 154.621 null] +>> endobj +2918 0 obj << +/D [2913 0 R /XYZ 85.039 136.147 null] +>> endobj +2912 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2921 0 obj << +/Length 2442 +/Filter /FlateDecode +>> +stream +xڭYs۸BuID|̴ȏN/[ɓ̤@;>TN틔hQvd.bwR=F-3OgJ8HwcӳG)C 7]4]c|?w`Y?V?@eRuue6ĕt%PD FYCc@Nqn0Pr8[Adüʞw8i3\b +5V0a)Wþ?Q6"EG*[+Fas$4T +E&rzKPlVi``Or6&{f,<5Ƙ=2jO{Р +`VD6Dl8C)y~d1o [Q+g&r TbMӡ/>2|mv;lNE6G;О9xx0*ɇG$x3dJ%|cD0=ejϫL9t0C51D\ʬhoˈ ٟ˰.4 +Н=pj]¡GCDt dXa1t4oi#f6tp6"!"!Zΐ rqR#SWzQOGMu!3U1 ,p\P'9:~#0+02bg ""/0Ж*hRI'X .4k薡m0gÎÂصcXFq֊:Z2 w޾gm_whC[ ,D"H <혂86tQfggBǶ)", * q S-;(b2 O:<1t(^c趪݌M$1$l1z(ob26 byq(l% +Z!%qm0暌'Yw$dz뷫$ǀGcwɐƩ([muP2 b+զ&2* m ۟1Ŀݗf:!")l3 _)|+xqW^8J RzS4B9!LƇ W\ˁK;P",Llhb_rw}@)ڡ*tK++"/hՠJ8\?&ᜯqu/L*PVϱn'Rjeydi)Ner蝏UvU՛Ӕ g-4}HbշdXB wY@G0lW8AY`{p&w֙_ 1q_s-媜/%AǑٞM"]͝_ixcvFg~!.@CWФJ\ʪ] 8rl}hd %9'ۓt8? +椢PCPf %9_G3 4e㔨Hh_z"|qM2'/B_4 IRpC+/x8RDv[|W'Cv3:OSK~ƋLʕRMendstream +endobj +2920 0 obj << +/Type /Page +/Contents 2921 0 R +/Resources 2919 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2885 0 R +>> endobj +2922 0 obj << +/D [2920 0 R /XYZ 85.039 781.388 null] +>> endobj +770 0 obj << +/D [2920 0 R /XYZ 85.039 544.417 null] +>> endobj +2923 0 obj << +/D [2920 0 R /XYZ 85.039 524.428 null] +>> endobj +774 0 obj << +/D [2920 0 R /XYZ 85.039 228.345 null] +>> endobj +2924 0 obj << +/D [2920 0 R /XYZ 85.039 207.751 null] +>> endobj +778 0 obj << +/D [2920 0 R /XYZ 85.039 109.069 null] +>> endobj +2925 0 obj << +/D [2920 0 R /XYZ 85.039 88.475 null] +>> endobj +2919 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2928 0 obj << +/Length 2044 +/Filter /FlateDecode +>> +stream +xڽXYoF~ׯhD󖘗"AaH) GTk)J 3|3KglxX3f25\V8r>:cǶ";W$3?_fN<32'x{{tK _^-^ޙx's}q+a߱o›k5(0q<+#Ry ;j޳b,qьϣq ٖ;hۖE|'lfk c^5୉;g[kN0൲m 6>5ـi ]c@1bٚwjU/v +js;pj͙gnT%& nS}%6xMhXo6 \YJі+Z9.UŪ+)UeA\O||֠Gu Tv^\ciq +c/e#1}puٜr)dʢR(:p_e5jX+RgR,+Rb# SHq3h }PZ!oD6^z"6[u.]d,f_P#pcNB&c6qK;щ1SZV~nunj}[#ENoxn/Cy[q}-' ^A=\c EFTѵhċA&;|hj%<*e=?IעFcuhzl_IxG@~1yA<r(PđOfApI +X ~Z/p+UJMR C;v^AQ==%\=fD֕mB$0L! S8$ ۄ r%H3UȸDGT\.Z_^|==Ϫn rєsm,17R,8;}bQŃYJmy[)+z&Ωk(^9\/Ek/ABxeSL9iT%nČ#!4dkq 6HS˙ȲLWw?WABEQ26L8ܧjѬǡsZ$:2XQ7C^Q,J9ݮVKqT 2%#qO}!.H!UDq#j H LRSA%++arK`tr['(NUzybwOľq!uaYJt r\q(0a=ϥJ@ ""Gٗ(mgDVޗ[*EGR 5#X[h,|TPN|c|VaNwO- ;rg`Ggfw6ub&u&=T E.I92lEZVgz ,=nK HS>Ν.m6/VI EcZu57f%Qev&/NV|6#$}e%xR=>DQMtgчuulNz^=jkz@l} S׶\4{ +l endstream +endobj +2927 0 obj << +/Type /Page +/Contents 2928 0 R +/Resources 2926 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2930 0 R +>> endobj +2929 0 obj << +/D [2927 0 R /XYZ 85.039 781.388 null] +>> endobj +2926 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2933 0 obj << +/Length 1561 +/Filter /FlateDecode +>> +stream +xXmoH_!DxwNh\'\%V;؛~3;N]NUo3<; l3x޳`y MzOB;O$yo`(Cwӓg O.qxL񳳁K#0PtlvX.`%0䒹N 5G WzǓC0 tsG/{6a_Af< 6iƳEZsa-1! %#|&| npv%-|N/[jR'(&4RFZJ2yЪ(*u<`)pxkKiְKwT:?|XA$H Dn+>$QQ騚_u*/#tA[/"eh$ ;Ǚ;kDaoz Wxp -`'IAh$0DSLGR +uZ:.7?5"ӌ]M>m(:6iInG^Wڇ4IC+7k$hK5 ypJHE}!M"drs_;}/?TuOnAp[i)̡${q +b&W&@eUfE͈#8(e'jZ'ȇ2REiCYz8g +64 Up: p>qul +;O\9zБxZaN;?1nYyzإ>LlQ &=;{;9]MǓ?~;Mw&?'uoxΏsaK},<~W3Ap*;mX{EMFu]M&d(T +逦 &|K(˴"09FW'\N5UTCU04UʜjbLFV}z; ŴX|%fTۤgM6-"6~G\f؆!xx4~>kͯ\rNA~)endstream +endobj +2932 0 obj << +/Type /Page +/Contents 2933 0 R +/Resources 2931 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2930 0 R +>> endobj +2934 0 obj << +/D [2932 0 R /XYZ 85.039 781.388 null] +>> endobj +782 0 obj << +/D [2932 0 R /XYZ 85.039 761.463 null] +>> endobj +2935 0 obj << +/D [2932 0 R /XYZ 85.039 741.337 null] +>> endobj +2936 0 obj << +/D [2932 0 R /XYZ 85.039 741.337 null] +>> endobj +2937 0 obj << +/D [2932 0 R /XYZ 85.039 741.337 null] +>> endobj +2931 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2940 0 obj << +/Length 1369 +/Filter /FlateDecode +>> +stream +xWmo6_9E#5E% fqt2Pْm!R`ߑGٖtay/xǰ.Bu=Fu.saZ~]2dO;櫡eNJf~0~?!zիQxs}y= }>Jh۫u[-0Xk_%e'x5O_Ɖc0s$30PfI:i7;pn~wݱiuҙt~ޙAEh G HAƝ݌|s |lzCW8c R>MVeQa8"?H|^˩qllz!_Y#-z4,>'$^5!Iv{<;m!\ 7l`r&)3{ z-ryTyZ|1&ywB:H]\I}Ό<M"r!B-߀CW ׄEHO ޔRYMu'EXEM-:$áv7e˯8]C`Bn=6Opv{l8rB3[6E#EI/b  `Skm ̥R`ٶKL%JƜt5ifT8 "X"Q5̶DEQyQatjy [>- +JƦQV%$B2 P +;&dmgҲ>M2J*LFt{p +oC2:2`<=\-PQw^YeS DOrϗ̖õ*}P}+H0{R8*jPNQf'X܇$fe=Q4ũ8R@Uᵴ'C uc?mIb9xreaGYb +떯7zzȀ rV0Pju +$YNLДTZj"?)ʭ(XGT"l4C8;Jg Ptvٰy2K_jIzPLQdZ#y +ovr[oq$N+ e%y$AgRJIx",*Eŝ?O<޽r'o/im R>Zohk;2> endobj +2944 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [361.189 502.381 414.575 514.071] +/Subtype /Link +/A << /S /GoTo /D (winbind-solaris9) >> +>> endobj +2941 0 obj << +/D [2939 0 R /XYZ 85.039 781.388 null] +>> endobj +2942 0 obj << +/D [2939 0 R /XYZ 85.039 519.048 null] +>> endobj +2943 0 obj << +/D [2939 0 R /XYZ 85.039 519.048 null] +>> endobj +2938 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2948 0 obj << +/Length 2188 +/Filter /FlateDecode +>> +stream +xڥY[s~ׯ;{CNJlGXN-zNDT$UMsYJ3{9{\sYXB#Gv8B'h> GLz +H;MDj$CB7,%W?^Oցb<$xuXﯮy|z ^_JOjƿi5z;u#0ZXH`spD&" +/ T,%{B:7Zܴήޱ=3S֚Љ0qE쭦ŲOuVMջsM/ytWWUHW:]L7yG'wſ6f:%ŹRUE!V:й}*6 ")xUIirʧ.+VmU.X02 Ds?yzJԽiXKYLMш%W_/3:+G !r7odӓHX۴@-n~b`ʪMn:edz͐S~s L$9{vE)@ IÃmDA)! Q+xd)PDۆ9Bk}lJ$l/Oi9gO즔p:g>n*nrX&M+%G0He%Q9D/oЫV8|ꑏk{F=6 ;=z=|!*'Q70xd+4Hw&EAHe "O` *Tbڌ2m'AS- +xi!}31rOUHgD~B   :PcTH +ygt*N!ciCCݖAkaSDu[2d- 5w`:1飶<"%m!XBފow2N!#s"'W %id^^ݔsB%3aa0@} P-jo3l~[̂׍rExUن}UdPST3{2cx->,+PQ6 VmR-8>yMGI_w]ǁ9{WeeEъ@E(3gܣH-֏I"rou-bu^긣{ばq+%1TviH!Nnh@+Ukc#> endobj +2949 0 obj << +/D [2947 0 R /XYZ 85.039 781.388 null] +>> endobj +2950 0 obj << +/D [2947 0 R /XYZ 85.039 341.117 null] +>> endobj +2951 0 obj << +/D [2947 0 R /XYZ 85.039 341.117 null] +>> endobj +786 0 obj << +/D [2947 0 R /XYZ 85.039 283.083 null] +>> endobj +2952 0 obj << +/D [2947 0 R /XYZ 85.039 262.488 null] +>> endobj +2953 0 obj << +/D [2947 0 R /XYZ 85.039 84.027 null] +>> endobj +2954 0 obj << +/D [2947 0 R /XYZ 85.039 84.027 null] +>> endobj +2946 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2957 0 obj << +/Length 1800 +/Filter /FlateDecode +>> +stream +xX[oH~ϯȣ#aߐK EeX rIcձ2v> +9OLe:$.7z;/'ž؋½, +R?.Vtft~yۙ+tD8Ng3_߼|sOp/^XمnH9k UJ w&H<__iL-}Ot3Q!rv^NM2Ո\姞0P Gm ;k[4:*,.F/M7igctX3޸rYoI~ 31č SWF^tbA8tv+d~[FSd-: HqN +EoV5ʭ] /,HK2Y_E.k{Ჶ+2k5oNc] (S'AGuJ8! WO~ d3ߕXa )#0O e܅2M !d,*0 g/s,z0 zwh .;C[BbcRe1 0iLJq~x=FX]i^`(6>6Ĝ y"/MnoEGR'X=lzWCpYW8y +py꿢LKC'@l0>6nEViq7CfloC2H5GL@0ۻr^&o]o0z@2˶M^'cΙш= > +ݺ.E",pJB9 m4 0:"ҶGn؁늳YD*Xb8&3U,Ak45o`7?ѻY"1B? eɣd>qƷ.@֚0+-Lj`=* yAOؒE%;{q^o2 mkk%ʦ0IqZ&hF&^-=w+Xd"@Qn XMksSRb;Pk$R:0Z +sWe}ɱEWٲH5m~Fk|/+ gHqS!FE3ro{!,0g1<X)^Cm`&}1zpN9%ᝮ(gdh [2C.}+%%Հ%At})p?8-!ʬaGL mP|r&NĦHA`waW^bMDն*Q0eU#Mf̏&CrXS0@{ +,pwxC}?;ax I_7F`~9w\~׽_7دBB_@)stendstream +endobj +2956 0 obj << +/Type /Page +/Contents 2957 0 R +/Resources 2955 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2930 0 R +>> endobj +2958 0 obj << +/D [2956 0 R /XYZ 85.039 781.388 null] +>> endobj +2955 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2961 0 obj << +/Length 1676 +/Filter /FlateDecode +>> +stream +xڽXmo6_a4 5-zM;.-EaR3Gr,;^A,Gs/}11g2;Aٳ&@B,PQo8%0}NSXM ;y6$R9P@Br'dY6_3(È0HRIbI+|ިrOG|eS-4߸Uc@;o[Q8d$Xx$b9kpܢPj(j`Qmdk>|K=.J2(Č0y ;z4} ؄Kme6]oUr0N_#oM6T2C%`0Rg +tdݡeE.iVIx;DkvW نphHpRCwR/ % +fr+:9Sjtv2N&5L5B۱ydr/(0-ڍJ`hj4jh'2po`C4NrzɯMǼvK׶ F +8cLߌ:%сj]ۊ(0B4bjuN7iT!'5mG찜,{&8I Q׹]"B텺KEd/N#:֖a.%:}liEղ 1ljJu`PeZm7_dݾRV,aUi)릕88 k> endobj +2962 0 obj << +/D [2960 0 R /XYZ 85.039 781.388 null] +>> endobj +2963 0 obj << +/D [2960 0 R /XYZ 85.039 679.517 null] +>> endobj +2964 0 obj << +/D [2960 0 R /XYZ 85.039 679.517 null] +>> endobj +2959 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2967 0 obj << +/Length 2390 +/Filter /FlateDecode +>> +stream +xYYoH~@7934fAK$"<q﷮&%bnVUW}u4eO,gO"ߴxFFd]\X-epMLlˌxОeqϫә뺆YF/77}xa;\z=Շwa\ngoo/fk^L W.^/N1#Ӳ<Ɨ_&  thrc˴xR\x>rse_,.ճ5ooXkYiEdZf VsmUKw|I&J.d:-2.̳e:kY\]U+ofSjNxVRm"-hmoOx5f35s jg*+i2r.$퉩U bn'JsZҺjxoP +LU+ +UA"R[kSn^_yJA`jU<?+JՇOnO1Z +$H<w$:|#o? L't2x ԳB,zn $w(6Aòe; %J+XYWk]ۇر㇪A&pHj}JNPXX 5{SqO8bm<6|^fTtZY6rWFmd Q +'I2GlNzOgAZ5s\》UW2vM@h D&/RLbVNH+lw<@ +}";՞ngkE`[bH{`'d0a}Ҏ0#Ӄ>nKsBDhT#ةg^p5@; : EЇ%L0}wXN`8V lw#L6 PCaH+ycdw|TiyO)#4r8" }ms)Z :k;Wj ZT##JΘwt(xx M]Ks מod ?t:%gWȇzp>#xve'E"cQ!LT͂sG{P!zܞwẂCZC":gzٜY0[ƀ(i”H .pLLVd:x[wlgo;Giӭטa [5s/"lB} R.J7H ꔙpphKwюP%ŧu|g!G^sUh186f#}z4"r0 N }2>?M Fl*[l>ܺbI!л +_YsU/%,担1a|غzϓ-qh&ǼNTuc>VfFܷjm0WH ǝuo^nN +wLe2S"^ +xV,qТRyAHnP C:å{AUn4O~n+ YQ%T"y+jXG0v vdn ]#A &j\^@OೖyXy4a_Pȹa:I>0GJ&+g\FΚmλI9ut R ZHK갼SCQO1tl>F%Go`9Z{}#RQ0>Fh +74+ޓvݳGX+_hendstream +endobj +2966 0 obj << +/Type /Page +/Contents 2967 0 R +/Resources 2965 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2971 0 R +>> endobj +2968 0 obj << +/D [2966 0 R /XYZ 85.039 781.388 null] +>> endobj +790 0 obj << +/D [2966 0 R /XYZ 85.039 413.993 null] +>> endobj +2969 0 obj << +/D [2966 0 R /XYZ 85.039 387.379 null] +>> endobj +794 0 obj << +/D [2966 0 R /XYZ 85.039 144.576 null] +>> endobj +2970 0 obj << +/D [2966 0 R /XYZ 85.039 117.961 null] +>> endobj +2965 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2974 0 obj << +/Length 2952 +/Filter /FlateDecode +>> +stream +xڭ]o=o"RWb\z -AdGdl%ٖX &9Cr83ZZ"Ib\-@~DAWIXigapuQ q.6P_(>n]U'miav*{f][-4?~a$Qa@]$3@TBM|x(x[Uڲy-SooJܰ[ h$ Aʮz.y}ID}wv\P*hp/H&孉`de@z= ) MՀZb3,;3vmo@ +{2k +dBȰEWS2Nq? (ϼ.U^ <#AnrmpQ# G^-48<2 40~DCFV]s)\Q-p6Cu'w儂?G%W*=5EeGMݴe|weϛ\O9YfFa䘕A,vmM^$],/ #3'LI+(y),et=/>k_u' 5&EݝԀBЛʉf牄(euT7ʄ*{XсIx؋ZXH{3+5#>eCJ(79ZRm9,ř-^`X2hKGwtxxt-NGZvd7bR?ʴ}\j9fj{U*]\|w+?xrD!d+"I0 A +?H)Z㪚GKv -+I)طǓ@]ehy#y46mk}N "ҎuSN[3& T.g6 ozzĘƦi.|]Q. 1BuVXp 7BVȽ3l8qK=$&=&Bk5'NZ&{gn%y_wҘ+xJiPfcp[1_Rs 񅔣p-Y:q^W1$n lWH9Ę֝5iO%Bt)Ky$]/=`r@,RQr%Q©c Tg4O&a䛌2\G( %*,]8U-Ї0)YI\-ժݦm81gue +O@ Zj\@J% +QX =[sf ^Bo $6J!0 et\#+֢U.(:zp\ +pi0LO'/=YhQJu\+OIս.űw}kX +ү" %pESB +ݛc:.i +SJh]T +ٜ򛰊P}IkEyrDWIBj+#z@9CگPF癜Bl.r/j GpHO +Wh-) }vPgK|9i=jVtD$K"Z;uMʣxxL,\*Cify2:F.h_i jA rݺF*RB "-\#$GgEdG>)|2pB \T_xLn,2tccJvh|( Х:{/:hg=lfIS;}D@s,5P bo$FߛK/9Zh'õ%-sssəħ-$>j9zV(qk WBV C ̩n{u6<kϩN>JW#iAAi7O>V>纔(IF#!JQ{Q&@SP=4w@z4r#endstream +endobj +2973 0 obj << +/Type /Page +/Contents 2974 0 R +/Resources 2972 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2971 0 R +>> endobj +2975 0 obj << +/D [2973 0 R /XYZ 85.039 781.388 null] +>> endobj +798 0 obj << +/D [2973 0 R /XYZ 85.039 761.463 null] +>> endobj +2976 0 obj << +/D [2973 0 R /XYZ 85.039 667.044 null] +>> endobj +802 0 obj << +/D [2973 0 R /XYZ 85.039 611.854 null] +>> endobj +2977 0 obj << +/D [2973 0 R /XYZ 85.039 582.45 null] +>> endobj +806 0 obj << +/D [2973 0 R /XYZ 85.039 364.615 null] +>> endobj +2978 0 obj << +/D [2973 0 R /XYZ 85.039 343.418 null] +>> endobj +810 0 obj << +/D [2973 0 R /XYZ 85.039 303.379 null] +>> endobj +2979 0 obj << +/D [2973 0 R /XYZ 85.039 280.058 null] +>> endobj +2980 0 obj << +/D [2973 0 R /XYZ 85.039 210.556 null] +>> endobj +2981 0 obj << +/D [2973 0 R /XYZ 85.039 158.82 null] +>> endobj +814 0 obj << +/D [2973 0 R /XYZ 85.039 98.425 null] +>> endobj +2982 0 obj << +/D [2973 0 R /XYZ 85.039 77.224 null] +>> endobj +2972 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F70 2201 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2985 0 obj << +/Length 3051 +/Filter /FlateDecode +>> +stream +xZ[s۶~Л9M<3nc''RΤy%J"]tt뷿r.nakv|Zr6[v2l/pq+}V_ۍ#[hw{g7Yz:u ױkO/l9ѡygh5[8Cz2U'U5*~wiɕU:4'%>yfTgm,"oPijteQʴo-)ePN1r= ªĥk҅w SOl?$93qFvU}jځgiT)\A +IYx4Ih@؆S^xSmQݡF4ie+k)w)f>f~Ido%I4M\`|Y{%Dpt6AIEr?Yw!wʝhْ0]vM7i5.ɳr>񝛛Kx(۬= +wGSؽѳN?N +4tZR*weTlMRҜĨ7 [<++J jYTI=,yJ?ɁqvBۥE3`zZNe3Ap5/5yv6z*&+x"vo{` Xb}`_&/ gņ24`[3,Z|h* w rb >.Z|d_G[Yfcct|22Qt7>J@}S"q'Z*>TŬ\cYkz͕{YM676/ 5,BnĠ ,шP:؏( +6 2F-~L{}0`٪sxm +g$p*h~+9:P5憎Uh]B)|ޚ{gbwM+ZTt$/utŀС"5I5aQ$ԬrL +e6Pyuq^Ch")7r\m}@Mpxͱ6acg=}Ma2F6ەag xs\F5Wmt4%?CN t\1 G-;y DL3G{z

n_^bigsŕD<6=ׁM?n$gDw  SIY7' }C^ABVb?+B~/d"_!$Ag-M5ܖ #NUc(mG)߇KʎHPC\/8#ËlRN+TfN ՟Y׶a#> ?Xg7Qq-`Kz# Td199PqAeb,\& p;M +~R˼S$ PL$ + +abP@zPl>)sTWT,q;~ #qN71˵}+q]W,@40+ yiRDIs[mu!LE\n?j +&@0}Vxbnr.1OR7 +=2urHeo@Pv  I,<x,ߓf~Co |}AHc  g|Uma>K)M lڷ}M@}\ آ"9<4 +2Yɠ.H(]mh5U8VENF(ćun_{-e;C#嫩PG_M_~5~{7gNnY)mn7mc|m>7Czs}Zlz8m8@pXu(,^)a'MXq{> endobj +2991 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [327.043 103.871 512.306 115.863] +/Subtype/Link/A<> +>> endobj +2992 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 91.837 216.398 102.314] +/Subtype/Link/A<> +>> endobj +2993 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [327.043 63.223 512.306 75.216] +/Subtype/Link/A<> +>> endobj +2994 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 51.189 233.58 61.667] +/Subtype/Link/A<> +>> endobj +2986 0 obj << +/D [2984 0 R /XYZ 85.039 781.388 null] +>> endobj +2987 0 obj << +/D [2984 0 R /XYZ 85.039 664.726 null] +>> endobj +2988 0 obj << +/D [2984 0 R /XYZ 85.039 585.892 null] +>> endobj +2989 0 obj << +/D [2984 0 R /XYZ 85.039 535.672 null] +>> endobj +818 0 obj << +/D [2984 0 R /XYZ 85.039 292.839 null] +>> endobj +2990 0 obj << +/D [2984 0 R /XYZ 85.039 271.077 null] +>> endobj +2983 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F38 2158 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F41 2104 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +2997 0 obj << +/Length 1931 +/Filter /FlateDecode +>> +stream +xXr6}Wm2f"M;팛Nqc}H@ EeY]삺Rz=%.$)ɤ.zn+=n?nKWnܟiyzzf0}ߑ s8 t~@w\~geRW8>L_.; D>G/{I cW8/zA0{ѻjO:ZE]2Xxc$0n`-~bpH`( |TQyUͪc&s`_Y1>xbѓ"Yeؑ<`k:Zi_ƱS*3?,xca#5 QrNcUM),7(߮UEQ!KF*jakR*ьˌmPki"1l4Ĵ&`1gUb.HL5`PDžzo.O֒O1n\Dfva2ǐj. iq;U'VKF@:!gMn`-wIMi&/g'W0U\069"MɔW]L!AI )C{,*jDy ".w(L۵ tOUE>!/B/ZO2, *tψmsI1[ϓ֒Qj8`=+2Y9,1E9>]HxU\̀҄K6tW:7C Pl7| `|/3Ւ5Ƒz! 2dD6[}iTJsrZSV_b5K 1k)k]C-ȫח0|}zPb'ḓtustnó=Aڬ\([40K\zE!hz?`1cD܁@lD<ɐC8'5LSG,kh"LUf'5MڃcT4QpALp1F\!-Z=hnk]:CŲPĐ3+b'4ҴPD"G"P?XɓQM{cӫ[sgyyr'{ !^P QEVY)V]m +3/&]St4ŽS\8>P-wš84j 8Jףۼ-U]txU06b1ԾkdF{TCc3kE+RM#FrM;i]yF\[5Gpq+UʎP>q̪5K,;B.0=VEF[*;-ŭw][^%+~ˤNM$٧kj!\G+fY+:"˷S>-.Mmp8Z*dWzq\ݖ XX=|&78On ɤ[2GI=tF:Y&RQya ިbMPZWyz`U}o]xl]dYHuIeI^l2'UyMެlnjI@ᾒJ> 8jUg0^'/ζؽtbd_F'HiLܚK:doS[g8JӰ˄REyTCj!~}"*GFOYwYܯ+85'Çajݏ1'ZϞ,5 dLlTk31t|@Dtd7>M.5VAGqMPgFJCzmo? U2{e[Sjf{1 gu^7 zC7yۿ뎿AI?zc endstream +endobj +2996 0 obj << +/Type /Page +/Contents 2997 0 R +/Resources 2995 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2971 0 R +/Annots [ 3000 0 R ] +>> endobj +3000 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [218.134 709.485 287.369 721.175] +/Subtype/Link/A<> +>> endobj +2998 0 obj << +/D [2996 0 R /XYZ 85.039 781.388 null] +>> endobj +822 0 obj << +/D [2996 0 R /XYZ 85.039 761.463 null] +>> endobj +2999 0 obj << +/D [2996 0 R /XYZ 85.039 736.911 null] +>> endobj +2995 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3003 0 obj << +/Length 1391 +/Filter /FlateDecode +>> +stream +xXmSF_ g^lL_\0JҙB:[ +Hg&qMCv}T3jC Ӻ.%jahX9iP%ah61:.7S OBď{#lYi]W5MWݤaI#\^&J'}y5M쎅P>4^ZhO8=\3 .D]}4 Df pƙaP:SOQCaDThHEXk߰iv]V^Pr&"x4Qh0 U%ۈL!p0)q 5ؐG(IeDHp3 qˆHƤ]Ajv&ɚCP@t?G B'ۡ9}(iEsQX, n>mGu!; $MTwX~xƲ֬zF]%k;6uGTel^ŇRb ?MX'-DEI@ <}^󀤄^AU]xn#:0igQW&x 0M$S8*[y"C,V\',LbsUɔ1ܕQe,wIkKtK;"v_y5IJ؏o yendstream +endobj +3002 0 obj << +/Type /Page +/Contents 3003 0 R +/Resources 3001 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2971 0 R +>> endobj +3004 0 obj << +/D [3002 0 R /XYZ 85.039 781.388 null] +>> endobj +826 0 obj << +/D [3002 0 R /XYZ 85.039 95.579 null] +>> endobj +3005 0 obj << +/D [3002 0 R /XYZ 85.039 74.989 null] +>> endobj +3001 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3008 0 obj << +/Length 440 +/Filter /FlateDecode +>> +stream +xڥRMO0WhKcZ Radil҆,'[)yf +PgҞfv6Dч9'0E(Je 2; %X!EyN>ͯ 5+2Nrm(m4:$v2C(ivd\B㜱MUx`ï IV\n'7,kѯX=}w S ++a#hh[C0cO愵v 8>[S8q?*x#DZ*~"SVxTNB +v< ڽ']pP_sendstream +endobj +3007 0 obj << +/Type /Page +/Contents 3008 0 R +/Resources 3006 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 2971 0 R +>> endobj +3009 0 obj << +/D [3007 0 R /XYZ 85.039 781.388 null] +>> endobj +3006 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3012 0 obj << +/Length 3611 +/Filter /FlateDecode +>> +stream +xڍZYF~_1K8ElcN"k+0z(JC <ֿߺI zoTv6o eD)7 +C(霙Y^$nYG#~Ymqnk\}uĽE|w3w3ߩf*ݬ8/5W>)iFe}[zs 4%σ1U0 +r3? +#}>̜W]0n)5=pʡec%p4jߍbe}M]P3=gú[#wPtWy 9k\xQf ,9<2 83T6if8/xe 5 "2> Bg3?s/rrDʢ?mx88m[o7/mZp=O<nvG.WqNVӓFt +#PBk;﹓:Y =f%ֶ :@+3 a:/{3≰Oi t۹F_+*07 f%jYՋay#Wʻt(JxYTBrv Y7o-ɶ*a$dA#\"Iߔ7wiH0h] Ð;1_\?I.kwZcG!QSXYy 27KCI2ך ͙7"Fu>"7K%=OEձjG*ΝPEBඅA?3gܐe }ܦN1 E=5ƺVxpJ< *"H*=6ˡEAeZ2V8XX"3~QD,v ?O撼hB]R.V"@z jvW"0KoŭzWo|DsX" +[\}3 W_?x|P]p<@MhJ;¶ Ytkk^N] 6kbj{zG }UM3юi{ ARݬdzn`J=Qdg1w ~M1%HVO([*4O]g0tFr~@.,y @ ;vb]hg#?SK}E.okZbprRcKKNs(q=Ƥ TaY4dF:zR}fI?v麿^(>DFv{.۶".;qa;{ E^s% %;cH؃EwS"1!Ogq4Yu,"ИB++Gqg&/6b+邿x-5xqMDƺr$:Vz(* 3Y`s6>[F8IxFo;$<觡DXLe\*> 9BV"c_Qs$bTOn &y[oV7\dANd؟YAV~tS?"Hق\h@gƎvi(r#/ۋn˜LP.kd7kdxf +mj)B9Z.NkYLsuc3:`A-."_h +SG i@0'pW56H}gu FMa3q(8xV#0 HBI'&fgqyl@|w9#A*Ht MMm`-z5RY&Tsea3wŒ]VL'Fe <%}7V(H秷WrP92P'' OI hΆ}*u쓘 , ],[Ȱ4|uH[\0ת7H\TH)7  D)W;^tbMˑ5mHfq I0C-=ldօpVۘ[Qb&GlEtjG hHҋL-IW,z\{0bXޙs7N]l+kkQR(أ:IAT92 +[z+?6FdEŦY\xT;:}T_m 3i{GlhG4:Q$J,< +%lӤ%[#Bz+Ys I#5d/[IyV12jeeN @{|OqS^ fhw`iԞnjAXBGY~r;q+mBn@o䃧ɶHAu- a`̃,0p*? +XF9+I?r, &֟;1 d&ɄEzJ<'$qͣG"v(ן!I҃\~22ivd?0^,ŗ[Xgf"?zgLMҎБ0)(*HxˆdU̽CAS 4# y=!.0'< S8sL `S*;$P!endstream +endobj +3011 0 obj << +/Type /Page +/Contents 3012 0 R +/Resources 3010 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3018 0 R +/Annots [ 3016 0 R ] +>> endobj +3016 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 313.422 824.811 326.323] +/Subtype/Link/A<> +>> endobj +3013 0 obj << +/D [3011 0 R /XYZ 85.039 781.388 null] +>> endobj +830 0 obj << +/D [3011 0 R /XYZ 85.039 761.463 null] +>> endobj +3014 0 obj << +/D [3011 0 R /XYZ 85.039 667.044 null] +>> endobj +834 0 obj << +/D [3011 0 R /XYZ 85.039 667.044 null] +>> endobj +3015 0 obj << +/D [3011 0 R /XYZ 85.039 639.536 null] +>> endobj +838 0 obj << +/D [3011 0 R /XYZ 85.039 232.013 null] +>> endobj +3017 0 obj << +/D [3011 0 R /XYZ 85.039 210.152 null] +>> endobj +3010 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3021 0 obj << +/Length 4053 +/Filter /FlateDecode +>> +stream +xڥZIwFWf0O@cc˱'$9@Db Fҿںyy<ꥺkԃ:MB 8Qn$;]A'J(SzQ]99sS/=#WǷW7?-A8*v8Nr~_Ka'λw_r ڹ¯?[,*׋oyrq3R: +pwZNyA>@sUnNt^\}G0~1MmV ]{&ةvFm;k}I/)78 +g]5f8(T bvU XrDgY]ƛvzi+<ݬz,Xs{ϵeRYr*L'@']ZYy`0H0cɅU\m]O+ʎwqXKⶢi̽H9;(-X u>YÉtgm9e.$dC @%Nj"wQ A0աm~f?qA^$߃\h7mk4j%<۶. =Ԟ QlDRh 3~#a̦RU٠ȣڹ2ʟ8Er[]jլd(c,3*o%ݪa:J؏'\k"y*"j[#ĶUR5m޷u)qPmLW8'ޱR0p;KTtz=-z8?aY7Ȍ %10qͲ襻-)lh@c);zƒ_l6l`ozĐ +A0gT| 4uygm(r}:/xi>k%"!hghD]O$PZBMݵ~qoI@ <7CrhKS8VpZk3z+W~`eX/"\⦧"FTW ?5N ^3RMD +v"0%GH.->F ÚSkF|e@ p옙8@<{4u,u +ǃ`Y96"R9C<ڋF×$0 V %8,((;ZdR4 +UhHxox Cw+LBU7[Tl3k] ow`00}*\,5+_UsBu4t( Rc |]وBHa7ѪR+d_Nf`9UJ-H`wuED>S*ɍ ^o&_9p~pȷͳ8c<1q3YP58l`!s!l!}!yfxfP}i`*CGj.I -HnfE.K$%XwqT$'!7iq JAw#yh #|wҿkfxMZ60k6qA* FO;[#lx,rI_or,?3+ڍ_VLb$hO1I a1$$_@6< ?L]5A9g@P#p%} 68JI&A"jwuֈ"q \|lȎY1Kk t 3/AZE궖 An3V4( + +fcͲ隣q:w|". rGJF[0 ᧡$c QyY|˙5Iﷺ=$kj DdfBLU +ZcMN o Nl0],Ώ8q /mF!P+9|C,w9 ^ 0}L,( x`?,Yxqy܁+F!Bu (}oL*>Ҡxpbah7Z(32f_gt*=ܑxlb@jy\x:;&ǒ#, +4eQDY؉l4(z7ەP9 ѯ3|!%| d ŻbrmPޮ~8`$s*#@f3ږ)ncn|3% aY;N> NO|PIRp>]jύtY@3<=_Ԣ_߽| q g//|"Y7vCbvfĽr( Sjn)險j9t8!`?c|)  +ٟ< w`˪Byp)mh Yr>O7OKk?( ĩRpe Tˠ-qzrbwc6ʓQEaQڝ1Y%2c5jy̍<Œk6q]HW@y؇htzy:kY@-U{=9}_|Kݗt{@9{e@Sb>MY!(^s"T +z642ڋCSuMQ:~ ++Yp i:'#Ѓ< +~~ןhyI8ta$a-1mѤee hG en +(:YD0@`6sTBKopgs/{X|bԮ1 -I2Hzxh֨ MroSl @Yt|$H&@*M˅~6kMlkzsFʆL/fHԓC}f % +K&s*_VF g|aw`cjsž̆~BqĂFsQ65v;Ж/BП%E i0RB/mT9=|wfE;?NMBSdYNS_Hb1F8M(J%9RбZN(tU+J0A&y +t{Av)@~b-; euJnkn|}nv7 s")F) + +wϷ=RtM"5Ƹ`t?[n;=)eI}?ߎy3Ͼ Ee<[K,޷n +> endobj +3022 0 obj << +/D [3020 0 R /XYZ 85.039 781.388 null] +>> endobj +842 0 obj << +/D [3020 0 R /XYZ 85.039 651.216 null] +>> endobj +3023 0 obj << +/D [3020 0 R /XYZ 85.039 630.626 null] +>> endobj +846 0 obj << +/D [3020 0 R /XYZ 85.039 400.898 null] +>> endobj +3024 0 obj << +/D [3020 0 R /XYZ 85.039 378.183 null] +>> endobj +850 0 obj << +/D [3020 0 R /XYZ 85.039 270.194 null] +>> endobj +3025 0 obj << +/D [3020 0 R /XYZ 85.039 246.212 null] +>> endobj +3019 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F56 1642 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3028 0 obj << +/Length 3344 +/Filter /FlateDecode +>> +stream +xڵr6_5θM_6V6iK %$=7xwd&sùj?5?,W~,`L F0 Mpi8R? ْPf_˿_Ϯޏ'Qy*Ǔ,˽~~]0 a]^}! DyoadzC$4B2~?`J< h`j:m$8vGjI?'QylV $xSla='?A$N9T^lPr`#*F -n6tS` z3rCҢϧPt;r߽c³ЏC%zugGq]/ۭ&0dPSڴ^jkd`^]횹zkyh5K4I pA|R[WUѴ`fq9ʏ(-G}&{'@噿 +Fk+@昫ț˔UVAn@p,Vq{5G`\1G<4 :ox|B=9~, /f%y֪?3 +?B<#@w%K)#9$+;Rd)Ne%;+v$KQEZԯAP aQw]Djb2S'A??s[բg*H<Ғ"͂ +k +,|y<|jt`L*h/р3Cݨ>|.խqqN\hcdD.2``Jٷ@GLPR'H֕2EUSw^$ciEdF){$cQkc󂁵8&5Cu lh#-<'ZҩN9ykt9c-36.H0HsUVw"ԝ'^$K@%A1 q5֤B–I`\|akw@K"-ҨeB| p Ui0 6lo070sl:Z1&ys6NC98j;t4[S5E"#/⠙ u˙)NtL)oa$F&qyH)殆YAEl9]qtà]]vpbBݦ GqxozCE1 w C;gqIS!< +_rSW^kp3a[*zA |:"zS%@:c<9 [@j3 ZL3I:Eo L@ov!¨7xf]mG'N̅ :VP͸9=L6^0 "P,-za.mH^Z:S|f]ڧRcbuz={JDݟJYach.tiuQƼ5nKA8؜J1bppFS*{ 1BHG"endstream +endobj +3027 0 obj << +/Type /Page +/Contents 3028 0 R +/Resources 3026 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3018 0 R +>> endobj +3029 0 obj << +/D [3027 0 R /XYZ 85.039 781.388 null] +>> endobj +854 0 obj << +/D [3027 0 R /XYZ 85.039 462.134 null] +>> endobj +3030 0 obj << +/D [3027 0 R /XYZ 85.039 440.933 null] +>> endobj +3031 0 obj << +/D [3027 0 R /XYZ 85.039 395.802 null] +>> endobj +3032 0 obj << +/D [3027 0 R /XYZ 85.039 346.794 null] +>> endobj +3033 0 obj << +/D [3027 0 R /XYZ 85.039 310.73 null] +>> endobj +3034 0 obj << +/D [3027 0 R /XYZ 85.039 274.665 null] +>> endobj +3026 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3037 0 obj << +/Length 3162 +/Filter /FlateDecode +>> +stream +xZYsF~ׯ[1(-y-zl  MR"st}@̣?Ff$0Mg›mh兯3q8зˋ`{neOYvz|nwHԹOwo;m̃Թ}Dqׯ y^,xp0C_ٚ8s,}Y6/L @ELV9$hN`x0(nGL>dUё~H'!{ ,pӒz8#Ab7>(>|3Y͜UϾkUOG3|EΛ;[8Hل` yI޺2v:_`;XIhhWMYGٛemT~aы$ÔJf"V"6cCVEniZ]ڝiGe#y7l6$8&_]_ +{Uڻ7HH/Hh#~t޲V؎u +A+.pM!C<:be-j)PlM ؑn+N'ۉvf.mIiv0ugt_󫞑%C`\ȫjKH .;lE72Tuo]'(ch |=a_NnGxkk\:_O8s|uNc\b7#У{ױ}WrA,$,)df\ak/$;Fo6mrx:cù"iDE+n)55^Ab3AXƶ{lfP?BhѺkPξ󾄣eV2XiŤF/ZQ.ΜFȱ@(kؘ794dyAL K6q?,|j>Q5B@׮ _u]O^A@rɩzHOC/a#}z )7ju##40bΫ%Z½#!}1HB Aʡm@mYBvEGLԠ@Y"FkzH0K_%t?,VԺ!_C4H9&/Dԅ{e2ai(t׺{nG.qؘ) HbS ]G{:EK6q;PbT)qdK{ʐ`F)EӵgZˣSVV2o$88I T[ӱZDt\-sHC&İoL1MFƙ׵%'a1 iU)5"I8kӾ +i궇9D|gZ# +@Ca@4'Ɛ-zi/Ymv"W.>N0 Gz 6n|)hVn3BB <_OsX(˫ As/a{ޱt6,]\ۺBٙk(HG~hjDY-,η8RP x>؁ W~Db]I1O72dp~s0frW''x'yW>1mefiE7cv.G_#2R`<` f}`I=(S'ݜi喍 CqXxUGo:r=B]mI Μ1~z41#0z?Bx{5xR͏w%(jeA2lLl[i* ~ˑJუuLfMIma=}.thvi!.&\uzN?-z?%a,FZϛoc>%zBendstream +endobj +3036 0 obj << +/Type /Page +/Contents 3037 0 R +/Resources 3035 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3018 0 R +>> endobj +3038 0 obj << +/D [3036 0 R /XYZ 85.039 781.388 null] +>> endobj +858 0 obj << +/D [3036 0 R /XYZ 85.039 625.193 null] +>> endobj +3039 0 obj << +/D [3036 0 R /XYZ 85.039 599.048 null] +>> endobj +862 0 obj << +/D [3036 0 R /XYZ 85.039 117.402 null] +>> endobj +3040 0 obj << +/D [3036 0 R /XYZ 85.039 95.541 null] +>> endobj +3035 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3043 0 obj << +/Length 2713 +/Filter /FlateDecode +>> +stream +xڽZYoH~"7d6q`13HɽH.Iţ[Wd"qQ]]WE38?Ekq<[mϜfޜ™) _Bo:v$嚖,߭ů7˫s-7Q[{ƹ[Ň%(~xvq>wWй=srD\*3ˀO#ML(_?SxNx׉Ε^ ߱Xv-{VWeΝ]Ko={+|`[lUkhv|Zm3%rf\kQmU18~\}Һ3*v姖Os+2EF$ +5?:(aUv{E[uW:vYU3:- +XҢz'"pnF$OnxT;Y3}OL4.t*>Ґ2\؜͟ 8z6#;m*Wmh*nmoGj1Uz;4!6OػiGxՙ {7_4XSo(NoBy^clQTh@w+]R(f*+YΘOnLpp+Ca4e:C䤢}̣E~OQy̵_D 2WJlԐ|+qD ÍkwNjYؐ봑)rVk"Ji@}x}'C< v?ZĶa xBsRmы91ʸᏬ* -e*Fk5.?aE~-TgyWa4X-}JI,a˗<%Ţ<<5c5S -u4Tm]E$xh8)p05_,wn<<.q`šl+OR΃fބ⍭O vxbaSZr] uy!fZyȞ.T ˅X/]9R^o=][iЍKE5Q3l {QJBm+:FAL.tйI1(>ͱWpE$ -02C08u9Q? \\9?/WtHWA4aH֤tڇ ?LGԿ{'hr_5(fkηZ endstream -endobj -1670 0 obj<>/XObject<>>>>>endobj -1671 0 obj<>stream -xWn8}W ] 4e;؇-} %"]~!)[v <Ħș9g?r/1M~P~*ȳNdS~9_GKΆohXSE6A7fb<aBKlPE8[[~]L a>NsA”*R#sd+ۨ're~ o5tghԚ#z#UVz|L]SV?%LhI n 1}e%;G` !oiGUJ;$@\n3ɘl ~&'GUH<4 ->Rl0(`JY()¶!(HGh%[ۦ<\ -/1WH`(}1 ™mXV3j ႀ0hroyshpy׎Xl`&9Vj@ u -n -6 eMGe[5b>r|̹ڒ0ֲX -\)*0,|5ԑU5wKjM)Qf|tnE9פ2U#o# -Cƶ%Y#R(ӡZꌏw= -/ -:O*Ph,DNx(Gn&}U>+T -Gh+2Iy#M3`RV>.RD'$展Ia7r)cGY 3J_ -GTQjZG a' `:@^H u3N6ZI +1,j9bWʶFkӨnJs>QƯ 0 ʜ݇qetrcFgZuȐ|c|zxF%-Тad()l]c\Wb`xt+(yQ|w`l1@4ifIƂZ] *M}1%$ җ16DzyLxFl*KۈEcM㩅ҧ-J79Uuyy^@* -zW|&IHnsK!cjR45,r,Ak@/d7?''t/ue\Í; En.%1~ҢM+6dE /@ mh*S趔kݥ73ͻ{pe;6XÐ:*U״6yD|} z s~Cl ܟѱT d۶m$~߁ekvk4}|R9צ yD"3fCm2%7Nb^dWS&ɘ~};wendstream -endobj -1672 0 obj<>/XObject<>>>>>endobj -1673 0 obj<>stream -xX]o6}ϯ@14j#G P`R{+"eD\Re'vWذ(\{o'S.gtvAiy򍦗,irEo|70=>]o&^\ფI2LhRZR73 NUM5TɄF n]kR' ¬|CyRImkZ.wN\뗼m+Ga(xL#XB6V.kJ%Eik\"ɶɻ~XGN>s|r-l:rN͍o4̌f\E(3EaֺZze]ߠښ%YU"Udc0 {ӧPWKO4uӜ`m\Jy0VX -tjqE=C:V ikʚuC pt1p -\=;{'Q.6̐TUNq&kTM(/ܞ KhkϮ1PR@}qaRQ;5~w^(f $9x2kt{2/&jUI|I|2ͥB*tƴ@ߎUHn,*vXFZZ"MWe%dAȩMCCh(5e`*ن#CBr#i4b OTE*҅+2\طR&]=(ȡ 2kW}k!g)k&Mn,?CR{kwt4'{hLx3 v!uPƞ>>gϭPƵA"+#U!6i&cT9z0;ЛFm!,=%2hSC+bC~KxYTjU pFahU>=`gvh-t<9*6aA2څ$Q0LQyK8QIZM:;[7cIxjj]7 "."ԃhq4_uV«ALe2?✩ԃŤH@CR&ڕ9a1|WZbzWy9@"SDWC ōJ=6mD|aBwUowbGxpУ;^&fC*yFPJ +a e**Z,uLAsdp-ޯښZ/n H GjS_\'䢉eD5M(A?*Y+ - {kCި&7ғp{1T_:og@t ֨᜗{t Ȁ7 <@ -1/3Sf2dϱ*~P#e"0J@Z H+~<&\yZ lX¯uo:m?ϓ~Aׅnt} -Y~bcvzqLht9NBK PJSd]W[Q &e8xdHendstream -endobj -1674 0 obj<>/XObject<<>>>>/Annots 881 0 R>>endobj -1675 0 obj<>stream -xVMo6W̭3e{KSlk{ PmqW"U}#ɍb"͛7o(=)_L˄Ҍze*R):tJ,  :Tie@)N6*N5%{nn:y1l-VêZה+;˻kX^Ų*i6_nqNqL%HB,NvTu q5K Qt!ViiDГ}TA6w=%kVR!$ZF::BeA/)C|(mצ'{>|ѕ5md^x{}z߯eUs$MAqH/We{m^ -%ȪA+0gI998S-<*@\^xBMz+KCp>me7mo/w$O8{t}MS }vyY:'Qu9S)_!Vҁ~c%Wi -eW?xq:wCM4S9Z~e*s-kC( + 0IBF":MpSgk„ 9ٽ έ( el3} v ީ w[6G̬FQG4|טtϛݏIH[Y%s \KطMc]Z(1ٌ8[/w%6UP"OpS0nTalXҶ $s۲0x^y=G3_Y+AUaI l!,O(-kW - RZؘ"^EKb;|O`(N8߉$FBaݹ tO?R0<ٖEF)k[4]9~knĤVy)qט#U(>?R^^_^<">}ȇow^ WtžJ)MSe qC˃l޲C{.!eoy" $9e7c/גendstream -endobj -1676 0 obj<>/XObject<<>>>>>>endobj -1677 0 obj<>stream -xVn6}Wc%K)E^ -q-EAS]ԒT}ϐ%m Q9&8ʠ!a*z;'yJE18ٜhׂ&fx}Y^.FqO{TݡBt{I V_z%iTLRBJ=9qR9 -ړВY9OiEۋ̜25m=T(ɒgWy4;D͆8<2t؞ZxV9y;:xߐ[ON8\d*hPXR('05Ш=ޡ 20N`-G%|VzPQS" yF8MQVRH!au‰V11;XrKr6kdl6_SVXmF:}Ȯ^Taklkz~a¢u4JF%ΘkBߟts 1}_A==9ƕW"u7q8G7LOp;#s(8 -=TUNQNj* OwJZQeeF1k9g7ՠDR0) ]͏XtR1!,Gy,,˲Y.U6FqhS`_#ѯC0m4OyPt!LZHO7 n'-D0tH"NJaA,Y FNn}4CL 50a)VFC9 `tLa?يdiiytln6nLq ==pO)|HsRCսtwS| Uk:_dY b2Z]rÍ'Lendstream -endobj -1678 0 obj<>/XObject<<>>>>/Annots 886 0 R>>endobj -1679 0 obj<>stream -xVMo8WmS -)ܒM.@@KtD"$e{߾o(q\ -mJ$ͼG3JhOBf4SHd>8)Zʼn4[I60.ϗ?F)bF FI*攧P~3/O ޸g.%'X!|A=NiQ=mQG,?$闏]KmO[vWPUIl36OTȺR6AB!)ixBvIh+X ,ɮ`Pi@ aK Nk[ؓmƟ){) K+?}Νj5 -ψnntxBN຿W-lWTg^7xz *cd,7DQAY?رq``18$C7%ŽճeL3^6K ~?MGc2yֺ#(rQ t-lJX[ R d)G*#u*o~ P\Cd`׈N\ml!=cz| f'k㷦Ƭ|Ga\v1+pq Vĸ8~xNUdlDr[[ UvQnRV~ME[ҵ}rctQńah%Cљ|\r)˱5x-ڤtLṗ2qgNd|tyA}Dҕ-:vX1Mx'YFs=nendstream -endobj -1680 0 obj<>/XObject<<>>>>/Annots 889 0 R>>endobj -1681 0 obj<>stream -xeTKO@W8lb 7PKUTJҪ.{/ػfq_oM@Qěx3cf_ MIhtAY= /g8x,Scx2H"l%fTSHugi`|;$MԋՒ6yxB\Zze4$)^ncousMJ6y%sڱf2jeGސ*R-k-_l%Sypӹj4vS;Y@"cwRJa(-[<ΰ#2b<^9gt6+WTZJBzmvf?OmiU)eAAbG)ƷQ,4y#&%h2c>]Q}s5m+ZK'PxŜrԇK S jh[:nBy)_k1z몧 !c82ʼn\}, 3eՔ,B[6*}EȔCG_Y]hccIwo/Bܨ8(!Qa]K=DvYS`p$ d)IfyF'X]h&+0tO} ~  ֮endstream -endobj -1682 0 obj<>/XObject<<>>>>/Annots 896 0 R>>endobj -1683 0 obj<>stream -xVM6W CZnM&hEPt{$b".IR%"@ ̼7(ƴNh͢~8ZQEyh?Jz]}Vq:LֳhNu+%w(iwEd֟.;Z,p-{_|zӅӟ>lG7;Jfj}KC/u!NJjT'AUf;GouF9mT)_l?f4M2~<['+rFJ5=*lu83R#Bѻ)]`@Zd 0{kCov>\Z$\IQ[; 0z2QQuN22s(xupXi,I %2ա8[;dՍ;t'm>#Qdi /ikGJRl5<HR%`D PRQ:.h6TόDNΜt7 _z[(KR ->%q^G>S%BՒ SqH2+B\SjPl, -U2d-Ri*,zW_P7\G' -~ }mi:ieݠǤZgFn}_ fTpNh3/5^RK0%_o&m]I -B<{ƶJ#F~H5?uCq7L$~C {8(Mg iGtqޑWDw?3wgJu2 -j ? ĐEu(%?m"# -%^?y|/[&OO$k0^=D TΪvn#PHW"Ac -QW`¾ďhd JӏNE(:A!gEA0}/t:cQY~Pubx4l6V#K5?^P@жj7zZjiLFf3n,@[HKύYēqW ߃AOT??cz2s?h8T9h+jn`ɬ|&҅~87N]U.Hk? tBu$ 1BԎaZ 'vpp?Ӹ=/*Bxq4 ӮQkksZ/geMSK_ʽg+/zIu59лPixdB7e5kAJY^JRcm*ǯDWEMƳ8gTc>/XObject<<>>>>>>endobj -1685 0 obj<>stream -xuAs01GҔ[;N/\JJ2>&mi -Ì-?g -MhRgxAyKZ+tRՑ7}xǚ}g+JXvԛ:- ]zzA7ق4]9:2.IkH -Mtts>/XObject<>>>>>endobj -1687 0 obj<>stream -xWoH~_1D - poihtHr=xYbvM;]+T|ӰG+Jg)FhD=<4 p_7F]ǣhL=|?~i~ֹSKh̻xn6bKK~DS˵k7SHG*ߜ>R7-.(vo|9hJ O=ot_HEZr&+0"[%:weLq?qN+.LԔB5InEl )7wkE[qv>a0eUԦsg2[ՍQa4*|F7\hH/43k~iDqctnMFS쇽*F&-B'. s -0'V:4 -h -EI z -lvHyv2Xnߏz -Ehm^5ӟ/nA:=@9Mf:$ I^`0,MJIvs尜<̘&a~ aNc$OŭK&7)+;ɮяe=Tp" Ј`~/`hr@K8.nʼ Kh':6{-t+ 8eڭe韷09,`?CfRf9UaĕuSlF?=8W|[54>/XObject<<>>>>>>endobj -1689 0 obj<>stream -xWn8}W )P˖:)(m} -Q6tI*gH%6MD&vΜi9]i2e#ٜ+>ƏT8dvJyN ->f+Z-KK[UJ'x2k*eQnFpɭ/$47ʔ3y_<_/^h0eSr=ݔ%:uJy`KjY~gTki#D/k>A,FtH,b2](ힴ3@ -up,%%NJĤ2q*hE:{ZI2?kcp]2(2\R|1jب-lc8ވ;6@4Ωneb (2r(MZJ$9 j *NTGYRiVd!Thok\^|Tf]i4"yĜO!?) -qD^@W,251%f@:Ƹ?U%PS%ЄD1DGذIІ((bµ9]Y#BDcUB%DLJ; ̹‹ %9[ -)F>Dڠ6urz7HS(7r@:渚PX $K\ь;ivhS5>mU-ο`J[Q<KN -}J'1)eu%,ٻEvZ|Ρ@kсC?JO!pEgm6K `rskWTڞv*`8;9sYofNfK dpQbwȐOGD 3:-`sBbrj?&yr㬃7D›TF`1m/:΢~>ZYp 612餄>/XObject<<>>>>>>endobj -1691 0 obj<>stream -xWn6}W ܇zDd-iKa} Pmq#*I IɎ66Ab[Μ99Cs1)~gt3%4|7V~}1f Zody7|:u>_glћ7͒x"}>,7z 4EGW8Kh*I0T|)IiQKpj2;]Fk؄UШ\TՁJ铴d6d52W[jG1)]ͮ9Gߚ2{>һ"4ǔ~~bWib>s2+iT 'U!|>˖Rx9KIJ~c)1 тg$ 켖i\ǎC4*DC{7JgRf?iTywba/=jOn^Ə9r~e -*6)s{cLۯ=95\㌽mܿ3p*ʿlNk$)̖Ie^ -iDգAUC%D*΅.&(6[ ]IƔEאeԄҴUAIxYF!} -[8%:3:qQ34i5buO̵HV突d!xTzGFChg= YAR=BJt:yDAWP}&6>|R-h7Չ[OJop޶s+99^RGU1KbfҧC~Z_H7}Uh΀Ifu|:y.ǁV!Y-e6Ԉ6^`_afN>=nn2N*!.s oC.m6  +5s3PCn2Mc 0li8MZ&3< x1$blafԈಏ?R7d,b#q70t1J{RK]GcS@^EQC+?{εzI(b#b P1/V08}I_:/WaIZ1pu:vP5yK4H;7FJZ^9oḶ &y`yA1mA~` Bs}}06{MO*Ӻ$a̔@ A>o"Fnm(4lF]0ΟyF?>8,JiQKw&ϹlI"fX )}qRѱ^0y8DajV ;Аh V7 Sa3hx,J!<Kgn:PsrI;_F/1{c.T+<PAh HܓOj}tt -q.87}Dv\\cdO -&+៹\SF7p '"apȮaA5][z|+,AqŋAwAM>[v{Xjݧ;jMf0w [pu3omjlvEl1g/8 kKendstream -endobj -1692 0 obj<>/XObject<<>>>>>>endobj -1693 0 obj<>stream -xX]S}WtlmXnnu] \l*yFf鞑m&U{|8}t4!xLYy0B'gx=iyp1?84ič^ӃͳCj}.8揮TiɅwxhc }H?{WW? 4+tNWREA.rK?@m}f{\:+ -vL) -emj~f6]6?aCEVdž :+GNh8l( ԓHah.VQ@J<*z-8' U&&pϺO5h,= 1hxCDeT4ڬQ-™UWԱ$Ƣ^EicP\#mrHhBDǛ* -.v|\f1qM TyuD1@S匍LP,M&IuqUd3,DMYwA7zry4q^gruʻg|8sZ1BK&*tF_ыh r]ixQ kb%]z6iO*+ď{%VH-⠍`v!(q4Ǥ}@%i|@vr8J-md(Vj (R w*m]jo,=z۾Cn k sJǧטM!t -cX:LŇȌ5!O b;zaC 8is@uδA3S$#ǤٕޙnӊEz5~"x,о$B"`VVZOe'C6 @05 ܄rrp١[wVޔʿ"}QPxgKą Q+}/G{r:f7X;n馐 -zhZO*B05(>x -S#5Hm - r˓A1K -%d%uV7$Bu3xkE}v {m) t\%"n jd-T+}]Kw^)YkoE ?+>DV 쎚=CE4 -UJ ی7<U/^I:amQRհ]>sj&80^@ aIKM77޽u&-]wb:mLvfT -BbQ]d1>Q! F4 -LC4T]DVdq0#ڋ%B&u ReX桊X@ذp=6aܩ KVv+сRk  DQ vQKxy@.`"4o!~Y_oȿld3@d@e11hTcStqdJ`,09 k;Q=Y$O+"?fI6@~ʗQߦ̲O<8E\#["€UJ.9ஜu -ӮbI-4X뱉'/I_P֖kN)W7TՑIw{DHA^bs]G[D,}nEi"KһRe{$GXAh֋Z{¬0cO ը]'E&0FAȜwل8-4lkn^lt#*rp GKeP>(ڲn3JxVj&n#mYjTO&$$&ԋ};;=t> 1OOΧt2,6 盽tw:߯Ogo# -O?XOendstream -endobj -1694 0 obj<>/XObject<<>>>>>>endobj -1695 0 obj<>stream -xXko6_q|Iص,Ma@f qX[Q@@KTE"UJKʎAڠ@+qιވч1PV C: =_+ػH_hDI#'( d^UoO, H #M#-*Iʑ䗒2-!9C"ҙh*yljzVeI2)CZ*pPi6% ?:Ł6A|@ -m+@8iI9(ARXyi*#Sg5d'r;J._$ʒQ) H6bi dN= %E; ʯz>Zd4W\/DFibܠtOdN*%;?f^&{ӸN&<[:H&drp1M?Og$M_hW?'4$oc8 3Pjwt44!j,Ȱb:\K TiۉBu3V#f -jń3QuPg-[+҃,}GSU5mv6NuȻcXANT5HVIN 4;,9?"wwk7NEpqZlhTޚ+ܭxY RseQ)yq`/IY*q)SAZ9?*FhyeWެ)9juξ\pbl$,nݒNANTpcuUգ\1[NiںOSr^Vi5XUךIWmJRJTVI{]6 ۽H[,+@~?Y$7:/ -N+'|^ӝ5C te;j3!.>'Ƹ1${ /endstream -endobj -1696 0 obj<>/XObject<<>>>>>>endobj -1697 0 obj<>stream -xWmOHί$E#U'Y6lwͮ 3k;o{wggyA:yC҃NCAkHs|JZtطw:8hv蒂^CLPSSCN6,%]L1WwqzYތ$1oIG&ӛq]\RrCsIOIKi[tW~9WDtnQ$tl4"Q8I0S+ 6ӭnuB*'Š(2t.(M2r4_5](re&;ˌH%[z) RF~`Hc0k w˃>LFj"AKN")&cA>J|_&'E4@. -[3̂=Gj{.>7ѴNNs_TT129!:— 8|8aHO1G a39i_ >LV$n+cYp -öD"qu˖g;C#Ld*1J&м aDEXIc}|5]ѴNs$ua"΅=Uh.xEdUf+rz=Z;qmVězvlr &87j]ƍCXT] >%2/LVIbY2@pC` --^JࡴƿA πD 4s ~q/5y,g3lmP]Qw#X3;jhg&^2sF*y)OOj7b_iq}H1?ʭ8k^<=q 4Ԕ <TXNbY[nQϧqԝr$딌䗂 BaPT+5tRwo(kP)^YK%W'0Hfr'Ew> ^fWW`'DKv~z6^g=T&tg|t}aendstream -endobj -1698 0 obj<>/XObject<<>>>>>>endobj -1699 0 obj<>stream -xRN0+1y H=DP"!n촩 n˒ٝ7'O'8DđW|x8dLnP8̹ -dLྏ,w3\Ej)j,^F5A\z^a'QR )o 6T$뺦Z2[r\V]ث^,&.N40n*9/э&XK䣬B[$>Yo ;?X߯UbhT%MF5Q@Y39 8-W!"Z5jy:}M[輫T݊Եez4^ YpfqQHI 6v9 Mendstream -endobj -1700 0 obj<>/XObject<>>>>>endobj -1701 0 obj<>stream -xWn8}W[SK.[l[7E ([TI^J(-kQ3gΜ8%LfJkJYrK|הM2GD?MWyjL/ƏhzI\2#D7BՍ4'TmtF+5KAU+~2\@$/7Fow+sLW7W^>ߓCLRTPքV;&-(-MTYRi+Mh8TX -sD.&1T"yS - bFB5PULsSjR6;m(0/@-gB{sm4Hpσ!Hm@"G@b5rGj@9d -C2D0tp6 -pSY׫+CBͺ1r ^. -rQ©r7:J 0B\2sGvzY6_ „]LtQ@_wf 5 -0L ?}y!h鹏kNf[j\l7dwY>$ƃpY)^WшfI2n\qSjv4eCRasQuq ${(:=*ohycJ*5i N"]o.]mU&Mr28x[$79]qUdĄ1z[#Tm,ŶlwJ;`a!kkA:P+Nj'eqͺ$%\ŕ,ݚAsӄԛCY%QdQu-H02 *v7vԷP-Ҁ%Hk`q|K Af!ϖ<[F4LgX>bF#= -= -JYab|sdK[AQε~M /GpmItA%)Ce-<`($e%V"GBjl oi#Z$,H (svW k峒74;RQ-}o7|4 [%4^N+La'}wd#Zp]<JyYbBSޕd.Mh6/s䊵#ٻl0ڳ+?g^h':GVE.],|!3D @QۍΊCõ;; -Ja>Ի2c0'R;mHQO,V-y+5:lLpVY|[KqRdߪ2G,?ӱQƏza6TnJ`K#+'0 -(UDdܱꙷe7At.Bƽ4A3ƂBqve5{3'v$7v*ຂLnZaխֲb622y.;B{񋃠Uwhn|JmDHtZ_ -PqoK409M7]60?g_Ebendstream -endobj -1702 0 obj<>/XObject<<>>>>>>endobj -1703 0 obj<>stream -xW]oF|X2mJ,g;n6yPȣt1cxT -ͤM;ȻIHS&,dv#^|KZ&8k: i9?e4Mq@ϥ]:QΦuelf&b9;]Sr6v/mBV紵N4=WJ&ȳ5%&մ7iJ[t5U^p>Gв8/@ k}~gbUN hM tDf2 rD͐Q%u nI&,Ut%*Mׇßz^.\mpg5|Uy, PqE9FI*ҡBa0wf0F#U# 8 7P7]r&6ƣU:'ف,SU-6:Zn3":b`8tcwA1LU wY `}A.k󸠏K#.Zf.|o--TV7uԬjZ^2 o7N,@CnPDX hޤ$RNZЎ)S9B"2ા7gE2hD a1Q/X^-}5S/N4/s,\ -n5VTf]"Y ]lX\hWm%Hֱ VVH/p1wCu)7n/EjWW$FǽHE s'H>^uX7^r:xSCt*$Gn\dN'Y<]TCIl c - bBH_B>k k 8׶n`VP–K]&R`:ϗ5$V(|œ/ij<9-upEYkrdP>ѪB"4n=I-M rq%ݞDP Q3BJ[Cfo}GB@NnbrpGG4yu_*n{O_Hab^*^+ww0"J'S4CiD@39qLč Ǘˬsh>%z0v:Yg-fl?r}6t├ƚPԛidAiqLהwiT"cӭy"~@Fe)h竓c;E{(b=B|b4ds8׫ӲBmȫyǓk~7f@nQRCt\|{e,WI/eV?BlH4(HFTP|{nH!cb'0ʻ80w>~u._ʘFb~o}-_ vμBc29R& ϝwX`0hM3*V씖_$LE0DU w/LC/Q<{(` 1H I&AGΰT =p˳-W+_?㍟=σsjS׵O7-|m>]3k&p/D~7w63LR&pzy|ӝLgb\, '3>~y?nendstream -endobj -1704 0 obj<>/XObject<<>>>>>>endobj -1705 0 obj<>stream -xX[OH~W7@M8J+K U{B8eŏq5̹|; R:hL`r>/gi ώhx[ߵ.uݺ꧃ B[+&zVJ wz}56AeGx3ԷOp,L~?BNLohh[]l)>$7l.6lY:~;'y˵o4 -~>EO/ivpjzpK>4i9c.ti|$=y ==hpL.KYJSxNjnv5} i$JmYCJ<ƚBDGɐ/BҐ.I^0įO͋QEBKIs]KYZ\ -K(mՍRQIvq ->ZM3Itԕ3f F- )`O8kMoG`kJttKPv ʓJ ~LtQ+E+@Loc%SG2mOAP#XbOU` Nn^FEWM“89П lc5~,@<:W$Az8=" D0Q$h[)hk糴x,Qt}|*$DЙ(,>ʪ.xr(frjH_Di#3fXhRׁpAoq@@ƭd9hdbc*sBl 7^;N23q"ێ(!I*I j439=I @:CWyd\d0ڑR1OD2^ T(3-M賮:&X+AG_5/Z6ecA$(gd>zn>9cJvѨ\r>]JYaC*lǞAC/J7a CLfFEDQkm$v/ks kѳe .j}A:,TdD< -<}َ>iv>'E -2C7>2 E>-g ^-^=qvC8.4}qzʵH -4 )}ֳVz5:w]ls1Fľ~ cgt42[TTZf,&ntK1Բz 1=q|0ɂtM[}ۛN~ u>Z8oT?Bttm;a*)ܘKxFVĐpg&&O=ϯ'Q`E J>/XObject<<>>>>>>endobj -1707 0 obj<>stream -xMo6s [Gq{G[^DGdVd}!)hMȔDμq" -uLɌh]^Qf75mr -0 i].3AwvIR=k24k5]CZJ:ڈv54dDUi(RC\,oBFICnvRiBZȼGc!j 4{DTOjCQ2/B -!IȬ, Mϥ)Xe7Wӝ0E}l1AsЦIYqĝ(Zeu B<`dzk<8Nw1xlTk+р"o*tM@TjQR^!~\|6߀{u605Žw R=\)~7!4 -vߝ?V?W< v[a01S׍ rϹ5Dhpui+{]̈́Nm#?ݏa7W}smr>qobX'+댷m`}m>؏7ߗCH+5R-KEm M:.>]kRiژBե> -Z:41\0OmC Q/Et fK$0Ϫ~oPT](ÁHK %6c[go%+ k)Rϭw;11$ 5`H]&4UCVeYSU4v}L?8LSf+816f#9p.ϘV]chB1BiL-+%H̝*x^2KNtZ@6~ȧY(h!4/6aP;Lo`e4>s ]]U*wo"'y OhP2m)ebxLvgE؋)}ܖUcm>jĶbUJyr@^*M-Ums@cc,c\XA?$|~W:m5!\^VsfA8OpAcqO"2\qҞ8u3J~Jp]*_U5||Wy0чlF<3endstream -endobj -1708 0 obj<>/XObject<<>>>>>>endobj -1709 0 obj<>stream -xW]oF|X%Na"-v'(n-(8GwDm$LKσ&YJ'3I<4S:ŏT\/'tAOqLhҷO>zwy_&I#a0umm *}nTuxhԾ7"eu<- 3Os?|z -#eĴ(V -\ Su(/nS΍$v|A5JO)u.NӘVԮk@Yл A^ -lVbbY>x^59M2ۏkiL(w Lhp:ρz0i[[,ܷy[f9#;'ס1&د -A++F}/W^'2St`.0vя~I 8U@}m(#I|1kaB6\;&*\4UxU .*au0cJus]42 E U]緶GmrKn#um0Ͷ!tUJ['+k!>% -H,F@7ohL:hvOSL=k_b YklyJ:F,x"(5+sCeh$B#ʸ[ LROdb%Y[qc.#+\c{g;T YV:;31r:صoJ=YA - 1+KUfՅCŬ"B_C7="nvmә $tyc856?2 ʽ>׺;mt烢um7r.CJ " :op>Kp$㴿FֱjdpuK~8Vok}p -wy Ws:Jo|y0 ;龹jA4.a|.A.7^\J,c}qۣk'Qn&3|>/XObject<<>>>>>>endobj -1711 0 obj<>stream -xWnF}W[@%Y"`7Na4buVRbB*}쒔H) -@aF935ɐƴ:OA0t6u9}?W xO;\EWnID֒ݓYuܳX$jIi$=cHEhD -?#[p28 ky* '|7#?܃c[EtIo$i>WWB%;$ B&+N> {Vwf!?t}CW 0 rլ 46.bNs»Kb&KJO -׮B9VuIoͷG,"#8UȱHRͅE7dJ IUBbM #d̍X̀v_p{UlmH # NG`V>L\7Q:g q,PҖ5`p7Ng4M&u{yE/^+ p[99yiG8b湠~$C9V80..ss -u,-'%9!μaĂ3\EEݿ_ˍ hLmeǠJCWX\2"8; U;ZbkqYW-ʳt 8&#ċ.\D{Y4Ri"*BW++9Y$kZ6Cb>BT6[~O+*-]~4b~t5'SQ><?:&Y0(1F%܍(KPy@w5Z72 o zIVT<}d}V1 uZV59Ԁ9 -*֢j: -8hɢ\vG9JZ@z݄:5endstream -endobj -1712 0 obj<>/XObject<<>>>>/Annots 899 0 R>>endobj -1713 0 obj<>stream -xWrFW*üJReYvJ N4)-,hj -KZfj8jU Ubj|\,)<^Kv -/wKvCĤbFxzR %,הJ5HUnE Ҳ&k )tUdG( jS,Ǚ\}"\ d(ؐBŢRZ`.pkĉݻLV.]qNi/jQJO.tq*e*Z&űXZ(!CFc k.,݈i$*l}To;Ŧe#{dR-\MP^u"A*INS-eBf YX{;8UW&QaJӂ.UbU8wCrs5!3P(VꤧS`cXUx~ogrbNT)` @> ™1ͬ#o( % ֥ dqtah8;kvҁB@%DFh.Jv̕XՍԍ>-N)yA%2m%X\票;o!@Q,A! a tdn0Ӱ %guFjy!Gڍl.?ݒqDx "q0Ӂ!e> N񣏆f01-MmmŘaD ^hi1tj#DcFooR #SJcU)N-~LS8NsvGڡF#;0;V;ܺxL6_yxj[ue=q Jw1mQ2.\x˔mPi#6kAv@#,?L14wyc"a}9e|1;7@CGbo[F 1>LCYx[\1$m)10'/ u2}0\oj1Ղo{6endstream -endobj -1714 0 obj<>/XObject<<>>>>>>endobj -1715 0 obj<>stream -xW]oF}W+PHQl+Jy1]{ء;3&aWl`{=`BcLvJ7 J8r-^fp8Ʉ69,niǴIjY^>~|i4]$3y9$㨔 <)LSfTTM[)jzΟw$tFJ/WmjҦOk~z;}6G1M2` )3PRkkRZj4%)$OUMuʁ|[4t&'Pnl*R2B❬P̥"[vيޟj | j>G{Pe"*+b&W]Q^I2(4jiojkBtDZySEަv;Q׽ȗ.(IW$P]Z}0TW;z -_{XXpw3yp^>2o%&E.jE!qiKLpzg& S(g 56CUpV!s!j|[,viaщv1+t)H%uzؙt?T]izre*С|yY|)A\OKܯPFg<BJ|@\-sFw栙"Kћ()E"koS[Ը/ծA0Xy^C -gX_' +$&fCÃLCT"4y~[vz\#ͩB#%H!{3NVa|7]*JUƚW JAљ\ 6`(ٽ{Qg׏K)2G7`YL.&;뷣m` Ws{) x>8DEbDTMY=X}/])|ʤȸ#}΋c|DaeD#G*g/3 -KNjCJ'u z8R&sl;K;mvfYBEX"V7 -֭_lcAk(ܐ_@:y6I<_ ƾ/,͙qfY\!6N%[g%~!] - -KLKᘹ5E]@Dv $^abvMIquZX$~5b\3TMOc'g}~k0-0D8P%[yk Ý;i|#}hyk1$4o:'D N&;I<#"AAOu5FBdyCm@A< - NCqpMOPC"#Bs6[髆 wq>ZDӁvv sf 2ư`rcwj@0|;IH'P1fX*~/A6攌Umt?u;"JhM´AXHN/E,W'9>/XObject<<>>>>>>endobj -1717 0 obj<>stream -xUMO@W=ە$@ 0 A,*'Ww#%ɔ,B!x8h3cuE#$zSqtz>:ZiluJXb<.MKW%Wa Ss>{ֵj+ -6A I([5@Ʊ6רkӢ'ZoTtOuʘ->wn>jCI睵F)߼!.0'^C͎l߀Ł7J=ػhH=ǃ+=hUK/-zídf;=~4m -1f ·պTWpg %ӸOEbn~1yWcZ`]Wlf>/XObject<<>>>>>>endobj -1719 0 obj<>stream -xWMo7WMNᬵ,;rH0|Vrv)-]rKrpijFb}p93o{3)~J|IUw6-tjVhqs36|9/?h6A7 :ר>jOt5xctz&Oɗn_8ZtkwPEl:ή%]5&uQNR15EG) j7*h9L٨ʒz磲1 Z5Oe9OqS[' 5!Èii-~Tb~VПqj\F5U>ƭNILSaD^qil-!7`jM{7x`$YwvOި'h:wmIUVRu@w/\Ю1UCV5Hl8"J`A>&B68@!@H{!q*4zI^W}rC֭>[r īPnxW#Qϥjm.}9|rݟv=m<;(2?C.l1-Rv,P Aч$mLE^٭ +53տL_e.tq%r )3`6f -YO >-_,2]Xso3}luj }=\܎u72aLZ U4Gɓ K,$Kp HV?6KդS}mkv;hxPWսkN&$S lZlEu` ;ͳVFUgFph+4$K`r8ȼG% IdD!Ge'jO-/_Zt#X&KVXP@G#v%@ʇ1ȪF(VHܰw29a^ &N>G tc .Qlkz@?[nېh:\2}F١cGLl&ad'pBa@afz9Qx}; X!s8DȬ'IJg:6Z"&d( |'=R= Aj:u];$PFeYt7v~4.i30~t -WӘ̧IΝ''b*Z{"lS^ힷ8>/XObject<<>>>>/Annots 902 0 R>>endobj -1721 0 obj<>stream -xVn8+@S %]443qWYmH IEϹ\?Nc؀8C;(+eNz&)K|V|%<@$>}ey<]'9Քgd=|1&ʖӗoF32bM37vt- tUmHN;ՉP*CRKOvԕ")ˇj  󿷕O =z+lRgS4)nZ\#&SZ}@A(O7&Cz[SeFef 4Q=!&T s [ʝmÏ0 U$:H[gP"g8EQ0J[6ИTࠄI2(0d p|ɭR.80>+U(mᣎx ^?ҶUyxKM%$NRmYvzebֳ&"_ ~@8l*m0Q>BR*k{[WHrl v֨pЁcE/ꍥ¢wC~DF zVg_aػw$[,'$pe&)G^r:"AfSD$5Fɠ9 !b>"J؂ +ڶjE*&Yzc-EPym -_$tVI 1F^l5H3A8xh*^a "E'.FCʚCm[~O}U+[cCb/BI9-Uqȃ(`sFj!,iKEjk0u{귓G4$+ B*z=ZЪxj0;ްa_@wu 6V:E1HuCHK)<֓m -~Top- -8RJ/9|஍cb('b7~'[ ?U2Sx;zp>XTg)~C7fp>/XObject<<>>>>/Annots 905 0 R>>endobj -1723 0 obj<>stream -xW]o6|X%,]Zi"I+҇{IkTEʊΒ}(N F G";_cgL Md'_^_LdN%RI(tshZ Ւrb<[&W뻗4:GrĖētp5M Uj2yg^{˰j:K&=qB‘@4'3j!߇32Y[SV BZJMYr$)M)xMN~rvHRZUjm=9CԵљ;* 3x.мqaZӇd!d%uf p"x"efI\xRceM/RRĶXN6nf[0`qo -@lA9wE U$喪8@L^Fޮ4eHGnzNUus eн(϶hmq0v Ͷ hds x:Rjxd00S4iApR8ᡔ-9,Jr=4XX.=Zdb7L\O߾yszplUAt~(iN3TxC퀛 0擵W|mRhT 9 <g.fEFq|"ja؞ysu zb+06?kxw5KH& ꁋv̼TҧmzU7t<C}O'D]#MZVUv$spCB_|(GÝiBFh¾67-/[ƫ8^Z>*hKՎ26v =y\҇ne8G7`"$AÀ)) ]@(SI's5( ڎ9r{D -V>DPx,#|ĥʚjj>/XObject<<>>>>/Annots 908 0 R>>endobj -1725 0 obj<>stream -xTko6_q [T,ȇK.aVZ*T`ߥdS40xyṏ/=Cy"$EoȆ czR@￴ -97˞{E)DM}e2] [qF:8DwpR$U<b"PHx4q)d?w8)L&Jw j5E*r#Nв yK:Fw9/x(3?#Qu-?`+M 0?rP)14Rړ'Hzmx, |Xj3݉RUSn -a292JȓxF# x-U&c5X,\[܀U*sA|iy tX)GHjidsTZd| Њq>/XObject<<>>>>>>endobj -1727 0 obj<>stream -xm1 -A >Z8&lf,,vfAaeVB |ϓ#[0jR~GWHiȰ+ 9{2tk~ۣ>EG%-Avk.$endstream -endobj -1728 0 obj<>/XObject<<>>>>/Annots 917 0 R>>endobj -1729 0 obj<>stream -xW]o6}KS V,ٱ<-n@Wlb@_hXKFRw.)يbC$2u9^IL3i|Ii5E3|s$^/-hM%2Jz qz;S8er z||byx'vfu>12Jsdܭ1wrl5egf7:M5m2 IqPW}$)UJI~xq&kdWRQ:jr$+ [GɈ67Ƀ,uSAt}MhCLR ⽿HPkU#cOut(^u颾840TgJܝahM3@ۛo3:kSTCUpl_0RIet%Gs ׫7N[c.dA#d^L~[QZMXLVʽU-=1\o xi ҭFpf=[I£(u}zK@֙i~W4ͳpTfpFxMP3+ {-=qH8*kon"mvᯛ`UsR&)?YPuxI9ݖ*-Ovj>bZl4͉rH6 &t" -P>A4"݋8-یES҇2ygČFQ,#Yi4# mݥsXɠVB?#= <;LC8}F(")KCi[GBĜ,lKE-~ke_fai;%B\qcd.13+tv4R/PGou8Hei2nY9\4apF+l>^Oq<"D>~Cjz9r>K(އщs4rw1Q[7[__EAdWbX*0>/XObject<<>>>>/Annots 922 0 R>>endobj -1731 0 obj<>stream -xWnF|W-&u$/uun,$/$7&RK mX0̙|=&lAIu64_\j)~o;tvu/b(\t6[l;w{t]|:ép_rrr հ9M&θjIԗX2mHP#i7^ ʤrlm{,"&WHJtU:=}禌!E)]7V4׸݊j#bm.a{(κPv,)1R8RedS"R!BNZչ/a{V&SIU,c779oӋ|Ik]Fש%}ʭ,uS9#.:Շ.!mԴ7\?oڮD90BբB7T* .NAtP:n49|~^4YJa\zu[I oY҂TnZ!~^|~6_b/|M.W,4evfEOucW(3] ?h:СWIY3btfe<45z{ExH_R:.)$<єdN<3ל&⊖!OHVhH݈ŧ -ɨS#n>ףѓ݌Y,>)W-j]+ھaH"!([P'>H7 bW t>BWK )׽a3eG N8vDW Җ ҃VYvO;?58gMNQBOyҏߨv2g>/XObject<<>>>>>>endobj -1733 0 obj<>stream -xV]oF|:Uo WIkiXP @q"WE{GZѿ쑴lq?bÐ%qvgfgϓ;!'}էpf4]!<:~1W˓Wc hF삖!OO˴w#esˤ)7;>ӟ(U-yWЍ.V&Tެ8K؛Iu|JSlI9@{s|O`(2n镫+|*TLak@bB shn?̙ܚ[]3BNL#|O_A%XJ"ٔt5_<_4~dpQL2GM8Lmch낚AnOήL=L#W)3 rh<]W)H;Ѓ\hkPX;/{r%{ĠpZMm5U::'˜FBhoVhBSMPzd8mUv9 [$r^>l;iր)CJN s(7D!U΂$̟9Y#>7Գ8j]i\ 7Eir -C{QhE?:hPqqi%n!ƫ,zPe|L^M,؝<=>>3[ŎrG ocbe*wejY4cA*+f n<z'Y%h\~|lLYO:J%.RwT%_w_\I H (mXʹ(wmY(:AqG0DNv~5aq.5zG 8i:cuUt [YˋE`ܪzy1?^Р9n7 !77Wsz',uZ&]Dr}']d>/XObject<<>>>>>>endobj -1735 0 obj<>stream -xV]o6}ϯblCvNm-ƆJlT2KId0(&yy瞫o)Ii1iFE}1NƔMɄf'qʸ0Bt~dJN8%}ܟ8Z̦ 01Cdy-.4^Y }.LW%ߋoɵ;T+a|omSIڊ{E"P/g?XA[C_Nz9Q0}(nA?ma\E+lױ5yHPm#qG3!Q@)xR^;k9J "pkAX8^PGhQ,Z٨&[v5yQps<O{U:Y+#QVJ`,}U$D0NE}7PV]R&ZT>/XObject<>>>>>endobj -1737 0 obj<>stream -xVn6}WLчzXk-4h6X%:f"ZrR/q&F"r8IOJcʫN,4h</{W. }=-% gIpkhip6p: V⨛dn|:$g?NzCJS-x:YA,|Od3] -b%Y?n»[uBŚb,Zvm9Z;x&+up4Q'J#Iij].TT1;a} A U"RVF;<8q@YGߟ;%Ŏʱ:&-%nq` .^.a`Qqe5 ³ҹ BԪd #^,_uGE! -eQ"Viǟrh>%Qȼ"”[*yJB!xόxd?ky.keG17TsW *)oıR-MSW\gXwMS$S%gܪڟJ9/lTt\=(šzBϭ72odpLR-RԎ!Ir(r mAi-K_h– -h"0ASAfȃ*˸4|e]araـf5JK[ V#ay*އU#3~`%!Se6:6GPyoՎ\oh{?Nrޚ?r+CؽczPyޅJ6:'7^KI1-wee -)\q7&u4CKIs].c utheI?e'&Iө;-J,q|}"1^ -a;n!\n90"hwxDśndCanťKznerSf[-sA잶04pL*o?:kk%.L&:ն?Pw҇B{p>/XObject<<>>>>>>endobj -1739 0 obj<>stream -xWMoFW̭1 -RI/+rEnLK)}$%I $Eə73Y}5)h5EJY}5MNgɚ4e:M7W/n^|Jb5mrB)ɮߔ |Н) --aOoP`WVM6_4/7KͺD˽MipӀ5h&6>6^v鳱9|ڷWiؠ8a[&g:h@Gr7O2ZqMh.MI)RhYrj.^)tڍvhm]`On4=#̫;BYFC:(SG|s]QEɧ*D3Ԁ`.FJ-#@p$|094a[> !ިeZ.876ʪBˈ;K^\^(v:zb)%j/`(y@P:謴\qaPT|\?EC`038fzWBգĞ6**u%Š O+_s]<ڢ:F/~l AM/u!؅.`*xGQH:[,\36RЍVGfz 0CQrIqA_ Zr/1ulp I}) {XRD(n ddY5 - h2'd- }+7'>na>˘#Jv#U/_Z(}B f&2xv6? -p\Xa L(s6˩̨kϤ}gɴŮLeɺq|ྞK9 kϕH9^](wo%&)|UǍ}*ȢNNV"CIWKax-{{c ݎn/tUyaϏ^j;E짥9`WU!^yEGr𕊷xUa'^- -֠LhwVgc~%OLX<'$ 9'̤Ox>p4})Ͻ7;->/XObject<<>>>>>>endobj -1741 0 obj<>stream -xUQoF|WL*]x KEµ:pW{b/x9]ovJPp{g&_G`b:G^bb*-=U8e*||~c1/|cd9$Ǫm+KMXrOT៼~VXkroDLf#Ii*$ˊwRLD*u`gdM*HE8(A7:R;%EC<:m++*3b3UyA;pURRlB%LE,}i:њ54L+b5]T vd -B YQ2G6l zV\`*p57H'<R`kFts6.Pod#|+E~̂5M8mWZX5<[kϭt\rk[؆݇5'wI bKI@tG.^xXlWJ907lH@Ⅰ28tgʿ͗_Z5zv&L=V?A'o8B=˺}oe-mWfT;JO:q kLl#:Ä0G:Ѓ7|7z5G*mRdG=m\۽R͠EF5gg|;V^q/K/1 -ƺc(2Ld:ǘ gaTXZr<9Tv D12dʪ+r9i,H ùj -qbfcm\z$YU̞͗b~R)gG+Aendstream -endobj -1742 0 obj<>/XObject<<>>>>>>endobj -1743 0 obj<>stream -x}Vo6} 8vO].C,<D\$R%D"%w޽{ד! H'd@E2|#YIy0]FI2~}urFZH2i &]D奥eBKcبBÛտ60n;zD7ёф*dJ29U𹱥M$)H%ok*kxrǂ88N=8&LMY 6LhʴA9癫dr"'c.F1@QPޒՎ9.%^pT:$ Y?|O,#UV,%| UhkM]a듴}Ϝ -a3ZvT* -4Y8 +r?7RBLU!\?<{ l<*,<7˳f`*+Ӣ@(zq19s'gjhT8ƩX6H< #h C`g2%(m#7\QG΀2[cfY"\ yWth^fѕ̤5O-!&Yf*[F'g5OX%gj2Hڦ)AMHG<8+dέϯ"O' B/[J0PKf/')OMn-kv蚮h2EFOh+X8`gQb2ʊ \]-K0' -V]it -M'ZN,TG1ں /Tr~BLx~AWFk:]B H^Lu7ށ[l1U%:wޯb\l %D_-.ørC}4O+~٠"d`?YC 0žO'tL/Fup:V'`endstream -endobj -1744 0 obj<>/XObject<<>>>>>>endobj -1745 0 obj<>stream -xV]o6}H"ɪlC6@AKTĄ"]CJrg< %܏sMq$HiSLeS\iyIN+WstΧ=Iw" HW5[FƉ/u>/XObject<<>>>>>>endobj -1747 0 obj<>stream -xuTn0 }Wחquv6(6kLw$%Ems!_R|2ZTԌ4IE *O7튲%jUFuKT7*Nhg \yncDІM}aҺwZP<N{q+REw19;%_F7)y [b -ڳj)F C(v^, "JHЃ0>HG=2ԋӖYdxxt?6oQnc3)c#YF܄=8 $GRQ':gBI;QXRڑ@X =R;#Z&r t'1qi{K#g<~8jIZ C=@ky -N?NHd GxI'z-yCn\ =['p/ы`Ö ڭc12뻯@yϙ N0M0GvO- c0 <55=fϓ[^RWѸ,h Uq -<>|`8$|(a뼚gǮqE1Oq= ZwMT£ y3eqdztWur7Soa?m|"A$$yv8F|iyd%aUPYYӝ?qt T9|LW;e9g M=<nendstream -endobj -1748 0 obj<>/XObject<<>>>>/Annots 933 0 R>>endobj -1749 0 obj<>stream -xWn7}W bVź䥰]_)q -(+Jb%7K{\I -òKrϜ9C=~:4Ro@Y~tѠ7g4gLJߎ:dLA2I~4 #,Ω7īGɰ~i;wus~mȺ=,xnr^?mw繜o= #1\DeI"O 3'WL)JNg_O:O;JdRz/@XrBe–ʚ$n5ΰުO0t2޺6/,Kft醌]JHU@mɄrN^|9)y3ju1l%7<%ӣ2sv4>oG.cQfGKV~Cʹq]xU..h]*̲YG"}Z8ҁ $ -_8FU1^"H5ZRmO6ܬez)t$ \:J4,zCҬߴZ(j.O!ɯȽI/BζF*/! x. - ̈́~&fI#4=exnrtH(e|tΫ̃B2 :HGeEQ~(x{x -ZIb>W-=kO.CmO'Ǔ[z<~:$guwh 7\;R|ekC{O [D, Ԡy *9 F.?N~27xOmC.TeR>XF}\;A]ZAy;oFBTVpuȅNhRef=D^c!Anm kH` jc*5 -$R} yp]o ~ᒩ7ц}U40YX3i5zK*2R!)\C9>/XObject<<>>>>/Annots 942 0 R>>endobj -1751 0 obj<>stream -xWQo6~8e)PI`HZgMѤY5a%V+(~#qQtkZɻx?1M)-{1/ϒD$[A^2>x,&; 1؃8, N&_hًG'p2,ix<;6^$p1EhD|\ÁHC̆RR({YW4CmzcVic)BS (#yv45d?bt98( oݴik5kD_+EyZk }8kJ'IM+8۲6ew`rTOQvvDj袵8K"A3x]7`*kSMhEOT -Kź) 4+X(eM[Ȣ 3qR+Mtص*>,o<y>M`½ifytzKf8ZHaa2zke_t H*iO28i+wo'aV vk,0hh@-Tұ*;/SfOM`sm2&rVPB`ѮV[Asq{35Zgu;eU"268|StV2;ƞkWxCA(ih[eiV!/" q= jIviU=dB3Ljz}bǚsSִu6>i㫛𕡑eC-@|͊GoY󯀽y%t?*>M$YWorvysʑTP\OB5$!! <B6BORp]Պc -TiYT6ϨMFjZVE˚RB>7 -~> ꝳ83х&07c@r׶SZ+VH€ۻۻOtEvݙ[WDeo3eX{1bzRچl2l: !)إ^+y b|kY<5 X OT˪6GYN՘\ -}A;ڗ̞C_-hz*>tJYË.w\ݬpgpd+KO޳'vϱ9N6֑c+<nfi]#;tdݑ3ΫqAJwABߣ?&t.^n YGM}{ eU:G(3NF@YvquwT{j04PnvE ӦE}n__~ة}r;|<{D>ʼVAZu&װa1Žeh^]c 6=w^䘰 Ξ[&Kvam>נXݬ;"a!w(&DP7-Ln4$|3xS)2^YHC|'1~s8;sۆozkҶļ&RF8 0?_$Iޯ7Xendstream -endobj -1752 0 obj<>/XObject<<>>>>/Annots 945 0 R>>endobj -1753 0 obj<>stream -xWn8}W R/K -Cb;Ej,(H+Rq{DȢ#\Ϝ:R4QDaz:4w0b1G :×.7yJy*x⍚WIz@.1MGNeo%I'͒ᓡ(֐)(6yҡG;⤁FF$2RYTfV$T6$YMv+U^+ί/3r,s[+Qq4w4Ǻ"Y%1;2J쥵a^3BfޙiUi Qaۆ;k<"-H2 0EhS ^n/hzng4D%J xCΊ%|i#'w")dV0dtY @ m˅T e]S6tVW< "#"W@2rf4I*vaJ>wFuu3j0~a#v15ȲH9s?M3QmCznu \Leck :Sa2fj]^:ffEh'#@)^1 dlj76Dj&@d,2uF 0u'UfW! ίj{OPLY[!tr5BYL<]PNY0sEeL |!m EpX䞭 pVCKļQQ¢ãw˸Ҥ)RLkX_Wt1lO +F:np+C\uF|X $KC#gǖnŽ?h C^8V]ٱctGG: $Wkw9 $̮(UO=D 63催oBeنi (|ڣҳX9^7lDA92uiiz*a{U՛ -gSW񛸻x[8 y&aqm9㩍ug`؎Z]xKzL˛ŗ.a*Q1;ǤOWwW1aoY|o?w.؈1 F*'};O:{ +FA U)e-0ӢQηW!ǝ4fMÛbs\Ty&d?y:U+RbNOf %ՐFb(s`z-?w35dzë&I4S4рzR1/9h8e> nƻ5d\ڦ4}Eɐk䏇ߣ0xϾ&pXp%F܃Ds1=px5HKLnZ/8Oa!FҶk4&ov%i5hd7DzMY5[?2yh:yqF@[ڴ2`v,,jV ظno>N- + `gDŽ!QBz= +Q +mRE?tf-ƥ)Hi3tjӆ)1C5 +>+N'x7)3VW,qRxZ") $CvUtNo?ݸ_bH>z Bendstream +endobj +3042 0 obj << +/Type /Page +/Contents 3043 0 R +/Resources 3041 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3018 0 R +>> endobj +3044 0 obj << +/D [3042 0 R /XYZ 85.039 781.388 null] +>> endobj +866 0 obj << +/D [3042 0 R /XYZ 85.039 708.141 null] +>> endobj +3045 0 obj << +/D [3042 0 R /XYZ 85.039 687.147 null] +>> endobj +870 0 obj << +/D [3042 0 R /XYZ 85.039 616.511 null] +>> endobj +3046 0 obj << +/D [3042 0 R /XYZ 85.039 584.986 null] +>> endobj +3047 0 obj << +/D [3042 0 R /XYZ 85.039 551.084 null] +>> endobj +3048 0 obj << +/D [3042 0 R /XYZ 85.039 514.413 null] +>> endobj +3049 0 obj << +/D [3042 0 R /XYZ 85.039 385.306 null] +>> endobj +3050 0 obj << +/D [3042 0 R /XYZ 85.039 362.184 null] +>> endobj +3051 0 obj << +/D [3042 0 R /XYZ 85.039 339.668 null] +>> endobj +3052 0 obj << +/D [3042 0 R /XYZ 85.039 303.604 null] +>> endobj +3053 0 obj << +/D [3042 0 R /XYZ 85.039 179.477 null] +>> endobj +3054 0 obj << +/D [3042 0 R /XYZ 85.039 156.962 null] +>> endobj +3055 0 obj << +/D [3042 0 R /XYZ 85.039 106.742 null] +>> endobj +3041 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3058 0 obj << +/Length 2181 +/Filter /FlateDecode +>> +stream +xڭY[o7~ׯЋos)vۦHl<%2ef~υn5$yxxw.d4b0R4IEt,'(L +!=u02Qӹaьe4QjXc p67& +~z78 7Ѕ;U`K[uO&^;0"E0G +<#Pa&P^CyJ:/ Vp"q{Q>&i* hMPeQ(lZNBŮ_Ln'5BӋlhQlfs1i be &@afP#w3! o\[P#LHb3"gBkEa=,7TXӃd* %Jc&ҩvQ6 L*Y2hn&Ӡ> t,6Zw0P5V+\d%<;w1B$ˮrVnZGMetQ-hyaJ)D~J2+;F7 0.xdYlmӺl=wqK7Wtۺ`wm̦#ޑ@>|CG00!aoH~`zT/{v`aUƛ+nz`=7[|2ha0F,C;Tq]AN$Ձ` a_XZbm;nqsd`뒻?CCMّ`Ap6w08T]n H"x 9~tD2-4˂ņd4>A]ZA(G<7?X0 Jդv"G^!L 2h߀tqWXDtE*P2/g=_)nPE!gKl~Tq„2\8U#RTl8uJy");Iὀ T^XN[u\:k&ꃐ˜] +R܀+Jd4.8 EE'?PvMނUm6Á A`ȞQCwV|Q 1/\IxZNU>#TinNWp߻~P +.7K*%-)CAQ@iPgЮҵO+DE%b/tEWa ȩ,glW5a!"%. + \* VvXxo̗H|qˎmZb\j 7?U5xW7cL88#, +'t>\ _aXNkgN7O#Fx)[g]sp8gl0 kGG{:+ ϕ%D9`7'RjM\ i_}qG](|:GTﻺi2]Sg&V3On%q6^dY3'dVf&8%Hq+)[Bťg Iu%hr,~[ jQ x}A}+u?or %r ]0]nfyXk .dc,>2KX$|OxykBidt7n(\rhۧI\[.WhDgJ4:g9x"OozT/(.]2±!4nU0w{W(=!NY p(s1-Y %^ ΐ3s _9endstream +endobj +3057 0 obj << +/Type /Page +/Contents 3058 0 R +/Resources 3056 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3018 0 R +>> endobj +3059 0 obj << +/D [3057 0 R /XYZ 85.039 781.388 null] +>> endobj +874 0 obj << +/D [3057 0 R /XYZ 85.039 761.463 null] +>> endobj +3060 0 obj << +/D [3057 0 R /XYZ 85.039 667.044 null] +>> endobj +878 0 obj << +/D [3057 0 R /XYZ 85.039 667.044 null] +>> endobj +3061 0 obj << +/D [3057 0 R /XYZ 85.039 639.536 null] +>> endobj +882 0 obj << +/D [3057 0 R /XYZ 85.039 406.729 null] +>> endobj +3062 0 obj << +/D [3057 0 R /XYZ 85.039 385.533 null] +>> endobj +886 0 obj << +/D [3057 0 R /XYZ 85.039 343.373 null] +>> endobj +3063 0 obj << +/D [3057 0 R /XYZ 85.039 322.172 null] +>> endobj +3056 0 obj << +/Font << /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >> +/XObject << /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3066 0 obj << +/Length 2349 +/Filter /FlateDecode +>> +stream +xڵYo8W`q2P3KEzMwE%!Jr;Rm9šIp72r?9Ju:)tnGf~:nE82",NH" tNK>y?=0h$XWt<;%?U{{v~ʄ$kN/iO&(ף_ (:MFLX-n\]sf_ xbT$T+MM@$adC{n6 Z: Ä}C\V0:"4iy'97l!Go*hJB +NU'Lqq5DPD\*4Ct\"} +c+SnR{֭|m͹T]V-7+bT-qϜn*sT˥f:CEIHJ|<ё ڊی\k_# o*p3wml1 Emԝ>5gns:/Mn!zV=Sz]^e/m-b)lPV0&Z$`p4LU6ViP!eTsnQ,F PQ l'v$Bo9}WhŃCІ"VC/=s-;y(*(@ +EIOz.F=B'}6pdžkִGYэ w$H.q&$kx +QpwLh,8wE䛲/u-q{ T@R5/]ӭHƎO{7/y+ 2aƮvv-PkXl 2<D'5HBGo7$d:&lw$Fw y@edz*1T+ +phsbN"$mP +#6!!c88MPqQ(/w8Y E}^?F;[&vֆ7ԁWtaz}ꦭ17qBajqFڶ/'JzpEƚmՋupJGM?цbQW!'N(&Jy@2?`*?jX.M%!yA2ɖRM{XtvN7XΝyU1z"IhZ>}-)^g,-d˒ܸ6\!C\DdXŹ$K" ;OV.Tp j Dn=5b ގAr)[/BRC!ۿZ +NJxl55"gN5A*ɮ q.=:l;՚OíI%=_a E_5u0R{?1^ʀË}^"gKW79H\!&QbJa˹t$_={mEQvD? N.̿QוBYw+ MWV(|#ïdn.3.[.;L}V> endobj +3067 0 obj << +/D [3065 0 R /XYZ 85.039 781.388 null] +>> endobj +890 0 obj << +/D [3065 0 R /XYZ 85.039 627.355 null] +>> endobj +3068 0 obj << +/D [3065 0 R /XYZ 85.039 608.404 null] +>> endobj +894 0 obj << +/D [3065 0 R /XYZ 85.039 366.597 null] +>> endobj +3069 0 obj << +/D [3065 0 R /XYZ 85.039 345.396 null] +>> endobj +898 0 obj << +/D [3065 0 R /XYZ 85.039 239.608 null] +>> endobj +3070 0 obj << +/D [3065 0 R /XYZ 85.039 216.892 null] +>> endobj +3064 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3074 0 obj << +/Length 3062 +/Filter /FlateDecode +>> +stream +xZYoH~ +k]k'Ķ63䁖(0E*$eMR,`Q]]](]Oţ0|sV00H^?f'or$<7lI$ٻR;a\ #'¹ƔI2rnίqWywg㯳NzL|;-@NMx GJ:EIr%FNC5\YC]E*l?rLkU3 MÏUۍvfI;:6iܢ⯥+MmFFqԞ℮$DFR9ރ/}xvפe͟Jӑi;>=2[_&/6Yzcʋgf'MZsݤXneM e0b&>O%7Ḙg?'xx|sL+XVnoZ5+2+Nsh "89d GkO0$J[Mr;:u4ul;He蹾ڷzD#Y[^ wZEL˅!|>>wz|{2}~ \ 9e_+4 k#EoBTǎTNeumg^0Zs2lz[0(X'En!E #rJYl/I #peqH8MngA]4OM@8@R&,Q,Zvࢴ 5eK&$-!J gR!3Qb&j?Btp`]3]+g=KX2d=I}s(#w>f">CZh$)k_kaUXÿ6ZO0+ ) z7JhՆgs01A,q8簫EB鹁bQK@!`)p = /csQ(ݩ1 <0Bwù[<i۾r^9t!{nmaL#S)n a[YJ;*#(0~ƍ687-%ZB0jA%eHfIm@/ph\;=%tm9ZU WkNyuG^`tLvS€)bfuuML)eUn |5XA4TE,Ϲtocr޴hի綠Bx +pt1;7^,ȍq͘qմYj$?±" 1S0-ɵàh4(um{6o09֠`t] /xHBMiW +nK*m:(ic7ȪH`o i'DZ^~Y%IT9luw"wWgƥ@Ծ6[^Ti `I[4=xTnXsQwz̫!8b:b:FVCAX Ir*_4E bgU$YԸ*sb7)Ҝ&{B?u~,к-C2ǚꉴZ@ebypkL +#=T$0i@j)Xá#ƹZ~[?(6fyj:%[@dϒ:>Vi6F|*(a7>Tȕ\"L̼E + WSY'h 8j. ߞ%V*oYq)Mh W٨4+]O] SQ*8F9Lt9Q'鑩+㬑;NNAs!yV5smk;Nl_ ("Տ32V[*<.S1䍕oFX&>$ ;^v)Cj?Az_H7y<<U9%\ycARiRrz +?Ƕ$+Aendstream +endobj +3073 0 obj << +/Type /Page +/Contents 3074 0 R +/Resources 3072 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3071 0 R +>> endobj +3075 0 obj << +/D [3073 0 R /XYZ 85.039 781.388 null] +>> endobj +902 0 obj << +/D [3073 0 R /XYZ 85.039 310.691 null] +>> endobj +3076 0 obj << +/D [3073 0 R /XYZ 85.039 292.022 null] +>> endobj +906 0 obj << +/D [3073 0 R /XYZ 85.039 292.022 null] +>> endobj +3077 0 obj << +/D [3073 0 R /XYZ 85.039 271.025 null] +>> endobj +3078 0 obj << +/D [3073 0 R /XYZ 85.039 131.177 null] +>> endobj +3079 0 obj << +/D [3073 0 R /XYZ 85.039 79.598 null] +>> endobj +3072 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F38 2158 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3082 0 obj << +/Length 3723 +/Filter /FlateDecode +>> +stream +xڵZYsF~ׯEd\yJD0 X﷯ @V%*qΞ{M\&IA: d؝5pw7 +g:NW4~iwWALę8y?ÿܛe'߿↛׷sung:v2Wg>%3 det;Sa*? S5r9;)IeN#'PpȝwZ鸫\ ZW%tZ4topgX*g~:+hj.@U +ۼE>xr }95(/jٔrRLOW[lfmPʋC2:2ü0ȡ^v+aA.#Z|Jħ$߮yM$^2y_e|tV4kc4b< Upw+n{FANcv?Rn(TFq|hnͶK$rNJ +hVQ?b`0#~\b74%k&V -Nط2xTX'lZ0 &@Ex Aƚ4c@ Ѣ+K@# +tI~=dc9 l!{"4PZZoT4-X"V2߶LiBKat7C%3т"kBۙS[VA(&^\EJ,RVVYdQ%ހ)=PU|{bF;J/#j2;kN; Ca}oÂ0Z>s0` ^<N#me2IeRcɺH-inHtqo6ZpC+^2J-0f/FAI]弑 WXld6ǸO-.ZwPhWYw\u,Q1ՠ=: :-uYP!61֞ 2DznC[/uF7BgPɾlE#~Vp+8 J ,pE/ڊ0ol:4‰Yv+o5\QϹVVkS1L뇶e`|m_}X1NW} k[֗ldW`̸HT@du#:烽"` +tロ*4˼[qa; zE1;iY7|Nl + zR3h&ɢyK6R/g#1zzidn;;pv`Cf[926Ix⚓wl%BRYNi/+/ZK;.b ͠$yyz/\/>6؁Zib|V,AN%ZaOQN놛_1 KW$?{ <+C`@Q+߄p,u]ޡcE"q,S3BFUn$Bv8LSh(Iա*Ɖ^ȆjphZhpx; RP .Vٷ W,5CMҵJr@X1m !#Α!(a ebG<M%=FF҃qzӍh]hjdv)=pL+SeNqYPW+8)*Dq ?K0b?r>J7I$;ȽTcA~wv'qi 2 m+'usĖ>@7oN_6h$TUs*W[d%Os1\bᄯMy$ ڟ7 Q%Ԣ%ч$YҡkWB|̓ߍ sb/x<r e>{!19ˎQ.l ?Ld"8:DuWtǃ3: 43KT=q匿BDihH/@c⹡&dN)/K4F,0ܾaL)Y+鹽lZl7!wߜhx:HBs)|π[yɒ҃f6g}SY02Ic|dl#؂u%#v\"6O=;Mb6xuFP=0PxuWŸ)Px hS@f`D6_eXQUR<f&ScZԀmZ"!F1ej8Q~q3oHtO8FDZ8\Z%qq,#l/j]@! 3&C=* a,cH>J2]]2_"9#DtS+sPDwg0d\s=u$C$J]K +vJni%VqȀ-xxۚ`*`RxV0X#R鑒,%HcV\gP) +鞛Hh="] w0߭t>X҅ONdVz+'VRdcnN{Gґg?F[wjASX-tRZ#;\8v{a\8GQN .^4IR\u,P<@񏔅_48L_èxOn9vendstream +endobj +3081 0 obj << +/Type /Page +/Contents 3082 0 R +/Resources 3080 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3071 0 R +>> endobj +3083 0 obj << +/D [3081 0 R /XYZ 85.039 781.388 null] +>> endobj +3084 0 obj << +/D [3081 0 R /XYZ 85.039 309.34 null] +>> endobj +3085 0 obj << +/D [3081 0 R /XYZ 85.039 286.293 null] +>> endobj +3086 0 obj << +/D [3081 0 R /XYZ 85.039 200.764 null] +>> endobj +3087 0 obj << +/D [3081 0 R /XYZ 85.039 79.638 null] +>> endobj +3080 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F65 2099 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3090 0 obj << +/Length 3146 +/Filter /FlateDecode +>> +stream +xr]_⋠`i׻Jˬڤl?@$$"#ߧENٮJ6*aiێOȵU.7'| +sm'q/ww:vħGY~_o?_(,7/0nޞoq~Z1gs/>-^]-YpvB:Pʯ'?✮N[ ۍ͉k%.1ʟWaS[r%+V+/Wn]"Hz*pY=/Xپ9Y{6,g /)7 Md -wۊ8pc L$j!Ҕ7 1_ϸJkBBF?_銧|_)ox㤀5+d?08d("yѣ>D\[9+2C·r~f*sY+#i@X`@xB +?=snĐ96v$kD'tVҤS'=yl>==iEi8ܔ KEG%8Ru%vp%Xr3XS%K=W>U@$̀%$I(ӊI~ s+ͦ,lyMQݐGN(ylVinhu]'OkoYq.wquNH+\/tbr|畷g٨x +*QZ4*BU7Q%fMb:ܵiYQzHR2ƞ!)=mr!&{3l b.@w CBtډ1):୵u<0aŸ= 1AzG.||*\@…q~ <>DYbkN9-0Gu@[XO ̸PwI[Wx>]8-Zu%` ݉i ̘DV} Xm7_v][{Q==g{B梲{@WA!;l/4vB H(Mdeq(jp9ǝu\hGG#51P(F52f 'H8&ճ!Db cUًdyz}X;&M;At\ l oHC\w +b85`X3!A2a@T#׼ȈlmBL6"'Xgg w 76i%Ff4"p+z/ŋơɃo"߄ +.{WK,uz&aT[}З/ś}[._P{Qya/ߩVddn(;(NvZS%durlZ>%}*}GxLf˲'p/oپegM`%-n[@Ixxd$wo%B6.ŗ?2n wd Y.ѿ,. dЉRByVG IZHeM,HلHsYջXaX%V8B/NN[Ru):9SK2%*!XfNI-=?n܏6f=RKg,\~wJKI#vuýA#2ISÌX8 +I +m1: j[~"&5oZhMi'@ԱB8q`"?u͑"حFvVv3]~Ȓw>ZɬbO'cUukZȪrLXٜMP!݋bfy7 )^sA)=Rɾ`DY++GۺŌIWMK%tnj3.mumfqw e56or{as  6~ݡbO}pm~ P~ó2?1/HxA/^ +OmDh34c*!t?S7nԢ|T8]=V4 ov;endstream +endobj +3089 0 obj << +/Type /Page +/Contents 3090 0 R +/Resources 3088 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3071 0 R +>> endobj +3091 0 obj << +/D [3089 0 R /XYZ 85.039 781.388 null] +>> endobj +3092 0 obj << +/D [3089 0 R /XYZ 85.039 761.463 null] +>> endobj +3093 0 obj << +/D [3089 0 R /XYZ 85.039 743.296 null] +>> endobj +910 0 obj << +/D [3089 0 R /XYZ 85.039 603.826 null] +>> endobj +3094 0 obj << +/D [3089 0 R /XYZ 85.039 585.353 null] +>> endobj +914 0 obj << +/D [3089 0 R /XYZ 85.039 283.436 null] +>> endobj +3095 0 obj << +/D [3089 0 R /XYZ 85.039 262.235 null] +>> endobj +3088 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3098 0 obj << +/Length 1139 +/Filter /FlateDecode +>> +stream +xWKs8 Wjf{6NfD{؊,$~rdf&Lf"I?d1i&β``O#=D`Hb4OHA~\WU>#548 a$%Wru]5&>]h" 7P~~2\,xYpimXh?F774kρ#s OrӅ (xJ[`wiCf{o֬ᮕd".)I]Cߪl~Gゆ`'daR k%2V-K 1g@;v<:.IS눔Eӌa@egzxbR*[[17W .l km<;j#X<=|UrY1hÔ "fߖ pbR _ők{RO&\'(ȴqOLwOoY33B]#%i. w0 T^9)mJ"ڼ֩lVo~^rkO; юeX'=' r`t QYr+h4tN]&nP`躉su{akn[D J^6 +}n^CGŚC74%D +_"j[%}Eݍ-/xխ@RSa >zoZ2:#̢vcWek lj0|"ߥ;^"&r+7;Ku].wA̐:ev EǕ(J ]RI BA˖TӲGrkM=:MC_ O~'D&o]Ԗ6}Tg6{#_:$/W~i.6?vendstream +endobj +3097 0 obj << +/Type /Page +/Contents 3098 0 R +/Resources 3096 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3071 0 R +>> endobj +3099 0 obj << +/D [3097 0 R /XYZ 85.039 781.388 null] +>> endobj +3096 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3102 0 obj << +/Length 1930 +/Filter /FlateDecode +>> +stream +xkoF;K/5JpUwV9ʿ >p.>ྏ_÷a*o/9}qGƎql;<=u:TxMY} a~|sg.ѣ=:> +e,(uŠ7uU(E^ (X,)6v^]ͥu^K֖+= i (&A<+b?_3 6Ԥ))!+{}7g.I<#_26C`ܜ`< +~woBh/y>O{!%-Q9M3&wƞ]K|A뛖<2@+|Ry}U1192eIr, $?Obh2 S2:`ޝ{cegKV@E\nz dR)%a@VF\:{V*%a}Vd{V@`ߞJ0]7h{2v̜k(oFg{b[վT]wGËExe g?ǘw)[(A@ 腔>(C鸮}CZFΞ2^(B΋FLV=AX#($ ">ƍ[_"gDge}A^XGG !P9rrZfV;\ #'yW >H2Jƨz3 wM^ * S&x Sqw2^ȦuЫVΊ*R;sTqY6{8 b2sဋ:$”Id,JmA{aXɔif@  ` dLA^bmdʴ{ +vP&&V^ O<hLIpMQ d6ic>cK%3hKecfg^Č#+C,K#D~č׼lS25K*3J3%HD!FI'ˬV>5لb05dv1TuO +U]C$* RlY%iBr64hh` ?++.LQF~4G*ijFt8;?rԽem[ +_ͨpÞ?"i0&{KY[򸚚(MV2BiiGI>I9QwX6srCTCbRHs5D`9/oF.w[}ABoi,YJ_S! nendstream +endobj +3101 0 obj << +/Type /Page +/Contents 3102 0 R +/Resources 3100 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3071 0 R +>> endobj +3103 0 obj << +/D [3101 0 R /XYZ 85.039 781.388 null] +>> endobj +3100 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F41 2104 0 R /F18 2207 0 R /F15 1628 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3106 0 obj << +/Length 2902 +/Filter /FlateDecode +>> +stream +xZKsFW|XeBGn$'Wdʻ"!%Pk! ѩ[hLwZ !UQހ.x-Qte-Bنf8k: 0UlBvrf9$ cW~sH7l}P1U.%+dhfqVBcmfbWݎG.qf|DPϲ2|qeYeJm2 &1'͖8/މEj&{q#ajXY "scsYfNF+`hsHaՠΣDDH踧3 +TLnY@qi Ji7LT ϡ]:۫5r(mX+ +sWЏe "rUi|Ye}pBJ_Xykw[~Q9uNt z'So)̷欕wB6'3k7IM03asvȑ3a9"!/ڪCpEF' v=}}S,klP?npAoqM{U +(azұKG}0M̡l}6Nɻ /|uR ܿoؕZ,@7J +C" ~99VW;aZ&>B ͌LLc /"H<`y|;a_(#3qi84iX; C qҨMt9U$]]A8bKYlxJx[sXwcKߒ;ׯh>ĒFOasU|W1,0\To\p.:RT 3D.$ (v=0VtQ]3t Q%)R/R5HJgh:;ݢBFwWGЎMbq|&ݯR{G($v<U/;ޡ:{J-Y+7KRdAAQ@w#(r b뒚StFx+5,,⻮`z,)dOgBis7aG!#_ox@:|㡪 v.^|sZfOJ-ss]Z輹Ô( h[+h{c2 VX3r:4퐌dϰ21L̯ @21J+L%Õ +uA@UȻu:Ttֈ!(|A,ܚ}(rB\/r=Xeisef)\(!Vܺfz9lEx׊t88DCX4Fr?ˈEQ b:Nj^iuxFVSlendstream +endobj +3105 0 obj << +/Type /Page +/Contents 3106 0 R +/Resources 3104 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3107 0 obj << +/D [3105 0 R /XYZ 85.039 781.388 null] +>> endobj +918 0 obj << +/D [3105 0 R /XYZ 85.039 761.463 null] +>> endobj +3108 0 obj << +/D [3105 0 R /XYZ 85.039 729.511 null] +>> endobj +922 0 obj << +/D [3105 0 R /XYZ 85.039 549.916 null] +>> endobj +3109 0 obj << +/D [3105 0 R /XYZ 85.039 528.055 null] +>> endobj +926 0 obj << +/D [3105 0 R /XYZ 85.039 459.843 null] +>> endobj +3110 0 obj << +/D [3105 0 R /XYZ 85.039 439.248 null] +>> endobj +3104 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3114 0 obj << +/Length 2998 +/Filter /FlateDecode +>> +stream +xڵrF]_7U9p֒mŖ<@$DL4Jo38H訤R"=====}CbߣdSq<[Gl 3g8:~ʙOf[BY~w~8Z}J)G܍9= #,p>Qe|~w''z8gr1sb=*dp$=D̊#(/ʼoQ9=Uv-+/<)II'O!<8$%Љs28v97\ KRf]+&LZx(Yy2#/XָЛlLֶ|UFFnPy'tJ^j֘)s#z腧eZW>5Ye?ny_X:G`tp&JMYê74Kh23*]kF{o鴴gnY@ `-/9J 5tv&c7ɀ֌ c>VKx]>"c2@MGD[2)424mUi ޅhhtR::og)H{m'C?)_K}o'L0PG/gr"T>>=σXR/ϐwZ q`PKF <h3Iŷ92E/T ~U޺jv^%뷔T\WpiOlxR,rbHzAA&uA)rջ ,NDtjbkÉAt3= !8?=Rhv|#Hb7tdl^Ҡcf0;4swO+X<)셱- +b{`h?_P`,JC9x6Fa ӋӃEVc4h((F$R$4.wM9I)rZ lVTCI +T VȈ խ)l%yoW2ÃZP\dxXKzpEbF~^66#:e~҈閯~5ZaСN}@BD9ɐiA5><*w0)cbc?)k^Y&j"^Ùg3ejPqf;dw($nMG +Ɏ+(y6wj;6O#/Nvfkx2 ޥ2f\"A^8ސmQBU346jWRQl +Zmeo(CaJ걾4WKMɜo*xh#vVYc#} +w/\ߐO +xm]'+@8.d!4~؍iI@{H{S5%-n!bQ$1'1ٴ ,K|KRNmHE:ܿ9(a9}NN,!}חGk]NM]cp{fTOw$j8ѳM|d7Еv3Sn;ߣ$]ps-F?l 9v@YNfHi$Z!rO$T)a &cˊ =M3:Ig煘VlP?@ xD}A/ 1wo~.z+"egz0U].}PP[`z[Ӳ8)1Q1pJܹJ^xHI >Wg A+<-$ށ +g X.댲GibFt/rRh4; ZVe"wE%>Di=k ]x5ZTp024(YmFOyQNΒ_.t;{F/-õlwxQmγ`[]_$hF.`a,_e(_~ 4s5'nLφ8jYlD$P\]b]$ 5)5qqr9HPCe~ UK)V)Eb ^I5P0/Pkj0nrvF0"Tuf$Kendstream +endobj +3113 0 obj << +/Type /Page +/Contents 3114 0 R +/Resources 3112 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3115 0 obj << +/D [3113 0 R /XYZ 85.039 781.388 null] +>> endobj +930 0 obj << +/D [3113 0 R /XYZ 85.039 761.463 null] +>> endobj +3116 0 obj << +/D [3113 0 R /XYZ 85.039 743.459 null] +>> endobj +934 0 obj << +/D [3113 0 R /XYZ 85.039 658.326 null] +>> endobj +3117 0 obj << +/D [3113 0 R /XYZ 85.039 639.853 null] +>> endobj +938 0 obj << +/D [3113 0 R /XYZ 85.039 581.213 null] +>> endobj +3118 0 obj << +/D [3113 0 R /XYZ 85.039 563.346 null] +>> endobj +942 0 obj << +/D [3113 0 R /XYZ 85.039 422.842 null] +>> endobj +3119 0 obj << +/D [3113 0 R /XYZ 85.039 393.438 null] +>> endobj +946 0 obj << +/D [3113 0 R /XYZ 85.039 126.341 null] +>> endobj +3120 0 obj << +/D [3113 0 R /XYZ 85.039 96.139 null] +>> endobj +3112 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3123 0 obj << +/Length 3431 +/Filter /FlateDecode +>> +stream +xZYoF~ׯ%@Hv.[hd-w=qȷ/ȵU-gO\pv~;9x ױc'^mnRr#{yrZw3z /LrnEWחܰrnrryL:P',6/'hb}eZw~,ܧAhK'j[j-݁Β$--pSA$5 2f'(gd#ڪҋFeńxOh|󃙤sW:iϜ24,ć p{v0 !Sf ]M' IR,&xu+Kp%^,U]Ɏgv#"m8#DC  S1TB0A@"h|+M߮ƪ`Gv}d%8cShs׉q`֣Ap~wJh1bۃ=Tm fO):A;-:3poK؁zwpU([&gXq#ݓ:PYQb4H]6Px&3**pE{y"MBmF)qWA)/m:T`mSW;Z&e<-S>5P}Xg:4 gdp<]Pp5 i}V:k+`DmWdJDP5>A4 >>fj|uCT#\`e +s|*gRl–>!n )kV1D]b A NX|vyUg27tlo ]Q6D'Hd5 FE'GsOtPu.&Y$@ nkʃ|h'*Ϝ#ֺph\uCT BxI*.3h)fvytp~HP-=7>!ABksw4 "s(> %1 gb }tϲ0 5CBHh*M@# 0"Iavz4k <A͞TlK?Kn.ֳĐ;W{O {brqwCw>qU,3D(/8q?{DT '&5ĬzQ7&Kn{QsHh>!ec:p;JfyB%ԈgqE?Ycѱ_6QmT[Z3Owd )# yvt-Z@C%yh*%nr:ٜfc |yC='H9څȀ~xfOmu(Oѓ$<5/G$XM uƩŒת]7Ew=;; 1CSGS/f`)׀8~\o)ZϒRۤ2i%/{>D"VV+:JH;R9|/Tф՘O7ULzendstream +endobj +3122 0 obj << +/Type /Page +/Contents 3123 0 R +/Resources 3121 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3124 0 obj << +/D [3122 0 R /XYZ 85.039 781.388 null] +>> endobj +950 0 obj << +/D [3122 0 R /XYZ 85.039 531.337 null] +>> endobj +3125 0 obj << +/D [3122 0 R /XYZ 85.039 509.575 null] +>> endobj +954 0 obj << +/D [3122 0 R /XYZ 85.039 410.893 null] +>> endobj +3126 0 obj << +/D [3122 0 R /XYZ 85.039 389.032 null] +>> endobj +958 0 obj << +/D [3122 0 R /XYZ 85.039 239.143 null] +>> endobj +3127 0 obj << +/D [3122 0 R /XYZ 85.039 217.942 null] +>> endobj +3121 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F38 2158 0 R /F35 1632 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3130 0 obj << +/Length 3180 +/Filter /FlateDecode +>> +stream +xkoFQ D[(mZ?rrA-Q6QIt]RD9nZ{fW_& +lz'Z$9@ DpT8o#stA ϣO'GckH'hH~?ӣ]@=<2 wcw39yӣ_?LLN"*9pp(&NՁ +Uxa$=N,ƀ,[A]9Qsc#H+t Y̓wUe*7(W(49N} NegG&7_ڌ?TEy妔:^Ft{nTN +63&"["rj!FxUb ƴJð9`4`tvDcG6=qM~ģGNox&k +8T4 +iY20$# !5u ED,("C,{_ m/,X{yƂDj% +'ŷom0G'rWu$%ceY6/x;DEu^ehP90Ek%@~p[Pn&o?= +0{D}RC=j*Ҥz5Hitb0b_us}g+Z UҲO PQqH.YgYH +T#Fóf 4cSI/ ;2ȹQu <(Mh| +[͋+InQ`E0!1`j|Rؠ㘽P:ao)3* GfaL +fF|(< pGlE͝+qnΪ/Z!( ̪ +=rBdSnFdxl!#0, /,%2\(2>v zYK!0e3/YHKWmJN.ydpAVPT}Z~t/#ٕAC> E!AۏXx`|ɀQb"kK(M.C"`Z9) pWU/HT1#1||8N3Gl32AcZ뾉r?!ˬIh 8CQxQxE _YF;D5]M68Z KW9aձ~3Aφ;JxzG.AmҀ}NNVYH5A6vqw/;Dӗ D[JXRoy!n|Eg7b7)(!4xH7ITdq/)w‚5O'1ɚ[P㚝z}W/I޽)kD`:j」G6"q9>yC\BJD#J^͵|lH(Ȇ.hl+.M:>04! 5sWXв+)naňlq%ꕟ;Glޖл:/.2Y7qw_%*63~[}n&gC/dp +)kN]'aEKXx!ϤETBq72T=->@^"'>g}}fp[0 65UOUHrev& $ G@q%丂w"h][;`Y +pt}攦2ΖerAK5vMP!+ fx5Z"VNLU(1&ޭb'@}$j_% )Nϱ8c=KEI%ed vxW>H/=UtϚNp9.-pyp-}WQt"ka&ѣHiλnJo)H)`7 i!nU|zRōzq: 7p$Zh˶("3q:.%[Z|PݍZDYlOZH bJP\'?mK +VKOY導=p3'#!?py9ٽtc)P| 0@`0OviCb5nmنLʯuk'ۉ0i['7 +[U>JCˡTM8Θ 2m= XFç=O'hqZ%AS\KmD^@ ɝQD= zg-10 Ht=l 8LO/ :ގ9`Z6VGڛ8kta@Ea!]ȡ;@"5Y-ďt"{L#Hߋ= ̉vM!mk6GaK֜p.7HL7_~/>XsV.2!FԳ; 2 +x)ޥUíQװ {Y|;;Rٖ'qLUp?3-t3`#_VCkZg^wk|@c>i,wʧc1kro#VXPUv_pj2藽WJůH8mqpo_v)?l&BQ|JS|S^sQDfT_O \xjR@ۧ`u3޻άoڿz[z=cPMHTyzzqr|'uW?]M'g*xlxAP1o?b}UyUXi@͛|7%$cPVӻѶsmaw_{}hB%e/x/*endstream +endobj +3129 0 obj << +/Type /Page +/Contents 3130 0 R +/Resources 3128 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3131 0 obj << +/D [3129 0 R /XYZ 85.039 781.388 null] +>> endobj +962 0 obj << +/D [3129 0 R /XYZ 85.039 719.568 null] +>> endobj +3132 0 obj << +/D [3129 0 R /XYZ 85.039 700.697 null] +>> endobj +3133 0 obj << +/D [3129 0 R /XYZ 85.039 482.087 null] +>> endobj +3134 0 obj << +/D [3129 0 R /XYZ 85.039 380.398 null] +>> endobj +3135 0 obj << +/D [3129 0 R /XYZ 85.039 328.662 null] +>> endobj +3136 0 obj << +/D [3129 0 R /XYZ 85.039 279.048 null] +>> endobj +3128 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3139 0 obj << +/Length 1713 +/Filter /FlateDecode +>> +stream +xڥnHHolB%ij51H̜}lѷOCϲeBa0'۞_MO Z!EmEv_e48.&HJ95A88 `-#1-ΆN8z?zGog2Emohi2r-חʏާ/v ھٖmKDQs=iy47pagG, fmX.˯!؃ %C'lĎ )>#ڤI>Q;wm +4l 7_*Δ^1+Z~hNͳ\3[VY|\ +E>n|2O'Fy#q]oI WD44O+r'Wk,"4twC|1 z3 qx=E-02dJi^$jE8i4G'!(am3Jo )xsGq!;=BڦEUv] +k2ac;wUT钏+ϘEQVnb}`)'eGrڈV +RuVVw2`_lWFP_\b rH!g[Ȗ>ylV+~Vp1gT-y)nj1B-쉸߸^#hYV-lT.ӨF1MӸ2X5K$>)EoА?(3Js *À9N.X5ȊqsvVQoEmmELz"5~@{{swej*U2I:5Z$8`B(WיSYȔ4c18lGߗMGPSG +q6JlHF6YɃ׆Mft3蠡T5/md;_pE 72 +n$2@J,Jer"Mrm(YS@qOs%madb]*@ͫþ@C @c&*IŜb v#KMד#94acX;Xfp@#.Mzv7M_V@bp`g!ݹZUhCLD_ByTK(g{aP~H5JCxkPJ81pg%[)ԣ^X2Si<6lgbf+~6.u(0q2j뺵(a\[@%9R@~}"G? +U?? }B8&NKc[[BZxԁ+jiZ왝!9r,MF 0OB"3ChނS' ~3\.V4-u0Vl)G~2oѾK=S;78d:p39|x>["oNgW#xBq~3DN H[C!!ҕ =dCs# +7΃_;s{Hmؖ#CMFVkRExsE/-u~ endstream +endobj +3138 0 obj << +/Type /Page +/Contents 3139 0 R +/Resources 3137 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3140 0 obj << +/D [3138 0 R /XYZ 85.039 781.388 null] +>> endobj +3137 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3143 0 obj << +/Length 2900 +/Filter /FlateDecode +>> +stream +xZ[s۶~ЋԌx˛OiKcL$PJR?{HJӴ9g:1b,a1ād•q<ɶgd #΄&8{CO&^2Ye||bv:R:"v(T8?ßt&[ ԏ^s%v5λYL?.~:/;)Wd seO\$ +(i/S5r׋ `9)`zts7Z|yS۷ZTw^e }Y<&΅3An29YdtۀDW&NoӺe:LE|LĽ{Z;ZɞٍwvD +'+U4f~-'*,1&ܕ +{0tRO<6{'ܝl. Xv$}?$nW{@SPN!c"'TtA?-<qz +[4:i$xz+&W4w%ׇU -%ߥÛ ey+79̗= hW={j}Ww>afh +&9nBJք㻡%̺C.!BkKbDf,n̡̗Ā +FDsxJgmN1RN+o[L͘|?̜vWʶGhpaF~d&@l ,]@9ǞOG׬THn<9[Nktt7IumG*4bx¸-T +(y,m mﳔA>uu.S45S~ l-$,]KY45؆bVxZt5ǚʺ [/R?cX3MQKȹ1ȍx4FWrXnb(Ǯ3NV1Hg?5-],Ɉ'D)xA$HKkd0RnvcĘ n-CbxEP ֑$\+J} ,WP0փ/MeyALc|c5&ȹZ,FYIIyϛtnOkID`GrXl5!K @7Մj4L. v%&C# f6{>#Ž$nD +R_q"!Ƅ4ӰJB'\`XVjkbHYAlVqE(wb4 QG7+QfNXOGwuU.'3hh803Do `Q*:PgnPoJ{ wcJ7_9HJF^-pȏrcAP/·'Zn8Q6kR(; /ɹ*z2XIjkfVh5sun ik#ʋoo CF.7]Y#'B47Ŕ(Tn̾ϣ^tIZ CBʈwc3"ut,ʈPb>ҧR&'?}MTOfЭT)ˊ-yq!)P-r Ciifc(5]q$h ӥRDž&_ĔE*5Z@@S@@r9 s6[6>Б| +ԸRaBLQT ̯S[01x %WP nr-| V>e=o}"9t`l endstream endobj -1754 0 obj<>/XObject<>>>/Annots 952 0 R>>endobj -1755 0 obj<>stream -xWS8~_ӗ 3O: RR[!*Zv)߷[ !o|E7iL %y/ BN>{W)i87`Bq(t̚UFWAhrrin蓳 ko fޠ|S`Oaw؁488UNn9r1,\8fx҉w~DQD-Gn2*u ioHE%>߮>/_G/cHPk,l̏V^G? -T2LyLz쥏1$v2kT[zI7u{R)KLReHi[,j'ec{@Nle -z4uUSZmir }6$WR2BʤPU|)uFNT*$Ȫ;*"[HEǨS(DZ窖Ճ)IKuۘrg`ـeOޟ˜h\}8ҩy(H)-D OQ-DA &Kkm=zPծut%-b=( -)Jpx|-EwYrvV8EQ`O)ɔԕEv75PIYz'*o!5|[6+ЦWr8 e^'$ -@1s^i2eibkmA9A=L8d 8@h05Oޏp&l]<})W@p8>;p0%F ֧8z.rI0nsϤqb"C -Il R6mE+)jӺBJsLG\I)ArY -xBdI4Reh~s}v1`Dz  G,h|$Fos0E!NFnTVBe@LQ)2pb2M^!J -{F`..3uBr8P2s[\ EOFa 1x$b6#S:5ȼkq>/-܏jF>M-qlZs OYaCmLaNx%esRkkppg@ډ7LvheT ׊eͶ$wm2{1avd_ِ&#| ;Wr(ڈLAͦY9gdL] tĚ.WOMendstream -endobj -1756 0 obj<>/XObject<<>>>>>>endobj -1757 0 obj<>stream -xMo0 n!%96[vJ, J2 -׏N@fP`S"#G.d8 Qbd<]9^Q i r)YIDȐ9+d2dE,p.knKeMgyӟV=xmpeU^a(BH򺺭nU3#JcZa! -RA˶sGiL]͑NnK-Tr#%bң;^r*90yLNCyZчlj0vmȂg0ϥjjt9WjV[}!`^jIK(9s=z8l״dA `/=ZEASƹ0Ȟ 䩩{7ܓhD*StK7gTfRAOaxqWFߣWendstream -endobj -1758 0 obj<>/XObject<<>>>>>>endobj -1759 0 obj<>stream -xV]O8}W\Haf݁٥J#I<$qv=-%B@{Li)]lNEw0&t>ds:~JLyNizsvxs贽n=->QT(R݇T)T55pUdn[y7vhK;YDj ktv >h(¶ BSg}Ū4CiUKq=T+Fb*, kToqruIߣ8f'K{9wyX^ HVo;5-x:ƕBڀFRiTr(62wIlmԩM")m[i*0awҗ#? )Ow:z0_ހvQ4Tk1K7Nc8 -/ɛR: lz'#eFX\}L#rR{ twpL X[7xR/u_z `a7.Acjq]`"\i{Hq`#5A+1#'n:z -o*H'9LvL')uyK~;/fCV0d"x?J1No+\B Jܗ%笐1u;i}<9iVh'P9$`v2EnZzt?+~xԁ2@6_2a8mhޏeT{"Dp1dvp$NqzDlEi %6XT1dwyVؾ| sH8`J&>c)TGpVƢuy8)I2MݧD1T-%IMSp.0,q>/XObject<<>>>>>>endobj -1761 0 obj<>stream -xVMo6W |iC v@Q J,n$R+Rq_7udoz($@ 3o޼yW3gF9-bJi4x6ܬܿXo&K'V۫46xmF@46ʒyM)ZMd)Ѿ\!Rf,L':#-I"M$PU*E3B7ZTmZЮD@a!2t,֟ŋrLIg ^j٨Jj'28PԘqN:rRxکJ!xyPICE 8{UqP W 㬶NVNw{Etݠxv6JAk/$SZ7-eiRF rZKnhTy4b,?k)TRShr@![ Dgֲ(#ҏ4-$UFjPP[tgi1_[! -Ej -0+sqѻ@PK5joe3h1C`"aiϰlAh6\ ;2FIK'<ބRpZ|YT$tf27McW 1f1%{A/%Z9thx=pMrs:9:T7*{Vʠ%̥ﺟlvUDHWr1c plzf .5dF7Taj-wߘ\=B@Ws^`tBE}Cl{ay.\Wn*$*)2ja|U0=4H=MHqQ2؎Xaڌ{D~-Z`ziY< -1tVG~OF]`ɢƁ7źF6W'(GnWB`4v`+֩`G'lТ5]˿ôMho{e P -yeΛ~ػ7 aytG5 Rɤq/xÁzz˫mXz^󱟷W_۰endstream -endobj -1762 0 obj<>/XObject<<>>>>>>endobj -1763 0 obj<>stream -xV]oH}ϯ⥩Ը!%t68}==wl Ͷʇu9ד iԣt|4 4?#i]Ň -Gk8)J~]~/LuETٷX (A8.JNosI4Va mLm#+S_phc4.d^>G$(1"N~x2 {s6h,{Cֱs*K xhV-U ĩL{"Eu&oe7ςT*̫Y6+ ZFT;C"O=3;HAF\om n(=Tǰ_١LmDj5meZxpԐ 5? ,(sD`/+Z& ,d"2YύJRA q0NԂ9 5%x߲`R` æؓ;%#rsO?ӛ?botS&^KuGx@i;[z1Zw5-/?)j:BzyMfFLwF_]LIJmZZ͘HW9z1cIҏ6h#eemNT)ضPD -M>xpT6t _xZ(3JaQ@V6=8 qH+肑F>@ AW_j@>/zvF0BI35^^[,{dvBrx(~O+s Ckk|5TTOM]k4 K$5Q&AL/b~{!f>7cS@obiiAR[jˡze=nLV\UUAb-F< 6NyvpVON)yj@fSLզh\-@ƌrF乍[, QϿ~o ״j4$ɟ'ɓendstream -endobj -1764 0 obj<>/XObject<<>>>>>>endobj -1765 0 obj<>stream -xmUMSHWBjc1lr[]92F@QfF8}=X։)(i=u}WLҜn!"AYG6k*7}FqL -5KB/.mJzid۾~׊:GҾ1MI2sS5uT$lJY Ei!hQ -'ʓ%.'?X~sQXkJe}L  G$55zA u/28[8L`p=F)89,&4zp,Ftj}s^k4%4eZ>\ "8@:(ј_ -aP}r!~D9ѿyf?'rL~||I} lcF}ܒp`j& - 0M'хxSܛ - 8c€š4V|)Oˊǐi7%s\MJz:|7״ D6/kQ^INЗq[o|Zendstream -endobj -1766 0 obj<>/XObject<>>>>>endobj -1767 0 obj<>stream -xWMo8W z,P˖N6) #M({%*UoH)p EDg޼y3qRZd4S^M NO%͖ ῕TtdќHa-Nq[UzB } ">w7w)eZxlXҺ D5}%Z/-M +INAy%[}o.tP1ӄVrLMgiHlRiIiP#ALI^:hg:EC5yCwBBxgCXN;i'em%^_y~t~89{iueM㫃Qf׍5]Kǫ\gIcZS.E}*7XJ1ېp#)(CyA|^L:>98v&A1 -] 5?"/^NDQxB Kmv[LU.lbPt\FoAgF! Z "5 -@o5V]J^۷l`6?Rp#BN6˒lj<?wb$Q=zrlj:eBѶ  <5]5CRҿ6 kúR Vu"Z:'n@\ny+sԈ N&g+FAvM Mm -`{U.EFa{%[Bp<;k7o Gq ̸|Kǚ$(t*#<0EB %6ZAo?|F"E+%0c F$0,a0a@ 2PJU">[Pt\_۾[2}=hcb -پ0<꦳"NX QRP_;/t6mr,Bռ9z.hW}q5jH,M&QҰ!GeOQvBi`͗L}ѷxendstream -endobj -1768 0 obj<>/XObject<<>>>>>>endobj -1769 0 obj<>stream -xW]oF|% -`Ӓ?yW -B~9Gb-wvdIhyܛkgDC!RV\Lv>hDh04_TSfJ9|ÆQa03]p/em@쾿m>|wkSvMAK!폎C$:m.ГE&'^khrypsOa&㩶grNg\}Pe#irlH*p$Z뜂%lqzᨳund#j87:`@I@m^=ijɘNea:%țʔma}*(R[R{`f{"ǫ*U8m&T fE;{VݣKozU7tsKS\lEtRAmk9;*G!ӥOy*)DFHQ/salB_wTA̮) *AH90T _ R{4nf%sy"eAl7ip[>ykf$4 -^ͬb^>9U%y>1:>s_ht2tI*}Ku2~D)m;zAiOѦ@Fe[ks[;@ -AHn t%rJ^z["֠{4(0($ZIp|t-= Yļc~AN..:{FDs0͔Ãf)g'ԢUwFR"_v[(mM .N(yUwBXy2!RY~kr#KqM`;ju^ڛI+Iݣ3“6ٽ yCf~{8Ո{0c}FD®&l巴Uw=1.J*rK[ wڪsJW,zڅ.Ue='BM]\3Al?jH3u'i^t@o$zsiW2Ba**u%f+ǁ243vCޜym,gyÎe_BX$jD^?ӏ~^͂`]幆gx@w0^z &8EuSqNgdS"Xs JQœˊk.YM-!mll;iė@llvfS8OюAD緷]dCe2L`bH6,}m)*-hY(8T}=s1&6*Aբ :0SV*BAqП#j0e{Iڗ[ *T@*W3 ?sȮYKK2B11Kd0bɦx Rx|^ҋEt|X^Y}⢵eUׁmZUiss<&CE 0 KQsWCXX{i'U4,+4ԠmK]d: -`i5]'y^\ZQX.XDZެ7n<jVLrcك'P0:X\I`""mx!9v(&X.op#p2B5alA'hZ2 ӓC4֏#~v=co,~endstream -endobj -1770 0 obj<>/XObject<>>>>>endobj -1771 0 obj<>stream -xWaO8ί!JOfvi?-I*!oݸ$qj;l;Ɇcό߼y3y?1-4SRxM*1[DϏ#u|{M_ΗǴ\邖)MdBLi'RLjKJDm%Pym$5LYr:m&KHB{IiL82ZhBx0HS#%+SƒmU&s)9dryp4kHԘ[o{9m#uG݊b%(OL9D­=&*UXm?e4]W8`%htNW^{yCwwg."k68N׆%4HJ$mytiZ6RWdI+w.NL# C4 -KD>=H'(Gk 7`B*dqΕO]?N+08Qۋ}.A. ѠzudhI t *9vUˆB`A@ns\DӗwĵLII0"GlbTň @{ɨM~ASH=h<96 Ǒ'Fq| -Z8p?F]suiI|Ŷd ?C ۧ3`_5'n dбnp^?^Ӡv -FP i o.7C 5KnCY)9GUW4!VGY?'Os}NoLH4}^.^3;2 -P:2Aj4f'_YuPg|,kQOdV":.VtOҭ5P˴um!Q+JHDn^QZ.ɰ5os[ɺ08 -a'ۡr -I+Z@W8g%Uj!ݽj>YU\6 -H['{-nzDrYy Ӷ>I 0QEtKp$1jyi"UBTiC'My: [QWkX=.8oXjs ߴWzoze-x2y.$5giǗG3xJ:M(pѶpt.#>3 ^,T 3P\>kzk_npPoE{FOC\~1q`Ǡ5kПYyHc\۫kGV,Ak0Rg0+\:Wy U3 - :UJ]B{^"?1>/XObject<<>>>>>>endobj -1773 0 obj<>stream -xXQs6~K,[v:ӇMn2snXss  (wi~isŒKi52%ٌVv]Eg2kë~s-SiRN[^yc`5;H|\#Dz֤._tFֺɨ_b~hI-ԽaOu56jqPQn -~?ۻ6 [er^z|[Och!ag^'tn >QҶVQ={zwmR 2c4SULz]W{~5f -_خh"_ZںFV#JGR g<#ݦ vQ ]5u,Sds+|4u]ʴ {NKUU;J%m0Hi;"(DxBH{ڰ(dW#1X k ϥ#שyv[Vd) -B7pVM8ͬ kLfq -UT^`RϪPN{:0Аg$s ԗ՗\Æ"hUk2gd]G9EHu e5U׋eKL]q]HO@nku -Zp CMj*4zu^pp* |66A=-E]7׏o~ P|nWZ^:X T&RI_ d yxVB}LQx}a<8L=+>Hwe - m#߆TDu -ъ:Ns_P:7dJ QUַh_OQɢ!{Kӵ 0dGQ+i@%̚'"h*5tq" }1yזiJzKzB]vN3 9 fhq+ Fv :ϋGDhF7t\*o߲qrU>d7W)k/bE\(IvI0[!jD+Vm5w1DLn2-+ـ`wBp^4gZ_{%&M!H~f@ч3@X7t#T:\^" :v,>f6]>s= X!;N ͑)+w&pmbL5:or&Ӧ m댑\`֡ 0{ eQïɑ2F8yRXBgm5!Pl,ybLn.p5N#9^~>̹ې\.VWE&J!;kHd!; S;{Ik1wA]P`1D @|PbHerE@woX/-g?| 6j;:a=B5 |>0yIWKf>N~; oOendstream -endobj -1774 0 obj<>/XObject<<>>>>/Annots 954 0 R>>endobj -1775 0 obj<>stream -xTn0}WDcCD&U[섊uJJ_&D^{D/|i^prNx[(=8(Mgaҭ6AMYNޚc.0@n'ipEHsM#c|@.@4 Qlys^ {6S[8VlY7R0 ɯҗ`Q4 'TxxpfΚP]de\cbr󧫆©Vm7qL߸0.Jz` -B{ ;QcJ -GސhL %s(gk^&/3oPZ%GZkw-CT##V{Vaˊ491}zrVT:ΫWA(&Ԧ,$@G^: ϧn 'O z3Z\*>Ó.ӽRW2lm;ss E_U( ( g/[3GQdUN>_R|o4Cl*Ќ,Onu_?'&У`YTg4pKJ3ull}1IRp )J+"J[Y߮@/W3.X%B]Fh"LfJR"|K_?endstream -endobj -1776 0 obj<>/XObject<<>>>>/Annots 959 0 R>>endobj -1777 0 obj<>stream -xWMs6WMDIlɹ9vLLg|IBL Z} PN&ՏтULgVy4:zco$~|e/ђ9^l:|*~_̣3W1N)YQf -HJC\ c'[w/5ޚxYB-NYVeb=: 0f OLU@u>óZ4muty~Cғjft2@+L>+G<#3T&υڪfvCԋֹl"RE e"%#t8Z9z%wM鳘^\>0{4"CpCGR_ kx i`(~1xX;vJ2 ԄVwAG?_zQo'9X## L0ǀ_q7 >b"zylO^ ]p:+FA;\@Ql=y ~k/y2sjϯ69#oDpJ<ž=Ϝ%z56#_]\ndB 5 'x3JܩW9ZXFttKo-gS|#Lp-pm`ڴ%*HU- g]"a|5孕v;^#}(|zP>5}, ^$ԡ WK[d Eu_w8|_oa-|a3m/gQendstream -endobj -1778 0 obj<>/XObject<<>>>>/Annots 976 0 R>>endobj -1779 0 obj<>stream -xX]o8}ϯ0Hf˶%̤.BKʼnDjH*_﹔8j;vbQԑL~{<4i48DhJ 1[I[^LJ7gxMh1ѰyiyOcA4x:7^MYd&Tp6a 5oau48CBA#m߇v4ƫ]<]<@pb>^Wp8 -WoVg׼L-Gq:* *xcS{wF{krz/Va}TMi(HY4笭ҋutJ7ZycieLH蔮wR*y /+ rX cN wIER:5{GoW}H΋<3(L#=lxEx#׬Q9*ҵrUŭʑ.*OI>)a@Wߗ?{a^(^u^21ڤ"*謕 G{][;d -qsh玶@ \j);FUQ^Պ>'[i26EP,mp}+DB ^}IS^![ex-eڕ҅H gGcnd?4٣C|]G #_= 9AXh< #ܲ7N.:/`q@GܘI&c0)7 |vJ\˶&jW,p2I *A+3f&AHzha>:r˦*z CQ(6"$2Wo"cw} $XP"Zw}xv4ZG@J_Z|8%ߢ6, xЮ -@orYDt%g.Ia%4K?i>uMkH m!S&/]mgOmCZJ)_&{rqrAwD {4=⎊/Bᵊudv},YЦ04d޾Ax(z^t' X9oSϻYr?SZc5"3 _1'dH|Iath7,*2M ck]Rި'8lu -54y_x0 !.ky@O~v`V 07|#a~Wƥk9O |X!%Ò}-_d/.<_h:F~}sMꋦiy f>lpQa>/XObject<<>>>>/Annots 981 0 R>>endobj -1781 0 obj<>stream -xWMs6WlO;/Kr/ǩ2ukM;E T-H*괙d}[`JjF%e`Lh1%3ZW '/obY2C`'S/;f6M)8zE<:M6qTI5t(Et?lA^TmH +#avY -\c 5&.ܼLh<#M>6:THZ@D˽08jG|=@Y }&5E;'7Bi9"$δu{2NFYH3E; 1sJS--W]Pq~<;X֐s! 6fׁ:""1BW~}<"H -M$@sNY)'lR, ۼrgCsڸcdOEC#} .NNbDڂhٍTnx@9TAJdzYTj^)8)r^[sȷ &i2Jz/vv؁ h.b5dz W5q*‘.^Tj.0znDk+%v)سH?HMJsq3b[3gp'uO-!Z|n -!tuj[^ j/Y(RԵ4NdBG0tƟA ڃAfQ H @Le̩T^pʊc7EHd, - -jS[B?m%:n=86&)R1Le`/BcTൔnԞ*9s:|g>[3p++)&R Jv7!*{u -#Tʓ{(!4R$^XWT 韲KRhMJ>l<3+ \\sLKW/BŢwֳm-b9I :@bwU1Ft& 6}2f!E{, /LW 26 ff 7H!N:B`Xɜz1DU*#' &g3@.T6;xeS05>Bp|$z -Hy^SLN// Y6ʂu[Io)^DgdzC夭"NG{mj*󲁿V`caT ְ8Y='JIШCTkVБ‘XDBo3!]]!X=Z _B&Jźbwĭ洪Mdyh],B( 4Op]Q:tM`ό&z{`D%CQ *[kLi;)7p:va\S;6`?Ƚߓ$^;(Kׁ|}}/]yIm{5X `t(~ ~dqendstream -endobj -1782 0 obj<>/XObject<<>>>>/Annots 989 0 R>>endobj -1783 0 obj<>stream -x}Wێ6}W ڦi}hEbUZgHUA.̙3g'sߜnP^Of O?LlK:[PM&[w>M֫lE"|x'/ٚVUzyt'/ -oWZ\8r2/ݰlѲ--f+fK"'կj;Z3ȭuA7z׸r~VZJP -hEmd7]d1UL\+mHc充)^7GgOړW^?3Dd2mK$B1B_tlr*p^5:Wi -[I);a*Qa90lG:(_>I0Ŕ GEC#SNL(#tFRѾ&[ 1gV]^ɷ䐫FgSJSͰkF$RԳ DNH.FU88۵dKj:V D1TS@7B} h@2Z as~s(,8 ufD!@zQ=۲mY: #szqQ"0ad|W蝥ƂGwRCYL$TxTG.s[Yl5>>lDJbt\GaGnv3|y6DZ6BsRco -(Ҕ9%p6D siBAPjfGHBYR!x+}} zlв2c= =޷d?0 OQU.N bk' -D/ϡx!hzJ{jY4,*~Qŋ>pNMF&JUR%ڃ2'bCO)1ik HYkؘO[vxAԂ"nC\-e! HɭC 'HøƿKc䰂.u-:4kD݉t-I5tj&MW0 -BԎ3hPZ8Ԉ$A"A/A2%~Pp(/BxaaD%ʍL8#d4#y(8.cو+2TsJCZ.1=Co%d#M!*ho΋<@Y!ÑWrml>/XObject<<>>>>>>endobj -1785 0 obj<>stream -xWnF|WlRiɲe@4iH;hY=rhEHMgF4_PM)/ْΖ)zM8ϲ^N/~utrsF*Y,/hUL*&*єOzUNVkMIhpJ'm|8K_M[ڙh/^S꼫_'U -km $c5)'s}0r}UmHY/AlTyU)_*\U1qϟD4: -`^5f^+n:4\8_`jk*S(pSJX#c^ օj/gm՞d5p \z=2S}D q)zpER l_E`V F{tbJrrsI3~Q@`8mۈ¢/eY]Jt=X$jsxOÅ:[\Fmj.k<@s5g1(06~̓9'hF@g̓\Nuzǎm#5v$MpQ7k-**lxUF:S"` 2}J208e -͎O9&Sy'ɼ%%=Oz@_>~Hc!`H/տ,z:v!B1lK -'嬥 -RuXOFh4 ˫oӯKo8ƚ:22 <4v 8`/XnLfڟѸ#PG[`ȁ"3sV}Q7)Zq6 -'2q}<NXۃ<}|@ [t|$0f٫r ĺ+w -XUA_L/b-Oly__8U6endstream -endobj -1786 0 obj<>endobj -1787 0 obj<>endobj -1788 0 obj<>endobj -1789 0 obj<>endobj -1790 0 obj<>endobj -1791 0 obj<>endobj -1792 0 obj<>endobj -1793 0 obj<>endobj -1794 0 obj<>endobj -1795 0 obj<>endobj -1796 0 obj<>endobj -1797 0 obj<>endobj -1798 0 obj<>endobj -1799 0 obj<>endobj -1800 0 obj<>endobj -1801 0 obj<>endobj -1802 0 obj<>endobj -1803 0 obj<>endobj -1804 0 obj<>endobj -1805 0 obj<>endobj -1806 0 obj<>endobj -1807 0 obj<>endobj -1808 0 obj<>endobj -1809 0 obj<>endobj -1810 0 obj<>endobj -1811 0 obj<>endobj -1812 0 obj<>endobj -1813 0 obj<>endobj -1814 0 obj<>endobj -1815 0 obj<>endobj -1816 0 obj<>endobj -1817 0 obj<>endobj -1818 0 obj<>endobj -1819 0 obj<>endobj -1820 0 obj<>endobj -1821 0 obj<>endobj -1822 0 obj<>endobj -1823 0 obj<>endobj -1824 0 obj<>endobj -1825 0 obj<>endobj -1826 0 obj<>endobj -1827 0 obj<>endobj -1828 0 obj<>endobj -1829 0 obj<>endobj -1830 0 obj<>endobj -1831 0 obj<>endobj -1832 0 obj<>endobj -1833 0 obj<>endobj -1834 0 obj<>endobj -1835 0 obj<>endobj -1836 0 obj<>endobj -1837 0 obj<>endobj -1838 0 obj<>endobj -1839 0 obj<>endobj -1840 0 obj<>endobj -1841 0 obj<>endobj -1842 0 obj<>endobj -1843 0 obj<>endobj -1844 0 obj<>endobj -1845 0 obj<>endobj -1846 0 obj<>endobj -1847 0 obj<>endobj -1848 0 obj<>endobj -1849 0 obj<>endobj -1850 0 obj<>endobj -1851 0 obj<>endobj -1852 0 obj<>endobj -1853 0 obj<>endobj -1854 0 obj<>endobj -1855 0 obj<>endobj -1856 0 obj<>endobj -1857 0 obj<>endobj -1858 0 obj<>endobj -1859 0 obj<>endobj -1860 0 obj<>endobj -1861 0 obj<>endobj -1862 0 obj<>endobj -1863 0 obj<>endobj -1864 0 obj<>endobj -1865 0 obj<>endobj -1866 0 obj<>endobj -1867 0 obj<>endobj -1868 0 obj<>endobj -1869 0 obj<>endobj -1870 0 obj<>endobj -1871 0 obj<>endobj -1872 0 obj<>endobj -1873 0 obj<>endobj -1874 0 obj<>endobj -1875 0 obj<>endobj -1876 0 obj<>endobj -1877 0 obj<>endobj -1878 0 obj<>endobj -1879 0 obj<>endobj -1880 0 obj<>endobj -1881 0 obj<>endobj -1882 0 obj<>endobj -1883 0 obj<>endobj -1884 0 obj<>endobj -1885 0 obj<>endobj -1886 0 obj<>endobj -1887 0 obj<>endobj -1888 0 obj<>endobj -1889 0 obj<>endobj -1890 0 obj<>endobj -1891 0 obj<>endobj -1892 0 obj<>endobj -1893 0 obj<>endobj -1894 0 obj<>endobj -1895 0 obj<>endobj -1896 0 obj<>endobj -1897 0 obj<>endobj -1898 0 obj<>endobj -1899 0 obj<>endobj -1900 0 obj<>endobj -1901 0 obj<>endobj -1902 0 obj<>endobj -1903 0 obj<>endobj -1904 0 obj<>endobj -1905 0 obj<>endobj -1906 0 obj<>endobj -1907 0 obj<>endobj -1908 0 obj<>endobj -1909 0 obj<>endobj -1910 0 obj<>endobj -1911 0 obj<>endobj -1912 0 obj<>endobj -1913 0 obj<>endobj -1914 0 obj<>endobj -1915 0 obj<>endobj -1916 0 obj<>endobj -1917 0 obj<>endobj -1918 0 obj<>endobj -1919 0 obj<>endobj -1920 0 obj<>endobj -1921 0 obj<>endobj -1922 0 obj<>endobj -1923 0 obj<>endobj -1924 0 obj<>endobj -1925 0 obj<>endobj -1926 0 obj<>endobj -1927 0 obj<>endobj -1928 0 obj<>endobj -1929 0 obj<>endobj -1930 0 obj<>endobj -1931 0 obj<>endobj -1932 0 obj<>endobj -1933 0 obj<>endobj -1934 0 obj<>endobj -1935 0 obj<>endobj -1936 0 obj<>endobj -1937 0 obj<>endobj -1938 0 obj<>endobj -1939 0 obj<>endobj -1940 0 obj<>endobj -1941 0 obj<>endobj -1942 0 obj<>endobj -1943 0 obj<>endobj -1944 0 obj<>endobj -1945 0 obj<>endobj -1946 0 obj<>endobj -1947 0 obj<>endobj -1948 0 obj<>endobj -1949 0 obj<>endobj -1950 0 obj<>endobj -1951 0 obj<>endobj -1952 0 obj<>endobj -1953 0 obj<>endobj -1954 0 obj<>endobj -1955 0 obj<>endobj -1956 0 obj<>endobj -1957 0 obj<>endobj -1958 0 obj<>endobj -1959 0 obj<>endobj -1960 0 obj<>endobj -1961 0 obj<>endobj -1962 0 obj<>endobj -1963 0 obj<>endobj -1964 0 obj<>endobj -1965 0 obj<>endobj -1966 0 obj<>endobj -1967 0 obj<>endobj -1968 0 obj<>endobj -1969 0 obj<>endobj -1970 0 obj<>endobj -1971 0 obj<>endobj -1972 0 obj<>endobj -1973 0 obj<>endobj -1974 0 obj<>endobj -1975 0 obj<>endobj -1976 0 obj<>endobj -1977 0 obj<>endobj -1978 0 obj<>endobj -1979 0 obj<>endobj -1980 0 obj<>endobj -1981 0 obj<>endobj -1982 0 obj<>endobj -1983 0 obj<>endobj -1984 0 obj<>endobj -1985 0 obj<>endobj -1986 0 obj<>endobj -1987 0 obj<>endobj -1988 0 obj<>endobj -1989 0 obj<>endobj -1990 0 obj<>endobj -1991 0 obj<>endobj -1992 0 obj<>endobj -1993 0 obj<>endobj -1994 0 obj<>endobj -1995 0 obj<>endobj -1996 0 obj<>endobj -1997 0 obj<>endobj -1998 0 obj<>endobj -1999 0 obj<>endobj -2000 0 obj<>endobj -2001 0 obj<>endobj -2002 0 obj<>endobj -2003 0 obj<>endobj -2004 0 obj<>endobj -2005 0 obj<>endobj -2006 0 obj<>endobj -2007 0 obj<>endobj -2008 0 obj<>endobj -2009 0 obj<>endobj -2010 0 obj<>endobj -2011 0 obj<>endobj -2012 0 obj<>endobj -2013 0 obj<>endobj -2014 0 obj<>endobj -2015 0 obj<>endobj -2016 0 obj<>endobj -2017 0 obj<>endobj -2018 0 obj<>endobj -2019 0 obj<>endobj -2020 0 obj<>endobj -2021 0 obj<>endobj -2022 0 obj<>endobj -2023 0 obj<>endobj -2024 0 obj<>endobj -2025 0 obj<>endobj -2026 0 obj<>endobj -2027 0 obj<>endobj -2028 0 obj<>endobj -2029 0 obj<>endobj -2030 0 obj<>endobj -2031 0 obj<>endobj -2032 0 obj<>endobj -2033 0 obj<>endobj -2034 0 obj<>endobj -2035 0 obj<>endobj -2036 0 obj<>endobj -2037 0 obj<>endobj -2038 0 obj<>endobj -2039 0 obj<>endobj -2040 0 obj<>endobj -2041 0 obj<>endobj -2042 0 obj<>endobj -2043 0 obj<>endobj -2044 0 obj<>endobj -2045 0 obj<>endobj -2046 0 obj<>endobj -2047 0 obj<>endobj -2048 0 obj<>endobj -2049 0 obj<>endobj -2050 0 obj<>endobj -2051 0 obj<>endobj -2052 0 obj<>endobj -2053 0 obj<>endobj -2054 0 obj<>endobj -2055 0 obj<>endobj -2056 0 obj<>endobj -2057 0 obj<>endobj -2058 0 obj<>endobj -2059 0 obj<>endobj -2060 0 obj<>endobj -2061 0 obj<>endobj -2062 0 obj<>endobj -2063 0 obj<>endobj -2064 0 obj<>endobj -2065 0 obj<>endobj -2066 0 obj<>endobj -2067 0 obj<>endobj -2068 0 obj<>endobj -2069 0 obj<>endobj -2070 0 obj<>endobj -2071 0 obj<>endobj -2072 0 obj<>endobj -2073 0 obj<>endobj -2074 0 obj<>endobj -2075 0 obj<>endobj -2076 0 obj<>endobj -2077 0 obj<>endobj -2078 0 obj<>endobj -2079 0 obj<>endobj -2080 0 obj<>endobj -2081 0 obj<>endobj -2082 0 obj<>endobj -2083 0 obj<>endobj -2084 0 obj<>endobj -2085 0 obj<>endobj -2086 0 obj<>endobj -2087 0 obj<>endobj -2088 0 obj<>endobj -2089 0 obj<>endobj -2090 0 obj<>endobj -2091 0 obj<>endobj -2092 0 obj<>endobj -2093 0 obj<>endobj -2094 0 obj<>endobj -2095 0 obj<>endobj -2096 0 obj<>endobj -2097 0 obj<>endobj -2098 0 obj<>endobj -2099 0 obj<>endobj -2100 0 obj<>endobj -2101 0 obj<>endobj -2102 0 obj<>endobj -2103 0 obj<>endobj -2104 0 obj<>endobj -2105 0 obj<>endobj -2106 0 obj<>endobj -2107 0 obj<>endobj -2108 0 obj<>endobj -2109 0 obj<>endobj -2110 0 obj<>endobj -2111 0 obj<>endobj -2112 0 obj<>endobj -2113 0 obj<>endobj -2114 0 obj<>endobj -2115 0 obj<>endobj -2116 0 obj<>endobj -2117 0 obj<>endobj -2118 0 obj<>endobj -2119 0 obj<>endobj -2120 0 obj<>endobj -2121 0 obj<>endobj -2122 0 obj<>endobj -2123 0 obj<>endobj -2124 0 obj<>endobj -2125 0 obj<>endobj -2126 0 obj<>endobj -2127 0 obj<>endobj -2128 0 obj<>endobj -2129 0 obj<>endobj -2130 0 obj<>endobj -2131 0 obj<>endobj -2132 0 obj<>endobj -2133 0 obj<>endobj -2134 0 obj<>endobj -2135 0 obj<>1<>10<>15<>16<>17<>21<>24<>29<>40<>41<>42<>44<>48<>56<>59<>61<>63<>64<>65<>70<>71<>82<>104<>117<>121<>126<>138<>141<>144<>147<>149<>156<>165<>167<>169<>170<>175<>177<>180<>184<>185<>189<>194<>197<>]>>>>endobj +3142 0 obj << +/Type /Page +/Contents 3143 0 R +/Resources 3141 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3111 0 R +>> endobj +3144 0 obj << +/D [3142 0 R /XYZ 85.039 781.388 null] +>> endobj +966 0 obj << +/D [3142 0 R /XYZ 85.039 667.608 null] +>> endobj +3145 0 obj << +/D [3142 0 R /XYZ 85.039 643.626 null] +>> endobj +3141 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3148 0 obj << +/Length 1851 +/Filter /FlateDecode +>> +stream +xio6Q` ̪Ö-Kkdfl!ITIa "Qt=8r` ;_w Wa1nzA?:o/~Wxug2[|rίf^?Gn?Ÿ'{7s ;Fs{Øn>8z~g{C7(ߝOzHSsQsh]w(p03\saXe?p! ύ G `vmz)sL ]QY,EٽD[@XhvS-f67;T`T,=#"42IN_$L7qcRߴc꫄ MZ׃G" )×ַX{ ˩-bꁛzwoUЋendstream +endobj +3147 0 obj << +/Type /Page +/Contents 3148 0 R +/Resources 3146 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3149 0 obj << +/D [3147 0 R /XYZ 85.039 781.388 null] +>> endobj +3146 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3153 0 obj << +/Length 1254 +/Filter /FlateDecode +>> +stream +xڥVmo8 _a(W:>eK^nWlnbu4HQv{_A")I >=Bn043sZ|{WcpfG,2g%_˛}36r /Thy1~|f1|Q&UfcJt8mR'}LjT Ss $Uf1e'/Rbvx5^w=jj +k% !⨔xwua|$~Uv:ZA]6Phic2YEA.Zf )%*k _`r*Tophuswz g(jkWcb0<2j1loRR|z:lJҮW6Oxpys;Gqj%~` M'78Lbd]n2[Wab9F!VaduUT!Lt'=? Azztn\&h GsK#ғ#웧u .dj(T̷}=2pAU`ĚS(B^[endstream +endobj +3152 0 obj << +/Type /Page +/Contents 3153 0 R +/Resources 3151 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3154 0 obj << +/D [3152 0 R /XYZ 85.039 781.388 null] +>> endobj +3151 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3157 0 obj << +/Length 3106 +/Filter /FlateDecode +>> +stream +xڕZKs ϯm*çDg';Njh-u EzIjlIJ rx_x~W,,*q!T$4I=\:rA~QK||k\EZW'l텹Xi-BMX޶9PbfG3{~5U[7u⿛}w궑A}3Wa@|χⰈ2Xƴ|:-;oJTǰHN&Ǣv.DK9Q@0W8~odf!\Ty?,·6jgԻ)YCXךޭUM& i1/ŐJw4[]moNmJw!ggδUuFwY"\/9`f<75Ѵb52Pyn]y}3Q}K5g9 ܻĶJƙrO}˶J@ȑdSO6ihG4`N)fvCBq+! +3ͬEx;$7q+8\,l3 ~GS?NVg8B8<Zл? +K"|ߵd^ۋup)2 "e;@c)(UDI<Ez:ބ` +,s| D< p,M8ᷓ +IjH!ؓಜ$K|Z_8Q5ȈRhDev+qB UѪf[ +h0ذU& r"TovaN.Gn}a|ʆ_lUt@VH_ؿ +d¼ÀyPfsu[Ñ\AT||+l`s1 bP#Gؚߏ. kq:B]cc'=;ctSj49f@WS5hB;lUκ+_>9yg?vo72q1"v{!"̪gI99$n#jz Lc:(GȺ}*!@Ƨ: bB\W⪼y MEbT?Zg q4 %L2qCy[R{g"2_HERcqcI8s8;"0͓ȝZtGu 5N?^u\io֮/|uA!yVa' e +gW豏t i:`Fź +j%evOv]K{K <=":;ZX_E~١PD;I3͵Z(PAZ0kNzOj_25^u87'#ZicƷҥ$fQJ0d9k4$4ڃvb֍RnɧAh_?^ _6=<n΢{ Msopj7E:<-VFBZH8o"wClmV~7T#F݈$C7>{6+EqKB'jd[J4IᬞPEa.Z3!6or`wQm11+C i4/ea槹4?_@ӳp?endstream +endobj +3156 0 obj << +/Type /Page +/Contents 3157 0 R +/Resources 3155 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3158 0 obj << +/D [3156 0 R /XYZ 85.039 781.388 null] +>> endobj +970 0 obj << +/D [3156 0 R /XYZ 85.039 761.463 null] +>> endobj +3159 0 obj << +/D [3156 0 R /XYZ 85.039 667.044 null] +>> endobj +974 0 obj << +/D [3156 0 R /XYZ 85.039 573.327 null] +>> endobj +3160 0 obj << +/D [3156 0 R /XYZ 85.039 541.802 null] +>> endobj +3155 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3163 0 obj << +/Length 3027 +/Filter /FlateDecode +>> +stream +xڵZ[oF~ "; +@Z-n(RKRQ܆3dy/0z̹~s55K# Y*7Hjs͞`/JVx-/~3幙͖dY|2wHԹ_tus˓B9ws?u/y_)Lr{|?cŇ"t8@6yެN Kg{h{ʲ"7 +\8]'.+p̏NOXRQ.>̅nƶ\ˆ̹ŋCVt_q)y9nIP!vbZn=߷ +vms(fw5|FS} Pr]vs:yJ{@5~⴬xre,X%p䓐l;0+M^5cp='IMFm/b7MY-*75:֢r2EaZ +W9Z'ַͿ{W@6LSgŷcѫGɲ|#vא쁠:c +YzT^t>i;<< A@BRZuF/)V(6hhH=am_ tnǽOx|?,+ [8k?S/=YVt;vqkW֬f#J,ю}wB4XftQ`y61V$,r z=Ʒy ?ޯ=, |EE^0_\ozVʼnKvESfNd +!/4P߂PrpG[ _>p3޼UU +ybB[v BB#./s0L ; (O4ƃ1URY/Yb֝&ޑm&muH /X_`ر[TB~$C0tiaY0{nacĄ k#kmth)uJ&ەv-9I&%Bgc]$4Ё"F^ q$$w&bCݢzZloy0cS߹r9^CHLx;6[$g+"_hGGYf1xl F*Q>RM:crI"JN\d'@5%Q! јY-d!hr$CG@D$-gv:{`8 WП5c;t9{.,'! !DpF.aJ4d- +^芳HpqįB<isS2#%ڵ6FѱPxEh#,F$| t6آٵ)yP Lĩ}5`,0]]B-o4fOwmƣT'g=q 8H;}ݲj! c1KHiĀ(IBTPfm8is #]H #R8Ɛh @U8!$]Fz10_rӠ +Y  LP:8*3LjRDO,QQ@jm*T\²m#R5vI^AccAjSR,EК " i^ą/9hLe-MVx05"h\ +JsH;bKvrj8Fu13۳ xH)j,u|KpaRU֞x=z7tx^a#GxƜ1:I>mǩhӭ%kFvE0LٰnEq+i Qɓ(1pB>? 0yUH_wMJbOKD4jte2B ;h;%T[ojXw R2,nYRQ4*R: @@>mɤPpmtoWz.J]09;w5MU}@i) bQr/WtǸ|9 dT]$9S } !7Ɣ1 ѷueS`fG1%SGO7+r\Ҵ sθ`Olը\~U Z#pvd\۠aZN2e'F1/U_ԃ5`ʲ‚ Ӷ6A`}6<$ ^C՗d`@vz]Q^67(L~W~J]뷏 +%A4=F7X -|Ƙg~?n*@8@8&֨l{9dLѱ4%8#GNCEl:沆o`yFe8/ ޯfÏҁT*TERxc(: UVTOմ*sh 0bxDvCUSf.Jc罩tg]RĒƻv[W'.' +ޫ6U]ȱQ)A ajgZ#nHs#[N-EL2ዯ憏'(ʯyG+^5ŁP}[tVY_.:H}`QWOM;UvZDٕ/YF+؆ +a}g2|,pxi\)VVrF .rVv"`*'-;n)xOݿ'pW?ΆrUp1弗$nŧYpE4l&RwȨ i1/ endstream +endobj +3162 0 obj << +/Type /Page +/Contents 3163 0 R +/Resources 3161 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3164 0 obj << +/D [3162 0 R /XYZ 85.039 781.388 null] +>> endobj +978 0 obj << +/D [3162 0 R /XYZ 85.039 761.463 null] +>> endobj +3165 0 obj << +/D [3162 0 R /XYZ 85.039 736.911 null] +>> endobj +982 0 obj << +/D [3162 0 R /XYZ 85.039 709.271 null] +>> endobj +3166 0 obj << +/D [3162 0 R /XYZ 85.039 687.41 null] +>> endobj +986 0 obj << +/D [3162 0 R /XYZ 85.039 537.42 null] +>> endobj +3167 0 obj << +/D [3162 0 R /XYZ 85.039 502.217 null] +>> endobj +990 0 obj << +/D [3162 0 R /XYZ 85.039 394.428 null] +>> endobj +3168 0 obj << +/D [3162 0 R /XYZ 85.039 362.902 null] +>> endobj +994 0 obj << +/D [3162 0 R /XYZ 85.039 242.539 null] +>> endobj +3169 0 obj << +/D [3162 0 R /XYZ 85.039 219.221 null] +>> endobj +3161 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3172 0 obj << +/Length 3177 +/Filter /FlateDecode +>> +stream +xڽZ[s۶~虈!xyS^&O$OZ%6T\7D5L `ۥ́?5Y+ۋf̶0ÅgNЛCw;qXow>\.<ϳTb_.(ovu{\_.ҍ՚I{af?^߭._tz ·C1>]3@ҟ.K3[%lˋ*eJWo-6DV?KiX*tBa)m[>0 i>U, +<r[IHl>A{y|$>h9 Z8m'%o} +Ga8Lt 3!Z/4ޱJ2\%H =}8!v }ԯR?x&ם3>%밤 |RV*yM"M<'+dP*&`6pjP(ùx,nT}fO^祅4`fryTҢ nZMs*#_K@1 *o>cmsv6 .c~j+J9u¥!sO&qQN]pYl +> l:FͰ"XHtq֏$rwOmWi$I.-2>;Pjr 1@zY DWW)qLL/ K,já"g/Æ0 m yT6kz&zalظOY~b> lwkroOCNjR'q67ͯXtì{hdp\(> .<:DZe,X-S쥅XN#a̭""ǺYW؁?21C1n>7 H-,m&/V^8.D`^g_ Us8䘻P؇d/&wz ^LǙ [ŐAc?fFKٱ$˅1e'}٤vқ:*?#SƁz!>l#Qg +Ҥ=^Hr+PAp#)f/rAsF!,o}GL@7aMr) Z,:U̘Aap$5˲׋0b)wjІBy`Db;tVQ%N@Y* FM"g=i,;M7!Y2B*Xya"a$E8}Q`I5 PZ a*1O8$jx0{ 9`a.rżKx%PzP4a=oýō4gx녹E*@RbFc1'h&7`iO/CY;v|j )P0 + .b zѤ7+]IpkԃQ袕)Dz d$  4̰T3'%? 8,lQ$>4Ispf#F`hT94zWrA_&-ƉGg2iA^&m +Lx*y0\w>WD}F}>-2Yn#ՆNj 敏(=@ &[C>38BGG8-d<{Q#߂v":D¥+hH.:ʎH*rB[ Xƺ?T1(\$lY +h٤[i(tpRp!x,xSZ(|_ʸ*Rt/f| =6U.؆3l;Ht,Fq.sydu\Ö1U?pTjK.r Z>`}\I՞ +CYQ7knFbBoͣ)ї]?J'HXyԲ#O_F&$@L,#6U&21VL\op;8Q{6D/O|z~X/M'|v1/qsۛ 8p^/ބ|Ĉ9)PWT.:rHKp;͚.,EP?EgGI0bDDa- TZaM6n-:ֲ٫{(r-e޾Lali4{&N8*9z2g699lpL*ՙV`WUBB@,%C +`I`> +d=>e%jҏrKlʤ e:oTXh F R1b`U(f jH8PfBU$WcϜgrI 쉋x[W[Bݡb%ˮ 1$]ة*u qRv $v^Nv24Ɂe%Up_0COMU*.]SؑKqilOGmD{5A!&6S3ڀ-zO)$C+~ιCxa?4 E}9wIAP'm-j7(|<7Z *Dpj ]k? +n-6j.{<02?QVOvbԵ#*-ä +F}/LQqm'W q _O8^dõ-·g T! Hdh֍endstream +endobj +3171 0 obj << +/Type /Page +/Contents 3172 0 R +/Resources 3170 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3173 0 obj << +/D [3171 0 R /XYZ 85.039 781.388 null] +>> endobj +998 0 obj << +/D [3171 0 R /XYZ 85.039 529.88 null] +>> endobj +3174 0 obj << +/D [3171 0 R /XYZ 85.039 511.008 null] +>> endobj +3170 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3177 0 obj << +/Length 2331 +/Filter /FlateDecode +>> +stream +xڥYYF~_! ,d7Λs-,ܭ EQ;|rs4r~|w._N]a-vvRyN#BVuj҂>򏇟!*g[ +;톸ktYQ5G(W+&kpj_JGW&amiie  $U˕#ZӓAe;Kd;ίU";]Vb +^eoĪC פM&)hwqp6E! +I/| "^w`YΆP5 ")QE9÷v:~d~>va֍+DfCnȬ[/MMdڌ +D>ZW~6Q6eKzdK!iS +"PBݺgK- L8q_[3L6|yGBh Z(&3 ,W3]q_k76 #9~+;F+: 'Vsx#V7bM&q—!k8G5M^Z^gf}Hʋ4'6XR p֑$[iO=dG0>45f?l;삩ESa7e}Lʠɪ}]M;͸.NbA H@*B;dfj|3@=1nLE5yl" BDv9 ߈hЍTl=^\64Չo8Q!ST$Mm* TJ~!7>Dd.cf<9X'6!d-8^%V9A XmvB+3id_gARVQD71TA8ká#ZU P2nfmgiy&fD$&H|obA+m ) +s)-}?!p ž+K{ +K+]rn&nb #yﺘt!Rj >{{^§O ?l㉈Bi31Rn~,$;#ΫCj}}.B4{u&.ox-5?y2Hcj@Dw*4nh"]}/]@~'k=s_ӊ˹1f(RFÀ(YY&X+58KQBd_~@tP(G@A>(ӥ8}۸Q^1Z)B|Wʮ"0tI99lHsHUs(I"l  +6۱E'B/,Ja+Um'(юrcCALN|>-Zj(߾vALз&[)Mg}ƆDz7{M [VHt |j=5ynM5ڑdSvKv 6)Kw5܄i1ǚ1&yRl,<5NkqS` `7.TW$^Jƌg_+.ug0~uMD.1Jk0?uM6iPvMZeMm} .aNAk7JC`7g,^?0DtOP0iD%-_*>01k4s IhPۧO44(nlc#UWGz +TO) * +A}W;@MΡ!HZ 2+[~=?t2&dH-̦vwn.~OB;7K>l/(asfK%8\ ^ƷWXg@3m=P6QGVnW,WsY~8n-] iѸ@FtwR40G_}}'}8\] h}]^X*c ̀h޳fyb`` +u[,p0()aRd)\e؃ŔQ6|Eͦ ~V͹c\e\) +G/hxMyUIV)? +n&?7 endstream +endobj +3176 0 obj << +/Type /Page +/Contents 3177 0 R +/Resources 3175 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3150 0 R +>> endobj +3178 0 obj << +/D [3176 0 R /XYZ 85.039 781.388 null] +>> endobj +1002 0 obj << +/D [3176 0 R /XYZ 85.039 761.463 null] +>> endobj +3179 0 obj << +/D [3176 0 R /XYZ 85.039 642.137 null] +>> endobj +1006 0 obj << +/D [3176 0 R /XYZ 85.039 642.137 null] +>> endobj +3180 0 obj << +/D [3176 0 R /XYZ 85.039 617.419 null] +>> endobj +3175 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3183 0 obj << +/Length 2143 +/Filter /FlateDecode +>> +stream +xY6^Q8ˢH +܇\6M%·C[h^ olɦk"L<3I$f$%>MI^{XyuC1a.'$ ,VzϢ{ˏ :K0Mw̾xoqr1)*a꽷 ^|x4wKpP?b@~^|_ sb،~@B엛~ +&hM,`$& jO7>1klb 4hѐ4rymtaumىb:k7ba),l:0 QyF *.Uޟ,6\]gB$4ԒhNn,~͋vgu!ZxaB J0aH3!nW@Ms| i۷,H!j49G\ +<1vP(pa<24 "L; +=h&.t)7gUkMEKխ[cAΞf7}n\, zZp(Gնhle + ҔRnXeсdž&ڏUY+8P @(be֢(+Bz kQUrlmS>^4hƻ[7%VexQnO"PKęh(ƫk20P1x8AOk,"V@]3VO0my]9/֐$ު=A8fQKeׄog T08344[zXҠ[HC/∳XuK.-ُe,i(/T>7$vp78,NGv4TZ%xG"ϸ&;RE君,Mfa˔~ܭ1RϪ= +"}hO,;! .YļI CmwlW~bX/8@ovr גcL`5QA VJ( | ΊTn -+8 v9W߶_庇2g9~^|uqi Qԫ9=xs/Ad{Cֈuofu! 73qxǀ0@7K8_VS z įݠ>ϾK$631l32:V> endobj +3184 0 obj << +/D [3182 0 R /XYZ 85.039 781.388 null] +>> endobj +3181 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3188 0 obj << +/Length 2658 +/Filter /FlateDecode +>> +stream +xYYoH~ 47wO v<`"))*EvMMUBs)Ȱ̄;*vyJTI&AX)A.lFz JLs +  B(ىAB{8##Cۅ@2aEx8dͅEaΜ3lJ}4-(F p_EQpLPr?M@79OSƐư)q̆C$j],LcT@Mfry&V*&z`ǶBgG@Ƞ@CY n` 06BJ%N l&4!e탬UA]u<CEc)X2| q%Q.Tˡ "03 Po>#d=$@ m4M-Cքtb[q:ߧAL <( +Y<nB ^&^`™" rX\M>NJﾜZ &Y 0@8AAJ +;Y? ++@E3Fyn.4Ê Y./:0䍏"Xgd+I%NqNG"6\/;?sr p`6# +7[x +@=S)K}?(: +b8?Oqendstream +endobj +3187 0 obj << +/Type /Page +/Contents 3188 0 R +/Resources 3186 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3185 0 R +/Annots [ 3191 0 R 3192 0 R ] +>> endobj +3191 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [294.66 181.829 400.604 193.518] +/Subtype/Link/A<> +>> endobj +3192 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [366.309 100.534 485.694 112.223] +/Subtype/Link/A<> +>> endobj +3189 0 obj << +/D [3187 0 R /XYZ 85.039 781.388 null] +>> endobj +1010 0 obj << +/D [3187 0 R /XYZ 85.039 214.839 null] +>> endobj +3190 0 obj << +/D [3187 0 R /XYZ 85.039 196.171 null] +>> endobj +3186 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3195 0 obj << +/Length 2220 +/Filter /FlateDecode +>> +stream +xڵX[o~%¢yE*Ѧq ]#rDqMrXV9sfF7iQA̙sΕrsQ`;tFG .ΜA +'\EC{=uR̓gw_#-ϱ0a4f7է3ܜGuu;t/x:.^d*>~]_#m̾̐G@`<ӇgzɁ;g;v\-_At4at:({~vÆHSܩ=>/ +6=8sa'؅um0}bM[X 6 MjQf k3%wMVX+Ɓ탹FƷu-M:-GCC}F^8#X7iAO F1{cpl0 E5DǏ< }܉\wYΉ`bȍE5:$ H*ZZPO(Kf7v fħ[ oVjÉ8+D  t1a-[%(+ٔC nJq,$Oە"Gv/;=g9Ҟ)[HAZ:)AŐp#}ϫىYC,]BWJzY-OVڕU+zQ(bvcUň +y%0^X"G ?鈕_gRE+aU <|F$\2, +[QIO,[^cXق'RNHuBH,$1+3KV+o%:\Ԑ$2V8uLqo +sz| +[|ql1m4Ds[JJ/c"GPV+;+GPJ$Ó7.t)f97&[1Qj4״yZ08tAZ;w\ 3>jeIN-#80Rf)T-:2*u#(3|:Fx#VץL_h g(ZaRsR&H_ҳ鲡*Ԏ(ZAe%IMr(ZACtMoFi#Qlf+҉*M˄LaJWcfOQsШcަTt!-VZʰ2qq20џN0n+,`nXeoz2QqU5B.EuVSZP؏ HQIjΚ$KeW(]bTXyeO,Ε]A+TʧRK@p}TZ}Z 29D4z6Ŵ9PkVwG C*Rzs 8TN)?D} LtIp$rђru @M4czlg`%͛x}1a|dYBuy ,|DQ +{yWox7*]{qԴAg=.|#=*2< D aoSg] 3>R$VdqW .7nO)T4[s+*Yyr"AAHtU*vah;J7oۮb.:m`eifWUG23mƼX9LRڑ3nO뷏EƀG; u'?טVOPendstream +endobj +3194 0 obj << +/Type /Page +/Contents 3195 0 R +/Resources 3193 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3185 0 R +>> endobj +3196 0 obj << +/D [3194 0 R /XYZ 85.039 781.388 null] +>> endobj +1014 0 obj << +/D [3194 0 R /XYZ 85.039 761.463 null] +>> endobj +3197 0 obj << +/D [3194 0 R /XYZ 85.039 741.134 null] +>> endobj +3193 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3200 0 obj << +/Length 1719 +/Filter /FlateDecode +>> +stream +xXnF}W( +P@.AuāPASĚe}粤$vi r/33g %@ +;q> Xy3z'\m6zj,-ZxvE{fO۽i۶,11}?0&cã7?lbJD﵀هI`nysg~|ͦd~G(83:m]̔›}}lpw#Ka0^2 qQ߳^ 9c>5@ӱBaش-G#_-۶z9kDe$z1ѴM\,<{bb5ʚqDmZ,-'yX|n=Y.Ӧw; +U]MIUBj~&2)XqT,&W),~-6i y5 +m7P 6- Dj'8 ܡJ HR8*᢬@T*|p(ֶqXNq~WKT`tLkƁB%>< =P`]%m{%9;`[C%=BSj9v.dי,|dlUMVmKxj=$.W(K}qSWuw vzPոw~p`Kfmzj +Z87p>p9  >6 *{$&3Ø7B>`E~'B0*#QN J8R$7=?k)yێp;&"ԫ:!/e nλO:;mmuQiua@p>Õp,{_lM %Iϻo(t'0u a>endstream +endobj +3199 0 obj << +/Type /Page +/Contents 3200 0 R +/Resources 3198 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3185 0 R +>> endobj +3201 0 obj << +/D [3199 0 R /XYZ 85.039 781.388 null] +>> endobj +1018 0 obj << +/D [3199 0 R /XYZ 85.039 612.769 null] +>> endobj +3202 0 obj << +/D [3199 0 R /XYZ 85.039 592.174 null] +>> endobj +1022 0 obj << +/D [3199 0 R /XYZ 85.039 363.837 null] +>> endobj +3203 0 obj << +/D [3199 0 R /XYZ 85.039 341.121 null] +>> endobj +3198 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3206 0 obj << +/Length 1821 +/Filter /FlateDecode +>> +stream +xڽXYo8~0P,*":o6mfa-ɶ$RXuv\~ñZ'kZ20e |` @y9}<{(,3tN3X^mbnTX) cƪBבB(FEaiAh"95Ohs$˾l*}\Ѣj aٚE4nẀ&5xӕ– PDeD>xGƃc^$@&CONVLFO\EH. N7/qFT)Z$jRm^Y=Iюg\w/x7 yMNtp!`>`m*oV^غi ELJFuF),`&Hm ((ASE^сkFH_!'~6,a^[Tendstream +endobj +3205 0 obj << +/Type /Page +/Contents 3206 0 R +/Resources 3204 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3185 0 R +>> endobj +3207 0 obj << +/D [3205 0 R /XYZ 85.039 781.388 null] +>> endobj +1026 0 obj << +/D [3205 0 R /XYZ 85.039 761.463 null] +>> endobj +3208 0 obj << +/D [3205 0 R /XYZ 85.039 741.337 null] +>> endobj +1030 0 obj << +/D [3205 0 R /XYZ 85.039 513 null] +>> endobj +3209 0 obj << +/D [3205 0 R /XYZ 85.039 490.285 null] +>> endobj +1034 0 obj << +/D [3205 0 R /XYZ 85.039 260.773 null] +>> endobj +3210 0 obj << +/D [3205 0 R /XYZ 85.039 232.037 null] +>> endobj +3204 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3213 0 obj << +/Length 2094 +/Filter /FlateDecode +>> +stream +xYKF+8ET*=ޞ6nֱ9h#$,/ GfWY܃?5dq<3o;fJ(]0\w #׏|n熡D?9rKcN~lRv( Nx&S70Z 헅 /4r~KtGUA/Eiyzn;5%#G vMhE+Š/m ]쐶ER2YR ]_Ō9Y xgJ4S9#aP)GRildtE^7AB;&mb._Q1iy--Kt;y,q884\$i׋"SX +ྒྷrKkC 88l7vkuH`=qr7ipKb5wL)Ê9+hzSZy(:Ag.zY$>%Tlwi3Wņ ;:ICAozZ# u5eɚ xL)`{".c0nm1w̒#r_kyfݕynZSܠcUu#e\--:v>+V +>0GCZ_!1Db8isp'klyHOGS ?#3HSg]]#0;a>jWbG.t K%rW/&%|Jp ٬cd oɼ'v>zq|R11B Ә4fBo:v`QVԣI ⢈G+$Cs%1t Dq)h@%(~A2Q5 +JUV%&YOcҠyCO61\/"EO""Lbj:!m0qwȀ*Oyzbv a{BF$7W<(e+2JO ^<۩ĽiSa,cύPs4ȋE4!qaSFZ~M6@ܝA@rɎ!'/j0'R%aw[)%leiŃ!"2Up9sr(jQl]݈?b܇uV1vƍ?t#;VZ}kCqg[ H@P&o*om)(CG& w4);0q(D9`Bu<Ht]UaHiVPq ed(fuYHp**a=LEÙoͭIвI+pxZ (1?U<.UpP%C\A _E1&Xw *e׳Z1hծh +@H*Qt*aed5*biuIIКPZ~w1SJO# \cƗ@-݉a Ef>{q2 ƞdad32+gtK7r湵nS#{lĕpAF~FW/,e}nҿ "p5~}'4 RQv\.:vP2RtWv0Ά uBS UOaU+IyA9.xB~QHo htF:Y&R ƀ][\}[kFue@zL99TQb9 +^D֩`EٞhJA>Q7\ʁ#{"6.b1nFMNTC"WW>!~/0=נsgendstream +endobj +3212 0 obj << +/Type /Page +/Contents 3213 0 R +/Resources 3211 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3185 0 R +>> endobj +3214 0 obj << +/D [3212 0 R /XYZ 85.039 781.388 null] +>> endobj +1038 0 obj << +/D [3212 0 R /XYZ 85.039 761.463 null] +>> endobj +3215 0 obj << +/D [3212 0 R /XYZ 85.039 672.697 null] +>> endobj +1042 0 obj << +/D [3212 0 R /XYZ 85.039 672.697 null] +>> endobj +3216 0 obj << +/D [3212 0 R /XYZ 85.039 641.171 null] +>> endobj +1046 0 obj << +/D [3212 0 R /XYZ 85.039 311.511 null] +>> endobj +3217 0 obj << +/D [3212 0 R /XYZ 85.039 284.896 null] +>> endobj +1050 0 obj << +/D [3212 0 R /XYZ 85.039 284.896 null] +>> endobj +3218 0 obj << +/D [3212 0 R /XYZ 85.039 263.903 null] +>> endobj +1054 0 obj << +/D [3212 0 R /XYZ 85.039 136.227 null] +>> endobj +3219 0 obj << +/D [3212 0 R /XYZ 85.039 117.961 null] +>> endobj +3211 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3222 0 obj << +/Length 2021 +/Filter /FlateDecode +>> +stream +xZKsWʘż؛:v,f*DX v_~ @ Z)TZP(,ސfME@q/EJɫl֔_*QTS*zOرALSL VO?2^BU +@p?"$"QGPGahEOQt1z՟d.+im/q׵s^%["?O`??dt2r)\4f -I135 +QhPduG+;*%Fa͹)2T6?jצFh@ঁfU`YZvBj"=WK嫺Rǧk2N֯mh-H-C?>kjZu +@6>\mV08ѱs ^ +{FCC`XiFF=lt(r&tuΠaaO}ֻn9L >cb<+aexe]"28wU9b#aCXDDkr3[+a5C5%V/hȖ+@P&%[aVlCQ(ߗb9 E`30ϫa=ʗ|x?Y=VcЅVԦqxq ElXװXeMڤݱvEpJ +0mUݓCWm;bmk`GOH%|5 mKnvӾz|3n:]b3JۉK aH+ jv{ԄG[gm,qzwpaVRcx Ցb{ZUvMбp# 1Vb^n[/nvVa7MB%ݶ8C+MOs6wp~E?Mp+k suGݺ ˍ >Of-kS +tTi3gudaXUi QPC\兓eu#bhhz `pmAW b>zjsiJ<ƎðOf#l!RL{;i&K{Ԣ55'{5/)e@2fU Y}/ 46ҥ;G>QpILS6@ 6 1QUo̠;kT֍}-ޟ"KrmNx\p}\ :g<Ν0RrE+d%vh\Ur7M鸶lP~ l[,>s0r~C?}u)#*!xj7Y,:p;a&E>'" @$>< +\S|RŃ6Ɲ(ΞCG kgpA67K,]n9n35GOKۚ=o1VpլҀ8x&O>Iħ}#خ?8q&{`cendstream +endobj +3221 0 obj << +/Type /Page +/Contents 3222 0 R +/Resources 3220 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3229 0 R +>> endobj +3223 0 obj << +/D [3221 0 R /XYZ 85.039 781.388 null] +>> endobj +3224 0 obj << +/D [3221 0 R /XYZ 85.039 758.673 null] +>> endobj +3225 0 obj << +/D [3221 0 R /XYZ 257.152 764.647 null] +>> endobj +1058 0 obj << +/D [3221 0 R /XYZ 85.039 619.462 null] +>> endobj +3226 0 obj << +/D [3221 0 R /XYZ 85.039 599.133 null] +>> endobj +1062 0 obj << +/D [3221 0 R /XYZ 85.039 360.311 null] +>> endobj +3227 0 obj << +/D [3221 0 R /XYZ 85.039 341.439 null] +>> endobj +1066 0 obj << +/D [3221 0 R /XYZ 85.039 223.65 null] +>> endobj +3228 0 obj << +/D [3221 0 R /XYZ 85.039 197.036 null] +>> endobj +3220 0 obj << +/Font << /F62 1689 0 R /F56 1642 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3232 0 obj << +/Length 1608 +/Filter /FlateDecode +>> +stream +xMoH_a2 IT&nR6 .3lvj5=a0KD aBfٰX 0o& ^NI4 p:#i{ȗRzQ(F~f(Lz(^@/t}ԟt^8\NcO$c[0,Aw@<n0χAHҽ/?vR댱~OᇹȣM(@^H_"IA$IVVݡT_;S7GH}DLD>\8blsyò9Y k/f# +cUevBo jq)gf\ե)֋28 [8$b {="';+鲅PTf`]5I(H dizE;vG[({^je5^^"I)E\WvZ:.FQ-Z5a +)i[~-2 ~S/ȾaIφ:j5 {kAF-8 U=TӮaқaxP7$P\Q 3hPѝְ[> qY@vhjI=ykB[7hdy50o@AI:t`_0󑉆{wdAu}tɼ_$(\ ZSWgb~Gc H9 mҪ4/Wef* btj-_@L1]a;GC*kڴhtb D5ŖͭCfG{j" +:DNYV۲*Kۄdt89tYb좏7S{nk]Mk #X} 4]eL:`+V~{>j۝"gnh[]iFAyçٯ}g Xٯ^-$~Xendstream +endobj +3231 0 obj << +/Type /Page +/Contents 3232 0 R +/Resources 3230 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3229 0 R +/Annots [ 3235 0 R 3236 0 R 3238 0 R ] +>> endobj +3235 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [141.013 726.489 469.456 738.481] +/Subtype/Link/A<> +>> endobj +3236 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [139.346 713.243 202.339 724.811] +/Subtype/Link/A<> +>> endobj +3238 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [141.013 527.64 309.095 539.633] +/Subtype/Link/A<> +>> endobj +3233 0 obj << +/D [3231 0 R /XYZ 85.039 781.388 null] +>> endobj +1070 0 obj << +/D [3231 0 R /XYZ 85.039 761.463 null] +>> endobj +3234 0 obj << +/D [3231 0 R /XYZ 85.039 743.459 null] +>> endobj +1074 0 obj << +/D [3231 0 R /XYZ 85.039 563.482 null] +>> endobj +3237 0 obj << +/D [3231 0 R /XYZ 85.039 544.61 null] +>> endobj +3230 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3241 0 obj << +/Length 2552 +/Filter /FlateDecode +>> +stream +xڭko6PI$(pd/v , +4)ږmmdɐo^d[6@ "9rC77$i4Y7|. mop8LD%fi? (?0W{QuЫ6#,˦nu+E k]3FC|{te>G`爉ӱc2WB3H}3(ykˮڑЀ2QX"{ނ4 kX(B(aIHqa5,M=R3rX-=[.\!jkt@خ@ cuXe)tJL3",j8UD`}U0[v5 eJlmǓjϛ%ԻF%bupS%tt:(AYZ6w˫:!BDc6A"pl`WnGyu~}x-KRxx-k (6E3#2#(Jn1|_n"dZPοjE2*kaX,lI8K(Τ;ZBA?` ]<"[͎ +V69p~w +S!,Pf#?XHxD{( CNJh;2 +.bK+DFq|y zO6| k^&}SK[v[軅<#`4#/H<`[bΈc۰.B.QOY!&"кh9v t3 3P]H$m]Vq=<>`MWӈ lZ+>^W5y'7IJz߱OWESH@E"=H> Rg;Zڊ 7+ 1_OY̢ 9" quڹ%"8Ho|(ٲ!\T&L"ۆ%P0,"`zۡLM"4Z3 t|`n'bSQ>n9ih4.5FB^œT)9 P+j42T| cFh0R:Tהo2VNh+Y8Upx=]kE!q`Gc8Uj"/aVU + >TQwK!GST= : juAZVA sOv&IHy-)cL]Aӡa.ф⿧<שmnn+dd2Ա&0yǍ4*gA\ًdp>X9Џj|u1(Ki6f K>Iknu㙌> D $Oa;j9YQm0]0Y Rb4džD(%sȾC+N'7,ڴvyQ(DNבvX"!gZ KuSJSsjwK($M'#)&)\:\O{aׂ+$*կ ,9Psn0VauR4ٔFc节 Zb|;֊O0"L +%΋5B q˟It'bLAw\zA_l]wAw.d$NGw3N?OOP 1(}Lo:. (LWϲhm#w +Mw{D&n9Ǚc~KI9#`֜3x}M+4fqUJ)$0BUB/ K+[2s3 \@ѽOF7R?V;Gʪe6aB> endobj +3245 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [465.374 560.105 512.306 571.795] +/Subtype/Link/A<> +>> endobj +3246 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 548.677 184.218 558.245] +/Subtype/Link/A<> +>> endobj +3247 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 478.81 163.483 490.499] +/Subtype/Link/A<> +>> endobj +3248 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [223.966 465.261 276.371 476.95] +/Subtype/Link/A<> +>> endobj +3242 0 obj << +/D [3240 0 R /XYZ 85.039 781.388 null] +>> endobj +1078 0 obj << +/D [3240 0 R /XYZ 85.039 761.463 null] +>> endobj +3243 0 obj << +/D [3240 0 R /XYZ 85.039 642.137 null] +>> endobj +1082 0 obj << +/D [3240 0 R /XYZ 85.039 642.137 null] +>> endobj +3244 0 obj << +/D [3240 0 R /XYZ 85.039 617.419 null] +>> endobj +3239 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F38 2158 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3251 0 obj << +/Length 1199 +/Filter /FlateDecode +>> +stream +xWKo8W2bE㘇Ӧ&EHr,ؖ ~AɎKQ$73t|'D ?L8"L'|8gJXDR!<G"S'[LV|u/>-^nljv.ev}g(Pt/A.|{1r`"5lq&Z_e7G͓*%gx9)hNRi7Mo=Zvc N$#s+h|e|z G6'ƿb,u%eY.M 1g6Qijūa1JT5x.kcZZS{CCTq'JM)S+I(q}rp" i*}[)2 U+E A +]ǂnF?sQ5u +,ys:@cO}zo^Ñ$E_ٖ"%ڒG3⮈;j.bz:[`{ٶgܚآPbM(ll9mDJM,7m'icV 2{-0ǧ2N=.\nendstream +endobj +3250 0 obj << +/Type /Page +/Contents 3251 0 R +/Resources 3249 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3229 0 R +>> endobj +3252 0 obj << +/D [3250 0 R /XYZ 85.039 781.388 null] +>> endobj +1086 0 obj << +/D [3250 0 R /XYZ 85.039 706.019 null] +>> endobj +3253 0 obj << +/D [3250 0 R /XYZ 85.039 687.147 null] +>> endobj +3249 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3256 0 obj << +/Length 2363 +/Filter /FlateDecode +>> +stream +xYKs8WHU i [bgv5+H^ohXHO@R=R5 ,1Y(O'lg0 %ў C'&];FL{AgnzO?,(ҳI:1+f*' +>]͊WTz}{ȩPai%Y( W;wf$ޙ(8v&3`GcCh3x˚L S򝳁6O qwZ ^De + i24/I=F2./VTa>2t9K 3KƲ@0f_g[gG4i:,"bf54ҩZ{I .w}1\J N {WA1(pLCeQ=b1n# -){}@gn逹G Ot~,6P}H*=U]uM]7q +('%ֱ(c.@jt04$uj0wxm-5ϔ]2bX|Qkx).@,Y].청e]֝ .}%wfYeܪIX  KR']^`"6u=uǭ}E6٠C+)9dǛ]G +kyѺx3@nhͨgJ~>ъ4376^خT\\'ۛԹ 'A6Y}n vX=/B =CiKL>S-^FԼesnc*-TnoIU>*W*UrњZ;;fH01!' N 0jܸyF@X)jw|o3"60#n?s JHD MtMQ9\_~R@'m5`ph>xJ锧PsdmlI,L[aor92 o"3N-7iB '4RY(ٔ k K1Ӂ>cGah蓵,qO9,Qu9 D&D)`8}af3?z!⿎v6L<ɨQƔ%_E!q':q@ģ{ +A@ p" t8E "Ѩ/9c]Y"dhsgeIU؆ؐ1=U * +JBQ lI6eAk +`r'bT@HSaI)c~f5܏` Ar\l2 /|/(sr=[\PH5HF3>oE%J2i6޺;  G҅@q?R*v[@cB3qr\!;1hGo@E6MY}s&Gd}sfGflf @4CB XuѿOlya)&Tk+ fA0W< ,3/p7,EL^09buxyoA8eF{)w]rm= +rUf|Y|TȨXNO\4endstream +endobj +3255 0 obj << +/Type /Page +/Contents 3256 0 R +/Resources 3254 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3229 0 R +>> endobj +3257 0 obj << +/D [3255 0 R /XYZ 85.039 781.388 null] +>> endobj +1090 0 obj << +/D [3255 0 R /XYZ 85.039 761.463 null] +>> endobj +3258 0 obj << +/D [3255 0 R /XYZ 85.039 647.888 null] +>> endobj +1094 0 obj << +/D [3255 0 R /XYZ 85.039 111.902 null] +>> endobj +3259 0 obj << +/D [3255 0 R /XYZ 85.039 81.701 null] +>> endobj +3254 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F41 2104 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3262 0 obj << +/Length 3108 +/Filter /FlateDecode +>> +stream +xr`ʄ0A夵7t A@ kӯ$*$*a=3=j,gq IfÕ7+%L^OELy[V;Ymu|{z0_A;_q|[{?W< Շ 3~{i'W{Ы8j3>~vꗫw~ (@wo;r2}rva:~yv3^5A#׏xn)A{XZi5A<^"tu( O7ũpgNyu&kOwSW~ Un?EjEɧ5V4[M`$sA.}S\PC]{n2YxnF^jo +K +NoQZBOLW̆gʢx=o[k2\Ӷp-CU遧Zk: 'yhe@* +q&-F@2ux)MB3mxد'dM +>Fly)O!'R#ȁi^]a+@hm~ĺ=&m#mIQ8$m&Z2f$I!;k T#XR-`L(3.!!2.pH p}7π0D*(LWZ*hkti Y2`ecԺ&dYaJN-S|>=ĔpCtD##|tFvk!$nRsaF[{ 2n7}1BM]ZLȘ0kr[~3ehbP'B5q 73jKXَ4-!tuG" 4Ǹdh[.I'OS&$v pL 2$^| #Ƅ^/<ޞ${/qEVMuُ`Q`!$ YCh8<6*WLu㽉To`t .EVAT\Git7:tB_BN௲1&Ãyɚ7^qW`fi`O8A&{ιbyrma(ol\zQNRVZs^Xs%Ӗ Dґ%fNr2PYI1uua%2vqx,LAV70 +1a:E Liwy Bΰ9\ ˭4S)OMԙgyQaV`[yH@@XdR1<,IжPzsmPZ=%\5"au'.F#FkMTLCnFb%qZ,X(bAI㯥j_^4&kmWT^GT;1Dd곫̋R%`fq6 k"GJhSr-v0<)i"C,1Ud8mK݀fi.Gm!<@+qL;lh'4Ę%\Jp{ &n7)*>M1q פ4~IZ|y{e^},vޒM >A,. k1fEj)`W9 Xj>A+$ {GcQiyd zFs7YC9$1}ck17%&X"h l*D0h&u#$PÙ*LoJb2$xQ^>857Pg k0&9%1TO:ߑZBC&DY qG/?q+ I'r 9ScOakrٵ7Mk?l@̼dhg* By<Ԃ S}R%\ž_(g +V_)CV nvendstream +endobj +3261 0 obj << +/Type /Page +/Contents 3262 0 R +/Resources 3260 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3229 0 R +>> endobj +3263 0 obj << +/D [3261 0 R /XYZ 85.039 781.388 null] +>> endobj +1098 0 obj << +/D [3261 0 R /XYZ 85.039 691.087 null] +>> endobj +3264 0 obj << +/D [3261 0 R /XYZ 85.039 668.014 null] +>> endobj +1102 0 obj << +/D [3261 0 R /XYZ 85.039 105.97 null] +>> endobj +3265 0 obj << +/D [3261 0 R /XYZ 85.039 84.109 null] +>> endobj +3260 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3268 0 obj << +/Length 1797 +/Filter /FlateDecode +>> +stream +xnF F47'qrHsĚ"rh߷ r)7oG؁8 mOq~/ gNջ:x6'Yzfvm2}|{2ĺ]~ַI[돌~u%w\_;~k}ŗwϣٖ~"5`ci2~ci:^зjt;{waxp;Ic8nd|G|Fv +>S +xe1z~`j'N nW/#oV~^Yi [w'D52SU%B!Q DċGÒ5uT^K0."%tqo Ҧ&{W*$E˦xg=쏎!([\_Mޚԋ!|ȃ,|7g$+A߉rGx}ˠߠ[xsҵI3lo(hEb*F9g.3~3%1S83ԩrD&-#T/(ԕ> endobj +3269 0 obj << +/D [3267 0 R /XYZ 85.039 781.388 null] +>> endobj +1106 0 obj << +/D [3267 0 R /XYZ 85.039 683.504 null] +>> endobj +3270 0 obj << +/D [3267 0 R /XYZ 85.039 661.643 null] +>> endobj +1110 0 obj << +/D [3267 0 R /XYZ 85.039 503.514 null] +>> endobj +3271 0 obj << +/D [3267 0 R /XYZ 85.039 479.532 null] +>> endobj +3266 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3275 0 obj << +/Length 3307 +/Filter /FlateDecode +>> +stream +xڥ]s6ݿB㗣n*$L.3v:nk;g^hxHwMb|}ngg@->|◓˅E,tX!7Yxg{?O'a(T]<`p»F0 ULynF~4"ɚw ԧ7S٪fnu<*;s g'l. (qk(K=MQXʨ.#ɉOw(d[?h5~?W#( rnq]ϱ4\"O{BD `[0 ]V!؞Peך {w|@I@ bWUK*4]owE…/xãl:;"dg֬\}4e_۬E^A~bTam +5n.M$|ĕ(7Bɏ]r8u,bŀ. +iskuW@H|~,6pѠҸ) &ËSx]6@Ѕj!l6M,dGəhe= -!] d { j@Ҋ0 + a:=0}O3D,CU2papJdoNy\R%'\<Avnyqu4".K F!И(hF&9?$>a)4Q),7bg}?28aN;9`?gU3h #(Wˣ[b{Vq7 )BH.nd!E>joldn:FS@)2A#mj0yp0 +,OVAlūgi]p&[QҒBP*aԡJj#UiqD"9R"lt $xpQl vôva䝙j Ƨ:!ipx\FCi =}1n1)a0lu+pzs/w_GaC5R)!T07S/S*0Gi)%)?I;HVƀc%9*EX>)1kep bxjՌ(c0.I9㋑N\N T+_]n̡o +=N +G[`o)h|Xq-q/ƼBi7TS|u:E-j[0|^ Vi*/ -n MHv'  aɆ'@Ho(=XE1Ius̰~W7 -"Uxo%MogśaiKluP1`]uD!ayyoU<ɯnHp!_ț5@QbH{$l1,eccO~ٱmuvoR&BfA&*4[Wtea^3yl50GWBzZAɄ1n }݆-fk^U T~B4ʆlw +sMMo7+R +7m&]XJX%9c7YyFA3|K\ LoqRnǝ#6u4u9s; Ļ`p)%FN.XwJ*.N%Lƨ)w[> endobj +3276 0 obj << +/D [3274 0 R /XYZ 85.039 781.388 null] +>> endobj +1114 0 obj << +/D [3274 0 R /XYZ 85.039 610.729 null] +>> endobj +3277 0 obj << +/D [3274 0 R /XYZ 85.039 563.392 null] +>> endobj +3273 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3280 0 obj << +/Length 3404 +/Filter /FlateDecode +>> +stream +xڥr8_PUțxĎRֻ5%%RCRQ@Rn*@wl,g"ߴxFF(ݜY%|8e5L+qr~ٖ[hD[?wu]q$ #cz;0qp3az؉^>w?lvqsy1sC3E>Ok7vfn0L;G3wMs{}6;kވO aپ'eFa2$92 +xP *w0nq4/Ms>8`YlR 0LH 6jBd |ެZ H-MmBXՀ*_mW҄r"(xHYiŒAUb͛a8wFD&UyJk7Y쪌.$p! +6"kx]GBYFC/+,0/?KjABwØ FЖ^I^(/cQYAq,6D9r/$"O#8]cÖ5,&M9A=Z'D{^ӢI6.k޳IR|ӊ yI ꖜ׀Vϱ'-AgLK`_hۮ \yGV=lۖ=y&H~ؑc5E{$oo@єx2WS%q9\&5AxMY-x[??_=c / |}~[Nlnp]cSva4T=AWB-]RM i4Lz~%V[5f~UpdUV޼b?6dt4 5/?A +ւ_٢~-)M$tcD㲽696D Mb5Z\4e?ZxÐ:So8􃈜6(b+sqcgo_I?dyg; ݽLz@'b-.%/,`(RdX $x)ydv!-Fx ulK2ҐyyJ@PeD<>pS7'%zX"zJ htΟ)<%i_hvr H]_VzNʀ7ڦn$/)pЍɵ%:E%YI< AaA,1'.g -BH= h^7jܼс;Wn`iޅ^tg]G~ `G#mݚR%T%u;|$Z)G 7Cw/pagnf(T5!rlBz;G3b0!:_`3;!-2JT VẂzAiGY3mTN\]1;˵(;]Re*13d)N͊+f*Aj-$YC?⽹N^ZJU +&=1;@`T9#9P M't#8n8f12m8p':ߒfNh$I0z"2 )n$H.(/uEYd&@"z^eqBr7"JT( ղ6s߀}gY7eE8m3侅vXv,ɹj/~ޖn*q7w}HB9 P;f[%r9^=9N86xwCu~7'mX1D?7b[MNqr+x6@9GVn|[↴s [\RL֜,(cmD:TV-ͯ5^vEM+_Ds߶y^aL@r>uW@HNa{2e^ + :ۦR4ޑR0'࠶~X +[L;9T 9k!ne#*/ .`7umK-1 B6w0Cf,&mkEDѸ8r!}l b!ZJRm($3 +\35!E]ŅMq፜…Xɰ4;R4cei7>nGAoW7UtIAX≉`Q7δ4<#VI +.:m0;,CO:$I},N<`J<|{-@3p:bD G` C/g𺸋> ^FIsjz7;n'CK[>R2S +V9W5&:Dơwv FniL(Б]?i(tg6˄ָG*ojh:U$T4c'AsM F [l_gF>Yw p%`wcEE`7K/W b/^~q&O.u_at +ԘP'اṒ}< +?=H6@i,,-=I` >":x- DBSY%?ńqiY: +"` n8Vh{uN<'e +MV&×tl̆E:IW fVzUJ Bsfc.A$ʿ?\|ESO_]'ҏ8`S^Սbz)!iIҲ:R=3£rd؞i; ߟ\ i:axH3Ȃendstream +endobj +3279 0 obj << +/Type /Page +/Contents 3280 0 R +/Resources 3278 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3272 0 R +>> endobj +3281 0 obj << +/D [3279 0 R /XYZ 85.039 781.388 null] +>> endobj +1118 0 obj << +/D [3279 0 R /XYZ 85.039 475.077 null] +>> endobj +3282 0 obj << +/D [3279 0 R /XYZ 85.039 456.811 null] +>> endobj +1122 0 obj << +/D [3279 0 R /XYZ 85.039 276.834 null] +>> endobj +3283 0 obj << +/D [3279 0 R /XYZ 85.039 257.962 null] +>> endobj +3278 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3286 0 obj << +/Length 1706 +/Filter /FlateDecode +>> +stream +xڥXmo:ί@d ot%ڲݖjLb8r`N:$sxuꃮz9`P75Onk|íGWڻNs;ϗW|jN||Oo'Y~}LoZAYޘgq/S>Fϵ_;p/}#5]Zn߸6Wɟ|Vځ;t]g0?n?.Zndk(/c +!`rHPi_Sp|-5. \sa +*Omx &c "c +VJk MTYb)Hƥ/Mu'×)U[@Lw|ӕTNվCsY RPw(]{&ѥD}78/ɣfMYzfH< Q + >z_xA͋ǧqӛ"yn8GAl <;j|;;20^Oo7B +:JqH]U=f4Iw~:"39CD젡S2S#Pc,>j0`7qZ:X9n0::=:t z戛(0N{m\oרE3(HU0Dgy8oZR\8LWj qr?m Q'%P &znrjwzB:qO}|NB<-{8;GLCB~E>&=m68r:V̓77sP86[Lu|i*qlwgvo 6h[ӕ {}cɖw gYmLg;Ci;roѨ^GN?z=|x5Nendstream +endobj +3285 0 obj << +/Type /Page +/Contents 3286 0 R +/Resources 3284 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3272 0 R +>> endobj +3287 0 obj << +/D [3285 0 R /XYZ 85.039 781.388 null] +>> endobj +3284 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3290 0 obj << +/Length 2490 +/Filter /FlateDecode +>> +stream +xkoF~cI)gmq E$e'+Q=`ػ;;;; ?^/7Hzs8-Wn v\yF!n̯=u7ׄ2_v00Ag0d:{3ƃ8'7~dz{?w=DX[oƃ?_͏*GE2կI{xI^0pB:]R=Sj*7q8 ׉ceq0 ݛwx~#^0'>7/P4g<[t)ĪMVߤMoE&&F$]2՟.ׯN0~Hw"xYYW<_EfE-aY_aIt"5B/;cbWyZ i1FwHǰV*J^?NVpp_IδK#Ȟ 99V[m//uTilv1L: S1ʼKm[}>Y.r9w6L ;/ҰzĴܹKȗ|ʊ'-(DKQNQGY~^}EFQ'weoJc66+^tpU6vZ6-maѕ4)@zjFn4.P*4$P զMܔֱ#1TDCߋ ?rQ@%*݇=IP=/S]ןŊF\O q9 {Fvp‘91Cw ŪGEhNOʊGu]K =y}(+T"'FQ +(WJ0hd9އX9'NDIdl~>;Љwҹ0݇YׁQfO80/!.[W>?5'hjU +:0 Q~jJm,=CK(Ų0POaL. A4[ # WX1'84tW7 J Y%2Ac +RघW;-)#ܵ1'1s$עs49CkŖv+GoLu5`=>.lqhd9]} Z1ET[<#D3X`|.#Ioo+Z7k[u}3 JnFΥl:A>ѱ$N)c> w`O]w?*#1ߓdjEzG톻_DSp9)oΎ!PƦBDanj8$OY}'”B<2ˑ? CtpX5:9w)ਡRa*|&< *s,&9%OjTeV2RQ_f"v%3(e-1,+dLpDQ~*g("E1̧lѧ%1Y4Bޒ8TE*]E'h$A-o 1[ŭ^#fnnpI2"9j ]25b;o 2>oD~%߳@ T$qHs䠵Z \r,)GafK1 g ėCRrO0̈}TRY{ BE^rE1a1m5yͫfs<½w%"'~{ب BD&^"YM*;NxTaЖJ44 +CGT{faIN|ԭw]q#>Bg@ OJʃKֻ[Rq{ax3YϢ??qho1fV_uOzV/qSq0m2/tVv$-t\R79W) ;nqޭNP2 Nt$~UQ|)}|N8Zj\׻?~Uk: g&^Q#!IB*CnjLz8vݔԇ>orJ| l޺ 749M\J?q3a@1"ZwXYs S*0 T"`r.2dsy2U eYPäZ9Z٩jSǨv+퀉cNXJbNPP(xg%p"eFN,lhYIB@<գFoP-_PG m{NAQDzGNdSP#D +7X_1v@TrQՇAuDNAa@^zە|/oq&$2eڭf،!42O%͈6\q+['Z҆ *|kۭ\/qDA`x7JN"ʴQendstream +endobj +3289 0 obj << +/Type /Page +/Contents 3290 0 R +/Resources 3288 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3272 0 R +>> endobj +3291 0 obj << +/D [3289 0 R /XYZ 85.039 781.388 null] +>> endobj +1126 0 obj << +/D [3289 0 R /XYZ 85.039 532.001 null] +>> endobj +3292 0 obj << +/D [3289 0 R /XYZ 85.039 511.008 null] +>> endobj +1130 0 obj << +/D [3289 0 R /XYZ 85.039 427.088 null] +>> endobj +3293 0 obj << +/D [3289 0 R /XYZ 85.039 404.679 null] +>> endobj +1134 0 obj << +/D [3289 0 R /XYZ 85.039 269.796 null] +>> endobj +3294 0 obj << +/D [3289 0 R /XYZ 85.039 246.478 null] +>> endobj +3288 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3297 0 obj << +/Length 390 +/Filter /FlateDecode +>> +stream +xڥRMs +8Cm2Щ:SM !fɐ]v߲{pDZƉo[t bR-8œQ46bskM{@"A$SLbiSogiD̪@ڶh3sFa,|"7/^; >YQ5"!JMK}  +)S:@;|6EH{y&ݹKɹoK*3ZםØF RY99[^Rg8)M.-n۟MpR>[]>bVJGb[JabUOSH(W5=bBl_?ѸLendstream +endobj +3296 0 obj << +/Type /Page +/Contents 3297 0 R +/Resources 3295 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3272 0 R +>> endobj +3298 0 obj << +/D [3296 0 R /XYZ 85.039 781.388 null] +>> endobj +3295 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3301 0 obj << +/Length 2374 +/Filter /FlateDecode +>> +stream +xڍYo6_[XC,mYn{X=06m %C'~e)w +~.OceEcw'u|aSB{bpFY+Iq0wƅ"O_~M],3w q.׿G3Ԕ3Uɲ??l!ȷғPċ4{owąN666{;EPuM ʺ-JLZ]IV*tTw: ΒFmBn 5w}2OZM6 +!$A+Bkqg01~GFIE4qW }HJ욛>&E}%kpg!}TT>2Afc2U%tlB'׾B scU&HQ +U^3Z_T +S:mܪl=<="NTʖ‚,B @ä=YvÎ܊Bێ^x6eP@Llu>3^ǎ^jvlC܊˓w,2,V#93_A> VJ";;7ʮ9I< u-5+'{"4'c'NW\׼ya`~{CD悚]UD+%H[5a'zj>HO^$swb%T)q]dЎpvȽsu7FgU,A:W  +Ȟ(b$8%mG> E@rnBj-J(󣰥SQrGAm皎t{B9=7Sbj|93Fs2hRM.\(chT92/Ue=hFI徾J5OᎽ w&!# k/lb9> endobj +3302 0 obj << +/D [3300 0 R /XYZ 85.039 781.388 null] +>> endobj +1138 0 obj << +/D [3300 0 R /XYZ 85.039 761.463 null] +>> endobj +2147 0 obj << +/D [3300 0 R /XYZ 85.039 667.661 null] +>> endobj +1142 0 obj << +/D [3300 0 R /XYZ 85.039 667.661 null] +>> endobj +3303 0 obj << +/D [3300 0 R /XYZ 85.039 642.943 null] +>> endobj +1146 0 obj << +/D [3300 0 R /XYZ 85.039 597.507 null] +>> endobj +3304 0 obj << +/D [3300 0 R /XYZ 85.039 568.103 null] +>> endobj +1150 0 obj << +/D [3300 0 R /XYZ 85.039 328.241 null] +>> endobj +3305 0 obj << +/D [3300 0 R /XYZ 85.039 298.837 null] +>> endobj +3299 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3309 0 obj << +/Length 2319 +/Filter /FlateDecode +>> +stream +xڵkoF~PD4]Rd~p]qrHb%R2/TTגـ;;;;3;ϵ?ǡd<}Wxy5<k׋B\a>) +ƾ&^2e~tn\6*@l;߹ݻy/vu?G?{e*{{$H y1zkz̻.1S?q ` Nִt4D9C8$- d4s >yDy)S%ϱn*ߛr$=g;N6NỆ>1\[hm@DdH,ohm_e6Dxi$;T++K +'`LS)* MHծЁ *ơY;tH\~ "g o ڲðHk0+2ej1;6xX- u9{06 K,t-=d~^8C~9PTuې I +Y{HM=E,6 +֚ dasg=4 "ÕUU(l!OW?ag㩊!&*bÏ|5}s!FGR +KaY|gDI&يYVop#!Š#( R!Ta`-^R3xā3a &29-=/Qz}n˵xwG6ukqÓ,b)(m_,UP&^mdu\93u>]aalEXU$w7ɣt 4+ϕ)uzNĚ%a8J<>rfŬC5-ш` 7H()/[1m Fj𤴢]&-VxQ c:{2mŞW9 { T%d[eurf`xl|D0Ţ' b)L08B<,\qADbtQX?E=څ )o]醚 [վ@+-jnt/߸?iP4!-"h }܆?%aEʷ:/$px߮~DKoD(<]c#[T} +i(Y=DEComn~2(}[mW_] < w{_aPhKҥ&4_l¯OpF5_}` ~Nd<!G'gw/7R?7o~~a~{]]ge 5G[WCg8|ۘ||SlE^eV|}?NWR(TD4Z +(O?rUa8`g==endstream +endobj +3308 0 obj << +/Type /Page +/Contents 3309 0 R +/Resources 3307 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3306 0 R +>> endobj +3310 0 obj << +/D [3308 0 R /XYZ 85.039 781.388 null] +>> endobj +1154 0 obj << +/D [3308 0 R /XYZ 85.039 761.463 null] +>> endobj +3311 0 obj << +/D [3308 0 R /XYZ 85.039 736.911 null] +>> endobj +1158 0 obj << +/D [3308 0 R /XYZ 85.039 508.6 null] +>> endobj +3312 0 obj << +/D [3308 0 R /XYZ 85.039 479.196 null] +>> endobj +1162 0 obj << +/D [3308 0 R /XYZ 85.039 171.71 null] +>> endobj +3313 0 obj << +/D [3308 0 R /XYZ 85.039 140.185 null] +>> endobj +3307 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3316 0 obj << +/Length 941 +/Filter /FlateDecode +>> +stream +xڥVmo6 _a'Uɒc}eY[һչ(\[M%g;GJr_a(ZQ"E!e6f><vZZ^bƂڂбOKg3J"gerv7r9' ЉG̙M^iM\]t2#s +s@2!{,~D= pD "rmVMcNONf8qR>%gY!<D1[ק^7sґ8v4j R4+*(I2oL)A2wum>^^v;"vR7szcx~U?G |U#HV#UO% xTXN'xz>UT8[U*U*-p.9B +&*:PžTbNI#P*Srx!Anbb֥_ *;iV n7+g1)5OFÞE>4: o(A- +*8Q(PEMkT}sht $68`< ,]"{LX_HZ3endstream +endobj +3315 0 obj << +/Type /Page +/Contents 3316 0 R +/Resources 3314 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3306 0 R +/Annots [ 3319 0 R ] +>> endobj +3319 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [237.716 552.867 359.98 564.86] +/Subtype/Link/A<> +>> endobj +3317 0 obj << +/D [3315 0 R /XYZ 85.039 781.388 null] +>> endobj +1166 0 obj << +/D [3315 0 R /XYZ 85.039 598.573 null] +>> endobj +3318 0 obj << +/D [3315 0 R /XYZ 85.039 567.047 null] +>> endobj +3314 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3322 0 obj << +/Length 2904 +/Filter /FlateDecode +>> +stream +xڵZ[~X%Taќ/-"qih0+qwIYs]#Ea˙3Ѫʼn)n\&oֻW=̼{:;k=3 Tljht,(]zNntYjHxt.~]^,UƺY,Mm_y # +n:tJS p1tMVȲ->L#ny`=2Slg*ڔv)Q Ƚ3qOpھ/[Ŧ$5BgNK&@G%lnD"\ϰUEqJNd-jöwaEχm䆩<D i۲y l3QU ʣÂH^'-p \n{_Y3Z 2(Zba*0SDal64VK}]:6ccgrod *P%oKp7ؔJ8q?:Tk}'Q +p Ŧ۠R}͍aRl[4!ŲTVǮX:xbfخavӵAZяMτmf?7ưыbPp`nc0Y;]v!qEHjDޕ89hPȺ_IxrE9Mj"?bA-krԙ$jx)8ю_ +我iC1DW'/ld l1ga%}uk1[\z˘)ǔ+Cnqr '$VFO5>f-EI2;M'e4{ўa xtCv)+&aV(VQD"r *%v!'2%:qC`ƽFuZ ;EQEgD:gҙ Lys +; fkK HRsK*ƶ$ۊŃ+1Qݚz4zv'yӛ;x=z%"J=h-UejS5o85 +kd !'t0*Zsk!%,Fp,aL+ 9T{S GHt%g2p؄C5GCD$M]3%ݧEVrQm5k),NB˻gp +P6)fܟ EnĒ_E:A_,=7.O|sz$Qy`P̟txrg +2HL9aa%%T)`13V8z7}<#m2ĘC6X%xjA_tg}=#ɥ [|놿 +\8[3my[M86(;3 6* 'Mt(ll MǶ9UTp}*d ʪD@@6ap؛xL6 + ןB L#c2` uFq@)~'3& my̕g|~\: i?KKjI VIżۖ1yjk Jʨgv0ŧ-O;O^l2,_|_jASrTis #&NP`s@cC0Z2'I +{8Qbr|B~/ܐq}~u [9oxI1!_ n4pC9vps&sqFBk# rTE8,֒ᓴ *Ȧpf;m_"nGKrp:> endobj +3326 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [425.738 463.492 509.276 475.182] +/Subtype/Link/A<> +>> endobj +3323 0 obj << +/D [3321 0 R /XYZ 85.039 781.388 null] +>> endobj +1170 0 obj << +/D [3321 0 R /XYZ 85.039 761.463 null] +>> endobj +3324 0 obj << +/D [3321 0 R /XYZ 85.039 666.319 null] +>> endobj +1174 0 obj << +/D [3321 0 R /XYZ 85.039 666.319 null] +>> endobj +3325 0 obj << +/D [3321 0 R /XYZ 85.039 642.749 null] +>> endobj +1178 0 obj << +/D [3321 0 R /XYZ 85.039 355.479 null] +>> endobj +3327 0 obj << +/D [3321 0 R /XYZ 85.039 326.743 null] +>> endobj +1182 0 obj << +/D [3321 0 R /XYZ 85.039 144.576 null] +>> endobj +3328 0 obj << +/D [3321 0 R /XYZ 85.039 117.961 null] +>> endobj +3320 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3331 0 obj << +/Length 1621 +/Filter /FlateDecode +>> +stream +xXmo6_yBMDȇK5-0űc-ZrQ} F$>|k'Jl ce=m7Zy޻B4ݧSZ@@ n)LRߢWM3<cO(.@auF^u9PWR- ahj1sk `u +yDdҲ%S)奚tGcbiwǿ_/^d|7>ȿQelD's6- T ,Wb5C(4Fx:ΪZZRd ]s 1}ߝ:'B0Fg8,*_qC.,:T|Qb/s$PKXF]<Pܧl4͕ Y!Ou JWi1@kElHJu5Gr4SRȵF +ٕc*E8ie/`[\Hش\wZw~[Ns3TCMX@-Gg5BG߁㕓rݜ-tcZ׳"pY!(ӭʂq ` QrVZVw!!ͅ]dNU#guh+7^$˯(IqnK,iqNt٬^R)k5[4"2 ʐ4YҲ2410ME%Bh¾|FIU>[X妩E8mƁ`)AD=-is ?IsdsG`RhkM]Zt +TCZiKSLYFrҜ +e+"R}E +$8-400#bE+ 6TueDZ+)`iٻ.lw5.5Xt✄\ol'vQj!7]㺬Cm(Y0ư|ALl=0`͇^q|]U]ͪ'h>LtXzOx#^pPo'~T,r +FPJJ{G;l3*,mNLa;cBPiAGW,ug|$ G~r1}.'-^t7<9ewO 7gA96ƹ[qY%𦣻ob7X@)=CƎR?tx's&7~ONh^۬ӒyD0Ƀ4Y:Vi*]^R(6˅qix%P"4ݿ7~Q1> endobj +3334 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [361.406 452.141 512.306 465.042] +/Subtype/Link/A<> +>> endobj +3335 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 438.895 308.034 450.887] +/Subtype/Link/A<> +>> endobj +3332 0 obj << +/D [3330 0 R /XYZ 85.039 781.388 null] +>> endobj +1186 0 obj << +/D [3330 0 R /XYZ 85.039 717.788 null] +>> endobj +3333 0 obj << +/D [3330 0 R /XYZ 85.039 688.99 null] +>> endobj +3329 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3338 0 obj << +/Length 3376 +/Filter /FlateDecode +>> +stream +xڵZmo6_ai[IIҦ1.q( ke.FyHjzE"Gp8/ W]FO]I2Uh^D0 %qb$0xmGSFqDPgZaۋRGa{]4\]'IiV*hյIӠܭUuխL +*h}jvnx}똴aYƄh2a&NW^!ϸ: 9zϫ14l5.CI|e|RcbDc +$^jD MwRԘǶ ʺk~WÞIoU8 s@C σQNaZ^ ay3(x{T%?@jR~΃t6]!iώwXvR|P#mJkhLMdqTC+EVM6o5Ύ~PF6ziq +'[`5-m-3"lH +GIN@;t~a _)0C1sWDxjDd"- 77워Y@?@K֬ɆMrlLmv1R{:=( _Chex7:!+/D{:R=(OH!FXkğ،zRn#`E~*HcH6L!ґCv޺#쇱1 $bn([ kv踳lBM~7]6>bxP{hS30LI[" Mxz8lm'Qwag!#g%֞)!:SR?t<B$\*S*pl9x# Z#?.#Cg,pE)B?(6-ҍvrcc²g-liiDkr#/kDžF gzT~1P,,"Y, 9NJ5NǰQ'ܞ| +(;v:Tn'=UʔC,8I$9#1-M N6 vZ +ӿiG({9&gh;7=@@jMl:zm3|Jҵb'9+.-'j +׵|A\a@`}pqWa5keYC rBjq#rZ?oRI)Uj%+/1"\}-%DyE;R8xۋw``u\29v3p}qi];i@_}doo_ʾ!sK0JwFDP Ԅe0+}-WP*y~O9V7z\]Q/=f$5:q%hjf֜> hFƸY2\BTj]F*%\ rʥǮJɴy $ q;oc)Ċj)MτdTUW,#)0%sP7067J33,([pvq7h~~uvj+.^)3ȫ4 ܭdfl&|~ ӎy}t1֞9vrbY"vwtCOT)qa!MW&bdtK?+D#+؅wxpqf+{99eu Ee$wݤD#)J@4:>yu r8LVwtR8O0 \w(R>-3άl+3 +> endobj +3339 0 obj << +/D [3337 0 R /XYZ 85.039 781.388 null] +>> endobj +1190 0 obj << +/D [3337 0 R /XYZ 85.039 761.463 null] +>> endobj +3340 0 obj << +/D [3337 0 R /XYZ 85.039 667.044 null] +>> endobj +1194 0 obj << +/D [3337 0 R /XYZ 85.039 667.044 null] +>> endobj +3341 0 obj << +/D [3337 0 R /XYZ 85.039 642.326 null] +>> endobj +1198 0 obj << +/D [3337 0 R /XYZ 85.039 192.312 null] +>> endobj +3342 0 obj << +/D [3337 0 R /XYZ 85.039 160.787 null] +>> endobj +3336 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3345 0 obj << +/Length 3282 +/Filter /FlateDecode +>> +stream +xڥr_,$x*3;3ތ̦6@QŘO_AT\e@4r=-wU.[<̇ _ EzqS/_ͯ^.RN$Ir;L|y/L[x*nˇ?xwoQ 0VHŸ-@tg٢#F υ ^ueGs44 ?/):}Ϲ3uwg;^];xo5 αׂf(+y 7^r~C$u>瞪`K XۀGGm3 U$.wָd/}uF][?3MPQ#( jd#efP6+bA# pޗ<ԗzIt񲞇"E>*;#•9E]--s78G[m6BXU^ sFRe`薴ۏj,^堞*}sD4*ȕLd5/2*;W0@?pG㶚msy9tZqj "aCO2#iT|~#VH ״ Y"J8bCΉ#)˾5 ǯA~㯜w:đ!}1`h?)" {5h$he֠0p0U +~lZB?Zc~jBP$nǜ3+ ȶlhؾ~u'DodwzCkEB@v73= +-DL`H#pX(|gJ'=̦aT2`l0}ȶA>ɝD*z?zk ;ɬ jWu)"M|5B`%g3B@Ak #O|=A(l"/"%;` H A?ؑH(%ŞC$2V;Q0l٣̔CNp4WS#aY썍$QYWz8՗Bũd@tV;JE SB[۾M΅'2G!RN7~F 8pPbq"Z!WaTŤm)$8NMF5Î'ϩ(kn/Pn8% n t΅u լ܋kxnBgb+{<^QB:46I"\y]*ĩI:~mJN3jqZlQKDUIٖHcTYy+nU +a+jiȓwc01ԙ +yC}?2ד;,css/L A]IϓlWci0CN ^5X[[b&-Ke,c7HPYWmEAz8Sⲃ>xכz>dhr&-ر%{AijߠV9k8\$"{ndo**-A]65_6/ QSة|rULeBNՇr +Xd*F"!N0ICjC^a"*%KHKT^֛V',3hr;;X]=)r:򍜬a[Xөw-}{˦/=iR"tw$>u$|~~`s ]}N +Eaݥ8nS+5C^F 8H|hXM*7yQ#7Sovz8bp°/gQ=Drxlu{b4LeOߖXOc|GWr![bL}K8QYJz +T.SoD`[ܑxwͯcdQwp`H/T$((2ezV4#ͮ + {>?Jntg5=ߙ<$A:"SX;kOT[l)J%U}itF8DW Xc]nr{G",| + >M'aA8LNJ$_{aG <9n$LĆDrB݀iW<.zT0ZM.GC7̒r4i@Q fꅇu!MS>ѥ@2L:c1{ݸKӋO^46+6 "Є +uA^xJ)*2HO(-(̠Kcv8x%+G9Am)7 wHP;'r>Q2n!M H6y\-!SrAlm:j'Ĉm\!+m٭n(!&ޞCbx7d_9Hl-[H#%ā9Czko?|TgVD.U}g~0El#*O*H~H _LZ49$ԇ-ߐX3endstream +endobj +3344 0 obj << +/Type /Page +/Contents 3345 0 R +/Resources 3343 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3348 0 R +>> endobj +3346 0 obj << +/D [3344 0 R /XYZ 85.039 781.388 null] +>> endobj +1202 0 obj << +/D [3344 0 R /XYZ 85.039 229.428 null] +>> endobj +3347 0 obj << +/D [3344 0 R /XYZ 85.039 184.88 null] +>> endobj +3343 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F65 2099 0 R /F35 1632 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3351 0 obj << +/Length 2333 +/Filter /FlateDecode +>> +stream +xڭYYs8~#U1oΛWZ[UT!ktH*oJR4@ia'ȷl76HXn͉m<ʇ8lóǥ-Nޟ!l+cc"E9xzMN`Maa^L¼c^34å)쏋= .l#)?-7Wۖccs{''nO5]#z·\xԵ( ŧyB;FZl/XjdHܨ-p +7kɃ/MOpM5<ɒQuR +Ԓ tR\+)+T1U +PLSƒY.k=L +z9A. +F) ԅqݔL^CBjedI8i%0Q;**a^z=x tAan+чG@hJ]+.L|Y5[ܙM՜r)4\ߤ."UJ2CKbTYOo.W(ʉ<]U5(IY@P{ b@.m+?8o;A;f,plۈ "eeX0Imq#[ޓTۺt%s1 k\ (1,LR]Wmdhgٻ=p_lh\'yMNiJ[/}R^Ҋr_\@< r@fo1 'Zr S1l^rvPڊ%sCVbdrAʫ A @N\(T aaejY2>'>lwuC ϳI6p׼ps9 +9zS{8=#c4RG߬΂E:irq DUnDeK? 8TAخYHFjW!G G+^t~ϵ:] gk0]s>:io@wH3ЯnTa[VOZ᱖Q{簣GdV)cDx) +=ɷ=8G*=i25fLe\V5C>xEBŏ9\X \&h~%o<^##^~Qd5 p=mߏ8?a"A/ t+ŋ]S ~07pۢfɆfw0k]R(̔O|h\L;Pw]ov\ǜSBy͇,`c!I2upu <f\;% g[͈'uY,",m-ZZU'㉯ + }j Cft0WbSngR]Dk[65/J!B[]u[A u9() a<יy2}4j$gS%xDu?^뚒Uͻ$ u q;Pz˧O&8&¬1m?ޢgNO9]ŮnN G)ڎg Qh>їƺ"UG>AaG,5`Ow+wU-` >gֿn_5"Df-茏?}^~:}-\cͶU%fVMUe(2p|uGIld#+sR вx!N|ϸtO:d ~1ĩ?^WDΙ\%ۼm4MRu> Xxxћ!8鼟 =g~/`'\PN߀n0-c}Le7n%S$2lm߸@ 7e 7aM,A-3 +}.V`)#Slb#7#c̺&M͠(Zr6Dpg:]Z> endobj +3352 0 obj << +/D [3350 0 R /XYZ 85.039 781.388 null] +>> endobj +3349 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3355 0 obj << +/Length 2179 +/Filter /FlateDecode +>> +stream +xY[o~[)d\^{[I(vOhh0E*$eWewIItZ/ ˙\JX + ]OVW&ܜypޝ 5ó׋Bd6-ṩZ{2_n_?u>4q'DWGس)r|i + dn.>\]1l:HnIx +seX0\,Rgg50/xՈLs$0pD>ە'Cg/.6[)=?t sdJSZ0u4l.MmhH>%0X^jC+\y-tcZ4I~~^(>|]#X"q|=AZw#O +A8W81@~|yZx)8`S~y*>dfmuG&X0rkHP| EʌT 1eUϺ[ku1Ʃ3-i8D,[3oM`L>dON}>^1MT`: + ixK2=녲*V(Mo6?J7 T7@T\ļLO0?Ša6LˈHIYt +0|H?/9U.d EsC\0Yf=Oy]&0< -uV{]Հ$"ݣgT Vf3J{dAh.2"\èYnujzL~ ^?Sfy_JiBt|mvaw;lޠLD:q 5*l$e-ݒȦ^f5@ +#rAVQ_Etu0AmT5Y4"< +U*2*w| /UzT|t6Q &ٮ DGv@AvITb +.#xS]v%Gc"RFPk8C}{^j?[Q 0|)RoO?b4y] R]Ydzd]H5kMM2{iB_luwV/^Yqhryw?лe#bl?D*U,ΜDl?s@}`&_tJPj'#]:1TRA0B96us b.' NUabpO)y*5{*1s6/c9?sH)2So_t{>zveͰaܙPh^6uCۜ *,*CdZ$鱠A endstream +endobj +3354 0 obj << +/Type /Page +/Contents 3355 0 R +/Resources 3353 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3348 0 R +>> endobj +3356 0 obj << +/D [3354 0 R /XYZ 85.039 781.388 null] +>> endobj +1206 0 obj << +/D [3354 0 R /XYZ 85.039 237.715 null] +>> endobj +3357 0 obj << +/D [3354 0 R /XYZ 85.039 218.843 null] +>> endobj +3353 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F15 1628 0 R /F41 2104 0 R /F20 1617 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3360 0 obj << +/Length 2111 +/Filter /FlateDecode +>> +stream +xڭX[s:~ϯȣ3ɷؼAB943  J/Jً8MR9L,V޴mXO~2x,Fb|+Gpq(ĥѳW7MD2^e~q߼L}wȝLgy5d*9x΋8sX:ǥk|4ԫ_O- D>c ?#I,ptյ. +d2-u+UdUpAժЭInt+xTrӀ,Ͽ~]NsB+1}1z}n9U; _*=Q~0cnK|Uqqܯ-G8fPw/QyjwܛyKk MV9,OLzF\F $v7R9ZE4C6]i@FQ kⴓiKX˪jp̣V3 3 Cu5gYgDkݥURrZWiFU2?!ٳwhz$RՒ`ܐŚY[ϪꍽW ne+4V,Scq9ޮ2]V^efnڧ Y ۇ[m^U9L|떆 +@w%.0&l@m;:۶P0N5Sϝ%OI7Њ(5FBj@x()3azR8'ն޾ˮas {иcCy0*-ƅTnKP:cBa` @im[1o`2K&3Pe D <*M3S#N׽Y 'X:9t$|@C}-,m)3İe k=,6 Wd'0d7J ǐ  f#'aoSl/ 53 h .<^QHeČ419HBV| -GU\ ];[/a,axj.C`h͓GMbcֶ!& M @ 9ti7K(mIA8O-'%8LWYHPxG00K5n%pH'^b7>[=Io}băJ5;{d' +#L5 #á+rLS3`ɳXô d毓OɚIqQ)n׌RӪyr!zI4Sm!~LCzDeq M#HЋT yI5=d + +y_>6nO +ǂ`/endstream +endobj +3359 0 obj << +/Type /Page +/Contents 3360 0 R +/Resources 3358 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3348 0 R +>> endobj +3361 0 obj << +/D [3359 0 R /XYZ 85.039 781.388 null] +>> endobj +1210 0 obj << +/D [3359 0 R /XYZ 85.039 761.463 null] +>> endobj +3362 0 obj << +/D [3359 0 R /XYZ 85.039 743.459 null] +>> endobj +1214 0 obj << +/D [3359 0 R /XYZ 85.039 261.834 null] +>> endobj +3363 0 obj << +/D [3359 0 R /XYZ 85.039 232.43 null] +>> endobj +3358 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3366 0 obj << +/Length 1602 +/Filter /FlateDecode +>> +stream +xڭXYoF~ׯw<6F[>RDz" +ZdT,iJ$k99$wOC;n˞ӟ͇N_qIot˾pvt23$ ;z0t]IA``c]!^]ڞ/N/> M>'- +E}ccvк)r~ѻ]5\NUÚb(4뢑 O7>pO 8SqUg}vDqͷR$KZH=G:" tYJ% dc2_I:洜dqOG3-h j8n#(T"gOKlVIP>Էg$)9x!"0x<+P%:J(׍i͡`&>;'SF,[nKYJ: +K`b Zոm%oN(@UwyPti%ػ,8*+ZaiEW$xzYb. +K`TW|EƓ[f!ێM2%8OE^3+.h3Noxk>+5K*P!Cf;`u!5֙35,]q.d%_*;J(I91L +:H*<7~6B9LXwt9E <)Iz10=NܰU> endobj +3369 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [147.71 627.887 511.015 639.879] +/Subtype/Link/A<> +>> endobj +3370 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [365.256 600.485 512.306 613.387] +/Subtype/Link/A<> +>> endobj +3371 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 587.542 167.915 599.111] +/Subtype/Link/A<> +>> endobj +3372 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [367.133 560.141 512.306 572.133] +/Subtype/Link/A<> +>> endobj +3373 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 546.592 331.441 558.584] +/Subtype/Link/A<> +>> endobj +3374 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [424.405 519.493 512.306 531.486] +/Subtype/Link/A<> +>> endobj +3375 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 505.944 388.713 517.937] +/Subtype/Link/A<> +>> endobj +3367 0 obj << +/D [3365 0 R /XYZ 85.039 781.388 null] +>> endobj +1218 0 obj << +/D [3365 0 R /XYZ 85.039 761.463 null] +>> endobj +3368 0 obj << +/D [3365 0 R /XYZ 85.039 736.911 null] +>> endobj +3364 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F38 2158 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3378 0 obj << +/Length 220 +/Filter /FlateDecode +>> +stream +xmPN0.v2"¢A iYI"c;P@A D5ܿu6u(U0̢`eՁTaZx1%eI0nw)K?D*en^V`a`9 dvh(nϻ>Oѭ0dҝ +?Pd1)TiG5G,..|_>iWsendstream +endobj +3377 0 obj << +/Type /Page +/Contents 3378 0 R +/Resources 3376 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3348 0 R +>> endobj +3379 0 obj << +/D [3377 0 R /XYZ 85.039 781.388 null] +>> endobj +1222 0 obj << +/D [3377 0 R /XYZ 85.039 542.44 null] +>> endobj +3376 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3382 0 obj << +/Length 2351 +/Filter /FlateDecode +>> +stream +xڥY[o6~02P+"k>Ltb:;x( r"D'Ϳs%2( yxHèy?jF~`y*ߤ|Sς)#Ga atk?K<:ubKY@߭f7?`?|#eX,MxByyιy,6O@JOgQ뢬 k? +ׄT=R !f]DS˶[M4c"6U\l`$T*(Y,sTK#|9DvSjyÝb CoyUEZ5"IW?#PȜh&>ѱ*Xg(1vqG =̨X># *g(U[ +o);H(rdjBn}ֺlž/d }ޱpB*VWp̰is\)#{`ն^xjLCgk +Tr*԰% Gh>ݶ}70w$@cESl +; n:vP%o4dc|6UBCF&Ŏ$F [~y QW#@. 8چ I<8h*{v0:~F + +BA\6>{|IJr`mE<`]ٯ1Y(j]19BYRd̅mY-yl6\f VslJIk]7-XeD&%E*ldN #*srވ-=Iۥڳ[ Ζǻr૜\/4GGCEl@ɆcRM$J\|(ԝ{_//+Y/GO|qWZAH`7T^ Edμ!|FwmUG dDbSdod~fȕ:cL9J ++t{2pSF|9Dጥ +_eUR_8Z0-={8͵dG~э]&sInDxT\iP3dW3 `'16ɴ ݽ_ +rn%-g߳|Uإ߿}b>v(_l-dK%`C|; =]YUny;n1KN$x$ +Te020B)og'xࢭtbk`H Jh49*1C6Zᢃrݲb$s\rȭ 3ٗ"G3u3ߨPB/$UZOjXp0~̜M@_1m2endstream +endobj +3381 0 obj << +/Type /Page +/Contents 3382 0 R +/Resources 3380 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3387 0 R +>> endobj +3383 0 obj << +/D [3381 0 R /XYZ 85.039 781.388 null] +>> endobj +3384 0 obj << +/D [3381 0 R /XYZ 85.039 761.463 null] +>> endobj +1226 0 obj << +/D [3381 0 R /XYZ 85.039 761.463 null] +>> endobj +2163 0 obj << +/D [3381 0 R /XYZ 85.039 671.926 null] +>> endobj +1230 0 obj << +/D [3381 0 R /XYZ 85.039 671.926 null] +>> endobj +3385 0 obj << +/D [3381 0 R /XYZ 85.039 643.191 null] +>> endobj +1234 0 obj << +/D [3381 0 R /XYZ 85.039 489.45 null] +>> endobj +3386 0 obj << +/D [3381 0 R /XYZ 85.039 460.046 null] +>> endobj +3380 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F56 1642 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3390 0 obj << +/Length 3267 +/Filter /FlateDecode +>> +stream +xڽZK۸ϯPA^{wvcO#Q)"%ص@<F?n'gFXH-Wl3?^I""4N~%3".fkZrmo_XDJyEf~k|E$翼?_" +*0{hBlj%t\w +ϥ35q(Z(QbaL.)%oE$ɼ[[qXآ}=65LT}Ӻ9 ) ;)n'r-nݒp-36O+*9Fװ9"+MkbC(ז*H;dUSwlX@HHص׻fiwם/xr)SvX*(H"f^%9FRqcM.id٥["}m֍{rMǎäL,D/d4~ 9 B_WkPAx՚8No;Qo;M8JR;R_߉eS'..:#SPˑny1]اL z%x7[0V d]Z}녾9' C6 dߞ<9ָ>򀂫"~wʱ4r-{~%|[G⊞u#z:_ziCg0'"=`$WFKJ + Ifd 2q|s>!S $pNy<~{S7xEgTb#fIZcKN@$ZN Dyq%Am*h>QH CG6~1J#}I/MDiP%B%ӉQGЦpVggT 0,F-#k).)癄AˆeogyyG |XH) P3)G='(Z@0ۛnt.sh+vR O@i=!BHt@)cJi +i,:d_wBNo_yϓ[ɴ-ۖ儦n02EcSFw)XJvDmϝp{WjO m6Qz@1>˟g^[9”PbrDD3bkKn#Q;Brб;vN}g +u8<;Ȅ,eJ%@yobџP~x]+;䔚MC_msm.!Ҧ|Y^CBH?TopS/ 3ޒq483œ*ccܹ[G+bs2SƋ5V1?Y+Cqƻ?I$@ K_@4 q⏾e:/yd^@tR =tJ- oe;;ڤNmG +C=U9׿Tju'00#XtA2w#a`l-` + dٹ3qTLឬvǝB:ac=Ņ+9c͓yjyE2}Obh?v)\`A1aA%pG*4A,삹F#˥˛O>b-*k \hx, q *+/ WNBl'i|,'W$$ė sGђC"(&T$BUO\ji +갪B*w8GAÀ%NYNr5V߃\v[ xanW9M p.w21a9yvk@R"c+UokbI019k-wU +0f∣wH_y&8msܝڔձ9aWx2wq)w>U.JSROh>7."@EnhrXuCHa9Z$G/B곗o¿аK"M!N!8[ۆnxG`,(B(Vb+vMDQS9Z2;za-r#OdGLH:S%8?+xa ,jGIH/|Yd)zԡ /bh> endobj +3391 0 obj << +/D [3389 0 R /XYZ 85.039 781.388 null] +>> endobj +1238 0 obj << +/D [3389 0 R /XYZ 85.039 650.648 null] +>> endobj +3392 0 obj << +/D [3389 0 R /XYZ 85.039 624.034 null] +>> endobj +3393 0 obj << +/D [3389 0 R /XYZ 85.039 606.001 null] +>> endobj +3394 0 obj << +/D [3389 0 R /XYZ 85.039 456.354 null] +>> endobj +3395 0 obj << +/D [3389 0 R /XYZ 85.039 287.653 null] +>> endobj +3388 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F20 1617 0 R /F70 2201 0 R /F18 2207 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3398 0 obj << +/Length 3144 +/Filter /FlateDecode +>> +stream +xڵ]o8=ח@>t^k|,X,|%VšhM!{T5 l7i:[.|#~GvyqSg* -7\է1Ӊ?_$I-yϐ~{{Bypk__//G.B? Ͽ"Ma*f02~7Z8]w[`mG_? *ҡ]C?(fiiܿz Ϣhkx1xHqf_f,38\^] Lk8DJpS"TpycEwkCko:?`D^}8C*֌vą ,XڕUo&ȃ$Q&Z##hN@l6_a쇹Nzx/k`/mߑ0΢`b aBn;GӸ֡v[zGK-"Vu5u $^.[ls`2fVb/mNĈ0:%s SrJ;$g8f!mѲ u=K8j`=;vxyøk5埚i6[`P/7*T>+k'<A-j[ 1b5F+6%Z< Ո@D+oS#qPGP9޷eQ4DPkO݄e}cB3apMsR伷ܲ gwoMS[t]^;3`Yȡm4-Zmy`l9nlso% b QٲMy%6,q"&X.oZjm\-9l˄bWm(jْgm&w;i|&Jы@*&"a \ݡsAi"yu`Vx{^RPQnߌ-OǙﷻ[# #?x@L1Yߍ\@0ܛΛnX_tnq~?gbhnI.d5 Quш9iEl4QWebc˂l1#1ڗۜw5:k>"`ws%PvL&)`%s&k0 +{kO/3k +,23H! +" ZW>|r[і'pp[#zQ@)ttA܊q<E-+K?x pJS.ul0E!;zJ'4WF~Q:/S%BA˟xD*U~(q l\&b`7Ȩ`J0 +#ˬE=95؈bX[PVxLah,5 Al}Dլi%!%}V`4'f\\9PNgK1r6\-Je]PjW4PNyol+ irOO.rZ:9h Jh=Wv^uT=G("`%a@2%}@%} 2_Y}1a +juS] jZ/JLjY|YsMD)j׮p j](g`cO>!!S+Pa>_QYICeqbz+KE(6 -EbB +~UMB~0s"]mP[6]`C%%5*Y'^Vg(F墈im_չ e '+Vx B2D-_iV'%e4yZm-*uUr6⮀TD +(+'-5W3djbibƝXy=fzx!3uT2iqKGm*{@MZ[g;ԁh솆AB;P] +i-X߮ȅA #ijIwd9#aat.*)U8JpOR&[ IDj0Ė-y8YlyF&.2PvܛQZ!͚ܱI zH]TԪOPq8{K+Cftd#`$03u1J}0myiu۹=S/wv@VTܓJ^QCЈ@m:88&ɷ݉;ԵwίvSu^4Xԯf ݙHAf +gS?Le) +k?1J83}%CsDri=5`2[_r|y_?u 9䯷٦t$繹B]^$ |I|PtеIxs9ޕQ`)SNA:0<'׆,Fmc`.dMu3x꨽MB!{!]fEh8P.g&:^LTI)5o\o#-0k@؆܎'kI3Iܒtײ˨9CȧY6i|"{i䕅|SM\| ~18UewꙦq*A˷"d:s]Tca-`Q;T52N-鄼v.n"SS^Ͳ`g~(wrб8Kݥ NC)dw`yE*du[+#alE}x cZ>pm2dcr +& 8 ZAIDEobUYtʩ}DF/vendstream +endobj +3397 0 obj << +/Type /Page +/Contents 3398 0 R +/Resources 3396 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3387 0 R +>> endobj +3399 0 obj << +/D [3397 0 R /XYZ 85.039 781.388 null] +>> endobj +3400 0 obj << +/D [3397 0 R /XYZ 85.039 165.173 null] +>> endobj +3396 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3403 0 obj << +/Length 3539 +/Filter /FlateDecode +>> +stream +xڵZmoF_!8D*jK. +/p-kJTIʎ3$Es_fwgwYK,OfQ?g͉;[Q'P3a77'߅LN&;&~_9(7?\Jk4_Rbq +}7n~<,zX_sg1I<{$mNt;M\W,|X2@ ZakI M3Cj@l2sjɭSdA#D&nV D ǂMHMYdpFՎ c>g;}ػ jԾrK.$;f]y>ﻔҮ8P&h(T +V㝘sź.nnܣ֣9UG6]WnSJ$960liͥ\'vz -aֆRyQn;k0#y&j]d⒢W1 =?s{4-R\;#] ձFRí5l'`Nw_j>>T # cA°_4 ȋd4ݴ[\,]<+Du?oYV{*p ƱP޳+t?o^ */*cZZN1fa=T%MmڳQ1Sd==̿Qv lnٌo4ߵhzaqcFYiAXKX\EsDɱ>$'f2t"&T{Mh25q<; ri),Y9tF$$ވ$w&7'x3:I|~7_mۊ8L*qgKX +q$;AMSܖ4A|DfV'C6ZFOq-6iY5A!S6u +8}/\UUXd26k#5d+ +$~f[Vw&>W/&'tgigg|+BnƷЏ*FϭydБ8z4ucQ@!!ʶ+C%6UF +x\g&V! CF#BU\ȑ6ccpl 9(P}b%CfPFZN>,X + 3 1c.c,iC eg9fҞdN;(e־P9A蛡}F%2>|xF 鰘TL#|Mh/ip%Tu`|$k5H QZ*8xL$®ARbGzIz g{Fw3TpTD4Q4xwD! +? H"gTZ?YòDÞ=ocQw D 7 h9>R&pVc8np*Z/ֹ<5H-cz Qj6/ZS \O}My匡.zD2k?r?d0QL PB><@ml6G0)lh̻d\('=4`.k,NLh묨e(s!h9]JBv"0Y#&{5XN4< !0=N%KEA^;|E0peTrϚ7P$ozFj`chwO/m6+_G!5l)Ɋ~vK|l<\?@:0/L8S')42Eס$E>-/[47G_K?Q ?#) > endobj +3404 0 obj << +/D [3402 0 R /XYZ 85.039 781.388 null] +>> endobj +3405 0 obj << +/D [3402 0 R /XYZ 85.039 761.463 null] +>> endobj +3406 0 obj << +/D [3402 0 R /XYZ 85.039 705.373 null] +>> endobj +3407 0 obj << +/D [3402 0 R /XYZ 85.039 517.54 null] +>> endobj +3408 0 obj << +/D [3402 0 R /XYZ 85.039 278.584 null] +>> endobj +3409 0 obj << +/D [3402 0 R /XYZ 85.039 247.5 null] +>> endobj +3410 0 obj << +/D [3402 0 R /XYZ 85.039 229.36 null] +>> endobj +3411 0 obj << +/D [3402 0 R /XYZ 85.039 198.883 null] +>> endobj +3412 0 obj << +/D [3402 0 R /XYZ 85.039 180.742 null] +>> endobj +3413 0 obj << +/D [3402 0 R /XYZ 85.039 98.16 null] +>> endobj +3401 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F38 2158 0 R /F41 2104 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3416 0 obj << +/Length 3796 +/Filter /FlateDecode +>> +stream +xڵZmoF_aKeb[i^CDI\ŋ7/_`@PuTrm|v&Ѹ^ac?_γG(u-ſ,f.y%Ѓږ: 8&Ua캶Tv9hpD.H/_WXk# U+ë^i.<^GVSق<;ۯSN^ܴLfu-KF+NNp.xBkfL{{w@ƭ 'E]Zv+U븅j'll\Y勵6-8s"raΦn9MI]ZܵXۗLlr+o}J2>ʂdPF80eIs*8GL"釢?22 4'،L܎|lB7/X#y42;a /K@%n~`RAzϽH?Ho~RIW"UJE:bKޓ$H +] X:C_uhfZp'YzVaD  т6+;ȁ +{9yV~sg_6]-x(J`N]ƺ.CWT ڋ[Y$l{{NFK)VXH>)ux崻BO(Xm~5j fy{B_x(zDF +U?vWz uR9JER|58՚ q皹@U]$ۗ "-U8zlD(E;XSk\,e?v>~x-(ܵ=L XӍF{3Q+;#4=my50aE_ +&&/&ik=^uNaM+Fsw"q}]1ngibOŲ)pO& +y TY,)r*x !$aiU4#nәQQI﹕-_',y!d8# O? 5[bò7go)ŮصZ: v-_ٌ&{npgl +.I/q*`b@` ]*}8 ( {X~cb:~ 9tyzzDI T*?6ڏN>9mAJM͆FDg̱r=Y3&q^@(#QVl,f*V@3 +nle.}踍g,م;WW)FwdMJE&u@΂,1 Uz*Ǝ=FYxZ12͈ U2mJvƑ.8fuر#&NmLuCQՖ ]09 +{4XXB Ǵ^ߒO-&̜G$rN0NyOMrap2VAqReaG^ ,$/!dS\8|FMDAA4稰K@ SL@%V |Z.;NVJ#[ ?ζ84HƇ6 LNDXV7>:Gi5c-.[oWlGnd:!r(eP\zCOW<`?6-e/H D+ ^ 1l毈sX;!+,$43hFWtoT5Cʁ!:f ScscG`e@3G w6EL|ǔ;d[&`.G<2KeƳ P0ga:V3 +nznAuuw1Qpֆ7bg[9I•GyȬ%L&Y\B))H'3JC +$3ӗ<0qU2嗃TYQ[il]#O }5x8KX=#p[#縈!R3֊(0VAg"᷁?B-ߔ׬ +te( ?R^wTE_e#1d[ +&ΊL9!yuڕڡlQx  +5V}3?<|u?)EIbl]ruOPMfM1u\֛EGHa@@#21|Є6[ 8FQH9ETtBub!וC.RsyYAdJu1W;]('", '*IfSew;LS\IJ (cf ( " +.%|&q&Eƈ nDarkG;{Ym؄P)z!K+$ +ءl<"vc'"r?b!<9|=(T>Is[.rI&ņ\Ξ:>+H*F'}aRdI"@lWuexO!Zh  rĘ5$ pdb &ٷ5gk*w1&z&벰|GsRFMV>Q`Q"^TY} 97l_ޗɂJ(')a;=qLkNN(^ +<~L~~)-gwOܗ,[  ]Y1gf1D|0i(|Ή:yOͯZO>8~Lq`&$y Ĺx~p&&,?" ):GL?z˒K.(> endobj +3417 0 obj << +/D [3415 0 R /XYZ 85.039 781.388 null] +>> endobj +3418 0 obj << +/D [3415 0 R /XYZ 85.039 713.704 null] +>> endobj +3419 0 obj << +/D [3415 0 R /XYZ 85.039 696.17 null] +>> endobj +3420 0 obj << +/D [3415 0 R /XYZ 85.039 665.087 null] +>> endobj +3421 0 obj << +/D [3415 0 R /XYZ 85.039 634.003 null] +>> endobj +3422 0 obj << +/D [3415 0 R /XYZ 85.039 455.971 null] +>> endobj +3423 0 obj << +/D [3415 0 R /XYZ 85.039 300.691 null] +>> endobj +3424 0 obj << +/D [3415 0 R /XYZ 85.039 194.759 null] +>> endobj +3414 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R /F38 2158 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3427 0 obj << +/Length 410 +/Filter /FlateDecode +>> +stream +xڥRMO@c{踳_=$m Ieiμv z;By;0+\1\# ]ZQ/+HQvuhL),]R\I'Ťp&pfarwjE+nYiVo$bLR,:Y=mĚ#ڲ "C^cR#sEmI5 J]I>,uMzMFrdpAgqrD0t:hJ{`La9H. +14A |hN> endobj +3430 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [212.407 723.034 369.551 734.724] +/Subtype /Link +/A << /S /GoTo /D (problems) >> +>> endobj +3428 0 obj << +/D [3426 0 R /XYZ 85.039 781.388 null] +>> endobj +1242 0 obj << +/D [3426 0 R /XYZ 85.039 761.463 null] +>> endobj +3429 0 obj << +/D [3426 0 R /XYZ 85.039 736.911 null] +>> endobj +3425 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3433 0 obj << +/Length 2894 +/Filter /FlateDecode +>> +stream +xɎ_QJmn`N0]I# *[i-DwuNP&ɷ/OI.Unݾ 01K]qNq 0az-#u +;/\ =Lx𪑚$L░$̕;26鉳)Xsۮ-S  \7}&n0?1fLlMzQE &#pb3:`2lс#z{?SdH5Olł.r#wBK4t?yz38X1W$= +I(. +)T;tXv*za$7M5=/;g\ߑi3MwY0$J( +I0nEp'\p/#_%2(3 28I.rT)F\d]S,S]N O^*e%t"*`g4mUL$p +AE\(jfĻ(9:ǎmB8hx9be +̰N7 T/o5TTΜN3'!IgJkfP+qڮ14Xn(4ԉ``CEIqGyѿEktQIչɘtVWXsˡR*s `8nVWD"8`令YN?daz*%8OP1J?lA:.t Ls2vT(Ouu\ya}GˈJyy?N' x[~|:g)Y488svhec,(m91V{h@ϜNb@ *p2m+T-Rc8Rƾ/GM x/D\369#1衎G/%$Nؖ מ=s0%1&_2|O< _"6H$=&S_2w֯v]}ltxdl2YB@/Ykc8TDBxGV4|{}ŇryP8r?t&41ř8Sa+?soCppw/\ф*B\*/ߑqMK( &%",ףYHfu,'Q(E,d({/Tj3Bў멢87 lendstream +endobj +3432 0 obj << +/Type /Page +/Contents 3433 0 R +/Resources 3431 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3439 0 R +/Annots [ 3436 0 R 3437 0 R ] +>> endobj +3436 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [389.071 266.298 509.276 279.199] +/Subtype/Link/A<> +>> endobj +3437 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [137.104 239.199 260.036 252.101] +/Subtype/Link/A<> +>> endobj +3434 0 obj << +/D [3432 0 R /XYZ 85.039 781.388 null] +>> endobj +1246 0 obj << +/D [3432 0 R /XYZ 85.039 761.463 null] +>> endobj +2164 0 obj << +/D [3432 0 R /XYZ 85.039 642.137 null] +>> endobj +1250 0 obj << +/D [3432 0 R /XYZ 85.039 586.947 null] +>> endobj +3435 0 obj << +/D [3432 0 R /XYZ 85.039 557.543 null] +>> endobj +1254 0 obj << +/D [3432 0 R /XYZ 85.039 131.639 null] +>> endobj +3438 0 obj << +/D [3432 0 R /XYZ 85.039 84.97 null] +>> endobj +3431 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3442 0 obj << +/Length 2826 +/Filter /FlateDecode +>> +stream +xZ[o8~ϯ>I4ibv[ʖGR&=7ʒ-YXd1ER也#(%(ʋ|una͑WnuhFUf74e9y$b8Ӌwox97/Zktӫ;D{hhgu;zHG/GxtmW$Ssq4={ +#~k@ ' *V:i\o;W*_|%2y_s0 b+/u69/ ^xꦢENLQLY]@, +[0%/*/ҊGnp +((G;0ɪr|m]@7(hk Rgbz +6\p_21'"/ .(&@hv!i(45"4^gDs%Ʌ7ñcipU;9Л3 WY"efk\9g6G`:%RfXڂ8f>}CުC M륾:]6P~ /.CAgAS6BӪiH5wHYB{=:+z+ВPoGY)kO%gi qytPǃ`sk0yX&aazwNm +ukE_[&,x<ײ )hhXxϦWW߿==L$sV#V73uu;Nb`P=j:8"Y]w)B$tf0h$;5 m*lCS̎|)]V/4Iـ]=F#\<= ;GsJo9痗njѤ{h %:_Q$K%.P+WyE`VBCon*YZ􀜺&&b|k.nZPt’4AbBnG]e(_Dꯔ0YZ =Uo eC%ǘ I]r8C#];$|aqA,MoE ʸ_/ĸ%P-m +E +Bn9}贿{efBB$B"vwa Xiod8FYYs_eyr *:O<>J@[&> [qFG&[X @aPO =HfɐT44Ad*ǂ! +.dЦmh2hԙ܉cMVD 0z0Ω!dvsVW2kÅR\>i,@O8o2Lf[ę`V7&*_ю^v.)Z +,Zd/J]RW N% ?w:ښ)Ww~[d A86 ĶEl V؁|ߖh7ea:(P"k!F +9d܇0.|me)#DXCneକ<6؀d7T?~9 `OQ{Y1ӹ$Z4y]Ƚӂ{s8+(n*vf|m󹺌ۥL;p_'UҙBƾj׶,mr K]AҐ<Ä),;Oj+F su'Ax+ 4dب=״ 89t>}<[>]JZtLJWh עIt`S7lAdRFNЩ*]b>Jx;ܪPΘeiiko+{WUHM*[ۍ1=Ixc+  bγ?ܬu3HC_š Zۺmb)ӵYNL(DPjy \o8HZJׂlalK͎ru"YfX6rۗj;@ltçG/?f{"3)OWi/Q$R9C{u{伔CY2e SB=[/5cQ+&E{ quR1"x&$6b[\>DUm|d]%t zuӢ;[,{1UյԢUYw[\HOoԽ_Ӝ/ڢ-Mp=l!F5p=qe-7h:Bvk +$"{-(KpzKT(y049` Gۣk6> endobj +3445 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [237.74 247.707 322.248 260.609] +/Subtype/Link/A<> +>> endobj +3446 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [376.679 189.127 512.306 202.029] +/Subtype/Link/A<> +>> endobj +3447 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [138.589 178.305 194.521 187.873] +/Subtype/Link/A<> +>> endobj +3448 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [231.213 139.513 412.479 152.415] +/Subtype/Link/A<> +>> endobj +3449 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [291.316 117.3 419.307 129.293] +/Subtype/Link/A<> +>> endobj +3450 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [247.013 94.482 434.521 107.383] +/Subtype/Link/A<> +>> endobj +3451 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [288.68 71.966 504.006 84.868] +/Subtype/Link/A<> +>> endobj +3443 0 obj << +/D [3441 0 R /XYZ 85.039 781.388 null] +>> endobj +1258 0 obj << +/D [3441 0 R /XYZ 85.039 291.595 null] +>> endobj +3444 0 obj << +/D [3441 0 R /XYZ 85.039 264.98 null] +>> endobj +3440 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F20 1617 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3454 0 obj << +/Length 3364 +/Filter /FlateDecode +>> +stream +xZ[6~_}5D&mMf3.[%G{niYɴX c<wfYALQ͖`WJ($ƦI™ +?Jh9ڦgH4,Qgc)[gdh5CwjpI;([M2 %~#6n?vxT%uҚ@MynhY50.^:g 0~붮IF5.Ӱg<*[3`E=g\ ^d`wJϥ%oY+4nBZ3FLϡÚ>Z5P︰fWμ4<mL(ؖ +žUB>s`Qv`sbqi!V|0H& + +gm ҍ +oU`īAl&[?0 AjO=PUq?Wfwώ#M0*e0=G[ָ(y( `!bť VWCn/[2lfy.Ш[#% . +Aɒdj/-Z,,@ +HvqC+BLrQ4#'y%h#co[ʱ%@A,F P#.0Dwɢ6T(XGmiO~ϖd}>[NbRLL&_X*'v[RvU-!b eY"% yHDc̝5T$0u6uG|I#VAN $ETjLR:cq&T|ɉڵRJ/a)e NJLߝ X #M{2YlXkƣJC/鋸䌢4:'ޒ.Р?ԏ'ar&PIцhWǐpfooej(M;2@;tRZq-\ZSn +Piؾ-1j/Fo"ӎ lwrov/on@JR]VdX֞(c6^&g6_%zSPϊaW 2!Uÿ40Bh0.9ľ/I,86z +ndFy2ݓ/#6[O#fi" C@ͽi',Re ^Cq偮_y|֒8\B\S+ơ N,-]R9CEZ|VC\OdO@:E`d)3I +.T.0x}kb?S762C)~.~DBǵ,c0x ;3?sI$NˊI +O`iL"^ +2;ybi.1]"qa[ -8CN R5 '=tПdXRX ?I?WSMy-TkcMfaWkca$r._WD'uQ;H'w_skyv *8%T9O7΅!:Z!>ȓ>x:^X؎ h²tKP ۧsi$}*{pS' -6yW[<`Yd8` 0F-?\0.硗>8q1 9)>̛3xwV{Ո{ޯLf;eu"o hoF ,m(>ڋw~,~Pybad+ ."_,dendstream +endobj +3453 0 obj << +/Type /Page +/Contents 3454 0 R +/Resources 3452 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3439 0 R +/Annots [ 3457 0 R 3458 0 R 3460 0 R 3461 0 R ] +>> endobj +3457 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [390.793 722.731 484.421 734.724] +/Subtype/Link/A<> +>> endobj +3458 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [335.18 682.084 480.851 694.076] +/Subtype/Link/A<> +>> endobj +3460 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [218.97 105.796 325.417 118.698] +/Subtype/Link/A<> +>> endobj +3461 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 81.425 133.339 90.993] +/Subtype/Link/A<> +>> endobj +3455 0 obj << +/D [3453 0 R /XYZ 85.039 781.388 null] +>> endobj +1262 0 obj << +/D [3453 0 R /XYZ 85.039 761.463 null] +>> endobj +3456 0 obj << +/D [3453 0 R /XYZ 85.039 736.911 null] +>> endobj +1266 0 obj << +/D [3453 0 R /XYZ 85.039 163.232 null] +>> endobj +3459 0 obj << +/D [3453 0 R /XYZ 85.039 133.828 null] +>> endobj +3452 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F41 2104 0 R /F65 2099 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3464 0 obj << +/Length 2671 +/Filter /FlateDecode +>> +stream +xڵَ}b` pk$Qaxc#=@yPwѐ|}"f`*u;~/~(t!/Pö=C,VNS-t%apHUp-\.?r4H{gE&Uw ِvWPc[+VbJ"aCnO*))l Ek@Es\9PxtL[5VrreܧVMûؘ¼cJ%Pj'2 v#óg D\5ײfnOH +_m8 )KתC<\G + B'H JqŘ;+ 4|7c#]ija_z8p+n:g+[HG9IVPaFɃLC>` Q9֣ 'UK-rQ|+2OI.w:dL>́B9tuN@JT4́QZᙧta>ej=y~bCzDkvR5QN3^uC%F(]Dzɤa)oFEKln:0Ì +h)$,b2̊Ej2Ɯ{|nSxUO0Ou9)YnoC_--?cr_~$m`~ +(O|t1.`|ތ扔xYp8z؋@ܝq*y2_>S7=o^dk[Aw@3)s=3H!x'MWɓ1 6:\R#u^:89ьJq ƸT 85a رdGXu)Xi4,0vAkz~/Z]MZ8N,bFG}ȹrkF N0K>x +P05WM +cހ'FtDʒXg|Qk9X`$èF%SLCI- +lG`K^ 8lAJn8q|eK>PlAWn s7/ _E_-%r5P,>iy0 .~U.T&-=zW/CNӑVhB5+7adïhؾ'VUBϦK&r6^ 0NOc ɍ9m7l …7.4'29_phnd]m**9i} }I&~EPȽεaϒO7'05'.td_*q?lLbEKH!;i$ +γ0aF '>?k0\nBA7Կؾa|OB0~sKaRFa?zn͕Hl]Lܦpñy47dC_lIJF y?>>QU#%zc8Lr^?JeR ! #D|p= P\}ߠ`؏4>öjl wkm;~kqBvZEJЮ꒫9Cm~ MOLendstream +endobj +3463 0 obj << +/Type /Page +/Contents 3464 0 R +/Resources 3462 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3439 0 R +/Annots [ 3468 0 R 3469 0 R 3471 0 R ] +>> endobj +3468 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [232.013 625.659 270.975 637.349] +/Subtype/Link/A<> +>> endobj +3469 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [341.801 435.668 475.519 447.66] +/Subtype/Link/A<> +>> endobj +3471 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [250.165 336.599 295.309 348.288] +/Subtype /Link +/A << /S /GoTo /D (diagnosis) >> +>> endobj +3465 0 obj << +/D [3463 0 R /XYZ 85.039 781.388 null] +>> endobj +1270 0 obj << +/D [3463 0 R /XYZ 85.039 761.463 null] +>> endobj +3466 0 obj << +/D [3463 0 R /XYZ 85.039 667.044 null] +>> endobj +1274 0 obj << +/D [3463 0 R /XYZ 85.039 667.044 null] +>> endobj +3467 0 obj << +/D [3463 0 R /XYZ 85.039 642.326 null] +>> endobj +1278 0 obj << +/D [3463 0 R /XYZ 85.039 420.224 null] +>> endobj +3470 0 obj << +/D [3463 0 R /XYZ 85.039 393.913 null] +>> endobj +1282 0 obj << +/D [3463 0 R /XYZ 85.039 282.629 null] +>> endobj +3472 0 obj << +/D [3463 0 R /XYZ 85.039 251.104 null] +>> endobj +3462 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3475 0 obj << +/Length 3450 +/Filter /FlateDecode +>> +stream +xڵZ[~_1ٗ%7TQ@<؉wUسV}` .;s8R4PuԹ|mmn4UN7f "~`bzssnς~O$ůޟۏRʋ2Mvz~Iwن޻3ɛFNf~ |O0nO7:V~O7wVγa+8V~jw0^9p#{(v`>8y93uMp|4Hɺwc.]zwmOX5Ȃ(4~Fӱxe%oX +pPnӮ+rLD`e"+ZBkO)oG+F-N{B2++JCovNb5ˎ +2B&W4hEsqꑢLJCkjcLRR>3e:L}A˹,s!Nl(C=g-[em"^Itr$y Qqy(S^0a\&}WthY!W梕!@ ZCHE'Jȅ o+l@%f!)JNl4&k¬]08U1bIqOeN9 ](Bp8Yf` Ǟu8혷q.<bJc gpvO 14wf̅_mQ ع6LqIz5z:B֚g B6RZD.; OPE0h!!qP_ã ̆|H;[\0s ؑ*bRY#&\J pKϓ<63Ƹ +/ kJ@jIЈ&h?B%QT=0C];r) >7VCO%HuZs'y+GЌ/zi4VLqpF&dԸtLn,gD.FVqRA5 zM F -xoGkL;$RVժ" =b?r%\k-%w8ĵc|FekE|%dV(ͷ:eZGT_q:`9Θ"<5%4en gxZ'J 2 +Z+*_GźFg*j]#k,c }:pOϜ3n$#hЇ3?(C~YgOk"D~K}SvIELu C Cܥ4r׏(Df_OV +Gux>*LSRCxqW ++%:Ip*I49=r_s)UAwʄ: njJpf\="Bf0feSr+gy{'S 3 E#j.MDبBkH=9wK}) 0OD[4Tl1.\PS~:PzqXu/ѳkףym-o-L/'/9T!_sۈQ-QUgoͿQIKIՄ,<t.c$@F-db 9Y*(aKg荲 dgWڱZJ!kMe!'[vph:O!ល H[Oglآuv7 +L{,3~g4q*㪆><Rp3<!e0\Ǯ.)|c1S[1PvAvIE8D° urd[2vY]p__j&0[ulJ%I/mK>C+?\jendstream +endobj +3474 0 obj << +/Type /Page +/Contents 3475 0 R +/Resources 3473 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3439 0 R +>> endobj +3476 0 obj << +/D [3474 0 R /XYZ 85.039 781.388 null] +>> endobj +1286 0 obj << +/D [3474 0 R /XYZ 85.039 596.451 null] +>> endobj +3477 0 obj << +/D [3474 0 R /XYZ 85.039 569.837 null] +>> endobj +1290 0 obj << +/D [3474 0 R /XYZ 85.039 268.864 null] +>> endobj +3478 0 obj << +/D [3474 0 R /XYZ 85.039 237.339 null] +>> endobj +1294 0 obj << +/D [3474 0 R /XYZ 85.039 142.394 null] +>> endobj +3479 0 obj << +/D [3474 0 R /XYZ 85.039 113.658 null] +>> endobj +3473 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F56 1642 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3482 0 obj << +/Length 211 +/Filter /FlateDecode +>> +stream +xm?O1 sI.Ju-j;])SDy???P,%`p屡_"egv, +f hY1OK#Z7 +V0Nm'}+h_OP x0Pt{n=U}#%E7bRv^8@v=c&`I`y"Rendstream +endobj +3481 0 obj << +/Type /Page +/Contents 3482 0 R +/Resources 3480 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3439 0 R +>> endobj +3483 0 obj << +/D [3481 0 R /XYZ 85.039 781.388 null] +>> endobj +1298 0 obj << +/D [3481 0 R /XYZ 85.039 542.44 null] +>> endobj +3480 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3486 0 obj << +/Length 2668 +/Filter /FlateDecode +>> +stream +xڵYKsW|1XB^{:wSVʒ}5HB7[)0tP-EIq|$|&Xl%#lhZht\*~`1:ul+m4?޾(2;yg +Y+^\)v\**?^/}7rkZ?P/*e4(eTPHҩR.5{X/Huj~i}VJGTu4bԉ&"AymNw/͎_zxv'8ˣJ/(U)P5C7>=W&nÁ}4hRjACAQG=̌pRR!-M ;H%ƦA񱮚lg 6cZq֯7ҴO-ToYvOu_8 ڄHL~\_ԻFrP /FJw͞ 9?6z(3W $0/n=eO|CS?E)[QCJa7XԡWEuqI1;meKK`LXUƎM{r> 7uo[*hW&LJM9˦io_P +@9FĽ[୬&<. sf0'ly^]q!Dž97pVﺙaemH f# o3T7XB /i :R {%:'X+_` +)`OOvX)8+w,_Fl>{d`asn;kzBr;9te*0l}?y^b6QE7OWiB3s~?\]36jqbD|͑^ ؏ET~d|H/b{JV"v_0zyn}$.\v Sf;uUL#BQ񤦰 됕źBB v~(ag..#2˾o߾q໢EKRL!b%X"*w[ҹ0ȬV2+5َT2VS6caj;B<')ZUK<@$_k _~t1ձ͒ڱ~+'ie_^/')ڰqYۖ[IzG`>tXr +J`f܇RXMa((Z/I=\S 6vE_v"2Y=Y*Y1 +nH4U9yB1169QU5zYek=DW}{"\F3#&(w:Hc+x$ThCw;= D[ 0wlX|e/O3l'&4SbBr]Aj8PPR!ńqC/w-Z4pW%Ɛ܍P[r튤K_ݾwŤZɛ-rcy+j'y*1ٿ^a?瓃FId fzWПxN#),({1pk7{</ԅ&- BAgMJɓ8Z"Q =YQ?ix_{uendstream +endobj +3485 0 obj << +/Type /Page +/Contents 3486 0 R +/Resources 3484 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3501 0 R +/Annots [ 3489 0 R 3492 0 R 3493 0 R 3496 0 R 3498 0 R 3499 0 R ] +>> endobj +3489 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [316.138 654.395 386.484 666.085] +/Subtype/Link/A<> +>> endobj +3492 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [435.86 506.629 512.306 518.621] +/Subtype/Link/A<> +>> endobj +3493 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 493.079 216.398 505.072] +/Subtype/Link/A<> +>> endobj +3496 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [195.316 312.568 375.35 324.56] +/Subtype/Link/A<> +>> endobj +3498 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [481.678 208.962 512.306 220.955] +/Subtype/Link/A<> +>> endobj +3499 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 195.413 210.671 207.406] +/Subtype/Link/A<> +>> endobj +3487 0 obj << +/D [3485 0 R /XYZ 85.039 781.388 null] +>> endobj +3488 0 obj << +/D [3485 0 R /XYZ 85.039 761.463 null] +>> endobj +1302 0 obj << +/D [3485 0 R /XYZ 85.039 761.463 null] +>> endobj +2146 0 obj << +/D [3485 0 R /XYZ 85.039 667.044 null] +>> endobj +1306 0 obj << +/D [3485 0 R /XYZ 85.039 625.403 null] +>> endobj +3490 0 obj << +/D [3485 0 R /XYZ 85.039 598.788 null] +>> endobj +1310 0 obj << +/D [3485 0 R /XYZ 85.039 598.788 null] +>> endobj +3491 0 obj << +/D [3485 0 R /XYZ 85.039 577.795 null] +>> endobj +1314 0 obj << +/D [3485 0 R /XYZ 85.039 478.811 null] +>> endobj +3494 0 obj << +/D [3485 0 R /XYZ 85.039 457.917 null] +>> endobj +1318 0 obj << +/D [3485 0 R /XYZ 85.039 402.208 null] +>> endobj +3495 0 obj << +/D [3485 0 R /XYZ 85.039 383.734 null] +>> endobj +1322 0 obj << +/D [3485 0 R /XYZ 85.039 298.299 null] +>> endobj +3497 0 obj << +/D [3485 0 R /XYZ 85.039 280.129 null] +>> endobj +3500 0 obj << +/D [3485 0 R /XYZ 85.039 107.945 null] +>> endobj +3484 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3504 0 obj << +/Length 2531 +/Filter /FlateDecode +>> +stream +xkoFP!I./>'BZ(W$%6 wggg=cgf?g,h]سvn/g_^\+pgb;-ׄL޽[|/֖|܍/Ŀ>x7wxq]hg)0V:fOʉ=-ۋTxϛ񩉷-<7PnE@OUOɱS|5Ԃ6žvc2PNNtkh^훬JX ɱ$Zί\צ ثZ&*/ʣ+5]e{D\-[%ͣs@1Hf8=2Al5OZu7FTg ?R~&Tѱ cZn +zBdv +/'Y)luFHmhѱd5S^?BJ|m%؞cLCxZ99z,XLb8 xGıۅ 3Ѷ|Ig)ì2]!xh9BeJ]]Ed댸f˯^*'J~7Sf `-,6,djtr( +f7AN($X@b< (C;0"5rt!Wr:5,b;jqBX>k ںUMb+Ѫ5ʃW5Lbx;0;;=,#ID+ 526>ɧLqq8=:'|BMђуq\S~ojB3բ^`63 g:poیNz!Ve.#3hU\ "Ъ |/O&J(T( ^/4ϩBJv^)N9F}Vā +N\O5l*a/C.kb8n7<t@0 `r@im|`x"kC-g7g̮ 9S0kUx/FN_ָ|Da*%q +r4ǨX{&ݙD~*==ZSn:װ {pv\S +1bڀYӈ2#ǟ!㪫W.\ZCbe +?[*_z(<)DQMϳ3mK|wew+,HS> n0l*!Bda*cpu(wT`: ƙqe- GO &0$FyIjE .1K.UdhL)NyLuẽ!Pꐛs}U]b^&-#F,3XhبS(?JKcKIC ;& [hl i_?0{,#2h栴 =o2$ wo*dٝ N'Z\G\*VU-٨JW0< Li5c%s8fd ~@ +\p3=l9L* S:Iy`A{dBف߲-bkrh#jJMJ48I^7a8=h/V)Ucb_MZOsmcu>_C +Ljᏻ;ɑt^&mWO:8Eg>G}: +;Lzz#6@ȑgk7 kں*LK#L5%!F Ն@e(B޹4,GFd2 c>{+e؇} +-vm]tVUZOj~=F('Қ$y;zf.r?4GHjC-_ku|cpB8aWQHl&*Bqw{ +6<>aws_w%չ `fUI*G+}EgVk>TD]/}$H:̈́u ) +9TFvfP2.QR@ [y=iԏ8\cڮ ]P6Okd8>Nj`@P[lXM|l͕iv0ҷ|!d\շl"S>kמh[T*TҐ*B7At})Z6-ٗ]*idB>ωjZ%jBF +`HdzܠGԳ [.!-6Z̟Op5W` kz19xͽh`mמdS Ȥ>h]8N"^= ilYX0wW|O57e}bQT9ה LAb'CFiBOb:C`Nua1endstream +endobj +3503 0 obj << +/Type /Page +/Contents 3504 0 R +/Resources 3502 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3501 0 R +/Annots [ 3510 0 R 3511 0 R 3512 0 R ] +>> endobj +3510 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [487.405 435.806 512.306 447.799] +/Subtype/Link/A<> +>> endobj +3511 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 421.954 296.579 434.856] +/Subtype/Link/A<> +>> endobj +3512 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [334.322 409.011 431.382 420.7] +/Subtype/Link/A<> +>> endobj +3505 0 obj << +/D [3503 0 R /XYZ 85.039 781.388 null] +>> endobj +3506 0 obj << +/D [3503 0 R /XYZ 85.039 761.463 null] +>> endobj +3507 0 obj << +/D [3503 0 R /XYZ 85.039 707.835 null] +>> endobj +3508 0 obj << +/D [3503 0 R /XYZ 85.039 544.838 null] +>> endobj +1326 0 obj << +/D [3503 0 R /XYZ 85.039 479.39 null] +>> endobj +3509 0 obj << +/D [3503 0 R /XYZ 85.039 449.986 null] +>> endobj +1330 0 obj << +/D [3503 0 R /XYZ 85.039 341.492 null] +>> endobj +3513 0 obj << +/D [3503 0 R /XYZ 85.039 309.967 null] +>> endobj +3502 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3516 0 obj << +/Length 2197 +/Filter /FlateDecode +>> +stream +xYoB(I9]|4i"(W_k)ʢ>€ ]i͍X 2gY4(J.E/Pe5bEʺfCN!K #ML#.aK4֋oñ~ 5EI۹xl:w,W]ި/m';~эAU'y:{"WHﶠQbX&/i_c-ЊQ5ٱwJ@Ti;٤5 +]mSy4(ޚkm]WyhWϏ`./wh(;6]ghc;?诸U&y{e2B%DY!l^hʠf]$_?urV[g4I>YF oIʄ,+Bt罧 []H`ڪ̡%I@ LJ$LNB%V) ?X Ǖ#fWf p +TiHx0J]87vo[a=O (U>=2bZ.1UX}:z1kBv 9gЋvy4hitމ:gM.R}e}^L;Eo-v)n9`z}/_q>IU3Rj;Nީ?Cv*GsB뭿 +k8ΜP5NE*}!ୃHhP>b% 6f0XaYL.bTb>{ >Y*AW=5F9FpTBڣC*,㢅|8 y _ݷ>B\x!TyJJɒ8{UNPQΏX|GVmI dȢ6-+0=, sy*KQJ +V5^qS!~qz=vvz8mgkh|gH:#CHnDuFHwvm%VH=sIiu R\RF +WYTZ9Vxz+!$o7fa$x |<5J᯲ $eL +e|JZ j + = (e#.spL<MU8:UچTYw•3oE <ȠZzrg& )#”Sb)G<'nfv66ccQ@{U7҃L4'Zll%ll詆& <̳ ?Qb%-ZӮn0 +c/{phsmɮcJR-keAp,> Kf^byJ4 B ָRi ?5yj8 Y΋pCsL_،+xҭ?#[sr;dA +W<>i"laa6`j#iꠉtUfMڔ}OݚX%o;f6]pf-`c ;Q4C3Z +_Nңozk*&f~xԟs) ljK! &z6 M8dendstream +endobj +3515 0 obj << +/Type /Page +/Contents 3516 0 R +/Resources 3514 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3501 0 R +>> endobj +3517 0 obj << +/D [3515 0 R /XYZ 85.039 781.388 null] +>> endobj +1334 0 obj << +/D [3515 0 R /XYZ 85.039 570.951 null] +>> endobj +3518 0 obj << +/D [3515 0 R /XYZ 85.039 539.426 null] +>> endobj +1338 0 obj << +/D [3515 0 R /XYZ 85.039 281.354 null] +>> endobj +3519 0 obj << +/D [3515 0 R /XYZ 85.039 260.158 null] +>> endobj +3514 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F20 1617 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3522 0 obj << +/Length 2248 +/Filter /FlateDecode +>> +stream +xَ"<x}Πaz'v+^t3\vJRv-́?wiYEMyv;Wv83e;ƥoWwo:vijՖ_޼8_o=_ady{3CWsz珯~wѣ eW7gb?9Gg;dzNiʗyqxԌOMжP}h8G2Dzȷ[8ʱR /Ĭ/\amv'7pAzUIJ١_#$irDu_9 W\fk f !{"bYX`y_.Ec`WV_1*'ޙTpy/bGb?^Јs& (vmVm +dKlAŹ Fᤡ隆 cD?c9}ǎ[wH:[@%U=ΞzދDE +uAobȴTI\xޱ\r2{E=畈{7s/s OLشm),P @?kI)it[@8ũ%7Wkvhc/~Sx|Vzt|R|KT?g@/I5@̊ ~}*Op+.mb)=890 z'-!pqmQG:7|F `$ + 5!C7 9+H'pas@ aK۸99L`;Є]w$6i U2#ôOtưUҫB(%e#is ;|6 <瀭,' 8 O6N7%b$)kHEH(pGK:Xe pDVϿQ'mG/zr9,(ۇQGKy!X0hQR>s I%DŖA$_smx/[/'+'OCJ@ KFzd FtM.eP/`Z^ARj&YYW2eqHBe]tnl]J5 zR (׵f / + 7mɝdhN9{a9GDm@Ldړp?Y&rb\(6H+/L"JZ^LccEj=3@*$X{ є\pX dfFn娕M82B87$a[YY6(6] ]lױWrpPC!%㿻$'5ܵJMY>cx! +89x17Ѩ u!#4 6( ZZc!ɚM_a\{'22"ѡn1L&vzZ\' 3QDC:A]VWQ x@)avݬy +w ]84 :M[ن@&Dѓ)#kAe؍‘S;hޔ$KYdrd0(Zr {\#SĀ眫rm5&82+M\;t+knhk0UN 4<ǤW#h&4@ yمgz8EǵcԍQp1@* 6,>ϔ# '3`N>RXR̭dF!q4* +/C +-3Tcwo6xBe{H!`5ۮe 4cR99f}OTe;2Iqi)7OG}jo) Qﺒ=bwI׏{$Eck+rh{> n O8EO Cc)`)9M,64Y])b"XMBqšۼ]!M6\lj80neB S~s}$U)jg> endobj +3523 0 obj << +/D [3521 0 R /XYZ 85.039 781.388 null] +>> endobj +1342 0 obj << +/D [3521 0 R /XYZ 85.039 719.568 null] +>> endobj +3524 0 obj << +/D [3521 0 R /XYZ 85.039 698.974 null] +>> endobj +1346 0 obj << +/D [3521 0 R /XYZ 85.039 624.261 null] +>> endobj +3525 0 obj << +/D [3521 0 R /XYZ 85.039 601.545 null] +>> endobj +1350 0 obj << +/D [3521 0 R /XYZ 85.039 450.539 null] +>> endobj +3526 0 obj << +/D [3521 0 R /XYZ 85.039 419.014 null] +>> endobj +1354 0 obj << +/D [3521 0 R /XYZ 85.039 282.475 null] +>> endobj +3527 0 obj << +/D [3521 0 R /XYZ 85.039 261.278 null] +>> endobj +3520 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3530 0 obj << +/Length 2194 +/Filter /FlateDecode +>> +stream +xYKsW Ce;OpD2k7*3utg^*B eUj,u[Z',3/}IXu5/7J +?=hXl©-?WdDÂG)5:Ǻј R 9A &sZ Oh|zn?Wz_Ak:rNGF¨/\ȂTǒHHaAƹKH` p lT? 39D׍ ~`6J籂3R~(`gpXiAq^UĐ6gZ Zd^"ԺJH=|2J3ح nIP@~蓨(G?hkbl-%ZU~Jjfw<ǭHyL8㕉=.aVy|#d+J Z;vCa6H'݌unv.::KHp:j™%yaeM6dGq0r +"Wc﵋N`Щu +^yɉa鋧iw((8sx ;ccBI|5.Bk,Bpp82zh_$u /a]>?¼1U)$|y>$.LQzQrߌ8VaEY /a2h>f$`g~h#`OeTkNDcS(6բFIטdUJN= +!!iQ5S=v +"P%2_rX!Xpŀ;N\X qpb5i5:g'#q +B8h@=#ӁY9S)+T6S8%<+,{ Fo2=#h,z@R:[K(_fPPY_R`DBy=7(!pO=O!0W~4fN>,f`g,`"Uܲ$yv.sq- x`tBqĝ(y79kw>S wo2_ћW"?TՕJ5v!XQkh1|GQ}"G߶sY^lgG< qS +ȏŰH{p3MpxqZ=jt ;nu,CGaK҆> endobj +3531 0 obj << +/D [3529 0 R /XYZ 85.039 781.388 null] +>> endobj +1358 0 obj << +/D [3529 0 R /XYZ 85.039 321.713 null] +>> endobj +3532 0 obj << +/D [3529 0 R /XYZ 85.039 300.516 null] +>> endobj +3528 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F35 1632 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F56 1642 0 R >> +/XObject << /Im1 2193 0 R /Im2 2261 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3535 0 obj << +/Length 563 +/Filter /FlateDecode +>> +stream +xڥTKS0Whh4x)$N}WƝΔ}~jW@8~@R͸tĦd2'Z>Fyp7ڛNhtfw${h]||M*%g 6gHoAtvy@<4 df$;(JSF-'"LF3pҒi%2G_YM5*a(vL;3XAMqL8Ƌ V"{E0a?uB!.ڧ-iLq ѴaHJ:&:v~ +Wqwᰫ +/~WD¡sl"PkmaSՅ, 5~^%&Xfmfހ} +M?4Ѣvt{`Y +%/7ˢUVuwsm#ztOxu| [^ȃ;Յ,VuP?v)(1G,a]aoEbI58K~P$ N=2. +[A0LC)4endstream +endobj +3534 0 obj << +/Type /Page +/Contents 3535 0 R +/Resources 3533 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3501 0 R +>> endobj +3536 0 obj << +/D [3534 0 R /XYZ 85.039 781.388 null] +>> endobj +3533 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R /F15 1628 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3539 0 obj << +/Length 2450 +/Filter /FlateDecode +>> +stream +xYIoF-0bbqeIO=H/!CI(\d>o+.1 f-}Rx_x~wiQ7] 3? BǑk k7NJ}Fwk< l|Nw*$r͋B +썭v;֡w >boz-ē[?ؒLh{l:boB7L,IR#'a|&s9V5 syfyL7 NQ4@{#R|q5n)N6>'$4ӠZ@*,N~!j7'(B9"2vws=ݾ^,ϳ5Gjn?#\YνϵiQD`%sji%ŽŎYE`gxy~EUW=ȳ{Jk4 !С5;8q"[ 'h#r5ӟH%ۺhdK(]wf{&߮0PHFggRbbOi`Aue FGF)LwHXסї +[j*=@v`n%ډ5;2p{ "YH J*blj굅JO0heIiA\fwǞ_|4]nw+P{M7Xn gn05"Fz]Kهʞa偼|z%X7J-=~ՄX+pes Mtr0ى18\`ø~ +=]m Hŋ ѓ ]twqd{gT GK遭i{•2M/*6?O? kq!.hߌL]h#eMqm g&|G%-c]JLGSopVmYyocGT!VKtܟ}e%ny?[ P<%LO(!D'l`NP Rh]_AG+ +Ӛ yH:"Z'hQ61&FPpC +±!)3"58t (Nbڟ08$ u!Vq ) N[4ٮP5*afH1sT)a8Qg2}o3Ĺ,5zipt²k lRuEo$w5eBm#*#dAaH_!gcPʸ/f )XJ\&SxԒS^C33\ߑEϒůvC>] v.p4A|ޜHV㲢d@J-{z3)S/8g.)Qsi/>nFPD4ZXW#f|-ʉ󯡼 +CT2t_۸8endstream +endobj +3538 0 obj << +/Type /Page +/Contents 3539 0 R +/Resources 3537 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3540 0 obj << +/D [3538 0 R /XYZ 85.039 781.388 null] +>> endobj +1362 0 obj << +/D [3538 0 R /XYZ 85.039 761.463 null] +>> endobj +3541 0 obj << +/D [3538 0 R /XYZ 85.039 646.155 null] +>> endobj +1366 0 obj << +/D [3538 0 R /XYZ 85.039 602.617 null] +>> endobj +3542 0 obj << +/D [3538 0 R /XYZ 85.039 571.092 null] +>> endobj +1370 0 obj << +/D [3538 0 R /XYZ 85.039 461.651 null] +>> endobj +3543 0 obj << +/D [3538 0 R /XYZ 85.039 440.454 null] +>> endobj +3537 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3547 0 obj << +/Length 2662 +/Filter /FlateDecode +>> +stream +xZIsWHUY %7/3&5JCCK$i +~$S\A @݉$ mO'q~L gOp&D!]/~yױS'W4enattlju7uϟ^Mߚ?~zucwLu>V`;L{L 0q9 Ϳ.~әd / ڎd{ſ]x,3ʘ^d{14|N75g4BvMq(gZX9궨AY9jwV^ih5ϭ٘y1ïgnd"UX HPi KID_LgahwaNԒ]Ѣ|TZNd<kU-ݩ%ʳ)JUXFwe _uUfB̍myI"mnZ"Onj.-ZD6ƒeDث%Ff.+o2}̼opZ\]J  T˝GC`;+gg*3l7I`mqwJsֈHWirs@j/ ۊ|3EJkiO"R)ڼע'U[E[srj<QVOe^7`4"!sH*EEA55СhRBO8 +*(gm]Ps`Z}1B^eT* /OYu'm:20K1fm̪y4G]z3KA=3]vtF6'^M +don|Vxs3rߍe!t ,J kZE?yW_5تbp, KJS)aTq;1*8cbj٥4%Q~Lm;Iy2‹{b.dJh|>@5h!t ݥ*&C::UQ6A8qBo79})"~Kۼ߼t.F"qip{ N2。l~2/=L~wX~TMYlwC٤1Pn=sNAtN(1҃Z*]HWT`QT aH Xۆ cS"o-ʂjn˄"3gAXe>t|[Z ++ak< uھq2((go#3 LjTa;P0rƪ+J<6|N +GF6WoT%oTR_pZX?8/_(5s]3 ?ND\y}y_( gݝ894$' ҹ *Zՙ= +ݧ+wRg "d~F}' 3vc׻oit_D8~lIW?9Hendstream +endobj +3546 0 obj << +/Type /Page +/Contents 3547 0 R +/Resources 3545 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3548 0 obj << +/D [3546 0 R /XYZ 85.039 781.388 null] +>> endobj +1374 0 obj << +/D [3546 0 R /XYZ 85.039 255.509 null] +>> endobj +3549 0 obj << +/D [3546 0 R /XYZ 85.039 234.914 null] +>> endobj +3545 0 obj << +/Font << /F62 1689 0 R /F41 2104 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3552 0 obj << +/Length 3822 +/Filter /FlateDecode +>> +stream +xڵZY8~_ᘗmذoL_]03*C\l㎉بBH:Ry|8E,T1[q|D "apo,"*fwDrW헻7_ TpX<޿z;Up'~u0;>q +ip~|yP)r" ӥmyѬrgGhGa\M0K7nft\Xq*BEaN*q6![q{vsoxT]@4ՀGG#3Rmvhd`qTܱmcw%~Bbiy8(MUP5nasL}"?r<, l!_(NCN^=A IV䩱ߝOLEJ{;TbiĹJC<{Z#Å8`TլA=Ь_t)Q0YpXYxglmB_x#ьtL5C0S}V}!w _PQ)*T +402|D+ :mv +]S:'ya8#c9lƩ1>y^z18ɚš/&*' OyI8`']GƐ =ݕUmMF 7_f (db?sa5XؐʰB ƺ ևExRɝ{!NY.i ojLe' Iͪ=Fu[㶓>>zwSU<4T Ë~gk&[qDwʕGY󃝮f&r[YT2=A( qbjd*19vZgh48p)BI(4zvMʑ:( Jƌ of?S. +ޚZVΉiq0Z +< \W($"ed4mhh[Lϖ`v$mtj4$^ f$ڳ%V›OhTaĮ3.pN!* mo}?hɌ9=3h&SBޕ֞뒡5y~) +(c'+!(A+NA$7^ۮbv,$1J+_! r0~q{$uX}{< +[і\ E,[$%"C +_BF P",ݙOI$j"[=m9rI|JbT碥e_r1$h6lu/qz'~@9^i%;jMS!fpohNwI%+Ťo_g{~pX J/H,$zre_KEBvlzA#qoU{BJHT>&QHʬIp[2ol+ |:Zj `< tدbv7R]!0F_c@ +a6,ힾa^/A'M}B뽨zOYZKXa3F +&8Ru&h-isT|ɼ*꓃'yq~p[k{Iis }[-ēeChN٨$/$ӍTy" +᧿ I +r*Zcy'l-.nOOF]*7l:]]Բ<9]HswдG~Q^JNu:-@^º)XSS>xr:eR./^y+ec\+I:10HGy=;*_~|ZĝYHIɯ\00g|:1fh)3|zsϟ&VJ0R#F^QrRKbHUϩdM8jl 8W쯐SS,phRdQ:ލEͨ?.>s$$[q:OB 7\+??5DT0IN`9~DkYSc#&xIN-GNP"p5Mt pmƂ4;ixH~GN/)7> L]6veCÕ3?RՔ (Ʀ'ĥnqֵ2΋8Mt}.[5tlR< +W+%3sNc1FM#6D+{*YWr}CR;Wa$?@w?SaI7/ݢ6_-endstream +endobj +3551 0 obj << +/Type /Page +/Contents 3552 0 R +/Resources 3550 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3553 0 obj << +/D [3551 0 R /XYZ 85.039 781.388 null] +>> endobj +1378 0 obj << +/D [3551 0 R /XYZ 85.039 626.845 null] +>> endobj +3554 0 obj << +/D [3551 0 R /XYZ 85.039 604.129 null] +>> endobj +1382 0 obj << +/D [3551 0 R /XYZ 85.039 250.134 null] +>> endobj +3555 0 obj << +/D [3551 0 R /XYZ 85.039 229.54 null] +>> endobj +3550 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3558 0 obj << +/Length 2202 +/Filter /FlateDecode +>> +stream +xZnF}W(bH./O'HA}`$FfK*IwnKQm]4EpoΜ93??džxy̜|Y፵G^Kd|rdrNQ;g9=y}43?8W'A\'SܹfGgϏeoG/-աB5/a'?[MΦBĄMa.nYGSn%0rUvMoqKrv]ݗqAسK` %KkKKF& k>@gTףȋįVpڸ:ց3Gu+MрEܐ{SW+omM`b6=ERQIuSVh{ 4d٦Cx.yPǨS"㩋-,\n,MwkagB"?1zoD;ie*!˰:k} @<<Bz`OBbᰋJ09~xqdK bkK},K`dūʛp,οAg?~ Z/BΫI!%H`RNmoB0tC&, )`d7Z;+*XP6(6TWc|זfBp%Tzy \CIiH5L5kMyJ׭"9@j (+~UQu^Wb-yzPKd{K0"WTBw٘xbW#Ϥ'C! j`ɣXS#sjo 1*`܂:)Ė>xt.@`Cf)mm`lUK5͆E3k{x*%+ޠ$ +4pTh)%p%e*G 9TC:kre!^_A w4ky\e͂iC-b]FX/Z7NOlI`s"Dti%/{˝jcCƗ{Dbȭ;w%!Z_ZLMq 0𭭅RNh7˯Eͪχ$nɨ[tpC +2h|^Z +;35%׌N׆i!k Hj@:?:{)so:R~ ppS[? >4UX>7ΑG;k>AČ`'KfܝR{r$|ddzH[5 A}ꔏ<nƦ4e.ek+hv3e6{+mR=Z*ѝyڕ..`N0>ג'̇rwqI@jR~VznOgR*[+"7{ށ#JqlK=ujktHxz(@^}w. E-endstream +endobj +3557 0 obj << +/Type /Page +/Contents 3558 0 R +/Resources 3556 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3559 0 obj << +/D [3557 0 R /XYZ 85.039 781.388 null] +>> endobj +1386 0 obj << +/D [3557 0 R /XYZ 85.039 761.463 null] +>> endobj +3560 0 obj << +/D [3557 0 R /XYZ 85.039 740.731 null] +>> endobj +1390 0 obj << +/D [3557 0 R /XYZ 85.039 658.326 null] +>> endobj +3561 0 obj << +/D [3557 0 R /XYZ 85.039 637.732 null] +>> endobj +1394 0 obj << +/D [3557 0 R /XYZ 85.039 554.721 null] +>> endobj +3562 0 obj << +/D [3557 0 R /XYZ 85.039 533.524 null] +>> endobj +3563 0 obj << +/D [3557 0 R /XYZ 85.039 430.743 null] +>> endobj +3564 0 obj << +/D [3557 0 R /XYZ 85.039 403.615 null] +>> endobj +3565 0 obj << +/D [3557 0 R /XYZ 85.039 382.984 null] +>> endobj +3566 0 obj << +/D [3557 0 R /XYZ 85.039 358.584 null] +>> endobj +3567 0 obj << +/D [3557 0 R /XYZ 85.039 340.444 null] +>> endobj +3568 0 obj << +/D [3557 0 R /XYZ 85.039 320.419 null] +>> endobj +3569 0 obj << +/D [3557 0 R /XYZ 85.039 296.019 null] +>> endobj +3570 0 obj << +/D [3557 0 R /XYZ 85.039 275.388 null] +>> endobj +3571 0 obj << +/D [3557 0 R /XYZ 85.039 250.988 null] +>> endobj +3572 0 obj << +/D [3557 0 R /XYZ 85.039 230.357 null] +>> endobj +3573 0 obj << +/D [3557 0 R /XYZ 85.039 208.447 null] +>> endobj +3574 0 obj << +/D [3557 0 R /XYZ 85.039 185.932 null] +>> endobj +3575 0 obj << +/D [3557 0 R /XYZ 85.039 160.925 null] +>> endobj +3576 0 obj << +/D [3557 0 R /XYZ 85.039 140.294 null] +>> endobj +3577 0 obj << +/D [3557 0 R /XYZ 85.039 118.385 null] +>> endobj +3578 0 obj << +/D [3557 0 R /XYZ 85.039 93.379 null] +>> endobj +3579 0 obj << +/D [3557 0 R /XYZ 85.039 72.748 null] +>> endobj +3556 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F65 2099 0 R /F41 2104 0 R /F70 2201 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3582 0 obj << +/Length 2193 +/Filter /FlateDecode +>> +stream +xmo6?Ċax4M.a(2%y4~wvye>eY ljL|Lh%aǦ,J`4=O7|h2nE 7MYXw ^.,m fe(ns*p +ZVvʒ<+<~[vE-T5g [!<x҆p>!{`Gp)hDAљ`S:Thg4Տ0DYL%-`-d2TzF"J"REѝ DpuԸ^µꊾ׺7>\.qUd NfAvwNn̢rzۑg(Zpm!lzXs1T2;r/* z>Un/9^pyEýŚD5o渭 nId\K FΝ1Ր05+QnҀ^mHͣXYЍ4-rsk37Ɩ +;`8w7U&d/}m[x7zUu*M<>MJJwR) +-ʗD;/X}WÆRTUUT7Xu=`sݞ*OEr~"U%c9z,꘲-լ +s.&eT}X'oazVr&%YJ~G 䰯# +LVm/vi]:SĢ%aruEZ 4'uڶl<4WX-U(-R9<zetsߔ83.&`) }KFkމz"~>{6:l)okc.TqH&_: mޡ!87gyW|yW7uobm>莤qߛ$`xHGHްyܨW}q zFendstream +endobj +3581 0 obj << +/Type /Page +/Contents 3582 0 R +/Resources 3580 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3583 0 obj << +/D [3581 0 R /XYZ 85.039 781.388 null] +>> endobj +3584 0 obj << +/D [3581 0 R /XYZ 85.039 761.463 null] +>> endobj +3585 0 obj << +/D [3581 0 R /XYZ 85.039 741.409 null] +>> endobj +1398 0 obj << +/D [3581 0 R /XYZ 85.039 686.912 null] +>> endobj +3586 0 obj << +/D [3581 0 R /XYZ 85.039 657.508 null] +>> endobj +3587 0 obj << +/D [3581 0 R /XYZ 85.039 602.784 null] +>> endobj +3588 0 obj << +/D [3581 0 R /XYZ 285.909 608.758 null] +>> endobj +1402 0 obj << +/D [3581 0 R /XYZ 85.039 442.729 null] +>> endobj +3589 0 obj << +/D [3581 0 R /XYZ 85.039 421.532 null] +>> endobj +1406 0 obj << +/D [3581 0 R /XYZ 85.039 164.777 null] +>> endobj +3590 0 obj << +/D [3581 0 R /XYZ 85.039 143.58 null] +>> endobj +3580 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F38 2158 0 R /F41 2104 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3593 0 obj << +/Length 2091 +/Filter /FlateDecode +>> +stream +xYYoF~[)y,n}Rч+r%-̫$3{Pr;7ą$ 7H'q9AL̝aәVQSg#NꦓJ,YZ?vV9S;fYWf$Wwrԏ;YDvaZɱZ◳6qH;A_\'H]KIyF I9G&r^auq낃낣@hIt'[۱xJE%?zhuRݡa# č{goiL^ITcu53]aFҋM3ݡ(^:$ e9P@A \'KCL8I}tB'dn6 +AVqgJThBENGkf݂04g[A $uu(#}E( `uc .nd^BxLm> +3LJO{hm[֝t;G7~0a&X Һ$xqY+tr6h\'-2D-%>mp2A\Dߝ'@ 3&QlѢ$!rVo^a%v1 Nj/%l<78H; z:1;fwi/}U.{ֻd>ۢ7LZgD׃িE,%pCy4f9O3&ӼӘ}{ҍ#̘H]/\[aȁ`[9/89`-51ZH[(F^wvHQVJ\u꥘b0ᣠp c]3JdoLI&^E!x{&HSK`L%_P*^NnC>b=CII+BIĈǾn:;7w@5;bhm'ǮDՅT.&n`DD._D_Cm%$||҂px_ @i!Aj +oE\GݾUt}L#z-A /pa p̳C}D-Zĕ,li7.h)~g1]NM6U'س8/>]bd; BЫaLs`;SH>V[zSi{'~`oM%z8F!!ԓ$"S&*:$G5rz/kX;~NOG~g$$ >'} +LeC)(eGK)rz7߮+9K|Wf[YƺN.\ WȀm䬻J]a1߈X&;Vd1.)v*3j! [ o |JD*g){W\ҰJoJڝc9oY-_+;}Z. VWWf!2شvQ咪;;6%Y{ DK[I%cZC#zWWF@ " +Zg\ +=Uyr`ֲaL|1jhh5J9x! ?h)[Jo]оke +jPH+'Ը n-TO on)C꤁Zpq]g5zoCMK^ՅRzܴ:gpVW݉ 4s9[ >3Y^8g-o~j%F7 8qŒ6`5_N9 Vd!54Yr*SM +\C`(#ÁBX+7{ĠíMd];֟2z/P{⃩R/ ח{e5=j2u8aYF;'۲{N rat\_^}q&heEM՞6c 0`:~NY9+d ㇬.7$u5J; Aendstream +endobj +3592 0 obj << +/Type /Page +/Contents 3593 0 R +/Resources 3591 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3544 0 R +>> endobj +3594 0 obj << +/D [3592 0 R /XYZ 85.039 781.388 null] +>> endobj +3595 0 obj << +/D [3592 0 R /XYZ 85.039 758.673 null] +>> endobj +3596 0 obj << +/D [3592 0 R /XYZ 263.137 764.647 null] +>> endobj +3591 0 obj << +/Font << /F62 1689 0 R /F56 1642 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3599 0 obj << +/Length 698 +/Filter /FlateDecode +>> +stream +xڥUKs0+8♠Hy6QL; #єW%0vHgծvVȄLC3 `B85=tu7c"B>$b<^lA@Yw`+Mf1rkV&jaldʘWZL-ǓբxץM4Yހ:( p= <k;1.5@_+v`oi^95[*TTRytTdFS z6?I_h)kjX0QqL5pMd+xn/~]}h1v o4~oj{jkQ$b;n)x/iu7mo +.i9-v\զoOBvOvgYИyVKJޟpN;$DKZkɻt]&ygU'j\Vw5Y$\yXt8ˣkM)!GKM(tg-UA2mlřhF2X@KNoB3eq1|a&I &luʷx+笩wJ@VH-VImi; RK͢}CQ_Eo77xendstream +endobj +3598 0 obj << +/Type /Page +/Contents 3599 0 R +/Resources 3597 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3601 0 R +>> endobj +3600 0 obj << +/D [3598 0 R /XYZ 85.039 781.388 null] +>> endobj +3597 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3604 0 obj << +/Length 2614 +/Filter /FlateDecode +>> +stream +xڵYoFB}0D|>&q6>Fa%R>TŇ,9][ 73koo,=WlU^f]xa}fr.BU&:G7nWo}5z&·}w͵Ocs +k~a?Ƹ{U8#R <%S9m9cgi簯vn-wz< mx^~ꦔmxn++ +y +/3( +5Z"k+8P +Df0C%tx.(AI,20ѡY#Z%˶(D5_•cE,H +Ů7upFk-̱'_8ժ&=1yAl`6`So3-;"kXe + N^s-/pcϛg\mg.yr_:T}#t.YFN; ـ]fb"VG]| k3o$NQըE;VmR>w(^eWvm2KKn ڌ1k@PcEzMɡkPX+tӊBʺK8l2wUP\AmV&Uqi6mLiIkqooxg$I{xF@OЀMag0c|!w"Z)fAi{#+=w휕hP0BZUӶf!*4@HDSO@@<0\X 5/v:$ۢXh?qҚ@&kˎG@_b"VDE[mq5VH m?Fh\k~.:Ɓ1K H+{@?x^CAnelr~HK˄ +Nq +T)F + >mm';lBj8hhFUe(\W*0fϹ!RpVB-% 1&\COu!Voׄl\|f)I<{Z^ ͸N_?pg9$) +yE(ŊE葷d6h +~,F;\ѿIKŁG)[<~ty ʏ)bLR3=xfhQ|eUq4XzyS+f:yfIV }ɇ (^7\1gC" 55 ,fl9oaj6[9E ym +plNspE1+)O-󿣬So6R1-%2a{RhS;a8)gn_J}ŬRteX$w,!GE+WsrEɢᕭ~Q3݆@>@rCKq#z.@J^ +u2U l@U3n,;$;QՙJ#b39j,Yc"/쬛n&0>kt[nNbql|ѫjoii Xۚ8ҕ4\rnlՇ3$>sٳɷkz*=JA҂Q~K wV=W= %^s}Jdr'ky<Ɨ >$P?lTӀ:Ex>\%3~LCILKĿv_t"0ꪬwϘ(=Wi'-aƕ/o~Əd嶃lZBB+?J0G$*uQ ר`xO˥?PgQ +E^T%S :;T_F3O}l! +'5x%v~z_MR&}9O> endobj +3605 0 obj << +/D [3603 0 R /XYZ 85.039 781.388 null] +>> endobj +1410 0 obj << +/D [3603 0 R /XYZ 85.039 761.463 null] +>> endobj +3606 0 obj << +/D [3603 0 R /XYZ 85.039 667.239 null] +>> endobj +1414 0 obj << +/D [3603 0 R /XYZ 85.039 612.119 null] +>> endobj +3607 0 obj << +/D [3603 0 R /XYZ 85.039 585.505 null] +>> endobj +1418 0 obj << +/D [3603 0 R /XYZ 85.039 377.326 null] +>> endobj +3608 0 obj << +/D [3603 0 R /XYZ 85.039 350.712 null] +>> endobj +1422 0 obj << +/D [3603 0 R /XYZ 85.039 263.87 null] +>> endobj +3609 0 obj << +/D [3603 0 R /XYZ 85.039 237.861 null] +>> endobj +3602 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3612 0 obj << +/Length 1134 +/Filter /FlateDecode +>> +stream +xڵWmoH_a>lz~AZR W;ǿ;q)=;;3 ILx<VQA%+xI!蓳`:C6bOD~NN?ItrOj5Ֆ:ImFJۻbj/a!l(ƎjvUMg圅he6Xv(Az J ͰLDfw7;A5:ZdͦԺaPz>16 +q%Q;<(j(%ujNc3 p$cGML‚aͲJm!R)ws}QkbDgUWst 3/"fVʷ%|Z ֮4[S֣-U=--͗p״cTaWWy91(^XNTvT E_WE~mSelS5me+]!JDш8l>*?j9YTn{;:nU*U5R]9]׹vwie4> _{;Vd endstream +endobj +3611 0 obj << +/Type /Page +/Contents 3612 0 R +/Resources 3610 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3601 0 R +>> endobj +3613 0 obj << +/D [3611 0 R /XYZ 85.039 781.388 null] +>> endobj +1426 0 obj << +/D [3611 0 R /XYZ 85.039 153.561 null] +>> endobj +3614 0 obj << +/D [3611 0 R /XYZ 85.039 124.826 null] +>> endobj +3610 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F56 1642 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3617 0 obj << +/Length 2003 +/Filter /FlateDecode +>> +stream +xڽXYoF~ׯ#<}siҦH@YDBRV;aE€73JNɩ :=?x—ɧbo'ӱ-<b |mv[ S^uFחg+$3 +7Yās7s@[) mR̔q Ksp%w39uJ mpbI֟VaWbx{txU@Ӧ-jȓ 0v(vWUܒgNW +:  !jtup0\Hd YWmP~@!|S(0xYB39X&:<@@~srڬߌnEM"ƎK#Ǟ 86oI<[qV37"U MLC#&Gkd% !cw8wϻO"޴If*=*#@8]Z +]`ls&0b>UVE\竬I tn;u-`cWnyn<ֶ*c3LϺsl7e-IVZ s.zۦRkҌme*!A@Xz ǩXA%{}5lO]W5O v ~Țlw*R"R%ay\]g+}f_ؘZ1J0#bP&hR`xggIۆ}pyͩ :h})]tȊN+C L]x=8?9C: «^yG90[3&]6i9" ) Ҹ}\)P1%ұ$C-=:)7,‘b7](&}$l\=nsSCF=[ $N?]zu^Z+6 +MAO8G@ ^@W?^hGJ֮ϰjՎeTeֵ,><)+ʝE_-]ߚo檴zW@3$՝.sJ#9s֥k Lĺ}l/U=2{rWdOxQKVZZZ#7"|!jbHO_}- .'_*bl>tIVp~@ΦMIg:_q650 J{*9tEݾ!ŨuH8F \]幋Z`χAP: [ ?9Yy61Pz:7Rendstream +endobj +3616 0 obj << +/Type /Page +/Contents 3617 0 R +/Resources 3615 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3601 0 R +>> endobj +3618 0 obj << +/D [3616 0 R /XYZ 85.039 781.388 null] +>> endobj +1430 0 obj << +/D [3616 0 R /XYZ 85.039 679.868 null] +>> endobj +3619 0 obj << +/D [3616 0 R /XYZ 85.039 651.132 null] +>> endobj +1434 0 obj << +/D [3616 0 R /XYZ 85.039 651.132 null] +>> endobj +3620 0 obj << +/D [3616 0 R /XYZ 85.039 627.814 null] +>> endobj +1438 0 obj << +/D [3616 0 R /XYZ 85.039 584.48 null] +>> endobj +3621 0 obj << +/D [3616 0 R /XYZ 85.039 557.865 null] +>> endobj +1442 0 obj << +/D [3616 0 R /XYZ 85.039 557.865 null] +>> endobj +3622 0 obj << +/D [3616 0 R /XYZ 85.039 534.548 null] +>> endobj +1446 0 obj << +/D [3616 0 R /XYZ 85.039 343.346 null] +>> endobj +2945 0 obj << +/D [3616 0 R /XYZ 85.039 324.475 null] +>> endobj +3615 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3625 0 obj << +/Length 3010 +/Filter /FlateDecode +>> +stream +xrF_ҋ*+/)YkeeDl$$"`do_l)*agnI^ĉr$9YGXᕒ: PkXi仞c׏ԣo^_މQ=λ p'0[SN37iŎ53E-wRj?v.q_LRoEG|'nS7'{#QN1&,YvepFQ=꒙.w5h9KI !.`j@ {fbecߒ>#I TTA /iOarރQ)b'z8+sakPA롊@Kʜ\&Hi2bdi^yۃ8!˟IEpdՠA/Ǽ.y#1 bԴsŸsy'B[ =+"!~Ԃ~uoy޿2zBL@tȕgޖǮLȖKzTg!y(6KXX C l +3O*Bvu,%W3d5/EVZה(6 bb/|/ɂ6ޡ7ȖO憃Ea?Q[GЁi4|::VXEU@IYvc]41 MMB,#A l8IJ + ROGBaz6c/mLptX^83HˋL+pu~- ˜)N4,[5x@q g1|vh <$k(eEB(ح!Egr.!fcfSgƹywo>3jmpR5 A?8LVQ eLco1^%]WC/NpH[w~fk]Ȧ΋| oOy宺.C>}5׉X$P\߄^Ɨ>WRPMG1*^&-pSlk4߰g= <Xs ɼ0@*[tR7ӊ$6*9( B5c[OG\Tr/WHN XFRa\P\~5V?~M>9QG! zǐS4T}9&oZbcVȮGO"|, -LSS^YܭP+ې+=91Uj(>;MQIlŨ7r,PJ~MActPR'AGV^b]qT~'@ + +L$pPk8l"c08A&3#`Q7g⏙ﻡ +f<9݌l̅@NX!N޻xt7USH>HwCT8S>Qo5q۟f=7 +S#gU iL>R.qϯ:YY[i,@5=-syxJ F>jY +.||-|AmO<m>V$RW6Fgh +s Lк˝rNPp)ljc +žxq{+),!4pfi'a:rѶ (%h(rW NwF&KduwoUe\.\6 )5_:~!' wwaC)EUy%/υ7OS,fcbw\ZL^q|*osM\޳e05TbRw6N2:,d1Q%+†:A}3 M^ඕmZqI70aO^ًSgY} =TWD#qtK#{nݷk.Lb{E.%lBN/9;F9r}ͭfiac_#w$jxg\Zwpx3ܛ ju 11C!)Ĭ>bAMj_]nfRO X@BDτ4:##^OXhq Lf†m"AbޕJ`:dMyh2"n㡡2M800#PҨ' R:^Ǭ{@+]*[ 4}lMq^e:B +IS>;+z{̕TƊ eí~-G^DkI<ʺy^o]]޻S.SA?>WCs??`S陟NO=fEyh~8 7n`WxwYSE̽#†9$Ppʁ3,qa5xz!4[{"1i+3*)-n<{I1ʐ> endobj +3629 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [135.619 595.065 177.399 607.966] +/Subtype/Link/A<> +>> endobj +3630 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [370.468 595.065 403.066 607.966] +/Subtype/Link/A<> +>> endobj +3631 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [466.071 487.277 509.276 498.967] +/Subtype/Link/A<> +>> endobj +3632 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [132.201 473.728 157.678 485.418] +/Subtype/Link/A<> +>> endobj +3633 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [111.316 446.327 330.942 458.319] +/Subtype/Link/A<> +>> endobj +3636 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [377.921 352.358 620.096 365.26] +/Subtype/Link/A<> +>> endobj +3626 0 obj << +/D [3624 0 R /XYZ 85.039 781.388 null] +>> endobj +1450 0 obj << +/D [3624 0 R /XYZ 85.039 761.463 null] +>> endobj +3627 0 obj << +/D [3624 0 R /XYZ 85.039 671.062 null] +>> endobj +1454 0 obj << +/D [3624 0 R /XYZ 85.039 638.952 null] +>> endobj +3628 0 obj << +/D [3624 0 R /XYZ 85.039 612.337 null] +>> endobj +1458 0 obj << +/D [3624 0 R /XYZ 85.039 430.884 null] +>> endobj +3634 0 obj << +/D [3624 0 R /XYZ 85.039 404.572 null] +>> endobj +1462 0 obj << +/D [3624 0 R /XYZ 85.039 404.572 null] +>> endobj +3635 0 obj << +/D [3624 0 R /XYZ 85.039 369.631 null] +>> endobj +3623 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F35 1632 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3639 0 obj << +/Length 3280 +/Filter /FlateDecode +>> +stream +xڽZ[o8~ϯ2P"Mi66>(h+KI{.$-َbb^s޹ 8JΣ*ϳՙ{_<==r~6{s4d\8i2UJ9J4bv9^^`\\/rC;y|w +[(Kՙ(J׫۳X)#眚S/  *AK0T hA +8&m&upP9YZsJa`MM[p 6$׾L5* \BB..Z-m(T=S"c:FSaGybzҿeЦtEV^p9l&S)=5(t6p +TP:BW>=EUӄG⚧tY\Bf<*z"c"I~GֶYC)K("]O8_f3ZʬmfыY^9%+(`ωӀ5ͭoRF7zzkeUH7.=}{Pxq`E5ܓ5tmSmY6'A褢ƣ] NΪǮtt`;E(:qcd~tcGNYҾD7^d3Bz*Yq~Bkt}ZU~.'B8@EwWhIwj-P6}w_TaBsr., NUt˳77PA*ʨyHQ(87h3Z|Lڈ5C VR E)> +6T@v V%_亜z彖Iڭ 2_jx^ J [7kQ<5;E=9{=ՐqJ:# *oBg%#O)tdP C9w'9*h:61̜Ff ]19^F7X0xӨIl Z { G0BFU2t'SPwnf\ ~`2&8$ѥ)$IC5Ev:t*Kh-y dYt6pFDp!]굤kE/rWfmwMoeSRx3WOkX*h@㺍U;wݲwzUcJDv.;+hl p`sHK)-?ejlTa U.#θ&g'0L"HC'Xl 9% N@!\埌(es?L#Ibd_=6;'"eT&pL 6Is5+s[v}XݳzӑE$>{t`yS6?GL-TBrK' "xFD9tu=iy+В\Dn)r(!$#EM݅2t(%nֈc,CGk&-8!^#0O#.8R]KtD^0y$ Ã]zz0d9ϩ9ι-NTs{ 1K#E nMGśa.OY6+'t#L=?۬ }0DIȯ ,IX n=#K줻e E<4 +zpC -.rɞ2I2݊yecPP!KU"xq뉒~bWk?54|Pw#x|&2L#2TF b)~y>դjW9{p(௣ׂ 9ؖrwIeQ}&p1@hk/jSӺ][0bt=0bL%`RERi^X#y@,vPG2ݸj7E,| +yЗO>7) .S1~b8戇B3d':@% b8i&Fd4Cc!'| l7^ֆ0Q$b,~9*zd6=XznМH&Т%hPev>oڰ;̡F9.ӻrF+ƲEt(c354[=!SC1R77w';{r!B^Dm_:ILP(c }g2۝L89Y= ?e"YDy g^BR:͚mñV1Ve63zmr|HIp1[9 %A`w?YIG~(ڽG"N1g +N /o:`~Pendstream +endobj +3638 0 obj << +/Type /Page +/Contents 3639 0 R +/Resources 3637 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3601 0 R +/Annots [ 3642 0 R 3643 0 R 3644 0 R 3646 0 R ] +>> endobj +3642 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [443.558 712.238 717.944 725.14] +/Subtype/Link/A<> +>> endobj +3643 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [129.766 698.689 348.214 711.591] +/Subtype/Link/A<> +>> endobj +3644 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [338.851 552.836 555.269 565.737] +/Subtype/Link/A<> +>> endobj +3646 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [382.155 461.982 612.784 474.884] +/Subtype/Link/A<> +>> endobj +3640 0 obj << +/D [3638 0 R /XYZ 85.039 781.388 null] +>> endobj +1466 0 obj << +/D [3638 0 R /XYZ 85.039 761.463 null] +>> endobj +3641 0 obj << +/D [3638 0 R /XYZ 85.039 729.511 null] +>> endobj +1470 0 obj << +/D [3638 0 R /XYZ 85.039 527.745 null] +>> endobj +3645 0 obj << +/D [3638 0 R /XYZ 85.039 492.804 null] +>> endobj +1474 0 obj << +/D [3638 0 R /XYZ 85.039 407.672 null] +>> endobj +3647 0 obj << +/D [3638 0 R /XYZ 85.039 385.811 null] +>> endobj +1478 0 obj << +/D [3638 0 R /XYZ 85.039 180.551 null] +>> endobj +3648 0 obj << +/D [3638 0 R /XYZ 85.039 151.147 null] +>> endobj +1482 0 obj << +/D [3638 0 R /XYZ 85.039 151.147 null] +>> endobj +3649 0 obj << +/D [3638 0 R /XYZ 85.039 129.954 null] +>> endobj +3637 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F41 2104 0 R /F35 1632 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3652 0 obj << +/Length 3198 +/Filter /FlateDecode +>> +stream +xڵZYo~ +.m,Fu4DIH͈߳Zh̙,Yh?'(vm?{Յ[ȇ Wf8=e;aC&o߇^uIz9M̾Xß.'ן-߷(qߵ.o]"YY+t #wU0;gBV5ʶ >*/gꇛn 0qrq]; ;u fL q?ji9Cpd ˔Yr%/(FKS3DFv]JuY \Ȳ} +, ij^Nf…eZ.پ>#Z0K=,@CTj}j?xj׳&tv?mܡE +P9+όe% / 32`&A#\kӚ |`]=)Eֲ7?D 7Ң`M]8uH.Hme育J--)sgCWu`w(vf^h K wRgq!`]-Zyvj9"idܮ +r>>8xRd2g8?@1"OmE/rvzA$.Ed|梬jmۊV/Α,rH\-HG{0ȷ:vEgq?Udf4|= ~$Sqy` J O[Hftuz*lsVܹf,(Pfrݨ%Z>:˱Hx~ e'~uvfn WL|+a\]bmP1v;8M[bRZį2uȫB(BZW,uth-De?D!-`SVS  +! t$F8=y%qF76U$;*k j3А`>>d7uL9W #u K }WlM#̏T͵LܨDm dp ݡ}M 3Yޝ=z.ꩵ_?P_KT4<8EPr&oMtRmK)`Ie?v>!yN'"@>aZх1N ;vcCQvO@*[m.3\ݪUyΜ=ShKwH:`΁BJB˩Yrrra>(J׏ݰXsOf{-nHll\r) }:1<%X=VU" XDIbvE(l,e&繬5y1sL>2^j`$3䄨ȢXv9&H,vp;P$9JȌ*v\>y"poƮ͂>B 6ˤ Zp)Qh +ҝc/+)Wզׄy]nj\kmFoNoR*W%kP21-;5`ڹ5C)X}KSCF `?HZ9nxt9A9g rƗJsv<ٲ$֪e#H6I(ܭYm\+p.> endobj +3657 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [394.325 421.418 452.136 434.32] +/Subtype/Link/A<> +>> endobj +3653 0 obj << +/D [3651 0 R /XYZ 85.039 781.388 null] +>> endobj +1486 0 obj << +/D [3651 0 R /XYZ 85.039 708.207 null] +>> endobj +3654 0 obj << +/D [3651 0 R /XYZ 85.039 684.889 null] +>> endobj +1490 0 obj << +/D [3651 0 R /XYZ 85.039 575.05 null] +>> endobj +3655 0 obj << +/D [3651 0 R /XYZ 85.039 553.853 null] +>> endobj +1494 0 obj << +/D [3651 0 R /XYZ 85.039 471.112 null] +>> endobj +3656 0 obj << +/D [3651 0 R /XYZ 85.039 449.916 null] +>> endobj +1498 0 obj << +/D [3651 0 R /XYZ 85.039 380.724 null] +>> endobj +3658 0 obj << +/D [3651 0 R /XYZ 85.039 358.863 null] +>> endobj +1502 0 obj << +/D [3651 0 R /XYZ 85.039 290.335 null] +>> endobj +3659 0 obj << +/D [3651 0 R /XYZ 85.039 269.139 null] +>> endobj +1506 0 obj << +/D [3651 0 R /XYZ 85.039 158.125 null] +>> endobj +3660 0 obj << +/D [3651 0 R /XYZ 85.039 127.924 null] +>> endobj +3650 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F41 2104 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3664 0 obj << +/Length 2875 +/Filter /FlateDecode +>> +stream +xڽYo8_adf)Q!Mnv&}P,"[^Ino(Iq{Cə|H  Jd0}ex0] F¡ґš7`kd0#I;jrv=cmЁ"קCVv0#e4jKKM Q⭛#n{n/*2hu- )v+spbhP6-7hxΉۗg@TZO@y ƛFn@4b[|L iH ȏVzBTkZ3aNqN#mp`yؿ#:G,xݏ5PQu.a$ `W d?#bA5Yr(/djhȱSp>d 싢}9-TK9ٺ1P,4/˔ y*eWLYѴض-: c#U 1g56 B4hy׍8Nfu +gMӲD#&nP3Jc<sp plLU-+a h˼ +3j5|Ot08c©RJPĿActi*cxh0@=/r\Udԝ,B0.wo +^|[Ԗ+O%G0pl 2mQa KHv%&qmg& RV7KV&4VT^.DNmh 8c5ׁ-Le(Rzyڸ5W ̅ |7ITA + +urǫSGAƆ%> endobj +3673 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [148.895 332.993 206.706 345.895] +/Subtype/Link/A<> +>> endobj +3665 0 obj << +/D [3663 0 R /XYZ 85.039 781.388 null] +>> endobj +3666 0 obj << +/D [3663 0 R /XYZ 85.039 761.463 null] +>> endobj +3667 0 obj << +/D [3663 0 R /XYZ 85.039 743.9 null] +>> endobj +3668 0 obj << +/D [3663 0 R /XYZ 85.039 721.384 null] +>> endobj +3669 0 obj << +/D [3663 0 R /XYZ 85.039 698.868 null] +>> endobj +3670 0 obj << +/D [3663 0 R /XYZ 85.039 675.747 null] +>> endobj +1510 0 obj << +/D [3663 0 R /XYZ 85.039 579.025 null] +>> endobj +3671 0 obj << +/D [3663 0 R /XYZ 85.039 555.707 null] +>> endobj +1514 0 obj << +/D [3663 0 R /XYZ 85.039 498.823 null] +>> endobj +3672 0 obj << +/D [3663 0 R /XYZ 85.039 472.209 null] +>> endobj +3662 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R /F41 2104 0 R /F73 2564 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3676 0 obj << +/Length 762 +/Filter /FlateDecode +>> +stream +xڥUMo0 WhKilk P:NjVY?Ҳ4u;`EHJ|$iN8IeҐ8T& +%X.=y0QNSB 5̐tѺ;j=җa',Ց?;j >\̜d> endobj +3679 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [165.346 582.508 348.339 594.198] +/Subtype/Link/A<> +>> endobj +3677 0 obj << +/D [3675 0 R /XYZ 85.039 781.388 null] +>> endobj +1518 0 obj << +/D [3675 0 R /XYZ 85.039 634.486 null] +>> endobj +3678 0 obj << +/D [3675 0 R /XYZ 85.039 612.724 null] +>> endobj +3674 0 obj << +/Font << /F62 1689 0 R /F70 2201 0 R /F18 2207 0 R /F20 1617 0 R /F15 1628 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3682 0 obj << +/Length 2515 +/Filter /FlateDecode +>> +stream +xڥَ6X-: Ed<ЖlkGG|E>:ZEX,]_ltV F)7 +C,*\/L$j +B7[j:]s^>-+'Ί?C7TSl_ֿ>(&zuٔKitڔm[wZ~Zw)Y lz)`C"pe:)G79"+wd= εMbCOsێZsKxڹ펿GEYV>*=m):n  Ҟ+4l=svAXCua C/2xV0P8[fKS>p n"$eউMrɇv|e<*^ ˂<}ah{oSC abV6 gX(yYB{1S%9J;w9cm(];{xT1b`Syd$?j{ٿC15Ԍ{ +IJ0 + 9^ >pp,VRI͓o”0 kdVMCF+\}$6 2 n"|8qMD.M Ƿ_Ei'UY8~-'et<*MaHT"hGirOJ,yPNc*B^BQBZE +o ,S:qM<\[`h127!ӆ"Od[6c ➆p\2 b$C> endobj +3683 0 obj << +/D [3681 0 R /XYZ 85.039 781.388 null] +>> endobj +1522 0 obj << +/D [3681 0 R /XYZ 85.039 761.463 null] +>> endobj +3684 0 obj << +/D [3681 0 R /XYZ 85.039 646.155 null] +>> endobj +1526 0 obj << +/D [3681 0 R /XYZ 85.039 532.75 null] +>> endobj +3685 0 obj << +/D [3681 0 R /XYZ 85.039 506.136 null] +>> endobj +1530 0 obj << +/D [3681 0 R /XYZ 85.039 261.65 null] +>> endobj +3686 0 obj << +/D [3681 0 R /XYZ 85.039 242.982 null] +>> endobj +3680 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F70 2201 0 R /F18 2207 0 R /F35 1632 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3689 0 obj << +/Length 2402 +/Filter /FlateDecode +>> +stream +xYo6_a'*E=8i7dӋ bH#D]Ic &e"Crf8!#&.I8L&Q,Ǔl}NV0w0O7d$Eٯ-L(TXS!5ZZ|8>rͮfL=gﯠs12.sܼG◓@zwP|NrבIN{^uihJ +nXe{5kQe64KMDK ׵, k*{(~x!ikt=.-ẹY+սjThnadnгn洽+cCZ}UeZV*4zM@}=bOb4;tHNl;ۙB=-5G!t`Kmf f{ %8: 1ϑ^yJXN=/Z3B`+EgiWL)7$=bOpDwDhQPN5cHtBZAs!bV'&VVGSק +$ʪZ, %"@F22mL UmЗNjyq_-W:vky*HPmxW@#BTw0W4#BX TRJ$.%ux"B60P@E%WZK;Ƃs vxȮ.{nێYDbzvXBv>E&vB)N[3\gqe8IOV!7ք<%qLޱnٶe&H^ǫu-n'L{FCL(z WGJCgGzqshS`FM1H/Lfgd?T^xŒi{[q( Zܩma-pm qmA ~()krkÁYl +J#.r38$G8>[MfnFcxֵ̦a-(LMI^ُb옶#>岉@V#eT#7q^ie<26(CINfJztd3K7ʖ@R1t&#6I%1הxЋ,p"p}u#Ț/Q^?Os\B7^ 線iZω¨ ɶ0 +A eܤ+M&CJ }'g1%K7PAQt))Hy~2#X툍dDHZ7 = sgi +3/QHш|F$gbFPt0F9zf<|U$uG`",q2XlxkZc ILr_Huty._yGyOoYHT5z!]&l40biaʚ2bJlvyHn3ǙB 7HE^{`a}._lb[~ + z@{.14#| +`L8  -{2f"6\W~)0tڮ{m6tzK;;ť̅JFbj3 /ޟ(9O4ENoh+v[vN< nz Kһ隺TbsNёRP3EfM8(F3_9pqև)x-.5ra3G)vtCK> + H=ݯRݶ/o‘f)!g^[)nMAJ! T:z:3]Óc+BGE8/Ft آ}em]ڗu݇΢F{ jUx) +S:wY?9.4tK56u~<ˑuVv47Fv1W#BPzND~=@^8Qtdendstream +endobj +3688 0 obj << +/Type /Page +/Contents 3689 0 R +/Resources 3687 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3661 0 R +>> endobj +3690 0 obj << +/D [3688 0 R /XYZ 85.039 781.388 null] +>> endobj +1534 0 obj << +/D [3688 0 R /XYZ 85.039 328.501 null] +>> endobj +3691 0 obj << +/D [3688 0 R /XYZ 85.039 307.304 null] +>> endobj +3687 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R /F20 1617 0 R /F41 2104 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3694 0 obj << +/Length 2890 +/Filter /FlateDecode +>> +stream +xZIsFWp|ʄЍ-+RqMerID 5)R:~-yF&t=?F1ey0B +o^O)Md4%/ջxx4VΗRʙyz>~x=/}йOs{s{ عn`VNޏ|q=Q? .~?_xڞdT^/ſSx.&MO 4<טpkR'}S_2-.\|{ҖIO\e0>dȑ0I 4㉎=]ڑqܒbw\8"vҖw,pw7ve&x_W%TM*ԋDȒHD9Qni(bڔmCT$tbBͨMg #Ice$h%n*]@r:50$ jv\s Cϙ#;(v>}'l&!}ǑwDu)OcxHh)4TCzJItjdy8Jk YCS#SQ%KtCZZM͚xZq Y\>P$=:juW[j3WQ*SZOu9;"[U :mxNI):;44ТLH9xX`p "{ ^6lJj'Kdf8e>\UEa^%^aՑVdEq:7?(DX0+o|d-^n4UI7mU9l*l@pxa:Y^Dp2='esZ)Js[{lk)lvlP/ + Ujtz#[6_О ۜ #0N^J s-/Rd +)ؽUs1`cvUfSVZ4;麣ZњE)Vy'$A׊g  z9ŞWhiLBa^w7t/l_t;ɛQkUFhA Xgi15@{'NˢB]"o1{bt"'구{os0jhm +B>&Fi"zsW'Dm &nDshp.?=' &ѵCbBVMF f{m.oJ5zSI#U~j=>C90q>`GygXg+^ P 9V}= ]ed}2e]H5ƌB\%]Y 6]g@&d_f"'o[﷌羉٘ACn,O`[/dShagH@dYÂC2YМs|!E9=tܦ b7DL[—67t(N3OM{봁<E#OY Ö9ҖND\WUt0oƨaa]i !9Ш/ۖ^l7UTL’~|-tYZҙȾ"[-;?QJS Fd}r%QRHQ_ŀp1%v.c(K9jT1i2A6?`v@Y)!RC֖pIbLV!oa,}$y~"3*uQUXXu92u)#yO{Q%Oz>.E)!3Rѐo(X͔_) Ky?k?s6g^i 4endstream +endobj +3693 0 obj << +/Type /Page +/Contents 3694 0 R +/Resources 3692 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3661 0 R +/Annots [ 3697 0 R ] +>> endobj +3697 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[0 1 1] +/Rect [386.344 563.626 509.276 576.528] +/Subtype/Link/A<> +>> endobj +3695 0 obj << +/D [3693 0 R /XYZ 85.039 781.388 null] +>> endobj +1538 0 obj << +/D [3693 0 R /XYZ 85.039 681.066 null] +>> endobj +3696 0 obj << +/D [3693 0 R /XYZ 85.039 659.87 null] +>> endobj +1542 0 obj << +/D [3693 0 R /XYZ 85.039 390.685 null] +>> endobj +3698 0 obj << +/D [3693 0 R /XYZ 85.039 372.017 null] +>> endobj +3692 0 obj << +/Font << /F62 1689 0 R /F35 1632 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F70 2201 0 R /F18 2207 0 R /F71 2204 0 R /F41 2104 0 R /F65 2099 0 R >> +/XObject << /Im1 2193 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3701 0 obj << +/Length 3154 +/Filter /FlateDecode +>> +stream +xڽZIsFWVYt7ֹɉ=q*3j|HrD$8hm LT%^5n#SyFr<]nnFɈ64׏7{[ET>>Ӑ~|8\eY<,Ti + qnq>ÁX#4~?~i7o'85{t[ BS(G*M0ۛY/ftgGܩ",t27Fg %>-T BdDú\xN 6,c] kмn/*#ꮃEuEK?J+?iz+'k14e_r {v0:j s\ln[΃ {ڏ7ڷwY4giC["ڋBMttY:őƿ +AA^<j XnA +`ELj]eq&/=PF< +<$J:Jrrm *Vrh "ˑvQɱE+p|1GMo$lz htֹQGPȰ@@s@Tͩ" CECVZH_X=gl$G +u~|l< MD 18$x)hH[>Ymjftm0gVA]6Iׁ\ϛi2 r4 A@ dB!mjveXz;4t2HĂmΘ&:!xƍKRLʮ@eԈ-1A %9T.җl6ZQF_ W*um3spI ѓu.,EATgLV~Q~!b?G/kC≮)[gޓqGVM"+U5ժ@UnǺ, :(.ăX#<GPHNyxes4s],;l%"aK3nWӝC4v< ^SXL%JA]5 &m!*e!" 7/r +^Q16&4U6]so]}$5* (bN4Ƽ_'3V(C5g$(r'I\?v{ s2=Y i(L]S8!>"o&r@Y .Wk[D\&gVԆ2-aclG𵙜ZɃ+dtʝEܬsh>v؄{+.7۝A\ &~AU,#cwF[ʧֿ<BjC #d_0B Џ"F!P\S3xhfYo6 +)m#H]Vs:\ BH6 G%܂"Bad]ĽA>V$gG +~}Kanl6anNL +0*08۩5vHQX)[J 'mhk.-, g\vez#7yí}vUHLˋ\dr#{cIi%)o$jJ +ە0K7(Y0!\ 9֭^JƜd',3l1M =v(;wM!r3TƵ +{K!`bHtB,ˈca1ԉ1xv1&vH(H{sB <عV4K*B[3:|uI6uӽ,"*ZQ"q KN1K789mHD{+ʒ}xR~eqG26fǬ^);lxK V8 AGg݊ z$j  6߱!F:O'6-I-=k.L>^h\ +.IfSwe?2 +Q QP u }^ GDTY%MT4?c9-:" EFr'?.Ae DbWGl 11¿tJe)g@XޒI#_AtC{Ozghb)XvMt{ZAUeLG;LBN;{<\yδ4y,6 1۔T;GNH}&X*ذYaBg + TFLa{<贼65۪ x `?/@iΙmv,EʔCk+`EB_jo_<5J~X\\–6}_q8 M" r- I…@J+:(c)] mNng]csVhi O< ` +. 6o$XğP[QnYkB(D zQ'y) +yU^[h 94يLg[P|b S#)l[GI:$54+Dm +]/!&i9cGQOR,QcQ3UG"l#-~h)}>A27M6I1pgWuL؇\wui)}hz\&W]R: @ٷQdKQoN4`edlJ+ _K5u}ٔ%V v+!37NTK;FV?whݝ\lJA Űd?lGyj> endobj +3702 0 obj << +/D [3700 0 R /XYZ 85.039 781.388 null] +>> endobj +1546 0 obj << +/D [3700 0 R /XYZ 85.039 761.463 null] +>> endobj +3703 0 obj << +/D [3700 0 R /XYZ 85.039 741.134 null] +>> endobj +1550 0 obj << +/D [3700 0 R /XYZ 85.039 644.777 null] +>> endobj +3704 0 obj << +/D [3700 0 R /XYZ 85.039 623.581 null] +>> endobj +1554 0 obj << +/D [3700 0 R /XYZ 85.039 515.796 null] +>> endobj +3705 0 obj << +/D [3700 0 R /XYZ 85.039 494.803 null] +>> endobj +1558 0 obj << +/D [3700 0 R /XYZ 85.039 314.22 null] +>> endobj +3706 0 obj << +/D [3700 0 R /XYZ 85.039 293.629 null] +>> endobj +1562 0 obj << +/D [3700 0 R /XYZ 85.039 156.625 null] +>> endobj +3707 0 obj << +/D [3700 0 R /XYZ 85.039 135.428 null] +>> endobj +3699 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F65 2099 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3711 0 obj << +/Length 957 +/Filter /FlateDecode +>> +stream +xڥVKo8WHˇ^<:iMI9b U$WVjwCJlQ,|Y\h㧙:,yy?"t{K0~h] _~B54} :RUi9%bKkus"sگ߀p^^cg.CѻÈGF߼/¯ ÏdKc'/5#ֻ- #Q)W`/63 +l4OPr |0˷5$S%+CQ*\ln _'ߠ`Aģ[L*p2 p`( : +͞ւw][<¾'[ DpKQd0EȇɌ $c30Dm=6}$Mrlq-TIV1+טamߓjEqn2Z-뇯Pg[aO9[YHEK.O8ڀ5?Q)'Z@LBYtyԓFV8:hOY sgAGE{rbq90)K{G:;RȣfcUJƙܕHQl ptNeݤ,^mig9T'ٞ`;>`5ٶnӷZi'򶹘^=[mlυy ݱ3z+bAXkPHl\L/y6y w'!ce(Bޡwb\K=9geɃ $#bq*y|"7+]<94Ǧ/*ɂk),j"B<~5]'5*lqYUdl߬{j5*;d 1po~cx"-)ٜ~ lX 6endstream +endobj +3710 0 obj << +/Type /Page +/Contents 3711 0 R +/Resources 3709 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3708 0 R +>> endobj +3712 0 obj << +/D [3710 0 R /XYZ 85.039 781.388 null] +>> endobj +1566 0 obj << +/D [3710 0 R /XYZ 85.039 761.463 null] +>> endobj +3713 0 obj << +/D [3710 0 R /XYZ 85.039 741.134 null] +>> endobj +3709 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3716 0 obj << +/Length 2860 +/Filter /FlateDecode +>> +stream +xڭZK#X03xrK%'Z)YV.ۇ!Ȃ ׿>|n)U-ӏRSi&OR4_n5|S2#!/ >чXA\_'A~Ќwtp?|E3CޓΔ'>+U33␭ݾfq>2N@]d-970|7a|·B{lwveי~f7(6ù +@`2 EefR=Ⱦt +wvf+7zXHV} {5]KeDM) 7%pUn;u +(m<n-`?gk* A(N6J z&6ku"yj$j\=/:_MP%p#'Ѩfd޶!H^稐,^,<|WvQZmQVb5*tH5VE+VH;H|[]vvgغA3K4`l9h՟a;AlҎbqkL7j5tˆ=T#=Fϔ]۲dJliDQkRα8g77Yqt< >cU{=\FT<(ab  B-cA&I-墜y͖U \ٲO#sN֎n t9 ~l* AP  }=0O#0L GݿQh%X##0Yɤ:Ʋ!g@[$tj,sA_e~?upb?@&P1/=#<ߠ_c8|`9_v嶬,Ty|Wx;%@yw;! waB)Y =;$hB+fxV=L!q G/ܹ`(vtny1/ic#sd߃߾ U\5BЂ]kȧfG8=yS# );Y3BL, [I!9zlxA89/Q8'XMe 'lQ~cP4Y)YiNbsQuDDo}  붨sVDsE#ΐWk^0rq4yq.@g/LI1\҅TY$C_MǛ~bv$ޚD%h@Xqj N;a#/-(<7ZH ` &\%G¤7618b-x%KA.~6 NGyr!3uDd@ד|7C F,? +60ݯ9ğdځ Vo EE {H?•,5/U* +NB-h;6`BSct5P/''(| (D‰zvh?sƈ'B_TYM+rDx.pFkvr uOSf>S}.O>^3$EO"fE` N|,Y؀|(疈 P<UVGV2dPp(:sH60}*:ѲXccsZ.R(NӸ=THKtkYɰ{DSO_ +X e޶B?O0i|jR3\N M!WC8av5!yV@=a8xӦRƼ_G$lY bMB,襒|U^{ge5v<+vo{wx':7(tZzRĚAYA:]'3ʞ7VT\y6M5'Y4L]rrn'E]Mgo/{L$B7Nޙq #:'#M? d;Ľ=3O8 tLYln(j-$e֊~'r@A֩{*򻉺ڨC :O?endstream +endobj +3715 0 obj << +/Type /Page +/Contents 3716 0 R +/Resources 3714 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3708 0 R +>> endobj +3717 0 obj << +/D [3715 0 R /XYZ 85.039 781.388 null] +>> endobj +1570 0 obj << +/D [3715 0 R /XYZ 85.039 761.463 null] +>> endobj +3718 0 obj << +/D [3715 0 R /XYZ 85.039 667.044 null] +>> endobj +1574 0 obj << +/D [3715 0 R /XYZ 85.039 667.044 null] +>> endobj +3719 0 obj << +/D [3715 0 R /XYZ 85.039 639.536 null] +>> endobj +1578 0 obj << +/D [3715 0 R /XYZ 85.039 406.978 null] +>> endobj +3720 0 obj << +/D [3715 0 R /XYZ 85.039 377.574 null] +>> endobj +1582 0 obj << +/D [3715 0 R /XYZ 85.039 172.114 null] +>> endobj +3721 0 obj << +/D [3715 0 R /XYZ 85.039 145.5 null] +>> endobj +3714 0 obj << +/Font << /F20 1617 0 R /F15 1628 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3724 0 obj << +/Length 2979 +/Filter /FlateDecode +>> +stream +xZK-K 08 DvJl$D ӯ${VyƋ5aEfPYXoFzˌh(58wi0M|?߽\)e*lp޼n oo?[&6 +x{}[]~ۻ +T!{?D Qb +V^czfұ \pZ;~J,h/Vvu7x|6Gx~pesw% 'dbpG,q"r@FȜ5.X3%aѕroK|x=#DQ6LȟC?9|Bg! ]gblżx,!|=Cl[Waxqdk@_+>͈(C2q$p4_kw"}n}5Z.-'7f.nU' HlFQ<р)s:ILI _>D + +^HP +cqX 2hhi^x3D;#RIL|7ؓS6aT8 FhC`Tt%߶r;G:o)0exip+yvN!1T]c(U ¯d}1Jյ<RVB?Go1WKgI"84 =_GiFNJ8sӑ"A#m +⫹ P=mr'= 2?5Ss7.Xڔ<'s>#JE)!Ne=Bqp#nQQXlf7Ĩ0Iq ABXs-|iyj){ pΧ5Ke9ϝ ?Suqp''do{>i'+-a& |T7ce13G +)쪳\zEyBrG{W1ϐ] @Sj 3y0S1̏e̥+ +a+sIԡLLĜmg9Ggă<θ)L֣ ao.(d{.sW<\jȝ#Sj{y22^ +,cڏ}cSQA`򘄨`&vx\}zR3kCw190ͳ3P+EfsvJ[)Z+WD,⾞r=$$MATcO\# hi(ATyc҃ ^~5*PD zW::"#u$@I/N<<Nl+˥NiGpW/ZTi({݁.G8M=׃w:O]%10f=чe9_E%\o)Yo2hC\[y +((;=_76^˓1H*pzg! !R\uwgt&L辀ήNMT쿓M~ޠ|@)qxg2CQr6CxVW^in +؞9=" 2I@D`w6MKlL&c-12_]O]5{X+xWh+zskgEXO/9Pcm'^AlX8[`9fXyz;BO+1V.A?|~w2- mⷶ|p^"= >jO/SpgOOЮϒ~?Ns-ЀW3% +4RK*> endobj +3725 0 obj << +/D [3723 0 R /XYZ 85.039 781.388 null] +>> endobj +1586 0 obj << +/D [3723 0 R /XYZ 85.039 664.197 null] +>> endobj +3726 0 obj << +/D [3723 0 R /XYZ 85.039 637.583 null] +>> endobj +1590 0 obj << +/D [3723 0 R /XYZ 85.039 483.53 null] +>> endobj +3727 0 obj << +/D [3723 0 R /XYZ 85.039 454.126 null] +>> endobj +1594 0 obj << +/D [3723 0 R /XYZ 85.039 397.708 null] +>> endobj +3728 0 obj << +/D [3723 0 R /XYZ 85.039 371.093 null] +>> endobj +1598 0 obj << +/D [3723 0 R /XYZ 85.039 257.688 null] +>> endobj +3729 0 obj << +/D [3723 0 R /XYZ 85.039 231.074 null] +>> endobj +1602 0 obj << +/D [3723 0 R /XYZ 85.039 144.767 null] +>> endobj +3730 0 obj << +/D [3723 0 R /XYZ 85.039 115.363 null] +>> endobj +3722 0 obj << +/Font << /F62 1689 0 R /F15 1628 0 R /F20 1617 0 R /F56 1642 0 R /F35 1632 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3733 0 obj << +/Length 615 +/Filter /FlateDecode +>> +stream +xڥTMS0W(Ӳ Phb8NةcJ~w%'rd&^]I?A2ørf,#:d e$N4A<\w$_x|@G_n$NRT'ft zv}~ۚj3d im0m;tt=(+*cp{قtS}6ϫm-zMJa菉V7Nˬ~nI1dҦ1+Bm7Յh?ۣay8>ߛ4 4͘ s6=%2g(:b +u>endstream +endobj +3732 0 obj << +/Type /Page +/Contents 3733 0 R +/Resources 3731 0 R +/MediaBox [0 0 595.276 841.89] +/Parent 3708 0 R +/Annots [ 3736 0 R ] +>> endobj +3736 0 obj << +/Type /Annot +/Border[0 0 0]/H/I/C[1 0 0] +/Rect [229.043 698.057 352.339 707.625] +/Subtype /Link +/A << /S /GoTo /D (Other-Clients) >> +>> endobj +3734 0 obj << +/D [3732 0 R /XYZ 85.039 781.388 null] +>> endobj +1606 0 obj << +/D [3732 0 R /XYZ 85.039 761.463 null] +>> endobj +3735 0 obj << +/D [3732 0 R /XYZ 85.039 736.911 null] +>> endobj +3731 0 obj << +/Font << /F62 1689 0 R /F20 1617 0 R /F15 1628 0 R >> +/ProcSet [ /PDF /Text ] +>> endobj +3737 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef] +>> endobj +2908 0 obj << +/Length1 892 +/Length2 2242 +/Length3 532 +/Length 2868 +/Filter /FlateDecode +>> +stream +xRk8#96%|5M`0 -5sΧ1a̘a`"H"J,r( *")dO[}ss_*V>TA#ZDI L2K`ZZS XREK't_6a_DX2D 0%0@^" +XӉdF8*rAFHB@hD&2wГL X2y7^ +IHӨlz@ft,a,*Ռ5M@!S}|YLI ͝)H"|~1 T2G󤂀 +Z RƓA ɂ$zL J4FxjikjkeתLcڰ}AC`ޖ @({w>-Y/&N4MtvrF'#zG~>|@@`[4T@N`h +Iq4rIh7>а΀C{9mAslMsJXfS>S7\ѸSrCDsSnX?I;Hb9i:T˭sy%g!InI.f{mOYH|?W/NtR^bZfڱZr֔wcp? ٍL>M0 {Lҡy FχPbNPΊ$X)?NB}% \-SjϷ"$/7{LJn0w42d>fő eK?6M T3cphYnaQݐu9֫+uC6ͬtCZ ;]vqܶ`EF(/գwZYHF%#znhl"|¥֑֚{?Daۧf)K⏭λuS~n]2@-imNmEȋr㯜_e1*ˋLusՖ&b6#z϶:9uYЧ?ca r˗e[ܪ[2f6nFlPLꦤW14Cu^Nf'!noI]/Û9WќG5sH3I?$?W3;Kf'5'H%߼%v"D^yD}M[h{' + 2ɨ8|Nt`dC~IﱠBce|G(4 Rb_nH4Ŋ^C㩨j΁km{({5pI!Yچ8\qhԡؠo:Vf2oϽt}ayOL Ƃ%gΈɹڰKn΂6q6&5„0FL%@kCpe.NkȤFt~]%2ePkIBZlIB]'!:8ҍS%Mckzʸ?jF1Ed+NV;eV>fbq~>u|98ʭR_$3W$;.2LYWsNV=R'-Cuř;C,;N"¥$&{A mP%kb8cGcM + +#OzÐdQJS pRcJϏ&ƚ0[T+nV~^+MHc:B8\ظH@qI/6 [L8uv=Uɧ\Lr djXd +S'L=?N^A_]5گ +R jHa[Gբl[ǿr3ԧ:wT6 *}%n.uIo„tgm&?߰%`By /,_}-n"2sFP޽jPӶ+\x`t:^wO~Zw̦E+MXPsfquŭt"9d5Qpj͹[%}LXɛ]QB;e4>ZD T`} +endstream +endobj +2909 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3737 0 R +/FirstChar 46 +/LastChar 116 +/Widths 3738 0 R +/BaseFont /SDMURR+CMITT10 +/FontDescriptor 2907 0 R +>> endobj +2907 0 obj << +/Ascent 611 +/CapHeight 611 +/Descent -222 +/FontName /SDMURR+CMITT10 +/ItalicAngle -14 +/StemV 69 +/XHeight 431 +/FontBBox [11 -233 669 696] +/Flags 4 +/CharSet (/period/slash/a/c/d/e/m/p/t) +/FontFile 2908 0 R +>> endobj +3738 0 obj +[525 525 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 525 0 525 525 525 0 0 0 0 0 0 0 525 0 0 525 0 0 0 525 ] +endobj +3739 0 obj << +/Type /Encoding +/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 160/space/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef] +>> endobj +2563 0 obj << +/Length1 779 +/Length2 1014 +/Length3 532 +/Length 1584 +/Filter /FlateDecode +>> +stream +xiTWǡJԸXPBx VC% Lf`2h&J\GEPDA\pQčh*ǥ.EZX Oc3{c[{ D,&pʞs"<.9pL6[DB n'o2s?+ DDDq T tx`XܷC C%$CāR Qce ďTPr&2&'Aߠw2H}B Q/ HL 08@I`_$*<'@Uz*4$!|B׏ \0LbdBԉp?cާvDU Ḳqٴ@P\.@B5Ct RyPE#spڙt #Hf߹h.ND$ʸ˿$T|:wMJ>^ +\Yi2IBFScJ +Jٚg֖f,(}S^P^paxփء$[we,G0{͊V ӂnxZbRZnNҕj~̝7gEmKnں/+!&tA.lɺ5';Z/f'wZdk['2 {AOxWM*K*a{4m\t3hpVoaʅs*cϹhq ?SnNꄤ9>q)#U +Nnv w*@ +ړ22;!ZnUB4bu޸iڹM~ ?sȿ~LWݏ3k_:ir,IqJFďk4.,ؔUbHȄYlZ^.;ab٦O!*]nQ|WqxvQٕh7 ;zנ51AuYG›䪭^ =s{c z`> endobj +2562 0 obj << +/Ascent 750 +/CapHeight 686 +/Descent -194 +/FontName /PRGWCT+CMBSY10 +/ItalicAngle -14 +/StemV 85 +/XHeight 444 +/FontBBox [-27 -940 1332 825] +/Flags 4 +/CharSet (/backslash) +/FontFile 2563 0 R +>> endobj +3740 0 obj +[575 ] +endobj +3741 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/omega/epsilon/theta1/pi1/rho1/sigma1/phi1/arrowlefttophalf/arrowleftbothalf/arrowrighttophalf/arrowrightbothalf/arrowhookleft/arrowhookright/triangleright/triangleleft/zerooldstyle/oneoldstyle/twooldstyle/threeoldstyle/fouroldstyle/fiveoldstyle/sixoldstyle/sevenoldstyle/eightoldstyle/nineoldstyle/period/comma/less/slash/greater/star/partialdiff/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/flat/natural/sharp/slurbelow/slurabove/lscript/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/dotlessi/dotlessj/weierstrass/vector/tie/psi 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/alpha/beta/gamma/delta/epsilon1/zeta/eta/theta/iota/kappa/lambda/mu/nu/xi/pi/rho/sigma/tau/upsilon/phi/chi/psi/tie 197/.notdef] +>> endobj +2434 0 obj << +/Length1 794 +/Length2 1135 +/Length3 532 +/Length 1714 +/Filter /FlateDecode +>> +stream +xRkTT# PALyĒa P^:qP0\ws *B0 +!Y (P4 +F +( bzʪlu?wgwD3`?&㰐@04@Ht! + `;ш?&d8S5"w+qD$DAHd P H~ 9a<h&@pRS4Jq9i +8lؤ$ b +}/FvI/ [*$BfT RD/ &)(xӝ&yO0! "_4Ig+#r.!BX(jK.7UYZ1:3ekQO<~63Ҽ2 +-×wZ3˽R~DT釻|?ؑuŸ&wF!}:˱mF=.AG2)dpn%.9) +a?̧ΝӺg_4 F}uOl|pL:U. -&ߎ=z|s|Hy10ʛC"oL}b=c>㡌K]F;&?7iz;Gx-ư0okImLGzRطv4kbgm!k%љjc,jslJx3Z';y+tK6i8;J3D%Zt1is:񄪫,mnٴ,ky@ +j԰k/|LmW737ե[z`)˧H j-=lb򛩏k#\?+o9Sj?_8^dL^fKÝG3uʾ+vU'K W0:@sMqBaϟZ+ nzo.4|sA=]Y7<u`||xT*|My&ƲKV%;-Oܦn=ŃI˜"u=ɫ狘z2 jmlCQ~no9Q{t'.qg7a';`fQszى^N3#FY,Ɖ:eJ2xѠ4+>ou\ o1Ja' +$'0Oendstream +endobj +2435 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3741 0 R +/FirstChar 60 +/LastChar 62 +/Widths 3742 0 R +/BaseFont /APYTPI+CMMIB10 +/FontDescriptor 2433 0 R +>> endobj +2433 0 obj << +/Ascent 694 +/CapHeight 686 +/Descent -194 +/FontName /APYTPI+CMMIB10 +/ItalicAngle -14 +/StemV 113 +/XHeight 444 +/FontBBox [-15 -250 1216 750] +/Flags 4 +/CharSet (/less/greater) +/FontFile 2434 0 R +>> endobj +3742 0 obj +[894 0 894 ] +endobj +3743 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +2206 0 obj << +/Length1 2135 +/Length2 10250 +/Length3 532 +/Length 11406 +/Filter /FlateDecode +>> +stream +xUXQ hn]ơqwwwww$XpA33ߐܽgoWުSާȔELF I#++@LAMĂLE%:YmŁN >+//+@ Ycgc@,̝b8qDl@@[da -@NLkk' G Ȅ `ba0Y"3Q$ck +pll?K. G(-D;D `2EfVCr Jo֊@?Qmhca/69@&6*05Xipp([8L֎A&-RH`VQբ׉cQhan/ #  +_zLlba i N. q.mip7ãHgyO7xXƝâxg&Ӻy>L׋J`'jem*Z5[ӄ[Ɛ}ej:u3DbY:q;^yk҄{*,x@; Vɥۈi3M{eVTQcq671iOФZީ(<)MplGsHf'p݉Ywm9&gwSygB~DA:%b'5qz F%09D,V#L܂tS0U療+Ög̜(m^X ^l]H9ihi?'U5$bK;XN5D8ߵXX9@{>\7 +"=M@ 5m +:CK~&GԦL6z,u1"8;~J~ɠbYrX=*kh Rf7nYv-t#1)#w>'4[\I*xbC Cȃppr@]u5爞8fŭ&F/lm~֧@ލ Q"D\@K l(]Ja9*!t֚< ^U=)j;jQQ80qpWRb?FZ,قQ("@T4|OPv>D6!_tq?񴸸_KݢXpG^ Ș*U7ċ覈%jU(4V.%ߤtHmh l1F\Y^߫<6M0t-^FbM. +4KLG/4 [y~hKMArFRfe\n凚~rzo1.Q@g\o5~f/W9:'<}?l*Bj q:]S$­y?=$4N-B>Fiəa.t/=]2x )H h &IreZWVGAKc*IW=א{O#`KieJf=ar)>lp7VH0kSJoAm;;f-g<NbX6s} `Wh9$syJ 0|LrMt44ƌ\ܯ`]C Ůgo^'y/f߫1O 00cKQZmE$yr%8hwR pk2l6#UPU.nV\6 >#r:aJ~„m.Umd7=qxhx"Wv֨lJա0sB~IP@NoϿMq*--V0a(ʑA~ 5'V"ͨ*UИ\37̖܎0;m6;yI]ZN:w d>ZQIzBd1Ɵ|I D-QlKVb$ 8g . ש֍HN9.ٖ z9gǾZx$|N|_8ne h`09b: E3Q2U,˭Ff ڌ)T51q)k%xyЯLq8`WJN4n 'YT1Z,sMVeE#L0 awv*ժzT[r KtF$XLl*IH[AuPىj>˵SRTJ\˚<ϚCM*iܐ'uOJoo]oߟV*z7֢ݮ_ vDQ.Vl۲riiT2y)B˵?yq^~:-ir5}_?8^1ir8MG(N&tytExf=ެ,GS̺HQGj1!Z1j0Q `Jw-A5y62 o],Hh޴ Lraf”x= R243o6w&-m]AI /h鿂lbr?/_fV bh WP[B/v;OW,cǺlt$xuoX9E3JJ|j<}pL2'ZVFe#^]4L()k)@t$l29tdT&+|_};˱5LMPN Yjt%rj"Qy5!=-de)ș .#NN/yP"GA+mcp٨#,#4ѬS<tssb2a㈩#H|kh?BWC3v)YY]E"*Vސa2MOU'G+,,zA([<f*$zK| X؜:Lx\PUⰚCdJZ%O-R [8JA17bR_n;OE<ٴN{^(&>Mޕ]eEs +A'R *CaMP>L5#s%qy+Icc0ף#Vb >ng8d-OW0ĪMpRK5qܩO1i?!Nt w>"#>6HB-nT6urOL/; +{xhu\sגsNֳwɿev|Cn"3:!7QAM/i";j&?,C}`D+vxT>\B$r U Yo6MCIYyyfm6Tr\`G=#;eiE=L|G`$.Ys۬AcC)lQOI[²E3J"u۾jSd}fo\Sz=p!,< >f)eLcAdPͫ31"K"x* nQC!xw[إ6 QioxX:6}rM; Z밸_C +pb5ܭ]5G98ZYH1wU]u2+0zs srOܷ)N.2P"jsr+u}abtIJ:z1I},K1~UCgf}O}Z<+ے_;S6jLɥiղ(.0p? V5ZjvI%$$)i'p-#tv>,5zmB:\?I7oh+Q$x%uXRvqd| [@<3WXT2&w MRp=otec~./㶌t շOQ-^6a|Odȵ?~3S}sゐT%gMB% _3)-K]d."u2ZuMm^jMq ea:b i#,|zJ&b\9B`#FD8=f᙭TtY{ V8AO0ѲvRbWpzrYl51F9*SҦkqF! n`RIi"FDcap_M hukkv! + aO+QWOEp m9kSuAGr7yqNW/D +Q9x|S +UIdXXj˷K p _a>)Qe^ob5ltRkVz#jK6F"/d$ڳ'nBx %)_Q)#;0Ϣ00L&>pObhGV՟9 :R*?wet"8樣֗\|Oݹͮx~1PI؇&#a ߳Б/Yi[9= >$(4u4XoxH}Ú^{q ٽO%e;:1.RMTR1NWVyEKKꇡT).$ Π8J 9oWS%2Mbub1WHD־zڨQ_mˋMVq ဧ^ͻE"k+ 94tꖿ!rGI"tȗr_y `\ZЎWK%@[lxz`?b+,35<5AS94aeg@hVJJ\ct.Œ歸=Uxb;HbԐy:lk֌~pѯs S‹_Oy6{Rv,6u+e_J;]^-|~aUΫ@0Ig7qL)͝ۈz_ʼnz/?+%w37hɽ&|_i,nDʾlp24SXwƄ"AK!|iy>?Qr#9Ƃ߽ )n?JTF_ ;)aT Tn\CN`}vwc[sD  NOM +w |Y_`~猕&qnZo3n- +Nƀ'ʻ6t kqD6]34l;1;Qw4*1 +t%ƤbJP;W@Z5hq=`;:U'0q-o2{2 'KSBC8#D6<"nAE_~G⦆0se:vO1ȥ`U͘rUp?Зzp:du_ۿLߨtLb8B6AFPo3+$GQat.^{ΓlߙN-7&~uƎ9wxyLwwϧr8?'Bځ̙>gTN|srקLYV?lT6(;]9 Qjb\*5) 5y\n\mRV{_͒]}A`m&nc=P/g4iRҏu֏4&]خ̈́EFz{b&KM<@f&{A:e,]|FH%cq5#5v(1gg!҉я7d֓0 4YئA=+Wi9VBrU[Rq*'x)4֝JTrQ'larԸ'LpǺ$Hxci= G`@k iv;l2^q/ ŵw`˭YMwsP%!wW 8hPܖƠ}`ʾ ͚핷Ȁf)9,ݍl`1Lj9ϭR nz;]ܳ5=o RFװvf)⧳ņ=(9q?gIf42-^=h$-(Ějceߋc19=v?n35"~cBݙ0O_VTxvNA0!,l;P˷  + $'UveB-W~>ֺQ)(×>5"=3 "rLF{ʯ!Fp Cc& +E쮫#[~Dlh:w->Q(A=m8Fq:-^3LMjO;dqE㐙Շ>.{'և*}ʠo}YMb[I˷:ceFZyoʼ,?KsGoѰUnjefBż6Ebbx#ZI_QNU…8`Yxы5u͍N5N?O3oM޿*6g'H + PlE)+QooU8iۤc6ݺ9jJ w^W-,k5p`融i1׸w$|p6bx%గ."yCia^AW} jDIxŨQyL2iyJ~Uxܩ mhδao_J k#'@H!a*J)5xpB(HJ y[rS:ht?) s"j3Ef^?Ro9yhVv2vHf:Û Щv87COHW,TFwPrz2ԙ>jx/czϑ[8$^\D;V ;biLRYs}'sk>fT~կ'iwgOIX+ z[MR +aŵ}ffL 1ŶȥY澹pp48ƛ~|/>r[oԳEdY\ao-֫w ULߘCp*{q]I~~pٸ~l3LIZWW|[{oxFf_E?)I;aFaftw${Xڬgc{4"5:X!/2endstream +endobj +2207 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 11 +/LastChar 123 +/Widths 3744 0 R +/BaseFont /SEJIRW+CMSS10 +/FontDescriptor 2205 0 R +>> endobj +2205 0 obj << +/Ascent 694 +/CapHeight 694 +/Descent -194 +/FontName /SEJIRW+CMSS10 +/ItalicAngle 0 +/StemV 78 +/XHeight 444 +/FontBBox [-61 -250 999 759] +/Flags 4 +/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash) +/FontFile 2206 0 R +>> endobj +3744 0 obj +[583 536 536 814 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 319 500 833 500 833 0 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 0 667 667 639 722 597 569 667 708 278 472 694 542 875 708 736 639 0 646 556 681 688 667 944 667 667 0 289 0 289 0 0 0 481 517 444 517 444 306 500 517 239 267 489 239 794 517 500 517 517 342 383 361 517 461 683 461 461 435 500 ] +endobj +2203 0 obj << +/Length1 963 +/Length2 2491 +/Length3 532 +/Length 3136 +/Filter /FlateDecode +>> +stream +xy<{ǹ2PPef0ƚ,C34 cFم.B!kꢐKHR"YµE!3<=>|?Q7!Ў4*Sl1+8 k JJft$Ө8& ZZH`F }HL`"$`x1I?W 25 +p|8  8 L8CB-YQ45L`|KA:k +5p-hTJ0@{u0BڦɔJh,&HliN$Y?f8 +oB:\k̰ 4'D~T6bjchjfm_ht / ALs /xLB`w?BJ0kA1Gn_" kTxR_;oL$s@< oozUlQUY! 1NGp׼X/ڶ(2 k @cnݮ#?S[&Q3㽻GU]d7l.;2 G̜Tlm!䣡^ ޱ46H*<1kK{MzL~[3lf +IEX;AM Zb`e񙺃#gP-+fttj`AC{Y*:A8Eʔ*g%HeDtNm.g_HjS\&YX(qf˥\hz[Ƣ7F,ۉ>}R+ޕ oī\?7uW\uQE]d}͢:DIe. ;S並@O}bT4C}u$qTK8b_in9/c4(3rSYon؛қU +QoCѤgGO4OfIR]`f:e",l*~Q)X>~v7ݯk=Pɗ4Ve ,pRQ*3(Us-4rzAd'sI>G(!P~CܨmնWN;uzOǚ-3Bz9?c}Tm ѿ4,IrmAqt +N{6>lW4`n< +0BHST԰(Tpɣ-"KL t׬dJL` DZl{A Z9hwmp%GY_uKrIu;TMZt i:}-4_"|K5o0}x@G}W{錘eUM Un:qdgƈ;1Ukt$'E´{CҒֆe}:"%1$?]۠|5`pkۑ;n`wTb3 +xOOO(ZThY geERj=cx\h N7hUt5M%GAY"gCb20rһ6e.wH47`ok %qk.S <#IWBޯ 9B.C|(A{/:{x@J& +Hx&msO_޺}VIYY,;a'TqN%͸aARgDR4R}/悖 իX1x[ }3s)fAqhi?U~M&oN{z,sU_5$.qϱD='%CV*hƋN7ӰDårw9ʉW]pхJ ~,F;r*Hk;]zSM\iz0MЫt :Ӥ"nE[yߋήˢ&]붲)8UuW%u)F@r^l<85>& {8:ݡϊOٿ = +!CO5 ]2KhƊS4^^8^$i]xb)qm;W'q3MRwu?8'kiZ<(w[zf&m a)HL96!W'V9^+F?:6aG-<Nyt#gĩ> O) Τ~\0endstream +endobj +2204 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 45 +/LastChar 118 +/Widths 3745 0 R +/BaseFont /KNTBCK+CMSSI10 +/FontDescriptor 2202 0 R +>> endobj +2202 0 obj << +/Ascent 694 +/CapHeight 694 +/Descent -194 +/FontName /KNTBCK+CMSSI10 +/ItalicAngle -12 +/StemV 80 +/XHeight 444 +/FontBBox [-97 -250 1077 759] +/Flags 4 +/CharSet (/hyphen/S/a/c/d/e/h/l/m/n/o/r/s/v) +/FontFile 2203 0 R +>> endobj +3745 0 obj +[333 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 481 0 444 517 444 0 0 517 0 0 0 239 794 517 500 0 0 342 383 0 0 461 ] +endobj +3746 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +2200 0 obj << +/Length1 1380 +/Length2 7269 +/Length3 532 +/Length 8111 +/Filter /FlateDecode +>> +stream +xe\]iFK`a`h鐔nFASBA@wy[?3_::ZD)c +\<8yxDrrr<.nl&&98ȃ<=G#$/(/!V92P0br<P 3@f{rd:=^`[.l-` `bl%/0a +0@X8lv@ B pWtvA[ +q-0Pق.j;u- g3]Ղx8@`4Ho @-59%߫Z ?sjy~3"!8`̓hD|?\l`{ |A? ,\`GTv08_["Aп*n0Dt'2 芨l) +2IMoBTʿTM) 1E7!hC܈x@߄M=߄x߄P7 h 8=v_3Br 7![&yDH@",1e1Yx%# @hk'J"? |9O8GVydgf2T0@q|zP1A Z嗹@L[tlN4JBsߦDb Q?gI>f>ͽ煒"xnYBV4Mf"_sJ=]c޳S:ikHn29EQ1~0 HY})i|MA2'p#5S y޳.U:n渲uO*U"]~Wjч41S _mW^axȖu:’\'+7=PpgE>:H|x@l2!~u s5!ydK[zs=h-N:e49EH5Ј(ټ+'y'Nbtf)%A[tغ/KG23\N%\9Հ0^lSR]LEN +]DIsLWJ]\dI/"i);ݵf NqJҸ%7L̆(z,x +*Or!itVՁ&M_ֆ{^A;.>BozɢmrѠ'ܐ<=r-+p@%ONޘ;ݱ$`+^J\\iT n1[6^xlEJdOmW^! @E`]!1JU$bGPP߲ +~vW܌h+6eQٯ-}ߟlʟMPU2 +{M#%TLZ}T;z|k1DS+t#|b?Ty dK7]-ҽaxrSHҔ2e: +hrqз) ]֖Zkg|cQ\*O,TA+sRA"qe{߉xWt~^Ijmߝzl/ðg (m橹c;׀&aԊDkUF곰1FojfP`;Pmt1މnjV^VxKU+a(J8Z"+&(\y[dSMLÙSSIoўqN|X[6d/0r$/UN"FI0)^ޏ]P):mVqfĎ+#A%[u4H內X 󂈾E 09{JL{&b7nCDWXt}feMsDby⊈ ëK1[HB |BȣAG #dy|}VPu|W *\#QEaIɄX%uk%J56ڜې_(|_ VclYG%fL1^,.݃eWㅨyk{>*\a7 )$5I,@X:z#Wt?&'r>t?u}ts@I5-2y)rbqWqSDء>"7"R/w'8*ǭ?Z5Өs NJJB7Ia[xX;D[*u+ŖjEgQsyQ '[φitSbgL였ZdJQGii%`꟝s|k1!an*a2ZoПn9izV-̴͎sۃ\Bnij_L|ɥZLzD6xpAEv[9}tu=X'xSHYo><)Ԋ 'u3yt7S2,5Z5+t3F͗QMN*9#`"PKb?^z"jS cCFa)a#WQ9#sqY%DZt,;rȾg/7W? Ik!?nX}3BZ|;B~Z}AyȡuCܹEL%Ų(F2^ $ t*19(s  ++5t[(?m';&*8vss~tA ̿a?zXy9\ך\VF劽G~7Qa^(^Tڶ*G57`RO8ϟ@P3="fS,\eE`݅+|Q]Y)%Yw]ɕ22#">A^iIE Rǫ&E7r[r_& l+* %ih3'5 r >K0iKfNQsy |ɖIqѻ Axnke#7a_{H *"H&3C MX.cY2]D9\E(WHbV#5Þ f5Y@̾far>$1VI(aWpz_R'F$f#/-oP66ƈy%9w[Oa0ь6_}8yl@~%_\9;X}|*0=@̦~5J?ȉK]SƠ88̊+a 1:Υnt>\YoX%S.#Ha=]iWq*^8A[h8طtQQߙRϛ{YtK"?(W;XTR6᯷dX%{/cu Xl+i1YgQ(ĻN%#KSn^VpkxS]gt+k6Pi|b0]4,!{ ;iwKo`ʊ1h +?I n?t=) Luk3n_ t897ޮ!a7ek`Po٨}tR3"1!;W+H +Wp,j` =`P ;endstream +endobj +2201 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3746 0 R +/FirstChar 33 +/LastChar 121 +/Widths 3747 0 R +/BaseFont /PLRCHZ+CMCSC10 +/FontDescriptor 2199 0 R +>> endobj +2199 0 obj << +/Ascent 514 +/CapHeight 683 +/Descent 0 +/FontName /PLRCHZ+CMCSC10 +/ItalicAngle 0 +/StemV 72 +/XHeight 431 +/FontBBox [14 -250 1077 750] +/Flags 4 +/CharSet (/exclam/quoteright/period/A/C/D/E/I/J/M/N/O/P/Q/R/S/T/U/W/bracketleft/bracketright/a/b/c/d/e/g/h/i/l/m/n/o/p/r/s/t/u/v/w/y) +/FontFile 2200 0 R +>> endobj +3747 0 obj +[319 0 0 0 0 0 319 0 0 0 0 0 0 319 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 814 0 786 829 742 0 0 0 406 567 0 0 989 814 844 742 844 800 611 786 814 0 1106 0 0 0 319 0 319 0 0 0 613 580 591 624 558 0 641 613 302 0 0 513 747 613 636 558 0 602 458 591 613 613 836 0 613 ] +endobj +2157 0 obj << +/Length1 793 +/Length2 1151 +/Length3 532 +/Length 1728 +/Filter /FlateDecode +>> +stream +xRkTSWRIzX<1H b OyH̽!$A%UY蒧(V@%Va +"" a9R*uu5kswin26b %l[R 3EтqXN "'``>`V 8ހp\t=9IR95d \ d =jnFXgx& 1(l66©JaNjJ 6}*3HQcJ' EBVRk0LjoȚ^\U5姜K^A&]K8bө;qRBY !W# +!ZG2Ĉ"BJ:aoJSVN%#JDa=IpDX M4U`q\CDF\```ub& + J L 0pF$fMb}ZP3н9ᒭX+|31E6iaI|y޾)Tq%}DHaX+([ogUwXXzt[DžK}~N7𦟢O~sr¡d$&SMs{ųl#pb+mio^lIoz{lW?`#3koz47msgk}T~v>8M< Ū1s͕;1Sݱ/˥67K_ay2*`B1cҸp鯳=nHsJb%ѣ W:)jCkpCVMz/f7KMmɮϒ^{Hm}0Y{00kسE-^>! [il=p eL +7\n̡<kWMfDΊt.r })n{]kX\W03,W/iw p^7AhK=N܉E'>z^ Tmj9(vh내݌Q \Kw֝28o~(*?Dmx ξlτ?("PrvچuOU) <>\kLι~oz;\cسѓ+@ Krn 9;wG[vԺ}4Zc+#Ge*A-U:b$O0Kt1A;TuI 3һzJʖJΨ[͸;si90^cn(Ne {<#*odR+yYe *ttmg|uشjF}gqZX58יoaN**uj\Z?;PVf?rV{1e71CG8&ESq索bOcxYTNUƓ{vZk.Oe*^ps^"%*J/ ~G!Kƞ+-,xiQ( _nKV7הέuAÑ{:;ǩˈWoN/wVR1>m]G[5}MN큌> endobj +2156 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /FPBQOM+CMMI10 +/ItalicAngle -14 +/StemV 72 +/XHeight 431 +/FontBBox [-32 -250 1048 750] +/Flags 4 +/CharSet (/less/greater) +/FontFile 2157 0 R +>> endobj +3748 0 obj +[778 0 778 ] +endobj +3749 0 obj << +/Type /Encoding +/Differences [ 0 /minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/arrowright/arrowup/arrowdown/arrowboth/arrownortheast/arrowsoutheast/similarequal/arrowdblleft/arrowdblright/arrowdblup/arrowdbldown/arrowdblboth/arrownorthwest/arrowsouthwest/proportional/prime/infinity/element/owner/triangle/triangleinv/negationslash/mapsto/universal/existential/logicalnot/emptyset/Rfractur/Ifractur/latticetop/perpendicular/aleph/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/union/intersection/unionmulti/logicaland/logicalor/turnstileleft/turnstileright/floorleft/floorright/ceilingleft/ceilingright/braceleft/braceright/angbracketleft/angbracketright/bar/bardbl/arrowbothv/arrowdblbothv/backslash/wreathproduct/radical/coproduct/nabla/integral/unionsq/intersectionsq/subsetsqequal/supersetsqequal/section/dagger/daggerdbl/paragraph/club/diamond/heart/spade/arrowleft 129/.notdef 161/minus/periodcentered/multiply/asteriskmath/divide/diamondmath/plusminus/minusplus/circleplus/circleminus 171/.notdef 173/circlemultiply/circledivide/circledot/circlecopyrt/openbullet/bullet/equivasymptotic/equivalence/reflexsubset/reflexsuperset/lessequal/greaterequal/precedesequal/followsequal/similar/approxequal/propersubset/propersuperset/lessmuch/greatermuch/precedes/follows/arrowleft/spade 197/.notdef] +>> endobj +2103 0 obj << +/Length1 867 +/Length2 1181 +/Length3 532 +/Length 1804 +/Filter /FlateDecode +>> +stream +xUkXg]A"}o 8"$4PdKD:Ld 0*pUARuED +4\*t"^*tv_̟y995~OFGƽcXPoW?hb=0a]X8RzXb%3CKS}e6gygX [WO@S(wrpfW;O lo_H1H6Zz$?J[PO޶ơThj;ۍVܼ"氝ƥu*cNySE]1xsu 53 'e} +U:pK:N [_yT^8 :̾STJ")@pyʼ1:hchRG39=^ # d_)i)h̸83>321ޔфӑo]~>j|I +{m}Uz4M܋.f ,{Wv^ՙ[2dx;6MC#jqSM)b|˕e3a-o1nkvA+RZ}]n1V.-g _gyh0Rn MZ_x165wqLmq"JҠ0#ձ0֋ME9' նBCW ' +A?u=v+̎ *৺1:Ϻ*~=!^G?yd:j6ֆu&izPdýР -,y[ꍐuΖkռ627ST ҄LHUi9ǡ၌u7]/ ijv +sVN?KecGr"j>׵TV,q:m;^㡉wdGBiT̳DžI+־v˾G +\:BZY`s)w!l#ъ+?[UKyhƟSf}m؟fmv^ݓxv8&FKkwӨ.]4m2smи(kii5No+7Ζ mҽs|?TE}R/éKNfmh'r[yrz20~le秧x79C &(ϕendstream +endobj +2104 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3749 0 R +/FirstChar 13 +/LastChar 110 +/Widths 3750 0 R +/BaseFont /NKXQES+CMSY10 +/FontDescriptor 2102 0 R +>> endobj +2102 0 obj << +/Ascent 750 +/CapHeight 683 +/Descent -194 +/FontName /NKXQES+CMSY10 +/ItalicAngle -14 +/StemV 85 +/XHeight 431 +/FontBBox [-29 -960 1116 775] +/Flags 4 +/CharSet (/circlecopyrt/bullet/braceleft/braceright/backslash) +/FontFile 2103 0 R +>> endobj +3750 0 obj +[1000 0 500 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 500 500 0 0 0 0 0 0 500 ] +endobj +3751 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/exclam/quotedblright/numbersign/sterling/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/exclamdown/equal/questiondown/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/quotedblleft/bracketright/circumflex/dotaccent/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/hungarumlaut/tilde/dieresis/suppress 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/suppress/dieresis 197/.notdef] +>> endobj +2098 0 obj << +/Length1 1930 +/Length2 16115 +/Length3 532 +/Length 17214 +/Filter /FlateDecode +>> +stream +xڬcxͶcvl6;mضѱmc۶:qqau5g3n`mn?vN[cmN`llߣNVFlL,t ,;͝L l7)eqa9 8)d&9h1|2g)+;CI67ۧcz:[);M`bϹ~=ɿbFO4,affŬ >SmƆV>p 08l&E'_ɟ~ YOSO `'<[?!vzG+G?z\O[Nf?;d'ϖ ?U~ +ۘOV} +?{?%'Y?$>UЧ< gSZ}'>MHύC^Ч?E}zC^C^ЧTWCS]}Ou?>5Csޟsg1>'_C~a~b~VW1|b~z ?MY"%Co~ ?]<`+ӕ_/t~r ?]u|r ?])6ۖU*(hILifؘvg 30p0q+jy8اWl,RB|D +f(qJ&Ҹ6x7_IUnc6}T8 Bqit 23ԇ`voL}J|V-}Ȟ+lywr{&՘ Z']: z;|.f[`R4~ٷ1g#e1dg1E=SneI>,{I}W\9 0ds6! +W:;rЂnI%F̷q/_'c`LJ퍧UꙞXuM1r3<]i]7N CKA$_+' ҷttdʤz ̱A> ҩLyHT_gKF 袟ɱg<:9xdJrͯu@+PL<Ά41- B{p8?R8m&.RPhfT`R W/!WSi7V^aΜ +<#ȦG7@i'l%U>AӢLK}C̆ 񲫬Q={B )j_PѱacU5 AQW2=mh;qqIGZv xN'I[g0#%tv-eCPo̎FSH7 engL"Yi5+T]Sme_.~)F92^z~Q^-,.O~g*:!>޷ Nе*Nb$J[_GKWVeskB+1:'7<%U ś9XKRAۘH۷js.= ݑ^ q)/o-;8i#7"תrlCy5)GTWz xSX.zA`X.«eQH"k{X/O[r&?(?it`ލ7x|3,f» u2H[aC,|j@W{/0ElΓ2גpuL,l&،\U*O?>n \[\̿K0_/g%Զ`?+?'.Uã>|U˛)gB/6'!*eP2Z}aiRkv +oq9 $ {33kPw_'#Y97/S4)(fYE,L}J>vx=Qєr`Qd PJCгQgGp(~?G|1xc[u4&B,^xY +]шqkl>LJ!iD΅' ɰUl%;]>V 6_Иy&_2'X,)qïI]vy9m?+K*b%ʅSnojBH;uyE^qwcQCrGPͦa߈_h*Z;cU/F-Ge +<ÃjDS;<@ƅUX?v^TzY2f2k?c"}I`0Q|p3I*x^6ᒟX!Gym2Ȕ"}k|-w͏vZdu[7>]C0 @00Rq$Nr*ÕM| $va3nGPP4qG]rZA[sٲ<KfQ:KDf2*_[mֶ7gjv +߹Cr-4ck?Rk=fb)܂i%ov#`.<"fjyEKFB~%97H \iH}!a %-k2W}LSюbocSwbe4Fgu3CeݱAV.uŽ鏄5AZ[ʆ ETý%\FPm1!wLzpGC5*wJG7pt޾u +pҏ(Z1H\9BZTV9>G5ysRy3HX50/%.<XI"@~ P{U{XXG2=F_xgr^Xd\~R΀2ʑ/[r j`񝀄0]y~ SAd$8y שdAj9)7,sORcjtgAMaWG(kgQi7d==GY7L%E][0 <6믣`vՄYNS\Z=D׬ gJ$e4\:ú/D_l-.;sM[(Yd=R1 c,1\*ָ*E•8g}8%+ Z 6ׯgfa5:&;5V溜Be2N˺6ӢL9rƬZсb3E hJښ(o26NR>? +~e}@ oDVم݅6iS$ +֌E0! ">^2Y 䁟;ƥgɾvk7P]wrNձxa&LZE#$4~8~l]J(u)-M&b޶jL:%y희>/0'AApk!WJ[ދ̐\ ?.T r><@RH 77ӪOT\_S^8K ~]ZrZ_`k,D5 +API9u/>ukcQP-d-0`vbRf `0"i?91tکIEOcTҿRL }_x'PCDŽ~3/ոd'~(Emyd.T\-{Ռy iN䦥-?uŐŒ~FK`oIh>6e /">(K_^*kdYsEw*fm&j=YfSRe̊Z}Δ)3Hq8iyK /xNl%i 6 9d0{g_Q["E= ZorMg + |20jمO݆;Zu3b qru-:BE֖F0x&:پh7-@XҪY_ujR, T:8J^&Jsjg76%8cF"ݔB6ke2qhq}8rH"IJI1rK=/~BHmk;I_Oٍ٧y$r*=.D[?Q-*?#FlsU;ߘ~2嗢WNk2=NRe2>[3WxSQ#CC"deƥCrzx7#b^`̢eTa-wg{-<ή)3Suf4'4[ҔNx /( )T@%mw6`\&ӫw4>`X'm(g=JN5ƻ)&1 + v6 UqTm 0:1>$X?JE70W6GlQCѿi:;QBV}Owje!phU3Kw[#LJ{|Zk"QN%BE댨S4 oo*ySG^R\Dsꭄ!HE_wE]+HGVLm&`6~Fx$K'6RFʂ6Cc^,Nogk}O$ S} t*sKFiPPu6Z4\h/= Ra )>Km .aЪ3~ ʹƍk +#+aG]%8՗ԖkJ ؂&6'Ϲ2t&6e1i!,){.KL4pXC_* svt*MBj4;"qi&/Đê*U - =fprCGle $<{)1{]K6<[t=IJM%<%gDPh x ^6HoX07'${h5HmfڃNuw Y½G8"/c Yar'!!Tr{idזL9:60)}F>FSnhF_ wvwсO}sn y/+}iSϫ֌*{@:$rщ~'!+\w-r7n"\#'Сta#RTT/y`oAa5/ J5+n)܆Rj1tw*^:؋W0aW I~qfW3=q|Di-Mi~ĸO ­ChBqfgj)ƞ|<3rHulqrweg-ge䠒O]"1]nى`~_mk!|mπ"Uj}O}G%3:wg +ȸi>ڜ3Љ۱oF 8DZ6-9NJ[DJӐλM̓|a2=$.20XnRo-*I||V1VGL!T?XZZٜmaE@ !*t`’mzoҌDo'~~G ++۫|cKd2+u-a]OQrG(H^ƩK/^L5%ɥwlS-@ŁҽPI6͐RUs]|r\U -i(SޙTo?͎>Duv9luW)1_yXiIZeAPk %Xr!p R Hnb/1,KU|RѾ-A{Z\lW& (.~kJ]ӁIs70Р.Y!` zpy%d.U Dj:TjEmᨼDP27. N!J]\IO4 qZTXс[>C-/4H=92oCd_5B˹h9Ml46&OU5١36gZpfZ}BUN|-rD r[jkUSu#7ԝXOZӬe<OQ聢w$hwq0GIw];Ɲ?|C"Z[ֹGjX&fiڇ>Ƽ U@@;P%@/3PY .uEX[oE&.3Pfft6-[ffWՋ[p;|,z7)+0-Sˢɬs*ޫF@ʜpal-@jQ.~`1K <KHY/z8e NA/h_&“ŭ'(^EV3Cd&0ލz}` 4c|\jolh +8 +9߷w3 07qfGIpO̖zNjЎy#QrƗ7tx"!m5!=$CFam?)ʎ; &]2~3"l_(qM;hl n9 RS1.ZNI5Hh,~H`-Loz¼,%8庉>EMTh$qNtblVعVo'ZCBܶ 5a0;V +.w:\B8e#;WWmj^}u_ [Lwe2Aw^yж92cZNv<:^nweEcP4Fr< DR=mN%H:B>rOkUt|09 0O{Uhg'O{fFҍ']hnFJQh9@"U.8#bQwywir9 *G&rJcN!L YXuceF6RFj o&b<9Hf;>/̢`g9ɧ:8'^OC3oI:]|Q!-HI8wpOz)V]NQ<+8ڀZ]Jf}pX^\Lm{CEH!π> dGIř0LܶPI] BMìM/Uif%/v;K">z1Ci 6 D@&xԇ|(߫&5[k }VB7~!no͐{HVcтGK(/G˂`([]WL6z1,òN`(h{Ҏ3$g1%#{G@i?!8IA΂ॡdHybeNUS %b[gZJ,NS$ߧdΔ%"eʊj&#snxjaf.8BQWXنui-v)g3n7Ha0A&u AԻ +y;aа +ZHo@#c6%R$kP=zX=cqюWfb߽cod{+YqDF.XUGh T4' F/P zqmZh601q1ӇFЁk@4!Kͻp$B;ګOMu9@%w~Ӕ +P>I/XBAȱ⨀d.KmfGj!7:/V?0>\ 5VYa_g\ +k'&]# lǛ{K.KٖZ#@~`-K11!nvMFh0&l`s M:2gu.dAÓZLe߮x|5VqŨ>X{RUM1`B]Fk61"dL{:(3K&$" n6G)2\{oZmoxng=WTD%1)p/bP#QӠ-C/Q+jJabInQC_p?bM,F1}׃ZȧV9H NO44 +T?}.J$MZ6zڣ_4 +즭_UU=/Côf]@R_%2f]IBRҲAKV"æOikTrOWL21%6pQ?E*llVNjݟc5Sq`(#cѕs0+DۊIĄ䄄5,q2 *m"(@E젠 P-C>CYPwp@8J |: 2!x-BGO%Au=Wc Q/wǪɱ.cL f'fý+́v0nSZizĩKr76o3u sqF"'>WCIe݁7V2n~~!6NKlrc(}O> S Pwz~&^e|+B Q֫ ʤb#gD2˫|2pg]uEL!`'-J.iWQ(b5, L}Oc%<TK8C %k^ip9\:E|JU#\ۂR=U B˖o#a2sU4(W]K"gO{d왛{֫.|+XV tnGdAZ`*rB L63p2ۻo8fM06:B[RiK97>vrd?ݚ 2Xƕ73H1MWB|DTY" \̱z;Joq1TP|y4BV>ENt=z?}"# ՄݾZtkYmҾ9 ]8J"utQf X=RkHU_bseΓUr'cNА\dƖ}R+ᦾL™ak'aH,3=!ȼiSxjHSqXs**q)H񤢠3.=CXê߯fb%Z[-b`A>Kۢɹ &KIhsIC4an,&jHov锶2ލV\K>-W#S\4؆8'!?x3ȜmkIHD(BgmZxYetvZ\mg]2@-c2u+es(;SE_@f4dY{k0ߨw+nM)noΰ[}8ځJG*uHSiF2"+EZƅj1PS֟?)C7UcqJ9p1@$50o(GA[g+<VrRc|Ǘl(T mAGmPCS_ㄚ8|?cR_M^n.Ö2rruf,SPBGMF -P6Gbo^{ T8JnJgMD"ݍۀiumdvԌ1[ (c0T; EY_Ez|^+82K7'>/x@91~Wn 4 eު ˩ʾg(Gw{r-hڣZZB\R/c`Jko֒#gb*>'ŻQ"="vԀ}zR(/m-YMύW#:7ޫ8 {{Y +JkSG& Cw_> P{P'27CqD QHR/ vx`g /_s )wCટT"k]TpF$H֣4_;gt.ԝ"1x@L"ZnpQ.^>zn$7 DCv-iLNBeW`4]th!]r2kd9V,}\ي;~eA.Skץ~Gym%۳D +4&H@Z?n&r6ŇVdIm~pu +0om@4"_8>}Eu˱Ai[]&pcޑoUEw֧(_]6첄ˋK"{GS@evd[Fsp$2MnE&~yV!ol%K`vhwI80uLu2ZsVq1ˌ׶5 +DpX`3^S$8YK#)ߓ5^9ͫVz0$17y$0k_:> ijwNLli1f6vL^1{7FNʬ.`C.˜K"'p,YvĈ : 2 &Ln~TL-JÓV4dpƝZ~s- ; Cq߳$㕚G.G:aN$g6"l>FmѠQ9 pPo6hΙI|הR/ =ث-Q+[-A;2D4Kt+(<$y{#Ml%%ꗠ7*F7to>Ng3Π>~HꉴK% 7 ,- +p[ ʒ +'|# ~>sf V{>Vã3ۉ@9r쩓][ں@h-~22zX;g"Ib?+Pxk zĹNJ;SCS<\lFgD׬.AS=BޚB64)&?wԋ&V54c?R6&Y am` xLF(:=Ü]pH 6 aZ\ +-gflpwO>@gq](lQx{y@Ct8H"'NΎhv$6m}2_dh +jE%(Č]f=P +e݊fdECyeւZ(4JvJ Kݵ'7iE27#6vgvzU:rydbsE:fX7I.'q + gɮ(aDA^ +.KYbN8B gt~!5;x}y=0P.NTx|qDЁ?&86*rm%͍4c`0^ fܧeY$04(ZI3T +=i*.H?eZ7ְ=K ئ3,QuF;FR^-8ɥ0AjM%x~I +6Iߢ;XThnd(SvzxLNU\Aa>P*EOc1 ӅG('Gw|.=tkhrl\"鄺h7vPrhs[FCI)o܃+ɦ$$Z+<0n[ MfIγL\a~ŵ|,yh?Mxߐ pMqedږJvyVdOU¡M0T$`瞉dC']s"wn=5bYl?[3Oܲ6#J㪥 _t~ qf05MgdyPr.CS)dA0oM31Z uqTIrb w" nKPºk\L׾S鶯W5YlpyL2]Ώk $ B _;5xDśPFu{~Tv%bc C~` DwxDb¹ ymS>dB/lU>LvuᙫknK!J`e5v%$@bO }Z0ݵuo>|6`u + Ɍ['ڶjﱍ&wݞjcCLT}ÎlHGKvdmD2-;E2 Z0|E؃Fs0-HфU 5Fq_ߘL +O%Ǧ$աՁ8DFE)j0;,NMS{ ޙQ4w%+rLӈtE6@2I?aSS Cւ? +J +e%vN&#bVĊ7N,7 ai/p[>DŲ;K~ %qt0|kuZ(eȃC 1(,ͅW*|+W^O==y5NϡrMҝ%31wDž&wF,͟#D奕G81&1v7*Eqk@qRA#yIÙJLGmW>׋) gvVff_~zu=Ma칸vԜHhDJ0cO#O~\8g%XЩX:T 4 9s!Lm_\ZQRbQHJFnD ̺qd~]I%vط˽mhJ{df.p-b"-XHi.|Ot7a\r~;<32$wl>m&I`YK{+_uJ.Ejޙ$k)Fl SzeWiu~Jf)~FNlGɧ"*neuRѽg{q&F\WhV]Pd8K\Ǻs?z罐^4J@69[.3?U:O.?rr>=czO7,8{)YU/^|sJCDuL >&{ڟ5@ +cEE\;Lv$\gX|(hٺ'oTҾ?3zlEj=> endobj +2097 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /AKTHUD+CMTI10 +/ItalicAngle -14 +/StemV 68 +/XHeight 431 +/FontBBox [-163 -250 1146 969] +/Flags 4 +/CharSet (/ff/fi/ffi/exclam/quotedblright/quoteright/parenleft/parenright/asterisk/comma/hyphen/period/slash/zero/two/three/four/five/eight/nine/colon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/Z/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/endash) +/FontFile 2098 0 R +>> endobj +3752 0 obj +[613 562 0 882 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 307 514 0 0 0 0 307 409 409 511 0 307 358 307 511 511 0 511 511 511 511 0 0 511 511 307 0 0 767 0 511 0 743 704 716 755 678 653 774 743 386 525 769 627 897 743 767 678 0 729 562 716 743 743 999 743 743 613 0 0 0 0 0 0 511 460 460 511 460 307 460 511 307 307 460 256 818 562 511 511 460 422 409 332 537 460 664 464 486 0 511 ] +endobj +1688 0 obj << +/Length1 1393 +/Length2 8536 +/Length3 532 +/Length 9398 +/Filter /FlateDecode +>> +stream +xU\ڶ)+NEkJ/Ŋ(Z(-Rܬ٬Ows~s0khrI[!/a\ n(@VUSq`33!fP3D]xyAQ~Q^D@vʲU$fU3gkb 3[& +qHp!N+ĒXB-搷P{l_`-]; +;!LX&0{[% +ChANo_ڪSy3;U\!p*R]ȿ̩B,.vUr6ZHۿD:C,5+3['qA ou8TNjA흵< Ȉn_F!&oo# 7F @%qG8rÜK`pOښ=!!D`!!1" zBǀx@gǼp?*x@+ˣ>D +~,b4fY'?";jA"GB,y$D#!z{$DC&!D;/ ь#!Q|$DJPHuGB>B]&a#!|$ȴ HuGB>B]oM e>@ " uH@N /q]@ ^>ļx|Bm{ DIqxxDZ{o +x;{af!.1W` ͉:cXgH}U1Yxӄ(0O@K+uFi!/M`7!x`H s6$g- 5cGl$~drnZ+S /M7?>M( ]xL'd\ ) [*^)7;/jؾ:޴  +nc;^`VtkIN:|@LFyHLXj 4TA27y  q'12{?O~*"m( v^hnL\f@(#>I\6W&Be?5tѼq)^wx1!+"ݲLE*ۖ<{o-Dw9؞6^IOr?8=Mu{F:5w|*8f.~ҙ{vgLڲ =DKcʄaA[e^ "7UJ&>< 9tBOf&/4!_<=TYyv +E 돛rD'=$"SNtςOT+UXB<^г#ɥZõB/SS'*\Jѻ7Ԥ.Cky+e0CNJzhrh;홐BrYJJy)'eWRX +HDGZƇ7+ٹ3-̶wHԞK +ҿ$bh@ߍ U,hPZ0qszemëSe-b]'؆K΋ZZ2ȉZgҭnLO[Rd}S5/5[09<Ϧ(yb۪I-2>6 RMw)t=袘%%rZw +lO|yB7F7$&@-l*/:Ѻ!躽0KV!K # 11\ mN|2$I|O}3}xҨMe*AKTNp-tUw3\U8/mP%Y!#%h`K3(~ҿ^0)EMKWG?~Pb6$&3aP2ؐχvW?y>b*UQ*M s).\zHu&Dt%c{*q{tӶ]H׳RL_˯=lÒ=%ҷ +hmi#s( >V|ʣ.%VDnѠ^r1}?ăG0eO<.oz EjJTX Z()AW!o\򬴰svFNos_NX4yG?7!DVWמu)CwIlyX}+] uSdNkШz{ŷ4u`dyj67˻p|1zFKIjoOzi6?nXWz)(1)?P\,´_(T}vHUt-(P;w33,\{Q `unϺF]G[>I{(P'JhS`k,67GUB<~ɐ<}jMBE]B-XoḢ{4['WvƪVtB׉)m܍6sAd|CVh>H 05*PWqwe!Y9*rke>hp +k^SշӎlB#( ٣i鵋-Lc.+HkEb_QRr"X_rۘϒ72/%VGA٘ΗZ|mc<xR&D-Qg\} ^DiAʨ$R3г|' _: 0OBAMIlSk!~6A{+îNfì E6"|q7^"\~8G7 F@z+2<7-8ϊ\oEj%_?2dDE5XH|D:?0ϴ( t8Cl`1C%ɿ ה*+t*iǙFnlj*˽_\62`v yr4X%AǙukZKꚲM U<--,7';j"=(az:E qoLfVan IG~@_=CR S4D#MIƶLRx2b423\EƤ놇$ +7A> ~V uzJ$ZXN(0(J߆NjRλS"Z: ʎ#ےi^6+StF`-ύx%DH|E\@-RZ7f&uh,xOY<\$뇳d{}@Wg3BrZ7L6Hfw955&.o9t +HGj_| ޖg"ځD+xMfx;ㆌ +q#biM#'5B%.DpH#X_?azme{Qf9^yVeTNn\JePQJ[ldx+XYxDrM+%}>2U󉁺F}z$Dev+uYԩ ?%&7lyqw6FŰὑzcav\ϓoMKęV:#cIoJR{xZL)k=1d󮁖}N탘K'>i(+-qdʪ e +ֱ7B!fox#ኌ?Ծ.a)_аo)Q{q&11rN]>63Yd-R7[FJĽB8~$eܖ^eJucOƋg'*KS-nc`*:aԙ}w;vsR-'yg}`}.+_-E2to'_6sc8Ih/)_ Q%|l^ޢ[cxu՗Hϸ-t e&PKuǝ_u1Yu%h@7y:9 +=Ht~Ba }T6c$(3$(d0Iz{+$0t7rIo%Nh9sZ]\MJ iٜm +bNhZ^m'"I# `NF#BJh3o}oPꜘD^ȃ)dəwTw~?Eb*aitU]x$_X{nY^+Ml=K{QAh>иGsƵU:#_ՠ<00~쓴+l`Bk?&:\g;1@Ʉ_L܅mZ%V@L&xTJhF"Uk7*H G)7۝_Ms{w%W@|'#Jpʆ b{ulҙK7澅jF%uq174"R䩖i3ty~g+}3l pQCpV"DFP{ljs&k˭ԶuI`,>'v)Ć%BCH:)~],e#<&g略y&iLnKltksPS6s'ᢙg @p<ڞ뽪#rio}bVyJEWw9: +#9fl9t T{XW'i+  iLT%Vsr uM%YNФ}lH% iKg6,]\/veuhXAcٻ +9z +s̟ND+ژ-M<a C&~S|3!R3s{_)gӑR5fIip+yZ%$uG7ȼqM<-_\TeH^1no +@c "xIfXZ7K\3'_a&p8iP|3"4V4A:z<"IROUVz6>d.:M] +Xkr`Q?"4@uJ"uD0-5o45Ƥi]Vw:{eOV!:E?z)Au,t Wmϣ%jҶڥn pLorT?6FKиI/:Z]OеѩJzNrb9߮cv\BbTv>"XȎΊ4jj[cְkNט[xS]D.Q,]4j.8 (q=lĸO6QGө(cj?쟆_ϲQ?Y>[ =<:W +[9**-.t!ҘrreIYȉ" ot 6fv@tNteI"cՙc_>Ӱja+ȼG磲_zq0Q]AVyX.~ǩ^Tx5N`r%rAgI+2㊅킠blAqmKȭc)W( +Im_^ar; oG)o.H]?Sd Ҽ ]cab7k;fE\ȳ;j%\*boGJnՔՈrhII"ыQIIGVUop$׬⧳,CODtCT )U~(ڷ:»mdv1dzK;jy_vhlP 6Őj%37h( +tQoL]@)lJ1  - +ͥ'L#EjJC I~ 1ߓ?82}f)}uz4N(]k*7` i+UݶN^0r*j>W]$s%.;=[ u'AJS*S %ϑvby`kՠa/_ޝ@Ev8Y unF 7t]yO6@kү:PoH 3өe#[k> (wJ!Ɯ.;O:f)!}ur (%3%ˊE Se:)SK9X1>c=-k۴~2Nk[p׭[RoyhTtRG|%ڡdB E7 j9Xia6a WZSJȑAD>(*a?nL(zxvk";l2% _㽥>O Fybal!{M܇Y=8.{8f3qbqZX2*bK_r Wh htUr+/ +FP0 GKCk^heK^b F&q 4Y`tzmU:IA3+~y?- 3`/endstream +endobj +1689 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 36 +/LastChar 116 +/Widths 3753 0 R +/BaseFont /FKZVHD+CMSL10 +/FontDescriptor 1687 0 R +>> endobj +1687 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /FKZVHD+CMSL10 +/ItalicAngle -9 +/StemV 79 +/XHeight 431 +/FontBBox [-62 -250 1123 750] +/Flags 4 +/CharSet (/dollar/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/A/B/C/D/E/F/G/H/I/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/e/n/o/s/t) +/FontFile 1688 0 R +>> endobj +3753 0 obj +[500 0 0 0 0 0 0 0 0 333 278 500 500 500 500 500 500 500 500 500 500 500 0 0 0 0 0 0 0 750 708 722 764 681 653 785 750 361 0 778 625 917 750 778 681 0 736 556 722 750 750 1028 750 750 0 0 0 0 0 0 0 0 0 0 0 444 0 0 0 0 0 0 0 0 556 500 0 0 0 394 389 ] +endobj +1641 0 obj << +/Length1 2027 +/Length2 14300 +/Length3 532 +/Length 15414 +/Filter /FlateDecode +>> +stream +xSxo۶mm6glNc65h;ZiZ߷ܘq{t$UVc1s01t22)j2QR9Z;č]HXyyH$M?_>N>.8J1G/gkK+W1ID͝M$ +ƮVv$j^L$"vv$ +N4I*HZK@_qr9oNm9:/t4Yb4p>)^;N/dkZ=еl*Q9.EyD\WӯS,:IQsBV*M |xh%5ޙx=! zaLxYzqo][&L`l+LT-e +?%VDx#/aO5ib;T ү'=hbפ-RT{؝sEUC½/6J@Q!-.(3Mi@eE^Ǽ{P;R&{*f$ h?,9oC2x3I ocBre9YCvGc=^9\eu1ΧjӅ:= K1Q[*[L$kX + ѓވ6 ٹ_)Xe>'A(i(5r .3:s,i<Ւ-8PelG` xBk:w}>&#h,  8G"^5Mҩ|n]>10բ!]L}(*r`Tt3ӭ,k2%n7YCp)n[ ܛ.KY-)tA +ryīNCtûF & ’:Tz }sEXMB~QRb,%Ȃb!f_DlmyR +|T'-TevHksgdy*&xEb}Hj%gPdcy wAA-ԃɬ%):ϚԶ )wWJ_+3$*AWyUezznp& O-m?#|&?cKMGUZls.ad aKʇ50ʶL}eDm,q mS!@]g"\﹦@I{ u԰tQ&\P%<Rʵ5j6 ѠQ;3KceKp>w^a@JLAua y[lܳ{$XG€7 TI>&S YCҙ"KVF ,3nu—JC"&gRH?|Nt8.[R~I*ĵG̚.Tq;J^'FqA7MLq=S%evMH5^"*䎑_ŸVV_ܻ +vopZ}UiOVJ2ˢC=)(gB +eeat`w9\xj-51)gy%mr+[(Ayly.) b8gV@~a3F/{xcrSroK;ŽȗW{b!N Df;g#ǾzHr)xoT>`$izkVW(jb8_l[()0DdZC}jDpmğt-<&+ܟHJ>gP4wXA3\htv - e-76˗z3E$,Wi]k)FU.DEE]dF4kc4 ٞ$ Ceyc);K - #갊s2~q=r|d=ȒJӒ91^G >7'%҃#P"rV{Si q-ς@]asDW@./;9Upl nȍ'a@Â3_ȜSK5ϴ)׉RrBJꏟ<:_P{m;,zR]?8$˜诼GGk@Z5WFC 'L:9=? s{62H bz]Agr]17:fa>}tQg)>ohhx4n!u hlmcwߠb~tg>%(e. +Jw%L{ťѻQosJL;p!*)_vWoj^'(h8|S`-V?]=}jP>ћ. 6UZf|g<5>$<뿑 2H$EĘI0~lC0-\+-zmSԻӪ`BF|9s_#6"ФCLyZes7\CalxCX+j-$usC~-n*dQ0S7555g:p \Ith5yĶR1!JwT=z F*D ӗg:̷ǻF/Q AOz9vʳmpdigJЌiߋ„lVf'>/ٱ++C.]^x#$Vb MbSU|D5tkNp[Ӻ*g0Øz_(~ +YWb~Pqٜ&ݔTC E'՚ya +]Ml2= "a$wz2_ |Ӯ+rb؈lynFVxXcW9 K +6D?=I[Ԏs#w\m>Fˣjs>71K2/{-39JYrX5buW$@͘/Opװ%٤Я!R(' +O=TێDb_u0!?i۹+n_M ׈ddTӥ_DId'!l^=`NXe&B^#z-4SۼgǨ@ɯ)/1F9>A"ДTaI[ 5v>ItxhmfIHy%rFX[6'vߋ1#'Jd٦i3_Z)siD@Mk]Y3R>Dxl9k|e2 vH;y_;*\=GeOlWwoo}Xyn7pFN ZCc2fVj t8ǻ㰚3l(rkT؇ +B$y8{u% +'ȫ-8z1g{&i̢NhÜ ?cUW66>N"MR96FqF.=(ʌm$Q$Dm>8w> ;#kq qR2D&GF17S߃yllX:|iދ Q#AagqZW=7a\& +^{:La uG4b`mD.bc .n#D 2fł=O,,hBSe_G1sMx.K󎴨km.qN+7A֨Wlݝ65sypog[y-7HQ&_t4r?? )3꾱ctg3`wʣ7b|9ekn{1\b& @TXa2d,4R{%jRfhDN+ |RvͰ"Q⌳` n\pS>m$ᆐBGL3wzN1''ں%OuIxsE'4ߜgUe;#'a5Vߌ)h2u/Z{ҿ Tj(ɿ*QvXBs(ە]4e䳇K'ONO$#ɷMomjBĶX=`H ϡ9FAEtWB0֨,if@9g*0Ҍk?RatK_XپE\rsXdUAeWpa{<=a}S-)4=n#^R2'AMRkmŸl 8B5,V_YL~Y{bd =Km7Y9kp+] kmz؄FdfFGmJX@$K9P[JdhOn2嵋k[$i6B3SNpu 5v IX + s#CledXC}9uazOreeF4'CC?@*Yd3c[&ԞC^!%j˫`z c.%F +%i =&[liQz[Ѕhk6xzְ + +uԓߘ|MNrR-P3/cߝ<gB<4\edWxhK+mnx ճ.}|ھQXv; + J"Z>Rb:z9А?IݺXpd {;*No\zT +` ++("c ,؆' z~]fH+9,Dz3)3EwE?T\h׎ɇ :/g+u[Xȱ*;NȻ+2Wܥ>iz7 fL +imrR(Wc $6vcI1V?1% +(:|v1Dr/"R73";fHbS7=mGlk,G1E*H6!D$v׊HsIwo9burg)OnG~apvDeFQ +fi!d23`oܧ)Fc0 +^ +;)?$x^mnֶ~lީߍ?Ra7뤱X1n)rz,Ze z9U08o#,nS&V^S,N -!g.=vs4_7 jB0dft5aN&gs=P`DP\JS#CRE 9ϊ>]5Vr + * sd󚏉azJ>}:!}yO5glz#;N`$Tz|+2{jY-'H_W)T5t]mV@ɤpe.hL\ojfN0ƣ]3aս|z1_~t]E΃`AlQz(de"Zo*z$RzN\~>&R{# WyNJPyUg2\ȩy&<`E5@8ꥬ!QlBD|[_&Fs :K^2wU $T]ȠQuyt~b!ŎX|V76]7ÎkHY*Ri'|D"Gl9t4J A9bO.{?N ~'ߖO=(]“pG/mT"ֈ'Rq4M(~$C7(R'+,i g82Ù"D &mT,!- '>DPJ4L3}ék:KakGp<;e[֑0T$X^ZnĪuA[!)b%x(eC4„ONl}oGQQ ?Ћ}j噃-WԻIW걳Q,t;fJs g߇ūF #ZOjleF@h +|=BϺ0 .;pS,ְ,.Y +k"2jPQ0gb'2&)NW ~O;x35Ijɹ= k&+x0Kܞ'߯pH$un] N]ڦgZhu=w1'( b vLMrj`֨YTfRix#m!k5 W$a*/[lL_.םH6vGBdKF^9TZ (Y9n"S%}BlB:ۛD:7͂vukFӮlM?]ׅ)*-zo哑ee!@(yˊ"c)R/0B%ػJd,x*nr_U+Fï0ޱf +( {͑n!׍uf  ALL@,qnW*uJ&^WNZioH0M#_N=2b_<Iq1+5Z9sΔDe]u my€NVY`(np݅TJq4Z*],ŒCU[qraW 5.qĽ] FCˉ, ~J6l +ϊ-ܼ-tmLʯZP6ަ}=Aͼj( AYأg2 +2ta k̈]l-6Ln$C$TTeX~ɔG긋Q$E6Q!~sc@#d<6¼ef>>7%zDʎ='(붰z=T*TKl'P#L#[wcnM[f1jsDSD 1`k:3qS7"a:>1櫢ּ= xZ篔;C0*^; T <ݾ 97P%r;oŊ4d|z{4K]xʎiӅ`BYq[JyK5~NSv#B{;0# P+:^0F/ekC %Kv7t E)xas"k#埅>ZŻjWM՝O7Plԥ!:!1KkݼR:0`h6&$շx{Fpd1M_4meOV[h *@P"4.8(Ӳo[SD +7A gAC +5@R9йF 6iAAY,f+IV$ΖǕaAtOnNCRP@06:*Dѳ:TRԗU{%_of$ߔfjgce* ۥ2&fF_%rd{'N"㞝1uJ | }gZCb7Ţ2nK4WZ[>FmcbO1Vq +A8`W.\j"uB(JQ#r`<) v_Üh]|e~87ʹ # X[ք},e V2*pi3/kً W}c!Zs*'NcH +_2Hא|8N +"UkQUcK7s3x>^Yic9N$|3B8*I .szG5D-NDBPQy"!&~HE]Jkm,uq O#ËXQx.~{5ǹ2ȟivIHXo̥<ܒd޽SNJ0 #qebhz/Ą,w 8t8,v\dr1ty@`Doi,мF/'J%;4߳^ޒc@b?v#j#ESL ![!{5uSDw$Q=6a˽{l?)-VͫIiBŠġ +*?[)0%Y#n+(d +zr,RlBXmSkWQH. i!Zh>9s]~,MB#͸v{Ă1Ī.ΦQ2??t+M0#9P$x.$ zkt=op.Ip"y- B-w?jw7q'u3J%U887)-Y>,GR^Ĺ;=\#ۤ0/(ILf0cA9!n^;+06Apme!EէF#>Tky 99skBFVrvDo$V??lKy7[k+H1֔Rౢ=?`q>-yG qM +|_PY 1KyA}Elly"ϑ '.dzia|Oݚ[Yv`7q2O5%BriدB+ҟ,F|w@fACW5 Z?b O#k.[N#8;YN,Ԥ1x7W@Iԩy+[x +խ(WU Tss-]2ߣv ז%.bi mפ/HM˨&> +'fbB:ehzT1Ίr'm">=6ћ#w,kzl>G W2đQLi)MiufHWݎ˛uBw0T{_q)~=@\0;"9eFTA,-H'D^+%~}[mYa~a3u,k\kLQ +]Ɵ{R$wg=mG%Pe.&y~IiFg2ZFH375ͧpbrAfrGl@CYtR%M~kfVuMd-zyv2/˧94 ͈0z-JjB-s:LFǧ91.y.,Q8W;wIσ6o'}&_̯ܗ- T_~ }{mxS> endobj +1640 0 obj << +/Ascent 694 +/CapHeight 686 +/Descent -194 +/FontName /GUFQBT+CMBX10 +/ItalicAngle 0 +/StemV 114 +/XHeight 444 +/FontBBox [-301 -250 1164 946] +/Flags 4 +/CharSet (/ff/fi/ffi/quotedblright/dollar/percent/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/eight/nine/colon/equal/A/B/C/D/E/F/H/I/J/K/L/M/N/O/P/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash) +/FontFile 1641 0 R +>> endobj +3754 0 obj +[671 639 0 958 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 603 0 575 958 0 319 447 447 575 894 319 383 319 575 575 575 575 575 575 575 575 0 575 575 319 0 0 894 0 0 0 869 818 831 882 756 724 0 900 436 594 901 692 1092 900 864 786 0 862 639 800 885 869 1189 869 869 0 319 0 319 0 0 0 559 639 511 639 527 351 575 639 319 351 607 319 958 639 575 639 607 474 454 447 639 607 831 607 607 511 575 1150 ] +endobj +3755 0 obj << +/Type /Encoding +/Differences [ 0 /Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde/dieresis/visiblespace 129/.notdef 160/space/Gamma/Delta/Theta/Lambda/Xi/Pi/Sigma/Upsilon/Phi/Psi 171/.notdef 173/Omega/arrowup/arrowdown/quotesingle/exclamdown/questiondown/dotlessi/dotlessj/grave/acute/caron/breve/macron/ring/cedilla/germandbls/ae/oe/oslash/AE/OE/Oslash/visiblespace/dieresis 197/.notdef] +>> endobj +1631 0 obj << +/Length1 2318 +/Length2 15115 +/Length3 532 +/Length 16377 +/Filter /FlateDecode +>> +stream +xUX\͢v ww4Xݝ Aww^d/oլ9ʛLEQd922+jh2!RQ;L]  SW)+//3))+ HE*rrZY҈ST 47u U4u؃07#U^Lvvjہzfr.o68M>ꟓ&\9B[bo#E%M`A7ILNo{#]F`7(x.*ovQ}#]F`7hE.:ov7nljn p#.\^Ϝ@gsc,>>]Aoˊ7lxfo67/gllm]B"/`'ۿ,e: +>B/[9l[B_r V! V!/[} {sfX8Yqw\\v5%&&f ed4AV|+5wsݮ%1-#.΁Clқ$ 'a ŬZz;!Gu*0Q`H<\:|Tǥ2f_M>}#йRu$ >Fko9TZQ[4s1xB#Bѫ9[G*N3<#;zSYGzJ`?pVKPB//Alb -lóxV $Wc I!>WfVGϴ9,.uOlzAab +kN4=!/=Nb߷(z2mtl6? @SJ ⹒|}tP!QKwç'dtN W;7 3qW6 +}s 7ހJ +\SR~?.^H_K.·A~ʹFzE9'i(KkE[Gmng 2d*i1U8oR!# /9[#ɸ1 %unX@1Du1"ñ؛WېYEKq!F%&gd., syr`\Fe)i, BshJc_9 +zdO6.Uc#׫ӲP)_ߑKSU]iJv.KӨ *ۮ\_'&h0^_]'X >i8InYP\\X.-aX2 Q +AZPR)?'^^D]ɮcìRgǞN3u +X,ބV즌}>^8z <4F'3LJ' o Atn[h^w +'+wGP}Xb"'^i^e!mEA]g~;gD|8]iL[?_E~d +i(MK$~K 6tT5Qտ`ӓgN [z{豛@4wkNnw8n*@H qǬڥ +UhvNS}[vͪzSD`YtZ%=T&'s33xw_O['#h I9F6:ᵩj %9eĢ(u 8t-ѨȤb N<މݏ6[ip)zj:yhPp<'H&)yzrLfvwpp;nU_ߪ~f2x +7OIVAfN44kBwӈp`_9c4{[!2adFhԧv:w̆q-&'-fބP~;Mzoz >HJR<Ӈ.XX=1m']%nW]Kq亿A~o .f_*TZZeax/i\r{Xswaj +d=&ڝ;zyu$ؽj8[җyR s/m 0}$%x|>37,1vczOOUeݝak]4h<{6y5#Iں?-9;SG6CgiFE^z0^J.M^Q@(+玜]a j_9\wQ傷&#ϴ8菚~KJu?ѵc].s|cVQT 213y_Z?Aa-JkDT~&=GGJTR:)Pɮ/!Ӿf{I+Dq>wh3 +u݆H.Zf|#F&5Me3"ߎN T6,߸d"TۈLzfsF늫ɾhP޻4,OmW5Y4/=9GFYT#c{-ڂ2}`o;2Oz"YcrZ$]eG@lCT~9>ʃ7:֥Q㜃⅍| Nd\Bj d (u$=rZ1؆.b  z odĬ7%:xRz`04|1X[t R_kVEL,jmrٚNo,ѵ upv`0Z]^R `K=r!0!`~{pOe4:c5cГ߲P>Z05 ^dKJX`x>&^lC};3܄绝}V.~ƞii!td4=gd`|AzBEx +lT\D2>,㊿.0q8JN5f%orJՃ +WYreB 0~BK{;, +C |:PKPyE BEeN#8C~j2Eۮ*^xН Ԕo=-ܶcp)ޓe%'0J4!>^`|`[&܄ HQ1ƏPh{v}6B u9}17Ia2AA]OU/> #Ys0=azIDu|a]aJĝateYn/ϺU^Kh:tK$FdtFc"s1`&(۬E zcg|,t|ښK2;u:ʛwHFn1)~kg>BCZzD5 nt:.<,3nGQn5 ^=۲Y4i"g. #/Y,N+9JcnUK wm[buVHa*lk.ÕPa{ }#ONV~z̫$~>RC iq@NQοP_񱥀Ey-Т<<*7K +ol ~qgy1 u ᜾im2Hf@r#h C|_nZHwK;8 ǝl&u]bFh ь_UiwNDqR/""*>\JKp +etkCiP5j"-oߪ:ߦv^V|-BYe\5yJf `6ĩ:;dž4X +FlȤb/w^V_KB.n+!ߏ _L,M`!~a;_BAq6܏g"/A<8ʐJ1.<>3}]F)ʁ輎 kng ຄKS|lqcJg 4MJoZd'8WOy7ŭZ*chw8䗂+WTgYJÀ}Ǒҡ\™v O+yO'_{ 8rںfJ{w (ڒ"\Gpd_ܭ875Cr1r^gEIrZ1ۀlа 3QNJ'4cZ٣9sd30OQu!ړeˮBYW(q]"ʯ&jʂZ=s +Vu6P֡&]3gH]Iz۟TH2~TB]~A4}Mg*@kOC<̂?ܗǟ;):Euu/%r w" + XVT.с1Gr=zэlvf,Z\!D!}Eҵcw [rrCRg#)0yչV /3+*2<M|\'%+p|a=ϚtXc^9%EMpMEe*'r1 EKBxP0!b +jjcm$:z/n.uYP|V~ ᱸ ݏQS6./PZZr3 J1FXId-Y&}!x9QY|R(N6^Id/иv vϨ!(d2$w5rd$OŽ*2:`3w`RpV;)#fypa:6^hn][VWm\ };.fE[Zi2}ثPMm3sɃ2E6}ݜ߳;^DC*}hjo: !i ^uj/ˊ/q~>SĐ,-W cXBHwHo/Rpu*2:¿T&v{،'S%=z}_p_oeuD FQV|R>=#xu|QT AL~T +ibGd..=vmv誔yV(3_mC(H@o>+?[h}It?CԖ"T(U3CNt2ِ/(~6 +!job/ dЇZ -VK$=~Lj-d87ySީұ WXPȴX-3hv?(žBJ_G6nH'"eXXΊ'&F82ER_@T5ް0]8᥄ko?Tc\Q=/Z@{95|hnM)wC\doN@RȝI"B6>^ȟm}W`>2+m7*@,s3a_>=9Pf4p,5I;}|-: Z ܪX1xG>va +FʧÀs0sATX *ӻ0"|"ͮ15F7 NiN '\eccF)f{ExF8Vqޯ8!5༄:Iw}DcFFt$Z'A&9z5TCjR(G3"a"w+v&d+nl3nL +UOLVD5qqr,ԗcF̀nESG=,;(c yBZڅ[]m3( =:{_%-fGJKq"3pOyqt^cBr<=Mhbhy%T_l{Jafyw8,>#At}$z˺!Ϟ,r A49=.mfzd´ڽ8ߠ|N*cgu7*m抌؇h˘ BB?5)V '!]Q_BsI[mF<\Q`D1V'rGo-{&=$qeիTg#׷%OgΒЙ*"ΐIOHu~zG9.uէßF{ Ni^3\xp&yN{", Bua܅UR]&RkO-O`8&5 뵰g;o&h#z~u/`WDG$Ϋ0[MVL|dG:[Sſ*mx%4ii}6NW{It]e֗P,)2ݒ&:q5sFW|믮taEvl-ä } " +0ȕ"=/kǐ9ݤPi1% Cf魰S@Hb<}l0¤fRµh5WBb7 <lJT8Ұ;&d7>5Z~]fyœ4:cv+re `וlt;O5/) ΑcJwBJ YtfK lTHU~J"}6|ER:)f!\Ŏy'ܻdy& +e5/j%k8*fBBH;kVԋ6 ]=UT"…fvL.ΏͱCUU͊2Y!.Q9M_͑ fLMMw;zBDÿP02 +j8oO%h~qPxf>"4Rqɑ&x%X wy tIp𩉗<փQ>XQg +Rq6ndrcIBs@598oA2PUʹM&mx.nF?c@;MO( ^YR6dq6Nx0H'S|fu6̚q9fW+lSG 9mWoϛr+hXŃʭ4tŵbW¢VS !b-ƙb;Ԫ1>"cJeChѨqEΉMd`;h9eZ`$E{xdhp(xϙ %Hgk<@&X+楖7>Zrch9H+"40t'nͨ7‘t=WQvR$Kd~ɫ0u/`d +ٮ$l#BVaw9€[zOMlOMzWNux1ܩ_I"cS&В Ť[cH+Y8Αz4u\9X(s&ZƾygGKĹr[DSRꘗ²R<8o)!q(wmP_fw$I=^ȌKߚš̏͝1~|e}dҪ%E=*}v` Sy4_{y+ܘ'BܶC7B\h>]t 1=$*-%~ wm KtC6ua$nB8($B^6ZAUl/'6{vvI̯2<9FGz ž|j8ME#Gs 9y*>2kC*hO Y2^ޯyjIH +*]&ՓID*+Ӑaͣna'VP'/nn;iEk],`郼1PWQN?[('Ư{Yx[A06Y%b1HXq0*1,O Su͸qX?wʙ`<|uN]蔏B`3Ei"3~qk>+)KL}iOMV%5|%s'G샯%{g2_Pabb&VY]epfD:jԢ%V.OhJY'@!A%Tqn}6͙!J_iݰ;4t ]fy+6 a$4/M0h)2>q٣ßoyCfb5Y1 U{#ͫ۴Qdu|ooQnnqFaJO Ẋcf]PrwdC!Du+Z@yH1~4 7CO4^zමYA-:]uY,HNirТ.IE,t_' (!;7EnGᾠ"舦JhWڲc#4\d뎫 QTkƾq wwuodX@fm=e[ȭ1l u<%4u*FhbbV?jX2v}uk9VErQRk$BrR|$ґEU+Vt׺;ȣf%+z~qJv(Pb!@dԉُ8' F`F_Whр{N Tq0%|jRw&I8Nȕo?E[9䎗*oryLQX\mBay7dsE!iGҿ +%nj:>j uhqKñr!YoJnRПǷۿBJ\%X.ژ|} uǓgwb}XNreMPuM5hp?GʪS嵺3.y-FE5Sj:k^JØ?32QVp*HI`=#3\zjщ(۲!5d $␭֞Nx NB>!X + +gӠD҇\%TFlgXԿ·>8-\(fhu <'}ƈOvHJ:dX771WdGAF9?EpǝHO(?洒֫$ӕ섩 ~*(2+jVP;'kse>gFJPN-APtpVJ#+fI+1Mq󼓝  U,3t]A1%A(~~Ǒ9(L_o^ʈy=֕^b.O~2Uݞ|[L@@~U*ێ,PrbTnI+GrԓR#0q Ŝ[fGHkΰT2# ~Ħme}&Jz/<%MUU AՅuZ:fua9ŠHI[꿌.*ϝ | 98 )D) (ZK`>R='ltMʽl3w{ü{"/允0ju2٣rk85V:}N?DM(U2#H +PmHB#~ a.B~Gi7lCб~f4 +5t#Q3"LVsԋC+X<Y|6hWYL-g$3Iv="{kXS͕cuaK٦JzTDM\-es^+qCJIBAdraz,T2N>l _ڌbcVP_K, | sG7ˏ^+KS/җМFTtǹ>**mf  "ݹNE`I0r&sP:|Vf!q8Ư)>Ыcdo~QA6yϼƕAHY".*2 8t * +(Xv!E5G,:%CQ.$Q(bƷlGT!sJw",ݨdjQ9+t? 1{픲Z& xvbH8Ӧ}ŌS&;I.g +g*A}#|9p BiYHHmv8=uՋo2VMTpIygyzHdITubgN*V$xlB#}:.`;o]cYX?3аPqy7w᱓,"W!˶8aqظ/}ppVROI:kIGW;*>lJΑ +8FOo1g :TfO,{'v2qK)[QT-dMW,6 y,Bsם[cmVgeZr>85]MXE$v*mW?koU"ɚsy-a5&G|[Ց;̹֠ǛBW~e,Hk} O~T)[LP릟AV,.# ߱:'ȭ*,qG"mb)5kw˳}xN$\QosBȻn&dM#8iɁ#&??B#+8.fi;gۍH%dZ҆"W $F.߬PѼD S6I9_{vlׅ%Pǘ0V.m( )kT%ǦH\/WrA +|qgWfapx zFaK|_D,<˜ +`nJ_D5p".ePjM]OG-־WUdVNKB,FL'ƴ)>SgO3F0}cw<`[ ut8[-=~s >@77b۟?|Ìz.IuH \]ܾd^v/5].3bS" +r_D&Ԩd_*C#iQ4)gY9ϹYwWͪ +k0!8'B-/Ye%UIj]h `cݍ{V5*P'a\z6:a-U 9!jПQQ֪GD2nu9 H\=dJH*(/) /m&d'۝JË]dw N6~1:vU;<|?-ss")tQܞZ}EFs'U[r%H2^ +Ps'lPCƸɧȥP`/ZbËf&Z:1wU{Kh'r-Z.>w)PדU{5Ke\(e;L^gntQ.kW +%J8 ;sx%U{giA{!u^@r'B@MnP::oU3԰->lvHwʡl+5Q4"{c})-mmv:w ?/n ۇ)iy :d\lLiwۅ_%\xUrQT(1HJW.nM/o 2$I4Ӷ"ex<Z?D:v& Q߼k}Qsn-V[ÖR(&&;g!7mp}TIIǟ=lI5{Edч!~CEyt!s?:g6xԭkd7$V-5L|PY[O9K F?C\GwD€Oδ:z?2> endobj +1630 0 obj << +/Ascent 611 +/CapHeight 611 +/Descent -222 +/FontName /QDWYNW+CMTT10 +/ItalicAngle 0 +/StemV 69 +/XHeight 431 +/FontBBox [-4 -235 731 800] +/Flags 4 +/CharSet (/exclam/quotedbl/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/backslash/bracketright/asciicircum/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/braceleft/bar/braceright/asciitilde) +/FontFile 1631 0 R +>> endobj +3756 0 obj +[525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 0 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 525 ] +endobj +1627 0 obj << +/Length1 2287 +/Length2 17128 +/Length3 532 +/Length 18419 +/Filter /FlateDecode +>> +stream +xڬeTͶpkp Hhݝ܃Cr꩚ju7* @֙DLAYB`leg+n %aa%ހ^$bvV$b4t"8Zے(;[l@cITL$"@ ?O83F3+Sg-?J2v$\o+ $EB/M-Ѓ `h rC.*3?mH`gp]5vSYVgc@;LԒW`k%@"ݿ_mVjb? ʎ;.3(,}撰53 a$1vt4@qxXٚI a&F[;g#$9"=g2W +B?Bdf6P3hl͟3O  ?GO4v"a8lzu2?Qbg `Ot-!A+8 ejgcc'Z%Z9%neǐ'h%G?"la۟v#쒝˟qOV:N$ptZ"hC< ccQN Adg_NT?A8AJ"#@*b!@!.P$D$@N2$#@.r"@. +@.J!n|C ?rQC ?rQC ?rC ?r\t_W?<w+GSs 1ߣ Y) -sB_r AyR1Ծ '$WcYY,dB_ AV?/Y9 +d* +d<J߅?f%*j +9lhy|zˈj335uqW}W/[>Aw)꒝)_𗴖 +_JhZpQxoA+ q9ڭL CCbW.ϓFZ7 +dA(- gJs[+rO Վ`7Ht]9$3a! l*anɉPA_֯\ПLTvi1UʋPQ"Pu$9^S ė0™Wpo"}*7d3,])aJ,z|?!I})K鍒\GMGg(3kӓ6[_^(pOQW_%Da~\f"yAG&Xu;z:*h +s +j=hvP[*e5-"S2XBCkaʑ%q`\];h3?Uw ֏{y+Lب6t `V$>]jfYl# + R;r:oŒsřJ8N|b#[q((L>K*yhJ-Zs\`|ub-d~+jvn>J#x}qh[MQ8ɾnHHAmjibza"H8Q= 7NjK|º8ۏ4 w: @aRԠju T\ɞCg/sx)j3fqNeą{l*2XM8RLQ*s fp|p6DւRuˤPkoG! M)iM)d~ܰeC]u.#zeh&_~6+61ݟ K!/L](d奯7cq2+(~'|FQWZf. )b|.]TCa@iʙQ>6@mFc5|.V /ih&3܄#-TAWO=HüſZJt8"N.T?7'2kXW-jß/R6J(/ܶOG +]FwPu1Ss)1ӦI*'KM!!"YrZ4ulpFW%'>I0=3ʞt[>[V(A45]aOdQ&]=I_x d7t3ZZųtlQ_2e_hJRUjݍKو͡R?6Jz#_eJd|cYWsO;5XPMKLu.s6 +ez ٙzǵ @ +pVIo$>6ᴴ%9(S +OX";-fP~)v"63 =TѴM[d_ QL RL=C{Kg␛K: 7wLX4Sۆ4'>?x%yaw?%:Lm*.ϯ9PyRw߷o#e$HQv[]j)2SO5P ki)[O|"Cb&ϕC`ۦo1JR;&qX)8"Q|U?_vK^f*ζKqn{ GgIU[3%FCCLd\P͂O+B1cdɾ͂YFV@ +cϫ(G,VubFONS4DЦ;[F޶h +3pƆB"`Nي1QRE4L8mZ +)OL="̾EX/}@MM¸>{ʮ "읻431͗^[-jŇ1 g2 "0Q]x[!hM#lo^崃UR|]~=? ëPG@#rhLR;J! Lm$"O(0Y IMRV,F̏I,oq7dW?]͎ %5OB;D 8j$9M~nhF.)A +^s#@b emS h\Gl06)\e0v4WN G,tIޛL ϶6i-b̳̙r`VyfH񦔐ŀf+k6c] +MkIIٶv/We̿0e2 +M拣Џ8ћ`fcمi^"zb#8a뚺z;jVe"[QL2S[::P8)v~D0}-T2J43r4C&a/kۏ#0.u]{Aۀ@B=@O(r6f2$amκf1fq;SVLuJ&`%ia Lk5ȯ5Eeg󌘬r^ibPפX="jR(ϬY߉MCN[Vk4e#T<5g:M^LuFA`ZkOXڏyJ?'^*E9FT}. |,5?b~w9@rh$0[زO2I&P2ROU\ҫvj` D7ve g[ALz6yj r"*܅*^_rkWcT΅#XNTIp/\CNHޜ_:ڡ:d Әmlk4q .͘qyuRS+l / SU/ Vc/GxLّݞpꮻ{a?x{ ;sT"&d9ﰊZRI6S?Nό+So仸a5E?ogg eO gw9OthyG\?˜`&1>Cg h!{亟koYIln/6 懑Yg(!Xh[K-n%4c7(0Ma Fx"qFmɊ$=$v&K C$4 >c{/ߏ,7^vRQB z G f-'\7ʇ[vS~ + cY+t[V)$(jI. &AXL|:0{~H-6$LG3_=ދtsf;%| +S ^uDfV a8:76~{ʆz͞n0#Hhj8.22rd ¢KdjhfI3dPEyS؆_u0v̙R_XFuVB1dʗgc\I豯@ֲczr.XQ7GgMn@b#ݼ*$PAv-QDSS;0?ïBe" {0WC==R",ܱ (}ۿnz-B6r1 +;ڨb[;izx*'?̆3ㆡ@h.|gVAs0 pp<NX 3{YPL.{3p@4]`Hl=hi&8䞟Y"[Mڥ񟝪) غbX3anU/<DCQp}PؖZ*+ `ùmU}n‡!JoQpǩO񗩂cas \}1ReEbm9U{8Y{,w{ @@ |'v팧>3:Go3C4t*>AZt+\-h@jS\oaM?.eW9eVJPu맥ǎԜ(4ܥ`d5Ǫ,1=Pf UQVc^j5IRmgkegjBβ*s߳[L_ժ'c~*'ayɌ+l{w"*u;]߰䥵>OPN\9C? ܔ,`~bqk{5Jeh1'& %1|ԔofmLmO-T:)@ MA{'iI_|ӿQq}yqOf3R;jr8HSIJq# ͣr zN,7lA=TìeBX$TNǫ/,gԝ;'U bѳ iʽE"=00pЎ"K> R˷bʋw[Jmm +sfK9G +N*2zTcdJhUpq^9vpfɭ<&? v;vSK!6#'?'mwz2RκK\~*]Nx;`9)G޹.aНK+%ϙtePaeyӋ}I;;)s$%t,'G'N<=(6`b30Q1}iKyU\_h t2K8:h?!v$6E +` +GkdkO8^ze_?ZZ{\-3?ϝ,3KwvJ6YU"kBy1ZPg.F1Q +#o.L,۝hF*4;>+NZc|>jǦ&0nJr lC.}ӏ ''ר"eL#=(Q||Uo{ e8" bR?zqt܇g]~Ꮱ,$j^\ ʋblj_wi:(kZe[Lа3j#(\hg("G&E~訚HX$1n)<1B;f.!>kS렿1BJr]Eߠ7x#䫦wr4\fi:[r .ۗ9/47"pd4=DŽ +:J>|1^ݍ#gn #N7\xywE=#|-؝BGSqV'|ya`b7VVwate4)H/63.¡>:KwL${6cZ^2^|aφyo|6>&wX&TaxpO.ow^fc> GfOd ;!"ǤԪ +ǥid#OʂL4jI‘H֭B魼*_I`>w8L( iD(9Ce}E2UʊZsmp6їDCRkk-] N e"7=Xnwsr&iߛg"HP|W3Cq')ݧVR8dQvݟLKs^80k5߼NAnCsa P͝J i{E)N +9GBWhև6Gn&Ge"%sRYqų>dv. q1Z`m.N/W@*Ft;Bx% .AHN[iG8F CY,j1"h`Ԡ}H1н*aD:gMɧ8-NlX ܣ3%F/ߤvbPO,/ФiOP8vtXo E;=*3ؒU2=ց?n΀x=yUYiYhM>4-|PwUbp՞|]M.~;Ũ£OR[tVC9`G(}뷛p +O&Q.R39&dw-~ժz^pٌGyVf>]La}q +lh?pԍ2ߢ/Z͏k^1u߿q >Jzrsq$KX桰nJz"|\tozXԱږK]*ɽV#_yET쬴M^ iDZ܀Jh((ϓ?@XBm R3{+L.K 9N݂Hrgh[0an^o +*"l[D.ڧ[cƍ~\uu}3Zƣ]$Xۊ%RRAA7^E:LTK6T2ՎoY}V1r4?OEjnC\kƲ2ϒwyb!)3o:7s:/.Cj'Hjw3GqaIÓQgEW$(o4&BN0Ȳ3;碚RRdl,/i&CfVC=Ey: so FsS:=X3?K߳R}Ȋl|W;]JMcޅ] c0hUZt+'[Jv]J@$oۄ4fzaMZFyըDJTZdLbP@ߴgDBx!#E7NPxK?O:rW>vt'/eđ+ܯɪZ !p!eqľHQ/^Q+3}+d2l,[x2ݹGW'fgz:gZV +DKSa^#⍏ ;E*`+]le?i0H- km6ˆ,PXjD"J/(h$^= qz:+gV@ɞ[HKJuk|r2} BJN4ъFy3 (V_h֔ $?-7"5秙mvb]?rqq'>1.mҖIU2)б—tе'Xn!Jln\wS5îc4>G~OsRhz .?YGfX{ 쑅|Ee1LByQ,o&i HtazkYb gZ7>>L'hK50/E|wQ=HF+x?jױs؆ )n/ny9-iJc{~XbQ- @ nΨo>t7wyqYdw4 ֢F(4ob>Rof`_9o}|jE{kj_)hJ̇E§zXQfyr :i" P>.[D,M^a=ZNڄ-2N!'24-8}|Ƹl[CwriGٿ҆L !p'|EwMeu=utQV!pxR }dj2tXa 5x3c0NfO1>vuyߘ7Jݺb6~vqwj4YӈVaD=^5ySJJ)!6~¥ +mz#E:BA=Pीߝh;'ƌgll%!gsvHAyăvGz$[ "r>fҽ;hKFO$+4VchA fݧrADG>܇:ʖF\c|Sh>Wr^2yDd8$?qGm la;aȵzp/56Pxaͪ 5TZn˻NC2a"~3;&-4e`<N.Ł_Ǵn!rfD8Qx%zv.sVI(-_hd'hƧÛ5RSDW>^P9Y "oڎ J# ^ھv ZO~3|ѢP6`+-+h}+<.5*![EN?ۯuVa=tuʃZ7C3GP,e?G/r7%kSc#c=0?A6RM޻Ew/,ƻl7|)Qoě-:Gu9= u!}~kuV:i"-JfmALg#**1.`]V!&œ= Ld4Pp3mCkF>.Kһ<4wA40(dQ\ulȉr N8 n􍓈eqt6೏_J;|^m_`0ޖ宼+yhV8yt752>Jk/8:]fw{dgѯ9v<<‡sQK%q5?>zJRfxS7bXֵ'ݭ$oM\w2M)li5wz`D|ԦPBlK'ΧESg{E]ε34TEE7/’,=ڂ$jCEM/?JJŖ,YӲX@/ы@g% =ޜ8)"Wzb +' Iv %P,wWDDjš!J"Ԋǝ*}Ux ́ ګď: %}#E}T`e\x>dLmE\=IjټƩҐߞHfKpT@s;8B]M֎ ZDv?+p +k7U +-yrL~s5a= UҡVҧNL>U>k(K'8OnBߩX~0wWf*"hs̓dlQӺ3n X *t14=Yy3 ˣs'}or\m,ZzEu0Zb6;T:+WHEN%a6%R5Q!-YhM@K :{EHVUǁv\?Ieix=Fp=,vP=S15Eiuü* UW̫rܥi}"?A2!t|irx9$_ʉ7f:!S~Av'ZR~Yݙ)nx`:&c-x:Jݓ +%!dC63 ݟ̠.;)\g%֗nκNL2[vx)u{0:)un֐9G&pOg9vQDlܧ9z?qVyAI + {FgsfϢeJ>FStiv" L#.%ލmh~F1VښfSh~P k +`\PRPU tQhi= 6iHo+䶆,:`DP'vx>cs9~j 傒b9|U&`%68B,~6.+]*:vn1$$Տc݌þ'!SAi:<S2w Ki.v#8QKZ9f yv瘺0kB)9д} ;ͽz8G(GwAW  ^h )t!{+z3hI,Av!&a8]}۠|!G9%ؙaXi;XEtYtiOgAo #3d2oˬagl 2Ez9JaHz;iJ4f^zaN̳ӹd~7zSч[@DҖZ8^?Yd5@^ٲ0Ԋ׿_)v"D&?db@eO{MV =A|02 k{;in^h 0Cs gBvx +焓8<@ޫQ 78zMmaYB< aJ1ٵVTN=Q{ByUCi/&ņIkY.WuwF0 &Iqq/)@)ܮQV{^WpKja6LƭHWpvLxGq'0TmC`d<}%'Ԩ6~AY!X49S e> j;g1ݓ*`"@z믣(YL3&W5:9wˬ~ S|˃oNף֬ <'*1.I:R9_%t$n?ii1]:ԫ^nYNHbxL9"T<74 +JpcIhJ)Ux4%ΫG4#Hshg|¢pp؅V6J`_2sTT4՗ ( +qi( JvW9W_! F?5z +!.|2@R%KӅM4Tk|LSBG~a>0՗;lrh, =ڗI;z..qR_P uV-yEI|hEd-ԫ(v?7Wʶ3Iy{-*Ѫ+gԣSjŇ*^u`y ҇W'o f쳡oQ9IqmkJhԛ."<7YA-VL9]3}]uQ9+-$f `ⷿmZө:4kIEOS]ωp\BN*6Ͽ${%8F6-%Ä@轣^+O# +0Vqj/>m>{ҹ{Hg"X{%w#$Q6@x! ~x^ŗs$atL1ghp;}*Xkv|reH{B@T3a8l4rhch7E1HZۥ'[u-BTUۂ1(H wPB:r[Sх%ťKU)%[gnp#V=iƗ0eֆ,W|H(,p\XXj }쫸uxP7ɗ&k܏uG~ * %y nˑ/?_o^$"3˽{ҵ'fim9y@<3"7&` ?I֫V4ݷF~0^(w-5'f&-;$@Sy] |?a&1Ǜ ~"VfBKm~PĠI: T it^%w&!8gv`UGlso"nEt ~ǎ<ퟵbJƘ +}{\x>-|hfVgsšn ʄ{#2U gX9j PV4L4mCB\qm` ąL>%J +-$.adST|b+H8$ pyl)˰ .w΅%"%[VtShE>DkkU*tʉ,";gbЇVcwgPϡ 0nV]S(K0Iʹ\ ASXF4$5߸Ѫ)H/D3$/Jki\c~$츓um[ƴnhjĔ4]7ĬG ߩ ;gQP1oMP;ތl<tO_X5L !&w_xoendstream +endobj +1628 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 11 +/LastChar 126 +/Widths 3757 0 R +/BaseFont /XPRUDN+CMR10 +/FontDescriptor 1626 0 R +>> endobj +1626 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /XPRUDN+CMR10 +/ItalicAngle 0 +/StemV 69 +/XHeight 431 +/FontBBox [-251 -250 1009 969] +/Flags 4 +/CharSet (/ff/fi/fl/ffi/exclam/quotedblright/numbersign/dollar/percent/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/semicolon/equal/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/bracketright/circumflex/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z/endash/emdash/tilde) +/FontFile 1627 0 R +>> endobj +3757 0 obj +[583 556 556 833 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 278 500 833 500 833 778 278 389 389 500 778 278 333 278 500 500 500 500 500 500 500 500 500 500 500 278 278 0 778 0 472 778 750 708 722 764 681 653 785 750 361 514 778 625 917 750 778 681 778 736 556 722 750 750 1028 750 750 611 278 0 278 500 0 278 500 556 444 556 444 306 500 556 278 306 528 278 833 556 500 556 528 392 394 389 556 528 722 528 528 444 500 1000 0 500 ] +endobj +1619 0 obj << +/Length1 988 +/Length2 3734 +/Length3 532 +/Length 4423 +/Filter /FlateDecode +>> +stream +xy<[ٷu13Hز-k`FȾgɒ,!PҠ"d oeoْM]<=9z]b&f2P Ad U@"@dLbbX$  5a8*QQP@ @T/ 'rq~)P$CAf8 +#Pww +o"L@qfv>|Xo(@,@ 2k!J7D3GM7N 1$ȿ"(zuq0wvqGL(om0A஀3ӎD#)ܷ@P=CB ɐLl`0H~G--4@X<dRnCH~O+1*t/C8ϓoioaѨe1\>}e5!ka;55^{s>1=0+{haꩆOk,6ߛ BՇYa98FhhRP,Bk;*>6U>OW p + dΎk*V\L7`lVW2i?gA+,nʁ`أBĨAMTi띵A縪nuGOlW{lv3q([{4!_ O m 8SN'17}7o)!XbtJ}͗T2~7qdE*v?g\;-L>RExQ[qay `|s]`8:{jHyhώ{ C<s+aəs]*C+e٬KyR{=Pp=VC+uOuԳ2,%Xfpg{Ö$~6: +2~ s'P$LIF5ڐˇ ({l_2yܠ{'7ތ + m?+yDTZ.UjZ51!iXwwDt5ƤrGةK-{Wxԛ`-9߁0S C69WTgwHYWj%w=j NnJm}'Cucp2]_G~omlޛy(ZDn@1NXsOzGn tr}!Ffs&̪1rLc#`\19:īy/Qo^mҰ4(h˷IPO~P9)ɕ|(#&- K@*sFfjk75sQRGGM͑"ۗ#=( +G&el՟PPL0*4$q0J7}cÒLצ*sq4Nfɧ=vݟ\Q$% *ڴD ÂƔaL3rn]կ{-іەmj|ֆ][nѹc\p@_8/cx6ZO[uɷ/gE+ cH?XlƵ3ND*ٙwMLn7^>T/ yQm½lߓt{C%L^峔$jɯ|*YWۛ|&g|D5ybcʍ~[kΊւw*cGM..s!lx?8C{ ØxCxvGIpIœ:'L֘q;ݕjQ. RinAX6+9ܵ˟aCh5t +\frif {$rJjZʆ غo~u=MxY5r?4b)8JE3W_6 6;TNS +*z18;sW'&cwg36p˹#} +ܶ K޴iX}6IJH}լH<ޚ?e¼<IhƅwBO80JUGv_.2"6p?s4pC;cH4][fd1ݲ-WSǢ<{*HǮYl%Fݶ9*'NCސ/6*mQ 4^uSp B@>Vb^o&Mz%]?˯ G2Ƽ} /vqxSS\Xf4J%I^ha +<ܤ7,o68輊&OD5CIb'ݑ0,bOsendstream +endobj +1620 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 36 +/LastChar 121 +/Widths 3758 0 R +/BaseFont /CUAHJM+CMR12 +/FontDescriptor 1618 0 R +>> endobj +1618 0 obj << +/Ascent 694 +/CapHeight 683 +/Descent -194 +/FontName /CUAHJM+CMR12 +/ItalicAngle 0 +/StemV 65 +/XHeight 431 +/FontBBox [-34 -251 988 750] +/Flags 4 +/CharSet (/dollar/zero/one/two/three/A/B/M/S/T/a/e/m/s/t/y) +/FontFile 1619 0 R +>> endobj +3758 0 obj +[490 0 0 0 0 0 0 0 0 0 0 0 490 490 490 490 0 0 0 0 0 0 0 0 0 0 0 0 0 734 693 0 0 0 0 0 0 0 0 0 0 897 0 0 0 0 0 544 707 0 0 0 0 0 0 0 0 0 0 0 0 490 0 0 0 435 0 0 0 0 0 0 0 816 0 0 0 0 0 386 381 0 0 0 0 517 ] +endobj +1616 0 obj << +/Length1 2015 +/Length2 12128 +/Length3 532 +/Length 13233 +/Filter /FlateDecode +>> +stream +xUX\]hSww [Np$8 ,8w8~1k5ljjb S4] &`gaCpZ$M\v~~v%GS rrrI :[8L\1Lj 3k @7\.@gw9 ;;` +v@bI=r:t`IzX`0Z *`?nvv& }_&v^wts:@@g=q*$jbgm&`iGEh +`abW`?_?X;{9{o '@)y&&^H&n; zYY@W,@H,)xY-r FXv&o!.hnj'<Vs[?{&`+ .h7ypXo!pmGp[bgbzAoo{z=Z9] r0k2.7e]ߦ Vu[9ہ^Lֆ].ނjbo$F*o.!FNHx}~#pi7w@ro]F`7(EvF`7||#]F`7hE.:&mjlbf to;w ۾mFx?BpA˿`c3jrק /1@Ot%VƳe nZvB“hKۀ_K攻Hyc2"R0~5aڴ*jL\"U227*)ͦ\Z<jE}롹a5ғԥs%c Q av 4 ~-+ccbz,WŸtf3lmRϨدi: P,uvYr(e-9]4]J1}pm˸ڀ˂B۬'L;J)qu(XdB ݧQi +BĽ]u-hCH֏>t ` [B1*Q!uӑai"T~&Osp%0>"}pʱJ."w^taT ~Ǎ.$,BEfejS$3P 8UeIzn鎧(fvغ<+{"QuYjc>﬿]PmDIWxY7! ecexIAz38kH?%Wڣ)eBx)%]n_hmXJa /u.[՗֏L}#ĕ5$Hu(|2q^ݬvҠ֐Ԍ8kV/)_ik~ /[_GH%NWU[rYs甃DkO{ծ(ғVy" #Z0<ɭBKvnSYJJmy= ݇aT75aŰep~|c wag3V)`McMP>پ75IU,eH$,~ M,((&vSNB|4 )O Ss %VC*[it\향q``*weTt0$>h+vt R3?wOnydY[1jUf1 $Y`r+P{C{ipK6<|}+R"8WXOJ_~%ũ=,k4N2V5aQϨ5r;/E?xqп;]e;;8 @0E};u25@ƿv8{1ftrٰpA `(,)H8é:a!'h)᮸7YɅ$:loC#nǍ;dCy+%udDZջ&ZɑuŧQTAfe6i*&wQ_G~jbj8 YMz\J}[17n֦ODR HF3O,fIr{A&tܤqfӉj>g V Gxb:MW# ǃbh*sjdFܘTOڦsCbFDXq䏘{\Sg'QPUTKq?N`< +H"8BZmTHE2_c΅~sDR_tb#9K RxC$jM"IH*x|2obrr(8΁-oMS5c rNGghZz#C"2[lAӕ)KHt*,LHS1gg"Ê?ĭH RZDLlBԹ_] +m7:UWtZr2` ^Gc+V~CiV+k7,e4~e]Ó==r=xrn9 WeB.z{#QP`RW ۵@%Oksb4E)f| Pu$V BI4y[  +(mq?8Y# +ӌ 2"rsYەʳn_KU$6cL=U,DC_=rGogS.LT8h,[{[ d%n$(0)uo0G_?@RQmv5SZ^!ɹW1 +-k,~/]/Ѷ}L"JGҰ/xZzǯh!= KwA)]iiplrLICGLKr>~V%|ڧ,Ɠ-xegecH_l䍉XBn.=q,oE/Bwjvr2hH=Ḁ3_5䨟6D}w5$tUVRK'g'E [D$L`~2?%{;]Bn *sOz)Tz^_TkUԗ-M_lNXTgɶ?rk'rȎeql}d>d!sA\~ԜEtDm/I@M ޾.0V}%/IXjzz<貯Ǟ!~-O^zya}È $&pB\z E/ N@Ydf{C$ȞQ䒤GW~7e{Fn*D26ͬVV$<A#݅k,?-,d{?Ea ol)ObtvOFnm(F8k"%쯫{GᄊCD(=#146Ѭ}'s6"p189.x<ݷxIY8=)lnpN;n.['1Y Ty(ǭR.pyhik'o8{H]UTY/aXhdET\F۱ i~ owf`0UxM٨XR./K45@+y,kD Ye =2RSRqHǔ=@Ϣ|jV`9Nj2lWTz^BQº*4_ Za]"Zx#yUP:SI)yzJ͉N)i=WŢOKf3KgRnuP2Oىzz2͔u2!+ #urנ,ױ%p!DŽ%7cGĜ(VR2zD 塜HhJO5ģ5'f=Lkn3Ć&tgChK-'aq3nt#OP f/4kYذF0 g͐h$}|Fzj{$sqU2gkOU8ѝC+8Bբgր8|R$ɓ .+C?a5BC~:'le<e \'OH\`(eޣE{],dHZ/V_iZ={CIdutX/+MtzJ3bbYywNsKwb}Mmc=w7%Uv߱(}|lҪeHxxD{鍒ċKSѠP.ƯwN"Vo{i-LC]Rf 3JI2`". zi{O|kmH[<іuȍc](o?qƛ9٧P<&<#kgՖC4Vw$"". ZeyJ"Af'?^A>ۋ&Y!3m*A6xŸ'v܅l5zk (-|m<ڬVf6" &Z :m8֏KVSxL&9ʹ2S:A9=䬂z +$]xzVB&Ax[,> +H3!yZ:csU *(V ʏ.>IfUP氆؃V\2L P%ᑧNj}lT'k a۵5:t~Ufs{LP] U ñnxkm|K1GwF͗5Ƨ^M:&t.P[ZsgUTW!5Ԛs⇿i|LŚ;F*lcX("@r _v>|F"4ơ67?YF/]C~_BJŠfຠp< +w0Qm|8sK̍A2@5M;oV_7˘.W)Sbd2:YI5"S+f?gHn6.8(hīc^njAqh۱b3A>;Bʻ|C瑩FMuj +B>y81[o^1~Vyq?]ھ6I*wwl!(|8Wp(۔@ٶu8ƺ»7>2WHGg->|N+hv5K-0ұ{g[A0pHw@eML;&FA։w!nyO9R*SsXk(v Oް/YCLf̮ԙ?Ub+_&EZO:Ie2KX,Ta_ ]y|[>,׌?Ha2,vq25D;zG%KD}zhvNҥMFݻ񄂟,VIKFF2: *]3"}I, %LVh:l,ƟRg]2_wxdi˯xhc&F?Mx8[\?GXO%R4?pk7w̾sSPIjsStfA*O q>yVyg_6_pRdۓz_W y{7NՌ]^k +~Vr$A/}s㍟\X$Tm#*6VݡX6qMb4 "셓],ɈB.v,s䣫ڮD&ܧ +mJyrrTHh6z1|#$x2lOu])` ` FF1Gl`8Bc|z^7ɔSqSYC%oCq v^!wϴ;lMPmVʗM9 /QX q7[8kJ!Hmd1޳fT8ՠ}z 3Я׺ _ JɕŠ;$nO(}ڻ!.ڹZM}YGn#KT㣱)l_5 +7B &]M400]BYH#9.O[IoEIqg֩jI?v* +BqQeyqIK|_tw搙KkC;ZmZ,cR㾚W8 ".QICJsy$\u}~6s!E)#fE!Pz; -ҁ\ q_p!"WǝUI! !57;;~F3#^Οr_sĤo Qa4j!=Ot0Û)JZLil`EnvSS{!}iuj/la^T-H"xcD7+-ʹDr%FVRSxUwFG .u,)Ңoc9' "B|I)+ +{vj'#M1qH~EҶ +#ι̚QC ;2z6n[baݨ7ƗGCM",7k}sP`\o"Kqڧ4ʎX~ԪLlU'G%ɘPjݗjʐ[2mX輞 g -[DZ{/?C\6 !b+ٍ+>]=鞉FN}xݧj +ѼP=\ ij7h^ =ÕT}FAt.kt+$6Dd !)G*. +AQEH%.Qs.ᑞH[_#Q aFғ+!娠;lbEꢏ>$]|9D@`齱Y3ek`-'(eܬaC 8(s G$rxǘ'ɭ$HivU%rDҾM_Q;PbDVF+&Qd\>b`@h%.PvN_bdaڵLQTi)%~*y{> eK4F.U6q|@)L-›t%ü7_]k* +ZD-Q$hyv(?fl1~i.Mzg%ҙHwm^ k +gQr`fM`Z= % d8He妢Ye'f%*|pzϓ 'k̉`':{vc\.mKk7)%alRobUGs؏xhSJ/ɐ<<iuaIۨ)SzRr#7>֞phrXj< j |XwXcw/Fsn=rˬ1HC9R&5j)$ JJ~3cMk 4O$d?VcJOg̙q`(pxcs}U1XKɊ:ngɟ*M jϡ9g՟'\o(;6ˢEB#K3sj>; Iė#ĚH3`nxIq_-gCt +%-e:lН8b|2-䮑zqh9L"aMo-vL-[9=R*w^X݆(w`\SYIɪNiŽpi`) +} #q]r +oI}f_ynv + +\v .7DxۤB$4t70Qj6"$~@*Y!>;Tw' +Z`Rң#FZ2trܱWbsQ W;ƾyO2R_huwf_T*"iuk\Mi/PNPӴ'>D/A(37*e|s\3@C Ht[ dS)mGd*lWGE7_:=s7A e3Th1(M0g3)"o5ثt6E;i$I!;[h=5 S܏/DEtÏEĭTz J}]-ҿ%֩cvݩg{aܞ{7Aϭ6mCx~yy|RđhC/hܷ6gIh +1L®¥Ya{; /ȔENdaKbӯ -j'z3sw8=j>)m ogU:J9Q /z)C2l 쌻Ij§Jt\"%Ͽ -hg?kD-Xr83he蝩A1ɼ{$oM1ì9igzQAڼ>gN+e)KMI"*ۻm/a;^-[MNWL֭ŝrsOG_S~V{ц +b+-Sp]XK9>^tㄢs> ̅bZ_4K[o"Aͽ @V%>U /ic{99UUQgm"ǚm;8&ԝ/CߋdS=lD~ cxhhxxܼ6Q/[EB9y5{3gQ_j:$?m8s SrB~qoS(,'XK/%Cs@&B!̩9/+)9D%Iaϗe.~UP AjiL9Ôڄ +PQ#OX;V.}[jUJZ0ątL%IwZ O{ҦcNp\8 nW$舙1Lf3ζ}JwwWmDēRoll1˩.uKcqawXSE+%ұ;%g86FoWz&ܡ%qf|Bmߝ$9,wdv)A׉u=tMH2tNq p RIť 4y1N +UN˟ߏ?ikw76z;> +<(B*7'Ҩn&؇~wE"c7ȸՂ:j{/i7&9g'L\2`>j!):v6WTS뜤X.rJVR0_-E&u;{SELpU{j!buBr3˳'fE_8X"EmWoLtT5{'7$;%z@.'Giў(j7a?*уg4ecZҤe5=J)e6 bk gu_k9s^8Bܗӌq%㇖*6y,I*%rj\f\\FͻeijzEgfgzm)\^ZAP•"k~{ve#Z X")E~&8|f+N5RߴaAsCM?Lr7p{T[x .pf|Bq3 WR*s(=G<[xΙ挨ߢAv5H8Ц0Oʗi2*|%ח^ șbVJߋQբDڢ#8db؉z"_9:2ICN/ &t8ՅF]Lhz)R5Ǵz e`l&8.Q2Ids)bCF!&\:}zy}fwj#!UO>q49ih]tއ{$K_j_O_puEu#z қ^]44jH .u ';~mJCU=m ӧZ'ΥK}s %h%|*7݊ʿ7UV3@4?EQ0X}"[o&ٗk-eoW{~n[~;t z #U?:4τ/*0[YZf= +^0(,3[c%HلDl;B0BjReُ_dcزDۇ^͟^WeUM<0iKCTx2r>y26|55c W?\Bu)Grbt ˱\ a(0M9])YRt'j?U :j3Xc3 a^z’yhcӽmb}րC:IbQ^8QF6M.%qS!䵯T¶Mo8;8uwMOZ00mjy _HMIAY|_5Tvz? } .0 ,53\B.[TEkv>i +!k2WB`nE-%K0w.v8 2r]Cf#O.[$zf[-NA~ѣIt;bMn{+yBS7ۑH%v=DO^*ھ{^OLKУI!,9{:pYE|*DY~Cx >RT7% dB=8;(ϕ8W(#Ug:h/8)hb`4[VS![8K"Eb+ 4oR Z'mJM*Cba0&DڪoIQ7 krcxN"^YG/;ɆMA"\ɽ!:?vZ C_1dol>sendstream +endobj +1617 0 obj << +/Type /Font +/Subtype /Type1 +/Encoding 3743 0 R +/FirstChar 11 +/LastChar 122 +/Widths 3759 0 R +/BaseFont /KEMIEU+CMSSBX10 +/FontDescriptor 1615 0 R +>> endobj +1615 0 obj << +/Ascent 694 +/CapHeight 694 +/Descent -194 +/FontName /KEMIEU+CMSSBX10 +/ItalicAngle 0 +/StemV 136 +/XHeight 458 +/FontBBox [-71 -250 1099 780] +/Flags 4 +/CharSet (/ff/fi/fl/exclam/quotedblright/dollar/quoteright/parenleft/parenright/comma/hyphen/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon/equal/question/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O/P/Q/R/S/T/U/V/W/X/Y/bracketleft/bracketright/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y/z) +/FontFile 1616 0 R +>> endobj +3759 0 obj +[642 586 586 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 367 558 0 550 0 0 306 428 428 0 0 306 367 306 550 550 550 550 550 550 550 550 550 550 550 306 0 0 856 0 519 0 733 733 703 794 642 611 733 794 331 519 764 581 978 794 794 703 794 703 611 733 764 733 1039 733 733 0 343 0 343 0 0 0 525 561 489 561 511 336 550 561 256 286 531 256 867 561 550 561 561 372 422 404 561 500 744 500 500 476 ] +endobj +1621 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [1610 0 R 1623 0 R 1637 0 R 1645 0 R 1684 0 R 1730 0 R] +>> endobj +1836 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [1784 0 R 1838 0 R 1887 0 R 1938 0 R 1988 0 R 2038 0 R] +>> endobj +2090 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [2087 0 R 2092 0 R 2106 0 R 2111 0 R 2119 0 R 2135 0 R] +>> endobj +2162 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [2149 0 R 2166 0 R 2170 0 R 2178 0 R 2184 0 R 2195 0 R] +>> endobj +2217 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [2213 0 R 2219 0 R 2228 0 R 2235 0 R 2243 0 R 2249 0 R] +>> endobj +2260 0 obj << +/Type /Pages +/Count 6 +/Parent 3760 0 R +/Kids [2255 0 R 2263 0 R 2270 0 R 2280 0 R 2287 0 R 2299 0 R] +>> endobj +2311 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2303 0 R 2313 0 R 2321 0 R 2327 0 R 2334 0 R 2346 0 R] +>> endobj +2360 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2351 0 R 2362 0 R 2371 0 R 2375 0 R 2382 0 R 2387 0 R] +>> endobj +2396 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2392 0 R 2398 0 R 2406 0 R 2414 0 R 2424 0 R 2429 0 R] +>> endobj +2445 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2438 0 R 2447 0 R 2452 0 R 2458 0 R 2464 0 R 2468 0 R] +>> endobj +2478 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2472 0 R 2480 0 R 2486 0 R 2490 0 R 2497 0 R 2512 0 R] +>> endobj +2529 0 obj << +/Type /Pages +/Count 6 +/Parent 3761 0 R +/Kids [2524 0 R 2531 0 R 2546 0 R 2553 0 R 2558 0 R 2567 0 R] +>> endobj +2577 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2574 0 R 2579 0 R 2586 0 R 2594 0 R 2601 0 R 2607 0 R] +>> endobj +2619 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2616 0 R 2621 0 R 2629 0 R 2633 0 R 2643 0 R 2653 0 R] +>> endobj +2664 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2659 0 R 2666 0 R 2675 0 R 2684 0 R 2691 0 R 2697 0 R] +>> endobj +2715 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2702 0 R 2717 0 R 2723 0 R 2730 0 R 2738 0 R 2743 0 R] +>> endobj +2750 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2747 0 R 2752 0 R 2757 0 R 2763 0 R 2774 0 R 2779 0 R] +>> endobj +2787 0 obj << +/Type /Pages +/Count 6 +/Parent 3762 0 R +/Kids [2783 0 R 2789 0 R 2793 0 R 2797 0 R 2801 0 R 2805 0 R] +>> endobj +2812 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [2809 0 R 2814 0 R 2823 0 R 2832 0 R 2839 0 R 2843 0 R] +>> endobj +2852 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [2849 0 R 2854 0 R 2858 0 R 2863 0 R 2868 0 R 2872 0 R] +>> endobj +2885 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [2879 0 R 2887 0 R 2894 0 R 2903 0 R 2913 0 R 2920 0 R] +>> endobj +2930 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [2927 0 R 2932 0 R 2939 0 R 2947 0 R 2956 0 R 2960 0 R] +>> endobj +2971 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [2966 0 R 2973 0 R 2984 0 R 2996 0 R 3002 0 R 3007 0 R] +>> endobj +3018 0 obj << +/Type /Pages +/Count 6 +/Parent 3763 0 R +/Kids [3011 0 R 3020 0 R 3027 0 R 3036 0 R 3042 0 R 3057 0 R] +>> endobj +3071 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3065 0 R 3073 0 R 3081 0 R 3089 0 R 3097 0 R 3101 0 R] +>> endobj +3111 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3105 0 R 3113 0 R 3122 0 R 3129 0 R 3138 0 R 3142 0 R] +>> endobj +3150 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3147 0 R 3152 0 R 3156 0 R 3162 0 R 3171 0 R 3176 0 R] +>> endobj +3185 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3182 0 R 3187 0 R 3194 0 R 3199 0 R 3205 0 R 3212 0 R] +>> endobj +3229 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3221 0 R 3231 0 R 3240 0 R 3250 0 R 3255 0 R 3261 0 R] +>> endobj +3272 0 obj << +/Type /Pages +/Count 6 +/Parent 3764 0 R +/Kids [3267 0 R 3274 0 R 3279 0 R 3285 0 R 3289 0 R 3296 0 R] +>> endobj +3306 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3300 0 R 3308 0 R 3315 0 R 3321 0 R 3330 0 R 3337 0 R] +>> endobj +3348 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3344 0 R 3350 0 R 3354 0 R 3359 0 R 3365 0 R 3377 0 R] +>> endobj +3387 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3381 0 R 3389 0 R 3397 0 R 3402 0 R 3415 0 R 3426 0 R] +>> endobj +3439 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3432 0 R 3441 0 R 3453 0 R 3463 0 R 3474 0 R 3481 0 R] +>> endobj +3501 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3485 0 R 3503 0 R 3515 0 R 3521 0 R 3529 0 R 3534 0 R] +>> endobj +3544 0 obj << +/Type /Pages +/Count 6 +/Parent 3765 0 R +/Kids [3538 0 R 3546 0 R 3551 0 R 3557 0 R 3581 0 R 3592 0 R] +>> endobj +3601 0 obj << +/Type /Pages +/Count 6 +/Parent 3766 0 R +/Kids [3598 0 R 3603 0 R 3611 0 R 3616 0 R 3624 0 R 3638 0 R] +>> endobj +3661 0 obj << +/Type /Pages +/Count 6 +/Parent 3766 0 R +/Kids [3651 0 R 3663 0 R 3675 0 R 3681 0 R 3688 0 R 3693 0 R] +>> endobj +3708 0 obj << +/Type /Pages +/Count 5 +/Parent 3766 0 R +/Kids [3700 0 R 3710 0 R 3715 0 R 3723 0 R 3732 0 R] +>> endobj +3760 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [1621 0 R 1836 0 R 2090 0 R 2162 0 R 2217 0 R 2260 0 R] +>> endobj +3761 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [2311 0 R 2360 0 R 2396 0 R 2445 0 R 2478 0 R 2529 0 R] +>> endobj +3762 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [2577 0 R 2619 0 R 2664 0 R 2715 0 R 2750 0 R 2787 0 R] +>> endobj +3763 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [2812 0 R 2852 0 R 2885 0 R 2930 0 R 2971 0 R 3018 0 R] +>> endobj +3764 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [3071 0 R 3111 0 R 3150 0 R 3185 0 R 3229 0 R 3272 0 R] +>> endobj +3765 0 obj << +/Type /Pages +/Count 36 +/Parent 3767 0 R +/Kids [3306 0 R 3348 0 R 3387 0 R 3439 0 R 3501 0 R 3544 0 R] +>> endobj +3766 0 obj << +/Type /Pages +/Count 17 +/Parent 3768 0 R +/Kids [3601 0 R 3661 0 R 3708 0 R] +>> endobj +3767 0 obj << +/Type /Pages +/Count 216 +/Parent 3769 0 R +/Kids [3760 0 R 3761 0 R 3762 0 R 3763 0 R 3764 0 R 3765 0 R] +>> endobj +3768 0 obj << +/Type /Pages +/Count 17 +/Parent 3769 0 R +/Kids [3766 0 R] +>> endobj +3769 0 obj << +/Type /Pages +/Count 233 +/Kids [3767 0 R 3768 0 R] +>> endobj +3770 0 obj << +/Type /Outlines +/First 7 0 R +/Last 1299 0 R +/Count 5 +>> endobj +1607 0 obj << +/Title 1608 0 R +/A 1605 0 R +/Parent 1571 0 R +/Prev 1603 0 R +>> endobj +1603 0 obj << +/Title 1604 0 R +/A 1601 0 R +/Parent 1571 0 R +/Prev 1599 0 R +/Next 1607 0 R +>> endobj +1599 0 obj << +/Title 1600 0 R +/A 1597 0 R +/Parent 1571 0 R +/Prev 1595 0 R +/Next 1603 0 R +>> endobj +1595 0 obj << +/Title 1596 0 R +/A 1593 0 R +/Parent 1571 0 R +/Prev 1591 0 R +/Next 1599 0 R +>> endobj +1591 0 obj << +/Title 1592 0 R +/A 1589 0 R +/Parent 1571 0 R +/Prev 1587 0 R +/Next 1595 0 R +>> endobj +1587 0 obj << +/Title 1588 0 R +/A 1585 0 R +/Parent 1571 0 R +/Prev 1583 0 R +/Next 1591 0 R +>> endobj +1583 0 obj << +/Title 1584 0 R +/A 1581 0 R +/Parent 1571 0 R +/Prev 1579 0 R +/Next 1587 0 R +>> endobj +1579 0 obj << +/Title 1580 0 R +/A 1577 0 R +/Parent 1571 0 R +/Prev 1575 0 R +/Next 1583 0 R +>> endobj +1575 0 obj << +/Title 1576 0 R +/A 1573 0 R +/Parent 1571 0 R +/Next 1579 0 R +>> endobj +1571 0 obj << +/Title 1572 0 R +/A 1569 0 R +/Parent 1299 0 R +/Prev 1523 0 R +/First 1575 0 R +/Last 1607 0 R +/Count -9 +>> endobj +1567 0 obj << +/Title 1568 0 R +/A 1565 0 R +/Parent 1527 0 R +/Prev 1563 0 R +>> endobj +1563 0 obj << +/Title 1564 0 R +/A 1561 0 R +/Parent 1527 0 R +/Prev 1559 0 R +/Next 1567 0 R +>> endobj +1559 0 obj << +/Title 1560 0 R +/A 1557 0 R +/Parent 1527 0 R +/Prev 1555 0 R +/Next 1563 0 R +>> endobj +1555 0 obj << +/Title 1556 0 R +/A 1553 0 R +/Parent 1527 0 R +/Prev 1551 0 R +/Next 1559 0 R +>> endobj +1551 0 obj << +/Title 1552 0 R +/A 1549 0 R +/Parent 1527 0 R +/Prev 1547 0 R +/Next 1555 0 R +>> endobj +1547 0 obj << +/Title 1548 0 R +/A 1545 0 R +/Parent 1527 0 R +/Prev 1543 0 R +/Next 1551 0 R +>> endobj +1543 0 obj << +/Title 1544 0 R +/A 1541 0 R +/Parent 1527 0 R +/Prev 1539 0 R +/Next 1547 0 R +>> endobj +1539 0 obj << +/Title 1540 0 R +/A 1537 0 R +/Parent 1527 0 R +/Prev 1535 0 R +/Next 1543 0 R +>> endobj +1535 0 obj << +/Title 1536 0 R +/A 1533 0 R +/Parent 1527 0 R +/Prev 1531 0 R +/Next 1539 0 R +>> endobj +1531 0 obj << +/Title 1532 0 R +/A 1529 0 R +/Parent 1527 0 R +/Next 1535 0 R +>> endobj +1527 0 obj << +/Title 1528 0 R +/A 1525 0 R +/Parent 1523 0 R +/First 1531 0 R +/Last 1567 0 R +/Count -10 +>> endobj +1523 0 obj << +/Title 1524 0 R +/A 1521 0 R +/Parent 1299 0 R +/Prev 1451 0 R +/Next 1571 0 R +/First 1527 0 R +/Last 1527 0 R +/Count -1 +>> endobj +1519 0 obj << +/Title 1520 0 R +/A 1517 0 R +/Parent 1451 0 R +/Prev 1515 0 R +>> endobj +1515 0 obj << +/Title 1516 0 R +/A 1513 0 R +/Parent 1451 0 R +/Prev 1507 0 R +/Next 1519 0 R +>> endobj +1511 0 obj << +/Title 1512 0 R +/A 1509 0 R +/Parent 1507 0 R +>> endobj +1507 0 obj << +/Title 1508 0 R +/A 1505 0 R +/Parent 1451 0 R +/Prev 1479 0 R +/Next 1515 0 R +/First 1511 0 R +/Last 1511 0 R +/Count -1 +>> endobj +1503 0 obj << +/Title 1504 0 R +/A 1501 0 R +/Parent 1479 0 R +/Prev 1499 0 R +>> endobj +1499 0 obj << +/Title 1500 0 R +/A 1497 0 R +/Parent 1479 0 R +/Prev 1495 0 R +/Next 1503 0 R +>> endobj +1495 0 obj << +/Title 1496 0 R +/A 1493 0 R +/Parent 1479 0 R +/Prev 1491 0 R +/Next 1499 0 R +>> endobj +1491 0 obj << +/Title 1492 0 R +/A 1489 0 R +/Parent 1479 0 R +/Prev 1487 0 R +/Next 1495 0 R +>> endobj +1487 0 obj << +/Title 1488 0 R +/A 1485 0 R +/Parent 1479 0 R +/Prev 1483 0 R +/Next 1491 0 R +>> endobj +1483 0 obj << +/Title 1484 0 R +/A 1481 0 R +/Parent 1479 0 R +/Next 1487 0 R +>> endobj +1479 0 obj << +/Title 1480 0 R +/A 1477 0 R +/Parent 1451 0 R +/Prev 1459 0 R +/Next 1507 0 R +/First 1483 0 R +/Last 1503 0 R +/Count -6 +>> endobj +1475 0 obj << +/Title 1476 0 R +/A 1473 0 R +/Parent 1459 0 R +/Prev 1471 0 R +>> endobj +1471 0 obj << +/Title 1472 0 R +/A 1469 0 R +/Parent 1459 0 R +/Prev 1467 0 R +/Next 1475 0 R +>> endobj +1467 0 obj << +/Title 1468 0 R +/A 1465 0 R +/Parent 1459 0 R +/Prev 1463 0 R +/Next 1471 0 R +>> endobj +1463 0 obj << +/Title 1464 0 R +/A 1461 0 R +/Parent 1459 0 R +/Next 1467 0 R +>> endobj +1459 0 obj << +/Title 1460 0 R +/A 1457 0 R +/Parent 1451 0 R +/Prev 1455 0 R +/Next 1479 0 R +/First 1463 0 R +/Last 1475 0 R +/Count -4 +>> endobj +1455 0 obj << +/Title 1456 0 R +/A 1453 0 R +/Parent 1451 0 R +/Next 1459 0 R +>> endobj +1451 0 obj << +/Title 1452 0 R +/A 1449 0 R +/Parent 1299 0 R +/Prev 1411 0 R +/Next 1523 0 R +/First 1455 0 R +/Last 1519 0 R +/Count -6 +>> endobj +1447 0 obj << +/Title 1448 0 R +/A 1445 0 R +/Parent 1439 0 R +/Prev 1443 0 R +>> endobj +1443 0 obj << +/Title 1444 0 R +/A 1441 0 R +/Parent 1439 0 R +/Next 1447 0 R +>> endobj +1439 0 obj << +/Title 1440 0 R +/A 1437 0 R +/Parent 1411 0 R +/Prev 1431 0 R +/First 1443 0 R +/Last 1447 0 R +/Count -2 +>> endobj +1435 0 obj << +/Title 1436 0 R +/A 1433 0 R +/Parent 1431 0 R +>> endobj +1431 0 obj << +/Title 1432 0 R +/A 1429 0 R +/Parent 1411 0 R +/Prev 1427 0 R +/Next 1439 0 R +/First 1435 0 R +/Last 1435 0 R +/Count -1 +>> endobj +1427 0 obj << +/Title 1428 0 R +/A 1425 0 R +/Parent 1411 0 R +/Prev 1423 0 R +/Next 1431 0 R +>> endobj +1423 0 obj << +/Title 1424 0 R +/A 1421 0 R +/Parent 1411 0 R +/Prev 1419 0 R +/Next 1427 0 R +>> endobj +1419 0 obj << +/Title 1420 0 R +/A 1417 0 R +/Parent 1411 0 R +/Prev 1415 0 R +/Next 1423 0 R +>> endobj +1415 0 obj << +/Title 1416 0 R +/A 1413 0 R +/Parent 1411 0 R +/Next 1419 0 R +>> endobj +1411 0 obj << +/Title 1412 0 R +/A 1409 0 R +/Parent 1299 0 R +/Prev 1363 0 R +/Next 1451 0 R +/First 1415 0 R +/Last 1439 0 R +/Count -6 +>> endobj +1407 0 obj << +/Title 1408 0 R +/A 1405 0 R +/Parent 1399 0 R +/Prev 1403 0 R +>> endobj +1403 0 obj << +/Title 1404 0 R +/A 1401 0 R +/Parent 1399 0 R +/Next 1407 0 R +>> endobj +1399 0 obj << +/Title 1400 0 R +/A 1397 0 R +/Parent 1363 0 R +/Prev 1367 0 R +/First 1403 0 R +/Last 1407 0 R +/Count -2 +>> endobj +1395 0 obj << +/Title 1396 0 R +/A 1393 0 R +/Parent 1367 0 R +/Prev 1371 0 R +>> endobj +1391 0 obj << +/Title 1392 0 R +/A 1389 0 R +/Parent 1371 0 R +/Prev 1387 0 R +>> endobj +1387 0 obj << +/Title 1388 0 R +/A 1385 0 R +/Parent 1371 0 R +/Prev 1383 0 R +/Next 1391 0 R +>> endobj +1383 0 obj << +/Title 1384 0 R +/A 1381 0 R +/Parent 1371 0 R +/Prev 1379 0 R +/Next 1387 0 R +>> endobj +1379 0 obj << +/Title 1380 0 R +/A 1377 0 R +/Parent 1371 0 R +/Prev 1375 0 R +/Next 1383 0 R +>> endobj +1375 0 obj << +/Title 1376 0 R +/A 1373 0 R +/Parent 1371 0 R +/Next 1379 0 R +>> endobj +1371 0 obj << +/Title 1372 0 R +/A 1369 0 R +/Parent 1367 0 R +/Next 1395 0 R +/First 1375 0 R +/Last 1391 0 R +/Count -5 +>> endobj +1367 0 obj << +/Title 1368 0 R +/A 1365 0 R +/Parent 1363 0 R +/Next 1399 0 R +/First 1371 0 R +/Last 1395 0 R +/Count -2 +>> endobj +1363 0 obj << +/Title 1364 0 R +/A 1361 0 R +/Parent 1299 0 R +/Prev 1303 0 R +/Next 1411 0 R +/First 1367 0 R +/Last 1399 0 R +/Count -2 +>> endobj +1359 0 obj << +/Title 1360 0 R +/A 1357 0 R +/Parent 1351 0 R +/Prev 1355 0 R +>> endobj +1355 0 obj << +/Title 1356 0 R +/A 1353 0 R +/Parent 1351 0 R +/Next 1359 0 R +>> endobj +1351 0 obj << +/Title 1352 0 R +/A 1349 0 R +/Parent 1303 0 R +/Prev 1335 0 R +/First 1355 0 R +/Last 1359 0 R +/Count -2 +>> endobj +1347 0 obj << +/Title 1348 0 R +/A 1345 0 R +/Parent 1339 0 R +/Prev 1343 0 R +>> endobj +1343 0 obj << +/Title 1344 0 R +/A 1341 0 R +/Parent 1339 0 R +/Next 1347 0 R +>> endobj +1339 0 obj << +/Title 1340 0 R +/A 1337 0 R +/Parent 1335 0 R +/First 1343 0 R +/Last 1347 0 R +/Count -2 +>> endobj +1335 0 obj << +/Title 1336 0 R +/A 1333 0 R +/Parent 1303 0 R +/Prev 1331 0 R +/Next 1351 0 R +/First 1339 0 R +/Last 1339 0 R +/Count -1 +>> endobj +1331 0 obj << +/Title 1332 0 R +/A 1329 0 R +/Parent 1303 0 R +/Prev 1327 0 R +/Next 1335 0 R +>> endobj +1327 0 obj << +/Title 1328 0 R +/A 1325 0 R +/Parent 1303 0 R +/Prev 1307 0 R +/Next 1331 0 R +>> endobj +1323 0 obj << +/Title 1324 0 R +/A 1321 0 R +/Parent 1315 0 R +/Prev 1319 0 R +>> endobj +1319 0 obj << +/Title 1320 0 R +/A 1317 0 R +/Parent 1315 0 R +/Next 1323 0 R +>> endobj +1315 0 obj << +/Title 1316 0 R +/A 1313 0 R +/Parent 1307 0 R +/Prev 1311 0 R +/First 1319 0 R +/Last 1323 0 R +/Count -2 +>> endobj +1311 0 obj << +/Title 1312 0 R +/A 1309 0 R +/Parent 1307 0 R +/Next 1315 0 R +>> endobj +1307 0 obj << +/Title 1308 0 R +/A 1305 0 R +/Parent 1303 0 R +/Next 1327 0 R +/First 1311 0 R +/Last 1315 0 R +/Count -2 +>> endobj +1303 0 obj << +/Title 1304 0 R +/A 1301 0 R +/Parent 1299 0 R +/Next 1363 0 R +/First 1307 0 R +/Last 1351 0 R +/Count -5 +>> endobj +1299 0 obj << +/Title 1300 0 R +/A 1297 0 R +/Parent 3770 0 R +/Prev 1223 0 R +/First 1303 0 R +/Last 1571 0 R +/Count -6 +>> endobj +1295 0 obj << +/Title 1296 0 R +/A 1293 0 R +/Parent 1271 0 R +/Prev 1291 0 R +>> endobj +1291 0 obj << +/Title 1292 0 R +/A 1289 0 R +/Parent 1271 0 R +/Prev 1287 0 R +/Next 1295 0 R +>> endobj +1287 0 obj << +/Title 1288 0 R +/A 1285 0 R +/Parent 1271 0 R +/Prev 1283 0 R +/Next 1291 0 R +>> endobj +1283 0 obj << +/Title 1284 0 R +/A 1281 0 R +/Parent 1271 0 R +/Prev 1279 0 R +/Next 1287 0 R +>> endobj +1279 0 obj << +/Title 1280 0 R +/A 1277 0 R +/Parent 1271 0 R +/Prev 1275 0 R +/Next 1283 0 R +>> endobj +1275 0 obj << +/Title 1276 0 R +/A 1273 0 R +/Parent 1271 0 R +/Next 1279 0 R +>> endobj +1271 0 obj << +/Title 1272 0 R +/A 1269 0 R +/Parent 1223 0 R +/Prev 1247 0 R +/First 1275 0 R +/Last 1295 0 R +/Count -6 +>> endobj +1267 0 obj << +/Title 1268 0 R +/A 1265 0 R +/Parent 1247 0 R +/Prev 1263 0 R +>> endobj +1263 0 obj << +/Title 1264 0 R +/A 1261 0 R +/Parent 1247 0 R +/Prev 1259 0 R +/Next 1267 0 R +>> endobj +1259 0 obj << +/Title 1260 0 R +/A 1257 0 R +/Parent 1247 0 R +/Prev 1255 0 R +/Next 1263 0 R +>> endobj +1255 0 obj << +/Title 1256 0 R +/A 1253 0 R +/Parent 1247 0 R +/Prev 1251 0 R +/Next 1259 0 R +>> endobj +1251 0 obj << +/Title 1252 0 R +/A 1249 0 R +/Parent 1247 0 R +/Next 1255 0 R +>> endobj +1247 0 obj << +/Title 1248 0 R +/A 1245 0 R +/Parent 1223 0 R +/Prev 1227 0 R +/Next 1271 0 R +/First 1251 0 R +/Last 1267 0 R +/Count -5 +>> endobj +1243 0 obj << +/Title 1244 0 R +/A 1241 0 R +/Parent 1227 0 R +/Prev 1239 0 R +>> endobj +1239 0 obj << +/Title 1240 0 R +/A 1237 0 R +/Parent 1227 0 R +/Prev 1235 0 R +/Next 1243 0 R +>> endobj +1235 0 obj << +/Title 1236 0 R +/A 1233 0 R +/Parent 1227 0 R +/Prev 1231 0 R +/Next 1239 0 R +>> endobj +1231 0 obj << +/Title 1232 0 R +/A 1229 0 R +/Parent 1227 0 R +/Next 1235 0 R +>> endobj +1227 0 obj << +/Title 1228 0 R +/A 1225 0 R +/Parent 1223 0 R +/Next 1247 0 R +/First 1231 0 R +/Last 1243 0 R +/Count -4 +>> endobj +1223 0 obj << +/Title 1224 0 R +/A 1221 0 R +/Parent 3770 0 R +/Prev 295 0 R +/Next 1299 0 R +/First 1227 0 R +/Last 1271 0 R +/Count -3 +>> endobj +1219 0 obj << +/Title 1220 0 R +/A 1217 0 R +/Parent 1191 0 R +/Prev 1215 0 R +>> endobj +1215 0 obj << +/Title 1216 0 R +/A 1213 0 R +/Parent 1191 0 R +/Prev 1203 0 R +/Next 1219 0 R +>> endobj +1211 0 obj << +/Title 1212 0 R +/A 1209 0 R +/Parent 1203 0 R +/Prev 1207 0 R +>> endobj +1207 0 obj << +/Title 1208 0 R +/A 1205 0 R +/Parent 1203 0 R +/Next 1211 0 R +>> endobj +1203 0 obj << +/Title 1204 0 R +/A 1201 0 R +/Parent 1191 0 R +/Prev 1199 0 R +/Next 1215 0 R +/First 1207 0 R +/Last 1211 0 R +/Count -2 +>> endobj +1199 0 obj << +/Title 1200 0 R +/A 1197 0 R +/Parent 1191 0 R +/Prev 1195 0 R +/Next 1203 0 R +>> endobj +1195 0 obj << +/Title 1196 0 R +/A 1193 0 R +/Parent 1191 0 R +/Next 1199 0 R +>> endobj +1191 0 obj << +/Title 1192 0 R +/A 1189 0 R +/Parent 295 0 R +/Prev 1171 0 R +/First 1195 0 R +/Last 1219 0 R +/Count -5 +>> endobj +1187 0 obj << +/Title 1188 0 R +/A 1185 0 R +/Parent 1171 0 R +/Prev 1183 0 R +>> endobj +1183 0 obj << +/Title 1184 0 R +/A 1181 0 R +/Parent 1171 0 R +/Prev 1179 0 R +/Next 1187 0 R +>> endobj +1179 0 obj << +/Title 1180 0 R +/A 1177 0 R +/Parent 1171 0 R +/Prev 1175 0 R +/Next 1183 0 R +>> endobj +1175 0 obj << +/Title 1176 0 R +/A 1173 0 R +/Parent 1171 0 R +/Next 1179 0 R +>> endobj +1171 0 obj << +/Title 1172 0 R +/A 1169 0 R +/Parent 295 0 R +/Prev 1139 0 R +/Next 1191 0 R +/First 1175 0 R +/Last 1187 0 R +/Count -4 +>> endobj +1167 0 obj << +/Title 1168 0 R +/A 1165 0 R +/Parent 1139 0 R +/Prev 1163 0 R +>> endobj +1163 0 obj << +/Title 1164 0 R +/A 1161 0 R +/Parent 1139 0 R +/Prev 1159 0 R +/Next 1167 0 R +>> endobj +1159 0 obj << +/Title 1160 0 R +/A 1157 0 R +/Parent 1139 0 R +/Prev 1155 0 R +/Next 1163 0 R +>> endobj +1155 0 obj << +/Title 1156 0 R +/A 1153 0 R +/Parent 1139 0 R +/Prev 1151 0 R +/Next 1159 0 R +>> endobj +1151 0 obj << +/Title 1152 0 R +/A 1149 0 R +/Parent 1139 0 R +/Prev 1147 0 R +/Next 1155 0 R +>> endobj +1147 0 obj << +/Title 1148 0 R +/A 1145 0 R +/Parent 1139 0 R +/Prev 1143 0 R +/Next 1151 0 R +>> endobj +1143 0 obj << +/Title 1144 0 R +/A 1141 0 R +/Parent 1139 0 R +/Next 1147 0 R +>> endobj +1139 0 obj << +/Title 1140 0 R +/A 1137 0 R +/Parent 295 0 R +/Prev 1091 0 R +/Next 1171 0 R +/First 1143 0 R +/Last 1167 0 R +/Count -7 +>> endobj +1135 0 obj << +/Title 1136 0 R +/A 1133 0 R +/Parent 1115 0 R +/Prev 1131 0 R +>> endobj +1131 0 obj << +/Title 1132 0 R +/A 1129 0 R +/Parent 1115 0 R +/Prev 1127 0 R +/Next 1135 0 R +>> endobj +1127 0 obj << +/Title 1128 0 R +/A 1125 0 R +/Parent 1115 0 R +/Prev 1123 0 R +/Next 1131 0 R +>> endobj +1123 0 obj << +/Title 1124 0 R +/A 1121 0 R +/Parent 1115 0 R +/Prev 1119 0 R +/Next 1127 0 R +>> endobj +1119 0 obj << +/Title 1120 0 R +/A 1117 0 R +/Parent 1115 0 R +/Next 1123 0 R +>> endobj +1115 0 obj << +/Title 1116 0 R +/A 1113 0 R +/Parent 1091 0 R +/Prev 1095 0 R +/First 1119 0 R +/Last 1135 0 R +/Count -5 +>> endobj +1111 0 obj << +/Title 1112 0 R +/A 1109 0 R +/Parent 1095 0 R +/Prev 1107 0 R +>> endobj +1107 0 obj << +/Title 1108 0 R +/A 1105 0 R +/Parent 1095 0 R +/Prev 1103 0 R +/Next 1111 0 R +>> endobj +1103 0 obj << +/Title 1104 0 R +/A 1101 0 R +/Parent 1095 0 R +/Prev 1099 0 R +/Next 1107 0 R +>> endobj +1099 0 obj << +/Title 1100 0 R +/A 1097 0 R +/Parent 1095 0 R +/Next 1103 0 R +>> endobj +1095 0 obj << +/Title 1096 0 R +/A 1093 0 R +/Parent 1091 0 R +/Next 1115 0 R +/First 1099 0 R +/Last 1111 0 R +/Count -4 +>> endobj +1091 0 obj << +/Title 1092 0 R +/A 1089 0 R +/Parent 295 0 R +/Prev 1079 0 R +/Next 1139 0 R +/First 1095 0 R +/Last 1115 0 R +/Count -2 +>> endobj +1087 0 obj << +/Title 1088 0 R +/A 1085 0 R +/Parent 1083 0 R +>> endobj +1083 0 obj << +/Title 1084 0 R +/A 1081 0 R +/Parent 1079 0 R +/First 1087 0 R +/Last 1087 0 R +/Count -1 +>> endobj +1079 0 obj << +/Title 1080 0 R +/A 1077 0 R +/Parent 295 0 R +/Prev 1039 0 R +/Next 1091 0 R +/First 1083 0 R +/Last 1083 0 R +/Count -1 +>> endobj +1075 0 obj << +/Title 1076 0 R +/A 1073 0 R +/Parent 1067 0 R +/Prev 1071 0 R +>> endobj +1071 0 obj << +/Title 1072 0 R +/A 1069 0 R +/Parent 1067 0 R +/Next 1075 0 R +>> endobj +1067 0 obj << +/Title 1068 0 R +/A 1065 0 R +/Parent 1039 0 R +/Prev 1047 0 R +/First 1071 0 R +/Last 1075 0 R +/Count -2 +>> endobj +1063 0 obj << +/Title 1064 0 R +/A 1061 0 R +/Parent 1047 0 R +/Prev 1059 0 R +>> endobj +1059 0 obj << +/Title 1060 0 R +/A 1057 0 R +/Parent 1047 0 R +/Prev 1055 0 R +/Next 1063 0 R +>> endobj +1055 0 obj << +/Title 1056 0 R +/A 1053 0 R +/Parent 1047 0 R +/Prev 1051 0 R +/Next 1059 0 R +>> endobj +1051 0 obj << +/Title 1052 0 R +/A 1049 0 R +/Parent 1047 0 R +/Next 1055 0 R +>> endobj +1047 0 obj << +/Title 1048 0 R +/A 1045 0 R +/Parent 1039 0 R +/Prev 1043 0 R +/Next 1067 0 R +/First 1051 0 R +/Last 1063 0 R +/Count -4 +>> endobj +1043 0 obj << +/Title 1044 0 R +/A 1041 0 R +/Parent 1039 0 R +/Next 1047 0 R +>> endobj +1039 0 obj << +/Title 1040 0 R +/A 1037 0 R +/Parent 295 0 R +/Prev 1003 0 R +/Next 1079 0 R +/First 1043 0 R +/Last 1067 0 R +/Count -3 +>> endobj +1035 0 obj << +/Title 1036 0 R +/A 1033 0 R +/Parent 1003 0 R +/Prev 1007 0 R +>> endobj +1031 0 obj << +/Title 1032 0 R +/A 1029 0 R +/Parent 1015 0 R +/Prev 1027 0 R +>> endobj +1027 0 obj << +/Title 1028 0 R +/A 1025 0 R +/Parent 1015 0 R +/Prev 1023 0 R +/Next 1031 0 R +>> endobj +1023 0 obj << +/Title 1024 0 R +/A 1021 0 R +/Parent 1015 0 R +/Prev 1019 0 R +/Next 1027 0 R +>> endobj +1019 0 obj << +/Title 1020 0 R +/A 1017 0 R +/Parent 1015 0 R +/Next 1023 0 R +>> endobj +1015 0 obj << +/Title 1016 0 R +/A 1013 0 R +/Parent 1007 0 R +/Prev 1011 0 R +/First 1019 0 R +/Last 1031 0 R +/Count -4 +>> endobj +1011 0 obj << +/Title 1012 0 R +/A 1009 0 R +/Parent 1007 0 R +/Next 1015 0 R +>> endobj +1007 0 obj << +/Title 1008 0 R +/A 1005 0 R +/Parent 1003 0 R +/Next 1035 0 R +/First 1011 0 R +/Last 1015 0 R +/Count -2 +>> endobj +1003 0 obj << +/Title 1004 0 R +/A 1001 0 R +/Parent 295 0 R +/Prev 971 0 R +/Next 1039 0 R +/First 1007 0 R +/Last 1035 0 R +/Count -2 +>> endobj +999 0 obj << +/Title 1000 0 R +/A 997 0 R +/Parent 991 0 R +/Prev 995 0 R +>> endobj +995 0 obj << +/Title 996 0 R +/A 993 0 R +/Parent 991 0 R +/Next 999 0 R +>> endobj +991 0 obj << +/Title 992 0 R +/A 989 0 R +/Parent 971 0 R +/Prev 979 0 R +/First 995 0 R +/Last 999 0 R +/Count -2 +>> endobj +987 0 obj << +/Title 988 0 R +/A 985 0 R +/Parent 979 0 R +/Prev 983 0 R +>> endobj +983 0 obj << +/Title 984 0 R +/A 981 0 R +/Parent 979 0 R +/Next 987 0 R +>> endobj +979 0 obj << +/Title 980 0 R +/A 977 0 R +/Parent 971 0 R +/Prev 975 0 R +/Next 991 0 R +/First 983 0 R +/Last 987 0 R +/Count -2 +>> endobj +975 0 obj << +/Title 976 0 R +/A 973 0 R +/Parent 971 0 R +/Next 979 0 R +>> endobj +971 0 obj << +/Title 972 0 R +/A 969 0 R +/Parent 295 0 R +/Prev 875 0 R +/Next 1003 0 R +/First 975 0 R +/Last 991 0 R +/Count -3 +>> endobj +967 0 obj << +/Title 968 0 R +/A 965 0 R +/Parent 951 0 R +/Prev 963 0 R +>> endobj +963 0 obj << +/Title 964 0 R +/A 961 0 R +/Parent 951 0 R +/Prev 955 0 R +/Next 967 0 R +>> endobj +959 0 obj << +/Title 960 0 R +/A 957 0 R +/Parent 955 0 R +>> endobj +955 0 obj << +/Title 956 0 R +/A 953 0 R +/Parent 951 0 R +/Next 963 0 R +/First 959 0 R +/Last 959 0 R +/Count -1 +>> endobj +951 0 obj << +/Title 952 0 R +/A 949 0 R +/Parent 875 0 R +/Prev 947 0 R +/First 955 0 R +/Last 967 0 R +/Count -3 +>> endobj +947 0 obj << +/Title 948 0 R +/A 945 0 R +/Parent 875 0 R +/Prev 943 0 R +/Next 951 0 R +>> endobj +943 0 obj << +/Title 944 0 R +/A 941 0 R +/Parent 875 0 R +/Prev 879 0 R +/Next 947 0 R +>> endobj +939 0 obj << +/Title 940 0 R +/A 937 0 R +/Parent 923 0 R +/Prev 935 0 R +>> endobj +935 0 obj << +/Title 936 0 R +/A 933 0 R +/Parent 923 0 R +/Prev 931 0 R +/Next 939 0 R +>> endobj +931 0 obj << +/Title 932 0 R +/A 929 0 R +/Parent 923 0 R +/Prev 927 0 R +/Next 935 0 R +>> endobj +927 0 obj << +/Title 928 0 R +/A 925 0 R +/Parent 923 0 R +/Next 931 0 R +>> endobj +923 0 obj << +/Title 924 0 R +/A 921 0 R +/Parent 879 0 R +/Prev 919 0 R +/First 927 0 R +/Last 939 0 R +/Count -4 +>> endobj +919 0 obj << +/Title 920 0 R +/A 917 0 R +/Parent 879 0 R +/Prev 903 0 R +/Next 923 0 R +>> endobj +915 0 obj << +/Title 916 0 R +/A 913 0 R +/Parent 903 0 R +/Prev 911 0 R +>> endobj +911 0 obj << +/Title 912 0 R +/A 909 0 R +/Parent 903 0 R +/Prev 907 0 R +/Next 915 0 R +>> endobj +907 0 obj << +/Title 908 0 R +/A 905 0 R +/Parent 903 0 R +/Next 911 0 R +>> endobj +903 0 obj << +/Title 904 0 R +/A 901 0 R +/Parent 879 0 R +/Prev 883 0 R +/Next 919 0 R +/First 907 0 R +/Last 915 0 R +/Count -3 +>> endobj +899 0 obj << +/Title 900 0 R +/A 897 0 R +/Parent 883 0 R +/Prev 895 0 R +>> endobj +895 0 obj << +/Title 896 0 R +/A 893 0 R +/Parent 883 0 R +/Prev 891 0 R +/Next 899 0 R +>> endobj +891 0 obj << +/Title 892 0 R +/A 889 0 R +/Parent 883 0 R +/Prev 887 0 R +/Next 895 0 R +>> endobj +887 0 obj << +/Title 888 0 R +/A 885 0 R +/Parent 883 0 R +/Next 891 0 R +>> endobj +883 0 obj << +/Title 884 0 R +/A 881 0 R +/Parent 879 0 R +/Next 903 0 R +/First 887 0 R +/Last 899 0 R +/Count -4 +>> endobj +879 0 obj << +/Title 880 0 R +/A 877 0 R +/Parent 875 0 R +/Next 943 0 R +/First 883 0 R +/Last 923 0 R +/Count -4 +>> endobj +875 0 obj << +/Title 876 0 R +/A 873 0 R +/Parent 295 0 R +/Prev 831 0 R +/Next 971 0 R +/First 879 0 R +/Last 951 0 R +/Count -4 +>> endobj +871 0 obj << +/Title 872 0 R +/A 869 0 R +/Parent 831 0 R +/Prev 859 0 R +>> endobj +867 0 obj << +/Title 868 0 R +/A 865 0 R +/Parent 859 0 R +/Prev 863 0 R +>> endobj +863 0 obj << +/Title 864 0 R +/A 861 0 R +/Parent 859 0 R +/Next 867 0 R +>> endobj +859 0 obj << +/Title 860 0 R +/A 857 0 R +/Parent 831 0 R +/Prev 835 0 R +/Next 871 0 R +/First 863 0 R +/Last 867 0 R +/Count -2 +>> endobj +855 0 obj << +/Title 856 0 R +/A 853 0 R +/Parent 851 0 R +>> endobj +851 0 obj << +/Title 852 0 R +/A 849 0 R +/Parent 835 0 R +/Prev 843 0 R +/First 855 0 R +/Last 855 0 R +/Count -1 +>> endobj +847 0 obj << +/Title 848 0 R +/A 845 0 R +/Parent 843 0 R +>> endobj +843 0 obj << +/Title 844 0 R +/A 841 0 R +/Parent 835 0 R +/Prev 839 0 R +/Next 851 0 R +/First 847 0 R +/Last 847 0 R +/Count -1 +>> endobj +839 0 obj << +/Title 840 0 R +/A 837 0 R +/Parent 835 0 R +/Next 843 0 R +>> endobj +835 0 obj << +/Title 836 0 R +/A 833 0 R +/Parent 831 0 R +/Next 859 0 R +/First 839 0 R +/Last 851 0 R +/Count -3 +>> endobj +831 0 obj << +/Title 832 0 R +/A 829 0 R +/Parent 295 0 R +/Prev 799 0 R +/Next 875 0 R +/First 835 0 R +/Last 871 0 R +/Count -3 +>> endobj +827 0 obj << +/Title 828 0 R +/A 825 0 R +/Parent 823 0 R +>> endobj +823 0 obj << +/Title 824 0 R +/A 821 0 R +/Parent 799 0 R +/Prev 819 0 R +/First 827 0 R +/Last 827 0 R +/Count -1 +>> endobj +819 0 obj << +/Title 820 0 R +/A 817 0 R +/Parent 799 0 R +/Prev 803 0 R +/Next 823 0 R +>> endobj +815 0 obj << +/Title 816 0 R +/A 813 0 R +/Parent 807 0 R +/Prev 811 0 R +>> endobj +811 0 obj << +/Title 812 0 R +/A 809 0 R +/Parent 807 0 R +/Next 815 0 R +>> endobj +807 0 obj << +/Title 808 0 R +/A 805 0 R +/Parent 803 0 R +/First 811 0 R +/Last 815 0 R +/Count -2 +>> endobj +803 0 obj << +/Title 804 0 R +/A 801 0 R +/Parent 799 0 R +/Next 819 0 R +/First 807 0 R +/Last 807 0 R +/Count -1 +>> endobj +799 0 obj << +/Title 800 0 R +/A 797 0 R +/Parent 295 0 R +/Prev 695 0 R +/Next 831 0 R +/First 803 0 R +/Last 823 0 R +/Count -3 +>> endobj +795 0 obj << +/Title 796 0 R +/A 793 0 R +/Parent 695 0 R +/Prev 791 0 R +>> endobj +791 0 obj << +/Title 792 0 R +/A 789 0 R +/Parent 695 0 R +/Prev 743 0 R +/Next 795 0 R +>> endobj +787 0 obj << +/Title 788 0 R +/A 785 0 R +/Parent 755 0 R +/Prev 783 0 R +>> endobj +783 0 obj << +/Title 784 0 R +/A 781 0 R +/Parent 755 0 R +/Prev 779 0 R +/Next 787 0 R +>> endobj +779 0 obj << +/Title 780 0 R +/A 777 0 R +/Parent 755 0 R +/Prev 775 0 R +/Next 783 0 R +>> endobj +775 0 obj << +/Title 776 0 R +/A 773 0 R +/Parent 755 0 R +/Prev 771 0 R +/Next 779 0 R +>> endobj +771 0 obj << +/Title 772 0 R +/A 769 0 R +/Parent 755 0 R +/Prev 767 0 R +/Next 775 0 R +>> endobj +767 0 obj << +/Title 768 0 R +/A 765 0 R +/Parent 755 0 R +/Prev 763 0 R +/Next 771 0 R +>> endobj +763 0 obj << +/Title 764 0 R +/A 761 0 R +/Parent 755 0 R +/Prev 759 0 R +/Next 767 0 R +>> endobj +759 0 obj << +/Title 760 0 R +/A 757 0 R +/Parent 755 0 R +/Next 763 0 R +>> endobj +755 0 obj << +/Title 756 0 R +/A 753 0 R +/Parent 743 0 R +/Prev 751 0 R +/First 759 0 R +/Last 787 0 R +/Count -8 +>> endobj +751 0 obj << +/Title 752 0 R +/A 749 0 R +/Parent 743 0 R +/Prev 747 0 R +/Next 755 0 R +>> endobj +747 0 obj << +/Title 748 0 R +/A 745 0 R +/Parent 743 0 R +/Next 751 0 R +>> endobj +743 0 obj << +/Title 744 0 R +/A 741 0 R +/Parent 695 0 R +/Prev 715 0 R +/Next 791 0 R +/First 747 0 R +/Last 755 0 R +/Count -3 +>> endobj +739 0 obj << +/Title 740 0 R +/A 737 0 R +/Parent 715 0 R +/Prev 735 0 R +>> endobj +735 0 obj << +/Title 736 0 R +/A 733 0 R +/Parent 715 0 R +/Prev 731 0 R +/Next 739 0 R +>> endobj +731 0 obj << +/Title 732 0 R +/A 729 0 R +/Parent 715 0 R +/Prev 727 0 R +/Next 735 0 R +>> endobj +727 0 obj << +/Title 728 0 R +/A 725 0 R +/Parent 715 0 R +/Prev 723 0 R +/Next 731 0 R +>> endobj +723 0 obj << +/Title 724 0 R +/A 721 0 R +/Parent 715 0 R +/Prev 719 0 R +/Next 727 0 R +>> endobj +719 0 obj << +/Title 720 0 R +/A 717 0 R +/Parent 715 0 R +/Next 723 0 R +>> endobj +715 0 obj << +/Title 716 0 R +/A 713 0 R +/Parent 695 0 R +/Prev 707 0 R +/Next 743 0 R +/First 719 0 R +/Last 739 0 R +/Count -6 +>> endobj +711 0 obj << +/Title 712 0 R +/A 709 0 R +/Parent 707 0 R +>> endobj +707 0 obj << +/Title 708 0 R +/A 705 0 R +/Parent 695 0 R +/Prev 703 0 R +/Next 715 0 R +/First 711 0 R +/Last 711 0 R +/Count -1 +>> endobj +703 0 obj << +/Title 704 0 R +/A 701 0 R +/Parent 695 0 R +/Prev 699 0 R +/Next 707 0 R +>> endobj +699 0 obj << +/Title 700 0 R +/A 697 0 R +/Parent 695 0 R +/Next 703 0 R +>> endobj +695 0 obj << +/Title 696 0 R +/A 693 0 R +/Parent 295 0 R +/Prev 635 0 R +/Next 799 0 R +/First 699 0 R +/Last 795 0 R +/Count -7 +>> endobj +691 0 obj << +/Title 692 0 R +/A 689 0 R +/Parent 635 0 R +/Prev 687 0 R +>> endobj +687 0 obj << +/Title 688 0 R +/A 685 0 R +/Parent 635 0 R +/Prev 683 0 R +/Next 691 0 R +>> endobj +683 0 obj << +/Title 684 0 R +/A 681 0 R +/Parent 635 0 R +/Prev 675 0 R +/Next 687 0 R +>> endobj +679 0 obj << +/Title 680 0 R +/A 677 0 R +/Parent 675 0 R +>> endobj +675 0 obj << +/Title 676 0 R +/A 673 0 R +/Parent 635 0 R +/Prev 671 0 R +/Next 683 0 R +/First 679 0 R +/Last 679 0 R +/Count -1 +>> endobj +671 0 obj << +/Title 672 0 R +/A 669 0 R +/Parent 635 0 R +/Prev 663 0 R +/Next 675 0 R +>> endobj +667 0 obj << +/Title 668 0 R +/A 665 0 R +/Parent 663 0 R +>> endobj +663 0 obj << +/Title 664 0 R +/A 661 0 R +/Parent 635 0 R +/Prev 659 0 R +/Next 671 0 R +/First 667 0 R +/Last 667 0 R +/Count -1 +>> endobj +659 0 obj << +/Title 660 0 R +/A 657 0 R +/Parent 635 0 R +/Prev 655 0 R +/Next 663 0 R +>> endobj +655 0 obj << +/Title 656 0 R +/A 653 0 R +/Parent 635 0 R +/Prev 651 0 R +/Next 659 0 R +>> endobj +651 0 obj << +/Title 652 0 R +/A 649 0 R +/Parent 635 0 R +/Prev 647 0 R +/Next 655 0 R +>> endobj +647 0 obj << +/Title 648 0 R +/A 645 0 R +/Parent 635 0 R +/Prev 643 0 R +/Next 651 0 R +>> endobj +643 0 obj << +/Title 644 0 R +/A 641 0 R +/Parent 635 0 R +/Prev 639 0 R +/Next 647 0 R +>> endobj +639 0 obj << +/Title 640 0 R +/A 637 0 R +/Parent 635 0 R +/Next 643 0 R +>> endobj +635 0 obj << +/Title 636 0 R +/A 633 0 R +/Parent 295 0 R +/Prev 543 0 R +/Next 695 0 R +/First 639 0 R +/Last 691 0 R +/Count -12 +>> endobj +631 0 obj << +/Title 632 0 R +/A 629 0 R +/Parent 595 0 R +/Prev 627 0 R +>> endobj +627 0 obj << +/Title 628 0 R +/A 625 0 R +/Parent 595 0 R +/Prev 623 0 R +/Next 631 0 R +>> endobj +623 0 obj << +/Title 624 0 R +/A 621 0 R +/Parent 595 0 R +/Prev 619 0 R +/Next 627 0 R +>> endobj +619 0 obj << +/Title 620 0 R +/A 617 0 R +/Parent 595 0 R +/Prev 615 0 R +/Next 623 0 R +>> endobj +615 0 obj << +/Title 616 0 R +/A 613 0 R +/Parent 595 0 R +/Prev 611 0 R +/Next 619 0 R +>> endobj +611 0 obj << +/Title 612 0 R +/A 609 0 R +/Parent 595 0 R +/Prev 607 0 R +/Next 615 0 R +>> endobj +607 0 obj << +/Title 608 0 R +/A 605 0 R +/Parent 595 0 R +/Prev 603 0 R +/Next 611 0 R +>> endobj +603 0 obj << +/Title 604 0 R +/A 601 0 R +/Parent 595 0 R +/Prev 599 0 R +/Next 607 0 R +>> endobj +599 0 obj << +/Title 600 0 R +/A 597 0 R +/Parent 595 0 R +/Next 603 0 R +>> endobj +595 0 obj << +/Title 596 0 R +/A 593 0 R +/Parent 543 0 R +/Prev 575 0 R +/First 599 0 R +/Last 631 0 R +/Count -9 +>> endobj +591 0 obj << +/Title 592 0 R +/A 589 0 R +/Parent 575 0 R +/Prev 587 0 R +>> endobj +587 0 obj << +/Title 588 0 R +/A 585 0 R +/Parent 575 0 R +/Prev 583 0 R +/Next 591 0 R +>> endobj +583 0 obj << +/Title 584 0 R +/A 581 0 R +/Parent 575 0 R +/Prev 579 0 R +/Next 587 0 R +>> endobj +579 0 obj << +/Title 580 0 R +/A 577 0 R +/Parent 575 0 R +/Next 583 0 R +>> endobj +575 0 obj << +/Title 576 0 R +/A 573 0 R +/Parent 543 0 R +/Prev 551 0 R +/Next 595 0 R +/First 579 0 R +/Last 591 0 R +/Count -4 +>> endobj +571 0 obj << +/Title 572 0 R +/A 569 0 R +/Parent 551 0 R +/Prev 567 0 R +>> endobj +567 0 obj << +/Title 568 0 R +/A 565 0 R +/Parent 551 0 R +/Prev 563 0 R +/Next 571 0 R +>> endobj +563 0 obj << +/Title 564 0 R +/A 561 0 R +/Parent 551 0 R +/Prev 559 0 R +/Next 567 0 R +>> endobj +559 0 obj << +/Title 560 0 R +/A 557 0 R +/Parent 551 0 R +/Prev 555 0 R +/Next 563 0 R +>> endobj +555 0 obj << +/Title 556 0 R +/A 553 0 R +/Parent 551 0 R +/Next 559 0 R +>> endobj +551 0 obj << +/Title 552 0 R +/A 549 0 R +/Parent 543 0 R +/Prev 547 0 R +/Next 575 0 R +/First 555 0 R +/Last 571 0 R +/Count -5 +>> endobj +547 0 obj << +/Title 548 0 R +/A 545 0 R +/Parent 543 0 R +/Next 551 0 R +>> endobj +543 0 obj << +/Title 544 0 R +/A 541 0 R +/Parent 295 0 R +/Prev 539 0 R +/Next 635 0 R +/First 547 0 R +/Last 595 0 R +/Count -4 +>> endobj +539 0 obj << +/Title 540 0 R +/A 537 0 R +/Parent 295 0 R +/Prev 499 0 R +/Next 543 0 R +>> endobj +535 0 obj << +/Title 536 0 R +/A 533 0 R +/Parent 499 0 R +/Prev 531 0 R +>> endobj +531 0 obj << +/Title 532 0 R +/A 529 0 R +/Parent 499 0 R +/Prev 527 0 R +/Next 535 0 R +>> endobj +527 0 obj << +/Title 528 0 R +/A 525 0 R +/Parent 499 0 R +/Prev 515 0 R +/Next 531 0 R +>> endobj +523 0 obj << +/Title 524 0 R +/A 521 0 R +/Parent 515 0 R +/Prev 519 0 R +>> endobj +519 0 obj << +/Title 520 0 R +/A 517 0 R +/Parent 515 0 R +/Next 523 0 R +>> endobj +515 0 obj << +/Title 516 0 R +/A 513 0 R +/Parent 499 0 R +/Prev 511 0 R +/Next 527 0 R +/First 519 0 R +/Last 523 0 R +/Count -2 +>> endobj +511 0 obj << +/Title 512 0 R +/A 509 0 R +/Parent 499 0 R +/Prev 507 0 R +/Next 515 0 R +>> endobj +507 0 obj << +/Title 508 0 R +/A 505 0 R +/Parent 499 0 R +/Prev 503 0 R +/Next 511 0 R +>> endobj +503 0 obj << +/Title 504 0 R +/A 501 0 R +/Parent 499 0 R +/Next 507 0 R +>> endobj +499 0 obj << +/Title 500 0 R +/A 497 0 R +/Parent 295 0 R +/Prev 395 0 R +/Next 539 0 R +/First 503 0 R +/Last 535 0 R +/Count -7 +>> endobj +495 0 obj << +/Title 496 0 R +/A 493 0 R +/Parent 395 0 R +/Prev 475 0 R +>> endobj +491 0 obj << +/Title 492 0 R +/A 489 0 R +/Parent 475 0 R +/Prev 487 0 R +>> endobj +487 0 obj << +/Title 488 0 R +/A 485 0 R +/Parent 475 0 R +/Prev 483 0 R +/Next 491 0 R +>> endobj +483 0 obj << +/Title 484 0 R +/A 481 0 R +/Parent 475 0 R +/Prev 479 0 R +/Next 487 0 R +>> endobj +479 0 obj << +/Title 480 0 R +/A 477 0 R +/Parent 475 0 R +/Next 483 0 R +>> endobj +475 0 obj << +/Title 476 0 R +/A 473 0 R +/Parent 395 0 R +/Prev 427 0 R +/Next 495 0 R +/First 479 0 R +/Last 491 0 R +/Count -4 +>> endobj +471 0 obj << +/Title 472 0 R +/A 469 0 R +/Parent 427 0 R +/Prev 467 0 R +>> endobj +467 0 obj << +/Title 468 0 R +/A 465 0 R +/Parent 427 0 R +/Prev 463 0 R +/Next 471 0 R +>> endobj +463 0 obj << +/Title 464 0 R +/A 461 0 R +/Parent 427 0 R +/Prev 459 0 R +/Next 467 0 R +>> endobj +459 0 obj << +/Title 460 0 R +/A 457 0 R +/Parent 427 0 R +/Prev 447 0 R +/Next 463 0 R +>> endobj +455 0 obj << +/Title 456 0 R +/A 453 0 R +/Parent 447 0 R +/Prev 451 0 R +>> endobj +451 0 obj << +/Title 452 0 R +/A 449 0 R +/Parent 447 0 R +/Next 455 0 R +>> endobj +447 0 obj << +/Title 448 0 R +/A 445 0 R +/Parent 427 0 R +/Prev 443 0 R +/Next 459 0 R +/First 451 0 R +/Last 455 0 R +/Count -2 +>> endobj +443 0 obj << +/Title 444 0 R +/A 441 0 R +/Parent 427 0 R +/Prev 439 0 R +/Next 447 0 R +>> endobj +439 0 obj << +/Title 440 0 R +/A 437 0 R +/Parent 427 0 R +/Prev 435 0 R +/Next 443 0 R +>> endobj +435 0 obj << +/Title 436 0 R +/A 433 0 R +/Parent 427 0 R +/Prev 431 0 R +/Next 439 0 R +>> endobj +431 0 obj << +/Title 432 0 R +/A 429 0 R +/Parent 427 0 R +/Next 435 0 R +>> endobj +427 0 obj << +/Title 428 0 R +/A 425 0 R +/Parent 395 0 R +/Prev 423 0 R +/Next 475 0 R +/First 431 0 R +/Last 471 0 R +/Count -9 +>> endobj +423 0 obj << +/Title 424 0 R +/A 421 0 R +/Parent 395 0 R +/Prev 419 0 R +/Next 427 0 R +>> endobj +419 0 obj << +/Title 420 0 R +/A 417 0 R +/Parent 395 0 R +/Prev 415 0 R +/Next 423 0 R +>> endobj +415 0 obj << +/Title 416 0 R +/A 413 0 R +/Parent 395 0 R +/Prev 403 0 R +/Next 419 0 R +>> endobj +411 0 obj << +/Title 412 0 R +/A 409 0 R +/Parent 403 0 R +/Prev 407 0 R +>> endobj +407 0 obj << +/Title 408 0 R +/A 405 0 R +/Parent 403 0 R +/Next 411 0 R +>> endobj +403 0 obj << +/Title 404 0 R +/A 401 0 R +/Parent 395 0 R +/Prev 399 0 R +/Next 415 0 R +/First 407 0 R +/Last 411 0 R +/Count -2 +>> endobj +399 0 obj << +/Title 400 0 R +/A 397 0 R +/Parent 395 0 R +/Next 403 0 R +>> endobj +395 0 obj << +/Title 396 0 R +/A 393 0 R +/Parent 295 0 R +/Prev 299 0 R +/Next 499 0 R +/First 399 0 R +/Last 495 0 R +/Count -8 +>> endobj +391 0 obj << +/Title 392 0 R +/A 389 0 R +/Parent 387 0 R +>> endobj +387 0 obj << +/Title 388 0 R +/A 385 0 R +/Parent 375 0 R +/Prev 383 0 R +/First 391 0 R +/Last 391 0 R +/Count -1 +>> endobj +383 0 obj << +/Title 384 0 R +/A 381 0 R +/Parent 375 0 R +/Prev 379 0 R +/Next 387 0 R +>> endobj +379 0 obj << +/Title 380 0 R +/A 377 0 R +/Parent 375 0 R +/Next 383 0 R +>> endobj +375 0 obj << +/Title 376 0 R +/A 373 0 R +/Parent 299 0 R +/Prev 363 0 R +/First 379 0 R +/Last 387 0 R +/Count -3 +>> endobj +371 0 obj << +/Title 372 0 R +/A 369 0 R +/Parent 363 0 R +/Prev 367 0 R +>> endobj +367 0 obj << +/Title 368 0 R +/A 365 0 R +/Parent 363 0 R +/Next 371 0 R +>> endobj +363 0 obj << +/Title 364 0 R +/A 361 0 R +/Parent 299 0 R +/Prev 347 0 R +/Next 375 0 R +/First 367 0 R +/Last 371 0 R +/Count -2 +>> endobj +359 0 obj << +/Title 360 0 R +/A 357 0 R +/Parent 347 0 R +/Prev 355 0 R +>> endobj +355 0 obj << +/Title 356 0 R +/A 353 0 R +/Parent 347 0 R +/Prev 351 0 R +/Next 359 0 R +>> endobj +351 0 obj << +/Title 352 0 R +/A 349 0 R +/Parent 347 0 R +/Next 355 0 R +>> endobj +347 0 obj << +/Title 348 0 R +/A 345 0 R +/Parent 299 0 R +/Prev 311 0 R +/Next 363 0 R +/First 351 0 R +/Last 359 0 R +/Count -3 +>> endobj +343 0 obj << +/Title 344 0 R +/A 341 0 R +/Parent 311 0 R +/Prev 339 0 R +>> endobj +339 0 obj << +/Title 340 0 R +/A 337 0 R +/Parent 311 0 R +/Prev 335 0 R +/Next 343 0 R +>> endobj +335 0 obj << +/Title 336 0 R +/A 333 0 R +/Parent 311 0 R +/Prev 331 0 R +/Next 339 0 R +>> endobj +331 0 obj << +/Title 332 0 R +/A 329 0 R +/Parent 311 0 R +/Prev 327 0 R +/Next 335 0 R +>> endobj +327 0 obj << +/Title 328 0 R +/A 325 0 R +/Parent 311 0 R +/Prev 323 0 R +/Next 331 0 R +>> endobj +323 0 obj << +/Title 324 0 R +/A 321 0 R +/Parent 311 0 R +/Prev 319 0 R +/Next 327 0 R +>> endobj +319 0 obj << +/Title 320 0 R +/A 317 0 R +/Parent 311 0 R +/Prev 315 0 R +/Next 323 0 R +>> endobj +315 0 obj << +/Title 316 0 R +/A 313 0 R +/Parent 311 0 R +/Next 319 0 R +>> endobj +311 0 obj << +/Title 312 0 R +/A 309 0 R +/Parent 299 0 R +/Prev 307 0 R +/Next 347 0 R +/First 315 0 R +/Last 343 0 R +/Count -8 +>> endobj +307 0 obj << +/Title 308 0 R +/A 305 0 R +/Parent 299 0 R +/Prev 303 0 R +/Next 311 0 R +>> endobj +303 0 obj << +/Title 304 0 R +/A 301 0 R +/Parent 299 0 R +/Next 307 0 R +>> endobj +299 0 obj << +/Title 300 0 R +/A 297 0 R +/Parent 295 0 R +/Next 395 0 R +/First 303 0 R +/Last 375 0 R +/Count -6 +>> endobj +295 0 obj << +/Title 296 0 R +/A 293 0 R +/Parent 3770 0 R +/Prev 83 0 R +/Next 1223 0 R +/First 299 0 R +/Last 1191 0 R +/Count -18 +>> endobj +291 0 obj << +/Title 292 0 R +/A 289 0 R +/Parent 283 0 R +/Prev 287 0 R +>> endobj +287 0 obj << +/Title 288 0 R +/A 285 0 R +/Parent 283 0 R +/Next 291 0 R +>> endobj +283 0 obj << +/Title 284 0 R +/A 281 0 R +/Parent 83 0 R +/Prev 251 0 R +/First 287 0 R +/Last 291 0 R +/Count -2 +>> endobj +279 0 obj << +/Title 280 0 R +/A 277 0 R +/Parent 251 0 R +/Prev 275 0 R +>> endobj +275 0 obj << +/Title 276 0 R +/A 273 0 R +/Parent 251 0 R +/Prev 271 0 R +/Next 279 0 R +>> endobj +271 0 obj << +/Title 272 0 R +/A 269 0 R +/Parent 251 0 R +/Prev 263 0 R +/Next 275 0 R +>> endobj +267 0 obj << +/Title 268 0 R +/A 265 0 R +/Parent 263 0 R +>> endobj +263 0 obj << +/Title 264 0 R +/A 261 0 R +/Parent 251 0 R +/Prev 259 0 R +/Next 271 0 R +/First 267 0 R +/Last 267 0 R +/Count -1 +>> endobj +259 0 obj << +/Title 260 0 R +/A 257 0 R +/Parent 251 0 R +/Prev 255 0 R +/Next 263 0 R +>> endobj +255 0 obj << +/Title 256 0 R +/A 253 0 R +/Parent 251 0 R +/Next 259 0 R +>> endobj +251 0 obj << +/Title 252 0 R +/A 249 0 R +/Parent 83 0 R +/Prev 211 0 R +/Next 283 0 R +/First 255 0 R +/Last 279 0 R +/Count -6 +>> endobj +247 0 obj << +/Title 248 0 R +/A 245 0 R +/Parent 239 0 R +/Prev 243 0 R +>> endobj +243 0 obj << +/Title 244 0 R +/A 241 0 R +/Parent 239 0 R +/Next 247 0 R +>> endobj +239 0 obj << +/Title 240 0 R +/A 237 0 R +/Parent 211 0 R +/Prev 235 0 R +/First 243 0 R +/Last 247 0 R +/Count -2 +>> endobj +235 0 obj << +/Title 236 0 R +/A 233 0 R +/Parent 211 0 R +/Prev 223 0 R +/Next 239 0 R +>> endobj +231 0 obj << +/Title 232 0 R +/A 229 0 R +/Parent 223 0 R +/Prev 227 0 R +>> endobj +227 0 obj << +/Title 228 0 R +/A 225 0 R +/Parent 223 0 R +/Next 231 0 R +>> endobj +223 0 obj << +/Title 224 0 R +/A 221 0 R +/Parent 211 0 R +/Prev 219 0 R +/Next 235 0 R +/First 227 0 R +/Last 231 0 R +/Count -2 +>> endobj +219 0 obj << +/Title 220 0 R +/A 217 0 R +/Parent 211 0 R +/Prev 215 0 R +/Next 223 0 R +>> endobj +215 0 obj << +/Title 216 0 R +/A 213 0 R +/Parent 211 0 R +/Next 219 0 R +>> endobj +211 0 obj << +/Title 212 0 R +/A 209 0 R +/Parent 83 0 R +/Prev 147 0 R +/Next 251 0 R +/First 215 0 R +/Last 239 0 R +/Count -5 +>> endobj +207 0 obj << +/Title 208 0 R +/A 205 0 R +/Parent 203 0 R +>> endobj +203 0 obj << +/Title 204 0 R +/A 201 0 R +/Parent 147 0 R +/Prev 179 0 R +/First 207 0 R +/Last 207 0 R +/Count -1 +>> endobj +199 0 obj << +/Title 200 0 R +/A 197 0 R +/Parent 179 0 R +/Prev 195 0 R +>> endobj +195 0 obj << +/Title 196 0 R +/A 193 0 R +/Parent 179 0 R +/Prev 191 0 R +/Next 199 0 R +>> endobj +191 0 obj << +/Title 192 0 R +/A 189 0 R +/Parent 179 0 R +/Prev 187 0 R +/Next 195 0 R +>> endobj +187 0 obj << +/Title 188 0 R +/A 185 0 R +/Parent 179 0 R +/Prev 183 0 R +/Next 191 0 R +>> endobj +183 0 obj << +/Title 184 0 R +/A 181 0 R +/Parent 179 0 R +/Next 187 0 R +>> endobj +179 0 obj << +/Title 180 0 R +/A 177 0 R +/Parent 147 0 R +/Prev 163 0 R +/Next 203 0 R +/First 183 0 R +/Last 199 0 R +/Count -5 +>> endobj +175 0 obj << +/Title 176 0 R +/A 173 0 R +/Parent 163 0 R +/Prev 171 0 R +>> endobj +171 0 obj << +/Title 172 0 R +/A 169 0 R +/Parent 163 0 R +/Prev 167 0 R +/Next 175 0 R +>> endobj +167 0 obj << +/Title 168 0 R +/A 165 0 R +/Parent 163 0 R +/Next 171 0 R +>> endobj +163 0 obj << +/Title 164 0 R +/A 161 0 R +/Parent 147 0 R +/Prev 159 0 R +/Next 179 0 R +/First 167 0 R +/Last 175 0 R +/Count -3 +>> endobj +159 0 obj << +/Title 160 0 R +/A 157 0 R +/Parent 147 0 R +/Prev 155 0 R +/Next 163 0 R +>> endobj +155 0 obj << +/Title 156 0 R +/A 153 0 R +/Parent 147 0 R +/Prev 151 0 R +/Next 159 0 R +>> endobj +151 0 obj << +/Title 152 0 R +/A 149 0 R +/Parent 147 0 R +/Next 155 0 R +>> endobj +147 0 obj << +/Title 148 0 R +/A 145 0 R +/Parent 83 0 R +/Prev 107 0 R +/Next 211 0 R +/First 151 0 R +/Last 203 0 R +/Count -6 +>> endobj +143 0 obj << +/Title 144 0 R +/A 141 0 R +/Parent 111 0 R +/Prev 135 0 R +>> endobj +139 0 obj << +/Title 140 0 R +/A 137 0 R +/Parent 135 0 R +>> endobj +135 0 obj << +/Title 136 0 R +/A 133 0 R +/Parent 111 0 R +/Prev 123 0 R +/Next 143 0 R +/First 139 0 R +/Last 139 0 R +/Count -1 +>> endobj +131 0 obj << +/Title 132 0 R +/A 129 0 R +/Parent 123 0 R +/Prev 127 0 R +>> endobj +127 0 obj << +/Title 128 0 R +/A 125 0 R +/Parent 123 0 R +/Next 131 0 R +>> endobj +123 0 obj << +/Title 124 0 R +/A 121 0 R +/Parent 111 0 R +/Prev 119 0 R +/Next 135 0 R +/First 127 0 R +/Last 131 0 R +/Count -2 +>> endobj +119 0 obj << +/Title 120 0 R +/A 117 0 R +/Parent 111 0 R +/Prev 115 0 R +/Next 123 0 R +>> endobj +115 0 obj << +/Title 116 0 R +/A 113 0 R +/Parent 111 0 R +/Next 119 0 R +>> endobj +111 0 obj << +/Title 112 0 R +/A 109 0 R +/Parent 107 0 R +/First 115 0 R +/Last 143 0 R +/Count -5 +>> endobj +107 0 obj << +/Title 108 0 R +/A 105 0 R +/Parent 83 0 R +/Prev 87 0 R +/Next 147 0 R +/First 111 0 R +/Last 111 0 R +/Count -1 +>> endobj +103 0 obj << +/Title 104 0 R +/A 101 0 R +/Parent 99 0 R +>> endobj +99 0 obj << +/Title 100 0 R +/A 97 0 R +/Parent 87 0 R +/Prev 95 0 R +/First 103 0 R +/Last 103 0 R +/Count -1 +>> endobj +95 0 obj << +/Title 96 0 R +/A 93 0 R +/Parent 87 0 R +/Prev 91 0 R +/Next 99 0 R +>> endobj +91 0 obj << +/Title 92 0 R +/A 89 0 R +/Parent 87 0 R +/Next 95 0 R +>> endobj +87 0 obj << +/Title 88 0 R +/A 85 0 R +/Parent 83 0 R +/Next 107 0 R +/First 91 0 R +/Last 99 0 R +/Count -3 +>> endobj +83 0 obj << +/Title 84 0 R +/A 81 0 R +/Parent 3770 0 R +/Prev 7 0 R +/Next 295 0 R +/First 87 0 R +/Last 283 0 R +/Count -6 +>> endobj +79 0 obj << +/Title 80 0 R +/A 77 0 R +/Parent 43 0 R +/Prev 75 0 R +>> endobj +75 0 obj << +/Title 76 0 R +/A 73 0 R +/Parent 43 0 R +/Prev 71 0 R +/Next 79 0 R +>> endobj +71 0 obj << +/Title 72 0 R +/A 69 0 R +/Parent 43 0 R +/Prev 67 0 R +/Next 75 0 R +>> endobj +67 0 obj << +/Title 68 0 R +/A 65 0 R +/Parent 43 0 R +/Prev 51 0 R +/Next 71 0 R +>> endobj +63 0 obj << +/Title 64 0 R +/A 61 0 R +/Parent 51 0 R +/Prev 55 0 R +>> endobj +59 0 obj << +/Title 60 0 R +/A 57 0 R +/Parent 55 0 R +>> endobj +55 0 obj << +/Title 56 0 R +/A 53 0 R +/Parent 51 0 R +/Next 63 0 R +/First 59 0 R +/Last 59 0 R +/Count -1 +>> endobj +51 0 obj << +/Title 52 0 R +/A 49 0 R +/Parent 43 0 R +/Prev 47 0 R +/Next 67 0 R +/First 55 0 R +/Last 63 0 R +/Count -2 +>> endobj +47 0 obj << +/Title 48 0 R +/A 45 0 R +/Parent 43 0 R +/Next 51 0 R +>> endobj +43 0 obj << +/Title 44 0 R +/A 41 0 R +/Parent 7 0 R +/Prev 11 0 R +/First 47 0 R +/Last 79 0 R +/Count -6 +>> endobj +39 0 obj << +/Title 40 0 R +/A 37 0 R +/Parent 11 0 R +/Prev 35 0 R +>> endobj +35 0 obj << +/Title 36 0 R +/A 33 0 R +/Parent 11 0 R +/Prev 31 0 R +/Next 39 0 R +>> endobj +31 0 obj << +/Title 32 0 R +/A 29 0 R +/Parent 11 0 R +/Prev 27 0 R +/Next 35 0 R +>> endobj +27 0 obj << +/Title 28 0 R +/A 25 0 R +/Parent 11 0 R +/Prev 23 0 R +/Next 31 0 R +>> endobj +23 0 obj << +/Title 24 0 R +/A 21 0 R +/Parent 11 0 R +/Prev 19 0 R +/Next 27 0 R +>> endobj +19 0 obj << +/Title 20 0 R +/A 17 0 R +/Parent 11 0 R +/Prev 15 0 R +/Next 23 0 R +>> endobj +15 0 obj << +/Title 16 0 R +/A 13 0 R +/Parent 11 0 R +/Next 19 0 R +>> endobj +11 0 obj << +/Title 12 0 R +/A 9 0 R +/Parent 7 0 R +/Next 43 0 R +/First 15 0 R +/Last 39 0 R +/Count -7 +>> endobj +7 0 obj << +/Title 8 0 R +/A 5 0 R +/Parent 3770 0 R +/Next 83 0 R +/First 11 0 R +/Last 43 0 R +/Count -2 +>> endobj +3771 0 obj << +/Names [(ADS) 2330 0 R (AdvancedNetworkManagement) 2976 0 R (Appendixes) 3488 0 R (CUPS-printing) 2733 0 R (Doc-Start) 1614 0 R (InterdomainTrusts) 3159 0 R (IntroSMB) 2096 0 R (Item.1) 2190 0 R (Item.10) 2294 0 R (Item.100) 3578 0 R (Item.101) 3579 0 R (Item.102) 3584 0 R (Item.103) 3585 0 R (Item.104) 3666 0 R (Item.105) 3667 0 R (Item.106) 3668 0 R (Item.107) 3669 0 R (Item.108) 3670 0 R (Item.11) 2295 0 R (Item.12) 2296 0 R (Item.13) 2410 0 R (Item.14) 2411 0 R (Item.15) 2412 0 R (Item.16) 2417 0 R (Item.17) 2475 0 R (Item.18) 2476 0 R (Item.19) 2477 0 R (Item.2) 2191 0 R (Item.20) 2625 0 R (Item.21) 2626 0 R (Item.22) 2627 0 R (Item.23) 2707 0 R (Item.24) 2708 0 R (Item.25) 2709 0 R (Item.26) 2710 0 R (Item.27) 2711 0 R (Item.28) 2712 0 R (Item.29) 2713 0 R (Item.3) 2238 0 R (Item.30) 2714 0 R (Item.31) 2980 0 R (Item.32) 2981 0 R (Item.33) 2987 0 R (Item.34) 2988 0 R (Item.35) 2989 0 R (Item.36) 3031 0 R (Item.37) 3032 0 R (Item.38) 3033 0 R (Item.39) 3034 0 R (Item.4) 2239 0 R (Item.40) 3047 0 R (Item.41) 3048 0 R (Item.42) 3049 0 R (Item.43) 3050 0 R (Item.44) 3051 0 R (Item.45) 3052 0 R (Item.46) 3053 0 R (Item.47) 3054 0 R (Item.48) 3055 0 R (Item.49) 3078 0 R (Item.5) 2240 0 R (Item.50) 3079 0 R (Item.51) 3084 0 R (Item.52) 3085 0 R (Item.53) 3086 0 R (Item.54) 3087 0 R (Item.55) 3092 0 R (Item.56) 3093 0 R (Item.57) 3133 0 R (Item.58) 3134 0 R (Item.59) 3135 0 R (Item.6) 2290 0 R (Item.60) 3136 0 R (Item.61) 3393 0 R (Item.62) 3394 0 R (Item.63) 3395 0 R (Item.64) 3400 0 R (Item.65) 3405 0 R (Item.66) 3406 0 R (Item.67) 3407 0 R (Item.68) 3408 0 R (Item.69) 3409 0 R (Item.7) 2291 0 R (Item.70) 3410 0 R (Item.71) 3411 0 R (Item.72) 3412 0 R (Item.73) 3413 0 R (Item.74) 3418 0 R (Item.75) 3419 0 R (Item.76) 3420 0 R (Item.77) 3421 0 R (Item.78) 3422 0 R (Item.79) 3423 0 R (Item.8) 2292 0 R (Item.80) 3424 0 R (Item.81) 3500 0 R (Item.82) 3506 0 R (Item.83) 3507 0 R (Item.84) 3508 0 R (Item.85) 3563 0 R (Item.86) 3564 0 R (Item.87) 3565 0 R (Item.88) 3566 0 R (Item.89) 3567 0 R (Item.9) 2293 0 R (Item.90) 3568 0 R (Item.91) 3569 0 R (Item.92) 3570 0 R (Item.93) 3571 0 R (Item.94) 3572 0 R (Item.95) 3573 0 R (Item.96) 3574 0 R (Item.97) 3575 0 R (Item.98) 3576 0 R (Item.99) 3577 0 R (NT4Migration) 3541 0 R (NetworkBrowsing) 2379 0 R (Other-Clients) 3627 0 R (PolicyMgmt) 3014 0 R (Portability) 3606 0 R (ProfileMgmt) 3060 0 R (SWAT) 3684 0 R (ServerType) 2174 0 R (VFS) 3215 0 R (ads-create-machine-account) 2341 0 R (ads-test-server) 2343 0 R (ads-test-smbclient) 2344 0 R (browse-force-master) 2404 0 R (bugreport) 3466 0 R (chapter*.1) 1648 0 R (chapter.1) 10 0 R (chapter.10) 394 0 R (chapter.11) 498 0 R (chapter.12) 538 0 R (chapter.13) 542 0 R (chapter.14) 634 0 R (chapter.15) 694 0 R (chapter.16) 798 0 R (chapter.17) 830 0 R (chapter.18) 874 0 R (chapter.19) 970 0 R (chapter.2) 42 0 R (chapter.20) 1002 0 R (chapter.21) 1038 0 R (chapter.22) 1078 0 R (chapter.23) 1090 0 R (chapter.24) 1138 0 R (chapter.25) 1170 0 R (chapter.26) 1190 0 R (chapter.27) 1226 0 R (chapter.28) 1246 0 R (chapter.29) 1270 0 R (chapter.3) 86 0 R (chapter.30) 1302 0 R (chapter.31) 1362 0 R (chapter.32) 1410 0 R (chapter.33) 1450 0 R (chapter.34) 1522 0 R (chapter.35) 1570 0 R (chapter.4) 106 0 R (chapter.5) 146 0 R (chapter.6) 210 0 R (chapter.7) 250 0 R (chapter.8) 282 0 R (chapter.9) 298 0 R (compiling) 2146 0 R (diagnosis) 2163 0 R (domain-member) 2278 0 R (groupmapping) 2624 0 R (id2733677) 2115 0 R (id2733814) 2109 0 R (id2733867) 2143 0 R (id2733970) 2139 0 R (id2733997) 2142 0 R (id2736665) 3190 0 R (id2736726) 3197 0 R (id2736835) 3202 0 R (id2736861) 3203 0 R (id2738692) 2131 0 R (id2738754) 2100 0 R (id2738812) 2101 0 R (id2738964) 2133 0 R (id2739101) 2175 0 R (id2788270) 3216 0 R (id2788445) 3180 0 R (id2788527) 2114 0 R (id2802059) 2145 0 R (id2802112) 2152 0 R (id2802151) 2153 0 R (id2802202) 2154 0 R (id2802305) 2155 0 R (id2802366) 2159 0 R (id2802412) 2188 0 R (id2802434) 2189 0 R (id2802598) 2176 0 R (id2802639) 2181 0 R (id2802654) 2182 0 R (id2802780) 2232 0 R (id2802804) 2233 0 R (id2802916) 2192 0 R (id2802970) 2198 0 R (id2803054) 2208 0 R (id2803230) 2216 0 R (id2803291) 2222 0 R (id2803311) 2223 0 R (id2803429) 2225 0 R (id2803493) 2309 0 R (id2803553) 2310 0 R (id2803565) 2307 0 R (id2803758) 2241 0 R (id2804059) 2252 0 R (id2804328) 2258 0 R (id2804562) 2266 0 R (id2804618) 2268 0 R (id2804725) 2274 0 R (id2804732) 2275 0 R (id2804770) 2276 0 R (id2804817) 2277 0 R (id2804868) 2283 0 R (id2804917) 2284 0 R (id2804942) 2285 0 R (id2805105) 2297 0 R (id2805216) 2331 0 R (id2805383) 2316 0 R (id2805407) 2317 0 R (id2805426) 2318 0 R (id2805460) 2319 0 R (id2805556) 2324 0 R (id2805585) 2325 0 R (id2805609) 2354 0 R (id2805766) 2332 0 R (id2805960) 2342 0 R (id2806114) 2349 0 R (id2806191) 2380 0 R (id2806514) 2365 0 R (id2806782) 2432 0 R (id2806842) 2385 0 R (id2807004) 2390 0 R (id2807131) 2395 0 R (id2807320) 2401 0 R (id2807585) 2409 0 R (id2807734) 2418 0 R (id2807751) 2419 0 R (id2807780) 2420 0 R (id2807891) 2421 0 R (id2807958) 2427 0 R (id2808132) 2591 0 R (id2808250) 2590 0 R (id2808414) 2436 0 R (id2808439) 2441 0 R (id2808469) 2442 0 R (id2808483) 2443 0 R (id2808550) 2444 0 R (id2808665) 2450 0 R (id2808712) 2455 0 R (id2808819) 2456 0 R (id2808899) 2461 0 R (id2808950) 2462 0 R (id2809295) 2483 0 R (id2809348) 2484 0 R (id2809510) 2493 0 R (id2809549) 2494 0 R (id2809583) 2495 0 R (id2809764) 2500 0 R (id2809793) 2501 0 R (id2809809) 2502 0 R (id2809816) 2503 0 R (id2809917) 2509 0 R (id2810056) 2517 0 R (id2810094) 2521 0 R (id2810204) 2527 0 R (id2810212) 2528 0 R (id2810329) 2534 0 R (id2810500) 2549 0 R (id2810537) 2550 0 R (id2810652) 2556 0 R (id2810932) 2565 0 R (id2810989) 2570 0 R (id2810996) 2571 0 R (id2811050) 2572 0 R (id2811195) 2582 0 R (id2811224) 2583 0 R (id2811268) 2584 0 R (id2811476) 2592 0 R (id2811597) 2597 0 R (id2811679) 2598 0 R (id2811783) 2599 0 R (id2811833) 2604 0 R (id2811992) 2605 0 R (id2812308) 2614 0 R (id2812430) 2680 0 R (id2812456) 2682 0 R (id2812535) 2694 0 R (id2812542) 2695 0 R (id2812694) 2637 0 R (id2812810) 2641 0 R (id2812857) 2646 0 R (id2813089) 2657 0 R (id2813187) 2662 0 R (id2813295) 2669 0 R (id2813427) 2678 0 R (id2813530) 2687 0 R (id2813550) 2688 0 R (id2813574) 2689 0 R (id2813747) 2700 0 R (id2813814) 2705 0 R (id2813856) 2706 0 R (id2813990) 2720 0 R (id2814213) 2734 0 R (id2814271) 2736 0 R (id2814297) 2755 0 R (id2814539) 2721 0 R (id2814615) 2726 0 R (id2814634) 2727 0 R (id2814659) 2728 0 R (id2814803) 2741 0 R (id2815273) 2882 0 R (id2815303) 2883 0 R (id2815332) 2884 0 R (id2815366) 2890 0 R (id2815389) 2891 0 R (id2815469) 2760 0 R (id2815510) 2761 0 R (id2815597) 2766 0 R (id2815763) 2777 0 R (id2816112) 2786 0 R (id2816498) 2817 0 R (id2816535) 2818 0 R (id2816954) 2837 0 R (id2817563) 2861 0 R (id2817669) 2866 0 R (id2817911) 2875 0 R (id2817939) 2876 0 R (id2818011) 2877 0 R (id2818101) 2978 0 R (id2818115) 2979 0 R (id2818167) 2990 0 R (id2818250) 2999 0 R (id2818334) 2977 0 R (id2818477) 2892 0 R (id2818549) 2897 0 R (id2818583) 2898 0 R (id2818611) 2899 0 R (id2818639) 2901 0 R (id2818714) 2906 0 R (id2818808) 2911 0 R (id2818885) 2916 0 R (id2819005) 2917 0 R (id2819210) 2918 0 R (id2819283) 2923 0 R (id2819398) 2924 0 R (id2819455) 2925 0 R (id2819700) 2935 0 R (id2819708) 2937 0 R (id2819844) 2943 0 R (id2819945) 2951 0 R (id2819982) 2952 0 R (id2820091) 2954 0 R (id2820315) 2964 0 R (id2820406) 2969 0 R (id2820461) 2970 0 R (id2820524) 2982 0 R (id2820685) 3062 0 R (id2820699) 3063 0 R (id2820796) 3061 0 R (id2820871) 3015 0 R (id2821084) 3005 0 R (id2821122) 3017 0 R (id2821211) 3023 0 R (id2821313) 3024 0 R (id2821336) 3025 0 R (id2821434) 3030 0 R (id2821541) 3039 0 R (id2821654) 3040 0 R (id2821674) 3045 0 R (id2821699) 3046 0 R (id2821880) 3160 0 R (id2822021) 3068 0 R (id2822117) 3069 0 R (id2822156) 3070 0 R (id2822276) 3076 0 R (id2822284) 3077 0 R (id2822555) 3094 0 R (id2822622) 3095 0 R (id2822892) 3108 0 R (id2822938) 3109 0 R (id2822956) 3110 0 R (id2823049) 3116 0 R (id2823071) 3117 0 R (id2823087) 3118 0 R (id2823121) 3119 0 R (id2823166) 3120 0 R (id2823208) 3125 0 R (id2823237) 3126 0 R (id2823276) 3127 0 R (id2823326) 3132 0 R (id2823710) 3145 0 R (id2824202) 3165 0 R (id2824215) 3166 0 R (id2824259) 3167 0 R (id2824283) 3168 0 R (id2824310) 3169 0 R (id2824406) 3174 0 R (id2825175) 3208 0 R (id2825208) 3209 0 R (id2825244) 3210 0 R (id2825412) 3244 0 R (id2825446) 3217 0 R (id2825454) 3218 0 R (id2825492) 3219 0 R (id2825530) 3224 0 R (id2825613) 3226 0 R (id2825751) 3227 0 R (id2825790) 3228 0 R (id2825812) 3234 0 R (id2825867) 3237 0 R (id2825942) 3259 0 R (id2826159) 3253 0 R (id2826228) 3282 0 R (id2826267) 3283 0 R (id2826310) 3292 0 R (id2826342) 3293 0 R (id2826354) 3294 0 R (id2826376) 3264 0 R (id2826514) 3265 0 R (id2826558) 3270 0 R (id2826601) 3271 0 R (id2826696) 3277 0 R (id2826803) 3303 0 R (id2826819) 3304 0 R (id2826920) 3313 0 R (id2826957) 3318 0 R (id2827268) 3305 0 R (id2827319) 3311 0 R (id2827361) 3312 0 R (id2827407) 3341 0 R (id2827556) 3325 0 R (id2827625) 3327 0 R (id2827715) 3328 0 R (id2827760) 3333 0 R (id2827902) 3385 0 R (id2827936) 3386 0 R (id2828069) 3342 0 R (id2828185) 3347 0 R (id2828409) 3357 0 R (id2828437) 3362 0 R (id2828517) 3363 0 R (id2828547) 3368 0 R (id2828675) 3435 0 R (id2828941) 3392 0 R (id2830051) 3429 0 R (id2830124) 3470 0 R (id2830215) 3467 0 R (id2830292) 3438 0 R (id2830434) 3444 0 R (id2830540) 3456 0 R (id2830694) 3459 0 R (id2830752) 3719 0 R (id2830777) 3490 0 R (id2830784) 3491 0 R (id2830817) 3494 0 R (id2830833) 3495 0 R (id2830910) 3472 0 R (id2831046) 3477 0 R (id2831139) 3478 0 R (id2831186) 3479 0 R (id2831225) 3543 0 R (id2831355) 3542 0 R (id2831397) 3497 0 R (id2831574) 3509 0 R (id2831615) 3513 0 R (id2831698) 3518 0 R (id2831835) 3519 0 R (id2831902) 3524 0 R (id2831933) 3525 0 R (id2831983) 3526 0 R (id2832050) 3527 0 R (id2832242) 3532 0 R (id2832373) 3608 0 R (id2832396) 3609 0 R (id2832471) 3607 0 R (id2832694) 3549 0 R (id2832748) 3554 0 R (id2832809) 3555 0 R (id2832867) 3560 0 R (id2832897) 3561 0 R (id2832922) 3562 0 R (id2833177) 3586 0 R (id2833194) 3587 0 R (id2833259) 3589 0 R (id2833331) 3595 0 R (id2833501) 3590 0 R (id2833599) 3628 0 R (id2833868) 3614 0 R (id2833905) 3619 0 R (id2833912) 3620 0 R (id2833938) 3621 0 R (id2833945) 3622 0 R (id2834033) 3686 0 R (id2834156) 3685 0 R (id2834174) 3634 0 R (id2834180) 3635 0 R (id2834263) 3641 0 R (id2834323) 3645 0 R (id2834352) 3647 0 R (id2834415) 3648 0 R (id2834422) 3649 0 R (id2834454) 3654 0 R (id2834484) 3655 0 R (id2834510) 3656 0 R (id2834541) 3658 0 R (id2834558) 3659 0 R (id2834585) 3660 0 R (id2834655) 3671 0 R (id2834672) 3672 0 R (id2834782) 3678 0 R (id2834849) 3720 0 R (id2835070) 3691 0 R (id2835143) 3696 0 R (id2835207) 3698 0 R (id2835315) 3703 0 R (id2835364) 3704 0 R (id2835413) 3705 0 R (id2835458) 3706 0 R (id2835496) 3707 0 R (id2835513) 3713 0 R (id2835738) 3721 0 R (id2835781) 3726 0 R (id2835834) 3727 0 R (id2835857) 3728 0 R (id2835914) 3729 0 R (id2835956) 3730 0 R (id2835977) 3735 0 R (install) 2138 0 R (integrate-ms-networks) 3258 0 R (introduction) 2095 0 R (locking) 3340 0 R (msdfs) 3243 0 R (optional) 2378 0 R (page.1) 1613 0 R (page.10) 1940 0 R (page.100) 2765 0 R (page.101) 2776 0 R (page.102) 2781 0 R (page.103) 2785 0 R (page.104) 2791 0 R (page.105) 2795 0 R (page.106) 2799 0 R (page.107) 2803 0 R (page.108) 2807 0 R (page.109) 2811 0 R (page.11) 1990 0 R (page.110) 2816 0 R (page.111) 2825 0 R (page.112) 2834 0 R (page.113) 2841 0 R (page.114) 2845 0 R (page.115) 2851 0 R (page.116) 2856 0 R (page.117) 2860 0 R (page.118) 2865 0 R (page.119) 2870 0 R (page.12) 2040 0 R (page.120) 2874 0 R (page.121) 2881 0 R (page.122) 2889 0 R (page.123) 2896 0 R (page.124) 2905 0 R (page.125) 2915 0 R (page.126) 2922 0 R (page.127) 2929 0 R (page.128) 2934 0 R (page.129) 2941 0 R (page.13) 2089 0 R (page.130) 2949 0 R (page.131) 2958 0 R (page.132) 2962 0 R (page.133) 2968 0 R (page.134) 2975 0 R (page.135) 2986 0 R (page.136) 2998 0 R (page.137) 3004 0 R (page.138) 3009 0 R (page.139) 3013 0 R (page.14) 2094 0 R (page.140) 3022 0 R (page.141) 3029 0 R (page.142) 3038 0 R (page.143) 3044 0 R (page.144) 3059 0 R (page.145) 3067 0 R (page.146) 3075 0 R (page.147) 3083 0 R (page.148) 3091 0 R (page.149) 3099 0 R (page.15) 2108 0 R (page.150) 3103 0 R (page.151) 3107 0 R (page.152) 3115 0 R (page.153) 3124 0 R (page.154) 3131 0 R (page.155) 3140 0 R (page.156) 3144 0 R (page.157) 3149 0 R (page.158) 3154 0 R (page.159) 3158 0 R (page.16) 2113 0 R (page.160) 3164 0 R (page.161) 3173 0 R (page.162) 3178 0 R (page.163) 3184 0 R (page.164) 3189 0 R (page.165) 3196 0 R (page.166) 3201 0 R (page.167) 3207 0 R (page.168) 3214 0 R (page.169) 3223 0 R (page.17) 2121 0 R (page.170) 3233 0 R (page.171) 3242 0 R (page.172) 3252 0 R (page.173) 3257 0 R (page.174) 3263 0 R (page.175) 3269 0 R (page.176) 3276 0 R (page.177) 3281 0 R (page.178) 3287 0 R (page.179) 3291 0 R (page.18) 2137 0 R (page.180) 3298 0 R (page.181) 3302 0 R (page.182) 3310 0 R (page.183) 3317 0 R (page.184) 3323 0 R (page.185) 3332 0 R (page.186) 3339 0 R (page.187) 3346 0 R (page.188) 3352 0 R (page.189) 3356 0 R (page.19) 2151 0 R (page.190) 3361 0 R (page.191) 3367 0 R (page.192) 3379 0 R (page.193) 3383 0 R (page.194) 3391 0 R (page.195) 3399 0 R (page.196) 3404 0 R (page.197) 3417 0 R (page.198) 3428 0 R (page.199) 3434 0 R (page.2) 1625 0 R (page.20) 2168 0 R (page.200) 3443 0 R (page.201) 3455 0 R (page.202) 3465 0 R (page.203) 3476 0 R (page.204) 3483 0 R (page.205) 3487 0 R (page.206) 3505 0 R (page.207) 3517 0 R (page.208) 3523 0 R (page.209) 3531 0 R (page.21) 2172 0 R (page.210) 3536 0 R (page.211) 3540 0 R (page.212) 3548 0 R (page.213) 3553 0 R (page.214) 3559 0 R (page.215) 3583 0 R (page.216) 3594 0 R (page.217) 3600 0 R (page.218) 3605 0 R (page.219) 3613 0 R (page.22) 2180 0 R (page.220) 3618 0 R (page.221) 3626 0 R (page.222) 3640 0 R (page.223) 3653 0 R (page.224) 3665 0 R (page.225) 3677 0 R (page.226) 3683 0 R (page.227) 3690 0 R (page.228) 3695 0 R (page.229) 3702 0 R (page.23) 2186 0 R (page.230) 3712 0 R (page.231) 3717 0 R (page.232) 3725 0 R (page.233) 3734 0 R (page.24) 2197 0 R (page.25) 2215 0 R (page.26) 2221 0 R (page.27) 2230 0 R (page.28) 2237 0 R (page.29) 2245 0 R (page.3) 1639 0 R (page.30) 2251 0 R (page.31) 2257 0 R (page.32) 2265 0 R (page.33) 2272 0 R (page.34) 2282 0 R (page.35) 2289 0 R (page.36) 2301 0 R (page.37) 2305 0 R (page.38) 2315 0 R (page.39) 2323 0 R (page.4) 1647 0 R (page.40) 2329 0 R (page.41) 2336 0 R (page.42) 2348 0 R (page.43) 2353 0 R (page.44) 2364 0 R (page.45) 2373 0 R (page.46) 2377 0 R (page.47) 2384 0 R (page.48) 2389 0 R (page.49) 2394 0 R (page.5) 1686 0 R (page.50) 2400 0 R (page.51) 2408 0 R (page.52) 2416 0 R (page.53) 2426 0 R (page.54) 2431 0 R (page.55) 2440 0 R (page.56) 2449 0 R (page.57) 2454 0 R (page.58) 2460 0 R (page.59) 2466 0 R (page.6) 1732 0 R (page.60) 2470 0 R (page.61) 2474 0 R (page.62) 2482 0 R (page.63) 2488 0 R (page.64) 2492 0 R (page.65) 2499 0 R (page.66) 2514 0 R (page.67) 2526 0 R (page.68) 2533 0 R (page.69) 2548 0 R (page.7) 1786 0 R (page.70) 2555 0 R (page.71) 2560 0 R (page.72) 2569 0 R (page.73) 2576 0 R (page.74) 2581 0 R (page.75) 2588 0 R (page.76) 2596 0 R (page.77) 2603 0 R (page.78) 2609 0 R (page.79) 2618 0 R (page.8) 1840 0 R (page.80) 2623 0 R (page.81) 2631 0 R (page.82) 2635 0 R (page.83) 2645 0 R (page.84) 2655 0 R (page.85) 2661 0 R (page.86) 2668 0 R (page.87) 2677 0 R (page.88) 2686 0 R (page.89) 2693 0 R (page.9) 1889 0 R (page.90) 2699 0 R (page.91) 2704 0 R (page.92) 2719 0 R (page.93) 2725 0 R (page.94) 2732 0 R (page.95) 2740 0 R (page.96) 2745 0 R (page.97) 2749 0 R (page.98) 2754 0 R (page.99) 2759 0 R (pam) 3179 0 R (part.1) 6 0 R (part.2) 82 0 R (part.3) 294 0 R (part.4) 1222 0 R (part.5) 1298 0 R (passdb) 2247 0 R (printing) 2636 0 R (problems) 2164 0 R (samba-bdc) 2306 0 R (samba-pdc) 2231 0 R (section*.2) 2936 0 R (section*.3) 2942 0 R (section*.4) 2950 0 R (section*.5) 2953 0 R (section*.6) 2963 0 R (section.1.1) 14 0 R (section.1.2) 18 0 R (section.1.3) 22 0 R (section.1.4) 26 0 R (section.1.5) 30 0 R (section.1.6) 34 0 R (section.1.7) 38 0 R (section.10.1) 398 0 R (section.10.2) 402 0 R (section.10.3) 414 0 R (section.10.4) 418 0 R (section.10.5) 422 0 R (section.10.6) 426 0 R (section.10.7) 474 0 R (section.10.8) 494 0 R (section.11.1) 502 0 R (section.11.2) 506 0 R (section.11.3) 510 0 R (section.11.4) 514 0 R (section.11.5) 526 0 R (section.11.6) 530 0 R (section.11.7) 534 0 R (section.13.1) 546 0 R (section.13.2) 550 0 R (section.13.3) 574 0 R (section.13.4) 594 0 R (section.14.1) 638 0 R (section.14.10) 682 0 R (section.14.11) 686 0 R (section.14.12) 690 0 R (section.14.2) 642 0 R (section.14.3) 646 0 R (section.14.4) 650 0 R (section.14.5) 654 0 R (section.14.6) 658 0 R (section.14.7) 662 0 R (section.14.8) 670 0 R (section.14.9) 674 0 R (section.15.1) 698 0 R (section.15.2) 702 0 R (section.15.3) 706 0 R (section.15.4) 714 0 R (section.15.5) 742 0 R (section.15.6) 790 0 R (section.15.7) 794 0 R (section.16.1) 802 0 R (section.16.2) 818 0 R (section.16.3) 822 0 R (section.17.1) 834 0 R (section.17.2) 858 0 R (section.17.3) 870 0 R (section.18.1) 878 0 R (section.18.2) 942 0 R (section.18.3) 946 0 R (section.18.4) 950 0 R (section.19.1) 974 0 R (section.19.2) 978 0 R (section.19.3) 990 0 R (section.2.1) 46 0 R (section.2.2) 50 0 R (section.2.3) 66 0 R (section.2.4) 70 0 R (section.2.5) 74 0 R (section.2.6) 78 0 R (section.20.1) 1006 0 R (section.20.2) 1034 0 R (section.21.1) 1042 0 R (section.21.2) 1046 0 R (section.21.3) 1066 0 R (section.22.1) 1082 0 R (section.23.1) 1094 0 R (section.23.2) 1114 0 R (section.24.1) 1142 0 R (section.24.2) 1146 0 R (section.24.3) 1150 0 R (section.24.4) 1154 0 R (section.24.5) 1158 0 R (section.24.6) 1162 0 R (section.24.7) 1166 0 R (section.25.1) 1174 0 R (section.25.2) 1178 0 R (section.25.3) 1182 0 R (section.25.4) 1186 0 R (section.26.1) 1194 0 R (section.26.2) 1198 0 R (section.26.3) 1202 0 R (section.26.4) 1214 0 R (section.26.5) 1218 0 R (section.27.1) 1230 0 R (section.27.2) 1234 0 R (section.27.3) 1238 0 R (section.27.4) 1242 0 R (section.28.1) 1250 0 R (section.28.2) 1254 0 R (section.28.3) 1258 0 R (section.28.4) 1262 0 R (section.28.5) 1266 0 R (section.29.1) 1274 0 R (section.29.2) 1278 0 R (section.29.3) 1282 0 R (section.29.4) 1286 0 R (section.29.5) 1290 0 R (section.29.6) 1294 0 R (section.3.1) 90 0 R (section.3.2) 94 0 R (section.3.3) 98 0 R (section.30.1) 1306 0 R (section.30.2) 1326 0 R (section.30.3) 1330 0 R (section.30.4) 1334 0 R (section.30.5) 1350 0 R (section.31.1) 1366 0 R (section.31.2) 1398 0 R (section.32.1) 1414 0 R (section.32.2) 1418 0 R (section.32.3) 1422 0 R (section.32.4) 1426 0 R (section.32.5) 1430 0 R (section.32.6) 1438 0 R (section.33.1) 1454 0 R (section.33.2) 1458 0 R (section.33.3) 1478 0 R (section.33.4) 1506 0 R (section.33.5) 1514 0 R (section.33.6) 1518 0 R (section.34.1) 1526 0 R (section.35.1) 1574 0 R (section.35.2) 1578 0 R (section.35.3) 1582 0 R (section.35.4) 1586 0 R (section.35.5) 1590 0 R (section.35.6) 1594 0 R (section.35.7) 1598 0 R (section.35.8) 1602 0 R (section.35.9) 1606 0 R (section.4.1) 110 0 R (section.5.1) 150 0 R (section.5.2) 154 0 R (section.5.3) 158 0 R (section.5.4) 162 0 R (section.5.5) 178 0 R (section.5.6) 202 0 R (section.6.1) 214 0 R (section.6.2) 218 0 R (section.6.3) 222 0 R (section.6.4) 234 0 R (section.6.5) 238 0 R (section.7.1) 254 0 R (section.7.2) 258 0 R (section.7.3) 262 0 R (section.7.4) 270 0 R (section.7.5) 274 0 R (section.7.6) 278 0 R (section.8.1) 286 0 R (section.8.2) 290 0 R (section.9.1) 302 0 R (section.9.2) 306 0 R (section.9.3) 310 0 R (section.9.4) 346 0 R (section.9.5) 362 0 R (section.9.6) 374 0 R (securing-samba) 2147 0 R (securitylevels) 2187 0 R (speed) 3718 0 R (subsection.10.2.1) 406 0 R (subsection.10.2.2) 410 0 R (subsection.10.6.1) 430 0 R (subsection.10.6.2) 434 0 R (subsection.10.6.3) 438 0 R (subsection.10.6.4) 442 0 R (subsection.10.6.5) 446 0 R (subsection.10.6.6) 458 0 R (subsection.10.6.7) 462 0 R (subsection.10.6.8) 466 0 R (subsection.10.6.9) 470 0 R (subsection.10.7.1) 478 0 R (subsection.10.7.2) 482 0 R (subsection.10.7.3) 486 0 R (subsection.10.7.4) 490 0 R (subsection.11.4.1) 518 0 R (subsection.11.4.2) 522 0 R (subsection.13.2.1) 554 0 R (subsection.13.2.2) 558 0 R (subsection.13.2.3) 562 0 R (subsection.13.2.4) 566 0 R (subsection.13.2.5) 570 0 R (subsection.13.3.1) 578 0 R (subsection.13.3.2) 582 0 R (subsection.13.3.3) 586 0 R (subsection.13.3.4) 590 0 R (subsection.13.4.1) 598 0 R (subsection.13.4.2) 602 0 R (subsection.13.4.3) 606 0 R (subsection.13.4.4) 610 0 R (subsection.13.4.5) 614 0 R (subsection.13.4.6) 618 0 R (subsection.13.4.7) 622 0 R (subsection.13.4.8) 626 0 R (subsection.13.4.9) 630 0 R (subsection.14.7.1) 666 0 R (subsection.14.9.1) 678 0 R (subsection.15.3.1) 710 0 R (subsection.15.4.1) 718 0 R (subsection.15.4.2) 722 0 R (subsection.15.4.3) 726 0 R (subsection.15.4.4) 730 0 R (subsection.15.4.5) 734 0 R (subsection.15.4.6) 738 0 R (subsection.15.5.1) 746 0 R (subsection.15.5.2) 750 0 R (subsection.15.5.3) 754 0 R (subsection.16.1.1) 806 0 R (subsection.16.3.1) 826 0 R (subsection.17.1.1) 838 0 R (subsection.17.1.2) 842 0 R (subsection.17.1.3) 850 0 R (subsection.17.2.1) 862 0 R (subsection.17.2.2) 866 0 R (subsection.18.1.1) 882 0 R (subsection.18.1.2) 902 0 R (subsection.18.1.3) 918 0 R (subsection.18.1.4) 922 0 R (subsection.18.4.1) 954 0 R (subsection.18.4.2) 962 0 R (subsection.18.4.3) 966 0 R (subsection.19.2.1) 982 0 R (subsection.19.2.2) 986 0 R (subsection.19.3.1) 994 0 R (subsection.19.3.2) 998 0 R (subsection.2.2.1) 54 0 R (subsection.2.2.2) 62 0 R (subsection.20.1.1) 1010 0 R (subsection.20.1.2) 1014 0 R (subsection.21.2.1) 1050 0 R (subsection.21.2.2) 1054 0 R (subsection.21.2.3) 1058 0 R (subsection.21.2.4) 1062 0 R (subsection.21.3.1) 1070 0 R (subsection.21.3.2) 1074 0 R (subsection.22.1.1) 1086 0 R (subsection.23.1.1) 1098 0 R (subsection.23.1.2) 1102 0 R (subsection.23.1.3) 1106 0 R (subsection.23.1.4) 1110 0 R (subsection.23.2.1) 1118 0 R (subsection.23.2.2) 1122 0 R (subsection.23.2.3) 1126 0 R (subsection.23.2.4) 1130 0 R (subsection.23.2.5) 1134 0 R (subsection.26.3.1) 1206 0 R (subsection.26.3.2) 1210 0 R (subsection.3.3.1) 102 0 R (subsection.30.1.1) 1310 0 R (subsection.30.1.2) 1314 0 R (subsection.30.4.1) 1338 0 R (subsection.30.5.1) 1354 0 R (subsection.30.5.2) 1358 0 R (subsection.31.1.1) 1370 0 R (subsection.31.1.2) 1394 0 R (subsection.31.2.1) 1402 0 R (subsection.31.2.2) 1406 0 R (subsection.32.5.1) 1434 0 R (subsection.32.6.1) 1442 0 R (subsection.32.6.2) 1446 0 R (subsection.33.2.1) 1462 0 R (subsection.33.2.2) 1466 0 R (subsection.33.2.3) 1470 0 R (subsection.33.2.4) 1474 0 R (subsection.33.3.1) 1482 0 R (subsection.33.3.2) 1486 0 R (subsection.33.3.3) 1490 0 R (subsection.33.3.4) 1494 0 R (subsection.33.3.5) 1498 0 R (subsection.33.3.6) 1502 0 R (subsection.33.4.1) 1510 0 R (subsection.34.1.1) 1530 0 R (subsection.34.1.10) 1566 0 R (subsection.34.1.2) 1534 0 R (subsection.34.1.3) 1538 0 R (subsection.34.1.4) 1542 0 R (subsection.34.1.5) 1546 0 R (subsection.34.1.6) 1550 0 R (subsection.34.1.7) 1554 0 R (subsection.34.1.8) 1558 0 R (subsection.34.1.9) 1562 0 R (subsection.4.1.1) 114 0 R (subsection.4.1.2) 118 0 R (subsection.4.1.3) 122 0 R (subsection.4.1.4) 134 0 R (subsection.4.1.5) 142 0 R (subsection.5.4.1) 166 0 R (subsection.5.4.2) 170 0 R (subsection.5.4.3) 174 0 R (subsection.5.5.1) 182 0 R (subsection.5.5.2) 186 0 R (subsection.5.5.3) 190 0 R (subsection.5.5.4) 194 0 R (subsection.5.5.5) 198 0 R (subsection.5.6.1) 206 0 R (subsection.6.3.1) 226 0 R (subsection.6.3.2) 230 0 R (subsection.6.5.1) 242 0 R (subsection.6.5.2) 246 0 R (subsection.7.3.1) 266 0 R (subsection.9.3.1) 314 0 R (subsection.9.3.2) 318 0 R (subsection.9.3.3) 322 0 R (subsection.9.3.4) 326 0 R (subsection.9.3.5) 330 0 R (subsection.9.3.6) 334 0 R (subsection.9.3.7) 338 0 R (subsection.9.3.8) 342 0 R (subsection.9.4.1) 350 0 R (subsection.9.4.2) 354 0 R (subsection.9.4.3) 358 0 R (subsection.9.5.1) 366 0 R (subsection.9.5.2) 370 0 R (subsection.9.6.1) 378 0 R (subsection.9.6.2) 382 0 R (subsection.9.6.3) 386 0 R (subsubsection.10.6.5.1) 450 0 R (subsubsection.10.6.5.2) 454 0 R (subsubsection.15.5.3.1) 758 0 R (subsubsection.15.5.3.2) 762 0 R (subsubsection.15.5.3.3) 766 0 R (subsubsection.15.5.3.4) 770 0 R (subsubsection.15.5.3.5) 774 0 R (subsubsection.15.5.3.6) 778 0 R (subsubsection.15.5.3.7) 782 0 R (subsubsection.15.5.3.8) 786 0 R (subsubsection.16.1.1.1) 810 0 R (subsubsection.16.1.1.2) 814 0 R (subsubsection.17.1.2.1) 846 0 R (subsubsection.17.1.3.1) 854 0 R (subsubsection.18.1.1.1) 886 0 R (subsubsection.18.1.1.2) 890 0 R (subsubsection.18.1.1.3) 894 0 R (subsubsection.18.1.1.4) 898 0 R (subsubsection.18.1.2.1) 906 0 R (subsubsection.18.1.2.2) 910 0 R (subsubsection.18.1.2.3) 914 0 R (subsubsection.18.1.4.1) 926 0 R (subsubsection.18.1.4.2) 930 0 R (subsubsection.18.1.4.3) 934 0 R (subsubsection.18.1.4.4) 938 0 R (subsubsection.18.4.1.1) 958 0 R (subsubsection.2.2.1.1) 58 0 R (subsubsection.20.1.2.1) 1018 0 R (subsubsection.20.1.2.2) 1022 0 R (subsubsection.20.1.2.3) 1026 0 R (subsubsection.20.1.2.4) 1030 0 R (subsubsection.30.1.2.1) 1318 0 R (subsubsection.30.1.2.2) 1322 0 R (subsubsection.30.4.1.1) 1342 0 R (subsubsection.30.4.1.2) 1346 0 R (subsubsection.31.1.1.1) 1374 0 R (subsubsection.31.1.1.2) 1378 0 R (subsubsection.31.1.1.3) 1382 0 R (subsubsection.31.1.1.4) 1386 0 R (subsubsection.31.1.1.5) 1390 0 R (subsubsection.4.1.3.1) 126 0 R (subsubsection.4.1.3.2) 130 0 R (subsubsection.4.1.4.1) 138 0 R (subsubsection.9.6.3.1) 390 0 R (table.21.1) 3225 0 R (table.31.1) 3588 0 R (table.31.2) 3596 0 R (troubleshooting) 3384 0 R (type) 2173 0 R (unicode) 3324 0 R (unix-permissions) 2589 0 R (winbind) 2226 0 R (winbind-solaris9) 2945 0 R] +/Limits [(ADS) (winbind-solaris9)] +>> endobj +3772 0 obj << +/Kids [3771 0 R] +>> endobj +3773 0 obj << +/Dests 3772 0 R +>> endobj +3774 0 obj << +/Type /Catalog +/Pages 3769 0 R +/Outlines 3770 0 R +/Names 3773 0 R +/PageMode /UseOutlines /URI<> /ViewerPreferences<<>> +/OpenAction 1609 0 R +/PTEX.Fullbanner (This is pdfTeX, Version 3.14159-1.10a) +>> endobj +3775 0 obj << +/Producer (pdfTeX-1.10a) +/Author()/Title()/Subject()/Creator(LaTeX with hyperref package)/Producer(pdfTeX-1.10a)/Keywords() +/Creator (TeX) +/CreationDate (D:20030501010500) +>> endobj xref -0 2136 -0000000000 65535 f -0000000015 00000 n -0000000247 00000 n -0000001813 00000 n -0000001887 00000 n -0000001966 00000 n -0000002048 00000 n -0000002126 00000 n -0000002203 00000 n -0000002282 00000 n -0000002365 00000 n -0000002442 00000 n -0000002524 00000 n -0000002609 00000 n -0000002698 00000 n -0000002757 00000 n -0000003184 00000 n -0000003922 00000 n -0000004024 00000 n -0000004127 00000 n -0000004230 00000 n -0000004333 00000 n -0000004436 00000 n -0000004538 00000 n -0000004640 00000 n -0000004742 00000 n -0000004845 00000 n -0000004948 00000 n -0000005051 00000 n -0000005154 00000 n -0000005257 00000 n -0000005360 00000 n -0000005463 00000 n -0000005565 00000 n -0000005668 00000 n -0000005771 00000 n -0000005874 00000 n -0000005977 00000 n -0000006080 00000 n -0000006183 00000 n -0000006286 00000 n -0000006389 00000 n -0000006492 00000 n -0000006595 00000 n -0000006697 00000 n -0000006800 00000 n -0000006903 00000 n -0000007006 00000 n -0000007109 00000 n -0000007212 00000 n -0000007315 00000 n -0000007418 00000 n -0000007521 00000 n -0000007624 00000 n -0000007726 00000 n -0000007829 00000 n -0000007932 00000 n -0000008034 00000 n -0000008135 00000 n -0000008236 00000 n -0000008546 00000 n -0000008648 00000 n -0000008751 00000 n -0000008854 00000 n -0000008957 00000 n -0000009060 00000 n -0000009163 00000 n -0000009266 00000 n -0000009369 00000 n -0000009472 00000 n -0000009575 00000 n -0000009678 00000 n -0000009781 00000 n -0000009884 00000 n -0000009987 00000 n -0000010090 00000 n -0000010193 00000 n -0000010296 00000 n -0000010399 00000 n -0000010502 00000 n -0000010604 00000 n -0000010706 00000 n -0000010808 00000 n -0000010911 00000 n -0000011014 00000 n -0000011117 00000 n -0000011220 00000 n -0000011322 00000 n -0000011425 00000 n -0000011528 00000 n -0000011631 00000 n -0000011734 00000 n -0000011837 00000 n -0000011940 00000 n -0000012042 00000 n -0000012145 00000 n -0000012248 00000 n -0000012351 00000 n -0000012454 00000 n -0000012557 00000 n -0000012660 00000 n -0000012763 00000 n -0000012865 00000 n -0000012967 00000 n -0000013288 00000 n -0000013391 00000 n -0000013495 00000 n -0000013599 00000 n -0000013703 00000 n -0000013807 00000 n -0000013911 00000 n -0000014015 00000 n -0000014119 00000 n -0000014223 00000 n -0000014327 00000 n +0 3776 +0000000001 65535 f +0000000002 00000 f +0000000003 00000 f +0000000004 00000 f +0000000000 00000 f +0000000009 00000 n +0000136457 00000 n +0001055067 00000 n +0000000051 00000 n +0000000091 00000 n +0000140279 00000 n +0001054958 00000 n +0000000136 00000 n +0000000178 00000 n +0000140403 00000 n +0001054884 00000 n +0000000226 00000 n +0000000259 00000 n +0000140526 00000 n +0001054797 00000 n +0000000307 00000 n +0000000341 00000 n +0000144468 00000 n +0001054710 00000 n +0000000389 00000 n +0000000428 00000 n +0000148740 00000 n +0001054623 00000 n +0000000476 00000 n +0000000514 00000 n +0000148864 00000 n +0001054536 00000 n +0000000562 00000 n +0000000605 00000 n +0000154611 00000 n +0001054449 00000 n +0000000653 00000 n +0000000684 00000 n +0000154735 00000 n +0001054375 00000 n +0000000732 00000 n +0000000768 00000 n +0000158156 00000 n +0001054265 00000 n +0000000814 00000 n +0000000864 00000 n +0000158280 00000 n +0001054191 00000 n +0000000912 00000 n +0000000965 00000 n +0000158403 00000 n +0001054067 00000 n +0000001013 00000 n +0000001053 00000 n +0000158527 00000 n +0001053956 00000 n +0000001106 00000 n +0000001156 00000 n +0000158651 00000 n +0001053895 00000 n +0000001214 00000 n +0000001276 00000 n +0000162385 00000 n +0001053821 00000 n +0000001329 00000 n +0000001358 00000 n +0000162509 00000 n +0001053734 00000 n +0000001406 00000 n +0000001476 00000 n +0000162632 00000 n +0001053647 00000 n +0000001524 00000 n +0000001582 00000 n +0000162756 00000 n +0001053560 00000 n +0000001630 00000 n +0000001726 00000 n +0000162880 00000 n +0001053486 00000 n +0000001774 00000 n +0000001823 00000 n +0000163666 00000 n +0001053359 00000 n +0000001866 00000 n +0000001915 00000 n +0000166659 00000 n +0001053247 00000 n +0000001961 00000 n +0000002010 00000 n +0000166783 00000 n +0001053173 00000 n +0000002058 00000 n +0000002099 00000 n +0000166907 00000 n +0001053086 00000 n +0000002147 00000 n +0000002190 00000 n +0000170588 00000 n +0001052972 00000 n +0000002238 00000 n +0000002279 00000 n +0000170711 00000 n +0001052908 00000 n +0000002333 00000 n +0000002382 00000 n +0000174048 00000 n +0001052778 00000 n +0000002429 00000 n +0000002478 00000 n +0000174173 00000 n +0001052674 00000 n +0000002527 00000 n +0000002580 00000 n +0000174298 00000 n +0001052595 00000 n +0000002634 00000 n +0000002679 00000 n +0000174547 00000 n +0001052502 00000 n +0000002733 00000 n +0000002779 00000 n +0000179862 00000 n +0001052370 00000 n +0000002833 00000 n +0000002880 00000 n +0000179987 00000 n +0001052291 00000 n +0000002939 00000 n +0000003025 00000 n +0000183593 00000 n +0001052212 00000 n +0000003084 00000 n +0000003157 00000 n +0000187287 00000 n +0001052080 00000 n +0000003211 00000 n +0000003258 00000 n +0000187411 00000 n +0001052015 00000 n +0000003317 00000 n +0000003398 00000 n +0000187536 00000 n +0001051936 00000 n +0000003452 00000 n +0000003496 00000 n +0000189919 00000 n +0001051805 00000 n +0000003543 00000 n +0000003615 00000 n +0000190044 00000 n +0001051726 00000 n +0000003664 00000 n +0000003708 00000 n +0000190169 00000 n +0001051633 00000 n +0000003757 00000 n +0000003791 00000 n +0000192905 00000 n +0001051540 00000 n +0000003840 00000 n +0000003903 00000 n +0000199218 00000 n +0001051408 00000 n +0000003952 00000 n +0000004041 00000 n +0000203306 00000 n +0001051329 00000 n +0000004095 00000 n +0000004162 00000 n +0000208020 00000 n +0001051236 00000 n +0000004216 00000 n +0000004289 00000 n +0000208145 00000 n +0001051157 00000 n +0000004343 00000 n +0000004401 00000 n +0000212003 00000 n +0001051025 00000 n +0000004450 00000 n +0000004500 00000 n +0000212128 00000 n +0001050946 00000 n +0000004554 00000 n +0000004623 00000 n +0000212253 00000 n +0001050853 00000 n +0000004677 00000 n +0000004884 00000 n +0000212377 00000 n +0001050760 00000 n +0000004938 00000 n +0000005010 00000 n +0000216554 00000 n +0001050667 00000 n +0000005064 00000 n +0000005177 00000 n +0000216679 00000 n +0001050588 00000 n +0000005231 00000 n +0000005375 00000 n +0000216802 00000 n +0001050470 00000 n +0000005424 00000 n +0000005480 00000 n +0000219993 00000 n +0001050405 00000 n +0000005534 00000 n +0000005602 00000 n +0000225948 00000 n +0001050274 00000 n +0000005649 00000 n +0000005725 00000 n +0000226073 00000 n +0001050195 00000 n +0000005774 00000 n +0000005818 00000 n +0000226198 00000 n +0001050102 00000 n +0000005867 00000 n +0000005901 00000 n +0000226321 00000 n +0001049970 00000 n +0000005950 00000 n +0000006024 00000 n +0000230057 00000 n +0001049891 00000 n +0000006078 00000 n +0000006154 00000 n +0000230182 00000 n +0001049812 00000 n +0000006208 00000 n +0000006257 00000 n +0000230306 00000 n +0001049719 00000 n +0000006306 00000 n +0000006383 00000 n +0000230431 00000 n +0001049601 00000 n +0000006432 00000 n +0000006484 00000 n +0000233419 00000 n +0001049522 00000 n +0000006538 00000 n +0000006602 00000 n +0000233544 00000 n +0001049443 00000 n +0000006656 00000 n +0000006710 00000 n +0000235680 00000 n +0001049312 00000 n +0000006757 00000 n +0000006807 00000 n +0000235805 00000 n +0001049233 00000 n +0000006856 00000 n +0000006899 00000 n +0000235930 00000 n +0001049140 00000 n +0000006948 00000 n +0000006997 00000 n +0000239806 00000 n +0001049008 00000 n +0000007046 00000 n +0000007097 00000 n +0000239931 00000 n +0001048943 00000 n +0000007151 00000 n +0000007192 00000 n +0000240056 00000 n +0001048850 00000 n +0000007241 00000 n +0000007287 00000 n +0000241845 00000 n +0001048757 00000 n +0000007336 00000 n +0000007382 00000 n +0000241970 00000 n +0001048678 00000 n +0000007431 00000 n +0000007460 00000 n +0000245879 00000 n +0001048561 00000 n +0000007507 00000 n +0000007566 00000 n +0000246004 00000 n +0001048482 00000 n +0000007615 00000 n +0000007674 00000 n +0000250585 00000 n +0001048403 00000 n +0000007723 00000 n +0000007789 00000 n +0000251412 00000 n +0001048268 00000 n +0000007833 00000 n +0000007879 00000 n +0000254100 00000 n +0001048150 00000 n +0000007926 00000 n +0000007989 00000 n +0000254225 00000 n +0001048071 00000 n +0000008038 00000 n +0000008079 00000 n +0000257406 00000 n +0001047978 00000 n +0000008128 00000 n +0000008162 00000 n +0000261767 00000 n +0001047846 00000 n +0000008211 00000 n +0000008257 00000 n +0000264971 00000 n +0001047767 00000 n +0000008311 00000 n +0000008366 00000 n +0000268280 00000 n +0001047674 00000 n +0000008420 00000 n +0000008472 00000 n +0000268404 00000 n +0001047581 00000 n +0000008526 00000 n +0000008582 00000 n +0000272543 00000 n +0001047488 00000 n +0000008636 00000 n +0000008692 00000 n +0000276057 00000 n +0001047395 00000 n +0000008746 00000 n +0000008802 00000 n +0000276181 00000 n +0001047302 00000 n +0000008856 00000 n +0000008901 00000 n +0000276306 00000 n +0001047209 00000 n +0000008955 00000 n +0000009017 00000 n +0000276431 00000 n +0001047130 00000 n +0000009071 00000 n +0000009136 00000 n +0000281296 00000 n +0001046998 00000 n +0000009185 00000 n +0000009255 00000 n +0000285270 00000 n +0001046919 00000 n +0000009309 00000 n +0000009359 00000 n +0000285395 00000 n +0001046826 00000 n +0000009413 00000 n +0000009455 00000 n +0000289012 00000 n +0001046747 00000 n +0000009509 00000 n +0000009554 00000 n +0000289137 00000 n +0001046615 00000 n +0000009603 00000 n +0000009640 00000 n +0000289261 00000 n +0001046536 00000 n +0000009694 00000 n +0000009748 00000 n +0000289386 00000 n +0001046457 00000 n +0000009802 00000 n +0000009849 00000 n +0000292429 00000 n +0001046339 00000 n +0000009898 00000 n +0000009952 00000 n +0000296634 00000 n +0001046260 00000 n +0000010006 00000 n +0000010057 00000 n +0000296759 00000 n +0001046167 00000 n +0000010111 00000 n +0000010155 00000 n +0000300271 00000 n +0001046049 00000 n +0000010209 00000 n +0000010258 00000 n +0000300396 00000 n +0001045984 00000 n +0000010317 00000 n +0000010382 00000 n +0000310698 00000 n +0001045852 00000 n +0000010430 00000 n +0000010478 00000 n +0000310823 00000 n +0001045773 00000 n +0000010528 00000 n +0000010565 00000 n +0000310948 00000 n +0001045641 00000 n +0000010615 00000 n +0000010670 00000 n +0000317073 00000 n +0001045562 00000 n +0000010725 00000 n +0000010780 00000 n +0000317198 00000 n +0001045483 00000 n +0000010835 00000 n +0000010899 00000 n +0000317323 00000 n +0001045390 00000 n +0000010949 00000 n +0000010995 00000 n +0000322220 00000 n +0001045297 00000 n +0000011045 00000 n +0000011080 00000 n +0000322345 00000 n +0001045204 00000 n +0000011130 00000 n +0000011158 00000 n +0000322470 00000 n +0001045072 00000 n +0000011208 00000 n +0000011237 00000 n +0000322595 00000 n +0001044993 00000 n +0000011292 00000 n +0000011331 00000 n +0000322719 00000 n +0001044900 00000 n +0000011386 00000 n +0000011440 00000 n +0000327697 00000 n +0001044807 00000 n +0000011495 00000 n +0000011544 00000 n +0000327822 00000 n +0001044714 00000 n +0000011599 00000 n +0000011678 00000 n +0000330418 00000 n +0001044582 00000 n +0000011733 00000 n +0000011787 00000 n +0000330541 00000 n +0001044503 00000 n +0000011847 00000 n +0000011898 00000 n +0000334540 00000 n +0001044424 00000 n +0000011958 00000 n +0000012004 00000 n +0000337917 00000 n +0001044331 00000 n +0000012059 00000 n +0000012116 00000 n +0000338042 00000 n +0001044238 00000 n +0000012171 00000 n +0000012223 00000 n +0000341134 00000 n +0001044145 00000 n +0000012278 00000 n +0000012347 00000 n +0000344535 00000 n +0001044066 00000 n +0000012402 00000 n +0000012468 00000 n +0000347065 00000 n +0001043934 00000 n +0000012518 00000 n +0000012548 00000 n +0000347189 00000 n +0001043855 00000 n +0000012603 00000 n +0000012651 00000 n +0000347314 00000 n +0001043762 00000 n +0000012706 00000 n +0000012744 00000 n +0000351664 00000 n +0001043669 00000 n +0000012799 00000 n +0000012873 00000 n +0000351789 00000 n +0001043590 00000 n +0000012928 00000 n +0000012993 00000 n +0000351914 00000 n +0001043511 00000 n +0000013043 00000 n +0000013071 00000 n +0000355209 00000 n +0001043379 00000 n +0000013119 00000 n +0000013198 00000 n +0000355334 00000 n +0001043300 00000 n +0000013248 00000 n +0000013340 00000 n +0000355459 00000 n +0001043207 00000 n +0000013390 00000 n +0000013457 00000 n +0000355584 00000 n +0001043114 00000 n +0000013507 00000 n +0000013554 00000 n +0000360077 00000 n +0001042982 00000 n +0000013604 00000 n +0000013666 00000 n +0000360201 00000 n +0001042903 00000 n +0000013721 00000 n +0000013764 00000 n +0000360326 00000 n +0001042824 00000 n +0000013819 00000 n +0000013867 00000 n +0000364230 00000 n +0001042731 00000 n +0000013917 00000 n +0000013981 00000 n +0000364355 00000 n +0001042638 00000 n +0000014031 00000 n +0000014114 00000 n +0000369138 00000 n +0001042559 00000 n +0000014164 00000 n +0000014247 00000 n +0000373360 00000 n +0001042466 00000 n +0000014295 00000 n +0000014343 00000 n +0000378699 00000 n +0001042334 00000 n +0000014391 00000 n 0000014430 00000 n -0000014534 00000 n -0000014638 00000 n -0000014742 00000 n -0000014846 00000 n -0000014950 00000 n -0000015054 00000 n -0000015158 00000 n -0000015262 00000 n -0000015366 00000 n -0000015469 00000 n -0000015573 00000 n -0000015677 00000 n -0000015781 00000 n -0000015885 00000 n -0000015989 00000 n -0000016093 00000 n -0000016197 00000 n -0000016300 00000 n -0000016404 00000 n -0000016508 00000 n -0000016611 00000 n -0000016714 00000 n -0000016817 00000 n -0000016921 00000 n -0000017025 00000 n -0000017129 00000 n -0000017233 00000 n -0000017337 00000 n -0000017440 00000 n -0000017542 00000 n -0000017644 00000 n -0000017997 00000 n -0000018100 00000 n -0000018204 00000 n -0000018307 00000 n -0000018410 00000 n -0000018514 00000 n -0000018618 00000 n -0000018722 00000 n -0000018826 00000 n -0000018930 00000 n -0000019034 00000 n -0000019138 00000 n -0000019242 00000 n -0000019346 00000 n -0000019450 00000 n -0000019554 00000 n -0000019658 00000 n -0000019762 00000 n -0000019866 00000 n -0000019970 00000 n -0000020074 00000 n -0000020178 00000 n -0000020282 00000 n -0000020386 00000 n -0000020490 00000 n -0000020594 00000 n -0000020698 00000 n -0000020801 00000 n -0000020905 00000 n -0000021009 00000 n -0000021113 00000 n -0000021217 00000 n -0000021321 00000 n -0000021425 00000 n -0000021529 00000 n -0000021633 00000 n -0000021737 00000 n -0000021841 00000 n -0000021945 00000 n -0000022049 00000 n -0000022153 00000 n -0000022257 00000 n -0000022361 00000 n -0000022714 00000 n -0000022817 00000 n -0000022921 00000 n -0000023025 00000 n -0000023129 00000 n -0000023233 00000 n +0000378824 00000 n +0001042255 00000 n +0000014480 00000 n +0000014517 00000 n +0000378949 00000 n +0001042123 00000 n +0000014567 00000 n +0000014605 00000 n +0000383311 00000 n +0001042044 00000 n +0000014660 00000 n +0000014707 00000 n +0000387076 00000 n +0001041951 00000 n +0000014762 00000 n +0000014826 00000 n +0000390130 00000 n +0001041858 00000 n +0000014881 00000 n +0000014942 00000 n +0000393924 00000 n +0001041765 00000 n +0000014997 00000 n +0000015066 00000 n +0000397165 00000 n +0001041686 00000 n +0000015121 00000 n +0000015171 00000 n +0000397290 00000 n +0001041554 00000 n +0000015221 00000 n +0000015266 00000 n +0000397415 00000 n +0001041475 00000 n +0000015321 00000 n +0000015365 00000 n +0000400877 00000 n +0001041382 00000 n +0000015420 00000 n +0000015479 00000 n +0000401002 00000 n +0001041289 00000 n +0000015534 00000 n +0000015580 00000 n +0000401127 00000 n +0001041210 00000 n +0000015635 00000 n +0000015685 00000 n +0000403963 00000 n +0001041092 00000 n +0000015735 00000 n +0000015769 00000 n +0000404088 00000 n +0001041013 00000 n +0000015824 00000 n +0000015863 00000 n +0000406849 00000 n +0001040920 00000 n +0000015918 00000 n +0000015971 00000 n +0000409623 00000 n +0001040827 00000 n +0000016026 00000 n +0000016077 00000 n +0000409748 00000 n +0001040734 00000 n +0000016132 00000 n +0000016196 00000 n +0000413408 00000 n +0001040641 00000 n +0000016251 00000 n +0000016297 00000 n +0000413533 00000 n +0001040548 00000 n +0000016352 00000 n +0000016403 00000 n +0000415543 00000 n +0001040455 00000 n +0000016458 00000 n +0000016507 00000 n +0000415668 00000 n +0001040362 00000 n +0000016562 00000 n +0000016606 00000 n +0000415793 00000 n +0001040283 00000 n +0000016661 00000 n +0000016702 00000 n +0000419441 00000 n +0001040150 00000 n +0000016750 00000 n +0000016794 00000 n +0000419566 00000 n +0001040071 00000 n +0000016844 00000 n +0000016881 00000 n +0000419691 00000 n +0001039978 00000 n +0000016931 00000 n +0000016985 00000 n +0000423132 00000 n +0001039885 00000 n +0000017035 00000 n +0000017089 00000 n +0000433674 00000 n +0001039792 00000 n +0000017139 00000 n +0000017196 00000 n +0000436639 00000 n +0001039699 00000 n +0000017246 00000 n +0000017319 00000 n +0000436764 00000 n +0001039606 00000 n +0000017369 00000 n +0000017429 00000 n +0000441445 00000 n +0001039474 00000 n +0000017479 00000 n +0000017534 00000 n +0000444574 00000 n +0001039409 00000 n +0000017589 00000 n +0000017626 00000 n +0000448944 00000 n +0001039316 00000 n +0000017676 00000 n +0000017723 00000 n +0000460436 00000 n +0001039184 00000 n +0000017773 00000 n +0000017828 00000 n +0000460561 00000 n +0001039119 00000 n +0000017883 00000 n +0000017932 00000 n +0000469056 00000 n +0001039026 00000 n +0000017983 00000 n +0000018053 00000 n +0000486416 00000 n +0001038933 00000 n +0000018104 00000 n +0000018174 00000 n +0000490103 00000 n +0001038854 00000 n +0000018225 00000 n +0000018284 00000 n +0000495540 00000 n +0001038722 00000 n +0000018332 00000 n +0000018411 00000 n +0000495665 00000 n +0001038643 00000 n +0000018461 00000 n +0000018494 00000 n +0000495790 00000 n +0001038550 00000 n +0000018544 00000 n +0000018581 00000 n +0000495915 00000 n +0001038418 00000 n +0000018631 00000 n +0000018677 00000 n +0000499967 00000 n +0001038353 00000 n +0000018732 00000 n +0000018770 00000 n +0000500092 00000 n +0001038221 00000 n +0000018820 00000 n +0000018862 00000 n +0000500217 00000 n +0001038142 00000 n +0000018917 00000 n +0000018976 00000 n +0000504404 00000 n +0001038049 00000 n +0000019031 00000 n +0000019093 00000 n +0000504529 00000 n +0001037956 00000 n +0000019148 00000 n +0000019194 00000 n +0000504654 00000 n +0001037863 00000 n +0000019249 00000 n +0000019308 00000 n +0000508888 00000 n +0001037770 00000 n +0000019363 00000 n +0000019418 00000 n +0000509013 00000 n +0001037691 00000 n +0000019473 00000 n +0000019514 00000 n +0000509138 00000 n +0001037559 00000 n +0000019564 00000 n +0000019619 00000 n +0000509263 00000 n +0001037480 00000 n +0000019674 00000 n +0000019713 00000 n +0000513616 00000 n +0001037387 00000 n +0000019768 00000 n +0000019807 00000 n +0000513741 00000 n +0001037269 00000 n +0000019862 00000 n +0000019907 00000 n +0000516912 00000 n +0001037190 00000 n +0000019967 00000 n +0000020023 00000 n +0000517037 00000 n +0001037097 00000 n +0000020083 00000 n +0000020182 00000 n +0000517162 00000 n +0001037004 00000 n +0000020242 00000 n +0000020289 00000 n +0000520126 00000 n +0001036911 00000 n +0000020349 00000 n +0000020396 00000 n +0000520251 00000 n +0001036818 00000 n +0000020456 00000 n +0000020524 00000 n +0000520376 00000 n +0001036725 00000 n +0000020584 00000 n +0000020654 00000 n +0000524885 00000 n +0001036632 00000 n +0000020714 00000 n +0000020773 00000 n +0000529906 00000 n +0001036553 00000 n +0000020833 00000 n +0000020887 00000 n +0000537324 00000 n +0001036460 00000 n +0000020937 00000 n +0000020973 00000 n +0000537449 00000 n +0001036381 00000 n +0000021023 00000 n +0000021058 00000 n +0000540923 00000 n +0001036249 00000 n +0000021106 00000 n +0000021157 00000 n +0000541048 00000 n +0001036131 00000 n +0000021207 00000 n +0000021271 00000 n +0000541172 00000 n +0001036027 00000 n +0000021326 00000 n +0000021381 00000 n +0000541297 00000 n +0001035948 00000 n +0000021441 00000 n +0000021500 00000 n +0000541547 00000 n +0001035869 00000 n +0000021560 00000 n +0000021604 00000 n +0000546151 00000 n +0001035776 00000 n +0000021654 00000 n +0000021707 00000 n +0000548879 00000 n +0001035658 00000 n +0000021757 00000 n +0000021808 00000 n +0000550778 00000 n +0001035593 00000 n +0000021863 00000 n +0000021931 00000 n +0000555957 00000 n +0001035461 00000 n +0000021979 00000 n +0000022029 00000 n +0000556082 00000 n +0001035343 00000 n +0000022079 00000 n +0000022141 00000 n +0000556207 00000 n +0001035264 00000 n +0000022196 00000 n +0000022245 00000 n +0000560782 00000 n +0001035132 00000 n +0000022300 00000 n +0000022357 00000 n +0000560907 00000 n +0001035067 00000 n +0000022417 00000 n +0000022462 00000 n +0000561032 00000 n +0001034949 00000 n +0000022517 00000 n +0000022586 00000 n +0000564926 00000 n +0001034884 00000 n +0000022646 00000 n +0000022724 00000 n +0000568861 00000 n +0001034752 00000 n +0000022774 00000 n +0000022829 00000 n +0000568986 00000 n +0001034673 00000 n +0000022884 00000 n +0000022932 00000 n +0000572263 00000 n +0001034594 00000 n +0000022987 00000 n +0000023030 00000 n +0000572388 00000 n +0001034515 00000 n +0000023080 00000 n +0000023149 00000 n +0000575644 00000 n +0001034383 00000 n +0000023197 00000 n +0000023246 00000 n +0000575769 00000 n +0001034265 00000 n +0000023296 00000 n 0000023337 00000 n -0000023441 00000 n -0000023545 00000 n -0000023649 00000 n -0000023753 00000 n -0000023857 00000 n -0000023961 00000 n -0000024065 00000 n -0000024169 00000 n -0000024273 00000 n -0000024377 00000 n -0000024481 00000 n -0000024585 00000 n -0000024688 00000 n -0000024792 00000 n +0000575894 00000 n +0001034147 00000 n +0000023392 00000 n +0000023459 00000 n +0000576019 00000 n +0001034068 00000 n +0000023519 00000 n +0000023570 00000 n +0000578933 00000 n +0001033975 00000 n +0000023630 00000 n +0000023688 00000 n +0000579058 00000 n +0001033882 00000 n +0000023748 00000 n +0000023833 00000 n +0000579183 00000 n +0001033803 00000 n +0000023893 00000 n +0000023955 00000 n +0000582838 00000 n +0001033671 00000 n +0000024010 00000 n +0000024085 00000 n +0000582963 00000 n +0001033592 00000 n +0000024145 00000 n +0000024203 00000 n +0000591351 00000 n +0001033499 00000 n +0000024263 00000 n +0000024315 00000 n +0000591476 00000 n +0001033420 00000 n +0000024375 00000 n +0000024432 00000 n +0000598835 00000 n +0001033327 00000 n +0000024487 00000 n +0000024574 00000 n +0000598960 00000 n +0001033209 00000 n +0000024629 00000 n +0000024711 00000 n +0000599085 00000 n +0001033130 00000 n +0000024771 00000 n +0000024836 00000 n +0000602676 00000 n +0001033037 00000 n 0000024896 00000 n -0000025000 00000 n -0000025104 00000 n -0000025207 00000 n -0000025311 00000 n -0000025415 00000 n -0000025519 00000 n -0000025623 00000 n -0000025727 00000 n -0000025831 00000 n -0000025935 00000 n -0000026039 00000 n -0000026142 00000 n -0000026246 00000 n -0000026350 00000 n -0000026454 00000 n -0000026558 00000 n -0000026662 00000 n -0000026766 00000 n -0000026870 00000 n -0000026974 00000 n -0000027078 00000 n -0000027181 00000 n -0000027283 00000 n -0000027652 00000 n -0000027755 00000 n -0000027859 00000 n -0000027963 00000 n -0000028067 00000 n -0000028171 00000 n -0000028275 00000 n -0000028379 00000 n -0000028483 00000 n -0000028586 00000 n -0000028690 00000 n -0000028794 00000 n -0000028898 00000 n -0000029001 00000 n -0000029105 00000 n -0000029209 00000 n -0000029313 00000 n -0000029417 00000 n -0000029521 00000 n -0000029625 00000 n -0000029729 00000 n -0000029833 00000 n -0000029937 00000 n -0000030040 00000 n -0000030144 00000 n -0000030248 00000 n -0000030351 00000 n -0000030455 00000 n -0000030559 00000 n -0000030663 00000 n -0000030767 00000 n -0000030871 00000 n -0000030975 00000 n -0000031079 00000 n -0000031183 00000 n -0000031287 00000 n -0000031391 00000 n -0000031495 00000 n -0000031598 00000 n -0000031702 00000 n -0000031806 00000 n -0000031909 00000 n -0000032011 00000 n -0000032113 00000 n -0000032474 00000 n -0000032577 00000 n -0000032681 00000 n -0000032785 00000 n -0000032889 00000 n -0000032993 00000 n -0000033097 00000 n -0000033201 00000 n -0000033305 00000 n -0000033408 00000 n -0000033512 00000 n -0000033616 00000 n -0000033720 00000 n -0000033824 00000 n -0000033928 00000 n -0000034032 00000 n -0000034135 00000 n -0000034239 00000 n -0000034343 00000 n -0000034447 00000 n -0000034551 00000 n -0000034654 00000 n -0000034757 00000 n -0000034861 00000 n -0000034965 00000 n -0000035069 00000 n -0000035173 00000 n -0000035277 00000 n -0000035381 00000 n -0000035485 00000 n -0000035589 00000 n -0000035693 00000 n -0000035797 00000 n -0000035900 00000 n -0000036004 00000 n -0000036108 00000 n -0000036212 00000 n -0000036316 00000 n -0000036419 00000 n -0000036523 00000 n -0000036626 00000 n -0000036728 00000 n -0000036830 00000 n -0000037183 00000 n -0000037286 00000 n -0000037390 00000 n -0000037494 00000 n -0000037598 00000 n -0000037701 00000 n -0000037805 00000 n -0000037909 00000 n -0000038013 00000 n -0000038117 00000 n -0000038221 00000 n -0000038325 00000 n -0000038429 00000 n -0000038533 00000 n -0000038637 00000 n -0000038741 00000 n -0000038845 00000 n -0000038949 00000 n -0000039053 00000 n -0000039157 00000 n +0000024939 00000 n +0000602801 00000 n +0001032944 00000 n +0000024999 00000 n +0000025040 00000 n +0000602926 00000 n +0001032865 00000 n +0000025100 00000 n +0000025136 00000 n +0000603051 00000 n +0001032772 00000 n +0000025186 00000 n +0000025229 00000 n +0000603176 00000 n +0001032679 00000 n +0000025279 00000 n +0000025336 00000 n +0000607171 00000 n +0001032561 00000 n +0000025386 00000 n +0000025444 00000 n +0000607296 00000 n +0001032443 00000 n +0000025499 00000 n +0000025542 00000 n +0000607421 00000 n +0001032378 00000 n +0000025602 00000 n +0000025680 00000 n +0000611194 00000 n +0001032285 00000 n +0000025735 00000 n +0000025788 00000 n +0000616978 00000 n +0001032206 00000 n +0000025843 00000 n +0000025888 00000 n +0000624534 00000 n +0001032073 00000 n +0000025936 00000 n +0000025990 00000 n +0000624659 00000 n +0001031994 00000 n +0000026040 00000 n +0000026094 00000 n +0000628180 00000 n +0001031862 00000 n +0000026144 00000 n +0000026211 00000 n +0000628305 00000 n +0001031783 00000 n +0000026266 00000 n +0000026356 00000 n +0000628429 00000 n +0001031704 00000 n +0000026411 00000 n +0000026507 00000 n +0000628553 00000 n +0001031586 00000 n +0000026557 00000 n +0000026622 00000 n +0000628678 00000 n +0001031507 00000 n +0000026677 00000 n +0000026734 00000 n +0000632363 00000 n +0001031427 00000 n +0000026789 00000 n +0000026846 00000 n +0000635258 00000 n +0001031289 00000 n +0000026895 00000 n +0000026973 00000 n +0000635384 00000 n +0001031164 00000 n +0000027024 00000 n +0000027063 00000 n +0000641538 00000 n +0001031080 00000 n +0000027119 00000 n +0000027176 00000 n +0000644338 00000 n +0001030955 00000 n +0000027232 00000 n +0000027308 00000 n +0000646566 00000 n +0001030871 00000 n +0000027369 00000 n +0000027436 00000 n +0000646692 00000 n +0001030772 00000 n +0000027497 00000 n +0000027559 00000 n +0000649022 00000 n +0001030673 00000 n +0000027620 00000 n +0000027679 00000 n +0000649148 00000 n +0001030589 00000 n +0000027740 00000 n +0000027813 00000 n +0000649270 00000 n +0001030505 00000 n +0000027864 00000 n +0000027916 00000 n +0000651887 00000 n +0001030366 00000 n +0000027965 00000 n +0000028010 00000 n +0000652013 00000 n +0001030282 00000 n +0000028061 00000 n +0000028117 00000 n +0000652139 00000 n +0001030142 00000 n +0000028168 00000 n +0000028210 00000 n +0000652265 00000 n +0001030058 00000 n +0000028266 00000 n +0000028299 00000 n +0000652391 00000 n +0001029959 00000 n +0000028355 00000 n +0000028396 00000 n +0000655062 00000 n +0001029860 00000 n +0000028452 00000 n +0000028487 00000 n +0000655188 00000 n +0001029776 00000 n +0000028543 00000 n +0000028579 00000 n +0000655314 00000 n +0001029651 00000 n +0000028630 00000 n +0000028687 00000 n +0000658032 00000 n +0001029567 00000 n +0000028743 00000 n +0000028781 00000 n +0000658158 00000 n +0001029483 00000 n +0000028837 00000 n +0000028870 00000 n +0000662094 00000 n +0001029344 00000 n +0000028919 00000 n +0000029000 00000 n +0000662220 00000 n +0001029234 00000 n +0000029051 00000 n +0000029089 00000 n +0000663942 00000 n +0001029165 00000 n +0000029145 00000 n +0000029178 00000 n +0000666814 00000 n +0001029026 00000 n +0000029227 00000 n +0000029293 00000 n +0000666940 00000 n +0001028901 00000 n +0000029344 00000 n +0000029412 00000 n +0000670613 00000 n +0001028817 00000 n +0000029468 00000 n +0000029506 00000 n +0000670739 00000 n +0001028718 00000 n +0000029562 00000 n +0000029606 00000 n +0000673057 00000 n +0001028619 00000 n +0000029662 00000 n +0000029704 00000 n +0000673183 00000 n +0001028535 00000 n +0000029760 00000 n +0000029806 00000 n +0000677013 00000 n +0001028410 00000 n +0000029857 00000 n +0000029935 00000 n +0000680954 00000 n +0001028326 00000 n +0000029991 00000 n +0000030041 00000 n +0000681080 00000 n +0001028227 00000 n +0000030097 00000 n +0000030141 00000 n +0000686168 00000 n +0001028128 00000 n +0000030197 00000 n +0000030235 00000 n +0000686294 00000 n +0001028029 00000 n +0000030291 00000 n +0000030329 00000 n +0000686420 00000 n +0001027945 00000 n +0000030385 00000 n +0000030424 00000 n +0000690076 00000 n +0001027806 00000 n +0000030473 00000 n +0000030511 00000 n +0000690202 00000 n +0001027722 00000 n +0000030562 00000 n +0000030600 00000 n +0000690328 00000 n +0001027623 00000 n +0000030651 00000 n +0000030704 00000 n +0000690454 00000 n +0001027524 00000 n +0000030755 00000 n +0000030807 00000 n +0000693282 00000 n +0001027425 00000 n +0000030858 00000 n +0000030900 00000 n +0000693408 00000 n +0001027326 00000 n +0000030951 00000 n +0000031003 00000 n +0000693532 00000 n +0001027227 00000 n +0000031054 00000 n +0000031095 00000 n +0000695170 00000 n +0001027143 00000 n +0000031146 00000 n +0000031187 00000 n +0000698776 00000 n +0001027004 00000 n +0000031236 00000 n +0000031276 00000 n +0000698902 00000 n +0001026920 00000 n +0000031327 00000 n +0000031383 00000 n +0000699028 00000 n +0001026821 00000 n +0000031434 00000 n +0000031478 00000 n +0000699154 00000 n +0001026722 00000 n +0000031529 00000 n +0000031580 00000 n +0000701746 00000 n +0001026638 00000 n +0000031631 00000 n +0000031674 00000 n +0000705658 00000 n +0001026514 00000 n +0000031723 00000 n +0000031770 00000 n +0000705784 00000 n +0001026430 00000 n +0000031821 00000 n +0000031857 00000 n +0000705910 00000 n +0001026331 00000 n +0000031908 00000 n +0000031969 00000 n +0000709687 00000 n +0001026191 00000 n +0000032020 00000 n +0000032099 00000 n +0000715147 00000 n +0001026107 00000 n +0000032155 00000 n +0000032210 00000 n +0000717838 00000 n +0001026023 00000 n +0000032266 00000 n +0000032316 00000 n +0000717964 00000 n +0001025924 00000 n +0000032367 00000 n +0000032419 00000 n +0000721634 00000 n +0001025840 00000 n +0000032470 00000 n +0000032514 00000 n +0000722377 00000 n +0001025701 00000 n +0000032559 00000 n +0000032598 00000 n +0000725208 00000 n +0001025576 00000 n +0000032647 00000 n +0000032690 00000 n +0000725334 00000 n +0001025492 00000 n +0000032741 00000 n +0000032779 00000 n +0000725460 00000 n +0001025393 00000 n +0000032830 00000 n +0000032867 00000 n +0000729292 00000 n +0001025294 00000 n +0000032918 00000 n +0000032953 00000 n +0000743520 00000 n +0001025210 00000 n +0000033004 00000 n +0000033052 00000 n +0000747284 00000 n +0001025070 00000 n +0000033101 00000 n +0000033161 00000 n +0000747410 00000 n +0001024986 00000 n +0000033212 00000 n +0000033255 00000 n +0000747536 00000 n +0001024887 00000 n +0000033306 00000 n +0000033401 00000 n +0000752216 00000 n +0001024788 00000 n +0000033452 00000 n +0000033490 00000 n +0000756869 00000 n +0001024689 00000 n +0000033541 00000 n +0000033602 00000 n +0000756995 00000 n +0001024605 00000 n +0000033653 00000 n +0000033710 00000 n +0000760756 00000 n +0001024480 00000 n +0000033759 00000 n +0000033797 00000 n +0000760882 00000 n +0001024396 00000 n +0000033848 00000 n +0000033886 00000 n +0000761008 00000 n +0001024297 00000 n +0000033937 00000 n +0000033975 00000 n +0000761134 00000 n +0001024198 00000 n +0000034026 00000 n +0000034064 00000 n +0000765093 00000 n +0001024099 00000 n +0000034115 00000 n +0000034156 00000 n +0000765219 00000 n +0001024000 00000 n +0000034207 00000 n +0000034263 00000 n +0000765345 00000 n +0001023916 00000 n +0000034314 00000 n +0000034347 00000 n +0000766079 00000 n +0001023791 00000 n +0000034392 00000 n +0000034425 00000 n +0000770338 00000 n +0001023666 00000 n +0000034474 00000 n +0000034518 00000 n +0000770464 00000 n +0001023541 00000 n +0000034569 00000 n +0000034627 00000 n +0000770590 00000 n +0001023457 00000 n +0000034683 00000 n +0000034723 00000 n +0000770716 00000 n +0001023332 00000 n +0000034779 00000 n +0000034830 00000 n +0000770842 00000 n +0001023248 00000 n +0000034891 00000 n +0000034938 00000 n +0000770968 00000 n +0001023164 00000 n +0000034999 00000 n +0000035043 00000 n +0000774825 00000 n +0001023065 00000 n +0000035094 00000 n +0000035165 00000 n +0000774950 00000 n +0001022966 00000 n +0000035216 00000 n +0000035273 00000 n +0000777656 00000 n +0001022826 00000 n +0000035324 00000 n +0000035371 00000 n +0000777782 00000 n +0001022716 00000 n +0000035427 00000 n +0000035500 00000 n +0000780553 00000 n +0001022632 00000 n +0000035561 00000 n +0000035634 00000 n +0000780679 00000 n +0001022548 00000 n +0000035695 00000 n +0000035768 00000 n +0000780805 00000 n +0001022423 00000 n +0000035819 00000 n +0000035871 00000 n +0000780931 00000 n +0001022339 00000 n +0000035927 00000 n +0000035979 00000 n +0000783648 00000 n +0001022255 00000 n +0000036035 00000 n +0000036099 00000 n +0000787681 00000 n +0001022115 00000 n +0000036148 00000 n +0000036209 00000 n +0000787807 00000 n +0001021990 00000 n +0000036260 00000 n +0000036314 00000 n +0000787933 00000 n +0001021865 00000 n +0000036370 00000 n +0000036408 00000 n +0000791104 00000 n +0001021781 00000 n +0000036469 00000 n +0000036512 00000 n +0000795435 00000 n +0001021682 00000 n +0000036573 00000 n +0000036636 00000 n +0000795561 00000 n +0001021583 00000 n +0000036697 00000 n +0000036740 00000 n +0000798271 00000 n +0001021484 00000 n +0000036801 00000 n +0000036857 00000 n +0000798397 00000 n +0001021400 00000 n +0000036918 00000 n +0000036971 00000 n +0000798523 00000 n +0001021316 00000 n +0000037027 00000 n +0000037081 00000 n +0000802462 00000 n +0001021191 00000 n +0000037132 00000 n +0000037175 00000 n +0000802715 00000 n +0001021107 00000 n +0000037231 00000 n +0000037279 00000 n +0000802841 00000 n +0001021023 00000 n +0000037335 00000 n +0000037391 00000 n +0000809673 00000 n +0001020883 00000 n +0000037440 00000 n +0000037475 00000 n +0000809799 00000 n +0001020799 00000 n +0000037526 00000 n +0000037556 00000 n +0000809925 00000 n +0001020700 00000 n +0000037607 00000 n +0000037641 00000 n +0000810051 00000 n +0001020601 00000 n +0000037692 00000 n +0000037722 00000 n +0000811679 00000 n +0001020502 00000 n +0000037773 00000 n +0000037824 00000 n +0000814205 00000 n +0001020362 00000 n +0000037875 00000 n +0000037904 00000 n +0000814331 00000 n +0001020293 00000 n +0000037960 00000 n +0000038009 00000 n +0000814457 00000 n +0001020168 00000 n +0000038060 00000 n +0000038093 00000 n +0000814582 00000 n +0001020084 00000 n +0000038149 00000 n +0000038197 00000 n +0000814708 00000 n +0001020000 00000 n +0000038253 00000 n +0000038301 00000 n +0000819400 00000 n +0001019860 00000 n +0000038350 00000 n +0000038402 00000 n +0000819526 00000 n +0001019776 00000 n +0000038453 00000 n +0000038497 00000 n +0000819652 00000 n +0001019636 00000 n +0000038548 00000 n +0000038584 00000 n +0000819778 00000 n +0001019552 00000 n +0000038640 00000 n +0000038743 00000 n +0000824390 00000 n +0001019453 00000 n +0000038799 00000 n +0000038907 00000 n +0000824516 00000 n +0001019354 00000 n +0000038963 00000 n +0000039064 00000 n +0000824642 00000 n +0001019270 00000 n +0000039120 00000 n +0000039210 00000 n +0000824768 00000 n +0001019130 00000 n 0000039261 00000 n -0000039364 00000 n -0000039468 00000 n -0000039572 00000 n -0000039676 00000 n -0000039780 00000 n -0000039884 00000 n -0000039988 00000 n -0000040092 00000 n -0000040196 00000 n -0000040299 00000 n -0000040403 00000 n -0000040507 00000 n -0000040611 00000 n -0000040715 00000 n -0000040819 00000 n -0000040923 00000 n -0000041027 00000 n -0000041131 00000 n -0000041235 00000 n -0000041339 00000 n -0000041442 00000 n -0000041545 00000 n -0000041647 00000 n -0000041749 00000 n -0000042118 00000 n -0000042221 00000 n -0000042325 00000 n -0000042428 00000 n -0000042532 00000 n -0000042636 00000 n -0000042740 00000 n -0000042844 00000 n -0000042948 00000 n -0000043051 00000 n -0000043155 00000 n -0000043259 00000 n -0000043363 00000 n -0000043467 00000 n -0000043571 00000 n -0000043675 00000 n -0000043812 00000 n -0000043866 00000 n -0000043952 00000 n -0000044005 00000 n -0000044091 00000 n -0000044145 00000 n -0000044232 00000 n -0000044287 00000 n -0000044373 00000 n -0000044440 00000 n -0000044526 00000 n -0000044629 00000 n -0000044733 00000 n -0000044837 00000 n -0000044941 00000 n -0000045045 00000 n -0000045149 00000 n -0000045253 00000 n -0000045357 00000 n -0000045461 00000 n -0000045565 00000 n -0000045669 00000 n -0000045773 00000 n -0000045877 00000 n -0000045981 00000 n -0000046085 00000 n -0000046189 00000 n -0000046293 00000 n -0000046397 00000 n -0000046500 00000 n -0000046602 00000 n -0000046704 00000 n -0000046806 00000 n -0000047039 00000 n -0000047143 00000 n -0000047247 00000 n -0000047351 00000 n -0000047455 00000 n -0000047559 00000 n -0000047663 00000 n -0000047767 00000 n -0000047871 00000 n -0000047975 00000 n -0000048079 00000 n -0000048183 00000 n -0000048287 00000 n -0000048390 00000 n -0000048494 00000 n -0000048598 00000 n -0000048702 00000 n -0000048806 00000 n -0000048910 00000 n -0000049014 00000 n -0000049118 00000 n -0000049222 00000 n -0000049326 00000 n -0000049430 00000 n -0000049534 00000 n -0000049638 00000 n -0000049742 00000 n -0000049846 00000 n -0000049950 00000 n -0000050054 00000 n -0000050158 00000 n -0000050262 00000 n -0000050366 00000 n -0000050470 00000 n -0000050574 00000 n -0000050678 00000 n -0000050782 00000 n -0000050886 00000 n -0000050990 00000 n -0000051094 00000 n -0000051198 00000 n -0000051302 00000 n -0000051406 00000 n -0000051510 00000 n -0000051614 00000 n -0000051716 00000 n -0000051820 00000 n -0000051924 00000 n -0000052028 00000 n -0000052132 00000 n -0000052236 00000 n -0000052339 00000 n -0000052441 00000 n -0000052543 00000 n -0000052984 00000 n -0000053088 00000 n -0000053192 00000 n -0000053296 00000 n -0000053400 00000 n -0000053504 00000 n -0000053608 00000 n -0000053712 00000 n -0000053816 00000 n -0000053920 00000 n -0000054024 00000 n -0000054128 00000 n -0000054232 00000 n -0000054336 00000 n -0000054440 00000 n -0000054544 00000 n -0000054648 00000 n -0000054752 00000 n -0000054856 00000 n -0000054960 00000 n -0000055064 00000 n -0000055168 00000 n -0000055272 00000 n -0000055376 00000 n -0000055480 00000 n -0000055584 00000 n -0000055688 00000 n -0000055792 00000 n -0000055896 00000 n -0000056000 00000 n -0000056104 00000 n -0000056208 00000 n -0000056312 00000 n -0000056416 00000 n -0000056520 00000 n -0000056624 00000 n -0000056728 00000 n -0000056832 00000 n -0000056936 00000 n -0000057040 00000 n -0000057144 00000 n -0000057248 00000 n -0000057352 00000 n +0000039309 00000 n +0000824894 00000 n +0001019046 00000 n +0000039365 00000 n +0000039431 00000 n +0000828818 00000 n +0001018947 00000 n +0000039487 00000 n +0000039554 00000 n +0000828944 00000 n +0001018848 00000 n +0000039610 00000 n +0000039669 00000 n +0000829069 00000 n +0001018749 00000 n +0000039725 00000 n +0000039779 00000 n +0000829195 00000 n +0001018650 00000 n +0000039835 00000 n +0000039893 00000 n +0000829321 00000 n +0001018566 00000 n +0000039949 00000 n +0000039994 00000 n +0000829447 00000 n +0001018426 00000 n +0000040045 00000 n +0000040086 00000 n +0000833348 00000 n +0001018357 00000 n +0000040142 00000 n +0000040187 00000 n +0000833474 00000 n +0001018258 00000 n +0000040238 00000 n +0000040291 00000 n +0000835019 00000 n +0001018174 00000 n +0000040342 00000 n +0000040382 00000 n +0000838086 00000 n +0001018034 00000 n +0000040431 00000 n +0000040497 00000 n +0000838212 00000 n +0001017923 00000 n +0000040548 00000 n +0000040600 00000 n +0000838337 00000 n +0001017839 00000 n +0000040656 00000 n +0000040705 00000 n +0000841290 00000 n +0001017740 00000 n +0000040761 00000 n +0000040814 00000 n +0000844924 00000 n +0001017641 00000 n +0000040870 00000 n +0000040916 00000 n +0000845049 00000 n +0001017542 00000 n +0000040972 00000 n +0000041015 00000 n +0000848825 00000 n +0001017443 00000 n +0000041071 00000 n +0000041113 00000 n +0000848951 00000 n +0001017344 00000 n +0000041169 00000 n +0000041214 00000 n +0000849077 00000 n +0001017245 00000 n +0000041270 00000 n +0000041313 00000 n +0000849203 00000 n +0001017146 00000 n +0000041369 00000 n +0000041412 00000 n +0000849328 00000 n +0001017047 00000 n +0000041468 00000 n +0000041509 00000 n +0000850808 00000 n +0001016963 00000 n +0000041566 00000 n +0000041619 00000 n +0000854177 00000 n +0001016838 00000 n +0000041668 00000 n +0000041716 00000 n +0000854303 00000 n +0001016754 00000 n +0000041767 00000 n +0000041804 00000 n +0000854429 00000 n +0001016655 00000 n +0000041855 00000 n +0000041895 00000 n +0000854555 00000 n +0001016556 00000 n +0000041946 00000 n +0000041981 00000 n +0000858041 00000 n +0001016457 00000 n +0000042032 00000 n +0000042066 00000 n +0000858167 00000 n +0001016358 00000 n +0000042117 00000 n +0000042152 00000 n +0000858292 00000 n +0001016259 00000 n +0000042203 00000 n +0000042237 00000 n +0000858418 00000 n +0001016160 00000 n +0000042288 00000 n +0000042323 00000 n +0000858544 00000 n +0001016061 00000 n +0000042374 00000 n +0000042411 00000 n +0000859860 00000 n +0001015977 00000 n +0000042462 00000 n +0000042501 00000 n +0000042880 00000 n +0000043129 00000 n +0000042555 00000 n +0000043003 00000 n +0000043066 00000 n +0001008999 00000 n +0000995475 00000 n +0001008831 00000 n +0000995006 00000 n +0000990297 00000 n +0000994841 00000 n +0001009897 00000 n +0000045598 00000 n +0000044684 00000 n +0000043217 00000 n +0000045535 00000 n +0000989262 00000 n +0000970555 00000 n +0000989097 00000 n +0000044855 00000 n +0000969537 00000 n +0000952871 00000 n +0000969371 00000 n +0000045023 00000 n +0000045195 00000 n +0000045364 00000 n +0000046712 00000 n +0000046321 00000 n +0000045686 00000 n +0000046649 00000 n +0000950938 00000 n +0000935235 00000 n +0000950772 00000 n +0000046465 00000 n +0000054523 00000 n +0000048642 00000 n +0000046814 00000 n +0000054397 00000 n +0000054460 00000 n +0000049083 00000 n +0000049233 00000 n +0000049386 00000 n +0000049541 00000 n +0000049695 00000 n +0000049850 00000 n +0000050005 00000 n +0000050159 00000 n +0000050313 00000 n +0000050468 00000 n +0000050621 00000 n +0000050776 00000 n +0000050931 00000 n +0000051091 00000 n +0000051256 00000 n +0000051415 00000 n +0000051570 00000 n +0000051725 00000 n +0000051879 00000 n +0000052034 00000 n +0000052184 00000 n +0000052337 00000 n +0000052491 00000 n +0000052646 00000 n +0000052801 00000 n +0000052961 00000 n +0000053114 00000 n +0000053269 00000 n +0000053429 00000 n +0000053588 00000 n +0000053747 00000 n +0000053912 00000 n +0000054076 00000 n +0000054234 00000 n +0000063616 00000 n +0000056970 00000 n +0000054611 00000 n +0000063553 00000 n +0000934635 00000 n +0000924949 00000 n +0000934469 00000 n 0000057456 00000 n -0000057560 00000 n -0000057664 00000 n -0000057768 00000 n -0000057872 00000 n -0000057976 00000 n -0000058080 00000 n -0000058183 00000 n -0000058285 00000 n -0000058387 00000 n -0000058820 00000 n -0000058924 00000 n -0000059028 00000 n -0000059132 00000 n -0000059236 00000 n -0000059340 00000 n -0000059444 00000 n -0000059548 00000 n -0000059652 00000 n -0000059756 00000 n -0000059860 00000 n -0000059964 00000 n -0000060068 00000 n -0000060172 00000 n -0000060276 00000 n -0000060380 00000 n -0000060484 00000 n -0000060588 00000 n -0000060692 00000 n -0000060796 00000 n -0000060900 00000 n -0000061004 00000 n -0000061108 00000 n -0000061212 00000 n -0000061316 00000 n -0000061420 00000 n -0000061524 00000 n -0000061628 00000 n -0000061732 00000 n -0000061836 00000 n -0000061940 00000 n -0000062044 00000 n -0000062147 00000 n -0000062251 00000 n -0000062355 00000 n -0000062459 00000 n -0000062563 00000 n -0000062667 00000 n -0000062771 00000 n -0000062875 00000 n -0000062979 00000 n -0000063083 00000 n -0000063187 00000 n -0000063291 00000 n -0000063395 00000 n -0000063499 00000 n -0000063603 00000 n -0000063707 00000 n -0000063811 00000 n -0000063914 00000 n -0000064016 00000 n -0000064118 00000 n -0000064543 00000 n -0000064647 00000 n -0000064751 00000 n -0000064855 00000 n -0000064959 00000 n -0000065063 00000 n -0000065167 00000 n -0000065271 00000 n -0000065375 00000 n -0000065479 00000 n -0000065583 00000 n -0000065687 00000 n -0000065791 00000 n -0000065895 00000 n -0000065999 00000 n -0000066103 00000 n -0000066207 00000 n -0000066311 00000 n -0000066415 00000 n -0000066519 00000 n -0000066623 00000 n -0000066727 00000 n -0000066831 00000 n -0000066935 00000 n -0000067039 00000 n -0000067143 00000 n -0000067247 00000 n -0000067351 00000 n -0000067455 00000 n -0000067559 00000 n -0000067663 00000 n -0000067767 00000 n -0000067871 00000 n -0000067975 00000 n -0000068079 00000 n -0000068183 00000 n -0000068480 00000 n -0000068529 00000 n -0000068616 00000 n -0000068720 00000 n -0000068824 00000 n -0000068927 00000 n -0000068976 00000 n -0000069080 00000 n -0000069183 00000 n -0000069216 00000 n -0000069272 00000 n -0000069359 00000 n -0000069428 00000 n -0000069515 00000 n -0000069566 00000 n -0000069653 00000 n -0000069738 00000 n -0000069825 00000 n -0000069881 00000 n -0000069968 00000 n -0000070018 00000 n -0000070105 00000 n -0000070157 00000 n -0000070244 00000 n -0000070306 00000 n -0000070391 00000 n -0000070472 00000 n -0000070526 00000 n -0000070612 00000 n -0000070666 00000 n -0000070753 00000 n -0000070786 00000 n -0000070827 00000 n -0000070914 00000 n -0000070958 00000 n -0000071045 00000 n -0000071090 00000 n -0000071177 00000 n -0000071221 00000 n -0000071308 00000 n -0000071352 00000 n -0000071439 00000 n -0000071481 00000 n -0000071568 00000 n -0000071616 00000 n -0000071703 00000 n -0000071776 00000 n -0000071880 00000 n -0000071983 00000 n -0000072016 00000 n -0000072069 00000 n -0000072155 00000 n -0000072180 00000 n -0000072227 00000 n -0000072313 00000 n -0000072360 00000 n -0000072446 00000 n -0000072479 00000 n -0000072524 00000 n -0000072611 00000 n -0000072656 00000 n -0000072742 00000 n -0000072775 00000 n -0000072820 00000 n -0000072906 00000 n -0000072949 00000 n -0000073035 00000 n -0000073076 00000 n -0000073162 00000 n -0000073211 00000 n -0000073297 00000 n -0000073343 00000 n -0000073429 00000 n -0000073474 00000 n -0000073560 00000 n -0000073612 00000 n -0000073698 00000 n -0000073748 00000 n -0000073834 00000 n -0000073880 00000 n -0000073966 00000 n -0000074009 00000 n -0000074095 00000 n -0000074139 00000 n -0000074225 00000 n -0000074268 00000 n -0000074354 00000 n -0000074399 00000 n -0000074485 00000 n -0000074523 00000 n -0000074609 00000 n -0000074651 00000 n -0000074737 00000 n -0000074780 00000 n -0000074866 00000 n -0000074904 00000 n -0000074990 00000 n -0000075032 00000 n -0000075118 00000 n -0000075162 00000 n -0000075248 00000 n -0000075295 00000 n -0000075381 00000 n -0000075483 00000 n -0000075585 00000 n -0000075778 00000 n -0000075882 00000 n -0000075907 00000 n -0000075956 00000 n -0000076042 00000 n -0000076067 00000 n -0000076114 00000 n -0000076201 00000 n -0000076305 00000 n -0000076338 00000 n -0000076391 00000 n -0000076478 00000 n -0000076503 00000 n -0000076607 00000 n -0000076710 00000 n -0000076814 00000 n -0000076855 00000 n -0000076897 00000 n -0000076984 00000 n -0000077027 00000 n -0000077114 00000 n -0000077164 00000 n -0000077251 00000 n -0000077299 00000 n -0000077386 00000 n -0000077435 00000 n -0000077478 00000 n -0000077565 00000 n -0000077619 00000 n -0000077706 00000 n -0000077751 00000 n -0000077838 00000 n -0000077895 00000 n -0000077981 00000 n -0000078077 00000 n -0000078162 00000 n -0000078219 00000 n -0000078265 00000 n -0000078352 00000 n -0000078398 00000 n -0000078483 00000 n -0000078527 00000 n -0000078614 00000 n -0000078665 00000 n -0000078752 00000 n -0000078801 00000 n -0000078888 00000 n -0000078945 00000 n -0000079008 00000 n -0000079095 00000 n -0000079153 00000 n -0000079240 00000 n -0000079334 00000 n -0000079420 00000 n -0000079461 00000 n -0000079504 00000 n -0000079590 00000 n -0000079638 00000 n -0000079725 00000 n -0000079766 00000 n -0000079853 00000 n -0000079897 00000 n -0000079984 00000 n -0000080028 00000 n -0000080114 00000 n -0000080171 00000 n -0000080217 00000 n -0000080304 00000 n -0000080353 00000 n -0000080438 00000 n -0000080471 00000 n -0000080525 00000 n -0000080612 00000 n -0000080663 00000 n -0000080750 00000 n -0000080804 00000 n -0000080891 00000 n -0000080941 00000 n -0000081028 00000 n -0000081077 00000 n -0000081127 00000 n -0000081212 00000 n -0000081237 00000 n -0000081301 00000 n -0000081388 00000 n -0000081413 00000 n -0000081465 00000 n -0000081550 00000 n -0000081575 00000 n -0000081639 00000 n -0000081726 00000 n -0000081792 00000 n -0000081879 00000 n -0000081937 00000 n -0000082024 00000 n -0000082118 00000 n -0000082205 00000 n -0000082269 00000 n -0000082356 00000 n -0000082417 00000 n -0000082504 00000 n -0000082569 00000 n -0000082646 00000 n -0000082732 00000 n -0000082757 00000 n -0000082847 00000 n -0000082933 00000 n -0000083022 00000 n -0000083108 00000 n -0000083179 00000 n -0000083265 00000 n -0000083397 00000 n -0000083483 00000 n -0000083532 00000 n -0000083606 00000 n -0000083692 00000 n -0000083789 00000 n -0000083875 00000 n -0000083940 00000 n -0000084027 00000 n -0000084068 00000 n -0000084133 00000 n -0000084220 00000 n -0000084245 00000 n -0000084307 00000 n -0000084394 00000 n -0000084419 00000 n -0000084468 00000 n -0000084555 00000 n -0000084580 00000 n -0000084628 00000 n -0000084715 00000 n -0000084765 00000 n -0000084849 00000 n -0000084893 00000 n -0000084977 00000 n -0000085018 00000 n -0000085062 00000 n -0000085148 00000 n -0000085198 00000 n -0000085284 00000 n -0000085334 00000 n -0000085420 00000 n -0000085469 00000 n -0000085555 00000 n -0000085602 00000 n -0000085688 00000 n -0000085745 00000 n -0000085827 00000 n -0000085914 00000 n -0000085999 00000 n -0000086086 00000 n -0000086138 00000 n -0000086225 00000 n -0000086277 00000 n -0000086363 00000 n -0000086412 00000 n -0000086527 00000 n -0000086614 00000 n -0000086729 00000 n -0000086815 00000 n -0000086848 00000 n -0000086901 00000 n -0000086988 00000 n -0000087038 00000 n -0000087125 00000 n -0000087158 00000 n -0000087247 00000 n -0000087333 00000 n -0000087396 00000 n -0000087481 00000 n -0000087514 00000 n -0000087575 00000 n -0000087661 00000 n -0000087686 00000 n -0000087805 00000 n -0000087891 00000 n -0000087934 00000 n -0000088021 00000 n -0000088064 00000 n -0000088151 00000 n -0000088192 00000 n -0000088296 00000 n -0000088399 00000 n -0000088432 00000 n -0000088485 00000 n -0000088572 00000 n -0000088597 00000 n -0000088652 00000 n -0000088739 00000 n -0000088764 00000 n -0000088856 00000 n -0000088942 00000 n -0000088967 00000 n -0000089016 00000 n -0000089103 00000 n -0000089166 00000 n -0000089253 00000 n -0000089316 00000 n -0000089403 00000 n -0000089457 00000 n -0000089544 00000 n -0000089593 00000 n -0000089661 00000 n -0000089747 00000 n -0000089802 00000 n -0000089889 00000 n -0000089922 00000 n -0000089977 00000 n -0000090063 00000 n -0000090131 00000 n -0000090217 00000 n -0000090292 00000 n -0000090379 00000 n -0000090449 00000 n -0000090535 00000 n -0000090614 00000 n -0000090701 00000 n -0000090758 00000 n -0000090840 00000 n -0000090926 00000 n -0000091001 00000 n -0000091088 00000 n -0000091161 00000 n -0000091248 00000 n -0000091326 00000 n -0000091413 00000 n -0000091462 00000 n -0000091510 00000 n -0000091597 00000 n -0000091622 00000 n -0000091670 00000 n -0000091757 00000 n -0000091851 00000 n -0000091938 00000 n -0000092032 00000 n -0000092118 00000 n -0000092159 00000 n -0000092263 00000 n -0000092288 00000 n -0000092343 00000 n -0000092430 00000 n -0000092486 00000 n -0000092573 00000 n -0000092606 00000 n -0000092654 00000 n -0000092741 00000 n -0000092815 00000 n -0000092902 00000 n -0000092970 00000 n -0000093057 00000 n -0000093111 00000 n -0000093198 00000 n -0000093266 00000 n -0000093353 00000 n -0000093427 00000 n -0000093514 00000 n -0000093562 00000 n -0000093649 00000 n +0000057616 00000 n +0000057769 00000 n +0000057924 00000 n +0000058079 00000 n +0000058234 00000 n +0000058389 00000 n +0000058549 00000 n +0000058708 00000 n +0000058868 00000 n +0000059023 00000 n +0000059182 00000 n +0000059342 00000 n +0000059502 00000 n +0000059662 00000 n +0000059822 00000 n +0000059976 00000 n +0000060136 00000 n +0000060287 00000 n +0000060441 00000 n +0000060596 00000 n +0000060751 00000 n +0000060911 00000 n +0000061071 00000 n +0000061226 00000 n +0000061381 00000 n +0000061541 00000 n +0000061700 00000 n +0000061853 00000 n +0000062008 00000 n +0000062161 00000 n +0000062316 00000 n +0000062476 00000 n +0000062631 00000 n +0000062786 00000 n +0000062941 00000 n +0000063094 00000 n +0000063249 00000 n +0000063403 00000 n +0000074547 00000 n +0000065955 00000 n +0000063718 00000 n +0000074484 00000 n +0000066540 00000 n +0000066693 00000 n +0000066848 00000 n +0000067003 00000 n +0000067158 00000 n +0000067318 00000 n +0000067478 00000 n +0000067638 00000 n +0000067798 00000 n +0000067957 00000 n +0000068117 00000 n +0000068277 00000 n +0000068436 00000 n +0000068591 00000 n +0000068751 00000 n +0000068911 00000 n +0000069071 00000 n +0000069226 00000 n +0000069386 00000 n +0000069546 00000 n +0000069701 00000 n +0000069860 00000 n +0000070020 00000 n +0000070180 00000 n +0000070345 00000 n +0000070499 00000 n +0000070655 00000 n +0000070811 00000 n +0000070972 00000 n +0000071133 00000 n +0000071289 00000 n +0000071445 00000 n +0000071600 00000 n +0000071755 00000 n +0000071916 00000 n +0000072077 00000 n +0000072237 00000 n +0000072398 00000 n +0000072559 00000 n +0000072725 00000 n +0000072891 00000 n +0000073052 00000 n +0000073213 00000 n +0000073374 00000 n +0000073535 00000 n +0000073689 00000 n +0000073850 00000 n +0000074011 00000 n +0000074171 00000 n +0000074330 00000 n +0000085294 00000 n +0000076930 00000 n +0000074649 00000 n +0000085231 00000 n +0000077506 00000 n +0000077660 00000 n +0000077816 00000 n +0000077972 00000 n +0000078128 00000 n +0000078284 00000 n +0000078445 00000 n +0000078606 00000 n +0000078762 00000 n +0000078917 00000 n +0000079073 00000 n +0000079226 00000 n +0000079379 00000 n +0000079535 00000 n +0000079691 00000 n +0000079852 00000 n +0000080013 00000 n +0000080174 00000 n +0000080335 00000 n +0000080495 00000 n +0000080651 00000 n +0000080812 00000 n +0000080971 00000 n +0000081131 00000 n +0000081292 00000 n +0000081448 00000 n +0000081609 00000 n +0000081770 00000 n +0000081931 00000 n +0000082092 00000 n +0000082253 00000 n +0000082413 00000 n +0000082573 00000 n +0000082734 00000 n +0000082895 00000 n +0000083049 00000 n +0000083205 00000 n +0000083361 00000 n +0000083517 00000 n +0000083673 00000 n +0000083829 00000 n +0000083985 00000 n +0000084140 00000 n +0000084299 00000 n +0000084454 00000 n +0000084609 00000 n +0000084768 00000 n +0000084923 00000 n +0000085077 00000 n +0001010022 00000 n +0000095363 00000 n +0000087590 00000 n +0000085396 00000 n +0000095300 00000 n +0000088130 00000 n +0000088284 00000 n +0000088439 00000 n +0000088594 00000 n +0000088749 00000 n +0000088909 00000 n +0000089064 00000 n +0000089224 00000 n +0000089384 00000 n +0000089543 00000 n +0000089703 00000 n +0000089863 00000 n +0000090022 00000 n +0000090177 00000 n +0000090337 00000 n +0000090497 00000 n +0000090657 00000 n +0000090822 00000 n +0000090987 00000 n +0000091152 00000 n +0000091316 00000 n +0000091481 00000 n +0000091646 00000 n +0000091811 00000 n +0000091975 00000 n +0000092130 00000 n +0000092285 00000 n +0000092439 00000 n +0000092594 00000 n +0000092754 00000 n +0000092919 00000 n +0000093083 00000 n +0000093237 00000 n +0000093392 00000 n +0000093552 00000 n 0000093706 00000 n -0000093793 00000 n -0000093874 00000 n -0000093929 00000 n -0000094015 00000 n -0000094096 00000 n -0000094183 00000 n -0000094216 00000 n -0000094270 00000 n -0000094357 00000 n -0000094421 00000 n -0000094508 00000 n -0000094563 00000 n -0000094650 00000 n -0000094754 00000 n -0000094803 00000 n -0000094837 00000 n -0000094871 00000 n -0000101697 00000 n -0000101741 00000 n -0000101785 00000 n -0000101829 00000 n -0000101873 00000 n -0000101917 00000 n -0000101961 00000 n -0000102005 00000 n -0000102050 00000 n -0000102095 00000 n -0000102140 00000 n -0000102185 00000 n -0000102230 00000 n -0000102275 00000 n -0000102320 00000 n -0000102365 00000 n -0000102410 00000 n -0000102455 00000 n -0000102500 00000 n -0000102545 00000 n -0000102590 00000 n -0000102635 00000 n +0000093861 00000 n +0000094021 00000 n +0000094181 00000 n +0000094346 00000 n +0000094506 00000 n +0000094671 00000 n +0000094826 00000 n +0000094985 00000 n +0000095145 00000 n +0000105915 00000 n +0000097788 00000 n +0000095465 00000 n +0000105852 00000 n +0000098346 00000 n +0000098500 00000 n +0000098655 00000 n +0000098815 00000 n +0000098980 00000 n +0000099145 00000 n +0000099310 00000 n +0000099475 00000 n +0000099634 00000 n +0000099799 00000 n +0000099964 00000 n +0000100128 00000 n +0000100288 00000 n +0000100448 00000 n +0000100613 00000 n +0000100778 00000 n +0000100943 00000 n +0000101108 00000 n +0000101263 00000 n +0000101417 00000 n +0000101572 00000 n +0000101732 00000 n +0000101897 00000 n +0000102056 00000 n +0000102216 00000 n +0000102370 00000 n +0000102525 00000 n 0000102680 00000 n -0000102725 00000 n -0000102770 00000 n -0000102815 00000 n -0000102860 00000 n -0000102905 00000 n -0000102950 00000 n -0000102995 00000 n -0000103040 00000 n -0000103085 00000 n -0000103130 00000 n -0000103175 00000 n -0000103220 00000 n -0000103265 00000 n -0000103310 00000 n -0000103355 00000 n -0000103400 00000 n -0000103445 00000 n -0000103490 00000 n -0000103535 00000 n -0000103580 00000 n -0000103625 00000 n -0000103670 00000 n -0000103715 00000 n -0000103760 00000 n -0000103805 00000 n -0000103850 00000 n -0000103895 00000 n -0000103940 00000 n -0000103985 00000 n -0000104030 00000 n -0000104075 00000 n -0000104120 00000 n -0000104165 00000 n -0000104210 00000 n -0000104255 00000 n -0000104300 00000 n -0000104345 00000 n -0000104390 00000 n -0000104435 00000 n -0000104480 00000 n -0000104525 00000 n -0000104570 00000 n -0000104615 00000 n -0000104660 00000 n -0000104705 00000 n -0000104750 00000 n -0000104795 00000 n -0000104840 00000 n -0000104885 00000 n -0000104930 00000 n -0000104975 00000 n -0000105020 00000 n -0000105065 00000 n -0000105110 00000 n -0000105155 00000 n -0000105200 00000 n -0000105245 00000 n -0000105290 00000 n -0000105335 00000 n -0000105380 00000 n -0000105425 00000 n -0000105470 00000 n -0000105515 00000 n -0000105560 00000 n -0000105605 00000 n -0000105650 00000 n -0000105695 00000 n -0000105740 00000 n -0000105785 00000 n -0000105830 00000 n -0000105875 00000 n -0000105920 00000 n -0000105965 00000 n -0000106010 00000 n -0000106055 00000 n -0000106100 00000 n -0000106145 00000 n -0000106190 00000 n -0000106235 00000 n -0000106280 00000 n -0000106325 00000 n -0000106370 00000 n -0000106415 00000 n -0000106460 00000 n -0000106505 00000 n -0000106550 00000 n -0000106595 00000 n -0000106640 00000 n -0000106685 00000 n -0000106730 00000 n -0000106775 00000 n -0000106820 00000 n -0000106865 00000 n -0000106910 00000 n -0000106955 00000 n -0000107000 00000 n -0000107045 00000 n -0000107090 00000 n -0000107135 00000 n -0000107180 00000 n -0000107225 00000 n -0000107270 00000 n -0000107315 00000 n -0000107360 00000 n -0000107405 00000 n -0000107450 00000 n -0000107495 00000 n -0000107540 00000 n -0000107585 00000 n -0000107630 00000 n -0000107675 00000 n -0000107720 00000 n -0000107765 00000 n -0000107810 00000 n -0000107855 00000 n -0000107900 00000 n -0000107945 00000 n -0000107990 00000 n -0000108035 00000 n -0000108080 00000 n -0000108125 00000 n -0000108170 00000 n -0000108215 00000 n -0000108260 00000 n -0000108305 00000 n -0000108350 00000 n -0000108395 00000 n -0000108440 00000 n -0000108485 00000 n -0000108530 00000 n -0000108575 00000 n -0000108620 00000 n -0000108665 00000 n -0000108710 00000 n -0000108755 00000 n -0000108800 00000 n -0000108845 00000 n -0000108890 00000 n -0000108935 00000 n -0000108980 00000 n -0000109025 00000 n -0000109070 00000 n -0000109115 00000 n -0000109160 00000 n -0000109205 00000 n -0000109250 00000 n -0000109295 00000 n -0000109340 00000 n -0000109385 00000 n -0000109430 00000 n -0000109475 00000 n -0000109520 00000 n -0000109565 00000 n -0000109610 00000 n -0000109655 00000 n -0000109700 00000 n -0000109745 00000 n -0000109790 00000 n -0000109835 00000 n -0000109880 00000 n -0000109925 00000 n -0000109970 00000 n -0000110015 00000 n -0000110060 00000 n -0000110105 00000 n -0000110150 00000 n -0000110195 00000 n -0000110240 00000 n -0000110285 00000 n -0000110330 00000 n -0000110375 00000 n -0000110420 00000 n -0000110465 00000 n -0000110510 00000 n -0000110555 00000 n -0000110600 00000 n -0000110645 00000 n -0000110690 00000 n -0000110735 00000 n -0000110780 00000 n -0000110825 00000 n -0000110870 00000 n -0000110915 00000 n -0000110960 00000 n -0000111005 00000 n -0000111050 00000 n -0000111095 00000 n -0000111140 00000 n -0000111185 00000 n -0000111230 00000 n -0000111275 00000 n -0000111320 00000 n -0000111365 00000 n -0000111410 00000 n -0000111455 00000 n -0000111500 00000 n -0000111545 00000 n -0000111590 00000 n -0000111635 00000 n -0000111680 00000 n -0000111725 00000 n -0000111770 00000 n -0000111815 00000 n -0000111860 00000 n -0000111905 00000 n -0000111950 00000 n -0000111995 00000 n -0000112040 00000 n -0000112085 00000 n -0000112130 00000 n -0000112175 00000 n -0000112220 00000 n -0000112265 00000 n -0000112310 00000 n -0000112355 00000 n -0000112400 00000 n -0000112445 00000 n -0000112490 00000 n -0000112535 00000 n -0000112580 00000 n -0000112625 00000 n -0000112670 00000 n +0000102840 00000 n +0000102999 00000 n +0000103153 00000 n +0000103313 00000 n +0000103473 00000 n +0000103627 00000 n +0000103782 00000 n +0000103942 00000 n +0000104102 00000 n +0000104267 00000 n +0000104432 00000 n +0000104597 00000 n +0000104762 00000 n +0000104916 00000 n +0000105070 00000 n +0000105224 00000 n +0000105378 00000 n +0000105536 00000 n +0000105694 00000 n +0000115869 00000 n +0000108078 00000 n +0000106017 00000 n +0000115806 00000 n +0000108627 00000 n +0000108787 00000 n +0000108942 00000 n +0000109102 00000 n +0000109262 00000 n +0000109416 00000 n +0000109571 00000 n +0000109731 00000 n +0000109885 00000 n +0000110040 00000 n +0000110199 00000 n +0000110359 00000 n +0000110519 00000 n +0000110679 00000 n +0000110834 00000 n +0000110994 00000 n +0000111154 00000 n +0000111314 00000 n +0000111474 00000 n +0000111633 00000 n +0000111787 00000 n +0000111941 00000 n +0000112095 00000 n +0000112250 00000 n +0000112405 00000 n +0000112560 00000 n 0000112715 00000 n -0000112760 00000 n -0000112805 00000 n -0000112850 00000 n -0000112895 00000 n -0000112940 00000 n -0000112985 00000 n -0000113030 00000 n -0000113075 00000 n -0000113120 00000 n -0000113165 00000 n -0000113210 00000 n -0000113255 00000 n -0000113300 00000 n -0000113345 00000 n -0000113390 00000 n -0000113435 00000 n -0000113480 00000 n -0000113525 00000 n -0000113570 00000 n -0000113615 00000 n -0000113660 00000 n -0000113705 00000 n -0000113750 00000 n -0000113795 00000 n -0000113840 00000 n -0000113885 00000 n -0000113930 00000 n -0000113975 00000 n -0000114020 00000 n -0000114065 00000 n -0000114110 00000 n -0000114155 00000 n -0000114200 00000 n -0000114245 00000 n -0000114290 00000 n -0000114335 00000 n -0000114380 00000 n -0000114425 00000 n -0000114470 00000 n -0000114515 00000 n -0000114560 00000 n -0000114605 00000 n -0000114650 00000 n -0000114695 00000 n -0000114740 00000 n -0000114785 00000 n -0000114830 00000 n -0000114875 00000 n -0000114920 00000 n -0000114965 00000 n -0000115010 00000 n -0000115055 00000 n -0000115100 00000 n -0000115145 00000 n -0000115190 00000 n -0000115235 00000 n -0000115280 00000 n -0000115325 00000 n -0000115370 00000 n -0000115415 00000 n -0000115460 00000 n -0000115505 00000 n -0000115550 00000 n -0000115595 00000 n -0000115640 00000 n -0000115685 00000 n -0000115730 00000 n -0000115775 00000 n -0000115820 00000 n -0000115865 00000 n -0000115910 00000 n -0000115955 00000 n -0000116000 00000 n -0000116045 00000 n -0000116090 00000 n -0000116135 00000 n -0000116180 00000 n -0000116225 00000 n -0000116270 00000 n -0000116315 00000 n -0000116360 00000 n -0000116405 00000 n -0000116450 00000 n -0000116495 00000 n -0000116540 00000 n -0000116585 00000 n -0000116630 00000 n -0000116675 00000 n -0000116720 00000 n -0000116765 00000 n -0000116810 00000 n -0000116855 00000 n -0000116900 00000 n -0000116945 00000 n -0000116990 00000 n -0000117035 00000 n -0000117080 00000 n -0000117125 00000 n -0000117170 00000 n -0000117215 00000 n -0000117260 00000 n -0000117305 00000 n -0000117350 00000 n -0000117395 00000 n -0000117440 00000 n -0000117485 00000 n -0000117530 00000 n -0000117575 00000 n -0000117620 00000 n -0000117665 00000 n -0000117710 00000 n -0000117755 00000 n -0000117800 00000 n -0000117845 00000 n -0000117890 00000 n -0000117935 00000 n -0000117980 00000 n -0000118025 00000 n -0000118070 00000 n -0000118115 00000 n -0000118160 00000 n -0000118205 00000 n -0000118250 00000 n -0000118295 00000 n -0000118340 00000 n -0000118385 00000 n -0000118429 00000 n -0000118474 00000 n -0000118519 00000 n -0000118564 00000 n -0000118609 00000 n -0000118654 00000 n -0000118699 00000 n -0000118744 00000 n -0000118789 00000 n -0000118834 00000 n -0000118879 00000 n -0000118924 00000 n -0000118969 00000 n -0000119014 00000 n -0000119059 00000 n -0000119104 00000 n -0000119149 00000 n -0000119194 00000 n -0000119239 00000 n -0000119284 00000 n -0000119329 00000 n -0000119374 00000 n -0000119419 00000 n -0000121259 00000 n -0000121420 00000 n -0000121589 00000 n -0000121782 00000 n -0000125683 00000 n -0000125877 00000 n -0000129684 00000 n -0000129878 00000 n -0000135036 00000 n -0000135230 00000 n -0000139393 00000 n -0000139587 00000 n -0000143499 00000 n -0000143693 00000 n -0000147516 00000 n -0000147710 00000 n -0000151497 00000 n -0000151691 00000 n -0000155674 00000 n -0000155868 00000 n -0000157463 00000 n -0000157675 00000 n -0000159650 00000 n -0000159834 00000 n -0000163045 00000 n -0000163229 00000 n -0000166130 00000 n -0000166305 00000 n -0000169056 00000 n -0000169231 00000 n -0000170935 00000 n -0000171096 00000 n -0000171284 00000 n -0000171454 00000 n -0000171766 00000 n -0000171955 00000 n -0000174141 00000 n -0000174321 00000 n -0000176495 00000 n -0000176684 00000 n -0000178855 00000 n -0000179034 00000 n -0000180227 00000 n -0000180439 00000 n -0000181949 00000 n -0000182166 00000 n -0000183599 00000 n -0000183802 00000 n -0000185726 00000 n -0000185946 00000 n -0000187772 00000 n -0000187970 00000 n -0000189898 00000 n -0000190105 00000 n -0000192023 00000 n -0000192232 00000 n -0000194544 00000 n -0000194732 00000 n -0000195923 00000 n -0000196152 00000 n -0000198021 00000 n -0000198250 00000 n -0000199817 00000 n -0000200014 00000 n -0000201509 00000 n -0000201722 00000 n -0000203907 00000 n -0000204110 00000 n -0000205859 00000 n -0000206073 00000 n -0000207485 00000 n -0000207707 00000 n -0000209406 00000 n -0000209610 00000 n -0000211358 00000 n -0000211556 00000 n -0000212782 00000 n -0000213021 00000 n -0000214640 00000 n -0000214837 00000 n -0000216010 00000 n -0000216171 00000 n -0000216361 00000 n -0000216531 00000 n -0000216829 00000 n -0000217018 00000 n -0000218704 00000 n -0000218892 00000 n -0000220323 00000 n -0000220520 00000 n -0000222281 00000 n -0000222461 00000 n -0000224425 00000 n -0000224638 00000 n -0000226435 00000 n -0000226657 00000 n -0000227714 00000 n -0000227944 00000 n -0000229337 00000 n -0000229551 00000 n -0000231074 00000 n -0000231287 00000 n -0000233291 00000 n -0000233565 00000 n -0000235350 00000 n -0000235563 00000 n -0000237174 00000 n -0000237372 00000 n -0000239039 00000 n -0000239218 00000 n -0000241250 00000 n -0000241480 00000 n -0000243300 00000 n -0000243494 00000 n -0000245049 00000 n -0000245229 00000 n -0000246969 00000 n -0000247158 00000 n -0000248359 00000 n -0000248624 00000 n -0000250091 00000 n -0000250289 00000 n -0000251269 00000 n -0000251501 00000 n -0000252904 00000 n -0000253139 00000 n -0000255056 00000 n -0000255217 00000 n -0000255410 00000 n -0000255580 00000 n -0000255880 00000 n -0000256119 00000 n -0000257874 00000 n -0000258081 00000 n -0000259925 00000 n -0000260123 00000 n -0000261768 00000 n -0000261980 00000 n -0000263396 00000 n -0000263575 00000 n -0000264392 00000 n -0000264589 00000 n -0000266084 00000 n -0000266348 00000 n -0000268071 00000 n -0000268317 00000 n -0000270245 00000 n -0000270477 00000 n -0000272487 00000 n -0000272719 00000 n -0000274371 00000 n -0000274575 00000 n -0000275920 00000 n -0000276142 00000 n -0000277705 00000 n -0000277884 00000 n -0000279453 00000 n -0000279632 00000 n -0000281152 00000 n -0000281331 00000 n -0000282834 00000 n -0000283013 00000 n -0000284679 00000 n -0000284849 00000 n -0000285594 00000 n -0000285816 00000 n -0000287734 00000 n -0000287975 00000 n -0000289704 00000 n -0000289916 00000 n -0000291975 00000 n -0000292173 00000 n -0000294227 00000 n -0000294434 00000 n -0000296252 00000 n -0000296465 00000 n -0000298568 00000 n -0000298775 00000 n -0000300524 00000 n -0000300711 00000 n -0000302390 00000 n -0000302579 00000 n -0000303471 00000 n -0000303641 00000 n -0000304739 00000 n -0000304909 00000 n -0000305600 00000 n -0000305770 00000 n -0000306631 00000 n -0000306801 00000 n -0000307902 00000 n -0000308125 00000 n -0000309507 00000 n -0000309723 00000 n -0000311503 00000 n -0000311738 00000 n -0000313722 00000 n -0000313901 00000 n -0000315704 00000 n -0000315873 00000 n -0000317384 00000 n -0000317642 00000 n -0000319991 00000 n -0000320212 00000 n -0000322355 00000 n -0000322575 00000 n -0000324444 00000 n -0000324663 00000 n -0000326321 00000 n -0000326510 00000 n -0000328202 00000 n -0000328381 00000 n -0000330126 00000 n -0000330314 00000 n -0000332148 00000 n -0000332342 00000 n -0000334257 00000 n -0000334488 00000 n -0000336593 00000 n -0000336805 00000 n -0000338241 00000 n -0000338454 00000 n -0000339903 00000 n -0000340110 00000 n -0000341347 00000 n -0000341526 00000 n -0000342513 00000 n -0000342701 00000 n -0000343833 00000 n -0000344021 00000 n -0000345522 00000 n -0000345710 00000 n -0000346792 00000 n -0000346981 00000 n -0000348314 00000 n -0000348520 00000 n -0000350170 00000 n -0000350424 00000 n -0000352205 00000 n -0000352374 00000 n -0000353770 00000 n -0000353939 00000 n -0000354707 00000 n -0000354910 00000 n -0000356865 00000 n -0000357062 00000 n -0000359262 00000 n -0000359482 00000 n -0000361458 00000 n -0000361646 00000 n -0000363383 00000 n -0000363562 00000 n -0000364887 00000 n -0000365127 00000 n -0000366643 00000 n -0000366840 00000 n -0000368665 00000 n -0000368853 00000 n -0000370852 00000 n -0000371095 00000 n -0000372920 00000 n -0000373109 00000 n -0000374742 00000 n -0000374963 00000 n -0000376662 00000 n -0000376884 00000 n -0000378540 00000 n -0000378719 00000 n -0000380608 00000 n -0000380786 00000 n -0000382127 00000 n -0000382359 00000 n -0000384185 00000 n -0000384363 00000 n -0000385772 00000 n -0000385932 00000 n -0000386222 00000 n -0000386401 00000 n -0000388180 00000 n -0000388378 00000 n -0000390106 00000 n -0000390326 00000 n -0000391934 00000 n -0000392163 00000 n -0000393722 00000 n -0000393932 00000 n -0000395624 00000 n -0000395827 00000 n -0000396948 00000 n -0000397145 00000 n -0000398422 00000 n -0000398625 00000 n -0000399738 00000 n -0000399923 00000 n -0000400775 00000 n -0000400988 00000 n -0000402475 00000 n -0000402655 00000 n -0000403419 00000 n -0000403660 00000 n -0000405267 00000 n -0000405465 00000 n -0000407315 00000 n -0000407512 00000 n -0000409135 00000 n -0000409314 00000 n -0000411367 00000 n -0000411546 00000 n -0000413384 00000 n -0000413563 00000 n -0000415273 00000 n -0000415452 00000 n -0000415883 00000 n -0000416103 00000 n -0000417840 00000 n -0000418037 00000 n -0000419891 00000 n -0000420060 00000 n -0000421757 00000 n -0000421926 00000 n -0000423135 00000 n -0000423323 00000 n -0000425021 00000 n -0000425209 00000 n -0000426665 00000 n -0000426878 00000 n -0000428480 00000 n -0000428668 00000 n -0000430329 00000 n -0000430517 00000 n -0000431346 00000 n -0000431534 00000 n -0000433105 00000 n -0000433299 00000 n -0000434565 00000 n -0000434777 00000 n -0000436371 00000 n -0000436593 00000 n -0000437510 00000 n -0000437671 00000 n -0000437871 00000 n -0000438065 00000 n -0000439648 00000 n -0000439861 00000 n -0000441389 00000 n -0000441577 00000 n -0000442839 00000 n -0000443027 00000 n -0000444296 00000 n -0000444549 00000 n -0000445886 00000 n -0000446084 00000 n -0000447614 00000 n -0000447793 00000 n -0000448726 00000 n -0000448905 00000 n -0000450433 00000 n -0000450621 00000 n -0000451590 00000 n -0000451769 00000 n -0000452602 00000 n -0000452797 00000 n -0000454528 00000 n -0000454741 00000 n -0000456424 00000 n -0000456618 00000 n -0000458325 00000 n -0000458560 00000 n -0000460245 00000 n -0000460415 00000 n -0000460942 00000 n -0000461112 00000 n -0000462619 00000 n -0000462789 00000 n -0000464188 00000 n -0000464358 00000 n -0000465908 00000 n -0000466077 00000 n -0000467041 00000 n -0000467291 00000 n -0000468760 00000 n -0000468947 00000 n -0000470891 00000 n -0000471120 00000 n -0000472980 00000 n -0000473187 00000 n -0000475319 00000 n -0000475522 00000 n -0000476277 00000 n -0000476481 00000 n -0000478283 00000 n -0000478505 00000 n -0000480369 00000 n -0000480591 00000 n -0000482145 00000 n -0000482358 00000 n -0000484104 00000 n -0000484321 00000 n -0000486105 00000 n -0000486164 00000 n -0000486267 00000 n -0000486432 00000 n -0000486528 00000 n -0000486646 00000 n -0000486762 00000 n -0000486871 00000 n -0000486994 00000 n -0000487106 00000 n -0000487276 00000 n -0000487377 00000 n -0000487493 00000 n -0000487614 00000 n -0000487734 00000 n -0000487859 00000 n -0000487972 00000 n -0000488076 00000 n -0000488254 00000 n -0000488375 00000 n -0000488535 00000 n -0000488653 00000 n -0000488750 00000 n -0000488902 00000 n -0000489042 00000 n -0000489220 00000 n -0000489375 00000 n -0000489477 00000 n -0000489577 00000 n -0000489786 00000 n -0000489887 00000 n -0000490075 00000 n -0000490216 00000 n -0000490360 00000 n -0000490514 00000 n -0000490623 00000 n -0000490735 00000 n -0000490902 00000 n -0000491014 00000 n -0000491188 00000 n -0000491291 00000 n -0000491464 00000 n -0000491585 00000 n -0000491715 00000 n -0000491841 00000 n -0000491956 00000 n -0000492064 00000 n -0000492211 00000 n -0000492316 00000 n -0000492435 00000 n -0000492564 00000 n -0000492723 00000 n -0000492857 00000 n -0000492994 00000 n -0000493126 00000 n -0000493275 00000 n -0000493407 00000 n -0000493555 00000 n -0000493669 00000 n -0000493787 00000 n -0000493941 00000 n -0000494072 00000 n -0000494166 00000 n -0000494290 00000 n -0000494402 00000 n -0000494579 00000 n -0000494688 00000 n -0000494813 00000 n -0000494959 00000 n -0000495061 00000 n -0000495237 00000 n -0000495381 00000 n -0000495493 00000 n -0000495620 00000 n -0000495748 00000 n -0000495876 00000 n -0000495987 00000 n -0000496186 00000 n -0000496297 00000 n -0000496412 00000 n -0000496556 00000 n -0000496764 00000 n -0000496898 00000 n -0000497052 00000 n -0000497177 00000 n -0000497346 00000 n -0000497479 00000 n -0000497767 00000 n -0000497920 00000 n -0000498114 00000 n -0000498325 00000 n -0000498486 00000 n -0000498607 00000 n -0000498810 00000 n -0000498921 00000 n -0000499036 00000 n -0000499229 00000 n -0000499372 00000 n -0000499488 00000 n -0000499646 00000 n -0000499803 00000 n -0000499934 00000 n -0000500055 00000 n -0000500232 00000 n +0000112870 00000 n +0000113024 00000 n +0000113178 00000 n +0000113333 00000 n +0000113488 00000 n +0000113643 00000 n +0000113797 00000 n +0000113952 00000 n +0000114107 00000 n +0000114262 00000 n +0000114422 00000 n +0000114582 00000 n +0000114737 00000 n +0000114891 00000 n +0000115041 00000 n +0000115195 00000 n +0000115349 00000 n +0000115501 00000 n +0000115653 00000 n +0000125988 00000 n +0000118134 00000 n +0000115971 00000 n +0000125925 00000 n +0000118683 00000 n +0000118837 00000 n +0000118992 00000 n +0000119147 00000 n +0000119302 00000 n +0000119457 00000 n +0000119612 00000 n +0000119766 00000 n +0000119921 00000 n +0000120076 00000 n +0000120230 00000 n +0000120385 00000 n +0000120540 00000 n +0000120695 00000 n +0000120845 00000 n +0000120999 00000 n +0000121154 00000 n +0000121314 00000 n +0000121474 00000 n +0000121639 00000 n +0000121804 00000 n +0000121959 00000 n +0000122114 00000 n +0000122268 00000 n +0000122428 00000 n +0000122593 00000 n +0000122757 00000 n +0000122911 00000 n +0000123071 00000 n +0000123231 00000 n +0000123385 00000 n +0000123540 00000 n +0000123700 00000 n +0000123865 00000 n +0000124029 00000 n +0000124194 00000 n +0000124359 00000 n +0000124524 00000 n +0000124683 00000 n +0000124838 00000 n +0000124998 00000 n +0000125158 00000 n +0000125312 00000 n +0000125467 00000 n +0000125620 00000 n +0000125773 00000 n +0000135862 00000 n +0000128178 00000 n +0000126090 00000 n +0000135799 00000 n +0000128718 00000 n +0000128873 00000 n +0000129033 00000 n +0000129188 00000 n +0000129348 00000 n +0000129508 00000 n +0000129662 00000 n +0000129817 00000 n +0000129971 00000 n +0000130131 00000 n +0000130291 00000 n +0000130451 00000 n +0000130611 00000 n +0000130766 00000 n +0000130926 00000 n +0000131086 00000 n +0000131246 00000 n +0000131405 00000 n +0000131565 00000 n +0000131725 00000 n +0000131879 00000 n +0000132038 00000 n +0000132193 00000 n +0000132348 00000 n +0000132502 00000 n +0000132657 00000 n +0000132817 00000 n +0000132977 00000 n +0000133136 00000 n +0000133295 00000 n +0000133455 00000 n +0000133615 00000 n +0000133774 00000 n +0000133934 00000 n +0000134094 00000 n +0000134255 00000 n +0000134409 00000 n +0000134564 00000 n +0000134719 00000 n +0000134874 00000 n +0000135028 00000 n +0000135183 00000 n +0000135338 00000 n +0000135492 00000 n +0000135646 00000 n +0000136517 00000 n +0000136271 00000 n +0000135964 00000 n +0000136394 00000 n +0001010147 00000 n +0000140649 00000 n +0000140030 00000 n +0000136605 00000 n +0000140153 00000 n +0000140216 00000 n +0000140340 00000 n +0000924091 00000 n +0000906588 00000 n +0000923925 00000 n +0000140464 00000 n +0000140587 00000 n +0000905160 00000 n +0000903069 00000 n +0000904994 00000 n +0000144592 00000 n +0000144282 00000 n +0000140765 00000 n +0000144405 00000 n +0000144529 00000 n +0000148987 00000 n +0000148148 00000 n +0000144708 00000 n +0000148677 00000 n +0000148801 00000 n +0000148925 00000 n +0000148301 00000 n +0000148486 00000 n +0000154858 00000 n +0000152423 00000 n +0000149117 00000 n +0000154548 00000 n +0000152648 00000 n +0000152818 00000 n +0000153017 00000 n +0000153212 00000 n +0000153401 00000 n +0000153594 00000 n +0000153789 00000 n +0000153974 00000 n +0000154166 00000 n +0000154672 00000 n +0000154361 00000 n +0000154796 00000 n +0000158774 00000 n +0000157454 00000 n +0000154988 00000 n +0000158093 00000 n +0000158217 00000 n +0000158341 00000 n +0000157616 00000 n +0000157782 00000 n +0000158464 00000 n +0000158588 00000 n +0000157935 00000 n +0000158711 00000 n +0000770401 00000 n +0000690139 00000 n +0000163003 00000 n +0000161866 00000 n +0000158890 00000 n +0000162322 00000 n +0000162446 00000 n +0000162569 00000 n +0000162693 00000 n +0000162817 00000 n +0000901167 00000 n +0000899153 00000 n +0000901002 00000 n +0000162940 00000 n +0000162019 00000 n +0000162171 00000 n +0001010272 00000 n +0000725271 00000 n +0000747347 00000 n +0000163727 00000 n +0000163480 00000 n +0000163161 00000 n +0000163603 00000 n +0000167030 00000 n +0000166410 00000 n +0000163815 00000 n +0000166533 00000 n +0000166596 00000 n +0000166720 00000 n +0000166844 00000 n +0000166968 00000 n +0000170835 00000 n +0000170402 00000 n +0000167160 00000 n +0000170525 00000 n +0000170649 00000 n +0000170773 00000 n +0000174672 00000 n +0000173862 00000 n +0000170951 00000 n +0000173985 00000 n +0000174110 00000 n +0000174235 00000 n +0000174360 00000 n +0000174423 00000 n +0000174486 00000 n +0000174609 00000 n +0000178269 00000 n +0000180112 00000 n +0000178146 00000 n +0000174774 00000 n +0000179799 00000 n +0000179924 00000 n +0000898554 00000 n +0000890154 00000 n +0000898387 00000 n +0000888713 00000 n +0000885289 00000 n +0000888546 00000 n +0000884330 00000 n +0000872635 00000 n +0000884164 00000 n +0000180049 00000 n +0000179628 00000 n +0000179686 00000 n +0000179776 00000 n +0000183718 00000 n +0000183407 00000 n +0000180327 00000 n +0000183530 00000 n +0000183655 00000 n +0001010397 00000 n +0000187660 00000 n +0000186930 00000 n +0000183862 00000 n +0000187224 00000 n +0000187348 00000 n +0000187473 00000 n +0000187074 00000 n +0000187598 00000 n +0000495602 00000 n +0000190294 00000 n +0000189733 00000 n +0000187818 00000 n +0000189856 00000 n +0000189981 00000 n +0000190106 00000 n +0000190231 00000 n +0000193030 00000 n +0000192530 00000 n +0000190467 00000 n +0000192653 00000 n +0000192716 00000 n +0000192779 00000 n +0000192842 00000 n +0000192967 00000 n +0000195507 00000 n +0000195151 00000 n +0000193160 00000 n +0000195444 00000 n +0000195295 00000 n +0000310760 00000 n +0000199343 00000 n +0000198862 00000 n +0000195680 00000 n +0000199155 00000 n +0000199280 00000 n +0000199006 00000 n +0000203431 00000 n +0000202932 00000 n +0000199487 00000 n +0000203243 00000 n +0000203368 00000 n +0000203076 00000 n +0001010522 00000 n +0000206961 00000 n +0000208270 00000 n +0000206817 00000 n +0000203632 00000 n +0000207957 00000 n +0000208082 00000 n +0000207774 00000 n +0000208207 00000 n +0000212502 00000 n +0000211639 00000 n +0000208471 00000 n +0000211940 00000 n +0000211783 00000 n +0000212065 00000 n +0000212190 00000 n +0000212315 00000 n +0000212439 00000 n +0000245941 00000 n +0000216925 00000 n +0000216368 00000 n +0000212674 00000 n +0000216491 00000 n +0000216616 00000 n +0000216739 00000 n +0000216862 00000 n +0000220117 00000 n +0000219366 00000 n +0000217041 00000 n +0000219489 00000 n +0000219552 00000 n +0000219615 00000 n +0000219678 00000 n +0000219741 00000 n +0000219804 00000 n +0000219867 00000 n +0000219930 00000 n +0000220054 00000 n +0000222836 00000 n +0000222650 00000 n +0000220247 00000 n +0000222773 00000 n +0000226445 00000 n +0000225567 00000 n +0000222995 00000 n +0000225885 00000 n +0000226010 00000 n +0000226135 00000 n +0000225711 00000 n +0000226260 00000 n +0000226383 00000 n +0001010647 00000 n +0000230556 00000 n +0000229871 00000 n +0000226547 00000 n +0000229994 00000 n +0000230119 00000 n +0000230244 00000 n +0000230368 00000 n +0000230493 00000 n +0000233669 00000 n +0000233233 00000 n +0000230672 00000 n +0000233356 00000 n +0000233481 00000 n +0000233606 00000 n +0000236054 00000 n +0000235494 00000 n +0000233799 00000 n +0000235617 00000 n +0000235742 00000 n +0000235867 00000 n +0000235992 00000 n +0000240181 00000 n +0000238923 00000 n +0000236227 00000 n +0000239743 00000 n +0000239094 00000 n +0000239254 00000 n +0000239416 00000 n +0000239586 00000 n +0000239868 00000 n +0000239993 00000 n +0000240118 00000 n +0000241907 00000 n +0000242095 00000 n +0000241659 00000 n +0000240354 00000 n +0000241782 00000 n +0000242032 00000 n +0000246128 00000 n +0000244750 00000 n +0000242211 00000 n +0000245816 00000 n +0000246066 00000 n +0000244930 00000 n +0000245108 00000 n +0000245286 00000 n +0000245472 00000 n +0000245654 00000 n +0001010772 00000 n +0000250710 00000 n +0000249608 00000 n +0000246258 00000 n +0000250522 00000 n +0000250647 00000 n +0000249779 00000 n +0000249969 00000 n +0000250135 00000 n +0000250309 00000 n +0000251473 00000 n +0000251226 00000 n +0000250911 00000 n +0000251349 00000 n +0000254350 00000 n +0000253851 00000 n +0000251561 00000 n +0000253974 00000 n +0000254037 00000 n +0000254162 00000 n +0000254287 00000 n +0000257531 00000 n +0000257220 00000 n +0000254509 00000 n +0000257343 00000 n +0000257468 00000 n +0000261892 00000 n +0000261581 00000 n +0000257661 00000 n +0000261704 00000 n +0000261829 00000 n +0000265096 00000 n +0000264785 00000 n +0000262022 00000 n +0000264908 00000 n +0000265033 00000 n +0001010897 00000 n +0000268529 00000 n +0000267738 00000 n +0000265226 00000 n +0000268217 00000 n +0000268341 00000 n +0000267891 00000 n +0000268054 00000 n +0000268466 00000 n +0000272855 00000 n +0000272357 00000 n +0000268673 00000 n +0000272480 00000 n +0000272604 00000 n +0000272667 00000 n +0000272730 00000 n +0000272793 00000 n +0000276556 00000 n +0000275808 00000 n +0000272985 00000 n +0000275931 00000 n +0000275994 00000 n +0000276118 00000 n +0000276243 00000 n +0000276368 00000 n +0000276493 00000 n +0000280418 00000 n +0000281421 00000 n +0000280295 00000 n +0000276686 00000 n +0000281233 00000 n +0000281358 00000 n +0000285520 00000 n +0000285084 00000 n +0000281608 00000 n +0000285207 00000 n +0000285332 00000 n +0000871442 00000 n +0000869441 00000 n +0000871276 00000 n +0000285457 00000 n +0000289511 00000 n +0000288826 00000 n +0000285678 00000 n +0000288949 00000 n +0000289074 00000 n +0000289199 00000 n +0000289323 00000 n +0000289448 00000 n +0001011022 00000 n +0000292553 00000 n +0000292243 00000 n +0000289698 00000 n +0000292366 00000 n +0000292491 00000 n +0000296884 00000 n +0000296448 00000 n +0000292683 00000 n +0000296571 00000 n +0000296696 00000 n +0000296821 00000 n +0000300521 00000 n +0000300085 00000 n +0000297099 00000 n +0000300208 00000 n +0000300333 00000 n +0000300458 00000 n +0000303934 00000 n +0000303748 00000 n +0000300637 00000 n +0000303871 00000 n +0000305975 00000 n +0000305789 00000 n +0000304050 00000 n +0000305912 00000 n +0000307748 00000 n +0000307373 00000 n +0000306077 00000 n +0000307496 00000 n +0000307559 00000 n +0000307622 00000 n +0000307685 00000 n +0001011147 00000 n +0000311073 00000 n +0000310512 00000 n +0000307850 00000 n +0000310635 00000 n +0000310885 00000 n +0000311010 00000 n +0000313480 00000 n +0000313294 00000 n +0000311175 00000 n +0000313417 00000 n +0000317448 00000 n +0000316887 00000 n +0000313653 00000 n +0000317010 00000 n +0000317135 00000 n +0000317260 00000 n +0000317385 00000 n +0000322844 00000 n +0000320888 00000 n +0000317606 00000 n +0000322157 00000 n +0000322282 00000 n +0000322407 00000 n +0000322532 00000 n +0000322657 00000 n +0000321077 00000 n +0000321248 00000 n +0000321433 00000 n +0000321600 00000 n +0000321801 00000 n +0000322781 00000 n +0000321973 00000 n +0000327947 00000 n +0000326411 00000 n +0000322988 00000 n +0000327634 00000 n +0000326600 00000 n +0000326769 00000 n +0000327759 00000 n +0000326938 00000 n +0000327117 00000 n +0000327296 00000 n +0000327884 00000 n +0000327467 00000 n +0000330666 00000 n +0000330232 00000 n +0000328077 00000 n +0000330355 00000 n +0000330478 00000 n +0000330603 00000 n +0001011272 00000 n +0000334665 00000 n +0000332457 00000 n +0000330782 00000 n +0000334477 00000 n +0000334602 00000 n +0000332682 00000 n +0000332865 00000 n +0000333041 00000 n +0000333222 00000 n +0000333402 00000 n +0000333582 00000 n +0000333759 00000 n +0000333945 00000 n +0000334128 00000 n +0000334309 00000 n +0000338167 00000 n +0000337561 00000 n +0000334795 00000 n +0000337854 00000 n +0000337979 00000 n +0000338104 00000 n +0000337705 00000 n +0000341259 00000 n +0000340948 00000 n +0000338325 00000 n +0000341071 00000 n +0000341196 00000 n +0000344660 00000 n +0000344154 00000 n +0000341389 00000 n +0000344472 00000 n +0000344298 00000 n +0000868209 00000 n +0000866336 00000 n +0000868041 00000 n +0000344597 00000 n +0000347439 00000 n +0000346879 00000 n +0000344818 00000 n +0000347002 00000 n +0000347126 00000 n +0000347251 00000 n +0000347376 00000 n +0000349365 00000 n +0000349179 00000 n +0000347583 00000 n +0000349302 00000 n +0001011397 00000 n +0000352039 00000 n +0000351478 00000 n +0000349524 00000 n +0000351601 00000 n +0000351726 00000 n +0000351851 00000 n +0000351976 00000 n +0000355709 00000 n +0000355023 00000 n +0000352169 00000 n +0000355146 00000 n +0000355271 00000 n +0000355396 00000 n +0000355521 00000 n +0000355646 00000 n +0000360449 00000 n +0000359891 00000 n +0000355896 00000 n +0000360014 00000 n +0000360138 00000 n +0000360263 00000 n +0000360387 00000 n +0000364480 00000 n +0000364044 00000 n +0000360607 00000 n +0000364167 00000 n +0000364292 00000 n +0000364417 00000 n +0000369263 00000 n +0000368170 00000 n +0000364610 00000 n +0000369075 00000 n +0000368341 00000 n +0000368523 00000 n +0000368703 00000 n +0000368890 00000 n +0000369200 00000 n +0000370153 00000 n +0000369967 00000 n +0000369407 00000 n +0000370090 00000 n +0001011522 00000 n +0000373674 00000 n +0000373174 00000 n +0000370255 00000 n +0000373297 00000 n +0000373422 00000 n +0000373485 00000 n +0000373548 00000 n +0000373611 00000 n +0000374950 00000 n +0000374764 00000 n +0000373790 00000 n +0000374887 00000 n +0000379074 00000 n +0000377909 00000 n +0000375066 00000 n +0000378636 00000 n +0000378761 00000 n +0000378886 00000 n +0000378071 00000 n +0000378251 00000 n +0000378426 00000 n +0000379011 00000 n +0000383435 00000 n +0000382185 00000 n +0000379275 00000 n +0000383248 00000 n +0000383373 00000 n +0000382365 00000 n +0000382542 00000 n +0000382711 00000 n +0000382888 00000 n +0000383068 00000 n +0000387201 00000 n +0000386687 00000 n +0000383622 00000 n +0000387013 00000 n +0000386831 00000 n +0000387138 00000 n +0000390255 00000 n +0000389753 00000 n +0000387402 00000 n +0000390067 00000 n +0000390192 00000 n +0000389897 00000 n +0001011647 00000 n +0000394049 00000 n +0000392939 00000 n +0000390399 00000 n +0000393861 00000 n +0000393986 00000 n +0000393110 00000 n +0000393298 00000 n +0000393485 00000 n +0000393675 00000 n +0000397540 00000 n +0000396584 00000 n +0000394193 00000 n +0000397102 00000 n +0000397227 00000 n +0000396737 00000 n +0000397352 00000 n +0000396923 00000 n +0000397477 00000 n +0000401252 00000 n +0000400691 00000 n +0000397670 00000 n +0000400814 00000 n +0000400939 00000 n +0000401064 00000 n +0000401189 00000 n +0000404213 00000 n +0000403777 00000 n +0000401410 00000 n +0000403900 00000 n +0000404025 00000 n +0000404150 00000 n +0000406974 00000 n +0000406663 00000 n +0000404329 00000 n +0000406786 00000 n +0000406911 00000 n +0000410374 00000 n +0000409437 00000 n +0000407104 00000 n +0000409560 00000 n +0000409685 00000 n +0000409810 00000 n +0000409873 00000 n +0000409936 00000 n +0000409999 00000 n +0000410062 00000 n +0000410125 00000 n +0000410188 00000 n +0000410250 00000 n +0000410312 00000 n +0001011772 00000 n +0000413658 00000 n +0000413222 00000 n +0000410504 00000 n +0000413345 00000 n +0000413470 00000 n +0000413595 00000 n +0000415918 00000 n +0000415357 00000 n +0000413774 00000 n +0000415480 00000 n +0000415605 00000 n +0000415730 00000 n +0000415855 00000 n +0000419815 00000 n +0000419065 00000 n +0000416034 00000 n +0000419378 00000 n +0000419503 00000 n +0000419628 00000 n +0000419209 00000 n +0000419752 00000 n +0000423257 00000 n +0000422946 00000 n +0000419931 00000 n +0000423069 00000 n +0000423194 00000 n +0000426455 00000 n +0000426269 00000 n +0000423486 00000 n +0000426392 00000 n +0000429412 00000 n +0000429226 00000 n +0000426656 00000 n +0000429349 00000 n +0001011897 00000 n +0000433799 00000 n +0000433488 00000 n +0000429571 00000 n +0000433611 00000 n +0000433736 00000 n +0000436889 00000 n +0000436453 00000 n +0000433957 00000 n +0000436576 00000 n +0000436701 00000 n +0000436826 00000 n +0000441570 00000 n +0000440085 00000 n +0000437033 00000 n +0000441382 00000 n +0000441507 00000 n +0000440274 00000 n +0000440455 00000 n +0000440638 00000 n +0000440812 00000 n +0000441023 00000 n +0000441204 00000 n +0000444699 00000 n +0000444388 00000 n +0000441714 00000 n +0000444511 00000 n +0000444636 00000 n +0000446306 00000 n +0000446120 00000 n +0000444829 00000 n +0000446243 00000 n +0000449069 00000 n +0000448758 00000 n +0000446408 00000 n +0000448881 00000 n +0000449006 00000 n +0001012022 00000 n +0000450303 00000 n +0000450117 00000 n +0000449213 00000 n +0000450240 00000 n +0000451802 00000 n +0000451616 00000 n +0000450405 00000 n +0000451739 00000 n +0000452865 00000 n +0000452679 00000 n +0000451904 00000 n +0000452802 00000 n +0000454108 00000 n +0000453922 00000 n +0000452967 00000 n +0000454045 00000 n +0000455454 00000 n +0000455268 00000 n +0000454210 00000 n +0000455391 00000 n +0000456696 00000 n +0000456510 00000 n +0000455556 00000 n +0000456633 00000 n +0001012147 00000 n +0000460686 00000 n +0000459604 00000 n +0000456798 00000 n +0000460373 00000 n +0000460498 00000 n +0000460623 00000 n +0000459766 00000 n +0000459960 00000 n +0000460167 00000 n +0000465180 00000 n +0000463846 00000 n +0000460830 00000 n +0000465117 00000 n +0000464026 00000 n +0000464214 00000 n +0000464463 00000 n +0000464712 00000 n +0000464903 00000 n +0000469180 00000 n +0000468476 00000 n +0000465339 00000 n +0000468993 00000 n +0000468629 00000 n +0000468811 00000 n +0000469118 00000 n +0000472406 00000 n +0000472220 00000 n +0000469367 00000 n +0000472343 00000 n +0000475763 00000 n +0000475374 00000 n +0000472508 00000 n +0000475700 00000 n +0000475518 00000 n +0000478643 00000 n +0000479519 00000 n +0000478520 00000 n +0000475865 00000 n +0000479456 00000 n +0001012272 00000 n +0000482824 00000 n +0000482638 00000 n +0000479692 00000 n +0000482761 00000 n +0000486541 00000 n +0000486230 00000 n +0000482983 00000 n +0000486353 00000 n +0000486478 00000 n +0000490228 00000 n +0000489917 00000 n +0000486643 00000 n +0000490040 00000 n +0000490165 00000 n +0000492561 00000 n +0000492375 00000 n +0000490415 00000 n +0000492498 00000 n +0000496040 00000 n +0000495354 00000 n +0000492734 00000 n +0000495477 00000 n +0000495727 00000 n +0000495852 00000 n +0000495977 00000 n 0000500342 00000 n +0000499781 00000 n +0000496156 00000 n +0000499904 00000 n +0000500029 00000 n +0000500154 00000 n +0000500279 00000 n +0001012397 00000 n +0000504778 00000 n +0000504218 00000 n 0000500472 00000 n -0000500642 00000 n -0000500736 00000 n -0000500863 00000 n -0000500990 00000 n -0000501086 00000 n -0000501273 00000 n -0000501400 00000 n -0000501534 00000 n -0000501661 00000 n -0000501773 00000 n -0000501979 00000 n -0000502138 00000 n -0000502286 00000 n -0000502414 00000 n -0000502595 00000 n -0000502705 00000 n -0000502820 00000 n -0000502965 00000 n -0000503129 00000 n -0000503279 00000 n -0000503416 00000 n -0000503582 00000 n -0000503686 00000 n -0000503843 00000 n -0000503954 00000 n -0000504099 00000 n -0000504241 00000 n -0000504391 00000 n -0000504508 00000 n -0000504672 00000 n -0000504783 00000 n -0000504923 00000 n -0000505050 00000 n -0000505167 00000 n -0000505306 00000 n -0000505412 00000 n -0000505546 00000 n -0000505678 00000 n -0000505823 00000 n -0000505950 00000 n -0000506082 00000 n -0000506212 00000 n -0000506337 00000 n -0000506445 00000 n -0000506617 00000 n -0000506721 00000 n -0000506856 00000 n -0000506991 00000 n -0000507225 00000 n -0000507379 00000 n -0000507520 00000 n -0000507694 00000 n -0000507784 00000 n -0000507912 00000 n -0000508086 00000 n -0000508188 00000 n -0000508339 00000 n -0000508490 00000 n -0000508616 00000 n -0000508822 00000 n -0000508922 00000 n -0000509040 00000 n -0000509205 00000 n -0000509296 00000 n -0000509457 00000 n -0000509583 00000 n -0000509726 00000 n -0000509853 00000 n -0000509993 00000 n -0000510129 00000 n -0000510237 00000 n -0000510411 00000 n -0000510517 00000 n -0000510637 00000 n -0000510749 00000 n -0000510866 00000 n -0000510968 00000 n -0000511146 00000 n -0000511315 00000 n -0000511423 00000 n -0000511557 00000 n -0000511675 00000 n -0000511852 00000 n -0000512019 00000 n -0000512135 00000 n -0000512273 00000 n -0000512409 00000 n -0000512583 00000 n -0000512698 00000 n -0000512808 00000 n -0000512944 00000 n -0000513120 00000 n -0000513266 00000 n -0000513400 00000 n -0000513556 00000 n -0000513724 00000 n -0000513873 00000 n -0000513997 00000 n -0000514135 00000 n -0000514298 00000 n -0000514408 00000 n -0000514542 00000 n -0000514654 00000 n -0000514835 00000 n -0000514956 00000 n -0000515142 00000 n -0000515299 00000 n -0000515462 00000 n -0000515632 00000 n -0000515756 00000 n -0000515879 00000 n -0000516083 00000 n -0000516188 00000 n -0000516320 00000 n -0000516441 00000 n -0000516612 00000 n -0000516734 00000 n -0000516894 00000 n -0000516993 00000 n -0000517111 00000 n -0000517226 00000 n -0000517328 00000 n -0000517489 00000 n -0000517593 00000 n -0000517692 00000 n -0000517899 00000 n -0000518027 00000 n -0000518112 00000 n -0000518304 00000 n -0000518476 00000 n -0000518580 00000 n -0000518704 00000 n -0000518826 00000 n -0000518938 00000 n -0000519120 00000 n -0000519236 00000 n -0000519360 00000 n -0000519478 00000 n -0000519596 00000 n -0000519701 00000 n -0000519878 00000 n -0000519990 00000 n -0000520121 00000 n -0000520245 00000 n -0000520412 00000 n -0000520529 00000 n -0000520659 00000 n -0000520799 00000 n -0000520936 00000 n -0000521072 00000 n -0000521208 00000 n -0000521345 00000 n -0000521457 00000 n -0000521621 00000 n -0000521725 00000 n -0000521858 00000 n -0000521990 00000 n -0000522112 00000 n -0000522241 00000 n -0000522348 00000 n -0000522514 00000 n -0000522636 00000 n -0000522760 00000 n -0000522891 00000 n -0000523000 00000 n -0000523114 00000 n -0000523284 00000 n -0000523446 00000 n -0000523552 00000 n -0000523669 00000 n -0000523820 00000 n -0000523957 00000 n -0000524122 00000 n -0000524247 00000 n -0000524403 00000 n -0000524521 00000 n -0000524651 00000 n -0000524838 00000 n -0000524996 00000 n -0000525100 00000 n -0000525220 00000 n -0000525343 00000 n -0000525504 00000 n -0000525600 00000 n -0000525714 00000 n -0000525824 00000 n -0000525955 00000 n -0000526102 00000 n -0000526203 00000 n -0000526302 00000 n -0000526480 00000 n -0000526590 00000 n -0000526744 00000 n -0000526913 00000 n -0000527101 00000 n -0000527282 00000 n -0000527438 00000 n -0000527604 00000 n -0000527736 00000 n -0000527883 00000 n -0000528022 00000 n -0000528156 00000 n -0000528280 00000 n -0000528401 00000 n -0000528534 00000 n -0000528640 00000 n -0000528832 00000 n -0000528974 00000 n -0000529086 00000 n -0000529209 00000 n -0000529332 00000 n -0000529454 00000 n -0000529579 00000 n -0000529702 00000 n -0000529820 00000 n -0000529995 00000 n -0000530098 00000 n -0000530218 00000 n -0000530333 00000 n -0000530447 00000 n -0000530562 00000 n -0000530676 00000 n -0000530791 00000 n -0000530909 00000 n -0000531026 00000 n -0000531132 00000 n -0000531301 00000 n -0000531405 00000 n -0000531522 00000 n -0000531637 00000 n -0000531751 00000 n -0000531937 00000 n -0000532046 00000 n -0000532221 00000 n -0000532339 00000 n -0000532480 00000 n -0000532603 00000 n -0000532753 00000 n -0000532857 00000 n -0000532975 00000 n -0000533093 00000 n -0000533214 00000 n -0000533350 00000 n -0000533449 00000 n +0000504341 00000 n +0000504466 00000 n +0000504591 00000 n +0000504715 00000 n +0000509387 00000 n +0000508502 00000 n +0000504908 00000 n +0000508825 00000 n +0000508950 00000 n +0000509075 00000 n +0000509200 00000 n +0000508646 00000 n +0000509325 00000 n +0000513866 00000 n +0000513244 00000 n +0000509503 00000 n +0000513553 00000 n +0000513678 00000 n +0000864265 00000 n +0000861109 00000 n +0000864098 00000 n +0000513388 00000 n +0000513803 00000 n +0000517287 00000 n +0000516726 00000 n +0000514038 00000 n +0000516849 00000 n +0000516974 00000 n +0000517099 00000 n +0000517224 00000 n +0000520500 00000 n +0000519940 00000 n +0000517417 00000 n +0000520063 00000 n +0000520188 00000 n +0000520313 00000 n +0000520438 00000 n +0000522941 00000 n +0000522755 00000 n +0000520630 00000 n +0000522878 00000 n +0001012522 00000 n +0000525136 00000 n +0000524699 00000 n +0000523057 00000 n +0000524822 00000 n +0000524947 00000 n +0000525010 00000 n +0000525073 00000 n +0000527209 00000 n +0000526716 00000 n +0000525266 00000 n +0000527020 00000 n +0000527083 00000 n +0000527146 00000 n +0000526860 00000 n +0000814771 00000 n +0000530155 00000 n +0000529594 00000 n +0000527325 00000 n +0000529717 00000 n +0000529780 00000 n +0000529843 00000 n +0000529968 00000 n +0000530031 00000 n +0000530093 00000 n +0000532352 00000 n +0000532166 00000 n +0000530285 00000 n +0000532289 00000 n +0000534537 00000 n +0000534225 00000 n +0000532468 00000 n +0000534348 00000 n +0000534411 00000 n +0000534474 00000 n +0000537574 00000 n +0000537138 00000 n +0000534667 00000 n +0000537261 00000 n +0000537386 00000 n +0000537511 00000 n +0001012647 00000 n +0000541670 00000 n +0000540737 00000 n +0000537704 00000 n +0000540860 00000 n +0000540985 00000 n +0000541110 00000 n +0000541234 00000 n +0000541359 00000 n +0000541422 00000 n +0000541485 00000 n +0000541608 00000 n +0000546276 00000 n +0000544932 00000 n +0000541800 00000 n +0000545899 00000 n +0000545962 00000 n +0000546025 00000 n +0000546088 00000 n +0000546213 00000 n +0000545103 00000 n +0000545302 00000 n +0000545500 00000 n +0000545700 00000 n +0000549004 00000 n +0000548503 00000 n +0000546491 00000 n +0000548816 00000 n +0000548941 00000 n +0000548647 00000 n +0000550901 00000 n +0000550592 00000 n +0000549120 00000 n +0000550715 00000 n +0000550839 00000 n +0000551724 00000 n +0000551538 00000 n +0000551017 00000 n +0000551661 00000 n +0000556332 00000 n +0000555518 00000 n +0000551826 00000 n +0000555894 00000 n +0000556019 00000 n +0000556144 00000 n +0000555662 00000 n +0000556269 00000 n +0001012772 00000 n +0000561157 00000 n +0000560596 00000 n +0000556462 00000 n +0000560719 00000 n +0000560844 00000 n +0000560969 00000 n +0000561094 00000 n +0000565302 00000 n +0000564740 00000 n +0000561315 00000 n +0000564863 00000 n +0000564988 00000 n +0000565051 00000 n +0000565114 00000 n +0000565177 00000 n +0000565239 00000 n +0000569110 00000 n +0000568675 00000 n +0000565432 00000 n +0000568798 00000 n +0000568923 00000 n +0000569048 00000 n +0000573080 00000 n +0000572077 00000 n +0000569283 00000 n +0000572200 00000 n +0000572325 00000 n +0000572450 00000 n +0000572513 00000 n +0000572576 00000 n +0000572639 00000 n +0000572702 00000 n +0000572765 00000 n +0000572828 00000 n +0000572891 00000 n +0000572954 00000 n +0000573017 00000 n +0000576144 00000 n +0000575458 00000 n +0000573196 00000 n +0000575581 00000 n +0000575706 00000 n +0000575831 00000 n +0000575956 00000 n +0000576081 00000 n +0000579308 00000 n +0000578747 00000 n +0000576317 00000 n +0000578870 00000 n +0000578995 00000 n +0000579120 00000 n +0000579245 00000 n +0001012897 00000 n +0000583213 00000 n +0000582652 00000 n +0000579509 00000 n +0000582775 00000 n +0000582900 00000 n +0000583025 00000 n +0000583088 00000 n +0000583151 00000 n +0000587682 00000 n +0000587246 00000 n +0000583442 00000 n +0000587369 00000 n +0000587432 00000 n +0000587494 00000 n +0000587557 00000 n +0000587620 00000 n +0000591601 00000 n +0000591039 00000 n +0000587812 00000 n +0000591162 00000 n +0000591225 00000 n +0000591288 00000 n +0000591413 00000 n +0000591538 00000 n +0000593137 00000 n +0000592951 00000 n +0000591731 00000 n +0000593074 00000 n +0000595507 00000 n +0000595321 00000 n +0000593310 00000 n +0000595444 00000 n +0000599210 00000 n +0000598649 00000 n +0000595666 00000 n +0000598772 00000 n +0000598897 00000 n +0000599022 00000 n +0000599147 00000 n +0001013022 00000 n +0000603300 00000 n +0000602490 00000 n +0000599411 00000 n +0000602613 00000 n +0000602738 00000 n +0000602863 00000 n +0000602988 00000 n +0000603113 00000 n +0000603238 00000 n +0000607546 00000 n +0000606985 00000 n +0000603473 00000 n +0000607108 00000 n +0000607233 00000 n +0000607358 00000 n +0000607483 00000 n +0000611571 00000 n +0000611008 00000 n +0000607747 00000 n +0000611131 00000 n +0000611256 00000 n +0000611319 00000 n +0000611382 00000 n +0000611445 00000 n +0000611508 00000 n +0000613695 00000 n +0000613509 00000 n +0000611715 00000 n +0000613632 00000 n +0000617103 00000 n +0000616792 00000 n +0000613811 00000 n +0000616915 00000 n +0000617040 00000 n +0000619408 00000 n +0000619222 00000 n +0000617290 00000 n +0000619345 00000 n +0001013147 00000 n +0000621045 00000 n +0000620859 00000 n +0000619524 00000 n +0000620982 00000 n +0000624784 00000 n +0000624348 00000 n +0000621161 00000 n +0000624471 00000 n +0000624596 00000 n +0000624721 00000 n +0000628803 00000 n +0000627994 00000 n +0000624886 00000 n +0000628117 00000 n +0000628242 00000 n +0000628367 00000 n +0000628490 00000 n +0000628615 00000 n +0000628740 00000 n +0000632487 00000 n +0000632177 00000 n +0000628919 00000 n +0000632300 00000 n +0000632424 00000 n +0000635510 00000 n +0000635072 00000 n +0000632660 00000 n +0000635195 00000 n +0000635321 00000 n +0000635447 00000 n +0000638093 00000 n +0000637907 00000 n +0000635683 00000 n +0000638030 00000 n +0001013272 00000 n +0000641664 00000 n +0000640948 00000 n +0000638209 00000 n +0000641475 00000 n +0000641601 00000 n +0000641101 00000 n +0000641289 00000 n +0000644464 00000 n +0000644152 00000 n +0000641851 00000 n +0000644275 00000 n +0000644401 00000 n +0000646818 00000 n +0000646380 00000 n +0000644580 00000 n +0000646503 00000 n +0000646629 00000 n +0000646755 00000 n +0000649396 00000 n +0000648836 00000 n +0000646934 00000 n +0000648959 00000 n +0000649085 00000 n +0000649207 00000 n +0000649333 00000 n +0000652517 00000 n +0000651701 00000 n +0000649526 00000 n +0000651824 00000 n +0000651950 00000 n +0000652076 00000 n +0000652202 00000 n +0000652328 00000 n +0000652454 00000 n +0000655439 00000 n +0000654749 00000 n +0000652647 00000 n +0000654872 00000 n +0000654935 00000 n +0000654998 00000 n +0000655125 00000 n +0000655251 00000 n +0000655376 00000 n +0001013397 00000 n +0000658283 00000 n +0000657244 00000 n +0000655555 00000 n +0000657969 00000 n +0000658095 00000 n +0000657406 00000 n +0000657612 00000 n +0000658221 00000 n +0000657792 00000 n +0000662346 00000 n +0000661032 00000 n +0000658399 00000 n +0000662031 00000 n +0000662157 00000 n +0000662283 00000 n +0000661203 00000 n +0000661439 00000 n +0000661675 00000 n +0000661853 00000 n +0000664068 00000 n +0000663756 00000 n +0000662476 00000 n +0000663879 00000 n +0000664005 00000 n +0000667065 00000 n +0000666628 00000 n +0000664184 00000 n +0000666751 00000 n +0000666877 00000 n +0000667003 00000 n +0000670863 00000 n +0000670427 00000 n +0000667238 00000 n +0000670550 00000 n +0000670676 00000 n +0000670801 00000 n +0000673309 00000 n +0000672871 00000 n +0000670993 00000 n +0000672994 00000 n +0000673120 00000 n +0000673246 00000 n +0001013522 00000 n +0000677139 00000 n +0000676827 00000 n +0000673439 00000 n +0000676950 00000 n +0000677076 00000 n +0000681206 00000 n +0000680768 00000 n +0000677283 00000 n +0000680891 00000 n +0000681017 00000 n +0000681143 00000 n +0000683309 00000 n +0000683123 00000 n +0000681336 00000 n +0000683246 00000 n +0000686546 00000 n +0000685982 00000 n +0000683411 00000 n +0000686105 00000 n +0000686231 00000 n +0000686357 00000 n +0000686483 00000 n +0000687333 00000 n +0000687147 00000 n +0000686676 00000 n +0000687270 00000 n +0000690580 00000 n +0000689890 00000 n +0000687435 00000 n +0000690013 00000 n +0000690265 00000 n +0000690391 00000 n +0000690517 00000 n +0001013647 00000 n +0000693657 00000 n +0000693096 00000 n +0000690696 00000 n +0000693219 00000 n +0000693345 00000 n +0000693469 00000 n +0000693594 00000 n +0000695296 00000 n +0000694795 00000 n +0000693773 00000 n +0000695107 00000 n +0000695233 00000 n +0000694939 00000 n +0000699280 00000 n +0000698397 00000 n +0000695412 00000 n +0000698713 00000 n +0000698839 00000 n +0000698965 00000 n +0000698541 00000 n +0000699091 00000 n +0000699217 00000 n +0000701871 00000 n +0000701112 00000 n +0000699410 00000 n +0000701683 00000 n +0000701809 00000 n +0000701265 00000 n +0000701474 00000 n +0000706036 00000 n +0000705472 00000 n +0000702015 00000 n +0000705595 00000 n +0000705721 00000 n +0000705847 00000 n +0000705973 00000 n +0000709812 00000 n +0000709501 00000 n +0000706138 00000 n +0000709624 00000 n +0000709750 00000 n +0001013772 00000 n +0000712542 00000 n +0000712356 00000 n +0000709942 00000 n +0000712479 00000 n +0000715273 00000 n +0000714961 00000 n +0000712701 00000 n +0000715084 00000 n +0000715210 00000 n +0000718089 00000 n +0000717652 00000 n +0000715460 00000 n +0000717775 00000 n +0000717901 00000 n +0000718027 00000 n +0000721760 00000 n +0000719888 00000 n +0000718205 00000 n +0000721571 00000 n +0000721697 00000 n +0000720086 00000 n +0000720297 00000 n +0000720510 00000 n +0000720723 00000 n +0000720935 00000 n +0000721147 00000 n +0000721359 00000 n +0000722439 00000 n +0000722191 00000 n +0000721890 00000 n +0000722314 00000 n +0000725585 00000 n +0000724959 00000 n +0000722527 00000 n +0000725082 00000 n +0000725145 00000 n +0000725397 00000 n +0000725522 00000 n +0001013897 00000 n +0000729607 00000 n +0000729106 00000 n +0000725758 00000 n +0000729229 00000 n +0000729355 00000 n +0000729418 00000 n +0000729481 00000 n +0000729544 00000 n +0000733268 00000 n +0000733019 00000 n +0000729794 00000 n +0000733142 00000 n +0000733205 00000 n +0000737822 00000 n +0000737075 00000 n +0000733455 00000 n +0000737198 00000 n +0000737261 00000 n +0000737324 00000 n +0000737387 00000 n +0000737449 00000 n +0000737512 00000 n +0000737573 00000 n +0000737635 00000 n +0000737698 00000 n +0000737761 00000 n +0000742526 00000 n +0000741900 00000 n +0000738023 00000 n +0000742023 00000 n +0000742086 00000 n +0000742149 00000 n +0000742211 00000 n +0000742274 00000 n +0000742337 00000 n +0000742400 00000 n +0000742463 00000 n +0000743646 00000 n +0000743161 00000 n +0000742670 00000 n +0000743457 00000 n +0000743583 00000 n +0000743305 00000 n +0000747660 00000 n +0000746723 00000 n +0000743748 00000 n +0000747221 00000 n +0000747473 00000 n +0000746876 00000 n +0000747048 00000 n +0000747599 00000 n +0001014022 00000 n +0000752341 00000 n +0000750683 00000 n +0000747776 00000 n +0000752153 00000 n +0000752279 00000 n +0000750881 00000 n +0000751045 00000 n +0000751236 00000 n +0000751427 00000 n +0000751612 00000 n +0000751781 00000 n +0000751965 00000 n +0000757121 00000 n +0000755930 00000 n +0000752485 00000 n +0000756806 00000 n +0000756932 00000 n +0000756101 00000 n +0000756266 00000 n +0000757058 00000 n +0000756439 00000 n +0000756610 00000 n +0000761260 00000 n +0000760031 00000 n +0000757279 00000 n +0000760693 00000 n +0000760819 00000 n +0000760945 00000 n +0000760193 00000 n +0000760369 00000 n +0000761071 00000 n +0000760540 00000 n +0000761197 00000 n +0000765471 00000 n +0000764907 00000 n +0000761376 00000 n +0000765030 00000 n +0000765156 00000 n +0000765282 00000 n +0000765408 00000 n +0000766141 00000 n +0000765893 00000 n +0000765601 00000 n +0000766016 00000 n +0000771157 00000 n +0000768978 00000 n +0000766229 00000 n +0000770212 00000 n +0000770275 00000 n +0000769167 00000 n +0000770527 00000 n +0000770653 00000 n +0000769333 00000 n +0000769512 00000 n +0000770779 00000 n +0000770905 00000 n +0000769692 00000 n +0000771031 00000 n +0000769870 00000 n +0000770041 00000 n +0000771094 00000 n +0001014147 00000 n +0000775076 00000 n +0000773871 00000 n +0000771259 00000 n +0000774573 00000 n +0000774636 00000 n +0000774699 00000 n +0000774762 00000 n +0000774887 00000 n +0000774033 00000 n +0000774218 00000 n +0000774403 00000 n +0000775013 00000 n +0000777908 00000 n +0000777470 00000 n +0000775192 00000 n +0000777593 00000 n +0000777719 00000 n +0000777845 00000 n +0000781057 00000 n +0000780367 00000 n +0000778038 00000 n +0000780490 00000 n +0000780616 00000 n +0000780742 00000 n +0000780868 00000 n +0000780994 00000 n +0000783774 00000 n +0000783462 00000 n +0000781187 00000 n +0000783585 00000 n +0000783711 00000 n +0000784805 00000 n +0000784619 00000 n +0000783975 00000 n +0000784742 00000 n +0000788059 00000 n +0000787495 00000 n +0000784964 00000 n +0000787618 00000 n +0000787744 00000 n +0000787870 00000 n +0000787996 00000 n +0001014272 00000 n +0000791230 00000 n +0000790918 00000 n +0000788175 00000 n +0000791041 00000 n +0000791167 00000 n +0000795686 00000 n +0000795249 00000 n +0000791346 00000 n +0000795372 00000 n +0000795498 00000 n +0000795624 00000 n +0000799718 00000 n +0000798085 00000 n +0000795802 00000 n +0000798208 00000 n +0000798334 00000 n +0000798460 00000 n +0000798586 00000 n +0000798649 00000 n +0000798712 00000 n +0000798775 00000 n +0000798838 00000 n +0000798901 00000 n +0000798964 00000 n +0000799027 00000 n +0000799090 00000 n +0000799153 00000 n +0000799216 00000 n +0000799279 00000 n +0000799342 00000 n +0000799405 00000 n +0000799468 00000 n +0000799531 00000 n +0000799594 00000 n +0000799656 00000 n +0000802966 00000 n +0000802150 00000 n +0000799876 00000 n +0000802273 00000 n +0000802336 00000 n +0000802399 00000 n +0000802525 00000 n +0000802588 00000 n +0000802651 00000 n +0000802778 00000 n +0000802904 00000 n +0000805609 00000 n +0000805296 00000 n +0000803124 00000 n +0000805419 00000 n +0000805482 00000 n +0000805545 00000 n +0000806690 00000 n +0000806504 00000 n +0000805725 00000 n +0000806627 00000 n +0001014397 00000 n +0000810176 00000 n +0000809487 00000 n +0000806792 00000 n +0000809610 00000 n +0000809736 00000 n +0000809862 00000 n +0000809988 00000 n +0000810113 00000 n +0000811805 00000 n +0000811493 00000 n +0000810278 00000 n +0000811616 00000 n +0000811742 00000 n +0000814834 00000 n +0000814019 00000 n +0000811935 00000 n +0000814142 00000 n +0000814268 00000 n +0000814394 00000 n +0000814519 00000 n +0000814645 00000 n +0000819904 00000 n +0000818027 00000 n +0000814936 00000 n +0000819337 00000 n +0000819463 00000 n +0000819589 00000 n +0000818216 00000 n +0000818388 00000 n +0000818578 00000 n +0000818763 00000 n +0000818955 00000 n +0000819715 00000 n +0000819841 00000 n +0000819142 00000 n +0000825020 00000 n +0000823381 00000 n +0000820020 00000 n +0000824327 00000 n +0000824453 00000 n +0000823552 00000 n +0000823750 00000 n +0000823942 00000 n +0000824579 00000 n +0000824132 00000 n +0000824705 00000 n +0000824831 00000 n +0000824957 00000 n +0000829573 00000 n +0000828443 00000 n +0000825164 00000 n +0000828755 00000 n +0000828881 00000 n +0000829006 00000 n +0000829132 00000 n +0000828587 00000 n +0000829258 00000 n +0000829384 00000 n +0000829510 00000 n +0001014522 00000 n +0000833600 00000 n +0000832659 00000 n +0000829703 00000 n +0000832972 00000 n +0000833035 00000 n +0000833098 00000 n +0000833159 00000 n +0000833222 00000 n +0000833285 00000 n +0000833411 00000 n +0000833537 00000 n +0000832803 00000 n +0000835145 00000 n +0000834601 00000 n +0000833758 00000 n +0000834956 00000 n +0000835082 00000 n +0000834745 00000 n +0000838462 00000 n +0000837900 00000 n +0000835304 00000 n +0000838023 00000 n +0000838149 00000 n +0000838274 00000 n +0000838399 00000 n +0000841416 00000 n +0000841104 00000 n +0000838621 00000 n +0000841227 00000 n +0000841353 00000 n +0000845175 00000 n +0000844545 00000 n +0000841574 00000 n +0000844861 00000 n +0000844987 00000 n +0000844689 00000 n +0000845112 00000 n +0000849454 00000 n +0000848639 00000 n +0000845404 00000 n +0000848762 00000 n +0000848888 00000 n +0000849014 00000 n +0000849140 00000 n +0000849265 00000 n +0000849391 00000 n +0001014647 00000 n +0000850934 00000 n +0000850622 00000 n +0000849584 00000 n +0000850745 00000 n +0000850871 00000 n +0000854679 00000 n +0000853991 00000 n +0000851050 00000 n +0000854114 00000 n +0000854240 00000 n +0000854366 00000 n +0000854492 00000 n +0000854618 00000 n +0000858670 00000 n +0000857855 00000 n +0000854795 00000 n +0000857978 00000 n +0000858104 00000 n +0000858229 00000 n +0000858355 00000 n +0000858481 00000 n +0000858607 00000 n +0000859986 00000 n +0000859496 00000 n +0000858800 00000 n +0000859797 00000 n +0000859923 00000 n +0000859640 00000 n +0000860088 00000 n +0000864491 00000 n +0000864672 00000 n +0000868420 00000 n +0000868445 00000 n +0000871657 00000 n +0000871688 00000 n +0000884872 00000 n +0000888947 00000 n +0000889144 00000 n +0000898871 00000 n +0000901380 00000 n +0000901411 00000 n +0000905411 00000 n +0000905639 00000 n +0000924554 00000 n +0000934967 00000 n +0000951442 00000 n +0000951852 00000 n +0000970160 00000 n +0000989856 00000 n +0000995250 00000 n +0001009493 00000 n +0001014763 00000 n +0001014889 00000 n +0001015015 00000 n +0001015141 00000 n +0001015267 00000 n +0001015393 00000 n +0001015519 00000 n +0001015618 00000 n +0001015745 00000 n +0001015826 00000 n +0001015900 00000 n +0001055177 00000 n +0001081128 00000 n +0001081169 00000 n +0001081209 00000 n +0001081441 00000 n trailer -<<5f751223613f7429fc6149872788f647>]>> +<< +/Size 3776 +/Root 3774 0 R +/Info 3775 0 R +>> startxref -534540 +1081637 %%EOF diff --git a/docs/faq/FAQ-ClientApp.html b/docs/faq/FAQ-ClientApp.html new file mode 100644 index 0000000000..3f680b78d7 --- /dev/null +++ b/docs/faq/FAQ-ClientApp.html @@ -0,0 +1,52 @@ + +Chapter4.Specific client application problems

Chapter4.Specific client application problems
PrevNext

Chapter4.Specific client application problems

Table of Contents

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"
How to use a Samba share as an administrative share for MS Office, etc.
Microsoft Access database opening errors

MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

+When installing MS Office on a Samba drive for which you have admin +user permissions, ie. admin users = username, you will find the +setup program unable to complete the installation. +

+To get around this problem, do the installation without admin user +permissions The problem is that MS Office Setup checks that a file is +rdonly by trying to open it for writing. +

+Admin users can always open a file for writing, as they run as root. +You just have to install as a non-admin user and then use "chown -R" +to fix the owner. +

How to use a Samba share as an administrative share for MS Office, etc.

+Microsoft Office products can be installed as an administrative installation +from which the application can either be run off the administratively installed +product that resides on a shared resource, or from which that product can be +installed onto workstation clients. +

+The general mechanism for implementing an adminstrative installation involves +running X:\setup /A, where X is the drive letter of either CDROM or floppy. +

+This installation process will NOT install the product for use per se, but +rather results in unpacking of the compressed distribution files into a target +shared folder. For this process you need write privilidge to the share and it +is desirable to enable file locking and share mode operation during this +process. +

+Subsequent installation of MS Office from this share will FAIL unless certain +precautions are taken. This failure will be caused by share mode operation +which will prevent the MS Office installation process from re-opening various +dynamic link library files and will cause sporadic file not found problems. +

  • +As soon as the administrative installation (unpacking) has completed +set the following parameters on the share containing it: +

    +[MSOP95]
+	path = /where_you_put_it
+	comment = Your comment
+	volume = "The_CD_ROM_Label"
+	read only = yes
+	available = yes
+	share modes = no
+	locking = no
+	browseable = yes
+	public = yes
+

  • Now you are ready to run the setup program from the Microsoft Windows +workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup +

Microsoft Access database opening errors

+Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg +

Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.
Make sure that you open the database as 'shared' and to 'lock modified records'
Of course locking must be enabled for the particular share (smb.conf)

+

PrevUpNext
Chapter3.Configuration problemsHomeChapter5.Common errors
diff --git a/docs/faq/FAQ-Config.html b/docs/faq/FAQ-Config.html new file mode 100644 index 0000000000..785522ec4e --- /dev/null +++ b/docs/faq/FAQ-Config.html @@ -0,0 +1,16 @@ + +Chapter3.Configuration problems
Chapter3.Configuration problems
PrevNext

Chapter3.Configuration problems

Table of Contents

I have set 'force user' and samba still makes 'root' the owner of all the files I touch!
I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!
How can I make samba use netbios scope ID's

I have set 'force user' and samba still makes 'root' the owner of all the files I touch!

+When you have a user in 'admin users', samba will always do file operations for +this user as 'root', even if 'force user' has been set. +

I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!

+Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these +passwords to the unix password database, so it needs it's own user database. You can +add users to this database using "smbpasswd -a user-name". +

+See also the "User database" chapter of the samba HOWTO Collection. +

How can I make samba use netbios scope ID's

By default Samba uses a blank scope ID. This means +all your windows boxes must also have a blank scope ID. +If you really want to use a non-blank scope ID then you will +need to use the 'netbios scope' smb.conf option. +All your PCs will need to have the same setting for +this to work. Scope ID's are not recommended.

PrevUpNext
Chapter2.Compiling and installing Samba on a Unix hostHomeChapter4.Specific client application problems
diff --git a/docs/faq/FAQ-Install.html b/docs/faq/FAQ-Install.html new file mode 100644 index 0000000000..411656bc76 --- /dev/null +++ b/docs/faq/FAQ-Install.html @@ -0,0 +1,194 @@ + +Chapter2.Compiling and installing Samba on a Unix host
Chapter2.Compiling and installing Samba on a Unix host
PrevNext

Chapter2.Compiling and installing Samba on a Unix host

Table of Contents

I can't see the Samba server in any browse lists!
Some files that I KNOW are on the server don't show up when I view the files from my client!
Some files on the server show up with really wierd filenames when I view the files from my client!
My client reports "cannot locate specified computer" or similar
My client reports "cannot locate specified share name" or similar
Printing doesn't work
My client reports "This server is not configured to list shared resources"
Log message "you appear to have a trapdoor uid system"
Why are my file's timestamps off by an hour, or by a few hours?
How do I set the printer driver name correctly?

I can't see the Samba server in any browse lists!

+See Browsing.html in the docs directory of the samba source +for more information on browsing. +

+If your GUI client does not permit you to select non-browsable +servers, you may need to do so on the command line. For example, under +Lan Manager you might connect to the above service as disk drive M: +thusly: +

+   net use M: \\mary\fred
+

+The details of how to do this and the specific syntax varies from +client to client - check your client's documentation. +

Some files that I KNOW are on the server don't show up when I view the files from my client!

See the next question.

Some files on the server show up with really wierd filenames when I view the files from my client!

+If you check what files are not showing up, you will note that they +are files which contain upper case letters or which are otherwise not +DOS-compatible (ie, they are not legal DOS filenames for some reason). +

+The Samba server can be configured either to ignore such files +completely, or to present them to the client in "mangled" form. If you +are not seeing the files at all, the Samba server has most likely been +configured to ignore them. Consult the man page smb.conf(5) for +details of how to change this - the parameter you need to set is +"mangled names = yes". +

My client reports "cannot locate specified computer" or similar

+This indicates one of three things: You supplied an incorrect server +name, the underlying TCP/IP layer is not working correctly, or the +name you specified cannot be resolved. +

+After carefully checking that the name you typed is the name you +should have typed, try doing things like pinging a host or telnetting +to somewhere on your network to see if TCP/IP is functioning OK. If it +is, the problem is most likely name resolution. +

+If your client has a facility to do so, hardcode a mapping between the +hosts IP and the name you want to use. For example, with Lan Manager +or Windows for Workgroups you would put a suitable entry in the file +LMHOSTS. If this works, the problem is in the communication between +your client and the netbios name server. If it does not work, then +there is something fundamental wrong with your naming and the solution +is beyond the scope of this document. +

+If you do not have any server on your subnet supplying netbios name +resolution, hardcoded mappings are your only option. If you DO have a +netbios name server running (such as the Samba suite's nmbd program), +the problem probably lies in the way it is set up. Refer to Section +Two of this FAQ for more ideas. +

+By the way, remember to REMOVE the hardcoded mapping before further +tests :-) +

My client reports "cannot locate specified share name" or similar

+This message indicates that your client CAN locate the specified +server, which is a good start, but that it cannot find a service of +the name you gave. +

+The first step is to check the exact name of the service you are +trying to connect to (consult your system administrator). Assuming it +exists and you specified it correctly (read your client's docs on how +to specify a service name correctly), read on: +

Many clients cannot accept or use service names longer than eight characters.
Many clients cannot accept or use service names containing spaces.
Some servers (not Samba though) are case sensitive with service names.
Some clients force service names into upper case.

Printing doesn't work

+Make sure that the specified print command for the service you are +connecting to is correct and that it has a fully-qualified path (eg., +use "/usr/bin/lpr" rather than just "lpr"). +

+Make sure that the spool directory specified for the service is +writable by the user connected to the service. In particular the user +"nobody" often has problems with printing, even if it worked with an +earlier version of Samba. Try creating another guest user other than +"nobody". +

+Make sure that the user specified in the service is permitted to use +the printer. +

+Check the debug log produced by smbd. Search for the printer name and +see if the log turns up any clues. Note that error messages to do with +a service ipc$ are meaningless - they relate to the way the client +attempts to retrieve status information when using the LANMAN1 +protocol. +

+If using WfWg then you need to set the default protocol to TCP/IP, not +Netbeui. This is a WfWg bug. +

+If using the Lanman1 protocol (the default) then try switching to +coreplus. Also not that print status error messages don't mean +printing won't work. The print status is received by a different +mechanism. +

My client reports "This server is not configured to list shared resources"

+Your guest account is probably invalid for some reason. Samba uses the +guest account for browsing in smbd. Check that your guest account is +valid. +

See also 'guest account' in smb.conf man page.

Log message "you appear to have a trapdoor uid system"

+This can have several causes. It might be because you are using a uid +or gid of 65535 or -1. This is a VERY bad idea, and is a big security +hole. Check carefully in your /etc/passwd file and make sure that no +user has uid 65535 or -1. Especially check the "nobody" user, as many +broken systems are shipped with nobody setup with a uid of 65535. +

It might also mean that your OS has a trapdoor uid/gid system :-)

+This means that once a process changes effective uid from root to +another user it can't go back to root. Unfortunately Samba relies on +being able to change effective uid from root to non-root and back +again to implement its security policy. If your OS has a trapdoor uid +system this won't work, and several things in Samba may break. Less +things will break if you use user or server level security instead of +the default share level security, but you may still strike +problems. +

+The problems don't give rise to any security holes, so don't panic, +but it does mean some of Samba's capabilities will be unavailable. +In particular you will not be able to connect to the Samba server as +two different uids at once. This may happen if you try to print as a +"guest" while accessing a share as a normal user. It may also affect +your ability to list the available shares as this is normally done as +the guest user. +

+Complain to your OS vendor and ask them to fix their system. +

+Note: the reason why 65535 is a VERY bad choice of uid and gid is that +it casts to -1 as a uid, and the setreuid() system call ignores (with +no error) uid changes to -1. This means any daemon attempting to run +as uid 65535 will actually run as root. This is not good! +

Why are my file's timestamps off by an hour, or by a few hours?

+This is from Paul Eggert eggert@twinsun.com. +

+Most likely it's a problem with your time zone settings. +

+Internally, Samba maintains time in traditional Unix format, +namely, the number of seconds since 1970-01-01 00:00:00 Universal Time +(or ``GMT''), not counting leap seconds. +

+On the server side, Samba uses the Unix TZ variable to convert +internal timestamps to and from local time. So on the server side, there are +two things to get right. +

The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.

+

TZ must have the correct value.

+If possible, use geographical time zone settings +(e.g. TZ='America/Los_Angeles' or perhaps + TZ=':US/Pacific'). These are supported by most +popular Unix OSes, are easier to get right, and are +more accurate for historical timestamps. If your +operating system has out-of-date tables, you should be +able to update them from the public domain time zone +tables at ftp://elsie.nci.nih.gov/pub/. +

If your system does not support geographical timezone +settings, you must use a Posix-style TZ strings, e.g. +TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. +Posix TZ strings can take the following form (with optional + items in brackets): +

+	StdOffset[Dst[Offset],Date/Time,Date/Time]
+

+ where: +

`Std' is the standard time designation (e.g. `PST').
`Offset' is the number of hours behind UTC (e.g. `8'). +Prepend a `-' if you are ahead of UTC, and +append `:30' if you are at a half-hour offset. +Omit all the remaining items if you do not use +daylight-saving time.
`Dst' is the daylight-saving time designation +(e.g. `PDT').
The optional second `Offset' is the number of +hours that daylight-saving time is behind UTC. +The default is 1 hour ahead of standard time. +
`Date/Time,Date/Time' specify when daylight-saving +time starts and ends. The format for a date is +`Mm.n.d', which specifies the dth day (0 is Sunday) +of the nth week of the mth month, where week 5 means +the last such day in the month. The format for a +time is [h]h[:mm[:ss]], using a 24-hour clock. +

+

+Other Posix string formats are allowed but you don't want +to know about them.

+On the client side, you must make sure that your client's clock and +time zone is also set appropriately. [[I don't know how to do this.]] +Samba traditionally has had many problems dealing with time zones, due +to the bizarre ways that Microsoft network protocols handle time +zones. +

How do I set the printer driver name correctly?

Question: +“ On NT, I opened "Printer Manager" and "Connect to Printer". + Enter ["\\ptdi270\ps1"] in the box of printer. I got the + following error message + ”

+ 

+     You do not have sufficient access to your machine
+     to connect to the selected printer, since a driver
+     needs to be installed locally.
+

+

Answer:

In the more recent versions of Samba you can now set the "printer +driver" in smb.conf. This tells the client what driver to use. For +example:

+     printer driver = HP LaserJet 4L
+

With this, NT knows to use the right driver. You have to get this string +exactly right.

To find the exact string to use, you need to get to the dialog box in +your client where you select which printer driver to install. The +correct strings for all the different printers are shown in a listbox +in that dialog box.

PrevUpNext
Chapter1.General InformationHomeChapter3.Configuration problems
diff --git a/docs/faq/FAQ-Printing.html b/docs/faq/FAQ-Printing.html new file mode 100644 index 0000000000..a924d40cd5 --- /dev/null +++ b/docs/faq/FAQ-Printing.html @@ -0,0 +1,16 @@ + +Chapter7.Printing problems
Chapter7.Printing problems
Prev

Chapter7.Printing problems

Ronan Waide

Table of Contents

setdriver or cupsaddsmb failes

setdriver or cupsaddsmb failes

+setdriver expects the following setup: + +

you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.
printer admins has to be defined in [global]
upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.
Make sure that the user you're connecting as is able to write to the print$ directories
Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)
Use setdriver to associate the driver with a printer

+

+The setdriver call will fail if the printer doesn't already exist in +samba's view of the world. Either create the printer in cups and +restart samba, or create an add printer command (see smb.conf doco) +and use RPC calls to create a printer. NB the add printer command MUST +return a single line of text indicating which port the printer was +added on. If it doesn't, Samba won't reload the printer +definitions. Although samba doesn't really support the notion of +ports, suitable add printer command and enumport command settings can +allow you pretty good remote control of the samba printer setup. +

PrevUp
Chapter6.FeaturesHome
diff --git a/docs/faq/FAQ-errors.html b/docs/faq/FAQ-errors.html new file mode 100644 index 0000000000..c2ec7e719b --- /dev/null +++ b/docs/faq/FAQ-errors.html @@ -0,0 +1,99 @@ + +Chapter5.Common errors
Chapter5.Common errors
PrevNext

Chapter5.Common errors

Table of Contents

Not listening for calling name
System Error 1240
smbclient ignores -N !
The data on the CD-Drive I've shared seems to be corrupted!
Why can users access home directories of other users?
Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"
I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

Not listening for calling name

+

+Session request failed (131,129) with myname=HOBBES destname=CALVIN
+Not listening for calling name
+

+

+If you get this when talking to a Samba box then it means that your +global "hosts allow" or "hosts deny" settings are causing the Samba +server to refuse the connection. +

+Look carefully at your "hosts allow" and "hosts deny" lines in the +global section of smb.conf. +

+It can also be a problem with reverse DNS lookups not functioning +correctly, leading to the remote host identity not being able to +be confirmed, but that is less likely. +

System Error 1240

+System error 1240 means that the client is refusing to talk +to a non-encrypting server. Microsoft changed WinNT in service +pack 3 to refuse to connect to servers that do not support +SMB password encryption. +

There are two main solutions: +

enable SMB password encryption in Samba. See the encryption part of +the samba HOWTO Collection
disable this new behaviour in NT. See the section about +Windows NT in the chapter "Portability" of the samba HOWTO collection +

+

smbclient ignores -N !

+“When getting the list of shares available on a host using the command +smbclient -N -L +the program always prompts for the password if the server is a Samba server. +It also ignores the "-N" argument when querying some (but not all) of our +NT servers. +” +

+No, it does not ignore -N, it is just that your server rejected the +null password in the connection, so smbclient prompts for a password +to try again. +

+To get the behaviour that you probably want use smbclient -L host -U% +

+This will set both the username and password to null, which is +an anonymous login for SMB. Using -N would only set the password +to null, and this is not accepted as an anonymous login for most +SMB servers. +

The data on the CD-Drive I've shared seems to be corrupted!

+Some OSes (notably Linux) default to auto detection of file type on +cdroms and do cr/lf translation. This is a very bad idea when use with +Samba. It causes all sorts of stuff ups. +

+To overcome this problem use conv=binary when mounting the cdrom +before exporting it with Samba. +

Why can users access home directories of other users?

+“ +We are unable to keep individual users from mapping to any other user's +home directory once they have supplied a valid password! They only need +to enter their own password. I have not found *any* method that I can +use to configure samba to enforce that only a user may map their own +home directory. +” +

“ +User xyzzy can map his home directory. Once mapped user xyzzy can also map +*anyone* elses home directory! +”

+This is not a security flaw, it is by design. Samba allows +users to have *exactly* the same access to the UNIX filesystem +as they would if they were logged onto the UNIX box, except +that it only allows such views onto the file system as are +allowed by the defined shares. +

+This means that if your UNIX home directories are set up +such that one user can happily cd into another users +directory and do an ls, the UNIX security solution is to +change the UNIX file permissions on the users home directories +such that the cd and ls would be denied. +

+Samba tries very hard not to second guess the UNIX administrators +security policies, and trusts the UNIX admin to set +the policies and permissions he or she desires. +

+Samba does allow the setup you require when you have set the +"only user = yes" option on the share, is that you have not set the +valid users list for the share. +

+Note that only user works in conjunction with the users= list, +so to get the behavior you require, add the line : +

+users = %S
+

+this is equivalent to: +

+valid users = %S
+

+to the definition of the [homes] share, as recommended in +the smb.conf man page. +

Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"

+A domain controller has to announce on the network who it is. This usually takes a while. +

I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs

Your loopback device isn't working correctly. Make sure it's running. +

PrevUpNext
Chapter4.Specific client application problemsHomeChapter6.Features
diff --git a/docs/faq/FAQ-features.html b/docs/faq/FAQ-features.html new file mode 100644 index 0000000000..9bcd8437b8 --- /dev/null +++ b/docs/faq/FAQ-features.html @@ -0,0 +1,214 @@ + +Chapter6.Features
Chapter6.Features
PrevNext

Chapter6.Features

Table of Contents

How can I prevent my samba server from being used to distribute the Nimda worm?
How can I use samba as a fax server?
Tools for printing faxes
Making the fax-server
Installing the client drivers
Example smb.conf
Samba doesn't work well together with DHCP!
How can I assign NetBIOS names to clients with DHCP?
How do I convert between unix and dos text formats?
Does samba have wins replication support?

How can I prevent my samba server from being used to distribute the Nimda worm?

Author: HASEGAWA Yosuke (translated by TAKAHASHI Motonobu)

+Nimba Worm is infected through shared disks on a network, as well as through +Microsoft IIS, Internet Explorer and mailer of Outlook series. +

+At this time, the worm copies itself by the name *.nws and *.eml on +the shared disk, moreover, by the name of Riched20.dll in the folder +where *.doc file is included. +

+To prevent infection through the shared disk offered by Samba, set +up as follows: +

+

+[global]
+  ...
+  # This can break Administration installations of Office2k.
+  # in that case, don't veto the riched20.dll
+  veto files = /*.eml/*.nws/riched20.dll/
+

+

+By setting the "veto files" parameter, matched files on the Samba +server are completely hidden from the clients and making it impossible +to access them at all. +

+In addition to it, the following setting is also pointed out by the +samba-jp:09448 thread: when the +"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on +a Samba server, it is visible only as "readme.txt" and dangerous +code may be executed if this file is double-clicked. +

+Setting the following, +

+  veto files = /*.{*}/
+

+any files having CLSID in its file extension will be inaccessible from any +clients. +

+This technical article is created based on the discussion of +samba-jp:09448 and samba-jp:10900 threads. +

How can I use samba as a fax server?

Contributor: Gerhard Zuber

Requirements: +

UNIX box (Linux preferred) with SAMBA and a faxmodem
ghostscript package
mgetty+sendfax package
pbm package (portable bitmap tools)

+

First, install and configure the required packages. Be sure to read the mgetty+sendfax +manual carefully.

Tools for printing faxes

Your incomed faxes are in: +/var/spool/fax/incoming. Print it with:

+for i in *
+do
+g3cat $i | g3tolj | lpr -P hp
+done
+

+

+g3cat is in the tools-section, g3tolj is in the contrib-section +for printing to HP lasers. +

+If you want to produce files for displaying and printing with Windows, use +some tools from the pbm-package like the following command: g3cat $i | g3topbm - | ppmtopcx - >$i.pcx +and view it with your favourite Windows tool (maybe paintbrush) +

Making the fax-server

fetch the file mgetty+sendfax/frontends/winword/faxfilter and place it in /usr/local/etc/mgetty+sendfax/(replace /usr/local/ with whatever place you installed mgetty+sendfax)

prepare your faxspool file as mentioned in this file +edit fax/faxspool.in and reinstall or change the final +/usr/local/bin/faxspool too. +

+if [ "$user" = "root" -o "$user" = "fax" -o \
+     "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
+

find the first line and change it to the second.

+make sure you have pbmtext (from the pbm-package). This is +needed for creating the small header line on each page. +

Prepare your faxheader /usr/local/etc/mgetty+sendfax/faxheader

+Edit your /etc/printcap file: +

+# FAX 
+lp3|fax:\
+        :lp=/dev/null:\
+        :sd=/usr/spool/lp3:\
+        :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
+        :lf=/usr/spool/lp3/fax-log:
+

Now, edit your smb.conf so you have a smb based printer named "fax"

Installing the client drivers

+Now you have a printer called "fax" which can be used via +TCP/IP-printing (lpd-system) or via SAMBA (windows printing). +

+On every system you are able to produce postscript-files you +are ready to fax. +

+On Windows 3.1 95 and NT: +

+Install a printer wich produces postscript output, + e.g. apple laserwriter +

Connect the "fax" to your printer.

+Now write your first fax. Use your favourite wordprocessor, +write, winword, notepad or whatever you want, and start +with the headerpage. +

+Usually each fax has a header page. It carries your name, +your address, your phone/fax-number. +

+It carries also the recipient, his address and his *** fax +number ***. Now here is the trick: +

+Use the text: +

+Fax-Nr: 123456789
+

+as the recipients fax-number. Make sure this text does not +occur in regular text ! Make sure this text is not broken +by formatting information, e.g. format it as a single entity. +(Windows Write and Win95 Wordpad are functional, maybe newer + versions of Winword are breaking formatting information). +

+The trick is that postscript output is human readable and +the faxfilter program scans the text for this pattern and +uses the found number as the fax-destination-number. +

+Now print your fax through the fax-printer and it will be +queued for later transmission. Use faxrunq for sending the +queue out. +

Example smb.conf

+[global]
+ printcap name = /etc/printcap
+ print command = /usr/bin/lpr -r -P %p %s
+ lpq command = /usr/bin/lpq -P %p
+ lprm command = /usr/bin/lprm -P %p %j
+
+[fax]
+    comment = FAX (mgetty+sendfax)
+    path = /tmp
+    printable = yes
+    public = yes
+    writable = no
+    create mode = 0700
+    browseable = yes
+    guest ok = no
+

Samba doesn't work well together with DHCP!

+We wish to help those folks who wish to use the ISC DHCP Server and provide +sample configuration settings. Most operating systems today come ship with +the ISC DHCP Server. ISC DHCP is available from: +ftp://ftp.isc.org/isc/dhcp +

+Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows +NT/2000) will lead to problems with browsing and with general network +operation. Windows 9X/ME users often report problems where the TCP/IP and related +network settings will inadvertantly become reset at machine start-up resulting +in loss of configuration settings. This results in increased maintenance +overheads as well as serious user frustration. +

+In recent times users on one mailing list incorrectly attributed the cause of +network operating problems to incorrect configuration of Samba. +

+One user insisted that the only way to provent Windows95 from periodically +performing a full system reset and hardware detection process on start-up was +to install the NetBEUI protocol in addition to TCP/IP. This assertion is not +correct. +

+In the first place, there is NO need for NetBEUI. All Microsoft Windows clients +natively run NetBIOS over TCP/IP, and that is the only protocol that is +recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will +cause problems with browse list operation on most networks. Even Windows NT +networks experience these problems when incorrectly configured Windows95 +systems share the same name space. It is important that only those protocols +that are strictly needed for site specific reasons should EVER be installed. +

+Secondly, and totally against common opinion, DHCP is NOT an evil design but is +an extension of the BOOTP protocol that has been in use in Unix environments +for many years without any of the melt-down problems that some sensationalists +would have us believe can be experienced with DHCP. In fact, DHCP in covered by +rfc1541 and is a very safe method of keeping an MS Windows desktop environment +under control and for ensuring stable network operation. +

+Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95 +store all network configuration settings a registry. There are a few reports +from MS Windows network administrators that warrant mention here. It would appear +that when one sets certain MS TCP/IP protocol settings (either directly or via +DHCP) that these do get written to the registry. Even though a subsequent +change of setting may occur the old value may persist in the registry. This +has been known to create serious networking problems. +

+An example of this occurs when a manual TCP/IP environment is configured to +include a NetBIOS Scope. In this event, when the administrator then changes the +configuration of the MS TCP/IP protocol stack, without first deleting the +current settings, by simply checking the box to configure the MS TCP/IP stack +via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be +applied to the resulting DHCP offered settings UNLESS the DHCP server also sets +a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS +Scope from your DHCP server. The can be done in the dhcpd.conf file with the +parameter: +option netbios-scope ""; +

+While it is true that the Microsoft DHCP server that comes with Windows NT +Server provides only a sub-set of rfc1533 functionality this is hardly an issue +in those sites that already have a large investment and commitment to Unix +systems and technologies. The current state of the art of the DHCP Server +specification in covered in rfc2132. +

How can I assign NetBIOS names to clients with DHCP?

+SMB network clients need to be configured so that all standard TCP/IP name to +address resolution works correctly. Once this has been achieved the SMB +environment provides additional tools and services that act as helper agents in +the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One +such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it +in their Windows NT Server implementation WINS (Windows Internet Name Server). +

+A client needs to be configured so that it has a unique Machine (Computer) +Name. +

+This can be done, but needs a few NT registry hacks and you need to be able to +speak UNICODE, which is of course no problem for a True Wizzard(tm) :) +Instructions on how to do this (including a small util for less capable +Wizzards) can be found at +

http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html

How do I convert between unix and dos text formats?

+Jim barry has written an +excellent drag-and-drop cr/lf converter for +windows. Just drag your file onto the icon and it converts the file. +

+The utilities unix2dos and dos2unix(in the mtools package) should do +the job under unix. +

Does samba have wins replication support?

+At the time of writing there is currently being worked on a wins replication implementation(wrepld). +

PrevUpNext
Chapter5.Common errorsHomeChapter7.Printing problems
diff --git a/docs/faq/FAQ-general.html b/docs/faq/FAQ-general.html new file mode 100644 index 0000000000..0e6cae78d8 --- /dev/null +++ b/docs/faq/FAQ-general.html @@ -0,0 +1,50 @@ + +Chapter1.General Information
Chapter1.General Information
PrevNext

Chapter1.General Information

Table of Contents

Where can I get it?
What do the version numbers mean?
What platforms are supported?
How do I subscribe to the Samba Mailing Lists?

Where can I get it?

+The Samba suite is available at the samba website. +

What do the version numbers mean?

+It is not recommended that you run a version of Samba with the word +"alpha" in its name unless you know what you are doing and are willing +to do some debugging. Many, many people just get the latest +recommended stable release version and are happy. If you are brave, by +all means take the plunge and help with the testing and development - +but don't install it on your departmental server. Samba is typically +very stable and safe, and this is mostly due to the policy of many +public releases. +

+How the scheme works: +

When major changes are made the version number is increased. For +example, the transition from 1.9.15 to 1.9.16. However, this version +number will not appear immediately and people should continue to use +1.9.15 for production systems (see next point.)
Just after major changes are made the software is considered +unstable, and a series of alpha releases are distributed, for example +1.9.16alpha1. These are for testing by those who know what they are +doing. The "alpha" in the filename will hopefully scare off those who +are just looking for the latest version to install.
When the release manager, currently Jerry, thinks that the alphas have stabilised to the point +where he would recommend new users install it, he renames it to the +same version number without the alpha, for example 1.9.16.
Inevitably bugs are found in the "stable" releases and minor patch +levels are released which give us the pXX series, for example 1.9.16p2.

+

+So the progression goes: + +

+1.9.15p7	(production)
+1.9.15p8	(production)
+1.9.16alpha1	(test sites only)
+:
+1.9.16alpha20	(test sites only)
+1.9.16		(production)
+1.9.16p1	(production)
+

+

+The above system means that whenever someone looks at the samba ftp +site they will be able to grab the highest numbered release without an +alpha in the name and be sure of getting the current recommended +version. +

What platforms are supported?

+Many different platforms have run Samba successfully. The platforms +most widely used and thus best tested are Linux and SunOS.

+At time of writing, there is support (or has been support for in earlier +versions): +

A/UX 3.0
AIX
Altos Series 386/1000
Amiga
Apollo Domain/OS sr10.3
BSDI
B.O.S. (Bull Operating System)
Cray, Unicos 8.0
Convex
DGUX.
DNIX.
FreeBSD
HP-UX
Intergraph.
Linux with/without shadow passwords and quota
LYNX 2.3.0
MachTen (a unix like system for Macintoshes)
Motorola 88xxx/9xx range of machines
NetBSD
NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
OS/2 using EMX 0.9b
OSF1
QNX 4.22
RiscIX.
RISCOs 5.0B
SEQUENT.
SCO (including: 3.2v2, European dist., OpenServer 5)
SGI.
SMP_DC.OSx v1.1-94c079 on Pyramid S series
SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
SUNOS 4
SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
Sunsoft ISC SVR3V4
SVR4
System V with some berkely extensions (Motorola 88k R32V3.2).
ULTRIX.
UNIXWARE
UXP/DS

How do I subscribe to the Samba Mailing Lists?

+Look at the samba mailing list page +

PrevUpNext
Samba FAQHomeChapter2.Compiling and installing Samba on a Unix host
diff --git a/docs/faq/faq-clientapp.html b/docs/faq/faq-clientapp.html deleted file mode 100644 index 4aa8a50c4b..0000000000 --- a/docs/faq/faq-clientapp.html +++ /dev/null @@ -1,281 +0,0 @@ - -Specific client application problems
Samba FAQ
PrevNext

Chapter 4. Specific client application problems

4.1. MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"

When installing MS Office on a Samba drive for which you have admin -user permissions, ie. admin users = username, you will find the -setup program unable to complete the installation.

To get around this problem, do the installation without admin user -permissions The problem is that MS Office Setup checks that a file is -rdonly by trying to open it for writing.

Admin users can always open a file for writing, as they run as root. -You just have to install as a non-admin user and then use "chown -R" -to fix the owner.

4.2. How to use a Samba share as an administrative share for MS Office, etc.

Microsoft Office products can be installed as an administrative installation -from which the application can either be run off the administratively installed -product that resides on a shared resource, or from which that product can be -installed onto workstation clients.

The general mechanism for implementing an adminstrative installation involves -running X:\setup /A, where X is the drive letter of either CDROM or floppy.

This installation process will NOT install the product for use per se, but -rather results in unpacking of the compressed distribution files into a target -shared folder. For this process you need write privilidge to the share and it -is desirable to enable file locking and share mode operation during this -process.

Subsequent installation of MS Office from this share will FAIL unless certain -precautions are taken. This failure will be caused by share mode operation -which will prevent the MS Office installation process from re-opening various -dynamic link library files and will cause sporadic file not found problems.

  • As soon as the administrative installation (unpacking) has completed -set the following parameters on the share containing it:

    [MSOP95]
-	path = /where_you_put_it
-	comment = Your comment
-	volume = "The_CD_ROM_Label"
-	read only = yes
-	available = yes
-	share modes = no
-	locking = no
-	browseable = yes
-	public = yes

  • Now you are ready to run the setup program from the Microsoft Windows -workstation as follows: \\"Server_Name"\MSOP95\msoffice\setup

4.3. Microsoft Access database opening errors

Here are some notes on running MS-Access on a Samba drive from Stefan Kjellberg

Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.
Make sure that you open the database as 'shared' and to 'lock modified records'
Of course locking must be enabled for the particular share (smb.conf)

PrevHomeNext
Configuration problems Common errors
\ No newline at end of file diff --git a/docs/faq/faq-config.html b/docs/faq/faq-config.html deleted file mode 100644 index 12bb8e2e2c..0000000000 --- a/docs/faq/faq-config.html +++ /dev/null @@ -1,182 +0,0 @@ - -Configuration problems
Samba FAQ
PrevNext

Chapter 3. Configuration problems

3.1. I have set 'force user' and samba still makes 'root' the owner of all the files I touch!

When you have a user in 'admin users', samba will always do file operations for -this user as 'root', even if 'force user' has been set.

3.2. I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!

Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these -passwords to the unix password database, so it needs it's own user database. You can -add users to this database using "smbpasswd -a user-name".

See also the "User database" chapter of the samba HOWTO Collection.

PrevHomeNext
Compiling and installing Samba on a Unix host Specific client application problems
\ No newline at end of file diff --git a/docs/faq/faq-errors.html b/docs/faq/faq-errors.html deleted file mode 100644 index 851970cd33..0000000000 --- a/docs/faq/faq-errors.html +++ /dev/null @@ -1,373 +0,0 @@ - -Common errors
Samba FAQ
PrevNext

Chapter 5. Common errors

5.1. Not listening for calling name

Session request failed (131,129) with myname=HOBBES destname=CALVIN
-Not listening for calling name

If you get this when talking to a Samba box then it means that your -global "hosts allow" or "hosts deny" settings are causing the Samba -server to refuse the connection.

Look carefully at your "hosts allow" and "hosts deny" lines in the -global section of smb.conf.

It can also be a problem with reverse DNS lookups not functioning -correctly, leading to the remote host identity not being able to -be confirmed, but that is less likely.

5.2. System Error 1240

System error 1240 means that the client is refusing to talk -to a non-encrypting server. Microsoft changed WinNT in service -pack 3 to refuse to connect to servers that do not support -SMB password encryption.

There are two main solutions: -

enable SMB password encryption in Samba. See the encryption part of -the samba HOWTO Collection
disable this new behaviour in NT. See the section about -Windows NT in the chapter "Portability" of the samba HOWTO collection

5.3. smbclient ignores -N !

"When getting the list of shares available on a host using the command -smbclient -N -L -the program always prompts for the password if the server is a Samba server. -It also ignores the "-N" argument when querying some (but not all) of our -NT servers."

No, it does not ignore -N, it is just that your server rejected the -null password in the connection, so smbclient prompts for a password -to try again.

To get the behaviour that you probably want use smbclient -L host -U%

This will set both the username and password to null, which is -an anonymous login for SMB. Using -N would only set the password -to null, and this is not accepted as an anonymous login for most -SMB servers.

5.4. The data on the CD-Drive I've shared seems to be corrupted!

Some OSes (notably Linux) default to auto detection of file type on -cdroms and do cr/lf translation. This is a very bad idea when use with -Samba. It causes all sorts of stuff ups.

To overcome this problem use conv=binary when mounting the cdrom -before exporting it with Samba.

5.5. Why can users access home directories of other users?

"We are unable to keep individual users from mapping to any other user's -home directory once they have supplied a valid password! They only need -to enter their own password. I have not found *any* method that I can -use to configure samba to enforce that only a user may map their own -home directory."

"User xyzzy can map his home directory. Once mapped user xyzzy can also map -*anyone* elses home directory!"

This is not a security flaw, it is by design. Samba allows -users to have *exactly* the same access to the UNIX filesystem -as they would if they were logged onto the UNIX box, except -that it only allows such views onto the file system as are -allowed by the defined shares.

This means that if your UNIX home directories are set up -such that one user can happily cd into another users -directory and do an ls, the UNIX security solution is to -change the UNIX file permissions on the users home directories -such that the cd and ls would be denied.

Samba tries very hard not to second guess the UNIX administrators -security policies, and trusts the UNIX admin to set -the policies and permissions he or she desires.

Samba does allow the setup you require when you have set the -"only user = yes" option on the share, is that you have not set the -valid users list for the share.

Note that only user works in conjunction with the users= list, -so to get the behavior you require, add the line : -

users = %S
-this is equivalent to: -
valid users = %S
-to the definition of the [homes] share, as recommended in -the smb.conf man page.

5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"

A domain controller has to announce on the network who it is. This usually takes a while.

PrevHomeNext
Specific client application problems Features
\ No newline at end of file diff --git a/docs/faq/faq-features.html b/docs/faq/faq-features.html deleted file mode 100644 index 7ec0d2143d..0000000000 --- a/docs/faq/faq-features.html +++ /dev/null @@ -1,601 +0,0 @@ - -Features
Samba FAQ
PrevNext

Chapter 6. Features

6.1. How can I prevent my samba server from being used to distribute the Nimda worm?

Author: HASEGAWA Yosuke (translated by TAKAHASHI Motonobu)

Nimba Worm is infected through shared disks on a network, as well as through -Microsoft IIS, Internet Explorer and mailer of Outlook series.

At this time, the worm copies itself by the name *.nws and *.eml on -the shared disk, moreover, by the name of Riched20.dll in the folder -where *.doc file is included.

To prevent infection through the shared disk offered by Samba, set -up as follows:

[global]
-  ...
-  # This can break Administration installations of Office2k.
-  # in that case, don't veto the riched20.dll
-  veto files = /*.eml/*.nws/riched20.dll/

By setting the "veto files" parameter, matched files on the Samba -server are completely hidden from the clients and making it impossible -to access them at all.

In addition to it, the following setting is also pointed out by the -samba-jp:09448 thread: when the -"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on -a Samba server, it is visible only as "readme.txt" and dangerous -code may be executed if this file is double-clicked.

Setting the following, -

  veto files = /*.{*}/
-any files having CLSID in its file extension will be inaccessible from any -clients.

This technical article is created based on the discussion of -samba-jp:09448 and samba-jp:10900 threads.

6.2. How can I use samba as a fax server?

Contributor: Gerhard Zuber

Requirements: -

UNIX box (Linux preferred) with SAMBA and a faxmodem
ghostscript package
mgetty+sendfax package
pbm package (portable bitmap tools)

First, install and configure the required packages. Be sure to read the mgetty+sendfax -manual carefully.

6.2.1. Tools for printing faxes

Your incomed faxes are in: -/var/spool/fax/incoming. Print it with:

for i in *
-do
-g3cat $i | g3tolj | lpr -P hp
-done

g3cat is in the tools-section, g3tolj is in the contrib-section -for printing to HP lasers.

If you want to produce files for displaying and printing with Windows, use -some tools from the pbm-package like the following command: g3cat $i | g3topbm - | ppmtopcx - >$i.pcx -and view it with your favourite Windows tool (maybe paintbrush)

6.2.2. Making the fax-server

fetch the file mgetty+sendfax/frontends/winword/faxfilter and place it in /usr/local/etc/mgetty+sendfax/(replace /usr/local/ with whatever place you installed mgetty+sendfax)

prepare your faxspool file as mentioned in this file -edit fax/faxspool.in and reinstall or change the final -/usr/local/bin/faxspool too.

if [ "$user" = "root" -o "$user" = "fax" -o \
-     "$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]

find the first line and change it to the second.

make sure you have pbmtext (from the pbm-package). This is -needed for creating the small header line on each page.

Prepare your faxheader /usr/local/etc/mgetty+sendfax/faxheader

Edit your /etc/printcap file: -

# FAX 
-lp3|fax:\
-        :lp=/dev/null:\
-        :sd=/usr/spool/lp3:\
-        :if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
-        :lf=/usr/spool/lp3/fax-log:

Now, edit your smb.conf so you have a smb based printer named "fax"

6.2.3. Installing the client drivers

Now you have a printer called "fax" which can be used via -TCP/IP-printing (lpd-system) or via SAMBA (windows printing).

On every system you are able to produce postscript-files you -are ready to fax.

On Windows 3.1 95 and NT:

Install a printer wich produces postscript output, - e.g. apple laserwriter

Connect the "fax" to your printer.

Now write your first fax. Use your favourite wordprocessor, -write, winword, notepad or whatever you want, and start -with the headerpage.

Usually each fax has a header page. It carries your name, -your address, your phone/fax-number.

It carries also the recipient, his address and his *** fax -number ***. Now here is the trick:

Use the text: -

Fax-Nr: 123456789
-as the recipients fax-number. Make sure this text does not -occur in regular text ! Make sure this text is not broken -by formatting information, e.g. format it as a single entity. -(Windows Write and Win95 Wordpad are functional, maybe newer - versions of Winword are breaking formatting information).

The trick is that postscript output is human readable and -the faxfilter program scans the text for this pattern and -uses the found number as the fax-destination-number.

Now print your fax through the fax-printer and it will be -queued for later transmission. Use faxrunq for sending the -queue out.

6.2.4. Example smb.conf

[global]
- printcap name = /etc/printcap
- print command = /usr/bin/lpr -r -P %p %s
- lpq command = /usr/bin/lpq -P %p
- lprm command = /usr/bin/lprm -P %p %j
-
-[fax]
-    comment = FAX (mgetty+sendfax)
-    path = /tmp
-    printable = yes
-    public = yes
-    writable = no
-    create mode = 0700
-    browseable = yes
-    guest ok = no

6.3. Samba doesn't work well together with DHCP!

We wish to help those folks who wish to use the ISC DHCP Server and provide -sample configuration settings. Most operating systems today come ship with -the ISC DHCP Server. ISC DHCP is available from: -ftp://ftp.isc.org/isc/dhcp

Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows -NT/2000) will lead to problems with browsing and with general network -operation. Windows 9X/ME users often report problems where the TCP/IP and related -network settings will inadvertantly become reset at machine start-up resulting -in loss of configuration settings. This results in increased maintenance -overheads as well as serious user frustration.

In recent times users on one mailing list incorrectly attributed the cause of -network operating problems to incorrect configuration of Samba.

One user insisted that the only way to provent Windows95 from periodically -performing a full system reset and hardware detection process on start-up was -to install the NetBEUI protocol in addition to TCP/IP. This assertion is not -correct.

In the first place, there is NO need for NetBEUI. All Microsoft Windows clients -natively run NetBIOS over TCP/IP, and that is the only protocol that is -recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will -cause problems with browse list operation on most networks. Even Windows NT -networks experience these problems when incorrectly configured Windows95 -systems share the same name space. It is important that only those protocols -that are strictly needed for site specific reasons should EVER be installed.

Secondly, and totally against common opinion, DHCP is NOT an evil design but is -an extension of the BOOTP protocol that has been in use in Unix environments -for many years without any of the melt-down problems that some sensationalists -would have us believe can be experienced with DHCP. In fact, DHCP in covered by -rfc1541 and is a very safe method of keeping an MS Windows desktop environment -under control and for ensuring stable network operation.

Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95 -store all network configuration settings a registry. There are a few reports -from MS Windows network administrators that warrant mention here. It would appear -that when one sets certain MS TCP/IP protocol settings (either directly or via -DHCP) that these do get written to the registry. Even though a subsequent -change of setting may occur the old value may persist in the registry. This -has been known to create serious networking problems.

An example of this occurs when a manual TCP/IP environment is configured to -include a NetBIOS Scope. In this event, when the administrator then changes the -configuration of the MS TCP/IP protocol stack, without first deleting the -current settings, by simply checking the box to configure the MS TCP/IP stack -via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be -applied to the resulting DHCP offered settings UNLESS the DHCP server also sets -a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS -Scope from your DHCP server. The can be done in the dhcpd.conf file with the -parameter: -option netbios-scope "";

While it is true that the Microsoft DHCP server that comes with Windows NT -Server provides only a sub-set of rfc1533 functionality this is hardly an issue -in those sites that already have a large investment and commitment to Unix -systems and technologies. The current state of the art of the DHCP Server -specification in covered in rfc2132.

6.4. How can I assign NetBIOS names to clients with DHCP?

SMB network clients need to be configured so that all standard TCP/IP name to -address resolution works correctly. Once this has been achieved the SMB -environment provides additional tools and services that act as helper agents in -the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One -such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it -in their Windows NT Server implementation WINS (Windows Internet Name Server).

A client needs to be configured so that it has a unique Machine (Computer) -Name.

This can be done, but needs a few NT registry hacks and you need to be able to -speak UNICODE, which is of course no problem for a True Wizzard(tm) :) -Instructions on how to do this (including a small util for less capable -Wizzards) can be found at

http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html

6.5. How do I convert between unix and dos text formats?

Jim barry has written an excellent drag-and-drop cr/lf converter for -windows. Just drag your file onto the icon and it converts the file.

The utilities unix2dos and dos2unix(in the mtools package) should do -the job under unix.

6.6. Does samba have wins replication support?

At the time of writing there is currently being worked on a wins replication implementation(wrepld).

PrevHomeNext
Common errors Printing problems
\ No newline at end of file diff --git a/docs/faq/faq-general.html b/docs/faq/faq-general.html deleted file mode 100644 index 790367e8e5..0000000000 --- a/docs/faq/faq-general.html +++ /dev/null @@ -1,484 +0,0 @@ - -General Information
Samba FAQ
PrevNext

Chapter 1. General Information

1.1. Where can I get it?

The Samba suite is available at the samba website.

1.2. What do the version numbers mean?

It is not recommended that you run a version of Samba with the word -"alpha" in its name unless you know what you are doing and are willing -to do some debugging. Many, many people just get the latest -recommended stable release version and are happy. If you are brave, by -all means take the plunge and help with the testing and development - -but don't install it on your departmental server. Samba is typically -very stable and safe, and this is mostly due to the policy of many -public releases.

How the scheme works: -

When major changes are made the version number is increased. For -example, the transition from 1.9.15 to 1.9.16. However, this version -number will not appear immediately and people should continue to use -1.9.15 for production systems (see next point.)
Just after major changes are made the software is considered -unstable, and a series of alpha releases are distributed, for example -1.9.16alpha1. These are for testing by those who know what they are -doing. The "alpha" in the filename will hopefully scare off those who -are just looking for the latest version to install.
When Andrew thinks that the alphas have stabilised to the point -where he would recommend new users install it, he renames it to the -same version number without the alpha, for example 1.9.16.
Inevitably bugs are found in the "stable" releases and minor patch -levels are released which give us the pXX series, for example 1.9.16p2.

So the progression goes: - -

1.9.15p7	(production)
-1.9.15p8	(production)
-1.9.16alpha1	(test sites only)
-:
-1.9.16alpha20	(test sites only)
-1.9.16		(production)
-1.9.16p1	(production)

The above system means that whenever someone looks at the samba ftp -site they will be able to grab the highest numbered release without an -alpha in the name and be sure of getting the current recommended -version.

1.3. What platforms are supported?

Many different platforms have run Samba successfully. The platforms -most widely used and thus best tested are Linux and SunOS.

At time of writing, there is support (or has been support for in earlier -versions):

A/UX 3.0
AIX
Altos Series 386/1000
Amiga
Apollo Domain/OS sr10.3
BSDI
B.O.S. (Bull Operating System)
Cray, Unicos 8.0
Convex
DGUX.
DNIX.
FreeBSD
HP-UX
Intergraph.
Linux with/without shadow passwords and quota
LYNX 2.3.0
MachTen (a unix like system for Macintoshes)
Motorola 88xxx/9xx range of machines
NetBSD
NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
OS/2 using EMX 0.9b
OSF1
QNX 4.22
RiscIX.
RISCOs 5.0B
SEQUENT.
SCO (including: 3.2v2, European dist., OpenServer 5)
SGI.
SMP_DC.OSx v1.1-94c079 on Pyramid S series
SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
SUNOS 4
SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
Sunsoft ISC SVR3V4
SVR4
System V with some berkely extensions (Motorola 88k R32V3.2).
ULTRIX.
UNIXWARE
UXP/DS

1.5. Pizza supply details

Those who have registered in the Samba survey as "Pizza Factory" will -already know this, but the rest may need some help. Andrew doesn't ask -for payment, but he does appreciate it when people give him -pizza. This calls for a little organisation when the pizza donor is -twenty thousand kilometres away, but it has been done.

Method 1: Ring up your local branch of an international pizza chain -and see if they honour their vouchers internationally. Pizza Hut do, -which is how the entire Canberra Linux Users Group got to eat pizza -one night, courtesy of someone in the US.

Method 2: Ring up a local pizza shop in Canberra and quote a credit -card number for a certain amount, and tell them that Andrew will be -collecting it (don't forget to tell him.) One kind soul from Germany -did this.

Method 3: Purchase a pizza voucher from your local pizza shop that has -no international affiliations and send it to Andrew. It is completely -useless but he can hang it on the wall next to the one he already has -from Germany :-)

Method 4: Air freight him a pizza with your favourite regional -flavours. It will probably get stuck in customs or torn apart by -hungry sniffer dogs but it will have been a noble gesture.

PrevHomeNext
Samba FAQ Compiling and installing Samba on a Unix host
\ No newline at end of file diff --git a/docs/faq/faq-install.html b/docs/faq/faq-install.html deleted file mode 100644 index 3d459ff334..0000000000 --- a/docs/faq/faq-install.html +++ /dev/null @@ -1,582 +0,0 @@ - -Compiling and installing Samba on a Unix host
Samba FAQ
PrevNext

Chapter 2. Compiling and installing Samba on a Unix host

2.1. I can't see the Samba server in any browse lists!

See Browsing.html in the docs directory of the samba source -for more information on browsing.

If your GUI client does not permit you to select non-browsable -servers, you may need to do so on the command line. For example, under -Lan Manager you might connect to the above service as disk drive M: -thusly: -

   net use M: \\mary\fred
-The details of how to do this and the specific syntax varies from -client to client - check your client's documentation.

2.3. Some files on the server show up with really wierd filenames when I view the files from my client!

If you check what files are not showing up, you will note that they -are files which contain upper case letters or which are otherwise not -DOS-compatible (ie, they are not legal DOS filenames for some reason).

The Samba server can be configured either to ignore such files -completely, or to present them to the client in "mangled" form. If you -are not seeing the files at all, the Samba server has most likely been -configured to ignore them. Consult the man page smb.conf(5) for -details of how to change this - the parameter you need to set is -"mangled names = yes".

2.4. My client reports "cannot locate specified computer" or similar

This indicates one of three things: You supplied an incorrect server -name, the underlying TCP/IP layer is not working correctly, or the -name you specified cannot be resolved.

After carefully checking that the name you typed is the name you -should have typed, try doing things like pinging a host or telnetting -to somewhere on your network to see if TCP/IP is functioning OK. If it -is, the problem is most likely name resolution.

If your client has a facility to do so, hardcode a mapping between the -hosts IP and the name you want to use. For example, with Lan Manager -or Windows for Workgroups you would put a suitable entry in the file -LMHOSTS. If this works, the problem is in the communication between -your client and the netbios name server. If it does not work, then -there is something fundamental wrong with your naming and the solution -is beyond the scope of this document.

If you do not have any server on your subnet supplying netbios name -resolution, hardcoded mappings are your only option. If you DO have a -netbios name server running (such as the Samba suite's nmbd program), -the problem probably lies in the way it is set up. Refer to Section -Two of this FAQ for more ideas.

By the way, remember to REMOVE the hardcoded mapping before further -tests :-)

2.5. My client reports "cannot locate specified share name" or similar

This message indicates that your client CAN locate the specified -server, which is a good start, but that it cannot find a service of -the name you gave.

The first step is to check the exact name of the service you are -trying to connect to (consult your system administrator). Assuming it -exists and you specified it correctly (read your client's docs on how -to specify a service name correctly), read on:

Many clients cannot accept or use service names longer than eight characters.
Many clients cannot accept or use service names containing spaces.
Some servers (not Samba though) are case sensitive with service names.
Some clients force service names into upper case.

2.6. Printing doesn't work

Make sure that the specified print command for the service you are -connecting to is correct and that it has a fully-qualified path (eg., -use "/usr/bin/lpr" rather than just "lpr").

Make sure that the spool directory specified for the service is -writable by the user connected to the service. In particular the user -"nobody" often has problems with printing, even if it worked with an -earlier version of Samba. Try creating another guest user other than -"nobody".

Make sure that the user specified in the service is permitted to use -the printer.

Check the debug log produced by smbd. Search for the printer name and -see if the log turns up any clues. Note that error messages to do with -a service ipc$ are meaningless - they relate to the way the client -attempts to retrieve status information when using the LANMAN1 -protocol.

If using WfWg then you need to set the default protocol to TCP/IP, not -Netbeui. This is a WfWg bug.

If using the Lanman1 protocol (the default) then try switching to -coreplus. Also not that print status error messages don't mean -printing won't work. The print status is received by a different -mechanism.

2.7. My client reports "This server is not configured to list shared resources"

Your guest account is probably invalid for some reason. Samba uses the -guest account for browsing in smbd. Check that your guest account is -valid.

See also 'guest account' in smb.conf man page.

2.8. Log message "you appear to have a trapdoor uid system"

This can have several causes. It might be because you are using a uid -or gid of 65535 or -1. This is a VERY bad idea, and is a big security -hole. Check carefully in your /etc/passwd file and make sure that no -user has uid 65535 or -1. Especially check the "nobody" user, as many -broken systems are shipped with nobody setup with a uid of 65535.

It might also mean that your OS has a trapdoor uid/gid system :-)

This means that once a process changes effective uid from root to -another user it can't go back to root. Unfortunately Samba relies on -being able to change effective uid from root to non-root and back -again to implement its security policy. If your OS has a trapdoor uid -system this won't work, and several things in Samba may break. Less -things will break if you use user or server level security instead of -the default share level security, but you may still strike -problems.

The problems don't give rise to any security holes, so don't panic, -but it does mean some of Samba's capabilities will be unavailable. -In particular you will not be able to connect to the Samba server as -two different uids at once. This may happen if you try to print as a -"guest" while accessing a share as a normal user. It may also affect -your ability to list the available shares as this is normally done as -the guest user.

Complain to your OS vendor and ask them to fix their system.

Note: the reason why 65535 is a VERY bad choice of uid and gid is that -it casts to -1 as a uid, and the setreuid() system call ignores (with -no error) uid changes to -1. This means any daemon attempting to run -as uid 65535 will actually run as root. This is not good!

2.9. Why are my file's timestamps off by an hour, or by a few hours?

This is from Paul Eggert eggert@twinsun.com.

Most likely it's a problem with your time zone settings.

Internally, Samba maintains time in traditional Unix format, -namely, the number of seconds since 1970-01-01 00:00:00 Universal Time -(or ``GMT''), not counting leap seconds.

On the server side, Samba uses the Unix TZ variable to convert -internal timestamps to and from local time. So on the server side, there are -two things to get right. -

The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.

TZ must have the correct value.

If possible, use geographical time zone settings -(e.g. TZ='America/Los_Angeles' or perhaps - TZ=':US/Pacific'). These are supported by most -popular Unix OSes, are easier to get right, and are -more accurate for historical timestamps. If your -operating system has out-of-date tables, you should be -able to update them from the public domain time zone -tables at ftp://elsie.nci.nih.gov/pub/.

If your system does not support geographical timezone -settings, you must use a Posix-style TZ strings, e.g. -TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. -Posix TZ strings can take the following form (with optional - items in brackets): -

	StdOffset[Dst[Offset],Date/Time,Date/Time]
- where:

`Std' is the standard time designation (e.g. `PST').
`Offset' is the number of hours behind UTC (e.g. `8'). -Prepend a `-' if you are ahead of UTC, and -append `:30' if you are at a half-hour offset. -Omit all the remaining items if you do not use -daylight-saving time.
`Dst' is the daylight-saving time designation -(e.g. `PDT').
The optional second `Offset' is the number of -hours that daylight-saving time is behind UTC. -The default is 1 hour ahead of standard time.
`Date/Time,Date/Time' specify when daylight-saving -time starts and ends. The format for a date is -`Mm.n.d', which specifies the dth day (0 is Sunday) -of the nth week of the mth month, where week 5 means -the last such day in the month. The format for a -time is [h]h[:mm[:ss]], using a 24-hour clock.

Other Posix string formats are allowed but you don't want -to know about them.

On the client side, you must make sure that your client's clock and -time zone is also set appropriately. [[I don't know how to do this.]] -Samba traditionally has had many problems dealing with time zones, due -to the bizarre ways that Microsoft network protocols handle time -zones.

2.10. How do I set the printer driver name correctly?

Question: -" On NT, I opened "Printer Manager" and "Connect to Printer". - Enter ["\\ptdi270\ps1"] in the box of printer. I got the - following error message - "

     You do not have sufficient access to your machine
-     to connect to the selected printer, since a driver
-     needs to be installed locally.
-
-

Answer:

In the more recent versions of Samba you can now set the "printer -driver" in smb.conf. This tells the client what driver to use. For -example:

     printer driver = HP LaserJet 4L

With this, NT knows to use the right driver. You have to get this string -exactly right.

To find the exact string to use, you need to get to the dialog box in -your client where you select which printer driver to install. The -correct strings for all the different printers are shown in a listbox -in that dialog box.

PrevHomeNext
General Information Configuration problems
\ No newline at end of file diff --git a/docs/faq/faq-printing.html b/docs/faq/faq-printing.html deleted file mode 100644 index a806b15de8..0000000000 --- a/docs/faq/faq-printing.html +++ /dev/null @@ -1,181 +0,0 @@ - -Printing problems
Samba FAQ
Prev 

Chapter 7. Printing problems

7.1. setdriver or cupsaddsmb failes

setdriver expects the following setup: - -

you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.
printer admins has to be defined in [global]
upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.
Make sure that the user you're connecting as is able to write to the print$ directories
Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)
Use setdriver to associate the driver with a printer

The setdriver call will fail if the printer doesn't already exist in -samba's view of the world. Either create the printer in cups and -restart samba, or create an add printer command (see smb.conf doco) -and use RPC calls to create a printer. NB the add printer command MUST -return a single line of text indicating which port the printer was -added on. If it doesn't, Samba won't reload the printer -definitions. Although samba doesn't really support the notion of -ports, suitable add printer command and enumport command settings can -allow you pretty good remote control of the samba printer setup.

PrevHome 
Features  
\ No newline at end of file diff --git a/docs/faq/samba-faq.html b/docs/faq/samba-faq.html index 600c966034..d9c14289b1 100644 --- a/docs/faq/samba-faq.html +++ b/docs/faq/samba-faq.html @@ -1,376 +1,11 @@ - -Samba FAQ

Samba FAQ

Samba Team

Dedication

This is the Frequently Asked Questions (FAQ) document for + +Samba FAQ

Samba FAQ
Next

Samba FAQ

Samba Team

October 2002

Dedication

+This is the Frequently Asked Questions (FAQ) document for Samba, the free and very popular SMB server product. An SMB server allows file and printer connections from clients such as Windows, OS/2, Linux and others. Current to version 3.0. Please send any corrections to the samba documentation mailinglist at -samba-doc@samba.org. +samba-doc@samba.org. This FAQ was based on the old Samba FAQ by Dan Shearer and Paul Blackman, -and the old samba text documents which were mostly written by John Terpstra.

Table of Contents
1. General Information
1.1. Where can I get it?
1.2. What do the version numbers mean?
1.3. What platforms are supported?
1.4. How do I subscribe to the Samba Mailing Lists?
1.5. Pizza supply details
2. Compiling and installing Samba on a Unix host
2.1. I can't see the Samba server in any browse lists!
2.2. Some files that I KNOW are on the server don't show up when I view the files from my client!
2.3. Some files on the server show up with really wierd filenames when I view the files from my client!
2.4. My client reports "cannot locate specified computer" or similar
2.5. My client reports "cannot locate specified share name" or similar
2.6. Printing doesn't work
2.7. My client reports "This server is not configured to list shared resources"
2.8. Log message "you appear to have a trapdoor uid system"
2.9. Why are my file's timestamps off by an hour, or by a few hours?
2.10. How do I set the printer driver name correctly?
3. Configuration problems
3.1. I have set 'force user' and samba still makes 'root' the owner of all the files I touch!
3.2. I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!
4. Specific client application problems
4.1. MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"
4.2. How to use a Samba share as an administrative share for MS Office, etc.
4.3. Microsoft Access database opening errors
5. Common errors
5.1. Not listening for calling name
5.2. System Error 1240
5.3. smbclient ignores -N !
5.4. The data on the CD-Drive I've shared seems to be corrupted!
5.5. Why can users access home directories of other users?
5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"
5.7. I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
6. Features
6.1. How can I prevent my samba server from being used to distribute the Nimda worm?
6.2. How can I use samba as a fax server?
6.2.1. Tools for printing faxes
6.2.2. Making the fax-server
6.2.3. Installing the client drivers
6.2.4. Example smb.conf
6.3. Samba doesn't work well together with DHCP!
6.4. How can I assign NetBIOS names to clients with DHCP?
6.5. How do I convert between unix and dos text formats?
6.6. Does samba have wins replication support?
7. Printing problems
7.1. setdriver or cupsaddsmb failes
  Next
  General Information
\ No newline at end of file +and the old samba text documents which were mostly written by John Terpstra. +

Table of Contents

1. General Information
Where can I get it?
What do the version numbers mean?
What platforms are supported?
How do I subscribe to the Samba Mailing Lists?
2. Compiling and installing Samba on a Unix host
I can't see the Samba server in any browse lists!
Some files that I KNOW are on the server don't show up when I view the files from my client!
Some files on the server show up with really wierd filenames when I view the files from my client!
My client reports "cannot locate specified computer" or similar
My client reports "cannot locate specified share name" or similar
Printing doesn't work
My client reports "This server is not configured to list shared resources"
Log message "you appear to have a trapdoor uid system"
Why are my file's timestamps off by an hour, or by a few hours?
How do I set the printer driver name correctly?
3. Configuration problems
I have set 'force user' and samba still makes 'root' the owner of all the files I touch!
I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!
How can I make samba use netbios scope ID's
4. Specific client application problems
MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"
How to use a Samba share as an administrative share for MS Office, etc.
Microsoft Access database opening errors
5. Common errors
Not listening for calling name
System Error 1240
smbclient ignores -N !
The data on the CD-Drive I've shared seems to be corrupted!
Why can users access home directories of other users?
Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"
I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs
6. Features
How can I prevent my samba server from being used to distribute the Nimda worm?
How can I use samba as a fax server?
Tools for printing faxes
Making the fax-server
Installing the client drivers
Example smb.conf
Samba doesn't work well together with DHCP!
How can I assign NetBIOS names to clients with DHCP?
How do I convert between unix and dos text formats?
Does samba have wins replication support?
7. Printing problems
setdriver or cupsaddsmb failes
Next
Chapter1.General Information
diff --git a/docs/htmldocs/Samba-Developers-Guide.html b/docs/htmldocs/Samba-Developers-Guide.html index 142d9dc537..cc12fe60f8 100644 --- a/docs/htmldocs/Samba-Developers-Guide.html +++ b/docs/htmldocs/Samba-Developers-Guide.html @@ -1,1176 +1,176 @@ - -SAMBA Developers Guide

Abstract

Last Update : Mon Sep 30 15:23:53 CDT 2002

This book is a collection of documents that might be useful for +SAMBA Developers Guide

SAMBA Developers Guide

SAMBA Team

Abstract

+Last Update : Mon Sep 30 15:23:53 CDT 2002 +

+This book is a collection of documents that might be useful for people developing samba or those interested in doing so. It's nothing more than a collection of documents written by samba developers about the internals of various parts of samba and the SMB protocol. It's still incomplete. The most recent version of this document -can be found at http://devel.samba.org/. -Please send updates to jelmer@samba.org.

This documentation is distributed under the GNU General Public License (GPL) +can be found at http://devel.samba.org/. +Please send updates to Jelmer Veenrooij. +

+This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt

Table of Contents
1. Definition of NetBIOS Protocol and Name Resolution Modes
1.1. NETBIOS
1.2. BROADCAST NetBIOS
1.3. NBNS NetBIOS
2. Samba Architecture
2.1. Introduction
2.2. Multithreading and Samba
2.3. Threading smbd
2.4. Threading nmbd
2.5. nbmd Design
3. The samba DEBUG system
3.1. New Output Syntax
3.2. The DEBUG() Macro
3.3. The DEBUGADD() Macro
3.4. The DEBUGLVL() Macro
3.5. New Functions
3.5.1. dbgtext()
3.5.2. dbghdr()
3.5.3. format_debug_text()
4. Coding Suggestions
5. Samba Internals
5.1. Character Handling
5.2. The new functions
5.3. Macros in byteorder.h
5.3.1. CVAL(buf,pos)
5.3.2. PVAL(buf,pos)
5.3.3. SCVAL(buf,pos,val)
5.3.4. SVAL(buf,pos)
5.3.5. IVAL(buf,pos)
5.3.6. SVALS(buf,pos)
5.3.7. IVALS(buf,pos)
5.3.8. SSVAL(buf,pos,val)
5.3.9. SIVAL(buf,pos,val)
5.3.10. SSVALS(buf,pos,val)
5.3.11. SIVALS(buf,pos,val)
5.3.12. RSVAL(buf,pos)
5.3.13. RIVAL(buf,pos)
5.3.14. RSSVAL(buf,pos,val)
5.3.15. RSIVAL(buf,pos,val)
5.4. LAN Manager Samba API
5.4.1. Parameters
5.4.2. Return value
5.5. Code character table
6. The smb.conf file
6.1. Lexical Analysis
6.1.1. Handling of Whitespace
6.1.2. Handling of Line Continuation
6.1.3. Line Continuation Quirks
6.2. Syntax
6.2.1. About params.c
7. NetBIOS in a Unix World
7.1. Introduction
7.2. Usernames
7.3. File Ownership
7.4. Passwords
7.5. Locking
7.6. Deny Modes
7.7. Trapdoor UIDs
7.8. Port numbers
7.9. Protocol Complexity
8. Tracing samba system calls
9. NT Domain RPC's
9.1. Introduction
9.1.1. Sources
9.1.2. Credits
9.2. Notes and Structures
9.2.1. Notes
9.2.2. Enumerations
9.2.3. Structures
9.3. MSRPC over Transact Named Pipe
9.3.1. MSRPC Pipes
9.3.2. Header
9.3.3. Tail
9.3.4. RPC Bind / Bind Ack
9.3.5. NTLSA Transact Named Pipe
9.3.6. LSA Open Policy
9.3.7. LSA Query Info Policy
9.3.8. LSA Enumerate Trusted Domains
9.3.9. LSA Open Secret
9.3.10. LSA Close
9.3.11. LSA Lookup SIDS
9.3.12. LSA Lookup Names
9.4. NETLOGON rpc Transact Named Pipe
9.4.1. LSA Request Challenge
9.4.2. LSA Authenticate 2
9.4.3. LSA Server Password Set
9.4.4. LSA SAM Logon
9.4.5. LSA SAM Logoff
9.5. \\MAILSLOT\NET\NTLOGON
9.5.1. Query for PDC
9.5.2. SAM Logon
9.6. SRVSVC Transact Named Pipe
9.6.1. Net Share Enum
9.6.2. Net Server Get Info
9.7. Cryptographic side of NT Domain Authentication
9.7.1. Definitions
9.7.2. Protocol
9.7.3. Comments
9.8. SIDs and RIDs
9.8.1. Well-known SIDs
9.8.2. Well-known RIDS
10. Samba Printing Internals
10.1. Abstract
10.2. Printing Interface to Various Back ends
10.3. Print Queue TDB's
10.4. ChangeID and Client Caching of Printer Information
10.5. Windows NT/2K Printer Change Notify
11. Samba WINS Internals
11.1. WINS Failover
12. The Upcoming SAM System
12.1. Security in the 'new SAM'
12.2. Standalone from UNIX
12.3. Handles and Races in the new SAM
12.4. Layers
12.4.1. Application
12.4.2. SAM Interface
12.4.3. SAM Modules
12.5. SAM Modules
12.5.1. Special Module: sam_passdb
12.5.2. sam_ads
12.6. Memory Management
12.7. Testing
13. LanMan and NT Password Encryption
13.1. Introduction
13.2. How does it work?
13.3. >The smbpasswd file
14. Modules
14.1. Advantages
14.2. Loading modules
14.2.1. Static modules
14.2.2. Shared modules
14.3. Writing modules
14.3.1. Static/Shared selection in configure.in
15. RPC Pluggable Modules
15.1. About
15.2. General Overview
16. Notes to packagers
16.1. Versioning
16.2. Modules

Chapter 1. Definition of NetBIOS Protocol and Name Resolution Modes

1.1. NETBIOS

NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX. +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt +

Table of Contents

1. Definition of NetBIOS Protocol and Name Resolution Modes
NETBIOS
BROADCAST NetBIOS
NBNS NetBIOS
2. Samba Architecture
Introduction
Multithreading and Samba
Threading smbd
Threading nmbd
nbmd Design
3. The samba DEBUG system
New Output Syntax
The DEBUG() Macro
The DEBUGADD() Macro
The DEBUGLVL() Macro
New Functions
dbgtext()
dbghdr()
format_debug_text()
4. Coding Suggestions
5. Samba Internals
Character Handling
The new functions
Macros in byteorder.h
CVAL(buf,pos)
PVAL(buf,pos)
SCVAL(buf,pos,val)
SVAL(buf,pos)
IVAL(buf,pos)
SVALS(buf,pos)
IVALS(buf,pos)
SSVAL(buf,pos,val)
SIVAL(buf,pos,val)
SSVALS(buf,pos,val)
SIVALS(buf,pos,val)
RSVAL(buf,pos)
RIVAL(buf,pos)
RSSVAL(buf,pos,val)
RSIVAL(buf,pos,val)
LAN Manager Samba API
Parameters
Return value
Code character table
6. The smb.conf file
Lexical Analysis
Handling of Whitespace
Handling of Line Continuation
Line Continuation Quirks
Syntax
About params.c
7. NetBIOS in a Unix World
Introduction
Usernames
File Ownership
Passwords
Locking
Deny Modes
Trapdoor UIDs
Port numbers
Protocol Complexity
8. Tracing samba system calls
9. NT Domain RPC's
Introduction
Sources
Credits
Notes and Structures
Notes
Enumerations
Structures
MSRPC over Transact Named Pipe
MSRPC Pipes
Header
Tail
RPC Bind / Bind Ack
NTLSA Transact Named Pipe
LSA Open Policy
LSA Query Info Policy
LSA Enumerate Trusted Domains
LSA Open Secret
LSA Close
LSA Lookup SIDS
LSA Lookup Names
NETLOGON rpc Transact Named Pipe
LSA Request Challenge
LSA Authenticate 2
LSA Server Password Set
LSA SAM Logon
LSA SAM Logoff
\\MAILSLOT\NET\NTLOGON
Query for PDC
SAM Logon
SRVSVC Transact Named Pipe
Net Share Enum
Net Server Get Info
Cryptographic side of NT Domain Authentication
Definitions
Protocol
Comments
SIDs and RIDs
Well-known SIDs
Well-known RIDS
10. Samba Printing Internals
Abstract
+Printing Interface to Various Back ends +
+Print Queue TDB's +
+ChangeID and Client Caching of Printer Information +
+Windows NT/2K Printer Change Notify +
11. Samba WINS Internals
WINS Failover
12. The Upcoming SAM System
Security in the 'new SAM'
Standalone from UNIX
Handles and Races in the new SAM
Layers
Application
SAM Interface
SAM Modules
SAM Modules
Special Module: sam_passdb
sam_ads
Memory Management
Testing
13. LanMan and NT Password Encryption
Introduction
How does it work?
The smbpasswd file
14. Modules
Advantages
Loading modules
Static modules
Shared modules
Writing modules
Static/Shared selection in configure.in
15. RPC Pluggable Modules
About
General Overview
16. Notes to packagers
Versioning
Modules

Chapter1.Definition of NetBIOS Protocol and Name Resolution Modes

Luke Leighton

12 June 1997

Table of Contents

NETBIOS
BROADCAST NetBIOS
NBNS NetBIOS

NETBIOS

+NetBIOS runs over the following tranports: TCP/IP; NetBEUI and IPX/SPX. Samba only uses NetBIOS over TCP/IP. For details on the TCP/IP NetBIOS Session Service NetBIOS Datagram Service, and NetBIOS Names, see -rfc1001.txt and rfc1002.txt.

+rfc1001.txt and rfc1002.txt. +

NetBEUI is a raw NetBIOS frame protocol implementation that allows NetBIOS datagrams to be sent out over the 'wire' embedded within LLC frames. NetBEUI is not required when using NetBIOS over TCP/IP protocols and it -is preferable NOT to install NetBEUI if it can be avoided.

+is preferable NOT to install NetBEUI if it can be avoided. +

IPX/SPX is also not required when using NetBIOS over TCP/IP, and it is preferable NOT to install the IPX/SPX transport unless you are using Novell servers. At the very least, it is recommended that you do not install -'NetBIOS over IPX/SPX'.

[When installing Windows 95, you will find that NetBEUI and IPX/SPX are +'NetBIOS over IPX/SPX'. +

+[When installing Windows 95, you will find that NetBEUI and IPX/SPX are installed as the default protocols. This is because they are the simplest -to manage: no Windows 95 user-configuration is required].

+to manage: no Windows 95 user-configuration is required]. +

NetBIOS applications (such as samba) offer their services (for example, SMB file and print sharing) on a NetBIOS name. They must claim this name on the network before doing so. The NetBIOS session service will then accept connections on the application's behalf (on the NetBIOS name claimed by the application). A NetBIOS session between the application -and the client can then commence.

+and the client can then commence. +

NetBIOS names consist of 15 characters plus a 'type' character. This is similar, in concept, to an IP address and a TCP port number, respectively. A NetBIOS-aware application on a host will offer different services under different NetBIOS name types, just as a host will offer different TCP/IP -services on different port numbers.

+services on different port numbers. +

NetBIOS names must be claimed on a network, and must be defended. The use of NetBIOS names is most suitable on a single subnet; a Local Area Network -or a Wide Area Network.

+or a Wide Area Network. +

NetBIOS names are either UNIQUE or GROUP. Only one application can claim a -UNIQUE NetBIOS name on a network.

There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point.

1.2. BROADCAST NetBIOS

+UNIQUE NetBIOS name on a network. +

+There are two kinds of NetBIOS Name resolution: Broadcast and Point-to-Point. +

BROADCAST NetBIOS

Clients can claim names, and therefore offer services on successfully claimed names, on their broadcast-isolated subnet. One way to get NetBIOS services (such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and SMB file/print sharing: see cifs4.txt) working on a LAN or WAN is to make -your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139.

+your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139. +

This, however, is not recommended. If you have a large LAN or WAN, you will find that some of your hosts spend 95 percent of their time dealing with broadcast traffic. [If you have IPX/SPX on your LAN or WAN, you will find that this is already happening: a packet analyzer will show, roughly -every twelve minutes, great swathes of broadcast traffic!].

1.3. NBNS NetBIOS

rfc1001.txt describes, amongst other things, the implementation and use +every twelve minutes, great swathes of broadcast traffic!]. +

NBNS NetBIOS

+rfc1001.txt describes, amongst other things, the implementation and use of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service' which is fully rfc1001/2 compliant, but has had to take specific action with certain NetBIOS names in order to make it useful. (for example, it -deals with the registration of <1c> <1d> <1e> names all in different ways. +deals with the registration of <1c> <1d> <1e> names all in different ways. I recommend the reading of the Microsoft WINS Server Help files for full -details).

+details). +

The use of a WINS server cuts down on broadcast network traffic for NetBIOS name resolution. It has the effect of pulling all the broadcast isolated subnets together into a single NetBIOS scope, across your LAN -or WAN, while avoiding the use of TCP/IP broadcast packets.

When you have a WINS server on your LAN, WINS clients will be able to +or WAN, while avoiding the use of TCP/IP broadcast packets. +

+When you have a WINS server on your LAN, WINS clients will be able to contact the WINS server to resolve NetBIOS names. Note that only those WINS clients that have registered with the same WINS server will be visible. The WINS server _can_ have static NetBIOS entries added to its database (usually for security reasons you might want to consider putting your domain controllers or other important servers as static entries, but you should not rely on this as your sole means of security), but for -the most part, NetBIOS names are registered dynamically.

This provides some confusion for lots of people, and is worth mentioning +the most part, NetBIOS names are registered dynamically. +

+This provides some confusion for lots of people, and is worth mentioning here: a Browse Server is NOT a WINS Server, even if these services are implemented in the same application. A Browse Server _needs_ a WINS server -because a Browse Server is a WINS client, which is _not_ the same thing].

Clients can claim names, and therefore offer services on successfully claimed +because a Browse Server is a WINS client, which is _not_ the same thing]. +

+Clients can claim names, and therefore offer services on successfully claimed names, on their broadcast-isolated subnet. One way to get NetBIOS services (such as browsing: see ftp.microsoft.com/drg/developr/CIFS/browdiff.txt; and SMB file/print sharing: see cifs6.txt) working on a LAN or WAN is to make your routers forward all broadcast packets from TCP/IP ports 137, 138 and 139. You will find, however, if you do this on a large LAN or a WAN, that your network is completely swamped by NetBIOS and browsing packets, which is why -WINS was developed to minimise the necessity of broadcast traffic.

+WINS was developed to minimise the necessity of broadcast traffic. +

WINS Clients therefore claim names from the WINS server. If the WINS server allows them to register a name, the client's NetBIOS session service can then offer services on this name. Other WINS clients will then -contact the WINS server to resolve a NetBIOS name.

Chapter 2. Samba Architecture

2.1. Introduction

This document gives a general overview of how Samba works +contact the WINS server to resolve a NetBIOS name. +

Chapter2.Samba Architecture

Dan Shearer

November 1997

Table of Contents

Introduction
Multithreading and Samba
Threading smbd
Threading nmbd
nbmd Design

Introduction

+This document gives a general overview of how Samba works internally. The Samba Team has tried to come up with a model which is the best possible compromise between elegance, portability, security and the constraints imposed by the very messy SMB and CIFS -protocol.

It also tries to answer some of the frequently asked questions such as:

  1. Is Samba secure when running on Unix? The xyz platform? - What about the root priveliges issue?

  2. Pros and cons of multithreading in various parts of Samba

  3. Why not have a separate process for name resolution, WINS, and browsing?

2.2. Multithreading and Samba

People sometimes tout threads as a uniformly good thing. They are very +protocol. +

+It also tries to answer some of the frequently asked questions such as: +

  1. + Is Samba secure when running on Unix? The xyz platform? + What about the root priveliges issue? +

  2. Pros and cons of multithreading in various parts of Samba

  3. Why not have a separate process for name resolution, WINS, and browsing?

Multithreading and Samba

+People sometimes tout threads as a uniformly good thing. They are very nice in their place but are quite inappropriate for smbd. nmbd is -another matter, and multi-threading it would be very nice.

The short version is that smbd is not multithreaded, and alternative +another matter, and multi-threading it would be very nice. +

+The short version is that smbd is not multithreaded, and alternative servers that take this approach under Unix (such as Syntax, at the time of writing) suffer tremendous performance penalties and are less robust. nmbd is not threaded either, but this is because it is not possible to do it while keeping code consistent and portable across 35 -or more platforms. (This drawback also applies to threading smbd.)

The longer versions is that there are very good reasons for not making +or more platforms. (This drawback also applies to threading smbd.) +

+The longer versions is that there are very good reasons for not making smbd multi-threaded. Multi-threading would actually make Samba much slower, less scalable, less portable and much less robust. The fact that we use a separate process for each connection is one of Samba's -biggest advantages.

2.3. Threading smbd

A few problems that would arise from a threaded smbd are:

  1. It's not only to create threads instead of processes, but you +biggest advantages. +

Threading smbd

+A few problems that would arise from a threaded smbd are: +

  1. + It's not only to create threads instead of processes, but you must care about all variables if they have to be thread specific - (currently they would be global).

  2. if one thread dies (eg. a seg fault) then all threads die. We can - immediately throw robustness out the window.

  3. many of the system calls we make are blocking. Non-blocking + (currently they would be global). +

  4. + if one thread dies (eg. a seg fault) then all threads die. We can + immediately throw robustness out the window. +

  5. + many of the system calls we make are blocking. Non-blocking equivalents of many calls are either not available or are awkward (and slow) to use. So while we block in one thread all clients are waiting. Imagine if one share is a slow NFS filesystem and the others - are fast, we will end up slowing all clients to the speed of NFS.

  6. you can't run as a different uid in different threads. This means + are fast, we will end up slowing all clients to the speed of NFS. +

  7. + you can't run as a different uid in different threads. This means we would have to switch uid/gid on _every_ SMB packet. It would be - horrendously slow.

  8. the per process file descriptor limit would mean that we could only - support a limited number of clients.

  9. we couldn't use the system locking calls as the locking context of - fcntl() is a process, not a thread.

2.4. Threading nmbd

This would be ideal, but gets sunk by portability requirements.

Andrew tried to write a test threads library for nmbd that used only + horrendously slow. +

  • + the per process file descriptor limit would mean that we could only + support a limited number of clients. +

  • + we couldn't use the system locking calls as the locking context of + fcntl() is a process, not a thread. +

    • Threading nmbd

    +This would be ideal, but gets sunk by portability requirements. +

    +Andrew tried to write a test threads library for nmbd that used only ansi-C constructs (using setjmp and longjmp). Unfortunately some OSes defeat this by restricting longjmp to calling addresses that are shallower than the current address on the stack (apparently AIX does @@ -1180,31 +180,22 @@ and without threads, and as the real aim of threads is to make the code clearer we would not have gained anything. (it is a myth that threads make things faster. threading is like recursion, it can make things clear but the same thing can always be done faster by some -other method)

    Chris tried to spec out a general design that would abstract threading +other method) +

    +Chris tried to spec out a general design that would abstract threading vs separate processes (vs other methods?) and make them accessible through some general API. This doesn't work because of the data sharing requirements of the protocol (packets in the future depending on packets now, etc.) At least, the code would work but would be very -clumsy, and besides the fork() type model would never work on Unix. (Is there an OS that it would work on, for nmbd?)

    A fork() is cheap, but not nearly cheap enough to do on every UDP +clumsy, and besides the fork() type model would never work on Unix. (Is there an OS that it would work on, for nmbd?) +

    +A fork() is cheap, but not nearly cheap enough to do on every UDP packet that arrives. Having a pool of processes is possible but is nasty to program cleanly due to the enormous amount of shared data (in complex structures) between the processes. We can't rely on each -platform having a shared memory system.

    2.5. nbmd Design

    Originally Andrew used recursion to simulate a multi-threaded +platform having a shared memory system. +

    nbmd Design

    +Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really confusing debugging sessions. Luke Leighton rewrote it to use a queuing system that keeps state information on each packet. The @@ -1216,361 +207,197 @@ and a pointer to a user-defined memory block. This suddenly made things much simpler: large numbers of functions could be made static, and modularised. This is the same principle as used in NT's kernel, and achieves the same effect as threads, but in -a single process.

    Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the +a single process. +

    +Then Jeremy rewrote nmbd. The packet data in nmbd isn't what's on the wire. It's a nice format that is very amenable to processing but still -keeps the idea of a distinct packet. See "struct packet_struct" in +keeps the idea of a distinct packet. See "struct packet_struct" in nameserv.h. It has all the detail but none of the on-the-wire mess. This makes it ideal for using in disk or memory-based databases -for browsing and WINS support.

    Chapter 3. The samba DEBUG system

    3.1. New Output Syntax

    The syntax of a debugging log file is represented as:

      >debugfile< :== { >debugmsg< }
+for browsing and WINS support. 
+

    Chapter3.The samba DEBUG system

    Chris Hertel

    July 1998

    Table of Contents

    New Output Syntax
    The DEBUG() Macro
    The DEBUGADD() Macro
    The DEBUGLVL() Macro
    New Functions
    dbgtext()
    dbghdr()
    format_debug_text()

    New Output Syntax

    + The syntax of a debugging log file is represented as: +

    +  >debugfile< :== { >debugmsg< }
 
-  >debugmsg<  :== >debughdr< '\n' >debugtext<
+  >debugmsg<  :== >debughdr< '\n' >debugtext<
 
-  >debughdr<  :== '[' TIME ',' LEVEL ']' FILE ':' [FUNCTION] '(' LINE ')'
+  >debughdr<  :== '[' TIME ',' LEVEL ']' FILE ':' [FUNCTION] '(' LINE ')'
 
-  >debugtext< :== { >debugline< }
+  >debugtext< :== { >debugline< }
 
-  >debugline< :== TEXT '\n'

    TEXT is a string of characters excluding the newline character.

    LEVEL is the DEBUG level of the message (an integer in the range - 0..10).

    TIME is a timestamp.

    FILE is the name of the file from which the debug message was -generated.

    FUNCTION is the function from which the debug message was generated.

    LINE is the line number of the debug statement that generated the -message.

    Basically, what that all means is:

    1. A debugging log file is made up of debug messages.

    2. Each debug message is made up of a header and text. The header is -separated from the text by a newline.

    3. The header begins with the timestamp and debug level of the + >debugline< :== TEXT '\n' +

      +TEXT is a string of characters excluding the newline character. +

      +LEVEL is the DEBUG level of the message (an integer in the range + 0..10). +

      +TIME is a timestamp. +

      +FILE is the name of the file from which the debug message was +generated. +

      +FUNCTION is the function from which the debug message was generated. +

      +LINE is the line number of the debug statement that generated the +message. +

      Basically, what that all means is:

      1. +A debugging log file is made up of debug messages. +

      2. +Each debug message is made up of a header and text. The header is +separated from the text by a newline. +

      3. +The header begins with the timestamp and debug level of the message enclosed in brackets. The filename, function, and line number at which the message was generated follow. The filename is terminated by a colon, and the function name is terminated by the parenthesis which contain the line number. Depending upon the compiler, the function name may be missing (it is generated by the -__FUNCTION__ macro, which is not universally implemented, dangit).

      4. The message text is made up of zero or more lines, each terminated -by a newline.

      Here's some example output:

          [1998/08/03 12:55:25, 1] nmbd.c:(659)
+__FUNCTION__ macro, which is not universally implemented, dangit).
+

    4. +The message text is made up of zero or more lines, each terminated +by a newline. +

    Here's some example output:

    +    [1998/08/03 12:55:25, 1] nmbd.c:(659)
       Netbios nameserver version 1.9.19-prealpha started.
       Copyright Andrew Tridgell 1994-1997
     [1998/08/03 12:55:25, 3] loadparm.c:(763)
-      Initializing global parameters

    Note that in the above example the function names are not listed on + Initializing global parameters +

    +Note that in the above example the function names are not listed on the header line. That's because the example above was generated on an -SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro.

    3.2. The DEBUG() Macro

    Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters. +SGI Indy, and the SGI compiler doesn't support the __FUNCTION__ macro. +

    The DEBUG() Macro

    +Use of the DEBUG() macro is unchanged. DEBUG() takes two parameters. The first is the message level, the second is the body of a function -call to the Debug1() function.

    That's confusing.

    Here's an example which may help a bit. If you would write

    printf( "This is a %s message.\n", "debug" );

    to send the output to stdout, then you would write

    DEBUG( 0, ( "This is a %s message.\n", "debug" ) );

    to send the output to the debug file. All of the normal printf() -formatting escapes work.

    Note that in the above example the DEBUG message level is set to 0. +call to the Debug1() function. +

    That's confusing.

    Here's an example which may help a bit. If you would write

    +printf( "This is a %s message.\n", "debug" );
+

    +to send the output to stdout, then you would write +

    +DEBUG( 0, ( "This is a %s message.\n", "debug" ) );
+

    +to send the output to the debug file. All of the normal printf() +formatting escapes work. +

    +Note that in the above example the DEBUG message level is set to 0. Messages at level 0 always print. Basically, if the message level is less than or equal to the global value DEBUGLEVEL, then the DEBUG -statement is processed.

    The output of the above example would be something like:

        [1998/07/30 16:00:51, 0] file.c:function(128)
-      This is a debug message.

    Each call to DEBUG() creates a new header *unless* the output produced +statement is processed. +

    +The output of the above example would be something like: +

    +    [1998/07/30 16:00:51, 0] file.c:function(128)
+      This is a debug message.
+

    +Each call to DEBUG() creates a new header *unless* the output produced by the previous call to DEBUG() did not end with a '\n'. Output to the debug file is passed through a formatting buffer which is flushed every time a newline is encountered. If the buffer is not empty when -DEBUG() is called, the new input is simply appended.

    ...but that's really just a Kludge. It was put in place because +DEBUG() is called, the new input is simply appended. +

    +...but that's really just a Kludge. It was put in place because DEBUG() has been used to write partial lines. Here's a simple (dumb) -example of the kind of thing I'm talking about:

        DEBUG( 0, ("The test returned " ) );
+example of the kind of thing I'm talking about:
+
    +    DEBUG( 0, ("The test returned " ) );
     if( test() )
-      DEBUG(0, ("True") );
+      DEBUG(0, ("True") );
     else
-      DEBUG(0, ("False") );
-    DEBUG(0, (".\n") );
    Without the format buffer, the output (assuming test() returned true)
-would look like this:
        [1998/07/30 16:00:51, 0] file.c:function(256)
+      DEBUG(0, ("False") );
+    DEBUG(0, (".\n") );
+
    
+Without the format buffer, the output (assuming test() returned true)
+would look like this:
+
    +    [1998/07/30 16:00:51, 0] file.c:function(256)
       The test returned
     [1998/07/30 16:00:51, 0] file.c:function(258)
       True
     [1998/07/30 16:00:51, 0] file.c:function(261)
-      .
    Which isn't much use. The format buffer kludge fixes this problem.

    3.3. The DEBUGADD() Macro

    In addition to the kludgey solution to the broken line problem + . +

    Which isn't much use. The format buffer kludge fixes this problem. +

    The DEBUGADD() Macro

    +In addition to the kludgey solution to the broken line problem described above, there is a clean solution. The DEBUGADD() macro never generates a header. It will append new text to the current debug message even if the format buffer is empty. The syntax of the -DEBUGADD() macro is the same as that of the DEBUG() macro.

        DEBUG( 0, ("This is the first line.\n" ) );
-    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );

    Produces

        [1998/07/30 16:00:51, 0] file.c:function(512)
+DEBUGADD() macro is the same as that of the DEBUG() macro.
+
    +    DEBUG( 0, ("This is the first line.\n" ) );
+    DEBUGADD( 0, ("This is the second line.\nThis is the third line.\n" ) );
+
    Produces
    +    [1998/07/30 16:00:51, 0] file.c:function(512)
       This is the first line.
       This is the second line.
-      This is the third line.

    3.4. The DEBUGLVL() Macro

    One of the problems with the DEBUG() macro was that DEBUG() lines + This is the third line. +

    The DEBUGLVL() Macro

    +One of the problems with the DEBUG() macro was that DEBUG() lines tended to get a bit long. Consider this example from -nmbd_sendannounce.c:

      DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
-            type, global_myname, subrec->subnet_name, work->work_group));

    One solution to this is to break it down using DEBUG() and DEBUGADD(), -as follows:

      DEBUG( 3, ( "send_local_master_announcement: " ) );
-  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
-  DEBUGADD( 3, ( "on subnet %s ", subrec->subnet_name ) );
-  DEBUGADD( 3, ( "for workgroup %s\n", work->work_group ) );

    A similar, but arguably nicer approach is to use the DEBUGLVL() macro. +nmbd_sendannounce.c: +

    +  DEBUG(3,("send_local_master_announcement: type %x for name %s on subnet %s for workgroup %s\n",
+            type, global_myname, subrec->subnet_name, work->work_group));
+

    +One solution to this is to break it down using DEBUG() and DEBUGADD(), +as follows: +

    +  DEBUG( 3, ( "send_local_master_announcement: " ) );
+  DEBUGADD( 3, ( "type %x for name %s ", type, global_myname ) );
+  DEBUGADD( 3, ( "on subnet %s ", subrec->subnet_name ) );
+  DEBUGADD( 3, ( "for workgroup %s\n", work->work_group ) );
+

    +A similar, but arguably nicer approach is to use the DEBUGLVL() macro. This macro returns True if the message level is less than or equal to -the global DEBUGLEVEL value, so:

      if( DEBUGLVL( 3 ) )
+the global DEBUGLEVEL value, so:
+
    +  if( DEBUGLVL( 3 ) )
     {
-    dbgtext( "send_local_master_announcement: " );
-    dbgtext( "type %x for name %s ", type, global_myname );
-    dbgtext( "on subnet %s ", subrec->subnet_name );
-    dbgtext( "for workgroup %s\n", work->work_group );
-    }
    (The dbgtext() function is explained below.)
    There are a few advantages to this scheme:
    1. The test is performed only once.
    2. You can allocate variables off of the stack that will only be used
-within the DEBUGLVL() block.
    3. Processing that is only relevant to debug output can be contained
-within the DEBUGLVL() block.

    3.5. New Functions

    3.5.1. dbgtext()

    This function prints debug message text to the debug file (and + dbgtext( "send_local_master_announcement: " ); + dbgtext( "type %x for name %s ", type, global_myname ); + dbgtext( "on subnet %s ", subrec->subnet_name ); + dbgtext( "for workgroup %s\n", work->work_group ); + } +

    (The dbgtext() function is explained below.)

    There are a few advantages to this scheme:

    1. +The test is performed only once. +

    2. +You can allocate variables off of the stack that will only be used +within the DEBUGLVL() block. +

    3. +Processing that is only relevant to debug output can be contained +within the DEBUGLVL() block. +

    New Functions

    dbgtext()

    +This function prints debug message text to the debug file (and possibly to syslog) via the format buffer. The function uses a variable argument list just like printf() or Debug1(). The input is printed into a buffer using the vslprintf() function, and then passed to format_debug_text(). If you use DEBUGLVL() you will probably print the body of the -message using dbgtext().

    3.5.2. dbghdr()

    This is the function that writes a debug message header. +message using dbgtext(). +

    dbghdr()

    +This is the function that writes a debug message header. Headers are not processed via the format buffer. Also note that if the format buffer is not empty, a call to dbghdr() will not -produce any output. See the comments in dbghdr() for more info.

    It is not likely that this function will be called directly. It -is used by DEBUG() and DEBUGADD().

    3.5.3. format_debug_text()

    This is a static function in debug.c. It stores the output text +produce any output. See the comments in dbghdr() for more info. +

    +It is not likely that this function will be called directly. It +is used by DEBUG() and DEBUGADD(). +

    format_debug_text()

    +This is a static function in debug.c. It stores the output text for the body of the message in a buffer until it encounters a newline. When the newline character is found, the buffer is written to the debug file via the Debug1() function, and the buffer is reset. This allows us to add the indentation at the beginning of each line of the message body, and also ensures that the output is written a line at a time (which cleans up -syslog output).

    Chapter 4. Coding Suggestions

    So you want to add code to Samba ...

    One of the daunting tasks facing a programmer attempting to write code for +syslog output). +

    Chapter4.Coding Suggestions

    Steve French

    Simo Sorce

    Andrew Bartlett

    Tim Potter

    Martin Pool

    +So you want to add code to Samba ... +

    +One of the daunting tasks facing a programmer attempting to write code for Samba is understanding the various coding conventions used by those most active in the project. These conventions were mostly unwritten and helped improve either the portability, stability or consistency of the code. This @@ -1578,305 +405,181 @@ document will attempt to document a few of the more important coding practices used at this time on the Samba project. The coding practices are expected to change slightly over time, and even to grow as more is learned about obscure portability considerations. Two existing documents -samba/source/internals.doc and -samba/source/architecture.doc provide -additional information.

    The loosely related question of coding style is very personal and this +samba/source/internals.doc and +samba/source/architecture.doc provide +additional information. +

    +The loosely related question of coding style is very personal and this document does not attempt to address that subject, except to say that I have observed that eight character tabs seem to be preferred in Samba source. If you are interested in the topic of coding style, two oft-quoted -documents are:

    http://lxr.linux.no/source/Documentation/CodingStyle

    http://www.fsf.org/prep/standards_toc.html

    But note that coding style in Samba varies due to the many different -programmers who have contributed.

    Following are some considerations you should use when adding new code to -Samba. First and foremost remember that:

    Portability is a primary consideration in adding function, as is network +documents are: +

    +http://lxr.linux.no/source/Documentation/CodingStyle +

    +http://www.fsf.org/prep/standards_toc.html +

    +But note that coding style in Samba varies due to the many different +programmers who have contributed. +

    +Following are some considerations you should use when adding new code to +Samba. First and foremost remember that: +

    +Portability is a primary consideration in adding function, as is network compatability with de facto, existing, real world CIFS/SMB implementations. There are lots of platforms that Samba builds on so use caution when adding a call to a library function that is not invoked in existing Samba code. Also note that there are many quite different SMB/CIFS clients that Samba tries to support, not all of which follow the SNIA CIFS Technical Reference (or the earlier Microsoft reference documents or the X/Open book on the SMB -Standard) perfectly.

    Here are some other suggestions:

    1. use d_printf instead of printf for display text - reason: enable auto-substitution of translated language text

    2. use SAFE_FREE instead of free - reason: reduce traps due to null pointers

    3. don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros - reason: not POSIX

    4. don't use strcpy and strlen (use safe_* equivalents) - reason: to avoid traps due to buffer overruns

    5. don't use getopt_long, use popt functions instead - reason: portability

    6. explicitly add const qualifiers on parm passing in functions where parm - is input only (somewhat controversial but const can be #defined away)

    7. when passing a va_list as an arg, or assigning one to another +Standard) perfectly. +

      +Here are some other suggestions: +

      1. + use d_printf instead of printf for display text + reason: enable auto-substitution of translated language text +

      2. + use SAFE_FREE instead of free + reason: reduce traps due to null pointers +

      3. + don't use bzero use memset, or ZERO_STRUCT and ZERO_STRUCTP macros + reason: not POSIX +

      4. + don't use strcpy and strlen (use safe_* equivalents) + reason: to avoid traps due to buffer overruns +

      5. + don't use getopt_long, use popt functions instead + reason: portability +

      6. + explicitly add const qualifiers on parm passing in functions where parm + is input only (somewhat controversial but const can be #defined away) +

      7. + when passing a va_list as an arg, or assigning one to another please use the VA_COPY() macro reason: on some platforms, va_list is a struct that must be - initialized in each function...can SEGV if you don't.

      8. discourage use of threads - reason: portability (also see architecture.doc)

      9. don't explicitly include new header files in C files - new h files + initialized in each function...can SEGV if you don't. +

      10. + discourage use of threads + reason: portability (also see architecture.doc) +

      11. + don't explicitly include new header files in C files - new h files should be included by adding them once to includes.h - reason: consistency

      12. don't explicitly extern functions (they are autogenerated by - "make proto" into proto.h) - reason: consistency

      13. use endian safe macros when unpacking SMBs (see byteorder.h and + reason: consistency +

      14. + don't explicitly extern functions (they are autogenerated by + "make proto" into proto.h) + reason: consistency +

      15. + use endian safe macros when unpacking SMBs (see byteorder.h and internals.doc) - reason: not everyone uses Intel

      16. Note Unicode implications of charset handling (see internals.doc). See + reason: not everyone uses Intel +

      17. + Note Unicode implications of charset handling (see internals.doc). See pull_* and push_* and convert_string functions. - reason: Internationalization

      18. Don't assume English only - reason: See above

      19. Try to avoid using in/out parameters (functions that return data which + reason: Internationalization +

      20. + Don't assume English only + reason: See above +

      21. + Try to avoid using in/out parameters (functions that return data which overwrites input parameters) - reason: Can cause stability problems

      22. Ensure copyright notices are correct, don't append Tridge's name to code + reason: Can cause stability problems +

      23. + Ensure copyright notices are correct, don't append Tridge's name to code that he didn't write. If you did not write the code, make sure that it - can coexist with the rest of the Samba GPLed code.

      24. Consider usage of DATA_BLOBs for length specified byte-data. - reason: stability

      25. Take advantage of tdbs for database like function - reason: consistency

      26. Don't access the SAM_ACCOUNT structure directly, they should be accessed + can coexist with the rest of the Samba GPLed code. +

      27. + Consider usage of DATA_BLOBs for length specified byte-data. + reason: stability +

      28. + Take advantage of tdbs for database like function + reason: consistency +

      29. + Don't access the SAM_ACCOUNT structure directly, they should be accessed via pdb_get...() and pdb_set...() functions. - reason: stability, consistency

      30. Don't check a password directly against the passdb, always use the + reason: stability, consistency +

      31. + Don't check a password directly against the passdb, always use the check_password() interface. - reason: long term pluggability

      32. Try to use asprintf rather than pstrings and fstrings where possible

      33. Use normal C comments / * instead of C++ comments // like + reason: long term pluggability +

      34. + Try to use asprintf rather than pstrings and fstrings where possible +

      35. + Use normal C comments / * instead of C++ comments // like this. Although the C++ comment format is part of the C99 - standard, some older vendor C compilers do not accept it.

      36. Try to write documentation for API functions and structures + standard, some older vendor C compilers do not accept it. +

      37. + Try to write documentation for API functions and structures explaining the point of the code, the way it should be used, and any special conditions or results. Mark these with a double-star comment start / ** so that they can be picked up by Doxygen, as in - this file.

      38. Keep the scope narrow. This means making functions/variables + this file. +

      39. + Keep the scope narrow. This means making functions/variables static whenever possible. We don't want our namespace polluted. Each module should have a minimal number of externally - visible functions or variables.

      40. Use function pointers to keep knowledge about particular pieces of + visible functions or variables. +

      41. + Use function pointers to keep knowledge about particular pieces of code isolated in one place. We don't want a particular piece of functionality to be spread out across lots of places - that makes for fragile, hand to maintain code. Instead, design an interface and use tables containing function pointers to implement specific functionality. This is particularly important for command - interpreters.

      42. Think carefully about what it will be like for someone else to add + interpreters. +

      43. + Think carefully about what it will be like for someone else to add to and maintain your code. If it would be hard for someone else to - maintain then do it another way.

      The suggestions above are simply that, suggestions, but the information may + maintain then do it another way. +

    +The suggestions above are simply that, suggestions, but the information may help in reducing the routine rework done on new code. The preceeding list is expected to change routinely as new support routines and macros are -added.

    Chapter 5. Samba Internals

    5.1. Character Handling

    This section describes character set handling in Samba, as implemented in -Samba 3.0 and above

    In the past Samba had very ad-hoc character set handling. Scattered +added. +

    Chapter5.Samba Internals

    8 May 1996

    Table of Contents

    Character Handling
    The new functions
    Macros in byteorder.h
    CVAL(buf,pos)
    PVAL(buf,pos)
    SCVAL(buf,pos,val)
    SVAL(buf,pos)
    IVAL(buf,pos)
    SVALS(buf,pos)
    IVALS(buf,pos)
    SSVAL(buf,pos,val)
    SIVAL(buf,pos,val)
    SSVALS(buf,pos,val)
    SIVALS(buf,pos,val)
    RSVAL(buf,pos)
    RIVAL(buf,pos)
    RSSVAL(buf,pos,val)
    RSIVAL(buf,pos,val)
    LAN Manager Samba API
    Parameters
    Return value
    Code character table

    Character Handling

    +This section describes character set handling in Samba, as implemented in +Samba 3.0 and above +

    +In the past Samba had very ad-hoc character set handling. Scattered throughout the code were numerous calls which converted particular strings to/from DOS codepages. The problem is that there was no way of telling if a particular char* is in dos codepage or unix codepage. This led to a nightmare of code that tried to cope with -particular cases without handlingt the general case.

    5.2. The new functions

    The new system works like this:

    1. all char* strings inside Samba are "unix" strings. These are - multi-byte strings that are in the charset defined by the "unix - charset" option in smb.conf.

    2. there is no single fixed character set for unix strings, but any +particular cases without handlingt the general case. +

    The new functions

    +The new system works like this: +

    1. + all char* strings inside Samba are "unix" strings. These are + multi-byte strings that are in the charset defined by the "unix + charset" option in smb.conf. +

    2. + there is no single fixed character set for unix strings, but any character set that is used does need the following properties: -

      1. must not contain NULLs except for termination -

      2. must be 7-bit compatible with C strings, so that a constant +

        1. + must not contain NULLs except for termination +

        2. + must be 7-bit compatible with C strings, so that a constant string or character in C will be byte-for-byte identical to the equivalent string in the chosen character set. -

        3. when you uppercase or lowercase a string it does not become +

        4. + when you uppercase or lowercase a string it does not become longer than the original string -

        5. must be able to correctly hold all characters that your client +

        6. + must be able to correctly hold all characters that your client will throw at it -

        For example, UTF-8 is fine, and most multi-byte asian character sets +

    + For example, UTF-8 is fine, and most multi-byte asian character sets are fine, but UCS2 could not be used for unix strings as they contain nulls. -

  • when you need to put a string into a buffer that will be sent on the +

  • + when you need to put a string into a buffer that will be sent on the wire, or you need a string in a character set format that is compatible with the clients character set then you need to use a pull_ or push_ function. The pull_ functions pull a string from a wire buffer into a (multi-byte) unix string. The push_ functions - push a string out to a wire buffer.

  • the two main pull_ and push_ functions you need to understand are + push a string out to a wire buffer. +

  • + the two main pull_ and push_ functions you need to understand are pull_string and push_string. These functions take a base pointer that should point at the start of the SMB packet that the string is in. The functions will check the flags field in this packet to @@ -1886,953 +589,426 @@ TYPE="a" STR_ASCII flags. For use in smbd/ and libsmb/ there are wrapper functions clistr_ and srvstr_ that call the pull_/push_ functions with the appropriate first argument. -

    You may also call the pull_ascii/pull_ucs2 or push_ascii/push_ucs2 +

    + You may also call the pull_ascii/pull_ucs2 or push_ascii/push_ucs2 functions if you know that a particular string is ascii or unicode. There are also a number of other convenience functions in charcnv.c that call the pull_/push_ functions with particularly common arguments, such as pull_ascii_pstring() -

  • The biggest thing to remember is that internal (unix) strings in Samba +

  • + The biggest thing to remember is that internal (unix) strings in Samba may now contain multi-byte characters. This means you cannot assume that characters are always 1 byte long. Often this means that you will have to convert strings to ucs2 and back again in order to do some (seemingly) simple task. For examples of how to do this see functions like strchr_m(). I know this is very slow, and we will eventually - speed it up but right now we want this stuff correct not fast.

  • all lp_ functions now return unix strings. The magic "DOS" flag on - parameters is gone.

  • all vfs functions take unix strings. Don't convert when passing to them

    • 5.3. Macros in byteorder.h

    This section describes the macros defined in byteorder.h. These macros -are used extensively in the Samba code.

    5.3.1. CVAL(buf,pos)

    returns the byte at offset pos within buffer buf as an unsigned character.

    5.3.2. PVAL(buf,pos)

    returns the value of CVAL(buf,pos) cast to type unsigned integer.

    5.3.3. SCVAL(buf,pos,val)

    sets the byte at offset pos within buffer buf to value val.

    5.3.4. SVAL(buf,pos)

    returns the value of the unsigned short (16 bit) little-endian integer at + speed it up but right now we want this stuff correct not fast. +

  • + all lp_ functions now return unix strings. The magic "DOS" flag on + parameters is gone. +

  • + all vfs functions take unix strings. Don't convert when passing to them +

    • Macros in byteorder.h

    +This section describes the macros defined in byteorder.h. These macros +are used extensively in the Samba code. +

    CVAL(buf,pos)

    +returns the byte at offset pos within buffer buf as an unsigned character. +

    PVAL(buf,pos)

    returns the value of CVAL(buf,pos) cast to type unsigned integer.

    SCVAL(buf,pos,val)

    sets the byte at offset pos within buffer buf to value val.

    SVAL(buf,pos)

    + returns the value of the unsigned short (16 bit) little-endian integer at offset pos within buffer buf. An integer of this type is sometimes - refered to as "USHORT".

    5.3.5. IVAL(buf,pos)

    returns the value of the unsigned 32 bit little-endian integer at offset -pos within buffer buf.

    5.3.6. SVALS(buf,pos)

    returns the value of the signed short (16 bit) little-endian integer at -offset pos within buffer buf.

    5.3.7. IVALS(buf,pos)

    returns the value of the signed 32 bit little-endian integer at offset pos -within buffer buf.

    5.3.8. SSVAL(buf,pos,val)

    sets the unsigned short (16 bit) little-endian integer at offset pos within -buffer buf to value val.

    5.3.9. SIVAL(buf,pos,val)

    sets the unsigned 32 bit little-endian integer at offset pos within buffer -buf to the value val.

    5.3.10. SSVALS(buf,pos,val)

    sets the short (16 bit) signed little-endian integer at offset pos within -buffer buf to the value val.

    5.3.11. SIVALS(buf,pos,val)

    sets the signed 32 bit little-endian integer at offset pos withing buffer -buf to the value val.

    5.3.12. RSVAL(buf,pos)

    returns the value of the unsigned short (16 bit) big-endian integer at -offset pos within buffer buf.

    5.3.13. RIVAL(buf,pos)

    returns the value of the unsigned 32 bit big-endian integer at offset -pos within buffer buf.

    5.3.14. RSSVAL(buf,pos,val)

    sets the value of the unsigned short (16 bit) big-endian integer at + refered to as "USHORT". +

    IVAL(buf,pos)

    returns the value of the unsigned 32 bit little-endian integer at offset +pos within buffer buf.

    SVALS(buf,pos)

    returns the value of the signed short (16 bit) little-endian integer at +offset pos within buffer buf.

    IVALS(buf,pos)

    returns the value of the signed 32 bit little-endian integer at offset pos +within buffer buf.

    SSVAL(buf,pos,val)

    sets the unsigned short (16 bit) little-endian integer at offset pos within +buffer buf to value val.

    SIVAL(buf,pos,val)

    sets the unsigned 32 bit little-endian integer at offset pos within buffer +buf to the value val.

    SSVALS(buf,pos,val)

    sets the short (16 bit) signed little-endian integer at offset pos within +buffer buf to the value val.

    SIVALS(buf,pos,val)

    sets the signed 32 bit little-endian integer at offset pos withing buffer +buf to the value val.

    RSVAL(buf,pos)

    returns the value of the unsigned short (16 bit) big-endian integer at +offset pos within buffer buf.

    RIVAL(buf,pos)

    returns the value of the unsigned 32 bit big-endian integer at offset +pos within buffer buf.

    RSSVAL(buf,pos,val)

    sets the value of the unsigned short (16 bit) big-endian integer at offset pos within buffer buf to value val. -refered to as "USHORT".

    5.3.15. RSIVAL(buf,pos,val)

    sets the value of the unsigned 32 bit big-endian integer at offset -pos within buffer buf to value val.

    5.4. LAN Manager Samba API

    This section describes the functions need to make a LAN Manager RPC call. +refered to as "USHORT".

    RSIVAL(buf,pos,val)

    sets the value of the unsigned 32 bit big-endian integer at offset +pos within buffer buf to value val.

    LAN Manager Samba API

    +This section describes the functions need to make a LAN Manager RPC call. This information had been obtained by examining the Samba code and the LAN Manager 2.0 API documentation. It should not be considered entirely -reliable.

    call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt, 
-	char *param, char *data, char **rparam, char **rdata);

    This function is defined in client.c. It uses an SMB transaction to call a -remote api.

    5.4.1. Parameters

    The parameters are as follows:

    1. prcnt: the number of bytes of parameters begin sent.

    2. drcnt: the number of bytes of data begin sent.

    3. mprcnt: the maximum number of bytes of parameters which should be returned

    4. mdrcnt: the maximum number of bytes of data which should be returned

    5. param: a pointer to the parameters to be sent.

    6. data: a pointer to the data to be sent.

    7. rparam: a pointer to a pointer which will be set to point to the returned - paramters. The caller of call_api() must deallocate this memory.

    8. rdata: a pointer to a pointer which will be set to point to the returned - data. The caller of call_api() must deallocate this memory.

    These are the parameters which you ought to send, in the order of their -appearance in the parameter block:

    1. An unsigned 16 bit integer API number. You should set this value with -SSVAL(). I do not know where these numbers are described.

    2. An ASCIIZ string describing the parameters to the API function as defined +reliable. +

      +

      +call_api(int prcnt, int drcnt, int mprcnt, int mdrcnt, 
+	char *param, char *data, char **rparam, char **rdata);
+

      +

      +This function is defined in client.c. It uses an SMB transaction to call a +remote api. +

      Parameters

      The parameters are as follows:

      1. + prcnt: the number of bytes of parameters begin sent. +

      2. + drcnt: the number of bytes of data begin sent. +

      3. + mprcnt: the maximum number of bytes of parameters which should be returned +

      4. + mdrcnt: the maximum number of bytes of data which should be returned +

      5. + param: a pointer to the parameters to be sent. +

      6. + data: a pointer to the data to be sent. +

      7. + rparam: a pointer to a pointer which will be set to point to the returned + paramters. The caller of call_api() must deallocate this memory. +

      8. + rdata: a pointer to a pointer which will be set to point to the returned + data. The caller of call_api() must deallocate this memory. +

      +These are the parameters which you ought to send, in the order of their +appearance in the parameter block: +

      1. +An unsigned 16 bit integer API number. You should set this value with +SSVAL(). I do not know where these numbers are described. +

      2. +An ASCIIZ string describing the parameters to the API function as defined in the LAN Manager documentation. The first parameter, which is the server name, is ommited. This string is based uppon the API function as described -in the manual, not the data which is actually passed.

      3. An ASCIIZ string describing the data structure which ought to be returned.

      4. Any parameters which appear in the function call, as defined in the LAN -Manager API documentation, after the "Server" and up to and including the -"uLevel" parameters.

      5. An unsigned 16 bit integer which gives the size in bytes of the buffer we +in the manual, not the data which is actually passed. +

      6. +An ASCIIZ string describing the data structure which ought to be returned. +

      7. +Any parameters which appear in the function call, as defined in the LAN +Manager API documentation, after the "Server" and up to and including the +"uLevel" parameters. +

      8. +An unsigned 16 bit integer which gives the size in bytes of the buffer we will use to receive the returned array of data structures. Presumably this -should be the same as mdrcnt. This value should be set with SSVAL().

      9. An ASCIIZ string describing substructures which should be returned. If no -substructures apply, this string is of zero length.

      The code in client.c always calls call_api() with no data. It is unclear -when a non-zero length data buffer would be sent.

      5.4.2. Return value

      The returned parameters (pointed to by rparam), in their order of appearance -are:

      1. An unsigned 16 bit integer which contains the API function's return code. -This value should be read with SVAL().

      2. An adjustment which tells the amount by which pointers in the returned +should be the same as mdrcnt. This value should be set with SSVAL(). +

      3. +An ASCIIZ string describing substructures which should be returned. If no +substructures apply, this string is of zero length. +

      +The code in client.c always calls call_api() with no data. It is unclear +when a non-zero length data buffer would be sent. +

      Return value

      +The returned parameters (pointed to by rparam), in their order of appearance +are:

      1. +An unsigned 16 bit integer which contains the API function's return code. +This value should be read with SVAL(). +

      2. +An adjustment which tells the amount by which pointers in the returned data should be adjusted. This value should be read with SVAL(). Basically, the address of the start of the returned data buffer should have the returned pointer value added to it and then have this value subtracted from it in -order to obtain the currect offset into the returned data buffer.

      3. A count of the number of elements in the array of structures returned. -It is also possible that this may sometimes be the number of bytes returned.

      When call_api() returns, rparam points to the returned parameters. The +order to obtain the currect offset into the returned data buffer. +

    3. +A count of the number of elements in the array of structures returned. +It is also possible that this may sometimes be the number of bytes returned. +

    +When call_api() returns, rparam points to the returned parameters. The first if these is the result code. It will be zero if the API call -suceeded. This value by be read with "SVAL(rparam,0)".

    The second parameter may be read as "SVAL(rparam,2)". It is a 16 bit offset +suceeded. This value by be read with "SVAL(rparam,0)". +

    +The second parameter may be read as "SVAL(rparam,2)". It is a 16 bit offset which indicates what the base address of the returned data buffer was when it was built on the server. It should be used to correct pointer before -use.

    The returned data buffer contains the array of returned data structures. +use. +

    +The returned data buffer contains the array of returned data structures. Note that all pointers must be adjusted before use. The function -fix_char_ptr() in client.c can be used for this purpose.

    The third parameter (which may be read as "SVAL(rparam,4)") has something to +fix_char_ptr() in client.c can be used for this purpose. +

    +The third parameter (which may be read as "SVAL(rparam,4)") has something to do with indicating the amount of data returned or possibly the amount of -data which can be returned if enough buffer space is allowed.

    5.5. Code character table

    Certain data structures are described by means of ASCIIz strings containing -code characters. These are the code characters:

    1. W a type byte little-endian unsigned integer

    2. N a count of substructures which follow

    3. D a four byte little-endian unsigned integer

    4. B a byte (with optional count expressed as trailing ASCII digits)

    5. z a four byte offset to a NULL terminated string

    6. l a four byte offset to non-string user data

    7. b an offset to data (with count expressed as trailing ASCII digits)

    8. r pointer to returned data buffer???

    9. L length in bytes of returned data buffer???

    10. h number of bytes of information available???

    Chapter 6. The smb.conf file

    6.1. Lexical Analysis

    Basically, the file is processed on a line by line basis. There are +data which can be returned if enough buffer space is allowed. +

    Code character table

    +Certain data structures are described by means of ASCIIz strings containing +code characters. These are the code characters: +

    1. +W a type byte little-endian unsigned integer +

    2. +N a count of substructures which follow +

    3. +D a four byte little-endian unsigned integer +

    4. +B a byte (with optional count expressed as trailing ASCII digits) +

    5. +z a four byte offset to a NULL terminated string +

    6. +l a four byte offset to non-string user data +

    7. +b an offset to data (with count expressed as trailing ASCII digits) +

    8. +r pointer to returned data buffer??? +

    9. +L length in bytes of returned data buffer??? +

    10. +h number of bytes of information available??? +

    Chapter6.The smb.conf file

    Chris Hertel

    November 1997

    Table of Contents

    Lexical Analysis
    Handling of Whitespace
    Handling of Line Continuation
    Line Continuation Quirks
    Syntax
    About params.c

    Lexical Analysis

    +Basically, the file is processed on a line by line basis. There are four types of lines that are recognized by the lexical analyzer -(params.c):

    1. Blank lines - Lines containing only whitespace.

    2. Comment lines - Lines beginning with either a semi-colon or a -pound sign (';' or '#').

    3. Section header lines - Lines beginning with an open square bracket ('[').

    4. Parameter lines - Lines beginning with any other character. -(The default line type.)

    The first two are handled exclusively by the lexical analyzer, which -ignores them. The latter two line types are scanned for

    1. - Section names

    2. - Parameter names

    3. - Parameter values

    These are the only tokens passed to the parameter loader +(params.c): +

    1. +Blank lines - Lines containing only whitespace. +

    2. +Comment lines - Lines beginning with either a semi-colon or a +pound sign (';' or '#'). +

    3. +Section header lines - Lines beginning with an open square bracket ('['). +

    4. +Parameter lines - Lines beginning with any other character. +(The default line type.) +

    +The first two are handled exclusively by the lexical analyzer, which +ignores them. The latter two line types are scanned for +

    1. + - Section names +

    2. + - Parameter names +

    3. + - Parameter values +

    +These are the only tokens passed to the parameter loader (loadparm.c). Parameter names and values are divided from one -another by an equal sign: '='.

    6.1.1. Handling of Whitespace

    Whitespace is defined as all characters recognized by the isspace() +another by an equal sign: '='. +

    Handling of Whitespace

    +Whitespace is defined as all characters recognized by the isspace() function (see ctype(3C)) except for the newline character ('\n') -The newline is excluded because it identifies the end of the line.

    1. The lexical analyzer scans past white space at the beginning of a line.

    2. Section and parameter names may contain internal white space. All -whitespace within a name is compressed to a single space character.

    3. Internal whitespace within a parameter value is kept verbatim with +The newline is excluded because it identifies the end of the line. +

      1. +The lexical analyzer scans past white space at the beginning of a line. +

      2. +Section and parameter names may contain internal white space. All +whitespace within a name is compressed to a single space character. +

      3. +Internal whitespace within a parameter value is kept verbatim with the exception of carriage return characters ('\r'), all of which -are removed.

      4. Leading and trailing whitespace is removed from names and values.

      6.1.2. Handling of Line Continuation

      Long section header and parameter lines may be extended across +are removed. +

    4. +Leading and trailing whitespace is removed from names and values. +

    Handling of Line Continuation

    +Long section header and parameter lines may be extended across multiple lines by use of the backslash character ('\\'). Line -continuation is ignored for blank and comment lines.

    If the last (non-whitespace) character within a section header or on +continuation is ignored for blank and comment lines. +

    +If the last (non-whitespace) character within a section header or on a parameter line is a backslash, then the next line will be (logically) concatonated with the current line by the lexical -analyzer. For example:

    	param name = parameter value string \
-	with line continuation.

    Would be read as

        param name = parameter value string     with line continuation.

    Note that there are five spaces following the word 'string', +analyzer. For example: +

    +	param name = parameter value string \
+	with line continuation.
+

    Would be read as

    +    param name = parameter value string     with line continuation.
+

    +Note that there are five spaces following the word 'string', representing the one space between 'string' and '\\' in the top line, plus the four preceeding the word 'with' in the second line. -(Yes, I'm counting the indentation.)

    Line continuation characters are ignored on blank lines and at the end +(Yes, I'm counting the indentation.) +

    +Line continuation characters are ignored on blank lines and at the end of comments. They are *only* recognized within section and parameter -lines.

    6.1.3. Line Continuation Quirks

    Note the following example:

    	param name = parameter value string \
+lines.
+

    Line Continuation Quirks

    Note the following example:

    +	param name = parameter value string \
     \
-    with line continuation.

    The middle line is *not* parsed as a blank line because it is first -concatonated with the top line. The result is

    param name = parameter value string         with line continuation.

    The same is true for comment lines.

    	param name = parameter value string \
+    with line continuation.
+

    +The middle line is *not* parsed as a blank line because it is first +concatonated with the top line. The result is +

    +param name = parameter value string         with line continuation.
+

    The same is true for comment lines.

    +	param name = parameter value string \
 	; comment \
-    with a comment.

    This becomes:

    param name = parameter value string     ; comment     with a comment.

    On a section header line, the closing bracket (']') is considered a -terminating character, and the rest of the line is ignored. The lines

    	[ section   name ] garbage \
-    param  name  = value

    are read as

    	[section name]
-    param name = value

    6.2. Syntax

    The syntax of the smb.conf file is as follows:

      <file>            :==  { <section> } EOF
-  <section>         :==  <section header> { <parameter line> }
-  <section header>  :==  '[' NAME ']'
-  <parameter line>  :==  NAME '=' VALUE NL

    Basically, this means that

    1. a file is made up of zero or more sections, and is terminated by - an EOF (we knew that).

    2. A section is made up of a section header followed by zero or more - parameter lines.

    3. A section header is identified by an opening bracket and + with a comment. +

      This becomes:

      +param name = parameter value string     ; comment     with a comment.
+

      +On a section header line, the closing bracket (']') is considered a +terminating character, and the rest of the line is ignored. The lines +

      +	[ section   name ] garbage \
+    param  name  = value
+

      are read as

      +	[section name]
+    param name = value
+

    Syntax

    The syntax of the smb.conf file is as follows:

    +  <file>            :==  { <section> } EOF
+  <section>         :==  <section header> { <parameter line> }
+  <section header>  :==  '[' NAME ']'
+  <parameter line>  :==  NAME '=' VALUE NL
+

    Basically, this means that

    1. + a file is made up of zero or more sections, and is terminated by + an EOF (we knew that). +

    2. + A section is made up of a section header followed by zero or more + parameter lines. +

    3. + A section header is identified by an opening bracket and terminated by the closing bracket. The enclosed NAME identifies - the section.

    4. A parameter line is divided into a NAME and a VALUE. The *first* + the section. +

    5. + A parameter line is divided into a NAME and a VALUE. The *first* equal sign on the line separates the NAME from the VALUE. The - VALUE is terminated by a newline character (NL = '\n').

    6.2.1. About params.c

    The parsing of the config file is a bit unusual if you are used to + VALUE is terminated by a newline character (NL = '\n'). +

    About params.c

    +The parsing of the config file is a bit unusual if you are used to lex, yacc, bison, etc. Both lexical analysis (scanning) and parsing are performed by params.c. Values are loaded via callbacks to -loadparm.c.

    Chapter 7. NetBIOS in a Unix World

    7.1. Introduction

    This is a short document that describes some of the issues that +loadparm.c. +

    Chapter7.NetBIOS in a Unix World

    Andrew Tridgell

    April 1995

    Table of Contents

    Introduction
    Usernames
    File Ownership
    Passwords
    Locking
    Deny Modes
    Trapdoor UIDs
    Port numbers
    Protocol Complexity

    Introduction

    +This is a short document that describes some of the issues that confront a SMB implementation on unix, and how Samba copes with -them. They may help people who are looking at unix<->PC -interoperability.

    It was written to help out a person who was writing a paper on unix to -PC connectivity.

    7.2. Usernames

    The SMB protocol has only a loose username concept. Early SMB +them. They may help people who are looking at unix<->PC +interoperability. +

    +It was written to help out a person who was writing a paper on unix to +PC connectivity. +

    Usernames

    +The SMB protocol has only a loose username concept. Early SMB protocols (such as CORE and COREPLUS) have no username concept at all. Even in later protocols clients often attempt operations (particularly printer operations) without first validating a username -on the server.

    Unix security is based around username/password pairs. A unix box +on the server. +

    +Unix security is based around username/password pairs. A unix box should not allow clients to do any substantive operation without some -sort of validation.

    The problem mostly manifests itself when the unix server is in "share -level" security mode. This is the default mode as the alternative -"user level" security mode usually forces a client to connect to the +sort of validation. +

    +The problem mostly manifests itself when the unix server is in "share +level" security mode. This is the default mode as the alternative +"user level" security mode usually forces a client to connect to the server as the same user for each connected share, which is -inconvenient in many sites.

    In "share level" security the client normally gives a username in the -"session setup" protocol, but does not supply an accompanying -password. The client then connects to resources using the "tree -connect" protocol, and supplies a password. The problem is that the +inconvenient in many sites. +

    +In "share level" security the client normally gives a username in the +"session setup" protocol, but does not supply an accompanying +password. The client then connects to resources using the "tree +connect" protocol, and supplies a password. The problem is that the user on the PC types the username and the password in different contexts, unaware that they need to go together to give access to the server. The username is normally the one the user typed in when they -"logged onto" the PC (this assumes Windows for Workgroups). The -password is the one they chose when connecting to the disk or printer.

    The user often chooses a totally different username for their login as +"logged onto" the PC (this assumes Windows for Workgroups). The +password is the one they chose when connecting to the disk or printer. +

    +The user often chooses a totally different username for their login as for the drive connection. Often they also want to access different drives as different usernames. The unix server needs some way of -divining the correct username to combine with each password.

    Samba tries to avoid this problem using several methods. These succeed +divining the correct username to combine with each password. +

    +Samba tries to avoid this problem using several methods. These succeed in the vast majority of cases. The methods include username maps, the service%user syntax, the saving of session setup usernames for later validation and the derivation of the username from the service name -(either directly or via the user= option).

    7.3. File Ownership

    The commonly used SMB protocols have no way of saying "you can't do -that because you don't own the file". They have, in fact, no concept -of file ownership at all.

    This brings up all sorts of interesting problems. For example, when +(either directly or via the user= option). +

    File Ownership

    +The commonly used SMB protocols have no way of saying "you can't do +that because you don't own the file". They have, in fact, no concept +of file ownership at all. +

    +This brings up all sorts of interesting problems. For example, when you copy a file to a unix drive, and the file is world writeable but owned by another user the file will transfer correctly but will receive the wrong date. This is because the utime() call under unix only succeeds for the owner of the file, or root, even if the file is world writeable. For security reasons Samba does all file operations as the validated user, not root, so the utime() fails. This can stuff -up shared development diectories as programs like "make" will not get -file time comparisons right.

    There are several possible solutions to this problem, including +up shared development diectories as programs like "make" will not get +file time comparisons right. +

    +There are several possible solutions to this problem, including username mapping, and forcing a specific username for particular -shares.

    7.4. Passwords

    Many SMB clients uppercase passwords before sending them. I have no +shares. +

    Passwords

    +Many SMB clients uppercase passwords before sending them. I have no idea why they do this. Interestingly WfWg uppercases the password only if the server is running a protocol greater than COREPLUS, so -obviously it isn't just the data entry routines that are to blame.

    Unix passwords are case sensitive. So if users use mixed case -passwords they are in trouble.

    Samba can try to cope with this by either using the "password level" +obviously it isn't just the data entry routines that are to blame. +

    +Unix passwords are case sensitive. So if users use mixed case +passwords they are in trouble. +

    +Samba can try to cope with this by either using the "password level" option which causes Samba to try the offered password with up to the -specified number of case changes, or by using the "password server" +specified number of case changes, or by using the "password server" option which allows Samba to do its validation via another machine -(typically a WinNT server).

    Samba supports the password encryption method used by SMB +(typically a WinNT server). +

    +Samba supports the password encryption method used by SMB clients. Note that the use of password encryption in Microsoft -networking leads to password hashes that are "plain text equivalent". +networking leads to password hashes that are "plain text equivalent". This means that it is *VERY* important to ensure that the Samba smbpasswd file containing these password hashes is only readable by the root user. See the documentation ENCRYPTION.txt for more -details.

    7.5. Locking

    Since samba 2.2, samba supports other types of locking as well. This -section is outdated.

    The locking calls available under a DOS/Windows environment are much +details. +

    Locking

    +Since samba 2.2, samba supports other types of locking as well. This +section is outdated. +

    +The locking calls available under a DOS/Windows environment are much richer than those available in unix. This means a unix server (like Samba) choosing to use the standard fcntl() based unix locking calls -to implement SMB locking has to improvise a bit.

    One major problem is that dos locks can be in a 32 bit (unsigned) +to implement SMB locking has to improvise a bit. +

    +One major problem is that dos locks can be in a 32 bit (unsigned) range. Unix locking calls are 32 bits, but are signed, giving only a 31 bit range. Unfortunately OLE2 clients use the top bit to select a -locking range used for OLE semaphores.

    To work around this problem Samba compresses the 32 bit range into 31 +locking range used for OLE semaphores. +

    +To work around this problem Samba compresses the 32 bit range into 31 bits by appropriate bit shifting. This seems to work but is not ideal. In a future version a separate SMB lockd may be added to cope -with the problem.

    It also doesn't help that many unix lockd daemons are very buggy and +with the problem. +

    +It also doesn't help that many unix lockd daemons are very buggy and crash at the slightest provocation. They normally go mostly unused in a unix environment because few unix programs use byte range locking. The stress of huge numbers of lock requests from dos/windows -clients can kill the daemon on some systems.

    The second major problem is the "opportunistic locking" requested by +clients can kill the daemon on some systems. +

    +The second major problem is the "opportunistic locking" requested by some clients. If a client requests opportunistic locking then it is asking the server to notify it if anyone else tries to do something on the same file, at which time the client will say if it is willing to give up its lock. Unix has no simple way of implementing -opportunistic locking, and currently Samba has no support for it.

    7.6. Deny Modes

    When a SMB client opens a file it asks for a particular "deny mode" to +opportunistic locking, and currently Samba has no support for it. +

    Deny Modes

    +When a SMB client opens a file it asks for a particular "deny mode" to be placed on the file. These modes (DENY_NONE, DENY_READ, DENY_WRITE, DENY_ALL, DENY_FCB and DENY_DOS) specify what actions should be allowed by anyone else who tries to use the file at the same time. If DENY_READ is placed on the file, for example, then any attempt to open -the file for reading should fail.

    Unix has no equivalent notion. To implement this Samba uses either lock +the file for reading should fail. +

    +Unix has no equivalent notion. To implement this Samba uses either lock files based on the files inode and placed in a separate lock directory or a shared memory implementation. The lock file method is clumsy and consumes processing and file resources, the shared memory implementation is vastly prefered and is turned on -by default for those systems that support it.

    7.7. Trapdoor UIDs

    A SMB session can run with several uids on the one socket. This +by default for those systems that support it. +

    Trapdoor UIDs

    +A SMB session can run with several uids on the one socket. This happens when a user connects to two shares with different usernames. To cope with this the unix server needs to switch uids within the one process. On some unixes (such as SCO) this is not possible. This means that on those unixes the client is restricted to -a single uid.

    Note that you can also get the "trapdoor uid" message for other -reasons. Please see the FAQ for details.

    7.8. Port numbers

    There is a convention that clients on sockets use high "unprivilaged" -port numbers (>1000) and connect to servers on low "privilaged" port +a single uid. +

    +Note that you can also get the "trapdoor uid" message for other +reasons. Please see the FAQ for details. +

    Port numbers

    +There is a convention that clients on sockets use high "unprivilaged" +port numbers (>1000) and connect to servers on low "privilaged" port numbers. This is enforced in Unix as non-root users can't open a -socket for listening on port numbers less than 1000.

    Most PC based SMB clients (such as WfWg and WinNT) don't follow this +socket for listening on port numbers less than 1000. +

    +Most PC based SMB clients (such as WfWg and WinNT) don't follow this convention completely. The main culprit is the netbios nameserving on udp port 137. Name query requests come from a source port of 137. This is a problem when you combine it with the common firewalling technique of not allowing incoming packets on low port numbers. This means that these clients can't query a netbios nameserver on the other side of a -low port based firewall.

    The problem is more severe with netbios node status queries. I've +low port based firewall. +

    +The problem is more severe with netbios node status queries. I've found that WfWg, Win95 and WinNT3.5 all respond to netbios node status queries on port 137 no matter what the source port was in the request. This works between machines that are both using port 137, but @@ -2840,421 +1016,179 @@ it means it's not possible for a unix user to do a node status request to any of these OSes unless they are running as root. The answer comes back, but it goes to port 137 which the unix user can't listen on. Interestingly WinNT3.1 got this right - it sends node status -responses back to the source port in the request.

    7.9. Protocol Complexity

    There are many "protocol levels" in the SMB protocol. It seems that +responses back to the source port in the request. +

    Protocol Complexity

    +There are many "protocol levels" in the SMB protocol. It seems that each time new functionality was added to a Microsoft operating system, they added the equivalent functions in a new protocol level of the SMB -protocol to "externalise" the new capabilities.

    This means the protocol is very "rich", offering many ways of doing +protocol to "externalise" the new capabilities. +

    +This means the protocol is very "rich", offering many ways of doing each file operation. This means SMB servers need to be complex and large. It also means it is very difficult to make them bug free. It is not just Samba that suffers from this problem, other servers such as WinNT don't support every variation of every call and it has almost certainly been a headache for MS developers to support the myriad of -SMB calls that are available.

    There are about 65 "top level" operations in the SMB protocol (things +SMB calls that are available. +

    +There are about 65 "top level" operations in the SMB protocol (things like SMBread and SMBwrite). Some of these include hundreds of sub-functions (SMBtrans has at least 120 sub-functions, like DosPrintQAdd and NetSessionEnum). All of them take several options that can change the way they work. Many take dozens of possible -"information levels" that change the structures that need to be -returned. Samba supports all but 2 of the "top level" functions. It +"information levels" that change the structures that need to be +returned. Samba supports all but 2 of the "top level" functions. It supports only 8 (so far) of the SMBtrans sub-functions. Even NT -doesn't support them all.

    Samba currently supports up to the "NT LM 0.12" protocol, which is the +doesn't support them all. +

    +Samba currently supports up to the "NT LM 0.12" protocol, which is the one preferred by Win95 and WinNT3.5. Luckily this protocol level has a -"capabilities" field which specifies which super-duper new-fangled +"capabilities" field which specifies which super-duper new-fangled options the server suports. This helps to make the implementation of -this protocol level much easier.

    There is also a problem with the SMB specications. SMB is a X/Open +this protocol level much easier. +

    +There is also a problem with the SMB specications. SMB is a X/Open spec, but the X/Open book is far from ideal, and fails to cover many important issues, leaving much to the imagination. Microsoft recently renamed the SMB protocol CIFS (Common Internet File System) and have published new specifications. These are far superior to the old X/Open documents but there are still undocumented calls and features. This specification is actively being worked on by a CIFS developers -mailing list hosted by Microsft.

    Chapter 8. Tracing samba system calls

    This file describes how to do a system call trace on Samba to work out +mailing list hosted by Microsft. +

    Chapter8.Tracing samba system calls

    Andrew Tridgell

    Samba Team

    +This file describes how to do a system call trace on Samba to work out what its doing wrong. This is not for the faint of heart, but if you -are reading this then you are probably desperate.

    Actually its not as bad as the the above makes it sound, just don't -expect the output to be very pretty :-)

    Ok, down to business. One of the big advantages of unix systems is +are reading this then you are probably desperate. +

    +Actually its not as bad as the the above makes it sound, just don't +expect the output to be very pretty :-) +

    +Ok, down to business. One of the big advantages of unix systems is that they nearly all come with a system trace utility that allows you to monitor all system calls that a program is making. This is extremely using for debugging and also helps when trying to work out why something is slower than you expect. You can use system tracing -without any special compilation options.

    The system trace utility is called different things on different +without any special compilation options. +

    +The system trace utility is called different things on different systems. On Linux systems its called strace. Under SunOS 4 its called trace. Under SVR4 style systems (including solaris) its called -truss. Under many BSD systems its called ktrace.

    The first thing you should do is read the man page for your native +truss. Under many BSD systems its called ktrace. +

    +The first thing you should do is read the man page for your native system call tracer. In the discussion below I'll assume its called strace as strace is the only portable system tracer (its available for free for many unix types) and its also got some of the nicest -features.

    Next, try using strace on some simple commands. For example, strace -ls or strace echo hello.

    +features. +

    +Next, try using strace on some simple commands. For example, strace +ls or strace echo hello. +

    You'll notice that it produces a LOT of output. It is showing you the arguments to every system call that the program makes and the result. Very little happens in a program without a system call so you get lots of output. You'll also find that it produces a lot of -"preamble" stuff showing the loading of shared libraries etc. Ignore -this (unless its going wrong!)

    For example, the only line that really matters in the strace echo -hello output is:

    write(1, "hello\n", 6)                  = 6

    all the rest is just setting up to run the program.

    Ok, now you're familiar with strace. To use it on Samba you need to +"preamble" stuff showing the loading of shared libraries etc. Ignore +this (unless its going wrong!) +

    +For example, the only line that really matters in the strace echo +hello output is: +

    +write(1, "hello\n", 6)                  = 6
+

    all the rest is just setting up to run the program.

    +Ok, now you're familiar with strace. To use it on Samba you need to strace the running smbd daemon. The way I tend ot use it is to first login from my Windows PC to the Samba server, then use smbstatus to find which process ID that client is attached to, then as root I do -strace -p PID to attach to that process. I normally redirect the +strace -p PID to attach to that process. I normally redirect the stderr output from this command to a file for later perusal. For -example, if I'm using a csh style shell:

    strace -f -p 3872 >& strace.out

    or with a sh style shell:

    strace -f -p 3872 > strace.out 2>&1

    Note the "-f" option. This is only available on some systems, and +example, if I'm using a csh style shell: +

    strace -f -p 3872 >& strace.out

    or with a sh style shell:

    strace -f -p 3872 > strace.out 2>&1

    +Note the "-f" option. This is only available on some systems, and allows you to trace not just the current process, but any children it forks. This is great for finding printing problems caused by the -"print command" being wrong.

    Once you are attached you then can do whatever it is on the client +"print command" being wrong. +

    +Once you are attached you then can do whatever it is on the client that is causing problems and you will capture all the system calls -that smbd makes.

    So how do you interpret the results? Generally I search through the +that smbd makes. +

    +So how do you interpret the results? Generally I search through the output for strings that I know will appear when the problem happens. For example, if I am having touble with permissions on a file I would search for that files name in the strace output and look at the surrounding lines. Another trick is to match up file descriptor -numbers and "follow" what happens to an open file until it is closed.

    Beyond this you will have to use your initiative. To give you an idea +numbers and "follow" what happens to an open file until it is closed. +

    +Beyond this you will have to use your initiative. To give you an idea of what you are looking for here is a piece of strace output that -shows that /dev/null is not world writeable, which -causes printing to fail with Samba:

    [pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
-[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)

    The process is trying to first open /dev/null read-write -then read-only. Both fail. This means /dev/null has -incorrect permissions.

    Chapter 9. NT Domain RPC's

    9.1. Introduction

    This document contains information to provide an NT workstation with login -services, without the need for an NT server. It is the sgml version of http://mailhost.cb1.com/~lkcl/cifsntdomain.txt, controlled by Luke.

    It should be possible to select a domain instead of a workgroup (in the NT +shows that /dev/null is not world writeable, which +causes printing to fail with Samba: +

    +[pid 28268] open("/dev/null", O_RDWR)   = -1 EACCES (Permission denied)
+[pid 28268] open("/dev/null", O_WRONLY) = -1 EACCES (Permission denied)
+

    +The process is trying to first open /dev/null read-write +then read-only. Both fail. This means /dev/null has +incorrect permissions. +

    Chapter9.NT Domain RPC's

    Luke Leighton

    <lkcl@switchboard.net>

    Duncan Stansfield

    <duncans@sco.com>

    01 November 97(version 0.0.24)

    Table of Contents

    Introduction
    Sources
    Credits
    Notes and Structures
    Notes
    Enumerations
    Structures
    MSRPC over Transact Named Pipe
    MSRPC Pipes
    Header
    Tail
    RPC Bind / Bind Ack
    NTLSA Transact Named Pipe
    LSA Open Policy
    LSA Query Info Policy
    LSA Enumerate Trusted Domains
    LSA Open Secret
    LSA Close
    LSA Lookup SIDS
    LSA Lookup Names
    NETLOGON rpc Transact Named Pipe
    LSA Request Challenge
    LSA Authenticate 2
    LSA Server Password Set
    LSA SAM Logon
    LSA SAM Logoff
    \\MAILSLOT\NET\NTLOGON
    Query for PDC
    SAM Logon
    SRVSVC Transact Named Pipe
    Net Share Enum
    Net Server Get Info
    Cryptographic side of NT Domain Authentication
    Definitions
    Protocol
    Comments
    SIDs and RIDs
    Well-known SIDs
    Well-known RIDS

    Introduction

    +This document contains information to provide an NT workstation with login +services, without the need for an NT server. It is the sgml version of http://mailhost.cb1.com/~lkcl/cifsntdomain.txt, controlled by Luke. +

    +It should be possible to select a domain instead of a workgroup (in the NT workstation's TCP/IP settings) and after the obligatory reboot, type in a username, password, select a domain and successfully log in. I would appreciate any feedback on your experiences with this process, and any -comments, corrections and additions to this document.

    The packets described here can be easily derived from (and are probably +comments, corrections and additions to this document. +

    +The packets described here can be easily derived from (and are probably better understood using) Netmon.exe. You will need to use the version of Netmon that matches your system, in order to correctly decode the NETLOGON, lsarpc and srvsvc Transact pipes. This document is derived from NT Service Pack 1 and its corresponding version of Netmon. It is intended that an annotated packet trace be produced, which will likely be more -instructive than this document.

    Also needed, to fully implement NT Domain Login Services, is the +instructive than this document. +

    +Also needed, to fully implement NT Domain Login Services, is the document describing the cryptographic part of the NT authentication. This document is available from comp.protocols.smb; from the ntsecurity.net -digest and from the samba digest, amongst other sources.

    A copy is available from:

    http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935

    http://mailhost.cb1.com/~lkcl/crypt.html

    A c-code implementation, provided by Linus Nordberg -of this protocol is available from:

    http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html

    http://mailhost.cb1.com/~lkcl/crypt.txt

    Also used to provide debugging information is the Check Build version of +digest and from the samba digest, amongst other sources. +

    +A copy is available from: +

    http://ntbugtraq.rc.on.ca/SCRIPTS/WA.EXE?A2=ind9708;L=ntbugtraq;O=A;P=2935

    http://mailhost.cb1.com/~lkcl/crypt.html

    +A c-code implementation, provided by Linus Nordberg +of this protocol is available from: +

    http://samba.org/cgi-bin/mfs/01/digest/1997/97aug/0391.html

    http://mailhost.cb1.com/~lkcl/crypt.txt

    +Also used to provide debugging information is the Check Build version of NT workstation, and enabling full debugging in NETLOGON. This is -achieved by setting the following REG_SZ registry key to 0x1ffffff:

    HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

    Incorrect direct editing of the registry can cause your +achieved by setting the following REG_SZ registry key to 0x1ffffff: +

    HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

    Incorrect direct editing of the registry can cause your machine to fail. Then again, so can incorrect implementation of this -protocol. See "Liability:" above.

    Bear in mind that each packet over-the-wire will have its origin in an +protocol. See "Liability:" above.

    +Bear in mind that each packet over-the-wire will have its origin in an API call. Therefore, there are likely to be structures, enumerations -and defines that are usefully documented elsewhere.

    This document is by no means complete or authoritative. Missing sections -include, but are not limited to:

    1. Mappings of RIDs to usernames (and vice-versa).

    2. What a User ID is and what a Group ID is.

    3. The exact meaning/definition of various magic constants or enumerations.

    4. The reply error code and use of that error code when a +and defines that are usefully documented elsewhere. +

      +This document is by no means complete or authoritative. Missing sections +include, but are not limited to: +

      1. Mappings of RIDs to usernames (and vice-versa).

      2. What a User ID is and what a Group ID is.

      3. The exact meaning/definition of various magic constants or enumerations.

      4. The reply error code and use of that error code when a workstation becomes a member of a domain (to be described later). Failure to return this error code will make the workstation report -that it is already a member of the domain.

      5. the cryptographic side of the NetrServerPasswordSet command, +that it is already a member of the domain.

      6. the cryptographic side of the NetrServerPasswordSet command, which would allow the workstation to change its password. This password is used to generate the long-term session key. [It is possible to reject this -command, and keep the default workstation password].

      9.1.1. Sources

      cket Traces from Netmonitor (Service Pack 1 and above)
      ul Ashton and Luke Leighton's other "NT Domain" doc.
      FS documentation - cifs6.txt
      FS documentation - cifsrap2.txt

      9.1.2. Credits

      Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.
      Duncan Stansfield: low-level analysis of MSRPC Pipes.
      Linus Nordberg: producing c-code from Paul's crypto spec.
      Windows Sourcer development team

      9.2. Notes and Structures

      9.2.1. Notes

      1. In the SMB Transact pipes, some "Structures", described here, appear to be +command, and keep the default workstation password].

      Sources

      cket Traces from Netmonitor (Service Pack 1 and above)
      ul Ashton and Luke Leighton's other "NT Domain" doc.
      FS documentation - cifs6.txt
      FS documentation - cifsrap2.txt

      Credits

      Paul Ashton: loads of work with Net Monitor; understanding the NT authentication system; reference implementation of the NT domain support on which this document is originally based.
      Duncan Stansfield: low-level analysis of MSRPC Pipes.
      Linus Nordberg: producing c-code from Paul's crypto spec.
      Windows Sourcer development team

      Notes and Structures

      Notes

      1. +In the SMB Transact pipes, some "Structures", described here, appear to be 4-byte aligned with the SMB header, at their start. Exactly which -"Structures" need aligning is not precisely known or documented.

      2. In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be -2-byte aligned with the start of the mailslot, at their start.

      3. Domain SID is of the format S-revision-version-auth1-auth2...authN. -e.g S-1-5-123-456-789-123-456. the 5 could be a sub-revision.

      4. any undocumented buffer pointers must be non-zero if the string buffer it +"Structures" need aligning is not precisely known or documented. +

      5. +In the UDP NTLOGON Mailslots, some "Structures", described here, appear to be +2-byte aligned with the start of the mailslot, at their start. +

      6. +Domain SID is of the format S-revision-version-auth1-auth2...authN. +e.g S-1-5-123-456-789-123-456. the 5 could be a sub-revision. +

      7. +any undocumented buffer pointers must be non-zero if the string buffer it refers to contains characters. exactly what value they should be is unknown. 0x0000 0002 seems to do the trick to indicate that the buffer exists. a NULL buffer pointer indicates that the string buffer is of zero length. @@ -3263,3707 +1197,90 @@ refers to is NOT put into (or taken out of) the SMB data stream. This is empirically derived from, for example, the LSA SAM Logon response packet, where if the buffer pointer is NULL, the user information is not inserted into the data stream. Exactly what happens with an array of buffer pointers -is not known, although an educated guess can be made.

      8. an array of structures (a container) appears to have a count and a pointer. +is not known, although an educated guess can be made. +

      9. +an array of structures (a container) appears to have a count and a pointer. if the count is zero, the pointer is also zero. no further data is put into or taken out of the SMB data stream. if the count is non-zero, then the pointer is also non-zero. immediately following the pointer is the count again, followed by an array of container sub-structures. the count -appears a third time after the last sub-structure.

      9.2.2. Enumerations

      9.2.2.1. MSRPC Header type

      command number in the msrpc packet header

      MSRPC_Request:

      0x00

      MSRPC_Response:

      0x02

      MSRPC_Bind:

      0x0B

      MSRPC_BindAck:

      0x0C

      9.2.2.2. MSRPC Packet info

      The meaning of these flags is undocumented

      FirstFrag:

      0x01

      LastFrag:

      0x02

      NotaFrag:

      0x04

      RecRespond:

      0x08

      NoMultiplex:

      0x10

      NotForIdemp:

      0x20

      NotforBcast:

      0x40

      NoUuid:

      0x80

      9.2.3. Structures

      9.2.3.1. VOID *

      sizeof VOID* is 32 bits.

      9.2.3.2. char

      sizeof char is 8 bits.

      9.2.3.3. UTIME

      UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).

      9.2.3.4. NTTIME

      NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).

      9.2.3.5. DOM_SID (domain SID structure)

      UINT32

      num of sub-authorities in domain SID

      UINT8

      SID revision number

      UINT8

      num of sub-authorities in domain SID

      UINT8[6]

      6 bytes for domain SID - Identifier Authority.

      UINT16[n_subauths]

      domain SID sub-authorities

      Note: the domain SID is documented elsewhere.

      9.2.3.6. STR (string)

      STR (string) is a char[] : a null-terminated string of ascii characters.

      9.2.3.7. UNIHDR (unicode string header)

      UINT16

      length of unicode string

      UINT16

      max length of unicode string

      UINT32

      4 - undocumented.

      9.2.3.8. UNIHDR2 (unicode string header plus buffer pointer)

      UNIHDR

      unicode string header

      VOID*

      undocumented buffer pointer

      9.2.3.9. UNISTR (unicode string)

      UINT16[]

      null-terminated string of unicode characters.

      9.2.3.10. NAME (length-indicated unicode string)

      UINT32

      length of unicode string

      UINT16[]

      null-terminated string of unicode characters.

      9.2.3.11. UNISTR2 (aligned unicode string)

      UINT8[]

      padding to get unicode string 4-byte aligned with the start of the SMB header.

      UINT32

      max length of unicode string

      UINT32

      0 - undocumented

      UINT32

      length of unicode string

      UINT16[]

      string of uncode characters

      9.2.3.12. OBJ_ATTR (object attributes)

      UINT32

      0x18 - length (in bytes) including the length field.

      VOID*

      0 - root directory (pointer)

      VOID*

      0 - object name (pointer)

      UINT32

      0 - attributes (undocumented)

      VOID*

      0 - security descriptior (pointer)

      UINT32

      0 - security quality of service

      9.2.3.14. DOM_SID2 (domain SID structure, SIDS stored in unicode)

      UINT32

      5 - SID type

      UINT32

      0 - undocumented

      UNIHDR2

      domain SID unicode string header

      UNISTR

      domain SID unicode string

      Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.

      Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.

      9.2.3.15. DOM_RID (domain RID structure)

      UINT32

      5 - well-known SID. 1 - user SID (see ShowACLs)

      UINT32

      5 - undocumented

      UINT32

      domain RID

      UINT32

      0 - domain index out of above reference domains

      9.2.3.16. LOG_INFO (server, account, client structure)

      Note: logon server name starts with two '\' characters and is upper case.

      Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.

      VOID*

      undocumented buffer pointer

      UNISTR2

      logon server unicode string

      UNISTR2

      account name unicode string

      UINT16

      sec_chan - security channel type

      UNISTR2

      logon client machine unicode string

      9.2.3.17. CLNT_SRV (server, client names structure)

      Note: logon server name starts with two '\' characters and is upper case.

      VOID*

      undocumented buffer pointer

      UNISTR2

      logon server unicode string

      VOID*

      undocumented buffer pointer

      UNISTR2

      logon client machine unicode string

      9.2.3.18. CREDS (credentials + time stamp)

      char[8]

      credentials

      UTIME

      time stamp

      9.2.3.19. CLNT_INFO2 (server, client structure, client credentials)

      Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to - maintain an authenticated request/response trail.

      CLNT_SRV

      client and server names

      UINT8[]

      ???? padding, for 4-byte alignment with SMB header.

      VOID*

      pointer to client credentials.

      CREDS

      client-calculated credentials + client time

      9.2.3.20. CLNT_INFO (server, account, client structure, client credentials)

      Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.

      LOG_INFO

      logon account info

      CREDS

      client-calculated credentials + client time

      9.2.3.21. ID_INFO_1 (id info structure, auth level 1)

      VOID*

      ptr_id_info_1

      UNIHDR

      domain name unicode header

      UINT32

      param control

      UINT64

      logon ID

      UNIHDR

      user name unicode header

      UNIHDR

      workgroup name unicode header

      char[16]

      arc4 LM OWF Password

      char[16]

      arc4 NT OWF Password

      UNISTR2

      domain name unicode string

      UNISTR2

      user name unicode string

      UNISTR2

      workstation name unicode string

      9.2.3.22. SAM_INFO (sam logon/logoff id info structure)

      Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.

      CLNT_INFO2

      client identification/authentication info

      VOID*

      pointer to return credentials.

      CRED

      return credentials - ignored.

      UINT16

      logon level

      UINT16

      switch value

              switch (switch_value)
+appears a third time after the last sub-structure.
+

    Enumerations

    MSRPC Header type

    command number in the msrpc packet header

    MSRPC_Request:

    0x00

    MSRPC_Response:

    0x02

    MSRPC_Bind:

    0x0B

    MSRPC_BindAck:

    0x0C

    MSRPC Packet info

    The meaning of these flags is undocumented

    FirstFrag:

    0x01

    LastFrag:

    0x02

    NotaFrag:

    0x04

    RecRespond:

    0x08

    NoMultiplex:

    0x10

    NotForIdemp:

    0x20

    NotforBcast:

    0x40

    NoUuid:

    0x80

    Structures

    VOID *

    sizeof VOID* is 32 bits.

    char

    sizeof char is 8 bits.

    UTIME

    UTIME is 32 bits, indicating time in seconds since 01jan1970. documented in cifs6.txt (section 3.5 page, page 30).

    NTTIME

    NTTIME is 64 bits. documented in cifs6.txt (section 3.5 page, page 30).

    DOM_SID (domain SID structure)

    UINT32

    num of sub-authorities in domain SID

    UINT8

    SID revision number

    UINT8

    num of sub-authorities in domain SID

    UINT8[6]

    6 bytes for domain SID - Identifier Authority.

    UINT16[n_subauths]

    domain SID sub-authorities

    Note: the domain SID is documented elsewhere. +

    STR (string)

    STR (string) is a char[] : a null-terminated string of ascii characters.

    UNIHDR (unicode string header)

    UINT16

    length of unicode string

    UINT16

    max length of unicode string

    UINT32

    4 - undocumented.

    UNIHDR2 (unicode string header plus buffer pointer)

    UNIHDR

    unicode string header

    VOID*

    undocumented buffer pointer

    UNISTR (unicode string)

    UINT16[]

    null-terminated string of unicode characters.

    NAME (length-indicated unicode string)

    UINT32

    length of unicode string

    UINT16[]

    null-terminated string of unicode characters.

    UNISTR2 (aligned unicode string)

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    max length of unicode string

    UINT32

    0 - undocumented

    UINT32

    length of unicode string

    UINT16[]

    string of uncode characters

    OBJ_ATTR (object attributes)

    UINT32

    0x18 - length (in bytes) including the length field.

    VOID*

    0 - root directory (pointer)

    VOID*

    0 - object name (pointer)

    UINT32

    0 - attributes (undocumented)

    VOID*

    0 - security descriptior (pointer)

    UINT32

    0 - security quality of service

    POL_HND (LSA policy handle)

    char[20]

    policy handle

    DOM_SID2 (domain SID structure, SIDS stored in unicode)

    UINT32

    5 - SID type

    UINT32

    0 - undocumented

    UNIHDR2

    domain SID unicode string header

    UNISTR

    domain SID unicode string

    Note: there is a conflict between the unicode string header and the unicode string itself as to which to use to indicate string length. this will need to be resolved.

    Note: the SID type indicates, for example, an alias; a well-known group etc. this is documented somewhere.

    DOM_RID (domain RID structure)

    UINT32

    5 - well-known SID. 1 - user SID (see ShowACLs)

    UINT32

    5 - undocumented

    UINT32

    domain RID

    UINT32

    0 - domain index out of above reference domains

    LOG_INFO (server, account, client structure)

    Note: logon server name starts with two '\' characters and is upper case.

    Note: account name is the logon client name from the LSA Request Challenge, with a $ on the end of it, in upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    account name unicode string

    UINT16

    sec_chan - security channel type

    UNISTR2

    logon client machine unicode string

    CLNT_SRV (server, client names structure)

    Note: logon server name starts with two '\' characters and is upper case.

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon client machine unicode string

    CREDS (credentials + time stamp)

    char[8]

    credentials

    UTIME

    time stamp

    CLNT_INFO2 (server, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will beused in subsequent credential checks. the presumed intention is to + maintain an authenticated request/response trail.

    CLNT_SRV

    client and server names

    UINT8[]

    ???? padding, for 4-byte alignment with SMB header.

    VOID*

    pointer to client credentials.

    CREDS

    client-calculated credentials + client time

    CLNT_INFO (server, account, client structure, client credentials)

    Note: whenever this structure appears in a request, you must take a copy of the client-calculated credentials received, because they will be used in subsequent credential checks. the presumed intention is to maintain an authenticated request/response trail.

    LOG_INFO

    logon account info

    CREDS

    client-calculated credentials + client time

    ID_INFO_1 (id info structure, auth level 1)

    VOID*

    ptr_id_info_1

    UNIHDR

    domain name unicode header

    UINT32

    param control

    UINT64

    logon ID

    UNIHDR

    user name unicode header

    UNIHDR

    workgroup name unicode header

    char[16]

    arc4 LM OWF Password

    char[16]

    arc4 NT OWF Password

    UNISTR2

    domain name unicode string

    UNISTR2

    user name unicode string

    UNISTR2

    workstation name unicode string

    SAM_INFO (sam logon/logoff id info structure)

    Note: presumably, the return credentials is supposedly for the server to verify that the credential chain hasn't been compromised.

    CLNT_INFO2

    client identification/authentication info

    VOID*

    pointer to return credentials.

    CRED

    return credentials - ignored.

    UINT16

    logon level

    UINT16

    switch value

    +        switch (switch_value)
         case 1:
         {
             ID_INFO_1     id_info_1;
-        }

    9.2.3.23. GID (group id info)

    UINT32

    group id

    UINT32

    user attributes (only used by NT 3.1 and 3.51)

    9.2.3.24. DOM_REF (domain reference info)

    VOID*

    undocumented buffer pointer.

    UINT32

    num referenced domains?

    VOID*

    undocumented domain name buffer pointer.

    UINT32

    32 - max number of entries

    UINT32

    4 - num referenced domains?

    UNIHDR2

    domain name unicode string header

    UNIHDR2[num_ref_doms-1]

    referenced domain unicode string headers

    UNISTR

    domain name unicode string

    DOM_SID[num_ref_doms]

    referenced domain SIDs

    9.2.3.25. DOM_INFO (domain info, levels 3 and 5 are the same))

    UINT8[]

    ??? padding to get 4-byte alignment with start of SMB header

    UINT16

    domain name string length * 2

    UINT16

    domain name string length * 2

    VOID*

    undocumented domain name string buffer pointer

    VOID*

    undocumented domain SID string buffer pointer

    UNISTR2

    domain name (unicode string)

    DOM_SID

    domain SID

    9.2.3.26. USER_INFO (user logon info)

    Note: it would be nice to know what the 16 byte user session key is for.

    NTTIME

    logon time

    NTTIME

    logoff time

    NTTIME

    kickoff time

    NTTIME

    password last set time

    NTTIME

    password can change time

    NTTIME

    password must change time

    UNIHDR

    username unicode string header

    UNIHDR

    user's full name unicode string header

    UNIHDR

    logon script unicode string header

    UNIHDR

    profile path unicode string header

    UNIHDR

    home directory unicode string header

    UNIHDR

    home directory drive unicode string header

    UINT16

    logon count

    UINT16

    bad password count

    UINT32

    User ID

    UINT32

    Group ID

    UINT32

    num groups

    VOID*

    undocumented buffer pointer to groups.

    UINT32

    user flags

    char[16]

    user session key

    UNIHDR

    logon server unicode string header

    UNIHDR

    logon domain unicode string header

    VOID*

    undocumented logon domain id pointer

    char[40]

    40 undocumented padding bytes. future expansion?

    UINT32

    0 - num_other_sids?

    VOID*

    NULL - undocumented pointer to other domain SIDs.

    UNISTR2

    username unicode string

    UNISTR2

    user's full name unicode string

    UNISTR2

    logon script unicode string

    UNISTR2

    profile path unicode string

    UNISTR2

    home directory unicode string

    UNISTR2

    home directory drive unicode string

    UINT32

    num groups

    GID[num_groups]

    group info

    UNISTR2

    logon server unicode string

    UNISTR2

    logon domain unicode string

    DOM_SID

    domain SID

    DOM_SID[num_sids]

    other domain SIDs?

    9.2.3.27. SH_INFO_1_PTR (pointers to level 1 share info strings)

    Note: see cifsrap2.txt section5, page 10.

    0 for shi1_type indicates a Disk.
    1 for shi1_type indicates a Print Queue.
    2 for shi1_type indicates a Device.
    3 for shi1_type indicates an IPC pipe.
    0x8000 0000 (top bit set in shi1_type) indicates a hidden share.

    VOID*

    shi1_netname - pointer to net name

    UINT32

    shi1_type - type of share. 0 - undocumented.

    VOID*

    shi1_remark - pointer to comment.

    9.2.3.28. SH_INFO_1_STR (level 1 share info strings)

    UNISTR2

    shi1_netname - unicode string of net name

    UNISTR2

    shi1_remark - unicode string of comment.

    9.2.3.29. SHARE_INFO_1_CTR

    share container with 0 entries:

    UINT32

    0 - EntriesRead

    UINT32

    0 - Buffer

    share container with > 0 entries:

    UINT32

    EntriesRead

    UINT32

    non-zero - Buffer

    UINT32

    EntriesRead

    SH_INFO_1_PTR[EntriesRead]

    share entry pointers

    SH_INFO_1_STR[EntriesRead]

    share entry strings

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    UINT32

    EntriesRead

    UINT32

    0 - padding

    9.2.3.30. SERVER_INFO_101

    Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.

    SV_TYPE_WORKSTATION

    0x00000001 All workstations

    SV_TYPE_SERVER

    0x00000002 All servers

    SV_TYPE_SQLSERVER

    0x00000004 Any server running with SQL server

    SV_TYPE_DOMAIN_CTRL

    0x00000008 Primary domain controller

    SV_TYPE_DOMAIN_BAKCTRL

    0x00000010 Backup domain controller

    SV_TYPE_TIME_SOURCE

    0x00000020 Server running the timesource service

    SV_TYPE_AFP

    0x00000040 Apple File Protocol servers

    SV_TYPE_NOVELL

    0x00000080 Novell servers

    SV_TYPE_DOMAIN_MEMBER

    0x00000100 Domain Member

    SV_TYPE_PRINTQ_SERVER

    0x00000200 Server sharing print queue

    SV_TYPE_DIALIN_SERVER

    0x00000400 Server running dialin service.

    SV_TYPE_XENIX_SERVER

    0x00000800 Xenix server

    SV_TYPE_NT

    0x00001000 NT server

    SV_TYPE_WFW

    0x00002000 Server running Windows for

    SV_TYPE_SERVER_NT

    0x00008000 Windows NT non DC server

    SV_TYPE_POTENTIAL_BROWSER

    0x00010000 Server that can run the browser service

    SV_TYPE_BACKUP_BROWSER

    0x00020000 Backup browser server

    SV_TYPE_MASTER_BROWSER

    0x00040000 Master browser server

    SV_TYPE_DOMAIN_MASTER

    0x00080000 Domain Master Browser server

    SV_TYPE_LOCAL_LIST_ONLY

    0x40000000 Enumerate only entries marked "local"

    SV_TYPE_DOMAIN_ENUM

    0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.

    UINT32

    500 - platform_id

    VOID*

    pointer to name

    UINT32

    5 - major version

    UINT32

    4 - minor version

    UINT32

    type (SV_TYPE_... bit field)

    VOID*

    pointer to comment

    UNISTR2

    sv101_name - unicode string of server name

    UNISTR2

    sv_101_comment - unicode string of server comment.

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    9.3. MSRPC over Transact Named Pipe

    For details on the SMB Transact Named Pipe, see cifs6.txt

    9.3.1. MSRPC Pipes

    The MSRPC is conducted over an SMB Transact Pipe with a name of -\PIPE\. You must first obtain a 16 bit file handle, by -sending a SMBopenX with the pipe name \PIPE\srvsvc for + } +

    GID (group id info)

    UINT32

    group id

    UINT32

    user attributes (only used by NT 3.1 and 3.51)

    DOM_REF (domain reference info)

    VOID*

    undocumented buffer pointer.

    UINT32

    num referenced domains?

    VOID*

    undocumented domain name buffer pointer.

    UINT32

    32 - max number of entries

    UINT32

    4 - num referenced domains?

    UNIHDR2

    domain name unicode string header

    UNIHDR2[num_ref_doms-1]

    referenced domain unicode string headers

    UNISTR

    domain name unicode string

    DOM_SID[num_ref_doms]

    referenced domain SIDs

    DOM_INFO (domain info, levels 3 and 5 are the same))

    UINT8[]

    ??? padding to get 4-byte alignment with start of SMB header

    UINT16

    domain name string length * 2

    UINT16

    domain name string length * 2

    VOID*

    undocumented domain name string buffer pointer

    VOID*

    undocumented domain SID string buffer pointer

    UNISTR2

    domain name (unicode string)

    DOM_SID

    domain SID

    USER_INFO (user logon info)

    Note: it would be nice to know what the 16 byte user session key is for.

    NTTIME

    logon time

    NTTIME

    logoff time

    NTTIME

    kickoff time

    NTTIME

    password last set time

    NTTIME

    password can change time

    NTTIME

    password must change time

    UNIHDR

    username unicode string header

    UNIHDR

    user's full name unicode string header

    UNIHDR

    logon script unicode string header

    UNIHDR

    profile path unicode string header

    UNIHDR

    home directory unicode string header

    UNIHDR

    home directory drive unicode string header

    UINT16

    logon count

    UINT16

    bad password count

    UINT32

    User ID

    UINT32

    Group ID

    UINT32

    num groups

    VOID*

    undocumented buffer pointer to groups.

    UINT32

    user flags

    char[16]

    user session key

    UNIHDR

    logon server unicode string header

    UNIHDR

    logon domain unicode string header

    VOID*

    undocumented logon domain id pointer

    char[40]

    40 undocumented padding bytes. future expansion?

    UINT32

    0 - num_other_sids?

    VOID*

    NULL - undocumented pointer to other domain SIDs.

    UNISTR2

    username unicode string

    UNISTR2

    user's full name unicode string

    UNISTR2

    logon script unicode string

    UNISTR2

    profile path unicode string

    UNISTR2

    home directory unicode string

    UNISTR2

    home directory drive unicode string

    UINT32

    num groups

    GID[num_groups]

    group info

    UNISTR2

    logon server unicode string

    UNISTR2

    logon domain unicode string

    DOM_SID

    domain SID

    DOM_SID[num_sids]

    other domain SIDs?

    SH_INFO_1_PTR (pointers to level 1 share info strings)

    Note: see cifsrap2.txt section5, page 10.

    0 for shi1_type indicates a Disk.
    1 for shi1_type indicates a Print Queue.
    2 for shi1_type indicates a Device.
    3 for shi1_type indicates an IPC pipe.
    0x8000 0000 (top bit set in shi1_type) indicates a hidden share.
    VOID*

    shi1_netname - pointer to net name

    UINT32

    shi1_type - type of share. 0 - undocumented.

    VOID*

    shi1_remark - pointer to comment.

    SH_INFO_1_STR (level 1 share info strings)

    UNISTR2

    shi1_netname - unicode string of net name

    UNISTR2

    shi1_remark - unicode string of comment.

    SHARE_INFO_1_CTR

    share container with 0 entries:

    UINT32

    0 - EntriesRead

    UINT32

    0 - Buffer

    share container with > 0 entries:

    UINT32

    EntriesRead

    UINT32

    non-zero - Buffer

    UINT32

    EntriesRead

    SH_INFO_1_PTR[EntriesRead]

    share entry pointers

    SH_INFO_1_STR[EntriesRead]

    share entry strings

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    UINT32

    EntriesRead

    UINT32

    0 - padding

    SERVER_INFO_101

    Note: see cifs6.txt section 6.4 - the fields described therein will be of assistance here. for example, the type listed below is the same as fServerType, which is described in 6.4.1.

    SV_TYPE_WORKSTATION

    0x00000001 All workstations

    SV_TYPE_SERVER

    0x00000002 All servers

    SV_TYPE_SQLSERVER

    0x00000004 Any server running with SQL server

    SV_TYPE_DOMAIN_CTRL

    0x00000008 Primary domain controller

    SV_TYPE_DOMAIN_BAKCTRL

    0x00000010 Backup domain controller

    SV_TYPE_TIME_SOURCE

    0x00000020 Server running the timesource service

    SV_TYPE_AFP

    0x00000040 Apple File Protocol servers

    SV_TYPE_NOVELL

    0x00000080 Novell servers

    SV_TYPE_DOMAIN_MEMBER

    0x00000100 Domain Member

    SV_TYPE_PRINTQ_SERVER

    0x00000200 Server sharing print queue

    SV_TYPE_DIALIN_SERVER

    0x00000400 Server running dialin service.

    SV_TYPE_XENIX_SERVER

    0x00000800 Xenix server

    SV_TYPE_NT

    0x00001000 NT server

    SV_TYPE_WFW

    0x00002000 Server running Windows for

    SV_TYPE_SERVER_NT

    0x00008000 Windows NT non DC server

    SV_TYPE_POTENTIAL_BROWSER

    0x00010000 Server that can run the browser service

    SV_TYPE_BACKUP_BROWSER

    0x00020000 Backup browser server

    SV_TYPE_MASTER_BROWSER

    0x00040000 Master browser server

    SV_TYPE_DOMAIN_MASTER

    0x00080000 Domain Master Browser server

    SV_TYPE_LOCAL_LIST_ONLY

    0x40000000 Enumerate only entries marked "local"

    SV_TYPE_DOMAIN_ENUM

    0x80000000 Enumerate Domains. The pszServer and pszDomain parameters must be NULL.

    UINT32

    500 - platform_id

    VOID*

    pointer to name

    UINT32

    5 - major version

    UINT32

    4 - minor version

    UINT32

    type (SV_TYPE_... bit field)

    VOID*

    pointer to comment

    UNISTR2

    sv101_name - unicode string of server name

    UNISTR2

    sv_101_comment - unicode string of server comment.

    UINT8[]

    padding to get unicode string 4-byte aligned with start of the SMB header.

    MSRPC over Transact Named Pipe

    For details on the SMB Transact Named Pipe, see cifs6.txt

    MSRPC Pipes

    +The MSRPC is conducted over an SMB Transact Pipe with a name of +\PIPE\. You must first obtain a 16 bit file handle, by +sending a SMBopenX with the pipe name \PIPE\srvsvc for example. You can then perform an SMB Trans, -and must carry out an SMBclose on the file handle once you are finished.

    Trans Requests must be sent with two setup UINT16s, no UINT16 params (none +and must carry out an SMBclose on the file handle once you are finished. +

    +Trans Requests must be sent with two setup UINT16s, no UINT16 params (none known about), and UINT8 data parameters sufficient to contain the MSRPC header, and MSRPC data. The first UINT16 setup parameter must be either 0x0026 to indicate an RPC, or 0x0001 to indicate Set Named Pipe Handle state. The second UINT16 parameter must be the file handle for the pipe, -obtained above.

    The Data section for an API Command of 0x0026 (RPC pipe) in the Trans +obtained above. +

    +The Data section for an API Command of 0x0026 (RPC pipe) in the Trans Request is the RPC Header, followed by the RPC Data. The Data section for an API Command of 0x0001 (Set Named Pipe Handle state) is two bytes. The -only value seen for these two bytes is 0x00 0x43.

    MSRPC Responses are sent as response data inside standard SMB Trans -responses, with the MSRPC Header, MSRPC Data and MSRPC tail.

    It is suspected that the Trans Requests will need to be at least 2-byte +only value seen for these two bytes is 0x00 0x43. +

    +MSRPC Responses are sent as response data inside standard SMB Trans +responses, with the MSRPC Header, MSRPC Data and MSRPC tail. +

    +It is suspected that the Trans Requests will need to be at least 2-byte aligned (probably 4-byte). This is standard practice for SMBs. It is also independent of the observed 4-byte alignments with the start of the MSRPC header, including the 4-byte alignment between the MSRPC header and the -MSRPC data.

    First, an SMBtconX connection is made to the IPC$ share. The connection +MSRPC data. +

    +First, an SMBtconX connection is made to the IPC$ share. The connection must be made using encrypted passwords, not clear-text. Then, an SMBopenX is made on the pipe. Then, a Set Named Pipe Handle State must be sent, after which the pipe is ready to accept API commands. Lastly, and SMBclose -is sent.

    To be resolved:

    lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe. Values seen so far are -listed below:

            initial SMBopenX request:         RPC API command 0x26 params:
-        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
-        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;

    9.3.2. Header

    [section to be rewritten, following receipt of work by Duncan Stansfield]

    Interesting note: if you set packed data representation to 0x0100 0000 -then all 4-byte and 2-byte word ordering is turned around!

    The start of each of the NTLSA and NETLOGON named pipes begins with:

    offset: 00

    Variable type: UINT8

    Variable data: 5 - RPC major version

    offset: 01

    Variable type: UINT8

    Variable data: 0 - RPC minor version

    offset: 02

    Variable type: UINT8

    Variable data: 2 - RPC response packet

    offset: 03

    Variable type: UINT8

    Variable data: 3 - (FirstFrag bit-wise or with LastFrag)

    offset: 04

    Variable type: UINT32

    Variable data: 0x1000 0000 - packed data representation

    offset: 08

    Variable type: UINT16

    Variable data: fragment length - data size (bytes) inc header and tail.

    offset: 0A

    Variable type: UINT16

    Variable data: 0 - authentication length

    offset: 0C

    Variable type: UINT32

    Variable data: call identifier. matches 12th UINT32 of incoming RPC data.

    offset: 10

    Variable type: UINT32

    Variable data: allocation hint - data size (bytes) minus header and tail.

    offset: 14

    Variable type: UINT16

    Variable data: 0 - presentation context identifier

    offset: 16

    Variable type: UINT8

    Variable data: 0 - cancel count

    offset: 17

    Variable type: UINT8

    Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.

    offset: 18

    Variable type: ......

    Variable data: start of data (goes on for allocation_hint bytes)

    9.3.2.1. RPC_Packet for request, response, bind and bind acknowledgement

    UINT8 versionmaj

    reply same as request (0x05)

    UINT8 versionmin

    reply same as request (0x00)

    UINT8 type

    one of the MSRPC_Type enums

    UINT8 flags

    reply same as request (0x00 for Bind, 0x03 for Request)

    UINT32 representation

    reply same as request (0x00000010)

    UINT16 fraglength

    the length of the data section of the SMB trans packet

    UINT16 authlength

    UINT32 callid

    call identifier. (e.g. 0x00149594)

    * stub USE TvPacket

    the remainder of the packet depending on the "type"

    9.3.2.2. Interface identification

    the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc

    abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
-transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)

    9.3.2.3. RPC_Iface RW

    UINT8 byte[16]

    16 bytes of number

    UINT32 version

    the interface number

    9.3.2.4. RPC_ReqBind RW

    the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck

    UINT16 maxtsize

    maximum transmission fragment size (0x1630)

    UINT16 maxrsize

    max receive fragment size (0x1630)

    UINT32 assocgid

    associated group id (0x0)

    UINT32 numelements

    the number of elements (0x1)

    UINT16 contextid

    presentation context identifier (0x0)

    UINT8 numsyntaxes

    the number of syntaxes (has always been 1?)(0x1)

    UINT8[]

    4-byte alignment padding, against SMB header

    * abstractint USE RPC_Iface

    num and vers. of interface client is using

    * transferint USE RPC_Iface

    num and vers. of interface to use for replies

    9.3.2.5. RPC_Address RW

    UINT16 length

    length of the string including null terminator

    * port USE string

    the string above in single byte, null terminated form

    9.3.2.6. RPC_ResBind RW

    the response to place after the header in the reply packet

    UINT16 maxtsize

    same as request

    UINT16 maxrsize

    same as request

    UINT32 assocgid

    zero

    * secondaddr USE RPC_Address

    the address string, as described earlier

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT8 numresults

    the number of results (0x01)

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT16 result

    result (0x00 = accept)

    UINT16 reason

    reason (0x00 = no reason specified)

    * transfersyntax USE RPC_Iface

    the transfer syntax from the request

    9.3.2.7. RPC_ReqNorm RW

    the remainder of the packet after the header for every other other request

    UINT32 allochint

    the size of the stub data in bytes

    UINT16 prescontext

    presentation context identifier (0x0)

    UINT16 opnum

    operation number (0x15)

    * stub USE TvPacket

    a packet dependent on the pipe name (probably the interface) and the op number)

    9.3.2.8. RPC_ResNorm RW

    UINT32 allochint

    # size of the stub data in bytes

    UINT16 prescontext

    # presentation context identifier (same as request)

    UINT8 cancelcount

    # cancel count? (0x0)

    UINT8 reserved

    # 0 - one byte padding

    * stub USE TvPacket

    # the remainder of the reply

    9.3.3. Tail

    The end of each of the NTLSA and NETLOGON named pipes ends with:

    ......

    end of data

    UINT32

    return code

    9.3.4. RPC Bind / Bind Ack

    RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc) -with a "transfer syntax" (see RPC_Iface structure). The purpose for doing -this is unknown.

    Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters. The first is 0x0026; the second is the file handle - returned by the SMBopenX Transact response.

    Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The +is sent. +

    +To be resolved: +

    +lkcl/01nov97 there appear to be two additional bytes after the null-terminated \PIPE\ name for the RPC pipe. Values seen so far are +listed below:

    +        initial SMBopenX request:         RPC API command 0x26 params:
+        "\\PIPE\\lsarpc"                  0x65 0x63; 0x72 0x70; 0x44 0x65;
+        "\\PIPE\\srvsvc"                  0x73 0x76; 0x4E 0x00; 0x5C 0x43;
+

    Header

    [section to be rewritten, following receipt of work by Duncan Stansfield]

    Interesting note: if you set packed data representation to 0x0100 0000 +then all 4-byte and 2-byte word ordering is turned around!

    The start of each of the NTLSA and NETLOGON named pipes begins with:

    offset: 00

    Variable type: UINT8

    Variable data: 5 - RPC major version

    offset: 01

    Variable type: UINT8

    Variable data: 0 - RPC minor version

    offset: 02

    Variable type: UINT8

    Variable data: 2 - RPC response packet

    offset: 03

    Variable type: UINT8

    Variable data: 3 - (FirstFrag bit-wise or with LastFrag)

    offset: 04

    Variable type: UINT32

    Variable data: 0x1000 0000 - packed data representation

    offset: 08

    Variable type: UINT16

    Variable data: fragment length - data size (bytes) inc header and tail.

    offset: 0A

    Variable type: UINT16

    Variable data: 0 - authentication length

    offset: 0C

    Variable type: UINT32

    Variable data: call identifier. matches 12th UINT32 of incoming RPC data.

    offset: 10

    Variable type: UINT32

    Variable data: allocation hint - data size (bytes) minus header and tail.

    offset: 14

    Variable type: UINT16

    Variable data: 0 - presentation context identifier

    offset: 16

    Variable type: UINT8

    Variable data: 0 - cancel count

    offset: 17

    Variable type: UINT8

    Variable data: in replies: 0 - reserved; in requests: opnum - see #defines.

    offset: 18

    Variable type: ......

    Variable data: start of data (goes on for allocation_hint bytes)

    RPC_Packet for request, response, bind and bind acknowledgement

    UINT8 versionmaj

    reply same as request (0x05)

    UINT8 versionmin

    reply same as request (0x00)

    UINT8 type

    one of the MSRPC_Type enums

    UINT8 flags

    reply same as request (0x00 for Bind, 0x03 for Request)

    UINT32 representation

    reply same as request (0x00000010)

    UINT16 fraglength

    the length of the data section of the SMB trans packet

    UINT16 authlength

    UINT32 callid

    call identifier. (e.g. 0x00149594)

    * stub USE TvPacket

    the remainder of the packet depending on the "type"

    Interface identification

    the interfaces are numbered. as yet I haven't seen more than one interface used on the same pipe name srvsvc

    +abstract (0x4B324FC8, 0x01D31670, 0x475A7812, 0x88E16EBF, 0x00000003)
+transfer (0x8A885D04, 0x11C91CEB, 0x0008E89F, 0x6048102B, 0x00000002)
+

    RPC_Iface RW

    UINT8 byte[16]

    16 bytes of number

    UINT32 version

    the interface number

    RPC_ReqBind RW

    the remainder of the packet after the header if "type" was Bind in the response header, "type" should be BindAck

    UINT16 maxtsize

    maximum transmission fragment size (0x1630)

    UINT16 maxrsize

    max receive fragment size (0x1630)

    UINT32 assocgid

    associated group id (0x0)

    UINT32 numelements

    the number of elements (0x1)

    UINT16 contextid

    presentation context identifier (0x0)

    UINT8 numsyntaxes

    the number of syntaxes (has always been 1?)(0x1)

    UINT8[]

    4-byte alignment padding, against SMB header

    * abstractint USE RPC_Iface

    num and vers. of interface client is using

    * transferint USE RPC_Iface

    num and vers. of interface to use for replies

    RPC_Address RW

    UINT16 length

    length of the string including null terminator

    * port USE string

    the string above in single byte, null terminated form

    RPC_ResBind RW

    the response to place after the header in the reply packet

    UINT16 maxtsize

    same as request

    UINT16 maxrsize

    same as request

    UINT32 assocgid

    zero

    * secondaddr USE RPC_Address

    the address string, as described earlier

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT8 numresults

    the number of results (0x01)

    UINT8[]

    4-byte alignment padding, against SMB header

    UINT16 result

    result (0x00 = accept)

    UINT16 reason

    reason (0x00 = no reason specified)

    * transfersyntax USE RPC_Iface

    the transfer syntax from the request

    RPC_ReqNorm RW

    the remainder of the packet after the header for every other other request

    UINT32 allochint

    the size of the stub data in bytes

    UINT16 prescontext

    presentation context identifier (0x0)

    UINT16 opnum

    operation number (0x15)

    * stub USE TvPacket

    a packet dependent on the pipe name (probably the interface) and the op number)

    RPC_ResNorm RW

    UINT32 allochint

    # size of the stub data in bytes

    UINT16 prescontext

    # presentation context identifier (same as request)

    UINT8 cancelcount

    # cancel count? (0x0)

    UINT8 reserved

    # 0 - one byte padding

    * stub USE TvPacket

    # the remainder of the reply

    Tail

    The end of each of the NTLSA and NETLOGON named pipes ends with:

    ......

    end of data

    UINT32

    return code

    RPC Bind / Bind Ack

    +RPC Binds are the process of associating an RPC pipe (e.g \PIPE\lsarpc) +with a "transfer syntax" (see RPC_Iface structure). The purpose for doing +this is unknown. +

    Note: The RPC_ResBind SMB Transact request is sent with two uint16 setup parameters. The first is 0x0026; the second is the file handle + returned by the SMBopenX Transact response.

    Note: The RPC_ResBind members maxtsize, maxrsize and assocgid are the same in the response as the same members in the RPC_ReqBind. The RPC_ResBind member transfersyntax is the same in the response as - the

    Note: The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe. The - mapping identified so far is:

    initial SMBopenX request:

    RPC_ResBind response:

    "\\PIPE\\srvsvc"

    "\\PIPE\\ntsvcs"

    "\\PIPE\\samr"

    "\\PIPE\\lsass"

    "\\PIPE\\lsarpc"

    "\\PIPE\\lsass"

    "\\PIPE\\wkssvc"

    "\\PIPE\\wksvcs"

    "\\PIPE\\NETLOGON"

    "\\PIPE\\NETLOGON"

    Note: The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.

    Request:

    RPC_Packet
    RPC_ReqBind

    Response:

    RPC_Packet
    RPC_ResBind

    9.3.5. NTLSA Transact Named Pipe

    The sequence of actions taken on this pipe are:

    Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle.
    Using the file handle, send a Set Named Pipe Handle state to 0x4300.
    Send an LSA Open Policy request. Store the Policy Handle.
    Using the Policy Handle, send LSA Query Info Policy requests, etc.
    Using the Policy Handle, send an LSA Close.
    Close the IPC$ share.

    Defines for this pipe, identifying the query are:

    LSA Open Policy:

    0x2c

    LSA Query Info Policy:

    0x07

    LSA Enumerate Trusted Domains:

    0x0d

    LSA Open Secret:

    0xff

    LSA Lookup SIDs:

    0xfe

    LSA Lookup Names:

    0xfd

    LSA Close:

    0x00

    9.3.6. LSA Open Policy

    Note: The policy handle can be anything you like.

    9.3.6.1. Request

    VOID*

    buffer pointer

    UNISTR2

    server name - unicode string starting with two '\'s

    OBJ_ATTR

    object attributes

    UINT32

    1 - desired access

    9.3.6.2. Response

    POL_HND

    LSA policy handle

    return

    0 - indicates success

    9.3.7. LSA Query Info Policy

    Note: The info class in response must be the same as that in the request.

    9.3.7.1. Request

    POL_HND

    LSA policy handle

    UINT16

    info class (also a policy handle?)

    9.3.7.2. Response

    VOID*

    undocumented buffer pointer

    UINT16

    info class (same as info class in request).

    switch (info class)
+	the
    Note:	The RPC_ResBind response member secondaddr contains the name of what is presumed to be the service behind the RPC pipe.  The
+	mapping identified so far is:
    initial SMBopenX request:
    RPC_ResBind response:
    "\\PIPE\\srvsvc"
    "\\PIPE\\ntsvcs"
    "\\PIPE\\samr"
    "\\PIPE\\lsass"
    "\\PIPE\\lsarpc"
    "\\PIPE\\lsass"
    "\\PIPE\\wkssvc"
    "\\PIPE\\wksvcs"
    "\\PIPE\\NETLOGON"
    "\\PIPE\\NETLOGON"
    Note:	The RPC_Packet fraglength member in both the Bind Request and Bind Acknowledgment must contain the length of the entire RPC data, including the RPC_Packet header.
    Request:
    RPC_Packet
    RPC_ReqBind
    Response:
    RPC_Packet
    RPC_ResBind

    NTLSA Transact Named Pipe

    The sequence of actions taken on this pipe are:

    Establish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    Open an RPC Pipe with the name "\\PIPE\\lsarpc". Store the file handle.
    Using the file handle, send a Set Named Pipe Handle state to 0x4300.
    Send an LSA Open Policy request. Store the Policy Handle.
    Using the Policy Handle, send LSA Query Info Policy requests, etc.
    Using the Policy Handle, send an LSA Close.
    Close the IPC$ share.

    Defines for this pipe, identifying the query are:

    LSA Open Policy:

    0x2c

    LSA Query Info Policy:

    0x07

    LSA Enumerate Trusted Domains:

    0x0d

    LSA Open Secret:

    0xff

    LSA Lookup SIDs:

    0xfe

    LSA Lookup Names:

    0xfd

    LSA Close:

    0x00

    LSA Open Policy

    Note: The policy handle can be anything you like.

    Request

    VOID*

    buffer pointer

    UNISTR2

    server name - unicode string starting with two '\'s

    OBJ_ATTR

    object attributes

    UINT32

    1 - desired access

    Response

    POL_HND

    LSA policy handle

    return

    0 - indicates success

    LSA Query Info Policy

    Note: The info class in response must be the same as that in the request.

    Request

    POL_HND

    LSA policy handle

    UINT16

    info class (also a policy handle?)

    Response

    VOID*

    undocumented buffer pointer

    UINT16

    info class (same as info class in request).

    +switch (info class)
 case 3:
 case 5:
 {
 DOM_INFO domain info, levels 3 and 5 (are the same).
 }
 
-return    0 - indicates success

    9.3.8. LSA Enumerate Trusted Domains

    9.3.8.1. Request

    no extra data

    9.3.8.2. Response

    UINT32

    0 - enumeration context

    UINT32

    0 - entries read

    UINT32

    0 - trust information

    return

    0x8000 001a - "no trusted domains" success code

    9.3.9. LSA Open Secret

    9.3.9.1. Request

    no extra data

    9.3.9.2. Response

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    return 0x0C00 0034 - "no such secret" success code

    9.3.10. LSA Close

    9.3.10.1. Request

    POL_HND

    policy handle to be closed

    9.3.10.2. Response

    POL_HND

    0s - closed policy handle (all zeros)

    return 0 - indicates success

    9.3.11. LSA Lookup SIDS

    Note: num_entries in response must be same as num_entries in request.

    9.3.11.1. Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    VOID*[num_entries] undocumented domain SID pointers to be looked up.

    DOM_SID[num_entries] domain SIDs to be looked up.

    char[16]

    completely undocumented 16 bytes.

    9.3.11.2. Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_SID2[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    9.3.12. LSA Lookup Names

    Note: num_entries in response must be same as num_entries in request.

    9.3.12.1. Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    NAME[num_entries]

    names to be looked up.

    char[]

    undocumented bytes - falsely translated SID structure?

    9.3.12.2. Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_RID[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    9.4. NETLOGON rpc Transact Named Pipe

    The sequence of actions taken on this pipe are:

    tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle.
    ing the file handle, send a Set Named Pipe Handle state to 0x4300.
    eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.
    lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.
    lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.
    ose the IPC$ share.

    Defines for this pipe, identifying the query are

    LSA Request Challenge:

    0x04

    LSA Server Password Set:

    0x06

    LSA SAM Logon:

    0x02

    LSA SAM Logoff:

    0x03

    LSA Auth 2:

    0x0f

    LSA Logon Control:

    0x0e

    9.4.1. LSA Request Challenge

    Note: logon server name starts with two '\' characters and is upper case.

    Note: logon client is the machine, not the user.

    Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).

    9.4.1.1. Request

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    logon client unicode string

    char[8]

    client challenge

    9.4.1.2. Response

    char[8]

    server challenge

    return 0 - indicates success

    9.4.2. LSA Authenticate 2

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: neg_flags in the response is the same as that in the request.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    9.4.2.1. Request

    LOG_INFO

    client identification info

    char[8]

    client-calculated credentials

    UINT8[]

    padding to 4-byte align with start of SMB header.

    UINT32

    neg_flags - negotiated flags (usual value is 0x0000 01ff)

    9.4.2.2. Response

    char[8]

    server credentials.

    UINT32

    neg_flags - same as neg_flags in request.

    return 0 - indicates success. failure value unknown.

    9.4.3. LSA Server Password Set

    Note: the new password is suspected to be a DES encryption using the old password to generate the key.

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    9.4.3.1. Request

    CLNT_INFO

    client identification/authentication info

    char[]

    new password - undocumented.

    9.4.3.2. Response

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success; 0xC000 006a indicates failure

    9.4.4. LSA SAM Logon

    Note: valid_user is True iff the username and password hash are valid for - the requested domain.

    9.4.4.1. Request

    SAM_INFO

    sam_id structure

    9.4.4.2. Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    if (valid_user)
+return    0 - indicates success
+

    LSA Enumerate Trusted Domains

    Request

    no extra data

    Response

    UINT32

    0 - enumeration context

    UINT32

    0 - entries read

    UINT32

    0 - trust information

    return

    0x8000 001a - "no trusted domains" success code

    LSA Open Secret

    Request

    no extra data

    Response

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    UINT32

    0 - undocumented

    return 0x0C00 0034 - "no such secret" success code

    LSA Close

    Request

    POL_HND

    policy handle to be closed

    Response

    POL_HND

    0s - closed policy handle (all zeros)

    return 0 - indicates success

    LSA Lookup SIDS

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    VOID*[num_entries] undocumented domain SID pointers to be looked up. +

    DOM_SID[num_entries] domain SIDs to be looked up.

    char[16]

    completely undocumented 16 bytes.

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_SID2[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    LSA Lookup Names

    Note: num_entries in response must be same as num_entries in request.

    Request

    POL_HND

    LSA policy handle

    UINT32

    num_entries

    UINT32

    num_entries

    VOID*

    undocumented domain SID buffer pointer

    VOID*

    undocumented domain name buffer pointer

    NAME[num_entries]

    names to be looked up.

    char[]

    undocumented bytes - falsely translated SID structure?

    Response

    DOM_REF

    domain reference response

    UINT32

    num_entries (listed above)

    VOID*

    undocumented buffer pointer

    UINT32

    num_entries (listed above)

    DOM_RID[num_entries]

    domain SIDs (from Request, listed above).

    UINT32

    num_entries (listed above)

    return 0 - indicates success

    NETLOGON rpc Transact Named Pipe

    The sequence of actions taken on this pipe are:

    tablish a connection to the IPC$ share (SMBtconX). use encrypted passwords.
    en an RPC Pipe with the name "\\PIPE\\NETLOGON". Store the file handle.
    ing the file handle, send a Set Named Pipe Handle state to 0x4300.
    eate Client Challenge. Send LSA Request Challenge. Store Server Challenge.
    lculate Session Key. Send an LSA Auth 2 Challenge. Store Auth2 Challenge.
    lc/Verify Client Creds. Send LSA Srv PW Set. Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logon . Calc/Verify Server Creds.
    lc/Verify Client Creds. Send LSA SAM Logoff. Calc/Verify Server Creds.
    ose the IPC$ share.

    Defines for this pipe, identifying the query are

    LSA Request Challenge:

    0x04

    LSA Server Password Set:

    0x06

    LSA SAM Logon:

    0x02

    LSA SAM Logoff:

    0x03

    LSA Auth 2:

    0x0f

    LSA Logon Control:

    0x0e

    LSA Request Challenge

    Note: logon server name starts with two '\' characters and is upper case.

    Note: logon client is the machine, not the user.

    Note: the initial LanManager password hash, against which the challenge is issued, is the machine name itself (lower case). there will becalls issued (LSA Server Password Set) which will change this, later. refusing these calls allows you to always deal with the same password (i.e the LM# of the machine name in lower case).

    Request

    VOID*

    undocumented buffer pointer

    UNISTR2

    logon server unicode string

    UNISTR2

    logon client unicode string

    char[8]

    client challenge

    Response

    char[8]

    server challenge

    return 0 - indicates success

    LSA Authenticate 2

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: neg_flags in the response is the same as that in the request.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    LOG_INFO

    client identification info

    char[8]

    client-calculated credentials

    UINT8[]

    padding to 4-byte align with start of SMB header.

    UINT32

    neg_flags - negotiated flags (usual value is 0x0000 01ff)

    Response

    char[8]

    server credentials.

    UINT32

    neg_flags - same as neg_flags in request.

    return 0 - indicates success. failure value unknown.

    LSA Server Password Set

    Note: the new password is suspected to be a DES encryption using the old password to generate the key.

    Note: in between request and response, calculate the client credentials, and check them against the client-calculated credentials (this process uses the previously received client credentials).

    Note: the server credentials are constructed from the client-calculated credentials and the client time + 1 second.

    Note: you must take a copy of the client-calculated credentials received here, because they will be used in subsequent authentication packets.

    Request

    CLNT_INFO

    client identification/authentication info

    char[]

    new password - undocumented.

    Response

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success; 0xC000 006a indicates failure

    LSA SAM Logon

    +Note: valid_user is True iff the username and password hash are valid for + the requested domain. +

    Request

    SAM_INFO

    sam_id structure

    Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    +if (valid_user)
 {
 	UINT16      3 - switch value indicating USER_INFO structure.
     VOID*     non-zero - pointer to USER_INFO structure
@@ -6981,1340 +1298,117 @@ else
     UINT32    1 - Authoritative response; 0 - Non-Auth?
 
     return    0xC000 0064 - NT_STATUS_NO_SUCH_USER.
-}

    9.4.5. LSA SAM Logoff

    Note: presumably, the SAM_INFO structure is validated, and a (currently - undocumented) error code returned if the Logoff is invalid.

    9.4.5.1. Request

    SAM_INFO

    sam_id structure

    9.4.5.2. Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success. undocumented failure indication.

    9.5. \\MAILSLOT\NET\NTLOGON

    Note: mailslots will contain a response mailslot, to which the response - should be sent. the target NetBIOS name is REQUEST_NAME<20>, where - REQUEST_NAME is the name of the machine that sent the request.

    9.5.1. Query for PDC

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    9.5.1.1. Request

    UINT16

    0x0007 - Query for PDC

    STR

    machine name

    STR

    response mailslot

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    9.5.1.2. Response

    UINT16

    0x000A - Respose to Query for PDC

    STR

    machine name (in uppercase)

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UNISTR

    domain name

    UINT32

    NTversion (same as received in request)

    UINT16

    LMNTtoken (same as received in request)

    UINT16

    LM20token (same as received in request)

    9.5.2. SAM Logon

    Note: machine name in response is preceded by two '\' characters.

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Note: user name in the response is presumably the same as that in the request.

    9.5.2.1. Request

    UINT16

    0x0012 - SAM Logon

    UINT16

    request count

    UNISTR

    machine name

    UNISTR

    user name

    STR

    response mailslot

    UINT32

    alloweable account

    UINT32

    domain SID size

    char[sid_size]

    domain SID, of sid_size bytes.

    UINT8[]

    ???? padding to 4? 2? -byte align with start of mailslot.

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    9.5.2.2. Response

    UINT16

    0x0013 - Response to SAM Logon

    UNISTR

    machine name

    UNISTR

    user name - workstation trust account

    UNISTR

    domain name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    9.6. SRVSVC Transact Named Pipe

    Defines for this pipe, identifying the query are:

    Net Share Enum

    0x0f

    Net Server Get Info

    0x15

    9.6.1. Net Share Enum

    Note: share level and switch value in the response are presumably the same as those in the request.

    Note: cifsrap2.txt (section 5) may be of limited assistance here.

    9.6.1.1. Request

    VOID*

    pointer (to server name?)

    UNISTR2

    server name

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info with 0 entries

    UINT32

    preferred maximum length (0xffff ffff)

    9.6.1.2. Response

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info (only added if share info ptr is non-zero)

    return 0 - indicates success

    9.6.2. Net Server Get Info

    Note: level is the same value as in the request.

    9.6.2.1. Request

    UNISTR2

    server name

    UINT32

    switch level

    9.6.2.2. Response

    UINT32

    switch level

    VOID*

    pointer to SERVER_INFO_101

    SERVER_INFO_101

    server info (only added if server info ptr is non-zero)

    return 0 - indicates success

    9.7. Cryptographic side of NT Domain Authentication

    9.7.1. Definitions

    Add(A1,A2)

    Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2

    E(K,D)

    DES ECB encryption of 8 byte data D using 7 byte key K

    lmowf()

    Lan man hash

    ntowf()

    NT hash

    PW

    md4(machine_password) == md4(lsadump $machine.acc) == -pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))

    ARC4(K,Lk,D,Ld)

    ARC4 encryption of data D of length Ld with key K of length Lk

    v[m..n(,l)]

    subset of v from bytes m to n, optionally padded with zeroes to length l

    Cred(K,D)

    E(K[7..7,7],E(K[0..6],D)) computes a credential

    Time()

    4 byte current time

    Cc,Cs

    8 byte client and server challenges Rc,Rs: 8 byte client and server credentials

    9.7.2. Protocol

    C->S ReqChal,Cc
-S->C Cs
    C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
    C: Rc = Cred(Ks,Cc)
-C->S Authenticate,Rc
+}
+

    LSA SAM Logoff

    +Note: presumably, the SAM_INFO structure is validated, and a (currently + undocumented) error code returned if the Logoff is invalid. +

    Request

    SAM_INFO

    sam_id structure

    Response

    VOID*

    undocumented buffer pointer

    CREDS

    server credentials. server time stamp appears to be ignored.

    return 0 - indicates success. undocumented failure indication.

    \\MAILSLOT\NET\NTLOGON

    +Note: mailslots will contain a response mailslot, to which the response + should be sent. the target NetBIOS name is REQUEST_NAME<20>, where + REQUEST_NAME is the name of the machine that sent the request. +

    Query for PDC

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Request

    UINT16

    0x0007 - Query for PDC

    STR

    machine name

    STR

    response mailslot

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x000A - Respose to Query for PDC

    STR

    machine name (in uppercase)

    UINT8[]

    padding to 2-byte align with start of mailslot.

    UNISTR

    machine name

    UNISTR

    domain name

    UINT32

    NTversion (same as received in request)

    UINT16

    LMNTtoken (same as received in request)

    UINT16

    LM20token (same as received in request)

    SAM Logon

    Note: machine name in response is preceded by two '\' characters.

    Note: NTversion, LMNTtoken, LM20token in response are the same as those given in the request.

    Note: user name in the response is presumably the same as that in the request.

    Request

    UINT16

    0x0012 - SAM Logon

    UINT16

    request count

    UNISTR

    machine name

    UNISTR

    user name

    STR

    response mailslot

    UINT32

    alloweable account

    UINT32

    domain SID size

    char[sid_size]

    domain SID, of sid_size bytes.

    UINT8[]

    ???? padding to 4? 2? -byte align with start of mailslot.

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    Response

    UINT16

    0x0013 - Response to SAM Logon

    UNISTR

    machine name

    UNISTR

    user name - workstation trust account

    UNISTR

    domain name

    UINT32

    NTversion

    UINT16

    LMNTtoken

    UINT16

    LM20token

    SRVSVC Transact Named Pipe

    Defines for this pipe, identifying the query are:

    Net Share Enum

    0x0f

    Net Server Get Info

    0x15

    Net Share Enum

    Note: share level and switch value in the response are presumably the same as those in the request.

    Note: cifsrap2.txt (section 5) may be of limited assistance here.

    Request

    VOID*

    pointer (to server name?)

    UNISTR2

    server name

    UINT8[]

    padding to get unicode string 4-byte aligned with the start of the SMB header.

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info with 0 entries

    UINT32

    preferred maximum length (0xffff ffff)

    Response

    UINT32

    share level

    UINT32

    switch value

    VOID*

    pointer to SHARE_INFO_1_CTR

    SHARE_INFO_1_CTR

    share info (only added if share info ptr is non-zero)

    return 0 - indicates success

    Net Server Get Info

    Note: level is the same value as in the request.

    Request

    UNISTR2

    server name

    UINT32

    switch level

    Response

    UINT32

    switch level

    VOID*

    pointer to SERVER_INFO_101

    SERVER_INFO_101

    server info (only added if server info ptr is non-zero)

    return 0 - indicates success

    Cryptographic side of NT Domain Authentication

    Definitions

    Add(A1,A2)

    Intel byte ordered addition of corresponding 4 byte words in arrays A1 and A2

    E(K,D)

    DES ECB encryption of 8 byte data D using 7 byte key K

    lmowf()

    Lan man hash

    ntowf()

    NT hash

    PW

    md4(machine_password) == md4(lsadump $machine.acc) == +pwdump(machine$) (initially) == md4(lmowf(unicode(machine))) +

    ARC4(K,Lk,D,Ld)

    ARC4 encryption of data D of length Ld with key K of length Lk

    v[m..n(,l)]

    subset of v from bytes m to n, optionally padded with zeroes to length l

    Cred(K,D)

    E(K[7..7,7],E(K[0..6],D)) computes a credential

    Time()

    4 byte current time

    Cc,Cs

    8 byte client and server challenges Rc,Rs: 8 byte client and server credentials

    Protocol

    +C->S ReqChal,Cc
+S->C Cs
+
    +C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
+
    +C: Rc = Cred(Ks,Cc)
+C->S Authenticate,Rc
 S: Rs = Cred(Ks,Cs), assert(Rc == Cred(Ks,Cc))
-S->C Rs
-C: assert(Rs == Cred(Ks,Cs))

    On joining the domain the client will optionally attempt to change its +S->C Rs +C: assert(Rs == Cred(Ks,Cs)) +

    +On joining the domain the client will optionally attempt to change its password and the domain controller may refuse to update it depending -on registry settings. This will also occur weekly afterwards.

    C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
-C->S ServerPasswordSet,Rc',Tc,arc4(Ks[0..7,16],lmowf(randompassword())
+on registry settings. This will also occur weekly afterwards.
+
    +C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
+C->S ServerPasswordSet,Rc',Tc,arc4(Ks[0..7,16],lmowf(randompassword())
 C: Rc = Cred(Ks,Rc+Tc+1)
 S: assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time()
 S: Rs' = Cred(Ks,Rs+Tc+1)
-S->C Rs',Ts
+S->C Rs',Ts
 C: assert(Rs' == Cred(Ks,Rs+Tc+1))
-S: Rs = Rs'
    User: U with password P wishes to login to the domain (incidental data
-such as workstation and domain omitted)
    C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
-C->S NetLogonSamLogon,Rc',Tc,U,arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16)
+S: Rs = Rs'
+
    
+User: U with password P wishes to login to the domain (incidental data
+such as workstation and domain omitted)
+
    +C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc)
+C->S NetLogonSamLogon,Rc',Tc,U,arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16)
 S: assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM)
-S: Ts = Time()
    S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
+S: Ts = Time()
+
    +S->C Cred(Ks,Cred(Ks,Rc+Tc+1)),userinfo(logon script,UID,SIDs,etc)
 C: assert(Rs == Cred(Ks,Cred(Rc+Tc+1))
-C: Rc = Cred(Ks,Rc+Tc+1)

    9.7.3. Comments

    On first joining the domain the session key could be computed by +C: Rc = Cred(Ks,Rc+Tc+1) +

    Comments

    +On first joining the domain the session key could be computed by anyone listening in on the network as the machine password has a well known value. Until the machine is rebooted it will use this session key to encrypt NT and LM one way functions of passwords which are password equivalents. Any user who logs in before the machine has been rebooted a second time will have their password equivalent exposed. Of -course the new machine password is exposed at this time anyway.

    None of the returned user info such as logon script, profile path and -SIDs *appear* to be protected by anything other than the TCP checksum.

    The server time stamps appear to be ignored.

    The client sends a ReturnAuthenticator in the SamLogon request which I +course the new machine password is exposed at this time anyway. +

    +None of the returned user info such as logon script, profile path and +SIDs *appear* to be protected by anything other than the TCP checksum. +

    +The server time stamps appear to be ignored. +

    +The client sends a ReturnAuthenticator in the SamLogon request which I can't find a use for. However its time is used as the timestamp -returned by the server.

    The password OWFs should NOT be sent over the network reversibly +returned by the server. +

    +The password OWFs should NOT be sent over the network reversibly encrypted. They should be sent using ARC4(Ks,md4(owf)) with the server -computing the same function using the owf values in the SAM.

    9.8. SIDs and RIDs

    SIDs and RIDs are well documented elsewhere.

    A SID is an NT Security ID (see DOM_SID structure). They are of the form:

    revision-NN-SubAuth1-SubAuth2-SubAuth3...
    revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...

    currently, the SID revision is 1. -The Sub-Authorities are known as Relative IDs (RIDs).

    9.8.1. Well-known SIDs

    9.8.1.1. Universal well-known SIDs

    Null SID

    S-1-0-0

    World

    S-1-1-0

    Local

    S-1-2-0

    Creator Owner ID

    S-1-3-0

    Creator Group ID

    S-1-3-1

    Creator Owner Server ID

    S-1-3-2

    Creator Group Server ID

    S-1-3-3

    (Non-unique IDs)

    S-1-4

    9.8.1.2. NT well-known SIDs

    NT Authority

    S-1-5

    Dialup

    S-1-5-1

    Network

    S-1-5-2

    Batch

    S-1-5-3

    Interactive

    S-1-5-4

    Service

    S-1-5-6

    AnonymousLogon(aka null logon session)

    S-1-5-7

    Proxy

    S-1-5-8

    ServerLogon(aka domain controller account)

    S-1-5-8

    (Logon IDs)

    S-1-5-5-X-Y

    (NT non-unique IDs)

    S-1-5-0x15-...

    (Built-in domain)

    s-1-5-0x20

    9.8.2. Well-known RIDS

    A RID is a sub-authority value, as part of either a SID, or in the case +computing the same function using the owf values in the SAM. +

    SIDs and RIDs

    +SIDs and RIDs are well documented elsewhere. +

    +A SID is an NT Security ID (see DOM_SID structure). They are of the form: +

    revision-NN-SubAuth1-SubAuth2-SubAuth3...
    revision-0xNNNNNNNNNNNN-SubAuth1-SubAuth2-SubAuth3...

    +currently, the SID revision is 1. +The Sub-Authorities are known as Relative IDs (RIDs). +

    Well-known SIDs

    Universal well-known SIDs

    Null SID

    S-1-0-0

    World

    S-1-1-0

    Local

    S-1-2-0

    Creator Owner ID

    S-1-3-0

    Creator Group ID

    S-1-3-1

    Creator Owner Server ID

    S-1-3-2

    Creator Group Server ID

    S-1-3-3

    (Non-unique IDs)

    S-1-4

    NT well-known SIDs

    NT Authority

    S-1-5

    Dialup

    S-1-5-1

    Network

    S-1-5-2

    Batch

    S-1-5-3

    Interactive

    S-1-5-4

    Service

    S-1-5-6

    AnonymousLogon(aka null logon session)

    S-1-5-7

    Proxy

    S-1-5-8

    ServerLogon(aka domain controller account)

    S-1-5-8

    (Logon IDs)

    S-1-5-5-X-Y

    (NT non-unique IDs)

    S-1-5-0x15-...

    (Built-in domain)

    s-1-5-0x20

    Well-known RIDS

    +A RID is a sub-authority value, as part of either a SID, or in the case of Group RIDs, part of the DOM_GID structure, in the USER_INFO_1 -structure, in the LSA SAM Logon response.

    9.8.2.1. Well-known RID users

    Groupname: DOMAIN_USER_RID_ADMIN

    ????: 0x0000

    RID: 01F4

    Groupname: DOMAIN_USER_RID_GUEST

    ????: 0x0000

    RID: 01F5

    9.8.2.2. Well-known RID groups

    Groupname: DOMAIN_GROUP_RID_ADMINS

    ????: 0x0000

    RID: 0200

    Groupname: DOMAIN_GROUP_RID_USERS

    ????: 0x0000

    RID: 0201

    Groupname: DOMAIN_GROUP_RID_GUESTS

    ????: 0x0000

    RID: 0202

    9.8.2.3. Well-known RID aliases

    Groupname: DOMAIN_ALIAS_RID_ADMINS

    ????: 0x0000

    RID: 0220

    Groupname: DOMAIN_ALIAS_RID_USERS

    ????: 0x0000

    RID: 0221

    Groupname: DOMAIN_ALIAS_RID_GUESTS

    ????: 0x0000

    RID: 0222

    Groupname: DOMAIN_ALIAS_RID_POWER_USERS

    ????: 0x0000

    RID: 0223

    Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS

    ????: 0x0000

    RID: 0224

    Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS

    ????: 0x0000

    RID: 0225

    Groupname: DOMAIN_ALIAS_RID_PRINT_OPS

    ????: 0x0000

    RID: 0226

    Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS

    ????: 0x0000

    RID: 0227

    Groupname: DOMAIN_ALIAS_RID_REPLICATOR

    ????: 0x0000

    RID: 0228

    Chapter 10. Samba Printing Internals

    10.1. Abstract

    The purpose of this document is to provide some insight into +structure, in the LSA SAM Logon response. +

    Well-known RID users

    Groupname: DOMAIN_USER_RID_ADMIN

    ????: 0x0000

    RID: 01F4

    Groupname: DOMAIN_USER_RID_GUEST

    ????: 0x0000

    RID: 01F5

    Well-known RID groups

    Groupname: DOMAIN_GROUP_RID_ADMINS

    ????: 0x0000

    RID: 0200

    Groupname: DOMAIN_GROUP_RID_USERS

    ????: 0x0000

    RID: 0201

    Groupname: DOMAIN_GROUP_RID_GUESTS

    ????: 0x0000

    RID: 0202

    Well-known RID aliases

    Groupname: DOMAIN_ALIAS_RID_ADMINS

    ????: 0x0000

    RID: 0220

    Groupname: DOMAIN_ALIAS_RID_USERS

    ????: 0x0000

    RID: 0221

    Groupname: DOMAIN_ALIAS_RID_GUESTS

    ????: 0x0000

    RID: 0222

    Groupname: DOMAIN_ALIAS_RID_POWER_USERS

    ????: 0x0000

    RID: 0223

    Groupname: DOMAIN_ALIAS_RID_ACCOUNT_OPS

    ????: 0x0000

    RID: 0224

    Groupname: DOMAIN_ALIAS_RID_SYSTEM_OPS

    ????: 0x0000

    RID: 0225

    Groupname: DOMAIN_ALIAS_RID_PRINT_OPS

    ????: 0x0000

    RID: 0226

    Groupname: DOMAIN_ALIAS_RID_BACKUP_OPS

    ????: 0x0000

    RID: 0227

    Groupname: DOMAIN_ALIAS_RID_REPLICATOR

    ????: 0x0000

    RID: 0228

    Chapter10.Samba Printing Internals

    Gerald Carter

    October 2002

    Table of Contents

    Abstract
    +Printing Interface to Various Back ends +
    +Print Queue TDB's +
    +ChangeID and Client Caching of Printer Information +
    +Windows NT/2K Printer Change Notify +

    Abstract

    +The purpose of this document is to provide some insight into Samba's printing functionality and also to describe the semantics -of certain features of Windows client printing.

    10.2. Printing Interface to Various Back ends

    Samba uses a table of function pointers to seven functions. The -function prototypes are defined in the printif structure declared -in printing.h.

    • retrieve the contents of a print queue

    • pause the print queue

    • resume a paused print queue

    • delete a job from the queue

    • pause a job in the print queue

    • result a paused print job in the queue

    • submit a job to the print queue

    Currently there are only two printing back end implementations -defined.

    • a generic set of functions for working with standard UNIX - printing subsystems

    • a set of CUPS specific functions (this is only enabled if - the CUPS libraries were located at compile time).

    10.3. Print Queue TDB's

    Samba provides periodic caching of the output from the "lpq command" +of certain features of Windows client printing. +

    +Printing Interface to Various Back ends +

    +Samba uses a table of function pointers to seven functions. The +function prototypes are defined in the printif structure declared +in printing.h. +

    • retrieve the contents of a print queue

    • pause the print queue

    • resume a paused print queue

    • delete a job from the queue

    • pause a job in the print queue

    • result a paused print job in the queue

    • submit a job to the print queue

    +Currently there are only two printing back end implementations +defined. +

    • a generic set of functions for working with standard UNIX + printing subsystems

    • a set of CUPS specific functions (this is only enabled if + the CUPS libraries were located at compile time).

    +Print Queue TDB's +

    +Samba provides periodic caching of the output from the "lpq command" for performance reasons. This cache time is configurable in seconds. Obviously the longer the cache time the less often smbd will be required to exec a copy of lpq. However, the accuracy of the print -queue contents displayed to clients will be diminished as well.

    The list of currently opened print queue TDB's can be found +queue contents displayed to clients will be diminished as well. +

    +The list of currently opened print queue TDB's can be found be examining the list of tdb_print_db structures ( see print_db_head in printing.c ). A queue TDB is opened using the wrapper function printing.c:get_print_db_byname(). The function ensures that smbd @@ -8322,17 +1416,15 @@ does not open more than MAX_PRINT_DBS_OPEN in an effort to prevent a large print server from exhausting all available file descriptors. If the number of open queue TDB's exceeds the MAX_PRINT_DBS_OPEN limit, smbd falls back to a most recently used algorithm for maintaining -a list of open TDB's.

    There are two ways in which a a print job can be entered into +a list of open TDB's. +

    +There are two ways in which a a print job can be entered into a print queue's TDB. The first is to submit the job from a Windows client which will insert the job information directly into the TDB. The second method is to have the print job picked up by executing the -"lpq command".

    /* included from printing.h */
+"lpq command".
+
    +/* included from printing.h */
 struct printjob {
 	pid_t pid; /* which process launched the job */
 	int sysjob; /* the system (lp) job number */
@@ -8348,61 +1440,28 @@ struct printjob {
 	fstring user; /* the user who started the job */
 	fstring queuename; /* service number of printer for this job */
 	NT_DEVICEMODE *nt_devmode;
-};
    The current manifestation of the printjob structure contains a field
-for the UNIX job id returned from the "lpq command" and a Windows job
+};
+

    +The current manifestation of the printjob structure contains a field +for the UNIX job id returned from the "lpq command" and a Windows job ID (32-bit bounded by PRINT_MAX_JOBID). When a print job is returned -by the "lpq command" that does not match an existing job in the queue's -TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to -the id reported by lpq.

    In order to match a 32-bit Windows jobid onto a 16-bit lanman print job +by the "lpq command" that does not match an existing job in the queue's +TDB, a 32-bit job ID above the <*vance doesn't know what word is missing here*> is generating by adding UNIX_JOB_START to +the id reported by lpq. +

    +In order to match a 32-bit Windows jobid onto a 16-bit lanman print job id, smbd uses an in memory TDB to match the former to a number appropriate -for old lanman clients.

    When updating a print queue, smbd will perform the following -steps ( refer to print.c:print_queue_update() ):

    1. Check to see if another smbd is currently in +for old lanman clients. +

      +When updating a print queue, smbd will perform the following +steps ( refer to print.c:print_queue_update() ): +

      1. Check to see if another smbd is currently in the process of updating the queue contents by checking the pid - stored in LOCK/printer_name. - If so, then do not update the TDB.

      2. Lock the mutex entry in the TDB and store our own pid. - Check that this succeeded, else fail.

      3. Store the updated time stamp for the new cache - listing

      4. Retrieve the queue listing via "lpq command"

      5. 	foreach job in the queue
+	stored in LOCK/printer_name.  
+	If so, then do not update the TDB.

      6. Lock the mutex entry in the TDB and store our own pid. + Check that this succeeded, else fail.

      7. Store the updated time stamp for the new cache + listing

      8. Retrieve the queue listing via "lpq command"

      9. +	foreach job in the queue
      	{
 		if the job is a UNIX job, create a new entry;
 		if the job has a Windows based jobid, then
@@ -8413,119 +1472,51 @@ CLASS="PROGRAMLISTING"
 			else
 				update the job status only
 		}
-	}

      10. Delete any jobs in the TDB that are not - in the in the lpq listing

      11. Store the print queue status in the TDB

      12. update the cache time stamp again

      Note that it is the contents of this TDB that is returned to Windows -clients and not the actual listing from the "lpq command".

      The NT_DEVICEMODE stored as part of the printjob structure is used to + }

    2. Delete any jobs in the TDB that are not + in the in the lpq listing

    3. Store the print queue status in the TDB

    4. update the cache time stamp again

    +Note that it is the contents of this TDB that is returned to Windows +clients and not the actual listing from the "lpq command". +

    +The NT_DEVICEMODE stored as part of the printjob structure is used to store a pointer to a non-default DeviceMode associated with the print job. The pointer will be non-null when the client included a Device Mode in the OpenPrinterEx() call and subsequently submitted a job for printing on that same handle. If the client did not include a Device Mode in the OpenPrinterEx() request, the nt_devmode field is NULL -and the job has the printer's device mode associated with it by default.

    Only non-default Device Mode are stored with print jobs in the print +and the job has the printer's device mode associated with it by default. +

    +Only non-default Device Mode are stored with print jobs in the print queue TDB. Otherwise, the Device Mode is obtained from the printer -object when the client issues a GetJob(level == 2) request.

    10.5. Windows NT/2K Printer Change Notify

    When working with Windows NT+ clients, it is possible for a +object when the client issues a GetJob(level == 2) request. +

    +ChangeID and Client Caching of Printer Information +

    +[To be filled in later] +

    +Windows NT/2K Printer Change Notify +

    +When working with Windows NT+ clients, it is possible for a print server to use RPC to send asynchronous change notification events to clients for certain printer and print job attributes. This can be useful when the client needs to know that a new job has been added to the queue for a given printer or that the driver for a printer has been changed. Note that this is done entirely orthogonal to cache updates based on a new ChangeID for -a printer object.

    The basic set of RPC's used to implement change notification are

    • RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )

    • RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )

    • FindClosePrinterChangeNotify( FCPCN )

    • ReplyOpenPrinter

    • ReplyClosePrinter

    • RouteRefreshPrinterChangeNotify ( RRPCN )

    One additional RPC is available to a server, but is never used by the -Windows spooler service:

    • RouteReplyPrinter()

    The opnum for all of these RPC's are defined in include/rpc_spoolss.h

    Windows NT print servers use a bizarre method of sending print +a printer object. +

    +The basic set of RPC's used to implement change notification are +

    • RemoteFindFirstPrinterChangeNotifyEx ( RFFPCN )

    • RemoteFindNextPrinterChangeNotifyEx ( RFNPCN )

    • FindClosePrinterChangeNotify( FCPCN )

    • ReplyOpenPrinter

    • ReplyClosePrinter

    • RouteRefreshPrinterChangeNotify ( RRPCN )

    +One additional RPC is available to a server, but is never used by the +Windows spooler service: +

    • RouteReplyPrinter()

    +The opnum for all of these RPC's are defined in include/rpc_spoolss.h +

    +Windows NT print servers use a bizarre method of sending print notification event to clients. The process of registering a new change notification handle is as follows. The 'C' is for client and the -'S' is for server. All error conditions have been eliminated.

    C:	Obtain handle to printer or to the printer
+'S' is for server.  All error conditions have been eliminated.
+
    +C:	Obtain handle to printer or to the printer
 	server via the standard OpenPrinterEx() call.
 S:	Respond with a valid handle to object
 
@@ -8534,7 +1525,7 @@ C:	Send a RFFPCN request with the previously obtained
 	to monitor, or (b) a PRINTER_NOTIFY_OPTIONS structure
 	containing the event information to monitor.  The windows
 	spooler has only been observed to use (b).
-S:	The <* another missing word*> opens a new TCP session to the client (thus requiring
+S:	The <* another missing word*> opens a new TCP session to the client (thus requiring
 	all print clients to be CIFS servers as well) and sends
 	a ReplyOpenPrinter() request to the client.
 C:	The client responds with a printer handle that can be used to
@@ -8555,452 +1546,229 @@ C:	If the change notification handle is ever released by the
 	or a piece of data was wrong.
 S:	The server closes the internal change notification handle
 	(POLICY_HND) and does not send any further change notification
-	events to the client for that printer or job.
    The current list of notification events supported by Samba can be
-found by examining the internal tables in srv_spoolss_nt.c
    • printer_notify_table[]
    • job_notify_table[]
    When an event occurs that could be monitored, smbd sends a message
+	events to the client for that printer or job.
+

    +The current list of notification events supported by Samba can be +found by examining the internal tables in srv_spoolss_nt.c +

    • printer_notify_table[]

    • job_notify_table[]

    +When an event occurs that could be monitored, smbd sends a message to itself about the change. The list of events to be transmitted are queued by the smbd process sending the message to prevent an overload of TDB usage and the internal message is sent during smbd's idle loop (refer to printing/notify.c and the functions -send_spoolss_notify2_msg() and print_notify_send_messages() ).

    The decision of whether or not the change is to be sent to connected +send_spoolss_notify2_msg() and print_notify_send_messages() ). +

    +The decision of whether or not the change is to be sent to connected clients is made by the routine which actually sends the notification. -( refer to srv_spoolss_nt.c:recieve_notify2_message() ).

    Because it possible to receive a listing of multiple changes for +( refer to srv_spoolss_nt.c:recieve_notify2_message() ). +

    +Because it possible to receive a listing of multiple changes for multiple printers, the notification events must be split into categories by the printer name. This makes it possible to group multiple change events to be sent in a single RPC according to the -printer handle obtained via a ReplyOpenPrinter().

    The actual change notification is performed using the RRPCN request -RPC. This packet contains

    • the printer handle registered with the -client's spooler on which the change occurred

    • The change_low value which was sent as part -of the last RFNPCN request from the client

    • The SPOOL_NOTIFY_INFO container with the event -information

    A SPOOL_NOTIFY_INFO contains:

    • the version and flags field are predefined -and should not be changed

    • The count field is the number of entries -in the SPOOL_NOTIFY_INFO_DATA array

    The SPOOL_NOTIFY_INFO_DATA entries contain:

    • The type defines whether or not this event -is for a printer or a print job

    • The field is the flag identifying the event

    • the notify_data union contains the new valuie of the -attribute

    • The enc_type defines the size of the structure for marshalling -and unmarshalling

    • (a) the id must be 0 for a printer event on a printer handle. +printer handle obtained via a ReplyOpenPrinter(). +

      +The actual change notification is performed using the RRPCN request +RPC. This packet contains +

      • the printer handle registered with the +client's spooler on which the change occurred

      • The change_low value which was sent as part +of the last RFNPCN request from the client

      • The SPOOL_NOTIFY_INFO container with the event +information

      +A SPOOL_NOTIFY_INFO contains: +

      • the version and flags field are predefined +and should not be changed

      • The count field is the number of entries +in the SPOOL_NOTIFY_INFO_DATA array

      +The SPOOL_NOTIFY_INFO_DATA entries contain: +

      • The type defines whether or not this event +is for a printer or a print job

      • The field is the flag identifying the event

      • the notify_data union contains the new valuie of the +attribute

      • The enc_type defines the size of the structure for marshalling +and unmarshalling

      • (a) the id must be 0 for a printer event on a printer handle. (b) the id must be the job id for an event on a printer job (c) the id must be the matching number of the printer index used in the response packet to the RFNPCN when using a print server handle for notification. Samba currently uses the snum of the printer for this which can break if the list of services -has been modified since the notification handle was registered.

      • The size is either (a) the string length in UNICODE for strings, +has been modified since the notification handle was registered.

      • The size is either (a) the string length in UNICODE for strings, (b) the size in bytes of the security descriptor, or (c) 0 for -data values.

    Chapter 11. Samba WINS Internals

    11.1. WINS Failover

    The current Samba codebase possesses the capability to use groups of WINS +data values.

    Chapter11.Samba WINS Internals

    Gerald Carter

    October 2002

    Table of Contents

    WINS Failover

    WINS Failover

    +The current Samba codebase possesses the capability to use groups of WINS servers that share a common namespace for NetBIOS name registration and -resolution. The formal parameter syntax is

    	WINS_SERVER_PARAM 	= SERVER [ SEPARATOR SERVER_LIST ]
-	WINS_SERVER_PARAM 	= "wins server"
+resolution.  The formal parameter syntax is
+
    +	WINS_SERVER_PARAM 	= SERVER [ SEPARATOR SERVER_LIST ]
+	WINS_SERVER_PARAM 	= "wins server"
 	SERVER 			= ADDR[:TAG]
 	ADDR 			= ip_addr | fqdn
 	TAG 			= string
 	SEPARATOR		= comma | \s+
-	SERVER_LIST		= SERVER [ SEPARATOR SERVER_LIST ]
    A simple example of a valid wins server setting is
    [global]
-	wins server = 192.168.1.2 192.168.1.3
    In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default
-TAG of "*".  A TAG is used to group servers of a shared NetBIOS namespace together.  Upon
+	SERVER_LIST		= SERVER [ SEPARATOR SERVER_LIST ]
+

    +A simple example of a valid wins server setting is +

    +[global]
+	wins server = 192.168.1.2 192.168.1.3
+

    +In the event that no TAG is defined in for a SERVER in the list, smbd assigns a default +TAG of "*". A TAG is used to group servers of a shared NetBIOS namespace together. Upon startup, nmbd will attempt to register the netbios name value with one server in each -tagged group.

    An example using tags to group WINS servers together is show here. Note that the use of -interface names in the tags is only by convention and is not a technical requirement.

    [global]
-	wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1

    Using this configuration, nmbd would attempt to register the server's NetBIOS name -with one WINS server in each group. Because the "eth0" group has two servers, the +tagged group. +

    +An example using tags to group WINS servers together is show here. Note that the use of +interface names in the tags is only by convention and is not a technical requirement. +

    +[global]
+	wins server = 192.168.1.2:eth0 192.168.1.3:eth0 192.168.2.2:eth1
+

    +Using this configuration, nmbd would attempt to register the server's NetBIOS name +with one WINS server in each group. Because the "eth0" group has two servers, the second server would only be used when a registration (or resolution) request to -the first server in that group timed out.

    NetBIOS name resolution follows a similar pattern as name registration. When resolving +the first server in that group timed out. +

    +NetBIOS name resolution follows a similar pattern as name registration. When resolving a NetBIOS name via WINS, smbd and other Samba programs will attempt to query a single WINS server in a tagged group until either a positive response is obtained at least once or until a server from every tagged group has responded negatively to the name query request. If a timeout occurs when querying a specific WINS server, that server is marked as down to prevent further timeouts and the next server in the WINS group is contacted. Once marked as dead, Samba will not attempt to contact that server for name registration/resolution queries -for a period of 10 minutes.

    Chapter 12. The Upcoming SAM System

    12.1. Security in the 'new SAM'

    One of the biggest problems with passdb is it's implementation of +for a period of 10 minutes. +

    Chapter12.The Upcoming SAM System

    Andrew Bartlett

    1 October 2002

    Table of Contents

    Security in the 'new SAM'
    Standalone from UNIX
    Handles and Races in the new SAM
    Layers
    Application
    SAM Interface
    SAM Modules
    SAM Modules
    Special Module: sam_passdb
    sam_ads
    Memory Management
    Testing

    Security in the 'new SAM'

    One of the biggest problems with passdb is it's implementation of 'security'. Access control is on a 'are you root at the moment' basis, and it has no concept of NT ACLs. Things like ldapsam had to add -'magic' 'are you root' checks.

    We took this very seriously when we started work, and the new structure +'magic' 'are you root' checks.

    We took this very seriously when we started work, and the new structure is designed with this in mind, from the ground up. Each call to the SAM has a NT_TOKEN and (if relevant) an 'access desired'. This is either provided as a parameter, or implicitly supplied by the object being -accessed.

    For example, when you call 

    NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
+accessed.
    
+For example, when you call 
+
    +NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
 NT_USER_TOKEN *access_token, uint32 access_desired, const char *domain,
-const char *name, SAM_ACCOUNT_HANDLE **account)
    The context can be NULL (and is used to allow import/export by setting
-up 2 contexts, and allowing calls on both simultaneously)
    The access token *must* be specified.  Normally the user's token out of
-current_user, this can also be a global 'system' context.
    The access desired is as per the ACL, for passing to the seaccess stuff.
    The domain/username are standard.  Even if we only have one domain,
+const char *name, SAM_ACCOUNT_HANDLE **account)
+

    +The context can be NULL (and is used to allow import/export by setting +up 2 contexts, and allowing calls on both simultaneously) +

    +The access token *must* be specified. Normally the user's token out of +current_user, this can also be a global 'system' context. +

    +The access desired is as per the ACL, for passing to the seaccess stuff. +

    +The domain/username are standard. Even if we only have one domain, keeping this ensures that we don't get 'unqualified' usernames (same -problem as we had with unqualified SIDs).

    We return a 'handle'. This is opaque to the rest of Samba, but is -operated on by get/set routines, all of which return NTSTATUS.

    The access checking is done by the SAM module. The reason it is not +problem as we had with unqualified SIDs). +

    +We return a 'handle'. This is opaque to the rest of Samba, but is +operated on by get/set routines, all of which return NTSTATUS. +

    +The access checking is done by the SAM module. The reason it is not done 'above' the interface is to ensure a 'choke point'. I put a lot of effort into the auth subsystem to ensure we never 'accidentally' forgot to check for null passwords, missed a restriction etc. I intend the SAM -to be written with the same caution.

    The reason the access checking is not handled by the interface itself is +to be written with the same caution. +

    +The reason the access checking is not handled by the interface itself is due to the different implementations it make take on. For example, on ADS, you cannot set a password over a non-SSL connection. Other backends may have similar requirements - we need to leave this policy up to the modules. They will naturally have access to 'helper' procedures -and good examples to avoid mishaps.

    (Furthermore, some backends my actually chose to push the whole ACL +and good examples to avoid mishaps. +

    +(Furthermore, some backends my actually chose to push the whole ACL issue to the remote server, and - assuming ldap for this example - bind -as the user directly)

    Each returned handle has an internal 'access permitted', which allows +as the user directly) +

    +Each returned handle has an internal 'access permitted', which allows the 'get' and 'set' routines to return 'ACCESS_DENIED' for things that were not able to be retrieved from the backend. This removes the need to specify the NT_TOKEN on every operation, and allows for 'object not -present' to be easily distinguished from 'access denied'.

    When you 'set' an object (calling sam_update_account) the internal +present' to be easily distinguished from 'access denied'. +

    +When you 'set' an object (calling sam_update_account) the internal details are again used. Each change that has been made to the object has been flagged, so as to avoid race conditions (on unmodified components) and to avoid violating any extra ACL requirements on the -actual data store (like the LDAP server).

    Finally, we have generic get_sec_desc() and set_sec_desc() routines to -allow external ACL manipulation. These do lookups based on SID.

    12.2. Standalone from UNIX

    One of the primary tenants of the 'new SAM' is that it would not attempt +actual data store (like the LDAP server). +

    +Finally, we have generic get_sec_desc() and set_sec_desc() routines to +allow external ACL manipulation. These do lookups based on SID. +

    Standalone from UNIX

    +One of the primary tenants of the 'new SAM' is that it would not attempt to deal with 'what unix id for that'. This would be left to the 'SMS' (Sid Mapping System') or SID farm, and probably administered via winbind. We have had constructive discussion on how 'basic' unix accounts like 'root' would be handled, and we think this can work. -Accounts not preexisting in unix would be served up via winbind.

    This is an *optional* part, and my preferred end-game. We have a fare -way to go before things like winbind up to it however.

    12.3. Handles and Races in the new SAM

    One of the things that the 'new SAM' work has tried to face is both +Accounts not preexisting in unix would be served up via winbind. +

    +This is an *optional* part, and my preferred end-game. We have a fare +way to go before things like winbind up to it however. +

    Handles and Races in the new SAM

    +One of the things that the 'new SAM' work has tried to face is both compatibility with existing code, and a closer alignment to the SAMR interface. I consider SAMR to be a 'primary customer' to the this work, because if we get alignment with that wrong, things get more, rather than less complex. Also, most other parts of Samba are much more -flexible with what they can allow.

    In any case, that was a decision taken as to how the general design -would progress. BTW, my understanding of SAMR may be completely flawed.

    One of the most race-prone areas of the new code is the conflicting -update problem. We have taken two approaches:

    • 'Not conflicting' conflicts. Due to the way usrmgr operates, it will +flexible with what they can allow. +

      +In any case, that was a decision taken as to how the general design +would progress. BTW, my understanding of SAMR may be completely flawed. +

      +One of the most race-prone areas of the new code is the conflicting +update problem. We have taken two approaches: +

      • 'Not conflicting' conflicts. Due to the way usrmgr operates, it will open a user, display all the properties and *save* them all, even if you -don't change any.

        For this, see what I've done in rpc_server/srv_samr_util.c. I intend +don't change any. +

        +For this, see what I've done in rpc_server/srv_samr_util.c. I intend to take this one step further, and operate on the 'handle' that the values were read from. This should mean that we only update things that -have *really* changed.

      • 'conflicting' updates: Currently we don't deal with this (in passdb +have *really* changed. +

      • +'conflicting' updates: Currently we don't deal with this (in passdb or the new sam stuff), but the design is sufficiently flexible to 'deny' -a second update. I don't foresee locking records however.

      12.4. Layers

      12.4.1. Application

      This is where smbd, samtest and whatever end-user replacement we have +a second update. I don't foresee locking records however. +

    Layers

    Application

    +This is where smbd, samtest and whatever end-user replacement we have for pdbedit sits. They use only the SAM interface, and do not get -'special knowledge' of what is below them.

    12.4.2. SAM Interface

    This level 'owns' the various handle structures, the get/set routines on +'special knowledge' of what is below them. +

    SAM Interface

    +This level 'owns' the various handle structures, the get/set routines on those structures and provides the public interface. The application layer may initialize a 'context' to be passed to all interface routines, else a default, self-initialising context will be supplied. This layser finds the appropriate backend module for the task, and tries very hard not to need to much 'knowledge'. It should just provide the required -abstraction to the modules below, and arrange for their initial loading.

    We could possibly add ACL checking at this layer, to avoid discrepancies -in implementation modules.

    12.4.3. SAM Modules

    These do not communicate with the application directly, only by setting +abstraction to the modules below, and arrange for their initial loading. +

    +We could possibly add ACL checking at this layer, to avoid discrepancies +in implementation modules. +

    SAM Modules

    +These do not communicate with the application directly, only by setting values in the handles, and receiving requests from the interface. These modules are responsible for translating values from the handle's .private into (say) an LDAP modification list. The module is expected to 'know' things like it's own domain SID, domain name, and any other state attached to the SAM. Simpler modules may call back to some helper -routine.

    12.5. SAM Modules

    12.5.1. Special Module: sam_passdb

    In order for there to be a smooth transition, kai is writing a module +routine. +

    SAM Modules

    Special Module: sam_passdb

    +In order for there to be a smooth transition, kai is writing a module that reads existing passdb backends, and translates them into SAM replies. (Also pulling data from the account policy DB etc). We also intend to write a module that does the reverse - gives the SAM a passdb -interface.

    12.5.2. sam_ads

    This is the first of the SAM modules to be committed to the tree - +interface. +

    sam_ads

    +This is the first of the SAM modules to be committed to the tree - mainly because I needed to coordinate work with metze (who authored most of it). This module aims to use Samba's libads code to provide an Active Directory LDAP client, suitable for use on a mixed-mode DC. While it is currently being tested against Win2k servers (with a password in the smb.conf file) it is expected to eventually use a (possibly modified) OpenLDAP server. We hope that this will assist in -the construction of an Samba AD DC.

    We also intend to construct a Samba 2.2/3.0 compatible ldap module, -again using libads code.

    12.6. Memory Management

    +the construction of an Samba AD DC. +

    +We also intend to construct a Samba 2.2/3.0 compatible ldap module, +again using libads code. +

    Memory Management

    The 'new SAM' development effort also concerned itself with getting a sane implementation of memory management. It was decided that we would be (as much as possible) talloc based, using an 'internal talloc @@ -9008,132 +1776,63 @@ context' on many objects. That is, the creation of an object would initiate it's own internal talloc context, and this would be used for all operations on that object. Much of this is already implemented in passdb. Also, like passdb, it will be possible to specify that some -object actually be created on a specified context.

    Memory management is important here because the APIs in the 'new SAM' do +object actually be created on a specified context. +

    +Memory management is important here because the APIs in the 'new SAM' do not use 'pdb_init()' or an equivalent. They always allocate new objects. Enumeration's are slightly different, and occur on a supplied context that 'owns' the entire list, rather than per-element. (the enumeration functions return an array of all elements - not full handles just basic (and public) info) Likewise for things that fill in a char -**.

    For example:

    NTSTATUS sam_lookup_sid(const SAM_CONTEXT *context, const NT_USER_TOKEN
+**.
+
    For example:
    +NTSTATUS sam_lookup_sid(const SAM_CONTEXT *context, const NT_USER_TOKEN
 *access_token, TALLOC_CTX *mem_ctx, const DOM_SID *sid, char **name,
-uint32 *type)
    Takes a context to allocate the 'name' on, while:
    NTSTATUS sam_get_account_by_sid(const SAM_CONTEXT *context, const
+uint32 *type)
+
    Takes a context to allocate the 'name' on, while:
    +NTSTATUS sam_get_account_by_sid(const SAM_CONTEXT *context, const
 NT_USER_TOKEN *access_token, uint32 access_desired, const DOM_SID
-*accountsid, SAM_ACCOUNT_HANDLE **account)
    Allocates a handle and stores the allocation context on that handle.
    I think that the following:
    NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const
+*accountsid, SAM_ACCOUNT_HANDLE **account)
+
    Allocates a handle and stores the allocation context on that handle.
    I think that the following:
    +NTSTATUS sam_enum_accounts(const SAM_CONTEXT *context, const
 NT_USER_TOKEN *access_token, const DOM_SID *domainsid, uint16 acct_ctrl,
-int32 *account_count, SAM_ACCOUNT_ENUM **accounts)

    12.7. Testing

    Testing is vital in any piece of software, and Samba is certainly no +int32 *account_count, SAM_ACCOUNT_ENUM **accounts) +

    Testing

    +Testing is vital in any piece of software, and Samba is certainly no exception. In designing this new subsystem, we have taken care to ensure -it is easily tested, independent of outside protocols.

    To this end, Jelmer has constructed 'samtest'.

    This utility (see torture/samtest.c) is structured like rpcclient, but +it is easily tested, independent of outside protocols. +

    +To this end, Jelmer has constructed 'samtest'. +

    +This utility (see torture/samtest.c) is structured like rpcclient, but instead operates on the SAM subsystem. It creates a 'custom' SAM context, that may be distinct from the default values used by the rest -of the system, and can load a separate configuration file.

    A small number of commands are currently implemented, but these have +of the system, and can load a separate configuration file. +

    +A small number of commands are currently implemented, but these have already proved vital in testing. I expect SAM module authors will find -it particularly valuable.

    Example useage:

    $ bin/samtest

    > context ads:ldap://192.168.1.96
    +it particularly valuable. +

    Example useage:

    $ bin/samtest

    +> context ads:ldap://192.168.1.96
+

    (this loads a new context, using the new ADS module. The parameter is -the 'location' of the ldap server)

    > lookup_name DOMAIN abartlet
    -(returns a sid).

    Because the 'new SAM' is NT ACL based, there will be a command to -specify an arbitrary NT ACL, but for now it uses 'system' by default.

    Chapter 13. LanMan and NT Password Encryption

    13.1. Introduction

    With the development of LanManager and Windows NT +the 'location' of the ldap server) +

    +> lookup_name DOMAIN abartlet
+

    +(returns a sid). +

    +Because the 'new SAM' is NT ACL based, there will be a command to +specify an arbitrary NT ACL, but for now it uses 'system' by default. +

    Chapter13.LanMan and NT Password Encryption

    Jeremy Allison

    Samba Team


    + <samba@samba.org>
    +

    19 Apr 1999

    Table of Contents

    Introduction
    How does it work?
    The smbpasswd file

    Introduction

    With the development of LanManager and Windows NT compatible password encryption for Samba, it is now able to validate user connections in exactly the same way as - a LanManager or Windows NT server.

    This document describes how the SMB password encryption + a LanManager or Windows NT server.

    This document describes how the SMB password encryption algorithm works and what issues there are in choosing whether you want to use it. You should read it carefully, especially - the part about security and the "PROS and CONS" section.

    13.2. How does it work?

    LanManager encryption is somewhat similar to UNIX + the part about security and the "PROS and CONS" section.

    How does it work?

    LanManager encryption is somewhat similar to UNIX password encryption. The server uses a file containing a hashed value of a user's password. This is created by taking the user's plaintext password, capitalising it, and either @@ -9141,619 +1840,190 @@ NAME="AEN3151" This 14 byte value is used as two 56 bit DES keys to encrypt a 'magic' eight byte value, forming a 16 byte value which is stored by the server and client. Let this value be known as - the "hashed password".

    Windows NT encryption is a higher quality mechanism, + the "hashed password".

    Windows NT encryption is a higher quality mechanism, consisting of doing an MD4 hash on a Unicode version of the user's password. This also produces a 16 byte hash value that is - non-reversible.

    When a client (LanManager, Windows for WorkGroups, Windows + non-reversible.

    When a client (LanManager, Windows for WorkGroups, Windows 95 or Windows NT) wishes to mount a Samba drive (or use a Samba resource), it first requests a connection and negotiates the protocol that the client and server will use. In the reply to this request the Samba server generates and appends an 8 byte, random value - this is stored in the Samba server after the reply is sent - and is known as the "challenge". The challenge is different for - every client connection.

    The client then uses the hashed password (16 byte values + and is known as the "challenge". The challenge is different for + every client connection.

    The client then uses the hashed password (16 byte values described above), appended with 5 null bytes, as three 56 bit DES keys, each of which is used to encrypt the challenge 8 byte - value, forming a 24 byte value known as the "response".

    In the SMB call SMBsessionsetupX (when user level security + value, forming a 24 byte value known as the "response".

    In the SMB call SMBsessionsetupX (when user level security is selected) or the call SMBtconX (when share level security is selected), the 24 byte response is returned by the client to the Samba server. For Windows NT protocol levels the above calculation is done on both hashes of the user's password and both responses are - returned in the SMB call, giving two 24 byte values.

    The Samba server then reproduces the above calculation, using + returned in the SMB call, giving two 24 byte values.

    The Samba server then reproduces the above calculation, using its own stored value of the 16 byte hashed password (read from the - smbpasswd file - described later) and the challenge + smbpasswd file - described later) and the challenge value that it kept from the negotiate protocol reply. It then checks to see if the 24 byte value it calculates matches the 24 byte value - returned to it from the client.

    If these values match exactly, then the client knew the + returned to it from the client.

    If these values match exactly, then the client knew the correct password (or the 16 byte hashed value - see security note below) and is thus allowed access. If not, then the client did not - know the correct password and is denied access.

    Note that the Samba server never knows or stores the cleartext + know the correct password and is denied access.

    Note that the Samba server never knows or stores the cleartext of the user's password - just the 16 byte hashed values derived from it. Also note that the cleartext password or 16 byte hashed values - are never transmitted over the network - thus increasing security.

    13.3. >The smbpasswd file

    In order for Samba to participate in the above protocol + are never transmitted over the network - thus increasing security.

    The smbpasswd file

    In order for Samba to participate in the above protocol it must be able to look up the 16 byte hashed values given a user name. Unfortunately, as the UNIX password value is also a one way hash function (ie. it is impossible to retrieve the cleartext of the user's password given the UNIX hash of it), a separate password file containing this 16 byte value must be kept. To minimise problems with - these two password files, getting out of sync, the UNIX /etc/passwd and the smbpasswd file, - a utility, mksmbpasswd.sh, is provided to generate - a smbpasswd file from a UNIX /etc/passwd file. -

    To generate the smbpasswd file from your /etc/passwd - file use the following command:

    $ cat /etc/passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd

    If you are running on a system that uses NIS, use

    $ ypcat passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd

    The mksmbpasswd.sh program is found in + these two password files, getting out of sync, the UNIX + /etc/passwd and the smbpasswd file, + a utility, mksmbpasswd.sh, is provided to generate + a smbpasswd file from a UNIX /etc/passwd file. +

    To generate the smbpasswd file from your /etc/passwd + file use the following command:

    $ cat /etc/passwd | mksmbpasswd.sh + > /usr/local/samba/private/smbpasswd

    If you are running on a system that uses NIS, use

    $ ypcat passwd | mksmbpasswd.sh + > /usr/local/samba/private/smbpasswd

    The mksmbpasswd.sh program is found in the Samba source directory. By default, the smbpasswd file is - stored in :

    /usr/local/samba/private/smbpasswd

    The owner of the /usr/local/samba/private/ + stored in :

    /usr/local/samba/private/smbpasswd

    The owner of the /usr/local/samba/private/ directory should be set to root, and the permissions on it should - be set to 0500 (chmod 500 /usr/local/samba/private). -

    Likewise, the smbpasswd file inside the private directory should + be set to 0500 (chmod 500 /usr/local/samba/private). +

    Likewise, the smbpasswd file inside the private directory should be owned by root and the permissions on is should be set to 0600 - (chmod 600 smbpasswd).

    The format of the smbpasswd file is (The line has been + (chmod 600 smbpasswd).

    The format of the smbpasswd file is (The line has been wrapped here. It should appear as one entry per line in - your smbpasswd file.)

    username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
-	[Account type]:LCT-<last-change-time>:Long name
-

    Although only the username, - uid, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, - [Account type] and last-change-time sections are significant - and are looked at in the Samba code.

    It is VITALLY important that there by 32 + your smbpasswd file.)

    +username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+	[Account type]:LCT-<last-change-time>:Long name
+

    Although only the username, + uid, + XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX, + [Account type] and + last-change-time sections are significant + and are looked at in the Samba code.

    It is VITALLY important that there by 32 'X' characters between the two ':' characters in the XXX sections - the smbpasswd and Samba code will fail to validate any entries that do not have 32 characters between ':' characters. The first XXX section is for the Lanman password hash, the second is for the - Windows NT version.

    When the password file is created all users have password entries + Windows NT version.

    When the password file is created all users have password entries consisting of 32 'X' characters. By default this disallows any access as this user. When a user has a password set, the 'X' characters change to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii - representation of the 16 byte hashed value of a user's password.

    To set a user to have no password (not recommended), edit the file + representation of the 16 byte hashed value of a user's password.

    To set a user to have no password (not recommended), edit the file using vi, and replace the first 11 characters with the ascii text - "NO PASSWORD" (minus the quotes).

    For example, to clear the password for user bob, his smbpasswd file - entry would look like :

    	bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
-

    If you are allowing users to use the smbpasswd command to set + "NO PASSWORD" (minus the quotes).

    For example, to clear the password for user bob, his smbpasswd file + entry would look like :

    +bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
+	[U          ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
+

    If you are allowing users to use the smbpasswd command to set their own passwords, you may want to give users NO PASSWORD initially so they do not have to enter a previous password when changing to their new password (not recommended). In order for you to allow this the - smbpasswd program must be able to connect to the - smbd daemon as that user with no password. Enable this - by adding the line :

    null passwords = yes

    to the [global] section of the smb.conf file (this is why + smbpasswd program must be able to connect to the + smbd daemon as that user with no password. Enable this + by adding the line :

    null passwords = yes

    to the [global] section of the smb.conf file (this is why the above scenario is not recommended). Preferably, allocate your users a default password to begin with, so you do not have - to enable this on your server.

    Note : This file should be protected very + to enable this on your server.

    Note : This file should be protected very carefully. Anyone with access to this file can (with enough knowledge of the protocols) gain access to your SMB server. The file is thus more - sensitive than a normal unix /etc/passwd file.

    Chapter 14. Modules

    14.1. Advantages

    The new modules system has the following advantages:

    Transparent loading of static and shared modules (no need -for a subsystem to know about modules)
    Simple selection between shared and static modules at configure time
    "preload modules" option for increasing performance for stable modules
    No nasty #define stuff anymore
    All backends are available as plugin now (including pdb_ldap and pdb_tdb)

    14.2. Loading modules

    Some subsystems in samba use different backends. These backends can be + sensitive than a normal unix /etc/passwd file.

    Chapter14.Modules

    Jelmer Vernooij

    Samba Team

    <jelmer@samba.org>

    19 March 2003

    Table of Contents

    Advantages
    Loading modules
    Static modules
    Shared modules
    Writing modules
    Static/Shared selection in configure.in

    Advantages

    +The new modules system has the following advantages: +

    Transparent loading of static and shared modules (no need +for a subsystem to know about modules)
    Simple selection between shared and static modules at configure time
    "preload modules" option for increasing performance for stable modules
    No nasty #define stuff anymore
    All backends are available as plugin now (including pdb_ldap and pdb_tdb)

    Loading modules

    +Some subsystems in samba use different backends. These backends can be either statically linked in to samba or available as a plugin. A subsystem should have a function that allows a module to register itself. For example, -the passdb subsystem has: 

    BOOL smb_register_passdb(const char *name, pdb_init_function init, int version);

    This function will be called by the initialisation function of the module to -register itself.

    14.2.1. Static modules

    The modules system compiles a list of initialisation functions for the +the passdb subsystem has: +

    +BOOL smb_register_passdb(const char *name, pdb_init_function init, int version);
+

    +This function will be called by the initialisation function of the module to +register itself. +

    Static modules

    +The modules system compiles a list of initialisation functions for the static modules of each subsystem. This is a define. For example, -it is here currently (from include/config.h): 

    /* Static init functions */
-#define static_init_pdb { pdb_mysql_init(); pdb_ldap_init(); pdb_smbpasswd_init(); pdb_tdbsam_init(); pdb_guest_init();}

    These functions should be called before the subsystem is used. That -should be done when the subsystem is initialised or first used.

    14.2.2. Shared modules

    If a subsystem needs a certain backend, it should check if it has +it is here currently (from include/config.h): +

    +/* Static init functions */
+#define static_init_pdb { pdb_mysql_init(); pdb_ldap_init(); pdb_smbpasswd_init(); pdb_tdbsam_init(); pdb_guest_init();}
+

    +These functions should be called before the subsystem is used. That +should be done when the subsystem is initialised or first used. +

    Shared modules

    +If a subsystem needs a certain backend, it should check if it has already been registered. If the backend hasn't been registered already, the subsystem should call smb_probe_module(char *subsystem, char *backend). This function tries to load the correct module from a certain path ($LIBDIR/subsystem/backend.so). If the first character in 'backend' is a slash, smb_probe_module() tries to load the module from the -absolute path specified in 'backend'.

    After smb_probe_module() has been executed, the subsystem -should check again if the module has been registered.

    14.3. Writing modules

    Each module has an initialisation function. For modules that are -included with samba this name is 'subsystem_backend_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()). -The prototype for these functions is:

    int init_module(void);

    This function should call one or more +absolute path specified in 'backend'. +

    After smb_probe_module() has been executed, the subsystem +should check again if the module has been registered. +

    Writing modules

    +Each module has an initialisation function. For modules that are +included with samba this name is 'subsystem_backend_init'. For external modules (that will never be built-in, but only available as a module) this name is always 'init_module'. (In the case of modules included with samba, the configure system will add a #define subsystem_backend_init() init_module()). +The prototype for these functions is: +

    +int init_module(void);
+

    This function should call one or more registration functions. The function should return non-zero on success and zero on -failure.

    For example, pdb_ldap_init() contains: 

    int pdb_ldap_init(void)
+failure.
    For example, pdb_ldap_init() contains: 
    +int pdb_ldap_init(void)
 {
-    smb_register_passdb("ldapsam", pdb_init_ldapsam, PASSDB_INTERFACE_VERSION);
-    smb_register_passdb("ldapsam_nua", pdb_init_ldapsam_nua, PASSDB_INTERFACE_VERSION);
+    smb_register_passdb("ldapsam", pdb_init_ldapsam, PASSDB_INTERFACE_VERSION);
+    smb_register_passdb("ldapsam_nua", pdb_init_ldapsam_nua, PASSDB_INTERFACE_VERSION);
 	return TRUE;
-}
    14.3.1. Static/Shared selection in configure.in
    Some macros in configure.in generate the various defines and substs that 
+}
+

    Static/Shared selection in configure.in

    +Some macros in configure.in generate the various defines and substs that are necessary for the system to work correct. All modules that should be built by default have to be added to the variable 'default_modules'. -For example, if ldap is found, pdb_ldap is added to this variable.

    On the bottom of configure.in, SMB_MODULE() should be called -for each module and SMB_SUBSYSTEM() for each subsystem.

    Syntax:

    SMB_MODULE(subsystem_backend, object files, plugin name, subsystem name, static_action, shared_action)
-SMB_SUBSYSTEM(subsystem)

    Also, make sure to add the correct directives to -Makefile.in. @SUBSYSTEM_STATIC@ +For example, if ldap is found, pdb_ldap is added to this variable. +

    +On the bottom of configure.in, SMB_MODULE() should be called +for each module and SMB_SUBSYSTEM() for each subsystem. +

    Syntax:

    +SMB_MODULE(subsystem_backend, object files, plugin name, subsystem name, static_action, shared_action)
+SMB_SUBSYSTEM(subsystem)
+

    Also, make sure to add the correct directives to +Makefile.in. @SUBSYSTEM_STATIC@ will be replaced with a list of objects files of the modules that need to -be linked in statically. @SUBSYSTEM_MODULES@ will -be replaced with the names of the plugins to build.

    You must make sure all .c files that contain defines that can +be linked in statically. @SUBSYSTEM_MODULES@ will +be replaced with the names of the plugins to build. +

    You must make sure all .c files that contain defines that can be changed by ./configure are rebuilded in the 'modules_clean' make target. -Practically, this means all c files that contain static_init_subsystem; calls need to be rebuilded.

    Chapter 15. RPC Pluggable Modules

    15.1. About

    This document describes how to make use the new RPC Pluggable Modules features +Practically, this means all c files that contain static_init_subsystem; calls need to be rebuilded. +

    Chapter15.RPC Pluggable Modules

    Anthony Liguori

    IBM

    <aliguor@us.ibm.com>

    Jelmer Vernooij

    Samba Team

    <jelmer@samba.org>

    January 2003

    Table of Contents

    About
    General Overview

    About

    +This document describes how to make use the new RPC Pluggable Modules features of Samba 3.0. This architecture was added to increase the maintainability of Samba allowing RPC Pipes to be worked on separately from the main CVS branch. The RPM architecture will also allow third-party vendors to add functionality -to Samba through plug-ins.

    15.2. General Overview

    When an RPC call is sent to smbd, smbd tries to load a shared library by the -name librpc_<pipename>.so to handle the call if +to Samba through plug-ins. +

    General Overview

    +When an RPC call is sent to smbd, smbd tries to load a shared library by the +name librpc_<pipename>.so to handle the call if it doesn't know how to handle the call internally. For instance, LSA calls -are handled by librpc_lsass.so.. -These shared libraries should be located in the <sambaroot>/lib/rpc. smbd then attempts to call the init_module function within -the shared library. Check the chapter on modules for more information.

    In the init_module function, the library should call -rpc_pipe_register_commands(). This function takes the following arguments:

    int rpc_pipe_register_commands(const char *clnt, const char *srv,
-                               const struct api_struct *cmds, int size);

    clnt

    the Client name of the named pipe

    srv

    the Server name of the named pipe

    cmds

    a list of api_structs that map RPC ordinal numbers to function calls

    size

    the number of api_structs contained in cmds

    See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of -how to use this library.

    Chapter 16. Notes to packagers

    16.1. Versioning

    Please, please update the version number in -source/include/version.h to include the versioning of your package. This makes it easier to distinguish standard samba builds +are handled by librpc_lsass.so.. +These shared libraries should be located in the <sambaroot>/lib/rpc. smbd then attempts to call the init_module function within +the shared library. Check the chapter on modules for more information. +

    +In the init_module function, the library should call +rpc_pipe_register_commands(). This function takes the following arguments: +

    +int rpc_pipe_register_commands(const char *clnt, const char *srv,
+                               const struct api_struct *cmds, int size);
+
    clnt

    the Client name of the named pipe

    srv

    the Server name of the named pipe

    cmds

    a list of api_structs that map RPC ordinal numbers to function calls

    size

    the number of api_structs contained in cmds

    +See rpc_server/srv_reg.c and rpc_server/srv_reg_nt.c for a small example of +how to use this library. +

    Chapter16.Notes to packagers

    Jelmer Vernooij

    Table of Contents

    Versioning
    Modules

    Versioning

    Please, please update the version number in +source/include/version.h to include the versioning of your package. This makes it easier to distinguish standard samba builds from custom-build samba builds (distributions often patch packages). For -example, a good version would be: 

    Version 2.999+3.0.alpha21-5 for Debian

    16.2. Modules

    Samba now has support for building parts of samba as plugins. This +example, a good version would be: 

    +Version 2.999+3.0.alpha21-5 for Debian
+

    Modules

    Samba now has support for building parts of samba as plugins. This makes it possible to, for example, put ldap or mysql support in a seperate package, thus making it possible to have a normal samba package not depending on ldap or mysql. To build as much parts of samba -as a plugin, run: 

    ./configure --with-shared-modules=rpc,vfs,auth,pdb,charset

    \ No newline at end of file +as a plugin, run: 

    +./configure --with-shared-modules=rpc,vfs,auth,pdb,charset
+
    diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 7147458209..8334ef82f3 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -1,1470 +1,118 @@ - -SAMBA Project Documentation

    SAMBA Project Documentation

    SAMBA Team

    Edited by

    Jelmer R. Vernooij

    John H. Terpstra

    Gerald (Jerry) Carter

    This book is a collection of HOWTOs added to Samba documentation over the years. -Samba is always under development, and so is it's documentation. -The most recent version of this document -can be found at http://www.samba.org/ -on the "Documentation" page. Please send updates to jerry@samba.org or -jelmer@samba.org.

    This documentation is distributed under the GNU General Public License (GPL) +SAMBA Project Documentation

    SAMBA Project Documentation

    SAMBA Team

    <samba@samba.org>

    +This documentation is distributed under the GNU General Public License (GPL) version 2. A copy of the license is included with the Samba source -distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt

    Table of Contents
    I. General installation
    1. Introduction to Samba
    1.1. Background
    1.2. Terminology
    1.3. Related Projects
    1.4. SMB Methodology
    1.5. Additional Resources
    1.6. Epilogue
    1.7. Miscellaneous
    2. How to Install and Test SAMBA
    2.1. Obtaining and installing samba
    2.2. Configuring samba
    2.3. Try listing the shares available on your - server
    2.4. Try connecting with the unix client
    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client
    2.6. What If Things Don't Work?
    3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide
    3.1. Discussion
    3.2. How browsing functions and how to deploy stable and -dependable browsing using Samba
    3.3. Use of the Remote Announce parameter
    3.4. Use of the Remote Browse Sync parameter
    3.5. Use of WINS
    3.6. Do NOT use more than one (1) protocol on MS Windows machines
    3.7. Name Resolution Order
    4. User information database
    4.1. Introduction
    4.2. Important Notes About Security
    4.3. The smbpasswd Command
    4.4. Plain text
    4.5. TDB
    4.6. LDAP
    4.7. MySQL
    4.8. XML
    II. Type of installation
    5. Nomenclature of Server Types
    5.1. Stand Alone Server
    5.2. Domain Member Server
    5.3. Domain Controller
    6. Samba as Stand-Alone Server
    6.1. User and Share security level
    7. Samba as an NT4 or Win2k Primary Domain Controller
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.5. Common Problems and Errors
    7.6. Domain Control for Windows 9x/ME
    8. Samba Backup Domain Controller to Samba Domain Control
    8.1. Prerequisite Reading
    8.2. Background
    8.3. What qualifies a Domain Controller on the network?
    8.4. Can Samba be a Backup Domain Controller to an NT PDC?
    8.5. How do I set up a Samba BDC?
    9. Samba as a ADS domain member
    9.1. Setup your smb.conf
    9.2. Setup your /etc/krb5.conf
    9.3. Create the computer account
    9.4. Test your server setup
    9.5. Testing with smbclient
    9.6. Notes
    10. Samba as a NT4 or Win2k domain member
    10.1. Joining an NT Domain with Samba 3.0
    10.2. Why is this better than security = server?
    III. Advanced Configuration
    11. UNIX Permission Bits and Windows NT Access Control Lists
    11.1. Viewing and changing UNIX permissions using the NT - security dialogs
    11.2. How to view file security on a Samba share
    11.3. Viewing file ownership
    11.4. Viewing file or directory permissions
    11.5. Modifying file or directory permissions
    11.6. Interaction with the standard Samba create mask - parameters
    11.7. Interaction with the standard Samba file attribute - mapping
    12. Configuring Group Mapping
    13. Printing Support
    13.1. Introduction
    13.2. Configuration
    13.3. The Imprints Toolset
    13.4. Diagnosis
    14. CUPS Printing Support
    14.1. Introduction
    14.2. Configuring smb.conf for CUPS
    14.3. CUPS - RAW Print Through Mode
    14.4. CUPS as a network PostScript RIP -- CUPS drivers working on server, Adobe -PostScript driver with CUPS-PPDs downloaded to clients
    14.5. Windows Terminal Servers (WTS) as CUPS clients
    14.6. Setting up CUPS for driver download
    14.7. Sources of CUPS drivers / PPDs
    14.8. The CUPS Filter Chains
    14.9. CUPS Print Drivers and Devices
    14.10. Limiting the number of pages users can print
    14.11. Advanced Postscript Printing from MS Windows
    14.12. Auto-Deletion of CUPS spool files
    15. Unified Logons between Windows NT and UNIX using Winbind
    15.1. Abstract
    15.2. Introduction
    15.3. What Winbind Provides
    15.4. How Winbind Works
    15.5. Installation and Configuration
    15.6. Limitations
    15.7. Conclusion
    16. Advanced Network Manangement
    16.1. Configuring Samba Share Access Controls
    16.2. Remote Server Administration
    16.3. Network Logon Script Magic
    17. System and Account Policies
    17.1. Creating and Managing System Policies
    17.2. Managing Account/User Policies
    17.3. System Startup and Logon Processing Overview
    18. Desktop Profile Management
    18.1. Roaming Profiles
    18.2. Mandatory profiles
    18.3. Creating/Managing Group Profiles
    18.4. Default Profile for Windows Users
    19. Interdomain Trust Relationships
    19.1. Trust Relationship Background
    19.2. Native MS Windows NT4 Trusts Configuration
    19.3. Configuring Samba NT-style Domain Trusts
    20. PAM Configuration for Centrally Managed Authentication
    20.1. Samba and PAM
    20.2. Distributed Authentication
    20.3. PAM Configuration in smb.conf
    21. Stackable VFS modules
    21.1. Introduction and configuration
    21.2. Included modules
    21.3. VFS modules available elsewhere
    22. Hosting a Microsoft Distributed File System tree on Samba
    22.1. Instructions
    23. Integrating MS Windows networks with Samba
    23.1. Name Resolution in a pure Unix/Linux world
    23.2. Name resolution as used within MS Windows networking
    24. Improved browsing in samba
    24.1. Overview of browsing
    24.2. Browsing support in samba
    24.3. Problem resolution
    24.4. Browsing across subnets
    24.5. Setting up a WINS server
    24.6. Setting up Browsing in a WORKGROUP
    24.7. Setting up Browsing in a DOMAIN
    24.8. Forcing samba to be the master
    24.9. Making samba the domain master
    24.10. Note about broadcast addresses
    24.11. Multiple interfaces
    25. Securing Samba
    25.1. Introduction
    25.2. Using host based protection
    25.3. Using interface protection
    25.4. Using a firewall
    25.5. Using a IPC$ share deny
    25.6. Upgrading Samba
    26. Unicode/Charsets
    26.1. What are charsets and unicode?
    26.2. Samba and charsets
    26.3. Conversion from old names
    26.4. Japanese charsets
    IV. Appendixes
    27. How to compile SAMBA
    27.1. Access Samba source code via CVS
    27.2. Accessing the samba sources via rsync and ftp
    27.3. Verifying Samba's PGP signature
    27.4. Building the Binaries
    27.5. Starting the smbd and nmbd
    28. Migration from NT4 PDC to Samba-3 PDC
    28.1. Planning and Getting Started
    28.2. Managing Samba-3 Domain Control
    29. Portability
    29.1. HPUX
    29.2. SCO Unix
    29.3. DNIX
    29.4. RedHat Linux Rembrandt-II
    29.5. AIX
    29.6. Solaris
    30. Samba and other CIFS clients
    30.1. Macintosh clients?
    30.2. OS2 Client
    30.3. Windows for Workgroups
    30.4. Windows '95/'98
    30.5. Windows 2000 Service Pack 2
    30.6. Windows NT 3.1
    31. SWAT - The Samba Web Admininistration Tool
    31.1. SWAT Features and Benefits
    32. Samba performance issues
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning
    33. The samba checklist
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?
    34. Analysing and solving samba problems
    34.1. Diagnostics tools
    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    34.3. Useful URL's
    34.4. Getting help from the mailing lists
    34.5. How to get off the mailinglists
    35. Reporting Bugs
    35.1. Introduction
    35.2. General info
    35.3. Debug levels
    35.4. Internal errors
    35.5. Attaching to a running process
    35.6. Patches

    I. General installation

    Introduction

    This part contains general info on how to install samba +distribution. A copy can be found on-line at http://www.fsf.org/licenses/gpl.txt +

    Monday April 21, 2003

    Abstract

    +This book is a collection of HOWTOs added to Samba documentation over the years. +Samba is always under development, and so is its' documentation. This release of the +documentation represents a major revision or layout as well as contents. +The most recent version of this document can be found at +http://www.samba.org/ +on the "Documentation" page. Please send updates to +Jelmer Venrooij, +John Terpstra or +Gerald (Jerry) Carter. +

    +The Samba-Team would like to express sincere thanks to the many people who have with +or without their knowledge contributed to this update. The size and scope of this +project would not have been possible without significant community contribution. A not +insignificant number of ideas for inclusion (if not content itself) has been obtained +from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. +Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and +application knowledge that is most to be desired by many Samba users and administrators. +

    Table of Contents

    I. General Installation
    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Additional Resources
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba
    Editing the smb.conf file
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client
    What If Things Don't Work?
    II. Server Configuration Basics
    3. Nomenclature of Server Types
    Stand Alone Server
    Domain Member Server
    Domain Controller
    Domain Controller Types
    4. Samba as Stand-Alone Server
    User and Share security level
    User Level Security
    Share Level Security
    Server Level Security
    Domain Level Security
    ADS Level Security
    5. +Samba as an NT4 or Win2k Primary Domain Controller +
    Prerequisite Reading
    +Background +
    Configuring the Samba Domain Controller
    Creating Machine Trust Accounts and Joining Clients to the Domain
    Manual Creation of Machine Trust Accounts
    "On-the-Fly" Creation of Machine Trust Accounts
    Joining the Client to the Domain
    Common Problems and Errors
    I cannot include a '$' in a machine name
    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not +exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    Domain Control for Windows 9x/ME
    Configuration Instructions: Network Logons
    6. +Samba Backup Domain Controller to Samba Domain Control +
    Prerequisite Reading
    Background
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    When is the PDC needed?
    Can Samba be a Backup Domain Controller to an NT PDC?
    How do I set up a Samba BDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?
    7. Samba as a ADS domain member
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Possible errors
    Test your server setup
    Testing with smbclient
    Notes
    8. Samba as a NT4 or Win2k domain member
    Joining an NT Domain with Samba 3.0
    Why is this better than security = server?
    III. Advanced Configuration
    9. Samba / MS Windows Network Browsing Guide
    What is Browsing?
    Discussion
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing samba to be the master
    Making samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in samba
    Problem resolution
    Browsing across subnets
    10. User information database
    Introduction
    Important Notes About Security
    Advantages of SMB Encryption
    Advantages of non-encrypted passwords
    The smbpasswd Command
    Plain text
    TDB
    LDAP
    Introduction
    Encrypted Password Database
    Supported LDAP Servers
    Schema and Relationship to the RFC 2307 posixAccount
    Configuring Samba with LDAP
    Accounts and Groups management
    Security and sambaAccount
    LDAP specials attributes for sambaAccounts
    Example LDIF Entries for a sambaAccount
    MySQL
    Creating the database
    Configuring
    Using plaintext passwords or encrypted password
    Getting non-column data from the table
    XML
    11. UNIX Permission Bits and Windows NT Access Control Lists
    Viewing and changing UNIX permissions using the NT + security dialogs
    How to view file security on a Samba share
    Viewing file ownership
    Viewing file or directory permissions
    File Permissions
    Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute + mapping
    12. Configuring Group Mapping
    13. Printing Support
    Introduction
    Configuration
    Creating [print$]
    Setting Drivers for Existing Printers
    Support a large number of printers
    Adding New Printers via the Windows NT APW
    Samba and Printer Ports
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints server
    The Installation Client
    Diagnosis
    Introduction
    Debugging printer problems
    What printers do I have?
    Setting up printcap and print servers
    Job sent, no output
    Job sent, strange output
    Raw PostScript printed
    Advanced Printing
    Real debugging
    14. CUPS Printing Support
    Introduction
    Configuring smb.conf for CUPS
    CUPS - RAW Print Through Mode
    CUPS as a network PostScript RIP
    Windows Terminal Servers (WTS) as CUPS clients
    Setting up CUPS for driver download
    Sources of CUPS drivers / PPDs
    cupsaddsmb
    The CUPS Filter Chains
    CUPS Print Drivers and Devices
    Further printing steps
    Limiting the number of pages users can print
    Advanced Postscript Printing from MS Windows
    Auto-Deletion of CUPS spool files
    15. Unified Logons between Windows NT and UNIX using Winbind
    Abstract
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Limitations
    Conclusion
    16. Advanced Network Manangement
    Configuring Samba Share Access Controls
    Share Permissions Management
    Remote Server Administration
    Network Logon Script Magic
    Adding printers without user intervention
    17. System and Account Policies
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    With Windows NT4/200x
    With a Samba PDC
    System Startup and Logon Processing Overview
    18. Desktop Profile Management
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    19. Interdomain Trust Relationships
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    20. PAM Configuration for Centrally Managed Authentication
    Samba and PAM
    PAM Configuration in smb.conf
    Password Synchronisation using pam_smbpass.so
    Distributed Authentication
    21. Stackable VFS modules
    Introduction and configuration
    Included modules
    audit
    extd_audit
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    22. Hosting a Microsoft Distributed File System tree on Samba
    Instructions
    Notes
    23. Integrating MS Windows networks with Samba
    Name Resolution in a pure Unix/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    24. Securing Samba
    Introduction
    Using host based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    25. Unicode/Charsets
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    26. File and Record Locking
    Discussion
    Samba Opportunistic Locking Control
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Additional Reading
    IV. Troubleshooting
    27. The samba checklist
    Introduction
    Assumptions
    The tests
    Still having troubles?
    28. Analysing and solving samba problems
    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URL's
    Getting help from the mailing lists
    How to get off the mailinglists
    29. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches
    V. Appendixes
    30. How to compile SAMBA
    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices
    32. Portability
    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    33. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?
    Are there any other issues when OS/2 (any version) + is used as a client?
    How do I get printer driver download working + for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    34. SWAT - The Samba Web Admininistration Tool
    SWAT Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    35. Samba performance issues
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning

    List of Tables

    21.1. Extended Auditing Log Information
    31.1. The 3 Major Site Types
    31.2. Nature of the Conversion Choices

    General Installation

    Preparing Samba for Configuration

    This section of the Samba-HOWTO-Collection contains general info on how to install samba and how to configure the parts of samba you will most likely need. -PLEASE read this.

    Chapter1.Introduction to Samba

    David Lechnyr

    Unofficial HOWTO

    <david@lechnyr.com>

    April 14, 2003

    Table of Contents

    Background
    Terminology
    Related Projects
    SMB Methodology
    Additional Resources
    Epilogue
    Miscellaneous

    +"If you understand what you're doing, you're not learning anything." +-- Anonymous +

    +Samba is a file and print server for Windows-based clients using TCP/IP as the underlying transport protocol. In fact, it can support any SMB/CIFS-enabled client. One of Samba's big strengths is that you can use it to blend your mix of Windows and Linux machines together without requiring a separate Windows NT/2000/2003 Server. Samba is actively being developed -by a global team of about 30 active programmers and was originally developed by Andrew Tridgell.

    1.1. Background

    Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed +by a global team of about 30 active programmers and was originally developed by Andrew Tridgell. +

    Background

    +Once long ago, there was a buzzword referred to as DCE/RPC. This stood for Distributed Computing Environment/Remote Procedure Calls and conceptually was a good idea. It was originally developed by Apollo/HP as NCA 1.0 (Network Computing Architecture) and only ran over UDP. When there was a need to run it over TCP so that it would be compatible with DECnet 3.0, it was redesigned, submitted to The Open Group, and officially became known as DCE/RPC. Microsoft came along and decided, rather than pay $20 per seat to license this technology, to reimplement DCE/RPC themselves as MSRPC. From this, the -concept continued in the form of SMB (Server Message Block, or the "what") using the -NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can +concept continued in the form of SMB (Server Message Block, or the "what") using the +NetBIOS (Network Basic Input/Output System, or the "how") compatibility layer. You can run SMB (i.e., transport) over several different protocols; many different implementations arose as a result, including NBIPX (NetBIOS over IPX, NwLnkNb, or NWNBLink) and NBT (NetBIOS over TCP/IP, or NetBT). As the years passed, NBT became the most common form -of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing +of implementation until the advance of "Direct-Hosted TCP" -- the Microsoft marketing term for eliminating NetBIOS entirely and running SMB by itself across TCP port 445 -only. As of yet, direct-hosted TCP has yet to catch on.

    Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS: -Common Insecurities Fail Scrutiny:

    Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba +only. As of yet, direct-hosted TCP has yet to catch on. +

    +Perhaps the best summary of the origins of SMB are voiced in the 1997 article titled, CIFS: +Common Insecurities Fail Scrutiny: +

    +Several megabytes of NT-security archives, random whitepapers, RFCs, the CIFS spec, the Samba stuff, a few MS knowledge-base articles, strings extracted from binaries, and packet dumps have been dutifully waded through during the information-gathering stages of this project, and there are *still* many missing pieces... While often tedious, at least the way has been generously littered with occurrences of clapping hand to forehead and muttering 'crikey, what are they -thinking?

    1.2. Terminology

    • SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. -

    • CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently - decided that SMB needed the word "Internet" in it, so they changed it to CIFS. -

    • Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp +thinking? +

    Terminology

    • + SMB: Acronym for "Server Message Block". This is Microsoft's file and printer sharing protocol. +

    • + CIFS: Acronym for "Common Internet File System". Around 1996, Microsoft apparently + decided that SMB needed the word "Internet" in it, so they changed it to CIFS. +

    • + Direct-Hosted: A method of providing file/printer sharing services over port 445/tcp only using DNS for name resolution instead of WINS. -

    • IPC: Acronym for "Inter-Process Communication". A method to communicate specific +

    • + IPC: Acronym for "Inter-Process Communication". A method to communicate specific information between programs. -

    • Marshalling: - A method of serializing (i.e., sequential ordering of) variable data +

    • + Marshalling: - A method of serializing (i.e., sequential ordering of) variable data suitable for transmission via a network connection or storing in a file. The source data can be re-created using a similar process called unmarshalling. -

    • NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; +

    • + NetBIOS: Acronym for "Network Basic Input/Output System". This is not a protocol; it is a method of communication across an existing protocol. This is a standard which was originally developed for IBM by Sytek in 1983. To exaggerate the analogy a bit, it can help to think of this in comparison your computer's BIOS -- it controls the @@ -1474,22 +122,16 @@ NAME="AEN67" is that NetBIOS is a transport standard, not a protocol. Unfortunately, even technically brilliant people tend to interchange NetBIOS with terms like NetBEUI without a second thought; this will cause no end (and no doubt) of confusion. -

    • NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI +

    • + NetBEUI: Acronym for the "NetBIOS Extended User Interface". Unlike NetBIOS, NetBEUI is a protocol, not a standard. It is also not routable, so traffic on one side of a router will be unable to communicate with the other side. Understanding NetBEUI is not essential to deciphering SMB; however it helps to point out that it is not the same as NetBIOS and to improve your score in trivia at parties. NetBEUI was originally - referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". + referred to by Microsoft as "NBF", or "The Windows NT NetBEUI Frame protocol driver". It is not often heard from these days. -

    • NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use +

    • + NBT: Acronym for "NetBIOS over TCP"; also known as "NetBT". Allows the continued use of NetBIOS traffic proxied over TCP/IP. As a result, NetBIOS names are made to IP addresses and NetBIOS name types are conceptually equivalent to TCP/IP ports. This is how file and printer sharing are accomplished in Windows 95/98/ME. They @@ -1498,279 +140,110 @@ NAME="AEN67" (nbsession) via TCP port 139. All name resolution is done via WINS, NetBIOS broadcasts, and DNS. NetBIOS over TCP is documented in RFC 1001 (Concepts and methods) and RFC 1002 (Detailed specifications). -

    • W2K: Acronym for Windows 2000 Professional or Server -

    • W3K: Acronym for Windows 2003 Server -

    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at -http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com

    1.3. Related Projects

    Currently, there are two projects that are directly related to Samba: SMBFS and CIFS network -client file systems for Linux, both available in the Linux kernel itself.

    • SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol +

    • + W2K: Acronym for Windows 2000 Professional or Server +

    • + W3K: Acronym for Windows 2003 Server +

    If you plan on getting help, make sure to subscribe to the Samba Mailing List (available at +http://www.samba.org). Optionally, you could just search mailing.unix.samba at http://groups.google.com +

    Related Projects

    +There are currently two network filesystem client projects for Linux that are directly +related to Samba: SMBFS and CIFS VFS. These are both available in the Linux kernel itself. +

    • + SMBFS (Server Message Block File System) allows you to mount SMB shares (the protocol that Microsoft Windows and OS/2 Lan Manager use to share files and printers over local networks) and access them just like any other Unix directory. This is useful if you just want to mount such filesystems without being a SMBFS server. -

    • CIFS (Common Internet File System) is the successor to SMB, and is actively being worked - on in the upcoming version of the Linux kernel. The intent of this module is to - provide advanced network file system functionality including support for dfs (heirarchical +

    • + CIFS VFS (Common Internet File System Virtual File System) is the successor to SMBFS, and + is being actively developed for the upcoming version of the Linux kernel. The intent of this module + is to provide advanced network file system functionality including support for dfs (heirarchical name space), secure per-user session establishment, safe distributed caching (oplock), optional packet signing, Unicode and other internationalization improvements, and optional Winbind (nsswitch) integration. -

    Again, it's important to note that these are implementations for client filesystems, and have -nothing to do with acting as a file and print server for SMB/CIFS clients.

    1.4. SMB Methodology

    Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), +

    +Again, it's important to note that these are implementations for client filesystems, and have +nothing to do with acting as a file and print server for SMB/CIFS clients. +

    +There are other Open Source CIFS client implementations, such as the jCIFS project +(jcifs.samba.org) which provides an SMB client toolkit written in Java. +

    SMB Methodology

    +Traditionally, SMB uses UDP port 137 (NetBIOS name service, or netbios-ns), UDP port 138 (NetBIOS datagram service, or netbios-dgm), and TCP port 139 (NetBIOS session service, or netbios-ssn). Anyone looking at their network with a good packet sniffer will be amazed at the amount of traffic generated by just opening -up a single file. In general, SMB sessions are established in the following order:

    • "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp +up a single file. In general, SMB sessions are established in the following order: +

      • + "TCP Connection" - establish 3-way handshake (connection) to port 139/tcp or 445/tcp. -

      • "NetBIOS Session Request" - using the following "Calling Names": The local +

      • + "NetBIOS Session Request" - using the following "Calling Names": The local machine's NetBIOS name plus the 16th character 0x00; The server's NetBIOS name plus the 16th character 0x20 -

      • "SMB Negotiate Protocol" - determine the protocol dialect to use, which will +

      • + "SMB Negotiate Protocol" - determine the protocol dialect to use, which will be one of the following: PC Network Program 1.0 (Core) - share level security mode only; Microsoft Networks 1.03 (Core Plus) - share level security mode only; Lanman1.0 (LAN Manager 1.0) - uses Challenge/Response Authentication; Lanman2.1 (LAN Manager 2.1) - uses Challenge/Response Authentication; NT LM 0.12 (NT LM 0.12) - uses Challenge/Response Authentication -

      • SMB Session Startup. Passwords are encrypted (or not) according to one of +

      • + SMB Session Startup. Passwords are encrypted (or not) according to one of the following methods: Null (no encryption); Cleartext (no encryption); LM and NTLM; NTLM; NTLMv2 -

      • SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect +

      • + SMB Tree Connect: Connect to a share name (e.g., \\servername\share); Connect to a service type (e.g., IPC$ named pipe) -

      A good way to examine this process in depth is to try out SecurityFriday's SWB program +

    +A good way to examine this process in depth is to try out SecurityFriday's SWB program at http://www.securityfriday.com/ToolDownload/SWB/swb_doc.html. It allows you to -walk through the establishment of a SMB/CIFS session step by step.

    1.5. Additional Resources

    • CIFS: Common Insecurities Fail Scrutiny by "Hobbit", - http://hr.uoregon.edu/davidrl/cifs.txt -

    • Doing the Samba on Windows by Financial Review, - http://afr.com/it/2002/10/01/FFXDF43AP6D.html -

    • Implementing CIFS by Christopher R. Hertel, - http://ubiqx.org/cifs/ -

    • Just What Is SMB? by Richard Sharpe, - http://samba.anu.edu.au/cifs/docs/what-is-smb.html -

    • Opening Windows Everywhere by Mike Warfield, - http://www.linux-mag.com/1999-05/samba_01.html -

    • SMB HOWTO by David Wood, - http://www.tldp.org/HOWTO/SMB-HOWTO.html -

    • SMB/CIFS by The Root by "ledin", - http://www.phrack.org/phrack/60/p60-0x0b.txt -

    • The Story of Samba by Christopher R. Hertel, - http://www.linux-mag.com/1999-09/samba_01.html -

    • The Unofficial Samba HOWTO by David Lechnyr, - http://hr.uoregon.edu/davidrl/samba/ -

    • Understanding the Network Neighborhood by Christopher R. Hertel, - http://www.linux-mag.com/2001-05/smb_01.html -

    • Using Samba as a PDC by Andrew Bartlett, - http://www.linux-mag.com/2002-02/samba_01.html -

    1.6. Epilogue

    "What's fundamentally wrong is that nobody ever had any taste when they +walk through the establishment of a SMB/CIFS session step by step. +

    Additional Resources

    Epilogue

    +"What's fundamentally wrong is that nobody ever had any taste when they did it. Microsoft has been very much into making the user interface look good, but internally it's just a complete mess. And even people who program for Microsoft and who have had years of experience, just don't know how it works internally. @@ -1778,26 +251,14 @@ Worse, nobody dares change it. Nobody dares to fix bugs because it's such a mess that fixing one bug might just break a hundred programs that depend on that bug. And Microsoft isn't interested in anyone fixing bugs -- they're interested in making money. They don't have anybody who takes pride in Windows 95 as an -operating system.

    People inside Microsoft know it's a bad operating system and they still +operating system. +

    +People inside Microsoft know it's a bad operating system and they still continue obviously working on it because they want to get the next version out because they want to have all these new features to sell more copies of the -system.

    The problem with that is that over time, when you have this kind of approach, +system. +

    +The problem with that is that over time, when you have this kind of approach, and because nobody understands it, because nobody REALLY fixes bugs (other than when they're really obvious), the end result is really messy. You can't trust it because under certain circumstances it just spontaneously reboots or just @@ -1805,4147 +266,751 @@ halts in the middle of something that shouldn't be strange. Normally it works fine and then once in a blue moon for some completely unknown reason, it's dead, and nobody knows why. Not Microsoft, not the experienced user and certainly not the completely clueless user who probably sits there shivering thinking -"What did I do wrong?" when they didn't do anything wrong at all.

    That's what's really irritating to me."

    -- Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 -(http://hr.uoregon.edu/davidrl/boot.txt)

    1.7. Miscellaneous

    This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0, -in case anyone asks.

    This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). +"What did I do wrong?" when they didn't do anything wrong at all. +

    +That's what's really irritating to me." +

    -- +Linus Torvalds, from an interview with BOOT Magazine, Sept 1998 +

    Miscellaneous

    +This chapter was lovingly handcrafted on a Dell Latitude C400 laptop running Slackware Linux 9.0, +in case anyone asks. +

    +This chapter is Copyright 2003 David Lechnyr (david at lechnyr dot com). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free -Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt.

    Chapter 2. How to Install and Test SAMBA

    2.1. Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or +Software Foundation. A copy of the license is available at http://www.gnu.org/licenses/fdl.txt. +

    Chapter2.How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba
    Editing the smb.conf file
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client
    What If Things Don't Work?

    Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or Unix distribution. There are also some packages available at - the samba homepage. -

    If you need to compile samba from source, check the - appropriate appendix chapter.

    2.2. Configuring samba

    Samba's configuration is stored in the smb.conf file, - that usually resides in /etc/samba/smb.conf - or /usr/local/samba/lib/smb.conf. You can either + the samba homepage. +

    If you need to compile samba from source, check the + appropriate appendix chapter.

    Configuring samba

    Samba's configuration is stored in the smb.conf file, + that usually resides in /etc/samba/smb.conf + or /usr/local/samba/lib/smb.conf. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the web-based interface swat, that - is included with samba.

    2.2.1. Editing the smb.conf file

    There are sample configuration files in the examples + is included with samba.

    Editing the smb.conf file

    There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in - practice. See the man page for all the options.

    The simplest useful configuration file would be - something like this:

    [global]
+	practice. See the man page for all the options.
    The simplest useful configuration file would be 
+	something like this:
    +[global]
 	workgroup = MYGROUP
 
 [homes]
 	guest ok = no
 	read only = no
-	
    which would allow connections by anyone with an 
+

    which would allow connections by anyone with an account on the server, using either their login name or - "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)

    Make sure you put the smb.conf file in the same place - you specified in theMakefile (the default is to - look for it in /usr/local/samba/lib/).

    For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba.

    2.2.1.1. Test your config file with - testparm

    It's important that you test the validity of your - smb.conf file using the testparm program. + "homes" as the service name. (Note that I also set the + workgroup that Samba is part of. See BROWSING.txt for details)

    Make sure you put the smb.conf file in the same place + you specified in theMakefile (the default is to + look for it in /usr/local/samba/lib/).

    For more information about security settings for the + [homes] share please refer to the chapter + Securing Samba.

    Test your config file with + testparm

    It's important that you test the validity of your + smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If - not it will give an error message.

    Make sure it runs OK and that the services look - reasonable before proceeding.

    Always run testparm again when you change - smb.conf!

    2.2.2. SWAT

    SWAT is a web-based interface that helps you configure samba. + not it will give an error message.

    Make sure it runs OK and that the services look + reasonable before proceeding.

    Always run testparm again when you change + smb.conf!

    SWAT

    + SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage + but in a separate package. Please read the swat manpage on compiling, installing and configuring swat from source. -

    To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.

    Note that you can attach to SWAT from any IP connected +

    To launch SWAT just run your favorite web browser and + point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you + are running samba on a different computer than your browser.

    Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent - in the clear over the wire.

    2.3. Try listing the shares available on your - server

    $ smbclient -L - yourhostname

    You should get back a list of shares available on + in the clear over the wire.

    Try listing the shares available on your + server

    $ smbclient -L + yourhostname

    You should get back a list of shares available on your server. If you don't then something is incorrectly setup. Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find + are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find that Samba requests a password before it will list the shares. - See the smbclient man page for details. (you + See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

    2.4. Try connecting with the unix client

    $ smbclient //yourhostname/aservice

    Typically the yourhostname - would be the name of the host where you installed smbd. - The aservice is - any service you have defined in the smb.conf - file. Try your user name if you just have a [homes] + with non-Samba servers)

    Try connecting with the unix client

    $ smbclient + //yourhostname/aservice

    Typically the yourhostname + would be the name of the host where you installed smbd. + The aservice is + any service you have defined in the smb.conf + file. Try your user name if you just have a [homes] section - in smb.conf.

    For example if your unix host is bambi - and your login name is fred you would type:

    $ smbclient //bambi/fred -

    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service -

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: - \\servername\spoolservice

    C:\WINDOWS\> print filename -

    2.6. What If Things Don't Work?

    Then you might read the file chapter - Diagnosis and the + in smb.conf.

    For example if your unix host is bambi + and your login name is fred you would type:

    $ smbclient //bambi/fred +

    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service +

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: + \\servername\spoolservice

    C:\WINDOWS\> print filename +

    What If Things Don't Work?

    Then you might read the file chapter + Diagnosis and the FAQ. If you are still stuck then try to follow - the Analysing and Solving Problems chapter + the Analysing and Solving Problems chapter Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

    2.6.1. Scope IDs

    By default Samba uses a blank scope ID. This means - all your windows boxes must also have a blank scope ID. - If you really want to use a non-blank scope ID then you will - need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for - this to work. I do not recommend scope IDs.

    2.6.2. Locking

    One area which sometimes causes trouble is locking.

    There are two types of locking which need to be - performed by a SMB server. The first is "record locking" - which allows a client to lock a range of bytes in a open file. - The second is the "deny modes" that are specified when a file - is open.

    Record locking semantics under Unix is very - different from record locking under Windows. Versions - of Samba before 2.2 have tried to use the native - fcntl() unix system call to implement proper record - locking between different Samba clients. This can not - be fully correct due to several reasons. The simplest - is the fact that a Windows client is allowed to lock a - byte range up to 2^32 or 2^64, depending on the client - OS. The unix locking only supports byte ranges up to - 2^31. So it is not possible to correctly satisfy a - lock request above 2^31. There are many more - differences, too many to be listed here.

    Samba 2.2 and above implements record locking - completely independent of the underlying unix - system. If a byte range lock that the client requests - happens to fall into the range 0-2^31, Samba hands - this request down to the Unix system. All other locks - can not be seen by unix anyway.

    Strictly a SMB server should check for locks before - every read and write call on a file. Unfortunately with the - way fcntl() works this can be slow and may overstress the - rpc.lockd. It is also almost always unnecessary as clients - are supposed to independently make locking calls before reads - and writes anyway if locking is important to them. By default - Samba only makes locking calls when explicitly asked - to by a client, but if you set "strict locking = yes" then it will - make lock checking calls on every read and write.

    You can also disable by range locking completely - using "locking = no". This is useful for those shares that - don't support locking or don't need it (such as cdroms). In - this case Samba fakes the return codes of locking calls to - tell clients that everything is OK.

    The second class of locking is the "deny modes". These - are set by an application when it opens a file to determine - what types of access should be allowed simultaneously with - its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatibility modes called - DENY_FCB and DENY_DOS.

    Chapter 3. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide

    This document should be read in conjunction with Browsing and may -be taken as the fast track guide to implementing browsing across subnets -and / or across workgroups (or domains). WINS is the best tool for resolution -of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling -except by way of name to address mapping.

    MS Windows 2000 and later can be configured to operate with NO NetBIOS -over TCP/IP. Samba-3 and later also supports this mode of operation.

    3.1. Discussion

    Firstly, all MS Windows networking is based on SMB (Server Message -Block) based messaging. SMB messaging may be implemented using NetBIOS or -without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. -MS Windows products can do likewise. NetBIOS based networking uses broadcast -messaging to affect browse list management. When running NetBIOS over -TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.

    Normally, only unicast UDP messaging can be forwarded by routers. The -remote announce -parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the -remote browse sync parameter of smb.conf -implements browse list collation using unicast UDP.

    Secondly, in those networks where Samba is the only SMB server technology -wherever possible nmbd should be configured on one (1) machine as the WINS -server. This makes it easy to manage the browsing environment. If each network -segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the -remote announce and the remote browse sync -parameters to your smb.conf file.

    If only one WINS server is used for an entire multi-segment network then -the use of the remote announce and the -remote browse sync parameters should NOT be necessary.

    As of Samba 3 WINS replication is being worked on. The bulk of the code has -been committed, but it still needs maturation.

    Right now samba WINS does not support MS-WINS replication. This means that -when setting up Samba as a WINS server there must only be one nmbd configured -as a WINS server on the network. Some sites have used multiple Samba WINS -servers for redundancy (one server per subnet) and then used -remote browse sync and remote announce -to affect browse list collation across all -segments. Note that this means clients will only resolve local names, -and must be configured to use DNS to resolve names on other subnets in -order to resolve the IP addresses of the servers they can see on other -subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie: an 'if all else fails' scenario).

    Lastly, take note that browse lists are a collection of unreliable broadcast -messages that are repeated at intervals of not more than 15 minutes. This means -that it will take time to establish a browse list and it can take up to 45 -minutes to stabilise, particularly across network segments.

    3.2. How browsing functions and how to deploy stable and -dependable browsing using Samba

    As stated above, MS Windows machines register their NetBIOS names -(i.e.: the machine name for each service type in operation) on start -up. Also, as stated above, the exact method by which this name registration -takes place is determined by whether or not the MS Windows client/server -has been given a WINS server address, whether or not LMHOSTS lookup -is enabled, or if DNS for NetBIOS name resolution is enabled, etc.

    In the case where there is no WINS server all name registrations as -well as name lookups are done by UDP broadcast. This isolates name -resolution to the local subnet, unless LMHOSTS is used to list all -names and IP addresses. In such situations Samba provides a means by -which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the -remote announce parameter).

    Where a WINS server is used, the MS Windows client will use UDP -unicast to register with the WINS server. Such packets can be routed -and thus WINS allows name resolution to function across routed networks.

    During the startup process an election will take place to create a -local master browser if one does not already exist. On each NetBIOS network -one machine will be elected to function as the domain master browser. This -domain browsing has nothing to do with MS security domain control. -Instead, the domain master browser serves the role of contacting each local -master browser (found by asking WINS or from LMHOSTS) and exchanging browse -list contents. This way every master browser will eventually obtain a complete -list of all machines that are on the network. Every 11-15 minutes an election -is held to determine which machine will be the master browser. By the nature of -the election criteria used, the machine with the highest uptime, or the -most senior protocol version, or other criteria, will win the election -as domain master browser.

    Clients wishing to browse the network make use of this list, but also depend -on the availability of correct name resolution to the respective IP -address/addresses.

    Any configuration that breaks name resolution and/or browsing intrinsics -will annoy users because they will have to put up with protracted -inability to use the network services.

    Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the remote -browse sync parameter in the smb.conf file. -This causes Samba to contact the local master browser on a remote network and -to request browse list synchronisation. This effectively bridges -two networks that are separated by routers. The two remote -networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the remote -browse sync parameter provides browse list synchronisation - and -that is distinct from name to address resolution, in other -words, for cross subnet browsing to function correctly it is -essential that a name to address resolution mechanism be provided. -This mechanism could be via DNS, /etc/hosts, -and so on.

    3.3. Use of the Remote Announce parameter

    The remote announce parameter of -smb.conf can be used to forcibly ensure -that all the NetBIOS names on a network get announced to a remote network. -The syntax of the remote announce parameter is: -

    	remote announce = a.b.c.d [e.f.g.h] ...
    -_or_ -
    	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
    + so maybe someone else has hit your problem and has overcome it.

    Server Configuration Basics

    First Steps in Server Configuration

    +Samba can operate in various modes within SMB networks. This HOWTO section contains information on +configuring samba to function as the type of server your network requires. Please read this +section carefully. +

    Table of Contents

    3. Nomenclature of Server Types
    Stand Alone Server
    Domain Member Server
    Domain Controller
    Domain Controller Types
    4. Samba as Stand-Alone Server
    User and Share security level
    User Level Security
    Share Level Security
    Server Level Security
    Domain Level Security
    ADS Level Security
    5. +Samba as an NT4 or Win2k Primary Domain Controller +
    Prerequisite Reading
    +Background +
    Configuring the Samba Domain Controller
    Creating Machine Trust Accounts and Joining Clients to the Domain
    Manual Creation of Machine Trust Accounts
    "On-the-Fly" Creation of Machine Trust Accounts
    Joining the Client to the Domain
    Common Problems and Errors
    I cannot include a '$' in a machine name
    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not +exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    Domain Control for Windows 9x/ME
    Configuration Instructions: Network Logons
    6. +Samba Backup Domain Controller to Samba Domain Control +
    Prerequisite Reading
    Background
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    When is the PDC needed?
    Can Samba be a Backup Domain Controller to an NT PDC?
    How do I set up a Samba BDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?
    7. Samba as a ADS domain member
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Possible errors
    Test your server setup
    Testing with smbclient
    Notes
    8. Samba as a NT4 or Win2k domain member
    Joining an NT Domain with Samba 3.0
    Why is this better than security = server?

    Chapter3.Nomenclature of Server Types

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Table of Contents

    Stand Alone Server
    Domain Member Server
    Domain Controller
    Domain Controller Types

    Adminstrators of Microsoft networks often refer to there being three +different type of servers:

    • Stand Alone Server

    • Domain Member Server

    • Domain Controller

      • Primary Domain Controller

      • Backup Domain Controller

      • ADS Domain Controller

    A network administrator who is familiar with these terms and who +wishes to migrate to or use Samba will want to know what these terms mean +within a Samba context.

    Stand Alone Server

    +The term stand alone server means that the server +will provide local authentication and access control for all resources +that are available from it. In general this means that there will be a +local user database. In more technical terms, it means that resources +on the machine will either be made available in either SHARE mode or in +USER mode. SHARE mode and USER mode security are documented under +discussions regarding "security mode". The smb.conf configuration parameters +that control security mode are: "security = user" and "security = share". +

    +No special action is needed other than to create user accounts. Stand-alone +servers do NOT provide network logon services, meaning that machines that +use this server do NOT perform a domain logon but instead make use only of +the MS Windows logon which is local to the MS Windows workstation/server. +

    +Samba tends to blur the distinction a little in respect of what is +a stand alone server. This is because the authentication database may be +local or on a remote server, even if from the samba protocol perspective +the samba server is NOT a member of a domain security context. +

    +Through the use of PAM (Pluggable Authentication Modules) and nsswitch +(the name service switcher) the source of authentication may reside on +another server. We would be inclined to call this the authentication server. +This means that the samba server may use the local Unix/Linux system +password database (/etc/passwd or /etc/shadow), may use a local smbpasswd +file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or +may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB +server for authentication. +

    Domain Member Server

    +This mode of server operation involves the samba machine being made a member +of a domain security context. This means by definition that all user authentication +will be done from a centrally defined authentication regime. The authentication +regime may come from an NT3/4 style (old domain technology) server, or it may be +provided from an Active Directory server (ADS) running on MS Windows 2000 or later. +

    +Of course it should be clear that the authentication back end itself could be from any +distributed directory architecture server that is supported by Samba. This can be +LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc. +

    +Please refer to the section on Howto configure Samba as a Primary Domain Controller +and for more information regarding how to create a domain machine account for a +domain member server as well as for information regarding how to enable the samba +domain member machine to join the domain and to be fully trusted by it. +

    Domain Controller

    +Over the years public perceptions of what Domain Control really is has taken on an +almost mystical nature. Before we branch into a brief overview of what Domain Control +is the following types of controller are known: +

    Domain Controller Types

    Primary Domain Controller
    Backup Domain Controller
    ADS Domain Controller

    +The Primary Domain Controller or PDC plays an important role in the MS +Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many +expect. The PDC seeds the Domain Control database (a part of the Windows registry) and +it plays a key part in synchronisation of the domain authentication database. +

    +New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as +the NT4 style SAM (Security Account Manager) database (one of the registry files). +The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and +valid options include smbpasswd tdbsam ldapsam nisplussam plugin unixsam. +The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix +Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux +system accounts, provided a uid range is defined from which SAM accounts can be created. +

    +The Backup Domain Controller or BDC plays a key role in servicing network +authentication requests. The BDC is biased to answer logon requests so that on a network segment +that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will +answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to +a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is +automatically demoted to a BDC. +

    +At this time Samba is NOT capable of acting as an ADS Domain Controller. +

    Chapter4.Samba as Stand-Alone Server

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Table of Contents

    User and Share security level
    User Level Security
    Share Level Security
    Server Level Security
    Domain Level Security
    ADS Level Security

    +In this section the function and purpose of Samba's security +modes are described. +

    User and Share security level

    +A SMB server tells the client at startup what "security level" it is +running. There are two options "share level" and "user level". Which +of these two the client receives affects the way the client then tries +to authenticate itself. It does not directly affect (to any great +extent) the way the Samba server does security. I know this is +strange, but it fits in with the client/server approach of SMB. In SMB +everything is initiated and controlled by the client, and the server +can only tell the client what is available and whether an action is +allowed. +

    User Level Security

    +I'll describe user level security first, as its simpler. In user level +security the client will send a "session setup" command directly after +the protocol negotiation. This contains a username and password. The +server can either accept or reject that username/password +combination. Note that at this stage the server has no idea what +share the client will eventually try to connect to, so it can't base +the "accept/reject" on anything other than: +

    1. the username/password

    2. the machine that the client is coming from

    +If the server accepts the username/password then the client expects to +be able to mount any share (using a "tree connection") without +specifying a password. It expects that all access rights will be as +the username/password specified in the "session setup". +

    +It is also possible for a client to send multiple "session setup" +requests. When the server responds it gives the client a "uid" to use +as an authentication tag for that username/password. The client can +maintain multiple authentication contexts in this way (WinDD is an +example of an application that does this) +

    Share Level Security

    +Ok, now for share level security. In share level security the client +authenticates itself separately for each share. It will send a +password along with each "tree connection" (share mount). It does not +explicitly send a username with this operation. The client is +expecting a password to be associated with each share, independent of +the user. This means that samba has to work out what username the +client probably wants to use. It is never explicitly sent the +username. Some commercial SMB servers such as NT actually associate +passwords directly with shares in share level security, but samba +always uses the unix authentication scheme where it is a +username/password that is authenticated, not a "share/password". +

    +Many clients send a "session setup" even if the server is in share +level security. They normally send a valid username but no +password. Samba records this username in a list of "possible +usernames". When the client then does a "tree connection" it also adds +to this list the name of the share they try to connect to (useful for +home directories) and any users listed in the user = smb.conf +line. The password is then checked in turn against these "possible +usernames". If a match is found then the client is authenticated as +that user. +

    Server Level Security

    +Finally "server level" security. In server level security the samba +server reports to the client that it is in user level security. The +client then does a "session setup" as described earlier. The samba +server takes the username/password that the client sends and attempts +to login to the "password server" by sending exactly the same +username/password that it got from the client. If that server is in +user level security and accepts the password then samba accepts the +clients connection. This allows the samba server to use another SMB +server as the "password server". +

    +You should also note that at the very start of all this, where the +server tells the client what security level it is in, it also tells +the client if it supports encryption. If it does then it supplies the +client with a random "cryptkey". The client will then send all +passwords in encrypted form. You have to compile samba with encryption +enabled to support this feature, and you have to maintain a separate +smbpasswd file with SMB style encrypted passwords. It is +cryptographically impossible to translate from unix style encryption +to SMB style encryption, although there are some fairly simple management +schemes by which the two could be kept in sync. +

    +"security = server" means that Samba reports to clients that +it is running in "user mode" but actually passes off all authentication +requests to another "user mode" server. This requires an additional +parameter "password server =" that points to the real authentication server. +That real authentication server can be another Samba server or can be a +Windows NT server, the later natively capable of encrypted password support. +

    Note

    +Server level security is incompatible with what is known +as schannel or "sign and seal" protocols. This means that +if you want to use server level security you must disable +the use of "sign and seal" on all machines on your network. +

    Configuring Samba for Seemless Windows Network Integration

    +MS Windows clients may use encrypted passwords as part of a challenege/response +authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple +password based authentication. It should be realized that with the SMB protocol +the password is passed over the network either in plain text or encrypted, but +not both in the same authentication request. +

    +When encrypted passwords are used a password that has been entered by the user +is encrypted in two ways: +

    • An MD4 hash of the UNICODE of the password + string. This is known as the NT hash. +

    • The password is converted to upper case, + and then padded or trucated to 14 bytes. This string is + then appended with 5 bytes of NULL characters and split to + form two 56 bit DES keys to encrypt a "magic" 8 byte value. + The resulting 16 bytes for the LanMan hash. +

    +MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 +pre-service pack 3 will use either mode of password authentication. All +versions of MS Windows that follow these versions no longer support plain +text passwords by default. +

    +MS Windows clients have a habit of dropping network mappings that have been idle +for 10 minutes or longer. When the user attempts to use the mapped drive +connection that has been dropped, the client re-establishes the connection using +a cached copy of the password. +

    +When Microsoft changed the default password mode, support was dropped for caching +of the plain text password. This means that when the registry parameter is changed +to re-enable use of plain text passwords it appears to work, but when a dropped +service connection mapping attempts to revalidate it will fail if the remote +authentication server does not support encrypted passwords. This means that it +is definitely not a good idea to re-enable plain text password support in such clients. +

    +The following parameters can be used to work around the issue of Windows 9x client +upper casing usernames and password before transmitting them to the SMB server +when using clear text authentication. +

    +	passsword level = integer
+	username level = integer
+

    +By default Samba will lower case the username before attempting to lookup the user +in the database of local system accounts. Because UNIX usernames conventionally +only contain lower case character, the username level parameter +is rarely needed. +

    +However, passwords on UNIX systems often make use of mixed case characters. +This means that in order for a user on a Windows 9x client to connect to a Samba +server using clear text authentication, the password level +must be set to the maximum number of upper case letter which could +appear is a password. Note that the server OS uses the traditional DES version +of crypt(), a password level of 8 will result in case +insensitive passwords as seen from Windows users. This will also result in longer +login times as Samba has to compute the permutations of the password string and +try them one by one until a match is located (or all combinations fail). +

    +The best option to adopt is to enable support for encrypted passwords +where ever Samba is used. There are three configuration possibilities +for support of encrypted passwords: +

    Use MS Windows NT as an authentication server

    +This method involves the additions of the following parameters in the smb.conf file: +

    +	encrypt passwords = Yes
+	security = server
+	password server = "NetBIOS_name_of_PDC"
+

    +There are two ways of identifying whether or not a username and +password pair was valid or not. One uses the reply information provided +as part of the authentication messaging process, the other uses +just an error code. +

    +The down-side of this mode of configuration is the fact that +for security reasons Samba will send the password server a bogus +username and a bogus password and if the remote server fails to +reject the username and password pair then an alternative mode +of identification of validation is used. Where a site uses password +lock out after a certain number of failed authentication attempts +this will result in user lockouts. +

    +Use of this mode of authentication does require there to be +a standard Unix account for the user, this account can be blocked +to prevent logons by other than MS Windows clients. +

    Domain Level Security

    +When samba is operating in security = domain mode this means that +the Samba server has a domain security trust account (a machine account) and will cause +all authentication requests to be passed through to the domain controllers. +

    Samba as a member of an MS Windows NT security domain

    +This method involves addition of the following parameters in the smb.conf file: +

    +	encrypt passwords = Yes
+	security = domain
+	workgroup = "name of NT domain"
+	password server = *
+

    +The use of the "*" argument to password server will cause samba to locate the +domain controller in a way analogous to the way this is done within MS Windows NT. +This is the default behaviour. +

    +In order for this method to work the Samba server needs to join the +MS Windows NT security domain. This is done as follows: +

    • On the MS Windows NT domain controller using + the Server Manager add a machine account for the Samba server. +

    • Next, on the Linux system execute: + smbpasswd -r PDC_NAME -j DOMAIN_NAME (samba 2.x) -where: -

      a.b.c.d and -e.f.g.h

      is either the LMB (Local Master Browser) IP address -or the broadcst address of the remote network. -ie: the LMB is at 192.168.1.10, or the address -could be given as 192.168.1.255 where the netmask -is assumed to be 24 bits (255.255.255.0). -When the remote announcement is made to the broadcast -address of the remote network every host will receive -our announcements. This is noisy and therefore -undesirable but may be necessary if we do NOT know -the IP address of the remote LMB.

      WORKGROUP

      is optional and can be either our own workgroup -or that of the remote network. If you use the -workgroup name of the remote network then our -NetBIOS machine names will end up looking like -they belong to that workgroup, this may cause -name resolution problems and should be avoided.

    3.4. Use of the Remote Browse Sync parameter

    The remote browse sync parameter of -smb.conf is used to announce to -another LMB that it must synchronise it's NetBIOS name list with our -Samba LMB. It works ONLY if the Samba server that has this option is -simultaneously the LMB on it's network segment.

    The syntax of the remote browse sync parameter is: + net join -U administrator%password (samba-3) +

    +Use of this mode of authentication does require there to be a standard Unix account +for the user in order to assign a uid once the account has been authenticated by +the remote Windows DC. This account can be blocked to prevent logons by clients other than +MS Windows through things such as setting an invalid shell in the +/etc/passwd entry. +

    +An alternative to assigning UIDs to Windows users on a Samba member server is +presented in the Winbind Overview chapter +in this HOWTO collection. +

    ADS Level Security

    +For information about the configuration option please refer to the entire section entitled +Samba as an ADS Domain Member. +

    Chapter5. +Samba as an NT4 or Win2k Primary Domain Controller +

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    David Bannon

    Samba Team

    <dbannon@samba.org>

    (26 Apr 2001)

    Table of Contents

    Prerequisite Reading
    +Background +
    Configuring the Samba Domain Controller
    Creating Machine Trust Accounts and Joining Clients to the Domain
    Manual Creation of Machine Trust Accounts
    "On-the-Fly" Creation of Machine Trust Accounts
    Joining the Client to the Domain
    Common Problems and Errors
    I cannot include a '$' in a machine name
    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not +exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    Domain Control for Windows 9x/ME
    Configuration Instructions: Network Logons

    Prerequisite Reading

    +Before you continue reading in this chapter, please make sure +that you are comfortable with configuring basic files services +in smb.conf and how to enable and administer password +encryption in Samba. Theses two topics are covered in the +smb.conf manpage. +

    +Background +

    +This article outlines the steps necessary for configuring Samba as a PDC. +It is necessary to have a working Samba server prior to implementing the +PDC functionality. +

    • + Domain logons for Windows NT 4.0 / 200x / XP Professional clients. +

    • + Placing Windows 9x / Me clients in user level security +

    • + Retrieving a list of users and groups from a Samba PDC to + Windows 9x / Me / NT / 200x / XP Professional clients +

    • + Roaming Profiles +

    • + Network/System Policies +

    Note

    +Roaming Profiles and System/Network policies are advanced network administration topics +that are covered separately in this document. +

    +The following functionalities are new to the Samba 3.0 release: +

    • + Windows NT 4 domain trusts +

    • + Adding users via the User Manager for Domains +

    +The following functionalities are NOT provided by Samba 3.0: +

    • + SAM replication with Windows NT 4.0 Domain Controllers + (i.e. a Samba PDC and a Windows NT BDC or vice versa) +

    • + Acting as a Windows 2000 Domain Controller (i.e. Kerberos and + Active Directory) +

    +Please note that Windows 9x / Me / XP Home clients are not true members of a domain +for reasons outlined in this article. Therefore the protocol for +support of Windows 9x-style domain logons is completely different +from NT4 / Win2k type domain logons and has been officially supported for some +time. +

    +MS Windows XP Home edition is NOT able to join a domain and does not permit +the use of domain logons. +

    +Implementing a Samba PDC can basically be divided into 3 broad +steps. +

    1. + Configuring the Samba PDC +

    2. + Creating machine trust accounts and joining clients to the domain +

    3. + Adding and managing domain user accounts +

    +There are other minor details such as user profiles, system +policies, etc... However, these are not necessarily specific +to a Samba PDC as much as they are related to Windows NT networking +concepts. +

    Configuring the Samba Domain Controller

    +The first step in creating a working Samba PDC is to +understand the parameters necessary in smb.conf. Here we +attempt to explain the parameters that are covered in +the smb.conf man page. +

    +Here is an example smb.conf for acting as a PDC: +

    +[global]
+    ; Basic server settings
+    netbios name = POGO
+    workgroup = NARNIA
 
-
    remote browse sync = a.b.c.d
    
+    ; User and Machine Account Backends
+    ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
+    ;              mysqlsam, xmlsam, guest
+    passdb backend = ldapsam, guest
 
-where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.

    3.5. Use of WINS

    Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly -recommended. Every NetBIOS machine registers it's name together with a -name_type value for each of of several types of service it has available. -eg: It registers it's name directly as a unique (the type 0x03) name. -It also registers it's name if it is running the lanmanager compatible -server service (used to make shares and printers available to other users) -by registering the server (the type 0x20) name.

    All NetBIOS names are up to 15 characters in length. The name_type variable -is added to the end of the name - thus creating a 16 character name. Any -name that is shorter than 15 characters is padded with spaces to the 15th -character. ie: All NetBIOS names are 16 characters long (including the -name_type information).

    WINS can store these 16 character names as they get registered. A client -that wants to log onto the network can ask the WINS server for a list -of all names that have registered the NetLogon service name_type. This saves -broadcast traffic and greatly expedites logon processing. Since broadcast -name resolution can not be used across network segments this type of -information can only be provided via WINS _or_ via statically configured -lmhosts files that must reside on all clients in the -absence of WINS.

    WINS also serves the purpose of forcing browse list synchronisation by all -LMB's. LMB's must synchronise their browse list with the DMB (domain master -browser) and WINS helps the LMB to identify it's DMB. By definition this -will work only within a single workgroup. Note that the domain master browser -has NOTHING to do with what is referred to as an MS Windows NT Domain. The -later is a reference to a security environment while the DMB refers to the -master controller for browse list information only.

    Use of WINS will work correctly only if EVERY client TCP/IP protocol stack -has been configured to use the WINS server/s. Any client that has not been -configured to use the WINS server will continue to use only broadcast based -name registration so that WINS may NEVER get to know about it. In any case, -machines that have not registered with a WINS server will fail name to address -lookup attempts by other clients and will therefore cause workstation access -errors.

    To configure Samba as a WINS server just add -wins support = yes to the smb.conf -file [globals] section.

    To configure Samba to register with a WINS server just add -"wins server = a.b.c.d" to your smb.conf file [globals] section.

    Never use both wins support = yes together -with wins server = a.b.c.d -particularly not using it's own IP address. -Specifying both will cause nmbd to refuse to start!

    3.5.1. WINS Replication

    Samba-3 permits WINS replication through the use of the wrepld utility. -This tool is not currently capable of being used as it is still in active development. -As soon as this tool becomes moderately functional we will prepare man pages and enhance this -section of the documentation to provide usage and technical details.

    3.5.2. Static WINS Entries

    New to Samba-3 is a tool called winsedit that may be used to add -static WINS entries to the WINS database. This tool can be used also to modify entries -existing in the WINS database.

    The development of the winsedit tool was made necessary due to the migration -of the older style wins.dat file into a new tdb binary backend data store.

    3.6. Do NOT use more than one (1) protocol on MS Windows machines

    A very common cause of browsing problems results from installing more than -one protocol on an MS Windows machine.

    Every NetBIOS machine takes part in a process of electing the LMB (and DMB) -every 15 minutes. A set of election criteria is used to determine the order -of precidence for winning this election process. A machine running Samba or -Windows NT will be biased so that the most suitable machine will predictably -win and thus retain it's role.

    The election process is "fought out" so to speak over every NetBIOS network -interface. In the case of a Windows 9x machine that has both TCP/IP and IPX -installed and has NetBIOS enabled over both protocols the election will be -decided over both protocols. As often happens, if the Windows 9x machine is -the only one with both protocols then the LMB may be won on the NetBIOS -interface over the IPX protocol. Samba will then lose the LMB role as Windows -9x will insist it knows who the LMB is. Samba will then cease to function -as an LMB and thus browse list operation on all TCP/IP only machines will -fail.

    Windows 95, 98, 98se, Me are referred to generically as Windows 9x. -The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly -referred to as the WinNT family, but it should be recognised that 2000 and -XP/2003 introduce new protocol extensions that cause them to behave -differently from MS Windows NT4. Generally, where a server does NOT support -the newer or extended protocol, these will fall back to the NT4 protocols.

    The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!

    3.7. Name Resolution Order

    Resolution of NetBIOS names to IP addresses can take place using a number -of methods. The only ones that can provide NetBIOS name_type information -are:

    WINS: the best tool!
    LMHOSTS: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.

    Alternative means of name resolution includes:

    /etc/hosts: is static, hard to maintain, and lacks name_type info
    DNS: is a good choice but lacks essential name_type info.

    Many sites want to restrict DNS lookups and want to avoid broadcast name -resolution traffic. The "name resolve order" parameter is of great help here. -The syntax of the "name resolve order" parameter is: -

    name resolve order = wins lmhosts bcast host
    -_or_ -
    name resolve order = wins lmhosts  	(eliminates bcast and host)
    -The default is: -
    name  resolve order = host lmhost wins bcast
    . -where "host" refers the the native methods used by the Unix system -to implement the gethostbyname() function call. This is normally -controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf.

    Chapter 4. User information database

    4.1. Introduction

    Old windows clients send plain text passwords over the wire. - Samba can check these passwords by crypting them and comparing them - to the hash stored in the unix user database. -

    Newer windows clients send encrypted passwords (so-called - Lanman and NT hashes) over - the wire, instead of plain text passwords. The newest clients - will only send encrypted passwords and refuse to send plain text - passwords, unless their registry is tweaked. -

    These passwords can't be converted to unix style encrypted - passwords. Because of that you can't use the standard unix - user database, and you have to store the Lanman and NT hashes - somewhere else.

    Next to a differently encrypted passwords, - windows also stores certain data for each user - that is not stored in a unix user database, e.g. - workstations the user may logon from, the location where his/her - profile is stored, etc. - Samba retrieves and stores this information using a "passdb backend". - Commonly - available backends are LDAP, plain text file, MySQL and nisplus. - For more information, see the documentation about the - passdb backend = parameter. -

    4.2. Important Notes About Security

    The unix and SMB password encryption techniques seem similar - on the surface. This similarity is, however, only skin deep. The unix - scheme typically sends clear text passwords over the network when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext password over the network but it does store the 16 byte - hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's - password from them, but they could potentially be used in a modified - client to gain access to a server. This would require considerable - technical knowledge on behalf of the attacker but is perfectly possible. - You should thus treat the data stored in whatever - passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.

    Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc).

    Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are never sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.

    Other Microsoft operating systems which also exhibit - this behavior includes

    These versions of MS Windows do not support full domain - security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.

    MS DOS Network client 3.0 with - the basic network redirector installed
    Windows 95 with the network redirector - update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain - security protocols.

    Windows NT 3.5x
    Windows NT 4.0
    Windows 2000 Professional
    Windows 200x Server/Advanced Server
    Windows XP Professional

    All current release of - Microsoft SMB/CIFS clients support authentication via the - SMB Challenge/Response mechanism described here. Enabling - clear text authentication does not disable the ability - of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. - Even when plain text passwords are re-enabled, through the appropriate - registry change, the plain text password is NEVER cached. This means that - in the event that a network connections should become disconnected (broken) - only the cached (encrypted) password will be sent to the resource server - to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.

    4.2.1. Advantages of SMB Encryption

    Plain text passwords are not passed across - the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.
    WinNT doesn't like talking to a server - that SM not support encrypted passwords. It will refuse - to browse the server if the server is also in user level - security mode. It will insist on prompting the user for the - password on each connection, which is very annoying. The - only things you can do to stop this is to use SMB encryption. -
    Encrypted password support allows automatic share - (resource) reconnects.

    4.2.2. Advantages of non-encrypted passwords

    Plain text passwords are not kept - on disk, and are NOT cached in memory.
    Uses same password file as other unix - services such as login and ftp
    Use of other services (such as telnet and ftp) which - send plain text passwords over the net, so sending them for SMB - isn't such a big deal.

    4.3. The smbpasswd Command

    The smbpasswd utility is a utility similar to the - passwd or yppasswd programs. - It maintains the two 32 byte password fields in the passdb backend.

    smbpasswd works in a client-server mode - where it contacts the local smbd to change the user's password on its - behalf. This has enormous benefits - as follows.

    smbpasswd has the capability - to change passwords on Windows NT servers (this only works when - the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).

    To run smbpasswd as a normal user just type :

    $ smbpasswd

    Old SMB password: <type old value here - - or hit return if there was no old password>

    New SMB Password: <type new value> -

    Repeat New SMB Password: <re-type new value -

    If the old value does not match the current value stored for - that user, or the two new values do not match each other, then the - password will not be changed.

    If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.

    If run by the root user smbpasswd may take an optional - argument, specifying the user name whose SMB password you wish to - change. Note that when run as root smbpasswd does not prompt for - or check the old password value, thus allowing root to set passwords - for users who have forgotten their passwords.

    smbpasswd is designed to work in the same way - and be familiar to UNIX users who use the passwd or - yppasswd commands.

    For more details on using smbpasswd refer - to the man page which will always be the definitive reference.

    4.4. Plain text

    Older versions of samba retrieved user information from the unix user database -and eventually some other fields from the file /etc/samba/smbpasswd -or /etc/smbpasswd. When password encryption is disabled, no -data is stored at all.

    4.5. TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend -doesn't require any additional configuration. This backend is recommended for new installations who -don't require LDAP.

    4.6. LDAP

    4.6.1. Introduction

    This document describes how to use an LDAP directory for storing Samba user -account information traditionally stored in the smbpasswd(5) file. It is -assumed that the reader already has a basic understanding of LDAP concepts -and has a working directory server already installed. For more information -on LDAP architectures and Directories, please refer to the following sites.

    Note that O'Reilly Publishing is working on -a guide to LDAP for System Administrators which has a planned release date of -early summer, 2002.

    Two additional Samba resources which may prove to be helpful are

    • The Samba-PDC-LDAP-HOWTO - maintained by Ignacio Coupeau.

    • The NT migration scripts from IDEALX that are - geared to manage users and group in such a Samba-LDAP Domain Controller configuration. -

    4.6.2. Introduction

    Traditionally, when configuring "encrypt -passwords = yes" in Samba's smb.conf file, user account -information such as username, LM/NT password hashes, password change times, and account -flags have been stored in the smbpasswd(5) file. There are several -disadvantages to this approach for sites with very large numbers of users (counted -in the thousands).

    • The first is that all lookups must be performed sequentially. Given that -there are approximately two lookups per domain logon (one for a normal -session connection such as when mapping a network drive or printer), this -is a performance bottleneck for lareg sites. What is needed is an indexed approach -such as is used in databases.

    • The second problem is that administrators who desired to replicate a -smbpasswd file to more than one Samba server were left to use external -tools such as rsync(1) and ssh(1) -and wrote custom, in-house scripts.

    • And finally, the amount of information which is stored in an -smbpasswd entry leaves no room for additional attributes such as -a home directory, password expiration time, or even a Relative -Identified (RID).

    As a result of these defeciencies, a more robust means of storing user attributes -used by smbd was developed. The API which defines access to user accounts -is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees).

    There are a few points to stress about what the ldapsam -does not provide. The LDAP support referred to in the this documentation does not -include:

    • A means of retrieving user account information from - an Windows 2000 Active Directory server.

    • A means of replacing /etc/passwd.

    The second item can be accomplished by using LDAP NSS and PAM modules. LGPL -versions of these libraries can be obtained from PADL Software -(http://www.padl.com/). However, -the details of configuring these packages are beyond the scope of this document.

    4.6.3. Supported LDAP Servers

    The LDAP samdb code in 2.2.3 (and later) has been developed and tested -using the OpenLDAP 2.0 server and client libraries. -The same code should be able to work with Netscape's Directory Server -and client SDK. However, due to lack of testing so far, there are bound -to be compile errors and bugs. These should not be hard to fix. -If you are so inclined, please be sure to forward all patches to -samba-patches@samba.org and -jerry@samba.org.

    4.6.4. Schema and Relationship to the RFC 2307 posixAccount

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in -examples/LDAP/samba.schema. The sambaAccount objectclass is given here:

    objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
-     DESC 'Samba Account'
-     MUST ( uid $ rid )
-     MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
-            logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
-            displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
-            description $ userWorkstations $ primaryGroupID $ domain ))

    The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are -owned by the Samba Team and as such is legal to be openly published. -If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to jerry@samba.org

    Just as the smbpasswd file is mean to store information which supplements a -user's /etc/passwd entry, so is the sambaAccount object -meant to supplement the UNIX user account information. A sambaAccount is a -STRUCTURAL objectclass so it can be stored individually -in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design.

    In order to store all user account information (UNIX and Samba) in the directory, -it is necessary to use the sambaAccount and posixAccount objectclasses in -combination. However, smbd will still obtain the user's UNIX account -information via the standard C library calls (e.g. getpwnam(), et. al.). -This means that the Samba server must also have the LDAP NSS library installed -and functioning correctly. This division of information makes it possible to -store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure.

    4.6.5. Configuring Samba with LDAP

    4.6.5.1. OpenLDAP configuration

    To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory.

    root# cp samba.schema /etc/openldap/schema/

    Next, include the samba.schema file in slapd.conf. -The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in cosine.schema and -the 'displayName' attribute is defined in the inetorgperson.schema -file. Both of these must be included before the samba.schema file.

    ## /etc/openldap/slapd.conf
-
-## schema files (core.schema is required by default)
-include	           /etc/openldap/schema/core.schema
+    ; we should act as the domain and local master browser
+    os level = 64
+    preferred master = yes
+    domain master = yes
+    local master = yes
+    
+    ; security settings (must user security = user)
+    security = user
+    
+    ; encrypted passwords are a requirement for a PDC
+    encrypt passwords = yes
+    
+    ; support domain logons
+    domain logons = yes
+    
+    ; where to store user profiles?
+    logon path = \\%N\profiles\%u
+    
+    ; where is a user's home directory and where should it be mounted at?
+    logon drive = H:
+    logon home = \\homeserver\%u
+    
+    ; specify a generic logon script for all users
+    ; this is a relative **DOS** path to the [netlogon] share
+    logon script = logon.cmd
 
-## needed for sambaAccount
-include            /etc/openldap/schema/cosine.schema
-include            /etc/openldap/schema/inetorgperson.schema
-include            /etc/openldap/schema/samba.schema
-include            /etc/openldap/schema/nis.schema
+; necessary share for domain controller
+[netlogon]
+    path = /usr/local/samba/lib/netlogon
+    read only = yes
+    write list = ntadmin
+    
+; share for storing user profiles
+[profiles]
+    path = /export/smb/ntprofile
+    read only = no
+    create mask = 0600
+    directory mask = 0700
+

    Note

    +The above parameters make for a full set of parameters that may define the server's mode +of operation. The following parameters are the essentials alone: -....

    It is recommended that you maintain some indices on some of the most usefull attributes, -like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well).

    # Indices to maintain
-## required by OpenLDAP 2.0
-index objectclass   eq
+
    +	workgroup = NARNIA
+	domain logons = Yes
+	security = User
+
    
 
-## support pb_getsampwnam()
-index uid           pres,eq
-## support pdb_getsambapwrid()
-index rid           eq
+The additional parameters shown in the longer listing above just makes for a
+more complete environment.
+

    +There are a couple of points to emphasize in the above configuration. +

    • + Encrypted passwords must be enabled. For more details on how + to do this, refer to the User Database chapter. +

    • + The server must support domain logons and a + [netlogon] share +

    • + The server must be the domain master browser in order for Windows + client to locate the server as a DC. Please refer to the various + Network Browsing documentation included with this distribution for + details. +

    +Samba 3.0 offers a complete implementation of group mapping +between Windows NT groups and Unix groups (this is really quite +complicated to explain in a short space). +

    Creating Machine Trust Accounts and Joining Clients to the Domain

    +A machine trust account is a Samba account that is used to +authenticate a client machine (rather than a user) to the Samba +server. In Windows terminology, this is known as a "Computer +Account."

    +The password of a machine trust account acts as the shared secret for +secure communication with the Domain Controller. This is a security +feature to prevent an unauthorized machine with the same NetBIOS name +from joining the domain and gaining access to domain user/group +accounts. Windows NT, 200x, XP Professional clients use machine trust +accounts, but Windows 9x / Me / XP Home clients do not. Hence, a +Windows 9x / Me / XP Home client is never a true member of a domain +because it does not possess a machine trust account, and thus has no +shared secret with the domain controller. +

    A Windows PDC stores each machine trust account in the Windows +Registry. A Samba-3 PDC also has to store machine trust account information +in a suitable backend data store. With Samba-3 there can be multiple back-ends +for this including: +

    • + smbpasswd - the plain ascii file stored used by + earlier versions of Samba. This file configuration option requires + a Unix/Linux system account for EVERY entry (ie: both for user and for + machine accounts). This file will be located in the private + directory (default is /usr/local/samba/lib/private or on linux /etc/samba). +

    • + smbpasswd_nua - This file is independant of the + system wide user accounts. The use of this back-end option requires + specification of the "non unix account range" option also. It is called + smbpasswd and will be located in the private directory. +

    • + tdbsam - a binary database backend that will be + stored in the private directory in a file called + passwd.tdb. The key benefit of this binary format + file is that it can store binary objects that can not be accomodated + in the traditional plain text smbpasswd file. +

    • + tdbsam_nua like the smbpasswd_nua option above, this + file allows the creation of arbitrary user and machine accounts without + requiring that account to be added to the system (/etc/passwd) file. It + too requires the specification of the "non unix account range" option + in the [globals] section of the smb.conf file. +

    • + ldapsam - An LDAP based back-end. Permits the + LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com +

    • + ldapsam_nua - LDAP based back-end with no unix + account requirement, like smbpasswd_nua and tdbsam_nua above. +

    Read the chapter about the User Database +for details.

    Note

    +The new tdbsam and ldapsam account backends store vastly more information than +smbpasswd is capable of. The new backend database includes capacity to specify +per user settings for many parameters, over-riding global settings given in the +smb.conf file. eg: logon drive, logon home, logon path, etc. +

    +A Samba PDC, however, stores each machine trust account in two parts, +as follows: -## uncomment these if you are storing posixAccount and -## posixGroup entries in the directory as well -##index uidNumber eq -##index gidNumber eq -##index cn eq -##index memberUid eq

    4.6.5.2. Configuring Samba

    The following parameters are available in smb.conf only with --with-ldapsam -was included with compiling Samba.

    These are described in the smb.conf(5) man -page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as

    ## /usr/local/samba/lib/smb.conf
+
    • A Samba account, stored in the same location as user
+    LanMan and NT password hashes (currently
+    smbpasswd). The Samba account 
+    possesses and uses only the NT password hash.
    • A corresponding Unix account, typically stored in
+    /etc/passwd. (Future releases will alleviate the need to
+    create /etc/passwd entries.) 
    
+
    
+There are two ways to create machine trust accounts:
+
    •  Manual creation. Both the Samba and corresponding
+	Unix account are created by hand.
    •  "On-the-fly" creation. The Samba machine trust
+	account is automatically created by Samba at the time the client
+	is joined to the domain. (For security, this is the
+	recommended method.) The corresponding Unix account may be
+	created automatically or manually. 
    Manual Creation of Machine Trust Accounts
    
+The first step in manually creating a machine trust account is to
+manually create the corresponding Unix account in
+/etc/passwd.  This can be done using
+vipw or other 'add user' command that is normally
+used to create new Unix accounts.  The following is an example for a
+Linux based Samba server:
+
    
+  root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine 
+nickname" -s /bin/false machine_name$ 
+
    
+root# passwd -l machine_name$
+
    On *BSD systems, this can be done using the 'chpass' utility:
    
+root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"
+
    
+The /etc/passwd entry will list the machine name 
+with a "$" appended, won't have a password, will have a null shell and no 
+home directory. For example a machine named 'doppy' would have an 
+/etc/passwd entry like this:
+
    +doppy$:x:505:501:machine_nickname:/dev/null:/bin/false
+
    
+Above, machine_nickname can be any
+descriptive name for the client, i.e., BasementComputer.
+machine_name absolutely must be the NetBIOS
+name of the client to be joined to the domain.  The "$" must be
+appended to the NetBIOS name of the client or Samba will not recognize
+this as a machine trust account.
+
    
+Now that the corresponding Unix account has been created, the next step is to create 
+the Samba account for the client containing the well-known initial 
+machine trust account password.  This can be done using the smbpasswd(8) command 
+as shown here:
+
    
+root# smbpasswd -a -m machine_name
+
    
+where machine_name is the machine's NetBIOS
+name.  The RID of the new machine account is generated from the UID of 
+the corresponding Unix account.
+
    Join the client to the domain immediately
    
+	Manually creating a machine trust account using this method is the 
+	equivalent of creating a machine trust account on a Windows NT PDC using 
+	the "Server Manager".  From the time at which the account is created
+	to the time which the client joins the domain and changes the password,
+	your domain is vulnerable to an intruder joining your domain using
+	a machine with the same NetBIOS name.  A PDC inherently trusts
+	members of the domain and will serve out a large degree of user 
+	information to such clients.  You have been warned!
+	
    "On-the-Fly" Creation of Machine Trust Accounts
    
+The second (and recommended) way of creating machine trust accounts is
+simply to allow the Samba server to create them as needed when the client
+is joined to the domain. 
    Since each Samba machine trust account requires a corresponding
+Unix account, a method for automatically creating the
+Unix account is usually supplied; this requires configuration of the
+add user script 
+option in smb.conf.  This
+method is not required, however; corresponding Unix accounts may also
+be created manually.
+
    Below is an example for a RedHat 6.2 Linux system.
+
     [global]
-     security = user
-     encrypt passwords = yes
-
-     netbios name = TASHTEGO
-     workgroup = NARNIA
-
-     # ldap related parameters
-
-     # define the DN to use when binding to the directory servers
-     # The password for this DN is not stored in smb.conf.  Rather it
-     # must be set by using 'smbpasswd -w secretpw' to store the
-     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
-     # changes, this password will need to be reset.
-     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
-
-     #  specify the LDAP server's hostname (defaults to locahost)
-     ldap server = ahab.samba.org
-
-     # Define the SSL option when connecting to the directory
-     # ('off', 'start tls', or 'on' (default))
-     ldap ssl = start tls
-
-     # define the port to use in the LDAP session (defaults to 636 when
-     # "ldap ssl = on")
-     ldap port = 389
-
-     # specify the base DN to use when searching the directory
-     ldap suffix = "ou=people,dc=samba,dc=org"
-
-     # generally the default ldap search filter is ok
-     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"

    4.6.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.

    Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts -in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your -NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).

    In Samba release 3.0, the group management system is based on posix -groups. This means that Samba make usage of the posixGroup objectclass. -For now, there is no NT-like group system management (global and local -groups).

    4.6.7. Security and sambaAccount

    There are two important points to remember when discussing the security -of sambaAccount entries in the directory.

    • Never retrieve the lmPassword or - ntPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to - view the lmPassword or ntPassword attribute values.

    These password hashes are clear text equivalents and can be used to impersonate -the user without deriving the original clear text strings. For more information -on the details of LM/NT password hashes, refer to the User Database of the Samba-HOWTO-Collection.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults -to require an encrypted session (ldap ssl = on) using -the default port of 636 -when contacting the directory server. When using an OpenLDAP 2.0 server, it -is possible to use the use the StartTLS LDAP extended operation in the place of -LDAPS. In either case, you are strongly discouraged to disable this security -(ldap ssl = off).

    Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS -extended operation. However, the OpenLDAP library still provides support for -the older method of securing communication between clients and servers.

    The second security precaution is to prevent non-administrative users from -harvesting password hashes from the directory. This can be done using the -following ACL in slapd.conf:

    ## allow the "ldap admin dn" access, but deny everyone else
-access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
-     by * none

    4.6.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    • lmPassword: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the - lmPassword and ntPassword attributes were last set. -

    • acctFlags: string of 11 characters surrounded by square brackets [] - representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • homeDrive: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.

    • scriptPath: The scriptPath property specifies the path of - the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.

    • profilePath: specifies a path to the user's profile. - This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.

    • smbHome: The homeDirectory property specifies the path of - the home directory for the user. The string can be null. If homeDrive is set and specifies - a drive letter, homeDirectory should be a UNC path. The path must be a network - UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. -

    • userWorkstation: character string value currently unused. -

    • rid: the integer representation of the user's relative identifier - (RID).

    • primaryGroupID: the relative identifier (RID) of the primary group - of the user.

    The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the Samba-PDC-HOWTO for details on -how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values:

    • smbHome

    • scriptPath

    • logonPath

    • homeDrive

    These attributes are only stored with the sambaAccount entry if -the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that logon home = \\%L\%u was defined in -its smb.conf file. When a user named "becky" logons to the domain, -the logon home string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", -this value is used. However, if this attribute does not exist, then the value -of the logon home parameter is used in its place. Samba -will only write the attribute value to the directory entry is the value is -something other than the default (e.g. \\MOBY\becky).

    4.6.9. Example LDIF Entries for a sambaAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    dn: uid=guest2, ou=people,dc=plainjoe,dc=org
-ntPassword: 878D8014606CDA29677A44EFA1353FC7
-pwdMustChange: 2147483647
-primaryGroupID: 1201
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-pwdLastSet: 1010179124
-logonTime: 0
-objectClass: sambaAccount
-uid: guest2
-kickoffTime: 2147483647
-acctFlags: [UX         ]
-logoffTime: 2147483647
-rid: 19006
-pwdCanChange: 0

    The following is an LDIF entry for using both the sambaAccount and -posixAccount objectclasses:

    dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
-logonTime: 0
-displayName: Gerald Carter
-lmPassword: 552902031BEDE9EFAAD3B435B51404EE
-primaryGroupID: 1201
-objectClass: posixAccount
-objectClass: sambaAccount
-acctFlags: [UX         ]
-userPassword: {crypt}BpM2ej8Rkzogo
-uid: gcarter
-uidNumber: 9000
-cn: Gerald Carter
-loginShell: /bin/bash
-logoffTime: 2147483647
-gidNumber: 100
-kickoffTime: 2147483647
-pwdLastSet: 1010179230
-rid: 19000
-homeDirectory: /home/tashtego/gcarter
-pwdCanChange: 0
-pwdMustChange: 2147483647
-ntPassword: 878D8014606CDA29677A44EFA1353FC7

    4.7. MySQL

    4.7.1. Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below -for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump -contains the correct queries to create the required tables. Use the command : + # <...remainder of parameters...> + add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u +

    Joining the Client to the Domain

    +The procedure for joining a client to the domain varies with the +version of Windows. +

    • Windows 2000

      + When the user elects to join the client to a domain, Windows prompts for + an account and password that is privileged to join the domain. A Samba administrative + account (i.e., a Samba account that has root privileges on the Samba server) must be + entered here; the operation will fail if an ordinary user account is given. + The password for this account should be set to a different password than the associated + /etc/passwd entry, for security reasons. +

      + The session key of the Samba administrative account acts as an + encryption key for setting the password of the machine trust + account. The machine trust account will be created on-the-fly, or + updated if it already exists. +

    • Windows NT

      If the machine trust account was created manually, on the + Identification Changes menu enter the domain name, but do not + check the box "Create a Computer Account in the Domain." In this case, + the existing machine trust account is used to join the machine to + the domain.

      If the machine trust account is to be created + on-the-fly, on the Identification Changes menu enter the domain + name, and check the box "Create a Computer Account in the Domain." In + this case, joining the domain proceeds as above for Windows 2000 + (i.e., you must supply a Samba administrative account when + prompted).

    • Samba

      Joining a samba client to a domain is documented in + the Domain Member chapter. +

    Common Problems and Errors

    I cannot include a '$' in a machine name

    +A 'machine name' in (typically) /etc/passwd +of the machine name with a '$' appended. FreeBSD (and other BSD +systems?) won't create a user with a '$' in their name. +

    +The problem is only in the program used to make the entry. Once made, it works perfectly. +Create a user without the '$' using vipw to edit the entry, adding +the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID! +

    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.

    +This happens if you try to create a machine trust account from the +machine itself and already have a connection (e.g. mapped drive) +to a share (or IPC$) on the Samba PDC. The following command +will remove all network drive connections: +

    +C:\WINNT\> net use * /d +

    +Further, if the machine is already a 'member of a workgroup' that +is the same name as the domain you are joining (bad idea) you will +get this message. Change the workgroup name to something else, it +does not matter what, reboot, and try again. +

    The system can not log you on (C000019B)....

    I joined the domain successfully but after upgrading +to a newer version of the Samba code I get the message, "The system +can not log you on (C000019B), Please try again or consult your +system administrator" when attempting to logon. +

    +This occurs when the domain SID stored in the secrets.tdb database +is changed. The most common cause of a change in domain SID is when +the domain name and/or the server name (netbios name) is changed. +The only way to correct the problem is to restore the original domain +SID or remove the domain client from the domain and rejoin. The domain +SID may be reset using either the net or rpcclient utilities. +

    +The reset or change the domain SID you can use the net command as follows: -mysql -uusername -hhostname -ppassword databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    4.7.2. Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: -

    passdb backend = [other-plugins] mysql:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with -the identifiers of other plugins or other instances of pdb_mysql. If you -specify multiple pdb_mysql.so entries in 'passdb backend', you also need to -use different identifiers!

    Additional options can be given thru the smb.conf file in the [global] section.

    identifier:mysql host                     - host name, defaults to 'localhost'
-identifier:mysql password
-identifier:mysql user                     - defaults to 'samba'
-identifier:mysql database                 - defaults to 'samba'
-identifier:mysql port                     - defaults to 3306
-identifier:table                          - Name of the table containing users

    Since the password for the mysql user is stored in the -smb.conf file, you should make the the smb.conf file -readable only to the user that runs samba. This is considered a security -bug and will be fixed soon.

    Names of the columns in this table(I've added column types those columns should have first):

    identifier:logon time column             - int(9)
-identifier:logoff time column            - int(9)
-identifier:kickoff time column           - int(9)
-identifier:pass last set time column     - int(9)
-identifier:pass can change time column   - int(9)
-identifier:pass must change time column  - int(9)
-identifier:username column               - varchar(255) - unix username
-identifier:domain column                 - varchar(255) - NT domain user is part of
-identifier:nt username column            - varchar(255) - NT username
-identifier:fullname column            - varchar(255) - Full name of user
-identifier:home dir column               - varchar(255) - Unix homedir path
-identifier:dir drive column              - varchar(2) - Directory drive path (eg: 'H:')
-identifier:logon script column           - varchar(255) - Batch file to run on client side when logging on
-identifier:profile path column           - varchar(255) - Path of profile
-identifier:acct desc column              - varchar(255) - Some ASCII NT user data
-identifier:workstations column           - varchar(255) - Workstations user can logon to (or NULL for all)
-identifier:unknown string column         - varchar(255) - unknown string
-identifier:munged dial column            - varchar(255) - ?
-identifier:uid column                    - int(9) - Unix user ID (uid)
-identifier:gid column                    - int(9) - Unix user group (gid)
-identifier:user sid column               - varchar(255) - NT user SID
-identifier:group sid column              - varchar(255) - NT group ID
-identifier:lanman pass column            - varchar(255) - encrypted lanman password
-identifier:nt pass column                - varchar(255) - encrypted nt passwd
-identifier:plain pass column             - varchar(255) - plaintext password
-identifier:acct control column           - int(9) - nt user data
-identifier:unknown 3 column              - int(9) - unknown
-identifier:logon divs column             - int(9) - ?
-identifier:hours len column              - int(9) - ?
-identifier:unknown 5 column              - int(9) - unknown
-identifier:unknown 6 column              - int(9) - unknown

    Eventually, you can put a colon (:) after the name of each column, which -should specify the column to update when updating the table. You can also -specify nothing behind the colon - then the data from the field will not be -updated.

    4.7.3. Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords.

    If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.

    4.7.4. Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    For example, you can set 'identifier:fullname column' to : -CONCAT(First_name,' ',Sur_name)

    Or, set 'identifier:workstations column' to : -NULL

    See the MySQL documentation for more language constructs.

    4.8. XML

    This module requires libxml2 to be installed.

    The usage of pdb_xml is pretty straightforward. To export data, use: - -pdbedit -e xml:filename - -(where filename is the name of the file to put the data in)

    To import data, use: -pdbedit -i xml:filename -e current-pdb - -Where filename is the name to read the data from and current-pdb to put it in.

    II. Type of installation

    Introduction

    Samba can operate in various SMB networks. This part contains information on configuring samba -for various environments.

    Chapter 5. Nomenclature of Server Types

    Adminstrators of Microsoft networks often refer to there being three -different type of servers:

    • Stand Alone Server

    • Domain Member Server

    • Domain Controller

      • Primary Domain Controller

      • Backup Domain Controller

      • ADS Domain Controller

    A network administrator who is familiar with these terms and who -wishes to migrate to or use Samba will want to know what these terms mean -within a Samba context.

    5.1. Stand Alone Server

    The term stand alone server means that the server -will provide local authentication and access control for all resources -that are available from it. In general this means that there will be a -local user database. In more technical terms, it means that resources -on the machine will either be made available in either SHARE mode or in -USER mode. SHARE mode and USER mode security are documented under -discussions regarding "security mode". The smb.conf configuration parameters -that control security mode are: "security = user" and "security = share".

    No special action is needed other than to create user accounts. Stand-alone -servers do NOT provide network logon services, meaning that machines that -use this server do NOT perform a domain logon but instead make use only of -the MS Windows logon which is local to the MS Windows workstation/server.

    Samba tends to blur the distinction a little in respect of what is -a stand alone server. This is because the authentication database may be -local or on a remote server, even if from the samba protocol perspective -the samba server is NOT a member of a domain security context.

    Through the use of PAM (Pluggable Authentication Modules) and nsswitch -(the name service switcher) the source of authentication may reside on -another server. We would be inclined to call this the authentication server. -This means that the samba server may use the local Unix/Linux system -password database (/etc/passwd or /etc/shadow), may use a local smbpasswd -file (/etc/samba/smbpasswd or /usr/local/samba/lib/private/smbpasswd), or -may use an LDAP back end, or even via PAM and Winbind another CIFS/SMB -server for authentication.

    5.2. Domain Member Server

    This mode of server operation involves the samba machine being made a member -of a domain security context. This means by definition that all user authentication -will be done from a centrally defined authentication regime. The authentication -regime may come from an NT3/4 style (old domain technology) server, or it may be -provided from an Active Directory server (ADS) running on MS Windows 2000 or later.

    Of course it should be clear that the authentication back end itself could be from any -distributed directory architecture server that is supported by Samba. This can be -LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc.

    Please refer to the section on Howto configure Samba as a Primary Domain Controller -and for more information regarding how to create a domain machine account for a -domain member server as well as for information regading how to enable the samba -domain member machine to join the domain and to be fully trusted by it.

    5.3. Domain Controller

    Over the years public perceptions of what Domain Control really is has taken on an -almost mystical nature. Before we branch into a brief overview of what Domain Control -is the following types of controller are known:

    5.3.1. Domain Controller Types

    Primary Domain Controller
    Backup Domain Controller
    ADS Domain Controller

    The Primary Domain Controller or PDC plays an important role in the MS -Windows NT3 and NT4 Domain Control architecture, but not in the manner that so many -expect. The PDC seeds the Domain Control database (a part of the Windows registry) and -it plays a key part in synchronisation of the domain authentication database.

    New to Samba-3.0.0 is the ability to use a back-end file that holds the same type of data as -the NT4 style SAM (Security Account Manager) database (one of the registry files). -The samba-3.0.0 SAM can be specified via the smb.conf file parameter "passwd backend" and -valid options include smbpasswd tdbsam ldapsam nisplussam plugin unixsam. -The smbpasswd, tdbsam and ldapsam options can have a "_nua" suffix to indicate that No Unix -Accounts need to be created. In other words, the Samba SAM will be independant of Unix/Linux -system accounts, provided a uid range is defined from which SAM accounts can be created.

    The Backup Domain Controller or BDC plays a key role in servicing network -authentication requests. The BDC is biased to answer logon requests so that on a network segment -that has a BDC and a PDC the BDC will be most likely to service network logon requests. The PDC will -answer network logon requests when the BDC is too busy (high load). A BDC can be promoted to -a PDC. If the PDC is on line at the time that the BDC is promoted to PDC the previous PDC is -automatically demoted to a BDC.

    At this time Samba is NOT capable of acting as an ADS Domain Controller.

    Chapter 6. Samba as Stand-Alone Server

    In this section the function and purpose of Samba's security -modes are described.

    6.1. User and Share security level

    A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which -of these two the client receives affects the way the client then tries -to authenticate itself. It does not directly affect (to any great -extent) the way the Samba server does security. I know this is -strange, but it fits in with the client/server approach of SMB. In SMB -everything is initiated and controlled by the client, and the server -can only tell the client what is available and whether an action is -allowed.

    6.1.1. User Level Security

    I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after -the protocol negotiation. This contains a username and password. The -server can either accept or reject that username/password -combination. Note that at this stage the server has no idea what -share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than:

    1. the username/password

    2. the machine that the client is coming from

    If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without -specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup".

    It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use -as an authentication tag for that username/password. The client can -maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this)

    6.1.2. Share Level Security

    Ok, now for share level security. In share level security the client -authenticates itself separately for each share. It will send a -password along with each "tree connection" (share mount). It does not -explicitly send a username with this operation. The client is -expecting a password to be associated with each share, independent of -the user. This means that samba has to work out what username the -client probably wants to use. It is never explicitly sent the -username. Some commercial SMB servers such as NT actually associate -passwords directly with shares in share level security, but samba -always uses the unix authentication scheme where it is a -username/password that is authenticated, not a "share/password".

    Many clients send a "session setup" even if the server is in share -level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds -to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the user = smb.conf -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user.

    6.1.3. Server Level Security

    Finally "server level" security. In server level security the samba -server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba -server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same -username/password that it got from the client. If that server is in -user level security and accepts the password then samba accepts the -clients connection. This allows the samba server to use another SMB -server as the "password server".

    You should also note that at the very start of all this, where the -server tells the client what security level it is in, it also tells -the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all -passwords in encrypted form. You have to compile samba with encryption -enabled to support this feature, and you have to maintain a separate -smbpasswd file with SMB style encrypted passwords. It is -cryptographically impossible to translate from unix style encryption -to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync.

    "security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. -That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support.

    6.1.3.1. Configuring Samba for Seemless Windows Network Integration

    MS Windows clients may use encrypted passwords as part of a challenege/response -authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple -password based authentication. It should be realized that with the SMB protocol -the password is passed over the network either in plain text or encrypted, but -not both in the same authentication requests.

    When encrypted passwords are used a password that has been entered by the user -is encrypted in two ways:

    • An MD4 hash of the UNICODE of the password - string. This is known as the NT hash. -

    • The password is converted to upper case, - and then padded or trucated to 14 bytes. This string is - then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. - The resulting 16 bytes for the LanMan hash. -

    MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 -pre-service pack 3 will use either mode of password authentication. All -versions of MS Windows that follow these versions no longer support plain -text passwords by default.

    MS Windows clients have a habit of dropping network mappings that have been idle -for 10 minutes or longer. When the user attempts to use the mapped drive -connection that has been dropped, the client re-establishes the connection using -a cached copy of the password.

    When Microsoft changed the default password mode, support was dropped for caching -of the plain text password. This means that when the registry parameter is changed -to re-enable use of plain text passwords it appears to work, but when a dropped -service connection mapping attempts to revalidate it will fail if the remote -authentication server does not support encrypted passwords. This means that it -is definitely not a good idea to re-enable plain text password support in such clients.

    The following parameters can be used to work around the issue of Windows 9x client -upper casing usernames and password before transmitting them to the SMB server -when using clear text authentication.

    	passsword level = integer
-	username level = integer

    By default Samba will lower case the username before attempting to lookup the user -in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the username level parameter -is rarely needed.

    However, passwords on UNIX systems often make use of mixed case characters. -This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level -must be set to the maximum number of upper case letter which could -appear is a password. Note that is the server OS uses the traditional DES version -of crypt(), then a password level of 8 will result in case -insensitive passwords as seen from Windows users. This will also result in longer -login times as Samba hash to compute the permutations of the password string and -try them one by one until a match is located (or all combinations fail).

    The best option to adopt is to enable support for encrypted passwords -where ever Samba is used. There are three configuration possibilities -for support of encrypted passwords:

    6.1.3.2. Use MS Windows NT as an authentication server

    This method involves the additions of the following parameters in the smb.conf file:

    	encrypt passwords = Yes
-	security = server
-	password server = "NetBIOS_name_of_PDC"

    There are two ways of identifying whether or not a username and -password pair was valid or not. One uses the reply information provided -as part of the authentication messaging process, the other uses -just and error code.

    The down-side of this mode of configuration is the fact that -for security reasons Samba will send the password server a bogus -username and a bogus password and if the remote server fails to -reject the username and password pair then an alternative mode -of identification of validation is used. Where a site uses password -lock out after a certain number of failed authentication attempts -this will result in user lockouts.

    Use of this mode of authentication does require there to be -a standard Unix account for the user, this account can be blocked -to prevent logons by other than MS Windows clients.

    6.1.4. Domain Level Security

    When samba is operating in security = domain mode this means that -the Samba server has a domain security trust account (a machine account) and will cause -all authentication requests to be passed through to the domain controllers.

    6.1.4.1. Samba as a member of an MS Windows NT security domain

    This method involves additon of the following paramters in the smb.conf file:

    	encrypt passwords = Yes
-	security = domain
-	workgroup = "name of NT domain"
-	password server = *

    The use of the "*" argument to password server will cause samba to locate the -domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour.

    In order for this method to work the Samba server needs to join the -MS Windows NT security domain. This is done as follows:

    • On the MS Windows NT domain controller using - the Server Manager add a machine account for the Samba server. -

    • Next, on the Linux system execute: - smbpasswd -r PDC_NAME -j DOMAIN_NAME -

    Use of this mode of authentication does require there to be a standard Unix account -for the user in order to assign a uid once the account has been authenticated by -the remote Windows DC. This account can be blocked to prevent logons by other than -MS Windows clients by things such as setting an invalid shell in the -/etc/passwd entry.

    An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the Winbind Overview chapter -in this HOWTO collection.

    6.1.5. ADS Level Security

    For information about the configuration option please refer to the entire section entitled -Samba as an ADS Domain Member.

    Chapter 7. Samba as an NT4 or Win2k Primary Domain Controller

    7.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure -that you are comfortable with configuring basic files services -in smb.conf and how to enable and administer password -encryption in Samba. Theses two topics are covered in the -smb.conf manpage.

    7.2. Background

    This article outlines the steps necessary for configuring Samba as a PDC. -It is necessary to have a working Samba server prior to implementing the -PDC functionality.

    • Domain logons for Windows NT 4.0 / 200x / XP Professional clients. -

    • Placing Windows 9x / Me clients in user level security -

    • Retrieving a list of users and groups from a Samba PDC to - Windows 9x / Me / NT / 200x / XP Professional clients -

    • Roaming Profiles -

    • Network/System Policies -

    Roaming Profiles and System/Network policies are advanced network administration topics -that are covered separately in this document.

    The following functionalities are new to the Samba 3.0 release:

    • Windows NT 4 domain trusts -

    • Adding users via the User Manager for Domains -

    The following functionalities are NOT provided by Samba 3.0:

    • SAM replication with Windows NT 4.0 Domain Controllers - (i.e. a Samba PDC and a Windows NT BDC or vice versa) -

    • Acting as a Windows 2000 Domain Controller (i.e. Kerberos and - Active Directory) -

    Please note that Windows 9x / Me / XP Home clients are not true members of a domain -for reasons outlined in this article. Therefore the protocol for -support Windows 9x-style domain logons is completely different -from NT4 / Win2k type domain logons and has been officially supported for some -time.

    MS Windows XP Home edition is NOT able to join a domain and does not permit -the use of domain logons.

    Implementing a Samba PDC can basically be divided into 3 broad -steps.

    1. Configuring the Samba PDC -

    2. Creating machine trust accounts and joining clients to the domain -

    3. Adding and managing domain user accounts -

    There are other minor details such as user profiles, system -policies, etc... However, these are not necessarily specific -to a Samba PDC as much as they are related to Windows NT networking -concepts.

    7.3. Configuring the Samba Domain Controller

    The first step in creating a working Samba PDC is to -understand the parameters necessary in smb.conf. Here we -attempt to explain the parameters that are covered in -the smb.conf man page.

    Here is an example smb.conf for acting as a PDC:

    [global]
-    ; Basic server settings
-    netbios name = POGO
-    workgroup = NARNIA
-
-    ; we should act as the domain and local master browser
-    os level = 64
-    preferred master = yes
-    domain master = yes
-    local master = yes
-    
-    ; security settings (must user security = user)
-    security = user
-    
-    ; encrypted passwords are a requirement for a PDC
-    encrypt passwords = yes
-    
-    ; support domain logons
-    domain logons = yes
-    
-    ; where to store user profiles?
-    logon path = \\%N\profiles\%u
-    
-    ; where is a user's home directory and where should it be mounted at?
-    logon drive = H:
-    logon home = \\homeserver\%u
-    
-    ; specify a generic logon script for all users
-    ; this is a relative **DOS** path to the [netlogon] share
-    logon script = logon.cmd
-
-; necessary share for domain controller
-[netlogon]
-    path = /usr/local/samba/lib/netlogon
-    read only = yes
-    write list = ntadmin
-    
-; share for storing user profiles
-[profiles]
-    path = /export/smb/ntprofile
-    read only = no
-    create mask = 0600
-    directory mask = 0700

    There are a couple of points to emphasize in the above configuration.

    • Encrypted passwords must be enabled. For more details on how - to do this, refer to the User Database chapter. -

    • The server must support domain logons and a - [netlogon] share -

    • The server must be the domain master browser in order for Windows - client to locate the server as a DC. Please refer to the various - Network Browsing documentation included with this distribution for - details. -

    Samba 3.0 offers a complete implementation of group mapping -between Windows NT groups and Unix groups (this is really quite -complicated to explain in a short space).

    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain

    A machine trust account is a Samba account that is used to -authenticate a client machine (rather than a user) to the Samba -server. In Windows terminology, this is known as a "Computer -Account."

    The password of a machine trust account acts as the shared secret for -secure communication with the Domain Controller. This is a security -feature to prevent an unauthorized machine with the same NetBIOS name -from joining the domain and gaining access to domain user/group -accounts. Windows NT, 200x, XP Professional clients use machine trust -accounts, but Windows 9x / Me / XP Home clients do not. Hence, a -Windows 9x / Me / XP Home client is never a true member of a domain -because it does not possess a machine trust account, and thus has no -shared secret with the domain controller.

    A Windows PDC stores each machine trust account in the Windows -Registry. A Samba-3 PDC also has to stoe machine trust account information -in a suitable back-end data store. With Samba-3 there can be multiple back-ends -for this including:

    • smbpaswd - the plain ascii file stored used by - earlier versions of Samba. This file configuration option requires - a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the private - directory (default is /usr/local/samba/lib/private or on linux /etc/samba). -

    • smbpasswd_nua - This file is independant of the - system wide user accounts. The use of this back-end option requires - specification of the "non unix account range" option also. It is called - smbpasswd and will be located in the private directory. -

    • tdbsam - a binary database backend that will be - stored in the private directory in a file called - passwd.tdb. The key benefit of this binary format - file is that it can store binary objects that can not be accomodated - in the traditional plain text smbpasswd file. -

    • tdbsam_nua like the smbpasswd_nua option above, this - file allows the creation of arbitrary user and machine accounts without - requiring that account to be added to the system (/etc/passwd) file. It - too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. -

    • ldapsam - An LDAP based back-end. Permits the - LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com -

    • ldapsam_nua - LDAP based back-end with no unix - account requirement, like smbpasswd_nua and tdbsam_nua above. -

    Read the chapter about the User Database -for details.

    A Samba PDC, however, stores each machine trust account in two parts, -as follows: - -

    • A Samba account, stored in the same location as user - LanMan and NT password hashes (currently - smbpasswd). The Samba account - possesses and uses only the NT password hash.

    • A corresponding Unix account, typically stored in - /etc/passwd. (Future releases will alleviate the need to - create /etc/passwd entries.)

    There are two ways to create machine trust accounts:

    • Manual creation. Both the Samba and corresponding - Unix account are created by hand.

    • "On-the-fly" creation. The Samba machine trust - account is automatically created by Samba at the time the client - is joined to the domain. (For security, this is the - recommended method.) The corresponding Unix account may be - created automatically or manually.

    7.4.1. Manual Creation of Machine Trust Accounts

    The first step in manually creating a machine trust account is to -manually create the corresponding Unix account in -/etc/passwd. This can be done using -vipw or other 'add user' command that is normally -used to create new Unix accounts. The following is an example for a -Linux based Samba server:

    root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine -nickname" -s /bin/false machine_name$

    root# passwd -l machine_name$

    On *BSD systems, this can be done using the 'chpass' utility:

    root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"

    The /etc/passwd entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no -home directory. For example a machine named 'doppy' would have an -/etc/passwd entry like this:

    doppy$:x:505:501:machine_nickname:/dev/null:/bin/false

    Above, machine_nickname can be any -descriptive name for the client, i.e., BasementComputer. -machine_name absolutely must be the NetBIOS -name of the client to be joined to the domain. The "$" must be -appended to the NetBIOS name of the client or Samba will not recognize -this as a machine trust account.

    Now that the corresponding Unix account has been created, the next step is to create -the Samba account for the client containing the well-known initial -machine trust account password. This can be done using the smbpasswd(8) command -as shown here:

    root# smbpasswd -a -m machine_name

    where machine_name is the machine's NetBIOS -name. The RID of the new machine account is generated from the UID of -the corresponding Unix account.

    Join the client to the domain immediately
     

    Manually creating a machine trust account using this method is the - equivalent of creating a machine trust account on a Windows NT PDC using - the "Server Manager". From the time at which the account is created - to the time which the client joins the domain and changes the password, - your domain is vulnerable to an intruder joining your domain using a - a machine with the same NetBIOS name. A PDC inherently trusts - members of the domain and will serve out a large degree of user - information to such clients. You have been warned! -

    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is -simply to allow the Samba server to create them as needed when the client -is joined to the domain.

    Since each Samba machine trust account requires a corresponding -Unix account, a method for automatically creating the -Unix account is usually supplied; this requires configuration of the -add user script -option in smb.conf. This -method is not required, however; corresponding Unix accounts may also -be created manually.

    Below is an example for a RedHat 6.2 Linux system.

    [global]
-   # <...remainder of parameters...>
-   add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

    7.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the -version of Windows.

    • Windows 2000

      When the user elects to join the client to a domain, Windows prompts for - an account and password that is privileged to join the domain. A - Samba administrative account (i.e., a Samba account that has root - privileges on the Samba server) must be entered here; the - operation will fail if an ordinary user account is given. - The password for this account should be - set to a different password than the associated - /etc/passwd entry, for security - reasons.

      The session key of the Samba administrative account acts as an - encryption key for setting the password of the machine trust - account. The machine trust account will be created on-the-fly, or - updated if it already exists.

    • Windows NT

      If the machine trust account was created manually, on the - Identification Changes menu enter the domain name, but do not - check the box "Create a Computer Account in the Domain." In this case, - the existing machine trust account is used to join the machine to - the domain.

      If the machine trust account is to be created - on-the-fly, on the Identification Changes menu enter the domain - name, and check the box "Create a Computer Account in the Domain." In - this case, joining the domain proceeds as above for Windows 2000 - (i.e., you must supply a Samba administrative account when - prompted).

    • Samba

      Joining a samba client to a domain is documented in - the Domain Member chapter.

    7.5. Common Problems and Errors

    7.5.1. I cannot include a '$' in a machine name

    A 'machine name' in (typically) /etc/passwd -of the machine name with a '$' appended. FreeBSD (and other BSD -systems?) won't create a user with a '$' in their name.

    The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use vipw to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique User ID !

    7.5.2. I get told "You already have a connection to the Domain...." -or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.

    This happens if you try to create a machine trust account from the -machine itself and already have a connection (e.g. mapped drive) -to a share (or IPC$) on the Samba PDC. The following command -will remove all network drive connections:

    C:\WINNT\> net use * /d

    Further, if the machine is a already a 'member of a workgroup' that -is the same name as the domain you are joining (bad idea) you will -get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again.

    7.5.3. The system can not log you on (C000019B)....

    I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system -can not log you on (C000019B), Please try again or consult your -system administrator" when attempting to logon.

    This occurs when the domain SID stored in the secrets.tdb database -is changed. The most common cause of a change in domain SID is when -the domain name and/or the server name (netbios name) is changed. -The only way to correct the problem is to restore the original domain -SID or remove the domain client from the domain and rejoin. The domain -SID may be reset using either the smbpasswd or rpcclient utilities.

    7.5.4. The machine trust account for this computer either does not -exist or is not accessible.

    When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". What's -wrong?

    This problem is caused by the PDC not having a suitable machine trust account. -If you are using the add user script method to create +

    +	net getlocalsid 'OLDNAME'
+	net setlocalsid 'SID'
+

    +

    The machine trust account for this computer either does not +exist or is not accessible.

    +When I try to join the domain I get the message "The machine account +for this computer either does not exist or is not accessible". What's +wrong? +

    +This problem is caused by the PDC not having a suitable machine trust account. +If you are using the add user script method to create accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working.

    Alternatively if you are creating account entries manually then they +admin user system is working. +

    +Alternatively if you are creating account entries manually then they have not been created correctly. Make sure that you have the entry correct for the machine trust account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd @@ -5954,275 +1019,136 @@ with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. Some people have reported that inconsistent subnet masks between the Samba server and the NT client have caused this problem. Make sure that these are consistent -for both client and server.

    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.

    At first be ensure to enable the useraccounts with smbpasswd -e -%user%, this is normally done, when you create an account.

    7.6. Domain Control for Windows 9x/ME

    A domain and a workgroup are exactly the same thing in terms of network +for both client and server. +

    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.

    +At first be ensure to enable the useraccounts with smbpasswd -e +%user%, this is normally done, when you create an account. +

    Domain Control for Windows 9x/ME

    +A domain and a workgroup are exactly the same thing in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a network. Also, different access rights can be granted to users if they successfully authenticate against a domain logon server. Samba-3 does this -now in the same way that MS Windows NT/2K.

    The SMB client logging on to a domain has an expectation that every other +now in the same way that MS Windows NT/2K. +

    +The SMB client logging on to a domain has an expectation that every other server in the domain should accept the same authentication information. Network browsing functionality of domains and workgroups is identical and is explained in this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support.

    Issues related to the single-logon network model are discussed in this +It should be noted, that browsing is totally orthogonal to logon support. +

    +Issues related to the single-logon network model are discussed in this section. Samba supports domain logons, network logon scripts, and user profiles for MS Windows for workgroups and MS Windows 9X/ME clients -which are the focus of this section.

    When an SMB client in a domain wishes to logon it broadcast requests for a +which are the focus of this section. +

    +When an SMB client in a domain wishes to logon it broadcast requests for a logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but very stupid) to create a domain where the user database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely -involved with domains.

    Using these features you can make your clients verify their logon via +involved with domains. +

    +Using these features you can make your clients verify their logon via the Samba server; make clients run a batch file when they logon to -the network and download their preferences, desktop and start menu.

    Before launching into the configuration instructions, it is -worthwhile lookingat how a Windows 9x/ME client performs a logon:

    1. The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the +the network and download their preferences, desktop and start menu. +

      +Before launching into the configuration instructions, it is +worthwhile to look at how a Windows 9x/ME client performs a logon: +

      1. + The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. -

      2. The client then connects to that server, logs on (does an SMBsessetupX) and +

      3. + The client then connects to that server, logs on (does an SMBsessetupX) and then connects to the IPC$ share (using an SMBtconX). -

      4. The client then does a NetWkstaUserLogon request, which retrieves the name +

      5. + The client then does a NetWkstaUserLogon request, which retrieves the name of the user's logon script. -

      6. The client then connects to the NetLogon share and searches for this +

      7. + The client then connects to the NetLogon share and searches for this and if it is found and can be read, is retrieved and executed by the client. After this, the client disconnects from the NetLogon share. -

      8. The client then sends a NetUserGetInfo request to the server, to retrieve +

      9. + The client then sends a NetUserGetInfo request to the server, to retrieve the user's home share, which is used to search for profiles. Since the - response to the NetUserGetInfo request does not contain much more + response to the NetUserGetInfo request does not contain much more then the user's home share, profiles for Win9X clients MUST reside in the user home directory. -

      10. The client then connects to the user's home share and searches for the +

      11. + The client then connects to the user's home share and searches for the user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. -

      12. The client then disconnects from the user's home share, and reconnects to +

      13. + The client then disconnects from the user's home share, and reconnects to the NetLogon share and looks for CONFIG.POL, the policies file. If this is found, it is read and implemented. -

      7.6.1. Configuration Instructions: Network Logons

      The main difference between a PDC and a Windows 9x logon -server configuration is that

      • Password encryption is not required for a Windows 9x logon server.

      • Windows 9x/ME clients do not possess machine trust accounts.

      Therefore, a Samba PDC will also act as a Windows 9x logon -server.

      security mode and master browsers
       

      There are a few comments to make in order to tie up some +

      Configuration Instructions: Network Logons

      +The main difference between a PDC and a Windows 9x logon +server configuration is that +

      • +Password encryption is not required for a Windows 9x logon server. +

      • +Windows 9x/ME clients do not possess machine trust accounts. +

      +Therefore, a Samba PDC will also act as a Windows 9x logon +server. +

      security mode and master browsers

      +There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue of whether or not it is ok to configure Samba as a Domain Controller in security -modes other than USER. The only security mode -which will not work due to technical reasons is SHARE -mode security. DOMAIN and SERVER -mode security is really just a variation on SMB user level security.

      Actually, this issue is also closely tied to the debate on whether +modes other than USER. The only security mode +which will not work due to technical reasons is SHARE +mode security. DOMAIN and SERVER +mode security is really just a variation on SMB user level security. +

      +Actually, this issue is also closely tied to the debate on whether or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons -are two distinctly different functions), it is not a good idea to +are two distinctly different functions), it is not a good idea to do so. You should remember that the DC must register the DOMAIN#1b NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. -For this reason, it is very wise to configure the Samba DC as the DMB.

      Now back to the issue of configuring a Samba DC to use a mode other -than "security = user". If a Samba host is configured to use +For this reason, it is very wise to configure the Samba DC as the DMB. +

      +Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network -(the "password server") knows more about user than the Samba host. +(the "password server") knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the "workgroup" parameter +in order to operate in domain mode security, the "workgroup" parameter must be set to the name of the Windows NT domain (which already -has a domain controller, right?)

      Therefore configuring a Samba box as a DC for a domain that +has a domain controller, right?) +

      +Therefore configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC to be the DMB -for its domain.

    Chapter 8. Samba Backup Domain Controller to Samba Domain Control

    8.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure +for its domain. +

    Chapter6. +Samba Backup Domain Controller to Samba Domain Control +

    Volker Lendecke

    Samba Team

    <Volker.Lendecke@SerNet.DE>

    (26 Apr 2001)

    Table of Contents

    Prerequisite Reading
    Background
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    When is the PDC needed?
    Can Samba be a Backup Domain Controller to an NT PDC?
    How do I set up a Samba BDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?

    Prerequisite Reading

    +Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC -as described in the Samba-PDC-HOWTO.

    8.2. Background

    What is a Domain Controller? It is a machine that is able to answer +as described in the Samba-PDC-HOWTO. +

    Background

    +What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a user logs into a Windows NT Workstation, the workstation connects to a Domain Controller and asks him whether the username and password the user typed in is correct. The Domain Controller replies with a lot of information about the user, for example the place where the users profile is stored, the users full name of the user. All this -information is stored in the NT user database, the so-called SAM.

    There are two kinds of Domain Controller in a NT 4 compatible Domain: +information is stored in the NT user database, the so-called SAM. +

    +There are two kinds of Domain Controller in a NT 4 compatible Domain: A Primary Domain Controller (PDC) and one or more Backup Domain Controllers (BDC). The PDC contains the master copy of the SAM. Whenever the SAM has to change, for example when a user changes @@ -6231,51 +1157,31 @@ Controller is a machine that maintains a read-only copy of the SAM. This way it is able to reply to logon requests and authenticate users in case the PDC is not available. During this time no changes to the SAM are possible. Whenever changes to the SAM are done on the PDC, -all BDC receive the changes from the PDC.

    Since version 2.2 Samba officially supports domain logons for all +all BDC receive the changes from the PDC. +

    +Since version 2.2 Samba officially supports domain logons for all current Windows Clients, including Windows 2000 and XP. This text assumes the domain to be named SAMBA. To be able to act as a PDC, some -parameters in the [global]-section of the smb.conf have to be set:

    workgroup = SAMBA
-domain master = yes
-domain logons = yes

    Several other things like a [homes] and a [netlogon] share also may be +parameters in the [global]-section of the smb.conf have to be set: +

    +	workgroup = SAMBA
+	domain master = yes
+	domain logons = yes
+

    +Several other things like a [homes] and a [netlogon] share also may be set along with settings for the profile path, the users home drive and -others. This will not be covered in this document.

    8.3. What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to +others. This will not be covered in this document. +

    What qualifies a Domain Controller on the network?

    +Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA#1b with the WINS server. The name type #1b is normally reserved for the domain master browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to -be on the same machine as the PDC.

    8.3.1. How does a Workstation find its domain controller?

    A NT workstation in the domain SAMBA that wants a local user to be +be on the same machine as the PDC. +

    How does a Workstation find its domain controller?

    +A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA#1c. It assumes that each of the machines it gets back from the queries is a @@ -6283,1721 +1189,1919 @@ domain controller and can answer logon requests. To not open security holes both the workstation and the selected (TODO: How is the DC chosen) domain controller authenticate each other. After that the workstation sends the user's credentials (his name and password) to -the domain controller, asking for approval.

    8.3.2. When is the PDC needed?

    Whenever a user wants to change his password, this has to be done on +the domain controller, asking for approval. +

    When is the PDC needed?

    +Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query for SAMBA#1b, assuming this machine maintains the master copy of the SAM. The workstation contacts the PDC, both mutually authenticate and -the password change is done.

    8.4. Can Samba be a Backup Domain Controller to an NT PDC?

    With version 2.2, no. The native NT SAM replication protocols have +the password change is done. +

    Can Samba be a Backup Domain Controller to an NT PDC?

    +With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not -been finished for version 2.2.

    With version 3.0, the work on both the replication protocols and a +been finished for version 2.2. +

    +With version 3.0, the work on both the replication protocols and a suitable storage mechanism has progressed, and some form of NT4 BDC -support is expected soon.

    Can I get the benefits of a BDC with Samba? Yes. The main reason for +support is expected soon. +

    +Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to -service logon requests whenever the PDC is down.

    8.5. How do I set up a Samba BDC?

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to +service logon requests whenever the PDC is down. +

    How do I set up a Samba BDC?

    +Several things have to be done: +

    • +The domain SID has to be the same on the PDC and the BDC. This used to be stored in the file private/MACHINE.SID. This file is not created anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is stored in the file private/secrets.tdb. Simply copying the secrets.tdb from the PDC to the BDC does not work, as the BDC would generate a new SID for itself and override the domain SID with this -new BDC SID.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the -secrets.tdb, execute 'net rpc getsid' on the BDC.

    • The Unix user database has to be synchronized from the PDC to the +new BDC SID.

      +To retrieve the domain SID from the PDC or an existing BDC and store it in the +secrets.tdb, execute 'net rpc getsid' on the BDC. +

    • +The Unix user database has to be synchronized from the PDC to the BDC. This means that both the /etc/passwd and /etc/group have to be replicated from the PDC to the BDC. This can be done manually whenever changes are made, or the PDC is set up as a NIS master server and the BDC as a NIS slave server. To set up the BDC as a mere NIS client would not be enough, as the BDC would not be able to -access its user database in case of a PDC failure.

    • The Samba password database in the file private/smbpasswd has to be +access its user database in case of a PDC failure. +

    • +The Samba password database in the file private/smbpasswd has to be replicated from the PDC to the BDC. This is a bit tricky, see the -next section.

    • Any netlogon share has to be replicated from the PDC to the +next section. +

    • +Any netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd -synchronization.

    Finally, the BDC has to be found by the workstations. This can be done -by setting

    workgroup = samba
-domain master = no
-domain logons = yes

    in the [global]-section of the smb.conf of the BDC. This makes the BDC +synchronization. +

    +Finally, the BDC has to be found by the workstations. This can be done +by setting +

    +	workgroup = samba
+	domain master = no
+	domain logons = yes
+

    +in the [global]-section of the smb.conf of the BDC. This makes the BDC only register the name SAMBA#1c with the WINS server. This is no problem as the name SAMBA#1c is a NetBIOS group name that is meant to be registered by more than one machine. The parameter 'domain master = no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS -name is reserved for the Primary Domain Controller.

    8.5.1. How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done +name is reserved for the Primary Domain Controller. +

    How do I replicate the smbpasswd file?

    +Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is done in the smbpasswd file and has to be replicated to the BDC. So -replicating the smbpasswd file very often is necessary.

    As the smbpasswd file contains plain text password equivalents, it +replicating the smbpasswd file very often is necessary. +

    +As the smbpasswd file contains plain text password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a -password.

    8.5.2. Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports +password. +

    Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports binding to a replica LDAP server, and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read only, so this will not occur -often).

    Chapter 9. Samba as a ADS domain member

    This is a rough guide to setting up Samba 3.0 with kerberos authentication against a -Windows2000 KDC.

    9.1. Setup your smb.conf

    You must use at least the following 3 options in smb.conf:

      realm = YOUR.KERBEROS.REALM
-  security = ADS
-  encrypt passwords = yes

    In case samba can't figure out your ads server using your realm name, use the -ads server option in smb.conf: -

      ads server = your.kerberos.server

    You do *not* need a smbpasswd file, and older clients will - be authenticated as if security = domain, +often). +

    Chapter7.Samba as a ADS domain member

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    2002/2003

    Table of Contents

    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Possible errors
    Test your server setup
    Testing with smbclient
    Notes

    +This is a rough guide to setting up Samba 3.0 with kerberos authentication against a +Windows2000 KDC. +

    Setup your smb.conf

    You must use at least the following 3 options in smb.conf:

    +	realm = YOUR.KERBEROS.REALM
+	security = ADS
+	encrypt passwords = yes
+

    +In case samba can't figure out your ads server using your realm name, use the +ads server option in smb.conf: +

    +	ads server = your.kerberos.server
+

    +

    Note

    You do *not* need a smbpasswd file, and older clients will + be authenticated as if security = domain, although it won't do any harm and allows you to have local users not in the domain. I expect that the above required options will change soon when we get better - active directory integration.

    9.2. Setup your /etc/krb5.conf

    The minimal configuration for krb5.conf is:

    [realms]
-    YOUR.KERBEROS.REALM = {
-	kdc = your.kerberos.server
-    }

    Test your config by doing a kinit USERNAME@REALM and making sure that - your password is accepted by the Win2000 KDC.

    The realm must be uppercase.

    You also must ensure that you can do a reverse DNS lookup on the IP + active directory integration.

    Setup your /etc/krb5.conf

    Note: you will need the krb5 workstation, devel, and libs installed

    The minimal configuration for krb5.conf is:

    +	[realms]
+	    YOUR.KERBEROS.REALM = {
+		kdc = your.kerberos.server
+	    }
+

    Test your config by doing a kinit +USERNAME@REALM and +making sure that your password is accepted by the Win2000 KDC. +

    Note

    The realm must be uppercase or you will get "Cannot find KDC for requested +realm while getting initial credentials" error

    Note

    Time between the two servers must be synchronized. You will get a +"kinit(v5): Clock skew too great while getting initial credentials" if the time +difference is more than five minutes.

    +You also must ensure that you can do a reverse DNS lookup on the IP address of your KDC. Also, the name that this reverse lookup maps to must either be the netbios name of the KDC (ie. the hostname with no domain attached) or it can alternatively be the netbios name -followed by the realm.

    The easiest way to ensure you get this right is to add a -/etc/hosts entry mapping the IP address of your KDC to +followed by the realm. +

    +The easiest way to ensure you get this right is to add a +/etc/hosts entry mapping the IP address of your KDC to its netbios name. If you don't get this right then you will get a -"local error" when you try to join the realm.

    If all you want is kerberos support in smbclient then you can skip -straight to Test with smbclient now. -Creating a computer account -and testing your servers -is only needed if you want kerberos -support for smbd and winbindd.

    9.3. Create the computer account

    As a user that has write permission on the Samba private directory +"local error" when you try to join the realm. +

    +If all you want is kerberos support in smbclient then you can skip +straight to Test with smbclient now. +Creating a computer account +and testing your servers +is only needed if you want kerberos support for smbd and winbindd. +

    Create the computer account

    +As a user that has write permission on the Samba private directory (usually root) run: -net ads join

    9.3.1. Possible errors

    "ADS support not compiled in"

    Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.

    9.4. Test your server setup

    On a Windows 2000 client try net use * \\server\share. You should +

    +	net join -U Administrator%password
+

    +

    Possible errors

    +

    "ADS support not compiled in"

    Samba must be reconfigured (remove config.cache) and recompiled + (make clean all install) after the kerberos libs and headers are installed. +

    net join prompts for user name

    You need to login to the domain using kinit + USERNAME@REALM. + USERNAME must be a user who has rights to add a machine + to the domain.

    +

    Test your server setup

    +If the join was successful, you will see a new computer account with the +NetBIOS name of your Samba server in Active Directory (in the "Computers" +folder under Users and Computers. +

    +On a Windows 2000 client try net use * \\server\share. You should be logged in with kerberos without needing to know a password. If -this fails then run klist tickets. Did you get a ticket for the -server? Does it have an encoding type of DES-CBC-MD5 ?

    9.5. Testing with smbclient

    On your Samba server try to login to a Win2000 server or your Samba -server using smbclient and kerberos. Use smbclient as usual, but -specify the -k option to choose kerberos authentication.

    9.6. Notes

    You must change administrator password at least once after DC -install, to create the right encoding types

    w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in - their defaults DNS setup. Maybe fixed in service packs?

    Chapter 10. Samba as a NT4 or Win2k domain member

    10.1. Joining an NT Domain with Samba 3.0

    Assume you have a Samba 3.0 server with a NetBIOS name of - SERV1 and are joining an or Win2k NT domain called - DOM, which has a PDC with a NetBIOS name - of DOMPDC and two backup domain controllers - with NetBIOS names DOMBDC1 and DOMBDC2 - .

    Firstly, you must edit your smb.conf file to tell Samba it should - now use domain security.

    Change (or add) your security = line in the [global] section - of your smb.conf to read:

    security = domain

    Next change the workgroup = line in the [global] section to read:

    workgroup = DOM

    as this is the name of the domain we are joining.

    You must also have the parameter encrypt passwords set to yes - in order for your users to authenticate to the NT PDC.

    Finally, add (or modify) a password server = line in the [global] - section to read:

    password server = DOMPDC DOMBDC1 DOMBDC2

    These are the primary and backup domain controllers Samba +this fails then run klist tickets. Did you get a ticket for the +server? Does it have an encoding type of DES-CBC-MD5 ? +

    Testing with smbclient

    +On your Samba server try to login to a Win2000 server or your Samba +server using smbclient and kerberos. Use smbclient as usual, but +specify the -k option to choose kerberos authentication. +

    Notes

    You must change administrator password at least once after DC +install, to create the right encoding types

    w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in + their defaults DNS setup. Maybe fixed in service packs?

    Chapter8.Samba as a NT4 or Win2k domain member

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    16 Apr 2001

    Table of Contents

    Joining an NT Domain with Samba 3.0
    Why is this better than security = server?

    Joining an NT Domain with Samba 3.0

    Assumptions: + 

    +		NetBIOS name: SERV1
+		Win2K/NT domain name: DOM
+		Domain's PDC NetBIOS name: DOMPDC
+		Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
+

    +

    First, you must edit your smb.conf file to tell Samba it should + now use domain security.

    Change (or add) your + security = line in the [global] section + of your smb.conf to read:

    security = domain

    Next change the + workgroup = line in the [global] section to read:

    workgroup = DOM

    as this is the name of the domain we are joining.

    You must also have the parameter + encrypt passwords set to yes + in order for your users to authenticate to the NT PDC.

    Finally, add (or modify) a + password server = line in the [global] + section to read:

    password server = DOMPDC DOMBDC1 DOMBDC2

    These are the primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load - among domain controllers.

    Alternatively, if you want smbd to automatically determine + among domain controllers.

    Alternatively, if you want smbd to automatically determine the list of Domain controllers to use for authentication, you may - set this line to be :

    password server = *

    This method, allows Samba to use exactly the same + set this line to be :

    password server = *

    This method, allows Samba to use exactly the same mechanism that NT does. This method either broadcasts or uses a WINS database in order to - find domain controllers to authenticate against.

    In order to actually join the domain, you must run this - command:

    root# net rpc join -S DOMPDC - -UAdministrator%password

    as we are joining the domain DOM and the PDC for that domain + find domain controllers to authenticate against.

    In order to actually join the domain, you must run this + command:

    root# net join -S DOMPDC + -UAdministrator%password

    + If the -S DOMPDC argument is not given then + the domain name will be obtained from smb.conf. +

    as we are joining the domain DOM and the PDC for that domain (the only machine that has write access to the domain SAM database) - is DOMPDC. The Administrator%password is + is DOMPDC. The Administrator%password is the login name and password for an account which has the necessary privilege to add machines to the domain. If this is successful - you will see the message:

    Joined domain DOM. - or Joined 'SERV1' to realm 'MYREALM' -

    in your terminal window. See the net(8) man page for more details.

    This process joins the server to thedomain + you will see the message:

    Joined domain DOM. + or Joined 'SERV1' to realm 'MYREALM' +

    in your terminal window. See the + net(8) man page for more details.

    This process joins the server to the domain without having to create the machine trust account on the PDC - beforehand.

    This command goes through the machine account password + beforehand.

    This command goes through the machine account password change protocol, then writes the new (random) machine account password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private/secrets.tdb

    This file is created and owned by root and is not + in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private/secrets.tdb

    This file is created and owned by root and is not readable by any other user. It is the key to the domain-level security for your system, and should be treated as carefully - as a shadow password file.

    Finally, restart your Samba daemons and get ready for - clients to begin using domain security!

    10.2. Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from + as a shadow password file.

    Finally, restart your Samba daemons and get ready for + clients to begin using domain security!

    Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching - to your server. This means that if domain user DOM\fred - attaches to your domain security Samba server, there needs + to your server. This means that if domain user DOM\fred + attaches to your domain security Samba server, there needs to be a local Unix user fred to represent that user in the Unix filesystem. This is very similar to the older Samba security mode - security = server, + security = server, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would. -

    Please refer to the Winbind - paper for information on a system to automatically +

    Please refer to the Winbind + paper for information on a system to automatically assign UNIX uids and gids to Windows NT Domain users and groups. - This code is available in development branches only at the moment, - but will be moved to release branches soon.

    The advantage to domain-level security is that the +

    The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC.

    In addition, with security = server every Samba + domain PDC to an account domain PDC).

    In addition, with security = server every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run - out of available connections. With security = domain, + out of available connections. With security = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.

    And finally, acting in the same manner as an NT server + thus conserving PDC connection resources.

    And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc.

    Much of the text of this document - was first published in the Web magazine - LinuxWorld as the article Doing - the NIS/NT Samba.

    III. Advanced Configuration

    Introduction

    Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.

    Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists

    11.1. Viewing and changing UNIX permissions using the NT - security dialogs

    Windows NT clients can use their native security settings - dialog box to view and modify the underlying UNIX permissions.

    Note that this ability is careful not to compromise + as the user SID, the list of NT groups the user belongs to, etc.

    Note

    Much of the text of this document + was first published in the Web magazine + LinuxWorld as the article Doing + the NIS/NT Samba.

    Advanced Configuration

    Valuable Nuts and Bolts Information

    +Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. +

    Table of Contents

    9. Samba / MS Windows Network Browsing Guide
    What is Browsing?
    Discussion
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing samba to be the master
    Making samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in samba
    Problem resolution
    Browsing across subnets
    10. User information database
    Introduction
    Important Notes About Security
    Advantages of SMB Encryption
    Advantages of non-encrypted passwords
    The smbpasswd Command
    Plain text
    TDB
    LDAP
    Introduction
    Encrypted Password Database
    Supported LDAP Servers
    Schema and Relationship to the RFC 2307 posixAccount
    Configuring Samba with LDAP
    Accounts and Groups management
    Security and sambaAccount
    LDAP specials attributes for sambaAccounts
    Example LDIF Entries for a sambaAccount
    MySQL
    Creating the database
    Configuring
    Using plaintext passwords or encrypted password
    Getting non-column data from the table
    XML
    11. UNIX Permission Bits and Windows NT Access Control Lists
    Viewing and changing UNIX permissions using the NT + security dialogs
    How to view file security on a Samba share
    Viewing file ownership
    Viewing file or directory permissions
    File Permissions
    Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute + mapping
    12. Configuring Group Mapping
    13. Printing Support
    Introduction
    Configuration
    Creating [print$]
    Setting Drivers for Existing Printers
    Support a large number of printers
    Adding New Printers via the Windows NT APW
    Samba and Printer Ports
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints server
    The Installation Client
    Diagnosis
    Introduction
    Debugging printer problems
    What printers do I have?
    Setting up printcap and print servers
    Job sent, no output
    Job sent, strange output
    Raw PostScript printed
    Advanced Printing
    Real debugging
    14. CUPS Printing Support
    Introduction
    Configuring smb.conf for CUPS
    CUPS - RAW Print Through Mode
    CUPS as a network PostScript RIP
    Windows Terminal Servers (WTS) as CUPS clients
    Setting up CUPS for driver download
    Sources of CUPS drivers / PPDs
    cupsaddsmb
    The CUPS Filter Chains
    CUPS Print Drivers and Devices
    Further printing steps
    Limiting the number of pages users can print
    Advanced Postscript Printing from MS Windows
    Auto-Deletion of CUPS spool files
    15. Unified Logons between Windows NT and UNIX using Winbind
    Abstract
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Limitations
    Conclusion
    16. Advanced Network Manangement
    Configuring Samba Share Access Controls
    Share Permissions Management
    Remote Server Administration
    Network Logon Script Magic
    Adding printers without user intervention
    17. System and Account Policies
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    With Windows NT4/200x
    With a Samba PDC
    System Startup and Logon Processing Overview
    18. Desktop Profile Management
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    19. Interdomain Trust Relationships
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    20. PAM Configuration for Centrally Managed Authentication
    Samba and PAM
    PAM Configuration in smb.conf
    Password Synchronisation using pam_smbpass.so
    Distributed Authentication
    21. Stackable VFS modules
    Introduction and configuration
    Included modules
    audit
    extd_audit
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    22. Hosting a Microsoft Distributed File System tree on Samba
    Instructions
    Notes
    23. Integrating MS Windows networks with Samba
    Name Resolution in a pure Unix/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    24. Securing Samba
    Introduction
    Using host based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    25. Unicode/Charsets
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    26. File and Record Locking
    Discussion
    Samba Opportunistic Locking Control
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Additional Reading

    Chapter9.Samba / MS Windows Network Browsing Guide

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    July 5, 1998

    Updated: April 21, 2003

    Table of Contents

    What is Browsing?
    Discussion
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing samba to be the master
    Making samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in samba
    Problem resolution
    Browsing across subnets

    +This document contains detailed information as well as a fast track guide to +implementing browsing across subnets and / or across workgroups (or domains). +WINS is the best tool for resolution of NetBIOS names to IP addesses. WINS is +NOT involved in browse list handling except by way of name to address resolution. +

    Note

    +MS Windows 2000 and later can be configured to operate with NO NetBIOS +over TCP/IP. Samba-3 and later also supports this mode of operation. +When the use of NetBIOS over TCP/IP has been disabled then the primary +means for resolution of MS Windows machine names is via DNS and Active Directory. +The following information assumes that your site is running NetBIOS over TCP/IP. +

    What is Browsing?

    +To most people browsing means that they can see the MS Windows and Samba servers +in the Network Neighborhood, and when the computer icon for a particular server is +clicked, it opens up and shows the shares and printers available on the target server. +

    +What seems so simple is in fact a very complex interaction of different technologies. +The technologies (or methods) employed in making all of this work includes: +

    MS Windows machines register their presence to the network
    Machines announce themselves to other machines on the network
    One or more machine on the network collates the local announcements
    The client machine finds the machine that has the collated list of machines
    The client machine is able to resolve the machine names to IP addresses
    The client machine is able to connect to a target machine

    +The samba application that controls/manages browse list management and name resolution is +called nmbd. The configuration parameters involved in nmbd's operation are: +

    +	Browsing options:
+	-----------------
+		* os level
+		  lm announce
+		  lm interval
+		* preferred master
+		* local master
+		* domain master
+		  browse list
+		  enhanced browsing
+
+	Name Resolution Method:
+	-----------------------
+		* name resolve order
+
+	WINS options:
+	-------------
+		  dns proxy
+		  wins proxy
+		* wins server
+		* wins support
+		  wins hook
+

    +WINS Server and WINS Support are mutually exclusive options. Those marked with an '*' are +the only options that commonly MAY need to be modified. Even if not one of these parameters +is set nmbd will still do it's job. +

    Discussion

    +Firstly, all MS Windows networking is based on SMB (Server Message +Block) based messaging. SMB messaging may be implemented using NetBIOS or +without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP. +MS Windows products can do likewise. NetBIOS based networking uses broadcast +messaging to affect browse list management. When running NetBIOS over +TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast. +

    +Normally, only unicast UDP messaging can be forwarded by routers. The +remote announce +parameter to smb.conf helps to project browse announcements +to remote network segments via unicast UDP. Similarly, the +remote browse sync parameter of smb.conf +implements browse list collation using unicast UDP. +

    +Secondly, in those networks where Samba is the only SMB server technology +wherever possible nmbd should be configured on one (1) machine as the WINS +server. This makes it easy to manage the browsing environment. If each network +segment is configured with it's own Samba WINS server, then the only way to +get cross segment browsing to work is by using the +remote announce and the remote browse sync +parameters to your smb.conf file. +

    +If only one WINS server is used for an entire multi-segment network then +the use of the remote announce and the +remote browse sync parameters should NOT be necessary. +

    +As of Samba 3 WINS replication is being worked on. The bulk of the code has +been committed, but it still needs maturation. +

    +Right now samba WINS does not support MS-WINS replication. This means that +when setting up Samba as a WINS server there must only be one nmbd configured +as a WINS server on the network. Some sites have used multiple Samba WINS +servers for redundancy (one server per subnet) and then used +remote browse sync and remote announce +to affect browse list collation across all +segments. Note that this means clients will only resolve local names, +and must be configured to use DNS to resolve names on other subnets in +order to resolve the IP addresses of the servers they can see on other +subnets. This setup is not recommended, but is mentioned as a practical +consideration (ie: an 'if all else fails' scenario). +

    +Lastly, take note that browse lists are a collection of unreliable broadcast +messages that are repeated at intervals of not more than 15 minutes. This means +that it will take time to establish a browse list and it can take up to 45 +minutes to stabilise, particularly across network segments. +

    How Browsing Functions

    +As stated above, MS Windows machines register their NetBIOS names +(ie: the machine name for each service type in operation) on start +up. Also, as stated above, the exact method by which this name registration +takes place is determined by whether or not the MS Windows client/server +has been given a WINS server address, whether or not LMHOSTS lookup +is enabled, or if DNS for NetBIOS name resolution is enabled, etc. +

    +In the case where there is no WINS server all name registrations as +well as name lookups are done by UDP broadcast. This isolates name +resolution to the local subnet, unless LMHOSTS is used to list all +names and IP addresses. In such situations Samba provides a means by +which the samba server name may be forcibly injected into the browse +list of a remote MS Windows network (using the +remote announce parameter). +

    +Where a WINS server is used, the MS Windows client will use UDP +unicast to register with the WINS server. Such packets can be routed +and thus WINS allows name resolution to function across routed networks. +

    +During the startup process an election will take place to create a +local master browser if one does not already exist. On each NetBIOS network +one machine will be elected to function as the domain master browser. This +domain browsing has nothing to do with MS security domain control. +Instead, the domain master browser serves the role of contacting each local +master browser (found by asking WINS or from LMHOSTS) and exchanging browse +list contents. This way every master browser will eventually obtain a complete +list of all machines that are on the network. Every 11-15 minutes an election +is held to determine which machine will be the master browser. By the nature of +the election criteria used, the machine with the highest uptime, or the +most senior protocol version, or other criteria, will win the election +as domain master browser. +

    +Clients wishing to browse the network make use of this list, but also depend +on the availability of correct name resolution to the respective IP +address/addresses. +

    +Any configuration that breaks name resolution and/or browsing intrinsics +will annoy users because they will have to put up with protracted +inability to use the network services. +

    +Samba supports a feature that allows forced synchonisation +of browse lists across routed networks using the remote +browse sync parameter in the smb.conf file. +This causes Samba to contact the local master browser on a remote network and +to request browse list synchronisation. This effectively bridges +two networks that are separated by routers. The two remote +networks may use either broadcast based name resolution or WINS +based name resolution, but it should be noted that the remote +browse sync parameter provides browse list synchronisation - and +that is distinct from name to address resolution, in other +words, for cross subnet browsing to function correctly it is +essential that a name to address resolution mechanism be provided. +This mechanism could be via DNS, /etc/hosts, +and so on. +

    Setting up WORKGROUP Browsing

    +To set up cross subnet browsing on a network containing machines +in up to be in a WORKGROUP, not an NT Domain you need to set up one +Samba server to be the Domain Master Browser (note that this is *NOT* +the same as a Primary Domain Controller, although in an NT Domain the +same machine plays both roles). The role of a Domain master browser is +to collate the browse lists from local master browsers on all the +subnets that have a machine participating in the workgroup. Without +one machine configured as a domain master browser each subnet would +be an isolated workgroup, unable to see any machines on any other +subnet. It is the presense of a domain master browser that makes +cross subnet browsing possible for a workgroup. +

    +In an WORKGROUP environment the domain master browser must be a +Samba server, and there must only be one domain master browser per +workgroup name. To set up a Samba server as a domain master browser, +set the following option in the [global] section of the smb.conf file : +

    +

    +	domain master = yes
+

    +

    +The domain master browser should also preferrably be the local master +browser for its own subnet. In order to achieve this set the following +options in the [global] section of the smb.conf file : +

    +

    +	domain master = yes
+	local master = yes
+	preferred master = yes
+	os level = 65
+

    +

    +The domain master browser may be the same machine as the WINS +server, if you require. +

    +Next, you should ensure that each of the subnets contains a +machine that can act as a local master browser for the +workgroup. Any MS Windows NT/2K/XP/2003 machine should be +able to do this, as will Windows 9x machines (although these +tend to get rebooted more often, so it's not such a good idea +to use these). To make a Samba server a local master browser +set the following options in the [global] section of the +smb.conf file : +

    +

    +	domain master = no
+	local master = yes
+	preferred master = yes
+	os level = 65
+

    +

    +Do not do this for more than one Samba server on each subnet, +or they will war with each other over which is to be the local +master browser. +

    +The local master parameter allows Samba to act as a +local master browser. The preferred master causes nmbd +to force a browser election on startup and the os level +parameter sets Samba high enough so that it should win any browser elections. +

    +If you have an NT machine on the subnet that you wish to +be the local master browser then you can disable Samba from +becoming a local master browser by setting the following +options in the [global] section of the +smb.conf file : +

    +

    +	domain master = no
+	local master = no
+	preferred master = no
+	os level = 0
+

    +

    Setting up DOMAIN Browsing

    +If you are adding Samba servers to a Windows NT Domain then +you must not set up a Samba server as a domain master browser. +By default, a Windows NT Primary Domain Controller for a Domain +name is also the Domain master browser for that name, and many +things will break if a Samba server registers the Domain master +browser NetBIOS name (DOMAIN<1B>) +with WINS instead of the PDC. +

    +For subnets other than the one containing the Windows NT PDC +you may set up Samba servers as local master browsers as +described. To make a Samba server a local master browser set +the following options in the [global] section +of the smb.conf file : +

    +

    +	domain master = no
+	local master = yes
+	preferred master = yes
+	os level = 65
+

    +

    +If you wish to have a Samba server fight the election with machines +on the same subnet you may set the os level parameter +to lower levels. By doing this you can tune the order of machines that +will become local master browsers if they are running. For +more details on this see the section +Forcing samba to be the master browser +below. +

    +If you have Windows NT machines that are members of the domain +on all subnets, and you are sure they will always be running then +you can disable Samba from taking part in browser elections and +ever becoming a local master browser by setting following options +in the [global] section of the smb.conf +file : +

    +

    +        domain master = no
+        local master = no
+        preferred master = no
+        os level = 0
+

    +

    Forcing samba to be the master

    +Who becomes the master browser is determined by an election +process using broadcasts. Each election packet contains a number of parameters +which determine what precedence (bias) a host should have in the +election. By default Samba uses a very low precedence and thus loses +elections to just about anyone else. +

    +If you want Samba to win elections then just set the os level global +option in smb.conf to a higher number. It defaults to 0. Using 34 +would make it win all elections over every other system (except other +samba systems!) +

    +A os level of 2 would make it beat WfWg and Win95, but not MS Windows +NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32. +

    The maximum os level is 255

    +If you want samba to force an election on startup, then set the +preferred master global option in smb.conf to "yes". Samba will +then have a slight advantage over other potential master browsers +that are not preferred master browsers. Use this parameter with +care, as if you have two hosts (whether they are windows 95 or NT or +samba) on the same local subnet both set with preferred master to +"yes", then periodically and continually they will force an election +in order to become the local master browser. +

    +If you want samba to be a domain master browser, then it is +recommended that you also set preferred master to "yes", because +samba will not become a domain master browser for the whole of your +LAN or WAN if it is not also a local master browser on its own +broadcast isolated subnet. +

    +It is possible to configure two samba servers to attempt to become +the domain master browser for a domain. The first server that comes +up will be the domain master browser. All other samba servers will +attempt to become the domain master browser every 5 minutes. They +will find that another samba server is already the domain master +browser and will fail. This provides automatic redundancy, should +the current domain master browser fail. +

    Making samba the domain master

    +The domain master is responsible for collating the browse lists of +multiple subnets so that browsing can occur between subnets. You can +make samba act as the domain master by setting domain master = yes +in smb.conf. By default it will not be a domain master. +

    +Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain. +

    +When samba is the domain master and the master browser it will listen +for master announcements (made roughly every twelve minutes) from local +master browsers on other subnets and then contact them to synchronise +browse lists. +

    +If you want samba to be the domain master then I suggest you also set +the os level high enough to make sure it wins elections, and set +preferred master to "yes", to get samba to force an election on +startup. +

    +Note that all your servers (including samba) and clients should be +using a WINS server to resolve NetBIOS names. If your clients are only +using broadcasting to resolve NetBIOS names, then two things will occur: +

    1. + your local master browsers will be unable to find a domain master + browser, as it will only be looking on the local subnet. +

    2. + if a client happens to get hold of a domain-wide browse list, and + a user attempts to access a host in that list, it will be unable to + resolve the NetBIOS name of that host. +

    +If, however, both samba and your clients are using a WINS server, then: +

    1. + your local master browsers will contact the WINS server and, as long as + samba has registered that it is a domain master browser with the WINS + server, your local master browser will receive samba's ip address + as its domain master browser. +

    2. + when a client receives a domain-wide browse list, and a user attempts + to access a host in that list, it will contact the WINS server to + resolve the NetBIOS name of that host. as long as that host has + registered its NetBIOS name with the same WINS server, the user will + be able to see that host. +

    Note about broadcast addresses

    +If your network uses a "0" based broadcast address (for example if it +ends in a 0) then you will strike problems. Windows for Workgroups +does not seem to support a 0's broadcast and you will probably find +that browsing and name lookups won't work. +

    Multiple interfaces

    +Samba now supports machines with multiple network interfaces. If you +have multiple interfaces then you will need to use the interfaces +option in smb.conf to configure them. +

    Use of the Remote Announce parameter

    +The remote announce parameter of +smb.conf can be used to forcibly ensure +that all the NetBIOS names on a network get announced to a remote network. +The syntax of the remote announce parameter is: +

    +	remote announce = a.b.c.d [e.f.g.h] ...
+

    +_or_ +

    +	remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...
+

    + +where: +

    a.b.c.d and +e.f.g.h

    is either the LMB (Local Master Browser) IP address +or the broadcst address of the remote network. +ie: the LMB is at 192.168.1.10, or the address +could be given as 192.168.1.255 where the netmask +is assumed to be 24 bits (255.255.255.0). +When the remote announcement is made to the broadcast +address of the remote network every host will receive +our announcements. This is noisy and therefore +undesirable but may be necessary if we do NOT know +the IP address of the remote LMB.

    WORKGROUP

    is optional and can be either our own workgroup +or that of the remote network. If you use the +workgroup name of the remote network then our +NetBIOS machine names will end up looking like +they belong to that workgroup, this may cause +name resolution problems and should be avoided. +

    +

    Use of the Remote Browse Sync parameter

    +The remote browse sync parameter of +smb.conf is used to announce to +another LMB that it must synchronise it's NetBIOS name list with our +Samba LMB. It works ONLY if the Samba server that has this option is +simultaneously the LMB on it's network segment. +

    +The syntax of the remote browse sync parameter is: + +

    +remote browse sync = a.b.c.d
+

    + +where a.b.c.d is either the IP address of the +remote LMB or else is the network broadcast address of the remote segment. +

    WINS - The Windows Internetworking Name Server

    +Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly +recommended. Every NetBIOS machine registers it's name together with a +name_type value for each of of several types of service it has available. +eg: It registers it's name directly as a unique (the type 0x03) name. +It also registers it's name if it is running the lanmanager compatible +server service (used to make shares and printers available to other users) +by registering the server (the type 0x20) name. +

    +All NetBIOS names are up to 15 characters in length. The name_type variable +is added to the end of the name - thus creating a 16 character name. Any +name that is shorter than 15 characters is padded with spaces to the 15th +character. ie: All NetBIOS names are 16 characters long (including the +name_type information). +

    +WINS can store these 16 character names as they get registered. A client +that wants to log onto the network can ask the WINS server for a list +of all names that have registered the NetLogon service name_type. This saves +broadcast traffic and greatly expedites logon processing. Since broadcast +name resolution can not be used across network segments this type of +information can only be provided via WINS _or_ via statically configured +lmhosts files that must reside on all clients in the +absence of WINS. +

    +WINS also serves the purpose of forcing browse list synchronisation by all +LMB's. LMB's must synchronise their browse list with the DMB (domain master +browser) and WINS helps the LMB to identify it's DMB. By definition this +will work only within a single workgroup. Note that the domain master browser +has NOTHING to do with what is referred to as an MS Windows NT Domain. The +later is a reference to a security environment while the DMB refers to the +master controller for browse list information only. +

    +Use of WINS will work correctly only if EVERY client TCP/IP protocol stack +has been configured to use the WINS server/s. Any client that has not been +configured to use the WINS server will continue to use only broadcast based +name registration so that WINS may NEVER get to know about it. In any case, +machines that have not registered with a WINS server will fail name to address +lookup attempts by other clients and will therefore cause workstation access +errors. +

    +To configure Samba as a WINS server just add +wins support = yes to the smb.conf +file [globals] section. +

    +To configure Samba to register with a WINS server just add +"wins server = a.b.c.d" to your smb.conf file [globals] section. +

    Important

    +Never use both wins support = yes together +with wins server = a.b.c.d +particularly not using it's own IP address. +Specifying both will cause nmbd to refuse to start! +

    Setting up a WINS server

    +Either a Samba machine or a Windows NT Server machine may be set up +as a WINS server. To set a Samba machine to be a WINS server you must +add the following option to the smb.conf file on the selected machine : +in the [globals] section add the line +

    +

    +	wins support = yes
+

    +

    +Versions of Samba prior to 1.9.17 had this parameter default to +yes. If you have any older versions of Samba on your network it is +strongly suggested you upgrade to a recent version, or at the very +least set the parameter to 'no' on all these machines. +

    +Machines with wins support = yes will keep a list of +all NetBIOS names registered with them, acting as a DNS for NetBIOS names. +

    +You should set up only ONE wins server. Do NOT set the +wins support = yes option on more than one Samba +server. +

    +To set up a Windows NT Server as a WINS server you need to set up +the WINS service - see your NT documentation for details. Note that +Windows NT WINS Servers can replicate to each other, allowing more +than one to be set up in a complex subnet environment. As Microsoft +refuse to document these replication protocols Samba cannot currently +participate in these replications. It is possible in the future that +a Samba->Samba WINS replication protocol may be defined, in which +case more than one Samba machine could be set up as a WINS server +but currently only one Samba server should have the +wins support = yes parameter set. +

    +After the WINS server has been configured you must ensure that all +machines participating on the network are configured with the address +of this WINS server. If your WINS server is a Samba machine, fill in +the Samba machine IP address in the "Primary WINS Server" field of +the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs +in Windows 95 or Windows NT. To tell a Samba server the IP address +of the WINS server add the following line to the [global] section of +all smb.conf files : +

    +

    +	wins server = <name or IP address>
+

    +

    +where <name or IP address> is either the DNS name of the WINS server +machine or its IP address. +

    +Note that this line MUST NOT BE SET in the smb.conf file of the Samba +server acting as the WINS server itself. If you set both the +wins support = yes option and the +wins server = <name> option then +nmbd will fail to start. +

    +There are two possible scenarios for setting up cross subnet browsing. +The first details setting up cross subnet browsing on a network containing +Windows 95, Samba and Windows NT machines that are not configured as +part of a Windows NT Domain. The second details setting up cross subnet +browsing on networks that contain NT Domains. +

    WINS Replication

    +Samba-3 permits WINS replication through the use of the wrepld utility. +This tool is not currently capable of being used as it is still in active development. +As soon as this tool becomes moderately functional we will prepare man pages and enhance this +section of the documentation to provide usage and technical details. +

    Static WINS Entries

    +New to Samba-3 is a tool called winsedit that may be used to add +static WINS entries to the WINS database. This tool can be used also to modify entries +existing in the WINS database. +

    +The development of the winsedit tool was made necessary due to the migration +of the older style wins.dat file into a new tdb binary backend data store. +

    Helpful Hints

    +The following hints should be carefully considered as they are stumbling points +for many new network administrators. +

    Windows Networking Protocols

    Warning

    +Do NOT use more than one (1) protocol on MS Windows machines +

    +A very common cause of browsing problems results from installing more than +one protocol on an MS Windows machine. +

    +Every NetBIOS machine takes part in a process of electing the LMB (and DMB) +every 15 minutes. A set of election criteria is used to determine the order +of precidence for winning this election process. A machine running Samba or +Windows NT will be biased so that the most suitable machine will predictably +win and thus retain it's role. +

    +The election process is "fought out" so to speak over every NetBIOS network +interface. In the case of a Windows 9x machine that has both TCP/IP and IPX +installed and has NetBIOS enabled over both protocols the election will be +decided over both protocols. As often happens, if the Windows 9x machine is +the only one with both protocols then the LMB may be won on the NetBIOS +interface over the IPX protocol. Samba will then lose the LMB role as Windows +9x will insist it knows who the LMB is. Samba will then cease to function +as an LMB and thus browse list operation on all TCP/IP only machines will +fail. +

    +Windows 95, 98, 98se, Me are referred to generically as Windows 9x. +The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly +referred to as the WinNT family, but it should be recognised that 2000 and +XP/2003 introduce new protocol extensions that cause them to behave +differently from MS Windows NT4. Generally, where a server does NOT support +the newer or extended protocol, these will fall back to the NT4 protocols. +

    +The safest rule of all to follow it this - USE ONLY ONE PROTOCOL! +

    Name Resolution Order

    +Resolution of NetBIOS names to IP addresses can take place using a number +of methods. The only ones that can provide NetBIOS name_type information +are:

    WINS: the best tool!
    LMHOSTS: is static and hard to maintain.
    Broadcast: uses UDP and can not resolve names across remote segments.

    +Alternative means of name resolution includes:

    /etc/hosts: is static, hard to maintain, and lacks name_type info
    DNS: is a good choice but lacks essential name_type info.

    +Many sites want to restrict DNS lookups and want to avoid broadcast name +resolution traffic. The "name resolve order" parameter is of great help here. +The syntax of the "name resolve order" parameter is: +

    +name resolve order = wins lmhosts bcast host
+

    +_or_ +

    +name resolve order = wins lmhosts  	(eliminates bcast and host)
+

    +The default is: +

    +name  resolve order = host lmhost wins bcast
+

    +where "host" refers the the native methods used by the Unix system +to implement the gethostbyname() function call. This is normally +controlled by /etc/host.conf, /etc/nsswitch.conf and /etc/resolv.conf. +

    Technical Overview of browsing

    +SMB networking provides a mechanism by which clients can access a list +of machines in a network, a so-called browse list. This list +contains machines that are ready to offer file and/or print services +to other machines within the network. Thus it does not include +machines which aren't currently able to do server tasks. The browse +list is heavily used by all SMB clients. Configuration of SMB +browsing has been problematic for some Samba users, hence this +document. +

    +MS Windows 2000 and later, as with Samba 3 and later, can be +configured to not use NetBIOS over TCP/IP. When configured this way +it is imperative that name resolution (using DNS/LDAP/ADS) be correctly +configured and operative. Browsing will NOT work if name resolution +from SMB machine names to IP addresses does not function correctly. +

    +Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. +WINS allows remote segment clients to obtain NetBIOS name_type information +that can NOT be provided by any other means of name resolution. +

    Browsing support in samba

    +Samba facilitates browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file. +Samba can act as a local browse master for a workgroup and the ability +to support domain logons and scripts is now available. +

    +Samba can also act as a domain master browser for a workgroup. This +means that it will collate lists from local browse masters into a +wide area network server list. In order for browse clients to +resolve the names they may find in this list, it is recommended that +both samba and your clients use a WINS server. +

    +Note that you should NOT set Samba to be the domain master for a +workgroup that has the same name as an NT Domain: on each wide area +network, you must only ever have one domain master browser per workgroup, +regardless of whether it is NT, Samba or any other type of domain master +that is providing this service. +

    Note

    +Nmbd can be configured as a WINS server, but it is not +necessary to specifically use samba as your WINS server. MS Windows +NT4, Server or Advanced Server 2000 or 2003 can be configured as +your WINS server. In a mixed NT/2000/2003 server and samba environment on +a Wide Area Network, it is recommended that you use the Microsoft +WINS server capabilities. In a samba-only environment, it is +recommended that you use one and only one Samba server as your WINS server. +

    +To get browsing to work you need to run nmbd as usual, but will need +to use the workgroup option in smb.conf +to control what workgroup Samba becomes a part of. +

    +Samba also has a useful option for a Samba server to offer itself for +browsing on another subnet. It is recommended that this option is only +used for 'unusual' purposes: announcements over the internet, for +example. See remote announce in the +smb.conf man page. +

    Problem resolution

    +If something doesn't work then hopefully the log.nmb file will help +you track down the problem. Try a debug level of 2 or 3 for finding +problems. Also note that the current browse list usually gets stored +in text form in a file called browse.dat. +

    +Note that if it doesn't work for you, then you should still be able to +type the server name as \\SERVER in filemanager then +hit enter and filemanager should display the list of available shares. +

    +Some people find browsing fails because they don't have the global +guest account set to a valid account. Remember that the +IPC$ connection that lists the shares is done as guest, and thus you must +have a valid guest account. +

    +MS Windows 2000 and upwards (as with Samba) can be configured to disallow +anonymous (ie: Guest account) access to the IPC$ share. In that case, the +MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the +name of the currently logged in user to query the IPC$ share. MS Windows +9X clients are not able to do this and thus will NOT be able to browse +server resources. +

    +The other big problem people have is that their broadcast address, +netmask or IP address is wrong (specified with the "interfaces" option +in smb.conf) +

    Browsing across subnets

    +Since the release of Samba 1.9.17(alpha1) Samba has been +updated to enable it to support the replication of browse lists +across subnet boundaries. New code and options have been added to +achieve this. This section describes how to set this feature up +in different settings. +

    +To see browse lists that span TCP/IP subnets (ie. networks separated +by routers that don't pass broadcast traffic) you must set up at least +one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing +NetBIOS name to IP address translation to be done by doing a direct +query of the WINS server. This is done via a directed UDP packet on +port 137 to the WINS server machine. The reason for a WINS server is +that by default, all NetBIOS name to IP address translation is done +by broadcasts from the querying machine. This means that machines +on one subnet will not be able to resolve the names of machines on +another subnet without using a WINS server. +

    +Remember, for browsing across subnets to work correctly, all machines, +be they Windows 95, Windows NT, or Samba servers must have the IP address +of a WINS server given to them by a DHCP server, or by manual configuration +(for Win95 and WinNT, this is in the TCP/IP Properties, under Network +settings) for Samba this is in the smb.conf file. +

    How does cross subnet browsing work ?

    +Cross subnet browsing is a complicated dance, containing multiple +moving parts. It has taken Microsoft several years to get the code +that achieves this correct, and Samba lags behind in some areas. +Samba is capable of cross subnet browsing when configured correctly. +

    +Consider a network set up as follows : +

    +

    +                                   (DMB)
+             N1_A      N1_B        N1_C       N1_D        N1_E
+              |          |           |          |           |
+          -------------------------------------------------------
+            |          subnet 1                       |
+          +---+                                      +---+
+          |R1 | Router 1                  Router 2   |R2 |
+          +---+                                      +---+
+            |                                          |
+            |  subnet 2              subnet 3          |
+  --------------------------       ------------------------------------
+  |     |     |      |               |        |         |           |
+ N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
+                    (WINS)
+

    +

    +Consisting of 3 subnets (1, 2, 3) connected by two routers +(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines +on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume +for the moment that all these machines are configured to be in the +same workgroup (for simplicities sake). Machine N1_C on subnet 1 +is configured as Domain Master Browser (ie. it will collate the +browse lists for the workgroup). Machine N2_D is configured as +WINS server and all the other machines are configured to register +their NetBIOS names with it. +

    +As all these machines are booted up, elections for master browsers +will take place on each of the three subnets. Assume that machine +N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on +subnet 3 - these machines are known as local master browsers for +their particular subnet. N1_C has an advantage in winning as the +local master browser on subnet 1 as it is set up as Domain Master +Browser. +

    +On each of the three networks, machines that are configured to +offer sharing services will broadcast that they are offering +these services. The local master browser on each subnet will +receive these broadcasts and keep a record of the fact that +the machine is offering a service. This list of records is +the basis of the browse list. For this case, assume that +all the machines are configured to offer services so all machines +will be on the browse list. +

    +For each network, the local master browser on that network is +considered 'authoritative' for all the names it receives via +local broadcast. This is because a machine seen by the local +master browser via a local broadcast must be on the same +network as the local master browser and thus is a 'trusted' +and 'verifiable' resource. Machines on other networks that +the local master browsers learn about when collating their +browse lists have not been directly seen - these records are +called 'non-authoritative'. +

    +At this point the browse lists look as follows (these are +the machines you would see in your network neighborhood if +you looked in it on a particular network right now). +

    +

    +Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+

    +

    +Note that at this point all the subnets are separate, no +machine is seen across any of the subnets. +

    +Now examine subnet 2. As soon as N2_B has become the local +master browser it looks for a Domain master browser to synchronize +its browse list with. It does this by querying the WINS server +(N2_D) for the IP address associated with the NetBIOS name +WORKGROUP<1B>. This name was registerd by the Domain master +browser (N1_C) with the WINS server as soon as it was booted. +

    +Once N2_B knows the address of the Domain master browser it +tells it that is the local master browser for subnet 2 by +sending a MasterAnnouncement packet as a UDP port 138 packet. +It then synchronizes with it by doing a NetServerEnum2 call. This +tells the Domain Master Browser to send it all the server +names it knows about. Once the domain master browser receives +the MasterAnnouncement packet it schedules a synchronization +request to the sender of that packet. After both synchronizations +are done the browse lists look like : +

    +

    +Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+
+Servers with a (*) after them are non-authoritative names.
+

    +

    +At this point users looking in their network neighborhood on +subnets 1 or 2 will see all the servers on both, users on +subnet 3 will still only see the servers on their own subnet. +

    +The same sequence of events that occured for N2_B now occurs +for the local master browser on subnet 3 (N3_D). When it +synchronizes browse lists with the domain master browser (N1_A) +it gets both the server entries on subnet 1, and those on +subnet 2. After N3_D has synchronized with N1_C and vica-versa +the browse lists look like. +

    +

    +Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+
+Servers with a (*) after them are non-authoritative names.
+

    +

    +At this point users looking in their network neighborhood on +subnets 1 or 3 will see all the servers on all sunbets, users on +subnet 2 will still only see the servers on subnets 1 and 2, but not 3. +

    +Finally, the local master browser for subnet 2 (N2_B) will sync again +with the domain master browser (N1_C) and will recieve the missing +server entries. Finally - and as a steady state (if no machines +are removed or shut off) the browse lists will look like : +

    +

    +Subnet           Browse Master   List
+------           -------------   ----
+Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
+                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+
+Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
+                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
+                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
+	
+Servers with a (*) after them are non-authoritative names.
+

    +

    +Synchronizations between the domain master browser and local +master browsers will continue to occur, but this should be a +steady state situation. +

    +If either router R1 or R2 fails the following will occur: +

    1. + Names of computers on each side of the inaccessible network fragments + will be maintained for as long as 36 minutes, in the network neighbourhood + lists. +

    2. + Attempts to connect to these inaccessible computers will fail, but the + names will not be removed from the network neighbourhood lists. +

    3. + If one of the fragments is cut off from the WINS server, it will only + be able to access servers on its local subnet, by using subnet-isolated + broadcast NetBIOS name resolution. The effects are similar to that of + losing access to a DNS server. +

    Chapter10.User information database

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Olivier (lem) Lemaire

    IDEALX

    <olem@IDEALX.org>

    February 2003

    Table of Contents

    Introduction
    Important Notes About Security
    Advantages of SMB Encryption
    Advantages of non-encrypted passwords
    The smbpasswd Command
    Plain text
    TDB
    LDAP
    Introduction
    Encrypted Password Database
    Supported LDAP Servers
    Schema and Relationship to the RFC 2307 posixAccount
    Configuring Samba with LDAP
    Accounts and Groups management
    Security and sambaAccount
    LDAP specials attributes for sambaAccounts
    Example LDIF Entries for a sambaAccount
    MySQL
    Creating the database
    Configuring
    Using plaintext passwords or encrypted password
    Getting non-column data from the table
    XML

    Introduction

    Old windows clients send plain text passwords over the wire. + Samba can check these passwords by crypting them and comparing them + to the hash stored in the unix user database. +

    + Newer windows clients send encrypted passwords (so-called + Lanman and NT hashes) over + the wire, instead of plain text passwords. The newest clients + will only send encrypted passwords and refuse to send plain text + passwords, unless their registry is tweaked. +

    These passwords can't be converted to unix style encrypted + passwords. Because of that you can't use the standard unix + user database, and you have to store the Lanman and NT hashes + somewhere else.

    Next to a differently encrypted passwords, + windows also stores certain data for each user + that is not stored in a unix user database, e.g. + workstations the user may logon from, the location where his/her + profile is stored, etc. + Samba retrieves and stores this information using a "passdb backend". + Commonly + available backends are LDAP, plain text file, MySQL and nisplus. + For more information, see the documentation about the + passdb backend = parameter. +

    Important Notes About Security

    The unix and SMB password encryption techniques seem similar + on the surface. This similarity is, however, only skin deep. The unix + scheme typically sends clear text passwords over the network when + logging in. This is bad. The SMB encryption scheme never sends the + cleartext password over the network but it does store the 16 byte + hashed values on disk. This is also bad. Why? Because the 16 byte hashed + values are a "password equivalent". You cannot derive the user's + password from them, but they could potentially be used in a modified + client to gain access to a server. This would require considerable + technical knowledge on behalf of the attacker but is perfectly possible. + You should thus treat the data stored in whatever + passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the + cleartext passwords of all your users. Its contents must be kept + secret, and the file should be protected accordingly.

    Ideally we would like a password scheme which neither requires + plain text passwords on the net or on disk. Unfortunately this + is not available as Samba is stuck with being compatible with + other SMB systems (WinNT, WfWg, Win95 etc).

    Warning

    Note that Windows NT 4.0 Service pack 3 changed the + default for permissible authentication so that plaintext + passwords are never sent over the wire. + The solution to this is either to switch to encrypted passwords + with Samba or edit the Windows NT registry to re-enable plaintext + passwords. See the document WinNT.txt for details on how to do + this.

    Other Microsoft operating systems which also exhibit + this behavior includes

    These versions of MS Windows do not support full domain + security protocols, although they may log onto a domain environment. + Of these Only MS Windows XP Home does NOT support domain logons.

    MS DOS Network client 3.0 with + the basic network redirector installed
    Windows 95 with the network redirector + update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain + security protocols.

    Windows NT 3.5x
    Windows NT 4.0
    Windows 2000 Professional
    Windows 200x Server/Advanced Server
    Windows XP Professional

    Note

    All current release of + Microsoft SMB/CIFS clients support authentication via the + SMB Challenge/Response mechanism described here. Enabling + clear text authentication does not disable the ability + of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. + Even when plain text passwords are re-enabled, through the appropriate + registry change, the plain text password is NEVER cached. This means that + in the event that a network connections should become disconnected (broken) + only the cached (encrypted) password will be sent to the resource server + to affect a auto-reconnect. If the resource server does not support encrypted + passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS + IS STRONGLY ADVISED.

    Advantages of SMB Encryption

    Plain text passwords are not passed across + the network. Someone using a network sniffer cannot just + record passwords going to the SMB server.
    WinNT doesn't like talking to a server + that does not support encrypted passwords. It will refuse + to browse the server if the server is also in user level + security mode. It will insist on prompting the user for the + password on each connection, which is very annoying. The + only things you can do to stop this is to use SMB encryption. +
    Encrypted password support allows automatic share + (resource) reconnects.

    Advantages of non-encrypted passwords

    Plain text passwords are not kept + on disk, and are NOT cached in memory.
    Uses same password file as other unix + services such as login and ftp
    Use of other services (such as telnet and ftp) which + send plain text passwords over the net, so sending them for SMB + isn't such a big deal.

    The smbpasswd Command

    The smbpasswd utility is a utility similar to the + passwd or yppasswd programs. + It maintains the two 32 byte password fields in the passdb backend.

    smbpasswd works in a client-server mode + where it contacts the local smbd to change the user's password on its + behalf. This has enormous benefits - as follows.

    smbpasswd has the capability + to change passwords on Windows NT servers (this only works when + the request is sent to the NT Primary Domain Controller if you + are changing an NT Domain user's password).

    To run smbpasswd as a normal user just type :

    $ smbpasswd

    Old SMB password: <type old value here - + or hit return if there was no old password>

    New SMB Password: <type new value> +

    Repeat New SMB Password: <re-type new value +

    If the old value does not match the current value stored for + that user, or the two new values do not match each other, then the + password will not be changed.

    If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.

    If run by the root user smbpasswd may take an optional + argument, specifying the user name whose SMB password you wish to + change. Note that when run as root smbpasswd does not prompt for + or check the old password value, thus allowing root to set passwords + for users who have forgotten their passwords.

    smbpasswd is designed to work in the same way + and be familiar to UNIX users who use the passwd or + yppasswd commands.

    For more details on using smbpasswd refer + to the man page which will always be the definitive reference.

    Plain text

    +Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file /etc/samba/smbpasswd +or /etc/smbpasswd. When password encryption is disabled, no +data is stored at all. +

    TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations that +don not require LDAP. +

    LDAP

    Introduction

    +This document describes how to use an LDAP directory for storing Samba user +account information traditionally stored in the smbpasswd(5) file. It is +assumed that the reader already has a basic understanding of LDAP concepts +and has a working directory server already installed. For more information +on LDAP architectures and Directories, please refer to the following sites. +

    +Note that O'Reilly Publishing is working on +a guide to LDAP for System Administrators which has a planned release date of +early summer, 2002. +

    +Two additional Samba resources which may prove to be helpful are +

    • The Samba-PDC-LDAP-HOWTO + maintained by Ignacio Coupeau.

    • The NT migration scripts from IDEALX that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. +

    Encrypted Password Database

    +Traditionally, when configuring "encrypt +passwords = yes" in Samba's smb.conf file, user account +information such as username, LM/NT password hashes, password change times, and account +flags have been stored in the smbpasswd(5) file. There are several +disadvantages to this approach for sites with very large numbers of users (counted +in the thousands). +

    • +The first is that all lookups must be performed sequentially. Given that +there are approximately two lookups per domain logon (one for a normal +session connection such as when mapping a network drive or printer), this +is a performance bottleneck for large sites. What is needed is an indexed approach +such as is used in databases. +

    • +The second problem is that administrators who desired to replicate a +smbpasswd file to more than one Samba server were left to use external +tools such as rsync(1) and ssh(1) +and wrote custom, in-house scripts. +

    • +And finally, the amount of information which is stored in an +smbpasswd entry leaves no room for additional attributes such as +a home directory, password expiration time, or even a Relative +Identified (RID). +

    +As a result of these defeciencies, a more robust means of storing user attributes +used by smbd was developed. The API which defines access to user accounts +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). +

    +There are a few points to stress about that the ldapsam +does not provide. The LDAP support referred to in the this documentation does not +include: +

    • A means of retrieving user account information from + an Windows 2000 Active Directory server.

    • A means of replacing /etc/passwd.

    +The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +versions of these libraries can be obtained from PADL Software +(http://www.padl.com/). More +information about the configuration of these packages may be found at "LDAP, +System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". +

    Supported LDAP Servers

    +The LDAP samdb code in 2.2.3 (and later) has been developed and tested +using the OpenLDAP 2.0 server and client libraries. +The same code should be able to work with Netscape's Directory Server +and client SDK. However, due to lack of testing so far, there are bound +to be compile errors and bugs. These should not be hard to fix. +If you are so inclined, please be sure to forward all patches to +samba-patches@samba.org and +jerry@samba.org. +

    Schema and Relationship to the RFC 2307 posixAccount

    +Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +examples/LDAP/samba.schema. The sambaAccount objectclass is given here: +

    +objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY
+     DESC 'Samba Account'
+     MUST ( uid $ rid )
+     MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
+            logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
+            displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
+            description $ userWorkstations $ primaryGroupID $ domain ))
+

    +The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are +owned by the Samba Team and as such is legal to be openly published. +If you translate the schema to be used with Netscape DS, please +submit the modified schema file as a patch to jerry@samba.org +

    +Just as the smbpasswd file is meant to store information which supplements a +user's /etc/passwd entry, so is the sambaAccount object +meant to supplement the UNIX user account information. A sambaAccount is a +STRUCTURAL objectclass so it can be stored individually +in the directory. However, there are several fields (e.g. uid) which overlap +with the posixAccount objectclass outlined in RFC2307. This is by design. +

    +In order to store all user account information (UNIX and Samba) in the directory, +it is necessary to use the sambaAccount and posixAccount objectclasses in +combination. However, smbd will still obtain the user's UNIX account +information via the standard C library calls (e.g. getpwnam(), et. al.). +This means that the Samba server must also have the LDAP NSS library installed +and functioning correctly. This division of information makes it possible to +store all Samba account information in LDAP, but still maintain UNIX account +information in NIS while the network is transitioning to a full LDAP infrastructure. +

    Configuring Samba with LDAP

    OpenLDAP configuration

    +To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory. +

    +root# cp samba.schema /etc/openldap/schema/ +

    +Next, include the samba.schema file in slapd.conf. +The sambaAccount object contains two attributes which depend upon other schema +files. The 'uid' attribute is defined in cosine.schema and +the 'displayName' attribute is defined in the inetorgperson.schema +file. Both of these must be included before the samba.schema file. +

    +## /etc/openldap/slapd.conf
+
+## schema files (core.schema is required by default)
+include	           /etc/openldap/schema/core.schema
+
+## needed for sambaAccount
+include            /etc/openldap/schema/cosine.schema
+include            /etc/openldap/schema/inetorgperson.schema
+include            /etc/openldap/schema/samba.schema
+include            /etc/openldap/schema/nis.schema
+
+....
+

    +It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well). +

    +# Indices to maintain
+## required by OpenLDAP 2.0
+index objectclass   eq
+
+## support pb_getsampwnam()
+index uid           pres,eq
+## support pdb_getsambapwrid()
+index rid           eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber     eq
+##index gidNumber     eq
+##index cn            eq
+##index memberUid     eq
+
+# (both fetched via ldapsearch):
+index   primaryGroupID  eq
+index   displayName     pres,eq
+
+

    Configuring Samba

    +The following parameters are available in smb.conf only with --with-ldapsam +was included when compiling Samba. +

    +These are described in the smb.conf(5) man +page and so will not be repeated here. However, a sample smb.conf file for +use with an LDAP directory could appear as +

    +## /usr/local/samba/lib/smb.conf
+[global]
+     security = user
+     encrypt passwords = yes
+
+     netbios name = TASHTEGO
+     workgroup = NARNIA
+
+     # ldap related parameters
+
+     # define the DN to use when binding to the directory servers
+     # The password for this DN is not stored in smb.conf.  Rather it
+     # must be set by using 'smbpasswd -w secretpw' to store the
+     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
+     # change, this password will need to be reset.
+     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
+
+     # Define the SSL option when connecting to the directory
+     # ('off', 'start tls', or 'on' (default))
+     ldap ssl = start tls
+
+     passdb backend ldapsam:ldap://ahab.samba.org
+
+     # smbpasswd -x delete the entire dn-entry
+     ldap delete dn = no
+
+     # the machine and user suffix added to the base suffix
+     # wrote WITHOUT quotes. NULL siffixes by default
+     ldap user suffix = ou=People
+     ldap machine suffix = ou=Systems
+
+     # define the port to use in the LDAP session (defaults to 636 when
+     # "ldap ssl = on")
+     ldap port = 389
+
+     # specify the base DN to use when searching the directory
+     ldap suffix = "ou=people,dc=samba,dc=org"
+
+     # generally the default ldap search filter is ok
+     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"
+

    Accounts and Groups management

    +As users accounts are managed thru the sambaAccount objectclass, you should +modify your existing administration tools to deal with sambaAccount attributes. +

    +Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to store thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file). +

    +In Samba release 3.0, the group management system is based on posix +groups. This means that Samba makes usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups). +

    Security and sambaAccount

    +There are two important points to remember when discussing the security +of sambaAccount entries in the directory. +

    • Never retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to + view the lmPassword or ntPassword attribute values.

    +These password hashes are clear text equivalents and can be used to impersonate +the user without deriving the original clear text strings. For more information +on the details of LM/NT password hashes, refer to the User Database of the Samba-HOWTO-Collection. +

    +To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (ldap ssl = on) using +the default port of 636 +when contacting the directory server. When using an OpenLDAP 2.0 server, it +is possible to use the use the StartTLS LDAP extended operation in the place of +LDAPS. In either case, you are strongly discouraged to disable this security +(ldap ssl = off). +

    +Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers. +

    +The second security precaution is to prevent non-administrative users from +harvesting password hashes from the directory. This can be done using the +following ACL in slapd.conf: +

    +## allow the "ldap admin dn" access, but deny everyone else
+access to attrs=lmPassword,ntPassword
+     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
+     by * none
+

    LDAP specials attributes for sambaAccounts

    +The sambaAccount objectclass is composed of the following attributes: +

    • lmPassword: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the + lmPassword and ntPassword attributes were last set. +

    • acctFlags: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • homeDrive: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.

    • scriptPath: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.

    • profilePath: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.

    • smbHome: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. +

    • userWorkstation: character string value currently unused. +

    • rid: the integer representation of the user's relative identifier + (RID).

    • primaryGroupID: the relative identifier (RID) of the primary group + of the user.

    +The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the Samba-PDC-HOWTO for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values: +

    • smbHome

    • scriptPath

    • logonPath

    • homeDrive

    +These attributes are only stored with the sambaAccount entry if +the values are non-default values. For example, assume TASHTEGO has now been +configured as a PDC and that logon home = \\%L\%u was defined in +its smb.conf file. When a user named "becky" logons to the domain, +the logon home string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +this value is used. However, if this attribute does not exist, then the value +of the logon home parameter is used in its place. Samba +will only write the attribute value to the directory entry if the value is +something other than the default (e.g. \\MOBY\becky). +

    Example LDIF Entries for a sambaAccount

    +The following is a working LDIF with the inclusion of the posixAccount objectclass: +

    +dn: uid=guest2, ou=people,dc=plainjoe,dc=org
+ntPassword: 878D8014606CDA29677A44EFA1353FC7
+pwdMustChange: 2147483647
+primaryGroupID: 1201
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+pwdLastSet: 1010179124
+logonTime: 0
+objectClass: sambaAccount
+uid: guest2
+kickoffTime: 2147483647
+acctFlags: [UX         ]
+logoffTime: 2147483647
+rid: 19006
+pwdCanChange: 0
+

    +The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses: +

    +dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
+logonTime: 0
+displayName: Gerald Carter
+lmPassword: 552902031BEDE9EFAAD3B435B51404EE
+primaryGroupID: 1201
+objectClass: posixAccount
+objectClass: sambaAccount
+acctFlags: [UX         ]
+userPassword: {crypt}BpM2ej8Rkzogo
+uid: gcarter
+uidNumber: 9000
+cn: Gerald Carter
+loginShell: /bin/bash
+logoffTime: 2147483647
+gidNumber: 100
+kickoffTime: 2147483647
+pwdLastSet: 1010179230
+rid: 19000
+homeDirectory: /home/tashtego/gcarter
+pwdCanChange: 0
+pwdMustChange: 2147483647
+ntPassword: 878D8014606CDA29677A44EFA1353FC7
+

    MySQL

    Creating the database

    +You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump +contains the correct queries to create the required tables. Use the command : + +mysql -uusername -hhostname -ppassword databasename > /path/to/samba/examples/pdb/mysql/mysql.dump + +

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: +

    +passdb backend = [other-plugins] mysql:identifier [other-plugins]
+

    +

    The identifier can be any string you like, as long as it doesn't collide with +the identifiers of other plugins or other instances of pdb_mysql. If you +specify multiple pdb_mysql.so entries in 'passdb backend', you also need to +use different identifiers! +

    +Additional options can be given thru the smb.conf file in the [global] section. +

    +identifier:mysql host                     - host name, defaults to 'localhost'
+identifier:mysql password
+identifier:mysql user                     - defaults to 'samba'
+identifier:mysql database                 - defaults to 'samba'
+identifier:mysql port                     - defaults to 3306
+identifier:table                          - Name of the table containing users
+

    Warning

    +Since the password for the mysql user is stored in the +smb.conf file, you should make the the smb.conf file +readable only to the user that runs samba. This is considered a security +bug and will be fixed soon. +

    Names of the columns in this table(I've added column types those columns should have first):

    +identifier:logon time column             - int(9)
+identifier:logoff time column            - int(9)
+identifier:kickoff time column           - int(9)
+identifier:pass last set time column     - int(9)
+identifier:pass can change time column   - int(9)
+identifier:pass must change time column  - int(9)
+identifier:username column               - varchar(255) - unix username
+identifier:domain column                 - varchar(255) - NT domain user is part of
+identifier:nt username column            - varchar(255) - NT username
+identifier:fullname column               - varchar(255) - Full name of user
+identifier:home dir column               - varchar(255) - Unix homedir path
+identifier:dir drive column              - varchar(2)   - Directory drive path (eg: 'H:')
+identifier:logon script column           - varchar(255)
+					 - Batch file to run on client side when logging on
+identifier:profile path column           - varchar(255) - Path of profile
+identifier:acct desc column              - varchar(255) - Some ASCII NT user data
+identifier:workstations column           - varchar(255)
+					 - Workstations user can logon to (or NULL for all)
+identifier:unknown string column         - varchar(255) - unknown string
+identifier:munged dial column            - varchar(255) - ?
+identifier:user sid column               - varchar(255) - NT user SID
+identifier:group sid column              - varchar(255) - NT group ID
+identifier:lanman pass column            - varchar(255) - encrypted lanman password
+identifier:nt pass column                - varchar(255) - encrypted nt passwd
+identifier:plain pass column             - varchar(255) - plaintext password
+identifier:acct control column           - int(9) - nt user data
+identifier:unknown 3 column              - int(9) - unknown
+identifier:logon divs column             - int(9) - ?
+identifier:hours len column              - int(9) - ?
+identifier:unknown 5 column              - int(9) - unknown
+identifier:unknown 6 column              - int(9) - unknown
+

    +Eventually, you can put a colon (:) after the name of each column, which +should specify the column to update when updating the table. You can also +specify nothing behind the colon - then the data from the field will not be +updated. +

    Using plaintext passwords or encrypted password

    +I strongly discourage the use of plaintext passwords, however, you can use them: +

    +If you would like to use plaintext passwords, set +'identifier:lanman pass column' and 'identifier:nt pass column' to +'NULL' (without the quotes) and 'identifier:plain pass column' to the +name of the column containing the plaintext passwords. +

    +If you use encrypted passwords, set the 'identifier:plain pass +column' to 'NULL' (without the quotes). This is the default. +

    Getting non-column data from the table

    +It is possible to have not all data in the database and making some 'constant'. +

    +For example, you can set 'identifier:fullname column' to : +CONCAT(First_name,' ',Sur_name) +

    +Or, set 'identifier:workstations column' to : +NULL

    See the MySQL documentation for more language constructs.

    XML

    This module requires libxml2 to be installed.

    The usage of pdb_xml is pretty straightforward. To export data, use: +

    + pdbedit -e xml:filename +

    +(where filename is the name of the file to put the data in) +

    +To import data, use: +pdbedit -i xml:filename -e current-pdb +

    +Where filename is the name to read the data from and current-pdb to put it in. +

    Chapter11.UNIX Permission Bits and Windows NT Access Control Lists

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    12 Apr 1999

    Table of Contents

    Viewing and changing UNIX permissions using the NT + security dialogs
    How to view file security on a Samba share
    Viewing file ownership
    Viewing file or directory permissions
    File Permissions
    Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute + mapping

    Viewing and changing UNIX permissions using the NT + security dialogs

    Windows NT clients can use their native security settings + dialog box to view and modify the underlying UNIX permissions.

    Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba - administrator can set.

    All access to Unix/Linux system file via Samba is controlled at + administrator can set.

    Note

    + All access to Unix/Linux system file via Samba is controlled at the operating system file access control level. When trying to figure out file access problems it is vitally important to identify the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. -

    11.2. How to view file security on a Samba share

    From an NT4/2000/XP client, single-click with the right +

    How to view file security on a Samba share

    From an NT4/2000/XP client, single-click with the right mouse button on any file or directory in a Samba mounted drive letter or UNC path. When the menu pops-up, click - on the Properties entry at the bottom of + on the Properties entry at the bottom of the menu. This brings up the file properties dialog - box. Click on the tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the + box. Click on the tab Security and you + will see three buttons, Permissions, + Auditing, and Ownership. + The Auditing button will cause either + an error message A requested privilege is not held + by the client to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

    11.3. Viewing file ownership

    Clicking on the "Ownership" button + useful button, the Add button will not currently + allow a list of users to be seen.

    Viewing file ownership

    Clicking on the "Ownership" button brings up a dialog box telling you who owns the given file. The - owner name will be of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) + owner name will be of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of + the Samba server, user is the user name of + the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the Close - button to remove this dialog.

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone".

    The Take Ownership button will not allow + GECOS field of the UNIX password database). Click on the Close + button to remove this dialog.

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone".

    The Take Ownership button will not allow you to change the ownership of this file to yourself (clicking on it will display a dialog box complaining that the user you are currently logged onto the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the root + operation in UNIX, available only to the root user. As clicking on this button causes NT to attempt to change the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba + client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba and allow a user with Administrator privilege connected to a Samba server as root to change the ownership of files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the Seclib - NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.

    11.4. Viewing file or directory permissions

    The third button is the "Permissions" + or Samba drive. This is available as part of the Seclib + NT security library written by Jeremy Allison of + the Samba Team, available from the main Samba ftp site.

    Viewing file or directory permissions

    The third button is the "Permissions" button. Clicking on this brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) + The owner is displayed in the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of + the Samba server, user is the user name of + the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files + GECOS field of the UNIX password database).

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone" and the + permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files and directories, so I'll describe the way file permissions - are displayed first.

    11.4.1. File Permissions

    The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions + are displayed first.

    File Permissions

    The standard UNIX user/group/world triple and + the corresponding "read", "write", "execute" permissions triples are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into - the global NT group Everyone, followed + the global NT group Everyone, followed by the list of permissions allowed for UNIX world. The UNIX owner and group permissions are displayed as an NT - user icon and an NT local - group icon respectively followed by the list - of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common - NT names such as "read", "change" or "full control" then - usually the permissions will be prefixed by the words "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed + user icon and an NT local + group icon respectively followed by the list + of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common + NT names such as "read", + "change" or "full control" then + usually the permissions will be prefixed by the words + "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute + to allow "no permissions" to be seen and modified then Samba + overloads the NT "Take Ownership" ACL attribute (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. + no permissions as having the NT "O" bit set. This was chosen of course to make it look like a zero, meaning zero permissions. More details on the decision behind this will - be given below.

    11.4.2. Directory Permissions

    Directories on an NT NTFS file system have two + be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" + in the first set of parentheses in the normal "RW" NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described - above, and is displayed in the same way.

    The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the "inherited" permissions that any file created within - this directory would inherit.

    Samba synthesises these inherited permissions for NT by + above, and is displayed in the same way.

    The second set of directory permissions has no real meaning + in the UNIX permissions world and represents the + "inherited" permissions that any file created within + this directory would inherit.

    Samba synthesises these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.

    11.5. Modifying file or directory permissions

    Modifying file and directory permissions is as simple + created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and - clicking the OK button. However, there are + clicking the OK button. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.

    If the parameter nt acl support - is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

    The first thing to note is that the "Add" + attributes that need to also be taken into account.

    If the parameter nt acl support + is set to false then any attempt to set + security permissions will fail with an "Access Denied" + message.

    The first thing to note is that the "Add" button will not return a list of users in Samba (it will give - an error message of "The remote procedure call failed - and did not execute"). This means that you can only + an error message of "The remote procedure call failed + and did not execute"). This means that you can only manipulate the current user/group/world permissions listed in the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.

    If a permission triple (either user, group, or world) + only permissions that UNIX actually has.

    If a permission triple (either user, group, or world) is removed from the list of permissions in the NT dialog box, - then when the "OK" button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This + then when the "OK" button is pressed it will + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT "O" flag, as described above. This allows you to add permissions back to a file or directory once - you have removed them from a triple component.

    As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.

    When setting permissions on a directory the second + you have removed them from a triple component.

    As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on + the Samba server.

    When setting permissions on a directory the second set of permissions (in the second set of parentheses) is by default applied to all files within that directory. If this - is not what you want you must uncheck the "Replace - permissions on existing files" checkbox in the NT - dialog before clicking "OK".

    If you wish to remove all permissions from a + is not what you want you must uncheck the "Replace + permissions on existing files" checkbox in the NT + dialog before clicking "OK".

    If you wish to remove all permissions from a user/group/world component then you may either highlight the - component and click the "Remove" button, - or set the component to only have the special "Take - Ownership" permission (displayed as "O" - ) highlighted.

    11.6. Interaction with the standard Samba create mask - parameters

    There are four parameters + component and click the "Remove" button, + or set the component to only have the special "Take + Ownership" permission (displayed as "O" + ) highlighted.

    Interaction with the standard Samba create mask + parameters

    There are four parameters to control interaction with the standard Samba create mask parameters. - These are :

    security mask

    force security mode

    directory security mask

    force directory security mode

    Once a user clicks "OK" to apply the + These are :

    security mask

    force security mode

    directory security mask

    force directory security mode

    Once a user clicks "OK" to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that + file against the bits set in the + security mask parameter. Any bits that were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask - mask may be treated as a set of bits the user is not + in the file permissions.

    Essentially, zero bits in the security mask + mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change. -

    If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the +

    If not set explicitly this parameter is set to the same value as + the create mask + parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter - to 0777.

    Next Samba checks the changed permissions for a file against - the bits set in the force security mode parameter. Any bits + to 0777.

    Next Samba checks the changed permissions for a file against + the bits set in the + force security mode parameter. Any bits that were changed that correspond to bits set to '1' in this parameter - are forced to be set.

    Essentially, bits set in the force security mode - parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value - as the force - create mode parameter. + are forced to be set.

    Essentially, bits set in the force security mode + parameter may be treated as a set of bits that, when + modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value + as the force + create mode parameter. To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force - security mode parameters are applied to the change - request in that order.

    For a directory Samba will perform the same operations as - described above for a file except using the parameter directory security mask instead of security - mask, and force directory security mode - parameter instead of force security mode - .

    The directory security mask parameter - by default is set to the same value as the directory mask - parameter and the force directory security - mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + with no restrictions set this parameter to 000.

    The security mask and force + security mode parameters are applied to the change + request in that order.

    For a directory Samba will perform the same operations as + described above for a file except using the parameter + directory security mask instead of security + mask, and force directory security mode + parameter instead of force security mode + .

    The directory security mask parameter + by default is set to the same value as the directory mask + parameter and the force directory security + mode parameter by default is set to the same value as + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control + to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't force any particular bits to be set 'on', then set the following - parameters in the smb.conf file in that share specific section :

    security mask = 0777

    force security mode = 0

    directory security mask = 0777

    force directory security mode = 0

    11.7. Interaction with the standard Samba file attribute - mapping

    Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can + parameters in the smb.conf file in that share specific section :

    security mask = 0777

    force security mode = 0

    directory security mask = 0777

    force directory security mode = 0

    Interaction with the standard Samba file attribute + mapping

    Samba maps some of the DOS attribute bits (such as "read + only") into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security dialog and the permission bits set by the file attribute mapping. -

    One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard +

    One way this can show up is if a file has no UNIX read access + for the owner it will show up as "read only" in the standard file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions + the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions to allow themselves read access using the security dialog, clicks - "OK" to get back to the standard attributes tab - dialog, and then clicks "OK" on that dialog, then + "OK" to get back to the standard attributes tab + dialog, and then clicks "OK" on that dialog, then NT will set the file permissions back to read-only (as that is what the attributes still say in the dialog). This means that after setting - permissions and clicking "OK" to get back to the - attributes dialog you should always hit "Cancel" - rather than "OK" to ensure that your changes - are not overridden.

    Chapter 12. Configuring Group Mapping

    -Starting with Samba 3.0 alpha 2, a new group mapping function is available. The -current method (likely to change) to manage the groups is a new command called -smbgroupedit.

    The first immediate reason to use the group mapping on a PDC, is that -the domain admin group of smb.conf is -now gone. This parameter was used to give the listed users local admin rights -on their workstations. It was some magic stuff that simply worked but didn't -scale very well for complex setups.

    Let me explain how it works on NT/W2K, to have this magic fade away. + permissions and clicking "OK" to get back to the + attributes dialog you should always hit "Cancel" + rather than "OK" to ensure that your changes + are not overridden.

    Chapter12.Configuring Group Mapping

    Jean Franois Micouleau

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    +Starting with Samba 3.0 alpha 2, new group mapping functionality +is available to create associations between Windows SIDs and UNIX +groups. The groupmap subcommand included with +the net tool can be used to manage these associations. +

    +The first immediate reason to use the group mapping on a Samba PDC, is that +the domain admin group smb.conf has been removed. +This parameter was used to give the listed users membership in the "Domain Admins" +Windows group which gave local admin rights on their workstations (in +default configurations). +

    When installing NT/W2K on a computer, the installer program creates some users and groups. Notably the 'Administrators' group, and gives to that group some privileges like the ability to change the date and time or to kill any process (or close too) running on the local machine. The 'Administrator' user is a member of the 'Administrators' group, and thus 'inherit' the 'Administrators' group privileges. If a 'joe' user is created and become a member of the -'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    When a NT/W2K machine is joined to a domain, during that phase, the "Domain -Administrators' group of the PDC is added to the 'Administrators' group of the -workstation. Every members of the 'Domain Administrators' group 'inherit' the -rights of the 'Administrators' group when logging on the workstation.

    You are now wondering how to make some of your samba PDC users members of the -'Domain Administrators' ? That's really easy.

    1. create a unix group (usually in /etc/group), let's call it domadm

    2. add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in /etc/group will look like:

      domadm:x:502:joe,john,mary

    3. Map this domadm group to the domain admins group by running the command:

      smbgroupedit -c "Domain Admins" -u domadm

    You're set, joe, john and mary are domain administrators !

    Like the Domain Admins group, you can map any arbitrary Unix group to any NT -group. You can also make any Unix group a domain group. For example, on a domain -member machine (an NT/W2K or a samba server running winbind), you would like to -give access to a certain directory to some users who are member of a group on -your samba PDC. Flag that group as a domain group by running:

    smbgroupedit -a unixgroup -td

    You can list the various groups in the mapping database like this

    smbgroupedit -v

    Chapter 13. Printing Support

    13.1. Introduction

    Beginning with the 2.2.0 release, Samba supports +'Administrator' group, 'joe' has exactly the same rights as 'Administrator'. +

    +When a NT/W2K machine is joined to a domain, the "Domain Adminis" group of the +PDC is added to the local 'Administrators' group of the workstation. Every +member of the 'Domain Administrators' group 'inherit' the +rights of the local 'Administrators' group when logging on the workstation. +

    +The following steps describe how to make samba PDC users members of the +'Domain Admins' group? +

    1. create a unix group (usually in /etc/group), + let's call it domadm

    2. add to this group the users that must be Administrators. For example + if you want joe,john and mary, your entry in /etc/group will + look like:

      +  domadm:x:502:joe,john,mary
+

    3. Map this domadm group to the "Domain Admins" group + by running the command:

      root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm

      The quotes around "Domain Admins" are necessary due to the space in the group name. Also make + sure to leave no whitespace surrounding the equal character (=).

    Now joe, john and mary are domain administrators!

    +It is possible to map any arbitrary UNIX group to any Windows NT +group as well as making any UNIX group a Windows domain group. +For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a +local file or printer on a domain member machine, you would flag +that group as a domain group by running the following on the Samba PDC: +

    root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct

    Be aware that the rid parmeter is a unsigned 32 bit integer that should +normally start at 1000. However, this rid must not overlap with any RID assigned +to a user. Verifying this is done differently depending on on the passdb backend +you are using. Future versions of the tools may perform the verification automatically, +but for now the burden in on you.

    You can list the various groups in the mapping database by executing +net groupmap list. Here is an example:

    root# net groupmap list
+System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
+Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
+Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
+Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
+

    For complete details on net groupmap, refer to the +net(8) man page.

    Chapter13.Printing Support

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Patrick Powell

    <papowell@lprng.org>

    (3 May 2001)

    Table of Contents

    Introduction
    Configuration
    Creating [print$]
    Setting Drivers for Existing Printers
    Support a large number of printers
    Adding New Printers via the Windows NT APW
    Samba and Printer Ports
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints server
    The Installation Client
    Diagnosis
    Introduction
    Debugging printer problems
    What printers do I have?
    Setting up printcap and print servers
    Job sent, no output
    Job sent, strange output
    Raw PostScript printed
    Advanced Printing
    Real debugging

    Introduction

    Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of -Samba only supported LanMan printing calls.

    The additional functionality provided by the new -SPOOLSS support includes:

    • Support for downloading printer driver +Samba only supported LanMan printing calls.

      The additional functionality provided by the new +SPOOLSS support includes:

      • Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon demand. -

      • Uploading of printer drivers via the +

      • Uploading of printer drivers via the Windows NT Add Printer Wizard (APW) or the - Imprints tool set (refer to http://imprints.sourceforge.net). -

      • Support for the native MS-RPC printing + Imprints tool set (refer to http://imprints.sourceforge.net). +

      • Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), etc... (See - the MSDN documentation at http://msdn.microsoft.com/ + the MSDN documentation at http://msdn.microsoft.com/ for more information on the Win32 printing API) -

      • Support for NT Access Control Lists (ACL) - on printer objects

      • Improved support for printer queue manipulation +

      • Support for NT Access Control Lists (ACL) + on printer objects

      • Improved support for printer queue manipulation through the use of an internal databases for spooled job - information

      There has been some initial confusion about what all this means + information

    +There has been some initial confusion about what all this means and whether or not it is a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients. As a side note, Samba does not use these drivers in any way to process -spooled files. They are utilized entirely by the clients.

    The following MS KB article, may be of some help if you are dealing with -Windows 2000 clients: How to Add Printers with No User -Interaction in Windows 2000

    http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP

    13.2. Configuration

    [print$] vs. [printer$]
     

    Previous versions of Samba recommended using a share named [printer$]. +spooled files. They are utilized entirely by the clients. +

    +The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: How to Add Printers with No User +Interaction in Windows 2000 +

    +http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP +

    Configuration

    [print$] vs. [printer$]

    +Previous versions of Samba recommended using a share named [printer$]. This name was taken from the printer$ service created by Windows 9x clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no -password in order to support printer driver downloads.

    However, the initial implementation allowed for a -parameter named printer driver location +password in order to support printer driver downloads. +

    +However, the initial implementation allowed for a +parameter named printer driver location to be used on a per share basis to specify the location of the driver files associated with that printer. Another -parameter named printer driver provided +parameter named printer driver provided a means of defining the printer driver name to be sent to -the client.

    13.2.1. Creating [print$]

    In order to support the uploading of printer driver +the client. +

    Creating [print$]

    +In order to support the uploading of printer driver files, you must first configure a file share named [print$]. The name of this share is hard coded in Samba's internals so the name is very important (print$ is the service used by Windows NT print servers to provide support for printer driver -download).

    You should modify the server's smb.conf file to add the global +download). +

    You should modify the server's smb.conf file to add the global parameters and to create the following file share (of course, some of the parameter values, such as 'path' are arbitrary and should be replaced with -appropriate values for your site):

    [global]
+appropriate values for your site):
    +[global]
     ; members of the ntadmin group should be able
     ; to add drivers and set printer properties
     ; root is implicitly a 'printer admin'
@@ -8013,290 +3117,100 @@ CLASS="PROGRAMLISTING"
     ; sure this account can copy files to the share.  If this
     ; is setup to a non-root account, then it should also exist
     ; as a 'printer admin'
-    write list = @ntadmin,root
    The write list is used to allow administrative 
+    write list = @ntadmin,root
+

    The +write list is used to allow administrative level user accounts to have write access in order to update files -on the share. See the smb.conf(5) -man page for more information on configuring file shares.

    The requirement for guest -ok = yes depends upon how your +on the share. See the smb.conf(5) +man page for more information on configuring file shares.

    The requirement for guest +ok = yes depends upon how your site is configured. If users will be guaranteed to have -an account on the Samba host, then this is a non-issue.

    Author's Note
     

    The non-issue is that if all your Windows NT users are guaranteed to be +an account on the Samba host, then this is a non-issue.

    Author's Note

    +The non-issue is that if all your Windows NT users are guaranteed to be authenticated by the Samba server (such as a domain member server and the NT user has already been validated by the Domain Controller in order to logon to the Windows NT console), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share for -guest access. You'll probably want to add map to guest = Bad User in the [global] section as well. Make sure +guest access. You'll probably want to add map to guest = Bad User + in the [global] section as well. Make sure you understand what this parameter does before using it -though. --jerry

    In order for a Windows NT print server to support +though. --jerry +

    In order for a Windows NT print server to support the downloading of driver files by multiple client architectures, it must create subdirectories within the [print$] service which correspond to each of the supported client architectures. -Samba follows this model as well.

    Next create the directory tree below the [print$] share -for each architecture you wish to support.

    [print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC"

    ATTENTION! REQUIRED PERMISSIONS
     

    In order to currently add a new driver to you Samba host, -one of two conditions must hold true:

    • The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host - must be a member of the printer - admin list.

    Of course, the connected account must still possess access +Samba follows this model as well.

    Next create the directory tree below the [print$] share +for each architecture you wish to support.

    +[print$]----- + |-W32X86 ; "Windows NT x86" + |-WIN40 ; "Windows 95/98" + |-W32ALPHA ; "Windows NT Alpha_AXP" + |-W32MIPS ; "Windows NT R4000" + |-W32PPC ; "Windows NT PowerPC" +

    ATTENTION! REQUIRED PERMISSIONS

    +In order to currently add a new driver to you Samba host, +one of two conditions must hold true: +

    • The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host + must be a member of the printer + admin list.

    +Of course, the connected account must still possess access to add files to the subdirectories beneath [print$]. Remember -that all file shares are set to 'read only' by default.

    Once you have created the required [print$] service and +that all file shares are set to 'read only' by default. +

    +Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using -a root (or printer admin) account -from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or -"My Network Places" and browse for the Samba host. Once you have located -the server, navigate to the "Printers..." folder. +a root (or printer admin) account +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. You should see an initial listing of printers -that matches the printer shares defined on your Samba host.

    13.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's +that matches the printer shares defined on your Samba host. +

    Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned to them. This defaults to a NULL string to allow the use of the local Add Printer Wizard on NT/2000 clients. Attempting to view the printer properties for a printer which has this default driver assigned will result in -the error message:

    Device settings cannot be displayed. The driver +the error message:

    +Device settings cannot be displayed. The driver for the specified printer is not installed, only spooler properties will be displayed. Do you want to install the -driver now?

    Click "No" in the error dialog and you will be presented with +driver now? +

    +Click "No" in the error dialog and you will be presented with the printer properties window. The way to assign a driver to a -printer is to either

    • Use the "New Driver..." button to install - a new printer driver, or

    • Select a driver from the popup list of - installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client -operating systems other than "Windows NT x86", you will need -to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you +printer is to either +

    • Use the "New Driver..." button to install + a new printer driver, or

    • Select a driver from the popup list of + installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client +operating systems other than "Windows NT x86", you will need +to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you will also be able modify other printer properties such as -ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible +ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible on a Windows NT print server to have printers listed in the Printers folder which are not shared. Samba does not make this distinction. By definition, the only printers of which Samba is aware are those which are specified as shares in -smb.conf.

    Another interesting side note is that Windows NT clients do +smb.conf.

    Another interesting side note is that Windows NT clients do not use the SMB printer share, but rather can print directly to any printer on another Windows NT host using MS-RPC. This of course assumes that the printing client has the necessary privileges on the remote host serving the printer. The default -permissions assigned by Windows NT to a printer gives the "Print" -permissions to the "Everyone" well-known group.

    13.2.3. Support a large number of printers

    One issue that has arisen during the development +permissions assigned by Windows NT to a printer gives the "Print" +permissions to the "Everyone" well-known group. +

    Support a large number of printers

    One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for 100's of printers. Using the Windows NT APW is somewhat awkward to say the list. If more than one printer are using the -same driver, the rpcclient's -setdriver command can be used to set the driver +same driver, the rpcclient's +setdriver command can be used to set the driver associated with an installed driver. The following is example -of how this could be accomplished:

    $ rpcclient pogo -U root%secret -c "enumdrivers" -

     
+of how this could be accomplished:
    
+$ rpcclient pogo -U root%secret -c "enumdrivers"
+
     
 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
  
 [Windows NT x86]
@@ -8307,145 +3221,53 @@ Printer Driver Info 1:
      Driver Name: [HP LaserJet 2100 Series PS]
  
 Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4Si/4SiMX PS]
    				  
-$ rpcclient pogo -U root%secret -c "enumprinters"
-
    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+     Driver Name: [HP LaserJet 4Si/4SiMX PS]
+
    				  
+$ rpcclient pogo -U root%secret -c "enumprinters"
+
    +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
      flags:[0x800000]
      name:[\\POGO\hp-print]
      description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
      comment:[]
-				  
    
-$ rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
-
    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-Successfully set hp-print to driver HP LaserJet 4000 Series PS.

    13.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in smb.conf -in the "Printers..." folder. Also existing in this folder is the Windows NT -Add Printer Wizard icon. The APW will be show only if

    • The connected user is able to successfully + +

      +$ rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" +

      +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+Successfully set hp-print to driver HP LaserJet 4000 Series PS.
+

    Adding New Printers via the Windows NT APW

    +By default, Samba offers all printer shares defined in smb.conf +in the "Printers..." folder. Also existing in this folder is the Windows NT +Add Printer Wizard icon. The APW will be show only if +

    • The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or printer admin). -

    • show - add printer wizard = yes (the default). -

    In order to be able to use the APW to successfully add a printer to a Samba -server, the add -printer command must have a defined value. The program + privileges (i.e. root or printer admin). +

  • show + add printer wizard = yes (the default). +

    • +In order to be able to use the APW to successfully add a printer to a Samba +server, the add +printer command must have a defined value. The program hook must successfully add the printer to the system (i.e. -/etc/printcap or appropriate files) and -smb.conf if necessary.

    When using the APW from a client, if the named printer share does -not exist, smbd will execute the add printer -command and reparse to the smb.conf +/etc/printcap or appropriate files) and +smb.conf if necessary. +

    +When using the APW from a client, if the named printer share does +not exist, smbd will execute the add printer +command and reparse to the smb.conf to attempt to locate the new printer share. If the share is still not defined, -an error of "Access Denied" is returned to the client. Note that the -add printer program is executed under the context -of the connected user, not necessarily a root account.

    There is a complementary delete -printer command for removing entries from the "Printers..." -folder.

    The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.

    #!/bin/sh
+an error of "Access Denied" is returned to the client.  Note that the 
+add printer program is executed under the context
+of the connected user, not necessarily a root account.
+
    
+There is a complementary delete
+printer command for removing entries from the "Printers..."
+folder.
+
    
+The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.
+
    +#!/bin/sh
 
 # Script to insert a new printer entry into printcap.local
 #
@@ -8461,213 +3283,84 @@ CLASS="PROGRAMLISTING"
 PRINTCAP=/etc/printcap.local
 DATE=`date +%Y%m%d-%H%M%S`
 LP=lp
-RESTART="service lpd restart"
+RESTART="service lpd restart"
 
 # Keep a copy
 cp $PRINTCAP $PRINTCAP.$DATE
 # Add the printer to $PRINTCAP
-echo ""				 			>> $PRINTCAP
-echo "$2|$1:\\" 					>> $PRINTCAP
-echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
-echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
-echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
+echo ""				 			>> $PRINTCAP
+echo "$2|$1:\\" 					>> $PRINTCAP
+echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
+echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
+echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
 
-touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
-chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
 
 mkdir /var/spool/lpd/$2
 chmod 700 /var/spool/lpd/$2
 chown $LP /var/spool/lpd/$2
-#echo $1 >> "/usr/local/samba/var/print/$5.prn"
-#echo $2 >> "/usr/local/samba/var/print/$5.prn"
-#echo $3 >> "/usr/local/samba/var/print/$5.prn"
-#echo $4 >> "/usr/local/samba/var/print/$5.prn"
-#echo $5 >> "/usr/local/samba/var/print/$5.prn"
-#echo $6 >> "/usr/local/samba/var/print/$5.prn"
-$RESTART >> "/usr/local/samba/var/print/$5.prn"
+#echo $1 >> "/usr/local/samba/var/print/$5.prn"
+#echo $2 >> "/usr/local/samba/var/print/$5.prn"
+#echo $3 >> "/usr/local/samba/var/print/$5.prn"
+#echo $4 >> "/usr/local/samba/var/print/$5.prn"
+#echo $5 >> "/usr/local/samba/var/print/$5.prn"
+#echo $6 >> "/usr/local/samba/var/print/$5.prn"
+$RESTART >> "/usr/local/samba/var/print/$5.prn"
 # Not sure if this is needed
 touch /usr/local/samba/lib/smb.conf
 #
 # You need to return a value, but I am not sure what it means.
 #
-echo "Done"
-exit 0

    13.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally +echo "Done" +exit 0 +

    Samba and Printer Ports

    +Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the concept of ports associated with a printer. By default, only one printer port, -named "Samba Printer Port", exists on a system. Samba does not really a port in -order to print, rather it is a requirement of Windows clients.

    Note that Samba does not support the concept of "Printer Pooling" internally +named "Samba Printer Port", exists on a system. Samba does not really a port in +order to print, rather it is a requirement of Windows clients. +

    +Note that Samba does not support the concept of "Printer Pooling" internally either. This is when a logical printer is assigned to multiple ports as -a form of load balancing or fail over.

    If you require that multiple ports be defined for some reason, -smb.conf possesses a enumports -command which can be used to define an external program -that generates a listing of ports on a system.

    13.3. The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the +a form of load balancing or fail over. +

    +If you require that multiple ports be defined for some reason, +smb.conf possesses a enumports +command which can be used to define an external program +that generates a listing of ports on a system. +

    The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please - refer to the Imprints web site at http://imprints.sourceforge.net/ as well as the documentation + refer to the Imprints web site at + http://imprints.sourceforge.net/ as well as the documentation included with the imprints source distribution. This section will - only provide a brief introduction to the features of Imprints.

    13.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals - of

    • Providing a central repository information - regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating - the Imprints printer driver packages.

    • Providing an installation client which + only provide a brief introduction to the features of Imprints.

      What is Imprints?

      Imprints is a collection of tools for supporting the goals + of

      • Providing a central repository information + regarding Windows NT and 95/98 printer driver packages

      • Providing the tools necessary for creating + the Imprints printer driver packages.

      • Providing an installation client which will obtain and install printer drivers on remote Samba - and Windows NT 4 print servers.

      13.3.2. Creating Printer Driver Packages

      The process of creating printer driver packages is beyond + and Windows NT 4 print servers.

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included with the Samba distribution for more information). In short, an Imprints driver package is a gzipped tarball containing the driver files, related INF files, and a control file needed by the - installation client.

    13.3.3. The Imprints server

    The Imprints server is really a database server that + installation client.

    The Imprints server

    The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer entry in the database has an associated URL for the actual downloading of the package. Each package is digitally signed via GnuPG which can be used to verify that package downloaded is actually the one referred in the Imprints database. It is - not recommended that this security check - be disabled.

    13.3.4. The Installation Client

    More information regarding the Imprints installation client - is available in the Imprints-Client-HOWTO.ps - file included with the imprints source package.

    The Imprints installation client comes in two forms.

    • a set of command line Perl scripts

    • a GTK+ based graphical interface to - the command line perl scripts

    The installation client (in both forms) provides a means + not recommended that this security check + be disabled.

    The Installation Client

    More information regarding the Imprints installation client + is available in the Imprints-Client-HOWTO.ps + file included with the imprints source package.

    The Imprints installation client comes in two forms.

    • a set of command line Perl scripts

    • a GTK+ based graphical interface to + the command line perl scripts

    The installation client (in both forms) provides a means of querying the Imprints database server for a matching list of known printer model names as well as a means to download and install the drivers on remote Samba and Windows - NT print servers.

    The basic installation process is in four steps and - perl code is wrapped around smbclient - and rpcclient.

    	
+		NT print servers.
    The basic installation process is in four steps and 
+		perl code is wrapped around smbclient 
+		and rpcclient.
    	
 foreach (supported architecture for a given driver)
 {
      1.  rpcclient: Get the appropriate upload directory 
@@ -8677,974 +3370,499 @@ foreach (supported architecture for a given driver)
 }
 	
 4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
-    create the printer
    One of the problems encountered when implementing 
+    create the printer
+

    One of the problems encountered when implementing the Imprints tool set was the name space issues between various supported client architectures. For example, Windows - NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 calls its version of this driver "Apple - LaserWriter II NTX"

    The problem is how to know what client drivers have + NT includes a driver named "Apple LaserWriter II NTX v51.8" + and Windows 95 calls its version of this driver "Apple + LaserWriter II NTX"

    The problem is how to know what client drivers have been uploaded for a printer. As astute reader will remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A quick look in the - Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment -

    will reveal that Windows NT always uses the NT driver + Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment +

    will reveal that Windows NT always uses the NT driver name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not - already been installed?

    The way of sidestepping this limitation is to require + already been installed?

    The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that NT driver is - installed first.

    13.4. Diagnosis

    13.4.1. Introduction

    This is a short description of how to debug printing problems with + installed first.

    Diagnosis

    Introduction

    +This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB client to a Samba server, not the other way around. For the reverse -see the examples/printing directory.

    Ok, so you want to print to a Samba server from your PC. The first +see the examples/printing directory. +

    +Ok, so you want to print to a Samba server from your PC. The first thing you need to understand is that Samba does not actually do any printing itself, it just acts as a middleman between your PC client and your Unix printing subsystem. Samba receives the file from the PC -then passes the file to a external "print command". What print command -you use is up to you.

    The whole things is controlled using options in smb.conf. The most +then passes the file to a external "print command". What print command +you use is up to you. +

    +The whole things is controlled using options in smb.conf. The most relevant options (which you should look up in the smb.conf man page) -are:

          [global]
+are:
+
    +      [global]
         print command     - send a file to a spooler
         lpq command       - get spool queue status
         lprm command      - remove a job
       [printers]
-        path = /var/spool/lpd/samba
    The following are nice to know about:
            queuepause command   - stop a printer or print queue
-        queueresume command  - start a printer or print queue
    Example:
            print command = /usr/bin/lpr -r -P%p %s
+        path = /var/spool/lpd/samba
+
    
+The following are nice to know about:
+
    +        queuepause command   - stop a printer or print queue
+        queueresume command  - start a printer or print queue
+
    
+Example:
+
    +        print command = /usr/bin/lpr -r -P%p %s
         lpq command   = /usr/bin/lpq    -P%p %s
         lprm command  = /usr/bin/lprm   -P%p %j
         queuepause command = /usr/sbin/lpc -P%p stop
-        queuepause command = /usr/sbin/lpc -P%p start
    Samba should set reasonable defaults for these depending on your
+        queuepause command = /usr/sbin/lpc -P%p start
+

    +Samba should set reasonable defaults for these depending on your system type, but it isn't clairvoyant. It is not uncommon that you have to tweak these for local conditions. The commands should always have fully specified pathnames, as the smdb may not have -the correct PATH values.

    When you send a job to Samba to be printed, it will make a temporary +the correct PATH values. +

    +When you send a job to Samba to be printed, it will make a temporary copy of it in the directory specified in the [printers] section. and it should be periodically cleaned out. The lpr -r option requests that the temporary copy be removed after printing; If printing fails then you might find leftover files in this directory, and it should be periodically cleaned out. Samba used the lpq -command to determine the "job number" assigned to your print job -by the spooler.

    The %>letter< are "macros" that get dynamically replaced with appropriate +command to determine the "job number" assigned to your print job +by the spooler. +

    +The %>letter< are "macros" that get dynamically replaced with appropriate values when they are used. The %s gets replaced with the name of the spool file that Samba creates and the %p gets replaced with the name of the -printer. The %j gets replaced with the "job number" which comes from -the lpq output.

    13.4.2. Debugging printer problems

    One way to debug printing problems is to start by replacing these +printer. The %j gets replaced with the "job number" which comes from +the lpq output. +

    Debugging printer problems

    +One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents of the print file. A simple example of this kind of things might -be:

    	print command = /tmp/saveprint %p %s
+be:
+
    +	print command = /tmp/saveprint %p %s
 
     #!/bin/saveprint
     # we make sure that we are the right user
-    /usr/bin/id -p >/tmp/tmp.print
+    /usr/bin/id -p >/tmp/tmp.print
     # we run the command and save the error messages
     # replace the command with the one appropriate for your system
-    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print
    Then you print a file and try removing it.  You may find that the
+    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print
+

    +Then you print a file and try removing it. You may find that the print queue needs to be stopped in order to see the queue status -and remove the job:

    
h4: {42} % echo hi >/tmp/hi
+and remove the job:
+
    +
+h4: {42} % echo hi >/tmp/hi
 h4: {43} % smbclient //localhost/lw4
 added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
 Password: 
 Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \> print /tmp/hi
+smb: \> print /tmp/hi
 putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \> queue
+smb: \> queue
 1049     3            hi-17534
-smb: \> cancel 1049
+smb: \> cancel 1049
 Error cancelling job 1049 : code 0
-smb: \> cancel 1049
+smb: \> cancel 1049
 Job 1049 cancelled
-smb: \> queue
-smb: \> exit
    The 'code 0' indicates that the job was removed.  The comment
+smb: \> queue
+smb: \> exit
+

    +The 'code 0' indicates that the job was removed. The comment by the smbclient is a bit misleading on this. You can observe the command output and then and look at the /tmp/tmp.print file to see what the results are. You can quickly find out if the problem is with your printing system. Often people have problems with their /etc/printcap file or permissions on -various print queues.

    13.4.3. What printers do I have?

    You can use the 'testprns' program to check to see if the printer +various print queues. +

    What printers do I have?

    +You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can -use:

        testprns printer /etc/printcap

    Samba can get its printcap information from a file or from a program. +use: +

    +    testprns printer /etc/printcap
+

    +Samba can get its printcap information from a file or from a program. You can try the following to see the format of the extracted -information:

        testprns -a printer /etc/printcap
+information:
+
    +    testprns -a printer /etc/printcap
 
-    testprns -a printer '|/bin/cat printcap'

    13.4.4. Setting up printcap and print servers

    You may need to set up some printcaps for your Samba system to use. + testprns -a printer '|/bin/cat printcap' +

    Setting up printcap and print servers

    +You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by -the print spooler to set up queues and printcap information.

    Samba requires either a printcap or program to deliver printcap -information. This printcap information has the format:

      name|alias1|alias2...:option=value:...

    For almost all printing systems, the printer 'name' must be composed +the print spooler to set up queues and printcap information. +

    +Samba requires either a printcap or program to deliver printcap +information. This printcap information has the format: +

    +  name|alias1|alias2...:option=value:...
+

    +For almost all printing systems, the printer 'name' must be composed only of alphanumeric or underscore '_' characters. Some systems also allow hyphens ('-') as well. An alias is an alternative name for the printer, and an alias with a space in it is used as a 'comment' about the printer. The printcap format optionally uses a \ at the end of lines -to extend the printcap to multiple lines.

    Here are some examples of printcap files:

    1. pr just printer name

    2. pr|alias printer name and alias

    3. pr|My Printer printer name, alias used as comment

    4. pr:sh:\ Same as pr:sh:cm= testing +to extend the printcap to multiple lines. +

      +Here are some examples of printcap files: +

      +

      1. +pr just printer name +

      2. +pr|alias printer name and alias +

      3. +pr|My Printer printer name, alias used as comment +

      4. +pr:sh:\ Same as pr:sh:cm= testing :cm= \ - testing

      5. pr:sh Same as pr:sh:cm= testing - :cm= testing

      Samba reads the printcap information when first started. If you make -changes in the printcap information, then you must do the following:

      1. make sure that the print spooler is aware of these changes. -The LPRng system uses the 'lpc reread' command to do this.

      2. make sure that the spool queues, etc., exist and have the + testing +

      3. +pr:sh Same as pr:sh:cm= testing + :cm= testing +

      +

      +Samba reads the printcap information when first started. If you make +changes in the printcap information, then you must do the following: +

      1. +make sure that the print spooler is aware of these changes. +The LPRng system uses the 'lpc reread' command to do this. +

      2. +make sure that the spool queues, etc., exist and have the correct permissions. The LPRng system uses the 'checkpc -f' -command to do this.

      3. You now should send a SIGHUP signal to the smbd server to have -it reread the printcap information.

      13.4.5. Job sent, no output

      This is the most frustrating part of printing. You may have sent the +command to do this. +

    5. +You now should send a SIGHUP signal to the smbd server to have +it reread the printcap information. +

    Job sent, no output

    +This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around -the command to send the file, but there was no output from the printer.

    First, check to make sure that the job REALLY is getting to the +the command to send the file, but there was no output from the printer. +

    +First, check to make sure that the job REALLY is getting to the right print queue. If you are using a BSD or LPRng print spooler, you can temporarily stop the printing of jobs. Jobs can still be -submitted, but they will not be printed. Use:

      lpc -Pprinter stop

    Now submit a print job and then use 'lpq -Pprinter' to see if the +submitted, but they will not be printed. Use: +

    +  lpc -Pprinter stop
+

    +Now submit a print job and then use 'lpq -Pprinter' to see if the job is in the print queue. If it is not in the print queue then -you will have to find out why it is not being accepted for printing.

    Next, you may want to check to see what the format of the job really +you will have to find out why it is not being accepted for printing. +

    +Next, you may want to check to see what the format of the job really was. With the assistance of the system administrator you can view the submitted jobs files. You may be surprised to find that these are not in what you would expect to call a printable format. You can use the UNIX 'file' utitily to determine what the job -format actually is:

        cd /var/spool/lpd/printer   # spool directory of print jobs
+format actually is:
+
    +    cd /var/spool/lpd/printer   # spool directory of print jobs
     ls                          # find job files
-    file dfA001myhost
    You should make sure that your printer supports this format OR that
+    file dfA001myhost
+

    +You should make sure that your printer supports this format OR that your system administrator has installed a 'print filter' that will -convert the file to a format appropriate for your printer.

    13.4.6. Job sent, strange output

    Once you have the job printing, you can then start worrying about -making it print nicely.

    The most common problem is extra pages of output: banner pages -OR blank pages at the end.

    If you are getting banner pages, check and make sure that the +convert the file to a format appropriate for your printer. +

    Job sent, strange output

    +Once you have the job printing, you can then start worrying about +making it print nicely. +

    +The most common problem is extra pages of output: banner pages +OR blank pages at the end. +

    +If you are getting banner pages, check and make sure that the printcap option or printer option is configured for no banners. If you have a printcap, this is the :sh (suppress header or banner -page) option. You should have the following in your printer.

       printer: ... :sh

    If you have this option and are still getting banner pages, there +page) option. You should have the following in your printer. +

    +   printer: ... :sh
+

    +If you have this option and are still getting banner pages, there is a strong chance that your printer is generating them for you automatically. You should make sure that banner printing is disabled for the printer. This usually requires using the printer setup software -or procedures supplied by the printer manufacturer.

    If you get an extra page of output, this could be due to problems +or procedures supplied by the printer manufacturer. +

    +If you get an extra page of output, this could be due to problems with your job format, or if you are generating PostScript jobs, incorrect setting on your printer driver on the MicroSoft client. -For example, under Win95 there is a option:

      Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|

    that allows you to choose if a Ctrl-D is appended to all jobs. +For example, under Win95 there is a option: +

    +  Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|
+

    +that allows you to choose if a Ctrl-D is appended to all jobs. This is a very bad thing to do, as most spooling systems will automatically add a ^D to the end of the job if it is detected as -PostScript. The multiple ^D may cause an additional page of output.

    13.4.7. Raw PostScript printed

    This is a problem that is usually caused by either the print spooling +PostScript. The multiple ^D may cause an additional page of output. +

    Raw PostScript printed

    +This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes the printer think the job is a text file, or your printer simply does not support PostScript. You may need to enable 'Automatic -Format Detection' on your printer.

    13.4.8. Advanced Printing

    Note that you can do some pretty magic things by using your -imagination with the "print command" option and some shell scripts. +Format Detection' on your printer. +

    Advanced Printing

    +Note that you can do some pretty magic things by using your +imagination with the "print command" option and some shell scripts. Doing print accounting is easy by passing the %U option to a print command shell script. You could even make the print command detect the type of output and its size and send it to an appropriate -printer.

    13.4.9. Real debugging

    If the above debug tips don't help, then maybe you need to bring in -the bug guns, system tracing. See Tracing.txt in this directory.

    Chapter 14. CUPS Printing Support

    14.1. Introduction

    The Common Unix Print System (CUPS) has become very popular, but to many it is +printer. +

    Real debugging

    +If the above debug tips don't help, then maybe you need to bring in +the bug guns, system tracing. See Tracing.txt in this directory. +

    Chapter14.CUPS Printing Support

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Kurt Pfeifle

    <kpfeifle@danka.de>

    (25 March 2003)

    Table of Contents

    Introduction
    Configuring smb.conf for CUPS
    CUPS - RAW Print Through Mode
    CUPS as a network PostScript RIP
    Windows Terminal Servers (WTS) as CUPS clients
    Setting up CUPS for driver download
    Sources of CUPS drivers / PPDs
    cupsaddsmb
    The CUPS Filter Chains
    CUPS Print Drivers and Devices
    Further printing steps
    Limiting the number of pages users can print
    Advanced Postscript Printing from MS Windows
    Auto-Deletion of CUPS spool files

    Introduction

    +The Common Unix Print System (CUPS) has become very popular, but to many it is a very mystical tool. There is a great deal of uncertainty regarding CUPS and how it works. The result is seen in a large number of posting on the samba mailing lists expressing frustration when MS Windows printers appear not to work with a CUPS -backr-end.

    This is a good time to point out how CUPS can be used and what it does. CUPS is more +backr-end. +

    +This is a good time to point out how CUPS can be used and what it does. CUPS is more than just a print spooling system - it is a complete printer management system that complies with HTTP and IPP protocols. It can be managed remotely via a web browser -and it can print using http and ipp protocols.

    CUPS allows to creation of RAW printers (ie: NO file format translation) as well as +and it can print using http and ipp protocols. +

    +CUPS allows to creation of RAW printers (ie: NO file format translation) as well as SMART printers (ie: CUPS does file format conversion as required for the printer). In many ways this gives CUPS similar capabilities to the MS Windows print monitoring system. Of course, if you are a CUPS advocate, you would agrue that CUPS is better! In any case, let us now move on to explore how one may configure CUPS for interfacing -with MS Windows print clients via Samba.

    CUPS is a newcomer in the UNIX printing scene, +with MS Windows print clients via Samba. +

    +CUPS is a newcomer in the UNIX printing scene, which has convinced many people upon first trial already. However, it has quite a few -new features, which make it different from other, more traditional printing systems.

    14.2. Configuring smb.conf for CUPS

    Printing with CUPS in the most basic smb.conf -setup in Samba-3 only needs two settings: printing = cups and -printcap = cups. While CUPS itself doesn't need a printcap -anymore, the cupsd.conf configuration file knows two directives -(example: Printcap /etc/printcap and PrintcapFormat -BSD), which control if such a file should be created for the +new features, which make it different from other, more traditional printing systems. +

    Configuring smb.conf for CUPS

    +Printing with CUPS in the most basic smb.conf +setup in Samba-3 only needs two settings: printing = cups and +printcap = cups. While CUPS itself doesn't need a printcap +anymore, the cupsd.conf configuration file knows two directives +(example: Printcap /etc/printcap and PrintcapFormat +BSD), which control if such a file should be created for the convenience of third party applications. Make sure it is set! For details see -man cupsd.conf and other CUPS-related documentation.

    If SAMBA is compiled against libcups, then printcap = cups uses the +man cupsd.conf and other CUPS-related documentation. +

    +If SAMBA is compiled against libcups, then printcap = cups uses the CUPS API to list printers, submit jobs, etc. Otherwise it maps to the System V commands -with an additional -oraw option for printing. On a Linux system, -you can use the ldd command to find out details (ldd may not be -present on other OS platforms, or its function may be embodied by a different command):

    transmeta:/home/kurt # ldd `which smbd`
-        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
-        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
-        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
-        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
-        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
-        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
-        libc.so.6 => /lib/libc.so.6 (0x4020b000)
-        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

    The line "libcups.so.2 => /usr/lib/libcups.so.2 -(0x40123000)" shows there is CUPS support compiled into this version of -Samba. If this is the case, and printing = cups is set, then any -otherwise manually set print command in smb.conf is ignored.

    14.3. CUPS - RAW Print Through Mode

    When used in raw print through mode is will be necessary to use the printer -vendor's drivers in each Windows client PC.

    When CUPS printers are configured for RAW print-through mode operation it is the +with an additional -oraw option for printing. On a Linux system, +you can use the ldd command to find out details (ldd may not be +present on other OS platforms, or its function may be embodied by a different command): +

    +

    transmeta:/home/kurt # ldd `which smbd`
+        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
+        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
+        libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
+        libdl.so.2 => /lib/libdl.so.2 (0x401e8000)
+        libnsl.so.1 => /lib/libnsl.so.1 (0x401ec000)
+        libpam.so.0 => /lib/libpam.so.0 (0x40202000)
+        libc.so.6 => /lib/libc.so.6 (0x4020b000)
+        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
+

    +The line "libcups.so.2 => /usr/lib/libcups.so.2 +(0x40123000)" shows there is CUPS support compiled into this version of +Samba. If this is the case, and printing = cups is set, then any +otherwise manually set print command in smb.conf is ignored. +

    CUPS - RAW Print Through Mode

    Note

    +When used in raw print through mode is will be necessary to use the printer +vendor's drivers in each Windows client PC. +

    +When CUPS printers are configured for RAW print-through mode operation it is the responsibility of the Samba client to fully render the print job (file) in a format that is suitable for direct delivery to the printer. In this case CUPS will NOT -do any print file format conversion work.

    The CUPS files that need to be correctly set for RAW mode printers to work are: +do any print file format conversion work. +

    +The CUPS files that need to be correctly set for RAW mode printers to work are: -

    • /etc/cups/mime.types

    • /etc/cups/mime.convs

    +

    • /etc/cups/mime.types

    • /etc/cups/mime.convs

    -Both contain entries that must be uncommented to allow RAW mode -operation.

    Firstly, to enable CUPS based printing from Samba the following options must be -enabled in your smb.conf file [globals] section: +Both contain entries that must be uncommented to allow RAW mode +operation. +

    +Firstly, to enable CUPS based printing from Samba the following options must be +enabled in your smb.conf file [globals] section: -

    • printing = CUPS

    • printcap = CUPS

    +

    • printing = CUPS

    • printcap = CUPS

    -When these parameters are specified the print directives in smb.conf (as well as in +When these parameters are specified the print directives in smb.conf (as well as in samba itself) will be ignored because samba will directly interface with CUPS through it's application program interface (API) - so long as Samba has been compiled with CUPS library (libcups) support. If samba has NOT been compiled with CUPS support then -printing will use the System V AT&T command set with the -oraw -option automatically passing through.

    Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) +printing will use the System V AT&T command set with the -oraw +option automatically passing through. +

    +Cupsomatic (an enhanced printing utility that is part of some CUPS implementations) on the Samba/CUPS server does *not* add any features if a file is really -printed "raw". However, if you have loaded the driver for the Windows client from -the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using -a "Foomatic" PPD, the PJL header in question is already added on the Windows client, +printed "raw". However, if you have loaded the driver for the Windows client from +the CUPS server, using the "cupsaddsmb" utility, and if this driver is one using +a "Foomatic" PPD, the PJL header in question is already added on the Windows client, at the time when the driver initially generated the PostScript data and CUPS in true -"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its -printer communication backend.

    NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* -"raw" printing, it only *allows* it.

    Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids +"-oraw" manner doesn't remove this PJL header and passes the file "as is" to its +printer communication backend. +

    Note

    NOTE: editing in the "mime.convs" and the "mime.types" file does not *enforce* +"raw" printing, it only *allows* it.

    +Print files that arrive from MS Windows printing are "auto-typed" by CUPS. This aids the process of determining proper treatment while in the print queue system. -

    • Files generated by PCL drivers and directed at PCK printers get auto-typed as - application/octet-stream. Unknown file format types also +

      • + Files generated by PCL drivers and directed at PCK printers get auto-typed as + application/octet-stream. Unknown file format types also get auto-typed with this tag. -

      • Files generated by a Postscript driver and directed at a Postscript printer +

      • + Files generated by a Postscript driver and directed at a Postscript printer are auto-typed depending on the auto-detected most suitable MIME type as: -

        • * application/postscript

        • * application/vnd.cups-postscript

        -

      "application/postscript" first goes thru the "pstops" filter (where the page counting +

      • * application/postscript

      • * application/vnd.cups-postscript

      +

    +

    +"application/postscript" first goes thru the "pstops" filter (where the page counting and accounting takes place). The outcome will be of MIME type -"application/vnd.cups-postscript". The pstopsfilter reads and uses information from +"application/vnd.cups-postscript". The pstopsfilter reads and uses information from the PPD and inserts user-provided options into the PostScript file. As a consequence, -the filtered file could possibly have an unwanted PJL header.

    "application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which -have as their first character string one of "%!" or ">04<%".

    "application/vnd.cups-postscript" will files which contain the string -"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the -first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes -(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS -or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced -with a "Generic PostScript driver" will just be tagged "application/postscript".

    Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" -or "cupsomatic" will take over (depending on the printer configuration, as -determined by the PPD in use).

    A printer queue with *no* PPD associated to it is a "raw" printer and all files +the filtered file could possibly have an unwanted PJL header. +

    +"application/postscript" will be all files with a ".ps", ".ai", ".eps" suffix or which +have as their first character string one of "%!" or ">04<%". +

    +"application/vnd.cups-postscript" will files which contain the string +"LANGUAGE=POSTSCRIPT" (or similar variations with different capitalization) in the +first 512 bytes, and also contain the "PJL super escape code" in the first 128 bytes +(">1B<%-12345X"). Very likely, most PostScript files generated on Windows using a CUPS +or other PPD, will have to be auto-typed as "vnd.cups-postscript". A file produced +with a "Generic PostScript driver" will just be tagged "application/postscript". +

    +Once the file is in "application/vnd.cups-postscript" format, either "pstoraster" +or "cupsomatic" will take over (depending on the printer configuration, as +determined by the PPD in use). +

    Note

    +A printer queue with *no* PPD associated to it is a "raw" printer and all files will go directly there as received by the spooler. The exeptions are file types -"application/octet-stream" which need "passthrough feature" enabled. -"Raw" queues don't do any filtering at all, they hand the file directly to the +"application/octet-stream" which need "passthrough feature" enabled. +"Raw" queues don't do any filtering at all, they hand the file directly to the CUPS backend. This backend is responsible for the sending of the data to the device -(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, -parallel:/, serial:/, usb:/ etc.)

    "cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. +(as in the "device URI" notation as lpd://, socket://, smb://, ipp://, http://, +parallel:/, serial:/, usb:/ etc.) +

    Note

    +"cupsomatic"/Foomatic are *not* native CUPS drivers and they don't ship with CUPS. They are a Third Party add-on, developed at Linuxprinting.org. As such, they are a brilliant hack to make all models (driven by Ghostscript drivers/filters in traditional spoolers) also work via CUPS, with the same (good or bad!) quality -as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript -commandline at that stage in the CUPS filtering chain, where "normally" the native -CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" +as in these other spoolers. "cupsomatic" is only a vehicle to execute a ghostscript +commandline at that stage in the CUPS filtering chain, where "normally" the native +CUPS "pstoraster" filter would kick in. cupsomatic by-passes pstoraster, "kidnaps" the printfile from CUPS away and re-directs it to go through Ghostscipt. CUPS accepts this, -because the associated CUPS-O-Matic-/Foomatic-PPD specifies:

       *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"

    This line persuades CUPS to hand the file to cupsomatic, once it has successfully -converted it to the MIME type "application/vnd.cups-postscript". This conversion will not -happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", -with the according changes in "/etc/cups/mime.types" in place.

    CUPS is widely configurable and flexible, even regarding its filtering mechanism. +because the associated CUPS-O-Matic-/Foomatic-PPD specifies: +

    +   *cupsFilter:  "application/vnd.cups-postscript 0 cupsomatic"
+

    +This line persuades CUPS to hand the file to cupsomatic, once it has successfully +converted it to the MIME type "application/vnd.cups-postscript". This conversion will not +happen for Jobs arriving from Windows which are auto-typed "application/octet-stream", +with the according changes in "/etc/cups/mime.types" in place. +

    +CUPS is widely configurable and flexible, even regarding its filtering mechanism. Another workaround in some situations would be to have -in "/etc/cups/mime.types" entries as follows:

       application/postscript           application/vnd.cups-raw  0  -
-   application/vnd.cups-postscript  application/vnd.cups-raw  0  -

    This would prevent all Postscript files from being filtered (rather, they will go -thru the virtual "nullfilter" denoted with "-"). This could only be useful for +in "/etc/cups/mime.types" entries as follows: +

    +   application/postscript           application/vnd.cups-raw  0  -
+   application/vnd.cups-postscript  application/vnd.cups-raw  0  -
+

    +This would prevent all Postscript files from being filtered (rather, they will go +thru the virtual "nullfilter" denoted with "-"). This could only be useful for PS printers. If you want to print PS code on non-PS printers an entry as follows -could be useful:

       */*           application/vnd.cups-raw  0  -

    and would effectively send *all* files to the backend without further processing.

    Lastly, you could have the following entry:

       application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter

    You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that +could be useful: +

    +   */*           application/vnd.cups-raw  0  -
+

    +and would effectively send *all* files to the backend without further processing. +

    +Lastly, you could have the following entry: +

    +   application/vnd.cups-postscript  application/vnd.cups-raw  0  my_PJL_stripping_filter
+

    +You will need to write a "my_PJL_stripping_filter" (could be a shellscript) that parses the PostScript and removes the unwanted PJL. This would need to conform to CUPS filter design (mainly, receive and pass the parameters printername, job-id, username, jobtitle, copies, print options and possibly the filename). It would -be installed as world executable into "/usr/lib/cups/filters/" and will be called -by CUPS if it encounters a MIME type "application/vnd.cups-postscript".

    CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue -"on hold". It will only be printed upon manual release by the printer operator. -This is a requirement in many "central reproduction departments", where a few +be installed as world executable into "/usr/lib/cups/filters/" and will be called +by CUPS if it encounters a MIME type "application/vnd.cups-postscript". +

    +CUPS can handle "-o job-hold-until=indefinite". This keeps the job in the queue +"on hold". It will only be printed upon manual release by the printer operator. +This is a requirement in many "central reproduction departments", where a few operators manage the jobs of hundreds of users on some big machine, where no user is allowed to have direct access. (The operators often need to load the proper paper type before running the 10.000 page job requested by marketing -for the mailing, etc.).

    CUPS as a network PostScript RIP

    +This is the configuration where CUPS drivers are working on server, and where the +Adobe PostScript driver with CUPS-PPDs is downloaded to clients. +

    +CUPS is perfectly able to use PPD files (PostScript Printer Descriptions). PPDs can control all print device options. They are usually provided by the manufacturer -- if you own a PostSript printer, that is. PPD files are always a component of PostScript printer drivers on MS Windows or Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate PostScript, PCL or PJL commands for the target printer. Printer driver GUI dialogs translate these -options "on-the-fly" into buttons and drop-down lists for the user to -select.

    CUPS can load, without any conversions, the PPD file from +options "on-the-fly" into buttons and drop-down lists for the user to +select. +

    +CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver and handle the options. There is a web browser interface to the print options (select -http://localhost:631/printers/ and click on one "Configure Printer" button -to see it), a commandline interface (see man lpoptions or -try if you have lphelp on your system) plus some different GUI frontends on Linux +http://localhost:631/printers/ and click on one "Configure Printer" button +to see it), a commandline interface (see man lpoptions or +try if you have lphelp on your system) plus some different GUI frontends on Linux UNIX, which can present PPD options to the users. PPD options are normally meant to become evaluated by the PostScript RIP on the real PostScript -printer.

    CUPS doesn't stop at "real" PostScript printers in its +printer. +

    +CUPS doesn't stop at "real" PostScript printers in its usage of PPDs. The CUPS developers have extended the PPD concept, to also describe available device and driver options for non-PostScript printers -through CUPS-PPDs.

    This is logical, as CUPS includes a fully featured +through CUPS-PPDs. +

    +This is logical, as CUPS includes a fully featured PostScript interpreter (RIP). This RIP is based on Ghostscript. It can process all received PostScript (and additionally many other file formats) from clients. All CUPS-PPDs geared to non-PostScript printers contain an -additional line, starting with the keyword *cupsFilter. +additional line, starting with the keyword *cupsFilter. This line tells the CUPS print system which printer-specific filter to use for the interpretation of the accompanying PostScript. Thus CUPS lets all its printers appear as PostScript devices to its clients, because it can act as a PostScript RIP for those printers, processing the received PostScript code -into a proper raster print format.

    CUPS-PPDs can also be used on Windows-Clients, on top of a -PostScript driver (recommended is the Adobe one).

    This feature enables CUPS to do a few tricks no other -spooler can do:

    • act as a networked PostScript RIP (Raster Image Processor), handling - printfiles from all client platforms in a uniform way;

    • act as a central accounting and billing server, as all files are passed - through the pstops Filter and are therefor logged in - the CUPS page_log. - NOTE: this - can not happen with "raw" print jobs, which always remain unfiltered - per definition;

    • enable clients to consolidate on a single PostScript driver, even for - many different target printers.

    14.5. Windows Terminal Servers (WTS) as CUPS clients

    This setup may be of special interest to people +into a proper raster print format. +

    +CUPS-PPDs can also be used on Windows-Clients, on top of a +PostScript driver (recommended is the Adobe one). +

    +This feature enables CUPS to do a few tricks no other +spooler can do: +

    • act as a networked PostScript RIP (Raster Image Processor), handling + printfiles from all client platforms in a uniform way;

    • act as a central accounting and billing server, as all files are passed + through the pstops Filter and are therefor logged in + the CUPS page_log. - NOTE: this + can not happen with "raw" print jobs, which always remain unfiltered + per definition;

    • enable clients to consolidate on a single PostScript driver, even for + many different target printers.

    Windows Terminal Servers (WTS) as CUPS clients

    +This setup may be of special interest to people experiencing major problems in WTS environments. WTS need often a multitude of non-PostScript drivers installed to run their clients' variety of different printer models. This often imposes the price of much increased @@ -9654,40 +3872,22 @@ their WTS to one generic PCL- and one PostScript driver. This however restricts the clients in the amount of printer options available for them -- often they can't get out more then simplex prints from one standard paper tray, while their devices could do much better, if driven by a different -driver!

    Using an Adobe PostScript driver, enabled with a CUPS-PPD, +driver! +

    +Using an Adobe PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these shortcomings. The PostScript driver is not known to cause major stability problems on WTS (even if used with many different PPDs). The clients will be able to (again) chose paper trays, duplex printing and other settings. However, there is a certain price for this too: a CUPS server acting as a PostScript RIP for its clients -requires more CPU and RAM than just to act as a "raw spooling" device. Plus, +requires more CPU and RAM than just to act as a "raw spooling" device. Plus, this setup is not yet widely tested, although the first feedbacks look very -promising...

    14.6. Setting up CUPS for driver download

    The cupsadsmb utility (shipped with all current +promising... +

    Setting up CUPS for driver download

    +The cupsadsmb utility (shipped with all current CUPS versions) makes the sharing of any (or all) installed CUPS printers very -easy. Prior to using it, you need the following settings in smb.conf:

    [global]
+easy. Prior to using it, you need the following settings in smb.conf:
+
    [global]
 		 load printers = yes
 		 printing = cups
 		 printcap name = cups
@@ -9709,25 +3909,15 @@ CLASS="PROGRAMLISTING"
 		 guest ok = no
 		 read only = yes
 		 write list = root
-	
    For licensing reasons the necessary files of the Adobe
+

    +For licensing reasons the necessary files of the Adobe Postscript driver can not be distributed with either Samba or CUPS. You need to download them yourself from the Adobe website. Once extracted, create a -drivers directory in the CUPS data directory (usually -/usr/share/cups/). Copy the Adobe files using -UPPERCASE filenames, to this directory as follows:

    		ADFONTS.MFM
+drivers directory in the CUPS data directory (usually
+/usr/share/cups/). Copy the Adobe files using
+UPPERCASE filenames, to this directory as follows:
+
    +		ADFONTS.MFM
 		ADOBEPS4.DRV
 		ADOBEPS4.HLP
 		ADOBEPS5.DLL
@@ -9735,200 +3925,84 @@ CLASS="PROGRAMLISTING"
 		ADOBEPSU.HLP
 		DEFPRTR2.PPD
 		ICONLIB.DLL
-	
    Users of the ESP Print Pro software are able to install
-their "Samba Drivers" package for this purpose with no problem.

    14.7. Sources of CUPS drivers / PPDs

    On the internet you can find now many thousand CUPS-PPD +

    +Users of the ESP Print Pro software are able to install +their "Samba Drivers" package for this purpose with no problem. +

    Sources of CUPS drivers / PPDs

    +On the internet you can find now many thousand CUPS-PPD files (with their companion filters), in many national languages, -supporting more than 1.000 non-PostScript models.

    +NOTE: the cupsomatic trick from Linuxprinting.org is working different from the other drivers. While the other drivers take the generic CUPS raster (produced by CUPS' own pstoraster PostScript RIP) as -their input, cupsomatic "kidnaps" the PostScript inside CUPS, before +their input, cupsomatic "kidnaps" the PostScript inside CUPS, before RIP-ping, deviates it to an external Ghostscript installation (which now becomes the RIP) and gives it back to a CUPS backend once Ghostscript is finished. -- CUPS versions from 1.1.15 and later will provide their pstoraster PostScript RIP function again inside a system-wide Ghostscript -installation rather than in "their own" pstoraster filter. (This +installation rather than in "their own" pstoraster filter. (This CUPS-enabling Ghostscript version may be installed either as a patch to GNU or AFPL Ghostscript, or as a complete ESP Ghostscript package). However, this will not change the cupsomatic approach of guiding the printjob along a different path through the filtering system than the standard CUPS -way...

    Once you installed a printer inside CUPS with one of the +way... +

    +Once you installed a printer inside CUPS with one of the recommended methods (the lpadmin command, the web browser interface or one of -the available GUI wizards), you can use cupsaddsmb to share the -printer via Samba. cupsaddsmb prepares the driver files for +the available GUI wizards), you can use cupsaddsmb to share the +printer via Samba. cupsaddsmb prepares the driver files for comfortable client download and installation upon their first contact with -this printer share.

    14.7.1. cupsaddsmb

    The cupsaddsmb command copies the needed files +this printer share. +

    cupsaddsmb

    +The cupsaddsmb command copies the needed files for convenient Windows client installations from the previously prepared CUPS data directory to your [print$] share. Additionally, the PPD -associated with this printer is copied from /etc/cups/ppd/ to -[print$].

    root#  cupsaddsmb -U root infotec_IS2027
-Password for root required to access localhost via SAMBA: [type in password 'secret']

    To share all printers and drivers, use the -a -parameter instead of a printer name.

    Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

    Probably you want to see what's going on. Use the --v parameter to get a more verbose output:

    Note: The following line shave been wrapped so that information is not lost.
+associated with this printer is copied from /etc/cups/ppd/ to
+[print$].
+
    +root#  cupsaddsmb -U root infotec_IS2027
+Password for root required to access localhost via
+SAMBA: [type in password 'secret']
+
    
+To share all printers and drivers, use the -a
+parameter instead of a printer name.
+
    
+Probably you want to see what's going on. Use the
+-v parameter to get a more verbose output:
+
    
+Probably you want to see what's going on. Use the
+-v parameter to get a more verbose output:
+
    +Note: The following line shave been wrapped so that information is not lost.
  
-root#  cupsaddsmb -v -U root infotec_IS2027
+root#  cupsaddsmb -v -U root infotec_IS2027
     Password for root required to access localhost via SAMBA:
     Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir W32X86;put
-       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put /usr/share/cups/drivers/
+       /var/spool/cups/tmp/3cd1cc66376c0 W32X86/infotec_IS2027.PPD;put
+       /usr/share/cups/drivers/
        ADOBEPS5.DLL W32X86/ADOBEPS5.DLL;put /usr/share/cups/drivers/ADOBEPSU.DLLr
        W32X86/ADOBEPSU.DLL;put /usr/share/cups/drivers/ADOBEPSU.HLP W32X86/ADOBEPSU.HLP'
     added interface ip=10.160.16.45 bcast=10.160.31.255 nmask=255.255.240.0
@@ -9936,14 +4010,14 @@ CLASS="PROMPT"
     added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
     Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
     NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \W32X86/infotec_IS2027.PPD (17394.6 kb/s)
-      (average 17395.2 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as \W32X86/ADOBEPS5.DLL (10877.4 kb/s)
-      (average 11343.0 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as \W32X86/ADOBEPSU.DLL (5095.2 kb/s)
-      (average 9260.4 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as \W32X86/ADOBEPSU.HLP (8828.7 kb/s)
-      (average 9247.1 kb/s)
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as
+      \W32X86/infotec_IS2027.PPD (17394.6 kb/s) (average 17395.2 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS5.DLL as
+      \W32X86/ADOBEPS5.DLL (10877.4 kb/s) (average 11343.0 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.DLL as
+      \W32X86/ADOBEPSU.DLL (5095.2 kb/s) (average 9260.4 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPSU.HLP as
+      \W32X86/ADOBEPSU.HLP (8828.7 kb/s) (average 9247.1 kb/s)
 
     Running command: smbclient //localhost/print\$ -N -U'root%secret' -c 'mkdir WIN40;put
       /var/spool/cups/tmp/3cd1cc66376c0 WIN40/infotec_IS2027.PPD;put
@@ -9958,32 +4032,37 @@ CLASS="PROMPT"
     added interface ip=172.16.200.1 bcast=172.16.200.255 nmask=255.255.255.0
     Domain=[TUX-NET] OS=[Unix] Server=[Samba 2.2.3a.200204262025cvs]
     NT_STATUS_OBJECT_NAME_COLLISION making remote directory \WIN40
-    putting file /var/spool/cups/tmp/3cd1cc66376c0 as \WIN40/infotec_IS2027.PPD (26091.5 kb/s)
-      (average 26092.8 kb/s)
-    putting file /usr/share/cups/drivers/ADFONTS.MFM as \WIN40/ADFONTS.MFM (11241.6 kb/s)
-      (average 11812.9 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \WIN40/ADOBEPS4.DRV (16640.6 kb/s)
-      (average 14679.3 kb/s)
-    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \WIN40/ADOBEPS4.HLP (11285.6 kb/s)
-      (average 14281.5 kb/s)
-    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \WIN40/DEFPRTR2.PPD (823.5 kb/s)
-      (average 12944.0 kb/s)
-    putting file /usr/share/cups/drivers/ICONLIB.DLL as \WIN40/ICONLIB.DLL (19226.2 kb/s)
-      (average 13169.7 kb/s)
-    putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL (18666.1 kb/s)
-      (average 13266.7 kb/s)
+    putting file /var/spool/cups/tmp/3cd1cc66376c0 as
+      \WIN40/infotec_IS2027.PPD (26091.5 kb/s) (average 26092.8 kb/s)
+    putting file /usr/share/cups/drivers/ADFONTS.MFM as
+      \WIN40/ADFONTS.MFM (11241.6 kb/s) (average 11812.9 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.DRV as
+      \WIN40/ADOBEPS4.DRV (16640.6 kb/s) (average 14679.3 kb/s)
+    putting file /usr/share/cups/drivers/ADOBEPS4.HLP as
+      \WIN40/ADOBEPS4.HLP (11285.6 kb/s) (average 14281.5 kb/s)
+    putting file /usr/share/cups/drivers/DEFPRTR2.PPD as
+      \WIN40/DEFPRTR2.PPD (823.5 kb/s) (average 12944.0 kb/s)
+    putting file /usr/share/cups/drivers/ICONLIB.DLL as
+      \WIN40/ICONLIB.DLL (19226.2 kb/s) (average 13169.7 kb/s)
+    putting file /usr/share/cups/drivers/PSMON.DLL as
+      \WIN40/PSMON.DLL (18666.1 kb/s) (average 13266.7 kb/s)
 
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows NT x86"
-       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:ADOBEPSU.HLP:NULL:RAW:NULL"'
-    cmd = adddriver "Windows NT x86" "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
-       ADOBEPSU.HLP:NULL:RAW:NULL"
+    Running command: rpcclient localhost -N -U'root%secret'
+       -c 'adddriver "Windows NT x86"
+       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
+		ADOBEPSU.HLP:NULL:RAW:NULL"'
+    cmd = adddriver "Windows NT x86"
+       "infotec_IS2027:ADOBEPS5.DLL:infotec_IS2027.PPD:ADOBEPSU.DLL:
+       ADOBEPSU.HLP:NULL:RAW:NULL"
     Printer Driver infotec_IS2027 successfully installed.
 
-    Running command: rpcclient localhost -N -U'root%secret' -c 'adddriver "Windows 4.0"
-       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
-       ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
-       ADOBEPS4.HLP:PSMON.DLL:RAW:ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+    Running command: rpcclient localhost -N -U'root%secret'
+       -c 'adddriver "Windows 4.0"
+       "infotec_IS2027:ADOBEPS4.DRV:infotec_IS2027.PPD:NULL:
+		ADOBEPS4.HLP:PSMON.DLL:RAW: ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+    cmd = adddriver "Windows 4.0" "infotec_IS2027:ADOBEPS4.DRV:
+		infotec_IS2027.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:
+		ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
     Printer Driver infotec_IS2027 successfully installed.
 
     Running command: rpcclient localhost -N -U'root%secret'
@@ -9991,84 +4070,45 @@ CLASS="PROMPT"
     cmd = setdriver infotec_IS2027 infotec_IS2027
     Succesfully set infotec_IS2027 to driver infotec_IS2027.
 
-    root# 
    If you look closely, you'll discover your root password was transfered unencrypted over
+    root# 
+

    +If you look closely, you'll discover your root password was transfered unencrypted over the wire, so beware! Also, if you look further her, you'll discover error messages like -NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because -the directories WIN40 and W32X86 already +NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because +the directories WIN40 and W32X86 already existed in the [print$] driver download share (from a previous driver -installation). They are harmless here.

    Now your printer is prepared for the clients to use. From -a client, browse to the CUPS/Samba server, open the "Printers" -share, right-click on this printer and select "Install..." or -"Connect..." (depending on the Windows version you use). Now their -should be a new printer in your client's local "Printers" folder, -named (in my case) "infotec_IS2027 on kdebitshop"

    NOTE: -cupsaddsmb will only reliably work i +installation). They are harmless here. +

    +Now your printer is prepared for the clients to use. From +a client, browse to the CUPS/Samba server, open the "Printers" +share, right-click on this printer and select "Install..." or +"Connect..." (depending on the Windows version you use). Now their +should be a new printer in your client's local "Printers" folder, +named (in my case) "infotec_IS2027 on kdebitshop" +

    +NOTE: +cupsaddsmb will only reliably work i with CUPS version 1.1.15 or higher and Samba from 2.2.4. If it doesn't work, or if the automatic printer driver download to the clients doesn't succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on clients and then point the client's printer queue to the Samba printer share for connection, should you desire to use the CUPS networked -PostScript RIP functions.

    14.8. The CUPS Filter Chains

    The following diagrams reveal how CUPS handles print jobs.

    #########################################################################
+PostScript RIP functions.
+

    The CUPS Filter Chains

    +The following diagrams reveal how CUPS handles print jobs. +

    +#########################################################################
 #
 # CUPS in and of itself has this (general) filter chain (CAPITAL
 # letters are FILE-FORMATS or MIME types, other are filters (this is
 # true for pre-1.1.15 of pre-4.3 versions of CUPS and ESP PrintPro):
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#     somethingtops
+#     somethingtops
 #      |
 #      |
 #      V
@@ -10086,18 +4126,15 @@ CLASS="REPLACEABLE"
 #      V
 #     pstoraster   # as shipped with CUPS, independent from any Ghostscipt
 #      |           # installation on the system
-#      |  (= "postscipt interpreter")
+#      |  (= "postscipt interpreter")
 #      |
 #      V
 # APPLICATION/VND.CUPS-RASTER
 #      |
 #      |
 #      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
+#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
 #      |
 #      V
 # SOMETHING-DEVICE-SPECIFIC
@@ -10107,37 +4144,24 @@ CLASS="REPLACEABLE"
 #     backend
 #
 #
-# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
-# CUPS, and also a somewhat improved "pstoraster" filter.
+# ESP PrintPro has some enhanced "rastertosomething" filters as compared to
+# CUPS, and also a somewhat improved "pstoraster" filter.
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-#########################################################################
    #########################################################################
+#########################################################################
+
    +#########################################################################
 #
-# This is how "cupsomatic" comes into play:
+# This is how "cupsomatic" comes into play:
 # =========================================
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#    somethingtops
+#    somethingtops
 #      |
 #      |
 #      V
@@ -10154,42 +4178,33 @@ CLASS="REPLACEABLE"
 #      |                                          V
 #      V                                         cupsomatic
 #    pstoraster                                  (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |  (= "postscipt interpreter")            Ghostscript commandline
 #      |                                         to let the file be
 #      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
 #      |                                         call...)
 #      |                                          |
 #      V                                          |
-#    rastertosomething                          V
-#      |    (= "raster driver")     +-------------------------+
+#    rastertosomething                          V
+#      |    (= "raster driver")     +-------------------------+
 #      |                            | Ghostscript at work.... |
 #      V                            |                         |
 # SOMETHING-DEVICE-SPECIFIC         *-------------------------+
 #      |                                          |
 #      |                                          |
 #      V                                          |
-#    backend >------------------------------------+
+#    backend >------------------------------------+
 #      |
 #      |
 #      V
 #    THE PRINTER
 #
 #
-# Note, that cupsomatic "kidnaps" the printfile after the
-# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
+# Note, that cupsomatic "kidnaps" the printfile after the
+# "APPLICATION/VND.CUPS-POSTSCRPT" stage and deviates it through
 # the CUPS-external, systemwide Ghostscript installation, bypassing the
-# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
-# "rastertosomething", and hands the rasterized file directly to the CUPS
+# "pstoraster" filter (therefor also bypassing the CUPS-raster-drivers
+# "rastertosomething", and hands the rasterized file directly to the CUPS
 # backend...
 #
 # cupsomatic is not made by the CUPS developers. It is an independent
@@ -10197,30 +4212,20 @@ CLASS="REPLACEABLE"
 # Linuxprinting.org. (see also http://www.cups.org/cups-help.html)
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-#########################################################################
    #########################################################################
+#########################################################################
+
    +#########################################################################
 #
 # And this is how it works for ESP PrintPro from 4.3:
 # ===================================================
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#     somethingtops
+#     somethingtops
 #      |
 #      |
 #      V
@@ -10237,18 +4242,15 @@ CLASS="REPLACEABLE"
 #      |
 #      V
 #     gsrip
-#      |  (= "postscipt interpreter")
+#      |  (= "postscipt interpreter")
 #      |
 #      V
 # APPLICATION/VND.CUPS-RASTER
 #      |
 #      |
 #      V
-#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
-#      |   (= "raster driver")
+#     rastertosomething  (f.e. Gimp-Print filters may be plugged in here)
+#      |   (= "raster driver")
 #      |
 #      V
 # SOMETHING-DEVICE-SPECIFIC
@@ -10258,31 +4260,21 @@ CLASS="REPLACEABLE"
 #     backend
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-#########################################################################
    #########################################################################
+#########################################################################
+
    +#########################################################################
 #
-# This is how "cupsomatic" would come into play with ESP PrintPro:
+# This is how "cupsomatic" would come into play with ESP PrintPro:
 # ================================================================
 #
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#    somethingtops
+#    somethingtops
 #      |
 #      |
 #      V
@@ -10299,58 +4291,42 @@ CLASS="REPLACEABLE"
 #      |                                          V
 #      V                                         cupsomatic
 #    gsrip                                       (constructs complicated
-#      |  (= "postscipt interpreter")            Ghostscript commandline
+#      |  (= "postscipt interpreter")            Ghostscript commandline
 #      |                                         to let the file be
 #      V                                         processed by a
-# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
+# APPLICATION/VND.CUPS-RASTER                    "-sDEVICE=s.th."
 #      |                                         call...)
 #      |                                          |
 #      V                                          |
-#    rastertosomething                          V
-#      |   (= "raster driver")      +-------------------------+
+#    rastertosomething                          V
+#      |   (= "raster driver")      +-------------------------+
 #      |                            | Ghostscript at work.... |
 #      V                            |                         |
 # SOMETHING-DEVICE-SPECIFIC         *-------------------------+
 #      |                                          |
 #      |                                          |
 #      V                                          |
-#    backend >------------------------------------+
+#    backend >------------------------------------+
 #      |
 #      |
 #      V
 #    THE PRINTER
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-#########################################################################
    #########################################################################
+#########################################################################
+
    +#########################################################################
 #
 # And this is how it works for CUPS from 1.1.15:
 # ==============================================
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#     somethingtops
+#     somethingtops
 #      |
 #      |
 #      V
@@ -10368,22 +4344,19 @@ CLASS="REPLACEABLE"
 #                  | Ghostscript                                     |
 #                  | at work...                                      |
 #                  | (with                                           |
-#                  | "-sDEVICE=cups")                                |
+#                  | "-sDEVICE=cups")                                |
 #                  |                                                 |
-#                  |         (= "postscipt interpreter")             |
+#                  |         (= "postscipt interpreter")             |
 #                  |                                                 |
 #                  +------------------v------------------------------+
 #                                     |
 #                                     |
-# APPLICATION/VND.CUPS-RASTER >-------+
+# APPLICATION/VND.CUPS-RASTER >-------+
 #      |
 #      |
 #      V
-#     rastertosomething
-#      |   (= "raster driver")
+#     rastertosomething
+#      |   (= "raster driver")
 #      |
 #      V
 # SOMETHING-DEVICE-SPECIFIC
@@ -10393,46 +4366,33 @@ CLASS="REPLACEABLE"
 #     backend
 #
 #
-# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
+# NOTE: since version 1.1.15 CUPS "outsourced" the pstoraster process to
 #       Ghostscript. GNU Ghostscript needs to be patched to handle the
 #       CUPS requirement; ESP Ghostscript has this builtin. In any case,
-#       "gs -h" needs to show up a "cups" device. pstoraster is now a
-#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
-#       the job. It will output "application/vnd.cup-raster", which will
-#       be finally processed by a CUPS raster driver "rastertosomething"
-#       Note the difference to "cupsomatic", which will *not* output
+#       "gs -h" needs to show up a "cups" device. pstoraster is now a
+#       calling an appropriate "gs -sDEVICE=cups..." commandline to do
+#       the job. It will output "application/vnd.cup-raster", which will
+#       be finally processed by a CUPS raster driver "rastertosomething"
+#       Note the difference to "cupsomatic", which will *not* output
 #       CUPS-raster, but a final version of the printfile, ready to be
-#       sent to the printer. cupsomatic also doesn't use the "cups"
+#       sent to the printer. cupsomatic also doesn't use the "cups"
 #       devicemode in Ghostscript, but one of the classical devicemodes....
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-#########################################################################
    #########################################################################
+#########################################################################
+
    +#########################################################################
 #
 # And this is how it works for CUPS from 1.1.15, with cupsomatic included:
 # ========================================================================
 #
-# SOMETHNG-FILEFORMAT
+# SOMETHNG-FILEFORMAT
 #      |
 #      |
 #      V
-#     somethingtops
+#     somethingtops
 #      |
 #      |
 #      V
@@ -10448,32 +4408,26 @@ CLASS="REPLACEABLE"
 #                                     |
 #                  +------------------v------------------------------+
 #                  | Ghostscript        . Ghostscript at work....    |
-#                  | at work...         . (with "-sDEVICE=           |
-#                  | (with              .            s.th."        |
-#                  | "-sDEVICE=cups")   .                            |
+#                  | at work...         . (with "-sDEVICE=           |
+#                  | (with              .            s.th."        |
+#                  | "-sDEVICE=cups")   .                            |
 #                  |                    .                            |
 #                  | (CUPS standard)    .      (cupsomatic)          |
 #                  |                    .                            |
-#                  |          (= "postscript interpreter")           |
+#                  |          (= "postscript interpreter")           |
 #                  |                    .                            |
 #                  +------------------v--------------v---------------+
 #                                     |              |
 #                                     |              |
-# APPLICATION/VND.CUPS-RASTER >-------+              |
+# APPLICATION/VND.CUPS-RASTER >-------+              |
 #      |                                             |
 #      |                                             |
 #      V                                             |
-#     rastertosomething                            |
-#      |   (= "raster driver")                       |
+#     rastertosomething                            |
+#      |   (= "raster driver")                       |
 #      |                                             |
 #      V                                             |
-# SOMETHING-DEVICE-SPECIFIC >------------------------+
+# SOMETHING-DEVICE-SPECIFIC >------------------------+
 #      |
 #      |
 #      V
@@ -10481,1375 +4435,529 @@ CLASS="REPLACEABLE"
 #
 #
 # NOTE: Gimp-Print and some other 3rd-Party-Filters (like TurboPrint) to
-#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
+#       CUPS and ESP PrintPro plug-in where rastertosomething is noted.
 #
-##########################################################################

    14.9. CUPS Print Drivers and Devices

    CUPS ships with good support for HP LaserJet type printers. You can install +########################################################################## +

    CUPS Print Drivers and Devices

    +CUPS ships with good support for HP LaserJet type printers. You can install the driver as follows: -

    • lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd -

    +

    • + lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd +

    -(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository +(The "-m" switch will retrieve the "laserjet.ppd" from the standard repository for not-yet-installed-PPDs, which CUPS typically stores in -/usr/share/cups/model. Alternatively, you may use -"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd").

    14.9.1. Further printing steps

    Always also consult the database on linuxprinting.org for all recommendations -about which driver is best used for each printer:

    http://www.linuxprinting.org/printer_list.cgi

    There select your model and click on "Show". You'll arrive at a page listing +/usr/share/cups/model. Alternatively, you may use +"-P /absolute/filesystem/path/to/where/there/is/PPD/your.ppd"). +

    Further printing steps

    +Always also consult the database on linuxprinting.org for all recommendations +about which driver is best used for each printer: +

    http://www.linuxprinting.org/printer_list.cgi

    +There select your model and click on "Show". You'll arrive at a page listing all drivers working with your model. There will always be *one* -recommended one. Try this one first. In your case -("HP LaserJet 4 Plus"), you'll arrive here:

    http://www.linuxprinting.org/show_printer.cgi?recnum=75104

    The recommended driver is "ljet4". It has a link to the page for the ljet4 -driver too:

    http://www.linuxprinting.org/show_driver.cgi?driver=ljet4

    On the driver's page, you'll find important and detailed info about how to use +recommended one. Try this one first. In your case +("HP LaserJet 4 Plus"), you'll arrive here: +

    http://www.linuxprinting.org/show_printer.cgi?recnum=75104

    +The recommended driver is "ljet4". It has a link to the page for the ljet4 +driver too: +

    http://www.linuxprinting.org/show_driver.cgi?driver=ljet4

    +On the driver's page, you'll find important and detailed info about how to use that driver within the various available spoolers. You can generate a PPD for CUPS. The PPD contains all the info about how to use your model and the driver; this is, once installed, working transparently for the user -- you'll only need to choose resolution, paper size etc. from the web-based menu or from -the print dialog GUI or from the commandline...

    On the driver's page, choose to use the "PPD-O-Matic" online PPD generator -program. Select your model and click "Generate PPD file". When you safe the -appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt -line endings and tabs), but use "Save as..." in your browser's menu. Save it -at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    Then install the printer:

        "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
-          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"

    Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need -a special "CUPS filter" named "cupsomatic". Get the latest version of -"cupsomatic" from:

    http://www.linuxprinting.org/cupsomatic

    This needs to be copied to /usr/lib/cups/filter/cupsomatic +the print dialog GUI or from the commandline... +

    +On the driver's page, choose to use the "PPD-O-Matic" online PPD generator +program. Select your model and click "Generate PPD file". When you safe the +appearing ASCII text file, don't use "cut'n'past" (as it could possiblly corrupt +line endings and tabs), but use "Save as..." in your browser's menu. Save it +at "/some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd" +

    +Then install the printer: +

    +    "lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \
+          -P /some/path/on/your/filesystem/somewhere/my-name-for-my-printer.ppd"
+

    +Note, that for all the "Foomatic-PPDs" from Linuxprinting.org, you also need +a special "CUPS filter" named "cupsomatic". Get the latest version of +"cupsomatic" from: +

    http://www.linuxprinting.org/cupsomatic

    +This needs to be copied to /usr/lib/cups/filter/cupsomatic and be made world executable. This filter is needed to read and act upon the specially encoded Foomatic comments, embedded in the printfile, which in turn are used to construct (transparently for you, the user) the complicated -ghostscript command line needed for your printer/driver combo.

    You can have a look at all the options for the Ghostscript commandline supported -by your printer and the ljet4 driver by going to the section "Execution details", -selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". -This will bring up this web page:

    http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details

    The ingenious thing is that the database is kept current. If there +ghostscript command line needed for your printer/driver combo. +

    +You can have a look at all the options for the Ghostscript commandline supported +by your printer and the ljet4 driver by going to the section "Execution details", +selecting your model (Laserjet 4 Plus) and clicking on "Show execution details". +This will bring up this web page: +

    http://www.linuxprinting.org/execution.cgi?driver=ljet4&printer=75104&.submit=Show+execution+details

    +The ingenious thing is that the database is kept current. If there is a bug fix and an improvement somewhere in the database, you will always get the most current and stable and feature-rich driver by following -the steps described above.

    Till Kamppeter from MandrakeSoft is doing an excellent job here that too few +the steps described above. +

    Note

    +Till Kamppeter from MandrakeSoft is doing an excellent job here that too few people are aware of. (So if you use it often, please send him a note showing -your appreciation).

    The latest and greatest improvement now is support for "custom page sizes" -for all those printers which support it.

    "cupsomatic" is documented here:

    http://www.linuxprinting.org/cups-doc.html

    More printing tutorial info may be found here:

    http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/

    Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now -approaching the "all-time high" number of 1.000 for the supported models) +your appreciation).

    +The latest and greatest improvement now is support for "custom page sizes" +for all those printers which support it. +

    +"cupsomatic" is documented here: +

    http://www.linuxprinting.org/cups-doc.html

    +More printing tutorial info may be found here: +

    http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/

    +Note, that *all* the Foomatic drivers listed on Linuxprinting.org (now +approaching the "all-time high" number of 1.000 for the supported models) are using a special filtering chain involving Ghostscript, as described -in this document.

    Summary - You need:

    A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
    The "cupsomatic" filter script (Perl) in /usr/lib/cups/filters/
    Perl to make cupsomatic run
    Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
    Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")

    In the case of the "hpijs" driver, you need a Ghostscript version, which -has "ijs" amongst its supported devices in "gs -h". In the case of -"hpijs+foomatic", a valid ghostscript commandline would be reading like this:

           gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
-             -sIjsServer=hpijsPageSize -dDuplex=Duplex Model        \
-             -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \
-             -sOutputFile=- -

    Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) +in this document. +

    +Summary - You need: +

    +

    A "foomatic+something" PPD is not enough to print with CUPS (but it is *one* important component)
    The "cupsomatic" filter script (Perl) in /usr/lib/cups/filters/
    Perl to make cupsomatic run
    Ghostscript (because it is called and controlled by the PPD/cupsomatic combo in a way to fit your printermodel/driver combo.
    Ghostscript *must*, depending on the driver/model, contain support for a certain "device" (as shown by "gs -h")

    +

    +In the case of the "hpijs" driver, you need a Ghostscript version, which +has "ijs" amongst its supported devices in "gs -h". In the case of +"hpijs+foomatic", a valid ghostscript commandline would be reading like this: +

    +       gs -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs       \
+             -sIjsServer=hpijsPageSize -dDuplex=Duplex Model        \
+             -rResolution,PS:MediaPosition=InputSlot -dIjsUseOutputFD \
+             -sOutputFile=- -
+

    Note

    +Note, that with CUPS and the "hpijs+foomatic" PPD (plus Perl and cupsomatic) you don't need to remember this. You can choose the available print options -thru a GUI print command (like "glp" from ESP's commercially supported -PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent -"xpp") or the CUPS web interface via human-readable drop-down selection -menus.

    If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software +thru a GUI print command (like "glp" from ESP's commercially supported +PrintPro software, or KDE's "kprinter", or GNOME's "gtklp" or the independent +"xpp") or the CUPS web interface via human-readable drop-down selection +menus. +

    +If you use "ESP Ghostscript" (also under the GPL, provided by Easy Software Products, the makers of CUPS, downloadable from -http://www.cups.org/software.html, +http://www.cups.org/software.html, co-maintained by the developers of linuxprinting.org), you are guaranteed to have in use the most uptodate, bug-fixed, enhanced and stable version of a Free Ghostscript. It contains support for ~300 devices, whereas plain vanilla -GNU Ghostscript 7.05 only has ~200.

    If you print only one CUPS test page, from the web interface and when you try to +GNU Ghostscript 7.05 only has ~200. +

    +If you print only one CUPS test page, from the web interface and when you try to print a windows test page, it acts like the job was never sent: -

    Can you print "standard" jobs from the CUPS machine?
    Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
    Most important: What kind of printer driver are you using on the Windows clients?

    +

    Can you print "standard" jobs from the CUPS machine?
    Are the jobs from Windows visible in the Web interface on CUPS (http://localhost:631/)?
    Most important: What kind of printer driver are you using on the Windows clients?

    -You can try to get a more detailed debugging info by setting "LogLevel debug" in -/etc/cups/cupsd.conf, re-start cupsd and investigate /var/log/cups/error_log -for the whereabouts of your Windows-originating printjobs:

    what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
    are there "filter" available for this MIME type?
    are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?

    14.10. Limiting the number of pages users can print

    The feature you want is dependent on the real print subsystem you're using. +You can try to get a more detailed debugging info by setting "LogLevel debug" in +/etc/cups/cupsd.conf, re-start cupsd and investigate /var/log/cups/error_log +for the whereabouts of your Windows-originating printjobs: +

    what does the "auto-typing" line say? which is the "MIME type" CUPS thinks is arriving from the Windows clients?
    are there "filter" available for this MIME type?
    are there "filter rules" defined in "/etc/cups/mime.convs" for this MIME type?

    Limiting the number of pages users can print

    +The feature you want is dependent on the real print subsystem you're using. Samba's part is always to receive the job files from the clients (filtered -*or* unfiltered) and hand it over to this printing subsystem.

    Of course one could "hack" things with one's own scripts.

    But there is CUPS (Common Unix Printing System). CUPS supports "quotas". +*or* unfiltered) and hand it over to this printing subsystem. +

    +Of course one could "hack" things with one's own scripts. +

    +But there is CUPS (Common Unix Printing System). CUPS supports "quotas". Quotas can be based on sizes of jobs or on the number of pages or both, -and are spanning any time period you want.

    This is an example command how root would set a print quota in CUPS, -assuming an existing printer named "quotaprinter":

      lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
-       -o job-page-limit=100

    This would limit every single user to print 100 pages or 1024 KB of -data (whichever comes first) within the last 604.800 seconds ( = 1 week).

    For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, -otherwise it uses a "dummy" count of "1". Some printfiles don't pass it +and are spanning any time period you want. +

    +This is an example command how root would set a print quota in CUPS, +assuming an existing printer named "quotaprinter": +

    +  lpadmin -p quotaprinter -o job-quota-period=604800 -o job-k-limit=1024 \
+       -o job-page-limit=100
+

    +This would limit every single user to print 100 pages or 1024 KB of +data (whichever comes first) within the last 604.800 seconds ( = 1 week). +

    +For CUPS to count correctly, the printfile needs to pass the CUPS "pstops" filter, +otherwise it uses a "dummy" count of "1". Some printfiles don't pass it (eg: image files) but then those are mostly 1 page jobs anyway. This also means, proprietary drivers for the target printer running on the client computers and -CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not -filtering them), will be counted as "1-pagers" too!

    You need to send PostScript from the clients (i.e. run a PostScript driver there) +CUPS/Samba then spooling these files as "raw" (i.e. leaving them untouched, not +filtering them), will be counted as "1-pagers" too! +

    +You need to send PostScript from the clients (i.e. run a PostScript driver there) for having the chance to get accounting done. If the printer is a non-PostScript model, you need to let CUPS do the job to convert the file to a print-ready format for the -target printer. This will be working for currently ~1.000 different printer models, see

         http://www.linuxprinting.org/printer_list.cgi

    Before CUPS-1.1.16 your only option was to use the Adobe PostScript +target printer. This will be working for currently ~1.000 different printer models, see +

    +     http://www.linuxprinting.org/printer_list.cgi
+

    +Before CUPS-1.1.16 your only option was to use the Adobe PostScript Driver on the Windows clients. The output of this driver was not always -passed thru the "pstops" filter on the CUPS/Samba side, and therefor was +passed thru the "pstops" filter on the CUPS/Samba side, and therefor was not counted correctly (the reason is that it often --- depending on the -"PPD" being used --- did write a "PJL"-header in front of the real +"PPD" being used --- did write a "PJL"-header in front of the real PostScript which made CUPS to skip the pstops and go directy to -the "pstoraster" stage).

    From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver -for Windows NT/2K/XP clients" (it is tagged in the download area of -http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). -It is *not* working for Win9x/ME clients. But it:

    it guarantees to not write an PJL-header
    it guarantees to still read and support all PJL-options named in the driver PPD with its own means
    it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
    it guarantees to page-count correctly the printfile

    You can read more about the setup of this combination in the -manpage for "cupsaddsmb" (only present with CUPS installed, only -current with CUPS 1.1.16).

    These are the items CUPS logs in the "page_log" for every single *page* of a job:

    Printer name
    User name
    Job ID
    Time of printing
    the page number
    the number of copies
    a billing info string (optional)

    Here is an extract of my CUPS server's page_log file to illustrate -the format and included items:

    infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing +the "pstoraster" stage). +

    +From CUPS-1.1.16 onward you can use the "CUPS PostScript Driver +for Windows NT/2K/XP clients" (it is tagged in the download area of +http://www.cups.org/ as the "cups-samba-1.1.16.tar.gz" package). +It is *not* working for Win9x/ME clients. But it: +

    it guarantees to not write an PJL-header
    it guarantees to still read and support all PJL-options named in the driver PPD with its own means
    it guarantees the file going thru the "pstops" filter on the CUPS/Samba server
    it guarantees to page-count correctly the printfile

    +You can read more about the setup of this combination in the +manpage for "cupsaddsmb" (only present with CUPS installed, only +current with CUPS 1.1.16). +

    +These are the items CUPS logs in the "page_log" for every single *page* of a job: +

    Printer name
    User name
    Job ID
    Time of printing
    the page number
    the number of copies
    a billing info string (optional)

    +

    +Here is an extract of my CUPS server's page_log file to illustrate +the format and included items: +

    + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 1 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 2 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 3 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 4 2 #marketing infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 5 2 #marketing - infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing

    This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job -printed in 2 copies and billed to "#marketing"...

    What flaws or shortcomings are there?

    the ones named above
    CUPS really counts the job pages being *processsed in software* - (going thru the "RIP") rather than the physical sheets successfully + infotec_IS2027 kurt 40 [22/Nov/2002:13:18:03 +0100] 6 2 #marketing +

    +This was Job ID "40", printed on "infotec_IS2027" by user "kurt", a 6-page job +printed in 2 copies and billed to "#marketing"... +

    +What flaws or shortcomings are there? +

    the ones named above
    + CUPS really counts the job pages being *processsed in software* + (going thru the "RIP") rather than the physical sheets successfully leaving the printing device -- if there is a jam while printing the 5th sheet out of 1000 and the job is aborted by the printer, - the "page count" will still show the figure of 1000 for that job -
    all quotas are the same for all users (no flexibility to give the + the "page count" will still show the figure of 1000 for that job +
    + all quotas are the same for all users (no flexibility to give the boss a higher quota than the clerk) no support for groups -
    no means to read out the current balance or "used-up" number of current quota -
    a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job -
    a user being denied a job because of a filled-up quota doesn't get a meaningful - error message from CUPS other than "client-error-not-possible". -

    But this is the best system out there currently. And there are -huge improvements under development:

    page counting will go into the "backends" (these talk +
    + no means to read out the current balance or "used-up" number of current quota +
    + a user having used up 99 sheets of 100 quota will still be able to send and print a 1.000 sheet job +
    + a user being denied a job because of a filled-up quota doesn't get a meaningful + error message from CUPS other than "client-error-not-possible". +

    +But this is the best system out there currently. And there are +huge improvements under development: +

    page counting will go into the "backends" (these talk directly to the printer and will increase the count in sync with the - actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)
    quotas will be handled more flexibly
    probably there will be support for users to inquire their "accounts" in advance
    probably there will be support for some other tools around this topic

    Other than the current stage of the CUPS development, I don't -know any other ready-to-use tool which you could consider.

    You can download the driver files from -http://www.cups.org/software.html. -It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 -Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to -download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal -the files:

    cups-samba.install - cups-samba.license - cups-samba.readme - cups-samba.remove - cups-samba.ss - -

    These have been packaged with the ESP meta packager software "EPM". The + actual printing process -- a jam at the 5th sheet will lead to a stop in the counting)

    quotas will be handled more flexibly
    probably there will be support for users to inquire their "accounts" in advance
    probably there will be support for some other tools around this topic

    +Other than the current stage of the CUPS development, I don't +know any other ready-to-use tool which you could consider. +

    +You can download the driver files from +http://www.cups.org/software.html. +It is a separate package from the CUPS base software files, tagged as "CUPS 1.1.16 +Windows NT/2k/XP Printer Driver for SAMBA (tar.gz, 192k)". The filename to +download is "cups-samba-1.1.16.tar.gz". Upon untar-/unzip-ping it will reveal +the files: +

    + + cups-samba.install + cups-samba.license + cups-samba.readme + cups-samba.remove + cups-samba.ss + +

    +These have been packaged with the ESP meta packager software "EPM". The *.install and *.remove files are simple shell script, which untars the *.ss (which is nothing else than a tar-archive) and puts its contents -into /usr/share/cups/drivers/. Its contents are 3 files:

    cupsdrvr.dll - cupsui.dll - cups.hlp - -

    Due to a bug one CUPS release puts the cups.hlp -into /usr/share/drivers/ instead of -/usr/share/cups/drivers/. To work around this, copy/move -the file after running the "./cups-samba.install" script manually to the right place:

    cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ - -

    This new CUPS PostScript driver is currently binary-only, but free +into /usr/share/cups/drivers/. Its contents are 3 files: +

    + + cupsdrvr.dll + cupsui.dll + cups.hlp + +

    Caution

    +Due to a bug one CUPS release puts the cups.hlp +into /usr/share/drivers/ instead of +/usr/share/cups/drivers/. To work around this, copy/move +the file after running the "./cups-samba.install" script manually to the right place: +

    + cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/ + +

    Note

    +This new CUPS PostScript driver is currently binary-only, but free no source code is provided (yet). The reason is this: it has been developed with the help of the Microsoft Driver Developer Kit (DDK) and compiled with Microsoft Visual Studio 6. It is not clear to the driver developers if they are allowed to distribute the whole of the source code -as Free Software. However, they will likely release the "diff" in source +as Free Software. However, they will likely release the "diff" in source code under the GPL, so anybody with a license of Visual Studio and a DDK -will be able to compile for him/herself.

    Once you have run the install script (and possibly manually moved the -"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be -put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" +will be able to compile for him/herself. +

    +Once you have run the install script (and possibly manually moved the +"cups.hlp" file to "/usr/share/cups/drivers/"), the driver is ready to be +put into Samba's [print$] share (which often maps to "/etc/samba/drivers/" and contains a subdir tree with WIN40 and W32X86 branches), by running -"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to -put root into the smbpasswd file by running "smbpasswd" should you run +"cupsaddsmb" (see also "man cupsaddsmb" for CUPS 1.1.16). [Don't forget to +put root into the smbpasswd file by running "smbpasswd" should you run this whole procedure for the first time.] Once the driver files are in the [print$] share, they are ready to be downloaded and installed by the -Win NT/2k/XP clients.

    Win 9x/ME clients won't work with this driver. For these you'd +Win NT/2k/XP clients. +

    Note

    + Win 9x/ME clients won't work with this driver. For these you'd still need to use the ADOBE*.* drivers as previously. -

    It is not harming if you've still the ADOBE*.* driver files from - previous installations in the "/usr/share/cups/drivers/" directory. +

    Note

    + It is not harming if you've still the ADOBE*.* driver files from + previous installations in the "/usr/share/cups/drivers/" directory. The new cupsaddsmb (from 1.1.16) will automatically use the - "newest" installed driver (which here then is the CUPS drivers). -

    Should your Win clients have had the old ADOBE*.* files and the + "newest" installed driver (which here then is the CUPS drivers). +

    Note

    + Should your Win clients have had the old ADOBE*.* files and the Adobe PostScript drivers installed, the download and installation of the new CUPS PostScript driver for Windows NT/2k/XP will fail at first. -

    It is not enough to "delete" the printer (as the driver files +

    + It is not enough to "delete" the printer (as the driver files will still be kept by the clients and re-used if you try to re-install the printer). To really get rid of the Adobe driver - files on the clients, open the "Printers" folder (possibly via - "Start --> Settings --> Control Panel --> Printers"), right-click - onto the folder background and select "Server Properties". A - new dialog opens; select the "Drivers" tab; on the list select - the driver you want to delete and click on the "Delete" button. + files on the clients, open the "Printers" folder (possibly via + "Start --> Settings --> Control Panel --> Printers"), right-click + onto the folder background and select "Server Properties". A + new dialog opens; select the "Drivers" tab; on the list select + the driver you want to delete and click on the "Delete" button. (This will only work if there is no single printer left which - uses that particular driver -- you need to "delete" all printers - using this driver in the "Printers" folder first.) -

    Once you have successfully downloaded the CUPS PostScript driver + uses that particular driver -- you need to "delete" all printers + using this driver in the "Printers" folder first.) +

    Note

    + Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all printers to this one - by proceeding as described elsewhere in the "Samba HOWTO - Collection" to change a driver for an existing printer. -

    What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" -as compared to the Adobe drivers?

    • no hassle with the Adobe EULA -

    • no hassle with the question "where do I get the ADOBE*.* driver files from?" -

    • the Adobe drivers (depending on the printer PPD associated with them) + by proceeding as described elsewhere in the "Samba HOWTO + Collection" to change a driver for an existing printer. +

    +What are the benefits with the "CUPS PostScript driver for Windows NT/2k/XP" +as compared to the Adobe drivers? +

    +

    + no hassle with the Adobe EULA +

    + no hassle with the question "where do I get the ADOBE*.* driver files from?" +

    + the Adobe drivers (depending on the printer PPD associated with them) often put a PJL header in front of the core PostScript part of the print - file (thus the file starts with "1B%-12345X" or "escape%-12345X" - instead of "%!PS"). This leads to the CUPS daemon autotyping the + file (thus the file starts with "1B%-12345X" + or "escape%-12345X" + instead of "%!PS"). This leads to the CUPS daemon autotyping the arriving file as a print-ready file, not requiring a pass thru the - "pstops" filter (to speak more technical, it is not regarded as the - generic MIME type "application/postscript", but as the more special - MIME type "application/cups.vnd-postscript"), which therefore also - leads to the page accounting in "/var/log/cups/page_log" not receiving - the exact mumber of pages; instead the dummy page number of "1" is + "pstops" filter (to speak more technical, it is not regarded as the + generic MIME type "application/postscript", but as the more special + MIME type "application/cups.vnd-postscript"), which therefore also + leads to the page accounting in "/var/log/cups/page_log" not receiving + the exact mumber of pages; instead the dummy page number of "1" is logged in a standard setup) -

  • the Adobe driver has more options to "mis-configure" the PostScript - generated by it (like setting it inadvertedly to "Optimize for Speed", - instead of "Optimize for Portability", which could lead to CUPS being +

    • + the Adobe driver has more options to "mis-configure" the PostScript + generated by it (like setting it inadvertedly to "Optimize for Speed", + instead of "Optimize for Portability", which could lead to CUPS being unable to process it) -

  • the CUPS PostScript driver output sent by Windows clients to the CUPS +

    • + the CUPS PostScript driver output sent by Windows clients to the CUPS server will be guaranteed to be auto-typed as generic MIME type - "application/postscript", thusly passing thru the CUPS "pstops" filter + "application/postscript", thusly passing thru the CUPS "pstops" filter and logging the correct number of pages in the page_log for accounting and quota purposes -

  • the CUPS PostScript driver supports the sending of additional print +

    • + the CUPS PostScript driver supports the sending of additional print options by the Win NT/2k/XP clients, such as naming the CUPS standard banner pages (or the custom ones, should they be installed at the time - of driver download), using the CUPS "page-label" option, setting a + of driver download), using the CUPS "page-label" option, setting a job-priority and setting the scheduled time of printing (with the option to support additional useful IPP job attributes in the future). -

  • the CUPS PostScript driver supports the inclusion of the new - "*cupsJobTicket" comments at the beginnig of the PostScript file (which +

    • + the CUPS PostScript driver supports the inclusion of the new + "*cupsJobTicket" comments at the beginnig of the PostScript file (which could be used in the future for all sort of beneficial extensions on the CUPS side, but which will not disturb any other application as those will regard it as a comment and simply ignore it). -

  • the CUPS PostScript driver will be the heart of the fully fledged CUPS +

    • + the CUPS PostScript driver will be the heart of the fully fledged CUPS IPP client for Windows NT/2k/XP to be released soon (probably alongside the first Beta release for CUPS 1.2). -

    14.11. Advanced Postscript Printing from MS Windows

    Let the Windows Clients use a PostScript driver to deliver poistscript to +

    +

    Advanced Postscript Printing from MS Windows

    +Let the Windows Clients use a PostScript driver to deliver poistscript to the samba print server (just like any Linux or Unix Client would also use -PostScript to send to the server)

    Make the Unix printing subsystem to which Samba sends the job convert the +PostScript to send to the server) +

    +Make the Unix printing subsystem to which Samba sends the job convert the incoming PostScript files to the native print format of the target printers -(would be PCL if you have an HP printer)

    Now if you are afraid that this would just mean using a *Generic* PostScript +(would be PCL if you have an HP printer) +

    +Now if you are afraid that this would just mean using a *Generic* PostScript driver for the clients that has no Simplex/Duplex selection, and no paper tray choice, but you need them to be able to set up print jobs, with all the bells -and whistles of your printers:-

    Not possible with traditional spooling systems
    But perfectly supported by CUPS (which uses "PPD" files to +and whistles of your printers:- +

    Not possible with traditional spooling systems
    + But perfectly supported by CUPS (which uses "PPD" files to describe how to control the print options for PostScript and non-PostScript devices alike... -

    CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript +

    +CUPS PPDs are working perfectly on Windows clients who use Adobe PostScript drivers (or the new CUPS PostScript driver for Windows NT/2K/XP). Clients can use them to setup the job to their liking and CUPS will use the received job options -to make the (PCL-, ESC/P- or PostScript-) printer behave as required.

    If you want to have the additional benefit of page count logging and accounting -then the CUPS PostScript driver is the best choice (better than the Adobe one).

    If you want to make the drivers downloadable for the clients then "cupsaddsmb" is +to make the (PCL-, ESC/P- or PostScript-) printer behave as required. +

    +If you want to have the additional benefit of page count logging and accounting +then the CUPS PostScript driver is the best choice (better than the Adobe one). +

    +If you want to make the drivers downloadable for the clients then "cupsaddsmb" is your friend. It will setup the [print$] share on the Samba host to be ready to serve -the clients for a "point and print" driver installation.

    What strings are attached?

    There are some. But, given the sheer CPU power you can buy nowadays, -these can be overcome easily. The strings:

    Well, if the CUPS/Samba side will have to print to many printers serving many users, +the clients for a "point and print" driver installation. +

    Warning

    What strings are attached?

    +There are some. But, given the sheer CPU power you can buy nowadays, +these can be overcome easily. The strings: +

    +Well, if the CUPS/Samba side will have to print to many printers serving many users, you probably will need to set up a second server (which can do automatic load balancing with the first one, plus a degree of fail-over mechanism). Converting the incoming -PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work -of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM -than for the mere "raw spooling" task your current setup is solving. It all depends -on the avarage and peak printing load the server should be able to handle.

    14.12. Auto-Deletion of CUPS spool files

    Samba print files pass thru two "spool" directories. One the incoming directory -managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers] -section of smb.conf). Second is the spool directory of your UNIX print subsystem. -For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive -"RequestRoot /var/spool/cups".

    I am not sure, which one of your directories keeps the files. From what you say, -it is most likely the Samba part.

    For the CUPS part, you may want to consult:

    http://localhost:631/sam.html#PreserveJobFiles
    http://localhost:631/sam.html#PreserveJobHistory
    http://localhost:631/sam.html#MaxJobs

    There are the settings described for your CUPS daemon, which could lead to completed -job files not being deleted.

    "PreserveJobHistory Yes" -- keeps some details of jobs in -cupsd's mind (well it keeps the "c12345", "c12346" etc. files +PostScript jobs, "interpreting" them for non-PostScript printers, amounts to the work +of a "RIP" (Raster Image Processor) done in software. This requires more CPU and RAM +than for the mere "raw spooling" task your current setup is solving. It all depends +on the avarage and peak printing load the server should be able to handle. +

    Auto-Deletion of CUPS spool files

    +Samba print files pass thru two "spool" directories. One the incoming directory +managed by Samba, (set eg: in the path = /var/spool/samba directive in the [printers] +section of smb.conf). Second is the spool directory of your UNIX print subsystem. +For CUPS it is normally "/var/spool/cups/", as set by the cupsd.conf directive +"RequestRoot /var/spool/cups". +

    +I am not sure, which one of your directories keeps the files. From what you say, +it is most likely the Samba part. +

    +For the CUPS part, you may want to consult: +

    http://localhost:631/sam.html#PreserveJobFiles
    http://localhost:631/sam.html#PreserveJobHistory
    http://localhost:631/sam.html#MaxJobs

    +There are the settings described for your CUPS daemon, which could lead to completed +job files not being deleted. +

    +"PreserveJobHistory Yes" -- keeps some details of jobs in +cupsd's mind (well it keeps the "c12345", "c12346" etc. files in the CUPS spool directory, which do a similar job as the -old-fashioned BSD-LPD control files). This is set to "Yes" -as a default.

    "PreserveJobFiles Yes" -- keeps the job files themselves in -cupsd's mind (well it keeps the "d12345", "d12346" etc. files -in the CUPS spool directory...). This is set to "No" as the -CUPS default.

    "MaxJobs 500" -- this directive controls the maximum number +old-fashioned BSD-LPD control files). This is set to "Yes" +as a default. +

    +"PreserveJobFiles Yes" -- keeps the job files themselves in +cupsd's mind (well it keeps the "d12345", "d12346" etc. files +in the CUPS spool directory...). This is set to "No" as the +CUPS default. +

    +"MaxJobs 500" -- this directive controls the maximum number of jobs that are kept in memory. Once the number of jobs reaches the limit, the oldest completed job is automatically purged from the system to make room for the new one. If all of the known jobs are still pending or active then the new job will be rejected. Setting the maximum to 0 disables this -functionality. The default setting is 0.

    (There are also additional settings for "MaxJobsPerUser" and -"MaxJobsPerPrinter"...)

    For everything to work as announced, you need to have three things:

    a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`) -
    a Samba-smb.conf setting of printing = cups -
    another Samba-smb.conf setting of printcap = cups -

    Note, that in this case all other manually set printing-related -commands (like "print command", "lpq command", "lprm command", -"lppause command" or "lpresume command") are ignored and they -should normally have no influence what-so-ever on your printing.

    If you want to do things manually, replace the "printing = cups" -by "printing = bsd". Then your manually set commands may work -(haven't tested this), and a "print command = lp -d %P %s; rm %s" -may do what you need.

    You forgot to mention the CUPS version you're using. If you did +functionality. The default setting is 0. +

    +(There are also additional settings for "MaxJobsPerUser" and +"MaxJobsPerPrinter"...) +

    +For everything to work as announced, you need to have three things: +

    + a Samba-smbd which is compiled against "libcups" (Check on Linux by running ldd `which smbd`) +
    + a Samba-smb.conf setting of printing = cups +
    + another Samba-smb.conf setting of printcap = cups +

    Note

    +Note, that in this case all other manually set printing-related +commands (like "print command", "lpq command", "lprm command", +"lppause command" or "lpresume command") are ignored and they +should normally have no influence what-so-ever on your printing. +

    +If you want to do things manually, replace the "printing = cups" +by "printing = bsd". Then your manually set commands may work +(haven't tested this), and a "print command = lp -d %P %s; rm %s" +may do what you need. +

    +You forgot to mention the CUPS version you're using. If you did set things up as described in the man pages, then the Samba spool files should be deleted. Otherwise it may be a bug. On the CUPS side, you can control the behaviour as described -above.

    If you have more problems, post the output of these commands:

    grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ - grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;"

    (adapt paths as needed). These commands sanitize the files +above. +

    +If you have more problems, post the output of these commands: +

    + + grep -v ^# /etc/cups/cupsd.conf | grep -v ^$ + grep -v ^# /etc/samba/smb.conf | grep -v ^$ | grep -v "^;" + +

    +(adapt paths as needed). These commands sanitize the files and cut out the empty lines and lines with comments, providing -the "naked settings" in a compact way.

    Chapter 15. Unified Logons between Windows NT and UNIX using Winbind

    15.1. Abstract

    Integration of UNIX and Microsoft Windows NT through - a unified logon has been considered a "holy grail" in heterogeneous +the "naked settings" in a compact way. +

    Chapter15.Unified Logons between Windows NT and UNIX using Winbind

    Tim Potter

    Samba Team

    <tpot@linuxcare.com.au>

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Naag Mummaneni

    <getnag@rediffmail.com>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    27 June 2002

    Table of Contents

    Abstract
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Limitations
    Conclusion

    Abstract

    Integration of UNIX and Microsoft Windows NT through + a unified logon has been considered a "holy grail" in heterogeneous computing environments for a long time. We present - winbind, a component of the Samba suite + winbind, a component of the Samba suite of programs as a solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind system, explaining the functionality it provides, how it is configured, - and how it works internally.

    15.2. Introduction

    It is well known that UNIX and Microsoft Windows NT have + and how it works internally.

    Introduction

    It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and use different technologies for implementing them. This fact has made it difficult to integrate the two systems in a satisfactory - manner.

    One common solution in use today has been to create + manner.

    One common solution in use today has been to create identically named user accounts on both the UNIX and Windows systems and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore and two sets of passwords are required both of which can lead to synchronization problems between the UNIX and Windows - systems and confusion for users.

    We divide the unified logon problem for UNIX machines into - three smaller problems:

    • Obtaining Windows NT user and group information -

    • Authenticating Windows NT users -

    • Password changing for Windows NT users -

    Ideally, a prospective solution to the unified logon problem + systems and confusion for users.

    We divide the unified logon problem for UNIX machines into + three smaller problems:

    • Obtaining Windows NT user and group information +

    • Authenticating Windows NT users +

    • Password changing for Windows NT users +

    Ideally, a prospective solution to the unified logon problem would satisfy all the above components without duplication of information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple and elegant solution to all three components of the unified logon - problem.

    15.3. What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by + problem.

    What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once this is done the UNIX box will see NT users and groups as if they were native UNIX users and groups, allowing the NT domain to be used in much the same manner that NIS+ is used within - UNIX-only environments.

    The end result is that whenever any + UNIX-only environments.

    The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely - transparent.

    Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files + transparent.

    Users on the UNIX machine can then use NT user and group + names as they would use "native" UNIX names. They can chown files so that they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is + UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is that user and group names take the form DOMAIN\user and DOMAIN\group. This is necessary as it allows Winbind to determine that redirection to a domain controller is wanted for a particular - lookup and which trusted domain is being referenced.

    Additionally, Winbind provides an authentication service + lookup and which trusted domain is being referenced.

    Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing passwords between systems since all passwords are stored in a single - location (on the domain controller).

    15.3.1. Target Uses

    Winbind is targeted at organizations that have an + location (on the domain controller).

    Target Uses

    Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to maintain a separate account infrastructure. This greatly simplifies the administrative overhead of deploying UNIX - workstations into a NT based organization.

    Another interesting way in which we expect Winbind to + workstations into a NT based organization.

    Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances that provide file and print services to Microsoft based networks will be able to use Winbind to provide seamless integration of - the appliance into the domain.

    15.4. How Winbind Works

    The winbind system is designed around a client/server - architecture. A long running winbindd daemon + the appliance into the domain.

    How Winbind Works

    The winbind system is designed around a client/server + architecture. A long running winbindd daemon listens on a UNIX domain socket waiting for requests to arrive. These requests are generated by the NSS and PAM - clients and processed sequentially.

    The technologies used to implement winbind are described - in detail below.

    15.4.1. Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway + clients and processed sequentially.

    The technologies used to implement winbind are described + in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -11857,25 +4965,13 @@ NAME="AEN2548" and print spooling. Although initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in Samba, it has also yielded a body of code which - can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users + can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user passwords. By directly querying a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.

    15.4.2. Microsoft Active Directory Services

    Since late 2001, Samba has gained the ability to + NT account information onto UNIX user and group names.

    Microsoft Active Directory Services

    + Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its 'Native Mode' protocols, rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running @@ -11883,18 +4979,7 @@ NAME="AEN2552" same way as a Win2k client would, and in so doing provide a much more efficient and effective winbind implementation. -

    15.4.3. Name Service Switch

    The Name Service Switch, or NSS, is a feature that is +

    Name Service Switch

    The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information to be resolved from different sources. For example, a standalone @@ -11902,9 +4987,7 @@ NAME="AEN2555" flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, and then consult a NIS database for user information or a DNS server - for hostname information.

    The NSS application programming interface allows winbind + for hostname information.

    The NSS application programming interface allows winbind to present itself as a source of system information when resolving UNIX usernames and groups. Winbind uses this interface, and information obtained from a Windows NT server using MSRPC @@ -11912,69 +4995,26 @@ NAME="AEN2555" UNIX library calls, one can enumerate the users and groups on a UNIX machine running winbind and see all users and groups in a NT domain plus any trusted domain as though they were local - users and groups.

    The primary control file for NSS is - /etc/nsswitch.conf. + users and groups.

    The primary control file for NSS is + /etc/nsswitch.conf. When a UNIX application makes a request to do a lookup - the C library looks in /etc/nsswitch.conf + the C library looks in /etc/nsswitch.conf for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names + example the "passwd" service type is used when user or group names are looked up. This config line species which implementations of that service should be tried and in what order. If the passwd - config line is:

    passwd: files example

    then the C library will first load a module called - /lib/libnss_files.so followed by - the module /lib/libnss_example.so. The + config line is:

    passwd: files example

    then the C library will first load a module called + /lib/libnss_files.so followed by + the module /lib/libnss_example.so. The C library will dynamically load each of these modules in turn and call resolver functions within the modules to try to resolve the request. Once the request is resolved the C library returns the - result to the application.

    This NSS interface provides a very easy way for Winbind + result to the application.

    This NSS interface provides a very easy way for Winbind to hook into the operating system. All that needs to be done - is to put libnss_winbind.so in /lib/ - then add "winbind" into /etc/nsswitch.conf at + is to put libnss_winbind.so in /lib/ + then add "winbind" into /etc/nsswitch.conf at the appropriate place. The C library will then call Winbind to - resolve user and group names.

    15.4.4. Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, + resolve user and group names.

    Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different authentication methods for different system applications without @@ -11982,48 +5022,24 @@ NAME="AEN2571" for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users stored in the local password file but only allow users resolved from - a NIS database to log in over the network.

    Winbind uses the authentication management and password + a NIS database to log in over the network.

    Winbind uses the authentication management and password management PAM interface to integrate Windows NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have this change take effect directly on the Primary Domain Controller. -

    PAM is configured by providing control files in the directory - /etc/pam.d/ for each of the services that +

    PAM is configured by providing control files in the directory + /etc/pam.d/ for each of the services that require authentication. When an authentication request is made by an application the PAM code in the C library looks up this control file to determine what modules to load to do the authentication check and in what order. This interface makes adding a new authentication service for Winbind very easy, all that needs - to be done is that the pam_winbind.so module - is copied to /lib/security/ and the PAM + to be done is that the pam_winbind.so module + is copied to /lib/security/ and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.

    15.4.5. User and Group ID Allocation

    When a user or group is created under Windows NT + for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify @@ -12034,22 +5050,9 @@ NAME="AEN2579" resolved for the first time, it is allocated the next UNIX id from the range. The same process applies for Windows NT groups. Over time, winbind will have mapped all Windows NT users and groups - to UNIX user ids and group ids.

    The results of this mapping are stored persistently in + to UNIX user ids and group ids.

    The results of this mapping are stored persistently in an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.

    15.4.6. Result Caching

    An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.

    Result Caching

    An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind uses a caching scheme based on the SAM sequence number supplied by NT domain controllers. User or group information returned @@ -12060,1485 +5063,651 @@ NAME="AEN2583" the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information is discarded and up to date information is requested directly - from the PDC.

    15.5. Installation and Configuration

    Many thanks to John Trostel jtrostel@snapserver.com -for providing the HOWTO for this section.

    This HOWTO describes how to get winbind services up and running + from the PDC.

    Installation and Configuration

    +Many thanks to John Trostel jtrostel@snapserver.com +for providing the HOWTO for this section. +

    +This HOWTO describes how to get winbind services up and running to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 2.2.2.

    15.5.1. Introduction

    This HOWTO describes the procedures used to get winbind up and +the winbind services which come with SAMBA 3.0. +

    Introduction

    +This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Win2K PDC for 'regular' services, such as telnet a nd ftp, as -well for SAMBA services.

    This HOWTO has been written from a 'RedHat-centric' perspective, so if +well for SAMBA services. +

    +This HOWTO has been written from a 'RedHat-centric' perspective, so if you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.

    • Why should I to this? -

      This allows the SAMBA administrator to rely on the +somewhat to fit the way your distribution works. +

      • + Why should I to this? +

        This allows the SAMBA administrator to rely on the authentication mechanisms on the NT/Win2K PDC for the authentication of domain members. NT/Win2K users no longer need to have separate accounts on the SAMBA server. -

      • Who should be reading this document? -

        This HOWTO is designed for system administrators. If you are +

      • + Who should be reading this document? +

        + This HOWTO is designed for system administrators. If you are implementing SAMBA on a file server and wish to (fairly easily) integrate existing NT/Win2K users from your PDC onto the SAMBA server, this HOWTO is for you. That said, I am no NT or PAM expert, so you may find a better or easier way to accomplish these tasks. -

      15.5.2. Requirements

      If you have a samba configuration file that you are currently -using... BACK IT UP! If your system already uses PAM, -back up the /etc/pam.d directory -contents! If you haven't already made a boot disk, -MAKE ONE NOW!

      Messing with the pam configuration files can make it nearly impossible +

    Requirements

    +If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, +back up the /etc/pam.d directory +contents! If you haven't already made a boot disk, +MAKE ONE NOW! +

    +Messing with the pam configuration files can make it nearly impossible to log in to yourmachine. That's why you want to be able to boot back into your machine in single user mode and restore your -/etc/pam.d back to the original state they were in if -you get frustrated with the way things are going. ;-)

    The latest version of SAMBA (version 3.0 as of this writing), now +/etc/pam.d back to the original state they were in if +you get frustrated with the way things are going. ;-) +

    +The latest version of SAMBA (version 3.0 as of this writing), now includes a functioning winbindd daemon. Please refer to the -main SAMBA web page or, +main SAMBA web page or, better yet, your closest SAMBA mirror site for instructions on -downloading the source code.

    To allow Domain users the ability to access SAMBA shares and +downloading the source code. +

    +To allow Domain users the ability to access SAMBA shares and files, as well as potentially other services provided by your SAMBA machine, PAM (pluggable authentication modules) must be setup properly on your machine. In order to compile the winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that -means pam-0.74-22. For best results, it is helpful to also -install the development packages in pam-devel-0.74-22.

    15.5.3. Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA -related daemons running on your server. Kill off all smbd, -nmbd, and winbindd processes that may +means pam-0.74-22. For best results, it is helpful to also +install the development packages in pam-devel-0.74-22. +

    Testing Things Out

    +Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all smbd, +nmbd, and winbindd processes that may be running. To use PAM, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the /etc/pam.d +standard PAM package (for RedHat) which supplies the /etc/pam.d directory structure, including the pam modules are used by pam-aware -services, several pam libraries, and the /usr/doc -and /usr/man entries for pam. Winbind built better +services, several pam libraries, and the /usr/doc +and /usr/man entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. For instance, -my RedHat system has both pam-0.74-22 and -pam-devel-0.74-22 RPMs installed.

    15.5.3.1. Configure and compile SAMBA

    The configuration and compilation of SAMBA is pretty straightforward. +my RedHat system has both pam-0.74-22 and +pam-devel-0.74-22 RPMs installed. +

    Configure and compile SAMBA

    +The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon -whether or not you have previously built the Samba binaries.

    root# autoconf
-root# make clean
-root# rm config.cache
-root# ./configure
-root# make
-root# make install

    This will, by default, install SAMBA in /usr/local/samba. +whether or not you have previously built the Samba binaries. +

    +root# autoconf
+root# make clean
+root# rm config.cache
+root# ./configure
+root# make
+root# make install
+

    +This will, by default, install SAMBA in /usr/local/samba. See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries.

    15.5.3.2. Configure nsswitch.conf and the -winbind libraries

    The libraries needed to run the winbindd daemon -through nsswitch need to be copied to their proper locations, so

    root# cp ../samba/source/nsswitch/libnss_winbind.so /lib

    I also found it necessary to make the following symbolic link:

    root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

    And, in the case of Sun solaris:

    root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2

    Now, as root you need to edit /etc/nsswitch.conf to -allow user and group entries to be visible from the winbindd -daemon. My /etc/nsswitch.conf file look like -this after editing:

    	passwd:     files winbind
+It will also build the winbindd executable and libraries. 
+

    Configure nsswitch.conf and the +winbind libraries on Linux and Solaris

    +The libraries needed to run the winbindd daemon +through nsswitch need to be copied to their proper locations, so +

    +root# cp ../samba/source/nsswitch/libnss_winbind.so /lib +

    +I also found it necessary to make the following symbolic link: +

    +root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 +

    And, in the case of Sun solaris:

    +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2 +

    +Now, as root you need to edit /etc/nsswitch.conf to +allow user and group entries to be visible from the winbindd +daemon. My /etc/nsswitch.conf file look like +this after editing: +

    +	passwd:     files winbind
 	shadow:     files 
-	group:      files winbind

    + group: files winbind +

    The libraries needed by the winbind daemon will be automatically -entered into the ldconfig cache the next time +entered into the ldconfig cache the next time your system reboots, but it -is faster (and you don't need to reboot) if you do it manually:

    root# /sbin/ldconfig -v | grep winbind

    This makes libnss_winbind available to winbindd -and echos back a check to you.

    15.5.3.3. Configure smb.conf

    Several parameters are needed in the smb.conf file to control -the behavior of winbindd. Configure -smb.conf These are described in more detail in -the winbindd(8) man page. My -smb.conf file was modified to -include the following entries in the [global] section:

    [global]
-     <...>
+is faster (and you don't need to reboot) if you do it manually:
+
    
+root# /sbin/ldconfig -v | grep winbind
+
    
+This makes libnss_winbind available to winbindd 
+and echos back a check to you.
+

    NSS Winbind on AIX

    (This section is only for those running AIX)

    +The winbind AIX identification module gets built as libnss_winbind.so in the +nsswitch directory of the samba source. This file can be copied to +/usr/lib/security, and the AIX naming convention would indicate that it +should be named WINBIND. A stanza like the following: +

    +WINBIND:
+        program = /usr/lib/security/WINBIND
+        options = authonly
+

    can then be added to +/usr/lib/security/methods.cfg. This module only +supports identification, but there have been success reports using the +standard winbind pam module for authentication. Use caution configuring +loadable authentication modules as it is possible to make it impossible +to logon to the system. More information about the AIX authentication +module API can be found at "Kernel Extensions and Device Support +Programming Concepts for AIX": +Chapter 18. Loadable Authentication Module Programming Interface +and more information on administering the modules at +"System Management Guide: Operating System and Devices". +

    Configure smb.conf

    +Several parameters are needed in the smb.conf file to control +the behavior of winbindd. Configure +smb.conf These are described in more detail in +the winbindd(8) man page. My +smb.conf file was modified to +include the following entries in the [global] section: +

    +[global]
+     <...>
      # separate domain and username with '+', like DOMAIN+username
-     winbind separator = +
+     winbind separator = +
      # use uids from 10000 to 20000 for domain users
-     winbind uid = 10000-20000
+     winbind uid = 10000-20000
      # use gids from 10000 to 20000 for domain groups
-     winbind gid = 10000-20000
+     winbind gid = 10000-20000
      # allow enumeration of winbind users and groups
-     winbind enum users = yes
-     winbind enum groups = yes
+     winbind enum users = yes
+     winbind enum groups = yes
      # give winbind users a real shell (only needed if they have telnet access)
-     template homedir = /home/winnt/%D/%U
-     template shell = /bin/bash

    15.5.3.4. Join the SAMBA server to the PDC domain

    Enter the following command to make the SAMBA server join the -PDC domain, where DOMAIN is the name of -your Windows domain and Administrator is -a domain user who has administrative privileges in the domain.

    root# /usr/local/samba/bin/net join -S PDC -U Administrator

    The proper response to the command should be: "Joined the domain -DOMAIN" where DOMAIN -is your DOMAIN name.

    15.5.3.5. Start up the winbindd daemon and test it!

    Eventually, you will want to modify your smb startup script to + template homedir = /home/winnt/%D/%U + template shell = /bin/bash +

    Join the SAMBA server to the PDC domain

    +Enter the following command to make the SAMBA server join the +PDC domain, where DOMAIN is the name of +your Windows domain and Administrator is +a domain user who has administrative privileges in the domain. +

    +root# /usr/local/samba/bin/net join -S PDC -U Administrator +

    +The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN +is your DOMAIN name. +

    Start up the winbindd daemon and test it!

    +Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of SAMBA start, but it is possible to test out just the winbind portion first. To start up winbind services, enter the following -command as root:

    root# /usr/local/samba/bin/winbindd

    Winbindd can now also run in 'dual daemon mode'. This will make it +command as root: +

    +root# /usr/local/samba/bin/winbindd +

    +Winbindd can now also run in 'dual daemon mode'. This will make it run as 2 processes. The first will answer all requests from the cache, thus making responses to clients faster. The other will update the cache for the query that the first has just responded. Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline:

    root# /usr/local/samba/bin/winbindd -B

    I'm always paranoid and like to make sure the daemon -is really running...

    root# ps -ae | grep winbindd

    This command should produce output like this, if the daemon is running

    3025 ? 00:00:00 winbindd

    Now... for the real test, try to get some information about the -users on your PDC

    root# /usr/local/samba/bin/wbinfo -u

    +You can enable dual daemon mode by adding '-B' to the commandline: +

    +root# /usr/local/samba/bin/winbindd -B +

    +I'm always paranoid and like to make sure the daemon +is really running... +

    +root# ps -ae | grep winbindd +

    +This command should produce output like this, if the daemon is running +

    +3025 ? 00:00:00 winbindd +

    +Now... for the real test, try to get some information about the +users on your PDC +

    +root# /usr/local/samba/bin/wbinfo -u +

    This should echo back a list of users on your Windows users on -your PDC. For example, I get the following response:

    CEO+Administrator
-CEO+burdell
-CEO+Guest
-CEO+jt-ad
-CEO+krbtgt
-CEO+TsInternetUser

    Obviously, I have named my domain 'CEO' and my winbind -separator is '+'.

    You can do the same sort of thing to get group information from -the PDC:

    root# /usr/local/samba/bin/wbinfo -g
-CEO+Domain Admins
-CEO+Domain Users
-CEO+Domain Guests
-CEO+Domain Computers
-CEO+Domain Controllers
-CEO+Cert Publishers
-CEO+Schema Admins
-CEO+Enterprise Admins
-CEO+Group Policy Creator Owners

    The function 'getent' can now be used to get unified +your PDC. For example, I get the following response: +

    +	CEO+Administrator
+	CEO+burdell
+	CEO+Guest
+	CEO+jt-ad
+	CEO+krbtgt
+	CEO+TsInternetUser
+

    +Obviously, I have named my domain 'CEO' and my winbind +separator is '+'. +

    +You can do the same sort of thing to get group information from +the PDC: +

    +root# /usr/local/samba/bin/wbinfo -g
+	CEO+Domain Admins
+	CEO+Domain Users
+	CEO+Domain Guests
+	CEO+Domain Computers
+	CEO+Domain Controllers
+	CEO+Cert Publishers
+	CEO+Schema Admins
+	CEO+Enterprise Admins
+	CEO+Group Policy Creator Owners
+

    +The function 'getent' can now be used to get unified lists of both local and PDC users and groups. -Try the following command:

    root# getent passwd

    You should get a list that looks like your /etc/passwd +Try the following command: +

    +root# getent passwd +

    +You should get a list that looks like your /etc/passwd list followed by the domain users with their new uids, gids, home -directories and default shells.

    The same thing can be done for groups with the command

    root# getent group

    15.5.3.6. Fix the init.d startup scripts

    15.5.3.6.1. Linux

    The winbindd daemon needs to start up after the -smbd and nmbd daemons are running. -To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in RedHat and -/etc/init.d/samba in Debian. +directories and default shells. +

    +The same thing can be done for groups with the command +

    +root# getent group +

    Fix the init.d startup scripts

    Linux

    +The winbindd daemon needs to start up after the +smbd and nmbd daemons are running. +To accomplish this task, you need to modify the startup scripts of your system. +They are located at /etc/init.d/smb in RedHat and +/etc/init.d/samba in Debian. script to add commands to invoke this daemon in the proper sequence. My -startup script starts up smbd, -nmbd, and winbindd from the -/usr/local/samba/bin directory directly. The 'start' -function in the script looks like this:

    start() {
-        KIND="SMB"
-        echo -n $"Starting $KIND services: "
+startup script starts up smbd, 
+nmbd, and winbindd from the 
+/usr/local/samba/bin directory directly.  The 'start' 
+function in the script looks like this:
+
    +start() {
+        KIND="SMB"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Starting $KIND services: "
+        KIND="NMB"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Starting $KIND services: "
+        KIND="Winbind"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/winbindd
         RETVAL3=$?
         echo
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \
-           RETVAL=1
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
+		touch /var/lock/subsys/smb || RETVAL=1
         return $RETVAL
-}
    If you would like to run winbindd in dual daemon mode, replace 
+}
+

    If you would like to run winbindd in dual daemon mode, replace the line -

            daemon /usr/local/samba/bin/winbindd
    +

    +        daemon /usr/local/samba/bin/winbindd
+

    in the example above with: -

            daemon /usr/local/samba/bin/winbindd -B
    .

    The 'stop' function has a corresponding entry to shut down the -services and looks like this:

    stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
+
    +        daemon /usr/local/samba/bin/winbindd -B
+
    .
+
    
+The 'stop' function has a corresponding entry to shut down the 
+services and looks like this:
+
    +stop() {
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
         killproc smbd
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
         killproc nmbd
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Shutting down $KIND services: "
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
         killproc winbindd
         RETVAL3=$?
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb
-        echo ""
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
+		 rm -f /var/lock/subsys/smb
+        echo ""
         return $RETVAL
-}
    15.5.3.6.2. Solaris

    On solaris, you need to modify the -/etc/init.d/samba.server startup script. It usually +} +

    Solaris

    Winbind doesn't work on solaris 9, see the Portability chapter for details.

    On solaris, you need to modify the +/etc/init.d/samba.server startup script. It usually only starts smbd and nmbd but should now start winbindd too. If you -have samba installed in /usr/local/samba/bin, -the file could contains something like this:

    ##
-## samba.server
-##
+have samba installed in /usr/local/samba/bin, 
+the file could contains something like this:
+
    +	##
+	## samba.server
+	##
 
-if [ ! -d /usr/bin ]
-then                    # /usr not mounted
-        exit
-fi
+	if [ ! -d /usr/bin ]
+	then                    # /usr not mounted
+		exit
+	fi
 
-killproc() {            # kill the named process(es)
-        pid=`/usr/bin/ps -e |
-             /usr/bin/grep -w $1 |
-             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
-        [ "$pid" != "" ] && kill $pid
-}
- 
-# Start/stop processes required for samba server
+	killproc() {            # kill the named process(es)
+		pid=`/usr/bin/ps -e |
+		     /usr/bin/grep -w $1 |
+		     /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
+		[ "$pid" != "" ] && kill $pid
+	}
+	 
+	# Start/stop processes required for samba server
 
-case "$1" in
+	case "$1" in
 
-'start')
-#
-# Edit these lines to suit your installation (paths, workgroup, host)
-#
-echo Starting SMBD
-   /usr/local/samba/bin/smbd -D -s \
-	/usr/local/samba/smb.conf
+	'start')
+	#
+	# Edit these lines to suit your installation (paths, workgroup, host)
+	#
+	echo Starting SMBD
+	   /usr/local/samba/bin/smbd -D -s \
+		/usr/local/samba/smb.conf
 
-echo Starting NMBD
-   /usr/local/samba/bin/nmbd -D -l \
-	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
+	echo Starting NMBD
+	   /usr/local/samba/bin/nmbd -D -l \
+		/usr/local/samba/var/log -s /usr/local/samba/smb.conf
 
-echo Starting Winbind Daemon
-   /usr/local/samba/bin/winbindd
-   ;;
+	echo Starting Winbind Daemon
+	   /usr/local/samba/bin/winbindd
+	   ;;
 
-'stop')
-   killproc nmbd
-   killproc smbd
-   killproc winbindd
-   ;;
+	'stop')
+	   killproc nmbd
+	   killproc smbd
+	   killproc winbindd
+	   ;;
 
-*)
-   echo "Usage: /etc/init.d/samba.server { start | stop }"
-   ;;
-esac
    Again, if you would like to run samba in dual daemon mode, replace 
-
       /usr/local/samba/bin/winbindd
    
+	*)
+	   echo "Usage: /etc/init.d/samba.server { start | stop }"
+	   ;;
+	esac
+

    +Again, if you would like to run samba in dual daemon mode, replace +

    +	/usr/local/samba/bin/winbindd
+

    in the script above with: -

       /usr/local/samba/bin/winbindd -B

    15.5.3.6.3. Restarting

    If you restart the smbd, nmbd, -and winbindd daemons at this point, you +

    +	/usr/local/samba/bin/winbindd -B
+

    +

    Restarting

    +If you restart the smbd, nmbd, +and winbindd daemons at this point, you should be able to connect to the samba server as a domain member just as -if you were a local user.

    15.5.3.7. Configure Winbind and PAM

    If you have made it this far, you know that winbindd and samba are working +if you were a local user. +

    Configure Winbind and PAM

    +If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other services, keep reading. The pam configuration files need to be altered in this step. (Did you remember to make backups of your original -/etc/pam.d files? If not, do it now.)

    You will need a pam module to use winbindd with these other services. This -module will be compiled in the ../source/nsswitch directory -by invoking the command

    root# make nsswitch/pam_winbind.so

    from the ../source directory. The -pam_winbind.so file should be copied to the location of +/etc/pam.d files? If not, do it now.) +

    +You will need a pam module to use winbindd with these other services. This +module will be compiled in the ../source/nsswitch directory +by invoking the command +

    +root# make nsswitch/pam_winbind.so +

    +from the ../source directory. The +pam_winbind.so file should be copied to the location of your other pam security modules. On my RedHat system, this was the -/lib/security directory. On Solaris, the pam security -modules reside in /usr/lib/security.

    root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security

    15.5.3.7.1. Linux/FreeBSD-specific PAM configuration

    The /etc/pam.d/samba file does not need to be changed. I -just left this fileas it was:

    auth    required        /lib/security/pam_stack.so service=system-auth
-account required        /lib/security/pam_stack.so service=system-auth

    The other services that I modified to allow the use of winbind +/lib/security directory. On Solaris, the pam security +modules reside in /usr/lib/security. +

    +root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security +

    Linux/FreeBSD-specific PAM configuration

    +The /etc/pam.d/samba file does not need to be changed. I +just left this fileas it was: +

    +	auth    required        /lib/security/pam_stack.so service=system-auth
+	account required        /lib/security/pam_stack.so service=system-auth
+

    +The other services that I modified to allow the use of winbind as an authentication service were the normal login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these services, you may first need to change the entries in -/etc/xinetd.d (or /etc/inetd.conf). +/etc/xinetd.d (or /etc/inetd.conf). RedHat 7.1 uses the new xinetd.d structure, in this case you need -to change the lines in /etc/xinetd.d/telnet -and /etc/xinetd.d/wu-ftp from 

    enable = no

    to

    enable = yes

    +to change the lines in /etc/xinetd.d/telnet +and /etc/xinetd.d/wu-ftp from +

    +	enable = no
+

    +to +

    +	enable = yes
+

    For ftp services to work properly, you will also need to either have individual directories for the domain users already present on the server, or change the home directory template to a general directory for all domain users. These can be easily set using -the smb.conf global entry -template homedir.

    The /etc/pam.d/ftp file can be changed +the smb.conf global entry +template homedir. +

    +The /etc/pam.d/ftp file can be changed to allow winbind ftp access in a manner similar to the -samba file. My /etc/pam.d/ftp file was -changed to look like this:

    auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
-auth       sufficient   /lib/security/pam_winbind.so
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_shells.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth

    The /etc/pam.d/login file can be changed nearly the -same way. It now looks like this:

    auth       required     /lib/security/pam_securetty.so
-auth       sufficient   /lib/security/pam_winbind.so
-auth       sufficient   /lib/security/pam_unix.so use_first_pass
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_nologin.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-password   required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth
-session    optional     /lib/security/pam_console.so

    In this case, I added the auth sufficient /lib/security/pam_winbind.so -lines as before, but also added the required pam_securetty.so +samba file. My /etc/pam.d/ftp file was +changed to look like this: +

    +	auth       required     /lib/security/pam_listfile.so item=user sense=deny \
+		 file=/etc/ftpusers onerr=succeed
+	auth       sufficient   /lib/security/pam_winbind.so
+	auth       required     /lib/security/pam_stack.so service=system-auth
+	auth       required     /lib/security/pam_shells.so
+	account    sufficient   /lib/security/pam_winbind.so
+	account    required     /lib/security/pam_stack.so service=system-auth
+	session    required     /lib/security/pam_stack.so service=system-auth
+

    +The /etc/pam.d/login file can be changed nearly the +same way. It now looks like this: +

    +	auth       required     /lib/security/pam_securetty.so
+	auth       sufficient   /lib/security/pam_winbind.so
+	auth       sufficient   /lib/security/pam_unix.so use_first_pass
+	auth       required     /lib/security/pam_stack.so service=system-auth
+	auth       required     /lib/security/pam_nologin.so
+	account    sufficient   /lib/security/pam_winbind.so
+	account    required     /lib/security/pam_stack.so service=system-auth
+	password   required     /lib/security/pam_stack.so service=system-auth
+	session    required     /lib/security/pam_stack.so service=system-auth
+	session    optional     /lib/security/pam_console.so
+

    +In this case, I added the auth sufficient /lib/security/pam_winbind.so +lines as before, but also added the required pam_securetty.so above it, to disallow root logins over the network. I also added a -sufficient /lib/security/pam_unix.so use_first_pass -line after the winbind.so line to get rid of annoying -double prompts for passwords.

    15.5.3.7.2. Solaris-specific configuration

    The /etc/pam.conf needs to be changed. I changed this file so that my Domain +sufficient /lib/security/pam_unix.so use_first_pass +line after the winbind.so line to get rid of annoying +double prompts for passwords. +

    Solaris-specific configuration

    +The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but be sure of those changes because in the worst case it will leave your system -nearly impossible to boot.

    #
-#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
-#
-# Copyright (c) 1996-1999, Sun Microsystems, Inc.
-# All Rights Reserved.
-#
-# PAM configuration
-#
-# Authentication management
-#
-login   auth required   /usr/lib/security/pam_winbind.so
-login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
-login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
-#
-rlogin  auth sufficient /usr/lib/security/pam_winbind.so
-rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-dtlogin auth sufficient /usr/lib/security/pam_winbind.so
-dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
-other   auth sufficient /usr/lib/security/pam_winbind.so
-other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-# Account management
-#
-login   account sufficient      /usr/lib/security/pam_winbind.so
-login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-dtlogin account sufficient      /usr/lib/security/pam_winbind.so
-dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-other   account sufficient      /usr/lib/security/pam_winbind.so
-other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Session management
-#
-other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Password management
-#
-#other   password sufficient     /usr/lib/security/pam_winbind.so
-other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
-dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
-#
-# Support for Kerberos V5 authentication (uncomment to use Kerberos)
-#
-#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

    I also added a try_first_pass line after the winbind.so line to get rid of -annoying double prompts for passwords.

    Now restart your Samba and try connecting through your application that you -configured in the pam.conf.

    15.6. Limitations

    Winbind has a number of limitations in its current +nearly impossible to boot. +

    +	#
+	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+	#
+	# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+	# All Rights Reserved.
+	#
+	# PAM configuration
+	#
+	# Authentication management
+	#
+	login   auth required   /usr/lib/security/pam_winbind.so
+	login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
+	login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
+	#
+	rlogin  auth sufficient /usr/lib/security/pam_winbind.so
+	rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+	rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+	dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
+	other   auth sufficient /usr/lib/security/pam_winbind.so
+	other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	# Account management
+	#
+	login   account sufficient      /usr/lib/security/pam_winbind.so
+	login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	dtlogin account sufficient      /usr/lib/security/pam_winbind.so
+	dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	other   account sufficient      /usr/lib/security/pam_winbind.so
+	other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	# Session management
+	#
+	other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	# Password management
+	#
+	#other   password sufficient     /usr/lib/security/pam_winbind.so
+	other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
+	dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
+	#
+	# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+	#
+	#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+

    +I also added a try_first_pass line after the winbind.so line to get rid of +annoying double prompts for passwords. +

    +Now restart your Samba and try connecting through your application that you +configured in the pam.conf. +

    Limitations

    Winbind has a number of limitations in its current released version that we hope to overcome in future - releases:

    • Winbind is currently only available for + releases:

      • Winbind is currently only available for the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.

      • The mappings of Windows NT RIDs to UNIX ids + PAM gain support among UNIX vendors.

      • The mappings of Windows NT RIDs to UNIX ids is not made algorithmically and depends on the order in which unmapped users or groups are seen by winbind. It may be difficult to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.

      • Currently the winbind PAM module does not take + containing this information is corrupted or destroyed.

      • Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

      15.7. Conclusion

      The winbind system, through the use of the Name Service + instead up to the PDC to enforce.

    Conclusion

    The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate Microsoft RPC calls have allowed us to provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.

    Chapter 16. Advanced Network Manangement

    This section attempts to document peripheral issues that are of great importance to network + cost of running a mixed UNIX and NT network.

    Chapter16.Advanced Network Manangement

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    April 3 2003

    Table of Contents

    Configuring Samba Share Access Controls
    Share Permissions Management
    Remote Server Administration
    Network Logon Script Magic
    Adding printers without user intervention

    +This section attempts to document peripheral issues that are of great importance to network administrators who want to improve network resource access control, to automate the user -environment, and to make their lives a little easier.

    16.1. Configuring Samba Share Access Controls

    This section deals with how to configure Samba per share access control restrictions. +environment, and to make their lives a little easier. +

    Configuring Samba Share Access Controls

    +This section deals with how to configure Samba per share access control restrictions. By default samba sets no restrictions on the share itself. Restrictions on the share itself can be set on MS Windows NT4/200x/XP shares. This can be a very effective way to limit who can connect to a share. In the absence of specific restrictions the default setting is to allow -the global user Everyone Full Control (ie: Full control, Change and Read).

    At this time Samba does NOT provide a tool for configuring access control setting on the Share +the global user Everyone Full Control (ie: Full control, Change and Read). +

    +At this time Samba does NOT provide a tool for configuring access control setting on the Share itself. Samba does have the capacity to store and act on access control settings, but the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x MMC for -Computer Management.

    Samba stores the per share access control settings in a file called share_info.tdb. +Computer Management. +

    +Samba stores the per share access control settings in a file called share_info.tdb. The location of this file on your system will depend on how samba was compiled. The default location -for samba's tdb files is under /usr/local/samba/var. If the tdbdump +for samba's tdb files is under /usr/local/samba/var. If the tdbdump utility has been compiled and installed on your system then you can examine the contents of this file -by: tdbdump share_info.tdb.

    16.1.1. Share Permissions Management

    The best tool for the task is platform dependant. Choose the best tool for your environmemt.

    16.1.1.1. Windows NT4 Workstation/Server

    The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. +by: tdbdump share_info.tdb. +

    Share Permissions Management

    +The best tool for the task is platform dependant. Choose the best tool for your environmemt. +

    Windows NT4 Workstation/Server

    +The tool you need to use to manage share permissions on a Samba server is the NT Server Manager. Server Manager is shipped with Windows NT4 Server products but not with Windows NT4 Workstation. -You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below.

    Instructions

    1. Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu -select Computer, then click on the Shared Directories entry.

    2. Now click on the share that you wish to manage, then click on the Properties tab, next click on - the Permissions tab. Now you can Add or change access control settings as you wish.

    16.1.1.2. Windows 200x/XP

    On MS Windows NT4/200x/XP system access control lists on the share itself are set using native +You can obtain the NT Server Manager for MS Windows NT4 Workstation from Microsoft - see details below. +

    Procedure16.1.Instructions

    1. +Launch the NT4 Server Manager, click on the Samba server you want to administer, then from the menu +select Computer, then click on the Shared Directories entry. +

    2. + Now click on the share that you wish to manage, then click on the Properties tab, next click on + the Permissions tab. Now you can Add or change access control settings as you wish. +

    Windows 200x/XP

    +On MS Windows NT4/200x/XP system access control lists on the share itself are set using native tools, usually from filemanager. For example, in Windows 200x: right click on the shared folder, then select 'Sharing', then click on 'Permissions'. The default Windows NT4/200x permission allows -Everyone Full Control on the Share.

    MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the -Microsoft Management Console (MMC). This tool is located by clicking on Control Panel -> -Administrative Tools -> Computer Management.

    Instructions

    1. After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', +Everyone Full Control on the Share. +

      +MS Windows 200x and later all comes with a tool called the 'Computer Management' snap-in for the +Microsoft Management Console (MMC). This tool is located by clicking on Control Panel -> +Administrative Tools -> Computer Management. +

      Procedure16.2.Instructions

      1. + After launching the MMC with the Computer Management snap-in, click on the menu item 'Action', select 'Connect to another computer'. If you are not logged onto a domain you will be prompted to enter a domain login user identifier and a password. This will authenticate you to the domain. - If you where already logged in with administrative privilidge this step is not offered.

      2. If the Samba server is not shown in the Select Computer box, then type in the name of the target + If you where already logged in with administrative privilidge this step is not offered. +

      3. +If the Samba server is not shown in the Select Computer box, then type in the name of the target Samba server in the field 'Name:'. Now click on the [+] next to 'System Tools', then on the [+] -next to 'Shared Folders' in the left panel.

      4. Now in the right panel, double-click on the share you wish to set access control permissions on. +next to 'Shared Folders' in the left panel. +

      5. +Now in the right panel, double-click on the share you wish to set access control permissions on. Then click on the tab 'Share Permissions'. It is now possible to add access control entities to the shared folder. Do NOT forget to set what type of access (full control, change, read) you -wish to assign for each entry.

      Be careful. If you take away all permissions from the Everyone user without removing this user +wish to assign for each entry. +

      Warning

      +Be careful. If you take away all permissions from the Everyone user without removing this user then effectively no user will be able to access the share. This is a result of what is known as ACL precidence. ie: Everyone with NO ACCESS means that MaryK who is part of the group Everyone -will have no access even if this user is given explicit full control access.

    16.2. Remote Server Administration

    How do I get 'User Manager' and 'Server Manager'?

    Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', -the 'Server Manager'?

    Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me -systems. The tools set includes:

    • Server Manager

    • User Manager for Domains

    • Event Viewer

    Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE

    The Windows NT 4.0 version of the 'User Manager for +will have no access even if this user is given explicit full control access. +

    Remote Server Administration

    +How do I get 'User Manager' and 'Server Manager'? +

    +Since I don't need to buy an NT4 Server, how do I get the 'User Manager for Domains', +the 'Server Manager'? +

    +Microsoft distributes a version of these tools called nexus for installation on Windows 9x / Me +systems. The tools set includes: +

    • Server Manager

    • User Manager for Domains

    • Event Viewer

    +Click here to download the archived file ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE +

    +The Windows NT 4.0 version of the 'User Manager for Domains' and 'Server Manager' are available from Microsoft via ftp -from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE

    16.3. Network Logon Script Magic

    This section needs work. Volunteer contributions most welcome. Please send your patches or updates -to John Terpstra.

    There are several opportunities for creating a custom network startup configuration environment.

    No Logon Script
    Simple universal Logon Script that applies to all users
    Use of a conditional Logon Script that applies per user or per group attirbutes
    Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create - a custom Logon Script and then execute it.
    User of a tool such as KixStart

    The Samba source code tree includes two logon script generation/execution tools. See examples directory genlogon and ntlogon subdirectories.

    The following listings are from the genlogon directory.

    This is the genlogon.pl file: +from ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE +

    Network Logon Script Magic

    +This section needs work. Volunteer contributions most welcome. Please send your patches or updates +to John Terpstra. +

    +There are several opportunities for creating a custom network startup configuration environment. +

    No Logon Script
    Simple universal Logon Script that applies to all users
    Use of a conditional Logon Script that applies per user or per group attirbutes
    Use of Samba's Preexec and Postexec functions on access to the NETLOGON share to create + a custom Logon Script and then execute it.
    User of a tool such as KixStart

    +The Samba source code tree includes two logon script generation/execution tools. See examples directory genlogon and ntlogon subdirectories. +

    +The following listings are from the genlogon directory. +

    +This is the genlogon.pl file: -

    	#!/usr/bin/perl
+
    +	#!/usr/bin/perl
 	#
 	# genlogon.pl
 	#
@@ -13564,31 +5733,31 @@ CLASS="PROGRAMLISTING"
 	# Log client connection
 	#($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
 	($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time);
-	open LOG, ">>/var/log/samba/netlogon.log";
-	print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
+	open LOG, ">>/var/log/samba/netlogon.log";
+	print LOG "$mon/$mday/$year $hour:$min:$sec - User $ARGV[0] logged into $ARGV[1]\n";
 	close LOG;
 
 	# Start generating logon script
-	open LOGON, ">/shared/netlogon/$ARGV[0].bat";
-	print LOGON "\@ECHO OFF\r\n";
+	open LOGON, ">/shared/netlogon/$ARGV[0].bat";
+	print LOGON "\@ECHO OFF\r\n";
 
 	# Connect shares just use by Software Development group
-	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
+	if ($ARGV[1] eq "SOFTDEV" || $ARGV[0] eq "softdev")
 	{
-		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
+		print LOGON "NET USE M: \\\\$ARGV[2]\\SOURCE\r\n";
 	}
 
 	# Connect shares just use by Technical Support staff
-	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
+	if ($ARGV[1] eq "SUPPORT" || $ARGV[0] eq "support")
 	{
-		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
+		print LOGON "NET USE S: \\\\$ARGV[2]\\SUPPORT\r\n";
 	}
 
 	# Connect shares just used by Administration staff
-	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
+	If ($ARGV[1] eq "ADMIN" || $ARGV[0] eq "admin")
 	{
-		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
-		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
+		print LOGON "NET USE L: \\\\$ARGV[2]\\ADMIN\r\n";
+		print LOGON "NET USE K: \\\\$ARGV[2]\\MKTING\r\n";
 	}
 
 	# Now connect Printers.  We handle just two or three users a little
@@ -13598,1814 +5767,732 @@ CLASS="PROGRAMLISTING"
 	if ($ARGV[0] eq 'jim'
 	    || $ARGV[0] eq 'yvonne')
 	{
-		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
-		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+		print LOGON "NET USE LPT2: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
 	}
 	else
 	{
-		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
-		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
+		print LOGON "NET USE LPT1: \\\\$ARGV[2]\\LJET3\r\n";
+		print LOGON "NET USE LPT3: \\\\$ARGV[2]\\FAXQ\r\n";
 	}
 
 	# All done! Close the output file.
-	close LOGON;
    Those wishing to use more elaborate or capable logon processing system should check out the following sites:
    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org

    Chapter 17. System and Account Policies

    17.1. Creating and Managing System Policies

    Under MS Windows platforms, particularly those following the release of MS Windows + close LOGON; +

    +

    +Those wishing to use more elaborate or capable logon processing system should check out the following sites: +

    http://www.craigelachie.org/rhacer/ntlogon
    http://www.kixtart.org
    http://support.microsoft.com/default.asp?scid=kb;en-us;189105

    Adding printers without user intervention

    +Printers may be added automatically during logon script processing through the use of: + +

    +	rundll32 printui.dll,PrintUIEntry /?
+

    + +See the documentation in the Microsoft knowledgebase article no: 189105 referred to above. +

    Chapter17.System and Account Policies

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    April 3 2003

    Table of Contents

    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    With Windows NT4/200x
    With a Samba PDC
    System Startup and Logon Processing Overview

    Creating and Managing System Policies

    +Under MS Windows platforms, particularly those following the release of MS Windows NT4 and MS Windows 95) it is possible to create a type of file that would be placed in the NETLOGON share of a domain controller. As the client logs onto the network this file is read and the contents initiate changes to the registry of the client machine. This file allows changes to be made to those parts of the registry that -affect users, groups of users, or machines.

    For MS Windows 9x/Me this file must be called Config.POL and may -be generated using a tool called poledit.exe, better known as the +affect users, groups of users, or machines. +

    +For MS Windows 9x/Me this file must be called Config.POL and may +be generated using a tool called poledit.exe, better known as the Policy Editor. The policy editor was provided on the Windows 98 installation CD, but dissappeared again with the introduction of MS Windows Me (Millenium Edition). From comments from MS Windows network administrators it would appear that this tool became -a part of the MS Windows Me Resource Kit.

    MS Windows NT4 Server products include the System Policy Editor -under the Start -> Programs -> Administrative Tools menu item. -For MS Windows NT4 and later clients this file must be called NTConfig.POL.

    New with the introduction of MS Windows 2000 was the Microsoft Management Console +a part of the MS Windows Me Resource Kit. +

    +MS Windows NT4 Server products include the System Policy Editor +under the Start -> Programs -> Administrative Tools menu item. +For MS Windows NT4 and later clients this file must be called NTConfig.POL. +

    +New with the introduction of MS Windows 2000 was the Microsoft Management Console or MMC. This tool is the new wave in the ever changing landscape of Microsoft methods for management of network access and security. Every new Microsoft product or technology seems to obsolete the old rules and to introduce newer and more complex tools and methods. To Microsoft's credit though, the MMC does appear to -be a step forward, but improved functionality comes at a great price.

    Before embarking on the configuration of network and system policies it is highly +be a step forward, but improved functionality comes at a great price. +

    +Before embarking on the configuration of network and system policies it is highly advisable to read the documentation available from Microsoft's web site regarding -Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. + +Implementing Profiles and Policies in Windows NT 4.0 from http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp available from Microsoft. There are a large number of documents in addition to this old one that should also -be read and understood. Try searching on the Microsoft web site for "Group Policies".

    What follows is a very brief discussion with some helpful notes. The information provided -here is incomplete - you are warned.

    17.1.1. Windows 9x/Me Policies

    You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. +be read and understood. Try searching on the Microsoft web site for "Group Policies". +

    +What follows is a very brief discussion with some helpful notes. The information provided +here is incomplete - you are warned. +

    Windows 9x/Me Policies

    +You need the Win98 Group Policy Editor to set Group Profiles up under Windows 9x/Me. It can be found on the Original full product Win98 installation CD under -tools/reskit/netadmin/poledit. Install this using the -Add/Remove Programs facility and then click on the 'Have Disk' tab.

    Use the Group Policy Editor to create a policy file that specifies the location of -user profiles and/or the My Documents etc. stuff. Then -save these settings in a file called Config.POL that needs to +tools/reskit/netadmin/poledit. Install this using the +Add/Remove Programs facility and then click on the 'Have Disk' tab. +

    +Use the Group Policy Editor to create a policy file that specifies the location of +user profiles and/or the My Documents etc. stuff. Then +save these settings in a file called Config.POL that needs to be placed in the root of the [NETLOGON] share. If Win98 is configured to log onto the Samba Domain, it will automatically read this file and update the Win9x/Me registry -of the machine as it logs on.

    Further details are covered in the Win98 Resource Kit documentation.

    If you do not take the right steps, then every so often Win9x/Me will check the +of the machine as it logs on. +

    +Further details are covered in the Win98 Resource Kit documentation. +

    +If you do not take the right steps, then every so often Win9x/Me will check the integrity of the registry and will restore it's settings from the back-up copy of the registry it stores on each Win9x/Me machine. Hence, you will -occasionally notice things changing back to the original settings.

    Install the group policy handler for Win9x to pick up group policies. Look on the -Win98 CD in \tools\reskit\netadmin\poledit. +occasionally notice things changing back to the original settings. +

    +Install the group policy handler for Win9x to pick up group policies. Look on the +Win98 CD in \tools\reskit\netadmin\poledit. Install group policies on a Win9x client by double-clicking -grouppol.inf. Log off and on again a couple of times and see +grouppol.inf. Log off and on again a couple of times and see if Win98 picks up group policies. Unfortunately this needs to be done on every -Win9x/Me machine that uses group policies.

    17.1.2. Windows NT4 Style Policy Files

    To create or edit ntconfig.pol you must use the NT Server -Policy Editor, poledit.exe which is included with NT4 Server -but not NT Workstation. There is a Policy Editor on a NT4 -Workstation but it is not suitable for creating Domain Policies. +Win9x/Me machine that uses group policies. +

    Windows NT4 Style Policy Files

    +To create or edit ntconfig.pol you must use the NT Server +Policy Editor, poledit.exe which is included with NT4 Server +but not NT Workstation. There is a Policy Editor on a NT4 +Workstation but it is not suitable for creating Domain Policies. Further, although the Windows 95 Policy Editor can be installed on an NT4 Workstation/Server, it will not work with NT clients. However, the files from -the NT Server will run happily enough on an NT4 Workstation.

    You need poledit.exe, common.adm and winnt.adm. -It is convenient to put the two *.adm files in the c:\winnt\inf +the NT Server will run happily enough on an NT4 Workstation. +

    +You need poledit.exe, common.adm and winnt.adm. +It is convenient to put the two *.adm files in the c:\winnt\inf directory which is where the binary will look for them unless told otherwise. Note also that that -directory is normally 'hidden'.

    The Windows NT policy editor is also included with the Service Pack 3 (and -later) for Windows NT 4.0. Extract the files using servicepackname /x, -i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor, -poledit.exe and the associated template files (*.adm) should +directory is normally 'hidden'. +

    +The Windows NT policy editor is also included with the Service Pack 3 (and +later) for Windows NT 4.0. Extract the files using servicepackname /x, +i.e. that's Nt4sp6ai.exe /x for service pack 6a. The policy editor, +poledit.exe and the associated template files (*.adm) should be extracted as well. It is also possible to downloaded the policy template files for Office97 and get a copy of the policy editor. Another possible -location is with the Zero Administration Kit available for download from Microsoft.

    17.1.2.1. Registry Tattoos

    With NT4 style registry based policy changes, a large number of settings are not +location is with the Zero Administration Kit available for download from Microsoft. +

    Registry Tattoos

    + With NT4 style registry based policy changes, a large number of settings are not automatically reversed as the user logs off. Since the settings that were in the NTConfig.POL file were applied to the client machine registry and that apply to the hive key HKEY_LOCAL_MACHINE are permanent until explicitly reversed. This is known as tattooing. It can have serious consequences down-stream and the administrator must be extremely careful not to lock out the ability to manage the machine at a later date. -

    17.1.3. MS Windows 200x / XP Professional Policies

    Windows NT4 System policies allows setting of registry parameters specific to +

    MS Windows 200x / XP Professional Policies

    +Windows NT4 System policies allows setting of registry parameters specific to users, groups and computers (client workstations) that are members of the NT4 -style domain. Such policy file will work with MS Windows 2000 / XP clients also.

    New to MS Windows 2000 Microsoft introduced a new style of group policy that confers +style domain. Such policy file will work with MS Windows 2000 / XP clients also. +

    +New to MS Windows 2000 Microsoft introduced a new style of group policy that confers a superset of capabilities compared with NT4 style policies. Obviously, the tool used -to create them is different, and the mechanism for implementing them is much changed.

    The older NT4 style registry based policies are known as Administrative Templates +to create them is different, and the mechanism for implementing them is much changed. +

    +The older NT4 style registry based policies are known as Administrative Templates in MS Windows 2000/XP Group Policy Objects (GPOs). The later includes ability to set various security configurations, enforce Internet Explorer browser settings, change and redirect aspects of the -users' desktop (including: the location of My Documents files (directory), as +users' desktop (including: the location of My Documents files (directory), as well as intrinsics of where menu items will appear in the Start menu). An additional new feature is the ability to make available particular software Windows applications to particular -users and/or groups.

    Remember: NT4 policy files are named NTConfig.POL and are stored in the root +users and/or groups. +

    +Remember: NT4 policy files are named NTConfig.POL and are stored in the root of the NETLOGON share on the domain controllers. A Windows NT4 user enters a username, a password and selects the domain name to which the logon will attempt to take place. During the logon process the client machine reads the NTConfig.POL file from the NETLOGON share on the authenticating -server, modifies the local registry values according to the settings in this file.

    Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of +server, modifies the local registry values according to the settings in this file. +

    +Windows 2K GPOs are very feature rich. They are NOT stored in the NETLOGON share, rather part of a Windows 200x policy file is stored in the Active Directory itself and the other part is stored in a shared (and replicated) volume called the SYSVOL folder. This folder is present on all Active Directory domain controllers. The part that is stored in the Active Directory itself is called the group policy container (GPC), and the part that is stored in the replicated share called SYSVOL is -known as the group policy template (GPT).

    With NT4 clients the policy file is read and executed upon only aas each user log onto the network. +known as the group policy template (GPT). +

    +With NT4 clients the policy file is read and executed upon only as each user logs onto the network. MS Windows 200x policies are much more complex - GPOs are processed and applied at client machine startup (machine specific part) and when the user logs onto the network the user specific part is applied. In MS Windows 200x style policy management each machine and/or user may be subject to any number of concurently applicable (and applied) policy sets (GPOs). Active Directory allows the administrator to also set filters over the policy settings. No such equivalent capability -exists with NT4 style policy files.

    17.1.3.1. Administration of Win2K / XP Policies

    Instructions

    Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the +exists with NT4 style policy files. +

    Administration of Win2K / XP Policies

    Administration of Win2K / XP Policies

    +Instead of using the tool called "The System Policy Editor", commonly called Poledit (from the executable name poledit.exe), GPOs are created and managed using a Microsoft Management Console -(MMC) snap-in as follows:

    1. Go to the Windows 200x / XP menu Start->Programs->Administrative Tools - and select the MMC snap-in called "Active Directory Users and Computers"

    2. Select the domain or organizational unit (OU) that you wish to manage, then right click -to open the context menu for that object, select the properties item.

    3. Now left click on the Group Policy tab, then left click on the New tab. Type a name -for the new policy you will create.

    4. Now left click on the Edit tab to commence the steps needed to create the GPO.

    All policy configuration options are controlled through the use of policy administrative +(MMC) snap-in as follows:

    1. +Go to the Windows 200x / XP menu Start->Programs->Administrative Tools + and select the MMC snap-in called "Active Directory Users and Computers" +

    2. +Select the domain or organizational unit (OU) that you wish to manage, then right click +to open the context menu for that object, select the properties item. +

    3. +Now left click on the Group Policy tab, then left click on the New tab. Type a name +for the new policy you will create. +

    4. +Now left click on the Edit tab to commence the steps needed to create the GPO. +

    +All policy configuration options are controlled through the use of policy administrative templates. These files have a .adm extension, both in NT4 as well as in Windows 200x / XP. Beware however, since the .adm files are NOT interchangible across NT4 and Windows 200x. The later introduces many new features as well as extended definition capabilities. It is well beyond the scope of this documentation to explain how to program .adm files, for that the adminsitrator is referred to the Microsoft Windows Resource Kit for your particular -version of MS Windows.

    The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used +version of MS Windows. +

    Note

    +The MS Windows 2000 Resource Kit contains a tool called gpolmig.exe. This tool can be used to migrate an NT4 NTConfig.POL file into a Windows 200x style GPO. Be VERY careful how you -use this powerful tool. Please refer to the resource kit manuals for specific usage information.

    17.2. Managing Account/User Policies

    Policies can define a specific user's settings or the settings for a group of users. The resulting +use this powerful tool. Please refer to the resource kit manuals for specific usage information. +

    Managing Account/User Policies

    +Policies can define a specific user's settings or the settings for a group of users. The resulting policy file contains the registry settings for all users, groups, and computers that will be using -the policy file. Separate policy files for each user, group, or computer are not not necessary.

    If you create a policy that will be automatically downloaded from validating domain controllers, +the policy file. Separate policy files for each user, group, or computer are not not necessary. +

    +If you create a policy that will be automatically downloaded from validating domain controllers, you should name the file NTconfig.POL. As system administrator, you have the option of renaming the policy file and, by modifying the Windows NT-based workstation, directing the computer to update the policy from a manual path. You can do this by either manually changing the registry or by using the System Policy Editor. This path can even be a local path such that each machine has its own policy file, -but if a change is necessary to all machines, this change must be made individually to each workstation.

    When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain +but if a change is necessary to all machines, this change must be made individually to each workstation. +

    +When a Windows NT4/200x/XP machine logs onto the network the NETLOGON share on the authenticating domain controller for the presence of the NTConfig.POL file. If one exists it is downloaded, parsed and then -applied to the user's part of the registry.

    MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, +applied to the user's part of the registry. +

    +MS Windows 200x/XP clients that log onto an MS Windows Active Directory security domain may additionally, acquire policy settings through Group Policy Objects (GPOs) that are defined and stored in Active Directory -itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect. -This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates.

    Inaddition to user access controls that may be imposed or applied via system and/or group policies +itself. The key benefit of using AS GPOs is that they impose no registry tatooing effect. +This has considerable advanage compared with the use of NTConfig.POL (NT4) style policy updates. +

    +In addition to user access controls that may be imposed or applied via system and/or group policies in a manner that works in conjunction with user profiles, the user management environment under MS Windows NT4/200x/XP allows per domain as well as per user account restrictions to be applied. -Common restrictions that are frequently used includes:

    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    17.2.1. With Windows NT4/200x

    The tools that may be used to configure these types of controls from the MS Windows environment are: +Common restrictions that are frequently used includes: +

    +

    Logon Hours
    Password Aging
    Permitted Logon from certain machines only
    Account type (Local or Global)
    User Rights

    +

    With Windows NT4/200x

    +The tools that may be used to configure these types of controls from the MS Windows environment are: The NT4 User Manager for domains, the NT4 System and Group Policy Editor, the registry editor (regedt32.exe). Under MS Windows 200x/XP this is done using the Microsoft Managment Console (MMC) with approapriate -"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor.

    17.2.2. With a Samba PDC

    With a Samba Domain Controller, the new tools for managing of user account and policy information includes: -smbpasswd, pdbedit, smbgroupedit, net, rpcclient.. The administrator should read the -man pages for these tools and become familiar with their use.

    17.3. System Startup and Logon Processing Overview

    The following attempts to document the order of processing of system and user policies following a system -reboot and as part of the user logon:

    1. Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming +"snap-ins", the registry editor, and potentially also the NT4 System and Group Policy Editor. +

    With a Samba PDC

    +With a Samba Domain Controller, the new tools for managing of user account and policy information includes: +smbpasswd, pdbedit, net, rpcclient.. The administrator should read the +man pages for these tools and become familiar with their use. +

    System Startup and Logon Processing Overview

    +The following attempts to document the order of processing of system and user policies following a system +reboot and as part of the user logon: +

    1. + Network starts, then Remote Procedure Call System Service (RPCSS) and Multiple Universal Naming Convention Provider (MUP) start -

    2. Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded +

    3. + Where Active Directory is involved, an ordered list of Group Policy Objects (GPOs) is downloaded and applied. The list may include GPOs that: -

      Apply to the location of machines in a Directory
      Apply only when settings have changed
      Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

      +

      Apply to the location of machines in a Directory
      Apply only when settings have changed
      Depend on configuration of scope of applicability: local, site, domain, organizational unit, etc.

      No desktop user interface is presented until the above have been processed. -

    4. Execution of start-up scripts (hidden and synchronous by defaut). -

    5. A keyboard action to affect start of logon (Ctrl-Alt-Del). -

    6. User credentials are validated, User profile is loaded (depends on policy settings). -

    7. An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: +

    8. + Execution of start-up scripts (hidden and synchronous by defaut). +

    9. + A keyboard action to affect start of logon (Ctrl-Alt-Del). +

    10. + User credentials are validated, User profile is loaded (depends on policy settings). +

    11. + An ordered list of User GPOs is obtained. The list contents depends on what is configured in respsect of: -

      Is user a domain member, thus subject to particular policies
      Loopback enablement, and the state of the loopback policy (Merge or Replace)
      Location of the Active Directory itself
      Has the list of GPOs changed. No processing is needed if not changed.

      -

    12. User Policies are applied from Active Directory. Note: There are several types. -

    13. Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group +

      Is user a domain member, thus subject to particular policies
      Loopback enablement, and the state of the loopback policy (Merge or Replace)
      Location of the Active Directory itself
      Has the list of GPOs changed. No processing is needed if not changed.

      +

    14. + User Policies are applied from Active Directory. Note: There are several types. +

    15. + Logon scripts are run. New to Win2K and Active Directory, logon scripts may be obtained based on Group Policy objects (hidden and executed synchronously). NT4 style logon scripts are then run in a normal window. -

    16. The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 +

    17. + The User Interface as determined from the GPOs is presented. Note: In a Samba domain (like and NT4 Domain) machine (system) policies are applied at start-up, User policies are applied at logon. -

    Chapter 18. Desktop Profile Management

    18.1. Roaming Profiles

    Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

    Before discussing how to configure roaming profiles, it is useful to see how -Windows 9x / Me and Windows NT4/200x clients implement these features.

    Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's +

    Chapter18.Desktop Profile Management

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    April 3 2003

    Table of Contents

    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP

    Roaming Profiles

    Warning

    +Roaming profiles support is different for Win9x / Me and Windows NT4/200x. +

    +Before discussing how to configure roaming profiles, it is useful to see how +Windows 9x / Me and Windows NT4/200x clients implement these features. +

    +Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate profiles location field, only the user's home share. This means that Win9X/Me -profiles are restricted to being stored in the user's home directory.

    Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, -including a separate field for the location of the user's profiles.

    18.1.1. Samba Configuration for Profile Handling

    This section documents how to configure Samba for MS Windows client profile support.

    18.1.1.1. NT4/200x User Profiles

    To support Windowns NT4/200x clients, in the [global] section of smb.conf set the -following (for example):

    	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
    +profiles are restricted to being stored in the user's home directory. +

    +Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, +including a separate field for the location of the user's profiles. +

    Samba Configuration for Profile Handling

    +This section documents how to configure Samba for MS Windows client profile support. +

    NT4/200x User Profiles

    +To support Windowns NT4/200x clients, in the [global] section of smb.conf set the +following (for example): +

    +

    +	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
+

    This is typically implemented like: -

    		logon path = \\%L\Profiles\%u
    -where %L translates to the name of the Samba server and %u translates to the user name

    The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. +

    +		logon path = \\%L\Profiles\%u
+

    +where %L translates to the name of the Samba server and %u translates to the user name +

    +The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile. The \\N%\%U service is created automatically by the [homes] service. If you are using a samba server for the profiles, you _must_ make the share specified in the logon path browseable. Please refer to the man page for smb.conf in respect of the different -symantics of %L and %N, as well as %U and %u.

    MS Windows NT/2K clients at times do not disconnect a connection to a server -between logons. It is recommended to NOT use the homes -meta-service name as part of the profile share path.

    18.1.1.2. Windows 9x / Me User Profiles

    To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has -now been fixed so that net use /home now works as well, and it, too, relies -on the logon home parameter.

    By using the logon home parameter, you are restricted to putting Win9x / Me +symantics of %L and %N, as well as %U and %u. +

    Note

    +MS Windows NT/2K clients at times do not disconnect a connection to a server +between logons. It is recommended to NOT use the homes +meta-service name as part of the profile share path. +

    Windows 9x / Me User Profiles

    +To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has +now been fixed so that net use /home now works as well, and it, too, relies +on the logon home parameter. +

    +By using the logon home parameter, you are restricted to putting Win9x / Me profiles in the user's home directory. But wait! There is a trick you -can use. If you set the following in the [global] section of your smb.conf file:

    	logon home = \\%L\%U\.profiles

    then your Windows 9x / Me clients will dutifully put their clients in a subdirectory -of your home directory called .profiles (thus making them hidden).

    Not only that, but net use/home will also work, because of a feature in +can use. If you set the following in the [global] section of your smb.conf file: +

    +	logon home = \\%L\%U\.profiles
+

    +then your Windows 9x / Me clients will dutifully put their clients in a subdirectory +of your home directory called .profiles (thus making them hidden). +

    +Not only that, but net use /home will also work, because of a feature in Windows 9x / Me. It removes any directory stuff off the end of the home directory area and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for logon home.

    18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example:

    	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u

    18.1.2. Windows Client Profile Configuration Information

    18.1.2.1. Windows 9x / Me Profile Setup

    When a user first logs in on Windows 9X, the file user.DAT is created, -as are folders "Start Menu", "Desktop", "Programs" and "Nethood". +specified \\%L\%U for logon home. +

    Mixed Windows 9x / Me and Windows NT4/200x User Profiles

    +You can support profiles for both Win9X and WinNT clients by setting both the +logon home and logon path parameters. For example: +

    +	logon home = \\%L\%u\.profiles
+	logon path = \\%L\profiles\%u
+

    Disabling Roaming Profile Support

    +A question often asked is "How may I enforce use of local profiles?" or +"How do I disable Roaming Profiles?" +

    +There are three ways of doing this: +

    • + In smb.conf: affect the following settings and ALL clients + will be forced to use a local profile: + 

      +		logon home =
+		logon path =
+

    • + MS Windows Registry: by using the Microsoft Management Console + gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This + of course modifies registry settings. The full path to the option is: + 

      +	Local Computer Policy\
+		Computer Configuration\
+			Administrative Templates\
+				System\
+					User Profiles\
+
+	Disable:	Only Allow Local User Profiles
+	Disable:	Prevent Roaming Profile Change from Propogating to the Server
+

      +

    • + Change of Profile Type: From the start menu right click on the + MY Computer icon, select Properties, click on the "User Profiles + tab, select the profile you wish to change from Roaming type to Local, click Change Type. +

    +Consult the MS Windows registry guide for your particular MS Windows version for more +information about which registry keys to change to enforce use of only local user +profiles. +

    Note

    +The specifics of how to convert a local profile to a roaming profile, or a roaming profile +to a local one vary according to the version of MS Windows you are running. Consult the +Microsoft MS Windows Resource Kit for your version of Windows for specific information. +

    Windows Client Profile Configuration Information

    Windows 9x / Me Profile Setup

    +When a user first logs in on Windows 9X, the file user.DAT is created, +as are folders "Start Menu", "Desktop", "Programs" and "Nethood". These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short preserve case = yes" and -"case sensitive = no" in order to maintain capital letters in shortcuts -in any of the profile folders.

    The user.DAT file contains all the user's preferences. If you wish to +options "preserve case = yes", "short preserve case = yes" and +"case sensitive = no" in order to maintain capital letters in shortcuts +in any of the profile folders. +

    +The user.DAT file contains all the user's preferences. If you wish to enforce a set of preferences, rename their user.DAT file to user.MAN, -and deny them write access to this file.

    1. On the Windows 9x / Me machine, go to Control Panel -> Passwords and +and deny them write access to this file. +

      1. + On the Windows 9x / Me machine, go to Control Panel -> Passwords and select the User Profiles tab. Select the required level of roaming preferences. Press OK, but do _not_ allow the computer to reboot. -

      2. On the Windows 9x / Me machine, go to Control Panel -> Network -> - Client for Microsoft Networks -> Preferences. Select 'Log on to +

      3. + On the Windows 9x / Me machine, go to Control Panel -> Network -> + Client for Microsoft Networks -> Preferences. Select 'Log on to NT Domain'. Then, ensure that the Primary Logon is 'Client for Microsoft Networks'. Press OK, and this time allow the computer to reboot. -

      Under Windows 9x / Me Profiles are downloaded from the Primary Logon. +

    +Under Windows 9x / Me Profiles are downloaded from the Primary Logon. If you have the Primary Logon as 'Client for Novell Networks', then the profiles and logon script will be downloaded from your Novell Server. If you have the Primary Logon as 'Windows Logon', then the profiles will be loaded from the local machine - a bit against the -concept of roaming profiles, it would seem!

    You will now find that the Microsoft Networks Login box contains +concept of roaming profiles, it would seem! +

    +You will now find that the Microsoft Networks Login box contains [user, password, domain] instead of just [user, password]. Type in the samba server's domain name (or any other domain known to exist, but bear in mind that the user will be authenticated against this domain and profiles downloaded from it, if that domain logon server -supports it), user name and user's password.

    Once the user has been successfully validated, the Windows 9x / Me machine +supports it), user name and user's password. +

    +Once the user has been successfully validated, the Windows 9x / Me machine will inform you that 'The user has not logged on before' and asks you -if you wish to save the user's preferences? Select 'yes'.

    Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the "logon path" -on the samba server and verify that the "Desktop", "Start Menu", -"Programs" and "Nethood" folders have been created.

    These folders will be cached locally on the client, and updated when +if you wish to save the user's preferences? Select 'yes'. +

    +Once the Windows 9x / Me client comes up with the desktop, you should be able +to examine the contents of the directory specified in the "logon path" +on the samba server and verify that the "Desktop", "Start Menu", +"Programs" and "Nethood" folders have been created. +

    +These folders will be cached locally on the client, and updated when the user logs off (if you haven't made them read-only by then). You will find that if the user creates further folders or short-cuts, that the client will merge the profile contents downloaded with the contents of the profile directory already on the local client, taking -the newest folders and short-cuts from each set.

    If you have made the folders / files read-only on the samba server, +the newest folders and short-cuts from each set. +

    +If you have made the folders / files read-only on the samba server, then you will get errors from the Windows 9x / Me machine on logon and logout, as it attempts to merge the local and the remote profile. Basically, if you have any errors reported by the Windows 9x / Me machine, check the Unix file permissions and ownership rights on the profile directory contents, -on the samba server.

    If you have problems creating user profiles, you can reset the user's +on the samba server. +

    +If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below. When this user then next logs in, -they will be told that they are logging in "for the first time".

    1. instead of logging in under the [user, password, domain] dialog, +they will be told that they are logging in "for the first time". +

      1. + instead of logging in under the [user, password, domain] dialog, press escape. -

      2. run the regedit.exe program, and look in: -

        HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList -

        you will find an entry, for each user, of ProfilePath. Note the +

      3. + run the regedit.exe program, and look in: +

        + HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList +

        + you will find an entry, for each user, of ProfilePath. Note the contents of this key (likely to be c:\windows\profiles\username), then delete the key ProfilePath for the required user. [Exit the registry editor]. -

      4. WARNING - before deleting the contents of the +

      5. + WARNING - before deleting the contents of the directory listed in the ProfilePath (this is likely to be - c:\windows\profiles\username), ask them if they + c:\windows\profiles\username), ask them if they have any important files stored on their desktop or in their start menu. Delete the contents of the directory ProfilePath (making a backup if any of the files are needed). -

        This will have the effect of removing the local (read-only hidden +

        + This will have the effect of removing the local (read-only hidden system file) user.DAT in their profile directory, as well as the - local "desktop", "nethood", "start menu" and "programs" folders. -

      6. search for the user's .PWL password-caching file in the c:\windows + local "desktop", "nethood", "start menu" and "programs" folders. +

      7. + search for the user's .PWL password-caching file in the c:\windows directory, and delete it. -

      8. log off the windows 9x / Me client. -

      9. check the contents of the profile path (see "logon path" described +

      10. + log off the windows 9x / Me client. +

      11. + check the contents of the profile path (see "logon path" described above), and delete the user.DAT or user.MAN file for the user, making a backup if required. -

      If all else fails, increase samba's debug log levels to between 3 and 10, +

    +If all else fails, increase samba's debug log levels to between 3 and 10, and / or run a packet trace program such as ethereal or netmon.exe, and -look for error messages.

    If you have access to an Windows NT4/200x server, then first set up roaming profiles +look for error messages. +

    +If you have access to an Windows NT4/200x server, then first set up roaming profiles and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces provided with Windows NT4/200x server, and see what the -differences are with the equivalent samba trace.

    18.1.2.2. Windows NT4 Workstation

    When a user first logs in to a Windows NT Workstation, the profile +differences are with the equivalent samba trace. +

    Windows NT4 Workstation

    +When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified -through the "logon path" parameter.

    There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to H: or any other drive, and -should be used in conjunction with the new "logon home" parameter.

    The entry for the NT4 profile is a _directory_ not a file. The NT +through the "logon path" parameter. +

    +There is a parameter that is now available for use with NT Profiles: +"logon drive". This should be set to H: or any other drive, and +should be used in conjunction with the new "logon home" parameter. +

    +The entry for the NT4 profile is a _directory_ not a file. The NT help on profiles mentions that a directory is also created with a .PDS extension. The user, while logging in, must have write permission to create the full profile path (and the folder with the .PDS extension -for those situations where it might be created.)

    In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -It creates "Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file +for those situations where it might be created.) +

    +In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. +It creates "Application Data" and others, as well as "Desktop", "Nethood", +"Start Menu" and "Programs". The profile itself is stored in a file NTuser.DAT. Nothing appears to be stored in the .PDS directory, and -its purpose is currently unknown.

    You can use the System Control Panel to copy a local profile onto +its purpose is currently unknown. +

    +You can use the System Control Panel to copy a local profile onto a samba server (see NT Help on profiles: it is also capable of firing up the correct location in the System Control Panel for you). The NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN -turns a profile into a mandatory one.

    The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN.

    18.1.2.3. Windows 2000/XP Professional

    You must first convert the profile from a local profile to a domain -profile on the MS Windows workstation as follows:

    • Log on as the LOCAL workstation administrator. -

    • Right click on the 'My Computer' Icon, select 'Properties' -

    • Click on the 'User Profiles' tab -

    • Select the profile you wish to convert (click on it once) -

    • Click on the button 'Copy To' -

    • In the "Permitted to use" box, click on the 'Change' button. -

    • Click on the 'Look in" area that lists the machine name, when you click +turns a profile into a mandatory one. +

      +The case of the profile is significant. The file must be called +NTuser.DAT or, for a mandatory profile, NTuser.MAN. +

    Windows 2000/XP Professional

    +You must first convert the profile from a local profile to a domain +profile on the MS Windows workstation as follows: +

    • + Log on as the LOCAL workstation administrator. +

    • + Right click on the 'My Computer' Icon, select 'Properties' +

    • + Click on the 'User Profiles' tab +

    • + Select the profile you wish to convert (click on it once) +

    • + Click on the button 'Copy To' +

    • + In the "Permitted to use" box, click on the 'Change' button. +

    • + Click on the 'Look in" area that lists the machine name, when you click here it will open up a selection box. Click on the domain to which the profile must be accessible. -

      You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.

    • To make the profile capable of being used by anyone select 'Everyone' -

    • Click OK. The Selection box will close. -

    • Now click on the 'Ok' button to create the profile in the path you +

      Note

      You will need to log on if a logon box opens up. Eg: In the connect + as: MIDEARTH\root, password: mypassword.

    • + To make the profile capable of being used by anyone select 'Everyone' +

    • + Click OK. The Selection box will close. +

    • + Now click on the 'Ok' button to create the profile in the path you nominated. -

    Done. You now have a profile that can be editted using the samba-3.0.0 -profiles tool.

    Under NT/2K the use of mandotory profiles forces the use of MS Exchange -storage of mail data. That keeps desktop profiles usable.

    • This is a security check new to Windows XP (or maybe only +

    +Done. You now have a profile that can be editted using the samba-3.0.0 +profiles tool. +

    Note

    +Under NT/2K the use of mandotory profiles forces the use of MS Exchange +storage of mail data. That keeps desktop profiles usable. +

    Note

    • +This is a security check new to Windows XP (or maybe only Windows XP service pack 1). It can be disabled via a group policy in -Active Directory. The policy is:

      "Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders"

      ...and it should be set to "Enabled". +Active Directory. The policy is:

      "Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders"

      ...and it should be set to "Enabled". Does the new version of samba have an Active Directory analogue? If so, -then you may be able to set the policy through this.

      If you cannot set group policies in samba, then you may be able to set +then you may be able to set the policy through this. +

      +If you cannot set group policies in samba, then you may be able to set the policy locally on each machine. If you want to try this, then do the following (N.B. I don't know for sure that this will work in the -same way as a domain group policy):

    • On the XP workstation log in with an Administrator account.

    • Click: "Start", "Run"

    • Type: "mmc"

    • Click: "OK"

    • A Microsoft Management Console should appear.

    • Click: File, "Add/Remove Snap-in...", "Add"

    • Double-Click: "Group Policy"

    • Click: "Finish", "Close"

    • Click: "OK"

    • In the "Console Root" window:

    • Expand: "Local Computer Policy", "Computer Configuration",

    • "Administrative Templates", "System", "User Profiles"

    • Double-Click: "Do not check for user ownership of Roaming Profile

    • Folders"

    • Select: "Enabled"

    • Click: OK"

    • Close the whole console. You do not need to save the settings (this +same way as a domain group policy): +

    • +On the XP workstation log in with an Administrator account. +

    • Click: "Start", "Run"

    • Type: "mmc"

    • Click: "OK"

    • A Microsoft Management Console should appear.

    • Click: File, "Add/Remove Snap-in...", "Add"

    • Double-Click: "Group Policy"

    • Click: "Finish", "Close"

    • Click: "OK"

    • In the "Console Root" window:

    • Expand: "Local Computer Policy", "Computer Configuration",

    • "Administrative Templates", "System", "User Profiles"

    • Double-Click: "Do not check for user ownership of Roaming Profile

    • Folders"

    • Select: "Enabled"

    • Click: OK"

    • Close the whole console. You do not need to save the settings (this refers to the console settings rather than the policies you have - changed).

    • Reboot

    18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    Sharing of desktop profiles between Windows versions is NOT recommended. + changed).

  • Reboot

    • Sharing Profiles between W9x/Me and NT4/200x/XP workstations

    +Sharing of desktop profiles between Windows versions is NOT recommended. Desktop profiles are an evolving phenomenon and profiles for later versions of MS Windows clients add features that may interfere with earlier versions of MS Windows clients. Probably the more salient reason to NOT mix profiles is that when logging off an earlier version of MS Windows the older format of profile contents may overwrite information that belongs to the newer version resulting in loss of profile information content when that user logs -on again with the newer version of MS Windows.

    If you then want to share the same Start Menu / Desktop with W9x/Me, you will +on again with the newer version of MS Windows. +

    +If you then want to share the same Start Menu / Desktop with W9x/Me, you will need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home.

    If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory.

    18.1.4. Profile Migration from Windows NT4/200x Server to Samba

    There is nothing to stop you specifying any path that you like for the +that need to be common are logon path and +logon home. +

    +If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory. +

    Profile Migration from Windows NT4/200x Server to Samba

    +There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the profile be stored on a samba server, or any other SMB server, as long as -that SMB server supports encrypted passwords.

    18.1.4.1. Windows NT4 Profile Management Tools

    Unfortunately, the Resource Kit information is specific to the version of MS Windows -NT4/200x. The correct resource kit is required for each platform.

    Here is a quick guide:

    • On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'.

    • Select a user profile you want to migrate and click on it.

      I am using the term "migrate" lossely. You can copy a profile to +that SMB server supports encrypted passwords. +

      Windows NT4 Profile Management Tools

      +Unfortunately, the Resource Kit information is specific to the version of MS Windows +NT4/200x. The correct resource kit is required for each platform. +

      +Here is a quick guide: +

      • +On your NT4 Domain Controller, right click on 'My Computer', then +select the tab labelled 'User Profiles'. +

      • +Select a user profile you want to migrate and click on it. +

        Note

        I am using the term "migrate" lossely. You can copy a profile to create a group profile. You can give the user 'Everyone' rights to the profile you copy this to. That is what you need to do, since your samba -domain is not a member of a trust relationship with your NT4 PDC.

    • Click the 'Copy To' button.

    • In the box labelled 'Copy Profile to' add your new path, eg: - c:\temp\foobar

    • Click on the button labelled 'Change' in the "Permitted to use" box.

    • Click on the group 'Everyone' and then click OK. This closes the - 'chose user' box.

    • Now click OK.

    Follow the above for every profile you need to migrate.

    18.1.4.2. Side bar Notes

    You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

    With Samba-3.0.0 alpha code you can import all you NT4 domain accounts +domain is not a member of a trust relationship with your NT4 PDC.

  • Click the 'Copy To' button.

  • In the box labelled 'Copy Profile to' add your new path, eg: + c:\temp\foobar

  • Click on the button labelled 'Change' in the "Permitted to use" box.

  • Click on the group 'Everyone' and then click OK. This closes the + 'chose user' box.

  • Now click OK.

    • +Follow the above for every profile you need to migrate. +

    Side bar Notes

    +You should obtain the SID of your NT4 domain. You can use smbpasswd to do +this. Read the man page.

    +With Samba-3.0.0 alpha code you can import all you NT4 domain accounts using the net samsync method. This way you can retain your profile -settings as well as all your users.

    18.1.4.3. moveuser.exe

    The W2K professional resource kit has moveuser.exe. moveuser.exe changes +settings as well as all your users. +

    moveuser.exe

    +The W2K professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account -domain to change, and/or the user name to change.

    18.1.4.4. Get SID

    You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 -Resource Kit.

    Windows NT 4.0 stores the local profile information in the registry under +domain to change, and/or the user name to change. +

    Get SID

    +You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 +Resource Kit. +

    +Windows NT 4.0 stores the local profile information in the registry under the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    Under the ProfileList key, there will be subkeys named with the SIDs of the +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList +

    +Under the ProfileList key, there will be subkeys named with the SIDs of the users who have logged on to this computer. (To find the profile information for the user whose locally cached profile you want to move, find the SID for the user with the GetSID.exe utility.) Inside of the appropriate user's -subkey, you will see a string value named ProfileImagePath.

    18.2. Mandatory profiles

    A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. +subkey, you will see a string value named ProfileImagePath. +

    Mandatory profiles

    +A Mandatory Profile is a profile that the user does NOT have the ability to overwrite. During the user's session it may be possible to change the desktop environment, but as the user logs out all changes made will be lost. If it is desired to NOT allow the user any ability to change the desktop environment then this must be done through -policy settings. See previous chapter.

    Under NO circumstances should the profile directory (or it's contents) be made read-only -as this may render the profile un-usable.

    For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles +policy settings. See previous chapter. +

    Note

    +Under NO circumstances should the profile directory (or it's contents) be made read-only +as this may render the profile un-usable. +

    +For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT -file in the copied profile and rename it to NTUser.MAN.

    For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to -affect a mandatory profile.

    18.3. Creating/Managing Group Profiles

    Most organisations are arranged into departments. There is a nice benenfit in +file in the copied profile and rename it to NTUser.MAN. +

    +For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to +affect a mandatory profile. +

    Creating/Managing Group Profiles

    +Most organisations are arranged into departments. There is a nice benenfit in this fact since usually most users in a department will require the same desktop applications and the same desktop layout. MS Windows NT4/200x/XP will allow the use of Group Profiles. A Group Profile is a profile that is created firstly using a template (example) user. Then using the profile migration tool (see above) the profile is assigned access rights for the user group that needs to be given access -to the group profile.

    The next step is rather important. PLEASE NOTE: Instead of assigning a group profile -to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned -the now modified profile.

    Be careful with group profiles, if the user who is a member of a group also +to the group profile. +

    +The next step is rather important. PLEASE NOTE: Instead of assigning a group profile +to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned +the now modified profile. +

    Note

    + Be careful with group profiles, if the user who is a member of a group also has a personal profile, then the result will be a fusion (merge) of the two. -

    18.4. Default Profile for Windows Users

    MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom +

    Default Profile for Windows Users

    +MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom a profile does not already exist. Armed with a knowledge of where the default profile is located on the Windows workstation, and knowing which registry keys affect the path from which the default profile is created, it is possible to modify the default profile to one that has been optimised for the site. This has significant administrative -advantages.

    18.4.1. MS Windows 9x/Me

    To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly.

    To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes.

    To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive -HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name -"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.

    18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?

    When a user logs on to a Windows 9x / Me machine, the local profile path, -HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked -for an existing entry for that user:

    If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached +advantages. +

    MS Windows 9x/Me

    +To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System +Policy Editor or change the registry directly. +

    +To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then +select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, +select User Profiles, click on the enable box. Do not forget to save the registry changes. +

    +To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive +HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name +"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. +

    How User Profiles Are Handled in Windows 9x / Me?

    +When a user logs on to a Windows 9x / Me machine, the local profile path, +HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked +for an existing entry for that user: +

    +If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached version of the user profile. Windows 9x / Me also checks the user's home directory (or other specified directory if the location has been modified) on the server for the User Profile. If a profile exists in both locations, the newer of the two is used. If the User Profile exists on the server, but does not exist on the local machine, the profile on the server is downloaded -and used. If the User Profile only exists on the local machine, that copy is used.

    If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me +and used. If the User Profile only exists on the local machine, that copy is used. +

    +If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me machine is used and is copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user's local profile. If the user has a roaming -profile, the changes are written to the user's profile on the server.

    18.4.2. MS Windows NT4 Workstation

    On MS Windows NT4 the default user profile is obtained from the location -%SystemRoot%\Profiles which in a default installation will translate to -C:\WinNT\Profiles. Under this directory on a clean install there will be -three (3) directories: Administrator, All Users, Default User.

    The All Users directory contains menu settings that are common across all -system users. The Default User directory contains menu entries that are -customisable per user depending on the profile settings chosen/created.

    When a new user first logs onto an MS Windows NT4 machine a new profile is created from:

    All Users settings
    Default User settings (contains the default NTUser.DAT file)

    When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain -the following steps are followed in respect of profile handling:

    1. The users' account information which is obtained during the logon process contains +profile, the changes are written to the user's profile on the server. +

    MS Windows NT4 Workstation

    +On MS Windows NT4 the default user profile is obtained from the location +%SystemRoot%\Profiles which in a default installation will translate to +C:\WinNT\Profiles. Under this directory on a clean install there will be +three (3) directories: Administrator, All Users, Default User. +

    +The All Users directory contains menu settings that are common across all +system users. The Default User directory contains menu entries that are +customisable per user depending on the profile settings chosen/created. +

    +When a new user first logs onto an MS Windows NT4 machine a new profile is created from: +

    All Users settings
    Default User settings (contains the default NTUser.DAT file)

    +When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain +the following steps are followed in respect of profile handling: +

    1. + The users' account information which is obtained during the logon process contains the location of the users' desktop profile. The profile path may be local to the machine or it may be located on a network share. If there exists a profile at the location of the path from the user account, then this profile is copied to the location - %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the - settings in the All Users profile in the %SystemRoot%\Profiles + %SystemRoot%\Profiles\%USERNAME%. This profile then inherits the + settings in the All Users profile in the %SystemRoot%\Profiles location. -

    2. If the user account has a profile path, but at it's location a profile does not exist, - then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% - directory from reading the Default User profile. -

    3. If the NETLOGON share on the authenticating server (logon server) contains a policy file - (NTConfig.POL) then it's contents are applied to the NTUser.DAT - which is applied to the HKEY_CURRENT_USER part of the registry. -

    4. When the user logs out, if the profile is set to be a roaming profile it will be written - out to the location of the profile. The NTuser.DAT file is then - re-created from the contents of the HKEY_CURRENT_USER contents. - Thus, should there not exist in the NETLOGON share an NTConfig.POL at the - next logon, the effect of the provious NTConfig.POL will still be held - in the profile. The effect of this is known as tatooing. -

    MS Windows NT4 profiles may be Local or Roaming. A Local profile -will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will -also remain stored in the same way, unless the following registry key is created:

    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
    +

  • + If the user account has a profile path, but at it's location a profile does not exist, + then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% + directory from reading the Default User profile. +

  • + If the NETLOGON share on the authenticating server (logon server) contains a policy file + (NTConfig.POL) then it's contents are applied to the NTUser.DAT + which is applied to the HKEY_CURRENT_USER part of the registry. +

  • + When the user logs out, if the profile is set to be a roaming profile it will be written + out to the location of the profile. The NTuser.DAT file is then + re-created from the contents of the HKEY_CURRENT_USER contents. + Thus, should there not exist in the NETLOGON share an NTConfig.POL at the + next logon, the effect of the provious NTConfig.POL will still be held + in the profile. The effect of this is known as tatooing. +

    • +MS Windows NT4 profiles may be Local or Roaming. A Local profile +will stored in the %SystemRoot%\Profiles\%USERNAME% location. A roaming profile will +also remain stored in the same way, unless the following registry key is created: +

    +

    +	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001
+

    -In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be -deleted on logout.

    Under MS Windows NT4 default locations for common resources (like My Documents +In which case, the local copy (in %SystemRoot%\Profiles\%USERNAME%) will be +deleted on logout. +

    +Under MS Windows NT4 default locations for common resources (like My Documents may be redirected to a network share by modifying the following registry keys. These changes may be affected via use of the System Policy Editor (to do so may require that you create your owns template extension for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first -creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.

    The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows NT4 is:

            HKEY_CURRENT_USER
+creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.
+
    
+The Registry Hive key that affects the behaviour of folders that are part of the default user profile
+are controlled by entries on Windows NT4 is:
+
    
+
    +        HKEY_CURRENT_USER
                 \Software
                         \Microsoft
                                 \Windows
                                         \CurrentVersion
                                                 \Explorer
-                                                        \User Shell Folders\
    The above hive key contains a list of automatically managed folders. The default entries are:
            
            Name            Default Value
+                                                        \User Shell Folders\
+
    
+
    
+The above hive key contains a list of automatically managed folders. The default entries are:
+
    
+        
    +        Name            Default Value
         --------------  -----------------------------------------
         AppData         %USERPROFILE%\Application Data
         Desktop         %USERPROFILE%\Desktop
@@ -15417,180 +6504,87 @@ CLASS="PROGRAMLISTING"
         SendTo          %USERPROFILE%\SendTo
         Start Menu      %USERPROFILE%\Start Menu
         Startup         %USERPROFILE%\Start Menu\Programs\Startup
-        
    
-        
    The registry key that contains the location of the default profile settings is:
+

    +

    +The registry key that contains the location of the default profile settings is: -

    	HKEY_LOCAL_MACHINE
+
    +	HKEY_LOCAL_MACHINE
 		\SOFTWARE
 			\Microsoft
 				\Windows
 					\CurrentVersion
 						\Explorer
-							\User Shell Folders
    
+							\User Shell Folders
+

    The default entries are: -

    	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
+
    +	Common Desktop		%SystemRoot%\Profiles\All Users\Desktop
 	Common Programs		%SystemRoot%\Profiles\All Users\Programs
 	Common Start Menu	%SystemRoot%\Profiles\All Users\Start Menu
-	Common Startu	p	%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup

    18.4.3. MS Windows 200x/XP

    MS Windows XP Home Edition does use default per user profiles, but can not participate + Common Startup %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup +

    +

    MS Windows 200x/XP

    Note

    + MS Windows XP Home Edition does use default per user profiles, but can not participate in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile only from itself. While there are benefits in doing this the beauty of those MS Windows clients that CAN participate in domain logon processes allows the administrator to create a global default profile and to enforce it through the use of Group Policy Objects (GPOs). -

    When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from -C:\Documents and Settings\Default User. The administrator can modify (or change -the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum +

    +When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from +C:\Documents and Settings\Default User. The administrator can modify (or change +the contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client -workstation.

    When MS Windows 200x/XP participate in a domain security context, and if the default user +workstation. +

    +When MS Windows 200x/XP participate in a domain security context, and if the default user profile is not found, then the client will search for a default profile in the NETLOGON share of the authenticating server. ie: In MS Windows parlance: -%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this -to the workstation to the C:\Documents and Settings\ under the Windows -login name of the user.

    This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory - should be created at the root of this share and msut be called Default Profile. -

    If a default profile does not exist in this location then MS Windows 200x/XP will use the local -default profile.

    On loging out, the users' desktop profile will be stored to the location specified in the registry +%LOGONSERVER%\NETLOGON\Default User and if one exits there it will copy this +to the workstation to the C:\Documents and Settings\ under the Windows +login name of the user. +

    Note

    + This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory + should be created at the root of this share and must be called Default Profile. +

    +If a default profile does not exist in this location then MS Windows 200x/XP will use the local +default profile. +

    +On loging out, the users' desktop profile will be stored to the location specified in the registry settings that pertain to the user. If no specific policies have been created, or passed to the client during the login process (as Samba does automatically), then the user's profile will be written to -the local machine only under the path C:\Documents and Settings\%USERNAME%.

    Those wishing to modify the default behaviour can do so through up to three methods:

    • Modify the registry keys on the local machine manually and place the new default profile in the +the local machine only under the path C:\Documents and Settings\%USERNAME%. +

      +Those wishing to modify the default behaviour can do so through three methods: +

      • + Modify the registry keys on the local machine manually and place the new default profile in the NETLOGON share root - NOT recommended as it is maintenance intensive. -

      • Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file +

      • + Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file in the root of the NETLOGON share along with the new default profile. -

      • Create a GPO that enforces this through Active Directory, and place the new default profile +

      • + Create a GPO that enforces this through Active Directory, and place the new default profile in the NETLOGON share. -

      The Registry Hive key that affects the behaviour of folders that are part of the default user profile -are controlled by entries on Windows 200x/XP is:

      	HKEY_CURRENT_USER
+

    +The Registry Hive key that affects the behaviour of folders that are part of the default user profile +are controlled by entries on Windows 200x/XP is: +

    +

    +	HKEY_CURRENT_USER
 		\Software
 			\Microsoft
 				\Windows
 					\CurrentVersion
 						\Explorer
-							\User Shell Folders\

    The above hive key contains a list of automatically managed folders. The default entries are:

    	Name		Default Value
+							\User Shell Folders\
+

    +

    +The above hive key contains a list of automatically managed folders. The default entries are: +

    + 

    +	Name		Default Value
 	--------------	-----------------------------------------
 	AppData		%USERPROFILE%\Application Data
 	Cache		%USERPROFILE%\Local Settings\Temporary Internet Files
@@ -15610,445 +6604,210 @@ CLASS="PROGRAMLISTING"
 	Start Menu	%USERPROFILE%\Start Menu
 	Startup		%USERPROFILE%\Start Menu\Programs\Startup
 	Templates	%USERPROFILE%\Templates
-
    -

    There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ.

    It makes a huge difference to the speed of handling roaming user profiles if all the folders are +

    +

    +There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all +the others are of type REG_EXPAND_SZ. +

    +It makes a huge difference to the speed of handling roaming user profiles if all the folders are stored on a dedicated location on a network server. This means that it will NOT be necessary to -write Outlook PST file over the network for every login and logout.

    To set this to a network location you could use the following examples: +write the Outlook PST file over the network for every login and logout. +

    +To set this to a network location you could use the following examples: -

    	%LOGONSERVER%\%USERNAME%\Default Folders
    +

    +	%LOGONSERVER%\%USERNAME%\Default Folders
+

    -This would store the folders in the user's home directory under a directory called "Default Folders" +This would store the folders in the user's home directory under a directory called "Default Folders" You could also use: -

    	\\SambaServer\FolderShare\%USERNAME%
    +

    +	\\SambaServer\FolderShare\%USERNAME%
+

    -in which case the default folders will be stored in the server named SambaServer -in the share called FolderShare under a directory that has the name of the MS Windows -user as seen by the Linux/Unix file system.

    Please note that once you have created a default profile share, you MUST migrate a user's profile -(default or custom) to it.

    MS Windows 200x/XP profiles may be Local or Roaming. -A roaming profile will be cached locally unless the following registry key is created:

    	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
-	"DeleteRoamingCache"=dword:00000001
    +in which case the default folders will be stored in the server named SambaServer +in the share called FolderShare under a directory that has the name of the MS Windows +user as seen by the Linux/Unix file system. +

    +Please note that once you have created a default profile share, you MUST migrate a user's profile +(default or custom) to it. +

    +MS Windows 200x/XP profiles may be Local or Roaming. +A roaming profile will be cached locally unless the following registry key is created: +

    +

    +	HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
+	"DeleteRoamingCache"=dword:00000001
+

    -In which case, the local cache copy will be deleted on logout.

    Chapter 19. Interdomain Trust Relationships

    Samba-3 supports NT4 style domain trust relationships. This is feature that many sites +In which case, the local cache copy will be deleted on logout. +

    Chapter19.Interdomain Trust Relationships

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Rafal Szczesniak

    Samba Team

    <mimir@samba.org>

    April 3, 2003

    Table of Contents

    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain

    +Samba-3 supports NT4 style domain trust relationships. This is feature that many sites will want to use if they migrate to Samba-3 from and NT4 style domain and do NOT want to adopt Active Directory or an LDAP based authentication back end. This section explains some background information regarding trust relationships and how to create them. It is now -possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts.

    19.1. Trust Relationship Background

    MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. +possible for Samba-3 to NT4 trust (and vice versa), as well as Samba3 to Samba3 trusts. +

    Trust Relationship Background

    +MS Windows NT3.x/4.0 type security domains employ a non-hierarchical security structure. The limitations of this architecture as it affects the scalability of MS Windows networking in large organisations is well known. Additionally, the flat-name space that results from this design significantly impacts the delegation of administrative responsibilities in -large and diverse organisations.

    Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means +large and diverse organisations. +

    +Microsoft developed Active Directory Service (ADS), based on Kerberos and LDAP, as a means of circumventing the limitations of the older technologies. Not every organisation is ready or willing to embrace ADS. For small companies the older NT4 style domain security paradigm is quite adequate, there thus remains an entrenched user base for whom there is no direct -desire to go through a disruptive change to adopt ADS.

    Microsoft introduced with MS Windows NT the ability to allow differing security domains +desire to go through a disruptive change to adopt ADS. +

    +Microsoft introduced with MS Windows NT the ability to allow differing security domains to affect a mechanism so that users from one domain may be given access rights and privileges in another domain. The language that describes this capability is couched in terms of -Trusts. Specifically, one domain will trust the users +Trusts. Specifically, one domain will trust the users from another domain. The domain from which users are available to another security domain is said to be a trusted domain. The domain in which those users have assigned rights and privileges is the trusting domain. With NT3.x/4.0 all trust relationships are always in one direction only, thus if users in both domains are to have privileges and rights in each others' domain, then it is -necessary to establish two (2) relationships, one in each direction.

    In an NT4 style MS security domain, all trusts are non-transitive. This means that if there +necessary to establish two (2) relationships, one in each direction. +

    +In an NT4 style MS security domain, all trusts are non-transitive. This means that if there are three (3) domains (let's call them RED, WHITE, and BLUE) where RED and WHITE have a trust relationship, and WHITE and BLUE have a trust relationship, then it holds that there is no implied trust between the RED and BLUE domains. ie: Relationships are explicit and not -transitive.

    New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way +transitive. +

    +New to MS Windows 2000 ADS security contexts is the fact that trust relationships are two-way by default. Also, all inter-ADS domain trusts are transitive. In the case of the RED, WHITE and BLUE domains above, with Windows 2000 and ADS the RED and BLUE domains CAN trust each other. This is an inherent feature of ADS domains. Samba-3 implements MS Windows NT4 style Interdomain trusts and interoperates with MS Windows 200x ADS -security domains in similar manner to MS Windows NT4 style domains.

    19.2. Native MS Windows NT4 Trusts Configuration

    There are two steps to creating an interdomain trust relationship.

    19.2.1. NT4 as the Trusting Domain (ie. creating the trusted account)

    For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. +security domains in similar manner to MS Windows NT4 style domains. +

    Native MS Windows NT4 Trusts Configuration

    +There are two steps to creating an interdomain trust relationship. +

    NT4 as the Trusting Domain (ie. creating the trusted account)

    +For MS Windows NT4, all domain trust relationships are configured using the Domain User Manager. To affect a two way trust relationship it is necessary for each domain administrator to make available (for use by an external domain) it's security resources. This is done from the Domain User Manager Policies entry on the menu bar. From the Policy menu, select Trust Relationships, then -next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and -"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that +next to the lower box that is labelled "Permitted to Trust this Domain" are two buttons, "Add" and +"Remove". The "Add" button will open a panel in which needs to be entered the remote domain that will be able to assign user rights to your domain. In addition it is necessary to enter a password that is specific to this trust relationship. The password needs to be -typed twice (for standard confirmation).

    19.2.2. NT4 as the Trusted Domain (ie. creating trusted account's password)

    A trust relationship will work only when the other (trusting) domain makes the appropriate connections +typed twice (for standard confirmation). +

    NT4 as the Trusted Domain (ie. creating trusted account's password)

    +A trust relationship will work only when the other (trusting) domain makes the appropriate connections with the trusted domain. To consumate the trust relationship the administrator will launch the Domain User Manager, from the menu select Policies, then select Trust Relationships, then click on the -"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in -which must be entered the name of the remote domain as well as the password assigned to that trust.

    19.3. Configuring Samba NT-style Domain Trusts

    This description is meant to be a fairly short introduction about how to set up a Samba server so +"Add" button that is next to the box that is labelled "Trusted Domains". A panel will open in +which must be entered the name of the remote domain as well as the password assigned to that trust. +

    Configuring Samba NT-style Domain Trusts

    +This description is meant to be a fairly short introduction about how to set up a Samba server so that it could participate in interdomain trust relationships. Trust relationship support in Samba -is in its early stage, so lot of things don't work yet.

    Each of the procedures described below is treated as they were performed with Windows NT4 Server on +is in its early stage, so lot of things don't work yet. +

    +Each of the procedures described below is treated as they were performed with Windows NT4 Server on one end. The remote end could just as well be another Samba-3 domain. It can be clearly seen, after reading this document, that combining Samba-specific parts of what's written below leads to trust -between domains in purely Samba environment.

    19.3.1. Samba-3 as the Trusting Domain

    In order to set Samba PDC to be trusted party of the relationship first you need +between domains in purely Samba environment. +

    Samba-3 as the Trusting Domain

    +In order to set the Samba PDC to be the trusted party of the relationship first you need to create special account for the domain that will be the trusting party. To do that, you can use the 'smbpasswd' utility. Creating the trusted domain account is very similiar to creating a trusted machine account. Suppose, your domain is called SAMBA, and the remote domain is called RUMBA. The first step -will be to issue this command from your favourite shell:

        deity# smbpasswd -a -i rumba
-    	New SMB password: XXXXXXXX
-    	Retype SMB password: XXXXXXXX
-    	Added user rumba$
    +will be to issue this command from your favourite shell: +

    +

    +deity# smbpasswd -a -i rumba
+	New SMB password: XXXXXXXX
+	Retype SMB password: XXXXXXXX
+	Added user rumba$
+

    -where -a means to add a new account into the -passdb database and -i means: ''create this -account with the InterDomain trust flag''

    The account name will be 'rumba$' (the name of the remote domain)

    After issuing this command you'll be asked to enter the password for +where -a means to add a new account into the +passdb database and -i means: ''create this +account with the InterDomain trust flag'' +

    +The account name will be 'rumba$' (the name of the remote domain) +

    +After issuing this command you'll be asked to enter the password for the account. You can use any password you want, but be aware that Windows NT will not change this password until 7 days following account creation. -After the command returns successfully, you can look at the entry for new account -(in the way depending on your configuration) and see that account's name is +After the command returns successfully, you can look at the entry for the new account +(in the stardard way depending on your configuration) and see that account's name is really RUMBA$ and it has 'I' flag in the flags field. Now you're ready to confirm -the trust by establishing it from Windows NT Server.

    Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. +the trust by establishing it from Windows NT Server. +

    +Open 'User Manager for Domains' and from menu 'Policies' select 'Trust Relationships...'. Right beside 'Trusted domains' list box press 'Add...' button. You will be prompted for the trusted domain name and the relationship password. Type in SAMBA, as this is your domain name, and the password used at the time of account creation. Press OK and, if everything went without incident, you will see 'Trusted domain relationship -successfully established' message.

    19.3.2. Samba-3 as the Trusted Domain

    This time activities are somewhat reversed. Again, we'll assume that your domain -controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA.

    The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC.

    Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. +successfully established' message. +

    Samba-3 as the Trusted Domain

    +This time activities are somewhat reversed. Again, we'll assume that your domain +controlled by the Samba PDC is called SAMBA and NT-controlled domain is called RUMBA. +

    +The very first thing requirement is to add an account for the SAMBA domain on RUMBA's PDC. +

    +Launch the Domain User Manager, then from the menu select 'Policies', 'Trust Relationships'. Now, next to 'Trusted Domains' box press the 'Add' button, and type in the name of the trusted -domain (SAMBA) and password securing the relationship.

    The password can be arbitrarily chosen. It is easy to change it the password -from Samba server whenever you want. After confirming the password your account is -ready for use. Now it's Samba's turn.

    Using your favourite shell while being logged in as root, issue this command:

    deity# net rpc trustdom establish rumba

    You will be prompted for the password you just typed on your Windows NT4 Server box. -Don not worry if you see an error message that mentions a returned code of -NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the +domain (SAMBA) and password securing the relationship. +

    +The password can be arbitrarily chosen. It is easy to change the password +from the Samba server whenever you want. After confirming the password your account is +ready for use. Now it's Samba's turn. +

    +Using your favourite shell while being logged in as root, issue this command: +

    +deity# net rpc trustdom establish rumba +

    +You will be prompted for the password you just typed on your Windows NT4 Server box. +Do not worry if you see an error message that mentions a returned code of +NT_STATUS_NOLOGON_INTERDOMAIN_TRUST_ACCOUNT. It means the password you gave is correct and the NT4 Server says the account is ready for interdomain connection and not for ordinary connection. After that, be patient it can take a while (especially in large networks), you should see the 'Success' message. Congratulations! Your trust -relationship has just been established.

    Note that you have to run this command as root because you must have write access to -the secrets.tdb file.

    Chapter 20. PAM Configuration for Centrally Managed Authentication

    20.1. Samba and PAM

    A number of Unix systems (eg: Sun Solaris), as well as the +relationship has just been established. +

    Note

    +Note that you have to run this command as root because you must have write access to +the secrets.tdb file. +

    Chapter20.PAM Configuration for Centrally Managed Authentication

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    (Jun 21 2001)

    Table of Contents

    Samba and PAM
    PAM Configuration in smb.conf
    Password Synchronisation using pam_smbpass.so
    Distributed Authentication

    Samba and PAM

    +A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, authorization and resource control services. Prior to the introduction of PAM, a decision to use an alternative to -the system password database (/etc/passwd) +the system password database (/etc/passwd) would require the provision of alternatives for all programs that provide security services. Such a choice would involve provision of -alternatives to such programs as: login, -passwd, chown, etc.

    PAM provides a mechanism that disconnects these security programs +alternatives to such programs as: login, +passwd, chown, etc. +

    +PAM provides a mechanism that disconnects these security programs from the underlying authentication/authorization infrastructure. -PAM is configured either through one file /etc/pam.conf (Solaris), -or by editing individual files that are located in /etc/pam.d.

    If the PAM authentication module (loadable link library file) is located in the +PAM is configured either through one file /etc/pam.conf (Solaris), +or by editing individual files that are located in /etc/pam.d. +

    Note

    + If the PAM authentication module (loadable link library file) is located in the default location then it is not necessary to specify the path. In the case of - Linux, the default location is /lib/security. If the module - is located other than default then the path may be specified as: + Linux, the default location is /lib/security. If the module + is located outside the default then the path must be specified as: - 

    	auth       required      /other_path/pam_strange_module.so
-
    -

    The following is an example /etc/pam.d/login configuration file. + 

    +	auth       required      /other_path/pam_strange_module.so
+

    +

    +The following is an example /etc/pam.d/login configuration file. This example had all options been uncommented is probably not usable as it stacks many conditions before allowing successful completion of the login process. Essentially all conditions can be disabled -by commenting them out except the calls to pam_pwdb.so.

    	#%PAM-1.0
+by commenting them out except the calls to pam_pwdb.so.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `login' service
 	#
 	auth 		required	pam_securetty.so
@@ -16061,22 +6820,13 @@ CLASS="PROGRAMLISTING"
 	session		required	pam_pwdb.so
 	# session 	optional	pam_lastlog.so
 	# password   	required   	pam_cracklib.so retry=3
-	password	required	pam_pwdb.so shadow md5
    PAM allows use of replacable modules. Those available on a 
-sample system include:
    $/bin/ls /lib/security
-
    	pam_access.so    pam_ftp.so          pam_limits.so     
+	password	required	pam_pwdb.so shadow md5
+
    
+PAM allows use of replacable modules. Those available on a 
+sample system include:
+
    $/bin/ls /lib/security
+
    +	pam_access.so    pam_ftp.so          pam_limits.so     
 	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
 	pam_cracklib.so  pam_group.so        pam_listfile.so   
 	pam_nologin.so   pam_rootok.so       pam_tally.so      
@@ -16087,588 +6837,326 @@ CLASS="PROGRAMLISTING"
 	pam_env.so       pam_ldap.so         pam_motd.so       
 	pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
 	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
-	pam_userdb.so    pam_warn.so         pam_unix_session.so
    The following example for the login program replaces the use of 
-the pam_pwdb.so module which uses the system 
-password database (/etc/passwd,
-/etc/shadow, /etc/group) with 
-the module pam_smbpass.so which uses the Samba 
+	pam_userdb.so    pam_warn.so         pam_unix_session.so
+

    +The following example for the login program replaces the use of +the pam_pwdb.so module which uses the system +password database (/etc/passwd, +/etc/shadow, /etc/group) with +the module pam_smbpass.so which uses the Samba database which contains the Microsoft MD4 encrypted password hashes. This database is stored in either -/usr/local/samba/private/smbpasswd, -/etc/samba/smbpasswd, or in -/etc/samba.d/smbpasswd, depending on the +/usr/local/samba/private/smbpasswd, +/etc/samba/smbpasswd, or in +/etc/samba.d/smbpasswd, depending on the Samba implementation for your Unix/Linux system. The -pam_smbpass.so module is provided by +pam_smbpass.so module is provided by Samba version 2.2.1 or later. It can be compiled by specifying the ---with-pam_smbpass options when running Samba's -configure script. For more information -on the pam_smbpass module, see the documentation -in the source/pam_smbpass directory of the Samba -source distribution.

    	#%PAM-1.0
+--with-pam_smbpass options when running Samba's
+configure script.  For more information
+on the pam_smbpass module, see the documentation
+in the source/pam_smbpass directory of the Samba 
+source distribution.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `login' service
 	#
 	auth		required	pam_smbpass.so nodelay
 	account		required	pam_smbpass.so nodelay
 	session		required	pam_smbpass.so nodelay
-	password	required	pam_smbpass.so nodelay
    The following is the PAM configuration file for a particular 
-Linux system. The default condition uses pam_pwdb.so.
    	#%PAM-1.0
+	password	required	pam_smbpass.so nodelay
+
    
+The following is the PAM configuration file for a particular 
+Linux system. The default condition uses pam_pwdb.so.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `samba' service
 	#
 	auth       required     pam_pwdb.so nullok nodelay shadow audit
 	account    required     pam_pwdb.so audit nodelay
 	session    required     pam_pwdb.so nodelay
-	password   required     pam_pwdb.so shadow md5
    In the following example the decision has been made to use the 
+	password   required     pam_pwdb.so shadow md5
+

    +In the following example the decision has been made to use the smbpasswd database even for basic samba authentication. Such a decision could also be made for the passwd program and would thus allow the smbpasswd passwords to be changed using the passwd -program.

    	#%PAM-1.0
+program.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `samba' service
 	#
 	auth       required     pam_smbpass.so nodelay
 	account    required     pam_pwdb.so audit nodelay
 	session    required     pam_pwdb.so nodelay
-	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
    PAM allows stacking of authentication mechanisms. It is 
+	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
+
    Note
    PAM allows stacking of authentication mechanisms. It is 
 also possible to pass information obtained within one PAM module through 
 to the next module in the PAM stack. Please refer to the documentation for 
 your particular system implementation for details regarding the specific 
 capabilities of PAM in this environment. Some Linux implmentations also 
-provide the pam_stack.so module that allows all 
+provide the pam_stack.so module that allows all 
 authentication to be configured in a single central file. The 
-pam_stack.so method has some very devoted followers 
+pam_stack.so method has some very devoted followers 
 on the basis that it allows for easier administration. As with all issues in 
 life though, every decision makes trade-offs, so you may want examine the 
-PAM documentation for further helpful information.

    20.2. Distributed Authentication

    The astute administrator will realize from this that the -combination of pam_smbpass.so, -winbindd, and a distributed -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed -user/password database that can also be used by all -PAM (eg: Linux) aware programs and applications. This arrangement -can have particularly potent advantages compared with the -use of Microsoft Active Directory Service (ADS) in so far as -reduction of wide area network authentication traffic.

    20.3. PAM Configuration in smb.conf

    There is an option in smb.conf called obey pam restrictions. -The following is from the on-line help for this option in SWAT;

    When Samba is configured to enable PAM support (i.e. ---with-pam), this parameter will +PAM documentation for further helpful information. +

    PAM Configuration in smb.conf

    +There is an option in smb.conf called obey pam restrictions. +The following is from the on-line help for this option in SWAT; +

    +When Samba is configured to enable PAM support (i.e. +--with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of -encrypt passwords = yes. +encrypt passwords = yes. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB -password encryption.

    Default: obey pam restrictions = no

    Chapter 21. Stackable VFS modules

    21.1. Introduction and configuration

    Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. +password encryption. +

    Default: obey pam restrictions = no

    Password Synchronisation using pam_smbpass.so

    +pam_smbpass is a PAM module which can be used on conforming systems to +keep the smbpasswd (Samba password) database in sync with the unix +password file. PAM (Pluggable Authentication Modules) is an API supported +under some Unices, such as Solaris, HPUX and Linux, that provides a +generic interface to authentication mechanisms. +

    +For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/ +

    +This module authenticates a local smbpasswd user database. If you require +support for authenticating against a remote SMB server, or if you're +concerned about the presence of suid root binaries on your system, it is +recommended that you use pam_winbind instead. +

    +Options recognized by this module are as follows:
+
+        debug           -       log more debugging info
+        audit           -       like debug, but also logs unknown usernames
+        use_first_pass  -       don't prompt the user for passwords;
+                                take them from PAM_ items instead
+        try_first_pass  -       try to get the password from a previous
+                                PAM module, fall back to prompting the user
+        use_authtok     -       like try_first_pass, but *fail* if the new
+                                PAM_AUTHTOK has not been previously set.
+                                (intended for stacking password modules only)
+        not_set_pass    -       don't make passwords used by this module
+                                available to other modules.
+        nodelay         -       don't insert ~1 second delays on authentication
+                                failure.
+        nullok          -       null passwords are allowed.
+        nonull          -       null passwords are not allowed. Used to
+                                override the Samba configuration.
+        migrate         -       only meaningful in an "auth" context;
+                                used to update smbpasswd file with a
+                                password used for successful authentication.
+        smbconf=< file >  -     specify an alternate path to the smb.conf
+                                file.
+
    +Thanks go to the following people:
+
+	* Andrew Morgan < morgan@transmeta.com >, for providing the Linux-PAM
+	framework, without which none of this would have happened
+
+	* Christian Gafton < gafton@redhat.com > and Andrew Morgan again, for the
+	pam_pwdb module upon which pam_smbpass was originally based
+
+	* Luke Leighton < lkcl@switchboard.net > for being receptive to the idea,
+	and for the occasional good-natured complaint about the project's status
+	that keep me working on it :)
+
+	* and of course, all the other members of the Samba team
+	<http://www.samba.org/samba/team.html>, for creating a great product
+	and for giving this project a purpose
+
+	---------------------
+	Stephen Langasek < vorlon@netexpress.net >
+

    +The following are examples of the use of pam_smbpass.so in the format of Linux +/etc/pam.d/ files structure. Those wishing to implement this +tool on other platforms will need to adapt this appropriately. +

    Password Synchonisation Configuration

    +A sample PAM configuration that shows the use of pam_smbpass to make +sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow) +is changed. Useful when an expired password might be changed by an +application (such as ssh). +

    +	#%PAM-1.0
+	# password-sync
+	#
+	auth       requisite        pam_nologin.so
+	auth       required         pam_unix.so
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   required         pam_smbpass.so nullok use_authtok try_first_pass
+	session    required         pam_unix.so
+

    Password Migration Configuration

    +A sample PAM configuration that shows the use of pam_smbpass to migrate +from plaintext to encrypted passwords for Samba. Unlike other methods, +this can be used for users who have never connected to Samba shares: +password migration takes place when users ftp in, login using ssh, pop +their mail, etc. +

    +	#%PAM-1.0
+	# password-migration
+	#
+	auth       requisite        pam_nologin.so
+	# pam_smbpass is called IFF pam_unix succeeds.
+	auth       requisite        pam_unix.so
+	auth       optional         pam_smbpass.so migrate
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   optional         pam_smbpass.so nullok use_authtok try_first_pass
+	session    required         pam_unix.so
+

    Mature Password Configuration

    +A sample PAM configuration for a 'mature' smbpasswd installation. +private/smbpasswd is fully populated, and we consider it an error if +the smbpasswd doesn't exist or doesn't match the Unix password. +

    +	#%PAM-1.0
+	# password-mature
+	#
+	auth       requisite        pam_nologin.so
+	auth       required         pam_unix.so
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   required         pam_smbpass.so use_authtok use_first_pass
+	session    required         pam_unix.so
+

    Kerberos Password Integration Configuration

    +A sample PAM configuration that shows pam_smbpass used together with +pam_krb5. This could be useful on a Samba PDC that is also a member of +a Kerberos realm. +

    +	#%PAM-1.0
+	# kdc-pdc
+	#
+	auth       requisite        pam_nologin.so
+	auth       requisite        pam_krb5.so
+	auth       optional         pam_smbpass.so migrate
+	account    required         pam_krb5.so
+	password   requisite        pam_cracklib.so retry=3
+	password   optional         pam_smbpass.so nullok use_authtok try_first_pass
+	password   required         pam_krb5.so use_authtok try_first_pass
+	session    required         pam_krb5.so
+

    Distributed Authentication

    +The astute administrator will realize from this that the +combination of pam_smbpass.so, +winbindd, and a distributed +passdb backend, such as ldap, will allow the establishment of a +centrally managed, distributed +user/password database that can also be used by all +PAM (eg: Linux) aware programs and applications. This arrangement +can have particularly potent advantages compared with the +use of Microsoft Active Directory Service (ADS) in so far as +reduction of wide area network authentication traffic. +

    Chapter21.Stackable VFS modules

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Alexander Bokovoy

    Tim Potter

    Simo Sorce

    Table of Contents

    Introduction and configuration
    Included modules
    audit
    extd_audit
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan

    Introduction and configuration

    +Since samba 3.0, samba supports stackable VFS(Virtual File System) modules. Samba passes each request to access the unix file system thru the loaded VFS modules. This chapter covers all the modules that come with the samba source and references to -some external modules.

    You may have problems to compile these modules, as shared libraries are +some external modules. +

    +You may have problems to compile these modules, as shared libraries are compiled and linked in different ways on different systems. -They currently have been tested against GNU/linux and IRIX.

    To use the VFS modules, create a share similar to the one below. The -important parameter is the vfs object parameter which must point to +They currently have been tested against GNU/linux and IRIX. +

    +To use the VFS modules, create a share similar to the one below. The +important parameter is the vfs object parameter which must point to the exact pathname of the shared library objects. For example, to log all access to files and use a recycle bin: -

           [audit]
+
    +       [audit]
                 comment = Audited /data directory
                 path = /data
                 vfs object = /path/to/audit.so /path/to/recycle.so
                 writeable = yes
-                browseable = yes
    The modules are used in the order they are specified.
    Further documentation on writing VFS modules for Samba can be found in
-the Samba Developers Guide.

    21.2. Included modules

    21.2.1. audit

    A simple module to audit file access to the syslog + browseable = yes +

    +

    +The modules are used in the order they are specified. +

    +Further documentation on writing VFS modules for Samba can be found in +the Samba Developers Guide. +

    Included modules

    audit

    A simple module to audit file access to the syslog facility. The following operations are logged: -

    share
    connect/disconnect
    directory opens/create/remove
    file open/close/rename/unlink/chmod

    21.2.2. extd_audit

    This module is identical with the audit module above except +

    share
    connect/disconnect
    directory opens/create/remove
    file open/close/rename/unlink/chmod

    +

    extd_audit

    +This module is identical with the audit module above except that it sends audit logs to both syslog as well as the smbd log file/s. The -loglevel for this module is set in the smb.conf file. At loglevel = 0, only file -and directory deletions and directory and file creations are logged. At loglevel = 1 -file opens are renames and permission changes are logged , while at loglevel = 2 file -open and close calls are logged also.

    21.2.3. recycle

    A recycle-bin like modules. When used any unlink call +loglevel for this module is set in the smb.conf file. +

    +The logging information that will be written to the smbd log file is controlled by +the log level parameter in smb.conf. The +following information will be recorded: +

    Table21.1.Extended Auditing Log Information

    Log LevelLog Details - File and Directory Operations
    0Creation / Deletion
    1Create / Delete / Rename / Permission Changes
    2Create / Delete / Rename / Perm Change / Open / Close

    recycle

    +A recycle-bin like module. When used any unlink call will be intercepted and files moved to the recycle -directory instead of beeing deleted.

    Supported options: -

    vfs_recycle_bin:repository

    FIXME

    vfs_recycle_bin:keeptree

    FIXME

    vfs_recycle_bin:versions

    FIXME

    vfs_recycle_bin:touch

    FIXME

    vfs_recycle_bin:maxsize

    FIXME

    vfs_recycle_bin:exclude

    FIXME

    vfs_recycle_bin:exclude_dir

    FIXME

    vfs_recycle_bin:noversions

    FIXME

    21.2.4. netatalk

    A netatalk module, that will ease co-existence of samba and -netatalk file sharing services.

    Advantages compared to the old netatalk module: -

    it doesn't care about creating of .AppleDouble forks, just keeps ones in sync
    if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    21.3. VFS modules available elsewhere

    This section contains a listing of various other VFS modules that +directory instead of being deleted. +

    Supported options: +

    vfs_recycle_bin:repository

    FIXME

    vfs_recycle_bin:keeptree

    FIXME

    vfs_recycle_bin:versions

    FIXME

    vfs_recycle_bin:touch

    FIXME

    vfs_recycle_bin:maxsize

    FIXME

    vfs_recycle_bin:exclude

    FIXME

    vfs_recycle_bin:exclude_dir

    FIXME

    vfs_recycle_bin:noversions

    FIXME

    +

    netatalk

    +A netatalk module, that will ease co-existence of samba and +netatalk file sharing services. +

    Advantages compared to the old netatalk module: +

    it doesn't care about creating of .AppleDouble forks, just keeps them in sync
    if share in smb.conf doesn't contain .AppleDouble item in hide or veto list, it will be added automatically

    +

    VFS modules available elsewhere

    +This section contains a listing of various other VFS modules that have been posted but don't currently reside in the Samba CVS -tree for one reason ot another (e.g. it is easy for the maintainer -to have his or her own CVS tree).

    No statemets about the stability or functionality any module -should be implied due to its presence here.

    21.3.1. DatabaseFS

    URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php

    By Eric Lorimer.

    I have created a VFS module which implements a fairly complete read-only +tree for one reason or another (e.g. it is easy for the maintainer +to have his or her own CVS tree). +

    +No statemets about the stability or functionality of any module +should be implied due to its presence here. +

    DatabaseFS

    +URL: http://www.css.tayloru.edu/~elorimer/databasefs/index.php +

    By Eric Lorimer.

    +I have created a VFS module which implements a fairly complete read-only filesystem. It presents information from a database as a filesystem in a modular and generic way to allow different databases to be used (originally designed for organizing MP3s under directories such as -"Artists," "Song Keywords," etc... I have since applied it to a student +"Artists," "Song Keywords," etc... I have since applied it to a student roster database very easily). The directory structure is stored in the database itself and the module makes no assumptions about the database -structure beyond the table it requires to run.

    Any feedback would be appreciated: comments, suggestions, patches, +structure beyond the table it requires to run. +

    +Any feedback would be appreciated: comments, suggestions, patches, etc... If nothing else, hopefully it might prove useful for someone -else who wishes to create a virtual filesystem.

    21.3.2. vscan

    URL: http://www.openantivirus.org/

    samba-vscan is a proof-of-concept module for Samba, which +else who wishes to create a virtual filesystem. +

    vscan

    URL: http://www.openantivirus.org/

    +samba-vscan is a proof-of-concept module for Samba, which uses the VFS (virtual file system) features of Samba 2.2.x/3.0 alphaX. Of couse, Samba has to be compiled with VFS support. samba-vscan supports various virus scanners and is maintained -by Rainer Link.

    Chapter 22. Hosting a Microsoft Distributed File System tree on Samba

    22.1. Instructions

    The Distributed File System (or Dfs) provides a means of +by Rainer Link. +

    Chapter22.Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software


    + <samba@samba.org>
    +

    12 Jul 2000

    Table of Contents

    Instructions
    Notes

    Instructions

    The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users see from the actual physical locations of these resources on the network. It allows for higher availability, smoother storage expansion, - load balancing etc. For more information about Dfs, refer to Microsoft documentation.

    This document explains how to host a Dfs tree on a Unix - machine (for Dfs-aware clients to browse) using Samba.

    To enable SMB-based DFS for Samba, configure it with the - --with-msdfs option. Once built, a + load balancing etc. For more information about Dfs, refer to + Microsoft documentation.

    This document explains how to host a Dfs tree on a Unix + machine (for Dfs-aware clients to browse) using Samba.

    To enable SMB-based DFS for Samba, configure it with the + --with-msdfs option. Once built, a Samba server can be made a Dfs server by setting the global - boolean host msdfs parameter in the smb.conf - file. You designate a share as a Dfs root using the share - level boolean msdfs root parameter. A Dfs root directory on + boolean + host msdfs parameter in the smb.conf + file. You designate a share as a Dfs root using the share + level boolean + msdfs root parameter. A Dfs root directory on Samba hosts Dfs links in the form of symbolic links that point to other servers. For example, a symbolic link - junction->msdfs:storage1\share1 in + junction->msdfs:storage1\share1 in the share directory acts as the Dfs junction. When Dfs-aware clients attempt to access the junction link, they are redirected - to the storage location (in this case, \\storage1\share1).

    Dfs trees on Samba work with all Dfs-aware clients ranging - from Windows 95 to 2000.

    Here's an example of setting up a Dfs tree on a Samba - server.

    # The smb.conf file:
+	to the storage location (in this case, \\storage1\share1).
    Dfs trees on Samba work with all Dfs-aware clients ranging 
+	from Windows 95 to 2000.
    Here's an example of setting up a Dfs tree on a Samba 
+	server.
    +# The smb.conf file:
 [global]
 	netbios name = SAMBA
 	host msdfs   = yes
@@ -16676,261 +7164,74 @@ CLASS="PROGRAMLISTING"
 [dfs]
 	path = /export/dfsroot
 	msdfs root = yes
-	
    In the /export/dfsroot directory we set up our dfs links to 
-	other servers on the network.
    root# cd /export/dfsroot
    root# chown root /export/dfsroot
    root# chmod 755 /export/dfsroot
    root# ln -s msdfs:storageA\\shareA linka
    root# ln -s msdfs:serverB\\share,serverC\\share linkb
    You should set up the permissions and ownership of 
+

    In the /export/dfsroot directory we set up our dfs links to + other servers on the network.

    root# cd /export/dfsroot

    root# chown root /export/dfsroot

    root# chmod 755 /export/dfsroot

    root# ln -s msdfs:storageA\\shareA linka

    root# ln -s msdfs:serverB\\share,serverC\\share linkb

    You should set up the permissions and ownership of the directory acting as the Dfs root such that only designated users can create, delete or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link name. Finally set up the symbolic links to point to the - network shares you want, and start Samba.

    Users on Dfs-aware clients can now browse the Dfs tree + network shares you want, and start Samba.

    Users on Dfs-aware clients can now browse the Dfs tree on the Samba server at \\samba\dfs. Accessing links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.

    22.1.1. Notes

    • Windows clients need to be rebooted + takes users directly to the appropriate shares on the network.

      Notes

      • Windows clients need to be rebooted if a previously mounted non-dfs share is made a dfs root or vice versa. A better way is to introduce a - new share and make it the dfs root.

      • Currently there's a restriction that msdfs - symlink names should all be lowercase.

      • For security purposes, the directory + new share and make it the dfs root.

      • Currently there's a restriction that msdfs + symlink names should all be lowercase.

      • For security purposes, the directory acting as the root of the Dfs tree should have ownership and permissions set so that only designated users can - modify the symbolic links in the directory.

    Chapter 23. Integrating MS Windows networks with Samba

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If you + modify the symbolic links in the directory.

    Chapter23.Integrating MS Windows networks with Samba

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    (Jan 01 2001)

    Table of Contents

    Name Resolution in a pure Unix/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup

    +This section deals with NetBIOS over TCP/IP name to IP address resolution. If your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this section does not apply to your installation. If your installation involves use of -NetBIOS over TCP/IP then this section may help you to resolve networking problems.

    NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS +NetBIOS over TCP/IP then this section may help you to resolve networking problems. +

    Note

    + NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS over Logical Link Control (LLC). On modern networks it is highly advised to NOT run NetBEUI at all. Note also that there is NO such thing as NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension.

    Since the introduction of MS Windows 2000 it is possible to run MS Windows networking + and utter mis-apprehension. +

    +Since the introduction of MS Windows 2000 it is possible to run MS Windows networking without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not.

    When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then +used and UDP port 137 and TCP port 139 will not. +

    Note

    +When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).

    When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that +Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic). +

    +When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration.

    23.1. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    23.1.1. /etc/hosts

    Contains a static list of IP Addresses and names. -eg:

    	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box

    The purpose of /etc/hosts is to provide a +over client workstation network configuration. +

    Name Resolution in a pure Unix/Linux world

    +The key configuration files covered in this section are: +

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    +Contains a static list of IP Addresses and names. +eg: +

    +	127.0.0.1	localhost localhost.localdomain
+	192.168.1.1	bigbox.caldera.com	bigbox	alias4box
+

    +The purpose of /etc/hosts is to provide a name resolution mechanism so that uses do not need to remember -IP addresses.

    Network packets that are sent over the physical network transport +IP addresses. +

    +Network packets that are sent over the physical network transport layer communicate not via IP addresses but rather using the Media Access Control address, or MAC address. IP Addresses are currently 32 bits in length and are typically presented as four (4) decimal -numbers that are separated by a dot (or period). eg: 168.192.1.1

    MAC Addresses use 48 bits (or 6 bytes) and are typically represented +numbers that are separated by a dot (or period). eg: 168.192.1.1 +

    +MAC Addresses use 48 bits (or 6 bytes) and are typically represented as two digit hexadecimal numbers separated by colons. eg: -40:8e:0a:12:34:56

    Every network interfrace must have an MAC address. Associated with +40:8e:0a:12:34:56 +

    +Every network interfrace must have an MAC address. Associated with a MAC address there may be one or more IP addresses. There is NO relationship between an IP address and a MAC address, all such assignments are arbitary or discretionary in nature. At the most basic level all @@ -16939,18 +7240,15 @@ addresses must be globally unique, and generally remains fixed for any particular interface, the assignment of an IP address makes sense from a network management perspective. More than one IP address can be assigned per MAC address. One address must be the primary IP address, -this is the address that will be returned in the ARP reply.

    When a user or a process wants to communicate with another machine -the protocol implementation ensures that the "machine name" or "host -name" is resolved to an IP address in a manner that is controlled +this is the address that will be returned in the ARP reply. +

    +When a user or a process wants to communicate with another machine +the protocol implementation ensures that the "machine name" or "host +name" is resolved to an IP address in a manner that is controlled by the TCP/IP configuration control files. The file -/etc/hosts is one such file.

    When the IP address of the destination interface has been +/etc/hosts is one such file. +

    +When the IP address of the destination interface has been determined a protocol called ARP/RARP is used to identify the MAC address of the target interface. ARP stands for Address Resolution Protocol, and is a broadcast oriented method that @@ -16960,104 +7258,41 @@ address. Network interfaces are programmed to respond to two MAC addresses only; their own unique address and the address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary IP address for each -interface.

    The /etc/hosts file is foundational to all +interface. +

    +The /etc/hosts file is foundational to all Unix/Linux TCP/IP installations and as a minumum will contain the localhost and local network interface IP addresses and the primary names by which they are known within the local machine. This file helps to prime the pump so that a basic level of name resolution can exist before any other method of name resolution -becomes available.

    23.1.2. /etc/resolv.conf

    This file tells the name resolution libraries:

    • The name of the domain to which the machine +becomes available. +

    /etc/resolv.conf

    +This file tells the name resolution libraries: +

    • The name of the domain to which the machine belongs -

    • The name(s) of any domains that should be +

    • The name(s) of any domains that should be automatically searched when trying to resolve unqualified host names to their IP address -

    • The name or IP address of available Domain +

    • The name or IP address of available Domain Name Servers that may be asked to perform name to address translation lookups -

    23.1.3. /etc/host.conf

    /etc/host.conf is the primary means by +

    /etc/host.conf

    +/etc/host.conf is the primary means by which the setting in /etc/resolv.conf may be affected. It is a critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is:

    	order hosts,bind
-	multi on

    then both addresses should be returned. Please refer to the -man page for host.conf for further details.

    23.1.4. /etc/nsswitch.conf

    This file controls the actual name resolution targets. The -file typically has resolver object specifications as follows:

    	# /etc/nsswitch.conf
+which name resolution may procede. The typical structure is:
+
    +	order hosts,bind
+	multi on
+
    
+then both addresses should be returned. Please refer to the 
+man page for host.conf for further details.
+

    /etc/nsswitch.conf

    +This file controls the actual name resolution targets. The +file typically has resolver object specifications as follows: +

    +	# /etc/nsswitch.conf
 	#
 	# Name Service Switch configuration file.
 	#
@@ -17074,2608 +7309,1597 @@ CLASS="PROGRAMLISTING"
 	networks:	nis files dns
 
 	ethers:		nis files
-	protocols:	nis files
-	rpc:		nis files
-	services:	nis files

    Of course, each of these mechanisms requires that the appropriate -facilities and/or services are correctly configured.

    It should be noted that unless a network request/message must be -sent, TCP/IP networks are silent. All TCP/IP communications assumes a -principal of speaking only when necessary.

    Starting with version 2.2.0 samba has Linux support for extensions to -the name service switch infrastructure so that linux clients will -be able to obtain resolution of MS Windows NetBIOS names to IP -Addresses. To gain this functionality Samba needs to be compiled -with appropriate arguments to the make command (ie: make -nsswitch/libnss_wins.so). The resulting library should -then be installed in the /lib directory and -the "wins" parameter needs to be added to the "hosts:" line in -the /etc/nsswitch.conf file. At this point it -will be possible to ping any MS Windows machine by it's NetBIOS -machine name, so long as that machine is within the workgroup to -which both the samba machine and the MS Windows machine belong.

    23.2. Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine -is given. This name is known variously (and inconsistently) as -the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a -simply name with which the machine is associated. All NetBIOS names -are exactly 16 characters in length. The 16th character is reserved. -It is used to store a one byte value that indicates service level -information for the NetBIOS name that is registered. A NetBIOS machine -name is therefore registered for each service type that is provided by -the client/server.

    The following are typical NetBIOS name/service type registrations:

    	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
-
-	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers

    It should be noted that all NetBIOS machines register their own -names as per the above. This is in vast contrast to TCP/IP -installations where traditionally the system administrator will -determine in the /etc/hosts or in the DNS database what names -are associated with each IP address.

    One further point of clarification should be noted, the /etc/hosts -file and the DNS records do not provide the NetBIOS name type information -that MS Windows clients depend on to locate the type of service that may -be needed. An example of this is what happens when an MS Windows client -wants to locate a domain logon server. It find this service and the IP -address of a server that provides it by performing a lookup (via a -NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each -IP address that is returned in the enumerated list of IP addresses. Which -ever machine first replies then ends up providing the logon services.

    The name "workgroup" or "domain" really can be confusing since these -have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates -that the primary nature of the network environment is that of a -peer-to-peer design. In a WORKGROUP all machines are responsible for -their own security, and generally such security is limited to use of -just a password (known as SHARE MODE security). In most situations -with peer-to-peer networking the users who control their own machines -will simply opt to have no security at all. It is possible to have -USER MODE security in a WORKGROUP environment, thus requiring use -of a user name and a matching password.

    MS Windows networking is thus predetermined to use machine names -for all local and remote machine message passing. The protocol used is -called Server Message Block (SMB) and this is implemented using -the NetBIOS protocol (Network Basic Input Output System). NetBIOS can -be encapsulated using LLC (Logical Link Control) protocol - in which case -the resulting protocol is called NetBEUI (Network Basic Extended User -Interface). NetBIOS can also be run over IPX (Internetworking Packet -Exchange) protocol as used by Novell NetWare, and it can be run -over TCP/IP protocols - in which case the resulting protocol is called -NBT or NetBT, the NetBIOS over TCP/IP.

    MS Windows machines use a complex array of name resolution mechanisms. -Since we are primarily concerned with TCP/IP this demonstration is -limited to this area.

    23.2.1. The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is -stored the NetBIOS names and IP addresses for all external -machines that that machine has communicated with over the -past 10-15 minutes. It is more efficient to obtain an IP address -for a machine from the local cache than it is to go through all the -configured name resolution mechanisms.

    If a machine whose name is in the local name cache has been shut -down before the name had been expired and flushed from the cache, then -an attempt to exchange a message with that machine will be subject -to time-out delays. i.e.: Its name is in the cache, so a name resolution -lookup will succeed, but the machine can not respond. This can be -frustrating for users - but it is a characteristic of the protocol.

    The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this -is called "nmblookup".

    23.2.2. The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or -2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains -the IP Address and the machine name in matched pairs. The -LMHOSTS file performs NetBIOS name -to IP address mapping oriented.

    It typically looks like:

    	# Copyright (c) 1998 Microsoft Corp.
-	#
-	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
-	# over TCP/IP) stack for Windows98
-	#
-	# This file contains the mappings of IP addresses to NT computernames
-	# (NetBIOS) names.  Each entry should be kept on an individual line.
-	# The IP address should be placed in the first column followed by the
-	# corresponding computername. The address and the comptername
-	# should be separated by at least one space or tab. The "#" character
-	# is generally used to denote the start of a comment (see the exceptions
-	# below).
-	#
-	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
-	# files and offers the following extensions:
-	#
-	#      #PRE
-	#      #DOM:<domain>
-	#      #INCLUDE <filename>
-	#      #BEGIN_ALTERNATE
-	#      #END_ALTERNATE
-	#      \0xnn (non-printing character support)
-	#
-	# Following any entry in the file with the characters "#PRE" will cause
-	# the entry to be preloaded into the name cache. By default, entries are
-	# not preloaded, but are parsed only after dynamic name resolution fails.
-	#
-	# Following an entry with the "#DOM:<domain>" tag will associate the
-	# entry with the domain specified by <domain>. This affects how the
-	# browser and logon services behave in TCP/IP environments. To preload
-	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The <domain> is always preloaded although it will not
-	# be shown when the name cache is viewed.
-	#
-	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-	# software to seek the specified <filename> and parse it as if it were
-	# local. <filename> is generally a UNC-based name, allowing a
-	# centralized lmhosts file to be maintained on a server.
-	# It is ALWAYS necessary to provide a mapping for the IP address of the
-	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addtion the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
-	# be able to read the lmhosts file successfully. This key is under
-	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
-	#
-	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
-	# statements to be grouped together. Any single successful include
-	# will cause the group to succeed.
-	#
-	# Finally, non-printing characters can be embedded in mappings by
-	# first surrounding the NetBIOS name in quotations, then using the
-	# \0xnn notation to specify a hex value for a non-printing character.
-	#
-	# The following example illustrates all of these extensions:
-	#
-	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
-	# 102.54.94.123    popular            #PRE             #source server
-	# 102.54.94.117    localsrv           #PRE             #needed for the include
-	#
-	# #BEGIN_ALTERNATE
-	# #INCLUDE \\localsrv\public\lmhosts
-	# #INCLUDE \\rhino\public\lmhosts
-	# #END_ALTERNATE
-	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
-	# system is unavailable.
-	#
-	# Note that the whole file is parsed including comments on each lookup,
-	# so keeping the number of comments to a minimum will improve performance.
-	# Therefore it is not advisable to simply add lmhosts file entries onto the
-	# end of this file.

    23.2.3. HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in -C:\WINNT\SYSTEM32\DRIVERS\ETC and contains -the IP Address and the IP hostname in matched pairs. It can be -used by the name resolution infrastructure in MS Windows, depending -on how the TCP/IP environment is configured. This file is in -every way the equivalent of the Unix/Linux /etc/hosts file.

    23.2.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network -configuration facility. If enabled an elaborate name resolution sequence -is followed the precise nature of which isdependant on what the NetBIOS -Node Type parameter is configured to. A Node Type of 0 means use -NetBIOS broadcast (over UDP broadcast) is first used if the name -that is the subject of a name lookup is not found in the NetBIOS name -cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to -Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the -WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast -lookup is used.

    23.2.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the -rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores -the names and IP addresses that are registered by a Windows client -if the TCP/IP setup has been given at least one WINS Server IP Address.

    To configure Samba to be a WINS server the following parameter needs -to be added to the smb.conf file:

    	wins support = Yes

    To configure Samba to use a WINS server the following parameters are -needed in the smb.conf file:

    	wins support = No
-	wins server = xxx.xxx.xxx.xxx

    where xxx.xxx.xxx.xxx is the IP address -of the WINS server.

    Chapter 24. Improved browsing in samba

    24.1. Overview of browsing

    SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called browse list. This list -contains machines that are ready to offer file and/or print services -to other machines within the network. Thus it does not include -machines which aren't currently able to do server tasks. The browse -list is heavily used by all SMB clients. Configuration of SMB -browsing has been problematic for some Samba users, hence this -document.

    MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.

    Where NetBIOS over TCP/IP is enabled use of a WINS server is highly -recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. -WINS allows remote segment clients to obtain NetBIOS name_type information -that can NOT be provided by any other means of name resolution.

    24.2. Browsing support in samba

    Samba facilitates browsing. The browsing is supported by nmbd -and is also controlled by options in the smb.conf file. -Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available.

    Samba can also act as a domain master browser for a workgroup. This -means that it will collate lists from local browse masters into a -wide area network server list. In order for browse clients to -resolve the names they may find in this list, it is recommended that -both samba and your clients use a WINS server.

    Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain: on each wide area -network, you must only ever have one domain master browser per workgroup, -regardless of whether it is NT, Samba or any other type of domain master -that is providing this service.

    Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.

    To get browsing to work you need to run nmbd as usual, but will need -to use the workgroup option in smb.conf -to control what workgroup Samba becomes a part of.

    Samba also has a useful option for a Samba server to offer itself for -browsing on another subnet. It is recommended that this option is only -used for 'unusual' purposes: announcements over the internet, for -example. See remote announce in the -smb.conf man page.

    24.3. Problem resolution

    If something doesn't work then hopefully the log.nmb file will help -you track down the problem. Try a debug level of 2 or 3 for finding -problems. Also note that the current browse list usually gets stored -in text form in a file called browse.dat.

    Note that if it doesn't work for you, then you should still be able to -type the server name as \\SERVER in filemanager then -hit enter and filemanager should display the list of available shares.

    Some people find browsing fails because they don't have the global -guest account set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must -have a valid guest account.

    MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.

    The other big problem people have is that their broadcast address, -netmask or IP address is wrong (specified with the "interfaces" option -in smb.conf)

    24.4. Browsing across subnets

    Since the release of Samba 1.9.17(alpha1) Samba has been -updated to enable it to support the replication of browse lists -across subnet boundaries. New code and options have been added to -achieve this. This section describes how to set this feature up -in different settings.

    To see browse lists that span TCP/IP subnets (ie. networks separated -by routers that don't pass broadcast traffic) you must set up at least -one WINS server. The WINS server acts as a DNS for NetBIOS names, allowing -NetBIOS name to IP address translation to be done by doing a direct -query of the WINS server. This is done via a directed UDP packet on -port 137 to the WINS server machine. The reason for a WINS server is -that by default, all NetBIOS name to IP address translation is done -by broadcasts from the querying machine. This means that machines -on one subnet will not be able to resolve the names of machines on -another subnet without using a WINS server.

    Remember, for browsing across subnets to work correctly, all machines, -be they Windows 95, Windows NT, or Samba servers must have the IP address -of a WINS server given to them by a DHCP server, or by manual configuration -(for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the smb.conf file.

    24.4.1. How does cross subnet browsing work ?

    Cross subnet browsing is a complicated dance, containing multiple -moving parts. It has taken Microsoft several years to get the code -that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly.

    Consider a network set up as follows :

                                       (DMB)
-             N1_A      N1_B        N1_C       N1_D        N1_E
-              |          |           |          |           |
-          -------------------------------------------------------
-            |          subnet 1                       |
-          +---+                                      +---+
-          |R1 | Router 1                  Router 2   |R2 |
-          +---+                                      +---+
-            |                                          |
-            |  subnet 2              subnet 3          |
-  --------------------------       ------------------------------------
-  |     |     |      |               |        |         |           |
- N2_A  N2_B  N2_C   N2_D           N3_A     N3_B      N3_C        N3_D 
-                    (WINS)

    Consisting of 3 subnets (1, 2, 3) connected by two routers -(R1, R2) - these do not pass broadcasts. Subnet 1 has 5 machines -on it, subnet 2 has 4 machines, subnet 3 has 4 machines. Assume -for the moment that all these machines are configured to be in the -same workgroup (for simplicities sake). Machine N1_C on subnet 1 -is configured as Domain Master Browser (ie. it will collate the -browse lists for the workgroup). Machine N2_D is configured as -WINS server and all the other machines are configured to register -their NetBIOS names with it.

    As all these machines are booted up, elections for master browsers -will take place on each of the three subnets. Assume that machine -N1_C wins on subnet 1, N2_B wins on subnet 2, and N3_D wins on -subnet 3 - these machines are known as local master browsers for -their particular subnet. N1_C has an advantage in winning as the -local master browser on subnet 1 as it is set up as Domain Master -Browser.

    On each of the three networks, machines that are configured to -offer sharing services will broadcast that they are offering -these services. The local master browser on each subnet will -receive these broadcasts and keep a record of the fact that -the machine is offering a service. This list of records is -the basis of the browse list. For this case, assume that -all the machines are configured to offer services so all machines -will be on the browse list.

    For each network, the local master browser on that network is -considered 'authoritative' for all the names it receives via -local broadcast. This is because a machine seen by the local -master browser via a local broadcast must be on the same -network as the local master browser and thus is a 'trusted' -and 'verifiable' resource. Machines on other networks that -the local master browsers learn about when collating their -browse lists have not been directly seen - these records are -called 'non-authoritative'.

    At this point the browse lists look as follows (these are -the machines you would see in your network neighborhood if -you looked in it on a particular network right now).

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D

    Note that at this point all the subnets are separate, no -machine is seen across any of the subnets.

    Now examine subnet 2. As soon as N2_B has become the local -master browser it looks for a Domain master browser to synchronize -its browse list with. It does this by querying the WINS server -(N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master -browser (N1_C) with the WINS server as soon as it was booted.

    Once N2_B knows the address of the Domain master browser it -tells it that is the local master browser for subnet 2 by -sending a MasterAnnouncement packet as a UDP port 138 packet. -It then synchronizes with it by doing a NetServerEnum2 call. This -tells the Domain Master Browser to send it all the server -names it knows about. Once the domain master browser receives -the MasterAnnouncement packet it schedules a synchronization -request to the sender of that packet. After both synchronizations -are done the browse lists look like :

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-
-Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on -subnets 1 or 2 will see all the servers on both, users on -subnet 3 will still only see the servers on their own subnet.

    The same sequence of events that occured for N2_B now occurs -for the local master browser on subnet 3 (N3_D). When it -synchronizes browse lists with the domain master browser (N1_A) -it gets both the server entries on subnet 1, and those on -subnet 2. After N3_D has synchronized with N1_C and vica-versa -the browse lists look like.

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-
-Servers with a (*) after them are non-authoritative names.

    At this point users looking in their network neighborhood on -subnets 1 or 3 will see all the servers on all sunbets, users on -subnet 2 will still only see the servers on subnets 1 and 2, but not 3.

    Finally, the local master browser for subnet 2 (N2_B) will sync again -with the domain master browser (N1_C) and will recieve the missing -server entries. Finally - and as a steady state (if no machines -are removed or shut off) the browse lists will look like :

    Subnet           Browse Master   List
-------           -------------   ----
-Subnet1          N1_C            N1_A, N1_B, N1_C, N1_D, N1_E, 
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*),
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
-
-Subnet2          N2_B            N2_A, N2_B, N2_C, N2_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*)
-                                 N3_A(*), N3_B(*), N3_C(*), N3_D(*)
+	protocols:	nis files
+	rpc:		nis files
+	services:	nis files
+

    +Of course, each of these mechanisms requires that the appropriate +facilities and/or services are correctly configured. +

    +It should be noted that unless a network request/message must be +sent, TCP/IP networks are silent. All TCP/IP communications assumes a +principal of speaking only when necessary. +

    +Starting with version 2.2.0 samba has Linux support for extensions to +the name service switch infrastructure so that linux clients will +be able to obtain resolution of MS Windows NetBIOS names to IP +Addresses. To gain this functionality Samba needs to be compiled +with appropriate arguments to the make command (ie: make +nsswitch/libnss_wins.so). The resulting library should +then be installed in the /lib directory and +the "wins" parameter needs to be added to the "hosts:" line in +the /etc/nsswitch.conf file. At this point it +will be possible to ping any MS Windows machine by it's NetBIOS +machine name, so long as that machine is within the workgroup to +which both the samba machine and the MS Windows machine belong. +

    Name resolution as used within MS Windows networking

    +MS Windows networking is predicated about the name each machine +is given. This name is known variously (and inconsistently) as +the "computer name", "machine name", "networking name", "netbios name", +"SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a +simply name with which the machine is associated. All NetBIOS names +are exactly 16 characters in length. The 16th character is reserved. +It is used to store a one byte value that indicates service level +information for the NetBIOS name that is registered. A NetBIOS machine +name is therefore registered for each service type that is provided by +the client/server. +

    +The following are typical NetBIOS name/service type registrations: +

    +	Unique NetBIOS Names:
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
 
-Subnet3          N3_D            N3_A, N3_B, N3_C, N3_D
-                                 N1_A(*), N1_B(*), N1_C(*), N1_D(*), N1_E(*),
-                                 N2_A(*), N2_B(*), N2_C(*), N2_D(*)
-	
-Servers with a (*) after them are non-authoritative names.

    Synchronizations between the domain master browser and local -master browsers will continue to occur, but this should be a -steady state situation.

    If either router R1 or R2 fails the following will occur:

    1. Names of computers on each side of the inaccessible network fragments - will be maintained for as long as 36 minutes, in the network neighbourhood - lists. -

    2. Attempts to connect to these inaccessible computers will fail, but the - names will not be removed from the network neighbourhood lists. -

    3. If one of the fragments is cut off from the WINS server, it will only - be able to access servers on its local subnet, by using subnet-isolated - broadcast NetBIOS name resolution. The effects are similar to that of - losing access to a DNS server. -

    24.5. Setting up a WINS server

    Either a Samba machine or a Windows NT Server machine may be set up -as a WINS server. To set a Samba machine to be a WINS server you must -add the following option to the smb.conf file on the selected machine : -in the [globals] section add the line

    wins support = yes

    Versions of Samba prior to 1.9.17 had this parameter default to -yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to a recent version, or at the very -least set the parameter to 'no' on all these machines.

    Machines with wins support = yes will keep a list of -all NetBIOS names registered with them, acting as a DNS for NetBIOS names.

    You should set up only ONE wins server. Do NOT set the -wins support = yes option on more than one Samba -server.

    To set up a Windows NT Server as a WINS server you need to set up -the WINS service - see your NT documentation for details. Note that -Windows NT WINS Servers can replicate to each other, allowing more -than one to be set up in a complex subnet environment. As Microsoft -refuse to document these replication protocols Samba cannot currently -participate in these replications. It is possible in the future that -a Samba->Samba WINS replication protocol may be defined, in which -case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the -wins support = yes parameter set.

    After the WINS server has been configured you must ensure that all -machines participating on the network are configured with the address -of this WINS server. If your WINS server is a Samba machine, fill in -the Samba machine IP address in the "Primary WINS Server" field of -the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs -in Windows 95 or Windows NT. To tell a Samba server the IP address -of the WINS server add the following line to the [global] section of -all smb.conf files :

    wins server = >name or IP address<

    where >name or IP address< is either the DNS name of the WINS server -machine or its IP address.

    Note that this line MUST NOT BE SET in the smb.conf file of the Samba -server acting as the WINS server itself. If you set both the -wins support = yes option and the -wins server = <name> option then -nmbd will fail to start.

    There are two possible scenarios for setting up cross subnet browsing. -The first details setting up cross subnet browsing on a network containing -Windows 95, Samba and Windows NT machines that are not configured as -part of a Windows NT Domain. The second details setting up cross subnet -browsing on networks that contain NT Domains.

    24.6. Setting up Browsing in a WORKGROUP

    To set up cross subnet browsing on a network containing machines -in up to be in a WORKGROUP, not an NT Domain you need to set up one -Samba server to be the Domain Master Browser (note that this is *NOT* -the same as a Primary Domain Controller, although in an NT Domain the -same machine plays both roles). The role of a Domain master browser is -to collate the browse lists from local master browsers on all the -subnets that have a machine participating in the workgroup. Without -one machine configured as a domain master browser each subnet would -be an isolated workgroup, unable to see any machines on any other -subnet. It is the presense of a domain master browser that makes -cross subnet browsing possible for a workgroup.

    In an WORKGROUP environment the domain master browser must be a -Samba server, and there must only be one domain master browser per -workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the smb.conf file :

    domain master = yes

    The domain master browser should also preferrably be the local master -browser for its own subnet. In order to achieve this set the following -options in the [global] section of the smb.conf file :

    domain master = yes
-local master = yes
-preferred master = yes
-os level = 65

    The domain master browser may be the same machine as the WINS -server, if you require.

    Next, you should ensure that each of the subnets contains a -machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the -smb.conf file :

    domain master = no
-local master = yes
-preferred master = yes
-os level = 65

    Do not do this for more than one Samba server on each subnet, -or they will war with each other over which is to be the local -master browser.

    The local master parameter allows Samba to act as a -local master browser. The preferred master causes nmbd -to force a browser election on startup and the os level -parameter sets Samba high enough so that it should win any browser elections.

    If you have an NT machine on the subnet that you wish to -be the local master browser then you can disable Samba from -becoming a local master browser by setting the following -options in the [global] section of the -smb.conf file :

    domain master = no
-local master = no
-preferred master = no
-os level = 0

    24.7. Setting up Browsing in a DOMAIN

    If you are adding Samba servers to a Windows NT Domain then -you must not set up a Samba server as a domain master browser. -By default, a Windows NT Primary Domain Controller for a Domain -name is also the Domain master browser for that name, and many -things will break if a Samba server registers the Domain master -browser NetBIOS name (DOMAIN<1B>) -with WINS instead of the PDC.

    For subnets other than the one containing the Windows NT PDC -you may set up Samba servers as local master browsers as -described. To make a Samba server a local master browser set -the following options in the [global] section -of the smb.conf file :

    domain master = no
-local master = yes
-preferred master = yes
-os level = 65

    If you wish to have a Samba server fight the election with machines -on the same subnet you may set the os level parameter -to lower levels. By doing this you can tune the order of machines that -will become local master browsers if they are running. For -more details on this see the section Forcing samba to be the master browser -below.

    If you have Windows NT machines that are members of the domain -on all subnets, and you are sure they will always be running then -you can disable Samba from taking part in browser elections and -ever becoming a local master browser by setting following options -in the [global] section of the smb.conf -file :

    domain master = no - local master = no - preferred master = no - os level = 0

    24.8. Forcing samba to be the master

    Who becomes the master browser is determined by an election -process using broadcasts. Each election packet contains a number of parameters -which determine what precedence (bias) a host should have in the -election. By default Samba uses a very low precedence and thus loses -elections to just about anyone else.

    If you want Samba to win elections then just set the os level global -option in smb.conf to a higher number. It defaults to 0. Using 34 -would make it win all elections over every other system (except other -samba systems!)

    A os level of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.

    The maximum os level is 255

    If you want samba to force an election on startup, then set the -preferred master global option in smb.conf to "yes". Samba will -then have a slight advantage over other potential master browsers -that are not preferred master browsers. Use this parameter with -care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with preferred master to -"yes", then periodically and continually they will force an election -in order to become the local master browser.

    If you want samba to be a domain master browser, then it is -recommended that you also set preferred master to "yes", because -samba will not become a domain master browser for the whole of your -LAN or WAN if it is not also a local master browser on its own -broadcast isolated subnet.

    It is possible to configure two samba servers to attempt to become -the domain master browser for a domain. The first server that comes -up will be the domain master browser. All other samba servers will -attempt to become the domain master browser every 5 minutes. They -will find that another samba server is already the domain master -browser and will fail. This provides automatic redundancy, should -the current domain master browser fail.

    24.9. Making samba the domain master

    The domain master is responsible for collating the browse lists of -multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting domain master = yes -in smb.conf. By default it will not be a domain master.

    Note that you should NOT set Samba to be the domain master for a -workgroup that has the same name as an NT Domain.

    When samba is the domain master and the master browser it will listen -for master announcements (made roughly every twelve minutes) from local -master browsers on other subnets and then contact them to synchronise -browse lists.

    If you want samba to be the domain master then I suggest you also set -the os level high enough to make sure it wins elections, and set -preferred master to "yes", to get samba to force an election on -startup.

    Note that all your servers (including samba) and clients should be -using a WINS server to resolve NetBIOS names. If your clients are only -using broadcasting to resolve NetBIOS names, then two things will occur:

    1. your local master browsers will be unable to find a domain master - browser, as it will only be looking on the local subnet. -

    2. if a client happens to get hold of a domain-wide browse list, and - a user attempts to access a host in that list, it will be unable to - resolve the NetBIOS name of that host. -

    If, however, both samba and your clients are using a WINS server, then:

    1. your local master browsers will contact the WINS server and, as long as - samba has registered that it is a domain master browser with the WINS - server, your local master browser will receive samba's ip address - as its domain master browser. -

    2. when a client receives a domain-wide browse list, and a user attempts - to access a host in that list, it will contact the WINS server to - resolve the NetBIOS name of that host. as long as that host has - registered its NetBIOS name with the same WINS server, the user will - be able to see that host. -

    24.10. Note about broadcast addresses

    If your network uses a "0" based broadcast address (for example if it -ends in a 0) then you will strike problems. Windows for Workgroups -does not seem to support a 0's broadcast and you will probably find -that browsing and name lookups won't work.

    24.11. Multiple interfaces

    Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the interfaces -option in smb.conf to configure them.

    Chapter 25. Securing Samba

    25.1. Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an + Group Names: + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers +

    +It should be noted that all NetBIOS machines register their own +names as per the above. This is in vast contrast to TCP/IP +installations where traditionally the system administrator will +determine in the /etc/hosts or in the DNS database what names +are associated with each IP address. +

    +One further point of clarification should be noted, the /etc/hosts +file and the DNS records do not provide the NetBIOS name type information +that MS Windows clients depend on to locate the type of service that may +be needed. An example of this is what happens when an MS Windows client +wants to locate a domain logon server. It finds this service and the IP +address of a server that provides it by performing a lookup (via a +NetBIOS broadcast) for enumeration of all machines that have +registered the name type *<1c>. A logon request is then sent to each +IP address that is returned in the enumerated list of IP addresses. Which +ever machine first replies then ends up providing the logon services. +

    +The name "workgroup" or "domain" really can be confusing since these +have the added significance of indicating what is the security +architecture of the MS Windows network. The term "workgroup" indicates +that the primary nature of the network environment is that of a +peer-to-peer design. In a WORKGROUP all machines are responsible for +their own security, and generally such security is limited to use of +just a password (known as SHARE MODE security). In most situations +with peer-to-peer networking the users who control their own machines +will simply opt to have no security at all. It is possible to have +USER MODE security in a WORKGROUP environment, thus requiring use +of a user name and a matching password. +

    +MS Windows networking is thus predetermined to use machine names +for all local and remote machine message passing. The protocol used is +called Server Message Block (SMB) and this is implemented using +the NetBIOS protocol (Network Basic Input Output System). NetBIOS can +be encapsulated using LLC (Logical Link Control) protocol - in which case +the resulting protocol is called NetBEUI (Network Basic Extended User +Interface). NetBIOS can also be run over IPX (Internetworking Packet +Exchange) protocol as used by Novell NetWare, and it can be run +over TCP/IP protocols - in which case the resulting protocol is called +NBT or NetBT, the NetBIOS over TCP/IP. +

    +MS Windows machines use a complex array of name resolution mechanisms. +Since we are primarily concerned with TCP/IP this demonstration is +limited to this area. +

    The NetBIOS Name Cache

    +All MS Windows machines employ an in memory buffer in which is +stored the NetBIOS names and IP addresses for all external +machines that that machine has communicated with over the +past 10-15 minutes. It is more efficient to obtain an IP address +for a machine from the local cache than it is to go through all the +configured name resolution mechanisms. +

    +If a machine whose name is in the local name cache has been shut +down before the name had been expired and flushed from the cache, then +an attempt to exchange a message with that machine will be subject +to time-out delays. i.e.: Its name is in the cache, so a name resolution +lookup will succeed, but the machine can not respond. This can be +frustrating for users - but it is a characteristic of the protocol. +

    +The MS Windows utility that allows examination of the NetBIOS +name cache is called "nbtstat". The Samba equivalent of this +is called "nmblookup". +

    The LMHOSTS file

    +This file is usually located in MS Windows NT 4.0 or +2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains +the IP Address and the machine name in matched pairs. The +LMHOSTS file performs NetBIOS name +to IP address mapping. +

    +It typically looks like: +

    +	# Copyright (c) 1998 Microsoft Corp.
+	#
+	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
+	# over TCP/IP) stack for Windows98
+	#
+	# This file contains the mappings of IP addresses to NT computernames
+	# (NetBIOS) names.  Each entry should be kept on an individual line.
+	# The IP address should be placed in the first column followed by the
+	# corresponding computername. The address and the comptername
+	# should be separated by at least one space or tab. The "#" character
+	# is generally used to denote the start of a comment (see the exceptions
+	# below).
+	#
+	# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
+	# files and offers the following extensions:
+	#
+	#      #PRE
+	#      #DOM:<domain>
+	#      #INCLUDE <filename>
+	#      #BEGIN_ALTERNATE
+	#      #END_ALTERNATE
+	#      \0xnn (non-printing character support)
+	#
+	# Following any entry in the file with the characters "#PRE" will cause
+	# the entry to be preloaded into the name cache. By default, entries are
+	# not preloaded, but are parsed only after dynamic name resolution fails.
+	#
+	# Following an entry with the "#DOM:<domain>" tag will associate the
+	# entry with the domain specified by <domain>. This affects how the
+	# browser and logon services behave in TCP/IP environments. To preload
+	# the host name associated with #DOM entry, it is necessary to also add a
+	# #PRE to the line. The <domain> is always preloaded although it will not
+	# be shown when the name cache is viewed.
+	#
+	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
+	# software to seek the specified <filename> and parse it as if it were
+	# local. <filename> is generally a UNC-based name, allowing a
+	# centralized lmhosts file to be maintained on a server.
+	# It is ALWAYS necessary to provide a mapping for the IP address of the
+	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
+	# In addtion the share "public" in the example below must be in the
+	# LanManServer list of "NullSessionShares" in order for client machines to
+	# be able to read the lmhosts file successfully. This key is under
+	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
+	# in the registry. Simply add "public" to the list found there.
+	#
+	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
+	# statements to be grouped together. Any single successful include
+	# will cause the group to succeed.
+	#
+	# Finally, non-printing characters can be embedded in mappings by
+	# first surrounding the NetBIOS name in quotations, then using the
+	# \0xnn notation to specify a hex value for a non-printing character.
+	#
+	# The following example illustrates all of these extensions:
+	#
+	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
+	# 102.54.94.102    "appname  \0x14"                    #special app server
+	# 102.54.94.123    popular            #PRE             #source server
+	# 102.54.94.117    localsrv           #PRE             #needed for the include
+	#
+	# #BEGIN_ALTERNATE
+	# #INCLUDE \\localsrv\public\lmhosts
+	# #INCLUDE \\rhino\public\lmhosts
+	# #END_ALTERNATE
+	#
+	# In the above example, the "appname" server contains a special
+	# character in its name, the "popular" and "localsrv" server names are
+	# preloaded, and the "rhino" server name is specified so it can be used
+	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+	# system is unavailable.
+	#
+	# Note that the whole file is parsed including comments on each lookup,
+	# so keeping the number of comments to a minimum will improve performance.
+	# Therefore it is not advisable to simply add lmhosts file entries onto the
+	# end of this file.
+

    HOSTS file

    +This file is usually located in MS Windows NT 4.0 or 2000 in +C:\WINNT\SYSTEM32\DRIVERS\ETC and contains +the IP Address and the IP hostname in matched pairs. It can be +used by the name resolution infrastructure in MS Windows, depending +on how the TCP/IP environment is configured. This file is in +every way the equivalent of the Unix/Linux /etc/hosts file. +

    DNS Lookup

    +This capability is configured in the TCP/IP setup area in the network +configuration facility. If enabled an elaborate name resolution sequence +is followed the precise nature of which is dependant on what the NetBIOS +Node Type parameter is configured to. A Node Type of 0 means use +NetBIOS broadcast (over UDP broadcast) is first used if the name +that is the subject of a name lookup is not found in the NetBIOS name +cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to +Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the +WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast +lookup is used. +

    WINS Lookup

    +A WINS (Windows Internet Name Server) service is the equivaent of the +rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores +the names and IP addresses that are registered by a Windows client +if the TCP/IP setup has been given at least one WINS Server IP Address. +

    +To configure Samba to be a WINS server the following parameter needs +to be added to the smb.conf file: +

    +	wins support = Yes
+

    +To configure Samba to use a WINS server the following parameters are +needed in the smb.conf file: +

    +	wins support = No
+	wins server = xxx.xxx.xxx.xxx
+

    +where xxx.xxx.xxx.xxx is the IP address +of the WINS server. +

    Chapter24.Securing Samba

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    17 March 2003

    Table of Contents

    Introduction
    Using host based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba

    Introduction

    +This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba -installations in general.

    25.2. Using host based protection

    In many installations of Samba the greatest threat comes for outside +installations in general. +

    Using host based protection

    +In many installations of Samba the greatest threat comes for outside your immediate network. By default Samba will accept connections from any host, which means that if you run an insecure version of Samba on a host that is directly connected to the Internet you can be -especially vulnerable.

    One of the simplest fixes in this case is to use the hosts allow and -hosts deny options in the Samba smb.conf configuration file to only +especially vulnerable. +

    +One of the simplest fixes in this case is to use the hosts allow and +hosts deny options in the Samba smb.conf configuration file to only allow access to your server from a specific range of hosts. An example -might be:

      hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
-  hosts deny = 0.0.0.0/0

    The above will only allow SMB connections from 'localhost' (your own +might be: +

    +	hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
+	hosts deny = 0.0.0.0/0
+

    +The above will only allow SMB connections from 'localhost' (your own computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused connections as soon +192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error.

    25.3. Using interface protection

    By default Samba will accept connections on any network interface that +'not listening on called name' error. +

    Using interface protection

    +By default Samba will accept connections on any network interface that it finds on your system. That means if you have a ISDN line or a PPP connection to the Internet then Samba will accept connections on those -links. This may not be what you want.

    You can change this behaviour using options like the following:

      interfaces = eth* lo
-  bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a +links. This may not be what you want. +

    +You can change this behaviour using options like the following: +

    +	interfaces = eth* lo
+	bind interfaces only = yes
+

    +This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what OS you are using, in the above I used the common name for Ethernet -adapters on Linux.

    If you use the above and someone tries to make a SMB connection to +adapters on Linux. +

    +If you use the above and someone tries to make a SMB connection to your host over a PPP interface called 'ppp0' then they will get a TCP connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that -interface to any process.

    25.4. Using a firewall

    Many people use a firewall to deny access to services that they don't +interface to any samba process. +

    Using a firewall

    +Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above methods so that you are protected even if your firewall is not active -for some reason.

    If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following:

    UDP/137    - used by nmbd
-UDP/138    - used by nmbd
-TCP/139    - used by smbd
-TCP/445    - used by smbd

    The last one is important as many older firewall setups may not be +for some reason. +

    +If you are setting up a firewall then you need to know what TCP and +UDP ports to allow and block. Samba uses the following: +

    +	UDP/137    - used by nmbd
+	UDP/138    - used by nmbd
+	TCP/139    - used by smbd
+	TCP/445    - used by smbd
+

    +The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in -recent years.

    25.5. Using a IPC$ share deny

    If the above methods are not suitable, then you could also place a +recent years. +

    Using a IPC$ share deny

    +If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that is used in the recently discovered security hole. This allows you to offer access to other shares while denying access to IPC$ from potentially untrustworthy -hosts.

    To do that you could use:

      [ipc$]
-     hosts allow = 192.168.115.0/24 127.0.0.1
-     hosts deny = 0.0.0.0/0

    this would tell Samba that IPC$ connections are not allowed from +hosts. +

    +To do that you could use: +

    +	[ipc$]
+	     hosts allow = 192.168.115.0/24 127.0.0.1
+	     hosts deny = 0.0.0.0/0
+

    +this would tell Samba that IPC$ connections are not allowed from anywhere but the two listed places (localhost and a local subnet). Connections to other shares would still be allowed. As the IPC$ share is the only share that is always accessible anonymously this provides some level of protection against attackers that do not -know a username/password for your host.

    If you use this method then clients will be given a 'access denied' +know a username/password for your host. +

    +If you use this method then clients will be given a 'access denied' reply when they try to access the IPC$ share. That means that those clients will not be able to browse shares, and may also be unable to -access some other resources.

    This is not recommended unless you cannot use one of the other -methods listed above for some reason.

    25.6. Upgrading Samba

    Please check regularly on http://www.samba.org/ for updates and +access some other resources. +

    +This is not recommended unless you cannot use one of the other +methods listed above for some reason. +

    NTLMv2 Security

    +To configure NTLMv2 authentication the following registry keys are worth knowing about: +

    +

    +	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
+	"lmcompatibilitylevel"=dword:00000003
+
+	0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
+	use NTLMv2 session security if the server supports it. Domain
+	controllers accept LM, NTLM and NTLMv2 authentication.
+
+	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
+	"NtlmMinClientSec"=dword:00080000
+
+	0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
+	NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
+	session security is not negotiated.
+

    +

    Upgrading Samba

    +Please check regularly on http://www.samba.org/ for updates and important announcements. Occasionally security releases are made and it is highly recommended to upgrade Samba when a security vulnerability -is discovered.

    Chapter 26. Unicode/Charsets

    26.1. What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be +is discovered. +

    Chapter25.Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    TAKAHASHI Motonobu

    <monyo@home.monyo.com>

    25 March 2003

    Table of Contents

    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets

    What are charsets and unicode?

    +Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned -to a certain number depends on the character set(charset) that is used. +to a certain number depends on the character set(charset) + that is used. A charset can be seen as a table that is used to translate numbers to letters. Not all computers use the same charset (there are charsets with German umlauts, Japanese characters, etc). Usually a charset contains 256 characters, which means that storing a character with it takes -exactly one byte.

    There are also charsets that support even more characters, +exactly one byte.

    +There are also charsets that support even more characters, but those need twice(or even more) as much storage space. These -charsets can contain 256 * 256 = 65536 characters, which +charsets can contain 256 * 256 = 65536 characters, which is more then all possible characters one could think of. They are called multibyte charsets (because they use more then one byte to -store one character).

    A standardised multibyte charset is unicode, info available at -www.unicode.org. -Big advantage of using a multibyte charset is that you only need one; no +store one character). +

    +A standardised multibyte charset is unicode, info is available at +www.unicode.org. +A big advantage of using a multibyte charset is that you only need one; no need to make sure two computers use the same charset when they are -communicating.

    Old windows clients used to use single-byte charsets, named +communicating. +

    Old windows clients used to use single-byte charsets, named 'codepages' by microsoft. However, there is no support for negotiating the charset to be used in the smb protocol. Thus, you have to make sure you are using the same charset when talking to an old client. -Newer clients (Windows NT, 2K, XP) talk unicode over the wire.

    26.2. Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, -samba knows of three kinds of character sets:

    unix charset

    This is the charset used internally by your operating system. - The default is ASCII, which is fine for most +Newer clients (Windows NT, 2K, XP) talk unicode over the wire. +

    Samba and charsets

    +As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, +samba knows of three kinds of character sets: +

    unix charset

    + This is the charset used internally by your operating system. + The default is ASCII, which is fine for most systems. -

    display charset

    This is the charset samba will use to print messages - on your screen. It should generally be the same as the unix charset. -

    dos charset

    This is the charset samba uses when communicating with +

    display charset

    This is the charset samba will use to print messages + on your screen. It should generally be the same as the unix charset. +

    dos charset

    This is the charset samba uses when communicating with DOS and Windows 9x clients. It will talk unicode to all newer clients. The default depends on the charsets you have installed on your system. - Run testparm -v | grep "dos charset" to see + Run testparm -v | grep "dos charset" to see what the default is on your system. -

    26.3. Conversion from old names

    Because previous samba versions did not do any charset conversion, +

    Conversion from old names

    Because previous samba versions did not do any charset conversion, characters in filenames are usually not correct in the unix charset but only -for the local charset used by the DOS/Windows clients.

    The following script from Steve Langasek converts all -filenames from CP850 to the iso8859-15 charset.

    #find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ - -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;

    26.4. Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:

    You should set mangling method = hash
    There are various iconv() implementations around and not all of -them work equally well. glibc2's iconv() has a critical problem in CP932. -libiconv-1.8 works with CP932 but still has some problems and does not -work with EUC-JP.
    You should set dos charset = CP932, not Shift_JIS, SJIS...
    Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. unix charset = EUC-JP doesn't work well because of iconv() issues.
    Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    IV. Appendixes

    Chapter 27. How to compile SAMBA

    You can obtain the samba source from the samba website. To obtain a development version, -you can download samba from CVS or using rsync.

    27.1. Access Samba source code via CVS

    27.1.1. Introduction

    Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can +for the local charset used by the DOS/Windows clients.

    The following script from Steve Langasek converts all +filenames from CP850 to the iso8859-15 charset.

    +#find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ + -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; + +

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are +points of attention when setting it up:

    • You should set mangling method = +hash

    • There are various iconv() implementations around and not +all of them work equally well. glibc2's iconv() has a critical problem +in CP932. libiconv-1.8 works with CP932 but still has some problems and +does not work with EUC-JP.

    • You should set dos charset = CP932, not +Shift_JIS, SJIS...

    • Currently only unix charset = CP932 +will work (but still has some problems...) because of iconv() issues. +unix charset = EUC-JP doesn't work well because of +iconv() issues.

    • Currently Samba 3.0 does not support unix charset += UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    Chapter26.File and Record Locking

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Table of Contents

    Discussion
    Samba Opportunistic Locking Control
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Additional Reading

    Discussion

    +One area which sometimes causes trouble is locking. +

    +There are two types of locking which need to be performed by a SMB server. +The first is record locking which allows a client to lock +a range of bytes in a open file. The second is the deny modes +that are specified when a file is open. +

    +Record locking semantics under Unix is very different from record locking under +Windows. Versions of Samba before 2.2 have tried to use the native fcntl() unix +system call to implement proper record locking between different Samba clients. +This can not be fully correct due to several reasons. The simplest is the fact +that a Windows client is allowed to lock a byte range up to 2^32 or 2^64, +depending on the client OS. The unix locking only supports byte ranges up to 2^31. +So it is not possible to correctly satisfy a lock request above 2^31. There are +many more differences, too many to be listed here. +

    +Samba 2.2 and above implements record locking completely independent of the +underlying unix system. If a byte range lock that the client requests happens +to fall into the range 0-2^31, Samba hands this request down to the Unix system. +All other locks can not be seen by unix anyway. +

    +Strictly a SMB server should check for locks before every read and write call on +a file. Unfortunately with the way fcntl() works this can be slow and may overstress +the rpc.lockd. It is also almost always unnecessary as clients are supposed to +independently make locking calls before reads and writes anyway if locking is +important to them. By default Samba only makes locking calls when explicitly asked +to by a client, but if you set strict locking = yes then it +will make lock checking calls on every read and write. +

    +You can also disable by range locking completely using locking = no. +This is useful for those shares that don't support locking or don't need it +(such as cdroms). In this case Samba fakes the return codes of locking calls to +tell clients that everything is OK. +

    +The second class of locking is the deny modes. These +are set by an application when it opens a file to determine what types of +access should be allowed simultaneously with its open. A client may ask for +DENY_NONE, DENY_READ, DENY_WRITE or DENY_ALL. There are also special compatibility +modes called DENY_FCB and DENY_DOS. +

    Samba Opportunistic Locking Control

    +Opportunistic locking essentially means that the client is allowed to download and cache +a file on their hard drive while making changes; if a second client wants to access the +file, the first client receives a break and must synchronise the file back to the server. +This can give significant performance gains in some cases; some programs insist on +synchronising the contents of the entire file back to the server for a single change. +

    +Level1 Oplocks (aka just plain "oplocks") is another term for opportunistic locking. +

    +Level2 Oplocks provids opportunistic locking for a file that will be treated as +read only. Typically this is used on files that are read-only or +on files that the client has no initial intention to write to at time of opening the file. +

    +Kernel Oplocks are essentially a method that allows the Linux kernel to co-exist with +Samba's oplocked files, although this has provided better integration of MS Windows network +file locking with the under lying OS, SGI IRIX and Linux are the only two OS's that are +oplock aware at this time. +

    +Unless your system supports kernel oplocks, you should disable oplocks if you are +accessing the same files from both Unix/Linux and SMB clients. Regardless, oplocks should +always be disabled if you are sharing a database file (e.g., Microsoft Access) between +multiple clients, as any break the first client receives will affect synchronisation of +the entire file (not just the single record), which will result in a noticable performance +impairment and, more likely, problems accessing the database in the first place. Notably, +Microsoft Outlook's personal folders (*.pst) react very badly to oplocks. If in doubt, +disable oplocks and tune your system from that point. +

    +If client-side caching is desirable and reliable on your network, you will benefit from +turning on oplocks. If your network is slow and/or unreliable, or you are sharing your +files among other file sharing mechanisms (e.g., NFS) or across a WAN, or multiple people +will be accessing the same files frequently, you probably will not benefit from the overhead +of your client sending oplock breaks and will instead want to disable oplocks for the share. +

    +Another factor to consider is the perceived performance of file access. If oplocks provide no +measurable speed benefit on your network, it might not be worth the hassle of dealing with them. +

    +You can disable oplocks on a per-share basis with the following: + +

    +	oplocks = False
+	level2 oplocks = False
+

    + +Alternately, you could disable oplocks on a per-file basis within the share: + +

    +	veto oplock files = /*.mdb/*.MDB/*.dbf/*.DBF/
+

    +

    +If you are experiencing problems with oplocks as apparent from Samba's log entries, +you may want to play it safe and disable oplocks and level2 oplocks. +

    MS Windows Opportunistic Locking and Caching Controls

    +There is a known issue when running applications (like Norton Anti-Virus) on a Windows 2000/ XP +workstation computer that can affect any application attempting to access shared database files +across a network. This is a result of a default setting configured in the Windows 2000/XP +operating system known as Opportunistic Locking. When a workstation +attempts to access shared data files located on another Windows 2000/XP computer, +the Windows 2000/XP operating system will attempt to increase performance by locking the +files and caching information locally. When this occurs, the application is unable to +properly function, which results in an Access Denied + error message being displayed during network operations. +

    +All Windows operating systems in the NT family that act as database servers for data files +(meaning that data files are stored there and accessed by other Windows PCs) may need to +have opportunistic locking disabled in order to minimize the risk of data file corruption. +This includes Windows 9x/Me, Windows NT, Windows 200x and Windows XP. +

    +If you are using a Windows NT family workstation in place of a server, you must also +disable opportunistic locking (oplocks) on that workstation. For example, if you use a +PC with the Windows NT Workstation operating system instead of Windows NT Server, and you +have data files located on it that are accessed from other Windows PCs, you may need to +disable oplocks on that system. +

    +The major difference is the location in the Windows registry where the values for disabling +oplocks are entered. Instead of the LanManServer location, the LanManWorkstation location +may be used. +

    +You can verify (or change or add, if necessary) this Registry value using the Windows +Registry Editor. When you change this registry value, you will have to reboot the PC +to ensure that the new setting goes into effect. +

    +The location of the client registry entry for opportunistic locking has changed in +Windows 2000 from the earlier location in Microsoft Windows NT. +

    Note

    +Windows 2000 will still respect the EnableOplocks registry value used to disable oplocks +in earlier versions of Windows. +

    +You can also deny the granting of opportunistic locks by changing the following registry entries: +

    +

    +	HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
+
+		OplocksDisabled REG_DWORD 0 or 1
+		Default: 0 (not disabled)
+

    +

    Note

    +The OplocksDisabled registry value configures Windows clients to either request or not +request opportunistic locks on a remote file. To disable oplocks, the value of + OplocksDisabled must be set to 1. +

    +

    +	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
+
+		EnableOplocks REG_DWORD 0 or 1
+		Default: 1 (Enabled by Default)
+
+		EnableOpLockForceClose REG_DWORD 0 or 1
+		Default: 0 (Disabled by Default)
+

    +

    Note

    +The EnableOplocks value configures Windows-based servers (including Workstations sharing +files) to allow or deny opportunistic locks on local files. +

    +To force closure of open oplocks on close or program exit EnableOpLockForceClose must be set to 1. +

    +An illustration of how level II oplocks work: +

    • + Station 1 opens the file, requesting oplock. +

    • + Since no other station has the file open, the server grants station 1 exclusive oplock. +

    • + Station 2 opens the file, requesting oplock. +

    • + Since station 1 has not yet written to the file, the server asks station 1 to Break + to Level II Oplock. +

    • + Station 1 complies by flushing locally buffered lock information to the server. +

    • + Station 1 informs the server that it has Broken to Level II Oplock (alternatively, + station 1 could have closed the file). +

    • + The server responds to station 2's open request, granting it level II oplock. + Other stations can likewise open the file and obtain level II oplock. +

    • + Station 2 (or any station that has the file open) sends a write request SMB. + The server returns the write response. +

    • + The server asks all stations that have the file open to Break to None, meaning no + station holds any oplock on the file. Because the workstations can have no cached + writes or locks at this point, they need not respond to the break-to-none advisory; + all they need do is invalidate locally cashed read-ahead data. +

    Workstation Service Entries

    +	\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
+
+	UseOpportunisticLocking   REG_DWORD   0 or 1
+	Default: 1 (true)
+

    +Indicates whether the redirector should use opportunistic-locking (oplock) performance +enhancement. This parameter should be disabled only to isolate problems. +

    Server Service Entries

    +	\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
+
+	EnableOplocks   REG_DWORD   0 or 1
+	Default: 1 (true)
+

    +Specifies whether the server allows clients to use oplocks on files. Oplocks are a +significant performance enhancement, but have the potential to cause lost cached +data on some networks, particularly wide-area networks. +

    +	MinLinkThroughput   REG_DWORD   0 to infinite bytes per second
+	Default: 0
+

    +Specifies the minimum link throughput allowed by the server before it disables +raw and opportunistic locks for this connection. +

    +	MaxLinkDelay   REG_DWORD   0 to 100,000 seconds
+	Default: 60
+

    +Specifies the maximum time allowed for a link delay. If delays exceed this number, +the server disables raw I/O and opportunistic locking for this connection. +

    +	OplockBreakWait   REG_DWORD   10 to 180 seconds
+	Default: 35
+

    +Specifies the time that the server waits for a client to respond to an oplock break +request. Smaller values can allow detection of crashed clients more quickly but can +potentially cause loss of cached data. +

    Persistent Data Corruption

    +If you have applied all of the settings discussed in this paper but data corruption problems +and other symptoms persist, here are some additional things to check out: +

    +We have credible reports from developers that faulty network hardware, such as a single +faulty network card, can cause symptoms similar to read caching and data corruption. +If you see persistent data corruption even after repeated reindexing, you may have to +rebuild the data files in question. This involves creating a new data file with the +same definition as the file to be rebuilt and transferring the data from the old file +to the new one. There are several known methods for doing this that can be found in +our Knowledge Base. +

    Additional Reading

    +You may want to check for an updated version of this white paper on our Web site from +time to time. Many of our white papers are updated as information changes. For those papers, +the Last Edited date is always at the top of the paper. +

    +Section of the Microsoft MSDN Library on opportunistic locking: +

    +Opportunistic Locks, Microsoft Developer Network (MSDN), Windows Development > +Windows Base Services > Files and I/O > SDK Documentation > File Storage > File Systems +> About File Systems > Opportunistic Locks, Microsoft Corporation. +http://msdn.microsoft.com/library/en-us/fileio/storage_5yk3.asp +

    +Microsoft Knowledge Base Article Q224992 "Maintaining Transactional Integrity with OPLOCKS", +Microsoft Corporation, April 1999, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224992. +

    +Microsoft Knowledge Base Article Q296264 "Configuring Opportunistic Locking in Windows 2000", +Microsoft Corporation, April 2001, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264. +

    +Microsoft Knowledge Base Article Q129202 "PC Ext: Explanation of Opportunistic Locking on Windows NT", + Microsoft Corporation, April 1995, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q129202. +

    Troubleshooting

    Table of Contents

    27. The samba checklist
    Introduction
    Assumptions
    The tests
    Still having troubles?
    28. Analysing and solving samba problems
    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URL's
    Getting help from the mailing lists
    How to get off the mailinglists
    29. Reporting Bugs
    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Chapter27.The samba checklist

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests
    Still having troubles?

    Introduction

    +This file contains a list of tests you can perform to validate your +Samba server. It also tells you what the likely cause of the problem +is if it fails any one of these steps. If it passes all these tests +then it is probably working fine. +

    +You should do ALL the tests, in the order shown. We have tried to +carefully choose them so later tests only use capabilities verified in +the earlier tests. However, do not stop at the first error as there +have been some instances when continuing with the tests has helped +to solve a problem. +

    +If you send one of the samba mailing lists an email saying "it doesn't work" +and you have not followed this test procedure then you should not be surprised +if your email is ignored. +

    Assumptions

    +In all of the tests it is assumed you have a Samba server called +BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP. +

    +The procedure is similar for other types of clients. +

    +It is also assumed you know the name of an available share in your +smb.conf. I will assume this share is called tmp. +You can add a tmp share like this by adding the +following to smb.conf: +

    +
+[tmp]
+ comment = temporary files 
+ path = /tmp
+ read only = yes
+
+

    +

    Note

    +These tests assume version 3.0 or later of the samba suite. +Some commands shown did not exist in earlier versions. +

    +Please pay attention to the error messages you receive. If any error message +reports that your server is being unfriendly you should first check that your +IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf +file points to name servers that really do exist. +

    +Also, if you do not have DNS server access for name resolution please check +that the settings for your smb.conf file results in dns proxy = no. The +best way to check this is with testparm smb.conf. +

    +It is helpful to monitor the log files during testing by using the +tail -F log_file_name in a separate +terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). +Relevant log files can be found (for default installations) in +/usr/local/samba/var. Also, connection logs from +machines can be found here or possibly in /var/log/samba +depending on how or if you specified logging in your smb.conf file. +

    +If you make changes to your smb.conf file while going through these test, +don't forget to restart smbd and nmbd. +

    The tests

    Procedure27.1.Diagnosing your samba server

    1. +In the directory in which you store your smb.conf file, run the command +testparm smb.conf. If it reports any errors then your smb.conf +configuration file is faulty. +

      Note

      +Your smb.conf file may be located in: /etc/samba +Or in: /usr/local/samba/lib +

    2. +Run the command ping BIGSERVER from the PC and +ping ACLIENT from +the unix box. If you don't get a valid response then your TCP/IP +software is not correctly installed. +

      +Note that you will need to start a "dos prompt" window on the PC to +run ping. +

      +If you get a message saying "host not found" or similar then your DNS +software or /etc/hosts file is not correctly setup. +It is possible to +run samba without DNS entries for the server and client, but I assume +you do have correct entries for the remainder of these tests. +

      +Another reason why ping might fail is if your host is running firewall +software. You will need to relax the rules to let in the workstation +in question, perhaps by allowing access from another subnet (on Linux +this is done via the ipfwadm program.) +

      +Note: Modern Linux distributions install ipchains/iptables by default. +This is a common problem that is often overlooked. +

    3. +Run the command smbclient -L BIGSERVER on the unix box. You +should get a list of available shares back. +

      +If you get a error message containing the string "Bad password" then +you probably have either an incorrect hosts allow, +hosts deny or valid users line in your +smb.conf, or your guest account is not +valid. Check what your guest account is using testparm and +temporarily remove any hosts allow, hosts deny, valid users or invalid users lines. +

      +If you get a "connection refused" response then the smbd server may +not be running. If you installed it in inetd.conf then you probably edited +that file incorrectly. If you installed it as a daemon then check that +it is running, and check that the netbios-ssn port is in a LISTEN +state using netstat -a. +

      Note

      +Some Unix / Linux systems use xinetd in place of +inetd. Check your system documentation for the location +of the control file/s for your particular system implementation of +this network super daemon. +

      +If you get a "session request failed" then the server refused the +connection. If it says "Your server software is being unfriendly" then +its probably because you have invalid command line parameters to smbd, +or a similar fatal problem with the initial startup of smbd. Also +check your config file (smb.conf) for syntax errors with testparm +and that the various directories where samba keeps its log and lock +files exist. +

      +There are a number of reasons for which smbd may refuse or decline +a session request. The most common of these involve one or more of +the following smb.conf file entries: +

      +	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy
+	bind interfaces only = Yes
+

      +In the above, no allowance has been made for any session requests that +will automatically translate to the loopback adaptor address 127.0.0.1. +To solve this problem change these lines to: +

      +	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy 127.
+

      +Do NOT use the bind interfaces only parameter where you +may wish to +use the samba password change facility, or where smbclient may need to +access a local service for name resolution or for local resource +connections. (Note: the bind interfaces only parameter deficiency +where it will not allow connections to the loopback address will be +fixed soon). +

      +Another common cause of these two errors is having something already running +on port 139, such as Samba (ie: smbd is running from inetd already) or +something like Digital's Pathworks. Check your inetd.conf file before trying +to start smbd as a daemon, it can avoid a lot of frustration! +

      +And yet another possible cause for failure of this test is when the subnet mask +and / or broadcast address settings are incorrect. Please check that the +network interface IP Address / Broadcast Address / Subnet Mask settings are +correct and that Samba has correctly noted these in the log.nmb file. +

    4. +Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the +IP address of your Samba server back. +

      +If you don't then nmbd is incorrectly installed. Check your inetd.conf +if you run it from there, or that the daemon is running and listening +to udp port 137. +

      +One common problem is that many inetd implementations can't take many +parameters on the command line. If this is the case then create a +one-line script that contains the right parameters and run that from +inetd. +

    5. run the command nmblookup -B ACLIENT '*'

      +You should get the PCs IP address back. If you don't then the client +software on the PC isn't installed correctly, or isn't started, or you +got the name of the PC wrong. +

      +If ACLIENT doesn't resolve via DNS then use the IP address of the +client in the above test. +

    6. +Run the command nmblookup -d 2 '*' +

      +This time we are trying the same as the previous test but are trying +it via a broadcast to the default broadcast address. A number of +Netbios/TCPIP hosts on the network should respond, although Samba may +not catch all of the responses in the short time it listens. You +should see "got a positive name query response" messages from several +hosts. +

      +If this doesn't give a similar result to the previous test then +nmblookup isn't correctly getting your broadcast address through its +automatic mechanism. In this case you should experiment with the +interfaces option in smb.conf to manually configure your IP +address, broadcast and netmask. +

      +If your PC and server aren't on the same subnet then you will need to +use the -B option to set the broadcast address to that of the PCs +subnet. +

      +This test will probably fail if your subnet mask and broadcast address are +not correct. (Refer to TEST 3 notes above). +

    7. +Run the command smbclient //BIGSERVER/TMP. You should +then be prompted for a password. You should use the password of the account +you are logged into the unix box with. If you want to test with +another account then add the -U accountname option to the end of +the command line. eg: +smbclient //bigserver/tmp -Ujohndoe +

      Note

      +It is possible to specify the password along with the username +as follows: +smbclient //bigserver/tmp -Ujohndoe%secret +

      +Once you enter the password you should get the smb> prompt. If you +don't then look at the error message. If it says "invalid network +name" then the service "tmp" is not correctly setup in your smb.conf. +

      +If it says "bad password" then the likely causes are: +

      1. + you have shadow passords (or some other password system) but didn't + compile in support for them in smbd +

      2. + your valid users configuration is incorrect +

      3. + you have a mixed case password and you haven't enabled the password + level option at a high enough level +

      4. + the path = line in smb.conf is incorrect. Check it with testparm +

      5. + you enabled password encryption but didn't create the SMB encrypted + password file +

      +Once connected you should be able to use the commands +dir get put etc. +Type help command for instructions. You should +especially check that the amount of free disk space shown is correct +when you type dir. +

    8. +On the PC, type the command net view \\BIGSERVER. You will +need to do this from within a "dos prompt" window. You should get back a +list of available shares on the server. +

      +If you get a "network name not found" or similar error then netbios +name resolution is not working. This is usually caused by a problem in +nmbd. To overcome it you could do one of the following (you only need +to choose one of them): +

      1. + fixup the nmbd installation +

      2. + add the IP address of BIGSERVER to the wins server box in the + advanced tcp/ip setup on the PC. +

      3. + enable windows name resolution via DNS in the advanced section of + the tcp/ip setup +

      4. + add BIGSERVER to your lmhosts file on the PC. +

      +If you get a "invalid network name" or "bad password error" then the +same fixes apply as they did for the smbclient -L test above. In +particular, make sure your hosts allow line is correct (see the man +pages) +

      +Also, do not overlook that fact that when the workstation requests the +connection to the samba server it will attempt to connect using the +name with which you logged onto your Windows machine. You need to make +sure that an account exists on your Samba server with that exact same +name and password. +

      +If you get "specified computer is not receiving requests" or similar +it probably means that the host is not contactable via tcp services. +Check to see if the host is running tcp wrappers, and if so add an entry in +the hosts.allow file for your client (or subnet, etc.) +

    9. +Run the command net use x: \\BIGSERVER\TMP. You should +be prompted for a password then you should get a "command completed +successfully" message. If not then your PC software is incorrectly +installed or your smb.conf is incorrect. make sure your hosts allow +and other config lines in smb.conf are correct. +

      +It's also possible that the server can't work out what user name to +connect you as. To see if this is the problem add the line user = +username to the [tmp] section of +smb.conf where username is the +username corresponding to the password you typed. If you find this +fixes things you may need the username mapping option. +

      +It might also be the case that your client only sends encrypted passwords +and you have encrypt passwords = no in smb.conf +Turn it back on to fix. +

    10. +Run the command nmblookup -M testgroup where +testgroup is the name of the workgroup that your Samba server and +Windows PCs belong to. You should get back the IP address of the +master browser for that workgroup. +

      +If you don't then the election process has failed. Wait a minute to +see if it is just being slow then try again. If it still fails after +that then look at the browsing options you have set in smb.conf. Make +sure you have preferred master = yes to ensure that +an election is held at startup. +

    11. +>From file manager try to browse the server. Your samba server should +appear in the browse list of your local workgroup (or the one you +specified in smb.conf). You should be able to double click on the name +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it +is refusing to browse a server that has no encrypted password +capability and is in user level security mode. In this case either set +security = server AND +password server = Windows_NT_Machine in your +smb.conf file, or make sure encrypted passwords is +set to "yes". +

    Still having troubles?

    Read the chapter on +Analysing and Solving Problems. +

    Chapter28.Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    David Bannon

    Samba Team

    <dbannon@samba.org>

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URL's
    Getting help from the mailing lists
    How to get off the mailinglists

    +There are many sources of information available in the form +of mailing lists, RFC's and documentation. The docs that come +with the samba distribution contain very good explanations of +general SMB topics such as browsing.

    Diagnostics tools

    +One of the best diagnostic tools for debugging problems is Samba itself. +You can use the -d option for both smbd and nmbd to specify what +'debug level' at which to run. See the man pages on smbd, nmbd and +smb.conf for more information on debugging options. The debug +level can range from 1 (the default) to 10 (100 for debugging passwords). +

    +Another helpful method of debugging is to compile samba using the +gcc -g flag. This will include debug +information in the binaries and allow you to attach gdb to the +running smbd / nmbd process. In order to attach gdb to an smbd +process for an NT workstation, first get the workstation to make the +connection. Pressing ctrl-alt-delete and going down to the domain box +is sufficient (at least, on the first time you join the domain) to +generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation +maintains an open connection, and therefore there will be an smbd +process running (assuming that you haven't set a really short smbd +idle timeout) So, in between pressing ctrl alt delete, and actually +typing in your password, you can attach gdb and continue. +

    +Some useful samba commands worth investigating: +

    • testparam | more

    • smbclient -L //{netbios name of server}

    +An SMB enabled version of tcpdump is available from +http://www.tcpdup.org/. +Ethereal, another good packet sniffer for Unix and Win32 +hosts, can be downloaded from http://www.ethereal.com. +

    +For tracing things on the Microsoft Windows NT, Network Monitor +(aka. netmon) is available on the Microsoft Developer Network CD's, +the Windows NT Server install CD and the SMS CD's. The version of +netmon that ships with SMS allows for dumping packets between any two +computers (i.e. placing the network interface in promiscuous mode). +The version on the NT Server install CD will only allow monitoring +of network traffic directed to the local NT box and broadcasts on the +local subnet. Be aware that Ethereal can read and write netmon +formatted files. +

    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box

    +Installing netmon on an NT workstation requires a couple +of steps. The following are for installing Netmon V4.00.349, which comes +with Microsoft Windows NT Server 4.0, on Microsoft Windows NT +Workstation 4.0. The process should be similar for other versions of +Windows NT / Netmon. You will need both the Microsoft Windows +NT Server 4.0 Install CD and the Workstation 4.0 Install CD. +

    +Initially you will need to install 'Network Monitor Tools and Agent' +on the NT Server. To do this +

    • Goto Start - Settings - Control Panel - + Network - Services - Add

    • Select the 'Network Monitor Tools and Agent' and + click on 'OK'.

    • Click 'OK' on the Network Control Panel. +

    • Insert the Windows NT Server 4.0 install CD + when prompted.

    +At this point the Netmon files should exist in +%SYSTEMROOT%\System32\netmon\*.*. +Two subdirectories exist as well, parsers\ +which contains the necessary DLL's for parsing the netmon packet +dump, and captures\. +

    +In order to install the Netmon tools on an NT Workstation, you will +first need to install the 'Network Monitor Agent' from the Workstation +install CD. +

    • Goto Start - Settings - Control Panel - + Network - Services - Add

    • Select the 'Network Monitor Agent' and click + on 'OK'.

    • Click 'OK' on the Network Control Panel. +

    • Insert the Windows NT Workstation 4.0 install + CD when prompted.

    +Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* +to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set +permissions as you deem appropriate for your site. You will need +administrative rights on the NT box to run netmon. +

    +To install Netmon on a Windows 9x box install the network monitor agent +from the Windows 9x CD (\admin\nettools\netmon). There is a readme +file located with the netmon driver files on the CD if you need +information on how to do this. Copy the files from a working +Netmon installation. +

    Useful URL's

    Getting help from the mailing lists

    +There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror +and then click on Support and then click on +Samba related mailing lists. +

    +For questions relating to Samba TNG go to +http://www.samba-tng.org/ +It has been requested that you don't post questions about Samba-TNG to the +main stream Samba lists.

    +If you post a message to one of the lists please observe the following guide lines : +

    • Always remember that the developers are volunteers, they are +not paid and they never guarantee to produce a particular feature at +a particular time. Any time lines are 'best guess' and nothing more. +

    • Always mention what version of samba you are using and what +operating system its running under. You should probably list the +relevant sections of your smb.conf file, at least the options +in [global] that affect PDC support.

    • In addition to the version, if you obtained Samba via +CVS mention the date when you last checked it out.

    • Try and make your question clear and brief, lots of long, +convoluted questions get deleted before they are completely read ! +Don't post html encoded messages (if you can select colour or font +size its html).

    • If you run one of those nifty 'I'm on holidays' things when +you are away, make sure its configured to not answer mailing lists. +

    • Don't cross post. Work out which is the best list to post to +and see what happens, i.e. don't post to both samba-ntdom and samba-technical. +Many people active on the lists subscribe to more +than one list and get annoyed to see the same message two or more times. +Often someone will see a message and thinking it would be better dealt +with on another, will forward it on for you.

    • You might include partial +log files written at a debug level set to as much as 20. +Please don't send the entire log but enough to give the context of the +error messages.

    • (Possibly) If you have a complete netmon trace ( from the opening of +the pipe to the error ) you can send the *.CAP file as well.

    • Please think carefully before attaching a document to an email. +Consider pasting the relevant parts into the body of the message. The samba +mailing lists go to a huge number of people, do they all need a copy of your +smb.conf in their attach directory?

    How to get off the mailinglists

    To have your name removed from a samba mailing list, go to the +same place you went to to get on it. Go to http://lists.samba.org, +click on your nearest mirror and then click on Support and +then click on Samba related mailing lists. Or perhaps see +here +

    +Please don't post messages to the list asking to be removed, you will just +be referred to the above address (unless that process failed in some way...) +

    Chapter29.Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using bugzilla.

    +Please take the time to read this file before you submit a bug +report. Also, please see if it has changed between releases, as we +may be changing the bug reporting mechanism at some time. +

    +Please also do as much as you can yourself to help track down the +bug. Samba is maintained by a dedicated group of people who volunteer +their time, skills and efforts. We receive far more mail about it than +we can possibly answer, so you have a much higher chance of an answer +and a fix if you send us a "developer friendly" bug report that lets +us fix it fast. +

    +Do not assume that if you post the bug to the comp.protocols.smb +newsgroup or the mailing list that we will read it. If you suspect that your +problem is not a bug but a configuration problem then it is better to send +it to the Samba mailing list, as there are (at last count) 5000 other users on +that list that may be able to help you. +

    +You may also like to look though the recent mailing list archives, +which are conveniently accessible on the Samba web pages +at http://samba.org/samba/. +

    General info

    +Before submitting a bug report check your config for silly +errors. Look in your log files for obvious messages that tell you that +you've misconfigured something and run testparm to test your config +file for correct syntax. +

    +Have you run through the diagnosis? +This is very important. +

    +If you include part of a log file with your bug report then be sure to +annotate it with exactly what you were doing on the client at the +time, and exactly what the results were. +

    Debug levels

    +If the bug has anything to do with Samba behaving incorrectly as a +server (like refusing to open a file) then the log files will probably +be very useful. Depending on the problem a log level of between 3 and +10 showing the problem may be appropriate. A higher level givesmore +detail, but may use too much disk space. +

    +To set the debug level use log level = in your +smb.conf. You may also find it useful to set the log +level higher for just one machine and keep separate logs for each machine. +To do this use: +

    +log level = 10
+log file = /usr/local/samba/lib/log.%m
+include = /usr/local/samba/lib/smb.conf.%m
+

    +then create a file +/usr/local/samba/lib/smb.conf.machine where +machine is the name of the client you wish to debug. In that file +put any smb.conf commands you want, for example +log level= may be useful. This also allows you to +experiment with different security systems, protocol levels etc on just +one machine. +

    +The smb.conf entry log level = +is synonymous with the entry debuglevel = that has been +used in older versions of Samba and is being retained for backwards +compatibility of smb.conf files. +

    +As the log level = value is increased you will record +a significantly increasing level of debugging information. For most +debugging operations you may not need a setting higher than 3. Nearly +all bugs can be tracked at a setting of 10, but be prepared for a VERY +large volume of log data. +

    Internal errors

    +If you get a "INTERNAL ERROR" message in your log files it means that +Samba got an unexpected signal while running. It is probably a +segmentation fault and almost certainly means a bug in Samba (unless +you have faulty hardware or system software). +

    +If the message came from smbd then it will probably be accompanied by +a message which details the last SMB message received by smbd. This +info is often very useful in tracking down the problem so please +include it in your bug report. +

    +You should also detail how to reproduce the problem, if +possible. Please make this reasonably detailed. +

    +You may also find that a core file appeared in a corefiles +subdirectory of the directory where you keep your samba log +files. This file is the most useful tool for tracking down the bug. To +use it you do this: +

    gdb smbd core

    +adding appropriate paths to smbd and core so gdb can find them. If you +don't have gdb then try dbx. Then within the debugger use the +command where to give a stack trace of where the problem +occurred. Include this in your mail. +

    +If you know any assembly language then do a disass of the routine +where the problem occurred (if its in a library routine then +disassemble the routine that called it) and try to work out exactly +where the problem is by looking at the surrounding code. Even if you +don't know assembly then incuding this info in the bug report can be +useful. +

    Attaching to a running process

    +Unfortunately some unixes (in particular some recent linux kernels) +refuse to dump a core file if the task has changed uid (which smbd +does often). To debug with this sort of system you could try to attach +to the running process using gdb smbd PID where you get PID from +smbstatus. Then use c to continue and try to cause the core dump +using the client. The debugger should catch the fault and tell you +where it occurred. +

    Patches

    +The best sort of bug report is one that includes a fix! If you send us +patches please use diff -u format if your version of +diff supports it, otherwise use diff -c4. Make sure +you do the diff against a clean version of the source and let me know +exactly what version you used. +

    Appendixes

    Table of Contents

    30. How to compile SAMBA
    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon
    31. Migration from NT4 PDC to Samba-3 PDC
    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices
    32. Portability
    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9
    33. Samba and other CIFS clients
    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?
    Are there any other issues when OS/2 (any version) + is used as a client?
    How do I get printer driver download working + for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1
    34. SWAT - The Samba Web Admininistration Tool
    SWAT Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page
    35. Samba performance issues
    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning

    Chapter30.How to compile SAMBA

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    (22 May 2001)

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    +You can obtain the samba source from the samba website. To obtain a development version, +you can download samba from CVS or using rsync. +

    Access Samba source code via CVS

    Introduction

    +Samba is developed in an open environment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can be accessed via anonymous CVS using the instructions -detailed in this chapter.

    This chapter is a modified version of the instructions found at -http://samba.org/samba/cvs.html

    27.1.2. CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS +detailed in this chapter. +

    +This chapter is a modified version of the instructions found at +http://samba.org/samba/cvs.html +

    CVS Access to samba.org

    +The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, including samba, rsync and jitterbug. There are two main ways of -accessing the CVS server on this host.

    27.1.2.1. Access via CVSweb

    You can access the source code via your +accessing the CVS server on this host. +

    Access via CVSweb

    +You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision history and commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository.

    Use the URL : http://samba.org/cgi-bin/cvsweb

    27.1.2.2. Access via cvs

    You can also access the source code via a -normal cvs client. This gives you much more control over you can +listing between any two versions on the repository. +

    +Use the URL : http://samba.org/cgi-bin/cvsweb +

    Access via cvs

    +You can also access the source code via a +normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees and keep them up to date via normal cvs commands. This is the preferred method of access if you are a developer and not -just a casual browser.

    To download the latest cvs source code, point your -browser at the URL : http://www.cyclic.com/. +just a casual browser. +

    +To download the latest cvs source code, point your +browser at the URL : http://www.cyclic.com/. and click on the 'How to get cvs' link. CVS is free software under the GNU GPL (as is Samba). Note that there are several graphical CVS clients which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com.

    To gain access via anonymous cvs use the following steps. +Links to theses clients are also available from http://www.cyclic.com. +

    +To gain access via anonymous cvs use the following steps. For this example it is assumed that you want a copy of the samba source code. For the other source code repositories -on this system just substitute the correct package name

    1. Install a recent copy of cvs. All you really need is a +on this system just substitute the correct package name +

      1. + Install a recent copy of cvs. All you really need is a copy of the cvs client binary. -

      2. Run the command -

        cvs -d :pserver:cvs@samba.org:/cvsroot login -

        When it asks you for a password type cvs. -

      3. Run the command -

        cvs -d :pserver:cvs@samba.org:/cvsroot co samba -

        This will create a directory called samba containing the +

      4. + Run the command +

        + cvs -d :pserver:cvs@samba.org:/cvsroot login +

        + When it asks you for a password type cvs. +

      5. + Run the command +

        + cvs -d :pserver:cvs@samba.org:/cvsroot co samba +

        + This will create a directory called samba containing the latest samba source code (i.e. the HEAD tagged cvs branch). This currently corresponds to the 3.0 development tree. -

        CVS branches other HEAD can be obtained by using the -r +

        + CVS branches other then HEAD can be obtained by using the -r and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the + "Development" page of the samba web site. A common request is to obtain the latest 2.2 release code. This could be done by using the following userinput. -

        cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba -

      6. Whenever you want to merge in the latest code changes use +

        + cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba +

      7. + Whenever you want to merge in the latest code changes use the following command from within the samba directory: -

        cvs update -d -P -

    27.2. Accessing the samba sources via rsync and ftp

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See the rsync homepage for more info on rsync. -

    The disadvantage of the unpacked trees +

    + cvs update -d -P +

    Accessing the samba sources via rsync and ftp

    + pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. + See the rsync homepage for more info on rsync. +

    + The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

    27.3. Verifying Samba's PGP signature

    In these days of insecurity, it's strongly recommended that you verify the PGP signature for any +

    Verifying Samba's PGP signature

    +In these days of insecurity, it's strongly recommended that you verify the PGP signature for any source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of all Samba downloads have had a corresponding PGP signature download (a very low percentage, which should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP -signatures should be a standard reflex.

    With that said, go ahead and download the following files:

         $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
-     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    The first file is the PGP signature for the Samba source file; the other is the Samba public -PGP key itself. Import the public PGP key with:

         $ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with:

         $ gzip -d samba-2.2.8a.tar.gz
-     $ gpg --verify samba-2.2.8a.tar.asc

    If you receive a message like, "Good signature from Samba Distribution Verification Key..." +signatures should be a standard reflex. +

    +With that said, go ahead and download the following files: +

    +     $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
+

    +The first file is the PGP signature for the Samba source file; the other is the Samba public +PGP key itself. Import the public PGP key with: +

    +     $ gpg --import samba-pubkey.asc
+

    +And verify the Samba source code integrity with: +

    +     $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc
+

    +If you receive a message like, "Good signature from Samba Distribution Verification Key..." then all is well. The warnings about trust relationships can be ignored. An example of what -you would not want to see would be:

         gpg: BAD signature from "Samba Distribution Verification Key"

    27.4. Building the Binaries

    To do this, first run the program ./configure - in the source directory. This should automatically +you would not want to see would be: +

    +     gpg: BAD signature from "Samba Distribution Verification Key"
+

    Building the Binaries

    To do this, first run the program ./configure + in the source directory. This should automatically configure Samba for your operating system. If you have unusual - needs then you may wish to run

    root# ./configure --help -

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully - compiled you can use

    root# make install

    to install the binaries and manual pages. You can - separately install the binaries and/or man pages using

    root# make installbin -

    and

    root# make installman -

    Note that if you are upgrading for a previous version + needs then you may wish to run

    root# ./configure --help +

    first to see what special options you can enable. + Then executing

    root# make

    will create the binaries. Once it's successfully + compiled you can use

    root# make install

    to install the binaries and manual pages. You can + separately install the binaries and/or man pages using

    root# make installbin +

    and

    root# make installman +

    Note that if you are upgrading for a previous version of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with

    root# make revert -

    if you find this version a disaster!

    27.4.1. Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed - on your system: -

    the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.
    the OpenLDAP development libraries.

    If your kerberos libraries are in a non-standard location then - remember to add the configure option --with-krb5=DIR.

    After you run configure make sure that include/config.h it generates contains lines like this:

    #define HAVE_KRB5 1
+	the binaries will be renamed with a ".old" extension. You 
+	can go back to the previous version with
    root# make revert
+	
    if you find this version a disaster!
    Compiling samba with Active Directory support
    In order to compile samba with ADS support, you need to have installed
+	on your system:
    • the MIT kerberos development libraries
+	    (either install from the sources or use a package). The
+	    heimdal libraries will not work.
    • the OpenLDAP development libraries.
    If your kerberos libraries are in a non-standard location then
+	  remember to add the configure option --with-krb5=DIR.
    After you run configure make sure that include/config.h it generates contains lines like this:
    +#define HAVE_KRB5 1
 #define HAVE_LDAP 1
-		  
    If it doesn't then configure did not find your krb5 libraries or
+

    If it doesn't then configure did not find your krb5 libraries or your ldap libraries. Look in config.log to figure out why and fix - it.

    27.4.1.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    libkrb5-dev
    krb5-user

    -

    27.4.1.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)

    -

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    27.5. Starting the smbd and nmbd

    You must choose to start smbd and nmbd either - as daemons or from inetdDon't try - to do both! Either you can put them in inetd.conf and have them started on demand - by inetd, or you can start them as - daemons either from the command line or in /etc/rc.local. See the man pages for details + it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    +

    • libkrb5-dev
    • krb5-user

    +

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    +

    • krb5-workstation (for kinit)
    • krb5-libs (for linking with)
    • krb5-devel (because you are compiling from source)

    +

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need + to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either + as daemons or from inetdDon't try + to do both! Either you can put them in + inetd.conf and have them started on demand + by inetd, or you can start them as + daemons either from the command line or in + /etc/rc.local. See the man pages for details on the command line options. Take particular care to read the bit about what user you need to be in order to start - Samba. In many cases you must be root.

    The main advantage of starting smbd - and nmbd using the recommended daemon method + Samba. In many cases you must be root.

    The main advantage of starting smbd + and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection - request.

    27.5.1. Starting from inetd.conf

    NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute services maps.

    Look at your /etc/services. + request.

    Starting from inetd.conf

    NOTE; The following will be different if + you use NIS, NIS+ or LDAP to distribute services maps.

    Look at your /etc/services. What is defined at port 139/tcp. If nothing is defined - then add a line like this:

    netbios-ssn 139/tcp

    similarly for 137/udp you should have an entry like:

    netbios-ns 137/udp

    Next edit your /etc/inetd.conf - and add two lines something like this:

    		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
+		then add a line like this:
    netbios-ssn     139/tcp
    similarly for 137/udp you should have an entry like:
    netbios-ns	137/udp
    Next edit your /etc/inetd.conf 
+		and add two lines something like this:
    +		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
 		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
-		
    The exact syntax of /etc/inetd.conf 
+

    The exact syntax of /etc/inetd.conf varies between unixes. Look at the other entries in inetd.conf - for a guide.

    Some unixes already have entries like netbios_ns - (note the underscore) in /etc/services. - You must either edit /etc/services or - /etc/inetd.conf to make them consistent.

    On many systems you may need to use the - interfaces option in smb.conf to specify the IP address - and netmask of your interfaces. Run ifconfig + for a guide.

    Note

    Some unixes already have entries like netbios_ns + (note the underscore) in /etc/services. + You must either edit /etc/services or + /etc/inetd.conf to make them consistent.

    Note

    On many systems you may need to use the + interfaces option in smb.conf to specify the IP address + and netmask of your interfaces. Run ifconfig as root if you don't know what the broadcast is for your - net. nmbd tries to determine it at run + net. nmbd tries to determine it at run time, but fails on some unixes. -

    Many unixes only accept around 5 - parameters on the command line in inetd.conf. +

    Warning

    Many unixes only accept around 5 + parameters on the command line in inetd.conf. This means you shouldn't use spaces between the options and arguments, or you should use a script, and start the script - from inetd.

    Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd then you may need to kill nmbd as well.

    27.5.2. Alternative: starting it as a daemon

    To start the server as a daemon you should create + from inetd.

    Restart inetd, perhaps just send + it a HUP. If you have installed an earlier version of + nmbd then you may need to kill nmbd as well.

    Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling - it startsmb.

    		#!/bin/sh
+		it startsmb.
    +		#!/bin/sh
 		/usr/local/samba/bin/smbd -D 
 		/usr/local/samba/bin/nmbd -D 
-		
    then make it executable with chmod 
-		+x startsmb
    You can then run startsmb by 
-		hand or execute it from /etc/rc.local
-		
    To kill it send a kill signal to the processes 
-		nmbd and smbd.
    If you use the SVR4 style init system then 
-		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.

    Chapter 28. Migration from NT4 PDC to Samba-3 PDC

    This is a rough guide to assist those wishing to migrate from NT4 domain control to -Samba-3 based domain control.

    28.1. Planning and Getting Started

    In the IT world there is often a saying that all problems are encountered because of +

    then make it executable with chmod + +x startsmb

    You can then run startsmb by + hand or execute it from /etc/rc.local +

    To kill it send a kill signal to the processes + nmbd and smbd.

    Note

    If you use the SVR4 style init system then + you may like to look at the examples/svr4-startup + script to make Samba fit into that system.

    Chapter31.Migration from NT4 PDC to Samba-3 PDC

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    April 3, 2003

    Table of Contents

    Planning and Getting Started
    Objectives
    Steps In Migration Process
    Migration Options
    Planning for Success
    Samba Implementation Choices

    +This is a rough guide to assist those wishing to migrate from NT4 domain control to +Samba-3 based domain control. +

    Planning and Getting Started

    +In the IT world there is often a saying that all problems are encountered because of poor planning. The corrollary to this saying is that not all problems can be anticpated -and planned for. Then again, good planning will anticpate most show stopper type situations.

    Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control +and planned for. Then again, good planning will anticpate most show stopper type situations. +

    +Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control environment would do well to develop a detailed migration plan. So here are a few pointers to -help migration get under way.

    28.1.1. Objectives

    The key objective for most organisations will be to make the migration from MS Windows NT4 +help migration get under way. +

    Objectives

    +The key objective for most organisations will be to make the migration from MS Windows NT4 to Samba-3 domain control as painless as possible. One of the challenges you may experience in your migration process may well be one of convincing management that the new environment should remain in place. Many who have introduced open source technologies have experienced -pressure to return to a Microsoft based platform solution at the first sign of trouble.

    It is strongly advised that before attempting a migration to a Samba-3 controlled network +pressure to return to a Microsoft based platform solution at the first sign of trouble. +

    +It is strongly advised that before attempting a migration to a Samba-3 controlled network that every possible effort be made to gain all-round commitment to the change. Firstly, you -should know precisely why the change is important for the organisation. -Possible motivations to make a change include:

    • Improve network manageability

    • Obtain better user level functionality

    • Reduce network operating costs

    • Reduce exposure caused by Microsoft withdrawal of NT4 support

    • Avoid MS License 6 implications

    • Reduce organisation's dependency on Microsoft

    It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers +should know precisely why the change is important for the organisation. +Possible motivations to make a change include: +

    • Improve network manageability

    • Obtain better user level functionality

    • Reduce network operating costs

    • Reduce exposure caused by Microsoft withdrawal of NT4 support

    • Avoid MS License 6 implications

    • Reduce organisation's dependency on Microsoft

    +It is vital that it be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers an alternative solution that is both different from MS Windows NT4 and that offers some advantages compared with it. It should also be recognised that Samba-3 lacks many of the features that Microsoft has promoted as core values in migration from MS Windows NT4 to -MS Windows 2000 and beyond (with or without Active Directory services).

    What are the features the Samba-3 can NOT provide?

    Active Directory Server
    Group Policy Objects (in Active Direcrtory)
    Machine Policy objects
    Logon Scripts in Active Directorty
    Software Application and Access Controls in Active Directory

    28.1.2. Steps In Migration Process

    This is not a definitive ste-by-step process yet - just a place holder so the info -is not lost. - -1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated - -2. Samba-3 set up as a DC with netlogon share, profile share, etc. - -3. Process: - a. Create a BDC account for the samba server using NT Server Manager - - Samba must NOT be running - - b. rpcclient NT4PDC -U Administrator%passwd - lsaquery - - Note the SID returned by step b. - - c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd - - Note the SID in step c. - - d. net getlocalsid - - Note the SID, now check that all three SIDS reported are the same! - - e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd - - f. net rpc vampire -S NT4PDC -U administrator%passwd - - g. pdbedit -l +MS Windows 2000 and beyond (with or without Active Directory services). +

    +What are the features that Samba-3 can NOT provide? +

    • Active Directory Server

    • Group Policy Objects (in Active Direcrtory)

    • Machine Policy objects

    • Logon Scripts in Active Directorty

    • Software Application and Access Controls in Active Directory

    +The features that Samba-3 DOES provide and that may be of compelling interest to your site +includes: +

    • Lower Cost of Ownership

    • Global availability of support with no strings attached

    • Dynamic SMB Servers (ie:Can run more than one server per Unix/Linux system)

    • Creation of on-the-fly logon scripts

    • Creation of on-the-fly Policy Files

    • Greater Stability, Reliability, Performance and Availability

    • Manageability via an ssh connection

    • Flexible choices of back-end authentication technologies (tdbsam, ldapsam, mysqlsam)

    • Ability to implement a full single-signon architecture

    • Ability to distribute authentication systems for absolute minimum wide area network bandwidth demand

    +Before migrating a network from MS Windows NT4 to Samba-3 it is vital that all necessary factors are +considered. Users should be educated about changes they may experience so that the change will be a +welcome one and not become an obstacle to the work they need to do. The following are some of the +factors that will go into a successful migration: +

    Domain Layout

    +Samba-3 can be configured as a domain controller, a back-up domain controller (probably best called +a secondary controller), a domain member, or as a stand-alone server. The Windows network security +domain context should be sized and scoped before implementation. Particular attention needs to be +paid to the location of the primary domain controller (PDC) as well as backup controllers (BDCs). +It should be noted that one way in which Samba-3 differs from Microsoft technology is that if one +chooses to use an LDAP authentication backend then the same database can be used by several different +domains. This means that in a complex organisation there can be a single LDAP database, that itself +can be distributed, that can simultaneously serve multiple domains (that can also be widely distributed). +

    +It is recommended that from a design perspective, the number of users per server, as well as the number +of servers, per domain should be scaled according to needs and should also consider server capacity +and network bandwidth. +

    +A physical network segment may house several domains, each of which may span multiple network segments. +Where domains span routed network segments it is most advisable to consider and test the performance +implications of the design and layout of a network. A Centrally located domain controller that is being +designed to serve mulitple routed network segments may result in severe performance problems if the +response time (eg: ping timing) between the remote segment and the PDC is more than 100 ms. In situations +where the delay is too long it is highly recommended to locate a backup controller (BDC) to serve as +the local authentication and access control server. +

    Server Share and Directory Layout

    +There are few cardinal rules to effective network design that can be broken with impunity. +The most important rule of effective network management is that simplicity is king in every +well controlled network. Every part of the infrastructure must be managed, the more complex +it is, the greater will be the demand of keeping systems secure and functional. +

    +The nature of the data that must be stored needs to be born in mind when deciding how many +shares must be created. The physical disk space layout should also be taken into account +when designing where share points will be created. Keep in mind that all data needs to be +backed up, thus the simpler the disk layout the easier it will be to keep track of what must +be backed up to tape or other off-line storage medium. Always plan and implement for minimum +maintenance. Leave nothing to chance in your design, above all, do not leave backups to chance: +Backup and test, validate every backup, create a disaster recovery plan and prove that it works. +

    +Users should be grouped according to data access control needs. File and directory access +is best controlled via group permissions and the use of the "sticky bit" on group controlled +directories may substantially avoid file access complaints from samba share users. +

    +Many network administrators who are new to the game will attempt to use elaborate techniques +to set access controls, on files, directories, shares, as well as in share definitions. +There is the ever present danger that that administrator's successor will not understand the +complex mess that has been inherited. Remember, apparent job security through complex design +and implementation may ultimately cause loss of operations and downtime to users as the new +administrator learns to untangle your web. Keep access controls simple and effective and +make sure that users will never be interrupted by the stupidity of complexity. +

    Logon Scripts

    +Please refer to the section of this document on Advanced Network Adminsitration for information +regarding the network logon script options for Samba-3. Logon scripts can help to ensure that +all users gain share and printer connections they need. +

    +Logon scripts can be created on-the-fly so that all commands executed are specific to the +rights and privilidges granted to the user. The preferred controls should be affected through +group membership so that group information can be used to custom create a logong script using +the root preexec parameters to the NETLOGON share. +

    +Some sites prefer to use a tool such as kixstart to establish a controlled +user environment. In any case you may wish to do a google search for logon script process controls. +In particular, you may wish to explore the use of the Microsoft knowledgebase article KB189105 that +deals with how to add printers without user intervention via the logon script process. +

    Profile Migration/Creation

    +User and Group Profiles may be migrated using the tools described in the section titled Desktop Profile +Management. +

    +Profiles may also be managed using the Samba-3 tool profiles. This tool allows +the MS Windows NT style security identifiers (SIDs) that are stored inside the profile NTuser.DAT file +to be changed to the SID of the Samba-3 domain. +

    User and Group Accounts

    +It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before +attempting to migrate user and group accounts it is STRONGLY advised to create in Samba-3 the +groups that are present on the MS Windows NT4 domain AND to connect these to +suitable Unix/Linux groups. Following this simple advice will mean that all user and group attributes +should migrate painlessly. +

    Steps In Migration Process

    +The approximate migration process is described below. +

    • +You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated +

    • +Samba-3 set up as a DC with netlogon share, profile share, etc. +

    Procedure31.1.The Account Migration Process

    1. Create a BDC account for the samba server using NT Server Manager

      1. Samba must NOT be running

    2. rpcclient NT4PDC -U Administrator%passwd

      1. lsaquery

      2. Note the SID returned

    3. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd

      1. Note the SID

    4. net getlocalsid

      1. Note the SID, now check that all three SIDS reported are the same!

    5. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd

    6. net rpc vampire -S NT4PDC -U administrator%passwd

    7. pdbedit -l

      1. Note - did the users migrate?

    8. initGrps.sh DOMNAME

    9. net groupmap list

      1. Now check that all groups are recognised

    10. net rpc campire -S NT4PDC -U administrator%passwd

    11. pdbedit -lv

      1. Note - check that all group membership has been migrated

    +Now it is time to migrate all the profiles, then migrate all policy files. +More later. +

    Migration Options

    +Based on feedback from many sites as well as from actual installation and maintenance +experience sites that wish to migrate from MS Windows NT4 Domain Control to a Samba +based solution fit into three basic categories. +

    Table31.1.The 3 Major Site Types

    Number of UsersDescription
    < 50

    Want simple conversion with NO pain

    50 - 250

    Want new features, can manage some in-house complexity

    > 250

    Solution/Implementation MUST scale well, complex needs. Cross departmental decision process. Local expertise in most areas

    Planning for Success

    +There are three basic choices for sites that intend to migrate from MS Windwows NT4 +to Samba-3. +

    • + Simple Conversion (total replacement) +

    • + Upgraded Conversion (could be one of integration) +

    • + Complete Redesign (completely new solution) +

    +No matter what choice you make, the following rules will minimise down-stream problems: +

    • + Take sufficient time +

    • + Avoid Panic +

    • + Test ALL assumptions +

    • + Test full roll-out program, including workstation deployment +

    Table31.2.Nature of the Conversion Choices

    SimpleUpgradedRedesign

    Make use of minimal OS specific features

    Translate NT4 features to new host OS features

    Decide:

    Suck all accounts from NT4 into Samba-3

    Copy and improve:

    Authentication Regime (database location and access)

    Make least number of operational changes

    Make progressive improvements

    Desktop Management Methods

    Take least amount of time to migrate

    Minimise user impact

    Better Control of Desktops / Users

    Live versus Isolated Conversion

    Maximise functionality

    Identify Needs for: Manageability, Scalability, Security, Availability

    Integrate Samba-3 then migrate while users are active, then Change of control (ie: swap out)

    Take advantage of lower maintenance opportunity

    Samba Implementation Choices

    +Authentication database back end
+	Winbind (external Samba or NT4/200x server)
+	Can use pam_mkhomedir.so to auto-create home dirs
+	External server could use Active Directory or NT4 Domain
 
-		Note - did the users migrate?
+Database type
+	smbpasswd, tdbsam, ldapsam, MySQLsam
 
-	h. initGrps.sh DOMNAME
+Access Control Points
+	On the Share itself (Use NT4 Server Manager)
+	On the file system
+	Unix permissions on files and directories
+	Posix ACLs enablement in file system?
+	Through Samba share parameters
+		Not recommended - except as only resort
 
-	i. smbgroupedit -v
+Policies (migrate or create new ones)
+	Group Policy Editor (NT4)
+	Watch out for Tattoo effect
 
-		Now check that all groups are recognised
+User and Group Profiles
+	Platform specific so use platform tool to change from a Local
+	to a Roaming profile Can use new profiles tool to change SIDs
+	(NTUser.DAT)
 
-	j. net rpc campire -S NT4PDC -U administrator%passwd
+Logon Scripts (Know how they work)
 
-	k. pdbedit -lv
+User and Group mapping to Unix/Linux
+	username map facility may be needed
+	Use 'net groupmap' to connect NT4 groups to Unix groups
+	Use pdbedit to set/change user configuration
+NOTE:
+If migrating to LDAP back end it may be easier to dump initial LDAP database
+to LDIF, then edit, then reload into LDAP
 
-		Note - check that all group membership has been migrated.
+	OS specific scripts / programs may be needed
+		Add / delete Users
+			Note OS limits on size of name (Linux 8 chars)
+				NT4 up to 254 chars
+		Add / delete machines
+			Applied only to domain members (note up to 16 chars)
+		Add / delete Groups
+			Note OS limits on size and nature
+				Linux limit is 16 char,
+				no spaces and no upper case chars (groupadd)
 
+Migration Tools
+	Domain Control (NT4 Style)
+	Profiles, Policies, Access Controls, Security
 
-Now it is time to migrate all the profiles, then migrate all policy files.
+Migration Tools
+	Samba: net, rpcclient, smbpasswd, pdbedit, profiles
+	Windows: NT4 Domain User Manager, Server Manager (NEXUS)
 
-Moe later.

    Chapter 29. Portability

    Samba works on a wide range of platforms but the interface all the +Authentication + New SAM back end (smbpasswd, tdbsam, ldapsam, mysqlsam) +

    +

    Chapter32.Portability

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Table of Contents

    HPUX
    SCO Unix
    DNIX
    RedHat Linux Rembrandt-II
    AIX
    Sequential Read Ahead
    Solaris
    Locking improvements
    Winbind on Solaris 9

    Samba works on a wide range of platforms but the interface all the platforms provide is not always compatible. This chapter contains -platform-specific information about compiling and using samba.

    29.1. HPUX

    HP's implementation of supplementary groups is, er, non-standard (for +platform-specific information about compiling and using samba.

    HPUX

    +HP's implementation of supplementary groups is, er, non-standard (for hysterical reasons). There are two group files, /etc/group and /etc/logingroup; the system maps UIDs to numbers using the former, but initgroups() reads the latter. Most system admins who know the ropes @@ -19684,66 +8908,39 @@ too stupid to go into here). initgroups() will complain if one of the groups you're in in /etc/logingroup has what it considers to be an invalid ID, which means outside the range [0..UID_MAX], where UID_MAX is (I think) 60000 currently on HP-UX. This precludes -2 and 65534, the usual 'nobody' -GIDs.

    If you encounter this problem, make sure that the programs that are failing +GIDs. +

    +If you encounter this problem, make sure that the programs that are failing to initgroups() be run as users not in any groups with GIDs outside the -allowed range.

    This is documented in the HP manual pages under setgroups(2) and passwd(4).

    On HPUX you must use gcc or the HP Ansi compiler. The free compiler +allowed range. +

    This is documented in the HP manual pages under setgroups(2) and passwd(4). +

    +On HPUX you must use gcc or the HP Ansi compiler. The free compiler that comes with HP-UX is not Ansi compliant and cannot compile -Samba.

    29.2. SCO Unix

    +Samba. +

    SCO Unix

    If you run an old version of SCO Unix then you may need to get important TCP/IP patches for Samba to work correctly. Without the patch, you may -encounter corrupt data transfers using samba.

    The patch you need is UOD385 Connection Drivers SLS. It is available from -SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z).

    29.3. DNIX

    DNIX has a problem with seteuid() and setegid(). These routines are +encounter corrupt data transfers using samba. +

    +The patch you need is UOD385 Connection Drivers SLS. It is available from +SCO (ftp.sco.com, directory SLS, files uod385a.Z and uod385a.ltr.Z). +

    DNIX

    +DNIX has a problem with seteuid() and setegid(). These routines are needed for Samba to work correctly, but they were left out of the DNIX -C library for some reason.

    For this reason Samba by default defines the macro NO_EID in the DNIX +C library for some reason. +

    +For this reason Samba by default defines the macro NO_EID in the DNIX section of includes.h. This works around the problem in a limited way, -but it is far from ideal, some things still won't work right.

    +but it is far from ideal, some things still won't work right. +

    To fix the problem properly you need to assemble the following two functions and then either add them to your C library or link them into -Samba.

    -put this in the file setegid.s:

            .globl  _setegid
+Samba.
+
     
+put this in the file setegid.s:
+
    +        .globl  _setegid
 _setegid:
         moveq   #47,d0
         movl    #100,a0
@@ -19754,17 +8951,11 @@ _setegid:
         jmp     cerror
 1$:
         clrl    d0
-        rts
    put this in the file seteuid.s:
            .globl  _seteuid
+        rts
+
    
+put this in the file seteuid.s:
+
    +        .globl  _seteuid
 _seteuid:
         moveq   #47,d0
         movl    #100,a0
@@ -19775,2445 +8966,550 @@ _seteuid:
         jmp     cerror
 1$:
         clrl    d0
-        rts
    after creating the above files you then assemble them using
    as seteuid.s
    as setegid.s
    that should produce the files seteuid.o and 
-setegid.o
    then you need to add these to the LIBSM line in the DNIX section of
-the Samba Makefile. Your LIBSM line will then look something like this:
    LIBSM = setegid.o seteuid.o -ln
     
-You should then remove the line:
    #define NO_EID
    from the DNIX section of includes.h

    29.4. RedHat Linux Rembrandt-II

    By default RedHat Rembrandt-II during installation adds an + rts +

    +after creating the above files you then assemble them using +

    as seteuid.s

    as setegid.s

    +that should produce the files seteuid.o and +setegid.o +

    +then you need to add these to the LIBSM line in the DNIX section of +the Samba Makefile. Your LIBSM line will then look something like this: +

    +LIBSM = setegid.o seteuid.o -ln
+

    +You should then remove the line: +

    +#define NO_EID
+

    from the DNIX section of includes.h

    RedHat Linux Rembrandt-II

    +By default RedHat Rembrandt-II during installation adds an entry to /etc/hosts as follows: -

    	127.0.0.1 loopback "hostname"."domainname"

    This causes Samba to loop back onto the loopback interface. +

    +	127.0.0.1 loopback "hostname"."domainname"
+

    +

    +This causes Samba to loop back onto the loopback interface. The result is that Samba fails to communicate correctly with the world and therefor may fail to correctly negotiate who -is the master browse list holder and who is the master browser.

    Corrective Action: Delete the entry after the word loopback - in the line starting 127.0.0.1

    29.5. AIX

    29.5.1. Sequential Read Ahead

    Disabling Sequential Read Ahead using vmtune -r 0 improves -samba performance significally.

    29.6. Solaris

    Some people have been experiencing problems with F_SETLKW64/fcntl +is the master browse list holder and who is the master browser. +

    +Corrective Action: Delete the entry after the word loopback + in the line starting 127.0.0.1 +

    AIX

    Sequential Read Ahead

    +Disabling Sequential Read Ahead using vmtune -r 0 improves +samba performance significally. +

    Solaris

    Locking improvements

    Some people have been experiencing problems with F_SETLKW64/fcntl when running samba on solaris. The built in file locking mechanism was not scalable. Performance would degrade to the point where processes would get into loops of trying to lock a file. It woul try a lock, then fail, then try again. The lock attempt was failing before the grant was occurring. So the visible manifestation of this would be a handful of processes stealing all of the CPU, and when they were trussed they would -be stuck if F_SETLKW64 loops.

    Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 -has not been released yet.

    The patch revision for 2.6 is 105181-34 +be stuck if F_SETLKW64 loops. +

    +Sun released patches for Solaris 2.6, 8, and 9. The patch for Solaris 7 +has not been released yet. +

    +The patch revision for 2.6 is 105181-34 for 8 is 108528-19 -and for 9 is 112233-04

    After the install of these patches it is recommended to reconfigure -and rebuild samba.

    Thanks to Joe Meslovich for reporting

    Chapter 30. Samba and other CIFS clients

    This chapter contains client-specific information.

    30.1. Macintosh clients?

    Yes. Thursby now have a CIFS Client / Server called DAVE - see

    They test it against Windows 95, Windows NT and samba for +and for 9 is 112233-04 +

    +After the install of these patches it is recommended to reconfigure +and rebuild samba. +

    Thanks to Joe Meslovich for reporting

    Winbind on Solaris 9

    +Nsswitch on Solaris 9 refuses to use the winbind nss module. This behavior +is fixed by Sun in patch 113476-05 which as of March 2003 is not in any +roll-up packages. +

    Chapter33.Samba and other CIFS clients

    Jim McDonough

    IBM

    <jmcd@us.ibm.com>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    5 Mar 2001

    Table of Contents

    Macintosh clients?
    OS2 Client
    How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?
    How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?
    Are there any other issues when OS/2 (any version) + is used as a client?
    How do I get printer driver download working + for OS/2 clients?
    Windows for Workgroups
    Use latest TCP/IP stack from Microsoft
    Delete .pwl files after password change
    Configure WfW password handling
    Case handling of passwords
    Use TCP/IP as default protocol
    Speed improvement
    Windows '95/'98
    Speed improvement
    Windows 2000 Service Pack 2
    Windows NT 3.1

    This chapter contains client-specific information.

    Macintosh clients?

    +Yes. Thursby now have a CIFS Client / Server called DAVE +

    +They test it against Windows 95, Windows NT and samba for compatibility issues. At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available as a free download from the Thursby web site (the speed of finder copies has been greatly -enhanced, and there are bug-fixes included).

    +enhanced, and there are bug-fixes included). +

    Alternatives - There are two free implementations of AppleTalk for several kinds of UNIX machnes, and several more commercial ones. These products allow you to run file services and print services natively to Macintosh users, with no additional support required on the Macintosh. The two free omplementations are -Netatalk, and -CAP. +Netatalk, and +CAP. What Samba offers MS Windows users, these packages offer to Macs. For more info on these packages, Samba, and Linux (and other UNIX-based systems) see -http://www.eats.com/linux_mac_win.html

    30.2. OS2 Client

    30.2.1. How can I configure OS/2 Warp Connect or - OS/2 Warp 4 as a client for Samba?

    A more complete answer to this question can be - found on http://carol.wins.uva.nl/~leeuw/samba/warp.html.

    Basically, you need three components:

    • The File and Print Client ('IBM Peer') -

    • TCP/IP ('Internet support') -

    • The "NetBIOS over TCP/IP" driver ('TCPBEUI') -

    Installing the first two together with the base operating +http://www.eats.com/linux_mac_win.html +

    OS2 Client

    How can I configure OS/2 Warp Connect or + OS/2 Warp 4 as a client for Samba?

    A more complete answer to this question can be + found on + http://carol.wins.uva.nl/~leeuw/samba/warp.html.

    Basically, you need three components:

    • The File and Print Client ('IBM Peer') +

    • TCP/IP ('Internet support') +

    • The "NetBIOS over TCP/IP" driver ('TCPBEUI') +

    Installing the first two together with the base operating system on a blank system is explained in the Warp manual. If Warp has already been installed, but you now want to install the - networking support, use the "Selective Install for Networking" - object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described + networking support, use the "Selective Install for Networking" + object in the "System Setup" folder.

    Adding the "NetBIOS over TCP/IP" driver is not described in the manual and just barely in the online documentation. Start - MPTS.EXE, click on OK, click on "Configure LAPS" and click - on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line + MPTS.EXE, click on OK, click on "Configure LAPS" and click + on "IBM OS/2 NETBIOS OVER TCP/IP" in 'Protocols'. This line is then moved to 'Current Configuration'. Select that line, - click on "Change number" and increase it from 0 to 1. Save this - configuration.

    If the Samba server(s) is not on your local subnet, you + click on "Change number" and increase it from 0 to 1. Save this + configuration.

    If the Samba server(s) is not on your local subnet, you can optionally add IP names and addresses of these servers - to the "Names List", or specify a WINS server ('NetBIOS + to the "Names List", or specify a WINS server ('NetBIOS Nameserver' in IBM and RFC terminology). For Warp Connect you may need to download an update for 'IBM Peer' to bring it on - the same level as Warp 4. See the webpage mentioned above.

    30.2.2. How can I configure OS/2 Warp 3 (not Connect), - OS/2 1.2, 1.3 or 2.x for Samba?

    You can use the free Microsoft LAN Manager 2.2c Client + the same level as Warp 4. See the webpage mentioned above.

    How can I configure OS/2 Warp 3 (not Connect), + OS/2 1.2, 1.3 or 2.x for Samba?

    You can use the free Microsoft LAN Manager 2.2c Client for OS/2 from - ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. - See http://carol.wins.uva.nl/~leeuw/lanman.html for + + ftp://ftp.microsoft.com/BusSys/Clients/LANMAN.OS2/. + See + http://carol.wins.uva.nl/~leeuw/lanman.html for more information on how to install and use this client. In a nutshell, edit the file \OS2VER in the root directory of - the OS/2 boot partition and add the lines:

    		20=setup.exe
+		the OS/2 boot partition and add the lines:
    +		20=setup.exe
 		20=netwksta.sys
 		20=netvdd.sys
-		
    before you install the client. Also, don't use the 
+

    before you install the client. Also, don't use the included NE2000 driver because it is buggy. Try the NE2000 or NS2000 driver from - ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead. -

    30.2.3. Are there any other issues when OS/2 (any version) - is used as a client?

    When you do a NET VIEW or use the "File and Print - Client Resource Browser", no Samba servers show up. This can - be fixed by a patch from http://carol.wins.uva.nl/~leeuw/samba/fix.html. + + ftp://ftp.cdrom.com/pub/os2/network/ndis/ instead. +

    Are there any other issues when OS/2 (any version) + is used as a client?

    When you do a NET VIEW or use the "File and Print + Client Resource Browser", no Samba servers show up. This can + be fixed by a patch from + http://carol.wins.uva.nl/~leeuw/samba/fix.html. The patch will be included in a later version of Samba. It also fixes a couple of other problems, such as preserving long filenames when objects are dragged from the Workplace Shell - to the Samba server.

    30.2.4. How do I get printer driver download working - for OS/2 clients?

    First, create a share called [PRINTDRV] that is + to the Samba server.

    How do I get printer driver download working + for OS/2 clients?

    First, create a share called [PRINTDRV] that is world-readable. Copy your OS/2 driver files there. Note that the .EA_ files must still be separate, so you will need to use the original install files, and not copy an installed - driver from an OS/2 system.

    Install the NT driver first for that printer. Then, + driver from an OS/2 system.

    Install the NT driver first for that printer. Then, add to your smb.conf a parameter, os2 driver map = - filename". Then, in the file - specified by filename, map the + filename". Then, in the file + specified by filename, map the name of the NT driver name to the OS/2 driver name as - follows:

    nt driver name = os2 "driver - name"."device name", e.g.: - HP LaserJet 5L = LASERJET.HP LaserJet 5L

    You can have multiple drivers mapped in this file.

    If you only specify the OS/2 driver name, and not the + follows:

    nt driver name = os2 "driver + name"."device name", e.g.: + HP LaserJet 5L = LASERJET.HP LaserJet 5L

    You can have multiple drivers mapped in this file.

    If you only specify the OS/2 driver name, and not the device name, the first attempt to download the driver will actually download the files, but the OS/2 client will tell you the driver is not available. On the second attempt, it will work. This is fixed simply by adding the device name to the mapping, after which it will work on the first attempt. -

    30.3. Windows for Workgroups

    30.3.1. Use latest TCP/IP stack from Microsoft

    Use the latest TCP/IP stack from microsoft if you use Windows -for workgroups.

    The early TCP/IP stacks had lots of bugs.

    +

    Windows for Workgroups

    Use latest TCP/IP stack from Microsoft

    Use the latest TCP/IP stack from microsoft if you use Windows +for workgroups. +

    The early TCP/IP stacks had lots of bugs.

    Microsoft has released an incremental upgrade to their TCP/IP 32-Bit VxD drivers. The latest release can be found on their ftp site at ftp.microsoft.com, located in /peropsys/windows/public/tcpip/wfwt32.exe. There is an update.txt file there that describes the problems that were fixed. New files include WINSOCK.DLL, TELNET.EXE, WSOCK.386, VNBT.386, -WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE.

    30.3.2. Delete .pwl files after password change

    WfWg does a lousy job with passwords. I find that if I change my +WSTCP.386, TRACERT.EXE, NETSTAT.EXE, and NBTSTAT.EXE. +

    Delete .pwl files after password change

    +WfWg does a lousy job with passwords. I find that if I change my password on either the unix box or the PC the safest thing to do is to -delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password.

    +delete the .pwl files in the windows directory. The PC will complain about not finding the files, but will soon get over it, allowing you to enter the new password. +

    If you don't do this you may find that WfWg remembers and uses the old -password, even if you told it a new one.

    -Often WfWg will totally ignore a password you give it in a dialog box.

    30.3.3. Configure WfW password handling

    There is a program call admincfg.exe +password, even if you told it a new one. +

    +Often WfWg will totally ignore a password you give it in a dialog box. +

    Configure WfW password handling

    +There is a program call admincfg.exe on the last disk (disk 8) of the WFW 3.11 disk set. To install it type EXPAND A:\ADMINCFG.EX_ C:\WINDOWS\ADMINCFG.EXE Then add an icon -for it via the "Progam Manager" "New" Menu. This program allows you +for it via the "Progam Manager" "New" Menu. This program allows you to control how WFW handles passwords. ie disable Password Caching etc -for use with security = user

    30.3.4. Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf(5) information on password level to specify what characters samba should try to uppercase when checking.

    30.3.5. Use TCP/IP as default protocol

    To support print queue reporting you may find +for use with security = user +

    Case handling of passwords

    Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the smb.conf(5) information on password level to specify what characters samba should try to uppercase when checking.

    Use TCP/IP as default protocol

    To support print queue reporting you may find that you have to use TCP/IP as the default protocol under WfWg. For some reason if you leave Netbeui as the default it may break the print queue reporting on some systems. -It is presumably a WfWg bug.

    30.4. Windows '95/'98

    When using Windows 95 OEM SR2 the following updates are recommended where Samba +It is presumably a WfWg bug.

    Speed improvement

    +Note that some people have found that setting DefaultRcvWindow in +the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a +big improvement. I don't know why. +

    +My own experience wth DefaultRcvWindow is that I get much better +performance with a large value (16384 or larger). Other people have +reported that anything over 3072 slows things down enourmously. One +person even reported a speed drop of a factor of 30 when he went from +3072 to 8192. I don't know why. +

    Windows '95/'98

    +When using Windows 95 OEM SR2 the following updates are recommended where Samba is being used. Please NOTE that the above change will affect you once these -updates have been installed.

    +updates have been installed. +

    There are more updates than the ones mentioned here. You are referred to the Microsoft Web site for all currently available updates to your specific version -of Windows 95.

    1. Kernel Update: KRNLUPD.EXE

    2. Ping Fix: PINGUPD.EXE

    3. RPC Update: RPCRTUPD.EXE

    4. TCP/IP Update: VIPUPD.EXE

    5. Redirector Update: VRDRUPD.EXE

    Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This +of Windows 95. +

    1. Kernel Update: KRNLUPD.EXE

    2. Ping Fix: PINGUPD.EXE

    3. RPC Update: RPCRTUPD.EXE

    4. TCP/IP Update: VIPUPD.EXE

    5. Redirector Update: VRDRUPD.EXE

    +Also, if using MS OutLook it is desirable to install the OLEUPD.EXE fix. This fix may stop your machine from hanging for an extended period when exiting OutLook and you may also notice a significant speedup when accessing network -neighborhood services.

    30.5. Windows 2000 Service Pack 2

    +neighborhood services. +

    Speed improvement

    +Configure the win95 TCPIP registry settings to give better +performance. I use a program called MTUSPEED.exe which I got off the +net. There are various other utilities of this type freely available. +

    Windows 2000 Service Pack 2

    There are several annoyances with Windows 2000 SP2. One of which only appears when using a Samba server to host user profiles to Windows 2000 SP2 clients in a Windows domain. This assumes that Samba is a member of the domain, but the problem will -likely occur if it is not.

    +likely occur if it is not. +

    In order to server profiles successfully to Windows 2000 SP2 clients (when not operating as a PDC), Samba must have -nt acl support = no +nt acl support = no added to the file share which houses the roaming profiles. If this is not done, then the Windows 2000 SP2 client will complain about not being able to access the profile (Access Denied) and create multiple copies of it on disk (DOMAIN.user.001, DOMAIN.user.002, etc...). See the -smb.conf(5) man page +smb.conf(5) man page for more details on this option. Also note that the -nt acl support parameter was formally a global parameter in -releases prior to Samba 2.2.2.

    -The following is a minimal profile share:

    	[profile]
+nt acl support parameter was formally a global parameter in
+releases prior to Samba 2.2.2.
+
     
+The following is a minimal profile share:
+
    +	[profile]
 		path = /export/profile
 		create mask = 0600
 		directory mask = 0700
 		nt acl support = no
-		read only = no
    The reason for this bug is that the Win2k SP2 client copies
+		read only = no
+

    +The reason for this bug is that the Win2k SP2 client copies the security descriptor for the profile which contains the Samba server's SID, and not the domain SID. The client compares the SID for SAMBA\user and realizes it is different that the one assigned to DOMAIN\user. Hence the reason -for the "access denied" message.

    By disabling the nt acl support parameter, Samba will send +for the "access denied" message. +

    +By disabling the nt acl support parameter, Samba will send the Win2k client a response to the QuerySecurityDescriptor trans2 call which causes the client to set a default ACL -for the profile. This default ACL includes

    DOMAIN\user "Full Control"

    This bug does not occur when using winbind to -create accounts on the Samba host for Domain users.

    30.6. Windows NT 3.1

    If you have problems communicating across routers with Windows -NT 3.1 workstations, read this Microsoft Knowledge Base article.

    Chapter 31. SWAT - The Samba Web Admininistration Tool

    This is a rough guide to SWAT.

    31.1. SWAT Features and Benefits

    You must use at least the following ...

    31.1.2. Global Settings

    Document steps right here!

    31.1.3. The SWAT Wizard

    Lots of blah blah here.

    31.1.4. Share Settings

    Document steps right here!

    31.1.5. Printing Settings

    Document steps right here!

    31.1.6. The Status Page

    Document steps right here!

    31.1.7. The Password Change Page

    Document steps right here!

    Chapter 32. Samba performance issues

    32.1. Comparisons

    The Samba server uses TCP to talk to the client. Thus if you are +for the profile. This default ACL includes +

    DOMAIN\user "Full Control"

    Note

    This bug does not occur when using winbind to +create accounts on the Samba host for Domain users.

    Windows NT 3.1

    If you have problems communicating across routers with Windows +NT 3.1 workstations, read this Microsoft Knowledge Base article. + +

    Chapter34.SWAT - The Samba Web Admininistration Tool

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    April 21, 2003

    Table of Contents

    SWAT Features and Benefits
    Enabling SWAT for use
    Securing SWAT through SSL
    The SWAT Home Page
    Global Settings
    Share Settings
    Printers Settings
    The SWAT Wizard
    The Status Page
    The View Page
    The Password Change Page

    +There are many and varied opinions regarding the usefulness or otherwise of SWAT. +No matter how hard one tries to produce the perfect configuration tool it remains +an object of personal taste. SWAT is a tool that will allow web based configuration +of samba. It has a wizard that may help to get samba configured quickly, it has context +sensitive help on each smb.conf parameter, it provides for monitoring of current state +of connection information, and it allows network wide MS Windows network password +management. +

    SWAT Features and Benefits

    +There are network administrators who believe that it is a good idea to write systems +documentation inside configuration files, for them SWAT will aways be a nasty tool. SWAT +does not store the configuration file in any intermediate form, rather, it stores only the +parameter settings, so when SWAT writes the smb.conf file to disk it will write only +those parameters that are at other than the default settings. The result is that all comments +will be lost from the smb.conf file. Additionally, the parameters will be written back in +internal ordering. +

    Note

    +So before using SWAT please be warned - SWAT will completely replace your smb.conf with +a fully optimised file that has been stripped of all comments you might have placed there +and only non-default settings will be written to the file. +

    Enabling SWAT for use

    +SWAT should be installed to run via the network super daemon. Depending on which system +your Unix/Linux system has you will have either an inetd or +xinetd based system. +

    +The nature and location of the network super-daemon varies with the operating system +implementation. The control file (or files) can be located in the file +/etc/inetd.conf or in the directory /etc/[x]inet.d +or similar. +

    +The control entry for the older style file might be: +

    +	# swat is the Samba Web Administration Tool
+	swat stream tcp nowait.400 root /usr/sbin/swat swat
+

    +A control file for the newer style xinetd could be: +

    +

    +	# default: off
+	# description: SWAT is the Samba Web Admin Tool. Use swat \
+	#              to configure your Samba server. To use SWAT, \
+	#              connect to port 901 with your favorite web browser.
+	service swat
+	{
+		port    = 901
+		socket_type     = stream
+		wait    = no
+		only_from = localhost
+		user    = root
+		server  = /usr/sbin/swat
+		log_on_failure  += USERID
+		disable = yes
+	}
+

    + +

    +Both the above examples assume that the swat binary has been +located in the /usr/sbin directory. In addition to the above +SWAT will use a directory access point from which it will load it's help files +as well as other control information. The default location for this on most Linux +systems is in the directory /usr/share/samba/swat. The default +location using samba defaults will be /usr/local/samba/swat. +

    +Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user +the only permission allowed is to view certain aspects of configuration as well as +access to the password change facility. The buttons that will be exposed to the non-root +user are: HOME, STATUS, VIEW, PASSWORD. The only page that allows +change capability in this case is PASSWORD. +

    +So long as you log onto SWAT as the user root you should obtain +full change and commit ability. The buttons that will be exposed includes: +HOME, GLOBALS, SHARES, PRINTERS, WIZARD, STATUS, VIEW, PASSWORD. +

    Securing SWAT through SSL

    +Lots of people have asked about how to setup SWAT with SSL to allow for secure remote +administration of Samba. Here is a method that works, courtesy of Markus Krieger +

    +Modifications to the swat setup are as following: +

    • + install OpenSSL +

    • + generate certificate and private key + + 

      +	root# /usr/bin/openssl req -new -x509 -days 365 -nodes -config \
+	 	/usr/share/doc/packages/stunnel/stunnel.cnf \
+		-out /etc/stunnel/stunnel.pem -keyout /etc/stunnel/stunnel.pem
+

    • + remove swat-entry from [x]inetd +

    • + start stunnel + + 

      +	root# stunnel -p /etc/stunnel/stunnel.pem -d 901 \
+		 -l /usr/local/samba/bin/swat swat 
+

    +afterwards simply contact to swat by using the URL "https://myhost:901", accept the certificate +and the SSL connection is up. +

    The SWAT Home Page

    +The SWAT title page provides access to the latest Samba documentation. The manual page for +each samba component is accessible from this page as are the Samba-HOWTO-Collection (this +document) as well as the O'Reilly book "Using Samba". +

    +Administrators who wish to validate their samba configuration may obtain useful information +from the man pages for the diganostic utilities. These are available from the SWAT home page +also. One diagnostic tool that is NOT mentioned on this page, but that is particularly +useful is ethereal, available from +http://www.ethereal.com. +

    Note

    +SWAT can be configured to run in demo mode. This is NOT recommended +as it runs SWAT without authentication and with full administrative ability. ie: Allows +changes to smb.conf as well as general operation with root privilidges. The option that +creates this ability is the -a flag to swat. DO NOT USE THIS IN ANY +PRODUCTION ENVIRONMENT - you have been warned! +

    Global Settings

    +The Globals button will expose a page that allows configuration of the global parameters +in smb.conf. There are three levels of exposure of the parameters: +

    • + Basic - exposes common configuration options. +

    • + Advanced - exposes configuration options needed in more + complex environments. +

    • + Developer - exposes configuration options that only the brave + will want to tamper with. +

    +To switch to other than Basic editing ability click on either the +Advanced or the Developer dial, then click the +Commit Changes button. +

    +After making any changes to configuration parameters make sure that you click on the +Commit Changes button before moving to another area otherwise +your changes will be immediately lost. +

    Note

    +SWAT has context sensitive help. To find out what each parameter is for simply click the +Help link to the left of the configurartion parameter. +

    Share Settings

    +To affect a currenly configured share, simply click on the pull down button between the +Choose Share and the Delete Share buttons, +select the share you wish to operate on, then to edit the settings click on the +Choose Share button, to delete the share simply press the +Delete Share button. +

    +To create a new share, next to the button labelled Create Share enter +into the text field the name of the share to be created, then click on the +Create Share button. +

    Printers Settings

    +To affect a currenly configured printer, simply click on the pull down button between the +Choose Printer and the Delete Printer buttons, +select the printer you wish to operate on, then to edit the settings click on the +Choose Printer button, to delete the share simply press the +Delete Printer button. +

    +To create a new printer, next to the button labelled Create Printer enter +into the text field the name of the share to be created, then click on the +Create Printer button. +

    The SWAT Wizard

    +The purpose if the SWAT Wizard is to help the Microsoft knowledgable network administrator +to configure Samba with a minimum of effort. +

    +The Wizard page provides a tool for rewiting the smb.conf file in fully optimised format. +This will also happen if you press the commit button. The two differ in the the rewrite button +ignores any changes that may have been made, while the Commit button causes all changes to be +affected. +

    +The Edit button permits the editing (setting) of the minimal set of +options that may be necessary to create a working samba server. +

    +Finally, there are a limited set of options that will determine what type of server samba +will be configured for, whether it will be a WINS server, participate as a WINS client, or +operate with no WINS support. By clicking on one button you can elect to epose (or not) user +home directories. +

    The Status Page

    +The status page serves a limited purpose. Firstly, it allows control of the samba daemons. +The key daemons that create the samba server environment are: smbd, nmbd, winbindd. +

    +The daemons may be controlled individually or as a total group. Additionally, you may set +an automatic screen refresh timing. As MS Windows clients interact with Samba new smbd processes +will be continually spawned. The auto-refresh facility will allow you to track the changing +conditions with minimal effort. +

    +Lastly, the Status page may be used to terminate specific smbd client connections in order to +free files that may be locked. +

    The View Page

    +This page allows the administrator to view the optimised smb.conf file and if you are +particularly massochistic will permit you also to see all possible global configuration +parameters and their settings. +

    The Password Change Page

    +The Password Change page is a popular tool. This tool allows the creation, deletion, deactivation +and reactivation of MS Windows networking users on the local machine. Alternatively, you can use +this tool to change a local password for a user account. +

    +When logged in as a non-root account the user will have to provide the old password as well as +the new password (twice). When logged in as root only the new password is +required. +

    +One popular use for this tool is to change user passwords across a range of remote MS Windows +servers. +

    Chapter35.Samba performance issues

    Paul Cochrane

    Dundee Limb Fitting Centre

    <paulc@dth.scot.nhs.uk>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Table of Contents

    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning

    Comparisons

    +The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to programs that use the same protocol. The most readily available programs for file transfer that use TCP are ftp or another TCP based -SMB server.

    If you want to test against something like a NT or WfWg server then +SMB server. +

    +If you want to test against something like a NT or WfWg server then you will have to disable all but TCP on either the client or server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid.

    Generally you should find that Samba performs similarly to ftp at raw +(such as Netbeui) and comparisons may not be valid. +

    +Generally you should find that Samba performs similarly to ftp at raw transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system.

    Several people have done comparisons between Samba and Novell, NFS or +although this very much depends on your system. +

    +Several people have done comparisons between Samba and Novell, NFS or WinNT. In some cases Samba performed the best, in others the worst. I suspect the biggest factor is not Samba vs some other system but the hardware and drivers used on the various systems. Given similar hardware Samba should certainly be competitive in speed with other -systems.

    32.2. Socket options

    There are a number of socket options that can greatly affect the -performance of a TCP based server like Samba.

    The socket options that Samba uses are settable both on the command -line with the -O option, or in the smb.conf file.

    The "socket options" section of the smb.conf manual page describes how -to set these and gives recommendations.

    Getting the socket options right can make a big difference to your +systems. +

    Socket options

    +There are a number of socket options that can greatly affect the +performance of a TCP based server like Samba. +

    +The socket options that Samba uses are settable both on the command +line with the -O option, or in the smb.conf file. +

    +The socket options section of the smb.conf manual page describes how +to set these and gives recommendations. +

    +Getting the socket options right can make a big difference to your performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network.

    The socket option TCP_NODELAY is the one that seems to make the +much. The correct settings are very dependent on your local network. +

    +The socket option TCP_NODELAY is the one that seems to make the biggest single difference for most networks. Many people report that -adding "socket options = TCP_NODELAY" doubles the read performance of -a Samba drive. The best explanation I have seen for this is that the -Microsoft TCP/IP stack is slow in sending tcp ACKs.

    32.3. Read size

    The option "read size" affects the overlap of disk reads/writes with -network reads/writes. If the amount of data being transferred in -several of the SMB commands (currently SMBwrite, SMBwriteX and +adding socket options = TCP_NODELAY doubles the read +performance of a Samba drive. The best explanation I have seen for this is +that the Microsoft TCP/IP stack is slow in sending tcp ACKs. +

    Read size

    +The option read size affects the overlap of disk +reads/writes with network reads/writes. If the amount of data being +transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing the data before it has received the whole packet from the network, or in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk.

    This overlapping works best when the speeds of disk and network access +all the data has been read from disk. +

    +This overlapping works best when the speeds of disk and network access are similar, having very little effect when the speed of one is much -greater than the other.

    The default value is 16384, but very little experimentation has been +greater than the other. +

    +The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily.

    32.4. Max xmit

    At startup the client and server negotiate a "maximum transmit" size, +pointless and will cause you to allocate memory unnecessarily. +

    Max xmit

    +At startup the client and server negotiate a maximum transmit size, which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the "max xmit = " option -in smb.conf. Note that this is the maximum size of SMB request that +maximum size that Samba will negotiate using the max xmit = option +in smb.conf. Note that this is the maximum size of SMB requests that Samba will accept, but not the maximum size that the *client* will accept. The client maximum receive size is sent to Samba by the client and Samba -honours this limit.

    It defaults to 65536 bytes (the maximum), but it is possible that some +honours this limit. +

    +It defaults to 65536 bytes (the maximum), but it is possible that some clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems.

    In most cases the default is the best option.

    32.5. Log level

    If you set the log level (also known as "debug level") higher than 2 +of less than 2048 is likely to cause severe problems. +

    +In most cases the default is the best option. +

    Log level

    +If you set the log level (also known as debug level) higher than 2 then you may suffer a large drop in performance. This is because the server flushes the log file after each operation, which can be very -expensive.

    32.6. Read raw

    The "read raw" operation is designed to be an optimised, low-latency +expensive. +

    Read raw

    +The read raw operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, -however. and Samba makes support for "read raw" optional, with it -being enabled by default.

    In some cases clients don't handle "read raw" very well and actually +however. and Samba makes support for read raw optional, with it +being enabled by default. +

    +In some cases clients don't handle read raw very well and actually get lower performance using it than they get using the conventional -read operations.

    So you might like to try "read raw = no" and see what happens on your +read operations. +

    +So you might like to try read raw = no and see what happens on your network. It might lower, raise or not affect your performance. Only -testing can really tell.

    32.7. Write raw

    The "write raw" operation is designed to be an optimised, low-latency +testing can really tell. +

    Write raw

    +The write raw operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, -however. and Samba makes support for "write raw" optional, with it -being enabled by default.

    Some machines may find "write raw" slower than normal write, in which -case you may wish to change this option.

    32.8. Slow Clients

    One person has reported that setting the protocol to COREPLUS rather -than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    I suspect that his PC's (386sx16 based) were asking for more data than -they could chew. I suspect a similar speed could be had by setting -"read raw = no" and "max xmit = 2048", instead of changing the -protocol. Lowering the "read size" might also help.

    32.9. Slow Logins

    Slow logins are almost always due to the password checking time. Using -the lowest practical "password level" will improve things a lot. You -could also enable the "UFC crypt" option in the Makefile.

    32.10. Client tuning

    Often a speed problem can be traced to the client. The client (for +however. and Samba makes support for write raw optional, with it +being enabled by default. +

    +Some machines may find write raw slower than normal write, in which +case you may wish to change this option. +

    Slow Logins

    +Slow logins are almost always due to the password checking time. Using +the lowest practical password level will improve things. +

    Client tuning

    +Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP -performance.

    See your client docs for details. In particular, I have heard rumours -that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a -large impact on performance.

    Also note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why.

    My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why.

    It probably depends a lot on your hardware, and the type of unix box -you have at the other end of the link.

    Paul Cochrane has done some testing on client side tuning and come -to the following conclusions:

    Install the W2setup.exe file from www.microsoft.com. This is an -update for the winsock stack and utilities which improve performance.

    Configure the win95 TCPIP registry settings to give better -perfomance. I use a program called MTUSPEED.exe which I got off the -net. There are various other utilities of this type freely available. -The setting which give the best performance for me are:

    1. MaxMTU Remove

    2. RWIN Remove

    3. MTUAutoDiscover Disable

    4. MTUBlackHoleDetect Disable

    5. Time To Live Enabled

    6. Time To Live - HOPS 32

    7. NDI Cache Size 0

    I tried virtually all of the items mentioned in the document and -the only one which made a difference to me was the socket options. It -turned out I was better off without any!!!!!

    In terms of overall speed of transfer, between various win95 clients -and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE -drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

    The figures are:          Put              Get 
-P166 client 3Com card:    420-440kB/s      500-520kB/s
-P100 client 3Com card:    390-410kB/s      490-510kB/s
-DX4-75 client NE2000:     370-380kB/s      330-350kB/s

    I based these test on transfer two files a 4.5MB text file and a 15MB -textfile. The results arn't bad considering the hardware Samba is -running on. It's a crap machine!!!!

    The updates mentioned in 1 and 2 brought up the transfer rates from -just over 100kB/s in some clients.

    A new client is a P333 connected via a 100MB/s card and hub. The -transfer rates from this were good: 450-500kB/s on put and 600+kB/s -on get.

    Looking at standard FTP throughput, Samba is a bit slower (100kB/s -upwards). I suppose there is more going on in the samba protocol, but -if it could get up to the rate of FTP the perfomance would be quite -staggering.

    Chapter 33. The samba checklist

    33.1. Introduction

    This file contains a list of tests you can perform to validate your -Samba server. It also tells you what the likely cause of the problem -is if it fails any one of these steps. If it passes all these tests -then it is probably working fine.

    You should do ALL the tests, in the order shown. We have tried to -carefully choose them so later tests only use capabilities verified in -the earlier tests.

    If you send one of the samba mailing lists an email saying "it doesn't work" -and you have not followed this test procedure then you should not be surprised -your email is ignored.

    33.2. Assumptions

    In all of the tests it is assumed you have a Samba server called -BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    The procedure is similar for other types of clients.

    It is also assumed you know the name of an available share in your -smb.conf. I will assume this share is called tmp. -You can add a tmp share like by adding the -following to smb.conf:

    
[tmp]
- comment = temporary files 
- path = /tmp
- read only = yes

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions.

    Please pay attention to the error messages you receive. If any error message -reports that your server is being unfriendly you should first check that you -IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf -file points to name servers that really do exist.

    Also, if you do not have DNS server access for name resolution please check -that the settings for your smb.conf file results in dns proxy = no. The -best way to check this is with testparm smb.conf.

    33.3. The tests

    Diagnosing your samba server

    1. In the directory in which you store your smb.conf file, run the command -testparm smb.conf. If it reports any errors then your smb.conf -configuration file is faulty.

      Your smb.conf file may be located in: /etc/samba -Or in: /usr/local/samba/lib

    2. Run the command ping BIGSERVER from the PC and -ping ACLIENT from -the unix box. If you don't get a valid response then your TCP/IP -software is not correctly installed.

      Note that you will need to start a "dos prompt" window on the PC to -run ping.

      If you get a message saying "host not found" or similar then your DNS -software or /etc/hosts file is not correctly setup. -It is possible to -run samba without DNS entries for the server and client, but I assume -you do have correct entries for the remainder of these tests.

      Another reason why ping might fail is if your host is running firewall -software. You will need to relax the rules to let in the workstation -in question, perhaps by allowing access from another subnet (on Linux -this is done via the ipfwadm program.)

    3. Run the command smbclient -L BIGSERVER on the unix box. You -should get a list of available shares back.

      If you get a error message containing the string "Bad password" then -you probably have either an incorrect hosts allow, -hosts deny or valid users line in your -smb.conf, or your guest account is not -valid. Check what your guest account is using testparm and -temporarily remove any hosts allow, hosts deny, valid users or invalid users lines.

      If you get a "connection refused" response then the smbd server may -not be running. If you installed it in inetd.conf then you probably edited -that file incorrectly. If you installed it as a daemon then check that -it is running, and check that the netbios-ssn port is in a LISTEN -state using netstat -a.

      If you get a "session request failed" then the server refused the -connection. If it says "Your server software is being unfriendly" then -its probably because you have invalid command line parameters to smbd, -or a similar fatal problem with the initial startup of smbd. Also -check your config file (smb.conf) for syntax errors with testparm -and that the various directories where samba keeps its log and lock -files exist.

      There are a number of reasons for which smbd may refuse or decline -a session request. The most common of these involve one or more of -the following smb.conf file entries:

      	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes

      In the above, no allowance has been made for any session requests that -will automatically translate to the loopback adaptor address 127.0.0.1. -To solve this problem change these lines to:

      	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.

      Do NOT use the bind interfaces only parameter where you -may wish to -use the samba password change facility, or where smbclient may need to -access local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency -where it will not allow connections to the loopback address will be -fixed soon).

      Another common cause of these two errors is having something already running -on port 139, such as Samba (ie: smbd is running from inetd already) or -something like Digital's Pathworks. Check your inetd.conf file before trying -to start smbd as a daemon, it can avoid a lot of frustration!

      And yet another possible cause for failure of this test is when the subnet mask -and / or broadcast address settings are incorrect. Please check that the -network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the log.nmb file.

    4. Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the -IP address of your Samba server back.

      If you don't then nmbd is incorrectly installed. Check your inetd.conf -if you run it from there, or that the daemon is running and listening -to udp port 137.

      One common problem is that many inetd implementations can't take many -parameters on the command line. If this is the case then create a -one-line script that contains the right parameters and run that from -inetd.

    5. run the command nmblookup -B ACLIENT '*'

      You should get the PCs IP address back. If you don't then the client -software on the PC isn't installed correctly, or isn't started, or you -got the name of the PC wrong.

      If ACLIENT doesn't resolve via DNS then use the IP address of the -client in the above test.

    6. Run the command nmblookup -d 2 '*'

      This time we are trying the same as the previous test but are trying -it via a broadcast to the default broadcast address. A number of -Netbios/TCPIP hosts on the network should respond, although Samba may -not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts.

      If this doesn't give a similar result to the previous test then -nmblookup isn't correctly getting your broadcast address through its -automatic mechanism. In this case you should experiment use the -interfaces option in smb.conf to manually configure your IP -address, broadcast and netmask.

      If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to the that of the PCs -subnet.

      This test will probably fail if your subnet mask and broadcast address are -not correct. (Refer to TEST 3 notes above).

    7. Run the command smbclient //BIGSERVER/TMP. You should -then be prompted for a password. You should use the password of the account -you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of -the command line. eg: -smbclient //bigserver/tmp -Ujohndoe

      It is possible to specify the password along with the username -as follows: -smbclient //bigserver/tmp -Ujohndoe%secret

      Once you enter the password you should get the smb> prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your smb.conf.

      If it says "bad password" then the likely causes are:

      1. you have shadow passords (or some other password system) but didn't - compile in support for them in smbd -

      2. your valid users configuration is incorrect -

      3. you have a mixed case password and you haven't enabled the password - level option at a high enough level -

      4. the path = line in smb.conf is incorrect. Check it with testparm -

      5. you enabled password encryption but didn't create the SMB encrypted - password file -

      Once connected you should be able to use the commands -dir get put etc. -Type help command for instructions. You should -especially check that the amount of free disk space shown is correct -when you type dir.

    8. On the PC type the command net view \\BIGSERVER. You will -need to do this from within a "dos prompt" window. You should get back a -list of available shares on the server.

      If you get a "network name not found" or similar error then netbios -name resolution is not working. This is usually caused by a problem in -nmbd. To overcome it you could do one of the following (you only need -to choose one of them):

      1. fixup the nmbd installation

      2. add the IP address of BIGSERVER to the wins server box in the - advanced tcp/ip setup on the PC.

      3. enable windows name resolution via DNS in the advanced section of - the tcp/ip setup

      4. add BIGSERVER to your lmhosts file on the PC.

      If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the smbclient -L test above. In -particular, make sure your hosts allow line is correct (see the man -pages)

      Also, do not overlook that fact that when the workstation requests the -connection to the samba server it will attempt to connect using the -name with which you logged onto your Windows machine. You need to make -sure that an account exists on your Samba server with that exact same -name and password.

      If you get "specified computer is not receiving requests" or similar -it probably means that the host is not contactable via tcp services. -Check to see if the host is running tcp wrappers, and if so add an entry in -the hosts.allow file for your client (or subnet, etc.)

    9. Run the command net use x: \\BIGSERVER\TMP. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly -installed or your smb.conf is incorrect. make sure your hosts allow -and other config lines in smb.conf are correct.

      It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = -username to the [tmp] section of -smb.conf where username is the -username corresponding to the password you typed. If you find this -fixes things you may need the username mapping option.

      It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf -Turn it back on to fix.

    10. Run the command nmblookup -M testgroup where -testgroup is the name of the workgroup that your Samba server and -Windows PCs belong to. You should get back the IP address of the -master browser for that workgroup.

      If you don't then the election process has failed. Wait a minute to -see if it is just being slow then try again. If it still fails after -that then look at the browsing options you have set in smb.conf. Make -sure you have preferred master = yes to ensure that -an election is held at startup.

    11. From file manager try to browse the server. Your samba server should -appear in the browse list of your local workgroup (or the one you -specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it -is refusing to browse a server that has no encrypted password -capability and is in user level security mode. In this case either set -security = server AND -password server = Windows_NT_Machine in your -smb.conf file, or make sure encrypted passwords is -set to "yes".

    Chapter 34. Analysing and solving samba problems

    There are many sources of information available in the form -of mailing lists, RFC's and documentation. The docs that come -with the samba distribution contain very good explanations of -general SMB topics such as browsing.

    34.1. Diagnostics tools

    One of the best diagnostic tools for debugging problems is Samba itself. -You can use the -d option for both smbd and nmbd to specify what -'debug level' at which to run. See the man pages on smbd, nmbd and -smb.conf for more information on debugging options. The debug -level can range from 1 (the default) to 10 (100 for debugging passwords).

    Another helpful method of debugging is to compile samba using the -gcc -g flag. This will include debug -information in the binaries and allow you to attach gdb to the -running smbd / nmbd process. In order to attach gdb to an smbd -process for an NT workstation, first get the workstation to make the -connection. Pressing ctrl-alt-delete and going down to the domain box -is sufficient (at least, on the first time you join the domain) to -generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation -maintains an open connection, and therefore there will be an smbd -process running (assuming that you haven't set a really short smbd -idle timeout) So, in between pressing ctrl alt delete, and actually -typing in your password, you can gdb attach and continue.

    Some useful samba commands worth investigating:

    • testparam | more

    • smbclient -L //{netbios name of server}

    An SMB enabled version of tcpdump is available from -http://www.tcpdup.org/. -Ethereal, another good packet sniffer for Unix and Win32 -hosts, can be downloaded from http://www.ethereal.com.

    For tracing things on the Microsoft Windows NT, Network Monitor -(aka. netmon) is available on the Microsoft Developer Network CD's, -the Windows NT Server install CD and the SMS CD's. The version of -netmon that ships with SMS allows for dumping packets between any two -computers (i.e. placing the network interface in promiscuous mode). -The version on the NT Server install CD will only allow monitoring -of network traffic directed to the local NT box and broadcasts on the -local subnet. Be aware that Ethereal can read and write netmon -formatted files.

    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box

    Installing netmon on an NT workstation requires a couple -of steps. The following are for installing Netmon V4.00.349, which comes -with Microsoft Windows NT Server 4.0, on Microsoft Windows NT -Workstation 4.0. The process should be similar for other version of -Windows NT / Netmon. You will need both the Microsoft Windows -NT Server 4.0 Install CD and the Workstation 4.0 Install CD.

    Initially you will need to install 'Network Monitor Tools and Agent' -on the NT Server. To do this

    • Goto Start - Settings - Control Panel - - Network - Services - Add

    • Select the 'Network Monitor Tools and Agent' and - click on 'OK'.

    • Click 'OK' on the Network Control Panel. -

    • Insert the Windows NT Server 4.0 install CD - when prompted.

    At this point the Netmon files should exist in -%SYSTEMROOT%\System32\netmon\*.*. -Two subdirectories exist as well, parsers\ -which contains the necessary DLL's for parsing the netmon packet -dump, and captures\.

    In order to install the Netmon tools on an NT Workstation, you will -first need to install the 'Network Monitor Agent' from the Workstation -install CD.

    • Goto Start - Settings - Control Panel - - Network - Services - Add

    • Select the 'Network Monitor Agent' and click - on 'OK'.

    • Click 'OK' on the Network Control Panel. -

    • Insert the Windows NT Workstation 4.0 install - CD when prompted.

    Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* -to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set -permissions as you deem appropriate for your site. You will need -administrative rights on the NT box to run netmon.

    To install Netmon on a Windows 9x box install the network monitor agent -from the Windows 9x CD (\admin\nettools\netmon). There is a readme -file located with the netmon driver files on the CD if you need -information on how to do this. Copy the files from a working -Netmon installation.

    34.3. Useful URL's

    34.4. Getting help from the mailing lists

    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror -and then click on Support and then click on Samba related mailing lists.

    For questions relating to Samba TNG go to -http://www.samba-tng.org/ -It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.

    If you post a message to one of the lists please observe the following guide lines :

    • Always remember that the developers are volunteers, they are -not paid and they never guarantee to produce a particular feature at -a particular time. Any time lines are 'best guess' and nothing more.

    • Always mention what version of samba you are using and what -operating system its running under. You should probably list the -relevant sections of your smb.conf file, at least the options -in [global] that affect PDC support.

    • In addition to the version, if you obtained Samba via -CVS mention the date when you last checked it out.

    • Try and make your question clear and brief, lots of long, -convoluted questions get deleted before they are completely read ! -Don't post html encoded messages (if you can select colour or font -size its html).

    • If you run one of those nifty 'I'm on holidays' things when -you are away, make sure its configured to not answer mailing lists.

    • Don't cross post. Work out which is the best list to post to -and see what happens, i.e. don't post to both samba-ntdom and samba-technical. -Many people active on the lists subscribe to more -than one list and get annoyed to see the same message two or more times. -Often someone will see a message and thinking it would be better dealt -with on another, will forward it on for you.

    • You might include partial -log files written at a debug level set to as much as 20. -Please don't send the entire log but enough to give the context of the -error messages.

    • (Possibly) If you have a complete netmon trace ( from the opening of -the pipe to the error ) you can send the *.CAP file as well.

    • Please think carefully before attaching a document to an email. -Consider pasting the relevant parts into the body of the message. The samba -mailing lists go to a huge number of people, do they all need a copy of your -smb.conf in their attach directory?

    34.5. How to get off the mailinglists

    To have your name removed from a samba mailing list, go to the -same place you went to to get on it. Go to http://lists.samba.org, -click on your nearest mirror and then click on Support and -then click on Samba related mailing lists. Or perhaps see -here

    Please don't post messages to the list asking to be removed, you will just -be referred to the above address (unless that process failed in some way...)

    Chapter 35. Reporting Bugs

    35.1. Introduction

    The email address for bug reports for stable releases is samba@samba.org. -Bug reports for alpha releases should go to samba-technical@samba.org.

    Please take the time to read this file before you submit a bug -report. Also, please see if it has changed between releases, as we -may be changing the bug reporting mechanism at some time.

    Please also do as much as you can yourself to help track down the -bug. Samba is maintained by a dedicated group of people who volunteer -their time, skills and efforts. We receive far more mail about it than -we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets -us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb -newsgroup or the mailing list that we will read it. If you suspect that your -problem is not a bug but a configuration problem then it is better to send -it to the Samba mailing list, as there are (at last count) 5000 other users on -that list that may be able to help you.

    You may also like to look though the recent mailing list archives, -which are conveniently accessible on the Samba web pages -at http://samba.org/samba/.

    35.2. General info

    Before submitting a bug report check your config for silly -errors. Look in your log files for obvious messages that tell you that -you've misconfigured something and run testparm to test your config -file for correct syntax.

    Have you run through the diagnosis? -This is very important.

    If you include part of a log file with your bug report then be sure to -annotate it with exactly what you were doing on the client at the -time, and exactly what the results were.

    35.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a -server (like refusing to open a file) then the log files will probably -be very useful. Depending on the problem a log level of between 3 and -10 showing the problem may be appropriate. A higher level givesmore -detail, but may use too much disk space.

    To set the debug level use log level = in your -smb.conf. You may also find it useful to set the log -level higher for just one machine and keep separate logs for each machine. -To do this use:

    log level = 10
-log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m

    then create a file -/usr/local/samba/lib/smb.conf.machine where -machine is the name of the client you wish to debug. In that file -put any smb.conf commands you want, for example -log level= may be useful. This also allows you to -experiment with different security systems, protocol levels etc on just -one machine.

    The smb.conf entry log level = -is synonymous with the entry debuglevel = that has been -used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.

    As the log level = value is increased you will record -a significantly increasing level of debugging information. For most -debugging operations you may not need a setting higher than 3. Nearly -all bugs can be tracked at a setting of 10, but be prepared for a VERY -large volume of log data.

    35.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that -Samba got an unexpected signal while running. It is probably a -segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software).

    If the message came from smbd then it will probably be accompanied by -a message which details the last SMB message received by smbd. This -info is often very useful in tracking down the problem so please -include it in your bug report.

    You should also detail how to reproduce the problem, if -possible. Please make this reasonably detailed.

    You may also find that a core file appeared in a corefiles -subdirectory of the directory where you keep your samba log -files. This file is the most useful tool for tracking down the bug. To -use it you do this:

    gdb smbd core

    adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try dbx. Then within the debugger use the -command where to give a stack trace of where the problem -occurred. Include this in your mail.

    If you known any assembly language then do a disass of the routine -where the problem occurred (if its in a library routine then -disassemble the routine that called it) and try to work out exactly -where the problem is by looking at the surrounding code. Even if you -don't know assembly then incuding this info in the bug report can be -useful.

    35.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) -refuse to dump a core file if the task has changed uid (which smbd -does often). To debug with this sort of system you could try to attach -to the running process using gdb smbd PID where you get PID from -smbstatus. Then use c to continue and try to cause the core dump -using the client. The debugger should catch the fault and tell you -where it occurred.

    35.6. Patches

    The best sort of bug report is one that includes a fix! If you send us -patches please use diff -u format if your version of -diff supports it, otherwise use diff -c4. Make sure -your do the diff against a clean version of the source and let me know -exactly what version you used.

    \ No newline at end of file +performance. Check the sections on the various clients in +Samba and Other Clients. +

    diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index ac0fac371f..b46173f559 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -1,431 +1,113 @@ - -Reporting Bugs
    SAMBA Project Documentation
    Prev 

    Chapter 35. Reporting Bugs

    35.1. Introduction

    The email address for bug reports for stable releases is samba@samba.org. -Bug reports for alpha releases should go to samba-technical@samba.org.

    Please take the time to read this file before you submit a bug + +Chapter29.Reporting Bugs

    Chapter29.Reporting Bugs
    PrevPartIV.TroubleshootingNext

    Chapter29.Reporting Bugs

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Samba Team

    27 June 1997

    Table of Contents

    Introduction
    General info
    Debug levels
    Internal errors
    Attaching to a running process
    Patches

    Introduction

    Please report bugs using bugzilla.

    +Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we -may be changing the bug reporting mechanism at some time.

    Please also do as much as you can yourself to help track down the +may be changing the bug reporting mechanism at some time. +

    +Please also do as much as you can yourself to help track down the bug. Samba is maintained by a dedicated group of people who volunteer their time, skills and efforts. We receive far more mail about it than we can possibly answer, so you have a much higher chance of an answer -and a fix if you send us a "developer friendly" bug report that lets -us fix it fast.

    Do not assume that if you post the bug to the comp.protocols.smb +and a fix if you send us a "developer friendly" bug report that lets +us fix it fast. +

    +Do not assume that if you post the bug to the comp.protocols.smb newsgroup or the mailing list that we will read it. If you suspect that your problem is not a bug but a configuration problem then it is better to send it to the Samba mailing list, as there are (at last count) 5000 other users on -that list that may be able to help you.

    You may also like to look though the recent mailing list archives, +that list that may be able to help you. +

    +You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba web pages -at http://samba.org/samba/.

    35.2. General info

    Before submitting a bug report check your config for silly +at http://samba.org/samba/. +

    General info

    +Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config -file for correct syntax.

    Have you run through the diagnosis? -This is very important.

    If you include part of a log file with your bug report then be sure to +file for correct syntax. +

    +Have you run through the diagnosis? +This is very important. +

    +If you include part of a log file with your bug report then be sure to annotate it with exactly what you were doing on the client at the -time, and exactly what the results were.

    35.3. Debug levels

    If the bug has anything to do with Samba behaving incorrectly as a +time, and exactly what the results were. +

    Debug levels

    +If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably be very useful. Depending on the problem a log level of between 3 and 10 showing the problem may be appropriate. A higher level givesmore -detail, but may use too much disk space.

    To set the debug level use log level = in your -smb.conf. You may also find it useful to set the log +detail, but may use too much disk space. +

    +To set the debug level use log level = in your +smb.conf. You may also find it useful to set the log level higher for just one machine and keep separate logs for each machine. -To do this use:

    log level = 10
+To do this use:
+
    +log level = 10
 log file = /usr/local/samba/lib/log.%m
-include = /usr/local/samba/lib/smb.conf.%m
    then create a file 
-/usr/local/samba/lib/smb.conf.machine where
-machine is the name of the client you wish to debug. In that file
-put any smb.conf commands you want, for example 
-log level= may be useful. This also allows you to 
+include = /usr/local/samba/lib/smb.conf.%m
+

    +then create a file +/usr/local/samba/lib/smb.conf.machine where +machine is the name of the client you wish to debug. In that file +put any smb.conf commands you want, for example +log level= may be useful. This also allows you to experiment with different security systems, protocol levels etc on just -one machine.

    The smb.conf entry log level = -is synonymous with the entry debuglevel = that has been +one machine. +

    +The smb.conf entry log level = +is synonymous with the entry debuglevel = that has been used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.

    As the log level = value is increased you will record +compatibility of smb.conf files. +

    +As the log level = value is increased you will record a significantly increasing level of debugging information. For most debugging operations you may not need a setting higher than 3. Nearly all bugs can be tracked at a setting of 10, but be prepared for a VERY -large volume of log data.

    35.4. Internal errors

    If you get a "INTERNAL ERROR" message in your log files it means that +large volume of log data. +

    Internal errors

    +If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software).

    If the message came from smbd then it will probably be accompanied by +you have faulty hardware or system software). +

    +If the message came from smbd then it will probably be accompanied by a message which details the last SMB message received by smbd. This info is often very useful in tracking down the problem so please -include it in your bug report.

    You should also detail how to reproduce the problem, if -possible. Please make this reasonably detailed.

    You may also find that a core file appeared in a corefiles +include it in your bug report. +

    +You should also detail how to reproduce the problem, if +possible. Please make this reasonably detailed. +

    +You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your samba log files. This file is the most useful tool for tracking down the bug. To -use it you do this:

    gdb smbd core

    adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try dbx. Then within the debugger use the -command where to give a stack trace of where the problem -occurred. Include this in your mail.

    If you known any assembly language then do a disass of the routine +use it you do this: +

    gdb smbd core

    +adding appropriate paths to smbd and core so gdb can find them. If you +don't have gdb then try dbx. Then within the debugger use the +command where to give a stack trace of where the problem +occurred. Include this in your mail. +

    +If you know any assembly language then do a disass of the routine where the problem occurred (if its in a library routine then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you don't know assembly then incuding this info in the bug report can be -useful.

    35.5. Attaching to a running process

    Unfortunately some unixes (in particular some recent linux kernels) +useful. +

    Attaching to a running process

    +Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd does often). To debug with this sort of system you could try to attach -to the running process using gdb smbd PID where you get PID from -smbstatus. Then use c to continue and try to cause the core dump +to the running process using gdb smbd PID where you get PID from +smbstatus. Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you -where it occurred.

    35.6. Patches

    The best sort of bug report is one that includes a fix! If you send us -patches please use diff -u format if your version of -diff supports it, otherwise use diff -c4. Make sure -your do the diff against a clean version of the source and let me know -exactly what version you used.

    PrevHome 
    Analysing and solving samba problemsUp 
    \ No newline at end of file +where it occurred. +

    Patches

    +The best sort of bug report is one that includes a fix! If you send us +patches please use diff -u format if your version of +diff supports it, otherwise use diff -c4. Make sure +you do the diff against a clean version of the source and let me know +exactly what version you used. +

    PrevUpNext
    Chapter28.Analysing and solving samba problemsHomePartV.Appendixes
    diff --git a/docs/htmldocs/compiling.html b/docs/htmldocs/compiling.html index 9c91e70ce1..c62fcf13f2 100644 --- a/docs/htmldocs/compiling.html +++ b/docs/htmldocs/compiling.html @@ -1,971 +1,186 @@ - -How to compile SAMBA
    SAMBA Project Documentation
    PrevNext

    Chapter 27. How to compile SAMBA

    You can obtain the samba source from the samba website. To obtain a development version, -you can download samba from CVS or using rsync.

    27.1. Access Samba source code via CVS

    27.1.1. Introduction

    Samba is developed in an open environment. Developers use CVS -(Concurrent Versioning System) to "checkin" (also known as -"commit") new source code. Samba's various CVS branches can + +Chapter30.How to compile SAMBA

    Chapter30.How to compile SAMBA
    PrevPartV.AppendixesNext

    Chapter30.How to compile SAMBA

    Samba Team

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    (22 May 2001)

    18 March 2003

    Table of Contents

    Access Samba source code via CVS
    Introduction
    CVS Access to samba.org
    Accessing the samba sources via rsync and ftp
    Verifying Samba's PGP signature
    Building the Binaries
    Compiling samba with Active Directory support
    Starting the smbd and nmbd
    Starting from inetd.conf
    Alternative: starting it as a daemon

    +You can obtain the samba source from the samba website. To obtain a development version, +you can download samba from CVS or using rsync. +

    Access Samba source code via CVS

    Introduction

    +Samba is developed in an open environment. Developers use CVS +(Concurrent Versioning System) to "checkin" (also known as +"commit") new source code. Samba's various CVS branches can be accessed via anonymous CVS using the instructions -detailed in this chapter.

    This chapter is a modified version of the instructions found at -http://samba.org/samba/cvs.html

    27.1.2. CVS Access to samba.org

    The machine samba.org runs a publicly accessible CVS +detailed in this chapter. +

    +This chapter is a modified version of the instructions found at +http://samba.org/samba/cvs.html +

    CVS Access to samba.org

    +The machine samba.org runs a publicly accessible CVS repository for access to the source code of several packages, including samba, rsync and jitterbug. There are two main ways of -accessing the CVS server on this host.

    27.1.2.1. Access via CVSweb

    You can access the source code via your +accessing the CVS server on this host. +

    Access via CVSweb

    +You can access the source code via your favourite WWW browser. This allows you to access the contents of individual files in the repository and also to look at the revision history and commit logs of individual files. You can also ask for a diff -listing between any two versions on the repository.

    Use the URL : http://samba.org/cgi-bin/cvsweb

    27.1.2.2. Access via cvs

    You can also access the source code via a -normal cvs client. This gives you much more control over you can +listing between any two versions on the repository. +

    +Use the URL : http://samba.org/cgi-bin/cvsweb +

    Access via cvs

    +You can also access the source code via a +normal cvs client. This gives you much more control over what you can do with the repository and allows you to checkout whole source trees and keep them up to date via normal cvs commands. This is the preferred method of access if you are a developer and not -just a casual browser.

    To download the latest cvs source code, point your -browser at the URL : http://www.cyclic.com/. +just a casual browser. +

    +To download the latest cvs source code, point your +browser at the URL : http://www.cyclic.com/. and click on the 'How to get cvs' link. CVS is free software under the GNU GPL (as is Samba). Note that there are several graphical CVS clients which provide a graphical interface to the sometimes mundane CVS commands. -Links to theses clients are also available from http://www.cyclic.com.

    To gain access via anonymous cvs use the following steps. +Links to theses clients are also available from http://www.cyclic.com. +

    +To gain access via anonymous cvs use the following steps. For this example it is assumed that you want a copy of the samba source code. For the other source code repositories -on this system just substitute the correct package name

    1. Install a recent copy of cvs. All you really need is a +on this system just substitute the correct package name +

      1. + Install a recent copy of cvs. All you really need is a copy of the cvs client binary. -

      2. Run the command -

        cvs -d :pserver:cvs@samba.org:/cvsroot login -

        When it asks you for a password type cvs. -

      3. Run the command -

        cvs -d :pserver:cvs@samba.org:/cvsroot co samba -

        This will create a directory called samba containing the +

      4. + Run the command +

        + cvs -d :pserver:cvs@samba.org:/cvsroot login +

        + When it asks you for a password type cvs. +

      5. + Run the command +

        + cvs -d :pserver:cvs@samba.org:/cvsroot co samba +

        + This will create a directory called samba containing the latest samba source code (i.e. the HEAD tagged cvs branch). This currently corresponds to the 3.0 development tree. -

        CVS branches other HEAD can be obtained by using the -r +

        + CVS branches other then HEAD can be obtained by using the -r and defining a tag name. A list of branch tag names can be found on the - "Development" page of the samba web site. A common request is to obtain the + "Development" page of the samba web site. A common request is to obtain the latest 2.2 release code. This could be done by using the following userinput. -

        cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba -

      6. Whenever you want to merge in the latest code changes use +

        + cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba +

      7. + Whenever you want to merge in the latest code changes use the following command from within the samba directory: -

        cvs update -d -P -

    27.2. Accessing the samba sources via rsync and ftp

    pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. - See the rsync homepage for more info on rsync. -

    The disadvantage of the unpacked trees +

    + cvs update -d -P +

    Accessing the samba sources via rsync and ftp

    + pserver.samba.org also exports unpacked copies of most parts of the CVS tree at ftp://pserver.samba.org/pub/unpacked and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/. I recommend using rsync rather than ftp. + See the rsync homepage for more info on rsync. +

    + The disadvantage of the unpacked trees is that they do not support automatic merging of local changes like CVS does. rsync access is most convenient for an initial install. -

    27.3. Verifying Samba's PGP signature

    In these days of insecurity, it's strongly recommended that you verify the PGP signature for any +

    Verifying Samba's PGP signature

    +In these days of insecurity, it's strongly recommended that you verify the PGP signature for any source file before installing it. According to Jerry Carter of the Samba Team, only about 22% of all Samba downloads have had a corresponding PGP signature download (a very low percentage, which should be considered a bad thing). Even if you're not downloading from a mirror site, verifying PGP -signatures should be a standard reflex.

    With that said, go ahead and download the following files:

         $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
-     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc

    The first file is the PGP signature for the Samba source file; the other is the Samba public -PGP key itself. Import the public PGP key with:

         $ gpg --import samba-pubkey.asc

    And verify the Samba source code integrity with:

         $ gzip -d samba-2.2.8a.tar.gz
-     $ gpg --verify samba-2.2.8a.tar.asc

    If you receive a message like, "Good signature from Samba Distribution Verification Key..." +signatures should be a standard reflex. +

    +With that said, go ahead and download the following files: +

    +     $ wget http://us1.samba.org/samba/ftp/samba-2.2.8a.tar.asc
+     $ wget http://us1.samba.org/samba/ftp/samba-pubkey.asc
+

    +The first file is the PGP signature for the Samba source file; the other is the Samba public +PGP key itself. Import the public PGP key with: +

    +     $ gpg --import samba-pubkey.asc
+

    +And verify the Samba source code integrity with: +

    +     $ gzip -d samba-2.2.8a.tar.gz
+     $ gpg --verify samba-2.2.8a.tar.asc
+

    +If you receive a message like, "Good signature from Samba Distribution Verification Key..." then all is well. The warnings about trust relationships can be ignored. An example of what -you would not want to see would be:

         gpg: BAD signature from "Samba Distribution Verification Key"

    27.4. Building the Binaries

    To do this, first run the program ./configure - in the source directory. This should automatically +you would not want to see would be: +

    +     gpg: BAD signature from "Samba Distribution Verification Key"
+

    Building the Binaries

    To do this, first run the program ./configure + in the source directory. This should automatically configure Samba for your operating system. If you have unusual - needs then you may wish to run

    root# ./configure --help -

    first to see what special options you can enable. - Then executing

    root# make

    will create the binaries. Once it's successfully - compiled you can use

    root# make install

    to install the binaries and manual pages. You can - separately install the binaries and/or man pages using

    root# make installbin -

    and

    root# make installman -

    Note that if you are upgrading for a previous version + needs then you may wish to run

    root# ./configure --help +

    first to see what special options you can enable. + Then executing

    root# make

    will create the binaries. Once it's successfully + compiled you can use

    root# make install

    to install the binaries and manual pages. You can + separately install the binaries and/or man pages using

    root# make installbin +

    and

    root# make installman +

    Note that if you are upgrading for a previous version of Samba you might like to know that the old versions of - the binaries will be renamed with a ".old" extension. You - can go back to the previous version with

    root# make revert -

    if you find this version a disaster!

    27.4.1. Compiling samba with Active Directory support

    In order to compile samba with ADS support, you need to have installed - on your system: -

    the MIT kerberos development libraries (either install from the sources or use a package). The heimdal libraries will not work.
    the OpenLDAP development libraries.

    If your kerberos libraries are in a non-standard location then - remember to add the configure option --with-krb5=DIR.

    After you run configure make sure that include/config.h it generates contains lines like this:

    #define HAVE_KRB5 1
+	the binaries will be renamed with a ".old" extension. You 
+	can go back to the previous version with
    root# make revert
+	
    if you find this version a disaster!
    Compiling samba with Active Directory support
    In order to compile samba with ADS support, you need to have installed
+	on your system:
    • the MIT kerberos development libraries
+	    (either install from the sources or use a package). The
+	    heimdal libraries will not work.
    • the OpenLDAP development libraries.
    If your kerberos libraries are in a non-standard location then
+	  remember to add the configure option --with-krb5=DIR.
    After you run configure make sure that include/config.h it generates contains lines like this:
    +#define HAVE_KRB5 1
 #define HAVE_LDAP 1
-		  
    If it doesn't then configure did not find your krb5 libraries or
+

    If it doesn't then configure did not find your krb5 libraries or your ldap libraries. Look in config.log to figure out why and fix - it.

    27.4.1.1. Installing the required packages for Debian

    On Debian you need to install the following packages:

    libkrb5-dev
    krb5-user

    -

    27.4.1.2. Installing the required packages for RedHat

    On RedHat this means you should have at least:

    krb5-workstation (for kinit)
    krb5-libs (for linking with)
    krb5-devel (because you are compiling from source)

    -

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need - to get them off CD2.

    27.5. Starting the smbd and nmbd

    You must choose to start smbd and nmbd either - as daemons or from inetdDon't try - to do both! Either you can put them in inetd.conf and have them started on demand - by inetd, or you can start them as - daemons either from the command line or in /etc/rc.local. See the man pages for details + it.

    Installing the required packages for Debian

    On Debian you need to install the following packages:

    +

    • libkrb5-dev
    • krb5-user

    +

    Installing the required packages for RedHat

    On RedHat this means you should have at least:

    +

    • krb5-workstation (for kinit)
    • krb5-libs (for linking with)
    • krb5-devel (because you are compiling from source)

    +

    in addition to the standard development environment.

    Note that these are not standard on a RedHat install, and you may need + to get them off CD2.

    Starting the smbd and nmbd

    You must choose to start smbd and nmbd either + as daemons or from inetdDon't try + to do both! Either you can put them in + inetd.conf and have them started on demand + by inetd, or you can start them as + daemons either from the command line or in + /etc/rc.local. See the man pages for details on the command line options. Take particular care to read the bit about what user you need to be in order to start - Samba. In many cases you must be root.

    The main advantage of starting smbd - and nmbd using the recommended daemon method + Samba. In many cases you must be root.

    The main advantage of starting smbd + and nmbd using the recommended daemon method is that they will respond slightly more quickly to an initial connection - request.

    27.5.1. Starting from inetd.conf

    NOTE; The following will be different if - you use NIS, NIS+ or LDAP to distribute services maps.

    Look at your /etc/services. + request.

    Starting from inetd.conf

    NOTE; The following will be different if + you use NIS, NIS+ or LDAP to distribute services maps.

    Look at your /etc/services. What is defined at port 139/tcp. If nothing is defined - then add a line like this:

    netbios-ssn 139/tcp

    similarly for 137/udp you should have an entry like:

    netbios-ns 137/udp

    Next edit your /etc/inetd.conf - and add two lines something like this:

    		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
+		then add a line like this:
    netbios-ssn     139/tcp
    similarly for 137/udp you should have an entry like:
    netbios-ns	137/udp
    Next edit your /etc/inetd.conf 
+		and add two lines something like this:
    +		netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd 
 		netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd 
-		
    The exact syntax of /etc/inetd.conf 
+

    The exact syntax of /etc/inetd.conf varies between unixes. Look at the other entries in inetd.conf - for a guide.

    Some unixes already have entries like netbios_ns - (note the underscore) in /etc/services. - You must either edit /etc/services or - /etc/inetd.conf to make them consistent.

    On many systems you may need to use the - interfaces option in smb.conf to specify the IP address - and netmask of your interfaces. Run ifconfig + for a guide.

    Note

    Some unixes already have entries like netbios_ns + (note the underscore) in /etc/services. + You must either edit /etc/services or + /etc/inetd.conf to make them consistent.

    Note

    On many systems you may need to use the + interfaces option in smb.conf to specify the IP address + and netmask of your interfaces. Run ifconfig as root if you don't know what the broadcast is for your - net. nmbd tries to determine it at run + net. nmbd tries to determine it at run time, but fails on some unixes. -

    Many unixes only accept around 5 - parameters on the command line in inetd.conf. +

    Warning

    Many unixes only accept around 5 + parameters on the command line in inetd.conf. This means you shouldn't use spaces between the options and arguments, or you should use a script, and start the script - from inetd.

    Restart inetd, perhaps just send - it a HUP. If you have installed an earlier version of nmbd then you may need to kill nmbd as well.

    27.5.2. Alternative: starting it as a daemon

    To start the server as a daemon you should create + from inetd.

    Restart inetd, perhaps just send + it a HUP. If you have installed an earlier version of + nmbd then you may need to kill nmbd as well.

    Alternative: starting it as a daemon

    To start the server as a daemon you should create a script something like this one, perhaps calling - it startsmb.

    		#!/bin/sh
+		it startsmb.
    +		#!/bin/sh
 		/usr/local/samba/bin/smbd -D 
 		/usr/local/samba/bin/nmbd -D 
-		
    then make it executable with chmod 
-		+x startsmb
    You can then run startsmb by 
-		hand or execute it from /etc/rc.local
-		
    To kill it send a kill signal to the processes 
-		nmbd and smbd.
    If you use the SVR4 style init system then 
-		you may like to look at the examples/svr4-startup
-		script to make Samba fit into that system.
    PrevHomeNext
    AppendixesUpMigration from NT4 PDC to Samba-3 PDC
    \ No newline at end of file +

    then make it executable with chmod + +x startsmb

    You can then run startsmb by + hand or execute it from /etc/rc.local +

    To kill it send a kill signal to the processes + nmbd and smbd.

    Note

    If you use the SVR4 style init system then + you may like to look at the examples/svr4-startup + script to make Samba fit into that system.

    PrevUpNext
    PartV.AppendixesHomeChapter31.Migration from NT4 PDC to Samba-3 PDC
    diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 3c3b3ee4bc..35c0ea11ac 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -1,912 +1,303 @@ - -The samba checklist
    SAMBA Project Documentation
    PrevNext

    Chapter 33. The samba checklist

    Table of Contents
    33.1. Introduction
    33.2. Assumptions
    33.3. The tests
    33.4. Still having troubles?

    33.1. Introduction

    This file contains a list of tests you can perform to validate your + +Chapter27.The samba checklist

    Chapter27.The samba checklist
    PrevPartIV.TroubleshootingNext

    Chapter27.The samba checklist

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Wed Jan 15

    Table of Contents

    Introduction
    Assumptions
    The tests
    Still having troubles?

    Introduction

    +This file contains a list of tests you can perform to validate your Samba server. It also tells you what the likely cause of the problem is if it fails any one of these steps. If it passes all these tests -then it is probably working fine.

    You should do ALL the tests, in the order shown. We have tried to +then it is probably working fine. +

    +You should do ALL the tests, in the order shown. We have tried to carefully choose them so later tests only use capabilities verified in -the earlier tests.

    If you send one of the samba mailing lists an email saying "it doesn't work" +the earlier tests. However, do not stop at the first error as there +have been some instances when continuing with the tests has helped +to solve a problem. +

    +If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then you should not be surprised -your email is ignored.

    33.2. Assumptions

    In all of the tests it is assumed you have a Samba server called -BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

    The procedure is similar for other types of clients.

    It is also assumed you know the name of an available share in your -smb.conf. I will assume this share is called tmp. -You can add a tmp share like by adding the -following to smb.conf:

    
[tmp]
+if your email is ignored.
+

    Assumptions

    +In all of the tests it is assumed you have a Samba server called +BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP. +

    +The procedure is similar for other types of clients. +

    +It is also assumed you know the name of an available share in your +smb.conf. I will assume this share is called tmp. +You can add a tmp share like this by adding the +following to smb.conf: +

    +
+[tmp]
  comment = temporary files 
  path = /tmp
- read only = yes

    These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions.

    Please pay attention to the error messages you receive. If any error message -reports that your server is being unfriendly you should first check that you -IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf -file points to name servers that really do exist.

    Also, if you do not have DNS server access for name resolution please check -that the settings for your smb.conf file results in dns proxy = no. The -best way to check this is with testparm smb.conf.

    33.3. The tests

    Diagnosing your samba server

    1. In the directory in which you store your smb.conf file, run the command -testparm smb.conf. If it reports any errors then your smb.conf -configuration file is faulty.

      Your smb.conf file may be located in: /etc/samba -Or in: /usr/local/samba/lib

    2. Run the command ping BIGSERVER from the PC and -ping ACLIENT from + read only = yes + +

      +

      Note

      +These tests assume version 3.0 or later of the samba suite. +Some commands shown did not exist in earlier versions. +

      +Please pay attention to the error messages you receive. If any error message +reports that your server is being unfriendly you should first check that your +IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf +file points to name servers that really do exist. +

      +Also, if you do not have DNS server access for name resolution please check +that the settings for your smb.conf file results in dns proxy = no. The +best way to check this is with testparm smb.conf. +

      +It is helpful to monitor the log files during testing by using the +tail -F log_file_name in a separate +terminal console (use ctrl-alt-F1 through F6 or multiple terminals in X). +Relevant log files can be found (for default installations) in +/usr/local/samba/var. Also, connection logs from +machines can be found here or possibly in /var/log/samba +depending on how or if you specified logging in your smb.conf file. +

      +If you make changes to your smb.conf file while going through these test, +don't forget to restart smbd and nmbd. +

    The tests

    Procedure27.1.Diagnosing your samba server

    1. +In the directory in which you store your smb.conf file, run the command +testparm smb.conf. If it reports any errors then your smb.conf +configuration file is faulty. +

      Note

      +Your smb.conf file may be located in: /etc/samba +Or in: /usr/local/samba/lib +

    2. +Run the command ping BIGSERVER from the PC and +ping ACLIENT from the unix box. If you don't get a valid response then your TCP/IP -software is not correctly installed.

      Note that you will need to start a "dos prompt" window on the PC to -run ping.

      If you get a message saying "host not found" or similar then your DNS -software or /etc/hosts file is not correctly setup. +software is not correctly installed. +

      +Note that you will need to start a "dos prompt" window on the PC to +run ping. +

      +If you get a message saying "host not found" or similar then your DNS +software or /etc/hosts file is not correctly setup. It is possible to run samba without DNS entries for the server and client, but I assume -you do have correct entries for the remainder of these tests.

      Another reason why ping might fail is if your host is running firewall +you do have correct entries for the remainder of these tests. +

      +Another reason why ping might fail is if your host is running firewall software. You will need to relax the rules to let in the workstation in question, perhaps by allowing access from another subnet (on Linux -this is done via the ipfwadm program.)

    3. Run the command smbclient -L BIGSERVER on the unix box. You -should get a list of available shares back.

      If you get a error message containing the string "Bad password" then -you probably have either an incorrect hosts allow, -hosts deny or valid users line in your -smb.conf, or your guest account is not -valid. Check what your guest account is using testparm and -temporarily remove any hosts allow, hosts deny, valid users or invalid users lines.

      If you get a "connection refused" response then the smbd server may +this is done via the ipfwadm program.) +

      +Note: Modern Linux distributions install ipchains/iptables by default. +This is a common problem that is often overlooked. +

    4. +Run the command smbclient -L BIGSERVER on the unix box. You +should get a list of available shares back. +

      +If you get a error message containing the string "Bad password" then +you probably have either an incorrect hosts allow, +hosts deny or valid users line in your +smb.conf, or your guest account is not +valid. Check what your guest account is using testparm and +temporarily remove any hosts allow, hosts deny, valid users or invalid users lines. +

      +If you get a "connection refused" response then the smbd server may not be running. If you installed it in inetd.conf then you probably edited that file incorrectly. If you installed it as a daemon then check that it is running, and check that the netbios-ssn port is in a LISTEN -state using netstat -a.

      If you get a "session request failed" then the server refused the -connection. If it says "Your server software is being unfriendly" then -its probably because you have invalid command line parameters to smbd, -or a similar fatal problem with the initial startup of smbd. Also -check your config file (smb.conf) for syntax errors with testparm +state using netstat -a. +

      Note

      +Some Unix / Linux systems use xinetd in place of +inetd. Check your system documentation for the location +of the control file/s for your particular system implementation of +this network super daemon. +

      +If you get a "session request failed" then the server refused the +connection. If it says "Your server software is being unfriendly" then +its probably because you have invalid command line parameters to smbd, +or a similar fatal problem with the initial startup of smbd. Also +check your config file (smb.conf) for syntax errors with testparm and that the various directories where samba keeps its log and lock -files exist.

      There are a number of reasons for which smbd may refuse or decline +files exist. +

      +There are a number of reasons for which smbd may refuse or decline a session request. The most common of these involve one or more of -the following smb.conf file entries:

      	hosts deny = ALL
+the following smb.conf file entries:
+
      +	hosts deny = ALL
 	hosts allow = xxx.xxx.xxx.xxx/yy
-	bind interfaces only = Yes
      In the above, no allowance has been made for any session requests that
+	bind interfaces only = Yes
+

      +In the above, no allowance has been made for any session requests that will automatically translate to the loopback adaptor address 127.0.0.1. -To solve this problem change these lines to:

      	hosts deny = ALL
-	hosts allow = xxx.xxx.xxx.xxx/yy 127.

      Do NOT use the bind interfaces only parameter where you +To solve this problem change these lines to: +

      +	hosts deny = ALL
+	hosts allow = xxx.xxx.xxx.xxx/yy 127.
+

      +Do NOT use the bind interfaces only parameter where you may wish to -use the samba password change facility, or where smbclient may need to -access local service for name resolution or for local resource -connections. (Note: the bind interfaces only parameter deficiency +use the samba password change facility, or where smbclient may need to +access a local service for name resolution or for local resource +connections. (Note: the bind interfaces only parameter deficiency where it will not allow connections to the loopback address will be -fixed soon).

      Another common cause of these two errors is having something already running -on port 139, such as Samba (ie: smbd is running from inetd already) or -something like Digital's Pathworks. Check your inetd.conf file before trying -to start smbd as a daemon, it can avoid a lot of frustration!

      And yet another possible cause for failure of this test is when the subnet mask +fixed soon). +

      +Another common cause of these two errors is having something already running +on port 139, such as Samba (ie: smbd is running from inetd already) or +something like Digital's Pathworks. Check your inetd.conf file before trying +to start smbd as a daemon, it can avoid a lot of frustration! +

      +And yet another possible cause for failure of this test is when the subnet mask and / or broadcast address settings are incorrect. Please check that the network interface IP Address / Broadcast Address / Subnet Mask settings are -correct and that Samba has correctly noted these in the log.nmb file.

    5. Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the -IP address of your Samba server back.

      If you don't then nmbd is incorrectly installed. Check your inetd.conf +correct and that Samba has correctly noted these in the log.nmb file. +

    6. +Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the +IP address of your Samba server back. +

      +If you don't then nmbd is incorrectly installed. Check your inetd.conf if you run it from there, or that the daemon is running and listening -to udp port 137.

      One common problem is that many inetd implementations can't take many +to udp port 137. +

      +One common problem is that many inetd implementations can't take many parameters on the command line. If this is the case then create a one-line script that contains the right parameters and run that from -inetd.

    7. run the command nmblookup -B ACLIENT '*'

      You should get the PCs IP address back. If you don't then the client +inetd. +

    8. run the command nmblookup -B ACLIENT '*'

      +You should get the PCs IP address back. If you don't then the client software on the PC isn't installed correctly, or isn't started, or you -got the name of the PC wrong.

      If ACLIENT doesn't resolve via DNS then use the IP address of the -client in the above test.

    9. Run the command nmblookup -d 2 '*'

      This time we are trying the same as the previous test but are trying +got the name of the PC wrong. +

      +If ACLIENT doesn't resolve via DNS then use the IP address of the +client in the above test. +

    10. +Run the command nmblookup -d 2 '*' +

      +This time we are trying the same as the previous test but are trying it via a broadcast to the default broadcast address. A number of Netbios/TCPIP hosts on the network should respond, although Samba may not catch all of the responses in the short time it listens. You -should see "got a positive name query response" messages from several -hosts.

      If this doesn't give a similar result to the previous test then +should see "got a positive name query response" messages from several +hosts. +

      +If this doesn't give a similar result to the previous test then nmblookup isn't correctly getting your broadcast address through its -automatic mechanism. In this case you should experiment use the -interfaces option in smb.conf to manually configure your IP -address, broadcast and netmask.

      If your PC and server aren't on the same subnet then you will need to -use the -B option to set the broadcast address to the that of the PCs -subnet.

      This test will probably fail if your subnet mask and broadcast address are -not correct. (Refer to TEST 3 notes above).

    11. Run the command smbclient //BIGSERVER/TMP. You should +automatic mechanism. In this case you should experiment with the +interfaces option in smb.conf to manually configure your IP +address, broadcast and netmask. +

      +If your PC and server aren't on the same subnet then you will need to +use the -B option to set the broadcast address to that of the PCs +subnet. +

      +This test will probably fail if your subnet mask and broadcast address are +not correct. (Refer to TEST 3 notes above). +

    12. +Run the command smbclient //BIGSERVER/TMP. You should then be prompted for a password. You should use the password of the account you are logged into the unix box with. If you want to test with -another account then add the -U accountname option to the end of +another account then add the -U accountname option to the end of the command line. eg: -smbclient //bigserver/tmp -Ujohndoe

      It is possible to specify the password along with the username +smbclient //bigserver/tmp -Ujohndoe +

      Note

      +It is possible to specify the password along with the username as follows: -smbclient //bigserver/tmp -Ujohndoe%secret

      Once you enter the password you should get the smb> prompt. If you -don't then look at the error message. If it says "invalid network -name" then the service "tmp" is not correctly setup in your smb.conf.

      If it says "bad password" then the likely causes are:

      1. you have shadow passords (or some other password system) but didn't - compile in support for them in smbd -

      2. your valid users configuration is incorrect -

      3. you have a mixed case password and you haven't enabled the password - level option at a high enough level -

      4. the path = line in smb.conf is incorrect. Check it with testparm -

      5. you enabled password encryption but didn't create the SMB encrypted +smbclient //bigserver/tmp -Ujohndoe%secret +

    +Once you enter the password you should get the smb> prompt. If you +don't then look at the error message. If it says "invalid network +name" then the service "tmp" is not correctly setup in your smb.conf. +

    +If it says "bad password" then the likely causes are: +

    1. + you have shadow passords (or some other password system) but didn't + compile in support for them in smbd +

    2. + your valid users configuration is incorrect +

    3. + you have a mixed case password and you haven't enabled the password + level option at a high enough level +

    4. + the path = line in smb.conf is incorrect. Check it with testparm +

    5. + you enabled password encryption but didn't create the SMB encrypted password file -

    Once connected you should be able to use the commands -dir get put etc. -Type help command for instructions. You should +

    +Once connected you should be able to use the commands +dir get put etc. +Type help command for instructions. You should especially check that the amount of free disk space shown is correct -when you type dir.

  • On the PC type the command net view \\BIGSERVER. You will -need to do this from within a "dos prompt" window. You should get back a -list of available shares on the server.

    If you get a "network name not found" or similar error then netbios +when you type dir. +

  • +On the PC, type the command net view \\BIGSERVER. You will +need to do this from within a "dos prompt" window. You should get back a +list of available shares on the server. +

    +If you get a "network name not found" or similar error then netbios name resolution is not working. This is usually caused by a problem in nmbd. To overcome it you could do one of the following (you only need -to choose one of them):

    1. fixup the nmbd installation

    2. add the IP address of BIGSERVER to the wins server box in the - advanced tcp/ip setup on the PC.

    3. enable windows name resolution via DNS in the advanced section of - the tcp/ip setup

    4. add BIGSERVER to your lmhosts file on the PC.

    If you get a "invalid network name" or "bad password error" then the -same fixes apply as they did for the smbclient -L test above. In -particular, make sure your hosts allow line is correct (see the man -pages)

    Also, do not overlook that fact that when the workstation requests the +to choose one of them): +

    1. + fixup the nmbd installation +

    2. + add the IP address of BIGSERVER to the wins server box in the + advanced tcp/ip setup on the PC. +

    3. + enable windows name resolution via DNS in the advanced section of + the tcp/ip setup +

    4. + add BIGSERVER to your lmhosts file on the PC. +

    +If you get a "invalid network name" or "bad password error" then the +same fixes apply as they did for the smbclient -L test above. In +particular, make sure your hosts allow line is correct (see the man +pages) +

    +Also, do not overlook that fact that when the workstation requests the connection to the samba server it will attempt to connect using the name with which you logged onto your Windows machine. You need to make sure that an account exists on your Samba server with that exact same -name and password.

    If you get "specified computer is not receiving requests" or similar +name and password. +

    +If you get "specified computer is not receiving requests" or similar it probably means that the host is not contactable via tcp services. Check to see if the host is running tcp wrappers, and if so add an entry in -the hosts.allow file for your client (or subnet, etc.)

  • Run the command net use x: \\BIGSERVER\TMP. You should -be prompted for a password then you should get a "command completed -successfully" message. If not then your PC software is incorrectly -installed or your smb.conf is incorrect. make sure your hosts allow -and other config lines in smb.conf are correct.

    It's also possible that the server can't work out what user name to -connect you as. To see if this is the problem add the line user = -username to the [tmp] section of -smb.conf where username is the +the hosts.allow file for your client (or subnet, etc.) +

  • +Run the command net use x: \\BIGSERVER\TMP. You should +be prompted for a password then you should get a "command completed +successfully" message. If not then your PC software is incorrectly +installed or your smb.conf is incorrect. make sure your hosts allow +and other config lines in smb.conf are correct. +

    +It's also possible that the server can't work out what user name to +connect you as. To see if this is the problem add the line user = +username to the [tmp] section of +smb.conf where username is the username corresponding to the password you typed. If you find this -fixes things you may need the username mapping option.

    It might also be the case that your client only sends encrypted passwords -and you have encrypt passwords = no in smb.conf -Turn it back on to fix.

  • Run the command nmblookup -M testgroup where -testgroup is the name of the workgroup that your Samba server and +fixes things you may need the username mapping option. +

    +It might also be the case that your client only sends encrypted passwords +and you have encrypt passwords = no in smb.conf +Turn it back on to fix. +

  • +Run the command nmblookup -M testgroup where +testgroup is the name of the workgroup that your Samba server and Windows PCs belong to. You should get back the IP address of the -master browser for that workgroup.

    If you don't then the election process has failed. Wait a minute to +master browser for that workgroup. +

    +If you don't then the election process has failed. Wait a minute to see if it is just being slow then try again. If it still fails after -that then look at the browsing options you have set in smb.conf. Make -sure you have preferred master = yes to ensure that -an election is held at startup.

  • From file manager try to browse the server. Your samba server should +that then look at the browsing options you have set in smb.conf. Make +sure you have preferred master = yes to ensure that +an election is held at startup. +

  • +>From file manager try to browse the server. Your samba server should appear in the browse list of your local workgroup (or the one you specified in smb.conf). You should be able to double click on the name -of the server and get a list of shares. If you get a "invalid -password" error when you do then you are probably running WinNT and it +of the server and get a list of shares. If you get a "invalid +password" error when you do then you are probably running WinNT and it is refusing to browse a server that has no encrypted password capability and is in user level security mode. In this case either set -security = server AND -password server = Windows_NT_Machine in your -smb.conf file, or make sure encrypted passwords is -set to "yes".

    • PrevHomeNext
    Samba performance issuesUpAnalysing and solving samba problems
    \ No newline at end of file +security = server AND +password server = Windows_NT_Machine in your +smb.conf file, or make sure encrypted passwords is +set to "yes". +

    Still having troubles?

    Read the chapter on +Analysing and Solving Problems. +

    PrevUpNext
    PartIV.TroubleshootingHomeChapter28.Analysing and solving samba problems
    diff --git a/docs/htmldocs/domain-member.html b/docs/htmldocs/domain-member.html index 9d70524a42..5be675a541 100644 --- a/docs/htmldocs/domain-member.html +++ b/docs/htmldocs/domain-member.html @@ -1,446 +1,79 @@ - -Samba as a NT4 or Win2k domain member
    SAMBA Project Documentation
    PrevNext

    Chapter 10. Samba as a NT4 or Win2k domain member

    10.1. Joining an NT Domain with Samba 3.0

    Assume you have a Samba 3.0 server with a NetBIOS name of - SERV1 and are joining an or Win2k NT domain called - DOM, which has a PDC with a NetBIOS name - of DOMPDC and two backup domain controllers - with NetBIOS names DOMBDC1 and DOMBDC2 - .

    Firstly, you must edit your smb.conf file to tell Samba it should - now use domain security.

    Change (or add) your security = line in the [global] section - of your smb.conf to read:

    security = domain

    Next change the workgroup = line in the [global] section to read:

    workgroup = DOM

    as this is the name of the domain we are joining.

    You must also have the parameter encrypt passwords set to yes - in order for your users to authenticate to the NT PDC.

    Finally, add (or modify) a password server = line in the [global] - section to read:

    password server = DOMPDC DOMBDC1 DOMBDC2

    These are the primary and backup domain controllers Samba + +Chapter8.Samba as a NT4 or Win2k domain member

    Chapter8.Samba as a NT4 or Win2k domain member
    PrevPartII.Server Configuration BasicsNext

    Chapter8.Samba as a NT4 or Win2k domain member

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    16 Apr 2001

    Table of Contents

    Joining an NT Domain with Samba 3.0
    Why is this better than security = server?

    Joining an NT Domain with Samba 3.0

    Assumptions: + 

    +		NetBIOS name: SERV1
+		Win2K/NT domain name: DOM
+		Domain's PDC NetBIOS name: DOMPDC
+		Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
+

    +

    First, you must edit your smb.conf file to tell Samba it should + now use domain security.

    Change (or add) your + security = line in the [global] section + of your smb.conf to read:

    security = domain

    Next change the + workgroup = line in the [global] section to read:

    workgroup = DOM

    as this is the name of the domain we are joining.

    You must also have the parameter + encrypt passwords set to yes + in order for your users to authenticate to the NT PDC.

    Finally, add (or modify) a + password server = line in the [global] + section to read:

    password server = DOMPDC DOMBDC1 DOMBDC2

    These are the primary and backup domain controllers Samba will attempt to contact in order to authenticate users. Samba will try to contact each of these servers in order, so you may want to rearrange this list in order to spread out the authentication load - among domain controllers.

    Alternatively, if you want smbd to automatically determine + among domain controllers.

    Alternatively, if you want smbd to automatically determine the list of Domain controllers to use for authentication, you may - set this line to be :

    password server = *

    This method, allows Samba to use exactly the same + set this line to be :

    password server = *

    This method, allows Samba to use exactly the same mechanism that NT does. This method either broadcasts or uses a WINS database in order to - find domain controllers to authenticate against.

    In order to actually join the domain, you must run this - command:

    root# net rpc join -S DOMPDC - -UAdministrator%password

    as we are joining the domain DOM and the PDC for that domain + find domain controllers to authenticate against.

    In order to actually join the domain, you must run this + command:

    root# net join -S DOMPDC + -UAdministrator%password

    + If the -S DOMPDC argument is not given then + the domain name will be obtained from smb.conf. +

    as we are joining the domain DOM and the PDC for that domain (the only machine that has write access to the domain SAM database) - is DOMPDC. The Administrator%password is + is DOMPDC. The Administrator%password is the login name and password for an account which has the necessary privilege to add machines to the domain. If this is successful - you will see the message:

    Joined domain DOM. - or Joined 'SERV1' to realm 'MYREALM' -

    in your terminal window. See the net(8) man page for more details.

    This process joins the server to thedomain + you will see the message:

    Joined domain DOM. + or Joined 'SERV1' to realm 'MYREALM' +

    in your terminal window. See the + net(8) man page for more details.

    This process joins the server to the domain without having to create the machine trust account on the PDC - beforehand.

    This command goes through the machine account password + beforehand.

    This command goes through the machine account password change protocol, then writes the new (random) machine account password for this Samba server into a file in the same directory - in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private/secrets.tdb

    This file is created and owned by root and is not + in which an smbpasswd file would be stored - normally :

    /usr/local/samba/private/secrets.tdb

    This file is created and owned by root and is not readable by any other user. It is the key to the domain-level security for your system, and should be treated as carefully - as a shadow password file.

    Finally, restart your Samba daemons and get ready for - clients to begin using domain security!

    10.2. Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from + as a shadow password file.

    Finally, restart your Samba daemons and get ready for + clients to begin using domain security!

    Why is this better than security = server?

    Currently, domain security in Samba doesn't free you from having to create local Unix users to represent the users attaching - to your server. This means that if domain user DOM\fred - attaches to your domain security Samba server, there needs + to your server. This means that if domain user DOM\fred + attaches to your domain security Samba server, there needs to be a local Unix user fred to represent that user in the Unix filesystem. This is very similar to the older Samba security mode - security = server, + security = server, where Samba would pass through the authentication request to a Windows NT server in the same way as a Windows 95 or Windows 98 server would. -

    Please refer to the Winbind - paper for information on a system to automatically +

    Please refer to the Winbind + paper for information on a system to automatically assign UNIX uids and gids to Windows NT Domain users and groups. - This code is available in development branches only at the moment, - but will be moved to release branches soon.

    The advantage to domain-level security is that the +

    The advantage to domain-level security is that the authentication in domain-level security is passed down the authenticated RPC channel in exactly the same way that an NT server would do it. This means Samba servers now participate in domain trust relationships in exactly the same way NT servers do (i.e., you can add Samba servers into a resource domain and have the authentication passed on from a resource - domain PDC to an account domain PDC.

    In addition, with security = server every Samba + domain PDC to an account domain PDC).

    In addition, with security = server every Samba daemon on a server has to keep a connection open to the authenticating server for as long as that daemon lasts. This can drain the connection resources on a Microsoft NT server and cause it to run - out of available connections. With security = domain, + out of available connections. With security = domain, however, the Samba daemons connect to the PDC/BDC only for as long as is necessary to authenticate the user, and then drop the connection, - thus conserving PDC connection resources.

    And finally, acting in the same manner as an NT server + thus conserving PDC connection resources.

    And finally, acting in the same manner as an NT server authenticating to a PDC means that as part of the authentication reply, the Samba server gets the user identification information such - as the user SID, the list of NT groups the user belongs to, etc.

    Much of the text of this document - was first published in the Web magazine - LinuxWorld as the article Doing - the NIS/NT Samba.

    PrevHomeNext
    Samba as a ADS domain memberUpAdvanced Configuration
    \ No newline at end of file + as the user SID, the list of NT groups the user belongs to, etc.

    Note

    Much of the text of this document + was first published in the Web magazine + LinuxWorld as the article Doing + the NIS/NT Samba.

    PrevUpNext
    Chapter7.Samba as a ADS domain memberHomePartIII.Advanced Configuration
    diff --git a/docs/htmldocs/editreg.1.html b/docs/htmldocs/editreg.1.html index 571e50560c..c5a86ee960 100644 --- a/docs/htmldocs/editreg.1.html +++ b/docs/htmldocs/editreg.1.html @@ -1,142 +1,12 @@ - -editreg

    editreg

    Name

    editreg -- A utility to report and change SIDs in registry files -

    Synopsis

    editreg [-v] [-c file] {file}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    editreg is a utility that +editreg

    Name

    editreg — A utility to report and change SIDs in registry files +

    Synopsis

    editreg [-v] [-c file] {file}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    editreg is a utility that can visualize windows registry files (currently only NT4) and apply so-called commandfiles to them. -

    OPTIONS

    registry_file

    Registry file to view or edit.

    -v,--verbose

    Increases verbosity of messages. -

    -c commandfile

    Read commands to execute on registry_file from commandfile. Currently not yet supported! -

    -h|--help

    Print a summary of command line options.

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +

    OPTIONS

    registry_file

    Registry file to view or edit.

    -v,--verbose

    Increases verbosity of messages. +

    -c commandfile

    Read commands to execute on registry_file from commandfile. Currently not yet supported! +

    -h|--help

    Print a summary of command line options. +

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The editreg man page was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The editreg man page was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/findsmb.1.html b/docs/htmldocs/findsmb.1.html index 34b63f4fe1..878c3d78fe 100644 --- a/docs/htmldocs/findsmb.1.html +++ b/docs/htmldocs/findsmb.1.html @@ -1,295 +1,61 @@ - -findsmb

    findsmb

    Name

    findsmb -- list info about machines that respond to SMB - name queries on a subnet

    Synopsis

    findsmb [subnet broadcast address]

    DESCRIPTION

    This perl script is part of the Samba(7) - suite.

    findsmb is a perl script that +findsmb

    Name

    findsmb — list info about machines that respond to SMB + name queries on a subnet

    Synopsis

    findsmb [subnet broadcast address]

    DESCRIPTION

    This perl script is part of the Samba(7) + suite.

    findsmb is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests. - It uses nmblookup(1) - and smbclient(1) + It uses nmblookup(1) + and smbclient(1) to obtain this information. -

    OPTIONS

    -r

    Controls whether findsmb takes +

    OPTIONS

    -r

    Controls whether findsmb takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only. - If set, nmblookup(1) - will be called with -B option.

    subnet broadcast address

    Without this option, findsmb - will probe the subnet of the machine where - findsmb(1) + If set, nmblookup(1) + will be called with -B option.

    subnet broadcast address

    Without this option, findsmb + will probe the subnet of the machine where + findsmb(1) is run. This value is passed to - nmblookup(1) - as part of the -B option.

    EXAMPLES

    The output of findsmb lists the following + nmblookup(1) + as part of the -B option.

    EXAMPLES

    The output of findsmb lists the following information for all machines that respond to the initial - nmblookup for any name: IP address, NetBIOS name, - Workgroup name, operating system, and SMB server version.

    There will be a '+' in front of the workgroup name for + nmblookup for any name: IP address, NetBIOS name, + Workgroup name, operating system, and SMB server version.

    There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup. There will be an '*' in front of the workgroup name for machines that are the domain master browser for that workgroup. Machines that are running Windows, Windows 95 or Windows 98 will not show any information about the operating system or server - version.

    The command with -r option - must be run on a system without nmbd(8) running. + version.

    The command with -r option + must be run on a system without nmbd(8) running. - If nmbd is running on the system, you will + If nmbd is running on the system, you will only get the IP address and the DNS name of the machine. To get proper responses from Windows 95 and Windows 98 machines, - the command must be run as root and with -r - option on a machine without nmbd running.

    For example, running findsmb - without -r option set would yield output similar - to the following

        IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
-    --------------------------------------------------------------------- 
-    192.168.35.10   MINESET-TEST1  [DMVENGR]
-    192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
-  5 192.168.35.56   HERBNT2        [HERB-NT]
-    192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
-    192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
-    192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
-    192.168.35.78   HERBDHCP1     +[HERB]
- 10 192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
-    192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
-    192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    nmbd(8), - smbclient(1), and nmblookup(1) -

    AUTHOR

    The original Samba software and related utilities + the command must be run as root and with -r + option on a machine without nmbd running.

    For example, running findsmb + without -r option set would yield output similar + to the following

    +IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
+--------------------------------------------------------------------- 
+192.168.35.10   MINESET-TEST1  [DMVENGR]
+192.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
+192.168.35.56   HERBNT2        [HERB-NT]
+192.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
+192.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
+192.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
+192.168.35.78   HERBDHCP1     +[HERB]
+192.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
+192.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
+192.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
+

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    nmbd(8), + smbclient(1), and nmblookup(1) +

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) + excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/groupmapping.html b/docs/htmldocs/groupmapping.html index f594ceca02..704b799631 100644 --- a/docs/htmldocs/groupmapping.html +++ b/docs/htmldocs/groupmapping.html @@ -1,236 +1,53 @@ - -Configuring Group Mapping
    SAMBA Project Documentation
    PrevNext

    Chapter 12. Configuring Group Mapping

    -Starting with Samba 3.0 alpha 2, a new group mapping function is available. The -current method (likely to change) to manage the groups is a new command called -smbgroupedit.

    The first immediate reason to use the group mapping on a PDC, is that -the domain admin group of smb.conf is -now gone. This parameter was used to give the listed users local admin rights -on their workstations. It was some magic stuff that simply worked but didn't -scale very well for complex setups.

    Let me explain how it works on NT/W2K, to have this magic fade away. + +Chapter12.Configuring Group Mapping

    Chapter12.Configuring Group Mapping
    PrevPartIII.Advanced ConfigurationNext

    Chapter12.Configuring Group Mapping

    Jean Franois Micouleau

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    +Starting with Samba 3.0 alpha 2, new group mapping functionality +is available to create associations between Windows SIDs and UNIX +groups. The groupmap subcommand included with +the net tool can be used to manage these associations. +

    +The first immediate reason to use the group mapping on a Samba PDC, is that +the domain admin group smb.conf has been removed. +This parameter was used to give the listed users membership in the "Domain Admins" +Windows group which gave local admin rights on their workstations (in +default configurations). +

    When installing NT/W2K on a computer, the installer program creates some users and groups. Notably the 'Administrators' group, and gives to that group some privileges like the ability to change the date and time or to kill any process (or close too) running on the local machine. The 'Administrator' user is a member of the 'Administrators' group, and thus 'inherit' the 'Administrators' group privileges. If a 'joe' user is created and become a member of the -'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.

    When a NT/W2K machine is joined to a domain, during that phase, the "Domain -Administrators' group of the PDC is added to the 'Administrators' group of the -workstation. Every members of the 'Domain Administrators' group 'inherit' the -rights of the 'Administrators' group when logging on the workstation.

    You are now wondering how to make some of your samba PDC users members of the -'Domain Administrators' ? That's really easy.

    1. create a unix group (usually in /etc/group), let's call it domadm

    2. add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in /etc/group will look like:

      domadm:x:502:joe,john,mary

    3. Map this domadm group to the domain admins group by running the command:

      smbgroupedit -c "Domain Admins" -u domadm

    You're set, joe, john and mary are domain administrators !

    Like the Domain Admins group, you can map any arbitrary Unix group to any NT -group. You can also make any Unix group a domain group. For example, on a domain -member machine (an NT/W2K or a samba server running winbind), you would like to -give access to a certain directory to some users who are member of a group on -your samba PDC. Flag that group as a domain group by running:

    smbgroupedit -a unixgroup -td

    You can list the various groups in the mapping database like this

    smbgroupedit -v

    PrevHomeNext
    UNIX Permission Bits and Windows NT Access Control ListsUpPrinting Support
    \ No newline at end of file +'Administrator' group, 'joe' has exactly the same rights as 'Administrator'. +

    +When a NT/W2K machine is joined to a domain, the "Domain Adminis" group of the +PDC is added to the local 'Administrators' group of the workstation. Every +member of the 'Domain Administrators' group 'inherit' the +rights of the local 'Administrators' group when logging on the workstation. +

    +The following steps describe how to make samba PDC users members of the +'Domain Admins' group? +

    1. create a unix group (usually in /etc/group), + let's call it domadm

    2. add to this group the users that must be Administrators. For example + if you want joe,john and mary, your entry in /etc/group will + look like:

      +  domadm:x:502:joe,john,mary
+

    3. Map this domadm group to the "Domain Admins" group + by running the command:

      root# net groupmap add ntgroup="Domain Admins" unixgroup=domadm

      The quotes around "Domain Admins" are necessary due to the space in the group name. Also make + sure to leave no whitespace surrounding the equal character (=).

    Now joe, john and mary are domain administrators!

    +It is possible to map any arbitrary UNIX group to any Windows NT +group as well as making any UNIX group a Windows domain group. +For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a +local file or printer on a domain member machine, you would flag +that group as a domain group by running the following on the Samba PDC: +

    root# net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct

    Be aware that the rid parmeter is a unsigned 32 bit integer that should +normally start at 1000. However, this rid must not overlap with any RID assigned +to a user. Verifying this is done differently depending on on the passdb backend +you are using. Future versions of the tools may perform the verification automatically, +but for now the burden in on you.

    You can list the various groups in the mapping database by executing +net groupmap list. Here is an example:

    root# net groupmap list
+System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
+Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
+Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
+Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
+

    For complete details on net groupmap, refer to the +net(8) man page.

    PrevUpNext
    Chapter11.UNIX Permission Bits and Windows NT Access Control ListsHomeChapter13.Printing Support
    diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index cf6bf1f199..1c107c0019 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -1,629 +1,75 @@ - -How to Install and Test SAMBA
    SAMBA Project Documentation
    PrevNext

    Chapter 2. How to Install and Test SAMBA

    2.1. Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or + +Chapter2.How to Install and Test SAMBA

    Chapter2.How to Install and Test SAMBA
    PrevPartI.General InstallationNext

    Chapter2.How to Install and Test SAMBA

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Karl Auer

    Table of Contents

    Obtaining and installing samba
    Configuring samba
    Editing the smb.conf file
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client
    What If Things Don't Work?

    Obtaining and installing samba

    Binary packages of samba are included in almost any Linux or Unix distribution. There are also some packages available at - the samba homepage. -

    If you need to compile samba from source, check the - appropriate appendix chapter.

    2.2. Configuring samba

    Samba's configuration is stored in the smb.conf file, - that usually resides in /etc/samba/smb.conf - or /usr/local/samba/lib/smb.conf. You can either + the samba homepage. +

    If you need to compile samba from source, check the + appropriate appendix chapter.

    Configuring samba

    Samba's configuration is stored in the smb.conf file, + that usually resides in /etc/samba/smb.conf + or /usr/local/samba/lib/smb.conf. You can either edit this file yourself or do it using one of the many graphical tools that are available, such as the web-based interface swat, that - is included with samba.

    2.2.1. Editing the smb.conf file

    There are sample configuration files in the examples + is included with samba.

    Editing the smb.conf file

    There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them carefully so you can see how the options go together in - practice. See the man page for all the options.

    The simplest useful configuration file would be - something like this:

    [global]
+	practice. See the man page for all the options.
    The simplest useful configuration file would be 
+	something like this:
    +[global]
 	workgroup = MYGROUP
 
 [homes]
 	guest ok = no
 	read only = no
-	
    which would allow connections by anyone with an 
+

    which would allow connections by anyone with an account on the server, using either their login name or - "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for details)

    Make sure you put the smb.conf file in the same place - you specified in theMakefile (the default is to - look for it in /usr/local/samba/lib/).

    For more information about security settings for the - [homes] share please refer to the chapter - Securing Samba.

    2.2.1.1. Test your config file with - testparm

    It's important that you test the validity of your - smb.conf file using the testparm program. + "homes" as the service name. (Note that I also set the + workgroup that Samba is part of. See BROWSING.txt for details)

    Make sure you put the smb.conf file in the same place + you specified in theMakefile (the default is to + look for it in /usr/local/samba/lib/).

    For more information about security settings for the + [homes] share please refer to the chapter + Securing Samba.

    Test your config file with + testparm

    It's important that you test the validity of your + smb.conf file using the testparm program. If testparm runs OK then it will list the loaded services. If - not it will give an error message.

    Make sure it runs OK and that the services look - reasonable before proceeding.

    Always run testparm again when you change - smb.conf!

    2.2.2. SWAT

    SWAT is a web-based interface that helps you configure samba. + not it will give an error message.

    Make sure it runs OK and that the services look + reasonable before proceeding.

    Always run testparm again when you change + smb.conf!

    SWAT

    + SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage + but in a separate package. Please read the swat manpage on compiling, installing and configuring swat from source. -

    To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you - are running samba on a different computer then your browser.

    Note that you can attach to SWAT from any IP connected +

    To launch SWAT just run your favorite web browser and + point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you + are running samba on a different computer than your browser.

    Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent - in the clear over the wire.

    2.3. Try listing the shares available on your - server

    $ smbclient -L - yourhostname

    You should get back a list of shares available on + in the clear over the wire.

    Try listing the shares available on your + server

    $ smbclient -L + yourhostname

    You should get back a list of shares available on your server. If you don't then something is incorrectly setup. Note that this method can also be used to see what shares - are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find + are available on other LanManager clients (such as WfWg).

    If you choose user level security then you may find that Samba requests a password before it will list the shares. - See the smbclient man page for details. (you + See the smbclient man page for details. (you can force it to list the shares without a password by adding the option -U% to the command line. This will not work - with non-Samba servers)

    2.4. Try connecting with the unix client

    $ smbclient //yourhostname/aservice

    Typically the yourhostname - would be the name of the host where you installed smbd. - The aservice is - any service you have defined in the smb.conf - file. Try your user name if you just have a [homes] + with non-Samba servers)

    Try connecting with the unix client

    $ smbclient + //yourhostname/aservice

    Typically the yourhostname + would be the name of the host where you installed smbd. + The aservice is + any service you have defined in the smb.conf + file. Try your user name if you just have a [homes] section - in smb.conf.

    For example if your unix host is bambi - and your login name is fred you would type:

    $ smbclient //bambi/fred -

    2.5. Try connecting from a DOS, WfWg, Win9x, WinNT, - Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service -

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: - \\servername\spoolservice

    C:\WINDOWS\> print filename -

    2.6. What If Things Don't Work?

    Then you might read the file chapter - Diagnosis and the + in smb.conf.

    For example if your unix host is bambi + and your login name is fred you would type:

    $ smbclient //bambi/fred +

    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client

    Try mounting disks. eg:

    C:\WINDOWS\> net use d: \\servername\service +

    Try printing. eg:

    C:\WINDOWS\> net use lpt1: + \\servername\spoolservice

    C:\WINDOWS\> print filename +

    What If Things Don't Work?

    Then you might read the file chapter + Diagnosis and the FAQ. If you are still stuck then try to follow - the Analysing and Solving Problems chapter + the Analysing and Solving Problems chapter Samba has been successfully installed at thousands of sites worldwide, - so maybe someone else has hit your problem and has overcome it.

    2.6.1. Scope IDs

    By default Samba uses a blank scope ID. This means - all your windows boxes must also have a blank scope ID. - If you really want to use a non-blank scope ID then you will - need to use the 'netbios scope' smb.conf option. - All your PCs will need to have the same setting for - this to work. I do not recommend scope IDs.

    2.6.2. Locking

    One area which sometimes causes trouble is locking.

    There are two types of locking which need to be - performed by a SMB server. The first is "record locking" - which allows a client to lock a range of bytes in a open file. - The second is the "deny modes" that are specified when a file - is open.

    Record locking semantics under Unix is very - different from record locking under Windows. Versions - of Samba before 2.2 have tried to use the native - fcntl() unix system call to implement proper record - locking between different Samba clients. This can not - be fully correct due to several reasons. The simplest - is the fact that a Windows client is allowed to lock a - byte range up to 2^32 or 2^64, depending on the client - OS. The unix locking only supports byte ranges up to - 2^31. So it is not possible to correctly satisfy a - lock request above 2^31. There are many more - differences, too many to be listed here.

    Samba 2.2 and above implements record locking - completely independent of the underlying unix - system. If a byte range lock that the client requests - happens to fall into the range 0-2^31, Samba hands - this request down to the Unix system. All other locks - can not be seen by unix anyway.

    Strictly a SMB server should check for locks before - every read and write call on a file. Unfortunately with the - way fcntl() works this can be slow and may overstress the - rpc.lockd. It is also almost always unnecessary as clients - are supposed to independently make locking calls before reads - and writes anyway if locking is important to them. By default - Samba only makes locking calls when explicitly asked - to by a client, but if you set "strict locking = yes" then it will - make lock checking calls on every read and write.

    You can also disable by range locking completely - using "locking = no". This is useful for those shares that - don't support locking or don't need it (such as cdroms). In - this case Samba fakes the return codes of locking calls to - tell clients that everything is OK.

    The second class of locking is the "deny modes". These - are set by an application when it opens a file to determine - what types of access should be allowed simultaneously with - its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatibility modes called - DENY_FCB and DENY_DOS.

    PrevHomeNext
    Introduction to SambaUpQuick Cross Subnet Browsing / Cross Workgroup Browsing guide
    \ No newline at end of file + so maybe someone else has hit your problem and has overcome it.

    PrevUpNext
    Chapter1.Introduction to SambaHomePartII.Server Configuration Basics
    diff --git a/docs/htmldocs/integrate-ms-networks.html b/docs/htmldocs/integrate-ms-networks.html index cacd20a152..70f446e09d 100644 --- a/docs/htmldocs/integrate-ms-networks.html +++ b/docs/htmldocs/integrate-ms-networks.html @@ -1,320 +1,55 @@ - -Integrating MS Windows networks with Samba
    SAMBA Project Documentation
    PrevNext

    Chapter 23. Integrating MS Windows networks with Samba

    This section deals with NetBIOS over TCP/IP name to IP address resolution. If you + +Chapter23.Integrating MS Windows networks with Samba

    Chapter23.Integrating MS Windows networks with Samba
    PrevPartIII.Advanced ConfigurationNext

    Chapter23.Integrating MS Windows networks with Samba

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    (Jan 01 2001)

    Table of Contents

    Name Resolution in a pure Unix/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup

    +This section deals with NetBIOS over TCP/IP name to IP address resolution. If your MS Windows clients are NOT configured to use NetBIOS over TCP/IP then this section does not apply to your installation. If your installation involves use of -NetBIOS over TCP/IP then this section may help you to resolve networking problems.

    NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS +NetBIOS over TCP/IP then this section may help you to resolve networking problems. +

    Note

    + NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS over Logical Link Control (LLC). On modern networks it is highly advised to NOT run NetBEUI at all. Note also that there is NO such thing as NetBEUI over TCP/IP - the existence of such a protocol is a complete - and utter mis-apprehension.

    Since the introduction of MS Windows 2000 it is possible to run MS Windows networking + and utter mis-apprehension. +

    +Since the introduction of MS Windows 2000 it is possible to run MS Windows networking without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over TCP/IP is disabled on MS Windows 2000 and later clients then only TCP port 445 will be -used and UDP port 137 and TCP port 139 will not.

    When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then +used and UDP port 137 and TCP port 139 will not. +

    Note

    +When using Windows 2000 or later clients, if NetBIOS over TCP/IP is NOT disabled, then the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet -Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic).

    When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that +Name Service or WINS), TCP port 139 AND TCP port 445 (for actual file and print traffic). +

    +When NetBIOS over TCP/IP is disabled the use of DNS is essential. Most installations that disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires Dynamic DNS with Service Resource Records (SRV RR) and with Incremental Zone Transfers (IXFR). Use of DHCP with ADS is recommended as a further means of maintaining central control -over client workstation network configuration.

    23.1. Name Resolution in a pure Unix/Linux world

    The key configuration files covered in this section are:

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    23.1.1. /etc/hosts

    Contains a static list of IP Addresses and names. -eg:

    	127.0.0.1	localhost localhost.localdomain
-	192.168.1.1	bigbox.caldera.com	bigbox	alias4box

    The purpose of /etc/hosts is to provide a +over client workstation network configuration. +

    Name Resolution in a pure Unix/Linux world

    +The key configuration files covered in this section are: +

    • /etc/hosts

    • /etc/resolv.conf

    • /etc/host.conf

    • /etc/nsswitch.conf

    /etc/hosts

    +Contains a static list of IP Addresses and names. +eg: +

    +	127.0.0.1	localhost localhost.localdomain
+	192.168.1.1	bigbox.caldera.com	bigbox	alias4box
+

    +The purpose of /etc/hosts is to provide a name resolution mechanism so that uses do not need to remember -IP addresses.

    Network packets that are sent over the physical network transport +IP addresses. +

    +Network packets that are sent over the physical network transport layer communicate not via IP addresses but rather using the Media Access Control address, or MAC address. IP Addresses are currently 32 bits in length and are typically presented as four (4) decimal -numbers that are separated by a dot (or period). eg: 168.192.1.1

    MAC Addresses use 48 bits (or 6 bytes) and are typically represented +numbers that are separated by a dot (or period). eg: 168.192.1.1 +

    +MAC Addresses use 48 bits (or 6 bytes) and are typically represented as two digit hexadecimal numbers separated by colons. eg: -40:8e:0a:12:34:56

    Every network interfrace must have an MAC address. Associated with +40:8e:0a:12:34:56 +

    +Every network interfrace must have an MAC address. Associated with a MAC address there may be one or more IP addresses. There is NO relationship between an IP address and a MAC address, all such assignments are arbitary or discretionary in nature. At the most basic level all @@ -323,18 +58,15 @@ addresses must be globally unique, and generally remains fixed for any particular interface, the assignment of an IP address makes sense from a network management perspective. More than one IP address can be assigned per MAC address. One address must be the primary IP address, -this is the address that will be returned in the ARP reply.

    When a user or a process wants to communicate with another machine -the protocol implementation ensures that the "machine name" or "host -name" is resolved to an IP address in a manner that is controlled +this is the address that will be returned in the ARP reply. +

    +When a user or a process wants to communicate with another machine +the protocol implementation ensures that the "machine name" or "host +name" is resolved to an IP address in a manner that is controlled by the TCP/IP configuration control files. The file -/etc/hosts is one such file.

    When the IP address of the destination interface has been +/etc/hosts is one such file. +

    +When the IP address of the destination interface has been determined a protocol called ARP/RARP is used to identify the MAC address of the target interface. ARP stands for Address Resolution Protocol, and is a broadcast oriented method that @@ -344,104 +76,41 @@ address. Network interfaces are programmed to respond to two MAC addresses only; their own unique address and the address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary IP address for each -interface.

    The /etc/hosts file is foundational to all +interface. +

    +The /etc/hosts file is foundational to all Unix/Linux TCP/IP installations and as a minumum will contain the localhost and local network interface IP addresses and the primary names by which they are known within the local machine. This file helps to prime the pump so that a basic level of name resolution can exist before any other method of name resolution -becomes available.

    23.1.2. /etc/resolv.conf

    This file tells the name resolution libraries:

    • The name of the domain to which the machine +becomes available. +

    /etc/resolv.conf

    +This file tells the name resolution libraries: +

    • The name of the domain to which the machine belongs -

    • The name(s) of any domains that should be +

    • The name(s) of any domains that should be automatically searched when trying to resolve unqualified host names to their IP address -

    • The name or IP address of available Domain +

    • The name or IP address of available Domain Name Servers that may be asked to perform name to address translation lookups -

    23.1.3. /etc/host.conf

    /etc/host.conf is the primary means by +

    /etc/host.conf

    +/etc/host.conf is the primary means by which the setting in /etc/resolv.conf may be affected. It is a critical configuration file. This file controls the order by -which name resolution may procede. The typical structure is:

    	order hosts,bind
-	multi on

    then both addresses should be returned. Please refer to the -man page for host.conf for further details.

    23.1.4. /etc/nsswitch.conf

    This file controls the actual name resolution targets. The -file typically has resolver object specifications as follows:

    	# /etc/nsswitch.conf
+which name resolution may procede. The typical structure is:
+
    +	order hosts,bind
+	multi on
+
    
+then both addresses should be returned. Please refer to the 
+man page for host.conf for further details.
+

    /etc/nsswitch.conf

    +This file controls the actual name resolution targets. The +file typically has resolver object specifications as follows: +

    +	# /etc/nsswitch.conf
 	#
 	# Name Service Switch configuration file.
 	#
@@ -460,101 +129,75 @@ CLASS="PROGRAMLISTING"
 	ethers:		nis files
 	protocols:	nis files
 	rpc:		nis files
-	services:	nis files

    Of course, each of these mechanisms requires that the appropriate -facilities and/or services are correctly configured.

    It should be noted that unless a network request/message must be + services: nis files +

    +Of course, each of these mechanisms requires that the appropriate +facilities and/or services are correctly configured. +

    +It should be noted that unless a network request/message must be sent, TCP/IP networks are silent. All TCP/IP communications assumes a -principal of speaking only when necessary.

    Starting with version 2.2.0 samba has Linux support for extensions to +principal of speaking only when necessary. +

    +Starting with version 2.2.0 samba has Linux support for extensions to the name service switch infrastructure so that linux clients will be able to obtain resolution of MS Windows NetBIOS names to IP Addresses. To gain this functionality Samba needs to be compiled -with appropriate arguments to the make command (ie: make -nsswitch/libnss_wins.so). The resulting library should -then be installed in the /lib directory and -the "wins" parameter needs to be added to the "hosts:" line in -the /etc/nsswitch.conf file. At this point it +with appropriate arguments to the make command (ie: make +nsswitch/libnss_wins.so). The resulting library should +then be installed in the /lib directory and +the "wins" parameter needs to be added to the "hosts:" line in +the /etc/nsswitch.conf file. At this point it will be possible to ping any MS Windows machine by it's NetBIOS machine name, so long as that machine is within the workgroup to -which both the samba machine and the MS Windows machine belong.

    23.2. Name resolution as used within MS Windows networking

    MS Windows networking is predicated about the name each machine +which both the samba machine and the MS Windows machine belong. +

    Name resolution as used within MS Windows networking

    +MS Windows networking is predicated about the name each machine is given. This name is known variously (and inconsistently) as -the "computer name", "machine name", "networking name", "netbios name", -"SMB name". All terms mean the same thing with the exception of -"netbios name" which can apply also to the name of the workgroup or the -domain name. The terms "workgroup" and "domain" are really just a +the "computer name", "machine name", "networking name", "netbios name", +"SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a simply name with which the machine is associated. All NetBIOS names are exactly 16 characters in length. The 16th character is reserved. It is used to store a one byte value that indicates service level information for the NetBIOS name that is registered. A NetBIOS machine name is therefore registered for each service type that is provided by -the client/server.

    The following are typical NetBIOS name/service type registrations:

    	Unique NetBIOS Names:
-		MACHINENAME<00>	= Server Service is running on MACHINENAME
-		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
-		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
-		WORKGROUP<1b> = Domain Master Browser
+the client/server.
+
    
+The following are typical NetBIOS name/service type registrations:
+
    +	Unique NetBIOS Names:
+		MACHINENAME<00>	= Server Service is running on MACHINENAME
+		MACHINENAME<03> = Generic Machine Name (NetBIOS name)
+		MACHINENAME<20> = LanMan Server service is running on MACHINENAME
+		WORKGROUP<1b> = Domain Master Browser
 
 	Group Names:
-		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
-		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
-		WORKGROUP<1d> = Local Master Browsers
-		WORKGROUP<1e> = Internet Name Resolvers
    It should be noted that all NetBIOS machines register their own 
+		WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
+		WORKGROUP<1c> = Domain Controllers / Netlogon Servers
+		WORKGROUP<1d> = Local Master Browsers
+		WORKGROUP<1e> = Internet Name Resolvers
+

    +It should be noted that all NetBIOS machines register their own names as per the above. This is in vast contrast to TCP/IP installations where traditionally the system administrator will determine in the /etc/hosts or in the DNS database what names -are associated with each IP address.

    One further point of clarification should be noted, the /etc/hosts +are associated with each IP address. +

    +One further point of clarification should be noted, the /etc/hosts file and the DNS records do not provide the NetBIOS name type information that MS Windows clients depend on to locate the type of service that may be needed. An example of this is what happens when an MS Windows client -wants to locate a domain logon server. It find this service and the IP +wants to locate a domain logon server. It finds this service and the IP address of a server that provides it by performing a lookup (via a NetBIOS broadcast) for enumeration of all machines that have -registered the name type *<1c>. A logon request is then sent to each +registered the name type *<1c>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Which -ever machine first replies then ends up providing the logon services.

    The name "workgroup" or "domain" really can be confusing since these +ever machine first replies then ends up providing the logon services. +

    +The name "workgroup" or "domain" really can be confusing since these have the added significance of indicating what is the security -architecture of the MS Windows network. The term "workgroup" indicates +architecture of the MS Windows network. The term "workgroup" indicates that the primary nature of the network environment is that of a peer-to-peer design. In a WORKGROUP all machines are responsible for their own security, and generally such security is limited to use of @@ -562,9 +205,9 @@ just a password (known as SHARE MODE security). In most situations with peer-to-peer networking the users who control their own machines will simply opt to have no security at all. It is possible to have USER MODE security in a WORKGROUP environment, thus requiring use -of a user name and a matching password.

    MS Windows networking is thus predetermined to use machine names +of a user name and a matching password. +

    +MS Windows networking is thus predetermined to use machine names for all local and remote machine message passing. The protocol used is called Server Message Block (SMB) and this is implemented using the NetBIOS protocol (Network Basic Input Output System). NetBIOS can @@ -573,64 +216,39 @@ the resulting protocol is called NetBEUI (Network Basic Extended User Interface). NetBIOS can also be run over IPX (Internetworking Packet Exchange) protocol as used by Novell NetWare, and it can be run over TCP/IP protocols - in which case the resulting protocol is called -NBT or NetBT, the NetBIOS over TCP/IP.

    MS Windows machines use a complex array of name resolution mechanisms. +NBT or NetBT, the NetBIOS over TCP/IP. +

    +MS Windows machines use a complex array of name resolution mechanisms. Since we are primarily concerned with TCP/IP this demonstration is -limited to this area.

    23.2.1. The NetBIOS Name Cache

    All MS Windows machines employ an in memory buffer in which is +limited to this area. +

    The NetBIOS Name Cache

    +All MS Windows machines employ an in memory buffer in which is stored the NetBIOS names and IP addresses for all external machines that that machine has communicated with over the past 10-15 minutes. It is more efficient to obtain an IP address for a machine from the local cache than it is to go through all the -configured name resolution mechanisms.

    If a machine whose name is in the local name cache has been shut +configured name resolution mechanisms. +

    +If a machine whose name is in the local name cache has been shut down before the name had been expired and flushed from the cache, then an attempt to exchange a message with that machine will be subject to time-out delays. i.e.: Its name is in the cache, so a name resolution lookup will succeed, but the machine can not respond. This can be -frustrating for users - but it is a characteristic of the protocol.

    The MS Windows utility that allows examination of the NetBIOS -name cache is called "nbtstat". The Samba equivalent of this -is called "nmblookup".

    23.2.2. The LMHOSTS file

    This file is usually located in MS Windows NT 4.0 or -2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains +frustrating for users - but it is a characteristic of the protocol. +

    +The MS Windows utility that allows examination of the NetBIOS +name cache is called "nbtstat". The Samba equivalent of this +is called "nmblookup". +

    The LMHOSTS file

    +This file is usually located in MS Windows NT 4.0 or +2000 in C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the machine name in matched pairs. The -LMHOSTS file performs NetBIOS name -to IP address mapping oriented.

    It typically looks like:

    	# Copyright (c) 1998 Microsoft Corp.
+LMHOSTS file performs NetBIOS name 
+to IP address mapping.
+
    
+It typically looks like:
+
    +	# Copyright (c) 1998 Microsoft Corp.
 	#
 	# This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
 	# over TCP/IP) stack for Windows98
@@ -639,7 +257,7 @@ CLASS="PROGRAMLISTING"
 	# (NetBIOS) names.  Each entry should be kept on an individual line.
 	# The IP address should be placed in the first column followed by the
 	# corresponding computername. The address and the comptername
-	# should be separated by at least one space or tab. The "#" character
+	# should be separated by at least one space or tab. The "#" character
 	# is generally used to denote the start of a comment (see the exceptions
 	# below).
 	#
@@ -647,34 +265,34 @@ CLASS="PROGRAMLISTING"
 	# files and offers the following extensions:
 	#
 	#      #PRE
-	#      #DOM:<domain>
-	#      #INCLUDE <filename>
+	#      #DOM:<domain>
+	#      #INCLUDE <filename>
 	#      #BEGIN_ALTERNATE
 	#      #END_ALTERNATE
 	#      \0xnn (non-printing character support)
 	#
-	# Following any entry in the file with the characters "#PRE" will cause
+	# Following any entry in the file with the characters "#PRE" will cause
 	# the entry to be preloaded into the name cache. By default, entries are
 	# not preloaded, but are parsed only after dynamic name resolution fails.
 	#
-	# Following an entry with the "#DOM:<domain>" tag will associate the
-	# entry with the domain specified by <domain>. This affects how the
+	# Following an entry with the "#DOM:<domain>" tag will associate the
+	# entry with the domain specified by <domain>. This affects how the
 	# browser and logon services behave in TCP/IP environments. To preload
 	# the host name associated with #DOM entry, it is necessary to also add a
-	# #PRE to the line. The <domain> is always preloaded although it will not
+	# #PRE to the line. The <domain> is always preloaded although it will not
 	# be shown when the name cache is viewed.
 	#
-	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
-	# software to seek the specified <filename> and parse it as if it were
-	# local. <filename> is generally a UNC-based name, allowing a
+	# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
+	# software to seek the specified <filename> and parse it as if it were
+	# local. <filename> is generally a UNC-based name, allowing a
 	# centralized lmhosts file to be maintained on a server.
 	# It is ALWAYS necessary to provide a mapping for the IP address of the
 	# server prior to the #INCLUDE. This mapping must use the #PRE directive.
-	# In addtion the share "public" in the example below must be in the
-	# LanManServer list of "NullSessionShares" in order for client machines to
+	# In addtion the share "public" in the example below must be in the
+	# LanManServer list of "NullSessionShares" in order for client machines to
 	# be able to read the lmhosts file successfully. This key is under
 	# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
-	# in the registry. Simply add "public" to the list found there.
+	# in the registry. Simply add "public" to the list found there.
 	#
 	# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
 	# statements to be grouped together. Any single successful include
@@ -687,7 +305,7 @@ CLASS="PROGRAMLISTING"
 	# The following example illustrates all of these extensions:
 	#
 	# 102.54.94.97     rhino         #PRE #DOM:networking  #net group's DC
-	# 102.54.94.102    "appname  \0x14"                    #special app server
+	# 102.54.94.102    "appname  \0x14"                    #special app server
 	# 102.54.94.123    popular            #PRE             #source server
 	# 102.54.94.117    localsrv           #PRE             #needed for the include
 	#
@@ -696,167 +314,51 @@ CLASS="PROGRAMLISTING"
 	# #INCLUDE \\rhino\public\lmhosts
 	# #END_ALTERNATE
 	#
-	# In the above example, the "appname" server contains a special
-	# character in its name, the "popular" and "localsrv" server names are
-	# preloaded, and the "rhino" server name is specified so it can be used
-	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
+	# In the above example, the "appname" server contains a special
+	# character in its name, the "popular" and "localsrv" server names are
+	# preloaded, and the "rhino" server name is specified so it can be used
+	# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
 	# system is unavailable.
 	#
 	# Note that the whole file is parsed including comments on each lookup,
 	# so keeping the number of comments to a minimum will improve performance.
 	# Therefore it is not advisable to simply add lmhosts file entries onto the
-	# end of this file.

    23.2.3. HOSTS file

    This file is usually located in MS Windows NT 4.0 or 2000 in -C:\WINNT\SYSTEM32\DRIVERS\ETC and contains + # end of this file. +

    HOSTS file

    +This file is usually located in MS Windows NT 4.0 or 2000 in +C:\WINNT\SYSTEM32\DRIVERS\ETC and contains the IP Address and the IP hostname in matched pairs. It can be used by the name resolution infrastructure in MS Windows, depending on how the TCP/IP environment is configured. This file is in -every way the equivalent of the Unix/Linux /etc/hosts file.

    23.2.4. DNS Lookup

    This capability is configured in the TCP/IP setup area in the network +every way the equivalent of the Unix/Linux /etc/hosts file. +

    DNS Lookup

    +This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled an elaborate name resolution sequence -is followed the precise nature of which isdependant on what the NetBIOS +is followed the precise nature of which is dependant on what the NetBIOS Node Type parameter is configured to. A Node Type of 0 means use NetBIOS broadcast (over UDP broadcast) is first used if the name that is the subject of a name lookup is not found in the NetBIOS name cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast -lookup is used.

    23.2.5. WINS Lookup

    A WINS (Windows Internet Name Server) service is the equivaent of the +lookup is used. +

    WINS Lookup

    +A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores the names and IP addresses that are registered by a Windows client -if the TCP/IP setup has been given at least one WINS Server IP Address.

    To configure Samba to be a WINS server the following parameter needs -to be added to the smb.conf file:

    	wins support = Yes

    To configure Samba to use a WINS server the following parameters are -needed in the smb.conf file:

    	wins support = No
-	wins server = xxx.xxx.xxx.xxx

    where xxx.xxx.xxx.xxx is the IP address -of the WINS server.

    PrevHomeNext
    Hosting a Microsoft Distributed File System tree on SambaUpImproved browsing in samba
    \ No newline at end of file +if the TCP/IP setup has been given at least one WINS Server IP Address. +

    +To configure Samba to be a WINS server the following parameter needs +to be added to the smb.conf file: +

    +	wins support = Yes
+

    +To configure Samba to use a WINS server the following parameters are +needed in the smb.conf file: +

    +	wins support = No
+	wins server = xxx.xxx.xxx.xxx
+

    +where xxx.xxx.xxx.xxx is the IP address +of the WINS server. +

    PrevUpNext
    Chapter22.Hosting a Microsoft Distributed File System tree on SambaHomeChapter24.Securing Samba
    diff --git a/docs/htmldocs/introduction.html b/docs/htmldocs/introduction.html index f45e60b5c5..f54776747c 100644 --- a/docs/htmldocs/introduction.html +++ b/docs/htmldocs/introduction.html @@ -1,152 +1,6 @@ - -General installation
    SAMBA Project Documentation
    PrevNext

    I. General installation

    Introduction

    This part contains general info on how to install samba + +PartI.General Installation

    PartI.General Installation
    PrevNext

    General Installation

    Preparing Samba for Configuration

    This section of the Samba-HOWTO-Collection contains general info on how to install samba and how to configure the parts of samba you will most likely need. -PLEASE read this.

    PrevHomeNext
    SAMBA Project Documentation Introduction to Samba
    \ No newline at end of file +PLEASE read this.

    Table of Contents

    1. Introduction to Samba
    Background
    Terminology
    Related Projects
    SMB Methodology
    Additional Resources
    Epilogue
    Miscellaneous
    2. How to Install and Test SAMBA
    Obtaining and installing samba
    Configuring samba
    Editing the smb.conf file
    SWAT
    Try listing the shares available on your + server
    Try connecting with the unix client
    Try connecting from a DOS, WfWg, Win9x, WinNT, + Win2k, OS/2, etc... client
    What If Things Don't Work?
    PrevUpNext
    SAMBA Project DocumentationHomeChapter1.Introduction to Samba
    diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 375fe5618d..9995b6937a 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -1,212 +1,37 @@ - -lmhosts

    lmhosts

    Name

    lmhosts -- The Samba NetBIOS hosts file

    Synopsis

    lmhosts is the Samba(7) NetBIOS name to IP address mapping file.

    DESCRIPTION

    This file is part of the Samba(7) suite.

    lmhosts is the Samba - NetBIOS name to IP address mapping file. It - is very similar to the /etc/hosts file +lmhosts

    Name

    lmhosts — The Samba NetBIOS hosts file

    Synopsis

    lmhosts is the Samba(7) NetBIOS name to IP address mapping file.

    DESCRIPTION

    This file is part of the Samba(7) suite.

    lmhosts is the Samba + NetBIOS name to IP address mapping file. It + is very similar to the /etc/hosts file format, except that the hostname component must correspond - to the NetBIOS naming format.

    FILE FORMAT

    It is an ASCII file containing one line for NetBIOS name. + to the NetBIOS naming format.

    FILE FORMAT

    It is an ASCII file containing one line for NetBIOS name. The two fields on each line are separated from each other by white space. Any entry beginning with '#' is ignored. Each line - in the lmhosts file contains the following information:

    • IP Address - in dotted decimal format.

    • NetBIOS Name - This name format is a + in the lmhosts file contains the following information:

      • IP Address - in dotted decimal format.

      • NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type - as two hexadecimal digits.

        If the trailing '#' is omitted then the given IP + as two hexadecimal digits.

        If the trailing '#' is omitted then the given IP address will be returned for all names that match the given - name, whatever the NetBIOS name type in the lookup.

      An example follows:

      #
+		name, whatever the NetBIOS name type in the lookup.

    An example follows:

    +#
 # Sample Samba lmhosts file.
 #
 192.9.200.1	TESTPC
 192.9.200.20	NTSERVER#20
 192.9.200.21	SAMBASERVER
-

    Contains three IP to NetBIOS name mappings. The first - and third will be returned for any queries for the names "TESTPC" - and "SAMBASERVER" respectively, whatever the type component of - the NetBIOS name requested.

    The second mapping will be returned only when the "0x20" name - type for a name "NTSERVER" is queried. Any other name type will not - be resolved.

    The default location of the lmhosts file - is in the same directory as the smb.conf(5) file.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbclient(1), smb.conf(5), and smbpasswd(8) -

    AUTHOR

    The original Samba software and related utilities +

    Contains three IP to NetBIOS name mappings. The first + and third will be returned for any queries for the names "TESTPC" + and "SAMBASERVER" respectively, whatever the type component of + the NetBIOS name requested.

    The second mapping will be returned only when the "0x20" name + type for a name "NTSERVER" is queried. Any other name type will not + be resolved.

    The default location of the lmhosts file + is in the same directory as the smb.conf(5) file.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbclient(1), smb.conf(5), and smbpasswd(8) +

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at - ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 was done by Alexander Bokovoy.

    \ No newline at end of file + XML 4.2 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/msdfs.html b/docs/htmldocs/msdfs.html index 77fc65c680..cb7592214e 100644 --- a/docs/htmldocs/msdfs.html +++ b/docs/htmldocs/msdfs.html @@ -1,147 +1,29 @@ - -Hosting a Microsoft Distributed File System tree on Samba
    SAMBA Project Documentation
    PrevNext

    Chapter 22. Hosting a Microsoft Distributed File System tree on Samba

    22.1. Instructions

    The Distributed File System (or Dfs) provides a means of + +Chapter22.Hosting a Microsoft Distributed File System tree on Samba

    Chapter22.Hosting a Microsoft Distributed File System tree on Samba
    PrevPartIII.Advanced ConfigurationNext

    Chapter22.Hosting a Microsoft Distributed File System tree on Samba

    Shirish Kalele

    Samba Team & Veritas Software


    + <samba@samba.org>
    +

    12 Jul 2000

    Table of Contents

    Instructions
    Notes

    Instructions

    The Distributed File System (or Dfs) provides a means of separating the logical view of files and directories that users see from the actual physical locations of these resources on the network. It allows for higher availability, smoother storage expansion, - load balancing etc. For more information about Dfs, refer to Microsoft documentation.

    This document explains how to host a Dfs tree on a Unix - machine (for Dfs-aware clients to browse) using Samba.

    To enable SMB-based DFS for Samba, configure it with the - --with-msdfs option. Once built, a + load balancing etc. For more information about Dfs, refer to + Microsoft documentation.

    This document explains how to host a Dfs tree on a Unix + machine (for Dfs-aware clients to browse) using Samba.

    To enable SMB-based DFS for Samba, configure it with the + --with-msdfs option. Once built, a Samba server can be made a Dfs server by setting the global - boolean host msdfs parameter in the smb.conf - file. You designate a share as a Dfs root using the share - level boolean msdfs root parameter. A Dfs root directory on + boolean + host msdfs parameter in the smb.conf + file. You designate a share as a Dfs root using the share + level boolean + msdfs root parameter. A Dfs root directory on Samba hosts Dfs links in the form of symbolic links that point to other servers. For example, a symbolic link - junction->msdfs:storage1\share1 in + junction->msdfs:storage1\share1 in the share directory acts as the Dfs junction. When Dfs-aware clients attempt to access the junction link, they are redirected - to the storage location (in this case, \\storage1\share1).

    Dfs trees on Samba work with all Dfs-aware clients ranging - from Windows 95 to 2000.

    Here's an example of setting up a Dfs tree on a Samba - server.

    # The smb.conf file:
+	to the storage location (in this case, \\storage1\share1).
    Dfs trees on Samba work with all Dfs-aware clients ranging 
+	from Windows 95 to 2000.
    Here's an example of setting up a Dfs tree on a Samba 
+	server.
    +# The smb.conf file:
 [global]
 	netbios name = SAMBA
 	host msdfs   = yes
@@ -149,160 +31,21 @@ CLASS="PROGRAMLISTING"
 [dfs]
 	path = /export/dfsroot
 	msdfs root = yes
-	
    In the /export/dfsroot directory we set up our dfs links to 
-	other servers on the network.
    root# cd /export/dfsroot
    root# chown root /export/dfsroot
    root# chmod 755 /export/dfsroot
    root# ln -s msdfs:storageA\\shareA linka
    root# ln -s msdfs:serverB\\share,serverC\\share linkb
    You should set up the permissions and ownership of 
+

    In the /export/dfsroot directory we set up our dfs links to + other servers on the network.

    root# cd /export/dfsroot

    root# chown root /export/dfsroot

    root# chmod 755 /export/dfsroot

    root# ln -s msdfs:storageA\\shareA linka

    root# ln -s msdfs:serverB\\share,serverC\\share linkb

    You should set up the permissions and ownership of the directory acting as the Dfs root such that only designated users can create, delete or modify the msdfs links. Also note that symlink names should be all lowercase. This limitation exists to have Samba avoid trying all the case combinations to get at the link name. Finally set up the symbolic links to point to the - network shares you want, and start Samba.

    Users on Dfs-aware clients can now browse the Dfs tree + network shares you want, and start Samba.

    Users on Dfs-aware clients can now browse the Dfs tree on the Samba server at \\samba\dfs. Accessing links linka or linkb (which appear as directories to the client) - takes users directly to the appropriate shares on the network.

    22.1.1. Notes

    • Windows clients need to be rebooted + takes users directly to the appropriate shares on the network.

      Notes

      • Windows clients need to be rebooted if a previously mounted non-dfs share is made a dfs root or vice versa. A better way is to introduce a - new share and make it the dfs root.

      • Currently there's a restriction that msdfs - symlink names should all be lowercase.

      • For security purposes, the directory + new share and make it the dfs root.

      • Currently there's a restriction that msdfs + symlink names should all be lowercase.

      • For security purposes, the directory acting as the root of the Dfs tree should have ownership and permissions set so that only designated users can - modify the symbolic links in the directory.

    PrevHomeNext
    Stackable VFS modulesUpIntegrating MS Windows networks with Samba
    \ No newline at end of file + modify the symbolic links in the directory.

    PrevUpNext
    Chapter21.Stackable VFS modulesHomeChapter23.Integrating MS Windows networks with Samba
    diff --git a/docs/htmldocs/net.8.html b/docs/htmldocs/net.8.html index 26711d936f..be30dbed05 100644 --- a/docs/htmldocs/net.8.html +++ b/docs/htmldocs/net.8.html @@ -1,1586 +1,146 @@ - -net

    net

    Name

    net -- Tool for administration of Samba and remote +net

    Name

    net — Tool for administration of Samba and remote CIFS servers. -

    Synopsis

    net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The samba net utility is meant to work just like the net utility +

    Synopsis

    net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The samba net utility is meant to work just like the net utility available for windows and DOS. The first argument should be used to specify the protocol to use when executing a certain command. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000. If this argument is omitted, net will try to determine it automatically. Not all commands are available on all protocols. -

    OPTIONS

    -h|--help

    Print a summary of command line options.

    -w target-workgroup

    Sets target workgroup or domain. You have to specify +

    OPTIONS

    -h|--help

    Print a summary of command line options. +

    -w target-workgroup

    + Sets target workgroup or domain. You have to specify either this option or the IP address or the name of a server. -

    -W workgroup

    Sets client workgroup or domain -

    -U user

    User name to use -

    -I ip-address

    IP address of target server to use. You have to +

    -W workgroup

    + Sets client workgroup or domain +

    -U user

    + User name to use +

    -I ip-address

    + IP address of target server to use. You have to specify either this option or a target workgroup or a target server. -

    -p port

    Port on the target server to connect to (usually 139 or 445). +

    -p port

    + Port on the target server to connect to (usually 139 or 445). Defaults to trying 445 first, then 139. -

    -n <primary NetBIOS name>

    This option allows you to override +

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command line setting will take precedence over settings in -smb.conf(5).

    -s <configuration file>

    The file specified contains the +smb.conf(5).

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -S server

    Name of target server. You should specify either +compile time.

    -S server

    + Name of target server. You should specify either this option or a target workgroup or a target IP address. -

    -l

    When listing data, give more information on each item. -

    -P

    Make queries to the external server using the machine account of the local server. -

    -d|--debug=debuglevel

    debuglevel is an integer +

    -l

    + When listing data, give more information on each item. +

    -P

    + Make queries to the external server using the machine account of the local server. +

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    COMMANDS

    TIME

    The NET TIME command allows you to view the time on a remote server - or synchronise the time on the local server with the time on the remote server.

    TIME

    Without any options, the NET TIME command -displays the time on the remote server.

    TIME SYSTEM

    Displays the time on the remote server in a format ready for /bin/date

    TIME SET

    Tries to set the date and time of the local server to that on -the remote server using /bin/date.

    TIME ZONE

    Displays the timezone in hours from GMT on the remote computer.

    [RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]

    Join a domain. If the account already exists on the server, and +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    COMMANDS

    TIME

    The NET TIME command allows you to view the time on a remote server + or synchronise the time on the local server with the time on the remote server.

    TIME

    Without any options, the NET TIME command +displays the time on the remote server. +

    TIME SYSTEM

    Displays the time on the remote server in a format ready for /bin/date

    TIME SET

    Tries to set the date and time of the local server to that on +the remote server using /bin/date.

    TIME ZONE

    Displays the timezone in hours from GMT on the remote computer.

    [RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]

    +Join a domain. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may -be created.

    [TYPE] may be PDC, BDC or MEMBER to specify the type of server -joining the domain.

    [RPC] OLDJOIN [options]

    Join a domain. Use the OLDJOIN option to join the domain +be created.

    +[TYPE] may be PDC, BDC or MEMBER to specify the type of server +joining the domain. +

    [RPC] OLDJOIN [options]

    Join a domain. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust -account in server manager first.

    [RPC|ADS] USER

    [RPC|ADS] USER DELETE target

    Delete specified user

    [RPC|ADS] USER LIST

    List all users

    [RPC|ADS] USER INFO target

    List the domain groups of a the specified user.

    [RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]

    Add specified user.

    [RPC|ADS] GROUP

    [RPC|ADS] GROUP [misc options] [targets]

    List user groups.

    [RPC|ADS] GROUP DELETE name [misc. options]

    Delete specified group.

    [RPC|ADS] GROUP ADD name [-C comment]

    Create specified group.

    [RAP|RPC] SHARE

    [RAP|RPC] SHARE [misc. options] [targets]

    Enumerates all exported resources (network shares) on target server.

    [RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]

    Adds a share from a server (makes the export active). Maxusers +account in server manager first.

    [RPC|ADS] USER

    [RPC|ADS] USER DELETE target

    Delete specified user

    [RPC|ADS] USER LIST

    List all users

    [RPC|ADS] USER INFO target

    List the domain groups of a the specified user.

    [RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]

    Add specified user.

    [RPC|ADS] GROUP

    [RPC|ADS] GROUP [misc options] [targets]

    List user groups.

    [RPC|ADS] GROUP DELETE name [misc. options]

    Delete specified group.

    [RPC|ADS] GROUP ADD name [-C comment]

    Create specified group.

    [RAP|RPC] SHARE

    [RAP|RPC] SHARE [misc. options] [targets]

    Enumerates all exported resources (network shares) on target server.

    [RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]

    Adds a share from a server (makes the export active). Maxusers specifies the number of users that can be connected to the -share simultaneously.

    SHARE DELETE sharenam

    Delete specified share.

    [RPC|RAP] FILE

    [RPC|RAP] FILE

    List all open files on remote server.

    [RPC|RAP] FILE CLOSE fileid

    Close file with specified fileid on -remote server.

    [RPC|RAP] FILE INFO fileid

    Print information on specified fileid. -Currently listed are: file-id, username, locks, path, permissions.

    [RAP|RPC] FILE USER

    Currently NOT implemented.

    SESSION

    RAP SESSION

    Without any other options, SESSION enumerates all active SMB/CIFS -sessions on the target server.

    RAP SESSION DELETE|CLOSE CLIENT_NAME

    Close the specified sessions.

    RAP SESSION INFO CLIENT_NAME

    Give a list with all the open files in specified session.

    RAP SERVER DOMAIN

    List all servers in specified domain or workgroup. Defaults -to local domain.

    RAP DOMAIN

    Lists all domains and workgroups visible on the -current network.

    RAP PRINTQ

    RAP PRINTQ LIST QUEUE_NAME

    Lists the specified print queue and print jobs on the server. -If the QUEUE_NAME is omitted, all -queues are listed.

    RAP PRINTQ DELETE JOBID

    Delete job with specified id.

    RAP VALIDATE user [password]

    Validate whether the specified user can log in to the +share simultaneously.

    SHARE DELETE sharenam

    Delete specified share.

    [RPC|RAP] FILE

    [RPC|RAP] FILE

    List all open files on remote server.

    [RPC|RAP] FILE CLOSE fileid

    Close file with specified fileid on +remote server.

    [RPC|RAP] FILE INFO fileid

    +Print information on specified fileid. +Currently listed are: file-id, username, locks, path, permissions. +

    [RAP|RPC] FILE USER

    Note

    Currently NOT implemented.

    SESSION

    RAP SESSION

    Without any other options, SESSION enumerates all active SMB/CIFS +sessions on the target server.

    RAP SESSION DELETE|CLOSE CLIENT_NAME

    Close the specified sessions.

    RAP SESSION INFO CLIENT_NAME

    Give a list with all the open files in specified session.

    RAP SERVER DOMAIN

    List all servers in specified domain or workgroup. Defaults +to local domain.

    RAP DOMAIN

    Lists all domains and workgroups visible on the +current network.

    RAP PRINTQ

    RAP PRINTQ LIST QUEUE_NAME

    Lists the specified print queue and print jobs on the server. +If the QUEUE_NAME is omitted, all +queues are listed.

    RAP PRINTQ DELETE JOBID

    Delete job with specified id.

    RAP VALIDATE user [password]

    +Validate whether the specified user can log in to the remote server. If the password is not specified on the commandline, it -will be prompted.

    Currently NOT implemented.

    RAP GROUPMEMBER

    RAP GROUPMEMBER LIST GROUP

    List all members of the specified group.

    RAP GROUPMEMBER DELETE GROUP USER

    Delete member from group.

    RAP GROUPMEMBER ADD GROUP USER

    Add member to group.

    RAP ADMIN command

    Execute the specified command on -the remote server. Only works with OS/2 servers.

    Currently NOT implemented.

    RAP SERVICE

    RAP SERVICE START NAME [arguments...]

    Start the specified service on the remote server. Not implemented yet.

    Currently NOT implemented.

    RAP SERVICE STOP

    Stop the specified service on the remote server.

    Currently NOT implemented.

    RAP PASSWORD USER OLDPASS NEWPASS

    Change password of USER from OLDPASS to NEWPASS.

    LOOKUP

    LOOKUP HOST HOSTNAME [TYPE]

    Lookup the IP address of the given host with the specified type (netbios suffix). -The type defaults to 0x20 (workstation).

    LOOKUP LDAP [DOMAIN

    Give IP address of LDAP server of specified DOMAIN. Defaults to local domain.

    LOOKUP KDC [REALM]

    Give IP address of KDC for the specified REALM. -Defaults to local realm.

    LOOKUP DC [DOMAIN]

    Give IP's of Domain Controllers for specified DOMAIN. Defaults to local domain.

    LOOKUP MASTER DOMAIN

    Give IP of master browser for specified DOMAIN -or workgroup. Defaults to local domain.

    CACHE

    Samba uses a general caching interface called 'gencache'. It -can be controlled using 'NET CACHE'.

    All the timeout parameters support the suffixes: +will be prompted. +

    Note

    Currently NOT implemented.

    RAP GROUPMEMBER

    RAP GROUPMEMBER LIST GROUP

    List all members of the specified group.

    RAP GROUPMEMBER DELETE GROUP USER

    Delete member from group.

    RAP GROUPMEMBER ADD GROUP USER

    Add member to group.

    RAP ADMIN command

    Execute the specified command on +the remote server. Only works with OS/2 servers. +

    Note

    Currently NOT implemented.

    RAP SERVICE

    RAP SERVICE START NAME [arguments...]

    Start the specified service on the remote server. Not implemented yet.

    Note

    Currently NOT implemented.

    RAP SERVICE STOP

    Stop the specified service on the remote server.

    Note

    Currently NOT implemented.

    RAP PASSWORD USER OLDPASS NEWPASS

    +Change password of USER from OLDPASS to NEWPASS. +

    LOOKUP

    LOOKUP HOST HOSTNAME [TYPE]

    +Lookup the IP address of the given host with the specified type (netbios suffix). +The type defaults to 0x20 (workstation). +

    LOOKUP LDAP [DOMAIN

    Give IP address of LDAP server of specified DOMAIN. Defaults to local domain.

    LOOKUP KDC [REALM]

    Give IP address of KDC for the specified REALM. +Defaults to local realm.

    LOOKUP DC [DOMAIN]

    Give IP's of Domain Controllers for specified +DOMAIN. Defaults to local domain.

    LOOKUP MASTER DOMAIN

    Give IP of master browser for specified DOMAIN +or workgroup. Defaults to local domain.

    CACHE

    Samba uses a general caching interface called 'gencache'. It +can be controlled using 'NET CACHE'.

    All the timeout parameters support the suffixes: -

    s - Seconds
    m - Minutes
    h - Hours
    d - Days
    w - Weeks

    CACHE ADD key data time-out

    Add specified key+data to the cache with the given timeout.

    CACHE DEL key

    Delete key from the cache.

    CACHE SET key data time-out

    Update data of existing cache entry.

    CACHE SEARCH PATTERN

    Search for the specified pattern in the cache data.

    CACHE LIST

    List all current items in the cache.

    CACHE FLUSH

    Remove all the current items from the cache.

    GETLOCALSID [DOMAIN]

    Print the SID of the specified domain, or if the parameter is -omitted, the SID of the domain the local server is in.

    SETLOCALSID S-1-5-21-x-y-z

    Sets domain sid for the local server to the specified SID.

    MAXRID

    Prints out the highest RID currently in use on the local -server (by the active 'passdb backend').

    RPC INFO

    Print information about the domain of the remote server, -such as domain name, domain sid and number of users and groups.

    [RPC|ADS] TESTJOIN

    Check whether participation in a domain is still valid.

    [RPC|ADS] CHANGETRUSTPW

    Force change of domain trust password.

    RPC TRUSTDOM

    RPC TRUSTDOM ADD DOMAIN

    Add a interdomain trust account for -DOMAIN to the remote server.

    RPC TRUSTDOM DEL DOMAIM

    Remove interdomain trust account for -DOMAIN from the remote server.

    Currently NOT implemented.

    RPC TRUSTDOM ESTABLISH DOMAIN

    Establish a trust relationship to a trusting domain. -Interdomain account must already be created on the remote PDC.

    RPC TRUSTDOM REVOKE DOMAIN

    Abandon relationship to trusted domain

    RPC TRUSTDOM LIST

    List all current interdomain trust relationships.

    RPC ABORTSHUTDOWN

    Abort the shutdown of a remote server.

    SHUTDOWN [-t timeout] [-r] [-f] [-C message]

    Shut down the remote server.

    -r

    Reboot after shutdown.

    -f

    Force shutting down all applications.

    -t timeout

    Timeout before system will be shut down. An interactive -user of the system can use this time to cancel the shutdown.

    -C message

    Display the specified message on the screen to -announce the shutdown.

    SAMDUMP

    Print out sam database of remote server. You need -to run this on either a BDC.

    VAMPIRE

    Export users, aliases and groups from remote server to -local server. Can only be run an a BDC.

    GETSID

    Fetch domain SID and store it in the local secrets.tdb.

    ADS LEAVE

    Make the remote host leave the domain it is part of.

    ADS STATUS

    Print out status of machine account of the local machine in ADS. +

    s - Seconds
    m - Minutes
    h - Hours
    d - Days
    w - Weeks

    + +

    CACHE ADD key data time-out

    Add specified key+data to the cache with the given timeout.

    CACHE DEL key

    Delete key from the cache.

    CACHE SET key data time-out

    Update data of existing cache entry.

    CACHE SEARCH PATTERN

    Search for the specified pattern in the cache data.

    CACHE LIST

    +List all current items in the cache. +

    CACHE FLUSH

    Remove all the current items from the cache.

    GETLOCALSID [DOMAIN]

    Print the SID of the specified domain, or if the parameter is +omitted, the SID of the domain the local server is in.

    SETLOCALSID S-1-5-21-x-y-z

    Sets domain sid for the local server to the specified SID.

    GROUPMAP

    Manage the mappings between Windows group SIDs and UNIX groups. +Parameters take the for "parameter=value". Common options include:

    • unixgroup - Name of the UNIX group

    • ntgroup - Name of the Windows NT group (must be + resolvable to a SID

    • rid - Unsigned 32-bit integer

    • sid - Full SID in the form of "S-1-..."

    • type - Type of the group; either 'domain', 'local', + or 'builtin'

    • comment - Freeform text description of the group

    GROUPMAP ADD

    Add a new group mapping entry

    net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]

    GROUPMAP DELETE

    Delete a group mapping entry

    net groupmap delete {ntgroup=string|sid=SID}

    GROUPMAP MODIFY

    Update en existing group entry

    net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}

    GROUPMAP LIST

    List existing group mapping entries

    net groupmap list [verbose] [ntgroup=string] [sid=SID]

    MAXRID

    Prints out the highest RID currently in use on the local +server (by the active 'passdb backend'). +

    RPC INFO

    Print information about the domain of the remote server, +such as domain name, domain sid and number of users and groups. +

    [RPC|ADS] TESTJOIN

    Check whether participation in a domain is still valid.

    [RPC|ADS] CHANGETRUSTPW

    Force change of domain trust password.

    RPC TRUSTDOM

    RPC TRUSTDOM ADD DOMAIN

    Add a interdomain trust account for +DOMAIN to the remote server. +

    RPC TRUSTDOM DEL DOMAIM

    Remove interdomain trust account for +DOMAIN from the remote server. +

    Note

    Currently NOT implemented.

    RPC TRUSTDOM ESTABLISH DOMAIN

    +Establish a trust relationship to a trusting domain. +Interdomain account must already be created on the remote PDC. +

    RPC TRUSTDOM REVOKE DOMAIN

    Abandon relationship to trusted domain

    RPC TRUSTDOM LIST

    List all current interdomain trust relationships.

    RPC ABORTSHUTDOWN

    Abort the shutdown of a remote server.

    SHUTDOWN [-t timeout] [-r] [-f] [-C message]

    Shut down the remote server.

    -r

    +Reboot after shutdown. +

    -f

    +Force shutting down all applications. +

    -t timeout

    +Timeout before system will be shut down. An interactive +user of the system can use this time to cancel the shutdown. +

    -C message

    Display the specified message on the screen to +announce the shutdown.

    SAMDUMP

    Print out sam database of remote server. You need +to run this on either a BDC.

    VAMPIRE

    Export users, aliases and groups from remote server to +local server. Can only be run an a BDC. +

    GETSID

    Fetch domain SID and store it in the local secrets.tdb.

    ADS LEAVE

    Make the remote host leave the domain it is part of.

    ADS STATUS

    Print out status of machine account of the local machine in ADS. Prints out quite some debug info. Aimed at developers, regular -users should use NET ADS TESTJOIN.

    ADS PRINTER

    ADS PRINTER INFO [PRINTER] [SERVER]

    Lookup info for PRINTER on SERVER. The printer name defaults to "*", the -server name defaults to the local host.

    ADS PRINTER PUBLISH PRINTER

    Publish specified printer using ADS.

    ADS PRINTER REMOVE PRINTER

    Remove specified printer from ADS directory.

    ADS SEARCH EXPRESSION ATTRIBUTES...

    Perform a raw LDAP search on a ADS server and dump the results. The +users should use NET ADS TESTJOIN.

    ADS PRINTER

    ADS PRINTER INFO [PRINTER] [SERVER]

    +Lookup info for PRINTER on SERVER. The printer name defaults to "*", the +server name defaults to the local host.

    ADS PRINTER PUBLISH PRINTER

    Publish specified printer using ADS.

    ADS PRINTER REMOVE PRINTER

    Remove specified printer from ADS directory.

    ADS SEARCH EXPRESSION ATTRIBUTES...

    Perform a raw LDAP search on a ADS server and dump the results. The expression is a standard LDAP search expression, and the -attributes are a list of LDAP fields to show in the results.

    Example: net ads search '(objectCategory=group)' sAMAccountName

    ADS DN DN (attributes)

    Perform a raw LDAP search on a ADS server and dump the results. The +attributes are a list of LDAP fields to show in the results.

    Example: net ads search '(objectCategory=group)' sAMAccountName +

    ADS DN DN (attributes)

    +Perform a raw LDAP search on a ADS server and dump the results. The DN standard LDAP DN, and the attributes are a list of LDAP fields -to show in the result.

    Example: net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName

    WORKGROUP

    Print out workgroup name for specified kerberos realm.

    HELP [COMMAND]

    Gives usage information for the specified command.

    VERSION

    This man page is incomplete for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +to show in the result. +

    Example: net ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName

    WORKGROUP

    Print out workgroup name for specified kerberos realm.

    HELP [COMMAND]

    Gives usage information for the specified command.

    VERSION

    This man page is complete for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The net manpage was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The net manpage was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 6b8161e02e..b07267fa45 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -1,712 +1,153 @@ - -nmbd

    nmbd

    Name

    nmbd -- NetBIOS name server to provide NetBIOS - over IP naming services to clients

    Synopsis

    nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    nmbd is a server that understands +nmbd

    Name

    nmbd — NetBIOS name server to provide NetBIOS + over IP naming services to clients

    Synopsis

    nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    nmbd is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients. It also participates in the browsing protocols which make up the - Windows "Network Neighborhood" view.

    SMB/CIFS clients, when they start up, may wish to + Windows "Network Neighborhood" view.

    SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server. That is, they wish to know what - IP number a specified host is using.

    Amongst other services, nmbd will + IP number a specified host is using.

    Amongst other services, nmbd will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it - is running on. Its "own NetBIOS name" is by + is running on. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, - but this can be overridden with the -n - option (see OPTIONS below). Thus nmbd will + but this can be overridden with the -n + option (see OPTIONS below). Thus nmbd will reply to broadcast queries for its own name(s). Additional - names for nmbd to respond on can be set - via parameters in the smb.conf(5) configuration file.

    nmbd can also be used as a WINS + names for nmbd to respond on can be set + via parameters in the smb.conf(5) configuration file.

    nmbd can also be used as a WINS (Windows Internet Name Server) server. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and - replying to queries from clients for these names.

    In addition, nmbd can act as a WINS + replying to queries from clients for these names.

    In addition, nmbd can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS - server.

    OPTIONS

    -D

    If specified, this parameter causes - nmbd to operate as a daemon. That is, + server.

    OPTIONS

    -D

    If specified, this parameter causes + nmbd to operate as a daemon. That is, it detaches itself and runs in the background, fielding - requests on the appropriate port. By default, nmbd + requests on the appropriate port. By default, nmbd will operate as a daemon if launched from a command shell. - nmbd can also be operated from the inetd + nmbd can also be operated from the inetd meta-daemon, although this is not recommended. -

    -F

    If specified, this parameter causes - the main nmbd process to not daemonize, +

    -F

    If specified, this parameter causes + the main nmbd process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running - nmbd under process supervisors such - as supervise and svscan - from Daniel J. Bernstein's daemontools + nmbd under process supervisors such + as supervise and svscan + from Daniel J. Bernstein's daemontools package, or the AIX process monitor. -

    -S

    If specified, this parameter causes - nmbd to log to standard output rather - than a file.

    -i

    If this parameter is specified it causes the - server to run "interactively", not as a daemon, even if the +

    -S

    If specified, this parameter causes + nmbd to log to standard output rather + than a file.

    -i

    If this parameter is specified it causes the + server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell. Setting this parameter negates the implicit daemon mode when run from the - command line. nmbd also logs to standard - output, as if the -S parameter had been - given.

    -h|--help

    Print a summary of command line options.

    -H <filename>

    NetBIOS lmhosts file. The lmhosts + command line. nmbd also logs to standard + output, as if the -S parameter had been + given.

    -h|--help

    Print a summary of command line options. +

    -H <filename>

    NetBIOS lmhosts file. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name - resolution mechanism name resolve - order described in smb.conf(5) to resolve any + resolution mechanism name resolve + order described in smb.conf(5) to resolve any NetBIOS name queries needed by the server. Note - that the contents of this file are NOT - used by nmbd to answer any name queries. + that the contents of this file are NOT + used by nmbd to answer any name queries. Adding a line to this file affects name NetBIOS resolution - from this host ONLY.

    The default path to this file is compiled into + from this host ONLY.

    The default path to this file is compiled into Samba as part of the build process. Common defaults - are /usr/local/samba/lib/lmhosts, - /usr/samba/lib/lmhosts or - /etc/samba/lmhosts. See the lmhosts(5) man page for details on the contents of this file.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + are /usr/local/samba/lib/lmhosts, + /usr/samba/lib/lmhosts or + /etc/samba/lmhosts. See the lmhosts(5) man page for details on the contents of this file.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -p <UDP port number>

    UDP port number is a positive integer value. +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -p <UDP port number>

    UDP port number is a positive integer value. This option changes the default UDP port number (normally 137) - that nmbd responds to name queries on. Don't + that nmbd responds to name queries on. Don't use this option unless you are an expert, in which case you - won't need help!

    FILES

    /etc/inetd.conf

    If the server is to be run by the - inetd meta-daemon, this file + won't need help!

    FILES

    /etc/inetd.conf

    If the server is to be run by the + inetd meta-daemon, this file must contain suitable startup information for the - meta-daemon. See the install document + meta-daemon. See the install document for details. -

    /etc/rc

    or whatever initialization script your - system uses).

    If running the server as a daemon at startup, +

    /etc/rc

    or whatever initialization script your + system uses).

    If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. See the "How to Install and Test SAMBA" document - for details.

    /etc/services

    If running the server via the - meta-daemon inetd, this file + sequence for the server. See the "How to Install and Test SAMBA" document + for details.

    /etc/services

    If running the server via the + meta-daemon inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - See the "How to Install and Test SAMBA" - document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of - the smb.conf(5) server + See the "How to Install and Test SAMBA" + document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of + the smb.conf(5) server configuration file. Other common places that systems - install this file are /usr/samba/lib/smb.conf - and /etc/samba/smb.conf.

    When run as a WINS server (see the - wins support - parameter in the smb.conf(5) man page), - nmbd - will store the WINS database in the file wins.dat - in the var/locks directory configured under - wherever Samba was configured to install itself.

    If nmbd is acting as a browse master (see the local master - parameter in the smb.conf(5) man page, nmbd - will store the browsing database in the file browse.dat - in the var/locks directory + install this file are /usr/samba/lib/smb.conf + and /etc/samba/smb.conf.

    When run as a WINS server (see the + wins support + parameter in the smb.conf(5) man page), + nmbd + will store the WINS database in the file wins.dat + in the var/locks directory configured under + wherever Samba was configured to install itself.

    If nmbd is acting as a + browse master (see the local master + parameter in the smb.conf(5) man page, nmbd + will store the browsing database in the file browse.dat + in the var/locks directory configured under wherever Samba was configured to install itself. -

    SIGNALS

    To shut down an nmbd process it is recommended - that SIGKILL (-9) NOT be used, except as a last +

    SIGNALS

    To shut down an nmbd process it is recommended + that SIGKILL (-9) NOT be used, except as a last resort, as this may leave the name database in an inconsistent state. - The correct way to terminate nmbd is to send it - a SIGTERM (-15) signal and wait for it to die on its own.

    nmbd will accept SIGHUP, which will cause - it to dump out its namelists into the file namelist.debug - in the /usr/local/samba/var/locks - directory (or the var/locks directory configured + The correct way to terminate nmbd is to send it + a SIGTERM (-15) signal and wait for it to die on its own.

    nmbd will accept SIGHUP, which will cause + it to dump out its namelists into the file namelist.debug + in the /usr/local/samba/var/locks + directory (or the var/locks directory configured under wherever Samba was configured to install itself). This will also - cause nmbd to dump out its server database in - the log.nmb file.

    The debug log level of nmbd may be raised or lowered - using smbcontrol(1) (SIGUSR[1|2] signals + cause nmbd to dump out its server database in + the log.nmb file.

    The debug log level of nmbd may be raised or lowered + using smbcontrol(1) (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running - at a normally low log level.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    inetd(8), smbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the Internet - RFC's rfc1001.txt, rfc1002.txt. + at a normally low log level.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    + inetd(8), smbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the Internet + RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available - as a link from the Web page - http://samba.org/cifs/.

    AUTHOR

    The original Samba software and related utilities + as a link from the Web page + http://samba.org/cifs/.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index cb1df2cd82..851544f0d8 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -1,494 +1,107 @@ - -nmblookup

    nmblookup

    Name

    nmblookup -- NetBIOS over TCP/IP client used to lookup NetBIOS - names

    Synopsis

    nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    nmblookup is used to query NetBIOS names +nmblookup

    Name

    nmblookup — NetBIOS over TCP/IP client used to lookup NetBIOS + names

    Synopsis

    nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    nmblookup is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine. All queries - are done over UDP.

    OPTIONS

    -M

    Searches for a master browser by looking - up the NetBIOS name name with a - type of 0x1d. If name is "-" then it does a lookup on the special name - __MSBROWSE__.

    -R

    Set the recursion desired bit in the packet + are done over UDP.

    OPTIONS

    -M

    Searches for a master browser by looking + up the NetBIOS name name with a + type of 0x1d. If + name is "-" then it does a lookup on the special name + __MSBROWSE__. Please note that in order to + use the name "-", you need to make sure "-" isn't parsed as an + argument, e.g. use : + nmblookup -M -- -.

    -R

    Set the recursion desired bit in the packet to do a recursive lookup. This is used when sending a name query to a machine running a WINS server and the user wishes to query the names in the WINS server. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead. See RFC1001, RFC1002 for details. -

    -S

    Once the name query has returned an IP +

    -S

    Once the name query has returned an IP address then do a node status query as well. A node status query returns the NetBIOS names registered by a host. -

    -r

    Try and bind to UDP port 137 to send and receive UDP +

    -r

    Try and bind to UDP port 137 to send and receive UDP datagrams. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and - in addition, if the nmbd(8) daemon is running on this machine it also binds to this port. -

    -A

    Interpret name as - an IP Address and do a node status query on this address.

    -n <primary NetBIOS name>

    This option allows you to override + in addition, if the nmbd(8) daemon is running on this machine it also binds to this port. +

    -A

    Interpret name as + an IP Address and do a node status query on this address.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command line setting will take precedence over settings in -smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that -nmblookup will use to communicate with when +smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that +nmblookup will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -very rarely used, only set this parameter +very rarely used, only set this parameter if you are the system administrator in charge of all the -NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This +NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This overrides the default domain which is the domain defined in smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client +SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client socket. See the socket options parameter in -the smb.conf(5) manual page for the list of valid -options.

    -h|--help

    Print a summary of command line options.

    -B <broadcast address>

    Send the query to the given broadcast address. Without +the smb.conf(5) manual page for the list of valid +options.

    -h|--help

    Print a summary of command line options. +

    -B <broadcast address>

    Send the query to the given broadcast address. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as - either auto-detected or defined in the interfaces - parameter of the smb.conf(5) file. -

    -U <unicast address>

    Do a unicast query to the specified address or - host unicast address. This option - (along with the -R option) is needed to - query a WINS server.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + either auto-detected or defined in the interfaces + parameter of the smb.conf(5) file. +

    -U <unicast address>

    Do a unicast query to the specified address or + host unicast address. This option + (along with the -R option) is needed to + query a WINS server.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -T

    This causes any IP addresses found in the +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -T

    This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a - DNS name, and printed out before each

    IP address .... NetBIOS name

    pair that is the normal output.

    -f

    Show which flags apply to the name that has been looked up. Possible + DNS name, and printed out before each

    IP address .... NetBIOS name

    pair that is the normal output.

    -f

    + Show which flags apply to the name that has been looked up. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast. -

    name

    This is the NetBIOS name being queried. Depending +

    name

    This is the NetBIOS name being queried. Depending upon the previous options this may be a NetBIOS name or IP address. If a NetBIOS name then the different name types may be specified - by appending '#<type>' to the name. This name may also be + by appending '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast - area.

    EXAMPLES

    nmblookup can be used to query - a WINS server (in the same way nslookup is - used to query DNS servers). To query a WINS server, nmblookup - must be called like this:

    nmblookup -U server -R 'name'

    For example, running :

    nmblookup -U samba.org -R 'IRIX#1B'

    would query the WINS server samba.org for the domain - master browser (1B name type) for the IRIX workgroup.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    nmbd(8), samba(7), and smb.conf(5).

    AUTHOR

    The original Samba software and related utilities + area.

    EXAMPLES

    nmblookup can be used to query + a WINS server (in the same way nslookup is + used to query DNS servers). To query a WINS server, nmblookup + must be called like this:

    nmblookup -U server -R 'name'

    For example, running :

    nmblookup -U samba.org -R 'IRIX#1B'

    would query the WINS server samba.org for the domain + master browser (1B name type) for the IRIX workgroup.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    nmbd(8), samba(7), and smb.conf(5).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/ntlm_auth.1.html b/docs/htmldocs/ntlm_auth.1.html index 95558aae38..956f30641d 100644 --- a/docs/htmldocs/ntlm_auth.1.html +++ b/docs/htmldocs/ntlm_auth.1.html @@ -1,261 +1,45 @@ - -ntlm_auth

    ntlm_auth

    Name

    ntlm_auth -- tool to allow external access to Winbind's NTLM authentication function

    Synopsis

    ntlm_auth [-d debuglevel] [-l logfile] [-s <smb config file>]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    ntlm_auth is a helper utility that authenticates +ntlm_auth

    Name

    ntlm_auth — tool to allow external access to Winbind's NTLM authentication function

    Synopsis

    ntlm_auth [-d debuglevel] [-l logfile] [-s <smb config file>]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    ntlm_auth is a helper utility that authenticates users using NT/LM authentication. It returns 0 if the users is authenticated successfully and 1 if access was denied. ntlm_auth uses winbind to access the user and authentication data for a domain. This utility is only to be used by other programs (currently squid). -

    OPTIONS

    --helper-protocol=PROTO

    Operate as a stdio-based helper -

    --username=USERNAME

    Specify username of user to authenticate -

    --domain=DOMAIN

    Specify domain of user to authenticate -

    --workstation=WORKSTATION

    Specify the workstation the user authenticated from -

    --challenge=STRING

    challenge (HEX encoded)

    --lm-response=RESPONSE

    LM Response to the challenge (HEX encoded)

    --nt-response=RESPONSE

    NT or NTLMv2 Response to the challenge (HEX encoded)

    --password=PASSWORD

    User's plaintext password

    --request-lm-key

    Retreive LM session key

    --request-nt-key

    Request NT key

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    OPTIONS

    --helper-protocol=PROTO

    + Operate as a stdio-based helper +

    --username=USERNAME

    + Specify username of user to authenticate +

    --domain=DOMAIN

    + Specify domain of user to authenticate +

    --workstation=WORKSTATION

    + Specify the workstation the user authenticated from +

    --challenge=STRING

    challenge (HEX encoded)

    --lm-response=RESPONSE

    LM Response to the challenge (HEX encoded)

    --nt-response=RESPONSE

    NT or NTLMv2 Response to the challenge (HEX encoded)

    --password=PASSWORD

    User's plaintext password

    --request-lm-key

    Retreive LM session key

    --request-nt-key

    Request NT key

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -h|--help

    Print a summary of command line options.

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -h|--help

    Print a summary of command line options. +

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The ntlm_auth manpage was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The ntlm_auth manpage was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/optional.html b/docs/htmldocs/optional.html index f719cf4a8c..33f7a02b7c 100644 --- a/docs/htmldocs/optional.html +++ b/docs/htmldocs/optional.html @@ -1,150 +1,7 @@ - -Advanced Configuration
    SAMBA Project Documentation
    PrevNext

    III. Advanced Configuration

    Introduction

    Samba has several features that you might want or might not want to use. The chapters in this part each cover one specific feature.

    PrevHomeNext
    Samba as a NT4 or Win2k domain member UNIX Permission Bits and Windows NT Access Control Lists
    \ No newline at end of file + +PartIII.Advanced Configuration
    PartIII.Advanced Configuration
    PrevNext

    Advanced Configuration

    Valuable Nuts and Bolts Information

    +Samba has several features that you might want or might not want to use. The chapters in this part each cover specific Samba features. +

    Table of Contents

    9. Samba / MS Windows Network Browsing Guide
    What is Browsing?
    Discussion
    How Browsing Functions
    Setting up WORKGROUP Browsing
    Setting up DOMAIN Browsing
    Forcing samba to be the master
    Making samba the domain master
    Note about broadcast addresses
    Multiple interfaces
    Use of the Remote Announce parameter
    Use of the Remote Browse Sync parameter
    WINS - The Windows Internetworking Name Server
    Setting up a WINS server
    WINS Replication
    Static WINS Entries
    Helpful Hints
    Windows Networking Protocols
    Name Resolution Order
    Technical Overview of browsing
    Browsing support in samba
    Problem resolution
    Browsing across subnets
    10. User information database
    Introduction
    Important Notes About Security
    Advantages of SMB Encryption
    Advantages of non-encrypted passwords
    The smbpasswd Command
    Plain text
    TDB
    LDAP
    Introduction
    Encrypted Password Database
    Supported LDAP Servers
    Schema and Relationship to the RFC 2307 posixAccount
    Configuring Samba with LDAP
    Accounts and Groups management
    Security and sambaAccount
    LDAP specials attributes for sambaAccounts
    Example LDIF Entries for a sambaAccount
    MySQL
    Creating the database
    Configuring
    Using plaintext passwords or encrypted password
    Getting non-column data from the table
    XML
    11. UNIX Permission Bits and Windows NT Access Control Lists
    Viewing and changing UNIX permissions using the NT + security dialogs
    How to view file security on a Samba share
    Viewing file ownership
    Viewing file or directory permissions
    File Permissions
    Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute + mapping
    12. Configuring Group Mapping
    13. Printing Support
    Introduction
    Configuration
    Creating [print$]
    Setting Drivers for Existing Printers
    Support a large number of printers
    Adding New Printers via the Windows NT APW
    Samba and Printer Ports
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints server
    The Installation Client
    Diagnosis
    Introduction
    Debugging printer problems
    What printers do I have?
    Setting up printcap and print servers
    Job sent, no output
    Job sent, strange output
    Raw PostScript printed
    Advanced Printing
    Real debugging
    14. CUPS Printing Support
    Introduction
    Configuring smb.conf for CUPS
    CUPS - RAW Print Through Mode
    CUPS as a network PostScript RIP
    Windows Terminal Servers (WTS) as CUPS clients
    Setting up CUPS for driver download
    Sources of CUPS drivers / PPDs
    cupsaddsmb
    The CUPS Filter Chains
    CUPS Print Drivers and Devices
    Further printing steps
    Limiting the number of pages users can print
    Advanced Postscript Printing from MS Windows
    Auto-Deletion of CUPS spool files
    15. Unified Logons between Windows NT and UNIX using Winbind
    Abstract
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Limitations
    Conclusion
    16. Advanced Network Manangement
    Configuring Samba Share Access Controls
    Share Permissions Management
    Remote Server Administration
    Network Logon Script Magic
    Adding printers without user intervention
    17. System and Account Policies
    Creating and Managing System Policies
    Windows 9x/Me Policies
    Windows NT4 Style Policy Files
    MS Windows 200x / XP Professional Policies
    Managing Account/User Policies
    With Windows NT4/200x
    With a Samba PDC
    System Startup and Logon Processing Overview
    18. Desktop Profile Management
    Roaming Profiles
    Samba Configuration for Profile Handling
    Windows Client Profile Configuration Information
    Sharing Profiles between W9x/Me and NT4/200x/XP workstations
    Profile Migration from Windows NT4/200x Server to Samba
    Mandatory profiles
    Creating/Managing Group Profiles
    Default Profile for Windows Users
    MS Windows 9x/Me
    MS Windows NT4 Workstation
    MS Windows 200x/XP
    19. Interdomain Trust Relationships
    Trust Relationship Background
    Native MS Windows NT4 Trusts Configuration
    NT4 as the Trusting Domain (ie. creating the trusted account)
    NT4 as the Trusted Domain (ie. creating trusted account's password)
    Configuring Samba NT-style Domain Trusts
    Samba-3 as the Trusting Domain
    Samba-3 as the Trusted Domain
    20. PAM Configuration for Centrally Managed Authentication
    Samba and PAM
    PAM Configuration in smb.conf
    Password Synchronisation using pam_smbpass.so
    Distributed Authentication
    21. Stackable VFS modules
    Introduction and configuration
    Included modules
    audit
    extd_audit
    recycle
    netatalk
    VFS modules available elsewhere
    DatabaseFS
    vscan
    22. Hosting a Microsoft Distributed File System tree on Samba
    Instructions
    Notes
    23. Integrating MS Windows networks with Samba
    Name Resolution in a pure Unix/Linux world
    /etc/hosts
    /etc/resolv.conf
    /etc/host.conf
    /etc/nsswitch.conf
    Name resolution as used within MS Windows networking
    The NetBIOS Name Cache
    The LMHOSTS file
    HOSTS file
    DNS Lookup
    WINS Lookup
    24. Securing Samba
    Introduction
    Using host based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba
    25. Unicode/Charsets
    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets
    26. File and Record Locking
    Discussion
    Samba Opportunistic Locking Control
    MS Windows Opportunistic Locking and Caching Controls
    Workstation Service Entries
    Server Service Entries
    Persistent Data Corruption
    Additional Reading
    PrevUpNext
    Chapter8.Samba as a NT4 or Win2k domain memberHomeChapter9.Samba / MS Windows Network Browsing Guide
    diff --git a/docs/htmldocs/pam.html b/docs/htmldocs/pam.html index 2b284dd929..f8624e94c5 100644 --- a/docs/htmldocs/pam.html +++ b/docs/htmldocs/pam.html @@ -1,201 +1,37 @@ - -PAM Configuration for Centrally Managed Authentication
    SAMBA Project Documentation
    PrevNext

    Chapter 20. PAM Configuration for Centrally Managed Authentication

    20.1. Samba and PAM

    A number of Unix systems (eg: Sun Solaris), as well as the + +Chapter20.PAM Configuration for Centrally Managed Authentication

    Chapter20.PAM Configuration for Centrally Managed Authentication
    PrevPartIII.Advanced ConfigurationNext

    Chapter20.PAM Configuration for Centrally Managed Authentication

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    (Jun 21 2001)

    Table of Contents

    Samba and PAM
    PAM Configuration in smb.conf
    Password Synchronisation using pam_smbpass.so
    Distributed Authentication

    Samba and PAM

    +A number of Unix systems (eg: Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, authorization and resource control services. Prior to the introduction of PAM, a decision to use an alternative to -the system password database (/etc/passwd) +the system password database (/etc/passwd) would require the provision of alternatives for all programs that provide security services. Such a choice would involve provision of -alternatives to such programs as: login, -passwd, chown, etc.

    PAM provides a mechanism that disconnects these security programs +alternatives to such programs as: login, +passwd, chown, etc. +

    +PAM provides a mechanism that disconnects these security programs from the underlying authentication/authorization infrastructure. -PAM is configured either through one file /etc/pam.conf (Solaris), -or by editing individual files that are located in /etc/pam.d.

    If the PAM authentication module (loadable link library file) is located in the +PAM is configured either through one file /etc/pam.conf (Solaris), +or by editing individual files that are located in /etc/pam.d. +

    Note

    + If the PAM authentication module (loadable link library file) is located in the default location then it is not necessary to specify the path. In the case of - Linux, the default location is /lib/security. If the module - is located other than default then the path may be specified as: + Linux, the default location is /lib/security. If the module + is located outside the default then the path must be specified as: - 

    	auth       required      /other_path/pam_strange_module.so
-
    -

    The following is an example /etc/pam.d/login configuration file. + 

    +	auth       required      /other_path/pam_strange_module.so
+

    +

    +The following is an example /etc/pam.d/login configuration file. This example had all options been uncommented is probably not usable as it stacks many conditions before allowing successful completion of the login process. Essentially all conditions can be disabled -by commenting them out except the calls to pam_pwdb.so.

    	#%PAM-1.0
+by commenting them out except the calls to pam_pwdb.so.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `login' service
 	#
 	auth 		required	pam_securetty.so
@@ -208,22 +44,13 @@ CLASS="PROGRAMLISTING"
 	session		required	pam_pwdb.so
 	# session 	optional	pam_lastlog.so
 	# password   	required   	pam_cracklib.so retry=3
-	password	required	pam_pwdb.so shadow md5
    PAM allows use of replacable modules. Those available on a 
-sample system include:
    $/bin/ls /lib/security
-
    	pam_access.so    pam_ftp.so          pam_limits.so     
+	password	required	pam_pwdb.so shadow md5
+
    
+PAM allows use of replacable modules. Those available on a 
+sample system include:
+
    $/bin/ls /lib/security
+
    +	pam_access.so    pam_ftp.so          pam_limits.so     
 	pam_ncp_auth.so  pam_rhosts_auth.so  pam_stress.so     
 	pam_cracklib.so  pam_group.so        pam_listfile.so   
 	pam_nologin.so   pam_rootok.so       pam_tally.so      
@@ -234,283 +61,220 @@ CLASS="PROGRAMLISTING"
 	pam_env.so       pam_ldap.so         pam_motd.so       
 	pam_radius.so    pam_smbpass.so      pam_unix_acct.so  
 	pam_wheel.so     pam_unix_auth.so    pam_unix_passwd.so
-	pam_userdb.so    pam_warn.so         pam_unix_session.so
    The following example for the login program replaces the use of 
-the pam_pwdb.so module which uses the system 
-password database (/etc/passwd,
-/etc/shadow, /etc/group) with 
-the module pam_smbpass.so which uses the Samba 
+	pam_userdb.so    pam_warn.so         pam_unix_session.so
+

    +The following example for the login program replaces the use of +the pam_pwdb.so module which uses the system +password database (/etc/passwd, +/etc/shadow, /etc/group) with +the module pam_smbpass.so which uses the Samba database which contains the Microsoft MD4 encrypted password hashes. This database is stored in either -/usr/local/samba/private/smbpasswd, -/etc/samba/smbpasswd, or in -/etc/samba.d/smbpasswd, depending on the +/usr/local/samba/private/smbpasswd, +/etc/samba/smbpasswd, or in +/etc/samba.d/smbpasswd, depending on the Samba implementation for your Unix/Linux system. The -pam_smbpass.so module is provided by +pam_smbpass.so module is provided by Samba version 2.2.1 or later. It can be compiled by specifying the ---with-pam_smbpass options when running Samba's -configure script. For more information -on the pam_smbpass module, see the documentation -in the source/pam_smbpass directory of the Samba -source distribution.

    	#%PAM-1.0
+--with-pam_smbpass options when running Samba's
+configure script.  For more information
+on the pam_smbpass module, see the documentation
+in the source/pam_smbpass directory of the Samba 
+source distribution.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `login' service
 	#
 	auth		required	pam_smbpass.so nodelay
 	account		required	pam_smbpass.so nodelay
 	session		required	pam_smbpass.so nodelay
-	password	required	pam_smbpass.so nodelay
    The following is the PAM configuration file for a particular 
-Linux system. The default condition uses pam_pwdb.so.
    	#%PAM-1.0
+	password	required	pam_smbpass.so nodelay
+
    
+The following is the PAM configuration file for a particular 
+Linux system. The default condition uses pam_pwdb.so.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `samba' service
 	#
 	auth       required     pam_pwdb.so nullok nodelay shadow audit
 	account    required     pam_pwdb.so audit nodelay
 	session    required     pam_pwdb.so nodelay
-	password   required     pam_pwdb.so shadow md5
    In the following example the decision has been made to use the 
+	password   required     pam_pwdb.so shadow md5
+

    +In the following example the decision has been made to use the smbpasswd database even for basic samba authentication. Such a decision could also be made for the passwd program and would thus allow the smbpasswd passwords to be changed using the passwd -program.

    	#%PAM-1.0
+program.
+
    +	#%PAM-1.0
 	# The PAM configuration file for the `samba' service
 	#
 	auth       required     pam_smbpass.so nodelay
 	account    required     pam_pwdb.so audit nodelay
 	session    required     pam_pwdb.so nodelay
-	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
    PAM allows stacking of authentication mechanisms. It is 
+	password   required     pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
+
    Note
    PAM allows stacking of authentication mechanisms. It is 
 also possible to pass information obtained within one PAM module through 
 to the next module in the PAM stack. Please refer to the documentation for 
 your particular system implementation for details regarding the specific 
 capabilities of PAM in this environment. Some Linux implmentations also 
-provide the pam_stack.so module that allows all 
+provide the pam_stack.so module that allows all 
 authentication to be configured in a single central file. The 
-pam_stack.so method has some very devoted followers 
+pam_stack.so method has some very devoted followers 
 on the basis that it allows for easier administration. As with all issues in 
 life though, every decision makes trade-offs, so you may want examine the 
-PAM documentation for further helpful information.

    20.2. Distributed Authentication

    The astute administrator will realize from this that the -combination of pam_smbpass.so, -winbindd, and a distributed -passdb backend, such as ldap, will allow the establishment of a -centrally managed, distributed -user/password database that can also be used by all -PAM (eg: Linux) aware programs and applications. This arrangement -can have particularly potent advantages compared with the -use of Microsoft Active Directory Service (ADS) in so far as -reduction of wide area network authentication traffic.

    20.3. PAM Configuration in smb.conf

    There is an option in smb.conf called obey pam restrictions. -The following is from the on-line help for this option in SWAT;

    When Samba is configured to enable PAM support (i.e. ---with-pam), this parameter will +PAM documentation for further helpful information. +

    PAM Configuration in smb.conf

    +There is an option in smb.conf called obey pam restrictions. +The following is from the on-line help for this option in SWAT; +

    +When Samba is configured to enable PAM support (i.e. +--with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of -encrypt passwords = yes. +encrypt passwords = yes. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB -password encryption.

    Default: obey pam restrictions = no

    PrevHomeNext
    Interdomain Trust RelationshipsUpStackable VFS modules
    \ No newline at end of file +password encryption. +

    Default: obey pam restrictions = no

    Password Synchronisation using pam_smbpass.so

    +pam_smbpass is a PAM module which can be used on conforming systems to +keep the smbpasswd (Samba password) database in sync with the unix +password file. PAM (Pluggable Authentication Modules) is an API supported +under some Unices, such as Solaris, HPUX and Linux, that provides a +generic interface to authentication mechanisms. +

    +For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/ +

    +This module authenticates a local smbpasswd user database. If you require +support for authenticating against a remote SMB server, or if you're +concerned about the presence of suid root binaries on your system, it is +recommended that you use pam_winbind instead. +

    +Options recognized by this module are as follows:
+
+        debug           -       log more debugging info
+        audit           -       like debug, but also logs unknown usernames
+        use_first_pass  -       don't prompt the user for passwords;
+                                take them from PAM_ items instead
+        try_first_pass  -       try to get the password from a previous
+                                PAM module, fall back to prompting the user
+        use_authtok     -       like try_first_pass, but *fail* if the new
+                                PAM_AUTHTOK has not been previously set.
+                                (intended for stacking password modules only)
+        not_set_pass    -       don't make passwords used by this module
+                                available to other modules.
+        nodelay         -       don't insert ~1 second delays on authentication
+                                failure.
+        nullok          -       null passwords are allowed.
+        nonull          -       null passwords are not allowed. Used to
+                                override the Samba configuration.
+        migrate         -       only meaningful in an "auth" context;
+                                used to update smbpasswd file with a
+                                password used for successful authentication.
+        smbconf=< file >  -     specify an alternate path to the smb.conf
+                                file.
+
    +Thanks go to the following people:
+
+	* Andrew Morgan < morgan@transmeta.com >, for providing the Linux-PAM
+	framework, without which none of this would have happened
+
+	* Christian Gafton < gafton@redhat.com > and Andrew Morgan again, for the
+	pam_pwdb module upon which pam_smbpass was originally based
+
+	* Luke Leighton < lkcl@switchboard.net > for being receptive to the idea,
+	and for the occasional good-natured complaint about the project's status
+	that keep me working on it :)
+
+	* and of course, all the other members of the Samba team
+	<http://www.samba.org/samba/team.html>, for creating a great product
+	and for giving this project a purpose
+
+	---------------------
+	Stephen Langasek < vorlon@netexpress.net >
+

    +The following are examples of the use of pam_smbpass.so in the format of Linux +/etc/pam.d/ files structure. Those wishing to implement this +tool on other platforms will need to adapt this appropriately. +

    Password Synchonisation Configuration

    +A sample PAM configuration that shows the use of pam_smbpass to make +sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow) +is changed. Useful when an expired password might be changed by an +application (such as ssh). +

    +	#%PAM-1.0
+	# password-sync
+	#
+	auth       requisite        pam_nologin.so
+	auth       required         pam_unix.so
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   required         pam_smbpass.so nullok use_authtok try_first_pass
+	session    required         pam_unix.so
+

    Password Migration Configuration

    +A sample PAM configuration that shows the use of pam_smbpass to migrate +from plaintext to encrypted passwords for Samba. Unlike other methods, +this can be used for users who have never connected to Samba shares: +password migration takes place when users ftp in, login using ssh, pop +their mail, etc. +

    +	#%PAM-1.0
+	# password-migration
+	#
+	auth       requisite        pam_nologin.so
+	# pam_smbpass is called IFF pam_unix succeeds.
+	auth       requisite        pam_unix.so
+	auth       optional         pam_smbpass.so migrate
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   optional         pam_smbpass.so nullok use_authtok try_first_pass
+	session    required         pam_unix.so
+

    Mature Password Configuration

    +A sample PAM configuration for a 'mature' smbpasswd installation. +private/smbpasswd is fully populated, and we consider it an error if +the smbpasswd doesn't exist or doesn't match the Unix password. +

    +	#%PAM-1.0
+	# password-mature
+	#
+	auth       requisite        pam_nologin.so
+	auth       required         pam_unix.so
+	account    required         pam_unix.so
+	password   requisite        pam_cracklib.so retry=3
+	password   requisite        pam_unix.so shadow md5 use_authtok try_first_pass
+	password   required         pam_smbpass.so use_authtok use_first_pass
+	session    required         pam_unix.so
+

    Kerberos Password Integration Configuration

    +A sample PAM configuration that shows pam_smbpass used together with +pam_krb5. This could be useful on a Samba PDC that is also a member of +a Kerberos realm. +

    +	#%PAM-1.0
+	# kdc-pdc
+	#
+	auth       requisite        pam_nologin.so
+	auth       requisite        pam_krb5.so
+	auth       optional         pam_smbpass.so migrate
+	account    required         pam_krb5.so
+	password   requisite        pam_cracklib.so retry=3
+	password   optional         pam_smbpass.so nullok use_authtok try_first_pass
+	password   required         pam_krb5.so use_authtok try_first_pass
+	session    required         pam_krb5.so
+

    Distributed Authentication

    +The astute administrator will realize from this that the +combination of pam_smbpass.so, +winbindd, and a distributed +passdb backend, such as ldap, will allow the establishment of a +centrally managed, distributed +user/password database that can also be used by all +PAM (eg: Linux) aware programs and applications. This arrangement +can have particularly potent advantages compared with the +use of Microsoft Active Directory Service (ADS) in so far as +reduction of wide area network authentication traffic. +

    PrevUpNext
    Chapter19.Interdomain Trust RelationshipsHomeChapter21.Stackable VFS modules
    diff --git a/docs/htmldocs/passdb.html b/docs/htmldocs/passdb.html index 7151610a63..9f313ee123 100644 --- a/docs/htmldocs/passdb.html +++ b/docs/htmldocs/passdb.html @@ -1,962 +1,214 @@ - -User information database
    SAMBA Project Documentation
    PrevNext

    Chapter 4. User information database

    4.1. Introduction

    Old windows clients send plain text passwords over the wire. + +Chapter10.User information database

    Chapter10.User information database
    PrevPartIII.Advanced ConfigurationNext

    Chapter10.User information database

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Olivier (lem) Lemaire

    IDEALX

    <olem@IDEALX.org>

    February 2003

    Table of Contents

    Introduction
    Important Notes About Security
    Advantages of SMB Encryption
    Advantages of non-encrypted passwords
    The smbpasswd Command
    Plain text
    TDB
    LDAP
    Introduction
    Encrypted Password Database
    Supported LDAP Servers
    Schema and Relationship to the RFC 2307 posixAccount
    Configuring Samba with LDAP
    Accounts and Groups management
    Security and sambaAccount
    LDAP specials attributes for sambaAccounts
    Example LDIF Entries for a sambaAccount
    MySQL
    Creating the database
    Configuring
    Using plaintext passwords or encrypted password
    Getting non-column data from the table
    XML

    Introduction

    Old windows clients send plain text passwords over the wire. Samba can check these passwords by crypting them and comparing them to the hash stored in the unix user database. -

    Newer windows clients send encrypted passwords (so-called +

    + Newer windows clients send encrypted passwords (so-called Lanman and NT hashes) over the wire, instead of plain text passwords. The newest clients will only send encrypted passwords and refuse to send plain text passwords, unless their registry is tweaked. -

    These passwords can't be converted to unix style encrypted +

    These passwords can't be converted to unix style encrypted passwords. Because of that you can't use the standard unix user database, and you have to store the Lanman and NT hashes - somewhere else.

    Next to a differently encrypted passwords, + somewhere else.

    Next to a differently encrypted passwords, windows also stores certain data for each user that is not stored in a unix user database, e.g. workstations the user may logon from, the location where his/her profile is stored, etc. - Samba retrieves and stores this information using a "passdb backend". + Samba retrieves and stores this information using a "passdb backend". Commonly available backends are LDAP, plain text file, MySQL and nisplus. For more information, see the documentation about the - passdb backend = parameter. -

    4.2. Important Notes About Security

    The unix and SMB password encryption techniques seem similar + passdb backend = parameter. +

    Important Notes About Security

    The unix and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The unix scheme typically sends clear text passwords over the network when logging in. This is bad. The SMB encryption scheme never sends the cleartext password over the network but it does store the 16 byte hashed values on disk. This is also bad. Why? Because the 16 byte hashed - values are a "password equivalent". You cannot derive the user's + values are a "password equivalent". You cannot derive the user's password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. You should thus treat the data stored in whatever passdb backend you use (smbpasswd file, ldap, mysql) as though it contained the cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.

    Ideally we would like a password scheme which neither requires + secret, and the file should be protected accordingly.

    Ideally we would like a password scheme which neither requires plain text passwords on the net or on disk. Unfortunately this is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc).

    Note that Windows NT 4.0 Service pack 3 changed the + other SMB systems (WinNT, WfWg, Win95 etc).

    Warning

    Note that Windows NT 4.0 Service pack 3 changed the default for permissible authentication so that plaintext - passwords are never sent over the wire. + passwords are never sent over the wire. The solution to this is either to switch to encrypted passwords with Samba or edit the Windows NT registry to re-enable plaintext passwords. See the document WinNT.txt for details on how to do - this.

    Other Microsoft operating systems which also exhibit - this behavior includes

    These versions of MS Windows do not support full domain + this.

    Other Microsoft operating systems which also exhibit + this behavior includes

    These versions of MS Windows do not support full domain security protocols, although they may log onto a domain environment. - Of these Only MS Windows XP Home does NOT support domain logons.

    MS DOS Network client 3.0 with - the basic network redirector installed
    Windows 95 with the network redirector - update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain - security protocols.

    Windows NT 3.5x
    Windows NT 4.0
    Windows 2000 Professional
    Windows 200x Server/Advanced Server
    Windows XP Professional

    All current release of + Of these Only MS Windows XP Home does NOT support domain logons.

    MS DOS Network client 3.0 with + the basic network redirector installed
    Windows 95 with the network redirector + update installed
    Windows 98 [se]
    Windows Me
    Windows XP Home

    The following versions of MS Windows fully support domain + security protocols.

    Windows NT 3.5x
    Windows NT 4.0
    Windows 2000 Professional
    Windows 200x Server/Advanced Server
    Windows XP Professional

    Note

    All current release of Microsoft SMB/CIFS clients support authentication via the SMB Challenge/Response mechanism described here. Enabling clear text authentication does not disable the ability - of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. + of the client to participate in encrypted authentication.

    MS Windows clients will cache the encrypted password alone. Even when plain text passwords are re-enabled, through the appropriate registry change, the plain text password is NEVER cached. This means that in the event that a network connections should become disconnected (broken) only the cached (encrypted) password will be sent to the resource server to affect a auto-reconnect. If the resource server does not support encrypted - passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS - IS STRONGLY ADVISED.

    4.2.1. Advantages of SMB Encryption

    Plain text passwords are not passed across + passwords the auto-reconnect will fail. USE OF ENCRYPTED PASSWORDS + IS STRONGLY ADVISED.

    Advantages of SMB Encryption

    Plain text passwords are not passed across the network. Someone using a network sniffer cannot just - record passwords going to the SMB server.
    WinNT doesn't like talking to a server - that SM not support encrypted passwords. It will refuse + record passwords going to the SMB server.
    WinNT doesn't like talking to a server + that does not support encrypted passwords. It will refuse to browse the server if the server is also in user level security mode. It will insist on prompting the user for the password on each connection, which is very annoying. The only things you can do to stop this is to use SMB encryption. -
    Encrypted password support allows automatic share - (resource) reconnects.

    4.2.2. Advantages of non-encrypted passwords

    Plain text passwords are not kept - on disk, and are NOT cached in memory.
    Uses same password file as other unix - services such as login and ftp
    Use of other services (such as telnet and ftp) which +
    Encrypted password support allows automatic share + (resource) reconnects.

    Advantages of non-encrypted passwords

    Plain text passwords are not kept + on disk, and are NOT cached in memory.
    Uses same password file as other unix + services such as login and ftp
    Use of other services (such as telnet and ftp) which send plain text passwords over the net, so sending them for SMB - isn't such a big deal.

    4.3. The smbpasswd Command

    The smbpasswd utility is a utility similar to the - passwd or yppasswd programs. - It maintains the two 32 byte password fields in the passdb backend.

    smbpasswd works in a client-server mode + isn't such a big deal.

    The smbpasswd Command

    The smbpasswd utility is a utility similar to the + passwd or yppasswd programs. + It maintains the two 32 byte password fields in the passdb backend.

    smbpasswd works in a client-server mode where it contacts the local smbd to change the user's password on its - behalf. This has enormous benefits - as follows.

    smbpasswd has the capability + behalf. This has enormous benefits - as follows.

    smbpasswd has the capability to change passwords on Windows NT servers (this only works when the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).

    To run smbpasswd as a normal user just type :

    $ smbpasswd

    Old SMB password: <type old value here - - or hit return if there was no old password>

    New SMB Password: <type new value> -

    Repeat New SMB Password: <re-type new value -

    If the old value does not match the current value stored for + are changing an NT Domain user's password).

    To run smbpasswd as a normal user just type :

    $ smbpasswd

    Old SMB password: <type old value here - + or hit return if there was no old password>

    New SMB Password: <type new value> +

    Repeat New SMB Password: <re-type new value +

    If the old value does not match the current value stored for that user, or the two new values do not match each other, then the - password will not be changed.

    If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.

    If run by the root user smbpasswd may take an optional + password will not be changed.

    If invoked by an ordinary user it will only allow the user + to change his or her own Samba password.

    If run by the root user smbpasswd may take an optional argument, specifying the user name whose SMB password you wish to change. Note that when run as root smbpasswd does not prompt for or check the old password value, thus allowing root to set passwords - for users who have forgotten their passwords.

    smbpasswd is designed to work in the same way - and be familiar to UNIX users who use the passwd or - yppasswd commands.

    For more details on using smbpasswd refer - to the man page which will always be the definitive reference.

    4.4. Plain text

    Older versions of samba retrieved user information from the unix user database -and eventually some other fields from the file /etc/samba/smbpasswd -or /etc/smbpasswd. When password encryption is disabled, no -data is stored at all.

    4.5. TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend -doesn't require any additional configuration. This backend is recommended for new installations who -don't require LDAP.

    4.6. LDAP

    4.6.1. Introduction

    This document describes how to use an LDAP directory for storing Samba user + for users who have forgotten their passwords.

    smbpasswd is designed to work in the same way + and be familiar to UNIX users who use the passwd or + yppasswd commands.

    For more details on using smbpasswd refer + to the man page which will always be the definitive reference.

    Plain text

    +Older versions of samba retrieved user information from the unix user database +and eventually some other fields from the file /etc/samba/smbpasswd +or /etc/smbpasswd. When password encryption is disabled, no +data is stored at all. +

    TDB

    Samba can also store the user data in a "TDB" (Trivial Database). Using this backend +doesn't require any additional configuration. This backend is recommended for new installations that +don not require LDAP. +

    LDAP

    Introduction

    +This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is assumed that the reader already has a basic understanding of LDAP concepts and has a working directory server already installed. For more information -on LDAP architectures and Directories, please refer to the following sites.

    Note that O'Reilly Publishing is working on +on LDAP architectures and Directories, please refer to the following sites. +

    +Note that O'Reilly Publishing is working on a guide to LDAP for System Administrators which has a planned release date of -early summer, 2002.

    Two additional Samba resources which may prove to be helpful are

    • The Samba-PDC-LDAP-HOWTO - maintained by Ignacio Coupeau.

    • The NT migration scripts from IDEALX that are +early summer, 2002. +

      +Two additional Samba resources which may prove to be helpful are +

      • The Samba-PDC-LDAP-HOWTO + maintained by Ignacio Coupeau.

      • The NT migration scripts from IDEALX that are geared to manage users and group in such a Samba-LDAP Domain Controller configuration. -

      4.6.2. Introduction

      Traditionally, when configuring "encrypt -passwords = yes" in Samba's smb.conf file, user account +

    Encrypted Password Database

    +Traditionally, when configuring "encrypt +passwords = yes" in Samba's smb.conf file, user account information such as username, LM/NT password hashes, password change times, and account -flags have been stored in the smbpasswd(5) file. There are several +flags have been stored in the smbpasswd(5) file. There are several disadvantages to this approach for sites with very large numbers of users (counted -in the thousands).

    • The first is that all lookups must be performed sequentially. Given that +in the thousands). +

      • +The first is that all lookups must be performed sequentially. Given that there are approximately two lookups per domain logon (one for a normal session connection such as when mapping a network drive or printer), this -is a performance bottleneck for lareg sites. What is needed is an indexed approach -such as is used in databases.

      • The second problem is that administrators who desired to replicate a +is a performance bottleneck for large sites. What is needed is an indexed approach +such as is used in databases. +

      • +The second problem is that administrators who desired to replicate a smbpasswd file to more than one Samba server were left to use external -tools such as rsync(1) and ssh(1) -and wrote custom, in-house scripts.

      • And finally, the amount of information which is stored in an +tools such as rsync(1) and ssh(1) +and wrote custom, in-house scripts. +

      • +And finally, the amount of information which is stored in an smbpasswd entry leaves no room for additional attributes such as a home directory, password expiration time, or even a Relative -Identified (RID).

      As a result of these defeciencies, a more robust means of storing user attributes +Identified (RID). +

    +As a result of these defeciencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees).

    There are a few points to stress about what the ldapsam +API, and is still so named in the CVS trees). +

    +There are a few points to stress about that the ldapsam does not provide. The LDAP support referred to in the this documentation does not -include:

    • A means of retrieving user account information from - an Windows 2000 Active Directory server.

    • A means of replacing /etc/passwd.

    The second item can be accomplished by using LDAP NSS and PAM modules. LGPL +include: +

    • A means of retrieving user account information from + an Windows 2000 Active Directory server.

    • A means of replacing /etc/passwd.

    +The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from PADL Software -(http://www.padl.com/). However, -the details of configuring these packages are beyond the scope of this document.

    4.6.3. Supported LDAP Servers

    The LDAP samdb code in 2.2.3 (and later) has been developed and tested +(http://www.padl.com/). More +information about the configuration of these packages may be found at "LDAP, +System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS". +

    Supported LDAP Servers

    +The LDAP samdb code in 2.2.3 (and later) has been developed and tested using the OpenLDAP 2.0 server and client libraries. The same code should be able to work with Netscape's Directory Server and client SDK. However, due to lack of testing so far, there are bound to be compile errors and bugs. These should not be hard to fix. If you are so inclined, please be sure to forward all patches to -samba-patches@samba.org and -jerry@samba.org.

    4.6.4. Schema and Relationship to the RFC 2307 posixAccount

    Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in -examples/LDAP/samba.schema. The sambaAccount objectclass is given here:

    objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top STRUCTURAL
+samba-patches@samba.org and
+jerry@samba.org.
+

    Schema and Relationship to the RFC 2307 posixAccount

    +Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in +examples/LDAP/samba.schema. The sambaAccount objectclass is given here: +

    +objectclass ( 1.3.1.5.1.4.1.7165.2.2.2 NAME 'sambaAccount' SUP top AUXILIARY
      DESC 'Samba Account'
      MUST ( uid $ rid )
      MAY  ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
             logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
             displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
-            description $ userWorkstations $ primaryGroupID $ domain ))

    The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are + description $ userWorkstations $ primaryGroupID $ domain )) +

    +The samba.schema file has been formatted for OpenLDAP 2.0. The OID's are owned by the Samba Team and as such is legal to be openly published. If you translate the schema to be used with Netscape DS, please -submit the modified schema file as a patch to jerry@samba.org

    Just as the smbpasswd file is mean to store information which supplements a -user's /etc/passwd entry, so is the sambaAccount object +submit the modified schema file as a patch to jerry@samba.org +

    +Just as the smbpasswd file is meant to store information which supplements a +user's /etc/passwd entry, so is the sambaAccount object meant to supplement the UNIX user account information. A sambaAccount is a -STRUCTURAL objectclass so it can be stored individually +STRUCTURAL objectclass so it can be stored individually in the directory. However, there are several fields (e.g. uid) which overlap -with the posixAccount objectclass outlined in RFC2307. This is by design.

    In order to store all user account information (UNIX and Samba) in the directory, +with the posixAccount objectclass outlined in RFC2307. This is by design. +

    +In order to store all user account information (UNIX and Samba) in the directory, it is necessary to use the sambaAccount and posixAccount objectclasses in combination. However, smbd will still obtain the user's UNIX account information via the standard C library calls (e.g. getpwnam(), et. al.). This means that the Samba server must also have the LDAP NSS library installed and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account -information in NIS while the network is transitioning to a full LDAP infrastructure.

    4.6.5. Configuring Samba with LDAP

    4.6.5.1. OpenLDAP configuration

    To include support for the sambaAccount object in an OpenLDAP directory -server, first copy the samba.schema file to slapd's configuration directory.

    root# cp samba.schema /etc/openldap/schema/

    Next, include the samba.schema file in slapd.conf. +information in NIS while the network is transitioning to a full LDAP infrastructure. +

    Configuring Samba with LDAP

    OpenLDAP configuration

    +To include support for the sambaAccount object in an OpenLDAP directory +server, first copy the samba.schema file to slapd's configuration directory. +

    +root# cp samba.schema /etc/openldap/schema/ +

    +Next, include the samba.schema file in slapd.conf. The sambaAccount object contains two attributes which depend upon other schema -files. The 'uid' attribute is defined in cosine.schema and -the 'displayName' attribute is defined in the inetorgperson.schema -file. Both of these must be included before the samba.schema file.

    ## /etc/openldap/slapd.conf
+files.  The 'uid' attribute is defined in cosine.schema and
+the 'displayName' attribute is defined in the inetorgperson.schema
+file.  Both of these must be included before the samba.schema file.
+
    +## /etc/openldap/slapd.conf
 
 ## schema files (core.schema is required by default)
 include	           /etc/openldap/schema/core.schema
@@ -967,16 +219,13 @@ include            /etc/openldap/schema/inetorgperson.schema
 include            /etc/openldap/schema/samba.schema
 include            /etc/openldap/schema/nis.schema
 
-....
    It is recommended that you maintain some indices on some of the most usefull attributes,
+....
+

    +It is recommended that you maintain some indices on some of the most usefull attributes, like in the following example, to speed up searches made on sambaAccount objectclasses -(and possibly posixAccount and posixGroup as well).

    # Indices to maintain
+(and possibly posixAccount and posixGroup as well).
+
    +# Indices to maintain
 ## required by OpenLDAP 2.0
 index objectclass   eq
 
@@ -990,87 +239,21 @@ index rid           eq
 ##index uidNumber     eq
 ##index gidNumber     eq
 ##index cn            eq
-##index memberUid     eq

    4.6.5.2. Configuring Samba

    The following parameters are available in smb.conf only with --with-ldapsam -was included with compiling Samba.

    These are described in the smb.conf(5) man +##index memberUid eq + +# (both fetched via ldapsearch): +index primaryGroupID eq +index displayName pres,eq + +

    Configuring Samba

    +The following parameters are available in smb.conf only with --with-ldapsam +was included when compiling Samba. +

    +These are described in the smb.conf(5) man page and so will not be repeated here. However, a sample smb.conf file for -use with an LDAP directory could appear as

    ## /usr/local/samba/lib/smb.conf
+use with an LDAP directory could appear as
+
    +## /usr/local/samba/lib/smb.conf
 [global]
      security = user
      encrypt passwords = yes
@@ -1082,357 +265,124 @@ CLASS="PROGRAMLISTING"
 
      # define the DN to use when binding to the directory servers
      # The password for this DN is not stored in smb.conf.  Rather it
-     # must be set by using 'smbpasswd -w secretpw' to store the
-     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
-     # changes, this password will need to be reset.
-     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
-
-     #  specify the LDAP server's hostname (defaults to locahost)
-     ldap server = ahab.samba.org
+     # must be set by using 'smbpasswd -w secretpw' to store the
+     # passphrase in the secrets.tdb file.  If the "ldap admin dn" values
+     # change, this password will need to be reset.
+     ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
 
      # Define the SSL option when connecting to the directory
      # ('off', 'start tls', or 'on' (default))
      ldap ssl = start tls
 
+     passdb backend ldapsam:ldap://ahab.samba.org
+
+     # smbpasswd -x delete the entire dn-entry
+     ldap delete dn = no
+
+     # the machine and user suffix added to the base suffix
+     # wrote WITHOUT quotes. NULL siffixes by default
+     ldap user suffix = ou=People
+     ldap machine suffix = ou=Systems
+
      # define the port to use in the LDAP session (defaults to 636 when
-     # "ldap ssl = on")
+     # "ldap ssl = on")
      ldap port = 389
 
      # specify the base DN to use when searching the directory
-     ldap suffix = "ou=people,dc=samba,dc=org"
+     ldap suffix = "ou=people,dc=samba,dc=org"
 
      # generally the default ldap search filter is ok
-     # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"

    4.6.6. Accounts and Groups management

    As users accounts are managed thru the sambaAccount objectclass, you should -modify you existing administration tools to deal with sambaAccount attributes.

    Machines accounts are managed with the sambaAccount objectclass, just -like users accounts. However, it's up to you to stored thoses accounts + # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))" +

    Accounts and Groups management

    +As users accounts are managed thru the sambaAccount objectclass, you should +modify your existing administration tools to deal with sambaAccount attributes. +

    +Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to store thoses accounts in a different tree of you LDAP namespace: you should use -"ou=Groups,dc=plainjoe,dc=org" to store groups and -"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration -file).

    In Samba release 3.0, the group management system is based on posix -groups. This means that Samba make usage of the posixGroup objectclass. +file). +

    +In Samba release 3.0, the group management system is based on posix +groups. This means that Samba makes usage of the posixGroup objectclass. For now, there is no NT-like group system management (global and local -groups).

    4.6.7. Security and sambaAccount

    There are two important points to remember when discussing the security -of sambaAccount entries in the directory.

    • Never retrieve the lmPassword or - ntPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to - view the lmPassword or ntPassword attribute values.

    These password hashes are clear text equivalents and can be used to impersonate +groups). +

    Security and sambaAccount

    +There are two important points to remember when discussing the security +of sambaAccount entries in the directory. +

    • Never retrieve the lmPassword or + ntPassword attribute values over an unencrypted LDAP session.

    • Never allow non-admin users to + view the lmPassword or ntPassword attribute values.

    +These password hashes are clear text equivalents and can be used to impersonate the user without deriving the original clear text strings. For more information -on the details of LM/NT password hashes, refer to the User Database of the Samba-HOWTO-Collection.

    To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults -to require an encrypted session (ldap ssl = on) using +on the details of LM/NT password hashes, refer to the User Database of the Samba-HOWTO-Collection. +

    +To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults +to require an encrypted session (ldap ssl = on) using the default port of 636 when contacting the directory server. When using an OpenLDAP 2.0 server, it is possible to use the use the StartTLS LDAP extended operation in the place of LDAPS. In either case, you are strongly discouraged to disable this security -(ldap ssl = off).

    Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +(ldap ssl = off). +

    +Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS extended operation. However, the OpenLDAP library still provides support for -the older method of securing communication between clients and servers.

    The second security precaution is to prevent non-administrative users from +the older method of securing communication between clients and servers. +

    +The second security precaution is to prevent non-administrative users from harvesting password hashes from the directory. This can be done using the -following ACL in slapd.conf:

    ## allow the "ldap admin dn" access, but deny everyone else
+following ACL in slapd.conf:
+
    +## allow the "ldap admin dn" access, but deny everyone else
 access to attrs=lmPassword,ntPassword
-     by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
-     by * none

    4.6.8. LDAP specials attributes for sambaAccounts

    The sambaAccount objectclass is composed of the following attributes:

    • lmPassword: the LANMAN password 16-byte hash stored as a character - representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character - representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the - lmPassword and ntPassword attributes were last set. -

    • acctFlags: string of 11 characters surrounded by square brackets [] + by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write + by * none +

    LDAP specials attributes for sambaAccounts

    +The sambaAccount objectclass is composed of the following attributes: +

    • lmPassword: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.

    • ntPassword: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.

    • pwdLastSet: The integer time in seconds since 1970 when the + lmPassword and ntPassword attributes were last set. +

    • acctFlags: string of 11 characters surrounded by square brackets [] representing account flags such as U (user), W(workstation), X(no password expiration), and - D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • homeDrive: specifies the drive letter to which to map the - UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" - where X is the letter of the drive to map. Refer to the "logon drive" parameter in the - smb.conf(5) man page for more information.

    • scriptPath: The scriptPath property specifies the path of + D(disabled).

    • logonTime: Integer value currently unused

    • logoffTime: Integer value currently unused

    • kickoffTime: Integer value currently unused

    • pwdCanChange: Integer value currently unused

    • pwdMustChange: Integer value currently unused

    • homeDrive: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.

    • scriptPath: The scriptPath property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path - is relative to the netlogon share. Refer to the "logon script" parameter in the - smb.conf(5) man page for more information.

    • profilePath: specifies a path to the user's profile. + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.

    • profilePath: specifies a path to the user's profile. This value can be a null string, a local absolute path, or a UNC path. Refer to the - "logon path" parameter in the smb.conf(5) man page for more information.

    • smbHome: The homeDirectory property specifies the path of + "logon path" parameter in the smb.conf(5) man page for more information.

    • smbHome: The homeDirectory property specifies the path of the home directory for the user. The string can be null. If homeDrive is set and specifies a drive letter, homeDirectory should be a UNC path. The path must be a network UNC path of the form \\server\share\directory. This value can be a null string. - Refer to the "logon home" parameter in the smb.conf(5) man page for more information. -

    • userWorkstation: character string value currently unused. -

    • rid: the integer representation of the user's relative identifier - (RID).

    • primaryGroupID: the relative identifier (RID) of the primary group - of the user.

    The majority of these parameters are only used when Samba is acting as a PDC of -a domain (refer to the Samba-PDC-HOWTO for details on + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. +

  • userWorkstation: character string value currently unused. +

  • rid: the integer representation of the user's relative identifier + (RID).

  • primaryGroupID: the relative identifier (RID) of the primary group + of the user.

    • +The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the Samba-PDC-HOWTO for details on how to configure Samba as a Primary Domain Controller). The following four attributes -are only stored with the sambaAccount entry if the values are non-default values:

    • smbHome

    • scriptPath

    • logonPath

    • homeDrive

    These attributes are only stored with the sambaAccount entry if +are only stored with the sambaAccount entry if the values are non-default values: +

    • smbHome

    • scriptPath

    • logonPath

    • homeDrive

    +These attributes are only stored with the sambaAccount entry if the values are non-default values. For example, assume TASHTEGO has now been -configured as a PDC and that logon home = \\%L\%u was defined in -its smb.conf file. When a user named "becky" logons to the domain, -the logon home string is expanded to \\TASHTEGO\becky. -If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +configured as a PDC and that logon home = \\%L\%u was defined in +its smb.conf file. When a user named "becky" logons to the domain, +the logon home string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value -of the logon home parameter is used in its place. Samba -will only write the attribute value to the directory entry is the value is -something other than the default (e.g. \\MOBY\becky).

    4.6.9. Example LDIF Entries for a sambaAccount

    The following is a working LDIF with the inclusion of the posixAccount objectclass:

    dn: uid=guest2, ou=people,dc=plainjoe,dc=org
+of the logon home parameter is used in its place.  Samba
+will only write the attribute value to the directory entry if the value is
+something other than the default (e.g. \\MOBY\becky).
+

    Example LDIF Entries for a sambaAccount

    +The following is a working LDIF with the inclusion of the posixAccount objectclass: +

    +dn: uid=guest2, ou=people,dc=plainjoe,dc=org
 ntPassword: 878D8014606CDA29677A44EFA1353FC7
 pwdMustChange: 2147483647
 primaryGroupID: 1201
@@ -1445,15 +395,12 @@ kickoffTime: 2147483647
 acctFlags: [UX         ]
 logoffTime: 2147483647
 rid: 19006
-pwdCanChange: 0

    The following is an LDIF entry for using both the sambaAccount and -posixAccount objectclasses:

    dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
+pwdCanChange: 0
+

    +The following is an LDIF entry for using both the sambaAccount and +posixAccount objectclasses: +

    +dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
 logonTime: 0
 displayName: Gerald Carter
 lmPassword: 552902031BEDE9EFAAD3B435B51404EE
@@ -1474,128 +421,38 @@ rid: 19000
 homeDirectory: /home/tashtego/gcarter
 pwdCanChange: 0
 pwdMustChange: 2147483647
-ntPassword: 878D8014606CDA29677A44EFA1353FC7

    4.7. MySQL

    4.7.1. Creating the database

    You either can set up your own table and specify the field names to pdb_mysql (see below -for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump +ntPassword: 878D8014606CDA29677A44EFA1353FC7 +

    MySQL

    Creating the database

    +You either can set up your own table and specify the field names to pdb_mysql (see below +for the column names) or use the default table. The file examples/pdb/mysql/mysql.dump contains the correct queries to create the required tables. Use the command : -mysql -uusername -hhostname -ppassword databasename < /path/to/samba/examples/pdb/mysql/mysql.dump

    4.7.2. Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: -

    passdb backend = [other-plugins] mysql:identifier [other-plugins]

    The identifier can be any string you like, as long as it doesn't collide with +mysql -uusername -hhostname -ppassword databasename > /path/to/samba/examples/pdb/mysql/mysql.dump + +

    Configuring

    This plugin lacks some good documentation, but here is some short info:

    Add a the following to the passdb backend variable in your smb.conf: +

    +passdb backend = [other-plugins] mysql:identifier [other-plugins]
+

    +

    The identifier can be any string you like, as long as it doesn't collide with the identifiers of other plugins or other instances of pdb_mysql. If you specify multiple pdb_mysql.so entries in 'passdb backend', you also need to -use different identifiers!

    Additional options can be given thru the smb.conf file in the [global] section.

    identifier:mysql host                     - host name, defaults to 'localhost'
+use different identifiers!
+
    
+Additional options can be given thru the smb.conf file in the [global] section.
+
    +identifier:mysql host                     - host name, defaults to 'localhost'
 identifier:mysql password
 identifier:mysql user                     - defaults to 'samba'
 identifier:mysql database                 - defaults to 'samba'
 identifier:mysql port                     - defaults to 3306
-identifier:table                          - Name of the table containing users
    Since the password for the mysql user is stored in the 
+identifier:table                          - Name of the table containing users
+
    Warning
    
+Since the password for the mysql user is stored in the 
 smb.conf file, you should make the the smb.conf file 
 readable only to the user that runs samba. This is considered a security 
-bug and will be fixed soon.
    Names of the columns in this table(I've added column types those columns should have first):
    identifier:logon time column             - int(9)
+bug and will be fixed soon.
+

    Names of the columns in this table(I've added column types those columns should have first):

    +identifier:logon time column             - int(9)
 identifier:logoff time column            - int(9)
 identifier:kickoff time column           - int(9)
 identifier:pass last set time column     - int(9)
@@ -1604,17 +461,17 @@ identifier:pass must change time column  - int(9)
 identifier:username column               - varchar(255) - unix username
 identifier:domain column                 - varchar(255) - NT domain user is part of
 identifier:nt username column            - varchar(255) - NT username
-identifier:fullname column            - varchar(255) - Full name of user
+identifier:fullname column               - varchar(255) - Full name of user
 identifier:home dir column               - varchar(255) - Unix homedir path
-identifier:dir drive column              - varchar(2) - Directory drive path (eg: 'H:')
-identifier:logon script column           - varchar(255) - Batch file to run on client side when logging on
+identifier:dir drive column              - varchar(2)   - Directory drive path (eg: 'H:')
+identifier:logon script column           - varchar(255)
+					 - Batch file to run on client side when logging on
 identifier:profile path column           - varchar(255) - Path of profile
 identifier:acct desc column              - varchar(255) - Some ASCII NT user data
-identifier:workstations column           - varchar(255) - Workstations user can logon to (or NULL for all)
+identifier:workstations column           - varchar(255)
+					 - Workstations user can logon to (or NULL for all)
 identifier:unknown string column         - varchar(255) - unknown string
 identifier:munged dial column            - varchar(255) - ?
-identifier:uid column                    - int(9) - Unix user ID (uid)
-identifier:gid column                    - int(9) - Unix user group (gid)
 identifier:user sid column               - varchar(255) - NT user SID
 identifier:group sid column              - varchar(255) - NT group ID
 identifier:lanman pass column            - varchar(255) - encrypted lanman password
@@ -1625,146 +482,37 @@ identifier:unknown 3 column              - int(9) - unknown
 identifier:logon divs column             - int(9) - ?
 identifier:hours len column              - int(9) - ?
 identifier:unknown 5 column              - int(9) - unknown
-identifier:unknown 6 column              - int(9) - unknown

    Eventually, you can put a colon (:) after the name of each column, which +identifier:unknown 6 column - int(9) - unknown +

    +Eventually, you can put a colon (:) after the name of each column, which should specify the column to update when updating the table. You can also specify nothing behind the colon - then the data from the field will not be -updated.

    4.7.3. Using plaintext passwords or encrypted password

    I strongly discourage the use of plaintext passwords, however, you can use them:

    If you would like to use plaintext passwords, set 'identifier:lanman pass column' and 'identifier:nt pass column' to 'NULL' (without the quotes) and 'identifier:plain pass column' to the name of the column containing the plaintext passwords.

    If you use encrypted passwords, set the 'identifier:plain pass column' to 'NULL' (without the quotes). This is the default.

    4.7.4. Getting non-column data from the table

    It is possible to have not all data in the database and making some 'constant'.

    For example, you can set 'identifier:fullname column' to : -CONCAT(First_name,' ',Sur_name)

    Or, set 'identifier:workstations column' to : -NULL

    See the MySQL documentation for more language constructs.

    4.8. XML

    This module requires libxml2 to be installed.

    The usage of pdb_xml is pretty straightforward. To export data, use: - -pdbedit -e xml:filename - -(where filename is the name of the file to put the data in)

    To import data, use: -pdbedit -i xml:filename -e current-pdb - -Where filename is the name to read the data from and current-pdb to put it in.

    PrevHomeNext
    Quick Cross Subnet Browsing / Cross Workgroup Browsing guideUpType of installation
    \ No newline at end of file +updated. +

    Using plaintext passwords or encrypted password

    +I strongly discourage the use of plaintext passwords, however, you can use them: +

    +If you would like to use plaintext passwords, set +'identifier:lanman pass column' and 'identifier:nt pass column' to +'NULL' (without the quotes) and 'identifier:plain pass column' to the +name of the column containing the plaintext passwords. +

    +If you use encrypted passwords, set the 'identifier:plain pass +column' to 'NULL' (without the quotes). This is the default. +

    Getting non-column data from the table

    +It is possible to have not all data in the database and making some 'constant'. +

    +For example, you can set 'identifier:fullname column' to : +CONCAT(First_name,' ',Sur_name) +

    +Or, set 'identifier:workstations column' to : +NULL

    See the MySQL documentation for more language constructs.

    XML

    This module requires libxml2 to be installed.

    The usage of pdb_xml is pretty straightforward. To export data, use: +

    + pdbedit -e xml:filename +

    +(where filename is the name of the file to put the data in) +

    +To import data, use: +pdbedit -i xml:filename -e current-pdb +

    +Where filename is the name to read the data from and current-pdb to put it in. +

    PrevUpNext
    Chapter9.Samba / MS Windows Network Browsing GuideHomeChapter11.UNIX Permission Bits and Windows NT Access Control Lists
    diff --git a/docs/htmldocs/pdbedit.8.html b/docs/htmldocs/pdbedit.8.html index 2fa0f15d38..f239011639 100644 --- a/docs/htmldocs/pdbedit.8.html +++ b/docs/htmldocs/pdbedit.8.html @@ -1,588 +1,131 @@ - -pdbedit

    pdbedit

    Name

    pdbedit -- manage the SAM database

    Synopsis

    pdbedit [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The pdbedit program is used to manage the users accounts - stored in the sam database and can only be run by root.

    The pdbedit tool uses the passdb modular interface and is +pdbedit

    Name

    pdbedit — manage the SAM database

    Synopsis

    pdbedit [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The pdbedit program is used to manage the users accounts + stored in the sam database and can only be run by root.

    The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added - without changing the tool).

    There are five main ways to use pdbedit: adding a user account, + without changing the tool).

    There are five main ways to use pdbedit: adding a user account, removing a user account, modifing a user account, listing user - accounts, importing users accounts.

    OPTIONS

    -l

    This option lists all the user accounts + accounts, importing users accounts.

    OPTIONS

    -l

    This option lists all the user accounts present in the users database. This option prints a list of user/uid pairs separated by - the ':' character.

    Example: pdbedit -l

        sorce:500:Simo Sorce
-    samba:45:Test User

    -v

    This option enables the verbose listing format. + the ':' character.

    Example: pdbedit -l

    +sorce:500:Simo Sorce
+samba:45:Test User
+
    -v

    This option enables the verbose listing format. It causes pdbedit to list the users in the database, printing - out the account fields in a descriptive format.

    Example: pdbedit -l -v

        ---------------
-    username:       sorce
-    user ID/Group:  500/500
-    user RID/GRID:  2000/2001
-  5 Full Name:      Simo Sorce
-    Home Directory: \\BERSERKER\sorce
-    HomeDir Drive:  H:
-    Logon Script:   \\BERSERKER\netlogon\sorce.bat
-    Profile Path:   \\BERSERKER\profile
- 10 ---------------
-    username:       samba
-    user ID/Group:  45/45
-    user RID/GRID:  1090/1091
-    Full Name:      Test User
- 15 Home Directory: \\BERSERKER\samba
-    HomeDir Drive:  
-    Logon Script:   
-    Profile Path:   \\BERSERKER\profile

    -w

    This option sets the "smbpasswd" listing format. + out the account fields in a descriptive format.

    Example: pdbedit -l -v

    +---------------
+username:       sorce
+user ID/Group:  500/500
+user RID/GRID:  2000/2001
+Full Name:      Simo Sorce
+Home Directory: \\BERSERKER\sorce
+HomeDir Drive:  H:
+Logon Script:   \\BERSERKER\netlogon\sorce.bat
+Profile Path:   \\BERSERKER\profile
+---------------
+username:       samba
+user ID/Group:  45/45
+user RID/GRID:  1090/1091
+Full Name:      Test User
+Home Directory: \\BERSERKER\samba
+HomeDir Drive:  
+Logon Script:   
+Profile Path:   \\BERSERKER\profile
+
    -w

    This option sets the "smbpasswd" listing format. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the - smbpasswd file format. (see the - smbpasswd(5) for details)

    Example: pdbedit -l -w

        sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
-    samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:
    -u username

    This option specifies the username to be + smbpasswd file format. (see the + smbpasswd(5) for details)

    Example: pdbedit -l -w

    +sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX         ]:LCT-00000000:
+samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX         ]:LCT-3BFA1E8D:
+
    -u username

    This option specifies the username to be used for the operation requested (listing, adding, removing). - It is required in add, remove and modify - operations and optional in list - operations.

    -f fullname

    This option can be used while adding or + It is required in add, remove and modify + operations and optional in list + operations.

    -f fullname

    This option can be used while adding or modifing a user account. It will specify the user's full - name.

    Example: -f "Simo Sorce"

    -h homedir

    This option can be used while adding or + name.

    Example: -f "Simo Sorce"

    -h homedir

    This option can be used while adding or modifing a user account. It will specify the user's home - directory network path.

    Example: -h "\\\\BERSERKER\\sorce" -

    -D drive

    This option can be used while adding or + directory network path.

    Example: -h "\\\\BERSERKER\\sorce" +

    -D drive

    This option can be used while adding or modifing a user account. It will specify the windows drive - letter to be used to map the home directory.

    Example: -d "H:" -

    -S script

    This option can be used while adding or + letter to be used to map the home directory.

    Example: -d "H:" +

    -S script

    This option can be used while adding or modifing a user account. It will specify the user's logon - script path.

    Example: -s "\\\\BERSERKER\\netlogon\\sorce.bat" -

    -p profile

    This option can be used while adding or + script path.

    Example: -s "\\\\BERSERKER\\netlogon\\sorce.bat" +

    -p profile

    This option can be used while adding or modifing a user account. It will specify the user's profile - directory.

    Example: -p "\\\\BERSERKER\\netlogon" -

    -a

    This option is used to add a user into the + directory.

    Example: -p "\\\\BERSERKER\\netlogon" +

    -a

    This option is used to add a user into the database. This command needs a user name specified with the -u switch. When adding a new user, pdbedit will also - ask for the password to be used.

    Example: pdbedit -a -u sorce -

    new password:
-retype new password

    -m

    This option may only be used in conjunction - with the -a option. It will make + ask for the password to be used.

    Example: pdbedit -a -u sorce +

    new password:
+retype new password
+

    +

    -m

    This option may only be used in conjunction + with the -a option. It will make pdbedit to add a machine trust account instead of a user - account (-u username will provide the machine name).

    Example: pdbedit -a -m -u w2k-wks -

    -x

    This option causes pdbedit to delete an account + account (-u username will provide the machine name).

    Example: pdbedit -a -m -u w2k-wks +

    -x

    This option causes pdbedit to delete an account from the database. It needs a username specified with the - -u switch.

    Example: pdbedit -x -u bob

    -i passdb-backend

    Use a different passdb backend to retrieve users + -u switch.

    Example: pdbedit -x -u bob

    -i passdb-backend

    Use a different passdb backend to retrieve users than the one specified in smb.conf. Can be used to import data into - your local user database.

    This option will ease migration from one passdb backend to - another.

    Example: pdbedit -i smbpasswd:/etc/smbpasswd.old -

    -e passdb-backend

    Exports all currently available users to the - specified password database backend.

    This option will ease migration from one passdb backend to - another and will ease backing up.

    Example: pdbedit -e smbpasswd:/root/samba-users.backup

    -g

    If you specify -g, - then -i in-backend -e out-backend - applies to the group mapping instead of the user database. - -

    This option will ease migration from one passdb backend to - another and will ease backing up.

    -g

    If you specify -g, - then -i in-backend -e out-backend - applies to the group mapping instead of the user database. - -

    This option will ease migration from one passdb backend to - another and will ease backing up.

    -b passdb-backend

    Use a different default passdb backend.

    Example: pdbedit -b xml:/root/pdb-backup.xml -l

    -P account-policy

    Display an account policy

    Valid policies are: minimum password age, reset count minutes, disconnect time, + your local user database.

    This option will ease migration from one passdb backend to + another.

    Example: pdbedit -i smbpasswd:/etc/smbpasswd.old +

    -e passdb-backend

    Exports all currently available users to the + specified password database backend.

    This option will ease migration from one passdb backend to + another and will ease backing up.

    Example: pdbedit -e smbpasswd:/root/samba-users.backup

    -g

    If you specify -g, + then -i in-backend -e out-backend + applies to the group mapping instead of the user database.

    This option will ease migration from one passdb backend to + another and will ease backing up.

    -g

    If you specify -g, + then -i in-backend -e out-backend + applies to the group mapping instead of the user database.

    This option will ease migration from one passdb backend to + another and will ease backing up.

    -b passdb-backend

    Use a different default passdb backend.

    Example: pdbedit -b xml:/root/pdb-backup.xml -l

    -P account-policy

    Display an account policy

    Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, - maximum password age and bad lockout attempt.

    Example: pdbedit -P "bad lockout attempt"

    account policy value for bad lockout attempt is 0

    -C account-policy-value

    Sets an account policy to a specified value. + maximum password age and bad lockout attempt.

    Example: pdbedit -P "bad lockout attempt"

    +account policy value for bad lockout attempt is 0
+
    -C account-policy-value

    Sets an account policy to a specified value. This option may only be used in conjunction - with the -P option. -

    Example: pdbedit -P "bad lockout attempt" -C 3

    account policy value for bad lockout attempt was 0
-account policy value for bad lockout attempt is now 3

    -h|--help

    Print a summary of command line options.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + with the -P option. +

    Example: pdbedit -P "bad lockout attempt" -C 3

    +account policy value for bad lockout attempt was 0
+account policy value for bad lockout attempt is now 3
+
    -h|--help

    Print a summary of command line options. +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    NOTES

    This command may be used only by root.

    VERSION

    This man page is correct for version 2.2 of - the Samba suite.

    SEE ALSO

    smbpasswd(5), samba(7)

    AUTHOR

    The original Samba software and related utilities +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    NOTES

    This command may be used only by root.

    VERSION

    This man page is correct for version 2.2 of + the Samba suite.

    SEE ALSO

    smbpasswd(5), samba(7)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook - XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/printing.html b/docs/htmldocs/printing.html index 76d703514d..620aa5e8ba 100644 --- a/docs/htmldocs/printing.html +++ b/docs/htmldocs/printing.html @@ -1,381 +1,59 @@ - -Printing Support
    SAMBA Project Documentation
    PrevNext

    Chapter 13. Printing Support

    13.1. Introduction

    Beginning with the 2.2.0 release, Samba supports + +Chapter13.Printing Support

    Chapter13.Printing Support
    PrevPartIII.Advanced ConfigurationNext

    Chapter13.Printing Support

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Patrick Powell

    <papowell@lprng.org>

    (3 May 2001)

    Table of Contents

    Introduction
    Configuration
    Creating [print$]
    Setting Drivers for Existing Printers
    Support a large number of printers
    Adding New Printers via the Windows NT APW
    Samba and Printer Ports
    The Imprints Toolset
    What is Imprints?
    Creating Printer Driver Packages
    The Imprints server
    The Installation Client
    Diagnosis
    Introduction
    Debugging printer problems
    What printers do I have?
    Setting up printcap and print servers
    Job sent, no output
    Job sent, strange output
    Raw PostScript printed
    Advanced Printing
    Real debugging

    Introduction

    Beginning with the 2.2.0 release, Samba supports the native Windows NT printing mechanisms implemented via MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of -Samba only supported LanMan printing calls.

    The additional functionality provided by the new -SPOOLSS support includes:

    • Support for downloading printer driver +Samba only supported LanMan printing calls.

      The additional functionality provided by the new +SPOOLSS support includes:

      • Support for downloading printer driver files to Windows 95/98/NT/2000 clients upon demand. -

      • Uploading of printer drivers via the +

      • Uploading of printer drivers via the Windows NT Add Printer Wizard (APW) or the - Imprints tool set (refer to http://imprints.sourceforge.net). -

      • Support for the native MS-RPC printing + Imprints tool set (refer to http://imprints.sourceforge.net). +

      • Support for the native MS-RPC printing calls such as StartDocPrinter, EnumJobs(), etc... (See - the MSDN documentation at http://msdn.microsoft.com/ + the MSDN documentation at http://msdn.microsoft.com/ for more information on the Win32 printing API) -

      • Support for NT Access Control Lists (ACL) - on printer objects

      • Improved support for printer queue manipulation +

      • Support for NT Access Control Lists (ACL) + on printer objects

      • Improved support for printer queue manipulation through the use of an internal databases for spooled job - information

      There has been some initial confusion about what all this means + information

    +There has been some initial confusion about what all this means and whether or not it is a requirement for printer drivers to be installed on a Samba host in order to support printing from Windows clients. As a side note, Samba does not use these drivers in any way to process -spooled files. They are utilized entirely by the clients.

    The following MS KB article, may be of some help if you are dealing with -Windows 2000 clients: How to Add Printers with No User -Interaction in Windows 2000

    http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP

    13.2. Configuration

    [print$] vs. [printer$]
     

    Previous versions of Samba recommended using a share named [printer$]. +spooled files. They are utilized entirely by the clients. +

    +The following MS KB article, may be of some help if you are dealing with +Windows 2000 clients: How to Add Printers with No User +Interaction in Windows 2000 +

    +http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP +

    Configuration

    [print$] vs. [printer$]

    +Previous versions of Samba recommended using a share named [printer$]. This name was taken from the printer$ service created by Windows 9x clients when a printer was shared. Windows 9x printer servers always have a printer$ service which provides read-only access via no -password in order to support printer driver downloads.

    However, the initial implementation allowed for a -parameter named printer driver location +password in order to support printer driver downloads. +

    +However, the initial implementation allowed for a +parameter named printer driver location to be used on a per share basis to specify the location of the driver files associated with that printer. Another -parameter named printer driver provided +parameter named printer driver provided a means of defining the printer driver name to be sent to -the client.

    13.2.1. Creating [print$]

    In order to support the uploading of printer driver +the client. +

    Creating [print$]

    +In order to support the uploading of printer driver files, you must first configure a file share named [print$]. The name of this share is hard coded in Samba's internals so the name is very important (print$ is the service used by Windows NT print servers to provide support for printer driver -download).

    You should modify the server's smb.conf file to add the global +download). +

    You should modify the server's smb.conf file to add the global parameters and to create the following file share (of course, some of the parameter values, such as 'path' are arbitrary and should be replaced with -appropriate values for your site):

    [global]
+appropriate values for your site):
    +[global]
     ; members of the ntadmin group should be able
     ; to add drivers and set printer properties
     ; root is implicitly a 'printer admin'
@@ -391,290 +69,100 @@ CLASS="PROGRAMLISTING"
     ; sure this account can copy files to the share.  If this
     ; is setup to a non-root account, then it should also exist
     ; as a 'printer admin'
-    write list = @ntadmin,root
    The write list is used to allow administrative 
+    write list = @ntadmin,root
+

    The +write list is used to allow administrative level user accounts to have write access in order to update files -on the share. See the smb.conf(5) -man page for more information on configuring file shares.

    The requirement for guest -ok = yes depends upon how your +on the share. See the smb.conf(5) +man page for more information on configuring file shares.

    The requirement for guest +ok = yes depends upon how your site is configured. If users will be guaranteed to have -an account on the Samba host, then this is a non-issue.

    Author's Note
     

    The non-issue is that if all your Windows NT users are guaranteed to be +an account on the Samba host, then this is a non-issue.

    Author's Note

    +The non-issue is that if all your Windows NT users are guaranteed to be authenticated by the Samba server (such as a domain member server and the NT user has already been validated by the Domain Controller in order to logon to the Windows NT console), then guest access is not necessary. Of course, in a workgroup environment where you just want to be able to print without worrying about silly accounts and security, then configure the share for -guest access. You'll probably want to add map to guest = Bad User in the [global] section as well. Make sure +guest access. You'll probably want to add map to guest = Bad User + in the [global] section as well. Make sure you understand what this parameter does before using it -though. --jerry

    In order for a Windows NT print server to support +though. --jerry +

    In order for a Windows NT print server to support the downloading of driver files by multiple client architectures, it must create subdirectories within the [print$] service which correspond to each of the supported client architectures. -Samba follows this model as well.

    Next create the directory tree below the [print$] share -for each architecture you wish to support.

    [print$]----- - |-W32X86 ; "Windows NT x86" - |-WIN40 ; "Windows 95/98" - |-W32ALPHA ; "Windows NT Alpha_AXP" - |-W32MIPS ; "Windows NT R4000" - |-W32PPC ; "Windows NT PowerPC"

    ATTENTION! REQUIRED PERMISSIONS
     

    In order to currently add a new driver to you Samba host, -one of two conditions must hold true:

    • The account used to connect to the Samba host - must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host - must be a member of the printer - admin list.

    Of course, the connected account must still possess access +Samba follows this model as well.

    Next create the directory tree below the [print$] share +for each architecture you wish to support.

    +[print$]----- + |-W32X86 ; "Windows NT x86" + |-WIN40 ; "Windows 95/98" + |-W32ALPHA ; "Windows NT Alpha_AXP" + |-W32MIPS ; "Windows NT R4000" + |-W32PPC ; "Windows NT PowerPC" +

    ATTENTION! REQUIRED PERMISSIONS

    +In order to currently add a new driver to you Samba host, +one of two conditions must hold true: +

    • The account used to connect to the Samba host + must have a uid of 0 (i.e. a root account)

    • The account used to connect to the Samba host + must be a member of the printer + admin list.

    +Of course, the connected account must still possess access to add files to the subdirectories beneath [print$]. Remember -that all file shares are set to 'read only' by default.

    Once you have created the required [print$] service and +that all file shares are set to 'read only' by default. +

    +Once you have created the required [print$] service and associated subdirectories, simply log onto the Samba server using -a root (or printer admin) account -from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or -"My Network Places" and browse for the Samba host. Once you have located -the server, navigate to the "Printers..." folder. +a root (or printer admin) account +from a Windows NT 4.0/2k client. Open "Network Neighbourhood" or +"My Network Places" and browse for the Samba host. Once you have located +the server, navigate to the "Printers..." folder. You should see an initial listing of printers -that matches the printer shares defined on your Samba host.

    13.2.2. Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's +that matches the printer shares defined on your Samba host. +

    Setting Drivers for Existing Printers

    The initial listing of printers in the Samba host's Printers folder will have no real printer driver assigned to them. This defaults to a NULL string to allow the use of the local Add Printer Wizard on NT/2000 clients. Attempting to view the printer properties for a printer which has this default driver assigned will result in -the error message:

    Device settings cannot be displayed. The driver +the error message:

    +Device settings cannot be displayed. The driver for the specified printer is not installed, only spooler properties will be displayed. Do you want to install the -driver now?

    Click "No" in the error dialog and you will be presented with +driver now? +

    +Click "No" in the error dialog and you will be presented with the printer properties window. The way to assign a driver to a -printer is to either

    • Use the "New Driver..." button to install - a new printer driver, or

    • Select a driver from the popup list of - installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client -operating systems other than "Windows NT x86", you will need -to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you +printer is to either +

    • Use the "New Driver..." button to install + a new printer driver, or

    • Select a driver from the popup list of + installed drivers. Initially this list will be empty.

    If you wish to install printer drivers for client +operating systems other than "Windows NT x86", you will need +to use the "Sharing" tab of the printer properties dialog.

    Assuming you have connected with a root account, you will also be able modify other printer properties such as -ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible +ACLs and device settings using this dialog box.

    A few closing comments for this section, it is possible on a Windows NT print server to have printers listed in the Printers folder which are not shared. Samba does not make this distinction. By definition, the only printers of which Samba is aware are those which are specified as shares in -smb.conf.

    Another interesting side note is that Windows NT clients do +smb.conf.

    Another interesting side note is that Windows NT clients do not use the SMB printer share, but rather can print directly to any printer on another Windows NT host using MS-RPC. This of course assumes that the printing client has the necessary privileges on the remote host serving the printer. The default -permissions assigned by Windows NT to a printer gives the "Print" -permissions to the "Everyone" well-known group.

    13.2.3. Support a large number of printers

    One issue that has arisen during the development +permissions assigned by Windows NT to a printer gives the "Print" +permissions to the "Everyone" well-known group. +

    Support a large number of printers

    One issue that has arisen during the development phase of Samba 2.2 is the need to support driver downloads for 100's of printers. Using the Windows NT APW is somewhat awkward to say the list. If more than one printer are using the -same driver, the rpcclient's -setdriver command can be used to set the driver +same driver, the rpcclient's +setdriver command can be used to set the driver associated with an installed driver. The following is example -of how this could be accomplished:

    $ rpcclient pogo -U root%secret -c "enumdrivers" -

     
+of how this could be accomplished:
    
+$ rpcclient pogo -U root%secret -c "enumdrivers"
+
     
 Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
  
 [Windows NT x86]
@@ -685,145 +173,53 @@ Printer Driver Info 1:
      Driver Name: [HP LaserJet 2100 Series PS]
  
 Printer Driver Info 1:
-     Driver Name: [HP LaserJet 4Si/4SiMX PS]
    				  
-$ rpcclient pogo -U root%secret -c "enumprinters"
-
    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+     Driver Name: [HP LaserJet 4Si/4SiMX PS]
+
    				  
+$ rpcclient pogo -U root%secret -c "enumprinters"
+
    +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
      flags:[0x800000]
      name:[\\POGO\hp-print]
      description:[POGO\\POGO\hp-print,NO DRIVER AVAILABLE FOR THIS PRINTER,]
      comment:[]
-				  
    
-$ rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\""
-
    Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
-Successfully set hp-print to driver HP LaserJet 4000 Series PS.

    13.2.4. Adding New Printers via the Windows NT APW

    By default, Samba offers all printer shares defined in smb.conf -in the "Printers..." folder. Also existing in this folder is the Windows NT -Add Printer Wizard icon. The APW will be show only if

    • The connected user is able to successfully + +

      +$ rpcclient pogo -U root%secret -c "setdriver hp-print \"HP LaserJet 4000 Series PS\"" +

      +Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
+Successfully set hp-print to driver HP LaserJet 4000 Series PS.
+

    Adding New Printers via the Windows NT APW

    +By default, Samba offers all printer shares defined in smb.conf +in the "Printers..." folder. Also existing in this folder is the Windows NT +Add Printer Wizard icon. The APW will be show only if +

    • The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - privileges (i.e. root or printer admin). -

    • show - add printer wizard = yes (the default). -

    In order to be able to use the APW to successfully add a printer to a Samba -server, the add -printer command must have a defined value. The program + privileges (i.e. root or printer admin). +

  • show + add printer wizard = yes (the default). +

    • +In order to be able to use the APW to successfully add a printer to a Samba +server, the add +printer command must have a defined value. The program hook must successfully add the printer to the system (i.e. -/etc/printcap or appropriate files) and -smb.conf if necessary.

    When using the APW from a client, if the named printer share does -not exist, smbd will execute the add printer -command and reparse to the smb.conf +/etc/printcap or appropriate files) and +smb.conf if necessary. +

    +When using the APW from a client, if the named printer share does +not exist, smbd will execute the add printer +command and reparse to the smb.conf to attempt to locate the new printer share. If the share is still not defined, -an error of "Access Denied" is returned to the client. Note that the -add printer program is executed under the context -of the connected user, not necessarily a root account.

    There is a complementary delete -printer command for removing entries from the "Printers..." -folder.

    The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.

    #!/bin/sh
+an error of "Access Denied" is returned to the client.  Note that the 
+add printer program is executed under the context
+of the connected user, not necessarily a root account.
+
    
+There is a complementary delete
+printer command for removing entries from the "Printers..."
+folder.
+
    
+The following is an example add printer command script. It adds the appropriate entries to /etc/printcap.local (change that to what you need) and returns a line of 'Done' which is needed for the whole process to work.
+
    +#!/bin/sh
 
 # Script to insert a new printer entry into printcap.local
 #
@@ -839,213 +235,84 @@ CLASS="PROGRAMLISTING"
 PRINTCAP=/etc/printcap.local
 DATE=`date +%Y%m%d-%H%M%S`
 LP=lp
-RESTART="service lpd restart"
+RESTART="service lpd restart"
 
 # Keep a copy
 cp $PRINTCAP $PRINTCAP.$DATE
 # Add the printer to $PRINTCAP
-echo ""				 			>> $PRINTCAP
-echo "$2|$1:\\" 					>> $PRINTCAP
-echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
-echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
-echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
+echo ""				 			>> $PRINTCAP
+echo "$2|$1:\\" 					>> $PRINTCAP
+echo "  :sd=/var/spool/lpd/$2:\\" 			>> $PRINTCAP
+echo "  :mx=0:ml=0:sh:\\" 				>> $PRINTCAP
+echo "  :lp=/usr/local/samba/var/print/$5.prn:" 	>> $PRINTCAP
 
-touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
-chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+touch "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
+chown $LP "/usr/local/samba/var/print/$5.prn" >> /tmp/printadd.$$ 2>&1
 
 mkdir /var/spool/lpd/$2
 chmod 700 /var/spool/lpd/$2
 chown $LP /var/spool/lpd/$2
-#echo $1 >> "/usr/local/samba/var/print/$5.prn"
-#echo $2 >> "/usr/local/samba/var/print/$5.prn"
-#echo $3 >> "/usr/local/samba/var/print/$5.prn"
-#echo $4 >> "/usr/local/samba/var/print/$5.prn"
-#echo $5 >> "/usr/local/samba/var/print/$5.prn"
-#echo $6 >> "/usr/local/samba/var/print/$5.prn"
-$RESTART >> "/usr/local/samba/var/print/$5.prn"
+#echo $1 >> "/usr/local/samba/var/print/$5.prn"
+#echo $2 >> "/usr/local/samba/var/print/$5.prn"
+#echo $3 >> "/usr/local/samba/var/print/$5.prn"
+#echo $4 >> "/usr/local/samba/var/print/$5.prn"
+#echo $5 >> "/usr/local/samba/var/print/$5.prn"
+#echo $6 >> "/usr/local/samba/var/print/$5.prn"
+$RESTART >> "/usr/local/samba/var/print/$5.prn"
 # Not sure if this is needed
 touch /usr/local/samba/lib/smb.conf
 #
 # You need to return a value, but I am not sure what it means.
 #
-echo "Done"
-exit 0

    13.2.5. Samba and Printer Ports

    Windows NT/2000 print servers associate a port with each printer. These normally +echo "Done" +exit 0 +

    Samba and Printer Ports

    +Windows NT/2000 print servers associate a port with each printer. These normally take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the concept of ports associated with a printer. By default, only one printer port, -named "Samba Printer Port", exists on a system. Samba does not really a port in -order to print, rather it is a requirement of Windows clients.

    Note that Samba does not support the concept of "Printer Pooling" internally +named "Samba Printer Port", exists on a system. Samba does not really a port in +order to print, rather it is a requirement of Windows clients. +

    +Note that Samba does not support the concept of "Printer Pooling" internally either. This is when a logical printer is assigned to multiple ports as -a form of load balancing or fail over.

    If you require that multiple ports be defined for some reason, -smb.conf possesses a enumports -command which can be used to define an external program -that generates a listing of ports on a system.

    13.3. The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the +a form of load balancing or fail over. +

    +If you require that multiple ports be defined for some reason, +smb.conf possesses a enumports +command which can be used to define an external program +that generates a listing of ports on a system. +

    The Imprints Toolset

    The Imprints tool set provides a UNIX equivalent of the Windows NT Add Printer Wizard. For complete information, please - refer to the Imprints web site at http://imprints.sourceforge.net/ as well as the documentation + refer to the Imprints web site at + http://imprints.sourceforge.net/ as well as the documentation included with the imprints source distribution. This section will - only provide a brief introduction to the features of Imprints.

    13.3.1. What is Imprints?

    Imprints is a collection of tools for supporting the goals - of

    • Providing a central repository information - regarding Windows NT and 95/98 printer driver packages

    • Providing the tools necessary for creating - the Imprints printer driver packages.

    • Providing an installation client which + only provide a brief introduction to the features of Imprints.

      What is Imprints?

      Imprints is a collection of tools for supporting the goals + of

      • Providing a central repository information + regarding Windows NT and 95/98 printer driver packages

      • Providing the tools necessary for creating + the Imprints printer driver packages.

      • Providing an installation client which will obtain and install printer drivers on remote Samba - and Windows NT 4 print servers.

      13.3.2. Creating Printer Driver Packages

      The process of creating printer driver packages is beyond + and Windows NT 4 print servers.

    Creating Printer Driver Packages

    The process of creating printer driver packages is beyond the scope of this document (refer to Imprints.txt also included with the Samba distribution for more information). In short, an Imprints driver package is a gzipped tarball containing the driver files, related INF files, and a control file needed by the - installation client.

    13.3.3. The Imprints server

    The Imprints server is really a database server that + installation client.

    The Imprints server

    The Imprints server is really a database server that may be queried via standard HTTP mechanisms. Each printer entry in the database has an associated URL for the actual downloading of the package. Each package is digitally signed via GnuPG which can be used to verify that package downloaded is actually the one referred in the Imprints database. It is - not recommended that this security check - be disabled.

    13.3.4. The Installation Client

    More information regarding the Imprints installation client - is available in the Imprints-Client-HOWTO.ps - file included with the imprints source package.

    The Imprints installation client comes in two forms.

    • a set of command line Perl scripts

    • a GTK+ based graphical interface to - the command line perl scripts

    The installation client (in both forms) provides a means + not recommended that this security check + be disabled.

    The Installation Client

    More information regarding the Imprints installation client + is available in the Imprints-Client-HOWTO.ps + file included with the imprints source package.

    The Imprints installation client comes in two forms.

    • a set of command line Perl scripts

    • a GTK+ based graphical interface to + the command line perl scripts

    The installation client (in both forms) provides a means of querying the Imprints database server for a matching list of known printer model names as well as a means to download and install the drivers on remote Samba and Windows - NT print servers.

    The basic installation process is in four steps and - perl code is wrapped around smbclient - and rpcclient.

    	
+		NT print servers.
    The basic installation process is in four steps and 
+		perl code is wrapped around smbclient 
+		and rpcclient.
    	
 foreach (supported architecture for a given driver)
 {
      1.  rpcclient: Get the appropriate upload directory 
@@ -1055,492 +322,260 @@ foreach (supported architecture for a given driver)
 }
 	
 4.  rpcclient: Issue an AddPrinterEx() MS-RPC to actually
-    create the printer
    One of the problems encountered when implementing 
+    create the printer
+

    One of the problems encountered when implementing the Imprints tool set was the name space issues between various supported client architectures. For example, Windows - NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 calls its version of this driver "Apple - LaserWriter II NTX"

    The problem is how to know what client drivers have + NT includes a driver named "Apple LaserWriter II NTX v51.8" + and Windows 95 calls its version of this driver "Apple + LaserWriter II NTX"

    The problem is how to know what client drivers have been uploaded for a printer. As astute reader will remember that the Windows NT Printer Properties dialog only includes space for one printer driver name. A quick look in the - Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment -

    will reveal that Windows NT always uses the NT driver + Windows NT 4.0 system registry at

    HKLM\System\CurrentControlSet\Control\Print\Environment +

    will reveal that Windows NT always uses the NT driver name. This is ok as Windows NT always requires that at least the Windows NT version of the printer driver is present. However, Samba does not have the requirement internally. Therefore, how can you use the NT driver name if is has not - already been installed?

    The way of sidestepping this limitation is to require + already been installed?

    The way of sidestepping this limitation is to require that all Imprints printer driver packages include both the Intel Windows NT and 95/98 printer drivers and that NT driver is - installed first.

    13.4. Diagnosis

    13.4.1. Introduction

    This is a short description of how to debug printing problems with + installed first.

    Diagnosis

    Introduction

    +This is a short description of how to debug printing problems with Samba. This describes how to debug problems with printing from a SMB client to a Samba server, not the other way around. For the reverse -see the examples/printing directory.

    Ok, so you want to print to a Samba server from your PC. The first +see the examples/printing directory. +

    +Ok, so you want to print to a Samba server from your PC. The first thing you need to understand is that Samba does not actually do any printing itself, it just acts as a middleman between your PC client and your Unix printing subsystem. Samba receives the file from the PC -then passes the file to a external "print command". What print command -you use is up to you.

    The whole things is controlled using options in smb.conf. The most +then passes the file to a external "print command". What print command +you use is up to you. +

    +The whole things is controlled using options in smb.conf. The most relevant options (which you should look up in the smb.conf man page) -are:

          [global]
+are:
+
    +      [global]
         print command     - send a file to a spooler
         lpq command       - get spool queue status
         lprm command      - remove a job
       [printers]
-        path = /var/spool/lpd/samba
    The following are nice to know about:
            queuepause command   - stop a printer or print queue
-        queueresume command  - start a printer or print queue
    Example:
            print command = /usr/bin/lpr -r -P%p %s
+        path = /var/spool/lpd/samba
+
    
+The following are nice to know about:
+
    +        queuepause command   - stop a printer or print queue
+        queueresume command  - start a printer or print queue
+
    
+Example:
+
    +        print command = /usr/bin/lpr -r -P%p %s
         lpq command   = /usr/bin/lpq    -P%p %s
         lprm command  = /usr/bin/lprm   -P%p %j
         queuepause command = /usr/sbin/lpc -P%p stop
-        queuepause command = /usr/sbin/lpc -P%p start
    Samba should set reasonable defaults for these depending on your
+        queuepause command = /usr/sbin/lpc -P%p start
+

    +Samba should set reasonable defaults for these depending on your system type, but it isn't clairvoyant. It is not uncommon that you have to tweak these for local conditions. The commands should always have fully specified pathnames, as the smdb may not have -the correct PATH values.

    When you send a job to Samba to be printed, it will make a temporary +the correct PATH values. +

    +When you send a job to Samba to be printed, it will make a temporary copy of it in the directory specified in the [printers] section. and it should be periodically cleaned out. The lpr -r option requests that the temporary copy be removed after printing; If printing fails then you might find leftover files in this directory, and it should be periodically cleaned out. Samba used the lpq -command to determine the "job number" assigned to your print job -by the spooler.

    The %>letter< are "macros" that get dynamically replaced with appropriate +command to determine the "job number" assigned to your print job +by the spooler. +

    +The %>letter< are "macros" that get dynamically replaced with appropriate values when they are used. The %s gets replaced with the name of the spool file that Samba creates and the %p gets replaced with the name of the -printer. The %j gets replaced with the "job number" which comes from -the lpq output.

    13.4.2. Debugging printer problems

    One way to debug printing problems is to start by replacing these +printer. The %j gets replaced with the "job number" which comes from +the lpq output. +

    Debugging printer problems

    +One way to debug printing problems is to start by replacing these command with shell scripts that record the arguments and the contents of the print file. A simple example of this kind of things might -be:

    	print command = /tmp/saveprint %p %s
+be:
+
    +	print command = /tmp/saveprint %p %s
 
     #!/bin/saveprint
     # we make sure that we are the right user
-    /usr/bin/id -p >/tmp/tmp.print
+    /usr/bin/id -p >/tmp/tmp.print
     # we run the command and save the error messages
     # replace the command with the one appropriate for your system
-    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print
    Then you print a file and try removing it.  You may find that the
+    /usr/bin/lpr -r -P$1 $2 2>>&/tmp/tmp.print
+

    +Then you print a file and try removing it. You may find that the print queue needs to be stopped in order to see the queue status -and remove the job:

    
h4: {42} % echo hi >/tmp/hi
+and remove the job:
+
    +
+h4: {42} % echo hi >/tmp/hi
 h4: {43} % smbclient //localhost/lw4
 added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
 Password: 
 Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
-smb: \> print /tmp/hi
+smb: \> print /tmp/hi
 putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
-smb: \> queue
+smb: \> queue
 1049     3            hi-17534
-smb: \> cancel 1049
+smb: \> cancel 1049
 Error cancelling job 1049 : code 0
-smb: \> cancel 1049
+smb: \> cancel 1049
 Job 1049 cancelled
-smb: \> queue
-smb: \> exit
    The 'code 0' indicates that the job was removed.  The comment
+smb: \> queue
+smb: \> exit
+

    +The 'code 0' indicates that the job was removed. The comment by the smbclient is a bit misleading on this. You can observe the command output and then and look at the /tmp/tmp.print file to see what the results are. You can quickly find out if the problem is with your printing system. Often people have problems with their /etc/printcap file or permissions on -various print queues.

    13.4.3. What printers do I have?

    You can use the 'testprns' program to check to see if the printer +various print queues. +

    What printers do I have?

    +You can use the 'testprns' program to check to see if the printer name you are using is recognized by Samba. For example, you can -use:

        testprns printer /etc/printcap

    Samba can get its printcap information from a file or from a program. +use: +

    +    testprns printer /etc/printcap
+

    +Samba can get its printcap information from a file or from a program. You can try the following to see the format of the extracted -information:

        testprns -a printer /etc/printcap
+information:
+
    +    testprns -a printer /etc/printcap
 
-    testprns -a printer '|/bin/cat printcap'

    13.4.4. Setting up printcap and print servers

    You may need to set up some printcaps for your Samba system to use. + testprns -a printer '|/bin/cat printcap' +

    Setting up printcap and print servers

    +You may need to set up some printcaps for your Samba system to use. It is strongly recommended that you use the facilities provided by -the print spooler to set up queues and printcap information.

    Samba requires either a printcap or program to deliver printcap -information. This printcap information has the format:

      name|alias1|alias2...:option=value:...

    For almost all printing systems, the printer 'name' must be composed +the print spooler to set up queues and printcap information. +

    +Samba requires either a printcap or program to deliver printcap +information. This printcap information has the format: +

    +  name|alias1|alias2...:option=value:...
+

    +For almost all printing systems, the printer 'name' must be composed only of alphanumeric or underscore '_' characters. Some systems also allow hyphens ('-') as well. An alias is an alternative name for the printer, and an alias with a space in it is used as a 'comment' about the printer. The printcap format optionally uses a \ at the end of lines -to extend the printcap to multiple lines.

    Here are some examples of printcap files:

    1. pr just printer name

    2. pr|alias printer name and alias

    3. pr|My Printer printer name, alias used as comment

    4. pr:sh:\ Same as pr:sh:cm= testing +to extend the printcap to multiple lines. +

      +Here are some examples of printcap files: +

      +

      1. +pr just printer name +

      2. +pr|alias printer name and alias +

      3. +pr|My Printer printer name, alias used as comment +

      4. +pr:sh:\ Same as pr:sh:cm= testing :cm= \ - testing

      5. pr:sh Same as pr:sh:cm= testing - :cm= testing

      Samba reads the printcap information when first started. If you make -changes in the printcap information, then you must do the following:

      1. make sure that the print spooler is aware of these changes. -The LPRng system uses the 'lpc reread' command to do this.

      2. make sure that the spool queues, etc., exist and have the + testing +

      3. +pr:sh Same as pr:sh:cm= testing + :cm= testing +

      +

      +Samba reads the printcap information when first started. If you make +changes in the printcap information, then you must do the following: +

      1. +make sure that the print spooler is aware of these changes. +The LPRng system uses the 'lpc reread' command to do this. +

      2. +make sure that the spool queues, etc., exist and have the correct permissions. The LPRng system uses the 'checkpc -f' -command to do this.

      3. You now should send a SIGHUP signal to the smbd server to have -it reread the printcap information.

      13.4.5. Job sent, no output

      This is the most frustrating part of printing. You may have sent the +command to do this. +

    5. +You now should send a SIGHUP signal to the smbd server to have +it reread the printcap information. +

    Job sent, no output

    +This is the most frustrating part of printing. You may have sent the job, verified that the job was forwarded, set up a wrapper around -the command to send the file, but there was no output from the printer.

    First, check to make sure that the job REALLY is getting to the +the command to send the file, but there was no output from the printer. +

    +First, check to make sure that the job REALLY is getting to the right print queue. If you are using a BSD or LPRng print spooler, you can temporarily stop the printing of jobs. Jobs can still be -submitted, but they will not be printed. Use:

      lpc -Pprinter stop

    Now submit a print job and then use 'lpq -Pprinter' to see if the +submitted, but they will not be printed. Use: +

    +  lpc -Pprinter stop
+

    +Now submit a print job and then use 'lpq -Pprinter' to see if the job is in the print queue. If it is not in the print queue then -you will have to find out why it is not being accepted for printing.

    Next, you may want to check to see what the format of the job really +you will have to find out why it is not being accepted for printing. +

    +Next, you may want to check to see what the format of the job really was. With the assistance of the system administrator you can view the submitted jobs files. You may be surprised to find that these are not in what you would expect to call a printable format. You can use the UNIX 'file' utitily to determine what the job -format actually is:

        cd /var/spool/lpd/printer   # spool directory of print jobs
+format actually is:
+
    +    cd /var/spool/lpd/printer   # spool directory of print jobs
     ls                          # find job files
-    file dfA001myhost
    You should make sure that your printer supports this format OR that
+    file dfA001myhost
+

    +You should make sure that your printer supports this format OR that your system administrator has installed a 'print filter' that will -convert the file to a format appropriate for your printer.

    13.4.6. Job sent, strange output

    Once you have the job printing, you can then start worrying about -making it print nicely.

    The most common problem is extra pages of output: banner pages -OR blank pages at the end.

    If you are getting banner pages, check and make sure that the +convert the file to a format appropriate for your printer. +

    Job sent, strange output

    +Once you have the job printing, you can then start worrying about +making it print nicely. +

    +The most common problem is extra pages of output: banner pages +OR blank pages at the end. +

    +If you are getting banner pages, check and make sure that the printcap option or printer option is configured for no banners. If you have a printcap, this is the :sh (suppress header or banner -page) option. You should have the following in your printer.

       printer: ... :sh

    If you have this option and are still getting banner pages, there +page) option. You should have the following in your printer. +

    +   printer: ... :sh
+

    +If you have this option and are still getting banner pages, there is a strong chance that your printer is generating them for you automatically. You should make sure that banner printing is disabled for the printer. This usually requires using the printer setup software -or procedures supplied by the printer manufacturer.

    If you get an extra page of output, this could be due to problems +or procedures supplied by the printer manufacturer. +

    +If you get an extra page of output, this could be due to problems with your job format, or if you are generating PostScript jobs, incorrect setting on your printer driver on the MicroSoft client. -For example, under Win95 there is a option:

      Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|

    that allows you to choose if a Ctrl-D is appended to all jobs. +For example, under Win95 there is a option: +

    +  Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|
+

    +that allows you to choose if a Ctrl-D is appended to all jobs. This is a very bad thing to do, as most spooling systems will automatically add a ^D to the end of the job if it is detected as -PostScript. The multiple ^D may cause an additional page of output.

    13.4.7. Raw PostScript printed

    This is a problem that is usually caused by either the print spooling +PostScript. The multiple ^D may cause an additional page of output. +

    Raw PostScript printed

    +This is a problem that is usually caused by either the print spooling system putting information at the start of the print job that makes the printer think the job is a text file, or your printer simply does not support PostScript. You may need to enable 'Automatic -Format Detection' on your printer.

    13.4.8. Advanced Printing

    Note that you can do some pretty magic things by using your -imagination with the "print command" option and some shell scripts. +Format Detection' on your printer. +

    Advanced Printing

    +Note that you can do some pretty magic things by using your +imagination with the "print command" option and some shell scripts. Doing print accounting is easy by passing the %U option to a print command shell script. You could even make the print command detect the type of output and its size and send it to an appropriate -printer.

    13.4.9. Real debugging

    If the above debug tips don't help, then maybe you need to bring in -the bug guns, system tracing. See Tracing.txt in this directory.

    PrevHomeNext
    Configuring Group MappingUpCUPS Printing Support
    \ No newline at end of file +printer. +

    Real debugging

    +If the above debug tips don't help, then maybe you need to bring in +the bug guns, system tracing. See Tracing.txt in this directory. +

    PrevUpNext
    Chapter12.Configuring Group MappingHomeChapter14.CUPS Printing Support
    diff --git a/docs/htmldocs/problems.html b/docs/htmldocs/problems.html index 7144657779..f2bc0008eb 100644 --- a/docs/htmldocs/problems.html +++ b/docs/htmldocs/problems.html @@ -1,139 +1,17 @@ - -Analysing and solving samba problems
    SAMBA Project Documentation
    PrevNext

    Chapter 34. Analysing and solving samba problems

    There are many sources of information available in the form + +Chapter28.Analysing and solving samba problems

    Chapter28.Analysing and solving samba problems
    PrevPartIV.TroubleshootingNext

    Chapter28.Analysing and solving samba problems

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    David Bannon

    Samba Team

    <dbannon@samba.org>

    8 Apr 2003

    Table of Contents

    Diagnostics tools
    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box
    Useful URL's
    Getting help from the mailing lists
    How to get off the mailinglists

    +There are many sources of information available in the form of mailing lists, RFC's and documentation. The docs that come with the samba distribution contain very good explanations of -general SMB topics such as browsing.

    34.1. Diagnostics tools

    One of the best diagnostic tools for debugging problems is Samba itself. +general SMB topics such as browsing.

    Diagnostics tools

    +One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug -level can range from 1 (the default) to 10 (100 for debugging passwords).

    Another helpful method of debugging is to compile samba using the -gcc -g flag. This will include debug +level can range from 1 (the default) to 10 (100 for debugging passwords). +

    +Another helpful method of debugging is to compile samba using the +gcc -g flag. This will include debug information in the binaries and allow you to attach gdb to the running smbd / nmbd process. In order to attach gdb to an smbd process for an NT workstation, first get the workstation to make the @@ -143,36 +21,16 @@ generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation maintains an open connection, and therefore there will be an smbd process running (assuming that you haven't set a really short smbd idle timeout) So, in between pressing ctrl alt delete, and actually -typing in your password, you can gdb attach and continue.

    Some useful samba commands worth investigating:

    • testparam | more

    • smbclient -L //{netbios name of server}

    An SMB enabled version of tcpdump is available from -http://www.tcpdup.org/. +typing in your password, you can attach gdb and continue. +

    +Some useful samba commands worth investigating: +

    • testparam | more

    • smbclient -L //{netbios name of server}

    +An SMB enabled version of tcpdump is available from +http://www.tcpdup.org/. Ethereal, another good packet sniffer for Unix and Win32 -hosts, can be downloaded from http://www.ethereal.com.

    For tracing things on the Microsoft Windows NT, Network Monitor +hosts, can be downloaded from http://www.ethereal.com. +

    +For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two @@ -180,381 +38,97 @@ computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon -formatted files.

    34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box

    Installing netmon on an NT workstation requires a couple +formatted files. +

    Installing 'Network Monitor' on an NT Workstation or a Windows 9x box

    +Installing netmon on an NT workstation requires a couple of steps. The following are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT -Workstation 4.0. The process should be similar for other version of +Workstation 4.0. The process should be similar for other versions of Windows NT / Netmon. You will need both the Microsoft Windows -NT Server 4.0 Install CD and the Workstation 4.0 Install CD.

    Initially you will need to install 'Network Monitor Tools and Agent' -on the NT Server. To do this

    • Goto Start - Settings - Control Panel - - Network - Services - Add

    • Select the 'Network Monitor Tools and Agent' and - click on 'OK'.

    • Click 'OK' on the Network Control Panel. -

    • Insert the Windows NT Server 4.0 install CD - when prompted.

    At this point the Netmon files should exist in -%SYSTEMROOT%\System32\netmon\*.*. -Two subdirectories exist as well, parsers\ +NT Server 4.0 Install CD and the Workstation 4.0 Install CD. +

    +Initially you will need to install 'Network Monitor Tools and Agent' +on the NT Server. To do this +

    • Goto Start - Settings - Control Panel - + Network - Services - Add

    • Select the 'Network Monitor Tools and Agent' and + click on 'OK'.

    • Click 'OK' on the Network Control Panel. +

    • Insert the Windows NT Server 4.0 install CD + when prompted.

    +At this point the Netmon files should exist in +%SYSTEMROOT%\System32\netmon\*.*. +Two subdirectories exist as well, parsers\ which contains the necessary DLL's for parsing the netmon packet -dump, and captures\.

    In order to install the Netmon tools on an NT Workstation, you will +dump, and captures\. +

    +In order to install the Netmon tools on an NT Workstation, you will first need to install the 'Network Monitor Agent' from the Workstation -install CD.

    • Goto Start - Settings - Control Panel - - Network - Services - Add

    • Select the 'Network Monitor Agent' and click - on 'OK'.

    • Click 'OK' on the Network Control Panel. -

    • Insert the Windows NT Workstation 4.0 install - CD when prompted.

    Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* +install CD. +

    • Goto Start - Settings - Control Panel - + Network - Services - Add

    • Select the 'Network Monitor Agent' and click + on 'OK'.

    • Click 'OK' on the Network Control Panel. +

    • Insert the Windows NT Workstation 4.0 install + CD when prompted.

    +Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set permissions as you deem appropriate for your site. You will need -administrative rights on the NT box to run netmon.

    To install Netmon on a Windows 9x box install the network monitor agent +administrative rights on the NT box to run netmon. +

    +To install Netmon on a Windows 9x box install the network monitor agent from the Windows 9x CD (\admin\nettools\netmon). There is a readme file located with the netmon driver files on the CD if you need information on how to do this. Copy the files from a working -Netmon installation.

    34.3. Useful URL's

    • Home of Samba site http://samba.org. We have a mirror near you !

    • The Development document +Netmon installation. +

    Useful URL's

    34.4. Getting help from the mailing lists

    There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror -and then click on Support and then click on Samba related mailing lists.

    For questions relating to Samba TNG go to -http://www.samba-tng.org/ +it might mean that the developers are working on it.

  • See how Scott Merrill simulates a BDC behavior at + + http://www.skippy.net/linux/smb-howto.html.

  • Although 2.0.7 has almost had its day as a PDC, David Bannon will + keep the 2.0.7 PDC pages at + http://bioserve.latrobe.edu.au/samba going for a while yet.

  • Misc links to CIFS information + http://samba.org/cifs/

  • NT Domains for Unix + http://mailhost.cb1.com/~lkcl/ntdom/

  • FTP site for older SMB specs: + + ftp://ftp.microsoft.com/developr/drg/CIFS/

    • Getting help from the mailing lists

    +There are a number of Samba related mailing lists. Go to http://samba.org, click on your nearest mirror +and then click on Support and then click on +Samba related mailing lists. +

    +For questions relating to Samba TNG go to +http://www.samba-tng.org/ It has been requested that you don't post questions about Samba-TNG to the -main stream Samba lists.

    If you post a message to one of the lists please observe the following guide lines :

    • Always remember that the developers are volunteers, they are +main stream Samba lists.

      +If you post a message to one of the lists please observe the following guide lines : +

      • Always remember that the developers are volunteers, they are not paid and they never guarantee to produce a particular feature at -a particular time. Any time lines are 'best guess' and nothing more.

      • Always mention what version of samba you are using and what +a particular time. Any time lines are 'best guess' and nothing more. +

      • Always mention what version of samba you are using and what operating system its running under. You should probably list the -relevant sections of your smb.conf file, at least the options -in [global] that affect PDC support.

      • In addition to the version, if you obtained Samba via -CVS mention the date when you last checked it out.

      • Try and make your question clear and brief, lots of long, +relevant sections of your smb.conf file, at least the options +in [global] that affect PDC support.

      • In addition to the version, if you obtained Samba via +CVS mention the date when you last checked it out.

      • Try and make your question clear and brief, lots of long, convoluted questions get deleted before they are completely read ! Don't post html encoded messages (if you can select colour or font -size its html).

      • If you run one of those nifty 'I'm on holidays' things when -you are away, make sure its configured to not answer mailing lists.

      • Don't cross post. Work out which is the best list to post to +size its html).

      • If you run one of those nifty 'I'm on holidays' things when +you are away, make sure its configured to not answer mailing lists. +

      • Don't cross post. Work out which is the best list to post to and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt -with on another, will forward it on for you.

      • You might include partial +with on another, will forward it on for you.

      • You might include partial log files written at a debug level set to as much as 20. Please don't send the entire log but enough to give the context of the -error messages.

      • (Possibly) If you have a complete netmon trace ( from the opening of -the pipe to the error ) you can send the *.CAP file as well.

      • Please think carefully before attaching a document to an email. +error messages.

      • (Possibly) If you have a complete netmon trace ( from the opening of +the pipe to the error ) you can send the *.CAP file as well.

      • Please think carefully before attaching a document to an email. Consider pasting the relevant parts into the body of the message. The samba mailing lists go to a huge number of people, do they all need a copy of your -smb.conf in their attach directory?

      34.5. How to get off the mailinglists

      To have your name removed from a samba mailing list, go to the -same place you went to to get on it. Go to http://lists.samba.org, -click on your nearest mirror and then click on Support and -then click on Samba related mailing lists. Or perhaps see -here

      Please don't post messages to the list asking to be removed, you will just -be referred to the above address (unless that process failed in some way...)

    PrevHomeNext
    The samba checklistUpReporting Bugs
    \ No newline at end of file +smb.conf in their attach directory?

    How to get off the mailinglists

    To have your name removed from a samba mailing list, go to the +same place you went to to get on it. Go to http://lists.samba.org, +click on your nearest mirror and then click on Support and +then click on Samba related mailing lists. Or perhaps see +here +

    +Please don't post messages to the list asking to be removed, you will just +be referred to the above address (unless that process failed in some way...) +

    PrevUpNext
    Chapter27.The samba checklistHomeChapter29.Reporting Bugs
    diff --git a/docs/htmldocs/profiles.1.html b/docs/htmldocs/profiles.1.html index 53deae6f28..ea9f779b57 100644 --- a/docs/htmldocs/profiles.1.html +++ b/docs/htmldocs/profiles.1.html @@ -1,139 +1,12 @@ - -profiles

    profiles

    Name

    profiles -- A utility to report and change SIDs in registry files -

    Synopsis

    profiles [-v] [-c SID] [-n SID] {file}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    profiles is a utility that +profiles

    Name

    profiles — A utility to report and change SIDs in registry files +

    Synopsis

    profiles [-v] [-c SID] [-n SID] {file}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    profiles is a utility that reports and changes SIDs in windows registry files. It currently only supports NT. -

    OPTIONS

    file

    Registry file to view or edit.

    -v,--verbose

    Increases verbosity of messages. -

    -c SID1 -n SID2

    Change all occurences of SID1 in file by SID2. -

    -h|--help

    Print a summary of command line options.

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +

    OPTIONS

    file

    Registry file to view or edit.

    -v,--verbose

    Increases verbosity of messages. +

    -c SID1 -n SID2

    Change all occurences of SID1 in file by SID2. +

    -h|--help

    Print a summary of command line options. +

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The profiles man page was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The profiles man page was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 4dfe449366..ed351b0096 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -1,1186 +1,198 @@ - -rpcclient

    rpcclient

    Name

    rpcclient -- tool for executing client side - MS-RPC functions

    Synopsis

    rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    rpcclient is a utility initially developed +rpcclient

    Name

    rpcclient — tool for executing client side + MS-RPC functions

    Synopsis

    rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    rpcclient is a utility initially developed to test MS-RPC functionality in Samba itself. It has undergone several stages of development and stability. Many system administrators have now written scripts around it to manage Windows NT clients from - their UNIX workstation.

    OPTIONS

    server

    NetBIOS name of Server to which to connect. + their UNIX workstation.

    OPTIONS

    server

    NetBIOS name of Server to which to connect. The server can be any SMB/CIFS server. The name is - resolved using the name resolve order line from smb.conf(5).

    -c|--command='command string'

    execute semicolon separated commands (listed - below))

    -I IP-address

    IP address is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named + resolved using the + name resolve order line from smb.conf(5).

    -c|--command='command string'

    execute semicolon separated commands (listed + below))

    -I IP-address

    IP address is the address of the server to connect to. + It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the name resolve order + mechanism described above in the name resolve order parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being - connected to will be ignored.

    There is no default for this parameter. If not supplied, + connected to will be ignored.

    There is no default for this parameter. If not supplied, it will be determined automatically by the client as described - above.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + above.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -N

    If specified, this parameter suppresses the normal +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -N

    If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when -accessing a service that does not require a password.

    Unless a password is specified on the command line or +accessing a service that does not require a password.

    Unless a password is specified on the command line or this parameter is specified, the client will request a -password.

    -k

    Try to authenticate with kerberos. Only useful in -an Active Directory environment.

    -A|--authfile=filename

    This option allows +password.

    -k

    +Try to authenticate with kerberos. Only useful in +an Active Directory environment. +

    -A|--authfile=filename

    This option allows you to specify a file from which to read the username and -password used in the connection. The format of the file is

    username = <value>
-password = <value>
-domain   = <value>

    Make certain that the permissions on the file restrict -access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The -client will first check the USER environment variable, then the -LOGNAME variable and if either exists, the +password used in the connection. The format of the file is +

    +username = <value>
+password = <value>
+domain   = <value>
+

    Make certain that the permissions on the file restrict +access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The +client will first check the USER environment variable, then the +LOGNAME variable and if either exists, the string is uppercased. If these environmental variables are not -found, the username GUEST is used.

    A third option is to use a credentials file which +found, the username GUEST is used.

    A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the --A for more details.

    Be cautious about including passwords in scripts. Also, on +-A for more details.

    Be cautious about including passwords in scripts. Also, on many systems the command line of a running process may be seen -via the ps command. To be safe always allow -rpcclient to prompt for a password and type -it in directly.

    -n <primary NetBIOS name>

    This option allows you to override +via the ps command. To be safe always allow +rpcclient to prompt for a password and type +it in directly.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command line setting will take precedence over settings in -smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that -nmblookup will use to communicate with when +smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that +nmblookup will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -very rarely used, only set this parameter +very rarely used, only set this parameter if you are the system administrator in charge of all the -NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This +NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This overrides the default domain which is the domain defined in smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client +SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client socket. See the socket options parameter in -the smb.conf(5) manual page for the list of valid -options.

    -h|--help

    Print a summary of command line options.

    COMMANDS

    LSARPC

    lsaquery

    Query info policy

    lookupsids

    Resolve a list +the smb.conf(5) manual page for the list of valid +options.

    -h|--help

    Print a summary of command line options. +

    COMMANDS

    LSARPC

    lsaquery

    Query info policy

    lookupsids

    Resolve a list of SIDs to usernames. -

    lookupnames

    Resolve a list +

    lookupnames

    Resolve a list of usernames to SIDs. -

    enumtrusts

    Enumerate trusted domains

    enumprivs

    Enumerate privileges

    getdispname

    Get the privilege name

    lsaenumsid

    Enumerate the LSA SIDS

    lsaenumprivsaccount

    Enumerate the privileges of an SID

    lsaenumacctrights

    Enumerate the rights of an SID

    lsaenumacctwithright

    Enumerate accounts with a right

    lsaaddacctrights

    Add rights to an account

    lsaremoveacctrights

    Remove rights from an account

    lsalookupprivvalue

    Get a privilege value given its name

    lsaquerysecobj

    Query LSA security object

    LSARPC-DS

    dsroledominfo

    Get Primary Domain Information

    DFS

    dfsexist

    Query DFS support

    dfsadd

    Add a DFS share

    dfsremove

    Remove a DFS share

    dfsgetinfo

    Query DFS share info

    dfsenum

    Enumerate dfs shares

    REG

    shutdown

    Remote Shutdown

    abortshutdown

    Abort Shutdown

    SRVSVC

    srvinfo

    Server query info

    netshareenum

    Enumerate shares

    netfileenum

    Enumerate open files

    netremotetod

    Fetch remote time of day

    SAMR

    queryuser

    Query user info

    querygroup

    Query group info

    queryusergroups

    Query user groups

    querygroupmem

    Query group membership

    queryaliasmem

    Query alias membership

    querydispinfo

    Query display info

    querydominfo

    Query domain info

    enumdomusers

    Enumerate domain users

    enumdomgroups

    Enumerate domain groups

    enumalsgroups

    Enumerate alias groups

    createdomuser

    Create domain user

    samlookupnames

    Look up names

    samlookuprids

    Look up names

    deletedomuser

    Delete domain user

    samquerysecobj

    Query SAMR security object

    getdompwinfo

    Retrieve domain password info

    lookupdomain

    Look up domain

    SPOOLSS

    adddriver <arch> <config>

    Execute an AddPrinterDriver() RPC to install the printer driver +

    enumtrusts

    Enumerate trusted domains

    enumprivs

    Enumerate privileges

    getdispname

    Get the privilege name

    lsaenumsid

    Enumerate the LSA SIDS

    lsaenumprivsaccount

    Enumerate the privileges of an SID

    lsaenumacctrights

    Enumerate the rights of an SID

    lsaenumacctwithright

    Enumerate accounts with a right

    lsaaddacctrights

    Add rights to an account

    lsaremoveacctrights

    Remove rights from an account

    lsalookupprivvalue

    Get a privilege value given its name

    lsaquerysecobj

    Query LSA security object

    LSARPC-DS

    dsroledominfo

    Get Primary Domain Information

    DFS

    dfsexist

    Query DFS support

    dfsadd

    Add a DFS share

    dfsremove

    Remove a DFS share

    dfsgetinfo

    Query DFS share info

    dfsenum

    Enumerate dfs shares

    REG

    shutdown

    Remote Shutdown

    abortshutdown

    Abort Shutdown

    SRVSVC

    srvinfo

    Server query info

    netshareenum

    Enumerate shares

    netfileenum

    Enumerate open files

    netremotetod

    Fetch remote time of day

    SAMR

    queryuser

    Query user info

    querygroup

    Query group info

    queryusergroups

    Query user groups

    querygroupmem

    Query group membership

    queryaliasmem

    Query alias membership

    querydispinfo

    Query display info

    querydominfo

    Query domain info

    enumdomusers

    Enumerate domain users

    enumdomgroups

    Enumerate domain groups

    enumalsgroups

    Enumerate alias groups

    createdomuser

    Create domain user

    samlookupnames

    Look up names

    samlookuprids

    Look up names

    deletedomuser

    Delete domain user

    samquerysecobj

    Query SAMR security object

    getdompwinfo

    Retrieve domain password info

    lookupdomain

    Look up domain

    SPOOLSS

    adddriver <arch> <config>

    + Execute an AddPrinterDriver() RPC to install the printer driver information on the server. Note that the driver files should already exist in the directory returned by - getdriverdir. Possible values for - arch are the same as those for - the getdriverdir command. - The config parameter is defined as - follows: 

    Long Printer Name:\
+		getdriverdir.  Possible values for 
+		arch are the same as those for 
+		the getdriverdir command.
+		The config parameter is defined as 
+		follows: 
    +Long Printer Name:\
 Driver File Name:\
 Data File Name:\
 Config File Name:\
 Help File Name:\
 Language Monitor Name:\
 Default Data Type:\
-Comma Separated list of Files
    Any empty fields should be enter as the string "NULL". 
    Samba does not need to support the concept of Print Monitors
+Comma Separated list of Files
+

    Any empty fields should be enter as the string "NULL".

    Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi-directional link for communication. This field should - be "NULL". On a remote NT print server, the Print Monitor for a + be "NULL". On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or - else the RPC will fail.

    addprinter <printername> - <sharename> <drivername> <port>

    Add a printer on the remote server. This printer + else the RPC will fail.

    addprinter <printername> + <sharename> <drivername> <port>

    + Add a printer on the remote server. This printer will be automatically shared. Be aware that the printer driver - must already be installed on the server (see adddriver) - and the portmust be a valid port name (see - enumports.

    deldriver

    Delete the + must already be installed on the server (see adddriver) + and the portmust be a valid port name (see + enumports.

    deldriver

    Delete the specified printer driver for all architectures. This does not delete the actual driver files from the server, only the entry from the server's list of drivers. -

    enumdata

    Enumerate all +

    enumdata

    Enumerate all printer setting data stored on the server. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB. This command corresponds to the MS Platform SDK GetPrinterData() function (* This - command is currently unimplemented).

    enumdataex

    Enumerate printer data for a key

    enumjobs <printer>

    List the jobs and status of a given printer. + command is currently unimplemented).

    enumdataex

    Enumerate printer data for a key

    enumjobs <printer>

    List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() - function

    enumkey

    Enumerate printer keys

    enumports [level]

    Executes an EnumPorts() call using the specified + function

    enumkey

    Enumerate + printer keys

    enumports [level]

    + Executes an EnumPorts() call using the specified info level. Currently only info levels 1 and 2 are supported. -

    enumdrivers [level]

    Execute an EnumPrinterDrivers() call. This lists the various installed +

    enumdrivers [level]

    + Execute an EnumPrinterDrivers() call. This lists the various installed printer drivers for all architectures. Refer to the MS Platform SDK documentation for more details of the various flags and calling - options. Currently supported info levels are 1, 2, and 3.

    enumprinters [level]

    Execute an EnumPrinters() call. This lists the various installed + options. Currently supported info levels are 1, 2, and 3.

    enumprinters [level]

    Execute an EnumPrinters() call. This lists the various installed and share printers. Refer to the MS Platform SDK documentation for more details of the various flags and calling options. Currently - supported info levels are 0, 1, and 2.

    getdata <printername> <valuename;>

    Retrieve the data for a given printer setting. See - the enumdata command for more information. + supported info levels are 0, 1, and 2.

    getdata <printername> <valuename;>

    Retrieve the data for a given printer setting. See + the enumdata command for more information. This command corresponds to the GetPrinterData() MS Platform - SDK function.

    getdataex

    Get printer driver data with keyname

    getdriver <printername>

    Retrieve the printer driver information (such as driver file, + SDK function.

    getdataex

    Get + printer driver data with + keyname

    getdriver <printername>

    + Retrieve the printer driver information (such as driver file, config file, dependent files, etc...) for the given printer. This command corresponds to the GetPrinterDriver() MS Platform SDK function. Currently info level 1, 2, and 3 are supported. -

    getdriverdir <arch>

    Execute a GetPrinterDriverDirectory() +

    getdriverdir <arch>

    + Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible - values for arch are "Windows 4.0" - (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows - Alpha_AXP", and "Windows NT R4000".

    getprinter <printername>

    Retrieve the current printer information. This command + values for arch are "Windows 4.0" + (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows + Alpha_AXP", and "Windows NT R4000".

    getprinter <printername>

    Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function. -

    getprintprocdir

    Get print processor directory

    openprinter <printername>

    Execute an OpenPrinterEx() and ClosePrinter() RPC - against a given printer.

    setdriver <printername> - <drivername>

    Execute a SetPrinter() command to update the printer driver +

    getprintprocdir

    Get + print processor + directory

    openprinter <printername>

    Execute an OpenPrinterEx() and ClosePrinter() RPC + against a given printer.

    setdriver <printername> + <drivername>

    Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must - already be correctly installed on the print server.

    See also the enumprinters and - enumdrivers commands for obtaining a list of - of installed printers and drivers.

    addform

    Add form

    setform

    Set form

    getform

    Get form

    deleteform

    Delete form

    enumforms

    Enumerate form

    setprinter

    Set printer comment

    setprinterdata

    Set REG_SZ printer data

    rffpcnex

    Rffpcnex test

    NETLOGON

    logonctrl2

    Logon Control 2

    logonctrl

    Logon Control

    samsync

    Sam Synchronisation

    samdeltas

    Query Sam Deltas

    samlogon

    Sam Logon

    GENERAL COMMANDS

    debuglevel

    Set the current - debug level used to log information.

    help (?)

    Print a listing of all + already be correctly installed on the print server.

    See also the enumprinters and + enumdrivers commands for obtaining a list of + of installed printers and drivers.

    addform

    Add form

    setform

    Set form

    getform

    Get form

    deleteform

    Delete form

    enumforms

    Enumerate form

    setprinter

    Set printer comment

    setprinterdata

    Set REG_SZ printer data

    rffpcnex

    Rffpcnex test

    NETLOGON

    logonctrl2

    Logon Control 2

    logonctrl

    Logon Control

    samsync

    Sam Synchronisation

    samdeltas

    Query Sam Deltas

    samlogon

    Sam Logon

    GENERAL COMMANDS

    debuglevel

    Set the current + debug level used to log information.

    help (?)

    Print a listing of all known commands or extended help on a particular command. -

    quit (exit)

    Exit rpcclient - .

    BUGS

    rpcclient is designed as a developer testing tool +

    quit (exit)

    Exit rpcclient + .

    BUGS

    rpcclient is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing). It has been known to generate a core dump upon failures when invalid - parameters where passed to the interpreter.

    From Luke Leighton's original rpcclient man page:

    WARNING! The MSRPC over SMB code has + parameters where passed to the interpreter.

    From Luke Leighton's original rpcclient man page:

    WARNING! The MSRPC over SMB code has been developed from examining Network traces. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work. Microsoft's implementation of these services has been demonstrated (and reported) - to be... a bit flaky in places.

    The development of Samba's implementation is also a bit rough, + to be... a bit flaky in places.

    The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in - versions of smbd(8) and rpcclient(1) that are incompatible for some commands or services. Additionally, + versions of smbd(8) and rpcclient(1) that are incompatible for some commands or services. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may - result in incompatibilities.

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities + result in incompatibilities.

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original rpcclient man page was written by Matthew + to the way the Linux kernel is developed.

    The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was - done by Alexander Bokovoy.

    \ No newline at end of file + done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/samba-bdc.html b/docs/htmldocs/samba-bdc.html index 203f96ece8..0a8a8fa2e1 100644 --- a/docs/htmldocs/samba-bdc.html +++ b/docs/htmldocs/samba-bdc.html @@ -1,178 +1,27 @@ - -Samba Backup Domain Controller to Samba Domain Control
    SAMBA Project Documentation
    PrevNext

    Chapter 8. Samba Backup Domain Controller to Samba Domain Control

    8.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure + +Chapter6. +Samba Backup Domain Controller to Samba Domain Control +

    Chapter6. +Samba Backup Domain Controller to Samba Domain Control +
    PrevPartII.Server Configuration BasicsNext

    Chapter6. +Samba Backup Domain Controller to Samba Domain Control +

    Volker Lendecke

    Samba Team

    <Volker.Lendecke@SerNet.DE>

    (26 Apr 2001)

    Table of Contents

    Prerequisite Reading
    Background
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    When is the PDC needed?
    Can Samba be a Backup Domain Controller to an NT PDC?
    How do I set up a Samba BDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?

    Prerequisite Reading

    +Before you continue reading in this chapter, please make sure that you are comfortable with configuring a Samba PDC -as described in the Samba-PDC-HOWTO.

    8.2. Background

    What is a Domain Controller? It is a machine that is able to answer +as described in the Samba-PDC-HOWTO. +

    Background

    +What is a Domain Controller? It is a machine that is able to answer logon requests from workstations in a Windows NT Domain. Whenever a user logs into a Windows NT Workstation, the workstation connects to a Domain Controller and asks him whether the username and password the user typed in is correct. The Domain Controller replies with a lot of information about the user, for example the place where the users profile is stored, the users full name of the user. All this -information is stored in the NT user database, the so-called SAM.

    There are two kinds of Domain Controller in a NT 4 compatible Domain: +information is stored in the NT user database, the so-called SAM. +

    +There are two kinds of Domain Controller in a NT 4 compatible Domain: A Primary Domain Controller (PDC) and one or more Backup Domain Controllers (BDC). The PDC contains the master copy of the SAM. Whenever the SAM has to change, for example when a user changes @@ -181,51 +30,31 @@ Controller is a machine that maintains a read-only copy of the SAM. This way it is able to reply to logon requests and authenticate users in case the PDC is not available. During this time no changes to the SAM are possible. Whenever changes to the SAM are done on the PDC, -all BDC receive the changes from the PDC.

    Since version 2.2 Samba officially supports domain logons for all +all BDC receive the changes from the PDC. +

    +Since version 2.2 Samba officially supports domain logons for all current Windows Clients, including Windows 2000 and XP. This text assumes the domain to be named SAMBA. To be able to act as a PDC, some -parameters in the [global]-section of the smb.conf have to be set:

    workgroup = SAMBA
-domain master = yes
-domain logons = yes

    Several other things like a [homes] and a [netlogon] share also may be +parameters in the [global]-section of the smb.conf have to be set: +

    +	workgroup = SAMBA
+	domain master = yes
+	domain logons = yes
+

    +Several other things like a [homes] and a [netlogon] share also may be set along with settings for the profile path, the users home drive and -others. This will not be covered in this document.

    8.3. What qualifies a Domain Controller on the network?

    Every machine that is a Domain Controller for the domain SAMBA has to +others. This will not be covered in this document. +

    What qualifies a Domain Controller on the network?

    +Every machine that is a Domain Controller for the domain SAMBA has to register the NetBIOS group name SAMBA#1c with the WINS server and/or by broadcast on the local network. The PDC also registers the unique NetBIOS name SAMBA#1b with the WINS server. The name type #1b is normally reserved for the domain master browser, a role that has nothing to do with anything related to authentication, but the Microsoft Domain implementation requires the domain master browser to -be on the same machine as the PDC.

    8.3.1. How does a Workstation find its domain controller?

    A NT workstation in the domain SAMBA that wants a local user to be +be on the same machine as the PDC. +

    How does a Workstation find its domain controller?

    +A NT workstation in the domain SAMBA that wants a local user to be authenticated has to find the domain controller for SAMBA. It does this by doing a NetBIOS name query for the group name SAMBA#1c. It assumes that each of the machines it gets back from the queries is a @@ -233,214 +62,87 @@ domain controller and can answer logon requests. To not open security holes both the workstation and the selected (TODO: How is the DC chosen) domain controller authenticate each other. After that the workstation sends the user's credentials (his name and password) to -the domain controller, asking for approval.

    8.3.2. When is the PDC needed?

    Whenever a user wants to change his password, this has to be done on +the domain controller, asking for approval. +

    When is the PDC needed?

    +Whenever a user wants to change his password, this has to be done on the PDC. To find the PDC, the workstation does a NetBIOS name query for SAMBA#1b, assuming this machine maintains the master copy of the SAM. The workstation contacts the PDC, both mutually authenticate and -the password change is done.

    8.4. Can Samba be a Backup Domain Controller to an NT PDC?

    With version 2.2, no. The native NT SAM replication protocols have +the password change is done. +

    Can Samba be a Backup Domain Controller to an NT PDC?

    +With version 2.2, no. The native NT SAM replication protocols have not yet been fully implemented. The Samba Team is working on understanding and implementing the protocols, but this work has not -been finished for version 2.2.

    With version 3.0, the work on both the replication protocols and a +been finished for version 2.2. +

    +With version 3.0, the work on both the replication protocols and a suitable storage mechanism has progressed, and some form of NT4 BDC -support is expected soon.

    Can I get the benefits of a BDC with Samba? Yes. The main reason for +support is expected soon. +

    +Can I get the benefits of a BDC with Samba? Yes. The main reason for implementing a BDC is availability. If the PDC is a Samba machine, a second Samba machine can be set up to -service logon requests whenever the PDC is down.

    8.5. How do I set up a Samba BDC?

    Several things have to be done:

    • The domain SID has to be the same on the PDC and the BDC. This used to +service logon requests whenever the PDC is down. +

    How do I set up a Samba BDC?

    +Several things have to be done: +

    • +The domain SID has to be the same on the PDC and the BDC. This used to be stored in the file private/MACHINE.SID. This file is not created anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is stored in the file private/secrets.tdb. Simply copying the secrets.tdb from the PDC to the BDC does not work, as the BDC would generate a new SID for itself and override the domain SID with this -new BDC SID.

      To retrieve the domain SID from the PDC or an existing BDC and store it in the -secrets.tdb, execute 'net rpc getsid' on the BDC.

    • The Unix user database has to be synchronized from the PDC to the +new BDC SID.

      +To retrieve the domain SID from the PDC or an existing BDC and store it in the +secrets.tdb, execute 'net rpc getsid' on the BDC. +

    • +The Unix user database has to be synchronized from the PDC to the BDC. This means that both the /etc/passwd and /etc/group have to be replicated from the PDC to the BDC. This can be done manually whenever changes are made, or the PDC is set up as a NIS master server and the BDC as a NIS slave server. To set up the BDC as a mere NIS client would not be enough, as the BDC would not be able to -access its user database in case of a PDC failure.

    • The Samba password database in the file private/smbpasswd has to be +access its user database in case of a PDC failure. +

    • +The Samba password database in the file private/smbpasswd has to be replicated from the PDC to the BDC. This is a bit tricky, see the -next section.

    • Any netlogon share has to be replicated from the PDC to the +next section. +

    • +Any netlogon share has to be replicated from the PDC to the BDC. This can be done manually whenever login scripts are changed, or it can be done automatically together with the smbpasswd -synchronization.

    Finally, the BDC has to be found by the workstations. This can be done -by setting

    workgroup = samba
-domain master = no
-domain logons = yes

    in the [global]-section of the smb.conf of the BDC. This makes the BDC +synchronization. +

    +Finally, the BDC has to be found by the workstations. This can be done +by setting +

    +	workgroup = samba
+	domain master = no
+	domain logons = yes
+

    +in the [global]-section of the smb.conf of the BDC. This makes the BDC only register the name SAMBA#1c with the WINS server. This is no problem as the name SAMBA#1c is a NetBIOS group name that is meant to be registered by more than one machine. The parameter 'domain master = no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS -name is reserved for the Primary Domain Controller.

    8.5.1. How do I replicate the smbpasswd file?

    Replication of the smbpasswd file is sensitive. It has to be done +name is reserved for the Primary Domain Controller. +

    How do I replicate the smbpasswd file?

    +Replication of the smbpasswd file is sensitive. It has to be done whenever changes to the SAM are made. Every user's password change is done in the smbpasswd file and has to be replicated to the BDC. So -replicating the smbpasswd file very often is necessary.

    As the smbpasswd file contains plain text password equivalents, it +replicating the smbpasswd file very often is necessary. +

    +As the smbpasswd file contains plain text password equivalents, it must not be sent unencrypted over the wire. The best way to set up smbpasswd replication from the PDC to the BDC is to use the utility rsync. rsync can use ssh as a transport. ssh itself can be set up to accept *only* rsync transfer without requiring the user to type a -password.

    8.5.2. Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports +password. +

    Can I do this all with LDAP?

    The simple answer is YES. Samba's pdb_ldap code supports binding to a replica LDAP server, and will also follow referrals and rebind to the master if it ever needs to make a modification to the database. (Normally BDCs are read only, so this will not occur -often).

    PrevHomeNext
    Samba as an NT4 or Win2k Primary Domain ControllerUpSamba as a ADS domain member
    \ No newline at end of file +often). +

    PrevUpNext
    Chapter5. +Samba as an NT4 or Win2k Primary Domain Controller +HomeChapter7.Samba as a ADS domain member
    diff --git a/docs/htmldocs/samba-pdc.html b/docs/htmldocs/samba-pdc.html index 72edc9244c..951dd2ea96 100644 --- a/docs/htmldocs/samba-pdc.html +++ b/docs/htmldocs/samba-pdc.html @@ -1,545 +1,172 @@ - -Samba as an NT4 or Win2k Primary Domain Controller
    SAMBA Project Documentation
    PrevNext

    Chapter 7. Samba as an NT4 or Win2k Primary Domain Controller

    Table of Contents
    7.1. Prerequisite Reading
    7.2. Background
    7.3. Configuring the Samba Domain Controller
    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain
    7.4.1. Manual Creation of Machine Trust Accounts
    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts
    7.4.3. Joining the Client to the Domain
    7.5. Common Problems and Errors
    7.5.1. I cannot include a '$' in a machine name
    7.5.2. I get told "You already have a connection to the Domain...." -or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.
    7.5.3. The system can not log you on (C000019B)....
    7.5.4. The machine trust account for this computer either does not -exist or is not accessible.
    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.
    7.6. Domain Control for Windows 9x/ME

    7.1. Prerequisite Reading

    Before you continue reading in this chapter, please make sure + +Chapter5. +Samba as an NT4 or Win2k Primary Domain Controller +

    Chapter5. +Samba as an NT4 or Win2k Primary Domain Controller +
    PrevPartII.Server Configuration BasicsNext

    Chapter5. +Samba as an NT4 or Win2k Primary Domain Controller +

    Gerald (Jerry) Carter

    Samba Team

    <jerry@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    David Bannon

    Samba Team

    <dbannon@samba.org>

    (26 Apr 2001)

    Table of Contents

    Prerequisite Reading
    +Background +
    Configuring the Samba Domain Controller
    Creating Machine Trust Accounts and Joining Clients to the Domain
    Manual Creation of Machine Trust Accounts
    "On-the-Fly" Creation of Machine Trust Accounts
    Joining the Client to the Domain
    Common Problems and Errors
    I cannot include a '$' in a machine name
    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not +exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    Domain Control for Windows 9x/ME
    Configuration Instructions: Network Logons

    Prerequisite Reading

    +Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the -smb.conf manpage.

    7.2. Background

    This article outlines the steps necessary for configuring Samba as a PDC. +smb.conf manpage. +

    +Background +

    +This article outlines the steps necessary for configuring Samba as a PDC. It is necessary to have a working Samba server prior to implementing the -PDC functionality.

    • Domain logons for Windows NT 4.0 / 200x / XP Professional clients. -

    • Placing Windows 9x / Me clients in user level security -

    • Retrieving a list of users and groups from a Samba PDC to +PDC functionality. +

      • + Domain logons for Windows NT 4.0 / 200x / XP Professional clients. +

      • + Placing Windows 9x / Me clients in user level security +

      • + Retrieving a list of users and groups from a Samba PDC to Windows 9x / Me / NT / 200x / XP Professional clients -

      • Roaming Profiles -

      • Network/System Policies -

      Roaming Profiles and System/Network policies are advanced network administration topics -that are covered separately in this document.

      The following functionalities are new to the Samba 3.0 release:

      • Windows NT 4 domain trusts -

      • Adding users via the User Manager for Domains -

      The following functionalities are NOT provided by Samba 3.0:

      • SAM replication with Windows NT 4.0 Domain Controllers +

      • + Roaming Profiles +

      • + Network/System Policies +

      Note

      +Roaming Profiles and System/Network policies are advanced network administration topics +that are covered separately in this document. +

      +The following functionalities are new to the Samba 3.0 release: +

      • + Windows NT 4 domain trusts +

      • + Adding users via the User Manager for Domains +

      +The following functionalities are NOT provided by Samba 3.0: +

      • + SAM replication with Windows NT 4.0 Domain Controllers (i.e. a Samba PDC and a Windows NT BDC or vice versa) -

      • Acting as a Windows 2000 Domain Controller (i.e. Kerberos and +

      • + Acting as a Windows 2000 Domain Controller (i.e. Kerberos and Active Directory) -

      Please note that Windows 9x / Me / XP Home clients are not true members of a domain +

    +Please note that Windows 9x / Me / XP Home clients are not true members of a domain for reasons outlined in this article. Therefore the protocol for -support Windows 9x-style domain logons is completely different +support of Windows 9x-style domain logons is completely different from NT4 / Win2k type domain logons and has been officially supported for some -time.

    MS Windows XP Home edition is NOT able to join a domain and does not permit -the use of domain logons.

    Implementing a Samba PDC can basically be divided into 3 broad -steps.

    1. Configuring the Samba PDC -

    2. Creating machine trust accounts and joining clients to the domain -

    3. Adding and managing domain user accounts -

    There are other minor details such as user profiles, system +time. +

    +MS Windows XP Home edition is NOT able to join a domain and does not permit +the use of domain logons. +

    +Implementing a Samba PDC can basically be divided into 3 broad +steps. +

    1. + Configuring the Samba PDC +

    2. + Creating machine trust accounts and joining clients to the domain +

    3. + Adding and managing domain user accounts +

    +There are other minor details such as user profiles, system policies, etc... However, these are not necessarily specific to a Samba PDC as much as they are related to Windows NT networking -concepts.

    7.3. Configuring the Samba Domain Controller

    The first step in creating a working Samba PDC is to +concepts. +

    Configuring the Samba Domain Controller

    +The first step in creating a working Samba PDC is to understand the parameters necessary in smb.conf. Here we attempt to explain the parameters that are covered in -the smb.conf man page.

    Here is an example smb.conf for acting as a PDC:

    [global]
+the smb.conf man page.
+
    
+Here is an example smb.conf for acting as a PDC:
+
    +[global]
     ; Basic server settings
-    netbios name = POGO
-    workgroup = NARNIA
+    netbios name = POGO
+    workgroup = NARNIA
+
+    ; User and Machine Account Backends
+    ; Choices are: tdbsam, tdbsam_nua, smbpasswd, smbpasswd_nua, ldapsam, ldapsam_nua, ...
+    ;              mysqlsam, xmlsam, guest
+    passdb backend = ldapsam, guest
 
     ; we should act as the domain and local master browser
-    os level = 64
-    preferred master = yes
-    domain master = yes
-    local master = yes
+    os level = 64
+    preferred master = yes
+    domain master = yes
+    local master = yes
     
     ; security settings (must user security = user)
-    security = user
+    security = user
     
     ; encrypted passwords are a requirement for a PDC
-    encrypt passwords = yes
+    encrypt passwords = yes
     
     ; support domain logons
-    domain logons = yes
+    domain logons = yes
     
     ; where to store user profiles?
-    logon path = \\%N\profiles\%u
+    logon path = \\%N\profiles\%u
     
     ; where is a user's home directory and where should it be mounted at?
-    logon drive = H:
-    logon home = \\homeserver\%u
+    logon drive = H:
+    logon home = \\homeserver\%u
     
     ; specify a generic logon script for all users
     ; this is a relative **DOS** path to the [netlogon] share
-    logon script = logon.cmd
+    logon script = logon.cmd
 
 ; necessary share for domain controller
 [netlogon]
-    path = /usr/local/samba/lib/netlogon
-    read only = yes
-    write list = ntadmin
+    path = /usr/local/samba/lib/netlogon
+    read only = yes
+    write list = ntadmin
     
 ; share for storing user profiles
 [profiles]
-    path = /export/smb/ntprofile
-    read only = no
-    create mask = 0600
-    directory mask = 0700
    There are a couple of points to emphasize in the above configuration.
    • 	Encrypted passwords must be enabled.  For more details on how 
-	to do this, refer to the User Database chapter.
-	
    • 	The server must support domain logons and a
-	[netlogon] share
-	
    • 	The server must be the domain master browser in order for Windows 
+    path = /export/smb/ntprofile
+    read only = no
+    create mask = 0600
+    directory mask = 0700
+

    Note

    +The above parameters make for a full set of parameters that may define the server's mode +of operation. The following parameters are the essentials alone: + +

    +	workgroup = NARNIA
+	domain logons = Yes
+	security = User
+

    + +The additional parameters shown in the longer listing above just makes for a +more complete environment. +

    +There are a couple of points to emphasize in the above configuration. +

    • + Encrypted passwords must be enabled. For more details on how + to do this, refer to the User Database chapter. +

    • + The server must support domain logons and a + [netlogon] share +

    • + The server must be the domain master browser in order for Windows client to locate the server as a DC. Please refer to the various Network Browsing documentation included with this distribution for details. -

    Samba 3.0 offers a complete implementation of group mapping +

    +Samba 3.0 offers a complete implementation of group mapping between Windows NT groups and Unix groups (this is really quite -complicated to explain in a short space).

    7.4. Creating Machine Trust Accounts and Joining Clients to the Domain

    A machine trust account is a Samba account that is used to +complicated to explain in a short space). +

    Creating Machine Trust Accounts and Joining Clients to the Domain

    +A machine trust account is a Samba account that is used to authenticate a client machine (rather than a user) to the Samba -server. In Windows terminology, this is known as a "Computer -Account."

    The password of a machine trust account acts as the shared secret for +server. In Windows terminology, this is known as a "Computer +Account."

    +The password of a machine trust account acts as the shared secret for secure communication with the Domain Controller. This is a security feature to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group @@ -547,576 +174,204 @@ accounts. Windows NT, 200x, XP Professional clients use machine trust accounts, but Windows 9x / Me / XP Home clients do not. Hence, a Windows 9x / Me / XP Home client is never a true member of a domain because it does not possess a machine trust account, and thus has no -shared secret with the domain controller.

    A Windows PDC stores each machine trust account in the Windows -Registry. A Samba-3 PDC also has to stoe machine trust account information -in a suitable back-end data store. With Samba-3 there can be multiple back-ends -for this including:

    • smbpaswd - the plain ascii file stored used by +shared secret with the domain controller. +

      A Windows PDC stores each machine trust account in the Windows +Registry. A Samba-3 PDC also has to store machine trust account information +in a suitable backend data store. With Samba-3 there can be multiple back-ends +for this including: +

      • + smbpasswd - the plain ascii file stored used by earlier versions of Samba. This file configuration option requires a Unix/Linux system account for EVERY entry (ie: both for user and for - machine accounts). This file will be located in the private + machine accounts). This file will be located in the private directory (default is /usr/local/samba/lib/private or on linux /etc/samba). -

      • smbpasswd_nua - This file is independant of the +

      • + smbpasswd_nua - This file is independant of the system wide user accounts. The use of this back-end option requires - specification of the "non unix account range" option also. It is called - smbpasswd and will be located in the private directory. -

      • tdbsam - a binary database backend that will be - stored in the private directory in a file called - passwd.tdb. The key benefit of this binary format + specification of the "non unix account range" option also. It is called + smbpasswd and will be located in the private directory. +

      • + tdbsam - a binary database backend that will be + stored in the private directory in a file called + passwd.tdb. The key benefit of this binary format file is that it can store binary objects that can not be accomodated in the traditional plain text smbpasswd file. -

      • tdbsam_nua like the smbpasswd_nua option above, this +

      • + tdbsam_nua like the smbpasswd_nua option above, this file allows the creation of arbitrary user and machine accounts without requiring that account to be added to the system (/etc/passwd) file. It - too requires the specification of the "non unix account range" option - in the [globals] section of the smb.conf file. -

      • ldapsam - An LDAP based back-end. Permits the + too requires the specification of the "non unix account range" option + in the [globals] section of the smb.conf file. +

      • + ldapsam - An LDAP based back-end. Permits the LDAP server to be specified. eg: ldap://localhost or ldap://frodo.murphy.com -

      • ldapsam_nua - LDAP based back-end with no unix +

      • + ldapsam_nua - LDAP based back-end with no unix account requirement, like smbpasswd_nua and tdbsam_nua above. -

      Read the chapter about the User Database -for details.

      A Samba PDC, however, stores each machine trust account in two parts, +

    Read the chapter about the User Database +for details.

    Note

    +The new tdbsam and ldapsam account backends store vastly more information than +smbpasswd is capable of. The new backend database includes capacity to specify +per user settings for many parameters, over-riding global settings given in the +smb.conf file. eg: logon drive, logon home, logon path, etc. +

    +A Samba PDC, however, stores each machine trust account in two parts, as follows: -

    • A Samba account, stored in the same location as user +

      • A Samba account, stored in the same location as user LanMan and NT password hashes (currently - smbpasswd). The Samba account - possesses and uses only the NT password hash.

      • A corresponding Unix account, typically stored in - /etc/passwd. (Future releases will alleviate the need to - create /etc/passwd entries.)

      There are two ways to create machine trust accounts:

      • Manual creation. Both the Samba and corresponding - Unix account are created by hand.

      • "On-the-fly" creation. The Samba machine trust + smbpasswd). The Samba account + possesses and uses only the NT password hash.

      • A corresponding Unix account, typically stored in + /etc/passwd. (Future releases will alleviate the need to + create /etc/passwd entries.)

      +

      +There are two ways to create machine trust accounts: +

      • Manual creation. Both the Samba and corresponding + Unix account are created by hand.

      • "On-the-fly" creation. The Samba machine trust account is automatically created by Samba at the time the client is joined to the domain. (For security, this is the recommended method.) The corresponding Unix account may be - created automatically or manually.

      7.4.1. Manual Creation of Machine Trust Accounts

      The first step in manually creating a machine trust account is to + created automatically or manually.

    Manual Creation of Machine Trust Accounts

    +The first step in manually creating a machine trust account is to manually create the corresponding Unix account in -/etc/passwd. This can be done using -vipw or other 'add user' command that is normally +/etc/passwd. This can be done using +vipw or other 'add user' command that is normally used to create new Unix accounts. The following is an example for a -Linux based Samba server:

    root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine -nickname" -s /bin/false machine_name$

    root# passwd -l machine_name$

    On *BSD systems, this can be done using the 'chpass' utility:

    root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin"

    The /etc/passwd entry will list the machine name -with a "$" appended, won't have a password, will have a null shell and no +Linux based Samba server: +

    + root# /usr/sbin/useradd -g 100 -d /dev/null -c "machine +nickname" -s /bin/false machine_name$ +

    +root# passwd -l machine_name$ +

    On *BSD systems, this can be done using the 'chpass' utility:

    +root# chpass -a "machine_name$:*:101:100::0:0:Workstation machine_name:/dev/null:/sbin/nologin" +

    +The /etc/passwd entry will list the machine name +with a "$" appended, won't have a password, will have a null shell and no home directory. For example a machine named 'doppy' would have an -/etc/passwd entry like this:

    doppy$:x:505:501:machine_nickname:/dev/null:/bin/false

    Above, machine_nickname can be any +/etc/passwd entry like this: +

    +doppy$:x:505:501:machine_nickname:/dev/null:/bin/false
+

    +Above, machine_nickname can be any descriptive name for the client, i.e., BasementComputer. -machine_name absolutely must be the NetBIOS -name of the client to be joined to the domain. The "$" must be +machine_name absolutely must be the NetBIOS +name of the client to be joined to the domain. The "$" must be appended to the NetBIOS name of the client or Samba will not recognize -this as a machine trust account.

    Now that the corresponding Unix account has been created, the next step is to create +this as a machine trust account. +

    +Now that the corresponding Unix account has been created, the next step is to create the Samba account for the client containing the well-known initial -machine trust account password. This can be done using the smbpasswd(8) command -as shown here:

    root# smbpasswd -a -m machine_name

    where machine_name is the machine's NetBIOS +machine trust account password. This can be done using the smbpasswd(8) command +as shown here: +

    +root# smbpasswd -a -m machine_name +

    +where machine_name is the machine's NetBIOS name. The RID of the new machine account is generated from the UID of -the corresponding Unix account.

    Join the client to the domain immediately
     

    Manually creating a machine trust account using this method is the +the corresponding Unix account. +

    Join the client to the domain immediately

    + Manually creating a machine trust account using this method is the equivalent of creating a machine trust account on a Windows NT PDC using - the "Server Manager". From the time at which the account is created + the "Server Manager". From the time at which the account is created to the time which the client joins the domain and changes the password, - your domain is vulnerable to an intruder joining your domain using a + your domain is vulnerable to an intruder joining your domain using a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! -

    7.4.2. "On-the-Fly" Creation of Machine Trust Accounts

    The second (and recommended) way of creating machine trust accounts is +

    "On-the-Fly" Creation of Machine Trust Accounts

    +The second (and recommended) way of creating machine trust accounts is simply to allow the Samba server to create them as needed when the client -is joined to the domain.

    Since each Samba machine trust account requires a corresponding +is joined to the domain.

    Since each Samba machine trust account requires a corresponding Unix account, a method for automatically creating the Unix account is usually supplied; this requires configuration of the -add user script -option in smb.conf. This +add user script +option in smb.conf. This method is not required, however; corresponding Unix accounts may also -be created manually.

    Below is an example for a RedHat 6.2 Linux system.

    [global]
-   # <...remainder of parameters...>
-   add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u

    7.4.3. Joining the Client to the Domain

    The procedure for joining a client to the domain varies with the -version of Windows.

    • Windows 2000

      When the user elects to join the client to a domain, Windows prompts for - an account and password that is privileged to join the domain. A - Samba administrative account (i.e., a Samba account that has root - privileges on the Samba server) must be entered here; the - operation will fail if an ordinary user account is given. - The password for this account should be - set to a different password than the associated - /etc/passwd entry, for security - reasons.

      The session key of the Samba administrative account acts as an +be created manually. +

      Below is an example for a RedHat 6.2 Linux system. +

      +[global]
+   # <...remainder of parameters...>
+   add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u 
+

    Joining the Client to the Domain

    +The procedure for joining a client to the domain varies with the +version of Windows. +

    • Windows 2000

      + When the user elects to join the client to a domain, Windows prompts for + an account and password that is privileged to join the domain. A Samba administrative + account (i.e., a Samba account that has root privileges on the Samba server) must be + entered here; the operation will fail if an ordinary user account is given. + The password for this account should be set to a different password than the associated + /etc/passwd entry, for security reasons. +

      + The session key of the Samba administrative account acts as an encryption key for setting the password of the machine trust account. The machine trust account will be created on-the-fly, or - updated if it already exists.

    • Windows NT

      If the machine trust account was created manually, on the + updated if it already exists. +

    • Windows NT

      If the machine trust account was created manually, on the Identification Changes menu enter the domain name, but do not - check the box "Create a Computer Account in the Domain." In this case, + check the box "Create a Computer Account in the Domain." In this case, the existing machine trust account is used to join the machine to - the domain.

      If the machine trust account is to be created + the domain.

      If the machine trust account is to be created on-the-fly, on the Identification Changes menu enter the domain - name, and check the box "Create a Computer Account in the Domain." In + name, and check the box "Create a Computer Account in the Domain." In this case, joining the domain proceeds as above for Windows 2000 (i.e., you must supply a Samba administrative account when - prompted).

    • Samba

      Joining a samba client to a domain is documented in - the Domain Member chapter.

    7.5. Common Problems and Errors

    7.5.1. I cannot include a '$' in a machine name

    A 'machine name' in (typically) /etc/passwd + prompted).

  • Samba

    Joining a samba client to a domain is documented in + the Domain Member chapter. +

    • Common Problems and Errors

    I cannot include a '$' in a machine name

    +A 'machine name' in (typically) /etc/passwd of the machine name with a '$' appended. FreeBSD (and other BSD -systems?) won't create a user with a '$' in their name.

    The problem is only in the program used to make the entry, once -made, it works perfectly. So create a user without the '$' and -use vipw to edit the entry, adding the '$'. Or create -the whole entry with vipw if you like, make sure you use a -unique User ID !

    7.5.2. I get told "You already have a connection to the Domain...." -or "Cannot join domain, the credentials supplied conflict with an -existing set.." when creating a machine trust account.

    This happens if you try to create a machine trust account from the +systems?) won't create a user with a '$' in their name. +

    +The problem is only in the program used to make the entry. Once made, it works perfectly. +Create a user without the '$' using vipw to edit the entry, adding +the '$'. Or create the whole entry with vipw if you like, make sure you use a unique User ID! +

    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.

    +This happens if you try to create a machine trust account from the machine itself and already have a connection (e.g. mapped drive) to a share (or IPC$) on the Samba PDC. The following command -will remove all network drive connections:

    C:\WINNT\> net use * /d

    Further, if the machine is a already a 'member of a workgroup' that +will remove all network drive connections: +

    +C:\WINNT\> net use * /d +

    +Further, if the machine is already a 'member of a workgroup' that is the same name as the domain you are joining (bad idea) you will get this message. Change the workgroup name to something else, it -does not matter what, reboot, and try again.

    7.5.3. The system can not log you on (C000019B)....

    I joined the domain successfully but after upgrading -to a newer version of the Samba code I get the message, "The system +does not matter what, reboot, and try again. +

    The system can not log you on (C000019B)....

    I joined the domain successfully but after upgrading +to a newer version of the Samba code I get the message, "The system can not log you on (C000019B), Please try again or consult your -system administrator" when attempting to logon.

    This occurs when the domain SID stored in the secrets.tdb database +system administrator" when attempting to logon. +

    +This occurs when the domain SID stored in the secrets.tdb database is changed. The most common cause of a change in domain SID is when the domain name and/or the server name (netbios name) is changed. The only way to correct the problem is to restore the original domain SID or remove the domain client from the domain and rejoin. The domain -SID may be reset using either the smbpasswd or rpcclient utilities.

    7.5.4. The machine trust account for this computer either does not -exist or is not accessible.

    When I try to join the domain I get the message "The machine account -for this computer either does not exist or is not accessible". What's -wrong?

    This problem is caused by the PDC not having a suitable machine trust account. -If you are using the add user script method to create +SID may be reset using either the net or rpcclient utilities. +

    +The reset or change the domain SID you can use the net command as follows: + +

    +	net getlocalsid 'OLDNAME'
+	net setlocalsid 'SID'
+

    +

    The machine trust account for this computer either does not +exist or is not accessible.

    +When I try to join the domain I get the message "The machine account +for this computer either does not exist or is not accessible". What's +wrong? +

    +This problem is caused by the PDC not having a suitable machine trust account. +If you are using the add user script method to create accounts then this would indicate that it has not worked. Ensure the domain -admin user system is working.

    Alternatively if you are creating account entries manually then they +admin user system is working. +

    +Alternatively if you are creating account entries manually then they have not been created correctly. Make sure that you have the entry correct for the machine trust account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd @@ -1125,294 +380,119 @@ with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. Some people have reported that inconsistent subnet masks between the Samba server and the NT client have caused this problem. Make sure that these are consistent -for both client and server.

    7.5.5. When I attempt to login to a Samba Domain from a NT4/W2K workstation, -I get a message about my account being disabled.

    At first be ensure to enable the useraccounts with smbpasswd -e -%user%, this is normally done, when you create an account.

    7.6. Domain Control for Windows 9x/ME

    A domain and a workgroup are exactly the same thing in terms of network +for both client and server. +

    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.

    +At first be ensure to enable the useraccounts with smbpasswd -e +%user%, this is normally done, when you create an account. +

    Domain Control for Windows 9x/ME

    +A domain and a workgroup are exactly the same thing in terms of network browsing. The difference is that a distributable authentication database is associated with a domain, for secure login access to a network. Also, different access rights can be granted to users if they successfully authenticate against a domain logon server. Samba-3 does this -now in the same way that MS Windows NT/2K.

    The SMB client logging on to a domain has an expectation that every other +now in the same way that MS Windows NT/2K. +

    +The SMB client logging on to a domain has an expectation that every other server in the domain should accept the same authentication information. Network browsing functionality of domains and workgroups is identical and is explained in this documentation under the browsing discussions. -It should be noted, that browsing is totally orthogonal to logon support.

    Issues related to the single-logon network model are discussed in this +It should be noted, that browsing is totally orthogonal to logon support. +

    +Issues related to the single-logon network model are discussed in this section. Samba supports domain logons, network logon scripts, and user profiles for MS Windows for workgroups and MS Windows 9X/ME clients -which are the focus of this section.

    When an SMB client in a domain wishes to logon it broadcast requests for a +which are the focus of this section. +

    +When an SMB client in a domain wishes to logon it broadcast requests for a logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but very stupid) to create a domain where the user database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely -involved with domains.

    Using these features you can make your clients verify their logon via +involved with domains. +

    +Using these features you can make your clients verify their logon via the Samba server; make clients run a batch file when they logon to -the network and download their preferences, desktop and start menu.

    Before launching into the configuration instructions, it is -worthwhile lookingat how a Windows 9x/ME client performs a logon:

    1. The client broadcasts (to the IP broadcast address of the subnet it is in) - a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the +the network and download their preferences, desktop and start menu. +

      +Before launching into the configuration instructions, it is +worthwhile to look at how a Windows 9x/ME client performs a logon: +

      1. + The client broadcasts (to the IP broadcast address of the subnet it is in) + a NetLogon request. This is sent to the NetBIOS name DOMAIN<1c> at the NetBIOS layer. The client chooses the first response it receives, which contains the NetBIOS name of the logon server to use in the format of \\SERVER. -

      2. The client then connects to that server, logs on (does an SMBsessetupX) and +

      3. + The client then connects to that server, logs on (does an SMBsessetupX) and then connects to the IPC$ share (using an SMBtconX). -

      4. The client then does a NetWkstaUserLogon request, which retrieves the name +

      5. + The client then does a NetWkstaUserLogon request, which retrieves the name of the user's logon script. -

      6. The client then connects to the NetLogon share and searches for this +

      7. + The client then connects to the NetLogon share and searches for this and if it is found and can be read, is retrieved and executed by the client. After this, the client disconnects from the NetLogon share. -

      8. The client then sends a NetUserGetInfo request to the server, to retrieve +

      9. + The client then sends a NetUserGetInfo request to the server, to retrieve the user's home share, which is used to search for profiles. Since the - response to the NetUserGetInfo request does not contain much more + response to the NetUserGetInfo request does not contain much more then the user's home share, profiles for Win9X clients MUST reside in the user home directory. -

      10. The client then connects to the user's home share and searches for the +

      11. + The client then connects to the user's home share and searches for the user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. -

      12. The client then disconnects from the user's home share, and reconnects to +

      13. + The client then disconnects from the user's home share, and reconnects to the NetLogon share and looks for CONFIG.POL, the policies file. If this is found, it is read and implemented. -

      7.6.1. Configuration Instructions: Network Logons

      The main difference between a PDC and a Windows 9x logon -server configuration is that

      • Password encryption is not required for a Windows 9x logon server.

      • Windows 9x/ME clients do not possess machine trust accounts.

      Therefore, a Samba PDC will also act as a Windows 9x logon -server.

      security mode and master browsers
       

      There are a few comments to make in order to tie up some +

      Configuration Instructions: Network Logons

      +The main difference between a PDC and a Windows 9x logon +server configuration is that +

      • +Password encryption is not required for a Windows 9x logon server. +

      • +Windows 9x/ME clients do not possess machine trust accounts. +

      +Therefore, a Samba PDC will also act as a Windows 9x logon +server. +

      security mode and master browsers

      +There are a few comments to make in order to tie up some loose ends. There has been much debate over the issue of whether or not it is ok to configure Samba as a Domain Controller in security -modes other than USER. The only security mode -which will not work due to technical reasons is SHARE -mode security. DOMAIN and SERVER -mode security is really just a variation on SMB user level security.

      Actually, this issue is also closely tied to the debate on whether +modes other than USER. The only security mode +which will not work due to technical reasons is SHARE +mode security. DOMAIN and SERVER +mode security is really just a variation on SMB user level security. +

      +Actually, this issue is also closely tied to the debate on whether or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons -are two distinctly different functions), it is not a good idea to +are two distinctly different functions), it is not a good idea to do so. You should remember that the DC must register the DOMAIN#1b NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. -For this reason, it is very wise to configure the Samba DC as the DMB.

      Now back to the issue of configuring a Samba DC to use a mode other -than "security = user". If a Samba host is configured to use +For this reason, it is very wise to configure the Samba DC as the DMB. +

      +Now back to the issue of configuring a Samba DC to use a mode other +than "security = user". If a Samba host is configured to use another SMB server or DC in order to validate user connection requests, then it is a fact that some other machine on the network -(the "password server") knows more about user than the Samba host. +(the "password server") knows more about the user than the Samba host. 99% of the time, this other host is a domain controller. Now -in order to operate in domain mode security, the "workgroup" parameter +in order to operate in domain mode security, the "workgroup" parameter must be set to the name of the Windows NT domain (which already -has a domain controller, right?)

      Therefore configuring a Samba box as a DC for a domain that +has a domain controller, right?) +

      +Therefore configuring a Samba box as a DC for a domain that already by definition has a PDC is asking for trouble. Therefore, you should always configure the Samba DC to be the DMB -for its domain.

    PrevHomeNext
    Samba as Stand-Alone ServerUpSamba Backup Domain Controller to Samba Domain Control
    \ No newline at end of file +for its domain. +

    PrevUpNext
    Chapter4.Samba as Stand-Alone ServerHomeChapter6. +Samba Backup Domain Controller to Samba Domain Control +
    diff --git a/docs/htmldocs/samba.7.html b/docs/htmldocs/samba.7.html index 728f42f6f9..a54d3e883f 100644 --- a/docs/htmldocs/samba.7.html +++ b/docs/htmldocs/samba.7.html @@ -1,756 +1,116 @@ - -samba

    samba

    Name

    Samba -- A Windows SMB/CIFS fileserver for UNIX

    Synopsis

    Samba

    DESCRIPTION

    The Samba software suite is a collection of programs +samba

    Name

    Samba — A Windows SMB/CIFS fileserver for UNIX

    Synopsis

    Samba

    DESCRIPTION

    The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems. This protocol is sometimes also referred to as the Common Internet File System (CIFS). For a - more thorough description, see http://www.ubiqx.org/cifs/. Samba also implements the NetBIOS - protocol in nmbd.

    smbd(8)

    The smbd daemon provides the file and print services to + more thorough description, see + http://www.ubiqx.org/cifs/. Samba also implements the NetBIOS + protocol in nmbd.

    smbd(8)

    The smbd daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file - for this daemon is described in smb.conf(5) -

    nmbd(8)

    The nmbd + for this daemon is described in smb.conf(5) +

    nmbd(8)

    The nmbd daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon - is described in smb.conf(5)

    smbclient(1)

    The smbclient + is described in smb.conf(5)

    smbclient(1)

    The smbclient program implements a simple ftp-like client. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to - any SMB server (such as a PC running Windows NT).

    testparm(1)

    The testparm - utility is a simple syntax checker for Samba's smb.conf(5) configuration file.

    testprns(1)

    The testprns + any SMB server (such as a PC running Windows NT).

    testparm(1)

    The testparm + utility is a simple syntax checker for Samba's smb.conf(5) configuration file.

    testprns(1)

    The testprns utility supports testing printer names defined - in your printcap file used - by Samba.

    smbstatus(1)

    The smbstatus + in your printcap file used + by Samba.

    smbstatus(1)

    The smbstatus tool provides access to information about the - current connections to smbd.

    nmblookup(1)

    The nmblookup + current connections to smbd.

    nmblookup(1)

    The nmblookup tools allows NetBIOS name queries to be made - from a UNIX host.

    smbgroupedit(8)

    The smbgroupedit + from a UNIX host.

    smbgroupedit(8)

    The smbgroupedit tool allows for mapping unix groups to NT Builtin, Domain, or Local groups. Also it allows setting - priviledges for that group, such as saAddUser, etc.

    smbpasswd(8)

    The smbpasswd + priviledges for that group, such as saAddUser, etc.

    smbpasswd(8)

    The smbpasswd command is a tool for changing LanMan and Windows NT - password hashes on Samba and Windows NT servers.

    smbcacls(1)

    The smbcacls command is - a tool to set ACL's on remote CIFS servers.

    smbsh(1)

    The smbsh command is + password hashes on Samba and Windows NT servers.

    smbcacls(1)

    The smbcacls command is + a tool to set ACL's on remote CIFS servers.

    smbsh(1)

    The smbsh command is a program that allows you to run a unix shell with - with an overloaded VFS.

    smbtree(1)

    The smbtree command - is a text-based network neighborhood tool.

    smbtar(1)

    The smbtar can make - backups of data on CIFS/SMB servers.

    smbspool(8)

    smbspool is a + with an overloaded VFS.

    smbtree(1)

    The smbtree command + is a text-based network neighborhood tool.

    smbtar(1)

    The smbtar can make + backups of data on CIFS/SMB servers.

    smbspool(8)

    smbspool is a helper utility for printing on printers connected - to CIFS servers.

    smbcontrol(1)

    smbcontrol is a utility + to CIFS servers.

    smbcontrol(1)

    smbcontrol is a utility that can change the behaviour of running samba daemons. -

    rpcclient(1)

    rpcclient is a utility +

    rpcclient(1)

    rpcclient is a utility that can be used to execute RPC commands on remote - CIFS servers.

    pdbedit(8)

    The pdbedit command + CIFS servers.

    pdbedit(8)

    The pdbedit command can be used to maintain the local user database on - a samba server.

    findsmb(1)

    The findsmb command + a samba server.

    findsmb(1)

    The findsmb command can be used to find SMB servers on the local network. -

    net(8)

    The net command +

    net(8)

    The net command is supposed to work similar to the DOS/Windows - NET.EXE command.

    swat(8)

    swat is a web-based - interface to configuring smb.conf. -

    winbindd(8)

    winbindd is a daemon + NET.EXE command.

    swat(8)

    swat is a web-based + interface to configuring smb.conf. +

    winbindd(8)

    winbindd is a daemon that is used for integrating authentication and - the user database into unix.

    wbinfo(1)

    wbinfo is a utility + the user database into unix.

    wbinfo(1)

    wbinfo is a utility that retrieves and stores information related to winbind. -

    editreg(1)

    editreg is a command-line +

    editreg(1)

    editreg is a command-line utility that can edit windows registry files. -

    profiles(1)

    profiles is a command-line +

    profiles(1)

    profiles is a command-line utility that can be used to replace all occurences of a certain SID with another SID. -

    vfstest(1)

    vfstest is a utility - that can be used to test vfs modules.

    ntlm_auth(1)

    ntlm_auth is a helper-utility +

    vfstest(1)

    vfstest is a utility + that can be used to test vfs modules.

    ntlm_auth(1)

    ntlm_auth is a helper-utility for external programs wanting to do NTLM-authentication. -

    smbmount(8), smbumount(8), smbmount(8)

    smbmount,smbmnt and smbmnt are commands that can be used to +

    smbmount(8), smbumount(8), smbmount(8)

    smbmount,smbmnt and smbmnt are commands that can be used to mount CIFS/SMB shares on Linux. -

    smbcquotas(1)

    smbcquotas is a tool that - can set remote QUOTA's on server with NTFS 5.

    COMPONENTS

    The Samba suite is made up of several components. Each +

    smbcquotas(1)

    smbcquotas is a tool that + can set remote QUOTA's on server with NTFS 5.

    COMPONENTS

    The Samba suite is made up of several components. Each component is described in a separate manual page. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use. If the manual pages and documents aren't clear enough then please visit - http://devel.samba.org - for information on how to file a bug report or submit a patch.

    If you require help, visit the Samba webpage at - http://www.samba.org/ and + http://devel.samba.org + for information on how to file a bug report or submit a patch.

    If you require help, visit the Samba webpage at + http://www.samba.org/ and explore the many option available to you. -

    AVAILABILITY

    The Samba software suite is licensed under the +

    AVAILABILITY

    The Samba software suite is licensed under the GNU Public License(GPL). A copy of that license should have come with the package in the file COPYING. You are encouraged to distribute copies of the Samba suite, but - please obey the terms of this license.

    The latest version of the Samba suite can be + please obey the terms of this license.

    The latest version of the Samba suite can be obtained via anonymous ftp from samba.org in the directory pub/samba/. It is also available on several - mirror sites worldwide.

    You may also find useful information about Samba - on the newsgroup comp.protocol.smb and the Samba mailing + mirror sites worldwide.

    You may also find useful information about Samba + on the newsgroup + comp.protocol.smb and the Samba mailing list. Details on how to join the mailing list are given in - the README file that comes with Samba.

    If you have access to a WWW viewer (such as Mozilla + the README file that comes with Samba.

    If you have access to a WWW viewer (such as Mozilla or Konqueror) then you will also find lots of useful information, including back issues of the Samba mailing list, at - http://lists.samba.org.

    VERSION

    This man page is correct for version 3.0 of the - Samba suite.

    CONTRIBUTIONS

    If you wish to contribute to the Samba project, + http://lists.samba.org.

    VERSION

    This man page is correct for version 3.0 of the + Samba suite.

    CONTRIBUTIONS

    If you wish to contribute to the Samba project, then I suggest you join the Samba mailing list at - http://lists.samba.org. -

    If you have patches to submit, visit - http://devel.samba.org/ + http://lists.samba.org. +

    If you have patches to submit, visit + http://devel.samba.org/ for information on how to do it properly. We prefer patches - in diff -u format.

    CONTRIBUTORS

    Contributors to the project are now too numerous + in diff -u format.

    CONTRIBUTORS

    Contributors to the project are now too numerous to mention here but all deserve the thanks of all Samba - users. To see a full list, look at ftp://samba.org/pub/samba/alpha/change-log - for the pre-CVS changes and at ftp://samba.org/pub/samba/alpha/cvs.log + users. To see a full list, look at + ftp://samba.org/pub/samba/alpha/change-log + for the pre-CVS changes and at + ftp://samba.org/pub/samba/alpha/cvs.log for the contributors to Samba post-CVS. CVS is the Open Source source code control system used by the Samba Team to develop - Samba. The project would have been unmanageable without it.

    In addition, several commercial organizations now help + Samba. The project would have been unmanageable without it.

    In addition, several commercial organizations now help fund the Samba Team with money and equipment. For details see - the Samba Web pages at http://samba.org/samba/samba-thanks.html.

    AUTHOR

    The original Samba software and related utilities + the Samba Web pages at + http://samba.org/samba/samba-thanks.html.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML - 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + 4.2 for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/securing-samba.html b/docs/htmldocs/securing-samba.html index 7fd34c5fa5..ae6408ea7b 100644 --- a/docs/htmldocs/securing-samba.html +++ b/docs/htmldocs/securing-samba.html @@ -1,357 +1,116 @@ - -Securing Samba
    SAMBA Project Documentation
    PrevNext

    Chapter 25. Securing Samba

    25.1. Introduction

    This note was attached to the Samba 2.2.8 release notes as it contained an + +Chapter24.Securing Samba

    Chapter24.Securing Samba
    PrevPartIII.Advanced ConfigurationNext

    Chapter24.Securing Samba

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    17 March 2003

    Table of Contents

    Introduction
    Using host based protection
    Using interface protection
    Using a firewall
    Using a IPC$ share deny
    NTLMv2 Security
    Upgrading Samba

    Introduction

    +This note was attached to the Samba 2.2.8 release notes as it contained an important security fix. The information contained here applies to Samba -installations in general.

    25.2. Using host based protection

    In many installations of Samba the greatest threat comes for outside +installations in general. +

    Using host based protection

    +In many installations of Samba the greatest threat comes for outside your immediate network. By default Samba will accept connections from any host, which means that if you run an insecure version of Samba on a host that is directly connected to the Internet you can be -especially vulnerable.

    One of the simplest fixes in this case is to use the hosts allow and -hosts deny options in the Samba smb.conf configuration file to only +especially vulnerable. +

    +One of the simplest fixes in this case is to use the hosts allow and +hosts deny options in the Samba smb.conf configuration file to only allow access to your server from a specific range of hosts. An example -might be:

      hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
-  hosts deny = 0.0.0.0/0

    The above will only allow SMB connections from 'localhost' (your own +might be: +

    +	hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
+	hosts deny = 0.0.0.0/0
+

    +The above will only allow SMB connections from 'localhost' (your own computer) and from the two private networks 192.168.2 and -192.168.3. All other connections will be refused connections as soon +192.168.3. All other connections will be refused as soon as the client sends its first packet. The refusal will be marked as a -'not listening on called name' error.

    25.3. Using interface protection

    By default Samba will accept connections on any network interface that +'not listening on called name' error. +

    Using interface protection

    +By default Samba will accept connections on any network interface that it finds on your system. That means if you have a ISDN line or a PPP connection to the Internet then Samba will accept connections on those -links. This may not be what you want.

    You can change this behaviour using options like the following:

      interfaces = eth* lo
-  bind interfaces only = yes

    This tells Samba to only listen for connections on interfaces with a +links. This may not be what you want. +

    +You can change this behaviour using options like the following: +

    +	interfaces = eth* lo
+	bind interfaces only = yes
+

    +This tells Samba to only listen for connections on interfaces with a name starting with 'eth' such as eth0, eth1, plus on the loopback interface called 'lo'. The name you will need to use depends on what OS you are using, in the above I used the common name for Ethernet -adapters on Linux.

    If you use the above and someone tries to make a SMB connection to +adapters on Linux. +

    +If you use the above and someone tries to make a SMB connection to your host over a PPP interface called 'ppp0' then they will get a TCP connection refused reply. In that case no Samba code is run at all as the operating system has been told not to pass connections from that -interface to any process.

    25.4. Using a firewall

    Many people use a firewall to deny access to services that they don't +interface to any samba process. +

    Using a firewall

    +Many people use a firewall to deny access to services that they don't want exposed outside their network. This can be a very good idea, although I would recommend using it in conjunction with the above methods so that you are protected even if your firewall is not active -for some reason.

    If you are setting up a firewall then you need to know what TCP and -UDP ports to allow and block. Samba uses the following:

    UDP/137    - used by nmbd
-UDP/138    - used by nmbd
-TCP/139    - used by smbd
-TCP/445    - used by smbd

    The last one is important as many older firewall setups may not be +for some reason. +

    +If you are setting up a firewall then you need to know what TCP and +UDP ports to allow and block. Samba uses the following: +

    +	UDP/137    - used by nmbd
+	UDP/138    - used by nmbd
+	TCP/139    - used by smbd
+	TCP/445    - used by smbd
+

    +The last one is important as many older firewall setups may not be aware of it, given that this port was only added to the protocol in -recent years.

    25.5. Using a IPC$ share deny

    If the above methods are not suitable, then you could also place a +recent years. +

    Using a IPC$ share deny

    +If the above methods are not suitable, then you could also place a more specific deny on the IPC$ share that is used in the recently discovered security hole. This allows you to offer access to other shares while denying access to IPC$ from potentially untrustworthy -hosts.

    To do that you could use:

      [ipc$]
-     hosts allow = 192.168.115.0/24 127.0.0.1
-     hosts deny = 0.0.0.0/0

    this would tell Samba that IPC$ connections are not allowed from +hosts. +

    +To do that you could use: +

    +	[ipc$]
+	     hosts allow = 192.168.115.0/24 127.0.0.1
+	     hosts deny = 0.0.0.0/0
+

    +this would tell Samba that IPC$ connections are not allowed from anywhere but the two listed places (localhost and a local subnet). Connections to other shares would still be allowed. As the IPC$ share is the only share that is always accessible anonymously this provides some level of protection against attackers that do not -know a username/password for your host.

    If you use this method then clients will be given a 'access denied' +know a username/password for your host. +

    +If you use this method then clients will be given a 'access denied' reply when they try to access the IPC$ share. That means that those clients will not be able to browse shares, and may also be unable to -access some other resources.

    This is not recommended unless you cannot use one of the other -methods listed above for some reason.

    25.6. Upgrading Samba

    Please check regularly on http://www.samba.org/ for updates and +access some other resources. +

    +This is not recommended unless you cannot use one of the other +methods listed above for some reason. +

    NTLMv2 Security

    +To configure NTLMv2 authentication the following registry keys are worth knowing about: +

    +

    +	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
+	"lmcompatibilitylevel"=dword:00000003
+
+	0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
+	use NTLMv2 session security if the server supports it. Domain
+	controllers accept LM, NTLM and NTLMv2 authentication.
+
+	[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
+	"NtlmMinClientSec"=dword:00080000
+
+	0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
+	NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
+	session security is not negotiated.
+

    +

    Upgrading Samba

    +Please check regularly on http://www.samba.org/ for updates and important announcements. Occasionally security releases are made and it is highly recommended to upgrade Samba when a security vulnerability -is discovered.

    PrevHomeNext
    Improved browsing in sambaUpUnicode/Charsets
    \ No newline at end of file +is discovered. +

    PrevUpNext
    Chapter23.Integrating MS Windows networks with SambaHomeChapter25.Unicode/Charsets
    diff --git a/docs/htmldocs/securitylevels.html b/docs/htmldocs/securitylevels.html index ed8bc3f45f..ddfb22536b 100644 --- a/docs/htmldocs/securitylevels.html +++ b/docs/htmldocs/securitylevels.html @@ -1,160 +1,42 @@ - -Samba as Stand-Alone Server
    SAMBA Project Documentation
    PrevNext

    Chapter 6. Samba as Stand-Alone Server

    In this section the function and purpose of Samba's security -modes are described.

    6.1. User and Share security level

    A SMB server tells the client at startup what "security level" it is -running. There are two options "share level" and "user level". Which + +Chapter4.Samba as Stand-Alone Server

    Chapter4.Samba as Stand-Alone Server
    PrevPartII.Server Configuration BasicsNext

    Chapter4.Samba as Stand-Alone Server

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Table of Contents

    User and Share security level
    User Level Security
    Share Level Security
    Server Level Security
    Domain Level Security
    ADS Level Security

    +In this section the function and purpose of Samba's security +modes are described. +

    User and Share security level

    +A SMB server tells the client at startup what "security level" it is +running. There are two options "share level" and "user level". Which of these two the client receives affects the way the client then tries to authenticate itself. It does not directly affect (to any great extent) the way the Samba server does security. I know this is strange, but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is -allowed.

    6.1.1. User Level Security

    I'll describe user level security first, as its simpler. In user level -security the client will send a "session setup" command directly after +allowed. +

    User Level Security

    +I'll describe user level security first, as its simpler. In user level +security the client will send a "session setup" command directly after the protocol negotiation. This contains a username and password. The server can either accept or reject that username/password combination. Note that at this stage the server has no idea what share the client will eventually try to connect to, so it can't base -the "accept/reject" on anything other than:

    1. the username/password

    2. the machine that the client is coming from

    If the server accepts the username/password then the client expects to -be able to mount any share (using a "tree connection") without +the "accept/reject" on anything other than: +

    1. the username/password

    2. the machine that the client is coming from

    +If the server accepts the username/password then the client expects to +be able to mount any share (using a "tree connection") without specifying a password. It expects that all access rights will be as -the username/password specified in the "session setup".

    It is also possible for a client to send multiple "session setup" -requests. When the server responds it gives the client a "uid" to use +the username/password specified in the "session setup". +

    +It is also possible for a client to send multiple "session setup" +requests. When the server responds it gives the client a "uid" to use as an authentication tag for that username/password. The client can maintain multiple authentication contexts in this way (WinDD is an -example of an application that does this)

    6.1.2. Share Level Security

    Ok, now for share level security. In share level security the client +example of an application that does this) +

    Share Level Security

    +Ok, now for share level security. In share level security the client authenticates itself separately for each share. It will send a -password along with each "tree connection" (share mount). It does not +password along with each "tree connection" (share mount). It does not explicitly send a username with this operation. The client is expecting a password to be associated with each share, independent of the user. This means that samba has to work out what username the @@ -162,380 +44,169 @@ client probably wants to use. It is never explicitly sent the username. Some commercial SMB servers such as NT actually associate passwords directly with shares in share level security, but samba always uses the unix authentication scheme where it is a -username/password that is authenticated, not a "share/password".

    Many clients send a "session setup" even if the server is in share +username/password that is authenticated, not a "share/password". +

    +Many clients send a "session setup" even if the server is in share level security. They normally send a valid username but no -password. Samba records this username in a list of "possible -usernames". When the client then does a "tree connection" it also adds +password. Samba records this username in a list of "possible +usernames". When the client then does a "tree connection" it also adds to this list the name of the share they try to connect to (useful for -home directories) and any users listed in the user = smb.conf -line. The password is then checked in turn against these "possible -usernames". If a match is found then the client is authenticated as -that user.

    6.1.3. Server Level Security

    Finally "server level" security. In server level security the samba +home directories) and any users listed in the user = smb.conf +line. The password is then checked in turn against these "possible +usernames". If a match is found then the client is authenticated as +that user. +

    Server Level Security

    +Finally "server level" security. In server level security the samba server reports to the client that it is in user level security. The -client then does a "session setup" as described earlier. The samba +client then does a "session setup" as described earlier. The samba server takes the username/password that the client sends and attempts -to login to the "password server" by sending exactly the same +to login to the "password server" by sending exactly the same username/password that it got from the client. If that server is in user level security and accepts the password then samba accepts the clients connection. This allows the samba server to use another SMB -server as the "password server".

    You should also note that at the very start of all this, where the +server as the "password server". +

    +You should also note that at the very start of all this, where the server tells the client what security level it is in, it also tells the client if it supports encryption. If it does then it supplies the -client with a random "cryptkey". The client will then send all +client with a random "cryptkey". The client will then send all passwords in encrypted form. You have to compile samba with encryption enabled to support this feature, and you have to maintain a separate smbpasswd file with SMB style encrypted passwords. It is cryptographically impossible to translate from unix style encryption to SMB style encryption, although there are some fairly simple management -schemes by which the two could be kept in sync.

    "security = server" means that Samba reports to clients that -it is running in "user mode" but actually passes off all authentication -requests to another "user mode" server. This requires an additional -parameter "password server =" that points to the real authentication server. +schemes by which the two could be kept in sync. +

    +"security = server" means that Samba reports to clients that +it is running in "user mode" but actually passes off all authentication +requests to another "user mode" server. This requires an additional +parameter "password server =" that points to the real authentication server. That real authentication server can be another Samba server or can be a -Windows NT server, the later natively capable of encrypted password support.

    6.1.3.1. Configuring Samba for Seemless Windows Network Integration

    MS Windows clients may use encrypted passwords as part of a challenege/response +Windows NT server, the later natively capable of encrypted password support. +

    Note

    +Server level security is incompatible with what is known +as schannel or "sign and seal" protocols. This means that +if you want to use server level security you must disable +the use of "sign and seal" on all machines on your network. +

    Configuring Samba for Seemless Windows Network Integration

    +MS Windows clients may use encrypted passwords as part of a challenege/response authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple password based authentication. It should be realized that with the SMB protocol the password is passed over the network either in plain text or encrypted, but -not both in the same authentication requests.

    When encrypted passwords are used a password that has been entered by the user -is encrypted in two ways:

    • An MD4 hash of the UNICODE of the password +not both in the same authentication request. +

      +When encrypted passwords are used a password that has been entered by the user +is encrypted in two ways: +

      • An MD4 hash of the UNICODE of the password string. This is known as the NT hash. -

      • The password is converted to upper case, +

      • The password is converted to upper case, and then padded or trucated to 14 bytes. This string is then appended with 5 bytes of NULL characters and split to - form two 56 bit DES keys to encrypt a "magic" 8 byte value. + form two 56 bit DES keys to encrypt a "magic" 8 byte value. The resulting 16 bytes for the LanMan hash. -

      MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 +

    +MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 pre-service pack 3 will use either mode of password authentication. All versions of MS Windows that follow these versions no longer support plain -text passwords by default.

    MS Windows clients have a habit of dropping network mappings that have been idle +text passwords by default. +

    +MS Windows clients have a habit of dropping network mappings that have been idle for 10 minutes or longer. When the user attempts to use the mapped drive connection that has been dropped, the client re-establishes the connection using -a cached copy of the password.

    When Microsoft changed the default password mode, support was dropped for caching +a cached copy of the password. +

    +When Microsoft changed the default password mode, support was dropped for caching of the plain text password. This means that when the registry parameter is changed to re-enable use of plain text passwords it appears to work, but when a dropped service connection mapping attempts to revalidate it will fail if the remote authentication server does not support encrypted passwords. This means that it -is definitely not a good idea to re-enable plain text password support in such clients.

    The following parameters can be used to work around the issue of Windows 9x client +is definitely not a good idea to re-enable plain text password support in such clients. +

    +The following parameters can be used to work around the issue of Windows 9x client upper casing usernames and password before transmitting them to the SMB server -when using clear text authentication.

    	passsword level = integer
-	username level = integer

    By default Samba will lower case the username before attempting to lookup the user +when using clear text authentication. +

    +	passsword level = integer
+	username level = integer
+

    +By default Samba will lower case the username before attempting to lookup the user in the database of local system accounts. Because UNIX usernames conventionally -only contain lower case character, the username level parameter -is rarely needed.

    However, passwords on UNIX systems often make use of mixed case characters. +only contain lower case character, the username level parameter +is rarely needed. +

    +However, passwords on UNIX systems often make use of mixed case characters. This means that in order for a user on a Windows 9x client to connect to a Samba -server using clear text authentication, the password level -must be set to the maximum number of upper case letter which could -appear is a password. Note that is the server OS uses the traditional DES version -of crypt(), then a password level of 8 will result in case +server using clear text authentication, the password level +must be set to the maximum number of upper case letter which could +appear is a password. Note that the server OS uses the traditional DES version +of crypt(), a password level of 8 will result in case insensitive passwords as seen from Windows users. This will also result in longer -login times as Samba hash to compute the permutations of the password string and -try them one by one until a match is located (or all combinations fail).

    The best option to adopt is to enable support for encrypted passwords +login times as Samba has to compute the permutations of the password string and +try them one by one until a match is located (or all combinations fail). +

    +The best option to adopt is to enable support for encrypted passwords where ever Samba is used. There are three configuration possibilities -for support of encrypted passwords:

    6.1.3.2. Use MS Windows NT as an authentication server

    This method involves the additions of the following parameters in the smb.conf file:

    	encrypt passwords = Yes
+for support of encrypted passwords:
+

    Use MS Windows NT as an authentication server

    +This method involves the additions of the following parameters in the smb.conf file: +

    +	encrypt passwords = Yes
 	security = server
-	password server = "NetBIOS_name_of_PDC"

    There are two ways of identifying whether or not a username and + password server = "NetBIOS_name_of_PDC" +

    +There are two ways of identifying whether or not a username and password pair was valid or not. One uses the reply information provided as part of the authentication messaging process, the other uses -just and error code.

    The down-side of this mode of configuration is the fact that +just an error code. +

    +The down-side of this mode of configuration is the fact that for security reasons Samba will send the password server a bogus username and a bogus password and if the remote server fails to reject the username and password pair then an alternative mode of identification of validation is used. Where a site uses password lock out after a certain number of failed authentication attempts -this will result in user lockouts.

    Use of this mode of authentication does require there to be +this will result in user lockouts. +

    +Use of this mode of authentication does require there to be a standard Unix account for the user, this account can be blocked -to prevent logons by other than MS Windows clients.

    6.1.4. Domain Level Security

    When samba is operating in security = domain mode this means that +to prevent logons by other than MS Windows clients. +

    Domain Level Security

    +When samba is operating in security = domain mode this means that the Samba server has a domain security trust account (a machine account) and will cause -all authentication requests to be passed through to the domain controllers.

    6.1.4.1. Samba as a member of an MS Windows NT security domain

    This method involves additon of the following paramters in the smb.conf file:

    	encrypt passwords = Yes
+all authentication requests to be passed through to the domain controllers.
+
    Samba as a member of an MS Windows NT security domain
    
+This method involves addition of the following parameters in the smb.conf file:
+
    +	encrypt passwords = Yes
 	security = domain
-	workgroup = "name of NT domain"
-	password server = *
    The use of the "*" argument to password server will cause samba to locate the
+	workgroup = "name of NT domain"
+	password server = *
+

    +The use of the "*" argument to password server will cause samba to locate the domain controller in a way analogous to the way this is done within MS Windows NT. -This is the default behaviour.

    In order for this method to work the Samba server needs to join the -MS Windows NT security domain. This is done as follows:

    • On the MS Windows NT domain controller using +This is the default behaviour. +

      +In order for this method to work the Samba server needs to join the +MS Windows NT security domain. This is done as follows: +

      • On the MS Windows NT domain controller using the Server Manager add a machine account for the Samba server. -

      • Next, on the Linux system execute: - smbpasswd -r PDC_NAME -j DOMAIN_NAME -

      Use of this mode of authentication does require there to be a standard Unix account +

    • Next, on the Linux system execute: + smbpasswd -r PDC_NAME -j DOMAIN_NAME (samba 2.x) + + net join -U administrator%password (samba-3) +

    +Use of this mode of authentication does require there to be a standard Unix account for the user in order to assign a uid once the account has been authenticated by -the remote Windows DC. This account can be blocked to prevent logons by other than -MS Windows clients by things such as setting an invalid shell in the -/etc/passwd entry.

    An alternative to assigning UIDs to Windows users on a Samba member server is -presented in the Winbind Overview chapter -in this HOWTO collection.

    6.1.5. ADS Level Security

    For information about the configuration option please refer to the entire section entitled -Samba as an ADS Domain Member.

    PrevHomeNext
    Nomenclature of Server TypesUpSamba as an NT4 or Win2k Primary Domain Controller
    \ No newline at end of file +the remote Windows DC. This account can be blocked to prevent logons by clients other than +MS Windows through things such as setting an invalid shell in the +/etc/passwd entry. +

    +An alternative to assigning UIDs to Windows users on a Samba member server is +presented in the Winbind Overview chapter +in this HOWTO collection. +

    ADS Level Security

    +For information about the configuration option please refer to the entire section entitled +Samba as an ADS Domain Member. +

    PrevUpNext
    Chapter3.Nomenclature of Server TypesHomeChapter5. +Samba as an NT4 or Win2k Primary Domain Controller +
    diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index dc4b0c3541..3a54a894ac 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -1,18588 +1,3103 @@ - -smb.conf

    smb.conf

    Name

    smb.conf -- The configuration file for the Samba suite

    SYNOPSIS

    The smb.conf file is a configuration - file for the Samba suite. smb.conf contains - runtime configuration information for the Samba programs. The smb.conf file - is designed to be configured and administered by the swat(8) program. The complete +smb.conf

    Name

    smb.conf — The configuration file for the Samba suite

    SYNOPSIS

    The smb.conf file is a configuration + file for the Samba suite. smb.conf contains + runtime configuration information for the Samba programs. The smb.conf file + is designed to be configured and administered by the swat(8) program. The complete description of the file format and possible parameters held within - are here for reference purposes.

    FILE FORMAT

    The file consists of sections and parameters. A section + are here for reference purposes.

    FILE FORMAT

    The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain parameters of the - form

    name = value -

    The file is line-based - that is, each newline-terminated - line represents either a comment, a section name or a parameter.

    Section and parameter names are not case sensitive.

    Only the first equals sign in a parameter is significant. + form

    name = value +

    The file is line-based - that is, each newline-terminated + line represents either a comment, a section name or a parameter.

    Section and parameter names are not case sensitive.

    Only the first equals sign in a parameter is significant. Whitespace before or after the first equals sign is discarded. Leading, trailing and internal whitespace in section and parameter names is irrelevant. Leading and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value - is retained verbatim.

    Any line beginning with a semicolon (';') or a hash ('#') - character is ignored, as are lines containing only whitespace.

    Any line ending in a '\' is continued - on the next line in the customary UNIX fashion.

    The values following the equals sign in parameters are all + is retained verbatim.

    Any line beginning with a semicolon (';') or a hash ('#') + character is ignored, as are lines containing only whitespace.

    Any line ending in a '\' is continued + on the next line in the customary UNIX fashion.

    The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or true/false. Case is not significant in boolean values, but is preserved in string values. Some items such as - create modes are numeric.

    SECTION DESCRIPTIONS

    Each section in the configuration file (except for the + create modes are numeric.

    SECTION DESCRIPTIONS

    Each section in the configuration file (except for the [global] section) describes a shared resource (known - as a "share"). The section name is the name of the + as a "share"). The section name is the name of the shared resource and the parameters within the section define - the shares attributes.

    There are three special sections, [global], + the shares attributes.

    There are three special sections, [global], [homes] and [printers], which are - described under special sections. The - following notes apply to ordinary section descriptions.

    A share consists of a directory to which access is being + described under special sections. The + following notes apply to ordinary section descriptions.

    A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service. Some housekeeping options are - also specifiable.

    Sections are either file share services (used by the + also specifiable.

    Sections are either file share services (used by the client as an extension of their native file systems) or printable services (used by the client to access print services - on the host running the server).

    Sections may be designated guest services, + on the host running the server).

    Sections may be designated guest services, in which case no password is required to access them. A specified - UNIX guest account is used to define access - privileges in this case.

    Sections other than guest services will require a password + UNIX guest account is used to define access + privileges in this case.

    Sections other than guest services will require a password to access them. The client provides the username. As older clients only provide passwords and not usernames, you may specify a list - of usernames to check against the password using the "user =" + of usernames to check against the password using the "user =" option in the share definition. For modern clients such as - Windows 95/98/ME/NT/2000, this should not be necessary.

    Note that the access rights granted by the server are + Windows 95/98/ME/NT/2000, this should not be necessary.

    Note that the access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system. The server does not grant more - access than the host system grants.

    The following sample section defines a file space share. - The user has write access to the path /home/bar. - The share is accessed via the share name "foo":

        [foo]
+	access than the host system grants.
    The following sample section defines a file space share. 
+	The user has write access to the path /home/bar. 
+	The share is accessed via the share name "foo":
    +
+[foo]
 	path = /home/bar
-	read only = no
    The following sample section defines a printable share. 
+	read only = no
+
+

    The following sample section defines a printable share. The share is readonly, but printable. That is, the only write access permitted is via calls to open, write to and close a - spool file. The guest ok parameter means + spool file. The guest ok parameter means access will be permitted as the default guest user (specified - elsewhere):

        [aprinter]
+	elsewhere):
    +
+[aprinter]
 	path = /usr/spool/public
 	read only = yes
 	printable = yes
-	guest ok = yes

    SPECIAL SECTIONS

    The [global] section

    parameters in this section apply to the server + guest ok = yes + +

    SPECIAL SECTIONS

    The [global] section

    parameters in this section apply to the server as a whole, or are defaults for sections which do not specifically define certain items. See the notes - under PARAMETERS for more information.

    The [homes] section

    If a section called homes is included in the + under PARAMETERS for more information.

    The [homes] section

    If a section called homes is included in the configuration file, services connecting clients to their - home directories can be created on the fly by the server.

    When the connection request is made, the existing + home directories can be created on the fly by the server.

    When the connection request is made, the existing sections are scanned. If a match is found, it is used. If no match is found, the requested section name is treated as a user name and looked up in the local password file. If the name exists and the correct password has been given, a share is - created by cloning the [homes] section.

    Some modifications are then made to the newly - created share:

    • The share name is changed from homes to - the located username.

    • If no path was given, the path is set to - the user's home directory.

    If you decide to use a path = line + created by cloning the [homes] section.

    Some modifications are then made to the newly + created share:

    • The share name is changed from homes to + the located username.

    • If no path was given, the path is set to + the user's home directory.

    If you decide to use a path = line in your [homes] section then you may find it useful - to use the %S macro. For example :

    path = /data/pchome/%S

    would be useful if you have different home directories - for your PCs than for UNIX access.

    This is a fast and simple way to give a large number + to use the %S macro. For example :

    path = /data/pchome/%S

    would be useful if you have different home directories + for your PCs than for UNIX access.

    This is a fast and simple way to give a large number of clients access to their home directories with a minimum - of fuss.

    A similar process occurs if the requested section - name is "homes", except that the share name is not + of fuss.

    A similar process occurs if the requested section + name is "homes", except that the share name is not changed to that of the requesting user. This method of using the [homes] section works well if different users share - a client PC.

    The [homes] section can specify all the parameters + a client PC.

    The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others. The following is a typical and suitable [homes] - section:

        [homes]
-	read only = no

    An important point is that if guest access is specified + section:

    +
+[homes]
+	read only = no
+
+

    An important point is that if guest access is specified in the [homes] section, all home directories will be - visible to all clients without a password. + visible to all clients without a password. In the very unlikely event that this is actually desirable, it - would be wise to also specify read only - access.

    Note that the browseable flag for + would be wise to also specify read only + access.

    Note that the browseable flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag. This is useful as - it means setting browseable = no in + it means setting browseable = no in the [homes] section will hide the [homes] share but make - any auto home directories visible.

    The [printers] section

    This section works like [homes], - but for printers.

    If a [printers] section occurs in the + any auto home directories visible.

    The [printers] section

    This section works like [homes], + but for printers.

    If a [printers] section occurs in the configuration file, users are able to connect to any printer - specified in the local host's printcap file.

    When a connection request is made, the existing sections + specified in the local host's printcap file.

    When a connection request is made, the existing sections are scanned. If a match is found, it is used. If no match is found, but a [homes] section exists, it is used as described above. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name. If a match is found, a new printer share is created by cloning - the [printers] section.

    A few modifications are then made to the newly created - share:

    • The share name is set to the located printer - name

    • If no printer name was given, the printer name - is set to the located printer name

    • If the share does not permit guest access and + the [printers] section.

      A few modifications are then made to the newly created + share:

      • The share name is set to the located printer + name

      • If no printer name was given, the printer name + is set to the located printer name

      • If the share does not permit guest access and no username was given, the username is set to the located - printer name.

      Note that the [printers] service MUST be + printer name.

    Note that the [printers] service MUST be printable - if you specify otherwise, the server will refuse - to load the configuration file.

    Typically the path specified would be that of a + to load the configuration file.

    Typically the path specified would be that of a world-writeable spool directory with the sticky bit set on it. A typical [printers] entry would look like - this:

        [printers]
+		this:
    
+[printers]
 	path = /usr/spool/public
 	guest ok = yes
-	printable = yes 
    All aliases given for a printer in the printcap file 
+	printable = yes 
+

    All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file consisting of one or - more lines like this:

        alias|alias|alias|alias...

    Each alias should be an acceptable printer name for + more lines like this:

    +
+alias|alias|alias|alias...    
+
+

    Each alias should be an acceptable printer name for your printing subsystem. In the [global] section, specify the new file as your printcap. The server will then only recognize names found in your pseudo-printcap, which of course can contain whatever aliases you like. The same technique could be used - simply to limit access to a subset of your local printers.

    An alias, by the way, is defined as any component of the + simply to limit access to a subset of your local printers.

    An alias, by the way, is defined as any component of the first entry of a printcap record. Records are separated by newlines, components (if there are more than one) are separated by vertical - bar symbols ('|').

    On SYSV systems which use lpstat to determine what + bar symbols ('|').

    Note

    On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use - "printcap name = lpstat" to automatically obtain a list - of printers. See the "printcap name" option - for more details.

    PARAMETERS

    parameters define the specific attributes of sections.

    Some parameters are specific to the [global] section - (e.g., security). Some parameters are usable - in all sections (e.g., create mode). All others + "printcap name = lpstat" to automatically obtain a list + of printers. See the "printcap name" option + for more details.

    PARAMETERS

    parameters define the specific attributes of sections.

    Some parameters are specific to the [global] section + (e.g., security). Some parameters are usable + in all sections (e.g., create mode). All others are permissible only in normal sections. For the purposes of the following descriptions the [homes] and [printers] - sections will be considered normal. The letter G + sections will be considered normal. The letter G in parentheses indicates that a parameter is specific to the - [global] section. The letter S + [global] section. The letter S indicates that a parameter can be specified in a service specific - section. Note that all S parameters can also be specified in + section. Note that all S parameters can also be specified in the [global] section - in which case they will define - the default behavior for all services.

    parameters are arranged here in alphabetical order - this may + the default behavior for all services.

    parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer - to the preferred synonym.

    VARIABLE SUBSTITUTIONS

    Many of the strings that are settable in the config file - can take substitutions. For example the option "path = - /tmp/%u" would be interpreted as "path = - /tmp/john" if the user connected with the username john.

    These substitutions are mostly noted in the descriptions below, + to the preferred synonym.

    VARIABLE SUBSTITUTIONS

    Many of the strings that are settable in the config file + can take substitutions. For example the option "path = + /tmp/%u" would be interpreted as "path = + /tmp/john" if the user connected with the username john.

    These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they - might be relevant. These are:

    %U

    session user name (the user name that the client - wanted, not necessarily the same as the one they got).

    %G

    primary group name of %U.

    %h

    the Internet hostname that Samba is running - on.

    %m

    the NetBIOS name of the client machine - (very useful).

    %L

    the NetBIOS name of the server. This allows you + might be relevant. These are:

    %U

    session user name (the user name that the client + wanted, not necessarily the same as the one they got).

    %G

    primary group name of %U.

    %h

    the Internet hostname that Samba is running + on.

    %m

    the NetBIOS name of the client machine + (very useful).

    %L

    the NetBIOS name of the server. This allows you to change your config based on what the client calls you. Your - server can have a "dual personality".

    Note that this parameter is not available when Samba listens - on port 445, as clients no longer send this information

    %M

    the Internet name of the client machine. -

    %R

    the selected protocol level after + server can have a "dual personality".

    Note that this parameter is not available when Samba listens + on port 445, as clients no longer send this information

    %M

    the Internet name of the client machine. +

    %R

    the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, - LANMAN1, LANMAN2 or NT1.

    %d

    The process id of the current server - process.

    %a

    the architecture of the remote + LANMAN1, LANMAN2 or NT1.

    %d

    The process id of the current server + process.

    %a

    the architecture of the remote machine. Only some are recognized, and those may not be 100% reliable. It currently recognizes Samba, WfWg, Win95, WinNT and Win2k. Anything else will be known as - "UNKNOWN". If it gets it wrong then sending a level - 3 log to samba@samba.org - should allow it to be fixed.

    %I

    The IP address of the client machine.

    %T

    the current date and time.

    %D

    Name of the domain or workgroup of the current user.

    %$(envvar)

    The value of the environment variable - envar.

    The following substitutes apply only to some configuration options(only those - that are used when a connection has been established):

    %S

    the name of the current service, if any.

    %P

    the root directory of the current service, - if any.

    %u

    user name of the current service, if any.

    %g

    primary group name of %u.

    %H

    the home directory of the user given - by %u.

    %N

    the name of your NIS home directory server. + "UNKNOWN". If it gets it wrong then sending a level + 3 log to samba@samba.org + should allow it to be fixed.

    %I

    The IP address of the client machine.

    %T

    the current date and time.

    %D

    Name of the domain or workgroup of the current user.

    %$(envvar)

    The value of the environment variable + envar.

    The following substitutes apply only to some configuration options(only those + that are used when a connection has been established):

    %S

    the name of the current service, if any.

    %P

    the root directory of the current service, + if any.

    %u

    user name of the current service, if any.

    %g

    primary group name of %u.

    %H

    the home directory of the user given + by %u.

    %N

    the name of your NIS home directory server. This is obtained from your NIS auto.map entry. If you have - not compiled Samba with the --with-automount - option then this value will be the same as %L.

    %p

    the path of the service's home directory, + not compiled Samba with the --with-automount + option then this value will be the same as %L.

    %p

    the path of the service's home directory, obtained from your NIS auto.map entry. The NIS auto.map entry - is split up as "%N:%p".

    There are some quite creative things that can be done - with these substitutions and other smb.conf options.

    NAME MANGLING

    Samba supports "name mangling" so that DOS and + is split up as "%N:%p".

    There are some quite creative things that can be done + with these substitutions and other smb.conf options.

    NAME MANGLING

    Samba supports "name mangling" so that DOS and Windows clients can use files that don't conform to the 8.3 format. - It can also be set to adjust the case of 8.3 format filenames.

    There are several options that control the way mangling is + It can also be set to adjust the case of 8.3 format filenames.

    There are several options that control the way mangling is performed, and they are grouped here rather than listed separately. - For the defaults look at the output of the testparm program.

    All of these options can be set separately for each service - (or globally, of course).

    The options are:

    mangle case = yes/no

    controls if names that have characters that - aren't of the "default" case are mangled. For example, - if this is yes then a name like "Mail" would be mangled. - Default no.

    case sensitive = yes/no

    controls whether filenames are case sensitive. If + For the defaults look at the output of the testparm program.

    All of these options can be set separately for each service + (or globally, of course).

    The options are:

    mangle case = yes/no

    controls if names that have characters that + aren't of the "default" case are mangled. For example, + if this is yes then a name like "Mail" would be mangled. + Default no.

    case sensitive = yes/no

    controls whether filenames are case sensitive. If they aren't then Samba must do a filename search and match on passed - names. Default no.

    default case = upper/lower

    controls what the default case is for new - filenames. Default lower.

    preserve case = yes/no

    controls if new files are created with the + names. Default no.

    default case = upper/lower

    controls what the default case is for new + filenames. Default lower.

    preserve case = yes/no

    controls if new files are created with the case that the client passes, or if they are forced to be the - "default" case. Default yes. -

    short preserve case = yes/no

    controls if new files which conform to 8.3 syntax, + "default" case. Default yes. +

    short preserve case = yes/no

    controls if new files which conform to 8.3 syntax, that is all in upper case and of suitable length, are created - upper case, or if they are forced to be the "default" - case. This option can be use with "preserve case = yes" + upper case, or if they are forced to be the "default" + case. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names - are lowercased. Default yes.

    By default, Samba 3.0 has the same semantics as a Windows - NT server, in that it is case insensitive but case preserving.

    NOTE ABOUT USERNAME/PASSWORD VALIDATION

    There are a number of ways in which a user can connect + are lowercased. Default yes.

    By default, Samba 3.0 has the same semantics as a Windows + NT server, in that it is case insensitive but case preserving.

    NOTE ABOUT USERNAME/PASSWORD VALIDATION

    There are a number of ways in which a user can connect to a service. The server uses the following steps in determining if it will allow a connection to a specified service. If all the steps fail, then the connection request is rejected. However, if one of the - steps succeeds, then the following steps are not checked.

    If the service is marked "guest only = yes" and the - server is running with share-level security ("security = share") - then steps 1 to 5 are skipped.

    1. If the client has passed a username/password + steps succeeds, then the following steps are not checked.

      If the service is marked "guest only = yes" and the + server is running with share-level security ("security = share") + then steps 1 to 5 are skipped.

      1. If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that username. Note that this includes the - \\server\service%username method of passing - a username.

      2. If the client has previously registered a username + \\server\service%username method of passing + a username.

      3. If the client has previously registered a username with the system and now supplies a correct password for that - username then the connection is allowed.

      4. The client's NetBIOS name and any previously + username then the connection is allowed.

      5. The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding - user.

      6. If the client has previously validated a + user.

      7. If the client has previously validated a username/password pair with the server and the client has passed - the validation token then that username is used.

      8. If a "user = " field is given in the - smb.conf file for the service and the client + the validation token then that username is used.

      9. If a "user = " field is given in the + smb.conf file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password checking) with one of the usernames - from the "user =" field then the connection is made as - the username in the "user =" line. If one - of the username in the "user =" list begins with a + from the "user =" field then the connection is made as + the username in the "user =" line. If one + of the username in the "user =" list begins with a '@' then that name expands to a list of names in - the group of the same name.

      10. If the service is a guest service then a - connection is made as the username given in the "guest - account =" for the service, irrespective of the - supplied password.

      COMPLETE LIST OF GLOBAL PARAMETERS

      Here is a list of all global parameters. See the section of - each parameter for details. Note that some are synonyms.

      COMPLETE LIST OF SERVICE PARAMETERS

      Here is a list of all service parameters. See the section on - each parameter for details. Note that some are synonyms.

      EXPLANATION OF EACH PARAMETER

      >abort shutdown script (G)

      This parameter only exists in the HEAD cvs branch - This a full path name to a script called by smbd(8) that - should stop a shutdown procedure issued by the shutdown script.

      This command will be run as user.

      Default: None.

      Example: abort shutdown script = /sbin/shutdown -c

      >addprinter command (G)

      With the introduction of MS-RPC based printing - support for Windows NT/2000 clients in Samba 2.2, The MS Add - Printer Wizard (APW) icon is now also available in the - "Printers..." folder displayed a share listing. The APW - allows for printers to be add remotely to a Samba or Windows - NT/2000 print server.

      For a Samba host this means that the printer must be - physically added to the underlying printing system. The add - printer command defines a script to be run which - will perform the necessary operations for adding the printer - to the print system and to add the appropriate service definition - to the smb.conf file in order that it can be - shared by smbd(8).

      The addprinter command is - automatically invoked with the following parameter (in - order):

      • printer name

      • share name

      • port name

      • driver name

      • location

      • Windows 9x driver location -

      All parameters are filled in from the PRINTER_INFO_2 structure sent - by the Windows NT/2000 client with one exception. The "Windows 9x - driver location" parameter is included for backwards compatibility - only. The remaining fields in the structure are generated from answers - to the APW questions.

      Once the addprinter command has - been executed, smbd will reparse the smb.conf to determine if the share defined by the APW - exists. If the sharename is still invalid, then smbd - will return an ACCESS_DENIED error to the client.

      The "add printer command" program can output a single line of text, - which Samba will set as the port the new printer is connected to. - If this line isn't output, Samba won't reload its printer shares. -

      See also deleteprinter command, printing, - show add - printer wizard

      Default: none

      Example: addprinter command = /usr/bin/addprinter -

      >add share command (G)

      Samba 2.2.0 introduced the ability to dynamically - add and delete shares via the Windows NT 4.0 Server Manager. The - add share command is used to define an - external program or script which will add a new service definition - to smb.conf. In order to successfully - execute the add share command, smbd - requires that the administrator be connected using a root account (i.e. - uid == 0). -

      When executed, smbd will automatically invoke the - add share command with four parameters. -

      • configFile - the location - of the global smb.conf file. -

      • shareName - the name of the new + the group of the same name.

      • If the service is a guest service then a + connection is made as the username given in the "guest + account =" for the service, irrespective of the + supplied password.

    COMPLETE LIST OF GLOBAL PARAMETERS

    Here is a list of all global parameters. See the section of + each parameter for details. Note that some are synonyms.

    COMPLETE LIST OF SERVICE PARAMETERS

    Here is a list of all service parameters. See the section on + each parameter for details. Note that some are synonyms.

    EXPLANATION OF EACH PARAMETER

    abort shutdown script (G)

    This parameter only exists in the HEAD cvs branch + This a full path name to a script called by smbd(8) that + should stop a shutdown procedure issued by the + shutdown script.

    This command will be run as user.

    Default: None.

    Example: abort shutdown script = /sbin/shutdown -c

    add group script (G)

    This is the full pathname to a script that will be run + AS ROOT by smbd(8) + when a new group is requested. It will expand any %g to the group name passed. This + script is only useful for installations using the Windows NT + domain administration tools. The script is free to create a + group with an arbitrary name to circumvent unix group name + restrictions. In that case the script must print the numeric gid + of the created group on stdout.

    add machine script (G)

    This is the full pathname to a script that will be run by + smbd(8) when a machine is added + to it's domain using the administrator username and password + method.

    This option is only required when using sam back-ends tied + to the Unix uid method of RID calculation such as smbpasswd. + This option is only available in Samba 3.0.

    Default: add machine script = <empty string>

    Example: add machine script = /usr/sbin/adduser -n -g + machines -c Machine -d /dev/null -s /bin/false %u

    addprinter command (G)

    With the introduction of MS-RPC based printing + support for Windows NT/2000 clients in Samba 2.2, The MS Add + Printer Wizard (APW) icon is now also available in the + "Printers..." folder displayed a share listing. The APW + allows for printers to be add remotely to a Samba or Windows + NT/2000 print server.

    For a Samba host this means that the printer must be + physically added to the underlying printing system. The add + printer command defines a script to be run which + will perform the necessary operations for adding the printer + to the print system and to add the appropriate service definition + to the smb.conf file in order that it can be + shared by smbd(8).

    The addprinter command is + automatically invoked with the following parameter (in + order):

    • printer name

    • share name

    • port name

    • driver name

    • location

    • Windows 9x driver location

    All parameters are filled in from the PRINTER_INFO_2 structure sent + by the Windows NT/2000 client with one exception. The "Windows 9x + driver location" parameter is included for backwards compatibility + only. The remaining fields in the structure are generated from answers + to the APW questions.

    Once the addprinter command has + been executed, smbd will reparse the + smb.conf to determine if the share defined by the APW + exists. If the sharename is still invalid, then smbd + will return an ACCESS_DENIED error to the client.

    + The "add printer command" program can output a single line of text, + which Samba will set as the port the new printer is connected to. + If this line isn't output, Samba won't reload its printer shares. +

    See also + deleteprinter command, + printing, + show add + printer wizard

    Default: none

    Example: addprinter command = /usr/bin/addprinter

    add share command (G)

    Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + add share command is used to define an + external program or script which will add a new service definition + to smb.conf. In order to successfully + execute the add share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). +

    + When executed, smbd will automatically invoke the + add share command with four parameters. +

    • configFile - the location + of the global smb.conf file. +

    • shareName - the name of the new share. -

    • pathName - path to an **existing** +

    • pathName - path to an **existing** directory on disk. -

    • comment - comment string to associate +

    • comment - comment string to associate with the new share. -

    This parameter is only used for add file shares. To add printer shares, - see the addprinter - command. -

    See also change share - command, delete share - command. -

    Default: none

    Example: add share command = /usr/local/bin/addshare

    >add machine script (G)

    This is the full pathname to a script that will - be run by smbd(8) when a machine is added - to it's domain using the administrator username and password method.

    This option is only required when using sam back-ends tied to the - Unix uid method of RID calculation such as smbpasswd. This option is only - available in Samba 3.0.

    Default: add machine script = <empty string> -

    Example: add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u -

    >ads server (G)

    If this option is specified, samba does - not try to figure out what ads server to use itself, but - uses the specified ads server. Either one DNS name or IP - address can be used.

    Default: ads server =

    Example: ads server = 192.168.1.2

    >add user script (G)

    This is the full pathname to a script that will - be run AS ROOT by smbd(8) under special circumstances described below.

    Normally, a Samba server requires that UNIX users are - created for all users accessing files on this server. For sites - that use Windows NT account databases as their primary user database - creating these users and keeping the user list in sync with the - Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users - ON DEMAND when a user accesses the Samba server.

    In order to use this option, smbd(8) must NOT be set to security = share - and add user script - must be set to a full pathname for a script that will create a UNIX - user given one argument of %u, which expands into - the UNIX user name to create.

    When the Windows user attempts to access the Samba server, - at login (session setup in the SMB protocol) time, smbd(8) contacts the password server and - attempts to authenticate the given user with the given password. If the - authentication succeeds then smbd - attempts to find a UNIX user in the UNIX password database to map the - Windows user into. If this lookup fails, and add user script - is set then smbd will - call the specified script AS ROOT, expanding - any %u argument to be the user name to create.

    If this script successfully creates the user then smbd - will continue on as though the UNIX user - already existed. In this way, UNIX users are dynamically created to - match existing Windows NT accounts.

    See also security, password server, - delete user - script.

    Default: add user script = <empty string> -

    Example: add user script = /usr/local/samba/bin/add_user - %u

    >add group script (G)

    This is the full pathname to a script that will - be run AS ROOT by smbd(8) when a new group is - requested. It will expand any - %g to the group name passed. - This script is only useful for installations using the - Windows NT domain administration tools. The script is - free to create a group with an arbitrary name to - circumvent unix group name restrictions. In that case - the script must print the numeric gid of the created - group on stdout. -

    >admin users (S)

    This is a list of users who will be granted - administrative privileges on the share. This means that they - will do all file operations as the super-user (root).

    You should use this option very carefully, as any user in - this list will be able to do anything they like on the share, - irrespective of file permissions.

    Default: no admin users

    Example: admin users = jason

    >add user to group script (G)

    Full path to the script that will be called when - a user is added to a group using the Windows NT domain administration - tools. It will be run by smbd(8) AS ROOT. - Any %g will be replaced with the group name and - any %u will be replaced with the user name. -

    Default: add user to group script =

    Example: add user to group script = /usr/sbin/adduser %u %g

    >allow hosts (S)

    Synonym for hosts allow.

    >algorithmic rid base (G)

    This determines how Samba will use its - algorithmic mapping from uids/gid to the RIDs needed to construct - NT Security Identifiers.

    Setting this option to a larger value could be useful to sites - transitioning from WinNT and Win2k, as existing user and - group rids would otherwise clash with sytem users etc. -

    All UIDs and GIDs must be able to be resolved into SIDs for - the correct operation of ACLs on the server. As such the algorithmic - mapping can't be 'turned off', but pushing it 'out of the way' should - resolve the issues. Users and groups can then be assigned 'low' RIDs - in arbitary-rid supporting backends.

    Default: algorithmic rid base = 1000

    Example: algorithmic rid base = 100000

    >allow trusted domains (G)

    This option only takes effect when the security option is set to - server or domain. - If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which smbd is running - in will fail, even if that domain is trusted by the remote server - doing the authentication.

    This is useful if you only want your Samba server to - serve resources to users in the domain it is a member of. As - an example, suppose that there are two domains DOMA and DOMB. DOMB - is trusted by DOMA, which contains the Samba server. Under normal - circumstances, a user with an account in DOMB can then access the - resources of a UNIX account with the same account name on the - Samba server even if they do not have an account in DOMA. This - can make implementing a security boundary difficult.

    Default: allow trusted domains = yes

    >announce as (G)

    This specifies what type of server nmbd(8) will announce itself as, to a network neighborhood browse - list. By default this is set to Windows NT. The valid options - are : "NT Server" (which can also be written as "NT"), - "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, - Windows NT Workstation, Windows 95 and Windows for Workgroups - respectively. Do not change this parameter unless you have a - specific need to stop Samba appearing as an NT server as this - may prevent Samba servers from participating as browser servers - correctly.

    Default: announce as = NT Server

    Example: announce as = Win95

    >announce version (G)

    This specifies the major and minor version numbers - that nmbd will use when announcing itself as a server. The default - is 4.9. Do not change this parameter unless you have a specific - need to set a Samba server to be a downlevel server.

    Default: announce version = 4.9

    Example: announce version = 2.0

    >auto services (G)

    This is a synonym for the preload.

    >auth methods (G)

    This option allows the administrator to chose what - authentication methods smbd will use when authenticating - a user. This option defaults to sensible values based on security. - - Each entry in the list attempts to authenticate the user in turn, until - the user authenticates. In practice only one method will ever actually - be able to complete the authentication. -

    Default: auth methods = <empty string>

    Example: auth methods = guest sam ntdomain

    >available (S)

    This parameter lets you "turn off" a service. If - available = no, then ALL - attempts to connect to the service will fail. Such failures are - logged.

    Default: available = yes

    >bind interfaces only (G)

    This global parameter allows the Samba admin - to limit what interfaces on a machine will serve SMB requests. It - affects file service smbd(8) and name service nmbd(8) in a slightly different ways.

    For name service it causes nmbd to bind - to ports 137 and 138 on the interfaces listed in the interfaces parameter. nmbd - also binds to the "all addresses" interface (0.0.0.0) - on ports 137 and 138 for the purposes of reading broadcast messages. - If this option is not set then nmbd will service - name requests on all of these sockets. If bind interfaces - only is set then nmbd will check the - source address of any packets coming in on the broadcast sockets - and discard any that don't match the broadcast addresses of the - interfaces in the interfaces parameter list. - As unicast packets are received on the other sockets it allows - nmbd to refuse to serve names to machines that - send packets that arrive through any interfaces not listed in the - interfaces list. IP Source address spoofing - does defeat this simple check, however, so it must not be used - seriously as a security feature for nmbd.

    For file service it causes smbd(8) to bind only to the interface list - given in the interfaces parameter. This restricts the networks that - smbd will serve to packets coming in those - interfaces. Note that you should not use this parameter for machines - that are serving PPP or other intermittent or non-broadcast network - interfaces as it will not cope with non-permanent interfaces.

    If bind interfaces only is set then - unless the network address 127.0.0.1 is added - to the interfaces parameter list smbpasswd(8) and swat(8) may not work as expected due to the reasons covered below.

    To change a users SMB password, the smbpasswd - by default connects to the localhost - 127.0.0.1 - address as an SMB client to issue the password change request. If - bind interfaces only is set then unless the - network address 127.0.0.1 is added to the - interfaces parameter list then smbpasswd will fail to connect in it's default mode. - smbpasswd can be forced to use the primary IP interface - of the local host by using its smbpasswd(8) -r remote machine - parameter, with remote machine set - to the IP name of the primary interface of the local host.

    The swat status page tries to connect with - smbd and nmbd at the address - 127.0.0.1 to determine if they are running. - Not adding 127.0.0.1 will cause smbd and nmbd to always show - "not running" even if they really are. This can prevent swat from starting/stopping/restarting smbd - and nmbd.

    Default: bind interfaces only = no

    >blocking locks (S)

    This parameter controls the behavior - of smbd(8) when given a request by a client - to obtain a byte range lock on a region of an open file, and the - request has a time limit associated with it.

    If this parameter is set and the lock range requested - cannot be immediately satisfied, samba will internally - queue the lock request, and periodically attempt to obtain - the lock until the timeout period expires.

    If this parameter is set to no, then - samba will behave as previous versions of Samba would and - will fail the lock request immediately if the lock range - cannot be obtained.

    Default: blocking locks = yes

    >block size (S)

    This parameter controls the behavior of smbd(8) when reporting disk free - sizes. By default, this reports a disk block size of 1024 bytes. -

    Changing this parameter may have some effect on the - efficiency of client writes, this is not yet confirmed. This - parameter was added to allow advanced administrators to change - it (usually to a higher value) and test the effect it has on - client write performance without re-compiling the code. As this - is an experimental option it may be removed in a future release. -

    Changing this option does not change the disk free reporting - size, just the block size unit reported to the client.

    >browsable (S)

    See the browseable.

    >browse list (G)

    This controls whether smbd(8) will serve a browse list to - a client doing a NetServerEnum call. Normally - set to yes. You should never need to change - this.

    Default: browse list = yes

    >browseable (S)

    This controls whether this share is seen in - the list of available shares in a net view and in the browse list.

    Default: browseable = yes

    >case sensitive (S)

    See the discussion in the section NAME MANGLING.

    Default: case sensitive = no

    >casesignames (S)

    Synonym for case - sensitive.

    >change notify timeout (G)

    This SMB allows a client to tell a server to - "watch" a particular directory for any changes and only reply to - the SMB request when a change has occurred. Such constant scanning of - a directory is expensive under UNIX, hence an smbd(8) daemon only performs such a scan - on each requested directory once every change notify - timeout seconds.

    Default: change notify timeout = 60

    Example: change notify timeout = 300

    Would change the scan time to every 5 minutes.

    >change share command (G)

    Samba 2.2.0 introduced the ability to dynamically - add and delete shares via the Windows NT 4.0 Server Manager. The - change share command is used to define an - external program or script which will modify an existing service definition - in smb.conf. In order to successfully - execute the change share command, smbd - requires that the administrator be connected using a root account (i.e. - uid == 0). -

    When executed, smbd will automatically invoke the - change share command with four parameters. -

    • configFile - the location - of the global smb.conf file. -

    • shareName - the name of the new +

    + This parameter is only used for add file shares. To add printer shares, + see the addprinter + command. +

    + See also change share + command, delete share + command. +

    Default: none

    Example: add share command = /usr/local/bin/addshare

    add user script (G)

    This is the full pathname to a script that will + be run AS ROOT by smbd(8) under special circumstances described below.

    Normally, a Samba server requires that UNIX users are + created for all users accessing files on this server. For sites + that use Windows NT account databases as their primary user database + creating these users and keeping the user list in sync with the + Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users + ON DEMAND when a user accesses the Samba server.

    In order to use this option, smbd(8) must NOT be set to security = share + and add user script + must be set to a full pathname for a script that will create a UNIX + user given one argument of %u, which expands into + the UNIX user name to create.

    When the Windows user attempts to access the Samba server, + at login (session setup in the SMB protocol) time, smbd(8) contacts the password server and + attempts to authenticate the given user with the given password. If the + authentication succeeds then smbd + attempts to find a UNIX user in the UNIX password database to map the + Windows user into. If this lookup fails, and add user script + is set then smbd will + call the specified script AS ROOT, expanding + any %u argument to be the user name to create.

    If this script successfully creates the user then smbd + will continue on as though the UNIX user + already existed. In this way, UNIX users are dynamically created to + match existing Windows NT accounts.

    See also + security, + password server, + delete user + script.

    Default: add user script = <empty string>

    Example: add user script = /usr/local/samba/bin/add_user %u

    add user to group script (G)

    Full path to the script that will be called when + a user is added to a group using the Windows NT domain administration + tools. It will be run by smbd(8) AS ROOT. + Any %g will be replaced with the group name and + any %u will be replaced with the user name. +

    Default: add user to group script =

    Example: add user to group script = /usr/sbin/adduser %u %g

    admin users (S)

    This is a list of users who will be granted + administrative privileges on the share. This means that they + will do all file operations as the super-user (root).

    You should use this option very carefully, as any user in + this list will be able to do anything they like on the share, + irrespective of file permissions.

    Default: no admin users

    Example: admin users = jason

    ads server (G)

    If this option is specified, samba does not try to figure out what + ads server to use itself, but uses the specified ads server. Either one + DNS name or IP address can be used.

    Default: ads server =

    Example: ads server = 192.168.1.2

    algorithmic rid base (G)

    This determines how Samba will use its + algorithmic mapping from uids/gid to the RIDs needed to construct + NT Security Identifiers. +

    Setting this option to a larger value could be useful to sites + transitioning from WinNT and Win2k, as existing user and + group rids would otherwise clash with sytem users etc. +

    All UIDs and GIDs must be able to be resolved into SIDs for + the correct operation of ACLs on the server. As such the algorithmic + mapping can't be 'turned off', but pushing it 'out of the way' should + resolve the issues. Users and groups can then be assigned 'low' RIDs + in arbitary-rid supporting backends. +

    Default: algorithmic rid base = 1000

    Example: algorithmic rid base = 100000

    allow hosts (S)

    Synonym for + hosts allow.

    allow trusted domains (G)

    This option only takes effect when the + security option is set to + server or domain. + If it is set to no, then attempts to connect to a resource from + a domain or workgroup other than the one which smbd is running + in will fail, even if that domain is trusted by the remote server + doing the authentication.

    This is useful if you only want your Samba server to + serve resources to users in the domain it is a member of. As + an example, suppose that there are two domains DOMA and DOMB. DOMB + is trusted by DOMA, which contains the Samba server. Under normal + circumstances, a user with an account in DOMB can then access the + resources of a UNIX account with the same account name on the + Samba server even if they do not have an account in DOMA. This + can make implementing a security boundary difficult.

    Default: allow trusted domains = yes

    announce as (G)

    This specifies what type of server nmbd(8) will announce itself as, to a network neighborhood browse + list. By default this is set to Windows NT. The valid options + are : "NT Server" (which can also be written as "NT"), + "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, + Windows NT Workstation, Windows 95 and Windows for Workgroups + respectively. Do not change this parameter unless you have a + specific need to stop Samba appearing as an NT server as this + may prevent Samba servers from participating as browser servers + correctly.

    Default: announce as = NT Server

    Example: announce as = Win95

    announce version (G)

    This specifies the major and minor version numbers + that nmbd will use when announcing itself as a server. The default + is 4.9. Do not change this parameter unless you have a specific + need to set a Samba server to be a downlevel server.

    Default: announce version = 4.9

    Example: announce version = 2.0

    auth methods (G)

    This option allows the administrator to chose what + authentication methods smbd will use when authenticating + a user. This option defaults to sensible values based on + security.

    Each entry in the list attempts to authenticate the user in turn, until + the user authenticates. In practice only one method will ever actually + be able to complete the authentication. +

    Default: auth methods = <empty string>

    Example: auth methods = guest sam ntdomain

    auto services (G)

    This is a synonym for the + preload.

    available (S)

    This parameter lets you "turn off" a service. If + available = no, then ALL + attempts to connect to the service will fail. Such failures are + logged.

    Default: available = yes

    bind interfaces only (G)

    This global parameter allows the Samba admin + to limit what interfaces on a machine will serve SMB requests. It + affects file service smbd(8) and name service nmbd(8) in a slightly different ways.

    For name service it causes nmbd to bind + to ports 137 and 138 on the interfaces listed in + the interfaces parameter. nmbd also + binds to the "all addresses" interface (0.0.0.0) + on ports 137 and 138 for the purposes of reading broadcast messages. + If this option is not set then nmbd will service + name requests on all of these sockets. If bind interfaces + only is set then nmbd will check the + source address of any packets coming in on the broadcast sockets + and discard any that don't match the broadcast addresses of the + interfaces in the interfaces parameter list. + As unicast packets are received on the other sockets it allows + nmbd to refuse to serve names to machines that + send packets that arrive through any interfaces not listed in the + interfaces list. IP Source address spoofing + does defeat this simple check, however, so it must not be used + seriously as a security feature for nmbd.

    For file service it causes smbd(8) to bind only to the interface list + given in the interfaces parameter. This + restricts the networks that smbd will serve + to packets coming in those interfaces. Note that you should not use this parameter + for machines that are serving PPP or other intermittent or non-broadcast network + interfaces as it will not cope with non-permanent interfaces.

    If bind interfaces only is set then + unless the network address 127.0.0.1 is added + to the interfaces parameter + list smbpasswd(8) and swat(8) may not work as expected due + to the reasons covered below.

    To change a users SMB password, the smbpasswd + by default connects to the localhost - 127.0.0.1 + address as an SMB client to issue the password change request. If + bind interfaces only is set then unless the + network address 127.0.0.1 is added to the + interfaces parameter list then + smbpasswd will fail to connect in it's default mode. + smbpasswd can be forced to use the primary IP interface + of the local host by using its smbpasswd(8) -r remote machine + parameter, with remote machine set + to the IP name of the primary interface of the local host.

    The swat status page tries to connect with + smbd and nmbd at the address + 127.0.0.1 to determine if they are running. + Not adding 127.0.0.1 will cause + smbd and nmbd to always show + "not running" even if they really are. This can prevent + swat from starting/stopping/restarting smbd + and nmbd.

    Default: bind interfaces only = no

    blocking locks (S)

    This parameter controls the behavior + of smbd(8) when given a request by a client + to obtain a byte range lock on a region of an open file, and the + request has a time limit associated with it.

    If this parameter is set and the lock range requested + cannot be immediately satisfied, samba will internally + queue the lock request, and periodically attempt to obtain + the lock until the timeout period expires.

    If this parameter is set to no, then + samba will behave as previous versions of Samba would and + will fail the lock request immediately if the lock range + cannot be obtained.

    Default: blocking locks = yes

    block size (S)

    This parameter controls the behavior of smbd(8) when reporting disk free + sizes. By default, this reports a disk block size of 1024 bytes. +

    Changing this parameter may have some effect on the + efficiency of client writes, this is not yet confirmed. This + parameter was added to allow advanced administrators to change + it (usually to a higher value) and test the effect it has on + client write performance without re-compiling the code. As this + is an experimental option it may be removed in a future release. +

    Changing this option does not change the disk free reporting + size, just the block size unit reported to the client. +

    browsable (S)

    See the + browseable.

    browseable (S)

    This controls whether this share is seen in + the list of available shares in a net view and in the browse list.

    Default: browseable = yes

    browse list (G)

    This controls whether smbd(8) will serve a browse list to + a client doing a NetServerEnum call. Normally + set to yes. You should never need to change + this.

    Default: browse list = yes

    case sensitive (S)

    See the discussion in the section NAME MANGLING.

    Default: case sensitive = no

    casesignames (S)

    Synonym for case sensitive.

    change notify timeout (G)

    This SMB allows a client to tell a server to + "watch" a particular directory for any changes and only reply to + the SMB request when a change has occurred. Such constant scanning of + a directory is expensive under UNIX, hence an smbd(8) daemon only performs such a scan + on each requested directory once every change notify + timeout seconds.

    Default: change notify timeout = 60

    Example: change notify timeout = 300

    Would change the scan time to every 5 minutes.

    change share command (G)

    Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + change share command is used to define an + external program or script which will modify an existing service definition + in smb.conf. In order to successfully + execute the change share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). +

    + When executed, smbd will automatically invoke the + change share command with four parameters. +

    • configFile - the location + of the global smb.conf file. +

    • shareName - the name of the new share. -

    • pathName - path to an **existing** +

    • pathName - path to an **existing** directory on disk. -

    • comment - comment string to associate +

    • comment - comment string to associate with the new share. -

    This parameter is only used modify existing file shares definitions. To modify - printer shares, use the "Printers..." folder as seen when browsing the Samba host. -

    See also add share - command, delete - share command. -

    Default: none

    Example: change share command = /usr/local/bin/addshare

    >comment (S)

    This is a text field that is seen next to a share - when a client does a queries the server, either via the network - neighborhood or via net view to list what shares - are available.

    If you want to set the string that is displayed next to the - machine name then see the server string parameter.

    Default: No comment string

    Example: comment = Fred's Files

    >config file (G)

    This allows you to override the config file - to use, instead of the default (usually smb.conf). - There is a chicken and egg problem here as this option is set - in the config file!

    For this reason, if the name of the config file has changed - when the parameters are loaded then it will reload them from - the new config file.

    This option takes the usual substitutions, which can - be very useful.

    If the config file doesn't exist then it won't be loaded - (allowing you to special case the config files of just a few - clients).

    Example: config file = /usr/local/samba/lib/smb.conf.%m -

    >copy (S)

    This parameter allows you to "clone" service - entries. The specified service is simply duplicated under the - current service's name. Any parameters specified in the current - section will override those in the section being copied.

    This feature lets you set up a 'template' service and - create similar services easily. Note that the service being - copied must occur earlier in the configuration file than the - service doing the copying.

    Default: no value

    Example: copy = otherservice

    >create mask (S)

    A synonym for this parameter is - create mode - .

    When a file is created, the necessary permissions are - calculated according to the mapping from DOS modes to UNIX - permissions, and the resulting UNIX mode is then bit-wise 'AND'ed - with this parameter. This parameter may be thought of as a bit-wise - MASK for the UNIX modes of a file. Any bit not - set here will be removed from the modes set on a file when it is - created.

    The default value of this parameter removes the - 'group' and 'other' write and execute bits from the UNIX modes.

    Following this Samba will bit-wise 'OR' the UNIX mode created - from this parameter with the value of the force create mode - parameter which is set to 000 by default.

    This parameter does not affect directory modes. See the - parameter directory mode - for details.

    See also the force - create mode parameter for forcing particular mode - bits to be set on created files. See also the directory mode parameter for masking - mode bits on created directories. See also the inherit permissions parameter.

    Note that this parameter does not apply to permissions - set by Windows NT/2000 ACL editors. If the administrator wishes to enforce - a mask on access control lists also, they need to set the security mask.

    Default: create mask = 0744

    Example: create mask = 0775

    >create mode (S)

    This is a synonym for create mask.

    >csc policy (S)

    This stands for client-side caching - policy, and specifies how clients capable of offline - caching will cache the files in the share. The valid values - are: manual, documents, programs, disable.

    These values correspond to those used on Windows - servers.

    For example, shares containing roaming profiles can have - offline caching disabled using csc policy = disable - .

    Default: csc policy = manual

    Example: csc policy = programs

    >deadtime (G)

    The value of the parameter (a decimal integer) - represents the number of minutes of inactivity before a connection - is considered dead, and it is disconnected. The deadtime only takes - effect if the number of open files is zero.

    This is useful to stop a server's resources being - exhausted by a large number of inactive connections.

    Most clients have an auto-reconnect feature when a - connection is broken so in most cases this parameter should be - transparent to users.

    Using this parameter with a timeout of a few minutes - is recommended for most systems.

    A deadtime of zero indicates that no auto-disconnection - should be performed.

    Default: deadtime = 0

    Example: deadtime = 15

    >debug hires timestamp (G)

    Sometimes the timestamps in the log messages - are needed with a resolution of higher that seconds, this - boolean parameter adds microsecond resolution to the timestamp - message header when turned on.

    Note that the parameter debug timestamp must be on for this to have an - effect.

    Default: debug hires timestamp = no

    >debug pid (G)

    When using only one log file for more then one - forked smbd-process there may be hard to follow which process - outputs which message. This boolean parameter is adds the process-id - to the timestamp message headers in the logfile when turned on.

    Note that the parameter debug timestamp must be on for this to have an - effect.

    Default: debug pid = no

    >debug timestamp (G)

    Samba debug log messages are timestamped - by default. If you are running at a high debug level these timestamps - can be distracting. This boolean parameter allows timestamping - to be turned off.

    Default: debug timestamp = yes

    >debug uid (G)

    Samba is sometimes run as root and sometime - run as the connected user, this boolean parameter inserts the - current euid, egid, uid and gid to the timestamp message headers - in the log file if turned on.

    Note that the parameter debug timestamp must be on for this to have an - effect.

    Default: debug uid = no

    >debuglevel (G)

    Synonym for log level.

    >default (G)

    A synonym for default service.

    >default case (S)

    See the section on NAME MANGLING. Also note the short preserve case parameter.

    Default: default case = lower

    >default devmode (S)

    This parameter is only applicable to printable services. When smbd is serving - Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba - server has a Device Mode which defines things such as paper size and - orientation and duplex settings. The device mode can only correctly be - generated by the printer driver itself (which can only be executed on a - Win32 platform). Because smbd is unable to execute the driver code - to generate the device mode, the default behavior is to set this field - to NULL. -

    Most problems with serving printer drivers to Windows NT/2k/XP clients - can be traced to a problem with the generated device mode. Certain drivers - will do things such as crashing the client's Explorer.exe with a NULL devmode. - However, other printer drivers can cause the client's spooler service - (spoolsv.exe) to die if the devmode was not created by the driver itself - (i.e. smbd generates a default devmode). -

    This parameter should be used with care and tested with the printer - driver in question. It is better to leave the device mode to NULL - and let the Windows client set the correct values. Because drivers do not - do this all the time, setting default devmode = yes - will instruct smbd to generate a default one. -

    For more information on Windows NT/2k printing and Device Modes, - see the MSDN documentation. -

    Default: default devmode = no

    >default service (G)

    This parameter specifies the name of a service - which will be connected to if the service actually requested cannot - be found. Note that the square brackets are NOT - given in the parameter value (see example below).

    There is no default value for this parameter. If this - parameter is not given, attempting to connect to a nonexistent - service results in an error.

    Typically the default service would be a guest ok, read-only service.

    Also note that the apparent service name will be changed - to equal that of the requested service, this is very useful as it - allows you to use macros like %S to make - a wildcard service.

    Note also that any "_" characters in the name of the service - used in the default service will get mapped to a "/". This allows for - interesting things.

    Example:

    [global]
+

    + This parameter is only used modify existing file shares definitions. To modify + printer shares, use the "Printers..." folder as seen when browsing the Samba host. +

    + See also add share + command, delete + share command. +

    Default: none

    Example: change share command = /usr/local/bin/addshare

    comment (S)

    This is a text field that is seen next to a share + when a client does a queries the server, either via the network + neighborhood or via net view to list what shares + are available.

    If you want to set the string that is displayed next to the + machine name then see the + server string parameter.

    Default: No comment string

    Example: comment = Fred's Files

    config file (G)

    This allows you to override the config file + to use, instead of the default (usually smb.conf). + There is a chicken and egg problem here as this option is set + in the config file!

    For this reason, if the name of the config file has changed + when the parameters are loaded then it will reload them from + the new config file.

    This option takes the usual substitutions, which can + be very useful.

    If the config file doesn't exist then it won't be loaded + (allowing you to special case the config files of just a few + clients).

    Example: config file = /usr/local/samba/lib/smb.conf.%m

    copy (S)

    This parameter allows you to "clone" service + entries. The specified service is simply duplicated under the + current service's name. Any parameters specified in the current + section will override those in the section being copied.

    This feature lets you set up a 'template' service and + create similar services easily. Note that the service being + copied must occur earlier in the configuration file than the + service doing the copying.

    Default: no value

    Example: copy = otherservice

    create mask (S)

    A synonym for this parameter is + create mode + .

    When a file is created, the necessary permissions are + calculated according to the mapping from DOS modes to UNIX + permissions, and the resulting UNIX mode is then bit-wise 'AND'ed + with this parameter. This parameter may be thought of as a bit-wise + MASK for the UNIX modes of a file. Any bit not + set here will be removed from the modes set on a file when it is + created.

    The default value of this parameter removes the + 'group' and 'other' write and execute bits from the UNIX modes.

    Following this Samba will bit-wise 'OR' the UNIX mode created + from this parameter with the value of the + force create mode + parameter which is set to 000 by default.

    This parameter does not affect directory modes. See the + parameter directory mode + for details.

    See also the force + create mode parameter for forcing particular mode + bits to be set on created files. See also the + directory mode parameter for masking + mode bits on created directories. See also the + inherit permissions parameter.

    Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the + security mask.

    Default: create mask = 0744

    Example: create mask = 0775

    create mode (S)

    This is a synonym for + create mask.

    csc policy (S)

    This stands for client-side caching + policy, and specifies how clients capable of offline + caching will cache the files in the share. The valid values + are: manual, documents, programs, disable.

    These values correspond to those used on Windows servers.

    For example, shares containing roaming profiles can have + offline caching disabled using csc policy = disable.

    Default: csc policy = manual

    Example: csc policy = programs

    dead time (G)

    The value of the parameter (a decimal integer) + represents the number of minutes of inactivity before a connection + is considered dead, and it is disconnected. The deadtime only takes + effect if the number of open files is zero.

    This is useful to stop a server's resources being + exhausted by a large number of inactive connections.

    Most clients have an auto-reconnect feature when a + connection is broken so in most cases this parameter should be + transparent to users.

    Using this parameter with a timeout of a few minutes + is recommended for most systems.

    A deadtime of zero indicates that no auto-disconnection + should be performed.

    Default: deadtime = 0

    Example: deadtime = 15

    debug hires timestamp (G)

    Sometimes the timestamps in the log messages + are needed with a resolution of higher that seconds, this + boolean parameter adds microsecond resolution to the timestamp + message header when turned on.

    Note that the parameter + debug timestamp must be on for this to have an + effect.

    Default: debug hires timestamp = no

    debug level (G)

    Synonym for + log level.

    debug pid (G)

    When using only one log file for more then one forked + smbd(8)-process there may be hard to + follow which process outputs which message. This boolean parameter + is adds the process-id to the timestamp message headers in the + logfile when turned on.

    Note that the parameter + debug timestamp must be on for this to have an + effect.

    Default: debug pid = no

    debug timestamp (G)

    Samba debug log messages are timestamped + by default. If you are running at a high + debug level these timestamps + can be distracting. This boolean parameter allows timestamping + to be turned off.

    Default: debug timestamp = yes

    debug uid (G)

    Samba is sometimes run as root and sometime + run as the connected user, this boolean parameter inserts the + current euid, egid, uid and gid to the timestamp message headers + in the log file if turned on.

    Note that the parameter + debug timestamp must be on for this to have an + effect.

    Default: debug uid = no

    default case (S)

    See the section on + NAME MANGLING. Also note the + short preserve case parameter.

    Default: default case = lower

    default devmode (S)

    This parameter is only applicable to printable services. + When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba + server has a Device Mode which defines things such as paper size and + orientation and duplex settings. The device mode can only correctly be + generated by the printer driver itself (which can only be executed on a + Win32 platform). Because smbd is unable to execute the driver code + to generate the device mode, the default behavior is to set this field + to NULL. +

    Most problems with serving printer drivers to Windows NT/2k/XP clients + can be traced to a problem with the generated device mode. Certain drivers + will do things such as crashing the client's Explorer.exe with a NULL devmode. + However, other printer drivers can cause the client's spooler service + (spoolsv.exe) to die if the devmode was not created by the driver itself + (i.e. smbd generates a default devmode). +

    This parameter should be used with care and tested with the printer + driver in question. It is better to leave the device mode to NULL + and let the Windows client set the correct values. Because drivers do not + do this all the time, setting default devmode = yes + will instruct smbd to generate a default one. +

    For more information on Windows NT/2k printing and Device Modes, + see the MSDN documentation. +

    Default: default devmode = no

    default service (G)

    This parameter specifies the name of a service + which will be connected to if the service actually requested cannot + be found. Note that the square brackets are NOT + given in the parameter value (see example below).

    There is no default value for this parameter. If this + parameter is not given, attempting to connect to a nonexistent + service results in an error.

    Typically the default service would be a + guest ok, + read-only service.

    Also note that the apparent service name will be changed + to equal that of the requested service, this is very useful as it + allows you to use macros like %S to make + a wildcard service.

    Note also that any "_" characters in the name of the service + used in the default service will get mapped to a "/". This allows for + interesting things.

    Example:

    +[global]
 	default service = pub
         
 [pub]
-	path = /%S

    >delete group script (G)

    This is the full pathname to a script that will - be run AS ROOT smbd(8) when a group is requested to be deleted. - It will expand any %g to the group name passed. - This script is only useful for installations using the Windows NT domain administration tools. -

    >deleteprinter command (G)

    With the introduction of MS-RPC based printer - support for Windows NT/2000 clients in Samba 2.2, it is now - possible to delete printer at run time by issuing the - DeletePrinter() RPC call.

    For a Samba host this means that the printer must be - physically deleted from underlying printing system. The deleteprinter command defines a script to be run which - will perform the necessary operations for removing the printer - from the print system and from smb.conf. -

    The deleteprinter command is - automatically called with only one parameter: "printer name".

    Once the deleteprinter command has - been executed, smbd will reparse the smb.conf to associated printer no longer exists. - If the sharename is still valid, then smbd - will return an ACCESS_DENIED error to the client.

    See also addprinter command, printing, - show add - printer wizard

    Default: none

    Example: deleteprinter command = /usr/bin/removeprinter -

    >delete readonly (S)

    This parameter allows readonly files to be deleted. - This is not normal DOS semantics, but is allowed by UNIX.

    This option may be useful for running applications such - as rcs, where UNIX file ownership prevents changing file - permissions, and DOS semantics prevent deletion of a read only file.

    Default: delete readonly = no

    >delete share command (G)

    Samba 2.2.0 introduced the ability to dynamically - add and delete shares via the Windows NT 4.0 Server Manager. The - delete share command is used to define an - external program or script which will remove an existing service - definition from smb.conf. In order to successfully - execute the delete share command, smbd - requires that the administrator be connected using a root account (i.e. - uid == 0). -

    When executed, smbd will automatically invoke the - delete share command with two parameters. -

    • configFile - the location - of the global smb.conf file. -

    • shareName - the name of + path = /%S +

    default (G)

    A synonym for + default service.

    delete group script (G)

    This is the full pathname to a script that will + be run AS ROOT smbd(8) when a group is requested to be deleted. + It will expand any %g to the group name passed. + This script is only useful for installations using the Windows NT domain administration tools. +

    deleteprinter command (G)

    With the introduction of MS-RPC based printer + support for Windows NT/2000 clients in Samba 2.2, it is now + possible to delete printer at run time by issuing the + DeletePrinter() RPC call.

    For a Samba host this means that the printer must be + physically deleted from underlying printing system. The + deleteprinter command defines a script to be run which + will perform the necessary operations for removing the printer + from the print system and from smb.conf. +

    The deleteprinter command is + automatically called with only one parameter: + "printer name".

    Once the deleteprinter command has + been executed, smbd will reparse the + smb.conf to associated printer no longer exists. + If the sharename is still valid, then smbd + will return an ACCESS_DENIED error to the client.

    See also + addprinter command, + printing, + show add + printer wizard

    Default: none

    Example: deleteprinter command = /usr/bin/removeprinter

    delete readonly (S)

    This parameter allows readonly files to be deleted. + This is not normal DOS semantics, but is allowed by UNIX.

    This option may be useful for running applications such + as rcs, where UNIX file ownership prevents changing file + permissions, and DOS semantics prevent deletion of a read only file.

    Default: delete readonly = no

    delete share command (G)

    Samba 2.2.0 introduced the ability to dynamically + add and delete shares via the Windows NT 4.0 Server Manager. The + delete share command is used to define an + external program or script which will remove an existing service + definition from smb.conf. In order to successfully + execute the delete share command, smbd + requires that the administrator be connected using a root account (i.e. + uid == 0). +

    + When executed, smbd will automatically invoke the + delete share command with two parameters. +

    • configFile - the location + of the global smb.conf file. +

    • shareName - the name of the existing service. -

    This parameter is only used to remove file shares. To delete printer shares, - see the deleteprinter - command. -

    See also add share - command, change - share command. -

    Default: none

    Example: delete share command = /usr/local/bin/delshare

    >delete user script (G)

    This is the full pathname to a script that will - be run by smbd(8) when managing users - with remote RPC (NT) tools. -

    This script is called when a remote client removes a user - from the server, normally using 'User Manager for Domains' or - rpcclient. -

    This script should delete the given UNIX username. -

    Default: delete user script = <empty string> -

    Example: delete user script = /usr/local/samba/bin/del_user - %u

    >delete user from group script (G)

    Full path to the script that will be called when - a user is removed from a group using the Windows NT domain administration - tools. It will be run by smbd(8) AS ROOT. - Any %g will be replaced with the group name and - any %u will be replaced with the user name. -

    Default: delete user from group script =

    Example: delete user from group script = /usr/sbin/deluser %u %g

    >delete veto files (S)

    This option is used when Samba is attempting to - delete a directory that contains one or more vetoed directories - (see the veto files - option). If this option is set to no (the default) then if a vetoed - directory contains any non-vetoed files or directories then the - directory delete will fail. This is usually what you want.

    If this option is set to yes, then Samba - will attempt to recursively delete any files and directories within - the vetoed directory. This can be useful for integration with file - serving systems such as NetAtalk which create meta-files within - directories you might normally veto DOS/Windows users from seeing - (e.g. .AppleDouble)

    Setting delete veto files = yes allows these - directories to be transparently deleted when the parent directory - is deleted (so long as the user has permissions to do so).

    See also the veto - files parameter.

    Default: delete veto files = no

    >deny hosts (S)

    Synonym for hosts - deny.

    >dfree command (G)

    The dfree command setting should - only be used on systems where a problem occurs with the internal - disk space calculations. This has been known to happen with Ultrix, - but may occur with other operating systems. The symptom that was - seen was an error of "Abort Retry Ignore" at the end of each - directory listing.

    This setting allows the replacement of the internal routines to - calculate the total disk space and amount available with an external - routine. The example below gives a possible script that might fulfill - this function.

    The external program will be passed a single parameter indicating - a directory in the filesystem being queried. This will typically consist - of the string ./. The script should return two - integers in ASCII. The first should be the total disk space in blocks, - and the second should be the number of available blocks. An optional - third return value can give the block size in bytes. The default - blocksize is 1024 bytes.

    Note: Your script should NOT be setuid or - setgid and should be owned by (and writeable only by) root!

    Default: By default internal routines for - determining the disk capacity and remaining space will be used. -

    Example: dfree command = /usr/local/samba/bin/dfree -

    Where the script dfree (which must be made executable) could be:

     
+			
    
+	This parameter is only used to remove file shares.  To delete printer shares, 
+	see the deleteprinter 
+	command.
+	
    
+	See also add share
+	command, change 
+	share command.
+	
    Default: none
    Example: delete share command = /usr/local/bin/delshare
    delete user from group script (G)

    Full path to the script that will be called when + a user is removed from a group using the Windows NT domain administration + tools. It will be run by smbd(8) AS ROOT. + Any %g will be replaced with the group name and + any %u will be replaced with the user name. +

    Default: delete user from group script =

    Example: delete user from group script = /usr/sbin/deluser %u %g

    delete user script (G)

    This is the full pathname to a script that will + be run by smbd(8) when managing users + with remote RPC (NT) tools. +

    This script is called when a remote client removes a user + from the server, normally using 'User Manager for Domains' or + rpcclient.

    This script should delete the given UNIX username.

    Default: delete user script = <empty string>

    Example: delete user script = /usr/local/samba/bin/del_user %u

    delete veto files (S)

    This option is used when Samba is attempting to + delete a directory that contains one or more vetoed directories + (see the veto files + option). If this option is set to no (the default) then if a vetoed + directory contains any non-vetoed files or directories then the + directory delete will fail. This is usually what you want.

    If this option is set to yes, then Samba + will attempt to recursively delete any files and directories within + the vetoed directory. This can be useful for integration with file + serving systems such as NetAtalk which create meta-files within + directories you might normally veto DOS/Windows users from seeing + (e.g. .AppleDouble)

    Setting delete veto files = yes allows these + directories to be transparently deleted when the parent directory + is deleted (so long as the user has permissions to do so).

    See also the veto + files parameter.

    Default: delete veto files = no

    deny hosts (S)

    Synonym for hosts + deny.

    dfree command (G)

    The dfree command setting + should only be used on systems where a problem occurs with the + internal disk space calculations. This has been known to happen + with Ultrix, but may occur with other operating systems. The + symptom that was seen was an error of "Abort Retry + Ignore" at the end of each directory listing.

    This setting allows the replacement of the internal routines to + calculate the total disk space and amount available with an external + routine. The example below gives a possible script that might fulfill + this function.

    The external program will be passed a single parameter indicating + a directory in the filesystem being queried. This will typically consist + of the string ./. The script should return two + integers in ASCII. The first should be the total disk space in blocks, + and the second should be the number of available blocks. An optional + third return value can give the block size in bytes. The default + blocksize is 1024 bytes.

    Note: Your script should NOT be setuid or + setgid and should be owned by (and writeable only by) root!

    Default: By default internal routines for + determining the disk capacity and remaining space will be used. +

    Example: dfree command = /usr/local/samba/bin/dfree

    Where the script dfree (which must be made executable) could be:

     
 #!/bin/sh
-df $1 | tail -1 | awk '{print $2" "$4}'

    or perhaps (on Sys V based systems):

     
+df $1 | tail -1 | awk '{print $2" "$4}'
+

    or perhaps (on Sys V based systems):

     
 #!/bin/sh
-/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'

    Note that you may have to replace the command names - with full path names on some systems.

    >directory (S)

    Synonym for path - .

    >directory mask (S)

    This parameter is the octal modes which are - used when converting DOS modes to UNIX modes when creating UNIX - directories.

    When a directory is created, the necessary permissions are - calculated according to the mapping from DOS modes to UNIX permissions, - and the resulting UNIX mode is then bit-wise 'AND'ed with this - parameter. This parameter may be thought of as a bit-wise MASK for - the UNIX modes of a directory. Any bit not set - here will be removed from the modes set on a directory when it is - created.

    The default value of this parameter removes the 'group' - and 'other' write bits from the UNIX mode, allowing only the - user who owns the directory to modify it.

    Following this Samba will bit-wise 'OR' the UNIX mode - created from this parameter with the value of the force directory mode - parameter. This parameter is set to 000 by - default (i.e. no extra mode bits are added).

    Note that this parameter does not apply to permissions - set by Windows NT/2000 ACL editors. If the administrator wishes to enforce - a mask on access control lists also, they need to set the directory security mask.

    See the force - directory mode parameter to cause particular mode - bits to always be set on created directories.

    See also the create mode - parameter for masking mode bits on created files, - and the directory - security mask parameter.

    Also refer to the inherit permissions parameter.

    Default: directory mask = 0755

    Example: directory mask = 0775

    >directory mode (S)

    Synonym for directory mask

    >directory security mask (S)

    This parameter controls what UNIX permission bits - can be modified when a Windows NT client is manipulating the UNIX - permission on a directory using the native NT security dialog - box.

    This parameter is applied as a mask (AND'ed with) to - the changed permission bits, thus preventing any bits not in - this mask from being modified. Essentially, zero bits in this - mask may be treated as a set of bits the user is not allowed - to change.

    If not set explicitly this parameter is set to 0777 - meaning a user is allowed to modify all the user/group/world - permissions on a directory.

    Note that users who can access the - Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to leave - it as the default of 0777.

    See also the force directory security mode, security mask, - force security mode - parameters.

    Default: directory security mask = 0777

    Example: directory security mask = 0700

    >disable netbios (G)

    Enabling this parameter will disable netbios support - in Samba. Netbios is the only available form of browsing in - all windows versions except for 2000 and XP.

    Note that clients that only support netbios won't be able to - see your samba server when netbios support is disabled. -

    Default: disable netbios = no

    Example: disable netbios = yes

    >disable spoolss (G)

    Enabling this parameter will disable Samba's support - for the SPOOLSS set of MS-RPC's and will yield identical behavior - as Samba 2.0.x. Windows NT/2000 clients will downgrade to using - Lanman style printing commands. Windows 9x/ME will be uneffected by - the parameter. However, this will also disable the ability to upload - printer drivers to a Samba server via the Windows NT Add Printer - Wizard or by using the NT printer properties dialog window. It will - also disable the capability of Windows NT/2000 clients to download - print drivers from the Samba host upon demand. - Be very careful about enabling this parameter. -

    See also use client driver -

    Default : disable spoolss = no

    >display charset (G)

    Specifies the charset that samba will use - to print messages to stdout and stderr and SWAT will use. - Should generally be the same as the unix charset. -

    Default: display charset = ASCII

    Example: display charset = UTF8

    >dns proxy (G)

    Specifies that nmbd(8) when acting as a WINS server and - finding that a NetBIOS name has not been registered, should treat the - NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server - for that name on behalf of the name-querying client.

    Note that the maximum length for a NetBIOS name is 15 - characters, so the DNS name (or DNS alias) can likewise only be - 15 characters, maximum.

    nmbd spawns a second copy of itself to do the - DNS name lookup requests, as doing a name lookup is a blocking - action.

    See also the parameter wins support.

    Default: dns proxy = yes

    >domain logons (G)

    If set to yes, the Samba server will serve - Windows 95/98 Domain logons for the workgroup it is in. Samba 2.2 - has limited capability to act as a domain controller for Windows - NT 4 Domains. For more details on setting up this feature see - the Samba-PDC-HOWTO included in the htmldocs/ - directory shipped with the source code.

    Default: domain logons = no

    >domain master (G)

    Tell smbd(8) to enable WAN-wide browse list - collation. Setting this option causes nmbd to - claim a special domain specific NetBIOS name that identifies - it as a domain master browser for its given workgroup. Local master browsers - in the same workgroup on broadcast-isolated - subnets will give this nmbd their local browse lists, - and then ask smbd(8) for a complete copy of the browse - list for the whole wide area network. Browser clients will then contact - their local master browser, and will receive the domain-wide browse list, - instead of just the list for their broadcast-isolated subnet.

    Note that Windows NT Primary Domain Controllers expect to be - able to claim this workgroup specific special - NetBIOS name that identifies them as domain master browsers for - that workgroup by default (i.e. there is no - way to prevent a Windows NT PDC from attempting to do this). This - means that if this parameter is set and nmbd claims - the special name for a workgroup before a Windows - NT PDC is able to do so then cross subnet browsing will behave - strangely and may fail.

    If domain logons = yes - , then the default behavior is to enable the domain - master parameter. If domain logons is - not enabled (the default setting), then neither will domain - master be enabled by default.

    Default: domain master = auto

    >dont descend (S)

    There are certain directories on some systems - (e.g., the /proc tree under Linux) that are either not - of interest to clients or are infinitely deep (recursive). This - parameter allows you to specify a comma-delimited list of directories - that the server should always show as empty.

    Note that Samba can be very fussy about the exact format - of the "dont descend" entries. For example you may need ./proc instead of just /proc. - Experimentation is the best policy :-)

    Default: none (i.e., all directories are OK - to descend)

    Example: dont descend = /proc,/dev

    >dos charset (G)

    DOS SMB clients assume the server has - the same charset as they do. This option specifies which - charset Samba should talk to DOS clients. -

    The default depends on which charsets you have installed. - Samba tries to use charset 850 but falls back to ASCII in - case it is not available. Run testparm(1) to check the default on your system. -

    >dos filemode (S)

    The default behavior in Samba is to provide - UNIX-like behavior where only the owner of a file/directory is - able to change the permissions on it. However, this behavior - is often confusing to DOS/Windows users. Enabling this parameter - allows a user who has write access to the file (by whatever - means) to modify the permissions on it. Note that a user - belonging to the group owning the file will not be allowed to - change permissions if the group is only granted read access. - Ownership of the file/directory is not changed, only the permissions - are modified.

    Default: dos filemode = no

    >dos filetime resolution (S)

    Under the DOS and Windows FAT filesystem, the finest - granularity on time resolution is two seconds. Setting this parameter - for a share causes Samba to round the reported time down to the - nearest two second boundary when a query call that requires one second - resolution is made to smbd(8).

    This option is mainly used as a compatibility option for Visual - C++ when used against Samba shares. If oplocks are enabled on a - share, Visual C++ uses two different time reading calls to check if a - file has changed since it was last read. One of these calls uses a - one-second granularity, the other uses a two second granularity. As - the two second call rounds any odd second down, then if the file has a - timestamp of an odd number of seconds then the two timestamps will not - match and Visual C++ will keep reporting the file has changed. Setting - this option causes the two timestamps to match, and Visual C++ is - happy.

    Default: dos filetime resolution = no

    >dos filetimes (S)

    Under DOS and Windows, if a user can write to a - file they can change the timestamp on it. Under POSIX semantics, - only the owner of the file or root may change the timestamp. By - default, Samba runs with POSIX semantics and refuses to change the - timestamp on a file if the user smbd is acting - on behalf of is not the file owner. Setting this option to yes allows DOS semantics and smbd(8) will change the file - timestamp as DOS requires.

    Default: dos filetimes = no

    >encrypt passwords (G)

    This boolean controls whether encrypted passwords - will be negotiated with the client. Note that Windows NT 4.0 SP3 and - above and also Windows 98 will by default expect encrypted passwords - unless a registry entry is changed. To use encrypted passwords in - Samba see the chapter User Database in the Samba HOWTO Collection.

    In order for encrypted passwords to work correctly - smbd(8) must either - have access to a local smbpasswd(5) file (see the smbpasswd(8) program for information on how to set up - and maintain this file), or set the security = [server|domain|ads] parameter which - causes smbd to authenticate against another - server.

    Default: encrypt passwords = yes

    >enhanced browsing (G)

    This option enables a couple of enhancements to - cross-subnet browse propagation that have been added in Samba - but which are not standard in Microsoft implementations. -

    The first enhancement to browse propagation consists of a regular - wildcard query to a Samba WINS server for all Domain Master Browsers, - followed by a browse synchronization with each of the returned - DMBs. The second enhancement consists of a regular randomised browse - synchronization with all currently known DMBs.

    You may wish to disable this option if you have a problem with empty - workgroups not disappearing from browse lists. Due to the restrictions - of the browse protocols these enhancements can cause a empty workgroup - to stay around forever which can be annoying.

    In general you should leave this option enabled as it makes - cross-subnet browse propagation much more reliable.

    Default: enhanced browsing = yes

    >enumports command (G)

    The concept of a "port" is fairly foreign - to UNIX hosts. Under Windows NT/2000 print servers, a port - is associated with a port monitor and generally takes the form of - a local port (i.e. LPT1:, COM1:, FILE:) or a remote port - (i.e. LPD Port Monitor, etc...). By default, Samba has only one - port defined--"Samba Printer Port". Under - Windows NT/2000, all printers must have a valid port name. - If you wish to have a list of ports displayed (smbd - does not use a port name for anything) other than - the default "Samba Printer Port", you - can define enumports command to point to - a program which should generate a list of ports, one per line, - to standard output. This listing will then be used in response - to the level 1 and 2 EnumPorts() RPC.

    Default: no enumports command

    Example: enumports command = /usr/bin/listports -

    >exec (S)

    This is a synonym for preexec.

    >fake directory create times (S)

    NTFS and Windows VFAT file systems keep a create - time for all files and directories. This is not the same as the - ctime - status change time - that Unix keeps, so Samba by default - reports the earliest of the various times Unix does keep. Setting - this parameter for a share causes Samba to always report midnight - 1-1-1980 as the create time for directories.

    This option is mainly used as a compatibility option for - Visual C++ when used against Samba shares. Visual C++ generated - makefiles have the object directory as a dependency for each object - file, and a make rule to create the directory. Also, when NMAKE - compares timestamps it uses the creation time when examining a - directory. Thus the object directory will be created if it does not - exist, but once it does exist it will always have an earlier - timestamp than the object files it contains.

    However, Unix time semantics mean that the create time - reported by Samba will be updated whenever a file is created or - or deleted in the directory. NMAKE finds all object files in - the object directory. The timestamp of the last one built is then - compared to the timestamp of the object directory. If the - directory's timestamp if newer, then all object files - will be rebuilt. Enabling this option - ensures directories always predate their contents and an NMAKE build - will proceed as expected.

    Default: fake directory create times = no

    >fake oplocks (S)

    Oplocks are the way that SMB clients get permission - from a server to locally cache file operations. If a server grants - an oplock (opportunistic lock) then the client is free to assume - that it is the only one accessing the file and it will aggressively - cache file data. With some oplock types the client may even cache - file open/close operations. This can give enormous performance benefits. -

    When you set fake oplocks = yes, smbd(8) will - always grant oplock requests no matter how many clients are using - the file.

    It is generally much better to use the real oplocks support rather - than this parameter.

    If you enable this option on all read-only shares or - shares that you know will only be accessed from one client at a - time such as physically read-only media like CDROMs, you will see - a big performance improvement on many operations. If you enable - this option on shares where multiple clients may be accessing the - files read-write at the same time you can get data corruption. Use - this option carefully!

    Default: fake oplocks = no

    >follow symlinks (S)

    This parameter allows the Samba administrator - to stop smbd(8) from following symbolic - links in a particular share. Setting this - parameter to no prevents any file or directory - that is a symbolic link from being followed (the user will get an - error). This option is very useful to stop users from adding a - symbolic link to /etc/passwd in their home - directory for instance. However it will slow filename lookups - down slightly.

    This option is enabled (i.e. smbd will - follow symbolic links) by default.

    Default: follow symlinks = yes

    >force create mode (S)

    This parameter specifies a set of UNIX mode bit - permissions that will always be set on a - file created by Samba. This is done by bitwise 'OR'ing these bits onto - the mode bits of a file that is being created or having its - permissions changed. The default for this parameter is (in octal) - 000. The modes in this parameter are bitwise 'OR'ed onto the file - mode after the mask set in the create mask - parameter is applied.

    See also the parameter create - mask for details on masking mode bits on files.

    See also the inherit - permissions parameter.

    Default: force create mode = 000

    Example: force create mode = 0755

    would force all created files to have read and execute - permissions set for 'group' and 'other' as well as the - read/write/execute bits set for the 'user'.

    >force directory mode (S)

    This parameter specifies a set of UNIX mode bit - permissions that will always be set on a directory - created by Samba. This is done by bitwise 'OR'ing these bits onto the - mode bits of a directory that is being created. The default for this - parameter is (in octal) 0000 which will not add any extra permission - bits to a created directory. This operation is done after the mode - mask in the parameter directory mask is - applied.

    See also the parameter directory mask for details on masking mode bits - on created directories.

    See also the inherit permissions parameter.

    Default: force directory mode = 000

    Example: force directory mode = 0755

    would force all created directories to have read and execute - permissions set for 'group' and 'other' as well as the - read/write/execute bits set for the 'user'.

    >force directory security mode (S)

    This parameter controls what UNIX permission bits - can be modified when a Windows NT client is manipulating the UNIX - permission on a directory using the native NT security dialog box.

    This parameter is applied as a mask (OR'ed with) to the - changed permission bits, thus forcing any bits in this mask that - the user may have modified to be on. Essentially, one bits in this - mask may be treated as a set of bits that, when modifying security - on a directory, the user has always set to be 'on'.

    If not set explicitly this parameter is 000, which - allows a user to modify all the user/group/world permissions on a - directory without restrictions.

    Note that users who can access the - Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to leave - it set as 0000.

    See also the directory security mask, security mask, - force security mode - parameters.

    Default: force directory security mode = 0

    Example: force directory security mode = 700

    >force group (S)

    This specifies a UNIX group name that will be - assigned as the default primary group for all users connecting - to this service. This is useful for sharing files by ensuring - that all access to files on service will use the named group for - their permissions checking. Thus, by assigning permissions for this - group to the files and directories within this service the Samba - administrator can restrict or allow sharing of these files.

    In Samba 2.0.5 and above this parameter has extended - functionality in the following way. If the group name listed here - has a '+' character prepended to it then the current user accessing - the share only has the primary group default assigned to this group - if they are already assigned as a member of that group. This allows - an administrator to decide that only users who are already in a - particular group will create files with group ownership set to that - group. This gives a finer granularity of ownership assignment. For - example, the setting force group = +sys means - that only users who are already in group sys will have their default - primary group assigned to sys when accessing this Samba share. All - other users will retain their ordinary primary group.

    If the force user - parameter is also set the group specified in - force group will override the primary group - set in force user.

    See also force - user.

    Default: no forced group

    Example: force group = agroup

    >force security mode (S)

    This parameter controls what UNIX permission - bits can be modified when a Windows NT client is manipulating - the UNIX permission on a file using the native NT security dialog - box.

    This parameter is applied as a mask (OR'ed with) to the - changed permission bits, thus forcing any bits in this mask that - the user may have modified to be on. Essentially, one bits in this - mask may be treated as a set of bits that, when modifying security - on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to 0, - and allows a user to modify all the user/group/world permissions on a file, - with no restrictions.

    Note that users who can access - the Samba server through other means can easily bypass this restriction, - so it is primarily useful for standalone "appliance" systems. - Administrators of most normal systems will probably want to leave - this set to 0000.

    See also the force directory security mode, - directory security - mask, security mask parameters.

    Default: force security mode = 0

    Example: force security mode = 700

    >force user (S)

    This specifies a UNIX user name that will be - assigned as the default user for all users connecting to this service. - This is useful for sharing files. You should also use it carefully - as using it incorrectly can cause security problems.

    This user name only gets used once a connection is established. - Thus clients still need to connect as a valid user and supply a - valid password. Once connected, all file operations will be performed - as the "forced user", no matter what username the client connected - as. This can be very useful.

    In Samba 2.0.5 and above this parameter also causes the - primary group of the forced user to be used as the primary group - for all file activity. Prior to 2.0.5 the primary group was left - as the primary group of the connecting user (this was a bug).

    See also force group -

    Default: no forced user

    Example: force user = auser

    >fstype (S)

    This parameter allows the administrator to - configure the string that specifies the type of filesystem a share - is using that is reported by smbd(8) when a client queries the filesystem type - for a share. The default type is NTFS for - compatibility with Windows NT but this can be changed to other - strings such as Samba or FAT - if required.

    Default: fstype = NTFS

    Example: fstype = Samba

    >getwd cache (G)

    This is a tuning option. When this is enabled a - caching algorithm will be used to reduce the time taken for getwd() - calls. This can have a significant impact on performance, especially - when the wide links - parameter is set to no.

    Default: getwd cache = yes

    >group (S)

    Synonym for force - group.

    >guest account (S)

    This is a username which will be used for access - to services which are specified as guest ok (see below). Whatever privileges this - user has will be available to any client connecting to the guest service. - Typically this user will exist in the password file, but will not - have a valid login. The user account "ftp" is often a good choice - for this parameter. If a username is specified in a given service, - the specified username overrides this one.

    One some systems the default guest account "nobody" may not - be able to print. Use another account in this case. You should test - this by trying to log in as your guest user (perhaps by using the - su - command) and trying to print using the - system print command such as lpr(1) or lp(1).

    This parameter does not accept % macros, because - many parts of the system require this value to be - constant for correct operation.

    Default: specified at compile time, usually - "nobody"

    Example: guest account = ftp

    >guest ok (S)

    If this parameter is yes for - a service, then no password is required to connect to the service. - Privileges will be those of the guest account.

    This paramater nullifies the benifits of setting - restrict - anonymous = 2

    See the section below on security for more information about this option. -

    Default: guest ok = no

    >guest only (S)

    If this parameter is yes for - a service, then only guest connections to the service are permitted. - This parameter will have no effect if guest ok is not set for the service.

    See the section below on security for more information about this option. -

    Default: guest only = no

    >hide dot files (S)

    This is a boolean parameter that controls whether - files starting with a dot appear as hidden files.

    Default: hide dot files = yes

    >hide files(S)

    This is a list of files or directories that are not - visible but are accessible. The DOS 'hidden' attribute is applied - to any files or directories that match.

    Each entry in the list must be separated by a '/', - which allows spaces to be included in the entry. '*' - and '?' can be used to specify multiple files or directories - as in DOS wildcards.

    Each entry must be a Unix path, not a DOS path and must - not include the Unix directory separator '/'.

    Note that the case sensitivity option is applicable - in hiding files.

    Setting this parameter will affect the performance of Samba, - as it will be forced to check all files and directories for a match - as they are scanned.

    See also hide - dot files, veto files and case sensitive.

    Default: no file are hidden

    Example: hide files = - /.*/DesktopFolderDB/TrashFor%m/resource.frk/

    The above example is based on files that the Macintosh - SMB client (DAVE) available from - Thursby creates for internal use, and also still hides - all files beginning with a dot.

    >hide local users(G)

    This parameter toggles the hiding of local UNIX - users (root, wheel, floppy, etc) from remote clients.

    Default: hide local users = no

    >hide unreadable (G)

    This parameter prevents clients from seeing the - existance of files that cannot be read. Defaults to off.

    Default: hide unreadable = no

    >hide unwriteable files (G)

    This parameter prevents clients from seeing - the existance of files that cannot be written to. Defaults to off. - Note that unwriteable directories are shown as usual. -

    Default: hide unwriteable = no

    >hide special files (G)

    This parameter prevents clients from seeing - special files such as sockets, devices and fifo's in directory - listings. -

    Default: hide special files = no

    >homedir map (G)

    Ifnis homedir - is yes, and smbd(8) is also acting - as a Win95/98 logon server then this parameter - specifies the NIS (or YP) map from which the server for the user's - home directory should be extracted. At present, only the Sun - auto.home map format is understood. The form of the map is:

    username server:/some/file/system

    and the program will extract the servername from before - the first ':'. There should probably be a better parsing system - that copes with different map formats and also Amd (another - automounter) maps.

    A working NIS client is required on - the system for this option to work.

    See also nis homedir - , domain logons - .

    Default: homedir map = <empty string>

    Example: homedir map = amd.homedir

    >host msdfs (G)

    This boolean parameter is only available - if Samba has been configured and compiled with the --with-msdfs option. If set to yes, - Samba will act as a Dfs server, and allow Dfs-aware clients - to browse Dfs trees hosted on the server.

    See also the msdfs root share level parameter. For - more information on setting up a Dfs tree on Samba, - refer to msdfs_setup.html. -

    Default: host msdfs = no

    >hostname lookups (G)

    Specifies whether samba should use (expensive) - hostname lookups or use the ip addresses instead. An example place - where hostname lookups are currently used is when checking - the hosts deny and hosts allow. -

    Default: hostname lookups = yes

    Example: hostname lookups = no

    >hosts allow (S)

    A synonym for this parameter is allow - hosts.

    This parameter is a comma, space, or tab delimited - set of hosts which are permitted to access a service.

    If specified in the [global] section then it will - apply to all services, regardless of whether the individual - service has a different setting.

    You can specify the hosts by name or IP number. For - example, you could restrict access to only the hosts on a - Class C subnet with something like allow hosts = 150.203.5. - . The full syntax of the list is described in the man - page hosts_access(5). Note that this man - page may not be present on your system, so a brief description will - be given here also.

    Note that the localhost address 127.0.0.1 will always - be allowed access unless specifically denied by a hosts deny option.

    You can also specify hosts by network/netmask pairs and - by netgroup names if your system supports netgroups. The - EXCEPT keyword can also be used to limit a - wildcard list. The following examples may provide some help:

    Example 1: allow all IPs in 150.203.*.*; except one

    hosts allow = 150.203. EXCEPT 150.203.6.66

    Example 2: allow hosts that match the given network/netmask

    hosts allow = 150.203.15.0/255.255.255.0

    Example 3: allow a couple of hosts

    hosts allow = lapland, arvidsjaur

    Example 4: allow only hosts in NIS netgroup "foonet", but - deny access from one particular host

    hosts allow = @foonet

    hosts deny = pirate

    Note that access still requires suitable user-level passwords.

    See testparm(1) for a way of testing your host access - to see if it does what you expect.

    Default: none (i.e., all hosts permitted access) -

    Example: allow hosts = 150.203.5. myhost.mynet.edu.au -

    >hosts deny (S)

    The opposite of hosts allow - - hosts listed here are NOT permitted access to - services unless the specific services have their own lists to override - this one. Where the lists conflict, the allow - list takes precedence.

    Default: none (i.e., no hosts specifically excluded) -

    Example: hosts deny = 150.203.4. badhost.mynet.edu.au -

    >hosts equiv (G)

    If this global parameter is a non-null string, - it specifies the name of a file to read for the names of hosts - and users who will be allowed access without specifying a password. -

    This is not be confused with hosts allow which is about hosts - access to services and is more useful for guest services. hosts equiv may be useful for NT clients which will - not supply passwords to Samba.

    The use of hosts equiv - can be a major security hole. This is because you are - trusting the PC to supply the correct username. It is very easy to - get a PC to supply a false username. I recommend that the - hosts equiv option be only used if you really - know what you are doing, or perhaps on a home network where you trust - your spouse and kids. And only if you really trust - them :-).

    Default: no host equivalences

    Example: hosts equiv = /etc/hosts.equiv

    >include (G)

    This allows you to include one config file - inside another. The file is included literally, as though typed - in place.

    It takes the standard substitutions, except %u - , %P and %S. -

    Default: no file included

    Example: include = /usr/local/samba/lib/admin_smb.conf -

    >inherit acls (S)

    This parameter can be used to ensure - that if default acls exist on parent directories, - they are always honored when creating a subdirectory. - The default behavior is to use the mode specified - when creating the directory. Enabling this option - sets the mode to 0777, thus guaranteeing that - default directory acls are propagated. -

    Default: inherit acls = no -

    >inherit permissions (S)

    The permissions on new files and directories - are normally governed by create mask, directory mask, force create mode - and force - directory mode but the boolean inherit - permissions parameter overrides this.

    New directories inherit the mode of the parent directory, - including bits such as setgid.

    New files inherit their read/write bits from the parent - directory. Their execute bits continue to be determined by - map archive - , map hidden - and map system - as usual.

    Note that the setuid bit is never set via - inheritance (the code explicitly prohibits this).

    This can be particularly useful on large systems with - many users, perhaps several thousand, to allow a single [homes] - share to be used flexibly by each user.

    See also create mask - , directory mask, force create mode and force directory mode - .

    Default: inherit permissions = no

    >interfaces (G)

    This option allows you to override the default - network interfaces list that Samba will use for browsing, name - registration and other NBT traffic. By default Samba will query - the kernel for the list of all active interfaces and use any - interfaces except 127.0.0.1 that are broadcast capable.

    The option takes a list of interface strings. Each string - can be in any of the following forms:

    • a network interface name (such as eth0). - This may include shell-like wildcards so eth* will match - any interface starting with the substring "eth"

    • an IP address. In this case the netmask is - determined from the list of interfaces obtained from the - kernel

    • an IP/mask pair.

    • a broadcast/mask pair.

    The "mask" parameters can either be a bit length (such - as 24 for a C class network) or a full netmask in dotted - decimal form.

    The "IP" parameters above can either be a full dotted - decimal IP address or a hostname which will be looked up via - the OS's normal hostname resolution mechanisms.

    For example, the following line:

    interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 -

    would configure three network interfaces corresponding - to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. - The netmasks of the latter two interfaces would be set to 255.255.255.0.

    See also bind - interfaces only.

    Default: all active interfaces except 127.0.0.1 - that are broadcast capable

    >invalid users (S)

    This is a list of users that should not be allowed - to login to this service. This is really a paranoid - check to absolutely ensure an improper setting does not breach - your security.

    A name starting with a '@' is interpreted as an NIS - netgroup first (if your system supports NIS), and then as a UNIX - group if the name was not found in the NIS netgroup database.

    A name starting with '+' is interpreted only - by looking in the UNIX group database. A name starting with - '&' is interpreted only by looking in the NIS netgroup database - (this requires NIS to be working on your system). The characters - '+' and '&' may be used at the start of the name in either order - so the value +&group means check the - UNIX group database, followed by the NIS netgroup database, and - the value &+group means check the NIS - netgroup database, followed by the UNIX group database (the - same as the '@' prefix).

    The current servicename is substituted for %S. - This is useful in the [homes] section.

    See also valid users - .

    Default: no invalid users

    Example: invalid users = root fred admin @wheel -

    >keepalive (G)

    The value of the parameter (an integer) represents - the number of seconds between keepalive - packets. If this parameter is zero, no keepalive packets will be - sent. Keepalive packets, if sent, allow the server to tell whether - a client is still present and responding.

    Keepalives should, in general, not be needed if the socket - being used has the SO_KEEPALIVE attribute set on it (see socket options). - Basically you should only use this option if you strike difficulties.

    Default: keepalive = 300

    Example: keepalive = 600

    >kernel oplocks (G)

    For UNIXes that support kernel based oplocks - (currently only IRIX and the Linux 2.4 kernel), this parameter - allows the use of them to be turned on or off.

    Kernel oplocks support allows Samba oplocks - to be broken whenever a local UNIX process or NFS operation - accesses a file that smbd(8) has oplocked. This allows complete - data consistency between SMB/CIFS, NFS and local file access (and is - a very cool feature :-).

    This parameter defaults to on, but is translated - to a no-op on systems that no not have the necessary kernel support. - You should never need to touch this parameter.

    See also the oplocks - and level2 oplocks - parameters.

    Default: kernel oplocks = yes

    >lanman auth (G)

    This parameter determines whether or not smbd(8) will attempt to authenticate users - using the LANMAN password hash. If disabled, only clients which support NT - password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not - Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.

    Default : lanman auth = yes

    >large readwrite (G)

    This parameter determines whether or not smbd(8) supports the new 64k streaming - read and write varient SMB requests introduced - with Windows 2000. Note that due to Windows 2000 client redirector bugs - this requires Samba to be running on a 64-bit capable operating system such - as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with - Windows 2000 clients. Defaults to on. Not as tested as some other Samba - code paths. -

    Default : large readwrite = yes

    >ldap admin dn (G)

    The ldap admin dn defines the Distinguished - Name (DN) name used by Samba to contact the ldap server when retreiving - user account information. The ldap - admin dn is used in conjunction with the admin dn password - stored in the private/secrets.tdb file. See the - smbpasswd(8) man page for more information on how - to accmplish this.

    >ldap delete dn (G)

    This parameter specifies whether a delete - operation in the ldapsam deletes the complete entry or only the attributes - specific to Samba. -

    Default : ldap delete dn = no

    >ldap filter (G)

    This parameter specifies the RFC 2254 compliant LDAP search filter. - The default is to match the login name with the uid - attribute for all entries matching the sambaAccount - objectclass. Note that this filter should only return one entry. -

    Default : ldap filter = (&(uid=%u)(objectclass=sambaAccount))

    >ldap port (G)

    This parameter is only available if Samba has been - configure to include the --with-ldapsam option - at compile time. -

    This option is used to control the tcp port number used to contact - the ldap server. - The default is to use the stand LDAPS port 636. -

    See Also: ldap ssl -

    Default : ldap port = 636 ; if ldap ssl = on

    Default : ldap port = 389 ; if ldap ssl = off

    >ldap server (G)

    This parameter is only available if Samba has been - configure to include the --with-ldapsam option - at compile time. -

    This parameter should contain the FQDN of the ldap directory - server which should be queried to locate user account information. -

    Default : ldap server = localhost

    >ldap ssl (G)

    This option is used to define whether or not Samba should - use SSL when connecting to the ldap server - This is NOT related to - Samba's previous SSL support which was enabled by specifying the - --with-ssl option to the configure - script. -

    The ldap ssl can be set to one of three values: -

    • Off = Never use SSL when querying the directory.

    • Start_tls = Use the LDAPv3 StartTLS extended operation - (RFC2830) for communicating with the directory server.

    • On = - Use SSL on the ldaps port when contacting the - ldap server. Only - available when the backwards-compatiblity --with-ldapsam option is specified - to configure. See passdb backend

    Default : ldap ssl = start_tls

    >ldap suffix (G)

    Specifies where user and machine accounts are added to the tree. Can be overriden by ldap user suffix and ldap machine suffix. It also used as the base dn for all ldap searches.

    Default : none

    >ldap user suffix (G)

    It specifies where users are added to the tree. -

    Default : none

    >ldap machine suffix (G)

    It specifies where machines should be - added to the ldap tree. -

    Default : none

    >ldap passwd sync (G)

    This option is used to define whether - or not Samba should sync the LDAP password with the NT - and LM hashes for normal accounts (NOT for - workstation, server or domain trusts) on a password - change via SAMBA. -

    The ldap passwd sync can be set to one of three values: -

    • Yes = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time.

    • No = Update NT and LM passwords and update the pwdLastSet time.

    • Only = Only update the LDAP password and let the LDAP server do the rest.

    Default : ldap passwd sync = no

    >ldap trust ids (G)

    Normally, Samba validates each entry - in the LDAP server against getpwnam(). This allows - LDAP to be used for Samba with the unix system using - NIS (for example) and also ensures that Samba does not - present accounts that do not otherwise exist.

    This option is used to disable this functionality, and - instead to rely on the presence of the appropriate - attributes in LDAP directly, which can result in a - significant performance boost in some situations. - Setting this option to yes effectivly assumes - that the local machine is running nss_ldap against the - same LDAP server.

    Default: ldap trust ids = No

    >level2 oplocks (S)

    This parameter controls whether Samba supports - level2 (read-only) oplocks on a share.

    Level2, or read-only oplocks allow Windows NT clients - that have an oplock on a file to downgrade from a read-write oplock - to a read-only oplock once a second client opens the file (instead - of releasing all oplocks on a second open, as in traditional, - exclusive oplocks). This allows all openers of the file that - support level2 oplocks to cache the file for read-ahead only (ie. - they may not cache writes or lock requests) and increases performance - for many accesses of files that are not commonly written (such as - application .EXE files).

    Once one of the clients which have a read-only oplock - writes to the file all clients are notified (no reply is needed - or waited for) and told to break their oplocks to "none" and - delete any read-ahead caches.

    It is recommended that this parameter be turned on - to speed access to shared executables.

    For more discussions on level2 oplocks see the CIFS spec.

    Currently, if kernel - oplocks are supported then level2 oplocks are - not granted (even if this parameter is set to yes). - Note also, the oplocks - parameter must be set to yes on this share in order for - this parameter to have any effect.

    See also the oplocks - and kernel oplocks - parameters.

    Default: level2 oplocks = yes

    >lm announce (G)

    This parameter determines if nmbd(8) will produce Lanman announce - broadcasts that are needed by OS/2 clients in order for them to see - the Samba server in their browse list. This parameter can have three - values, yes, no, or - auto. The default is auto. - If set to no Samba will never produce these - broadcasts. If set to yes Samba will produce - Lanman announce broadcasts at a frequency set by the parameter - lm interval. If set to auto - Samba will not send Lanman announce broadcasts by default but will - listen for them. If it hears such a broadcast on the wire it will - then start sending them at a frequency set by the parameter - lm interval.

    See also lm interval - .

    Default: lm announce = auto

    Example: lm announce = yes

    >lm interval (G)

    If Samba is set to produce Lanman announce - broadcasts needed by OS/2 clients (see the lm announce parameter) then this - parameter defines the frequency in seconds with which they will be - made. If this is set to zero then no Lanman announcements will be - made despite the setting of the lm announce - parameter.

    See also lm - announce.

    Default: lm interval = 60

    Example: lm interval = 120

    >load printers (G)

    A boolean variable that controls whether all - printers in the printcap will be loaded for browsing by default. - See the printers section for - more details.

    Default: load printers = yes

    >local master (G)

    This option allows nmbd(8) to try and become a local master browser - on a subnet. If set to no then nmbd will not attempt to become a local master browser - on a subnet and will also lose in all browsing elections. By - default this value is set to yes. Setting this value to yes doesn't - mean that Samba will become the local master - browser on a subnet, just that nmbd will participate in elections for local master browser.

    Setting this value to no will cause nmbd - never to become a local master browser.

    Default: local master = yes

    >lock dir (G)

    Synonym for lock directory.

    >lock directory (G)

    This option specifies the directory where lock - files will be placed. The lock files are used to implement the - max connections - option.

    Default: lock directory = ${prefix}/var/locks

    Example: lock directory = /var/run/samba/locks -

    >lock spin count (G)

    This parameter controls the number of times - that smbd should attempt to gain a byte range lock on the - behalf of a client request. Experiments have shown that - Windows 2k servers do not reply with a failure if the lock - could not be immediately granted, but try a few more times - in case the lock could later be aquired. This behavior - is used to support PC database formats such as MS Access - and FoxPro. -

    Default: lock spin count = 2 -

    >lock spin time (G)

    The time in microseconds that smbd should - pause before attempting to gain a failed lock. See - lock spin - count for more details. -

    Default: lock spin time = 10 -

    >locking (S)

    This controls whether or not locking will be - performed by the server in response to lock requests from the - client.

    If locking = no, all lock and unlock - requests will appear to succeed and all lock queries will report - that the file in question is available for locking.

    If locking = yes, real locking will be performed - by the server.

    This option may be useful for read-only - filesystems which may not need locking (such as - CDROM drives), although setting this parameter of no - is not really recommended even in this case.

    Be careful about disabling locking either globally or in a - specific service, as lack of locking may result in data corruption. - You should never need to set this parameter.

    Default: locking = yes

    >log file (G)

    This option allows you to override the name - of the Samba log file (also known as the debug file).

    This option takes the standard substitutions, allowing - you to have separate log files for each user or machine.

    Example: log file = /usr/local/samba/var/log.%m -

    >log level (G)

    The value of the parameter (a astring) allows - the debug level (logging level) to be specified in the - smb.conf file. This parameter has been - extended since the 2.2.x series, now it allow to specify the debug - level for multiple debug classes. This is to give greater - flexibility in the configuration of the system.

    The default will be the log level specified on - the command line or level zero if none was specified.

    Example: log level = 3 passdb:5 auth:10 winbind:2 -

    >logon drive (G)

    This parameter specifies the local path to - which the home directory will be connected (see logon home) - and is only used by NT Workstations.

    Note that this option is only useful if Samba is set up as a - logon server.

    Default: logon drive = z:

    Example: logon drive = h:

    >logon home (G)

    This parameter specifies the home directory - location when a Win95/98 or NT Workstation logs into a Samba PDC. - It allows you to do

    C:\> NET USE H: /HOME -

    from a command prompt, for example.

    This option takes the standard substitutions, allowing - you to have separate logon scripts for each user or machine.

    This parameter can be used with Win9X workstations to ensure - that roaming profiles are stored in a subdirectory of the user's - home directory. This is done in the following way:

    logon home = \\%N\%U\profile

    This tells Samba to return the above string, with - substitutions made when a client requests the info, generally - in a NetUserGetInfo request. Win9X clients truncate the info to - \\server\share when a user does net use /home - but use the whole string when dealing with profiles.

    Note that in prior versions of Samba, the logon path was returned rather than - logon home. This broke net use - /home but allowed profiles outside the home directory. - The current implementation is correct, and can be used for - profiles if you use the above trick.

    This option is only useful if Samba is set up as a logon - server.

    Default: logon home = "\\%N\%U"

    Example: logon home = "\\remote_smb_server\%U" -

    >logon path (G)

    This parameter specifies the home directory - where roaming profiles (NTuser.dat etc files for Windows NT) are - stored. Contrary to previous versions of these manual pages, it has - nothing to do with Win 9X roaming profiles. To find out how to - handle roaming profiles for Win 9X system, see the logon home parameter.

    This option takes the standard substitutions, allowing you - to have separate logon scripts for each user or machine. It also - specifies the directory from which the "Application Data", - (desktop, start menu, - network neighborhood, programs - and other folders, and their contents, are loaded and displayed on - your Windows NT client.

    The share and the path must be readable by the user for - the preferences and directories to be loaded onto the Windows NT - client. The share must be writeable when the user logs in for the first - time, in order that the Windows NT client can create the NTuser.dat - and other directories.

    Thereafter, the directories and any of the contents can, - if required, be made read-only. It is not advisable that the - NTuser.dat file be made read-only - rename it to NTuser.man to - achieve the desired effect (a MANdatory - profile).

    Windows clients can sometimes maintain a connection to - the [homes] share, even though there is no user logged in. - Therefore, it is vital that the logon path does not include a - reference to the homes share (i.e. setting this parameter to - \%N\%U\profile_path will cause problems).

    This option takes the standard substitutions, allowing - you to have separate logon scripts for each user or machine.

    Note that this option is only useful if Samba is set up - as a logon server.

    Default: logon path = \\%N\%U\profile

    Example: logon path = \\PROFILESERVER\PROFILE\%U

    >logon script (G)

    This parameter specifies the batch file (.bat) or - NT command file (.cmd) to be downloaded and run on a machine when - a user successfully logs in. The file must contain the DOS - style CR/LF line endings. Using a DOS-style editor to create the - file is recommended.

    The script must be a relative path to the [netlogon] - service. If the [netlogon] service specifies a path of /usr/local/samba/netlogon - , and logon script = STARTUP.BAT, then - the file that will be downloaded is:

    /usr/local/samba/netlogon/STARTUP.BAT

    The contents of the batch file are entirely your choice. A - suggested command would be to add NET TIME \\SERVER /SET - /YES, to force every machine to synchronize clocks with - the same time server. Another use would be to add NET USE - U: \\SERVER\UTILS for commonly used utilities, or NET USE Q: \\SERVER\ISO9001_QA for example.

    Note that it is particularly important not to allow write - access to the [netlogon] share, or to grant users write permission - on the batch files in a secure environment, as this would allow - the batch files to be arbitrarily modified and security to be - breached.

    This option takes the standard substitutions, allowing you - to have separate logon scripts for each user or machine.

    This option is only useful if Samba is set up as a logon - server.

    Default: no logon script defined

    Example: logon script = scripts\%U.bat

    >lppause command (S)

    This parameter specifies the command to be - executed on the server host in order to stop printing or spooling - a specific print job.

    This command should be a program or script which takes - a printer name and job number to pause the print job. One way - of implementing this is by using job priorities, where jobs - having a too low priority won't be sent to the printer.

    If a %p is given then the printer name - is put in its place. A %j is replaced with - the job number (an integer). On HPUX (see printing=hpux - ), if the -p%p option is added - to the lpq command, the job will show up with the correct status, i.e. - if the job priority is lower than the set fence priority it will - have the PAUSED status, whereas if the priority is equal or higher it - will have the SPOOLED or PRINTING status.

    Note that it is good practice to include the absolute path - in the lppause command as the PATH may not be available to the server.

    See also the printing - parameter.

    Default: Currently no default value is given to - this string, unless the value of the printing - parameter is SYSV, in which case the default is :

    lp -i %p-%j -H hold

    or if the value of the printing parameter - is SOFTQ, then the default is:

    qstat -s -j%j -h

    Example for HPUX: lppause command = /usr/bin/lpalt - %p-%j -p0

    >lpq cache time (G)

    This controls how long lpq info will be cached - for to prevent the lpq command being called too - often. A separate cache is kept for each variation of the lpq command used by the system, so if you use different - lpq commands for different users then they won't - share cache information.

    The cache files are stored in /tmp/lpq.xxxx - where xxxx is a hash of the lpq command in use.

    The default is 10 seconds, meaning that the cached results - of a previous identical lpq command will be used - if the cached data is less than 10 seconds old. A large value may - be advisable if your lpq command is very slow.

    A value of 0 will disable caching completely.

    See also the printing - parameter.

    Default: lpq cache time = 10

    Example: lpq cache time = 30

    >lpq command (S)

    This parameter specifies the command to be - executed on the server host in order to obtain lpq - -style printer status information.

    This command should be a program or script which - takes a printer name as its only parameter and outputs printer - status information.

    Currently nine styles of printer status information - are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. - This covers most UNIX systems. You control which type is expected - using the printing = option.

    Some clients (notably Windows for Workgroups) may not - correctly send the connection number for the printer they are - requesting status information about. To get around this, the - server reports on the first printer service connected to by the - client. This only happens if the connection number sent is invalid.

    If a %p is given then the printer name - is put in its place. Otherwise it is placed at the end of the - command.

    Note that it is good practice to include the absolute path - in the lpq command as the $PATH - may not be available to the server. When compiled with - the CUPS libraries, no lpq command is - needed because smbd will make a library call to obtain the - print queue listing.

    See also the printing - parameter.

    Default: depends on the setting of printing

    Example: lpq command = /usr/bin/lpq -P%p

    >lpresume command (S)

    This parameter specifies the command to be - executed on the server host in order to restart or continue - printing or spooling a specific print job.

    This command should be a program or script which takes - a printer name and job number to resume the print job. See - also the lppause command - parameter.

    If a %p is given then the printer name - is put in its place. A %j is replaced with - the job number (an integer).

    Note that it is good practice to include the absolute path - in the lpresume command as the PATH may not - be available to the server.

    See also the printing - parameter.

    Default: Currently no default value is given - to this string, unless the value of the printing - parameter is SYSV, in which case the default is :

    lp -i %p-%j -H resume

    or if the value of the printing parameter - is SOFTQ, then the default is:

    qstat -s -j%j -r

    Example for HPUX: lpresume command = /usr/bin/lpalt - %p-%j -p2

    >lprm command (S)

    This parameter specifies the command to be - executed on the server host in order to delete a print job.

    This command should be a program or script which takes - a printer name and job number, and deletes the print job.

    If a %p is given then the printer name - is put in its place. A %j is replaced with - the job number (an integer).

    Note that it is good practice to include the absolute - path in the lprm command as the PATH may not be - available to the server.

    See also the printing - parameter.

    Default: depends on the setting of printing -

    Example 1: lprm command = /usr/bin/lprm -P%p %j -

    Example 2: lprm command = /usr/bin/cancel %p-%j -

    >machine password timeout (G)

    If a Samba server is a member of a Windows - NT Domain (see the security = domain) - parameter) then periodically a running smbd(8) process will try and change the MACHINE ACCOUNT - PASSWORD stored in the TDB called private/secrets.tdb - . This parameter specifies how often this password - will be changed, in seconds. The default is one week (expressed in - seconds), the same as a Windows NT Domain member server.

    See also smbpasswd(8), and the security = domain) parameter.

    Default: machine password timeout = 604800

    >magic output (S)

    This parameter specifies the name of a file - which will contain output created by a magic script (see the - magic script - parameter below).

    Warning: If two clients use the same magic script - in the same directory the output file content - is undefined.

    Default: magic output = <magic script name>.out -

    Example: magic output = myfile.txt

    >magic script (S)

    This parameter specifies the name of a file which, - if opened, will be executed by the server when the file is closed. - This allows a UNIX script to be sent to the Samba host and - executed on behalf of the connected user.

    Scripts executed in this way will be deleted upon - completion assuming that the user has the appropriate level - of privilege and the file permissions allow the deletion.

    If the script generates output, output will be sent to - the file specified by the magic output parameter (see above).

    Note that some shells are unable to interpret scripts - containing CR/LF instead of CR as - the end-of-line marker. Magic scripts must be executable - as is on the host, which for some hosts and - some shells will require filtering at the DOS end.

    Magic scripts are EXPERIMENTAL and - should NOT be relied upon.

    Default: None. Magic scripts disabled.

    Example: magic script = user.csh

    >mangle case (S)

    See the section on NAME MANGLING

    Default: mangle case = no

    >mangled map (S)

    This is for those who want to directly map UNIX - file names which cannot be represented on Windows/DOS. The mangling - of names is not always what is needed. In particular you may have - documents with file extensions that differ between DOS and UNIX. - For example, under UNIX it is common to use .html - for HTML files, whereas under Windows/DOS .htm - is more commonly used.

    So to map html to htm - you would use:

    mangled map = (*.html *.htm)

    One very useful case is to remove the annoying ;1 - off the ends of filenames on some CDROMs (only visible - under some UNIXes). To do this use a map of (*;1 *;).

    Default: no mangled map

    Example: mangled map = (*;1 *;)

    >mangled names (S)

    This controls whether non-DOS names under UNIX - should be mapped to DOS-compatible names ("mangled") and made visible, - or whether non-DOS names should simply be ignored.

    See the section on NAME MANGLING for details on how to control the mangling process.

    If mangling is used then the mangling algorithm is as follows:

    • The first (up to) five alphanumeric characters +/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' +

      Note that you may have to replace the command names with full path names on some systems.

    directory mask (S)

    This parameter is the octal modes which are + used when converting DOS modes to UNIX modes when creating UNIX + directories.

    When a directory is created, the necessary permissions are + calculated according to the mapping from DOS modes to UNIX permissions, + and the resulting UNIX mode is then bit-wise 'AND'ed with this + parameter. This parameter may be thought of as a bit-wise MASK for + the UNIX modes of a directory. Any bit not set + here will be removed from the modes set on a directory when it is + created.

    The default value of this parameter removes the 'group' + and 'other' write bits from the UNIX mode, allowing only the + user who owns the directory to modify it.

    Following this Samba will bit-wise 'OR' the UNIX mode + created from this parameter with the value of the + force directory mode parameter. + This parameter is set to 000 by default (i.e. no extra mode bits are added).

    Note that this parameter does not apply to permissions + set by Windows NT/2000 ACL editors. If the administrator wishes to enforce + a mask on access control lists also, they need to set the + directory security mask.

    See the force + directory mode parameter to cause particular mode + bits to always be set on created directories.

    See also the create mode + parameter for masking mode bits on created files, + and the directory + security mask parameter.

    Also refer to the + inherit permissions parameter.

    Default: directory mask = 0755

    Example: directory mask = 0775

    directory mode (S)

    Synonym for + directory mask

    directory security mask (S)

    This parameter controls what UNIX permission bits + can be modified when a Windows NT client is manipulating the UNIX + permission on a directory using the native NT security dialog + box.

    This parameter is applied as a mask (AND'ed with) to + the changed permission bits, thus preventing any bits not in + this mask from being modified. Essentially, zero bits in this + mask may be treated as a set of bits the user is not allowed + to change.

    If not set explicitly this parameter is set to 0777 + meaning a user is allowed to modify all the user/group/world + permissions on a directory.

    Note that users who can access the + Samba server through other means can easily bypass this restriction, + so it is primarily useful for standalone "appliance" systems. + Administrators of most normal systems will probably want to leave + it as the default of 0777.

    See also the + force directory security mode, + security mask, + force security mode + parameters.

    Default: directory security mask = 0777

    Example: directory security mask = 0700

    directory (S)

    Synonym for path.

    disable netbios (G)

    Enabling this parameter will disable netbios support + in Samba. Netbios is the only available form of browsing in + all windows versions except for 2000 and XP.

    Note

    Note that clients that only support netbios won't be able to + see your samba server when netbios support is disabled. +

    Default: disable netbios = no

    Example: disable netbios = yes

    disable spoolss (G)

    Enabling this parameter will disable Samba's support + for the SPOOLSS set of MS-RPC's and will yield identical behavior + as Samba 2.0.x. Windows NT/2000 clients will downgrade to using + Lanman style printing commands. Windows 9x/ME will be uneffected by + the parameter. However, this will also disable the ability to upload + printer drivers to a Samba server via the Windows NT Add Printer + Wizard or by using the NT printer properties dialog window. It will + also disable the capability of Windows NT/2000 clients to download + print drivers from the Samba host upon demand. + Be very careful about enabling this parameter. +

    See also use client driver +

    Default : disable spoolss = no

    display charset (G)

    Specifies the charset that samba will use + to print messages to stdout and stderr and SWAT will use. + Should generally be the same as the unix charset. +

    Default: display charset = ASCII

    Example: display charset = UTF8

    dns proxy (G)

    Specifies that nmbd(8) when acting as a WINS server and + finding that a NetBIOS name has not been registered, should treat the + NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server + for that name on behalf of the name-querying client.

    Note that the maximum length for a NetBIOS name is 15 + characters, so the DNS name (or DNS alias) can likewise only be + 15 characters, maximum.

    nmbd spawns a second copy of itself to do the + DNS name lookup requests, as doing a name lookup is a blocking + action.

    See also the parameter + wins support.

    Default: dns proxy = yes

    domain logons (G)

    If set to yes, the Samba server will serve + Windows 95/98 Domain logons for the + workgroup it is in. Samba 2.2 + has limited capability to act as a domain controller for Windows + NT 4 Domains. For more details on setting up this feature see + the Samba-PDC-HOWTO included in the Samba documentation.

    Default: domain logons = no

    domain master (G)

    Tell smbd(8) to enable WAN-wide browse list + collation. Setting this option causes nmbd to + claim a special domain specific NetBIOS name that identifies + it as a domain master browser for its given + workgroup. Local master browsers + in the same workgroup on broadcast-isolated + subnets will give this nmbd their local browse lists, + and then ask smbd(8) for a complete copy of the browse + list for the whole wide area network. Browser clients will then contact + their local master browser, and will receive the domain-wide browse list, + instead of just the list for their broadcast-isolated subnet.

    Note that Windows NT Primary Domain Controllers expect to be + able to claim this workgroup specific special + NetBIOS name that identifies them as domain master browsers for + that workgroup by default (i.e. there is no + way to prevent a Windows NT PDC from attempting to do this). This + means that if this parameter is set and nmbd claims + the special name for a workgroup before a Windows + NT PDC is able to do so then cross subnet browsing will behave + strangely and may fail.

    If domain logons = yes + , then the default behavior is to enable the domain + master parameter. If domain logons is + not enabled (the default setting), then neither will domain + master be enabled by default.

    Default: domain master = auto

    dont descend (S)

    There are certain directories on some systems + (e.g., the /proc tree under Linux) that are either not + of interest to clients or are infinitely deep (recursive). This + parameter allows you to specify a comma-delimited list of directories + that the server should always show as empty.

    Note that Samba can be very fussy about the exact format + of the "dont descend" entries. For example you may need + ./proc instead of just /proc. + Experimentation is the best policy :-)

    Default: none (i.e., all directories are OK + to descend)

    Example: dont descend = /proc,/dev

    dos charset (G)

    DOS SMB clients assume the server has + the same charset as they do. This option specifies which + charset Samba should talk to DOS clients. +

    The default depends on which charsets you have installed. + Samba tries to use charset 850 but falls back to ASCII in + case it is not available. Run testparm(1) to check the default on your system.

    dos filemode (S)

    The default behavior in Samba is to provide + UNIX-like behavior where only the owner of a file/directory is + able to change the permissions on it. However, this behavior + is often confusing to DOS/Windows users. Enabling this parameter + allows a user who has write access to the file (by whatever + means) to modify the permissions on it. Note that a user + belonging to the group owning the file will not be allowed to + change permissions if the group is only granted read access. + Ownership of the file/directory is not changed, only the permissions + are modified.

    Default: dos filemode = no

    dos filetime resolution (S)

    Under the DOS and Windows FAT filesystem, the finest + granularity on time resolution is two seconds. Setting this parameter + for a share causes Samba to round the reported time down to the + nearest two second boundary when a query call that requires one second + resolution is made to smbd(8).

    This option is mainly used as a compatibility option for Visual + C++ when used against Samba shares. If oplocks are enabled on a + share, Visual C++ uses two different time reading calls to check if a + file has changed since it was last read. One of these calls uses a + one-second granularity, the other uses a two second granularity. As + the two second call rounds any odd second down, then if the file has a + timestamp of an odd number of seconds then the two timestamps will not + match and Visual C++ will keep reporting the file has changed. Setting + this option causes the two timestamps to match, and Visual C++ is + happy.

    Default: dos filetime resolution = no

    dos filetimes (S)

    Under DOS and Windows, if a user can write to a + file they can change the timestamp on it. Under POSIX semantics, + only the owner of the file or root may change the timestamp. By + default, Samba runs with POSIX semantics and refuses to change the + timestamp on a file if the user smbd is acting + on behalf of is not the file owner. Setting this option to + yes allows DOS semantics and smbd(8) will change the file + timestamp as DOS requires.

    Default: dos filetimes = no

    encrypt passwords (G)

    This boolean controls whether encrypted passwords + will be negotiated with the client. Note that Windows NT 4.0 SP3 and + above and also Windows 98 will by default expect encrypted passwords + unless a registry entry is changed. To use encrypted passwords in + Samba see the chapter "User Database" in the Samba HOWTO Collection.

    In order for encrypted passwords to work correctly + smbd(8) must either + have access to a local smbpasswd(5) file (see the smbpasswd(8) program for information on how to set up + and maintain this file), or set the security = [server|domain|ads] parameter which + causes smbd to authenticate against another + server.

    Default: encrypt passwords = yes

    enhanced browsing (G)

    This option enables a couple of enhancements to + cross-subnet browse propagation that have been added in Samba + but which are not standard in Microsoft implementations. +

    The first enhancement to browse propagation consists of a regular + wildcard query to a Samba WINS server for all Domain Master Browsers, + followed by a browse synchronization with each of the returned + DMBs. The second enhancement consists of a regular randomised browse + synchronization with all currently known DMBs.

    You may wish to disable this option if you have a problem with empty + workgroups not disappearing from browse lists. Due to the restrictions + of the browse protocols these enhancements can cause a empty workgroup + to stay around forever which can be annoying.

    In general you should leave this option enabled as it makes + cross-subnet browse propagation much more reliable.

    Default: enhanced browsing = yes

    enumports command (G)

    The concept of a "port" is fairly foreign + to UNIX hosts. Under Windows NT/2000 print servers, a port + is associated with a port monitor and generally takes the form of + a local port (i.e. LPT1:, COM1:, FILE:) or a remote port + (i.e. LPD Port Monitor, etc...). By default, Samba has only one + port defined--"Samba Printer Port". Under + Windows NT/2000, all printers must have a valid port name. + If you wish to have a list of ports displayed (smbd + does not use a port name for anything) other than + the default "Samba Printer Port", you + can define enumports command to point to + a program which should generate a list of ports, one per line, + to standard output. This listing will then be used in response + to the level 1 and 2 EnumPorts() RPC.

    Default: no enumports command

    Example: enumports command = /usr/bin/listports

    exec (S)

    This is a synonym for + preexec.

    fake directory create times (S)

    NTFS and Windows VFAT file systems keep a create + time for all files and directories. This is not the same as the + ctime - status change time - that Unix keeps, so Samba by default + reports the earliest of the various times Unix does keep. Setting + this parameter for a share causes Samba to always report midnight + 1-1-1980 as the create time for directories.

    This option is mainly used as a compatibility option for + Visual C++ when used against Samba shares. Visual C++ generated + makefiles have the object directory as a dependency for each object + file, and a make rule to create the directory. Also, when NMAKE + compares timestamps it uses the creation time when examining a + directory. Thus the object directory will be created if it does not + exist, but once it does exist it will always have an earlier + timestamp than the object files it contains.

    However, Unix time semantics mean that the create time + reported by Samba will be updated whenever a file is created or + or deleted in the directory. NMAKE finds all object files in + the object directory. The timestamp of the last one built is then + compared to the timestamp of the object directory. If the + directory's timestamp if newer, then all object files + will be rebuilt. Enabling this option + ensures directories always predate their contents and an NMAKE build + will proceed as expected.

    Default: fake directory create times = no

    fake oplocks (S)

    Oplocks are the way that SMB clients get permission + from a server to locally cache file operations. If a server grants + an oplock (opportunistic lock) then the client is free to assume + that it is the only one accessing the file and it will aggressively + cache file data. With some oplock types the client may even cache + file open/close operations. This can give enormous performance benefits. +

    When you set fake oplocks = yes, smbd(8) will + always grant oplock requests no matter how many clients are using the file.

    It is generally much better to use the real + oplocks support rather + than this parameter.

    If you enable this option on all read-only shares or + shares that you know will only be accessed from one client at a + time such as physically read-only media like CDROMs, you will see + a big performance improvement on many operations. If you enable + this option on shares where multiple clients may be accessing the + files read-write at the same time you can get data corruption. Use + this option carefully!

    Default: fake oplocks = no

    follow symlinks (S)

    This parameter allows the Samba administrator + to stop smbd(8) from following symbolic + links in a particular share. Setting this + parameter to no prevents any file or directory + that is a symbolic link from being followed (the user will get an + error). This option is very useful to stop users from adding a + symbolic link to /etc/passwd in their home + directory for instance. However it will slow filename lookups + down slightly.

    This option is enabled (i.e. smbd will + follow symbolic links) by default.

    Default: follow symlinks = yes

    force create mode (S)

    This parameter specifies a set of UNIX mode bit + permissions that will always be set on a + file created by Samba. This is done by bitwise 'OR'ing these bits onto + the mode bits of a file that is being created or having its + permissions changed. The default for this parameter is (in octal) + 000. The modes in this parameter are bitwise 'OR'ed onto the file + mode after the mask set in the create mask + parameter is applied.

    See also the parameter create + mask for details on masking mode bits on files.

    See also the inherit + permissions parameter.

    Default: force create mode = 000

    Example: force create mode = 0755

    would force all created files to have read and execute + permissions set for 'group' and 'other' as well as the + read/write/execute bits set for the 'user'.

    force directory mode (S)

    This parameter specifies a set of UNIX mode bit + permissions that will always be set on a directory + created by Samba. This is done by bitwise 'OR'ing these bits onto the + mode bits of a directory that is being created. The default for this + parameter is (in octal) 0000 which will not add any extra permission + bits to a created directory. This operation is done after the mode + mask in the parameter directory mask is + applied.

    See also the parameter + directory mask for details on masking mode bits + on created directories.

    See also the + inherit permissions parameter.

    Default: force directory mode = 000

    Example: force directory mode = 0755

    would force all created directories to have read and execute + permissions set for 'group' and 'other' as well as the + read/write/execute bits set for the 'user'.

    force directory security mode (S)

    This parameter controls what UNIX permission bits + can be modified when a Windows NT client is manipulating the UNIX + permission on a directory using the native NT security dialog box.

    This parameter is applied as a mask (OR'ed with) to the + changed permission bits, thus forcing any bits in this mask that + the user may have modified to be on. Essentially, one bits in this + mask may be treated as a set of bits that, when modifying security + on a directory, the user has always set to be 'on'.

    If not set explicitly this parameter is 000, which + allows a user to modify all the user/group/world permissions on a + directory without restrictions.

    Note that users who can access the + Samba server through other means can easily bypass this restriction, + so it is primarily useful for standalone "appliance" systems. + Administrators of most normal systems will probably want to leave + it set as 0000.

    See also the + directory security mask, + security mask, + force security mode + parameters.

    Default: force directory security mode = 0

    Example: force directory security mode = 700

    force group (S)

    This specifies a UNIX group name that will be + assigned as the default primary group for all users connecting + to this service. This is useful for sharing files by ensuring + that all access to files on service will use the named group for + their permissions checking. Thus, by assigning permissions for this + group to the files and directories within this service the Samba + administrator can restrict or allow sharing of these files.

    In Samba 2.0.5 and above this parameter has extended + functionality in the following way. If the group name listed here + has a '+' character prepended to it then the current user accessing + the share only has the primary group default assigned to this group + if they are already assigned as a member of that group. This allows + an administrator to decide that only users who are already in a + particular group will create files with group ownership set to that + group. This gives a finer granularity of ownership assignment. For + example, the setting force group = +sys means + that only users who are already in group sys will have their default + primary group assigned to sys when accessing this Samba share. All + other users will retain their ordinary primary group.

    If the force user + parameter is also set the group specified in + force group will override the primary group + set in force user.

    See also force user.

    Default: no forced group

    Example: force group = agroup

    force security mode (S)

    This parameter controls what UNIX permission + bits can be modified when a Windows NT client is manipulating + the UNIX permission on a file using the native NT security dialog + box.

    This parameter is applied as a mask (OR'ed with) to the + changed permission bits, thus forcing any bits in this mask that + the user may have modified to be on. Essentially, one bits in this + mask may be treated as a set of bits that, when modifying security + on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to 0, + and allows a user to modify all the user/group/world permissions on a file, + with no restrictions.

    Note that users who can access + the Samba server through other means can easily bypass this restriction, + so it is primarily useful for standalone "appliance" systems. + Administrators of most normal systems will probably want to leave + this set to 0000.

    See also the + force directory security mode, + directory security + mask, + security mask parameters.

    Default: force security mode = 0

    Example: force security mode = 700

    force user (S)

    This specifies a UNIX user name that will be + assigned as the default user for all users connecting to this service. + This is useful for sharing files. You should also use it carefully + as using it incorrectly can cause security problems.

    This user name only gets used once a connection is established. + Thus clients still need to connect as a valid user and supply a + valid password. Once connected, all file operations will be performed + as the "forced user", no matter what username the client connected + as. This can be very useful.

    In Samba 2.0.5 and above this parameter also causes the + primary group of the forced user to be used as the primary group + for all file activity. Prior to 2.0.5 the primary group was left + as the primary group of the connecting user (this was a bug).

    See also force group

    Default: no forced user

    Example: force user = auser

    fstype (S)

    This parameter allows the administrator to + configure the string that specifies the type of filesystem a share + is using that is reported by smbd(8) when a client queries the filesystem type + for a share. The default type is NTFS for + compatibility with Windows NT but this can be changed to other + strings such as Samba or FAT + if required.

    Default: fstype = NTFS

    Example: fstype = Samba

    getwd cache (G)

    This is a tuning option. When this is enabled a + caching algorithm will be used to reduce the time taken for getwd() + calls. This can have a significant impact on performance, especially + when the wide links + parameter is set to no.

    Default: getwd cache = yes

    group (S)

    Synonym for + force group.

    guest account (G,S)

    This is a username which will be used for access + to services which are specified as + guest ok (see below). Whatever privileges this + user has will be available to any client connecting to the guest service. + Typically this user will exist in the password file, but will not + have a valid login. The user account "ftp" is often a good choice + for this parameter. If a username is specified in a given service, + the specified username overrides this one. +

    One some systems the default guest account "nobody" may not + be able to print. Use another account in this case. You should test + this by trying to log in as your guest user (perhaps by using the + su - command) and trying to print using the + system print command such as lpr(1) or + lp(1).

    This parameter does not accept % macros, because + many parts of the system require this value to be + constant for correct operation.

    Default: specified at compile time, usually "nobody"

    Example: guest account = ftp

    guest ok (S)

    If this parameter is yes for + a service, then no password is required to connect to the service. + Privileges will be those of the + guest account.

    This paramater nullifies the benifits of setting + restrict + anonymous = 2

    See the section below on + security for more information about this option. +

    Default: guest ok = no

    guest only (S)

    If this parameter is yes for + a service, then only guest connections to the service are permitted. + This parameter will have no effect if + guest ok is not set for the service.

    See the section below on + security for more information about this option. +

    Default: guest only = no

    hide dot files (S)

    This is a boolean parameter that controls whether + files starting with a dot appear as hidden files.

    Default: hide dot files = yes

    hide files (S)

    This is a list of files or directories that are not + visible but are accessible. The DOS 'hidden' attribute is applied + to any files or directories that match.

    Each entry in the list must be separated by a '/', + which allows spaces to be included in the entry. '*' + and '?' can be used to specify multiple files or directories + as in DOS wildcards.

    Each entry must be a Unix path, not a DOS path and must + not include the Unix directory separator '/'.

    Note that the case sensitivity option is applicable + in hiding files.

    Setting this parameter will affect the performance of Samba, + as it will be forced to check all files and directories for a match + as they are scanned.

    See also hide + dot files, + veto files and + case sensitive.

    Default: no file are hidden

    Example: hide files = + /.*/DesktopFolderDB/TrashFor%m/resource.frk/

    The above example is based on files that the Macintosh + SMB client (DAVE) available from + Thursby creates for internal use, and also still hides + all files beginning with a dot.

    hide local users (G)

    This parameter toggles the hiding of local UNIX + users (root, wheel, floppy, etc) from remote clients.

    Default: hide local users = no

    hide special files (S)

    This parameter prevents clients from seeing + special files such as sockets, devices and fifo's in directory + listings. +

    Default: hide special files = no

    hide unreadable (S)

    This parameter prevents clients from seeing the + existance of files that cannot be read. Defaults to off.

    Default: hide unreadable = no

    hide unwriteable files (S)

    This parameter prevents clients from seeing + the existance of files that cannot be written to. Defaults to off. + Note that unwriteable directories are shown as usual. +

    Default: hide unwriteable = no

    homedir map (G)

    Ifnis homedir + is yes, and smbd(8) is also acting + as a Win95/98 logon server then this parameter + specifies the NIS (or YP) map from which the server for the user's + home directory should be extracted. At present, only the Sun + auto.home map format is understood. The form of the map is:

    username server:/some/file/system

    and the program will extract the servername from before + the first ':'. There should probably be a better parsing system + that copes with different map formats and also Amd (another + automounter) maps.

    Note

    A working NIS client is required on + the system for this option to work.

    See also nis homedir + , domain logons + .

    Default: homedir map = <empty string>

    Example: homedir map = amd.homedir

    host msdfs (G)

    This boolean parameter is only available + if Samba has been configured and compiled with the + --with-msdfs option. If set to yes, + Samba will act as a Dfs server, and allow Dfs-aware clients + to browse Dfs trees hosted on the server.

    See also the + msdfs root share level parameter. For + more information on setting up a Dfs tree on Samba, + refer to msdfs_setup.html. +

    Default: host msdfs = no

    hostname lookups (G)

    Specifies whether samba should use (expensive) + hostname lookups or use the ip addresses instead. An example place + where hostname lookups are currently used is when checking + the hosts deny and hosts allow. +

    Default: hostname lookups = yes

    Example: hostname lookups = no

    hosts allow (S)

    A synonym for this parameter is allow + hosts.

    This parameter is a comma, space, or tab delimited + set of hosts which are permitted to access a service.

    If specified in the [global] section then it will + apply to all services, regardless of whether the individual + service has a different setting.

    You can specify the hosts by name or IP number. For + example, you could restrict access to only the hosts on a + Class C subnet with something like allow hosts = 150.203.5. + . The full syntax of the list is described in the man + page hosts_access(5). Note that this man + page may not be present on your system, so a brief description will + be given here also.

    Note that the localhost address 127.0.0.1 will always + be allowed access unless specifically denied by a + hosts deny option.

    You can also specify hosts by network/netmask pairs and + by netgroup names if your system supports netgroups. The + EXCEPT keyword can also be used to limit a + wildcard list. The following examples may provide some help:

    Example 1: allow all IPs in 150.203.*.*; except one

    hosts allow = 150.203. EXCEPT 150.203.6.66

    Example 2: allow hosts that match the given network/netmask

    hosts allow = 150.203.15.0/255.255.255.0

    Example 3: allow a couple of hosts

    hosts allow = lapland, arvidsjaur

    Example 4: allow only hosts in NIS netgroup "foonet", but + deny access from one particular host

    hosts allow = @foonet

    hosts deny = pirate

    Note

    Note that access still requires suitable user-level passwords.

    See testparm(1) for a way of testing your host access + to see if it does what you expect.

    Default: none (i.e., all hosts permitted access)

    Example: allow hosts = 150.203.5. myhost.mynet.edu.au

    hosts deny (S)

    The opposite of hosts allow + - hosts listed here are NOT permitted access to + services unless the specific services have their own lists to override + this one. Where the lists conflict, the allow + list takes precedence.

    Default: none (i.e., no hosts specifically excluded)

    Example: hosts deny = 150.203.4. badhost.mynet.edu.au

    hosts equiv (G)

    If this global parameter is a non-null string, + it specifies the name of a file to read for the names of hosts + and users who will be allowed access without specifying a password. +

    This is not be confused with + hosts allow which is about hosts + access to services and is more useful for guest services. + hosts equiv may be useful for NT clients which will + not supply passwords to Samba.

    Note

    The use of hosts equiv + can be a major security hole. This is because you are + trusting the PC to supply the correct username. It is very easy to + get a PC to supply a false username. I recommend that the + hosts equiv option be only used if you really + know what you are doing, or perhaps on a home network where you trust + your spouse and kids. And only if you really trust + them :-).

    Default: no host equivalences

    Example: hosts equiv = /etc/hosts.equiv

    include (G)

    This allows you to include one config file + inside another. The file is included literally, as though typed + in place.

    It takes the standard substitutions, except %u + , %P and %S. +

    Default: no file included

    Example: include = /usr/local/samba/lib/admin_smb.conf

    inherit acls (S)

    This parameter can be used to ensure that if default acls + exist on parent directories, they are always honored when creating a + subdirectory. The default behavior is to use the mode specified when + creating the directory. Enabling this option sets the mode to 0777, + thus guaranteeing that default directory acls are propagated. +

    Default: inherit acls = no +

    inherit permissions (S)

    The permissions on new files and directories + are normally governed by + create mask, + directory mask, + force create mode + and force + directory mode but the boolean inherit + permissions parameter overrides this.

    New directories inherit the mode of the parent directory, + including bits such as setgid.

    New files inherit their read/write bits from the parent + directory. Their execute bits continue to be determined by + map archive + , map hidden + and map system + as usual.

    Note that the setuid bit is never set via + inheritance (the code explicitly prohibits this).

    This can be particularly useful on large systems with + many users, perhaps several thousand, to allow a single [homes] + share to be used flexibly by each user.

    See also create mask + , + directory mask, + force create mode and + force directory mode + .

    Default: inherit permissions = no

    interfaces (G)

    This option allows you to override the default + network interfaces list that Samba will use for browsing, name + registration and other NBT traffic. By default Samba will query + the kernel for the list of all active interfaces and use any + interfaces except 127.0.0.1 that are broadcast capable.

    The option takes a list of interface strings. Each string + can be in any of the following forms:

    • a network interface name (such as eth0). + This may include shell-like wildcards so eth* will match + any interface starting with the substring "eth"

    • an IP address. In this case the netmask is + determined from the list of interfaces obtained from the + kernel

    • an IP/mask pair.

    • a broadcast/mask pair.

    The "mask" parameters can either be a bit length (such + as 24 for a C class network) or a full netmask in dotted + decimal form.

    The "IP" parameters above can either be a full dotted + decimal IP address or a hostname which will be looked up via + the OS's normal hostname resolution mechanisms.

    For example, the following line:

    interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0

    would configure three network interfaces corresponding + to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. + The netmasks of the latter two interfaces would be set to 255.255.255.0.

    See also bind + interfaces only.

    Default: all active interfaces except 127.0.0.1 + that are broadcast capable

    invalid users (S)

    This is a list of users that should not be allowed + to login to this service. This is really a paranoid + check to absolutely ensure an improper setting does not breach + your security.

    A name starting with a '@' is interpreted as an NIS + netgroup first (if your system supports NIS), and then as a UNIX + group if the name was not found in the NIS netgroup database.

    A name starting with '+' is interpreted only + by looking in the UNIX group database. A name starting with + '&' is interpreted only by looking in the NIS netgroup database + (this requires NIS to be working on your system). The characters + '+' and '&' may be used at the start of the name in either order + so the value +&group means check the + UNIX group database, followed by the NIS netgroup database, and + the value &+group means check the NIS + netgroup database, followed by the UNIX group database (the + same as the '@' prefix).

    The current servicename is substituted for %S. + This is useful in the [homes] section.

    See also valid users + .

    Default: no invalid users

    Example: invalid users = root fred admin @wheel

    keepalive (G)

    The value of the parameter (an integer) represents + the number of seconds between keepalive + packets. If this parameter is zero, no keepalive packets will be + sent. Keepalive packets, if sent, allow the server to tell whether + a client is still present and responding.

    Keepalives should, in general, not be needed if the socket + being used has the SO_KEEPALIVE attribute set on it (see + socket options). + Basically you should only use this option if you strike difficulties.

    Default: keepalive = 300

    Example: keepalive = 600

    kernel oplocks (G)

    For UNIXes that support kernel based + oplocks + (currently only IRIX and the Linux 2.4 kernel), this parameter + allows the use of them to be turned on or off.

    Kernel oplocks support allows Samba oplocks + to be broken whenever a local UNIX process or NFS operation + accesses a file that smbd(8) has oplocked. This allows complete + data consistency between SMB/CIFS, NFS and local file access (and is + a very cool feature :-).

    This parameter defaults to on, but is translated + to a no-op on systems that no not have the necessary kernel support. + You should never need to touch this parameter.

    See also the oplocks + and level2 oplocks + parameters.

    Default: kernel oplocks = yes

    lanman auth (G)

    This parameter determines whether or not smbd(8) will attempt to authenticate users + using the LANMAN password hash. If disabled, only clients which support NT + password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not + Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.

    Default : lanman auth = yes

    large readwrite (G)

    This parameter determines whether or not + smbd(8) supports the new 64k + streaming read and write varient SMB requests introduced with + Windows 2000. Note that due to Windows 2000 client redirector bugs + this requires Samba to be running on a 64-bit capable operating + system such as IRIX, Solaris or a Linux 2.4 kernel. Can improve + performance by 10% with Windows 2000 clients. Defaults to on. Not as + tested as some other Samba code paths.

    Default: large readwrite = yes

    ldap admin dn (G)

    The ldap admin dn + defines the Distinguished Name (DN) name used by Samba to + contact the ldap server when retreiving user account + information. The ldap admin + dn is used in conjunction with the admin dn password + stored in the private/secrets.tdb file. + See the smbpasswd(8) man page for more + information on how to accmplish this.

    ldap delete dn (G)

    This parameter specifies whether a delete + operation in the ldapsam deletes the complete entry or only the attributes + specific to Samba. +

    Default: ldap delete dn = no

    ldap filter (G)

    This parameter specifies the RFC 2254 compliant LDAP search filter. + The default is to match the login name with the uid + attribute for all entries matching the sambaAccount + objectclass. Note that this filter should only return one entry. +

    Default: ldap filter = (&(uid=%u)(objectclass=sambaAccount))

    ldap machine suffix (G)

    It specifies where machines should be added to the ldap tree.

    Default: none

    ldap passwd sync (G)

    This option is used to define whether + or not Samba should sync the LDAP password with the NT + and LM hashes for normal accounts (NOT for + workstation, server or domain trusts) on a password + change via SAMBA. +

    The ldap passwd + sync can be set to one of three values:

    • Yes = Try + to update the LDAP, NT and LM passwords and update the pwdLastSet time.

    • No = Update NT and + LM passwords and update the pwdLastSet time.

    • Only = Only update + the LDAP password and let the LDAP server do the rest.

    Default: ldap passwd sync = no

    ldap port (G)

    This parameter is only available if Samba has been + configure to include the --with-ldapsam option + at compile time.

    This option is used to control the tcp port number used to contact + the ldap server. + The default is to use the stand LDAPS port 636.

    See Also: ldap ssl

    Default : ldap port = 636 ; if ldap ssl = on

    Default : ldap port = 389 ; if ldap ssl = off

    ldap server (G)

    This parameter is only available if Samba has been + configure to include the --with-ldapsam + option at compile time.

    This parameter should contain the FQDN of the ldap directory + server which should be queried to locate user account information. +

    Default : ldap server = localhost

    ldap ssl (G)

    This option is used to define whether or not Samba should + use SSL when connecting to the ldap server + This is NOT related to + Samba's previous SSL support which was enabled by specifying the + --with-ssl option to the configure + script.

    The ldap ssl can be set to one of three values:

    • Off = Never + use SSL when querying the directory.

    • Start_tls = Use + the LDAPv3 StartTLS extended operation (RFC2830) for + communicating with the directory server.

    • On = Use SSL + on the ldaps port when contacting the ldap server. Only available when the + backwards-compatiblity --with-ldapsam option is specified + to configure. See passdb backend

    Default : ldap ssl = start_tls

    ldap suffix (G)

    Specifies where user and machine accounts are added to the + tree. Can be overriden by ldap user + suffix and ldap machine + suffix. It also used as the base dn for all ldap + searches.

    Default: none

    ldap trust ids (G)

    Normally, Samba validates each entry in the LDAP server + against getpwnam(). This allows LDAP to be used for Samba with + the unix system using NIS (for example) and also ensures that + Samba does not present accounts that do not otherwise exist. +

    This option is used to disable this functionality, and + instead to rely on the presence of the appropriate attributes + in LDAP directly, which can result in a significant performance + boost in some situations. Setting this option to yes effectivly + assumes that the local machine is running nss_ldap against the same LDAP + server.

    Default: ldap trust ids = No

    ldap user suffix (G)

    It specifies where users are added to the tree.

    Default: none

    level2 oplocks (S)

    This parameter controls whether Samba supports + level2 (read-only) oplocks on a share.

    Level2, or read-only oplocks allow Windows NT clients + that have an oplock on a file to downgrade from a read-write oplock + to a read-only oplock once a second client opens the file (instead + of releasing all oplocks on a second open, as in traditional, + exclusive oplocks). This allows all openers of the file that + support level2 oplocks to cache the file for read-ahead only (ie. + they may not cache writes or lock requests) and increases performance + for many accesses of files that are not commonly written (such as + application .EXE files).

    Once one of the clients which have a read-only oplock + writes to the file all clients are notified (no reply is needed + or waited for) and told to break their oplocks to "none" and + delete any read-ahead caches.

    It is recommended that this parameter be turned on to + speed access to shared executables.

    For more discussions on level2 oplocks see the CIFS spec.

    Currently, if kernel + oplocks are supported then level2 oplocks are + not granted (even if this parameter is set to yes). + Note also, the oplocks + parameter must be set to yes on this share in order for + this parameter to have any effect.

    See also the oplocks + and kernel oplocks + parameters.

    Default: level2 oplocks = yes

    lm announce (G)

    This parameter determines if nmbd(8) will produce Lanman announce + broadcasts that are needed by OS/2 clients in order for them to see + the Samba server in their browse list. This parameter can have three + values, yes, no, or + auto. The default is auto. + If set to no Samba will never produce these + broadcasts. If set to yes Samba will produce + Lanman announce broadcasts at a frequency set by the parameter + lm interval. If set to auto + Samba will not send Lanman announce broadcasts by default but will + listen for them. If it hears such a broadcast on the wire it will + then start sending them at a frequency set by the parameter + lm interval.

    See also lm interval.

    Default: lm announce = auto

    Example: lm announce = yes

    lm interval (G)

    If Samba is set to produce Lanman announce + broadcasts needed by OS/2 clients (see the + lm announce parameter) then this + parameter defines the frequency in seconds with which they will be + made. If this is set to zero then no Lanman announcements will be + made despite the setting of the lm announce + parameter.

    See also lm announce.

    Default: lm interval = 60

    Example: lm interval = 120

    load printers (G)

    A boolean variable that controls whether all + printers in the printcap will be loaded for browsing by default. + See the printers section for + more details.

    Default: load printers = yes

    local master (G)

    This option allows nmbd(8) to try and become a local master browser + on a subnet. If set to no then + nmbd will not attempt to become a local master browser + on a subnet and will also lose in all browsing elections. By + default this value is set to yes. Setting this value to + yes doesn't mean that Samba will become the + local master browser on a subnet, just that nmbd + will participate in elections for local master browser.

    Setting this value to no will cause nmbd never to become a local + master browser.

    Default: local master = yes

    lock directory (G)

    This option specifies the directory where lock + files will be placed. The lock files are used to implement the + max connections + option.

    Default: lock directory = ${prefix}/var/locks

    Example: lock directory = /var/run/samba/locks

    lock dir (G)

    Synonym for + lock directory. +

    locking (S)

    This controls whether or not locking will be + performed by the server in response to lock requests from the + client.

    If locking = no, all lock and unlock + requests will appear to succeed and all lock queries will report + that the file in question is available for locking.

    If locking = yes, real locking will be performed + by the server.

    This option may be useful for read-only + filesystems which may not need locking (such as + CDROM drives), although setting this parameter of no + is not really recommended even in this case.

    Be careful about disabling locking either globally or in a + specific service, as lack of locking may result in data corruption. + You should never need to set this parameter.

    Default: locking = yes

    lock spin count (G)

    This parameter controls the number of times + that smbd should attempt to gain a byte range lock on the + behalf of a client request. Experiments have shown that + Windows 2k servers do not reply with a failure if the lock + could not be immediately granted, but try a few more times + in case the lock could later be aquired. This behavior + is used to support PC database formats such as MS Access + and FoxPro. +

    Default: lock spin count = 2

    lock spin time (G)

    The time in microseconds that smbd should + pause before attempting to gain a failed lock. See + lock spin + count for more details.

    Default: lock spin time = 10

    log file (G)

    This option allows you to override the name + of the Samba log file (also known as the debug file).

    This option takes the standard substitutions, allowing + you to have separate log files for each user or machine.

    Example: log file = /usr/local/samba/var/log.%m

    log level (G)

    The value of the parameter (a astring) allows + the debug level (logging level) to be specified in the + smb.conf file. This parameter has been + extended since the 2.2.x series, now it allow to specify the debug + level for multiple debug classes. This is to give greater + flexibility in the configuration of the system.

    The default will be the log level specified on + the command line or level zero if none was specified.

    Example: log level = 3 passdb:5 auth:10 winbind:2

    logon drive (G)

    This parameter specifies the local path to + which the home directory will be connected (see + logon home) + and is only used by NT Workstations.

    Note that this option is only useful if Samba is set up as a + logon server.

    Default: logon drive = z:

    Example: logon drive = h:

    logon home (G)

    This parameter specifies the home directory + location when a Win95/98 or NT Workstation logs into a Samba PDC. + It allows you to do

    C:\> + NET USE H: /HOME +

    from a command prompt, for example.

    This option takes the standard substitutions, allowing + you to have separate logon scripts for each user or machine.

    This parameter can be used with Win9X workstations to ensure + that roaming profiles are stored in a subdirectory of the user's + home directory. This is done in the following way:

    logon home = \\%N\%U\profile

    This tells Samba to return the above string, with + substitutions made when a client requests the info, generally + in a NetUserGetInfo request. Win9X clients truncate the info to + \\server\share when a user does net use /home + but use the whole string when dealing with profiles.

    Note that in prior versions of Samba, the + logon path was returned rather than + logon home. This broke net use /home but allowed profiles outside the home directory. + The current implementation is correct, and can be used for profiles if you use + the above trick.

    This option is only useful if Samba is set up as a logon + server.

    Default: logon home = "\\%N\%U"

    Example: logon home = "\\remote_smb_server\%U"

    logon path (G)

    This parameter specifies the home directory + where roaming profiles (NTuser.dat etc files for Windows NT) are + stored. Contrary to previous versions of these manual pages, it has + nothing to do with Win 9X roaming profiles. To find out how to + handle roaming profiles for Win 9X system, see the + logon home parameter.

    This option takes the standard substitutions, allowing you + to have separate logon scripts for each user or machine. It also + specifies the directory from which the "Application Data", + (desktop, start menu, + network neighborhood, programs + and other folders, and their contents, are loaded and displayed on + your Windows NT client.

    The share and the path must be readable by the user for + the preferences and directories to be loaded onto the Windows NT + client. The share must be writeable when the user logs in for the first + time, in order that the Windows NT client can create the NTuser.dat + and other directories.

    Thereafter, the directories and any of the contents can, + if required, be made read-only. It is not advisable that the + NTuser.dat file be made read-only - rename it to NTuser.man to + achieve the desired effect (a MANdatory + profile).

    Windows clients can sometimes maintain a connection to + the [homes] share, even though there is no user logged in. + Therefore, it is vital that the logon path does not include a + reference to the homes share (i.e. setting this parameter to + \%N\%U\profile_path will cause problems).

    This option takes the standard substitutions, allowing + you to have separate logon scripts for each user or machine.

    Note that this option is only useful if Samba is set up + as a logon server.

    Default: logon path = \\%N\%U\profile

    Example: logon path = \\PROFILESERVER\PROFILE\%U

    logon script (G)

    This parameter specifies the batch file (.bat) or + NT command file (.cmd) to be downloaded and run on a machine when + a user successfully logs in. The file must contain the DOS + style CR/LF line endings. Using a DOS-style editor to create the + file is recommended.

    The script must be a relative path to the [netlogon] + service. If the [netlogon] service specifies a + path of /usr/local/samba/netlogon, and logon script = STARTUP.BAT, then + the file that will be downloaded is:

    /usr/local/samba/netlogon/STARTUP.BAT

    The contents of the batch file are entirely your choice. A + suggested command would be to add NET TIME \\SERVER /SET + /YES, to force every machine to synchronize clocks with + the same time server. Another use would be to add NET USE + U: \\SERVER\UTILS for commonly used utilities, or + NET USE Q: \\SERVER\ISO9001_QA for example.

    Note that it is particularly important not to allow write + access to the [netlogon] share, or to grant users write permission + on the batch files in a secure environment, as this would allow + the batch files to be arbitrarily modified and security to be + breached.

    This option takes the standard substitutions, allowing you + to have separate logon scripts for each user or machine.

    This option is only useful if Samba is set up as a logon + server.

    Default: no logon script defined

    Example: logon script = scripts\%U.bat

    lppause command (S)

    This parameter specifies the command to be + executed on the server host in order to stop printing or spooling + a specific print job.

    This command should be a program or script which takes + a printer name and job number to pause the print job. One way + of implementing this is by using job priorities, where jobs + having a too low priority won't be sent to the printer.

    If a %p is given then the printer name + is put in its place. A %j is replaced with + the job number (an integer). On HPUX (see printing=hpux + ), if the -p%p option is added + to the lpq command, the job will show up with the correct status, i.e. + if the job priority is lower than the set fence priority it will + have the PAUSED status, whereas if the priority is equal or higher it + will have the SPOOLED or PRINTING status.

    Note that it is good practice to include the absolute path + in the lppause command as the PATH may not be available to the server.

    See also the printing + parameter.

    Default: Currently no default value is given to + this string, unless the value of the printing + parameter is SYSV, in which case the default is :

    lp -i %p-%j -H hold

    or if the value of the printing parameter + is SOFTQ, then the default is:

    qstat -s -j%j -h

    Example for HPUX: lppause command = /usr/bin/lpalt %p-%j -p0

    lpq cache time (G)

    This controls how long lpq info will be cached + for to prevent the lpq command being called too + often. A separate cache is kept for each variation of the + lpq command used by the system, so if you use different + lpq commands for different users then they won't + share cache information.

    The cache files are stored in /tmp/lpq.xxxx + where xxxx is a hash of the lpq command in use.

    The default is 10 seconds, meaning that the cached results + of a previous identical lpq command will be used + if the cached data is less than 10 seconds old. A large value may + be advisable if your lpq command is very slow.

    A value of 0 will disable caching completely.

    See also the printing parameter.

    Default: lpq cache time = 10

    Example: lpq cache time = 30

    lpq command (S)

    This parameter specifies the command to be + executed on the server host in order to obtain lpq + -style printer status information.

    This command should be a program or script which + takes a printer name as its only parameter and outputs printer + status information.

    Currently nine styles of printer status information + are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. + This covers most UNIX systems. You control which type is expected + using the printing = option.

    Some clients (notably Windows for Workgroups) may not + correctly send the connection number for the printer they are + requesting status information about. To get around this, the + server reports on the first printer service connected to by the + client. This only happens if the connection number sent is invalid.

    If a %p is given then the printer name + is put in its place. Otherwise it is placed at the end of the + command.

    Note that it is good practice to include the absolute path + in the lpq command as the $PATH + may not be available to the server. When compiled with + the CUPS libraries, no lpq command is + needed because smbd will make a library call to obtain the + print queue listing.

    See also the printing + parameter.

    Default: depends on the setting of + printing

    Example: lpq command = /usr/bin/lpq -P%p

    lpresume command (S)

    This parameter specifies the command to be + executed on the server host in order to restart or continue + printing or spooling a specific print job.

    This command should be a program or script which takes + a printer name and job number to resume the print job. See + also the lppause command + parameter.

    If a %p is given then the printer name + is put in its place. A %j is replaced with + the job number (an integer).

    Note that it is good practice to include the absolute path + in the lpresume command as the PATH may not + be available to the server.

    See also the printing + parameter.

    Default: Currently no default value is given + to this string, unless the value of the printing + parameter is SYSV, in which case the default is :

    lp -i %p-%j -H resume

    or if the value of the printing parameter + is SOFTQ, then the default is:

    qstat -s -j%j -r

    Example for HPUX: lpresume command = /usr/bin/lpalt %p-%j -p2

    lprm command (S)

    This parameter specifies the command to be + executed on the server host in order to delete a print job.

    This command should be a program or script which takes + a printer name and job number, and deletes the print job.

    If a %p is given then the printer name + is put in its place. A %j is replaced with + the job number (an integer).

    Note that it is good practice to include the absolute + path in the lprm command as the PATH may not be + available to the server.

    See also the printing + parameter.

    Default: depends on the setting of printing +

    Example 1: lprm command = /usr/bin/lprm -P%p %j

    Example 2: lprm command = /usr/bin/cancel %p-%j

    machine password timeout (G)

    If a Samba server is a member of a Windows + NT Domain (see the security = domain) + parameter) then periodically a running + smbd(8) process will try and change the MACHINE ACCOUNT + PASSWORD stored in the TDB called private/secrets.tdb + . This parameter specifies how often this password + will be changed, in seconds. The default is one week (expressed in + seconds), the same as a Windows NT Domain member server.

    See also smbpasswd(8), and the + security = domain) parameter.

    Default: machine password timeout = 604800

    magic output (S)

    This parameter specifies the name of a file + which will contain output created by a magic script (see the + magic script + parameter below).

    Warning: If two clients use the same magic script + in the same directory the output file content + is undefined.

    Default: magic output = <magic script name>.out

    Example: magic output = myfile.txt

    magic script (S)

    This parameter specifies the name of a file which, + if opened, will be executed by the server when the file is closed. + This allows a UNIX script to be sent to the Samba host and + executed on behalf of the connected user.

    Scripts executed in this way will be deleted upon + completion assuming that the user has the appropriate level + of privilege and the file permissions allow the deletion.

    If the script generates output, output will be sent to + the file specified by the + magic output parameter (see above).

    Note that some shells are unable to interpret scripts + containing CR/LF instead of CR as + the end-of-line marker. Magic scripts must be executable + as is on the host, which for some hosts and + some shells will require filtering at the DOS end.

    Magic scripts are EXPERIMENTAL and + should NOT be relied upon.

    Default: None. Magic scripts disabled.

    Example: magic script = user.csh

    mangle case (S)

    See the section on NAME MANGLING

    Default: mangle case = no

    mangled map (S)

    This is for those who want to directly map UNIX + file names which cannot be represented on Windows/DOS. The mangling + of names is not always what is needed. In particular you may have + documents with file extensions that differ between DOS and UNIX. + For example, under UNIX it is common to use .html + for HTML files, whereas under Windows/DOS .htm + is more commonly used.

    So to map html to htm + you would use:

    mangled map = (*.html *.htm)

    One very useful case is to remove the annoying ;1 + off the ends of filenames on some CDROMs (only visible + under some UNIXes). To do this use a map of (*;1 *;).

    Default: no mangled map

    Example: mangled map = (*;1 *;)

    mangled names (S)

    This controls whether non-DOS names under UNIX + should be mapped to DOS-compatible names ("mangled") and made visible, + or whether non-DOS names should simply be ignored.

    See the section on NAME MANGLING for + details on how to control the mangling process.

    If mangling is used then the mangling algorithm is as follows:

    • The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters - of the mangled name.

    • A tilde "~" is appended to the first part of the mangled + of the mangled name.

    • A tilde "~" is appended to the first part of the mangled name, followed by a two-character unique sequence, based on the original root name (i.e., the original filename minus its final extension). The final extension is included in the hash calculation only if it contains any upper case characters or is longer than three - characters.

      Note that the character to use may be specified using - the mangling char - option, if you don't like '~'.

    • The first three alphanumeric characters of the final + characters.

      Note that the character to use may be specified using + the mangling char + option, if you don't like '~'.

    • The first three alphanumeric characters of the final extension are preserved, forced to upper case and appear as the extension of the mangled name. The final extension is defined as that part of the original filename after the rightmost dot. If there are no dots in the filename, the mangled name will have no extension (except - in the case of "hidden files" - see below).

    • Files whose UNIX name begins with a dot will be + in the case of "hidden files" - see below).

    • Files whose UNIX name begins with a dot will be presented as DOS hidden files. The mangled name will be created as - for other filenames, but with the leading dot removed and "___" as + for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that's three - underscores).

    The two-digit hash value consists of upper case - alphanumeric characters.

    This algorithm can cause name collisions only if files - in a directory share the same first five alphanumeric characters. - The probability of such a clash is 1/1300.

    The name mangling (if enabled) allows a file to be - copied between UNIX directories from Windows/DOS while retaining - the long UNIX filename. UNIX files can be renamed to a new extension - from Windows/DOS and will retain the same basename. Mangled names - do not change between sessions.

    Default: mangled names = yes

    >mangling method (G)

    controls the algorithm used for the generating - the mangled names. Can take two different values, "hash" and - "hash2". "hash" is the default and is the algorithm that has been - used in Samba for many years. "hash2" is a newer and considered - a better algorithm (generates less collisions) in the names. - However, many Win32 applications store the mangled names and so - changing to the new algorithm must not be done - lightly as these applications may break unless reinstalled.

    Default: mangling method = hash2

    Example: mangling method = hash

    >mangle prefix (G)

    controls the number of prefix - characters from the original name used when generating - the mangled names. A larger value will give a weaker - hash and therefore more name collisions. The minimum - value is 1 and the maximum value is 6.

    Default: mangle prefix = 1

    Example: mangle prefix = 4

    >mangled stack (G)

    This parameter controls the number of mangled names - that should be cached in the Samba server smbd(8).

    This stack is a list of recently mangled base names - (extensions are only maintained if they are longer than 3 characters - or contains upper case characters).

    The larger this value, the more likely it is that mangled - names can be successfully converted to correct long UNIX names. - However, large stack sizes will slow most directory accesses. Smaller - stacks save memory in the server (each stack element costs 256 bytes). -

    It is not possible to absolutely guarantee correct long - filenames, so be prepared for some surprises!

    Default: mangled stack = 50

    Example: mangled stack = 100

    >mangling char (S)

    This controls what character is used as - the magic character in name mangling. The default is a '~' - but this may interfere with some software. Use this option to set - it to whatever you prefer.

    Default: mangling char = ~

    Example: mangling char = ^

    >map archive (S)

    This controls whether the DOS archive attribute - should be mapped to the UNIX owner execute bit. The DOS archive bit - is set when a file has been modified since its last backup. One - motivation for this option it to keep Samba/your PC from making - any file it touches from becoming executable under UNIX. This can - be quite annoying for shared source code, documents, etc...

    Note that this requires the create mask - parameter to be set such that owner execute bit is not masked out - (i.e. it must include 100). See the parameter create mask for details.

    Default: map archive = yes

    >map hidden (S)

    This controls whether DOS style hidden files - should be mapped to the UNIX world execute bit.

    Note that this requires the create mask - to be set such that the world execute bit is not masked out (i.e. - it must include 001). See the parameter create mask for details.

    Default: map hidden = no

    >map system (S)

    This controls whether DOS style system files - should be mapped to the UNIX group execute bit.

    Note that this requires the create mask - to be set such that the group execute bit is not masked out (i.e. - it must include 010). See the parameter create mask for details.

    Default: map system = no

    >map to guest (G)

    This parameter is only useful in security modes other than security = share - - i.e. user, server, - and domain.

    This parameter can take three different values, which tell - smbd(8) what to do with user - login requests that don't match a valid UNIX user in some way.

    The three settings are :

    • Never - Means user login - requests with an invalid password are rejected. This is the - default.

    • Bad User - Means user - logins with an invalid password are rejected, unless the username - does not exist, in which case it is treated as a guest login and - mapped into the guest account.

    • Bad Password - Means user logins - with an invalid password are treated as a guest login and mapped - into the guest account. Note that - this can cause problems as it means that any user incorrectly typing - their password will be silently logged on as "guest" - and - will not know the reason they cannot access files they think - they should - there will have been no message given to them - that they got their password wrong. Helpdesk services will - hate you if you set the map to - guest parameter this way :-).

    Note that this parameter is needed to set up "Guest" - share services when using security modes other than - share. This is because in these modes the name of the resource being - requested is not sent to the server until after - the server has successfully authenticated the client so the server - cannot make authentication decisions at the correct time (connection - to the share) for "Guest" shares.

    For people familiar with the older Samba releases, this - parameter maps to the old compile-time setting of the GUEST_SESSSETUP value in local.h.

    Default: map to guest = Never

    Example: map to guest = Bad User

    >max connections (S)

    This option allows the number of simultaneous - connections to a service to be limited. If max connections - is greater than 0 then connections will be refused if - this number of connections to the service are already open. A value - of zero mean an unlimited number of connections may be made.

    Record lock files are used to implement this feature. The - lock files will be stored in the directory specified by the lock directory - option.

    Default: max connections = 0

    Example: max connections = 10

    >max disk size (G)

    This option allows you to put an upper limit - on the apparent size of disks. If you set this option to 100 - then all shares will appear to be not larger than 100 MB in - size.

    Note that this option does not limit the amount of - data you can put on the disk. In the above case you could still - store much more than 100 MB on the disk, but if a client ever asks - for the amount of free disk space or the total disk size then the - result will be bounded by the amount specified in max - disk size.

    This option is primarily useful to work around bugs - in some pieces of software that can't handle very large disks, - particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

    >max log size (G)

    This option (an integer in kilobytes) specifies - the max size the log file should grow to. Samba periodically checks - the size and if it is exceeded it will rename the file, adding - a .old extension.

    A size of 0 means no limit.

    Default: max log size = 5000

    Example: max log size = 1000

    >max mux (G)

    This option controls the maximum number of - outstanding simultaneous SMB operations that Samba tells the client - it will allow. You should never need to set this parameter.

    Default: max mux = 50

    >max open files (G)

    This parameter limits the maximum number of - open files that one smbd(8) file - serving process may have open for a client at any one time. The - default for this parameter is set very high (10,000) as Samba uses - only one bit per unopened file.

    The limit of the number of open files is usually set - by the UNIX per-process file descriptor limit rather than - this parameter so you should never need to touch this parameter.

    Default: max open files = 10000

    >max print jobs (S)

    This parameter limits the maximum number of - jobs allowable in a Samba printer queue at any given moment. - If this number is exceeded, smbd(8) will remote "Out of Space" to the client. - See all total - print jobs. -

    Default: max print jobs = 1000

    Example: max print jobs = 5000

    >max protocol (G)

    The value of the parameter (a string) is the highest - protocol level that will be supported by the server.

    Possible values are :

    • CORE: Earliest version. No - concept of user names.

    • COREPLUS: Slight improvements on - CORE for efficiency.

    • LANMAN1: First modern version of the protocol. Long filename - support.

    • LANMAN2: Updates to Lanman1 protocol. -

    • NT1: Current up to date version of - the protocol. Used by Windows NT. Known as CIFS.

    Normally this option should not be set as the automatic - negotiation phase in the SMB protocol takes care of choosing - the appropriate protocol.

    See also min - protocol

    Default: max protocol = NT1

    Example: max protocol = LANMAN1

    >max smbd processes (G)

    This parameter limits the maximum number of - smbd(8) - processes concurrently running on a system and is intended - as a stopgap to prevent degrading service to clients in the event - that the server has insufficient resources to handle more than this - number of connections. Remember that under normal operating - conditions, each user will have an smbd(8) associated with him or her - to handle connections to all shares from a given host. -

    Default: max smbd processes = 0 ## no limit

    Example: max smbd processes = 1000

    >max ttl (G)

    This option tells nmbd(8) - what the default 'time to live' of NetBIOS names should be (in seconds) - when nmbd is requesting a name using either a - broadcast packet or from a WINS server. You should never need to - change this parameter. The default is 3 days.

    Default: max ttl = 259200

    >max wins ttl (G)

    This option tells smbd(8) when acting as a WINS server ( wins support = yes) what the maximum - 'time to live' of NetBIOS names that nmbd - will grant will be (in seconds). You should never need to change this - parameter. The default is 6 days (518400 seconds).

    See also the min - wins ttl parameter.

    Default: max wins ttl = 518400

    >max xmit (G)

    This option controls the maximum packet size - that will be negotiated by Samba. The default is 65535, which - is the maximum. In some cases you may find you get better performance - with a smaller value. A value below 2048 is likely to cause problems. -

    Default: max xmit = 65535

    Example: max xmit = 8192

    >message command (G)

    This specifies what command to run when the - server receives a WinPopup style message.

    This would normally be a command that would - deliver the message somehow. How this is to be done is - up to your imagination.

    An example is:

    message command = csh -c 'xedit %s;rm %s' & -

    This delivers the message using xedit, then - removes it afterwards. NOTE THAT IT IS VERY IMPORTANT - THAT THIS COMMAND RETURN IMMEDIATELY. That's why I - have the '&' on the end. If it doesn't return immediately then - your PCs may freeze when sending messages (they should recover - after 30 seconds, hopefully).

    All messages are delivered as the global guest user. - The command takes the standard substitutions, although %u won't work (%U may be better - in this case).

    Apart from the standard substitutions, some additional - ones apply. In particular:

    • %s = the filename containing - the message.

    • %t = the destination that - the message was sent to (probably the server name).

    • %f = who the message - is from.

    You could make this command send mail, or whatever else - takes your fancy. Please let us know of any really interesting - ideas you have.

    Here's a way of sending the messages as mail to root:

    message command = /bin/mail -s 'message from %f on - %m' root < %s; rm %s

    If you don't have a message command then the message - won't be delivered and Samba will tell the sender there was - an error. Unfortunately WfWg totally ignores the error code - and carries on regardless, saying that the message was delivered. -

    If you want to silently delete it then try:

    message command = rm %s

    Default: no message command

    Example: message command = csh -c 'xedit %s; - rm %s' &

    >min passwd length (G)

    Synonym for min password length.

    >min password length (G)

    This option sets the minimum length in characters - of a plaintext password that smbd will accept when performing - UNIX password changing.

    See also unix - password sync, passwd program and passwd chat debug - .

    Default: min password length = 5

    >min print space (S)

    This sets the minimum amount of free disk - space that must be available before a user will be able to spool - a print job. It is specified in kilobytes. The default is 0, which - means a user can always spool a print job.

    See also the printing - parameter.

    Default: min print space = 0

    Example: min print space = 2000

    >min protocol (G)

    The value of the parameter (a string) is the - lowest SMB protocol dialect than Samba will support. Please refer - to the max protocol - parameter for a list of valid protocol names and a brief description - of each. You may also wish to refer to the C source code in - source/smbd/negprot.c for a listing of known protocol - dialects supported by clients.

    If you are viewing this parameter as a security measure, you should - also refer to the lanman - auth parameter. Otherwise, you should never need - to change this parameter.

    Default : min protocol = CORE

    Example : min protocol = NT1 # disable DOS - clients

    >min wins ttl (G)

    This option tells nmbd(8) - when acting as a WINS server ( wins support = yes) what the minimum 'time to live' - of NetBIOS names that nmbd will grant will be (in - seconds). You should never need to change this parameter. The default - is 6 hours (21600 seconds).

    Default: min wins ttl = 21600

    >msdfs proxy (S)

    This parameter indicates that the share is a - stand-in for another CIFS share whose location is specified by - the value of the parameter. When clients attempt to connect to - this share, they are redirected to the proxied share using - the SMB-Dfs protocol.

    Only Dfs roots can act as proxy shares. Take a look at the - msdfs root - and - host msdfs - options to find out how to set up a Dfs root share.

    Example: msdfs proxy = \\\\otherserver\\someshare

    >msdfs root (S)

    This boolean parameter is only available if - Samba is configured and compiled with the --with-msdfs option. If set to yes, - Samba treats the share as a Dfs root and allows clients to browse - the distributed file system tree rooted at the share directory. - Dfs links are specified in the share directory by symbolic - links of the form msdfs:serverA\\shareA,serverB\\shareB - and so on. For more information on setting up a Dfs tree - on Samba, refer to "Hosting a Microsoft - Distributed File System tree on Samba" document.

    See also host msdfs -

    Default: msdfs root = no

    >name cache timeout (G)

    Specifies the number of seconds it takes before - entries in samba's hostname resolve cache time out. If - the timeout is set to 0. the caching is disabled. -

    Default: name cache timeout = 660

    Example: name cache timeout = 0

    >name resolve order (G)

    This option is used by the programs in the Samba - suite to determine what naming services to use and in what order - to resolve host names to IP addresses. The option takes a space - separated string of name resolution options.

    The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows :

    • lmhosts : Lookup an IP - address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see the lmhosts(5) for details) then - any name type matches for lookup.

    • host : Do a standard host - name to IP address resolution, using the system /etc/hosts - , NIS, or DNS lookups. This method of name resolution - is operating system depended for instance on IRIX or Solaris this - may be controlled by the /etc/nsswitch.conf - file. Note that this method is only used if the NetBIOS name - type being queried is the 0x20 (server) name type, otherwise - it is ignored.

    • wins : Query a name with - the IP address listed in the wins server parameter. If no WINS server has - been specified this method will be ignored.

    • bcast : Do a broadcast on - each of the known local interfaces listed in the interfaces - parameter. This is the least reliable of the name resolution - methods as it depends on the target host being on a locally - connected subnet.

    Default: name resolve order = lmhosts host wins bcast -

    Example: name resolve order = lmhosts bcast host -

    This will cause the local lmhosts file to be examined - first, followed by a broadcast attempt, followed by a normal - system hostname lookup.

    >netbios aliases (G)

    This is a list of NetBIOS names that nmbd(8) will advertise as additional - names by which the Samba server is known. This allows one machine - to appear in browse lists under multiple names. If a machine is - acting as a browse server or logon server none - of these names will be advertised as either browse server or logon - servers, only the primary name of the machine will be advertised - with these capabilities.

    See also netbios - name.

    Default: empty string (no additional names)

    Example: netbios aliases = TEST TEST1 TEST2

    >netbios name (G)

    This sets the NetBIOS name by which a Samba - server is known. By default it is the same as the first component - of the host's DNS name. If a machine is a browse server or - logon server this name (or the first component - of the hosts DNS name) will be the name that these services are - advertised under.

    See also netbios - aliases.

    Default: machine DNS name

    Example: netbios name = MYNAME

    >netbios scope (G)

    This sets the NetBIOS scope that Samba will - operate under. This should not be set unless every machine - on your LAN also sets this value.

    >nis homedir (G)

    Get the home share server from a NIS map. For - UNIX systems that use an automounter, the user's home directory - will often be mounted on a workstation on demand from a remote - server.

    When the Samba logon server is not the actual home directory - server, but is mounting the home directories via NFS then two - network hops would be required to access the users home directory - if the logon server told the client to use itself as the SMB server - for home directories (one over SMB and one over NFS). This can - be very slow.

    This option allows Samba to return the home share as - being on a different server to the logon server and as - long as a Samba daemon is running on the home directory server, - it will be mounted on the Samba client directly from the directory - server. When Samba is returning the home share to the client, it - will consult the NIS map specified in homedir map and return the server - listed there.

    Note that for this option to work there must be a working - NIS system and the Samba server with this option must also - be a logon server.

    Default: nis homedir = no

    >non unix account range (G)

    The non unix account range parameter specifies - the range of 'user ids' that are allocated by the various 'non unix - account' passdb backends. These backends allow - the storage of passwords for users who don't exist in /etc/passwd. - This is most often used for machine account creation. - This range of ids should have no existing local or NIS users within - it as strange conflicts can occur otherwise.

    These userids never appear on the system and Samba will never - 'become' these users. They are used only to ensure that the algorithmic - RID mapping does not conflict with normal users. -

    Default: non unix account range = <empty string> -

    Example: non unix account range = 10000-20000

    >nt acl support (S)

    This boolean parameter controls whether - smbd(8) will attempt to map - UNIX permissions into Windows NT access control lists. - This parameter was formally a global parameter in releases - prior to 2.2.2.

    Default: nt acl support = yes

    >nt pipe support (G)

    This boolean parameter controls whether - smbd(8) will allow Windows NT - clients to connect to the NT SMB specific IPC$ - pipes. This is a developer debugging option and can be left - alone.

    Default: nt pipe support = yes

    >nt status support (G)

    This boolean parameter controls whether smbd(8) will negotiate NT specific status - support with Windows NT/2k/XP clients. This is a developer - debugging option and should be left alone. - If this option is set to no then Samba offers - exactly the same DOS error codes that versions prior to Samba 2.2.3 - reported.

    You should not need to ever disable this parameter.

    Default: nt status support = yes

    >null passwords (G)

    Allow or disallow client access to accounts - that have null passwords.

    See also smbpasswd(5).

    Default: null passwords = no

    >obey pam restrictions (G)

    When Samba 2.2 is configured to enable PAM support - (i.e. --with-pam), this parameter will control whether or not Samba - should obey PAM's account and session management directives. The - default behavior is to use PAM for clear text authentication only - and to ignore any account or session management. Note that Samba - always ignores PAM for authentication in the case of encrypt passwords = yes - . The reason is that PAM modules cannot support the challenge/response - authentication mechanism needed in the presence of SMB password encryption. -

    Default: obey pam restrictions = no

    >only user (S)

    This is a boolean option that controls whether - connections with usernames not in the user - list will be allowed. By default this option is disabled so that a - client can supply a username to be used by the server. Enabling - this parameter will force the server to only use the login - names from the user list and is only really - useful in share level - security.

    Note that this also means Samba won't try to deduce - usernames from the service name. This can be annoying for - the [homes] section. To get around this you could use user = - %S which means your user list - will be just the service name, which for home directories is the - name of the user.

    See also the user - parameter.

    Default: only user = no

    >only guest (S)

    A synonym for guest only.

    >oplock break wait time (G)

    This is a tuning parameter added due to bugs in - both Windows 9x and WinNT. If Samba responds to a client too - quickly when that client issues an SMB that can cause an oplock - break request, then the network client can fail and not respond - to the break request. This tuning parameter (which is set in milliseconds) - is the amount of time Samba will wait before sending an oplock break - request to such (broken) clients.

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ - AND UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock break wait time = 0

    >oplock contention limit (S)

    This is a very advanced - smbd(8) tuning option to - improve the efficiency of the granting of oplocks under multiple - client contention for the same file.

    In brief it specifies a number, which causes smbd(8)not to grant an oplock even when requested - if the approximate number of clients contending for an oplock on the same file goes over this - limit. This causes smbd to behave in a similar - way to Windows NT.

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ - AND UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock contention limit = 2

    >oplocks (S)

    This boolean option tells smbd whether to - issue oplocks (opportunistic locks) to file open requests on this - share. The oplock code can dramatically (approx. 30% or more) improve - the speed of access to files on Samba servers. It allows the clients - to aggressively cache files locally and you may want to disable this - option for unreliable network environments (it is turned on by - default in Windows NT Servers). For more information see the file - Speed.txt in the Samba docs/ - directory.

    Oplocks may be selectively turned off on certain files with a - share. See the veto oplock files parameter. On some systems - oplocks are recognized by the underlying operating system. This - allows data synchronization between all access to oplocked files, - whether it be via Samba or NFS or a local UNIX process. See the - kernel oplocks parameter for details.

    See also the kernel - oplocks and level2 oplocks parameters.

    Default: oplocks = yes

    >ntlm auth (G)

    This parameter determines - whether or not smbd(8) will - attempt to authenticate users using the NTLM password hash. - If disabled, only the lanman password hashes will be used. -

    Please note that at least this option or lanman auth should - be enabled in order to be able to log in. -

    Default : ntlm auth = yes

    >os level (G)

    This integer value controls what level Samba - advertises itself as for browse elections. The value of this - parameter determines whether nmbd(8) - has a chance of becoming a local master browser for the WORKGROUP in the local broadcast area.

    Note :By default, Samba will win - a local master browsing election over all Microsoft operating - systems except a Windows NT 4.0/2000 Domain Controller. This - means that a misconfigured Samba host can effectively isolate - a subnet for browsing purposes. See BROWSING.txt - in the Samba docs/ directory - for details.

    Default: os level = 20

    Example: os level = 65

    >os2 driver map (G)

    The parameter is used to define the absolute - path to a file containing a mapping of Windows NT printer driver - names to OS/2 printer driver names. The format is:

    <nt driver name> = <os2 driver - name>.<device name>

    For example, a valid entry using the HP LaserJet 5 - printer driver would appear as HP LaserJet 5L = LASERJET.HP - LaserJet 5L.

    The need for the file is due to the printer driver namespace - problem described in the Samba - Printing HOWTO. For more details on OS/2 clients, please - refer to the OS2-Client-HOWTO containing in the Samba documentation.

    Default: os2 driver map = <empty string> -

    >pam password change (G)

    With the addition of better PAM support in Samba 2.2, - this parameter, it is possible to use PAM's password change control - flag for Samba. If enabled, then PAM will be used for password - changes when requested by an SMB client instead of the program listed in - passwd program. - It should be possible to enable this without changing your - passwd chat - parameter for most setups. -

    Default: pam password change = no

    >panic action (G)

    This is a Samba developer option that allows a - system command to be called when either smbd(8) or smbd(8) crashes. This is usually used to - draw attention to the fact that a problem occurred.

    Default: panic action = <empty string>

    Example: panic action = "/bin/sleep 90000"

    >paranoid server security (G)

    Some version of NT 4.x allow non-guest - users with a bad passowrd. When this option is enabled, samba will not - use a broken NT 4.x server as password server, but instead complain - to the logs and exit. -

    Disabling this option prevents Samba from making - this check, which involves deliberatly attempting a - bad logon to the remote server.

    Default: paranoid server security = yes

    >passdb backend (G)

    This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both - smbpasswd and tdbsam to be used without a recompile. - Multiple backends can be specified, separated by spaces. The backends will be searched in the order they are specified. New users are always added to the first backend specified. - Experimental backends must still be selected - (eg --with-tdbsam) at configure time. -

    This parameter is in two parts, the backend's name, and a 'location' - string that has meaning only to that particular backed. These are separated - by a : character.

    Available backends can include: -

    • smbpasswd - The default smbpasswd - backend. Takes a path to the smbpasswd file as an optional argument.

    • smbpasswd_nua - The smbpasswd - backend, but with support for 'not unix accounts'. - Takes a path to the smbpasswd file as an optional argument.

      See also non unix account range

    • tdbsam - The TDB based password storage - backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb - in the private dir directory.

    • tdbsam_nua - The TDB based password storage - backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb - in the private dir directory.

      See also non unix account range

    • ldapsam - The LDAP based passdb - backend. Takes an LDAP URL as an optional argument (defaults to - ldap://localhost)

    • ldapsam_nua - The LDAP based passdb - backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to - ldap://localhost)

      Note: In this module, any account without a matching POSIX account is regarded - as 'non unix'.

      See also non unix account - range

      LDAP connections should be secured where - possible. This may be done using either - Start-TLS (see ldap ssl) or by - specifying ldaps:// in - the URL argument. -

    • nisplussam - The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with sun NIS+ servers.

    • plugin - Allows Samba to load an - arbitary passdb backend from the .so specified as a compulsary argument. -

      Any characters after the (optional) second : are passed to the plugin - for its own processing

    • unixsam - Allows samba to map all (other) available unix users

      This backend uses the standard unix database for retrieving users. Users included - in this pdb are NOT listed in samba user listings and users included in this pdb won't be - able to login. The use of this backend is to always be able to display the owner of a file - on the samba server - even when the user doesn't have a 'real' samba account in one of the - other passdb backends. -

      This backend should always be the last backend listed, since it contains all users in - the unix passdb and might 'override' mappings if specified earlier. It's meant to only return - accounts for users that aren't covered by the previous backends.

    -

    Default: passdb backend = smbpasswd unixsam

    Example: passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd unixsam

    Example: passdb backend = ldapsam_nua:ldaps://ldap.example.com unixsam

    Example: passdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb

    >passwd chat (G)

    This string controls the "chat" - conversation that takes places between smbd(8) and the local password changing - program to change the user's password. The string describes a - sequence of response-receive pairs that smbd(8) uses to determine what to send to the - passwd program - and what to expect back. If the expected output is not - received then the password is not changed.

    This chat sequence is often quite site specific, depending - on what local methods are used for password control (such as NIS - etc).

    Note that this parameter only is only used if the unix - password sync parameter is set to yes. This - sequence is then called AS ROOT when the SMB password - in the smbpasswd file is being changed, without access to the old - password cleartext. This means that root must be able to reset the user's password - without knowing the text of the previous password. In the presence of NIS/YP, - this means that the passwd program must be - executed on the NIS master. -

    The string can contain the macro %n which is substituted - for the new password. The chat sequence can also contain the standard - macros \\n, \\r, \\t and \\s to give line-feed, - carriage-return, tab and space. The chat sequence string can also contain - a '*' which matches any sequence of characters. - Double quotes can be used to collect strings with spaces - in them into a single string.

    If the send string in any part of the chat sequence - is a full stop ".", then no string is sent. Similarly, - if the expect string is a full stop then no string is expected.

    If the pam - password change parameter is set to yes, the chat pairs - may be matched in any order, and success is determined by the PAM result, - not any particular output. The \n macro is ignored for PAM conversions. -

    See also unix password - sync, passwd program , passwd chat debug and pam password change.

    Default: passwd chat = *new*password* %n\\n - *new*password* %n\\n *changed*

    Example: passwd chat = "*Enter OLD password*" %o\\n - "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password - changed*"

    >passwd chat debug (G)

    This boolean specifies if the passwd chat script - parameter is run in debug mode. In this mode the - strings passed to and received from the passwd chat are printed - in the smbd(8) log with a - debug level - of 100. This is a dangerous option as it will allow plaintext passwords - to be seen in the smbd log. It is available to help - Samba admins debug their passwd chat scripts - when calling the passwd program and should - be turned off after this has been done. This option has no effect if the - pam password change - paramter is set. This parameter is off by default.

    See also passwd chat - , pam password change - , passwd program - .

    Default: passwd chat debug = no

    >passwd program (G)

    The name of a program that can be used to set - UNIX user passwords. Any occurrences of %u - will be replaced with the user name. The user name is checked for - existence before calling the password changing program.

    Also note that many passwd programs insist in reasonable - passwords, such as a minimum length, or the inclusion - of mixed case chars and digits. This can pose a problem as some clients - (such as Windows for Workgroups) uppercase the password before sending - it.

    Note that if the unix - password sync parameter is set to yes - then this program is called AS ROOT - before the SMB password in the smbpasswd(5) - file is changed. If this UNIX password change fails, then - smbd will fail to change the SMB password also - (this is by design).

    If the unix password sync parameter - is set this parameter MUST USE ABSOLUTE PATHS - for ALL programs called, and must be examined - for security implications. Note that by default unix - password sync is set to no.

    See also unix - password sync.

    Default: passwd program = /bin/passwd

    Example: passwd program = /sbin/npasswd %u -

    >password level (G)

    Some client/server combinations have difficulty - with mixed-case passwords. One offending client is Windows for - Workgroups, which for some reason forces passwords to upper - case when using the LANMAN1 protocol, but leaves them alone when - using COREPLUS! Another problem child is the Windows 95/98 - family of operating systems. These clients upper case clear - text passwords even when NT LM 0.12 selected by the protocol - negotiation request/response.

    This parameter defines the maximum number of characters - that may be upper case in passwords.

    For example, say the password given was "FRED". If password level is set to 1, the following combinations - would be tried if "FRED" failed:

    "Fred", "fred", "fRed", "frEd","freD"

    If password level was set to 2, - the following combinations would also be tried:

    "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..

    And so on.

    The higher value this parameter is set to the more likely - it is that a mixed case password will be matched against a single - case password. However, you should be aware that use of this - parameter reduces security and increases the time taken to - process a new connection.

    A value of zero will cause only two attempts to be - made - the password as is and the password in all-lower case.

    Default: password level = 0

    Example: password level = 4

    >password server (G)

    By specifying the name of another SMB server (such - as a WinNT box) with this option, and using security = domain - or security = server you can get Samba - to do all its username/password validation via a remote server.

    This option sets the name of the password server to use. - It must be a NetBIOS name, so if the machine's NetBIOS name is - different from its Internet name then you may have to add its NetBIOS - name to the lmhosts file which is stored in the same directory - as the smb.conf file.

    The name of the password server is looked up using the - parameter name - resolve order and so may resolved - by any method and order described in that parameter.

    The password server must be a machine capable of using - the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in - user level security mode.

    Using a password server - means your UNIX box (running Samba) is only as secure as your - password server. DO NOT CHOOSE A PASSWORD SERVER THAT - YOU DON'T COMPLETELY TRUST.

    Never point a Samba server at itself for password - serving. This will cause a loop and could lock up your Samba - server!

    The name of the password server takes the standard - substitutions, but probably the only useful one is %m - , which means the Samba server will use the incoming - client as the password server. If you use this then you better - trust your clients, and you had better restrict them with hosts allow!

    If the security parameter is set to - domain, then the list of machines in this - option must be a list of Primary or Backup Domain controllers for the - Domain or the character '*', as the Samba server is effectively - in that domain, and will use cryptographically authenticated RPC calls - to authenticate the user logging on. The advantage of using security = domain is that if you list several hosts in the - password server option then smbd - will try each in turn till it finds one that responds. This - is useful in case your primary server goes down.

    If the password server option is set - to the character '*', then Samba will attempt to auto-locate the - Primary or Backup Domain controllers to authenticate against by - doing a query for the name WORKGROUP<1C> - and then contacting each server returned in the list of IP - addresses from the name resolution source.

    If the list of servers contains both names and the '*' - character, the list is treated as a list of preferred - domain controllers, but an auto lookup of all remaining DC's - will be added to the list as well. Samba will not attempt to optimize - this list by locating the closest DC.

    If the security parameter is - set to server, then there are different - restrictions that security = domain doesn't - suffer from:

    • You may list several password servers in - the password server parameter, however if an - smbd makes a connection to a password server, - and then the password server fails, no more users will be able - to be authenticated from this smbd. This is a - restriction of the SMB/CIFS protocol when in security = server - mode and cannot be fixed in Samba.

    • If you are using a Windows NT server as your - password server then you will have to ensure that your users - are able to login from the Samba server, as when in security = server mode the network logon will appear to - come from there rather than from the users workstation.

    See also the security - parameter.

    Default: password server = <empty string> -

    Example: password server = NT-PDC, NT-BDC1, NT-BDC2, * -

    Example: password server = *

    >path (S)

    This parameter specifies a directory to which - the user of the service is to be given access. In the case of - printable services, this is where print data will spool prior to - being submitted to the host for printing.

    For a printable service offering guest access, the service - should be readonly and the path should be world-writeable and - have the sticky bit set. This is not mandatory of course, but - you probably won't get the results you expect if you do - otherwise.

    Any occurrences of %u in the path - will be replaced with the UNIX username that the client is using - on this connection. Any occurrences of %m - will be replaced by the NetBIOS name of the machine they are - connecting from. These replacements are very useful for setting - up pseudo home directories for users.

    Note that this path will be based on root dir if one was specified.

    Default: none

    Example: path = /home/fred

    >pid directory (G)

    This option specifies the directory where pid - files will be placed.

    Default: pid directory = ${prefix}/var/locks

    Example: pid directory = /var/run/ -

    >posix locking (S)

    The smbd(8) - daemon maintains an database of file locks obtained by SMB clients. - The default behavior is to map this internal database to POSIX - locks. This means that file locks obtained by SMB clients are - consistent with those seen by POSIX compliant applications accessing - the files via a non-SMB method (e.g. NFS or local file access). - You should never need to disable this parameter.

    Default: posix locking = yes

    >postexec (S)

    This option specifies a command to be run - whenever the service is disconnected. It takes the usual - substitutions. The command may be run as the root on some - systems.

    An interesting example may be to unmount server - resources:

    postexec = /etc/umount /cdrom

    See also preexec - .

    Default: none (no command executed) -

    Example: postexec = echo \"%u disconnected from %S - from %m (%I)\" >> /tmp/log

    >preexec (S)

    This option specifies a command to be run whenever - the service is connected to. It takes the usual substitutions.

    An interesting example is to send the users a welcome - message every time they log in. Maybe a message of the day? Here - is an example:

    preexec = csh -c 'echo \"Welcome to %S!\" | - /usr/local/samba/bin/smbclient -M %m -I %I' &

    Of course, this could get annoying after a while :-)

    See also preexec close - and postexec - .

    Default: none (no command executed)

    Example: preexec = echo \"%u connected to %S from %m - (%I)\" >> /tmp/log

    >preexec close (S)

    This boolean option controls whether a non-zero - return code from preexec - should close the service being connected to.

    Default: preexec close = no

    >preferred master (G)

    This boolean parameter controls if nmbd(8) is a preferred master browser - for its workgroup.

    If this is set to yes, on startup, nmbd - will force an election, and it will have a slight advantage in - winning the election. It is recommended that this parameter is - used in conjunction with domain master = yes, so that nmbd can guarantee becoming a domain master.

    Use this option with caution, because if there are several - hosts (whether Samba servers, Windows 95 or NT) that are preferred - master browsers on the same subnet, they will each periodically - and continuously attempt to become the local master browser. - This will result in unnecessary broadcast traffic and reduced browsing - capabilities.

    See also os level - .

    Default: preferred master = auto

    >prefered master (G)

    Synonym for preferred master for people who cannot spell :-).

    >preload (G)

    This is a list of services that you want to be - automatically added to the browse lists. This is most useful - for homes and printers services that would otherwise not be - visible.

    Note that if you just want all printers in your - printcap file loaded then the load printers option is easier.

    Default: no preloaded services

    Example: preload = fred lp colorlp

    >preload modules (G)

    This is a list of paths to modules that should - be loaded into smbd before a client connects. This improves - the speed of smbd when reacting to new connections somewhat.

    It is recommended to only use this option on heavy-performance - servers.

    Default: preload modules =

    Example: preload modules = /usr/lib/samba/passdb/mysql.so

    >preserve case (S)

    This controls if new filenames are created - with the case that the client passes, or if they are forced to - be the default case - .

    Default: preserve case = yes

    See the section on NAME - MANGLING for a fuller discussion.

    >print command (S)

    After a print job has finished spooling to - a service, this command will be used via a system() - call to process the spool file. Typically the command specified will - submit the spool file to the host's printing subsystem, but there - is no requirement that this be the case. The server will not remove - the spool file, so whatever command you specify should remove the - spool file when it has been processed, otherwise you will need to - manually remove old spool files.

    The print command is simply a text string. It will be used - verbatim after macro substitutions have been made:

    s, %p - the path to the spool - file name

    %p - the appropriate printer - name

    %J - the job - name as transmitted by the client.

    %c - The number of printed pages - of the spooled job (if known).

    %z - the size of the spooled - print job (in bytes)

    The print command MUST contain at least - one occurrence of %s or %f - - the %p is optional. At the time - a job is submitted, if no printer name is supplied the %p - will be silently removed from the printer command.

    If specified in the [global] section, the print command given - will be used for any printable service that does not have its own - print command specified.

    If there is neither a specified print command for a - printable service nor a global print command, spool files will - be created but not processed and (most importantly) not removed.

    Note that printing may fail on some UNIXes from the - nobody account. If this happens then create - an alternative guest account that can print and set the guest account - in the [global] section.

    You can form quite complex print commands by realizing - that they are just passed to a shell. For example the following - will log a print job, print the file, then remove it. Note that - ';' is the usual separator for command in shell scripts.

    print command = echo Printing %s >> - /tmp/print.log; lpr -P %p %s; rm %s

    You may have to vary this command considerably depending - on how you normally print files on your system. The default for - the parameter varies depending on the setting of the printing parameter.

    Default: For printing = BSD, AIX, QNX, LPRNG - or PLP :

    print command = lpr -r -P%p %s

    For printing = SYSV or HPUX :

    print command = lp -c -d%p %s; rm %s

    For printing = SOFTQ :

    print command = lp -d%p -s %s; rm %s

    For printing = CUPS : If SAMBA is compiled against - libcups, then printcap = cups - uses the CUPS API to - submit jobs, etc. Otherwise it maps to the System V - commands with the -oraw option for printing, i.e. it - uses lp -c -d%p -oraw; rm %s. - With printing = cups, - and if SAMBA is compiled against libcups, any manually - set print command will be ignored.

    Example: print command = /usr/local/samba/bin/myprintscript - %p %s

    >print ok (S)

    Synonym for printable.

    >printable (S)

    If this parameter is yes, then - clients may open, write to and submit spool files on the directory - specified for the service.

    Note that a printable service will ALWAYS allow writing - to the service path (user privileges permitting) via the spooling - of print data. The read only - parameter controls only non-printing access to - the resource.

    Default: printable = no

    >printcap (G)

    Synonym for printcap name.

    >printcap name (G)

    This parameter may be used to override the - compiled-in default printcap name used by the server (usually /etc/printcap). See the discussion of the [printers] section above for reasons - why you might want to do this.

    To use the CUPS printing interface set printcap name = cups - . This should be supplemented by an addtional setting - printing = cups in the [global] - section. printcap name = cups will use the - "dummy" printcap created by CUPS, as specified in your CUPS - configuration file. -

    On System V systems that use lpstat to - list available printers you can use printcap name = lpstat - to automatically obtain lists of available printers. This - is the default for systems that define SYSV at configure time in - Samba (this includes most System V based systems). If printcap name is set to lpstat on - these systems then Samba will launch lpstat -v and - attempt to parse the output to obtain a printer list.

    A minimal printcap file would look something like this:

    print1|My Printer 1
+			underscores).
    The two-digit hash value consists of upper case alphanumeric characters.
    This algorithm can cause name collisions only if files 
+	in a directory share the same first five alphanumeric characters. 
+	The probability of such a clash is 1/1300.
    The name mangling (if enabled) allows a file to be 
+	copied between UNIX directories from Windows/DOS while retaining 
+	the long UNIX filename. UNIX files can be renamed to a new extension 
+	from Windows/DOS and will retain the same basename. Mangled names 
+	do not change between sessions.
    Default: mangled names = yes
    mangling stack (G)

    This parameter controls the number of mangled names + that should be cached in the Samba server smbd(8).

    This stack is a list of recently mangled base names + (extensions are only maintained if they are longer than 3 characters + or contains upper case characters).

    The larger this value, the more likely it is that mangled + names can be successfully converted to correct long UNIX names. + However, large stack sizes will slow most directory accesses. Smaller + stacks save memory in the server (each stack element costs 256 bytes). +

    It is not possible to absolutely guarantee correct long + filenames, so be prepared for some surprises!

    Default: mangled stack = 50

    Example: mangled stack = 100

    mangling prefix (G)

    controls the number of prefix + characters from the original name used when generating + the mangled names. A larger value will give a weaker + hash and therefore more name collisions. The minimum + value is 1 and the maximum value is 6.

    Default: mangle prefix = 1

    Example: mangle prefix = 4

    mangling char (S)

    This controls what character is used as + the magic character in name mangling. The + default is a '~' but this may interfere with some software. Use this option to set + it to whatever you prefer.

    Default: mangling char = ~

    Example: mangling char = ^

    mangling method (G)

    controls the algorithm used for the generating + the mangled names. Can take two different values, "hash" and + "hash2". "hash" is the default and is the algorithm that has been + used in Samba for many years. "hash2" is a newer and considered + a better algorithm (generates less collisions) in the names. + However, many Win32 applications store the mangled names and so + changing to the new algorithm must not be done + lightly as these applications may break unless reinstalled.

    Default: mangling method = hash2

    Example: mangling method = hash

    map archive (S)

    This controls whether the DOS archive attribute + should be mapped to the UNIX owner execute bit. The DOS archive bit + is set when a file has been modified since its last backup. One + motivation for this option it to keep Samba/your PC from making + any file it touches from becoming executable under UNIX. This can + be quite annoying for shared source code, documents, etc...

    Note that this requires the create mask + parameter to be set such that owner execute bit is not masked out + (i.e. it must include 100). See the parameter + create mask for details.

    Default: map archive = yes

    map hidden (S)

    This controls whether DOS style hidden files + should be mapped to the UNIX world execute bit.

    Note that this requires the create mask + to be set such that the world execute bit is not masked out (i.e. + it must include 001). See the parameter + create mask for details.

    Default: map hidden = no

    map system (S)

    This controls whether DOS style system files + should be mapped to the UNIX group execute bit.

    Note that this requires the create mask + to be set such that the group execute bit is not masked out (i.e. + it must include 010). See the parameter + create mask for details.

    Default: map system = no

    map to guest (G)

    This parameter is only useful in + security modes other than security = share + - i.e. user, server, + and domain.

    This parameter can take three different values, which tell + smbd(8) what to do with user + login requests that don't match a valid UNIX user in some way.

    The three settings are :

    • Never - Means user login + requests with an invalid password are rejected. This is the + default.

    • Bad User - Means user + logins with an invalid password are rejected, unless the username + does not exist, in which case it is treated as a guest login and + mapped into the + guest account.

    • Bad Password - Means user logins + with an invalid password are treated as a guest login and mapped + into the guest account. Note that + this can cause problems as it means that any user incorrectly typing + their password will be silently logged on as "guest" - and + will not know the reason they cannot access files they think + they should - there will have been no message given to them + that they got their password wrong. Helpdesk services will + hate you if you set the map to + guest parameter this way :-).

    Note that this parameter is needed to set up "Guest" + share services when using security modes other than + share. This is because in these modes the name of the resource being + requested is not sent to the server until after + the server has successfully authenticated the client so the server + cannot make authentication decisions at the correct time (connection + to the share) for "Guest" shares.

    For people familiar with the older Samba releases, this + parameter maps to the old compile-time setting of the + GUEST_SESSSETUP value in local.h.

    Default: map to guest = Never

    Example: map to guest = Bad User

    max connections (S)

    This option allows the number of simultaneous connections to a service to be limited. + If max connections is greater than 0 then connections + will be refused if this number of connections to the service are already open. A value + of zero mean an unlimited number of connections may be made.

    Record lock files are used to implement this feature. The lock files will be stored in + the directory specified by the + lock directory option.

    Default: max connections = 0

    Example: max connections = 10

    max disk size (G)

    This option allows you to put an upper limit + on the apparent size of disks. If you set this option to 100 + then all shares will appear to be not larger than 100 MB in + size.

    Note that this option does not limit the amount of + data you can put on the disk. In the above case you could still + store much more than 100 MB on the disk, but if a client ever asks + for the amount of free disk space or the total disk size then the + result will be bounded by the amount specified in max + disk size.

    This option is primarily useful to work around bugs + in some pieces of software that can't handle very large disks, + particularly disks over 1GB in size.

    A max disk size of 0 means no limit.

    Default: max disk size = 0

    Example: max disk size = 1000

    max log size (G)

    This option (an integer in kilobytes) specifies + the max size the log file should grow to. Samba periodically checks + the size and if it is exceeded it will rename the file, adding + a .old extension.

    A size of 0 means no limit.

    Default: max log size = 5000

    Example: max log size = 1000

    max mux (G)

    This option controls the maximum number of + outstanding simultaneous SMB operations that Samba tells the client + it will allow. You should never need to set this parameter.

    Default: max mux = 50

    max open files (G)

    This parameter limits the maximum number of + open files that one smbd(8) file + serving process may have open for a client at any one time. The + default for this parameter is set very high (10,000) as Samba uses + only one bit per unopened file.

    The limit of the number of open files is usually set + by the UNIX per-process file descriptor limit rather than + this parameter so you should never need to touch this parameter.

    Default: max open files = 10000

    max print jobs (S)

    This parameter limits the maximum number of + jobs allowable in a Samba printer queue at any given moment. + If this number is exceeded, smbd(8) will remote "Out of Space" to the client. + See all total + print jobs. +

    Default: max print jobs = 1000

    Example: max print jobs = 5000

    max protocol (G)

    The value of the parameter (a string) is the highest + protocol level that will be supported by the server.

    Possible values are :

    • CORE: Earliest version. No + concept of user names.

    • COREPLUS: Slight improvements on + CORE for efficiency.

    • LANMAN1: First + modern version of the protocol. Long filename + support.

    • LANMAN2: Updates to Lanman1 protocol.

    • NT1: Current up to date version of the protocol. + Used by Windows NT. Known as CIFS.

    Normally this option should not be set as the automatic + negotiation phase in the SMB protocol takes care of choosing + the appropriate protocol.

    See also min + protocol

    Default: max protocol = NT1

    Example: max protocol = LANMAN1

    max smbd processes (G)

    This parameter limits the maximum number of smbd(8) processes concurrently running on a system and is intended + as a stopgap to prevent degrading service to clients in the event that the server has insufficient + resources to handle more than this number of connections. Remember that under normal operating + conditions, each user will have an smbd(8) associated with him or her to handle connections to all + shares from a given host.

    Default: max smbd processes = 0 ## no limit

    Example: max smbd processes = 1000

    max ttl (G)

    This option tells nmbd(8) what the default 'time to live' + of NetBIOS names should be (in seconds) when nmbd is + requesting a name using either a broadcast packet or from a WINS server. You should + never need to change this parameter. The default is 3 days.

    Default: max ttl = 259200

    max wins ttl (G)

    This option tells smbd(8) when acting as a WINS server ( + wins support = yes) what the maximum + 'time to live' of NetBIOS names that nmbd + will grant will be (in seconds). You should never need to change this + parameter. The default is 6 days (518400 seconds).

    See also the min + wins ttl parameter.

    Default: max wins ttl = 518400

    max xmit (G)

    This option controls the maximum packet size + that will be negotiated by Samba. The default is 65535, which + is the maximum. In some cases you may find you get better performance + with a smaller value. A value below 2048 is likely to cause problems. +

    Default: max xmit = 65535

    Example: max xmit = 8192

    message command (G)

    This specifies what command to run when the + server receives a WinPopup style message.

    This would normally be a command that would + deliver the message somehow. How this is to be done is + up to your imagination.

    An example is:

    message command = csh -c 'xedit %s;rm %s' & +

    This delivers the message using xedit, then + removes it afterwards. NOTE THAT IT IS VERY IMPORTANT + THAT THIS COMMAND RETURN IMMEDIATELY. That's why I + have the '&' on the end. If it doesn't return immediately then + your PCs may freeze when sending messages (they should recover + after 30 seconds, hopefully).

    All messages are delivered as the global guest user. + The command takes the standard substitutions, although + %u won't work (%U may be better + in this case).

    Apart from the standard substitutions, some additional + ones apply. In particular:

    • %s = the filename containing + the message.

    • %t = the destination that + the message was sent to (probably the server name).

    • %f = who the message + is from.

    You could make this command send mail, or whatever else + takes your fancy. Please let us know of any really interesting + ideas you have.

    Here's a way of sending the messages as mail to root:

    message command = /bin/mail -s 'message from %f on + %m' root < %s; rm %s

    If you don't have a message command then the message + won't be delivered and Samba will tell the sender there was + an error. Unfortunately WfWg totally ignores the error code + and carries on regardless, saying that the message was delivered. +

    If you want to silently delete it then try:

    message command = rm %s

    Default: no message command

    Example: message command = csh -c 'xedit %s; rm %s' &

    min passwd length (G)

    Synonym for + min password length. +

    min password length (G)

    This option sets the minimum length in characters of a + plaintext password that smbd will + accept when performing UNIX password changing.

    See also unix + password sync, + passwd program and + passwd chat debug.

    Default: min password length = 5

    min print space (S)

    This sets the minimum amount of free disk + space that must be available before a user will be able to spool + a print job. It is specified in kilobytes. The default is 0, which + means a user can always spool a print job.

    See also the printing + parameter.

    Default: min print space = 0

    Example: min print space = 2000

    min protocol (G)

    The value of the parameter (a string) is the + lowest SMB protocol dialect than Samba will support. Please refer + to the max protocol + parameter for a list of valid protocol names and a brief description + of each. You may also wish to refer to the C source code in + source/smbd/negprot.c for a listing of known protocol + dialects supported by clients.

    If you are viewing this parameter as a security measure, you should + also refer to the lanman + auth parameter. Otherwise, you should never need + to change this parameter.

    Default : min protocol = CORE

    Example : min protocol = NT1 # disable DOS clients

    min wins ttl (G)

    This option tells nmbd(8) + when acting as a WINS server ( + wins support = yes) what the minimum 'time to live' + of NetBIOS names that nmbd will grant will be (in + seconds). You should never need to change this parameter. The default + is 6 hours (21600 seconds).

    Default: min wins ttl = 21600

    msdfs proxy (S)

    This parameter indicates that the share is a + stand-in for another CIFS share whose location is specified by + the value of the parameter. When clients attempt to connect to + this share, they are redirected to the proxied share using + the SMB-Dfs protocol.

    Only Dfs roots can act as proxy shares. Take a look at the + msdfs root + and host msdfs + options to find out how to set up a Dfs root share.

    Example: msdfs proxy = \\\\otherserver\\someshare

    msdfs root (S)

    This boolean parameter is only available if + Samba is configured and compiled with the + --with-msdfs option. If set to yes, + Samba treats the share as a Dfs root and allows clients to browse + the distributed file system tree rooted at the share directory. + Dfs links are specified in the share directory by symbolic + links of the form msdfs:serverA\\shareA,serverB\\shareB + and so on. For more information on setting up a Dfs tree + on Samba, refer to "Hosting a Microsoft + Distributed File System tree on Samba" document.

    See also host msdfs

    Default: msdfs root = no

    name cache timeout (G)

    Specifies the number of seconds it takes before + entries in samba's hostname resolve cache time out. If + the timeout is set to 0. the caching is disabled. +

    Default: name cache timeout = 660

    Example: name cache timeout = 0

    name resolve order (G)

    This option is used by the programs in the Samba + suite to determine what naming services to use and in what order + to resolve host names to IP addresses. The option takes a space + separated string of name resolution options.

    The options are: "lmhosts", "host", + "wins" and "bcast". They cause names to be + resolved as follows:

    • lmhosts : Lookup an IP + address in the Samba lmhosts file. If the line in lmhosts has + no name type attached to the NetBIOS name (see the lmhosts(5) for details) then + any name type matches for lookup.

    • host : Do a standard host + name to IP address resolution, using the system /etc/hosts + , NIS, or DNS lookups. This method of name resolution + is operating system depended for instance on IRIX or Solaris this + may be controlled by the /etc/nsswitch.conf + file. Note that this method is only used if the NetBIOS name + type being queried is the 0x20 (server) name type, otherwise + it is ignored.

    • wins : Query a name with + the IP address listed in the + wins server parameter. If no WINS server has + been specified this method will be ignored.

    • bcast : Do a broadcast on + each of the known local interfaces listed in the interfaces + parameter. This is the least reliable of the name resolution + methods as it depends on the target host being on a locally + connected subnet.

    Default: name resolve order = lmhosts host wins bcast

    Example: name resolve order = lmhosts bcast host

    This will cause the local lmhosts file to be examined + first, followed by a broadcast attempt, followed by a normal + system hostname lookup.

    netbios aliases (G)

    This is a list of NetBIOS names that nmbd(8) will + advertise as additional names by which the Samba server is known. This allows one machine + to appear in browse lists under multiple names. If a machine is acting as a browse server + or logon server none of these names will be advertised as either browse server or logon + servers, only the primary name of the machine will be advertised with these capabilities. +

    See also netbios + name.

    Default: empty string (no additional names)

    Example: netbios aliases = TEST TEST1 TEST2

    netbios name (G)

    This sets the NetBIOS name by which a Samba + server is known. By default it is the same as the first component + of the host's DNS name. If a machine is a browse server or + logon server this name (or the first component + of the hosts DNS name) will be the name that these services are + advertised under.

    See also netbios + aliases.

    Default: machine DNS name

    Example: netbios name = MYNAME

    netbios scope (G)

    This sets the NetBIOS scope that Samba will + operate under. This should not be set unless every machine + on your LAN also sets this value.

    nis homedir (G)

    Get the home share server from a NIS map. For + UNIX systems that use an automounter, the user's home directory + will often be mounted on a workstation on demand from a remote + server.

    When the Samba logon server is not the actual home directory + server, but is mounting the home directories via NFS then two + network hops would be required to access the users home directory + if the logon server told the client to use itself as the SMB server + for home directories (one over SMB and one over NFS). This can + be very slow.

    This option allows Samba to return the home share as + being on a different server to the logon server and as + long as a Samba daemon is running on the home directory server, + it will be mounted on the Samba client directly from the directory + server. When Samba is returning the home share to the client, it + will consult the NIS map specified in + homedir map and return the server + listed there.

    Note that for this option to work there must be a working + NIS system and the Samba server with this option must also + be a logon server.

    Default: nis homedir = no

    non unix account range (G)

    The non unix account range parameter specifies + the range of 'user ids' that are allocated by the various 'non unix + account' passdb backends. These backends allow + the storage of passwords for users who don't exist in /etc/passwd. + This is most often used for machine account creation. + This range of ids should have no existing local or NIS users within + it as strange conflicts can occur otherwise.

    Note

    These userids never appear on the system and Samba will never + 'become' these users. They are used only to ensure that the algorithmic + RID mapping does not conflict with normal users. +

    Default: non unix account range = <empty string>

    Example: non unix account range = 10000-20000

    nt acl support (S)

    This boolean parameter controls whether smbd(8) will attempt to map + UNIX permissions into Windows NT access control lists. + This parameter was formally a global parameter in releases + prior to 2.2.2.

    Default: nt acl support = yes

    ntlm auth (G)

    This parameter determines whether or not smbd(8) will attempt to authenticate users using the NTLM password hash. + If disabled, only the lanman password hashes will be used.

    Please note that at least this option or lanman auth should + be enabled in order to be able to log in.

    Default : ntlm auth = yes

    nt pipe support (G)

    This boolean parameter controls whether + smbd(8) will allow Windows NT + clients to connect to the NT SMB specific IPC$ + pipes. This is a developer debugging option and can be left + alone.

    Default: nt pipe support = yes

    nt status support (G)

    This boolean parameter controls whether smbd(8) will negotiate NT specific status + support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone. + If this option is set to no then Samba offers + exactly the same DOS error codes that versions prior to Samba 2.2.3 + reported.

    You should not need to ever disable this parameter.

    Default: nt status support = yes

    null passwords (G)

    Allow or disallow client access to accounts that have null passwords.

    See also smbpasswd(5).

    Default: null passwords = no

    obey pam restrictions (G)

    When Samba 3.0 is configured to enable PAM support + (i.e. --with-pam), this parameter will control whether or not Samba + should obey PAM's account and session management directives. The + default behavior is to use PAM for clear text authentication only + and to ignore any account or session management. Note that Samba + always ignores PAM for authentication in the case of + encrypt passwords = yes. The reason + is that PAM modules cannot support the challenge/response + authentication mechanism needed in the presence of SMB password encryption. +

    Default: obey pam restrictions = no

    only guest (S)

    A synonym for + guest only.

    only user (S)

    This is a boolean option that controls whether + connections with usernames not in the user + list will be allowed. By default this option is disabled so that a + client can supply a username to be used by the server. Enabling + this parameter will force the server to only use the login + names from the user list and is only really + useful in share level + security.

    Note that this also means Samba won't try to deduce + usernames from the service name. This can be annoying for + the [homes] section. To get around this you could use user = + %S which means your user list + will be just the service name, which for home directories is the + name of the user.

    See also the user + parameter.

    Default: only user = no

    oplock break wait time (G)

    This is a tuning parameter added due to bugs in + both Windows 9x and WinNT. If Samba responds to a client too + quickly when that client issues an SMB that can cause an oplock + break request, then the network client can fail and not respond + to the break request. This tuning parameter (which is set in milliseconds) + is the amount of time Samba will wait before sending an oplock break + request to such (broken) clients.

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND + UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock break wait time = 0

    oplock contention limit (S)

    This is a very advanced + smbd(8) tuning option to + improve the efficiency of the granting of oplocks under multiple + client contention for the same file.

    In brief it specifies a number, which causes smbd(8)not to grant an oplock even when requested + if the approximate number of clients contending for an oplock on the same file goes over this + limit. This causes smbd to behave in a similar + way to Windows NT.

    DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ + AND UNDERSTOOD THE SAMBA OPLOCK CODE.

    Default: oplock contention limit = 2

    oplocks (S)

    This boolean option tells smbd whether to + issue oplocks (opportunistic locks) to file open requests on this + share. The oplock code can dramatically (approx. 30% or more) improve + the speed of access to files on Samba servers. It allows the clients + to aggressively cache files locally and you may want to disable this + option for unreliable network environments (it is turned on by + default in Windows NT Servers). For more information see the file + Speed.txt in the Samba docs/ + directory.

    Oplocks may be selectively turned off on certain files with a + share. See the + veto oplock files parameter. On some systems + oplocks are recognized by the underlying operating system. This + allows data synchronization between all access to oplocked files, + whether it be via Samba or NFS or a local UNIX process. See the + kernel oplocks parameter for details.

    See also the kernel + oplocks and + level2 oplocks parameters.

    Default: oplocks = yes

    os2 driver map (G)

    The parameter is used to define the absolute + path to a file containing a mapping of Windows NT printer driver + names to OS/2 printer driver names. The format is:

    <nt driver name> = <os2 driver name>.<device name>

    For example, a valid entry using the HP LaserJet 5 + printer driver would appear as HP LaserJet 5L = LASERJET.HP + LaserJet 5L.

    The need for the file is due to the printer driver namespace + problem described in the Samba + Printing HOWTO. For more details on OS/2 clients, please + refer to the OS2-Client-HOWTO containing in the Samba documentation.

    Default: os2 driver map = <empty string>

    os level (G)

    This integer value controls what level Samba + advertises itself as for browse elections. The value of this + parameter determines whether nmbd(8) + has a chance of becoming a local master browser for the + WORKGROUP in the local broadcast area.

    Note :By default, Samba will win + a local master browsing election over all Microsoft operating + systems except a Windows NT 4.0/2000 Domain Controller. This + means that a misconfigured Samba host can effectively isolate + a subnet for browsing purposes. See BROWSING.txt + in the Samba docs/ directory + for details.

    Default: os level = 20

    Example: os level = 65

    pam password change (G)

    With the addition of better PAM support in Samba 2.2, + this parameter, it is possible to use PAM's password change control + flag for Samba. If enabled, then PAM will be used for password + changes when requested by an SMB client instead of the program listed in + passwd program. + It should be possible to enable this without changing your + passwd chat + parameter for most setups.

    Default: pam password change = no

    panic action (G)

    This is a Samba developer option that allows a + system command to be called when either smbd(8) or smbd(8) crashes. This is usually used to + draw attention to the fact that a problem occurred.

    Default: panic action = <empty string>

    Example: panic action = "/bin/sleep 90000"

    paranoid server security (G)

    Some version of NT 4.x allow non-guest + users with a bad passowrd. When this option is enabled, samba will not + use a broken NT 4.x server as password server, but instead complain + to the logs and exit. +

    Disabling this option prevents Samba from making + this check, which involves deliberatly attempting a + bad logon to the remote server.

    Default: paranoid server security = yes

    passdb backend (G)

    This option allows the administrator to chose which backends + to retrieve and store passwords with. This allows (for example) both + smbpasswd and tdbsam to be used without a recompile. Multiple + backends can be specified, separated by spaces. The backends will be + searched in the order they are specified. New users are always added + to the first backend specified.

    This parameter is in two parts, the backend's name, and a 'location' + string that has meaning only to that particular backed. These are separated + by a : character.

    Available backends can include: +

    • smbpasswd - The default smbpasswd + backend. Takes a path to the smbpasswd file as an optional argument. +

    • smbpasswd_nua - The smbpasswd + backend, but with support for 'not unix accounts'. + Takes a path to the smbpasswd file as an optional argument.

      See also + non unix account range

    • tdbsam - The TDB based password storage + backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb + in the + private dir directory.

    • tdbsam_nua - The TDB based password storage + backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb + in the + private dir directory.

      See also + non unix account range

    • ldapsam - The LDAP based passdb + backend. Takes an LDAP URL as an optional argument (defaults to + ldap://localhost)

    • ldapsam_nua - The LDAP based passdb + backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to + ldap://localhost)

      Note: In this module, any account without a matching POSIX account is regarded + as 'non unix'.

      See also + non unix account range

      LDAP connections should be secured where possible. This may be done using either + Start-TLS (see ldap ssl) or by + specifying ldaps:// in + the URL argument.

    • nisplussam - + The NIS+ based passdb backend. Takes name NIS domain as + an optional argument. Only works with sun NIS+ servers. +

    +

    Default: passdb backend = smbpasswd unixsam

    Example: passdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd guest

    Example: passdb backend = ldapsam_nua:ldaps://ldap.example.com guest

    Example: passdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb

    passwd chat debug (G)

    This boolean specifies if the passwd chat script + parameter is run in debug mode. In this mode the + strings passed to and received from the passwd chat are printed + in the smbd(8) log with a + debug level + of 100. This is a dangerous option as it will allow plaintext passwords + to be seen in the smbd log. It is available to help + Samba admins debug their passwd chat scripts + when calling the passwd program and should + be turned off after this has been done. This option has no effect if the + pam password change + paramter is set. This parameter is off by default.

    See also passwd chat + , pam password change + , passwd program + .

    Default: passwd chat debug = no

    passwd chat (G)

    This string controls the "chat" + conversation that takes places between smbd(8) and the local password changing + program to change the user's password. The string describes a + sequence of response-receive pairs that smbd(8) uses to determine what to send to the + passwd program + and what to expect back. If the expected output is not + received then the password is not changed.

    This chat sequence is often quite site specific, depending + on what local methods are used for password control (such as NIS + etc).

    Note that this parameter only is only used if the unix password sync + parameter is set to yes. This sequence is + then called AS ROOT when the SMB password in the + smbpasswd file is being changed, without access to the old password + cleartext. This means that root must be able to reset the user's password without + knowing the text of the previous password. In the presence of + NIS/YP, this means that the passwd program must + be executed on the NIS master. +

    The string can contain the macro %n which is substituted + for the new password. The chat sequence can also contain the standard + macros \\n, \\r, \\t and \\s to + give line-feed, carriage-return, tab and space. The chat sequence string can also contain + a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces + in them into a single string.

    If the send string in any part of the chat sequence is a full + stop ".", then no string is sent. Similarly, if the + expect string is a full stop then no string is expected.

    If the pam + password change parameter is set to yes, the chat pairs + may be matched in any order, and success is determined by the PAM result, + not any particular output. The \n macro is ignored for PAM conversions. +

    See also unix password + sync, + passwd program , + passwd chat debug and + pam password change.

    Default: passwd chat = *new*password* %n\\n + *new*password* %n\\n *changed*

    Example: passwd chat = "*Enter OLD password*" %o\\n + "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n + "*Password changed*"

    passwd program (G)

    The name of a program that can be used to set + UNIX user passwords. Any occurrences of %u + will be replaced with the user name. The user name is checked for + existence before calling the password changing program.

    Also note that many passwd programs insist in reasonable + passwords, such as a minimum length, or the inclusion + of mixed case chars and digits. This can pose a problem as some clients + (such as Windows for Workgroups) uppercase the password before sending + it.

    Note that if the unix + password sync parameter is set to yes + then this program is called AS ROOT + before the SMB password in the smbpasswd(5) + file is changed. If this UNIX password change fails, then + smbd will fail to change the SMB password also + (this is by design).

    If the unix password sync parameter + is set this parameter MUST USE ABSOLUTE PATHS + for ALL programs called, and must be examined + for security implications. Note that by default unix + password sync is set to no.

    See also unix + password sync.

    Default: passwd program = /bin/passwd

    Example: passwd program = /sbin/npasswd %u

    password level (G)

    Some client/server combinations have difficulty + with mixed-case passwords. One offending client is Windows for + Workgroups, which for some reason forces passwords to upper + case when using the LANMAN1 protocol, but leaves them alone when + using COREPLUS! Another problem child is the Windows 95/98 + family of operating systems. These clients upper case clear + text passwords even when NT LM 0.12 selected by the protocol + negotiation request/response.

    This parameter defines the maximum number of characters + that may be upper case in passwords.

    For example, say the password given was "FRED". If + password level is set to 1, the following combinations + would be tried if "FRED" failed:

    "Fred", "fred", "fRed", "frEd","freD"

    If password level was set to 2, + the following combinations would also be tried:

    "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..

    And so on.

    The higher value this parameter is set to the more likely + it is that a mixed case password will be matched against a single + case password. However, you should be aware that use of this + parameter reduces security and increases the time taken to + process a new connection.

    A value of zero will cause only two attempts to be + made - the password as is and the password in all-lower case.

    Default: password level = 0

    Example: password level = 4

    password server (G)

    By specifying the name of another SMB server (such + as a WinNT box) with this option, and using security = domain + or security = server you can get Samba + to do all its username/password validation via a remote server.

    This option sets the name of the password server to use. + It must be a NetBIOS name, so if the machine's NetBIOS name is + different from its Internet name then you may have to add its NetBIOS + name to the lmhosts file which is stored in the same directory + as the smb.conf file.

    The name of the password server is looked up using the + parameter name + resolve order and so may resolved + by any method and order described in that parameter.

    The password server must be a machine capable of using + the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in + user level security mode.

    Note

    Using a password server means your UNIX box (running + Samba) is only as secure as your password server. DO NOT + CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST. +

    Never point a Samba server at itself for password serving. + This will cause a loop and could lock up your Samba server!

    The name of the password server takes the standard + substitutions, but probably the only useful one is %m + , which means the Samba server will use the incoming + client as the password server. If you use this then you better + trust your clients, and you had better restrict them with hosts allow!

    If the security parameter is set to + domain, then the list of machines in this + option must be a list of Primary or Backup Domain controllers for the + Domain or the character '*', as the Samba server is effectively + in that domain, and will use cryptographically authenticated RPC calls + to authenticate the user logging on. The advantage of using + security = domain is that if you list several hosts in the + password server option then smbd + will try each in turn till it finds one that responds. This + is useful in case your primary server goes down.

    If the password server option is set + to the character '*', then Samba will attempt to auto-locate the + Primary or Backup Domain controllers to authenticate against by + doing a query for the name WORKGROUP<1C> + and then contacting each server returned in the list of IP + addresses from the name resolution source.

    If the list of servers contains both names and the '*' + character, the list is treated as a list of preferred + domain controllers, but an auto lookup of all remaining DC's + will be added to the list as well. Samba will not attempt to optimize + this list by locating the closest DC.

    If the security parameter is + set to server, then there are different + restrictions that security = domain doesn't + suffer from:

    • You may list several password servers in + the password server parameter, however if an + smbd makes a connection to a password server, + and then the password server fails, no more users will be able + to be authenticated from this smbd. This is a + restriction of the SMB/CIFS protocol when in security = server + mode and cannot be fixed in Samba.

    • If you are using a Windows NT server as your + password server then you will have to ensure that your users + are able to login from the Samba server, as when in + security = server mode the network logon will appear to + come from there rather than from the users workstation.

    See also the security + parameter.

    Default: password server = <empty string>

    Example: password server = NT-PDC, NT-BDC1, NT-BDC2, *

    Example: password server = *

    path (S)

    This parameter specifies a directory to which + the user of the service is to be given access. In the case of + printable services, this is where print data will spool prior to + being submitted to the host for printing.

    For a printable service offering guest access, the service + should be readonly and the path should be world-writeable and + have the sticky bit set. This is not mandatory of course, but + you probably won't get the results you expect if you do + otherwise.

    Any occurrences of %u in the path + will be replaced with the UNIX username that the client is using + on this connection. Any occurrences of %m + will be replaced by the NetBIOS name of the machine they are + connecting from. These replacements are very useful for setting + up pseudo home directories for users.

    Note that this path will be based on + root dir if one was specified.

    Default: none

    Example: path = /home/fred

    pid directory (G)

    This option specifies the directory where pid + files will be placed.

    Default: pid directory = ${prefix}/var/locks

    Example: pid directory = /var/run/

    posix locking (S)

    The smbd(8) + daemon maintains an database of file locks obtained by SMB clients. + The default behavior is to map this internal database to POSIX + locks. This means that file locks obtained by SMB clients are + consistent with those seen by POSIX compliant applications accessing + the files via a non-SMB method (e.g. NFS or local file access). + You should never need to disable this parameter.

    Default: posix locking = yes

    postexec (S)

    This option specifies a command to be run + whenever the service is disconnected. It takes the usual + substitutions. The command may be run as the root on some + systems.

    An interesting example may be to unmount server + resources:

    postexec = /etc/umount /cdrom

    See also preexec.

    Default: none (no command executed)

    Example: postexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log

    preexec close (S)

    This boolean option controls whether a non-zero + return code from preexec + should close the service being connected to.

    Default: preexec close = no

    preexec (S)

    This option specifies a command to be run whenever + the service is connected to. It takes the usual substitutions.

    An interesting example is to send the users a welcome + message every time they log in. Maybe a message of the day? Here + is an example:

    preexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' &

    Of course, this could get annoying after a while :-)

    See also preexec close and postexec + .

    Default: none (no command executed)

    Example: preexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log

    prefered master (G)

    Synonym for + preferred master for people who cannot spell :-).

    preferred master (G)

    This boolean parameter controls if + nmbd(8) is a preferred master + browser for its workgroup.

    If this is set to yes, on startup, nmbd + will force an election, and it will have a slight advantage in + winning the election. It is recommended that this parameter is + used in conjunction with + domain master = yes, so + that nmbd can guarantee becoming a domain master.

    Use this option with caution, because if there are several + hosts (whether Samba servers, Windows 95 or NT) that are + preferred master browsers on the same subnet, they will each + periodically and continuously attempt to become the local + master browser. This will result in unnecessary broadcast + traffic and reduced browsing capabilities.

    See also os level.

    Default: preferred master = auto

    preload modules (G)

    This is a list of paths to modules that should + be loaded into smbd before a client connects. This improves + the speed of smbd when reacting to new connections somewhat.

    It is recommended to only use this option on heavy-performance + servers.

    Default: preload modules =

    Example: preload modules = /usr/lib/samba/passdb/mysql.so+++

    preload (G)

    This is a list of services that you want to be + automatically added to the browse lists. This is most useful + for homes and printers services that would otherwise not be + visible.

    Note that if you just want all printers in your + printcap file loaded then the + load printers option is easier.

    Default: no preloaded services

    Example: preload = fred lp colorlp

    preserve case (S)

    This controls if new filenames are created + with the case that the client passes, or if they are forced to + be the default case + .

    Default: preserve case = yes

    See the section on NAME MANGLING for a fuller discussion.

    printable (S)

    If this parameter is yes, then + clients may open, write to and submit spool files on the directory + specified for the service.

    Note that a printable service will ALWAYS allow writing + to the service path (user privileges permitting) via the spooling + of print data. The read only + parameter controls only non-printing access to + the resource.

    Default: printable = no

    printcap name (S)

    This parameter may be used to override the + compiled-in default printcap name used by the server (usually + /etc/printcap). See the discussion of the [printers] section above for reasons + why you might want to do this.

    To use the CUPS printing interface set printcap name = cups + . This should be supplemented by an addtional setting + printing = cups in the [global] + section. printcap name = cups will use the + "dummy" printcap created by CUPS, as specified in your CUPS + configuration file. +

    On System V systems that use lpstat to + list available printers you can use printcap name = lpstat + to automatically obtain lists of available printers. This + is the default for systems that define SYSV at configure time in + Samba (this includes most System V based systems). If + printcap name is set to lpstat on + these systems then Samba will launch lpstat -v and + attempt to parse the output to obtain a printer list.

    A minimal printcap file would look something like this:

    +print1|My Printer 1
 print2|My Printer 2
 print3|My Printer 3
 print4|My Printer 4
-print5|My Printer 5

    where the '|' separates aliases of a printer. The fact - that the second alias has a space in it gives a hint to Samba - that it's a comment.

    Under AIX the default printcap - name is /etc/qconfig. Samba will assume the - file is in AIX qconfig format if the string - qconfig appears in the printcap filename.

    Default: printcap name = /etc/printcap

    Example: printcap name = /etc/myprintcap

    >printer admin (S)

    This is a list of users that can do anything to - printers via the remote administration interfaces offered by MS-RPC - (usually using a NT workstation). Note that the root user always - has admin rights.

    Default: printer admin = <empty string> -

    Example: printer admin = admin, @staff

    >printer name (S)

    This parameter specifies the name of the printer - to which print jobs spooled through a printable service will be sent.

    If specified in the [global] section, the printer - name given will be used for any printable service that does - not have its own printer name specified.

    Default: none (but may be lp - on many systems)

    Example: printer name = laserwriter

    >printer (S)

    Synonym for printer name.

    >printing (S)

    This parameters controls how printer status - information is interpreted on your system. It also affects the - default values for the print command, - lpq command, lppause command - , lpresume command, and - lprm command if specified in the - [global] section.

    Currently nine printing styles are supported. They are - BSD, AIX, - LPRNG, PLP, - SYSV, HPUX, - QNX, SOFTQ, - and CUPS.

    To see what the defaults are for the other print - commands when using the various options use the testparm(1) program.

    This option can be set on a per printer basis

    See also the discussion in the [printers] section.

    >private dir (G)

    This parameters defines the directory - smbd will use for storing such files as smbpasswd - and secrets.tdb. -

    Default :private dir = ${prefix}/private

    >protocol (G)

    Synonym for max protocol.

    >public (S)

    Synonym for guest - ok.

    >queuepause command (S)

    This parameter specifies the command to be - executed on the server host in order to pause the printer queue.

    This command should be a program or script which takes - a printer name as its only parameter and stops the printer queue, - such that no longer jobs are submitted to the printer.

    This command is not supported by Windows for Workgroups, - but can be issued from the Printers window under Windows 95 - and NT.

    If a %p is given then the printer name - is put in its place. Otherwise it is placed at the end of the command. -

    Note that it is good practice to include the absolute - path in the command as the PATH may not be available to the - server.

    Default: depends on the setting of printing -

    Example: queuepause command = disable %p

    >queueresume command (S)

    This parameter specifies the command to be - executed on the server host in order to resume the printer queue. It - is the command to undo the behavior that is caused by the - previous parameter ( queuepause command).

    This command should be a program or script which takes - a printer name as its only parameter and resumes the printer queue, - such that queued jobs are resubmitted to the printer.

    This command is not supported by Windows for Workgroups, - but can be issued from the Printers window under Windows 95 - and NT.

    If a %p is given then the printer name - is put in its place. Otherwise it is placed at the end of the - command.

    Note that it is good practice to include the absolute - path in the command as the PATH may not be available to the - server.

    Default: depends on the setting of printing -

    Example: queuepause command = enable %p -

    >read bmpx (G)

    This boolean parameter controls whether smbd(8) will support the "Read - Block Multiplex" SMB. This is now rarely used and defaults to - no. You should never need to set this - parameter.

    Default: read bmpx = no

    >read list (S)

    This is a list of users that are given read-only - access to a service. If the connecting user is in this list then - they will not be given write access, no matter what the read only - option is set to. The list can include group names using the - syntax described in the invalid users parameter.

    See also the write list parameter and the invalid users - parameter.

    Default: read list = <empty string>

    Example: read list = mary, @students

    >read only (S)

    An inverted synonym is writeable.

    If this parameter is yes, then users - of a service may not create or modify files in the service's - directory.

    Note that a printable service (printable = yes) - will ALWAYS allow writing to the directory - (user privileges permitting), but only via spooling operations.

    Default: read only = yes

    >read raw (G)

    This parameter controls whether or not the server - will support the raw read SMB requests when transferring data - to clients.

    If enabled, raw reads allow reads of 65535 bytes in - one packet. This typically provides a major performance benefit. -

    However, some clients either negotiate the allowable - block size incorrectly or are incapable of supporting larger block - sizes, and for these clients you may need to disable raw reads.

    In general this parameter should be viewed as a system tuning - tool and left severely alone. See also write raw.

    Default: read raw = yes

    >read size (G)

    The option read size - affects the overlap of disk reads/writes with network reads/writes. - If the amount of data being transferred in several of the SMB - commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger - than this value then the server begins writing the data before it - has received the whole packet from the network, or in the case of - SMBreadbraw, it begins writing to the network before all the data - has been read from disk.

    This overlapping works best when the speeds of disk and - network access are similar, having very little effect when the - speed of one is much greater than the other.

    The default value is 16384, but very little experimentation - has been done yet to determine the optimal value, and it is likely - that the best value will vary greatly between systems anyway. - A value over 65536 is pointless and will cause you to allocate - memory unnecessarily.

    Default: read size = 16384

    Example: read size = 8192

    >realm (G)

    This option specifies the kerberos realm to use. The realm is - used as the ADS equivalent of the NT4domain. It - is usually set to the DNS name of the kerberos server. -

    Default: realm =

    Example: realm = mysambabox.mycompany.com

    >remote announce (G)

    This option allows you to setup nmbd(8) to periodically announce itself - to arbitrary IP addresses with an arbitrary workgroup name.

    This is useful if you want your Samba server to appear - in a remote workgroup for which the normal browse propagation - rules don't work. The remote workgroup can be anywhere that you - can send IP packets to.

    For example:

    remote announce = 192.168.2.255/SERVERS - 192.168.4.255/STAFF

    the above line would cause nmbd to announce itself - to the two given IP addresses using the given workgroup names. - If you leave out the workgroup name then the one given in - the workgroup - parameter is used instead.

    The IP addresses you choose would normally be the broadcast - addresses of the remote networks, but can also be the IP addresses - of known browse masters if your network config is that stable.

    See the documentation file BROWSING - in the docs/ directory.

    Default: remote announce = <empty string> -

    >remote browse sync (G)

    This option allows you to setup nmbd(8) to periodically request - synchronization of browse lists with the master browser of a Samba - server that is on a remote segment. This option will allow you to - gain browse lists for multiple workgroups across routed networks. This - is done in a manner that does not work with any non-Samba servers.

    This is useful if you want your Samba server and all local - clients to appear in a remote workgroup for which the normal browse - propagation rules don't work. The remote workgroup can be anywhere - that you can send IP packets to.

    For example:

    remote browse sync = 192.168.2.255 192.168.4.255 -

    the above line would cause nmbd to request - the master browser on the specified subnets or addresses to - synchronize their browse lists with the local server.

    The IP addresses you choose would normally be the broadcast - addresses of the remote networks, but can also be the IP addresses - of known browse masters if your network config is that stable. If - a machine IP address is given Samba makes NO attempt to validate - that the remote machine is available, is listening, nor that it - is in fact the browse master on its segment.

    Default: remote browse sync = <empty string> -

    >restrict anonymous (G)

    This is a integer parameter, and - mirrors as much as possible the functinality the - RestrictAnonymous - registry key does on NT/Win2k.

    Default: restrict anonymous = 0

    >root (G)

    Synonym for root directory".

    >root dir (G)

    Synonym for root directory".

    >root directory (G)

    The server will chroot() (i.e. - Change its root directory) to this directory on startup. This is - not strictly necessary for secure operation. Even without it the - server will deny access to files not in one of the service entries. - It may also check for, and deny access to, soft links to other - parts of the filesystem, or attempts to use ".." in file names - to access other directories (depending on the setting of the wide links - parameter).

    Adding a root directory entry other - than "/" adds an extra level of security, but at a price. It - absolutely ensures that no access is given to files not in the - sub-tree specified in the root directory - option, including some files needed for - complete operation of the server. To maintain full operability - of the server you will need to mirror some system files - into the root directory tree. In particular - you will need to mirror /etc/passwd (or a - subset of it), and any binaries or configuration files needed for - printing (if required). The set of files that must be mirrored is - operating system dependent.

    Default: root directory = /

    Example: root directory = /homes/smb

    >root postexec (S)

    This is the same as the postexec - parameter except that the command is run as root. This - is useful for unmounting filesystems - (such as CDROMs) after a connection is closed.

    See also postexec.

    Default: root postexec = <empty string> -

    >root preexec (S)

    This is the same as the preexec - parameter except that the command is run as root. This - is useful for mounting filesystems (such as CDROMs) when a - connection is opened.

    See also preexec and preexec close.

    Default: root preexec = <empty string> -

    >root preexec close (S)

    This is the same as the preexec close - parameter except that the command is run as root.

    See also preexec and preexec close.

    Default: root preexec close = no

    >security (G)

    This option affects how clients respond to - Samba and is one of the most important settings in the smb.conf file.

    The option sets the "security mode bit" in replies to - protocol negotiations with smbd(8) to turn share level security on or off. Clients decide - based on this bit whether (and how) to transfer user and password - information to the server.

    The default is security = user, as this is - the most common setting needed when talking to Windows 98 and - Windows NT.

    The alternatives are security = share, - security = server or security = domain - .

    In versions of Samba prior to 2.0.0, the default was - security = share mainly because that was - the only option at one stage.

    There is a bug in WfWg that has relevance to this - setting. When in user or server level security a WfWg client - will totally ignore the password you type in the "connect - drive" dialog box. This makes it very difficult (if not impossible) - to connect to a Samba service as anyone except the user that - you are logged into WfWg as.

    If your PCs use usernames that are the same as their - usernames on the UNIX machine then you will want to use - security = user. If you mostly use usernames - that don't exist on the UNIX box then use security = - share.

    You should also use security = share if you - want to mainly setup shares without a password (guest shares). This - is commonly used for a shared printer server. It is more difficult - to setup guest shares with security = user, see - the map to guest - parameter for details.

    It is possible to use smbd in a hybrid mode where it is offers both user and share - level security under different NetBIOS aliases.

    The different settings will now be explained.

    >SECURITY = SHARE -

    When clients connect to a share level security server they - need not log onto the server with a valid username and password before - attempting to connect to a shared resource (although modern clients - such as Windows 95/98 and Windows NT will send a logon request with - a username but no password when talking to a security = share - server). Instead, the clients send authentication information - (passwords) on a per-share basis, at the time they attempt to connect - to that share.

    Note that smbd ALWAYS - uses a valid UNIX user to act on behalf of the client, even in - security = share level security.

    As clients are not required to send a username to the server - in share level security, smbd uses several - techniques to determine the correct UNIX user to use on behalf - of the client.

    A list of possible UNIX usernames to match with the given - client password is constructed using the following methods :

    • If the guest - only parameter is set, then all the other - stages are missed and only the guest account username is checked. -

    • Is a username is sent with the share connection - request, then this username (after mapping - see username map), - is added as a potential username.

    • If the client did a previous logon - request (the SessionSetup SMB call) then the - username sent in this SMB will be added as a potential username. -

    • The name of the service the client requested is - added as a potential username.

    • The NetBIOS name of the client is added to - the list as a potential username.

    • Any users on the user list are added as potential usernames. -

    If the guest only parameter is - not set, then this list is then tried with the supplied password. - The first user for whom the password matches will be used as the - UNIX user.

    If the guest only parameter is - set, or no username can be determined then if the share is marked - as available to the guest account, then this - guest user will be used, otherwise access is denied.

    Note that it can be very confusing - in share-level security as to which UNIX username will eventually - be used in granting access.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    >SECURITY = USER -

    This is the default security setting in Samba 3.0. - With user-level security a client must first "log-on" with a - valid username and password (which can be mapped using the username map - parameter). Encrypted passwords (see the encrypted passwords parameter) can also - be used in this security mode. Parameters such as user and guest only if set are then applied and - may change the UNIX user to use on this connection, but only after - the user has been successfully authenticated.

    Note that the name of the resource being - requested is not sent to the server until after - the server has successfully authenticated the client. This is why - guest shares don't work in user level security without allowing - the server to automatically map unknown users into the guest account. - See the map to guest - parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    >SECURITY = DOMAIN - -

    This mode will only work correctly if net(8) has been used to add this - machine into a Windows NT Domain. It expects the encrypted passwords - parameter to be set to yes. In this - mode Samba will try to validate the username/password by passing - it to a Windows NT Primary or Backup Domain Controller, in exactly - the same way that a Windows NT Server would do.

    Note that a valid UNIX user must still - exist as well as the account on the Domain Controller to allow - Samba to have a valid UNIX account to map file access to.

    Note that from the client's point - of view security = domain is the same as security = user - . It only affects how the server deals with the authentication, - it does not in any way affect what the client sees.

    Note that the name of the resource being - requested is not sent to the server until after - the server has successfully authenticated the client. This is why - guest shares don't work in user level security without allowing - the server to automatically map unknown users into the guest account. - See the map to guest - parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the password - server parameter and the encrypted passwords - parameter.

    >SECURITY = SERVER -

    In this mode Samba will try to validate the username/password - by passing it to another SMB server, such as an NT box. If this - fails it will revert to security = - user. It expects the encrypted passwords - parameter to be set to - yes, unless the remote server - does not support them. However note - that if encrypted passwords have been negotiated then Samba cannot - revert back to checking the UNIX password file, it must have a valid - smbpasswd file to check users against. See the - documentation file in the docs/ directory - ENCRYPTION.txt for details on how to set this - up.

    Note this mode of operation - has significant pitfalls, due to the fact that is - activly initiates a man-in-the-middle attack on the - remote SMB server. In particular, this mode of - operation can cause significant resource consuption on - the PDC, as it must maintain an active connection for - the duration of the user's session. Furthermore, if - this connection is lost, there is no way to - reestablish it, and futher authenticaions to the Samba - server may fail. (From a single client, till it - disconnects).

    Note that from the client's point of - view security = server is the same as security = user. It only affects how the server deals - with the authentication, it does not in any way affect what the - client sees.

    Note that the name of the resource being - requested is not sent to the server until after - the server has successfully authenticated the client. This is why - guest shares don't work in user level security without allowing - the server to automatically map unknown users into the guest account. - See the map to guest - parameter for details on doing this.

    See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the password - server parameter and the encrypted passwords - parameter.

    Default: security = USER

    Example: security = DOMAIN

    >security mask (S)

    This parameter controls what UNIX permission - bits can be modified when a Windows NT client is manipulating - the UNIX permission on a file using the native NT security - dialog box.

    This parameter is applied as a mask (AND'ed with) to - the changed permission bits, thus preventing any bits not in - this mask from being modified. Essentially, zero bits in this - mask may be treated as a set of bits the user is not allowed - to change.

    If not set explicitly this parameter is 0777, allowing - a user to modify all the user/group/world permissions on a file. -

    Note that users who can access the - Samba server through other means can easily bypass this - restriction, so it is primarily useful for standalone - "appliance" systems. Administrators of most normal systems will - probably want to leave it set to 0777.

    See also the force directory security mode, - directory - security mask, force security mode parameters.

    Default: security mask = 0777

    Example: security mask = 0770

    >server schannel (G)

    This controls whether the server offers or even - demands the use of the netlogon schannel. - server schannel = no does not - offer the schannel, server schannel = - auto offers the schannel but does not - enforce it, and server schannel = - yes denies access if the client is not - able to speak netlogon schannel. This is only the case - for Windows NT4 before SP4.

    Please note that with this set to - no you will have to apply the - WindowsXP requireSignOrSeal-Registry patch found in - the docs/Registry subdirectory.

    Default: server schannel = auto

    Example: server schannel = yes/para> -

    >server string (G)

    This controls what string will show up in the - printer comment box in print manager and next to the IPC connection - in net view. It can be any string that you wish - to show to your users.

    It also sets what will appear in browse lists next - to the machine name.

    A %v will be replaced with the Samba - version number.

    A %h will be replaced with the - hostname.

    Default: server string = Samba %v

    Example: server string = University of GNUs Samba - Server

    >set primary group script (G)

    Thanks to the Posix subsystem in NT a - Windows User has a primary group in addition to the - auxiliary groups. This script sets the primary group - in the unix userdatase when an administrator sets the - primary group from the windows user manager or when - fetching a SAM with net rpc - vampire. %u will be - replaced with the user whose primary group is to be - set. %g will be replaced with - the group to set. - -

    Default: No default value

    Example: set primary group script = /usr/sbin/usermod -g '%g' '%u'

    >set directory (S)

    If set directory = no, then - users of the service may not use the setdir command to change - directory.

    The setdir command is only implemented - in the Digital Pathworks client. See the Pathworks documentation - for details.

    Default: set directory = no

    >share modes (S)

    This enables or disables the honoring of - the share modes during a file open. These - modes are used by clients to gain exclusive read or write access - to a file.

    These open modes are not directly supported by UNIX, so - they are simulated using shared memory, or lock files if your - UNIX doesn't support shared memory (almost all do).

    The share modes that are enabled by this option are - DENY_DOS, DENY_ALL, - DENY_READ, DENY_WRITE, - DENY_NONE and DENY_FCB. -

    This option gives full share compatibility and enabled - by default.

    You should NEVER turn this parameter - off as many Windows applications will break if you do so.

    Default: share modes = yes

    >short preserve case (S)

    This boolean parameter controls if new files - which conform to 8.3 syntax, that is all in upper case and of - suitable length, are created upper case, or if they are forced - to be the default case - . This option can be use with preserve case = yes - to permit long filenames to retain their case, while short - names are lowered.

    See the section on NAME MANGLING.

    Default: short preserve case = yes

    >show add printer wizard (G)

    With the introduction of MS-RPC based printing support - for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will - appear on Samba hosts in the share listing. Normally this folder will - contain an icon for the MS Add Printer Wizard (APW). However, it is - possible to disable this feature regardless of the level of privilege - of the connected user.

    Under normal circumstances, the Windows NT/2000 client will - open a handle on the printer server with OpenPrinterEx() asking for - Administrator privileges. If the user does not have administrative - access on the print server (i.e is not root or a member of the - printer admin group), the OpenPrinterEx() - call fails and the client makes another open call with a request for - a lower privilege level. This should succeed, however the APW - icon will not be displayed.

    Disabling the show add printer wizard - parameter will always cause the OpenPrinterEx() on the server - to fail. Thus the APW icon will never be displayed. Note :This does not prevent the same user from having - administrative privilege on an individual printer.

    See also addprinter - command, deleteprinter command, printer admin

    Default :show add printer wizard = yes

    >shutdown script (G)

    This parameter only exists in the HEAD cvs branch - This a full path name to a script called by - smbd(8) that - should start a shutdown procedure.

    This command will be run as the user connected to the - server.

    %m %t %r %f parameters are expanded

    %m will be substituted with the - shutdown message sent to the server.

    %t will be substituted with the - number of seconds to wait before effectively starting the - shutdown procedure.

    %r will be substituted with the - switch -r. It means reboot after shutdown - for NT. -

    %f will be substituted with the - switch -f. It means force the shutdown - even if applications do not respond for NT.

    Default: None.

    Example: abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f

    Shutdown script example: -

    #!/bin/bash
+print5|My Printer 5
+

    where the '|' separates aliases of a printer. The fact + that the second alias has a space in it gives a hint to Samba + that it's a comment.

    Note

    Under AIX the default printcap + name is /etc/qconfig. Samba will assume the + file is in AIX qconfig format if the string + qconfig appears in the printcap filename.

    Default: printcap name = /etc/printcap

    Example: printcap name = /etc/myprintcap

    printcap (G)

    Synonym for + printcap name.

    print command (S)

    After a print job has finished spooling to + a service, this command will be used via a system() + call to process the spool file. Typically the command specified will + submit the spool file to the host's printing subsystem, but there + is no requirement that this be the case. The server will not remove + the spool file, so whatever command you specify should remove the + spool file when it has been processed, otherwise you will need to + manually remove old spool files.

    The print command is simply a text string. It will be used + verbatim after macro substitutions have been made:

    %s, %p - the path to the spool + file name

    %p - the appropriate printer + name

    %J - the job + name as transmitted by the client.

    %c - The number of printed pages + of the spooled job (if known).

    %z - the size of the spooled + print job (in bytes)

    The print command MUST contain at least + one occurrence of %s or %f + - the %p is optional. At the time + a job is submitted, if no printer name is supplied the %p + will be silently removed from the printer command.

    If specified in the [global] section, the print command given + will be used for any printable service that does not have its own + print command specified.

    If there is neither a specified print command for a + printable service nor a global print command, spool files will + be created but not processed and (most importantly) not removed.

    Note that printing may fail on some UNIXes from the + nobody account. If this happens then create + an alternative guest account that can print and set the + guest account + in the [global] section.

    You can form quite complex print commands by realizing + that they are just passed to a shell. For example the following + will log a print job, print the file, then remove it. Note that + ';' is the usual separator for command in shell scripts.

    print command = echo Printing %s >> + /tmp/print.log; lpr -P %p %s; rm %s

    You may have to vary this command considerably depending + on how you normally print files on your system. The default for + the parameter varies depending on the setting of the + printing parameter.

    Default: For printing = BSD, AIX, QNX, LPRNG + or PLP :

    print command = lpr -r -P%p %s

    For printing = SYSV or HPUX :

    print command = lp -c -d%p %s; rm %s

    For printing = SOFTQ :

    print command = lp -d%p -s %s; rm %s

    For printing = CUPS : If SAMBA is compiled against + libcups, then printcap = cups + uses the CUPS API to + submit jobs, etc. Otherwise it maps to the System V + commands with the -oraw option for printing, i.e. it + uses lp -c -d%p -oraw; rm %s. + With printing = cups, + and if SAMBA is compiled against libcups, any manually + set print command will be ignored.

    Example: print command = /usr/local/samba/bin/myprintscript %p %s

    printer admin (S)

    This is a list of users that can do anything to + printers via the remote administration interfaces offered by MS-RPC + (usually using a NT workstation). Note that the root user always + has admin rights.

    Default: printer admin = <empty string>

    Example: printer admin = admin, @staff

    printer name (S)

    This parameter specifies the name of the printer + to which print jobs spooled through a printable service will be sent.

    If specified in the [global] section, the printer + name given will be used for any printable service that does + not have its own printer name specified.

    Default: none (but may be lp + on many systems)

    Example: printer name = laserwriter

    printer (S)

    Synonym for + printer name.

    printing (S)

    This parameters controls how printer status information is + interpreted on your system. It also affects the default values for + the print command, lpq command, lppause command , lpresume command, and lprm command if specified in the + [global] section.

    Currently nine printing styles are supported. They are + BSD, AIX, + LPRNG, PLP, + SYSV, HPUX, + QNX, SOFTQ, + and CUPS.

    To see what the defaults are for the other print + commands when using the various options use the testparm(1) program.

    This option can be set on a per printer basis

    See also the discussion in the + [printers] section.

    print ok (S)

    Synonym for + printable.

    private dir (G)

    This parameters defines the directory + smbd will use for storing such files as smbpasswd + and secrets.tdb. +

    Default :private dir = ${prefix}/private

    protocol (G)

    Synonym for + max protocol.

    public (S)

    Synonym for guest + ok.

    queuepause command (S)

    This parameter specifies the command to be + executed on the server host in order to pause the printer queue.

    This command should be a program or script which takes + a printer name as its only parameter and stops the printer queue, + such that no longer jobs are submitted to the printer.

    This command is not supported by Windows for Workgroups, + but can be issued from the Printers window under Windows 95 + and NT.

    If a %p is given then the printer name + is put in its place. Otherwise it is placed at the end of the command. +

    Note that it is good practice to include the absolute + path in the command as the PATH may not be available to the + server.

    Default: depends on the setting of printing

    Example: queuepause command = disable %p

    queueresume command (S)

    This parameter specifies the command to be + executed on the server host in order to resume the printer queue. It + is the command to undo the behavior that is caused by the + previous parameter ( + queuepause command).

    This command should be a program or script which takes + a printer name as its only parameter and resumes the printer queue, + such that queued jobs are resubmitted to the printer.

    This command is not supported by Windows for Workgroups, + but can be issued from the Printers window under Windows 95 + and NT.

    If a %p is given then the printer name + is put in its place. Otherwise it is placed at the end of the + command.

    Note that it is good practice to include the absolute + path in the command as the PATH may not be available to the + server.

    Default: depends on the setting of + printing

    Example: queuepause command = enable %p

    read bmpx (G)

    This boolean parameter controls whether + smbd(8) will support the "Read + Block Multiplex" SMB. This is now rarely used and defaults to + no. You should never need to set this + parameter.

    Default: read bmpx = no

    read list (S)

    This is a list of users that are given read-only + access to a service. If the connecting user is in this list then + they will not be given write access, no matter what the + read only + option is set to. The list can include group names using the + syntax described in the + invalid users parameter.

    See also the + write list parameter and the + invalid users + parameter.

    Default: read list = <empty string>

    Example: read list = mary, @students

    read only (S)

    An inverted synonym is + writeable.

    If this parameter is yes, then users + of a service may not create or modify files in the service's + directory.

    Note that a printable service (printable = yes) + will ALWAYS allow writing to the directory + (user privileges permitting), but only via spooling operations.

    Default: read only = yes

    read raw (G)

    This parameter controls whether or not the server + will support the raw read SMB requests when transferring data + to clients.

    If enabled, raw reads allow reads of 65535 bytes in + one packet. This typically provides a major performance benefit. +

    However, some clients either negotiate the allowable + block size incorrectly or are incapable of supporting larger block + sizes, and for these clients you may need to disable raw reads.

    In general this parameter should be viewed as a system tuning + tool and left severely alone. See also + write raw.

    Default: read raw = yes

    read size (G)

    The option read size + affects the overlap of disk reads/writes with network reads/writes. + If the amount of data being transferred in several of the SMB + commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger + than this value then the server begins writing the data before it + has received the whole packet from the network, or in the case of + SMBreadbraw, it begins writing to the network before all the data + has been read from disk.

    This overlapping works best when the speeds of disk and + network access are similar, having very little effect when the + speed of one is much greater than the other.

    The default value is 16384, but very little experimentation + has been done yet to determine the optimal value, and it is likely + that the best value will vary greatly between systems anyway. + A value over 65536 is pointless and will cause you to allocate + memory unnecessarily.

    Default: read size = 16384

    Example: read size = 8192

    realm (G)

    This option specifies the kerberos realm to use. The realm is + used as the ADS equivalent of the NT4 domain. It + is usually set to the DNS name of the kerberos server. +

    Default: realm =

    Example: realm = mysambabox.mycompany.com

    remote announce (G)

    This option allows you to setup nmbd(8)to periodically announce itself + to arbitrary IP addresses with an arbitrary workgroup name.

    This is useful if you want your Samba server to appear + in a remote workgroup for which the normal browse propagation + rules don't work. The remote workgroup can be anywhere that you + can send IP packets to.

    For example:

    remote announce = 192.168.2.255/SERVERS + 192.168.4.255/STAFF

    the above line would cause nmbd to announce itself + to the two given IP addresses using the given workgroup names. + If you leave out the workgroup name then the one given in + the workgroup + parameter is used instead.

    The IP addresses you choose would normally be the broadcast + addresses of the remote networks, but can also be the IP addresses + of known browse masters if your network config is that stable.

    See the documentation file BROWSING + in the docs/ directory.

    Default: remote announce = <empty string>

    remote browse sync (G)

    This option allows you to setup nmbd(8) to periodically request + synchronization of browse lists with the master browser of a Samba + server that is on a remote segment. This option will allow you to + gain browse lists for multiple workgroups across routed networks. This + is done in a manner that does not work with any non-Samba servers.

    This is useful if you want your Samba server and all local + clients to appear in a remote workgroup for which the normal browse + propagation rules don't work. The remote workgroup can be anywhere + that you can send IP packets to.

    For example:

    remote browse sync = 192.168.2.255 192.168.4.255

    the above line would cause nmbd to request + the master browser on the specified subnets or addresses to + synchronize their browse lists with the local server.

    The IP addresses you choose would normally be the broadcast + addresses of the remote networks, but can also be the IP addresses + of known browse masters if your network config is that stable. If + a machine IP address is given Samba makes NO attempt to validate + that the remote machine is available, is listening, nor that it + is in fact the browse master on its segment.

    Default: remote browse sync = <empty string>

    restrict anonymous (G)

    This is a integer parameter, and mirrors as much as possible the functinality the + RestrictAnonymous registry key does on NT/Win2k. +

    Default: restrict anonymous = 0

    root directory (G)

    The server will chroot() (i.e. + Change its root directory) to this directory on startup. This is + not strictly necessary for secure operation. Even without it the + server will deny access to files not in one of the service entries. + It may also check for, and deny access to, soft links to other + parts of the filesystem, or attempts to use ".." in file names + to access other directories (depending on the setting of the + wide links + parameter). +

    Adding a root directory entry other + than "/" adds an extra level of security, but at a price. It + absolutely ensures that no access is given to files not in the + sub-tree specified in the root directory + option, including some files needed for + complete operation of the server. To maintain full operability + of the server you will need to mirror some system files + into the root directory tree. In particular + you will need to mirror /etc/passwd (or a + subset of it), and any binaries or configuration files needed for + printing (if required). The set of files that must be mirrored is + operating system dependent.

    Default: root directory = /

    Example: root directory = /homes/smb

    root dir (G)

    Synonym for + root directory". +

    root postexec (S)

    This is the same as the postexec + parameter except that the command is run as root. This + is useful for unmounting filesystems + (such as CDROMs) after a connection is closed.

    See also + postexec.

    Default: root postexec = <empty string>

    root preexec close (S)

    This is the same as the preexec close + parameter except that the command is run as root.

    See also + preexec and + preexec close.

    Default: root preexec close = no

    root preexec (S)

    This is the same as the preexec + parameter except that the command is run as root. This + is useful for mounting filesystems (such as CDROMs) when a + connection is opened.

    See also + preexec and + preexec close.

    Default: root preexec = <empty string>

    root (G)

    Synonym for + root directory". +

    security mask (S)

    This parameter controls what UNIX permission + bits can be modified when a Windows NT client is manipulating + the UNIX permission on a file using the native NT security + dialog box.

    This parameter is applied as a mask (AND'ed with) to + the changed permission bits, thus preventing any bits not in + this mask from being modified. Essentially, zero bits in this + mask may be treated as a set of bits the user is not allowed + to change.

    If not set explicitly this parameter is 0777, allowing + a user to modify all the user/group/world permissions on a file. +

    Note that users who can access the + Samba server through other means can easily bypass this + restriction, so it is primarily useful for standalone + "appliance" systems. Administrators of most normal systems will + probably want to leave it set to 0777.

    See also the + force directory security mode, + directory + security mask, + force security mode parameters.

    Default: security mask = 0777

    Example: security mask = 0770

    security (G)

    This option affects how clients respond to + Samba and is one of the most important settings in the + smb.conf file.

    The option sets the "security mode bit" in replies to + protocol negotiations with smbd(8) to turn share level security on or off. Clients decide + based on this bit whether (and how) to transfer user and password + information to the server.

    The default is security = user, as this is + the most common setting needed when talking to Windows 98 and + Windows NT.

    The alternatives are security = share, + security = server or security = domain + .

    In versions of Samba prior to 2.0.0, the default was + security = share mainly because that was + the only option at one stage.

    There is a bug in WfWg that has relevance to this + setting. When in user or server level security a WfWg client + will totally ignore the password you type in the "connect + drive" dialog box. This makes it very difficult (if not impossible) + to connect to a Samba service as anyone except the user that + you are logged into WfWg as.

    If your PCs use usernames that are the same as their + usernames on the UNIX machine then you will want to use + security = user. If you mostly use usernames + that don't exist on the UNIX box then use security = + share.

    You should also use security = share if you + want to mainly setup shares without a password (guest shares). This + is commonly used for a shared printer server. It is more difficult + to setup guest shares with security = user, see + the map to guest + parameter for details.

    It is possible to use smbd in a + hybrid mode where it is offers both user and share + level security under different + NetBIOS aliases.

    The different settings will now be explained.

    SECURITY = SHARE

    When clients connect to a share level security server they + need not log onto the server with a valid username and password before + attempting to connect to a shared resource (although modern clients + such as Windows 95/98 and Windows NT will send a logon request with + a username but no password when talking to a security = share + server). Instead, the clients send authentication information + (passwords) on a per-share basis, at the time they attempt to connect + to that share.

    Note that smbd ALWAYS + uses a valid UNIX user to act on behalf of the client, even in + security = share level security.

    As clients are not required to send a username to the server + in share level security, smbd uses several + techniques to determine the correct UNIX user to use on behalf + of the client.

    A list of possible UNIX usernames to match with the given + client password is constructed using the following methods :

    • If the guest + only parameter is set, then all the other + stages are missed and only the + guest account username is checked. +

    • Is a username is sent with the share connection + request, then this username (after mapping - see + username map), + is added as a potential username. +

    • If the client did a previous logon + request (the SessionSetup SMB call) then the + username sent in this SMB will be added as a potential username. +

    • The name of the service the client requested is + added as a potential username. +

    • The NetBIOS name of the client is added to + the list as a potential username. +

    • Any users on the + user list are added as potential usernames. +

    If the guest only parameter is + not set, then this list is then tried with the supplied password. + The first user for whom the password matches will be used as the + UNIX user.

    If the guest only parameter is + set, or no username can be determined then if the share is marked + as available to the guest account, then this + guest user will be used, otherwise access is denied.

    Note that it can be very confusing + in share-level security as to which UNIX username will eventually + be used in granting access.

    See also the section + NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    SECURITY = USER

    This is the default security setting in Samba 3.0. + With user-level security a client must first "log-on" with a + valid username and password (which can be mapped using the + username map + parameter). Encrypted passwords (see the + encrypted passwords parameter) can also + be used in this security mode. Parameters such as + user and + guest only if set are then applied and + may change the UNIX user to use on this connection, but only after + the user has been successfully authenticated.

    Note that the name of the resource being + requested is not sent to the server until after + the server has successfully authenticated the client. This is why + guest shares don't work in user level security without allowing + the server to automatically map unknown users into the + guest account. + See the map to guest + parameter for details on doing this.

    See also the section + NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    SECURITY = DOMAIN

    This mode will only work correctly if net(8) has been used to add this + machine into a Windows NT Domain. It expects the + encrypted passwords + parameter to be set to yes. In this + mode Samba will try to validate the username/password by passing + it to a Windows NT Primary or Backup Domain Controller, in exactly + the same way that a Windows NT Server would do.

    Note that a valid UNIX user must still + exist as well as the account on the Domain Controller to allow + Samba to have a valid UNIX account to map file access to.

    Note that from the client's point + of view security = domain is the same + as security = user. It only + affects how the server deals with the authentication, + it does not in any way affect what the client sees.

    Note that the name of the resource being + requested is not sent to the server until after + the server has successfully authenticated the client. This is why + guest shares don't work in user level security without allowing + the server to automatically map unknown users into the + guest account. + See the map to guest + parameter for details on doing this.

    See also the section + NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the password + server parameter and the + encrypted passwords + parameter.

    SECURITY = SERVER

    In this mode Samba will try to validate the username/password + by passing it to another SMB server, such as an NT box. If this + fails it will revert to security = + user. It expects the + encrypted passwords parameter + to be set to yes, unless the remote server + does not support them. However note that if encrypted passwords have been + negotiated then Samba cannot revert back to checking the UNIX password file, + it must have a valid smbpasswd file to check + users against. See the documentation file in the docs/ directory + ENCRYPTION.txt for details on how to set this up.

    Note this mode of operation has + significant pitfalls, due to the fact that is activly initiates a + man-in-the-middle attack on the remote SMB server. In particular, + this mode of operation can cause significant resource consuption on + the PDC, as it must maintain an active connection for the duration + of the user's session. Furthermore, if this connection is lost, + there is no way to reestablish it, and futher authenticaions to the + Samba server may fail. (From a single client, till it disconnects). +

    Note that from the client's point of + view security = server is the + same as security = user. It + only affects how the server deals with the authentication, it does + not in any way affect what the client sees.

    Note that the name of the resource being + requested is not sent to the server until after + the server has successfully authenticated the client. This is why + guest shares don't work in user level security without allowing + the server to automatically map unknown users into the + guest account. + See the map to guest + parameter for details on doing this.

    See also the section + NOTE ABOUT USERNAME/PASSWORD VALIDATION.

    See also the password + server parameter and the + encrypted passwords parameter.

    Default: security = USER

    Example: security = DOMAIN

    server schannel (G)

    This controls whether the server offers or even + demands the use of the netlogon schannel. + server schannel = no does not + offer the schannel, server schannel = + auto offers the schannel but does not + enforce it, and server schannel = + yes denies access if the client is not + able to speak netlogon schannel. This is only the case + for Windows NT4 before SP4.

    Please note that with this set to + no you will have to apply the + WindowsXP requireSignOrSeal-Registry patch found in + the docs/Registry subdirectory.

    Default: server schannel = auto

    Example: server schannel = yes

    server string (G)

    This controls what string will show up in the printer comment box in print + manager and next to the IPC connection in net view. It + can be any string that you wish to show to your users.

    It also sets what will appear in browse lists next + to the machine name.

    A %v will be replaced with the Samba + version number.

    A %h will be replaced with the + hostname.

    Default: server string = Samba %v

    Example: server string = University of GNUs Samba + Server

    set directory (S)

    If set directory = no, then + users of the service may not use the setdir command to change + directory.

    The setdir command is only implemented + in the Digital Pathworks client. See the Pathworks documentation + for details.

    Default: set directory = no

    set primary group script (G)

    Thanks to the Posix subsystem in NT a Windows User has a + primary group in addition to the auxiliary groups. This script + sets the primary group in the unix userdatase when an + administrator sets the primary group from the windows user + manager or when fetching a SAM with net rpc + vampire. %u will be replaced + with the user whose primary group is to be set. + %g will be replaced with the group to + set.

    Default: No default value

    Example: set primary group script = /usr/sbin/usermod -g '%g' '%u'

    share modes (S)

    This enables or disables the honoring of + the share modes during a file open. These + modes are used by clients to gain exclusive read or write access + to a file.

    These open modes are not directly supported by UNIX, so + they are simulated using shared memory, or lock files if your + UNIX doesn't support shared memory (almost all do).

    The share modes that are enabled by this option are + DENY_DOS, DENY_ALL, + DENY_READ, DENY_WRITE, + DENY_NONE and DENY_FCB. +

    This option gives full share compatibility and enabled + by default.

    You should NEVER turn this parameter + off as many Windows applications will break if you do so.

    Default: share modes = yes

    short preserve case (S)

    This boolean parameter controls if new files + which conform to 8.3 syntax, that is all in upper case and of + suitable length, are created upper case, or if they are forced + to be the default case + . This option can be use with preserve case = yes + to permit long filenames to retain their case, while short + names are lowered.

    See the section on NAME MANGLING.

    Default: short preserve case = yes

    show add printer wizard (G)

    With the introduction of MS-RPC based printing support + for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will + appear on Samba hosts in the share listing. Normally this folder will + contain an icon for the MS Add Printer Wizard (APW). However, it is + possible to disable this feature regardless of the level of privilege + of the connected user.

    Under normal circumstances, the Windows NT/2000 client will + open a handle on the printer server with OpenPrinterEx() asking for + Administrator privileges. If the user does not have administrative + access on the print server (i.e is not root or a member of the + printer admin group), the OpenPrinterEx() + call fails and the client makes another open call with a request for + a lower privilege level. This should succeed, however the APW + icon will not be displayed.

    Disabling the show add printer wizard + parameter will always cause the OpenPrinterEx() on the server + to fail. Thus the APW icon will never be displayed. + Note :This does not prevent the same user from having + administrative privilege on an individual printer.

    See also addprinter + command, + deleteprinter command, + printer admin

    Default :show add printer wizard = yes

    shutdown script (G)

    This parameter only exists in the HEAD cvs branch + This a full path name to a script called by smbd(8) that should start a shutdown procedure.

    This command will be run as the user connected to the server.

    %m %t %r %f parameters are expanded:

    • %m will be substituted with the + shutdown message sent to the server.

    • %t will be substituted with the + number of seconds to wait before effectively starting the + shutdown procedure.

    • %r will be substituted with the + switch -r. It means reboot after shutdown + for NT.

    • %f will be substituted with the + switch -f. It means force the shutdown + even if applications do not respond for NT.

    Default: None.

    Example: abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f

    Shutdown script example: +

    +#!/bin/bash
 		
 $time=0
-let "time/60"
-let "time++"
+let "time/60"
+let "time++"
 
-/sbin/shutdown $3 $4 +$time $1 &
    - Shutdown does not return so we need to launch it in background. -

    See also abort shutdown script.

    >smb passwd file (G)

    This option sets the path to the encrypted - smbpasswd file. By default the path to the smbpasswd file - is compiled into Samba.

    Default: smb passwd file = ${prefix}/private/smbpasswd -

    Example: smb passwd file = /etc/samba/smbpasswd -

    >smb ports (G)

    Specifies which ports the server should listen on - for SMB traffic. -

    Default: smb ports = 445 139

    >socket address (G)

    This option allows you to control what - address Samba will listen for connections on. This is used to - support multiple virtual interfaces on the one server, each - with a different configuration.

    By default Samba will accept connections on any - address.

    Example: socket address = 192.168.2.20 -

    >socket options (G)

    This option allows you to set socket options - to be used when talking with the client.

    Socket options are controls on the networking layer - of the operating systems which allow the connection to be - tuned.

    This option will typically be used to tune your Samba - server for optimal performance for your local network. There is - no way that Samba can know what the optimal parameters are for - your net, so you must experiment and choose them yourself. We - strongly suggest you read the appropriate documentation for your - operating system first (perhaps man setsockopt - will help).

    You may find that on some systems Samba will say - "Unknown socket option" when you supply an option. This means you - either incorrectly typed it or you need to add an include file - to includes.h for your OS. If the latter is the case please - send the patch to samba@samba.org.

    Any of the supported socket options may be combined - in any way you like, as long as your OS allows it.

    This is the list of socket options currently settable - using this option:

    • SO_KEEPALIVE

    • SO_REUSEADDR

    • SO_BROADCAST

    • TCP_NODELAY

    • IPTOS_LOWDELAY

    • IPTOS_THROUGHPUT

    • SO_SNDBUF *

    • SO_RCVBUF *

    • SO_SNDLOWAT *

    • SO_RCVLOWAT *

    Those marked with a '*' take an integer - argument. The others can optionally take a 1 or 0 argument to enable - or disable the option, by default they will be enabled if you - don't specify 1 or 0.

    To specify an argument use the syntax SOME_OPTION = VALUE - for example SO_SNDBUF = 8192. Note that you must - not have any spaces before or after the = sign.

    If you are on a local network then a sensible option - might be

    socket options = IPTOS_LOWDELAY

    If you have a local network then you could try:

    socket options = IPTOS_LOWDELAY TCP_NODELAY

    If you are on a wide area network then perhaps try - setting IPTOS_THROUGHPUT.

    Note that several of the options may cause your Samba - server to fail completely. Use these options with caution!

    Default: socket options = TCP_NODELAY

    Example: socket options = IPTOS_LOWDELAY

    >source environment (G)

    This parameter causes Samba to set environment - variables as per the content of the file named.

    If the value of this parameter starts with a "|" character - then Samba will treat that value as a pipe command to open and - will set the environment variables from the output of the pipe.

    The contents of the file or the output of the pipe should - be formatted as the output of the standard Unix env(1) - command. This is of the form :

    Example environment entry:

    SAMBA_NETBIOS_NAME = myhostname

    Default: No default value

    Examples: source environment = |/etc/smb.conf.sh -

    Example: source environment = - /usr/local/smb_env_vars

    >use spnego (G)

    This variable controls controls whether samba will try - to use Simple and Protected NEGOciation (as specified by rfc2478) with - WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. - Unless further issues are discovered with our SPNEGO - implementation, there is no reason this should ever be - disabled.

    Default: use spnego = yes

    >stat cache (G)

    This parameter determines if smbd(8) will use a cache in order to - speed up case insensitive name mappings. You should never need - to change this parameter.

    Default: stat cache = yes

    >stat cache size (G)

    This parameter determines the number of - entries in the stat cache. You should - never need to change this parameter.

    Default: stat cache size = 50

    >strict allocate (S)

    This is a boolean that controls the handling of - disk space allocation in the server. When this is set to yes - the server will change from UNIX behaviour of not committing real - disk storage blocks when a file is extended to the Windows behaviour - of actually forcing the disk system to allocate real storage blocks - when a file is created or extended to be a given size. In UNIX - terminology this means that Samba will stop creating sparse files. - This can be slow on some systems.

    When strict allocate is no the server does sparse - disk block allocation when a file is extended.

    Setting this to yes can help Samba return - out of quota messages on systems that are restricting the disk quota - of users.

    Default: strict allocate = no

    >strict locking (S)

    This is a boolean that controls the handling of - file locking in the server. When this is set to yes - the server will check every read and write access for file locks, and - deny access if locks exist. This can be slow on some systems.

    When strict locking is no the server does file - lock checks only when the client explicitly asks for them.

    Well-behaved clients always ask for lock checks when it - is important, so in the vast majority of cases strict - locking = no is preferable.

    Default: strict locking = no

    >strict sync (S)

    Many Windows applications (including the Windows - 98 explorer shell) seem to confuse flushing buffer contents to - disk with doing a sync to disk. Under UNIX, a sync call forces - the process to be suspended until the kernel has ensured that - all outstanding data in kernel disk buffers has been safely stored - onto stable storage. This is very slow and should only be done - rarely. Setting this parameter to no (the - default) means that smbd(8) ignores the Windows applications requests for - a sync call. There is only a possibility of losing data if the - operating system itself that Samba is running on crashes, so there is - little danger in this default setting. In addition, this fixes many - performance problems that people have reported with the new Windows98 - explorer shell file copies.

    See also the sync - always> parameter.

    Default: strict sync = no

    >strip dot (G)

    This is a boolean that controls whether to - strip trailing dots off UNIX filenames. This helps with some - CDROMs that have filenames ending in a single dot.

    Default: strip dot = no

    >sync always (S)

    This is a boolean parameter that controls - whether writes will always be written to stable storage before - the write call returns. If this is no then the server will be - guided by the client's request in each write call (clients can - set a bit indicating that a particular write should be synchronous). - If this is yes then every write will be followed by a fsync() - call to ensure the data is written to disk. Note that - the strict sync parameter must be set to - yes in order for this parameter to have - any affect.

    See also the strict - sync parameter.

    Default: sync always = no

    >syslog (G)

    This parameter maps how Samba debug messages - are logged onto the system syslog logging levels. Samba debug - level zero maps onto syslog LOG_ERR, debug - level one maps onto LOG_WARNING, debug level - two maps onto LOG_NOTICE, debug level three - maps onto LOG_INFO. All higher levels are mapped to LOG_DEBUG.

    This parameter sets the threshold for sending messages - to syslog. Only messages with debug level less than this value - will be sent to syslog.

    Default: syslog = 1

    >syslog only (G)

    If this parameter is set then Samba debug - messages are logged into the system syslog only, and not to - the debug log files.

    Default: syslog only = no

    >template homedir (G)

    When filling out the user information for a Windows NT - user, the winbindd(8) daemon - uses this parameter to fill in the home directory for that user. - If the string %D is present it is substituted - with the user's Windows NT domain name. If the string %U - is present it is substituted with the user's Windows - NT user name.

    Default: template homedir = /home/%D/%U

    >template shell (G)

    When filling out the user information for a Windows NT - user, the winbindd(8) daemon - uses this parameter to fill in the login shell for that user.

    Default: template shell = /bin/false

    >time offset (G)

    This parameter is a setting in minutes to add - to the normal GMT to local time conversion. This is useful if - you are serving a lot of PCs that have incorrect daylight - saving time handling.

    Default: time offset = 0

    Example: time offset = 60

    >time server (G)

    This parameter determines if nmbd(8) advertises itself as a time server to Windows - clients.

    Default: time server = no

    >timestamp logs (G)

    Synonym for debug timestamp.

    >total print jobs (G)

    This parameter accepts an integer value which defines - a limit on the maximum number of print jobs that will be accepted - system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbd(8) will return an - error indicating that no space is available on the server. The - default value of 0 means that no such limit exists. This parameter - can be used to prevent a server from exceeding its capacity and is - designed as a printing throttle. See also - max print jobs. -

    Default: total print jobs = 0

    Example: total print jobs = 5000

    >unicode (G)

    Specifies whether Samba should try - to use unicode on the wire by default. Note: This does NOT - mean that samba will assume that the unix machine uses unicode! -

    Default: unicode = yes

    >unix charset (G)

    Specifies the charset the unix machine - Samba runs on uses. Samba needs to know this in order to be able to - convert text to the charsets other SMB clients use. -

    Default: unix charset = UTF8

    Example: unix charset = ASCII

    >unix extensions(G)

    This boolean parameter controls whether Samba - implments the CIFS UNIX extensions, as defined by HP. - These extensions enable Samba to better serve UNIX CIFS clients - by supporting features such as symbolic links, hard links, etc... - These extensions require a similarly enabled client, and are of - no current use to Windows clients.

    Default: unix extensions = no

    >unix password sync (G)

    This boolean parameter controls whether Samba - attempts to synchronize the UNIX password with the SMB password - when the encrypted SMB password in the smbpasswd file is changed. - If this is set to yes the program specified in the passwd - programparameter is called AS ROOT - - to allow the new UNIX password to be set without access to the - old UNIX password (as the SMB password change code has no - access to the old password cleartext, only the new).

    See also passwd - program, passwd chat.

    Default: unix password sync = no

    >update encrypted (G)

    This boolean parameter allows a user logging - on with a plaintext password to have their encrypted (hashed) - password in the smbpasswd file to be updated automatically as - they log on. This option allows a site to migrate from plaintext - password authentication (users authenticate with plaintext - password over the wire, and are checked against a UNIX account - database) to encrypted password authentication (the SMB - challenge/response authentication mechanism) without forcing - all users to re-enter their passwords via smbpasswd at the time the - change is made. This is a convenience option to allow the change over - to encrypted passwords to be made over a longer period. Once all users - have encrypted representations of their passwords in the smbpasswd - file this parameter should be set to no.

    In order for this parameter to work correctly the encrypt passwords - parameter must be set to no when - this parameter is set to yes.

    Note that even when this parameter is set a user - authenticating to smbd must still enter a valid - password in order to connect correctly, and to update their hashed - (smbpasswd) passwords.

    Default: update encrypted = no

    >use client driver (S)

    This parameter applies only to Windows NT/2000 - clients. It has no affect on Windows 95/98/ME clients. When - serving a printer to Windows NT/2000 clients without first installing - a valid printer driver on the Samba host, the client will be required - to install a local printer driver. From this point on, the client - will treat the print as a local printer and not a network printer - connection. This is much the same behavior that will occur - when disable spoolss = yes.

    The differentiating - factor is that under normal circumstances, the NT/2000 client will - attempt to open the network printer using MS-RPC. The problem is that - because the client considers the printer to be local, it will attempt - to issue the OpenPrinterEx() call requesting access rights associated - with the logged on user. If the user possesses local administator rights - but not root privilegde on the Samba host (often the case), the OpenPrinterEx() - call will fail. The result is that the client will now display an "Access - Denied; Unable to connect" message in the printer queue window (even though - jobs may successfully be printed).

    If this parameter is enabled for a printer, then any attempt - to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped - to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() - call to succeed. This parameter MUST not be able enabled - on a print share which has valid print driver installed on the Samba - server.

    See also disable spoolss -

    Default: use client driver = no

    >use mmap (G)

    This global parameter determines if the tdb internals of Samba can - depend on mmap working correctly on the running system. Samba requires a coherent - mmap/read-write system memory cache. Currently only HPUX does not have such a - coherent cache, and so this parameter is set to no by - default on HPUX. On all other systems this parameter should be left alone. This - parameter is provided to help the Samba developers track down problems with - the tdb internal code. -

    Default: use mmap = yes

    >user (S)

    Synonym for username.

    >users (S)

    Synonym for username.

    >username (S)

    Multiple users may be specified in a comma-delimited - list, in which case the supplied password will be tested against - each username in turn (left to right).

    The username line is needed only when - the PC is unable to supply its own username. This is the case - for the COREPLUS protocol or where your users have different WfWg - usernames to UNIX usernames. In both these cases you may also be - better using the \\server\share%user syntax instead.

    The username line is not a great - solution in many cases as it means Samba will try to validate - the supplied password against each of the usernames in the - username line in turn. This is slow and - a bad idea for lots of users in case of duplicate passwords. - You may get timeouts or security breaches using this parameter - unwisely.

    Samba relies on the underlying UNIX security. This - parameter does not restrict who can login, it just offers hints - to the Samba server as to what usernames might correspond to the - supplied password. Users can login as whoever they please and - they will be able to do no more damage than if they started a - telnet session. The daemon runs as the user that they log in as, - so they cannot do anything that user cannot do.

    To restrict a service to a particular set of users you - can use the valid users - parameter.

    If any of the usernames begin with a '@' then the name - will be looked up first in the NIS netgroups list (if Samba - is compiled with netgroup support), followed by a lookup in - the UNIX groups database and will expand to a list of all users - in the group of that name.

    If any of the usernames begin with a '+' then the name - will be looked up only in the UNIX groups database and will - expand to a list of all users in the group of that name.

    If any of the usernames begin with a '&' then the name - will be looked up only in the NIS netgroups database (if Samba - is compiled with netgroup support) and will expand to a list - of all users in the netgroup group of that name.

    Note that searching though a groups database can take - quite some time, and some clients may time out during the - search.

    See the section NOTE ABOUT - USERNAME/PASSWORD VALIDATION for more information on how - this parameter determines access to the services.

    Default: The guest account if a guest service, - else <empty string>.

    Examples:username = fred, mary, jack, jane, - @users, @pcgroup

    >username level (G)

    This option helps Samba to try and 'guess' at - the real UNIX username, as many DOS clients send an all-uppercase - username. By default Samba tries all lowercase, followed by the - username with the first letter capitalized, and fails if the - username is not found on the UNIX machine.

    If this parameter is set to non-zero the behavior changes. - This parameter is a number that specifies the number of uppercase - combinations to try while trying to determine the UNIX user name. The - higher the number the more combinations will be tried, but the slower - the discovery of usernames will be. Use this parameter when you have - strange usernames on your UNIX machine, such as AstrangeUser - .

    Default: username level = 0

    Example: username level = 5

    >username map (G)

    This option allows you to specify a file containing - a mapping of usernames from the clients to the server. This can be - used for several purposes. The most common is to map usernames - that users use on DOS or Windows machines to those that the UNIX - box uses. The other is to map multiple users to a single username - so that they can more easily share files.

    The map file is parsed line by line. Each line should - contain a single UNIX username on the left then a '=' followed - by a list of usernames on the right. The list of usernames on the - right may contain names of the form @group in which case they - will match any UNIX username in that group. The special client - name '*' is a wildcard and matches any name. Each line of the - map file may be up to 1023 characters long.

    The file is processed on each line by taking the - supplied username and comparing it with each username on the right - hand side of the '=' signs. If the supplied name matches any of - the names on the right hand side then it is replaced with the name - on the left. Processing then continues with the next line.

    If any line begins with a '#' or a ';' then it is - ignored

    If any line begins with an '!' then the processing - will stop after that line if a mapping was done by the line. - Otherwise mapping continues with every line being processed. - Using '!' is most useful when you have a wildcard mapping line - later in the file.

    For example to map from the name admin - or administrator to the UNIX name root you would use:

    root = admin administrator

    Or to map anyone in the UNIX group system - to the UNIX name sys you would use:

    sys = @system

    You can have as many mappings as you like in a username - map file.

    If your system supports the NIS NETGROUP option then - the netgroup database is checked before the /etc/group - database for matching groups.

    You can map Windows usernames that have spaces in them - by using double quotes around the name. For example:

    tridge = "Andrew Tridgell"

    would map the windows username "Andrew Tridgell" to the - unix username "tridge".

    The following example would map mary and fred to the - unix user sys, and map the rest to guest. Note the use of the - '!' to tell Samba to stop processing if it gets a match on - that line.

    !sys = mary fred
-guest = *

    Note that the remapping is applied to all occurrences - of usernames. Thus if you connect to \\server\fred and fred is remapped to mary then you - will actually be connecting to \\server\mary and will need to - supply a password suitable for mary not - fred. The only exception to this is the - username passed to the password server (if you have one). The password - server will receive whatever username the client supplies without - modification.

    Also note that no reverse mapping is done. The main effect - this has is with printing. Users who have been mapped may have - trouble deleting print jobs as PrintManager under WfWg will think - they don't own the print job.

    Default: no username map

    Example: username map = /usr/local/samba/lib/users.map -

    >use sendfile (S)

    If this parameter is yes, and Samba - was built with the --with-sendfile-support option, and the underlying operating - system supports sendfile system call, then some SMB read calls (mainly ReadAndX - and ReadRaw) will use the more efficient sendfile system call for files that - are exclusively oplocked. This may make more efficient use of the system CPU's - and cause Samba to be faster. This is off by default as it's effects are unknown - as yet. -

    Default: use sendfile = no

    >utmp (G)

    This boolean parameter is only available if - Samba has been configured and compiled with the option --with-utmp. If set to yes then Samba will attempt - to add utmp or utmpx records (depending on the UNIX system) whenever a - connection is made to a Samba server. Sites may use this to record the - user connecting to a Samba share.

    Due to the requirements of the utmp record, we - are required to create a unique identifier for the - incoming user. Enabling this option creates an n^2 - algorithm to find this number. This may impede - performance on large installations.

    See also the utmp directory parameter.

    Default: utmp = no

    >utmp directory(G)

    This parameter is only available if Samba has - been configured and compiled with the option --with-utmp. It specifies a directory pathname that is - used to store the utmp or utmpx files (depending on the UNIX system) that - record user connections to a Samba server. See also the utmp parameter. By default this is - not set, meaning the system will use whatever utmp file the - native system is set to use (usually - /var/run/utmp on Linux).

    Default: no utmp directory

    Example: utmp directory = /var/run/utmp

    >wtmp directory(G)

    This parameter is only available if Samba has - been configured and compiled with the option --with-utmp. It specifies a directory pathname that is - used to store the wtmp or wtmpx files (depending on the UNIX system) that - record user connections to a Samba server. The difference with - the utmp directory is the fact that user info is kept after a user - has logged out. - - See also the utmp parameter. By default this is - not set, meaning the system will use whatever utmp file the - native system is set to use (usually - /var/run/wtmp on Linux).

    Default: no wtmp directory

    Example: wtmp directory = /var/log/wtmp

    >valid users (S)

    This is a list of users that should be allowed - to login to this service. Names starting with '@', '+' and '&' - are interpreted using the same rules as described in the - invalid users parameter.

    If this is empty (the default) then any user can login. - If a username is in both this list and the invalid - users list then access is denied for that user.

    The current servicename is substituted for %S - . This is useful in the [homes] section.

    See also invalid users -

    Default: No valid users list (anyone can login) -

    Example: valid users = greg, @pcusers

    >veto files(S)

    This is a list of files and directories that - are neither visible nor accessible. Each entry in the list must - be separated by a '/', which allows spaces to be included - in the entry. '*' and '?' can be used to specify multiple files - or directories as in DOS wildcards.

    Each entry must be a unix path, not a DOS path and - must not include the unix directory - separator '/'.

    Note that the case sensitive option - is applicable in vetoing files.

    One feature of the veto files parameter that it - is important to be aware of is Samba's behaviour when - trying to delete a directory. If a directory that is - to be deleted contains nothing but veto files this - deletion will fail unless you also set - the delete veto files parameter to - yes.

    Setting this parameter will affect the performance - of Samba, as it will be forced to check all files and directories - for a match as they are scanned.

    See also hide files - and case sensitive.

    Default: No files or directories are vetoed. -

    Examples:

    ; Veto any files containing the word Security, 
+/sbin/shutdown $3 $4 +$time $1 &
+

    +Shutdown does not return so we need to launch it in background. +

    See also + abort shutdown script.

    smb passwd file (G)

    This option sets the path to the encrypted smbpasswd file. By + default the path to the smbpasswd file is compiled into Samba.

    Default: smb passwd file = ${prefix}/private/smbpasswd

    Example: smb passwd file = /etc/samba/smbpasswd

    smb ports (G)

    Specifies which ports the server should listen on for SMB traffic.

    Default: smb ports = 445 139

    socket address (G)

    This option allows you to control what + address Samba will listen for connections on. This is used to + support multiple virtual interfaces on the one server, each + with a different configuration.

    By default Samba will accept connections on any + address.

    Example: socket address = 192.168.2.20

    socket options (G)

    This option allows you to set socket options + to be used when talking with the client.

    Socket options are controls on the networking layer + of the operating systems which allow the connection to be + tuned.

    This option will typically be used to tune your Samba server + for optimal performance for your local network. There is no way + that Samba can know what the optimal parameters are for your net, + so you must experiment and choose them yourself. We strongly + suggest you read the appropriate documentation for your operating + system first (perhaps man + setsockopt will help).

    You may find that on some systems Samba will say + "Unknown socket option" when you supply an option. This means you + either incorrectly typed it or you need to add an include file + to includes.h for your OS. If the latter is the case please + send the patch to + samba-technical@samba.org.

    Any of the supported socket options may be combined + in any way you like, as long as your OS allows it.

    This is the list of socket options currently settable + using this option:

    • SO_KEEPALIVE

    • SO_REUSEADDR

    • SO_BROADCAST

    • TCP_NODELAY

    • IPTOS_LOWDELAY

    • IPTOS_THROUGHPUT

    • SO_SNDBUF *

    • SO_RCVBUF *

    • SO_SNDLOWAT *

    • SO_RCVLOWAT *

    Those marked with a '*' take an integer + argument. The others can optionally take a 1 or 0 argument to enable + or disable the option, by default they will be enabled if you + don't specify 1 or 0.

    To specify an argument use the syntax SOME_OPTION = VALUE + for example SO_SNDBUF = 8192. Note that you must + not have any spaces before or after the = sign.

    If you are on a local network then a sensible option + might be:

    socket options = IPTOS_LOWDELAY

    If you have a local network then you could try:

    socket options = IPTOS_LOWDELAY TCP_NODELAY

    If you are on a wide area network then perhaps try + setting IPTOS_THROUGHPUT.

    Note that several of the options may cause your Samba + server to fail completely. Use these options with caution!

    Default: socket options = TCP_NODELAY

    Example: socket options = IPTOS_LOWDELAY

    source environment (G)

    This parameter causes Samba to set environment + variables as per the content of the file named.

    If the value of this parameter starts with a "|" character + then Samba will treat that value as a pipe command to open and + will set the environment variables from the output of the pipe.

    The contents of the file or the output of the pipe should + be formatted as the output of the standard Unix env(1) command. This is of the form:

    Example environment entry:

    SAMBA_NETBIOS_NAME = myhostname

    Default: No default value

    Examples: source environment = |/etc/smb.conf.sh

    Example: source environment = + /usr/local/smb_env_vars

    stat cache size (G)

    This parameter determines the number of + entries in the stat cache. You should + never need to change this parameter.

    Default: stat cache size = 50

    stat cache (G)

    This parameter determines if smbd(8) will use a cache in order to + speed up case insensitive name mappings. You should never need + to change this parameter.

    Default: stat cache = yes

    strict allocate (S)

    This is a boolean that controls the handling of + disk space allocation in the server. When this is set to yes + the server will change from UNIX behaviour of not committing real + disk storage blocks when a file is extended to the Windows behaviour + of actually forcing the disk system to allocate real storage blocks + when a file is created or extended to be a given size. In UNIX + terminology this means that Samba will stop creating sparse files. + This can be slow on some systems.

    When strict allocate is no the server does sparse + disk block allocation when a file is extended.

    Setting this to yes can help Samba return + out of quota messages on systems that are restricting the disk quota + of users.

    Default: strict allocate = no

    strict locking (S)

    This is a boolean that controls the handling of + file locking in the server. When this is set to yes + the server will check every read and write access for file locks, and + deny access if locks exist. This can be slow on some systems.

    When strict locking is no the server does file + lock checks only when the client explicitly asks for them.

    Well-behaved clients always ask for lock checks when it + is important, so in the vast majority of cases strict + locking = no is preferable.

    Default: strict locking = no

    strict sync (S)

    Many Windows applications (including the Windows 98 explorer + shell) seem to confuse flushing buffer contents to disk with doing + a sync to disk. Under UNIX, a sync call forces the process to be + suspended until the kernel has ensured that all outstanding data in + kernel disk buffers has been safely stored onto stable storage. + This is very slow and should only be done rarely. Setting this + parameter to no (the default) means that + smbd(8) ignores the Windows + applications requests for a sync call. There is only a possibility + of losing data if the operating system itself that Samba is running + on crashes, so there is little danger in this default setting. In + addition, this fixes many performance problems that people have + reported with the new Windows98 explorer shell file copies.

    See also the sync + always parameter.

    Default: strict sync = no

    strip dot (G)

    This is a boolean that controls whether to + strip trailing dots off UNIX filenames. This helps with some + CDROMs that have filenames ending in a single dot.

    Default: strip dot = no

    sync always (S)

    This is a boolean parameter that controls + whether writes will always be written to stable storage before + the write call returns. If this is no then the server will be + guided by the client's request in each write call (clients can + set a bit indicating that a particular write should be synchronous). + If this is yes then every write will be followed by a fsync() + call to ensure the data is written to disk. Note that + the strict sync parameter must be set to + yes in order for this parameter to have + any affect.

    See also the strict + sync parameter.

    Default: sync always = no

    syslog only (G)

    If this parameter is set then Samba debug + messages are logged into the system syslog only, and not to + the debug log files.

    Default: syslog only = no

    syslog (G)

    This parameter maps how Samba debug messages + are logged onto the system syslog logging levels. Samba debug + level zero maps onto syslog LOG_ERR, debug + level one maps onto LOG_WARNING, debug level + two maps onto LOG_NOTICE, debug level three + maps onto LOG_INFO. All higher levels are mapped to + LOG_DEBUG.

    This parameter sets the threshold for sending messages + to syslog. Only messages with debug level less than this value + will be sent to syslog.

    Default: syslog = 1

    template homedir (G)

    When filling out the user information for a Windows NT + user, the winbindd(8) daemon uses this + parameter to fill in the home directory for that user. If the + string %D is present it + is substituted with the user's Windows NT domain name. If the + string %U is present it + is substituted with the user's Windows NT user name.

    Default: template homedir = /home/%D/%U

    template shell (G)

    When filling out the user information for a Windows NT + user, the winbindd(8) daemon uses this + parameter to fill in the login shell for that user.

    Default: template shell = /bin/false

    time offset (G)

    This parameter is a setting in minutes to add + to the normal GMT to local time conversion. This is useful if + you are serving a lot of PCs that have incorrect daylight + saving time handling.

    Default: time offset = 0

    Example: time offset = 60

    time server (G)

    This parameter determines if nmbd(8) advertises itself as a time server to Windows + clients.

    Default: time server = no

    timestamp logs (G)

    Synonym for + debug timestamp.

    total print jobs (G)

    This parameter accepts an integer value which defines + a limit on the maximum number of print jobs that will be accepted + system wide at any given time. If a print job is submitted + by a client which will exceed this number, then smbd(8) will return an + error indicating that no space is available on the server. The + default value of 0 means that no such limit exists. This parameter + can be used to prevent a server from exceeding its capacity and is + designed as a printing throttle. See also + max print jobs. +

    Default: total print jobs = 0

    Example: total print jobs = 5000

    unicode (G)

    Specifies whether Samba should try + to use unicode on the wire by default. Note: This does NOT + mean that samba will assume that the unix machine uses unicode! +

    Default: unicode = yes

    unix charset (G)

    Specifies the charset the unix machine + Samba runs on uses. Samba needs to know this in order to be able to + convert text to the charsets other SMB clients use. +

    Default: unix charset = UTF8

    Example: unix charset = ASCII

    unix extensions (G)

    This boolean parameter controls whether Samba + implments the CIFS UNIX extensions, as defined by HP. + These extensions enable Samba to better serve UNIX CIFS clients + by supporting features such as symbolic links, hard links, etc... + These extensions require a similarly enabled client, and are of + no current use to Windows clients.

    Default: unix extensions = no

    unix password sync (G)

    This boolean parameter controls whether Samba + attempts to synchronize the UNIX password with the SMB password + when the encrypted SMB password in the smbpasswd file is changed. + If this is set to yes the program specified in the passwd + programparameter is called AS ROOT - + to allow the new UNIX password to be set without access to the + old UNIX password (as the SMB password change code has no + access to the old password cleartext, only the new).

    See also passwd + program, + passwd chat. +

    Default: unix password sync = no

    update encrypted (G)

    This boolean parameter allows a user logging on with + a plaintext password to have their encrypted (hashed) password in + the smbpasswd file to be updated automatically as they log + on. This option allows a site to migrate from plaintext + password authentication (users authenticate with plaintext + password over the wire, and are checked against a UNIX account + database) to encrypted password authentication (the SMB + challenge/response authentication mechanism) without forcing all + users to re-enter their passwords via smbpasswd at the time the + change is made. This is a convenience option to allow the change + over to encrypted passwords to be made over a longer period. + Once all users have encrypted representations of their passwords + in the smbpasswd file this parameter should be set to + no.

    In order for this parameter to work correctly the + encrypt passwords parameter must + be set to no when this parameter is set to yes.

    Note that even when this parameter is set a user + authenticating to smbd must still enter a valid + password in order to connect correctly, and to update their hashed + (smbpasswd) passwords.

    Default: update encrypted = no

    use client driver (S)

    This parameter applies only to Windows NT/2000 + clients. It has no affect on Windows 95/98/ME clients. When + serving a printer to Windows NT/2000 clients without first installing + a valid printer driver on the Samba host, the client will be required + to install a local printer driver. From this point on, the client + will treat the print as a local printer and not a network printer + connection. This is much the same behavior that will occur + when disable spoolss = yes. +

    The differentiating factor is that under normal + circumstances, the NT/2000 client will attempt to open the network + printer using MS-RPC. The problem is that because the client + considers the printer to be local, it will attempt to issue the + OpenPrinterEx() call requesting access rights associated with the + logged on user. If the user possesses local administator rights but + not root privilegde on the Samba host (often the case), the + OpenPrinterEx() call will fail. The result is that the client will + now display an "Access Denied; Unable to connect" message + in the printer queue window (even though jobs may successfully be + printed).

    If this parameter is enabled for a printer, then any attempt + to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped + to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() + call to succeed. This parameter MUST not be able enabled + on a print share which has valid print driver installed on the Samba + server.

    See also disable spoolss

    Default: use client driver = no

    use mmap (G)

    This global parameter determines if the tdb internals of Samba can + depend on mmap working correctly on the running system. Samba requires a coherent + mmap/read-write system memory cache. Currently only HPUX does not have such a + coherent cache, and so this parameter is set to no by + default on HPUX. On all other systems this parameter should be left alone. This + parameter is provided to help the Samba developers track down problems with + the tdb internal code. +

    Default: use mmap = yes

    username level (G)

    This option helps Samba to try and 'guess' at + the real UNIX username, as many DOS clients send an all-uppercase + username. By default Samba tries all lowercase, followed by the + username with the first letter capitalized, and fails if the + username is not found on the UNIX machine.

    If this parameter is set to non-zero the behavior changes. + This parameter is a number that specifies the number of uppercase + combinations to try while trying to determine the UNIX user name. The + higher the number the more combinations will be tried, but the slower + the discovery of usernames will be. Use this parameter when you have + strange usernames on your UNIX machine, such as AstrangeUser + .

    Default: username level = 0

    Example: username level = 5

    username map (G)

    This option allows you to specify a file containing + a mapping of usernames from the clients to the server. This can be + used for several purposes. The most common is to map usernames + that users use on DOS or Windows machines to those that the UNIX + box uses. The other is to map multiple users to a single username + so that they can more easily share files.

    The map file is parsed line by line. Each line should + contain a single UNIX username on the left then a '=' followed + by a list of usernames on the right. The list of usernames on the + right may contain names of the form @group in which case they + will match any UNIX username in that group. The special client + name '*' is a wildcard and matches any name. Each line of the + map file may be up to 1023 characters long.

    The file is processed on each line by taking the + supplied username and comparing it with each username on the right + hand side of the '=' signs. If the supplied name matches any of + the names on the right hand side then it is replaced with the name + on the left. Processing then continues with the next line.

    If any line begins with a '#' or a ';' then it is ignored

    If any line begins with an '!' then the processing + will stop after that line if a mapping was done by the line. + Otherwise mapping continues with every line being processed. + Using '!' is most useful when you have a wildcard mapping line + later in the file.

    For example to map from the name admin + or administrator to the UNIX name + root you would use:

    root = admin administrator

    Or to map anyone in the UNIX group system + to the UNIX name sys you would use:

    sys = @system

    You can have as many mappings as you like in a username map file.

    If your system supports the NIS NETGROUP option then + the netgroup database is checked before the /etc/group + database for matching groups.

    You can map Windows usernames that have spaces in them + by using double quotes around the name. For example:

    tridge = "Andrew Tridgell"

    would map the windows username "Andrew Tridgell" to the + unix username "tridge".

    The following example would map mary and fred to the + unix user sys, and map the rest to guest. Note the use of the + '!' to tell Samba to stop processing if it gets a match on + that line.

    +!sys = mary fred
+guest = *
+

    Note that the remapping is applied to all occurrences + of usernames. Thus if you connect to \\server\fred and + fred is remapped to mary then you + will actually be connecting to \\server\mary and will need to + supply a password suitable for mary not + fred. The only exception to this is the + username passed to the + password server (if you have one). The password + server will receive whatever username the client supplies without + modification.

    Also note that no reverse mapping is done. The main effect + this has is with printing. Users who have been mapped may have + trouble deleting print jobs as PrintManager under WfWg will think + they don't own the print job.

    Default: no username map

    Example: username map = /usr/local/samba/lib/users.map

    username (S)

    Multiple users may be specified in a comma-delimited + list, in which case the supplied password will be tested against + each username in turn (left to right).

    The username line is needed only when + the PC is unable to supply its own username. This is the case + for the COREPLUS protocol or where your users have different WfWg + usernames to UNIX usernames. In both these cases you may also be + better using the \\server\share%user syntax instead.

    The username line is not a great + solution in many cases as it means Samba will try to validate + the supplied password against each of the usernames in the + username line in turn. This is slow and + a bad idea for lots of users in case of duplicate passwords. + You may get timeouts or security breaches using this parameter + unwisely.

    Samba relies on the underlying UNIX security. This + parameter does not restrict who can login, it just offers hints + to the Samba server as to what usernames might correspond to the + supplied password. Users can login as whoever they please and + they will be able to do no more damage than if they started a + telnet session. The daemon runs as the user that they log in as, + so they cannot do anything that user cannot do.

    To restrict a service to a particular set of users you + can use the valid users + parameter.

    If any of the usernames begin with a '@' then the name + will be looked up first in the NIS netgroups list (if Samba + is compiled with netgroup support), followed by a lookup in + the UNIX groups database and will expand to a list of all users + in the group of that name.

    If any of the usernames begin with a '+' then the name + will be looked up only in the UNIX groups database and will + expand to a list of all users in the group of that name.

    If any of the usernames begin with a '&' then the name + will be looked up only in the NIS netgroups database (if Samba + is compiled with netgroup support) and will expand to a list + of all users in the netgroup group of that name.

    Note that searching though a groups database can take + quite some time, and some clients may time out during the + search.

    See the section NOTE ABOUT + USERNAME/PASSWORD VALIDATION for more information on how + this parameter determines access to the services.

    Default: The guest account if a guest service, + else <empty string>.

    Examples:username = fred, mary, jack, jane, + @users, @pcgroup

    users (S)

    Synonym for + username.

    user (S)

    Synonym for username.

    use sendfile (S)

    If this parameter is yes, and Samba + was built with the --with-sendfile-support option, and the underlying operating + system supports sendfile system call, then some SMB read calls (mainly ReadAndX + and ReadRaw) will use the more efficient sendfile system call for files that + are exclusively oplocked. This may make more efficient use of the system CPU's + and cause Samba to be faster. This is off by default as it's effects are unknown + as yet.

    Default: use sendfile = no

    use spnego (G)

    This variable controls controls whether samba will try + to use Simple and Protected NEGOciation (as specified by rfc2478) with + WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. + Unless further issues are discovered with our SPNEGO + implementation, there is no reason this should ever be + disabled.

    Default: use spnego = yes

    utmp directory (G)

    This parameter is only available if Samba has + been configured and compiled with the option + --with-utmp. It specifies a directory pathname that is + used to store the utmp or utmpx files (depending on the UNIX system) that + record user connections to a Samba server. See also the + utmp parameter. By default this is + not set, meaning the system will use whatever utmp file the + native system is set to use (usually + /var/run/utmp on Linux).

    Default: no utmp directory

    Example: utmp directory = /var/run/utmp

    utmp (G)

    This boolean parameter is only available if + Samba has been configured and compiled with the option + --with-utmp. If set to yes then Samba will attempt + to add utmp or utmpx records (depending on the UNIX system) whenever a + connection is made to a Samba server. Sites may use this to record the + user connecting to a Samba share.

    Due to the requirements of the utmp record, we + are required to create a unique identifier for the + incoming user. Enabling this option creates an n^2 + algorithm to find this number. This may impede + performance on large installations.

    See also the + utmp directory parameter.

    Default: utmp = no

    valid users (S)

    This is a list of users that should be allowed + to login to this service. Names starting with '@', '+' and '&' + are interpreted using the same rules as described in the + invalid users parameter.

    If this is empty (the default) then any user can login. + If a username is in both this list and the invalid + users list then access is denied for that user.

    The current servicename is substituted for %S + . This is useful in the [homes] section.

    See also invalid users +

    Default: No valid users list (anyone can login) +

    Example: valid users = greg, @pcusers

    veto files (S)

    This is a list of files and directories that + are neither visible nor accessible. Each entry in the list must + be separated by a '/', which allows spaces to be included + in the entry. '*' and '?' can be used to specify multiple files + or directories as in DOS wildcards.

    Each entry must be a unix path, not a DOS path and + must not include the unix directory + separator '/'.

    Note that the case sensitive option + is applicable in vetoing files.

    One feature of the veto files parameter that it + is important to be aware of is Samba's behaviour when + trying to delete a directory. If a directory that is + to be deleted contains nothing but veto files this + deletion will fail unless you also set + the delete veto files parameter to + yes.

    Setting this parameter will affect the performance + of Samba, as it will be forced to check all files and directories + for a match as they are scanned.

    See also hide files + and + case sensitive.

    Default: No files or directories are vetoed. +

    Examples: +

    +; Veto any files containing the word Security, 
 ; any ending in .tmp, and any directory containing the
 ; word root.
 veto files = /*Security*/*.tmp/*root*/
 
 ; Veto the Apple specific files that a NetAtalk server
 ; creates.
-veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/

    >veto oplock files (S)

    This parameter is only valid when the oplocks - parameter is turned on for a share. It allows the Samba administrator - to selectively turn off the granting of oplocks on selected files that - match a wildcarded list, similar to the wildcarded list used in the - veto files - parameter.

    Default: No files are vetoed for oplock - grants

    You might want to do this on files that you know will - be heavily contended for by clients. A good example of this - is in the NetBench SMB benchmark program, which causes heavy - client contention for files ending in .SEM. - To cause Samba not to grant oplocks on these files you would use - the line (either in the [global] section or in the section for - the particular NetBench share :

    Example: veto oplock files = /*.SEM/ -

    >vfs path (S)

    This parameter specifies the directory - to look in for vfs modules. The name of every vfs object - will be prepended by this directory -

    Default: vfs path =

    Example: vfs path = /usr/lib/samba/vfs

    >vfs object (S)

    This parameter specifies a shared object files that - are used for Samba VFS I/O operations. By default, normal - disk I/O operations are used but these can be overloaded - with one or more VFS objects.

    Default : no value

    >vfs options (S)

    This parameter allows parameters to be passed - to the vfs layer at initialization time. - See also vfs object.

    Default : no value

    >volume (S)

    This allows you to override the volume label - returned for a share. Useful for CDROMs with installation programs - that insist on a particular volume label.

    Default: the name of the share

    >wide links (S)

    This parameter controls whether or not links - in the UNIX file system may be followed by the server. Links - that point to areas within the directory tree exported by the - server are always allowed; this parameter controls access only - to areas that are outside the directory tree being exported.

    Note that setting this parameter can have a negative - effect on your server performance due to the extra system calls - that Samba has to do in order to perform the link checks.

    Default: wide links = yes

    >winbind cache time (G)

    This parameter specifies the number of - seconds the winbindd(8) daemon will cache - user and group information before querying a Windows NT server - again.

    Default: winbind cache type = 15

    >winbind enum users (G)

    On large installations using winbindd(8) it may be - necessary to suppress the enumeration of users through the setpwent(), - getpwent() and - endpwent() group of system calls. If - the winbind enum users parameter is - no, calls to the getpwent system call - will not return any data.

    Warning: Turning off user - enumeration may cause some programs to behave oddly. For - example, the finger program relies on having access to the - full user list when searching for matching - usernames.

    Default: winbind enum users = yes

    >winbind enum groups (G)

    On large installations using winbindd(8) it may be necessary to suppress - the enumeration of groups through the setgrent(), - getgrent() and - endgrent() group of system calls. If - the winbind enum groups parameter is - no, calls to the getgrent() system - call will not return any data.

    Warning: Turning off group - enumeration may cause some programs to behave oddly. -

    Default: winbind enum groups = yes -

    >winbind gid (G)

    The winbind gid parameter specifies the range of group - ids that are allocated by the winbindd(8) daemon. This range of group ids should have no - existing local or NIS groups within it as strange conflicts can - occur otherwise.

    Default: winbind gid = <empty string> -

    Example: winbind gid = 10000-20000

    >winbind separator (G)

    This parameter allows an admin to define the character - used when listing a username of the form of DOMAIN - \user. This parameter - is only applicable when using the pam_winbind.so - and nss_winbind.so modules for UNIX services. -

    Please note that setting this parameter to + causes problems - with group membership at least on glibc systems, as the character + - is used as a special character for NIS in /etc/group.

    Default: winbind separator = '\'

    Example: winbind separator = +

    >winbind uid (G)

    The winbind gid parameter specifies the range of group - ids that are allocated by the winbindd(8) daemon. This range of ids should have no - existing local or NIS users within it as strange conflicts can - occur otherwise.

    Default: winbind uid = <empty string> -

    Example: winbind uid = 10000-20000

    >winbind use default domain (G)

    This parameter specifies whether the winbindd(8) daemon should operate on users - without domain component in their username. - Users without a domain component are treated as is part of the winbindd server's - own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail - function in a way much closer to the way they would in a native unix system.

    Default: winbind use default domain = <no> -

    Example: winbind use default domain = yes

    >wins hook (G)

    When Samba is running as a WINS server this - allows you to call an external program for all changes to the - WINS database. The primary use for this option is to allow the - dynamic update of external name resolution databases such as - dynamic DNS.

    The wins hook parameter specifies the name of a script - or executable that will be called as follows:

    wins_hook operation name nametype ttl IP_list -

    • The first argument is the operation and is one - of "add", "delete", or "refresh". In most cases the operation can - be ignored as the rest of the parameters provide sufficient - information. Note that "refresh" may sometimes be called when the - name has not previously been added, in that case it should be treated - as an add.

    • The second argument is the NetBIOS name. If the +veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ +

    veto oplock files (S)

    This parameter is only valid when the + oplocks + parameter is turned on for a share. It allows the Samba administrator + to selectively turn off the granting of oplocks on selected files that + match a wildcarded list, similar to the wildcarded list used in the + veto files + parameter.

    Default: No files are vetoed for oplock grants

    You might want to do this on files that you know will + be heavily contended for by clients. A good example of this + is in the NetBench SMB benchmark program, which causes heavy + client contention for files ending in .SEM. + To cause Samba not to grant oplocks on these files you would use + the line (either in the [global] section or in the section for + the particular NetBench share :

    Example: veto oplock files = /*.SEM/

    vfs object (S)

    This parameter specifies a shared object files that + are used for Samba VFS I/O operations. By default, normal + disk I/O operations are used but these can be overloaded + with one or more VFS objects.

    Default: no value

    vfs options (S)

    This parameter allows parameters to be passed + to the vfs layer at initialization time. + See also + vfs object.

    Default: no value

    vfs path (S)

    This parameter specifies the directory + to look in for vfs modules. The name of every vfs object + will be prepended by this directory.

    Default: vfs path =

    Example: vfs path = /usr/lib/samba/vfs

    volume (S)

    This allows you to override the volume label + returned for a share. Useful for CDROMs with installation programs + that insist on a particular volume label.

    Default: the name of the share

    wide links (S)

    This parameter controls whether or not links + in the UNIX file system may be followed by the server. Links + that point to areas within the directory tree exported by the + server are always allowed; this parameter controls access only + to areas that are outside the directory tree being exported.

    Note that setting this parameter can have a negative + effect on your server performance due to the extra system calls + that Samba has to do in order to perform the link checks.

    Default: wide links = yes

    winbind cache time (G)

    This parameter specifies the number of + seconds the winbindd(8) daemon will cache + user and group information before querying a Windows NT server + again.

    Default: winbind cache type = 15

    winbind enum groups (G)

    On large installations using winbindd(8) it may be necessary to suppress + the enumeration of groups through the setgrent(), + getgrent() and + endgrent() group of system calls. If + the winbind enum groups parameter is + no, calls to the getgrent() system + call will not return any data.

    Warning: Turning off group + enumeration may cause some programs to behave oddly. +

    Default: winbind enum groups = yes

    winbind enum users (G)

    On large installations using winbindd(8) it may be + necessary to suppress the enumeration of users through the setpwent(), + getpwent() and + endpwent() group of system calls. If + the winbind enum users parameter is + no, calls to the getpwent system call + will not return any data.

    Warning: Turning off user + enumeration may cause some programs to behave oddly. For + example, the finger program relies on having access to the + full user list when searching for matching + usernames.

    Default: winbind enum users = yes

    winbind gid (G)

    The winbind gid parameter specifies the range of group + ids that are allocated by the winbindd(8) daemon. This range of group ids should have no + existing local or NIS groups within it as strange conflicts can + occur otherwise.

    Default: winbind gid = <empty string>

    Example: winbind gid = 10000-20000

    winbind separator (G)

    This parameter allows an admin to define the character + used when listing a username of the form of DOMAIN + \user. This parameter + is only applicable when using the pam_winbind.so + and nss_winbind.so modules for UNIX services. +

    Please note that setting this parameter to + causes problems + with group membership at least on glibc systems, as the character + + is used as a special character for NIS in /etc/group.

    Default: winbind separator = '\'

    Example: winbind separator = +

    winbind uid (G)

    The winbind gid parameter specifies the range of group + ids that are allocated by the winbindd(8) daemon. This range of ids should have no + existing local or NIS users within it as strange conflicts can + occur otherwise.

    Default: winbind uid = <empty string>

    Example: winbind uid = 10000-20000

    winbind used default domain (G)

    This parameter specifies whether the + winbindd(8) daemon should operate on users + without domain component in their username. Users without a domain + component are treated as is part of the winbindd server's own + domain. While this does not benifit Windows users, it makes SSH, FTP and + e-mail function in a way much closer to the way they + would in a native unix system.

    Default: winbind use default domain = <no>

    Example: winbind use default domain = yes

    wins hook (G)

    When Samba is running as a WINS server this + allows you to call an external program for all changes to the + WINS database. The primary use for this option is to allow the + dynamic update of external name resolution databases such as + dynamic DNS.

    The wins hook parameter specifies the name of a script + or executable that will be called as follows:

    wins_hook operation name nametype ttl IP_list

    • The first argument is the operation and is + one of "add", "delete", or + "refresh". In most cases the operation + can be ignored as the rest of the parameters + provide sufficient information. Note that + "refresh" may sometimes be called when + the name has not previously been added, in that + case it should be treated as an add.

    • The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores - and periods.

    • The third argument is the NetBIOS name - type as a 2 digit hexadecimal number.

    • The fourth argument is the TTL (time to live) - for the name in seconds.

    • The fifth and subsequent arguments are the IP + and periods.

    • The third argument is the NetBIOS name + type as a 2 digit hexadecimal number.

    • The fourth argument is the TTL (time to live) + for the name in seconds.

    • The fifth and subsequent arguments are the IP addresses currently registered for that name. If this list is - empty then the name should be deleted.

    An example script that calls the BIND dynamic DNS update - program nsupdate is provided in the examples - directory of the Samba source code.

    >wins proxy (G)

    This is a boolean that controls if nmbd(8) will respond to broadcast name - queries on behalf of other hosts. You may need to set this - to yes for some older clients.

    Default: wins proxy = no

    >wins server (G)

    This specifies the IP address (or DNS name: IP - address for preference) of the WINS server that nmbd(8) should register with. If you have a WINS server on - your network then you should set this to the WINS server's IP.

    You should point this at your WINS server if you have a - multi-subnetted network.

    If you want to work in multiple namespaces, you can - give every wins server a 'tag'. For each tag, only one - (working) server will be queried for a name. The tag should be - seperated from the ip address by a colon. -

    You need to set up Samba to point - to a WINS server if you have multiple subnets and wish cross-subnet - browsing to work correctly.

    See the documentation file Browsing in the samba howto collection.

    Default: not enabled

    Example: wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61

    For this example when querying a certain name, 192.19.200.1 will - be asked first and if that doesn't respond 192.168.2.61. If either - of those doesn't know the name 192.168.3.199 will be queried. -

    Example: wins server = 192.9.200.1 192.168.2.61

    >wins support (G)

    This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should - not set this to yes unless you have a multi-subnetted network and - you wish a particular nmbd to be your WINS server. - Note that you should NEVER set this to yes - on more than one machine in your network.

    Default: wins support = no

    >workgroup (G)

    This controls what workgroup your server will - appear to be in when queried by clients. Note that this parameter - also controls the Domain name used with the security = domain - setting.

    Default: set at compile time to WORKGROUP

    Example: workgroup = MYGROUP

    >writable (S)

    Synonym for writeable for people who can't spell :-).

    >write cache size (S)

    If this integer parameter is set to non-zero value, - Samba will create an in-memory cache for each oplocked file - (it does not do this for - non-oplocked files). All writes that the client does not request - to be flushed directly to disk will be stored in this cache if possible. - The cache is flushed onto disk when a write comes in whose offset - would not fit into the cache or when the file is closed by the client. - Reads for the file are also served from this cache if the data is stored - within it.

    This cache allows Samba to batch client writes into a more - efficient write size for RAID disks (i.e. writes may be tuned to - be the RAID stripe size) and can improve performance on systems - where the disk subsystem is a bottleneck but there is free - memory for userspace programs.

    The integer parameter specifies the size of this cache - (per oplocked file) in bytes.

    Default: write cache size = 0

    Example: write cache size = 262144

    for a 256k cache size per file.

    >write list (S)

    This is a list of users that are given read-write - access to a service. If the connecting user is in this list then - they will be given write access, no matter what the read only - option is set to. The list can include group names using the - @group syntax.

    Note that if a user is in both the read list and the - write list then they will be given write access.

    See also the read list - option.

    Default: write list = <empty string> -

    Example: write list = admin, root, @staff -

    >wins partners (G)

    A space separated list of partners' IP addresses for - WINS replication. WINS partners are always defined as push/pull - partners as defining only one way WINS replication is unreliable. - WINS replication is currently experimental and unreliable between - samba servers. -

    Default: wins partners =

    Example: wins partners = 192.168.0.1 172.16.1.2

    >write ok (S)

    Inverted synonym for read only.

    >write raw (G)

    This parameter controls whether or not the server - will support raw write SMB's when transferring data from clients. - You should never need to change this parameter.

    Default: write raw = yes

    >writeable (S)

    Inverted synonym for read only.

    WARNINGS

    Although the configuration file permits service names + empty then the name should be deleted.

    An example script that calls the BIND dynamic DNS update + program nsupdate is provided in the examples + directory of the Samba source code.

    wins partner (G)

    A space separated list of partners' IP addresses for + WINS replication. WINS partners are always defined as push/pull + partners as defining only one way WINS replication is unreliable. + WINS replication is currently experimental and unreliable between + samba servers. +

    Default: wins partners =

    Example: wins partners = 192.168.0.1 172.16.1.2

    wins proxy (G)

    This is a boolean that controls if nmbd(8) will respond to broadcast name + queries on behalf of other hosts. You may need to set this + to yes for some older clients.

    Default: wins proxy = no

    wins server (G)

    This specifies the IP address (or DNS name: IP + address for preference) of the WINS server that nmbd(8) should register with. If you have a WINS server on + your network then you should set this to the WINS server's IP.

    You should point this at your WINS server if you have a + multi-subnetted network.

    If you want to work in multiple namespaces, you can + give every wins server a 'tag'. For each tag, only one + (working) server will be queried for a name. The tag should be + seperated from the ip address by a colon. +

    Note

    You need to set up Samba to point + to a WINS server if you have multiple subnets and wish cross-subnet + browsing to work correctly.

    See the documentation file Browsing in the samba howto collection.

    Default: not enabled

    Example: wins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61

    For this example when querying a certain name, 192.19.200.1 will + be asked first and if that doesn't respond 192.168.2.61. If either + of those doesn't know the name 192.168.3.199 will be queried. +

    Example: wins server = 192.9.200.1 192.168.2.61

    wins support (G)

    This boolean controls if the nmbd(8) process in Samba will act as a WINS server. You should + not set this to yes unless you have a multi-subnetted network and + you wish a particular nmbd to be your WINS server. + Note that you should NEVER set this to yes + on more than one machine in your network.

    Default: wins support = no

    workgroup (G)

    This controls what workgroup your server will + appear to be in when queried by clients. Note that this parameter + also controls the Domain name used with + the security = domain + setting.

    Default: set at compile time to WORKGROUP

    Example: workgroup = MYGROUP

    writable (S)

    Synonym for + writeable for people who can't spell :-).

    writeable (S)

    Inverted synonym for + read only.

    write cache size (S)

    If this integer parameter is set to non-zero value, + Samba will create an in-memory cache for each oplocked file + (it does not do this for + non-oplocked files). All writes that the client does not request + to be flushed directly to disk will be stored in this cache if possible. + The cache is flushed onto disk when a write comes in whose offset + would not fit into the cache or when the file is closed by the client. + Reads for the file are also served from this cache if the data is stored + within it.

    This cache allows Samba to batch client writes into a more + efficient write size for RAID disks (i.e. writes may be tuned to + be the RAID stripe size) and can improve performance on systems + where the disk subsystem is a bottleneck but there is free + memory for userspace programs.

    The integer parameter specifies the size of this cache + (per oplocked file) in bytes.

    Default: write cache size = 0

    Example: write cache size = 262144

    for a 256k cache size per file.

    write list (S)

    This is a list of users that are given read-write + access to a service. If the connecting user is in this list then + they will be given write access, no matter what the + read only + option is set to. The list can include group names using the + @group syntax.

    Note that if a user is in both the read list and the + write list then they will be given write access.

    See also the read list + option.

    Default: write list = <empty string>

    Example: write list = admin, root, @staff

    write ok (S)

    Inverted synonym for + read only.

    write raw (G)

    This parameter controls whether or not the server + will support raw write SMB's when transferring data from clients. + You should never need to change this parameter.

    Default: write raw = yes

    wtmp directory (G)

    This parameter is only available if Samba has + been configured and compiled with the option + --with-utmp. It specifies a directory pathname that is + used to store the wtmp or wtmpx files (depending on the UNIX system) that + record user connections to a Samba server. The difference with + the utmp directory is the fact that user info is kept after a user + has logged out.

    See also the + utmp parameter. By default this is + not set, meaning the system will use whatever utmp file the + native system is set to use (usually + /var/run/wtmp on Linux).

    Default: no wtmp directory

    Example: wtmp directory = /var/log/wtmp

    WARNINGS

    Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons anyway, so it shouldn't be a - problem - but be aware of the possibility.

    On a similar note, many clients - especially DOS clients - - limit service names to eight characters. smbd(8) has no such limitation, but attempts to connect from such + problem - but be aware of the possibility.

    On a similar note, many clients - especially DOS clients - + limit service names to eight characters. smbd(8) has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters - in length.

    Use of the [homes] and [printers] special sections make life + in length.

    Use of the [homes] and [printers] special sections make life for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme care when designing these sections. In particular, ensure that the permissions on spool - directories are correct.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    samba(7), smbpasswd(8), swat(8), smbd(8), nmbd(8), smbclient(1), nmblookup(1), testparm(1), testprns(1).

    AUTHOR

    The original Samba software and related utilities + directories are correct.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    + samba(7), smbpasswd(8), swat(8), smbd(8), nmbd(8), smbclient(1), nmblookup(1), testparm(1), testprns(1).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index fa70a288cd..f987680f33 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -1,510 +1,95 @@ - -smbcacls

    smbcacls

    Name

    smbcacls -- Set or get ACLs on an NT file or directory names

    Synopsis

    smbcacls {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbcacls program manipulates NT Access Control - Lists (ACLs) on SMB file shares.

    OPTIONS

    The following options are available to the smbcacls program. - The format of ACLs is described in the section ACL FORMAT

    -A acls

    Add the ACLs specified to the ACL list. Existing - access control entries are unchanged.

    -M acls

    Modify the mask value (permissions) for the ACLs +smbcacls

    Name

    smbcacls — Set or get ACLs on an NT file or directory names

    Synopsis

    smbcacls {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbcacls program manipulates NT Access Control + Lists (ACLs) on SMB file shares.

    OPTIONS

    The following options are available to the smbcacls program. + The format of ACLs is described in the section ACL FORMAT

    -A acls

    Add the ACLs specified to the ACL list. Existing + access control entries are unchanged.

    -M acls

    Modify the mask value (permissions) for the ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list -

    -D acls

    Delete any ACLs specified on the command line. +

    -D acls

    Delete any ACLs specified on the command line. An error will be printed for each ACL specified that was not - already present in the ACL list.

    -S acls

    This command sets the ACLs on the file with + already present in the ACL list.

    -S acls

    This command sets the ACLs on the file with only the ones specified on the command line. All other ACLs are erased. Note that the ACL specified must contain at least a revision, - type, owner and group for the call to succeed.

    -U username

    Specifies a username used to connect to the - specified service. The username may be of the form "username" in + type, owner and group for the call to succeed.

    -U username

    Specifies a username used to connect to the + specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the - workgroup specified in the smb.conf(5) file is - used, or "username%password" or "DOMAIN\username%password" and the - password and workgroup names are used as provided.

    -C name

    The owner of a file or directory can be changed - to the name given using the -C option. + workgroup specified in the smb.conf(5) file is + used, or "username%password" or "DOMAIN\username%password" and the + password and workgroup names are used as provided.

    -C name

    The owner of a file or directory can be changed + to the name given using the -C option. The name can be a sid in the form S-1-x-y-z or a name resolved - against the server specified in the first argument.

    This command is a shortcut for -M OWNER:name. -

    -G name

    The group owner of a file or directory can - be changed to the name given using the -G + against the server specified in the first argument.

    This command is a shortcut for -M OWNER:name. +

    -G name

    The group owner of a file or directory can + be changed to the name given using the -G option. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument. -

    This command is a shortcut for -M GROUP:name.

    -n

    This option displays all ACL information in numeric +

    This command is a shortcut for -M GROUP:name.

    -n

    This option displays all ACL information in numeric format. The default is to convert SIDs to names and ACE types - and masks to a readable string format.

    -t

    Don't actually do anything, only validate the correctness of + and masks to a readable string format.

    -t

    + Don't actually do anything, only validate the correctness of the arguments. -

    -h|--help

    Print a summary of command line options.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -h|--help

    Print a summary of command line options. +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    ACL FORMAT

    The format of an ACL is one or more ACL entries separated by - either commas or newlines. An ACL entry is one of the following: 

     
-REVISION:<revision number>
-OWNER:<sid or name>
-GROUP:<sid or name>
-ACL:<sid or name>:<type>/<flags>/<mask>

    The revision of the ACL specifies the internal Windows +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    ACL FORMAT

    The format of an ACL is one or more ACL entries separated by + either commas or newlines. An ACL entry is one of the following: 

     
+REVISION:<revision number>
+OWNER:<sid or name>
+GROUP:<sid or name>
+ACL:<sid or name>:<type>/<flags>/<mask>
+

    The revision of the ACL specifies the internal Windows NT ACL revision for the security descriptor. If not specified it defaults to 1. Using values other than 1 may - cause strange behaviour.

    The owner and group specify the owner and group sids for the + cause strange behaviour.

    The owner and group specify the owner and group sids for the object. If a SID in the format CWS-1-x-y-z is specified this is used, otherwise the name specified is resolved using the server on which - the file or directory resides.

    ACLs specify permissions granted to the SID. This SID again + the file or directory resides.

    ACLs specify permissions granted to the SID. This SID again can be specified in CWS-1-x-y-z format or as a name in which case it is resolved against the server on which the file or directory resides. The type, flags and mask values determine the type of - access granted to the SID.

    The type can be either 0 or 1 corresponding to ALLOWED or + access granted to the SID.

    The type can be either 0 or 1 corresponding to ALLOWED or DENIED access to the SID. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs. Some - common flags are:

    • #define SEC_ACE_FLAG_OBJECT_INHERIT 0x1

    • #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

    • #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4

    • #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

    At present flags can only be specified as decimal or - hexadecimal values.

    The mask is a value which expresses the access right + common flags are:

    • #define SEC_ACE_FLAG_OBJECT_INHERIT 0x1

    • #define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2

    • #define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4

    • #define SEC_ACE_FLAG_INHERIT_ONLY 0x8

    At present flags can only be specified as decimal or + hexadecimal values.

    The mask is a value which expresses the access right granted to the SID. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT - file permissions of the same name.

    • R - Allow read access

    • W - Allow write access

    • X - Execute permission on the object

    • D - Delete the object

    • P - Change permissions

    • O - Take ownership

    The following combined permissions can be specified:

    • READ - Equivalent to 'RX' - permissions

    • CHANGE - Equivalent to 'RXWD' permissions -

    • FULL - Equivalent to 'RWXDPO' - permissions

    EXIT STATUS

    The smbcacls program sets the exit status + file permissions of the same name.

    • R - Allow read access

    • W - Allow write access

    • X - Execute permission on the object

    • D - Delete the object

    • P - Change permissions

    • O - Take ownership

    The following combined permissions can be specified:

    • READ - Equivalent to 'RX' + permissions

    • CHANGE - Equivalent to 'RXWD' permissions +

    • FULL - Equivalent to 'RWXDPO' + permissions

    EXIT STATUS

    The smbcacls program sets the exit status depending on the success or otherwise of the operations performed. - The exit status may be one of the following values.

    If the operation succeeded, smbcacls returns and exit - status of 0. If smbcacls couldn't connect to the specified server, + The exit status may be one of the following values.

    If the operation succeeded, smbcacls returns and exit + status of 0. If smbcacls couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line - arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities + arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    smbcacls was written by Andrew Tridgell - and Tim Potter.

    The conversion to DocBook for Samba 2.2 was done + to the way the Linux kernel is developed.

    smbcacls was written by Andrew Tridgell + and Tim Potter.

    The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done - by Alexander Bokovoy.

    \ No newline at end of file + by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 9ea84de950..49f00fb2db 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -1,1599 +1,424 @@ - -smbclient

    smbclient

    Name

    smbclient -- ftp-like client to access SMB/CIFS resources - on servers

    Synopsis

    smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbclient is a client that can +smbclient

    Name

    smbclient — ftp-like client to access SMB/CIFS resources + on servers

    Synopsis

    smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbclient is a client that can 'talk' to an SMB/CIFS server. It offers an interface - similar to that of the ftp program (see ftp(1)). + similar to that of the ftp program (see ftp(1)). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server - and so on.

    OPTIONS

    servicename

    servicename is the name of the service + and so on.

    OPTIONS

    servicename

    servicename is the name of the service you want to use on the server. A service name takes the form - //server/service where server - is the NetBIOS name of the SMB/CIFS server - offering the desired service and service + //server/service where server + is the NetBIOS name of the SMB/CIFS server + offering the desired service and service is the name of the service offered. Thus to connect to - the service "printer" on the SMB/CIFS server "smbserver", - you would use the servicename //smbserver/printer -

    Note that the server name required is NOT necessarily + the service "printer" on the SMB/CIFS server "smbserver", + you would use the servicename //smbserver/printer +

    Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server. -

    The server name is looked up according to either - the -R parameter to smbclient or +

    The server name is looked up according to either + the -R parameter to smbclient or using the name resolve order parameter in - the smb.conf(5) file, + the smb.conf(5) file, allowing an administrator to change the order and methods - by which server names are looked up.

    password

    The password required to access the specified + by which server names are looked up.

    password

    The password required to access the specified service on the specified server. If this parameter is - supplied, the -N option (suppress - password prompt) is assumed.

    There is no default password. If no password is supplied + supplied, the -N option (suppress + password prompt) is assumed.

    There is no default password. If no password is supplied on the command line (either by using this parameter or adding - a password to the -U option (see - below)) and the -N option is not + a password to the -U option (see + below)) and the -N option is not specified, the client will prompt for a password, even if the desired service does not require one. (If no password is required, simply press ENTER to provide a null password.) -

    Note: Some servers (including OS/2 and Windows for +

    Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers. -

    Be cautious about including passwords in scripts. -

    -R <name resolve order>

    This option is used by the programs in the Samba +

    Be cautious about including passwords in scripts. +

    -R <name resolve order>

    This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated - string of different name resolution options.

    The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows:

    • lmhosts: Lookup an IP + string of different name resolution options.

      The options are :"lmhosts", "host", "wins" and "bcast". They + cause names to be resolved as follows:

      • lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see - the lmhosts(5) for details) then - any name type matches for lookup.

      • host: Do a standard host - name to IP address resolution, using the system /etc/hosts - , NIS, or DNS lookups. This method of name resolution + the lmhosts(5) for details) then + any name type matches for lookup.

      • host: Do a standard host + name to IP address resolution, using the system /etc/hosts + , NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this - may be controlled by the /etc/nsswitch.conf + may be controlled by the /etc/nsswitch.conf file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise - it is ignored.

      • wins: Query a name with - the IP address listed in the wins server + it is ignored.

      • wins: Query a name with + the IP address listed in the wins server parameter. If no WINS server has - been specified this method will be ignored.

      • bcast: Do a broadcast on + been specified this method will be ignored.

      • bcast: Do a broadcast on each of the known local interfaces listed in the - interfaces + interfaces parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally - connected subnet.

      If this parameter is not set then the name resolve order - defined in the smb.conf(5) file parameter - (name resolve order) will be used.

      The default order is lmhosts, host, wins, bcast and without - this parameter or any entry in the name resolve order - parameter of the smb.conf(5) file the name resolution - methods will be attempted in this order.

    -M NetBIOS name

    This options allows you to send messages, using - the "WinPopup" protocol, to another computer. Once a connection is + connected subnet.

    If this parameter is not set then the name resolve order + defined in the smb.conf(5) file parameter + (name resolve order) will be used.

    The default order is lmhosts, host, wins, bcast and without + this parameter or any entry in the name resolve order + parameter of the smb.conf(5) file the name resolution + methods will be attempted in this order.

    -M NetBIOS name

    This options allows you to send messages, using + the "WinPopup" protocol, to another computer. Once a connection is established you then type your message, pressing ^D (control-D) to - end.

    If the receiving computer is running WinPopup the user will + end.

    If the receiving computer is running WinPopup the user will receive the message and probably a beep. If they are not running WinPopup the message will be lost, and no error message will - occur.

    The message is also automatically truncated if the message + occur.

    The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol. -

    One useful trick is to cat the message through - smbclient. For example: cat mymessage.txt | smbclient -M FRED will - send the message in the file mymessage.txt - to the machine FRED.

    You may also find the -U and - -I options useful, as they allow you to - control the FROM and TO parts of the message.

    See the message command parameter in the smb.conf(5) for a description of how to handle incoming - WinPopup messages in Samba.

    Note: Copy WinPopup into the startup group +

    One useful trick is to cat the message through + smbclient. For example: + cat mymessage.txt | smbclient -M FRED will + send the message in the file mymessage.txt + to the machine FRED.

    You may also find the -U and + -I options useful, as they allow you to + control the FROM and TO parts of the message.

    See the message command parameter in the smb.conf(5) for a description of how to handle incoming + WinPopup messages in Samba.

    Note: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive - messages.

    -p port

    This number is the TCP port number that will be used + messages.

    -p port

    This number is the TCP port number that will be used when making connections to the server. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the - default.

    -l logfilename

    If specified, logfilename specifies a base filename + default.

    -l logfilename

    If specified, logfilename specifies a base filename into which operational data from the running client will be - logged.

    The default base name is specified at compile time.

    The base name is used to generate actual log file names. - For example, if the name specified was "log", the debug file - would be log.client.

    The log file generated is never removed by the client. -

    -h|--help

    Print a summary of command line options.

    -I IP-address

    IP address is the address of the server to connect to. - It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named + logged.

    The default base name is specified at compile time.

    The base name is used to generate actual log file names. + For example, if the name specified was "log", the debug file + would be log.client.

    The log file generated is never removed by the client. +

    -h|--help

    Print a summary of command line options. +

    -I IP-address

    IP address is the address of the server to connect to. + It should be specified in standard "a.b.c.d" notation.

    Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution - mechanism described above in the name resolve order + mechanism described above in the name resolve order parameter above. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being - connected to will be ignored.

    There is no default for this parameter. If not supplied, + connected to will be ignored.

    There is no default for this parameter. If not supplied, it will be determined automatically by the client as described - above.

    -E

    This parameter causes the client to write messages + above.

    -E

    This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard - output stream.

    By default, the client writes messages to standard output - - typically the user's tty.

    -L

    This option allows you to look at what services - are available on a server. You use it as smbclient -L - host and a list should appear. The -I - option may be useful if your NetBIOS names don't + output stream.

    By default, the client writes messages to standard output + - typically the user's tty.

    -L

    This option allows you to look at what services + are available on a server. You use it as smbclient -L + host and a list should appear. The -I + option may be useful if your NetBIOS names don't match your TCP/IP DNS host names or if you are trying to reach a - host on another network.

    -t terminal code

    This option tells smbclient how to interpret + host on another network.

    -t terminal code

    This option tells smbclient how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than - SMB/CIFS servers (EUC instead of SJIS for example). Setting this parameter will let - smbclient convert between the UNIX filenames and + SMB/CIFS servers (EUC instead of + SJIS for example). Setting this parameter will let + smbclient convert between the UNIX filenames and the SMB filenames correctly. This option has not been seriously tested - and may have some problems.

    The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, + and may have some problems.

    The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet, CWhex, CWcap. This is not a complete list, check the Samba - source code for the complete list.

    -b buffersize

    This option changes the transmit/send buffer + source code for the complete list.

    -b buffersize

    This option changes the transmit/send buffer size when getting or putting a file from/to the server. The default is 65520 bytes. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server. -

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -N

    If specified, this parameter suppresses the normal +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -N

    If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when -accessing a service that does not require a password.

    Unless a password is specified on the command line or +accessing a service that does not require a password.

    Unless a password is specified on the command line or this parameter is specified, the client will request a -password.

    -k

    Try to authenticate with kerberos. Only useful in -an Active Directory environment.

    -A|--authfile=filename

    This option allows +password.

    -k

    +Try to authenticate with kerberos. Only useful in +an Active Directory environment. +

    -A|--authfile=filename

    This option allows you to specify a file from which to read the username and -password used in the connection. The format of the file is

    username = <value>
-password = <value>
-domain   = <value>

    Make certain that the permissions on the file restrict -access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The -client will first check the USER environment variable, then the -LOGNAME variable and if either exists, the +password used in the connection. The format of the file is +

    +username = <value>
+password = <value>
+domain   = <value>
+

    Make certain that the permissions on the file restrict +access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The +client will first check the USER environment variable, then the +LOGNAME variable and if either exists, the string is uppercased. If these environmental variables are not -found, the username GUEST is used.

    A third option is to use a credentials file which +found, the username GUEST is used.

    A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the --A for more details.

    Be cautious about including passwords in scripts. Also, on +-A for more details.

    Be cautious about including passwords in scripts. Also, on many systems the command line of a running process may be seen -via the ps command. To be safe always allow -rpcclient to prompt for a password and type -it in directly.

    -n <primary NetBIOS name>

    This option allows you to override +via the ps command. To be safe always allow +rpcclient to prompt for a password and type +it in directly.

    -n <primary NetBIOS name>

    This option allows you to override the NetBIOS name that Samba uses for itself. This is identical -to setting the NetBIOS -name parameter in the smb.conf(5) file. However, a command +to setting the NetBIOS +name parameter in the smb.conf(5) file. However, a command line setting will take precedence over settings in -smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that -nmblookup will use to communicate with when +smb.conf(5).

    -i <scope>

    This specifies a NetBIOS scope that +nmblookup will use to communicate with when generating NetBIOS names. For details on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -very rarely used, only set this parameter +very rarely used, only set this parameter if you are the system administrator in charge of all the -NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This +NetBIOS systems you communicate with.

    -W|--workgroup=domain

    Set the SMB domain of the username. This overrides the default domain which is the domain defined in smb.conf. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client +SAM (as opposed to the Domain SAM).

    -O socket options

    TCP socket options to set on the client socket. See the socket options parameter in -the smb.conf(5) manual page for the list of valid -options.

    -T tar options

    smbclient may be used to create tar(1) - compatible backups of all the files on an SMB/CIFS +the smb.conf(5) manual page for the list of valid +options.

    -T tar options

    smbclient may be used to create tar(1) + compatible backups of all the files on an SMB/CIFS share. The secondary tar flags that can be given to this option - are :

    • c - Create a tar file on UNIX. + are :

      • c - Create a tar file on UNIX. Must be followed by the name of a tar file, tape device - or "-" for standard output. If using standard output you must + or "-" for standard output. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file. This flag is mutually exclusive with the - x flag.

      • x - Extract (restore) a local + x flag.

      • x - Extract (restore) a local tar file back to a share. Unless the -D option is given, the tar files will be restored from the top level of the share. Must be - followed by the name of the tar file, device or "-" for standard - input. Mutually exclusive with the c flag. + followed by the name of the tar file, device or "-" for standard + input. Mutually exclusive with the c flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get - their creation dates restored properly.

      • I - Include files and directories. + their creation dates restored properly.

      • I - Include files and directories. Is the default behavior when filenames are specified above. Causes tar files to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing - works in one of two ways. See r below.

      • X - Exclude files and directories. + works in one of two ways. See r below.

      • X - Exclude files and directories. Causes tar files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. - See r below.

      • b - Blocksize. Must be followed + See r below.

      • b - Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. -

      • g - Incremental. Only back up +

      • g - Incremental. Only back up files that have the archive bit set. Useful only with the - c flag.

      • q - Quiet. Keeps tar from printing + c flag.

      • q - Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet. -

      • r - Regular expression include +

      • r - Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. -

      • N - Newer than. Must be followed +

      • N - Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the - c flag.

      • a - Set archive bit. Causes the + c flag.

      • a - Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the - g and c flags. -

      Tar Long File Names

      smbclient's tar option now supports long + g and c flags. +

    Tar Long File Names

    smbclient's tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when - a tar archive is created, smbclient's tar option places all + a tar archive is created, smbclient's tar option places all files in the archive with relative names, not absolute names. -

    Tar Filenames

    All file names can be given as DOS path names (with '\\' +

    Tar Filenames

    All file names can be given as DOS path names (with '\\' as the component separator) or as UNIX path names (with '/' as - the component separator).

    Examples

    Restore from tar file backup.tar into myshare on mypc - (no password on share).

    smbclient //mypc/yshare "" -N -Tx backup.tar -

    Restore everything except users/docs -

    smbclient //mypc/myshare "" -N -TXx backup.tar - users/docs

    Create a tar file of the files beneath users/docs.

    smbclient //mypc/myshare "" -N -Tc - backup.tar users/docs

    Create the same tar file as above, but now use - a DOS path name.

    smbclient //mypc/myshare "" -N -tc backup.tar - users\edocs

    Create a tar file of all the files and directories in - the share.

    smbclient //mypc/myshare "" -N -Tc backup.tar * -

    -D initial directory

    Change to initial directory before starting. Probably - only of any use with the tar -T option.

    -c command string

    command string is a semicolon-separated list of - commands to be executed instead of prompting from stdin. -N is implied by -c.

    This is particularly useful in scripts and for printing stdin - to the server, e.g. -c 'print -'.

    OPERATIONS

    Once the client is running, the user is presented with - a prompt :

    smb:\>

    The backslash ("\\") indicates the current working directory + the component separator).

    Examples

    Restore from tar file backup.tar into myshare on mypc + (no password on share).

    smbclient //mypc/yshare "" -N -Tx backup.tar +

    Restore everything except users/docs +

    smbclient //mypc/myshare "" -N -TXx backup.tar + users/docs

    Create a tar file of the files beneath + users/docs.

    smbclient //mypc/myshare "" -N -Tc + backup.tar users/docs

    Create the same tar file as above, but now use + a DOS path name.

    smbclient //mypc/myshare "" -N -tc backup.tar + users\edocs

    Create a tar file of all the files and directories in + the share.

    smbclient //mypc/myshare "" -N -Tc backup.tar * +

    -D initial directory

    Change to initial directory before starting. Probably + only of any use with the tar -T option.

    -c command string

    command string is a semicolon-separated list of + commands to be executed instead of prompting from stdin. + -N is implied by -c.

    This is particularly useful in scripts and for printing stdin + to the server, e.g. -c 'print -'.

    OPERATIONS

    Once the client is running, the user is presented with + a prompt :

    smb:\>

    The backslash ("\\") indicates the current working directory on the server, and will change if the current working directory - is changed.

    The prompt indicates that the client is ready and waiting to + is changed.

    The prompt indicates that the client is ready and waiting to carry out a user command. Each command is a single word, optionally followed by parameters specific to that command. Command and parameters are space-delimited unless these notes specifically state otherwise. All commands are case-insensitive. Parameters to commands may or may not be case sensitive, depending on the command. -

    You can specify file names which have spaces in them by quoting - the name with double quotes, for example "a long file name".

    Parameters shown in square brackets (e.g., "[parameter]") are +

    You can specify file names which have spaces in them by quoting + the name with double quotes, for example "a long file name".

    Parameters shown in square brackets (e.g., "[parameter]") are optional. If not given, the command will use suitable defaults. Parameters - shown in angle brackets (e.g., "<parameter>") are required. -

    Note that all commands operating on the server are actually + shown in angle brackets (e.g., "<parameter>") are required. +

    Note that all commands operating on the server are actually performed by issuing a request to the server. Thus the behavior may vary from server to server, depending on how the server was implemented. -

    The commands available are given here in alphabetical order.

    ? [command]

    If command is specified, the ? command will display +

    The commands available are given here in alphabetical order.

    ? [command]

    If command is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will - be displayed.

    ! [shell command]

    If shell command is specified, the ! + be displayed.

    ! [shell command]

    If shell command is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run. -

    altname file

    The client will request that the server return - the "alternate" name (the 8.3 name) for a file or directory. -

    cancel jobid0 [jobid1] ... [jobidN]

    The client will request that the server cancel +

    altname file

    The client will request that the server return + the "alternate" name (the 8.3 name) for a file or directory. +

    cancel jobid0 [jobid1] ... [jobidN]

    The client will request that the server cancel the printjobs identified by the given numeric print job ids. -

    chmod file mode in octal

    This command depends on the server supporting the CIFS +

    chmod file mode in octal

    This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server change the UNIX permissions to the given octal mode, in standard UNIX format. -

    chown file uid gid

    This command depends on the server supporting the CIFS +

    chown file uid gid

    This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server change the UNIX user and group ownership to the given decimal values. Note there is currently no way to remotely look up the UNIX uid and gid values for a given name. This may be addressed in future versions of the CIFS UNIX extensions. -

    cd [directory name]

    If "directory name" is specified, the current +

    cd [directory name]

    If "directory name" is specified, the current working directory on the server will be changed to the directory specified. This operation will fail if for any reason the specified - directory is inaccessible.

    If no directory name is specified, the current working - directory on the server will be reported.

    del <mask>

    The client will request that the server attempt - to delete all files matching mask from the current working - directory on the server.

    dir <mask>

    A list of the files matching mask in the current + directory is inaccessible.

    If no directory name is specified, the current working + directory on the server will be reported.

    del <mask>

    The client will request that the server attempt + to delete all files matching mask from the current working + directory on the server.

    dir <mask>

    A list of the files matching mask in the current working directory on the server will be retrieved from the server - and displayed.

    exit

    Terminate the connection with the server and exit - from the program.

    get <remote file name> [local file name]

    Copy the file called remote file name from + and displayed.

    exit

    Terminate the connection with the server and exit + from the program.

    get <remote file name> [local file name]

    Copy the file called remote file name from the server to the machine running the client. If specified, name - the local copy local file name. Note that all transfers in - smbclient are binary. See also the - lowercase command.

    help [command]

    See the ? command above.

    lcd [directory name]

    If directory name is specified, the current + the local copy local file name. Note that all transfers in + smbclient are binary. See also the + lowercase command.

    help [command]

    See the ? command above.

    lcd [directory name]

    If directory name is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any - reason the specified directory is inaccessible.

    If no directory name is specified, the name of the + reason the specified directory is inaccessible.

    If no directory name is specified, the name of the current working directory on the local machine will be reported. -

    link source destination

    This command depends on the server supporting the CIFS +

    link source destination

    This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server create a hard link between the source and destination files. The source file must not exist. -

    lowercase

    Toggle lowercasing of filenames for the get and - mget commands.

    When lowercasing is toggled ON, local filenames are converted +

    lowercase

    Toggle lowercasing of filenames for the get and + mget commands.

    When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands. This is often useful when copying (say) MSDOS files from a server, because - lowercase filenames are the norm on UNIX systems.

    ls <mask>

    See the dir command above.

    mask <mask>

    This command allows the user to set up a mask + lowercase filenames are the norm on UNIX systems.

    ls <mask>

    See the dir command above.

    mask <mask>

    This command allows the user to set up a mask which will be used during recursive operation of the mget and - mput commands.

    The masks specified to the mget and mput commands act as + mput commands.

    The masks specified to the mget and mput commands act as filters for directories rather than files when recursion is - toggled ON.

    The mask specified with the mask command is necessary + toggled ON.

    The mask specified with the mask command is necessary to filter files within those directories. For example, if the - mask specified in an mget command is "source*" and the mask - specified with the mask command is "*.c" and recursion is + mask specified in an mget command is "source*" and the mask + specified with the mask command is "*.c" and recursion is toggled ON, the mget command will retrieve all files matching - "*.c" in all directories below and including all directories - matching "source*" in the current working directory.

    Note that the value for mask defaults to blank (equivalent - to "*") and remains so until the mask command is used to change it. + "*.c" in all directories below and including all directories + matching "source*" in the current working directory.

    Note that the value for mask defaults to blank (equivalent + to "*") and remains so until the mask command is used to change it. It retains the most recently specified value indefinitely. To avoid unexpected results it would be wise to change the value of - mask back to "*" after using the mget or mput commands.

    md <directory name>

    See the mkdir command.

    mget <mask>

    Copy all files matching mask from the server to - the machine running the client.

    Note that mask is interpreted differently during recursive + mask back to "*" after using the mget or mput commands.

    md <directory name>

    See the mkdir command.

    mget <mask>

    Copy all files matching mask from the server to + the machine running the client.

    Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in - smbclient are binary. See also the lowercase command.

    mkdir <directory name>

    Create a new directory on the server (user access - privileges permitting) with the specified name.

    mput <mask>

    Copy all files matching mask in the current working + smbclient are binary. See also the lowercase command.

    mkdir <directory name>

    Create a new directory on the server (user access + privileges permitting) with the specified name.

    mput <mask>

    Copy all files matching mask in the current working directory on the local machine to the current working directory on - the server.

    Note that mask is interpreted differently during recursive + the server.

    Note that mask is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask - commands for more information. Note that all transfers in smbclient - are binary.

    print <file name>

    Print the specified file from the local machine - through a printable service on the server.

    See also the printmode command.

    printmode <graphics or text>

    Set the print mode to suit either binary data + commands for more information. Note that all transfers in smbclient + are binary.

    print <file name>

    Print the specified file from the local machine + through a printable service on the server.

    See also the printmode command.

    printmode <graphics or text>

    Set the print mode to suit either binary data (such as graphical information) or text. Subsequent print - commands will use the currently set print mode.

    prompt

    Toggle prompting for filenames during operation - of the mget and mput commands.

    When toggled ON, the user will be prompted to confirm + commands will use the currently set print mode.

    prompt

    Toggle prompting for filenames during operation + of the mget and mput commands.

    When toggled ON, the user will be prompted to confirm the transfer of each file during these commands. When toggled OFF, all specified files will be transferred without prompting. -

    put <local file name> [remote file name]

    Copy the file called local file name from the +

    put <local file name> [remote file name]

    Copy the file called local file name from the machine running the client to the server. If specified, - name the remote copy remote file name. Note that all transfers - in smbclient are binary. See also the lowercase command. -

    queue

    Displays the print queue, showing the job id, - name, size and current status.

    quit

    See the exit command.

    rd <directory name>

    See the rmdir command.

    recurse

    Toggle directory recursion for the commands mget - and mput.

    When toggled ON, these commands will process all directories + name the remote copy remote file name. Note that all transfers + in smbclient are binary. See also the lowercase command. +

    queue

    Displays the print queue, showing the job id, + name, size and current status.

    quit

    See the exit command.

    rd <directory name>

    See the rmdir command.

    recurse

    Toggle directory recursion for the commands mget + and mput.

    When toggled ON, these commands will process all directories in the source directory (i.e., the directory they are copying from ) and will recurse into any that match the mask specified to the command. Only files that match the mask specified using the mask command will be retrieved. See also the mask command. -

    When recursion is toggled OFF, only files from the current +

    When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mget or mput commands will be copied, and any mask specified - using the mask command will be ignored.

    rm <mask>

    Remove all files matching mask from the current - working directory on the server.

    rmdir <directory name>

    Remove the specified directory (user access - privileges permitting) from the server.

    setmode <filename> <perm=[+|\-]rsha>

    A version of the DOS attrib command to set - file permissions. For example:

    setmode myfile +r

    would make myfile read only.

    symlink source destination

    This command depends on the server supporting the CIFS + using the mask command will be ignored.

    rm <mask>

    Remove all files matching mask from the current + working directory on the server.

    rmdir <directory name>

    Remove the specified directory (user access + privileges permitting) from the server.

    setmode <filename> <perm=[+|\-]rsha>

    A version of the DOS attrib command to set + file permissions. For example:

    setmode myfile +r

    would make myfile read only.

    symlink source destination

    This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server create a symbolic hard link between the source and destination files. The source file must not exist. Note that the server will not create a link to any path that lies outside the currently connected share. This is enforced by the Samba server. -

    tar <c|x>[IXbgNa]

    Performs a tar operation - see the -T - command line option above. Behavior may be affected +

    tar <c|x>[IXbgNa]

    Performs a tar operation - see the -T + command line option above. Behavior may be affected by the tarmode command (see below). Using g (incremental) and N - (newer) will affect tarmode settings. Note that using the "-" option + (newer) will affect tarmode settings. Note that using the "-" option with tar x may not work - use the command line option instead. -

    blocksize <blocksize>

    Blocksize. Must be followed by a valid (greater +

    blocksize <blocksize>

    Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in - blocksize*TBLOCK (usually 512 byte) blocks.

    tarmode <full|inc|reset|noreset>

    Changes tar's behavior with regard to archive + blocksize*TBLOCK (usually 512 byte) blocks.

    tarmode <full|inc|reset|noreset>

    Changes tar's behavior with regard to archive bits. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode). In incremental mode, tar will only back up files with the archive bit set. In reset mode, tar will reset the archive bit on all files it backs up (implies - read/write share).

    NOTES

    Some servers are fussy about the case of supplied usernames, + read/write share).

    NOTES

    Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names. If you fail to connect try giving all parameters in uppercase. -

    It is often necessary to use the -n option when connecting +

    It is often necessary to use the -n option when connecting to some types of servers. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid - name that would be known to the server.

    smbclient supports long file names where the server - supports the LANMAN2 protocol or above.

    ENVIRONMENT VARIABLES

    The variable USER may contain the + name that would be known to the server.

    smbclient supports long file names where the server + supports the LANMAN2 protocol or above.

    ENVIRONMENT VARIABLES

    The variable USER may contain the username of the person using the client. This information is used only if the protocol level is high enough to support - session-level passwords.

    The variable PASSWD may contain + session-level passwords.

    The variable PASSWD may contain the password of the person using the client. This information is used only if the protocol level is high enough to support - session-level passwords.

    The variable LIBSMB_PROG may contain + session-level passwords.

    The variable LIBSMB_PROG may contain the path, executed with system(), which the client should connect to instead of connecting to a server. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS - file

    INSTALLATION

    The location of the client program is a matter for + file

    INSTALLATION

    The location of the client program is a matter for individual system administrators. The following are thus - suggestions only.

    It is recommended that the smbclient software be installed - in the /usr/local/samba/bin/ or /usr/samba/bin/ directory, this directory readable + suggestions only.

    It is recommended that the smbclient software be installed + in the /usr/local/samba/bin/ or + /usr/samba/bin/ directory, this directory readable by all, writeable only by root. The client program itself should - be executable by all. The client should NOT be - setuid or setgid!

    The client log files should be put in a directory readable - and writeable only by the user.

    To test the client, you will need to know the name of a - running SMB/CIFS server. It is possible to run smbd(8) as an ordinary user - running that server as a daemon + be executable by all. The client should NOT be + setuid or setgid!

    The client log files should be put in a directory readable + and writeable only by the user.

    To test the client, you will need to know the name of a + running SMB/CIFS server. It is possible to run smbd(8) as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) - would provide a suitable test server.

    DIAGNOSTICS

    Most diagnostics issued by the client are logged in a + would provide a suitable test server.

    DIAGNOSTICS

    Most diagnostics issued by the client are logged in a specified log file. The log file name is specified at compile time, - but may be overridden on the command line.

    The number and nature of diagnostics available depends + but may be overridden on the command line.

    The number and nature of diagnostics available depends on the debug level used by the client. If you have problems, - set the debug level to 3 and peruse the log files.

    VERSION

    This man page is correct for version 2.2 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities + set the debug level to 3 and peruse the log files.

    VERSION

    This man page is correct for version 2.2 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.

    \ No newline at end of file + was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 0afbbcd3f2..6fa017fdb0 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -1,468 +1,71 @@ - -smbcontrol

    smbcontrol

    Name

    smbcontrol -- send messages to smbd, nmbd or winbindd processes

    Synopsis

    smbcontrol [-i] [-s]

    smbcontrol [destination] [message-type] [parameter]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbcontrol is a very small program, which - sends messages to a smbd(8), a nmbd(8), or a winbindd(8) daemon running on the system.

    OPTIONS

    -h|--help

    Print a summary of command line options.

    -s <configuration file>

    The file specified contains the +smbcontrol

    Name

    smbcontrol — send messages to smbd, nmbd or winbindd processes

    Synopsis

    smbcontrol [-i] [-s]

    smbcontrol [destination] [message-type] [parameter]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbcontrol is a very small program, which + sends messages to a smbd(8), a nmbd(8), or a winbindd(8) daemon running on the system.

    OPTIONS

    -h|--help

    Print a summary of command line options. +

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -i

    Run interactively. Individual commands +compile time.

    -i

    Run interactively. Individual commands of the form destination message-type parameters can be entered - on STDIN. An empty command line or a "q" will quit the - program.

    destination

    One of nmbd, smbd or a process ID.

    The smbd destination causes the - message to "broadcast" to all smbd daemons.

    The nmbd destination causes the + on STDIN. An empty command line or a "q" will quit the + program.

    destination

    One of nmbd, smbd or a process ID.

    The smbd destination causes the + message to "broadcast" to all smbd daemons.

    The nmbd destination causes the message to be sent to the nmbd daemon specified in the - nmbd.pid file.

    If a single process ID is given, the message is sent - to only that process.

    message-type

    Type of message to send. See - the section MESSAGE-TYPES for details. -

    parameters

    any parameters required for the message-type

    MESSAGE-TYPES

    Available message types are:

    close-share

    Order smbd to close the client + nmbd.pid file.

    If a single process ID is given, the message is sent + to only that process.

    message-type

    Type of message to send. See + the section MESSAGE-TYPES for details. +

    parameters

    any parameters required for the message-type

    MESSAGE-TYPES

    Available message types are:

    close-share

    Order smbd to close the client connections to the named share. Note that this doesn't affect client connections to any other shares. This message-type takes an argument of the share name for which client connections will be closed, or the - "*" character which will close all currently open shares. + "*" character which will close all currently open shares. This may be useful if you made changes to the access controls on the share. - This message can only be sent to smbd.

    debug

    Set debug level to the value specified by the - parameter. This can be sent to any of the destinations.

    force-election

    This message causes the nmbd daemon to - force a new browse master election.

    ping

    Send specified number of "ping" messages and - wait for the same number of reply "pong" messages. This can be sent to - any of the destinations.

    profile

    Change profile settings of a daemon, based on the - parameter. The parameter can be "on" to turn on profile stats - collection, "off" to turn off profile stats collection, "count" + This message can only be sent to smbd.

    debug

    Set debug level to the value specified by the + parameter. This can be sent to any of the destinations.

    force-election

    This message causes the nmbd daemon to + force a new browse master election.

    ping

    + Send specified number of "ping" messages and + wait for the same number of reply "pong" messages. This can be sent to + any of the destinations.

    profile

    Change profile settings of a daemon, based on the + parameter. The parameter can be "on" to turn on profile stats + collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are - disabled), and "flush" to zero the current profile stats. This can - be sent to any smbd or nmbd destinations.

    debuglevel

    Request debuglevel of a certain daemon and write it to stdout. This - can be sent to any of the destinations.

    profilelevel

    Request profilelevel of a certain daemon and write it to stdout. - This can be sent to any smbd or nmbd destinations.

    printnotify

    Order smbd to send a printer notify message to any Windows NT clients + disabled), and "flush" to zero the current profile stats. This can + be sent to any smbd or nmbd destinations.

    debuglevel

    + Request debuglevel of a certain daemon and write it to stdout. This + can be sent to any of the destinations.

    profilelevel

    + Request profilelevel of a certain daemon and write it to stdout. + This can be sent to any smbd or nmbd destinations.

    printnotify

    + Order smbd to send a printer notify message to any Windows NT clients connected to a printer. This message-type takes the following arguments: -

    queuepause printername

    Send a queue pause change notify - message to the printer specified.

    queueresume printername

    Send a queue resume change notify - message for the printer specified.

    jobpause printername unixjobid

    Send a job pause change notify +

    queuepause printername

    Send a queue pause change notify + message to the printer specified.

    queueresume printername

    Send a queue resume change notify + message for the printer specified.

    jobpause printername unixjobid

    Send a job pause change notify message for the printer and unix jobid - specified.

    jobresume printername unixjobid

    Send a job resume change notify + specified.

    jobresume printername unixjobid

    Send a job resume change notify message for the printer and unix jobid - specified.

    jobdelete printername unixjobid

    Send a job delete change notify + specified.

    jobdelete printername unixjobid

    Send a job delete change notify message for the printer and unix jobid - specified.

    Note that this message only sends notification that an + specified.

    + Note that this message only sends notification that an event has occured. It doesn't actually cause the event to happen. -

    This message can only be sent to smbd.

    samsync

    Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd.

    Not working at the moment

    samrepl

    Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually.

    dmalloc-mark

    Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    dmalloc-log-changed

    Dump the pointers that have changed since the mark set by dmalloc-mark. - Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    shutdown

    Shut down specified daemon. Can be sent to both smbd and nmbd.

    pool-usage

    Print a human-readable description of all +

    This message can only be sent to smbd.

    samsync

    Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd.

    Note

    Not working at the moment

    samrepl

    Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually.

    dmalloc-mark

    Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    dmalloc-log-changed

    + Dump the pointers that have changed since the mark set by dmalloc-mark. + Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.

    shutdown

    Shut down specified daemon. Can be sent to both smbd and nmbd.

    pool-usage

    Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process. Available - for both smbd and nmbd.

    drvupgrade

    Force clients of printers using specified driver + for both smbd and nmbd.

    drvupgrade

    Force clients of printers using specified driver to update their local version of the driver. Can only be - sent to smbd.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    nmbd(8) and smbd(8).

    AUTHOR

    The original Samba software and related utilities + sent to smbd.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    nmbd(8) and smbd(8).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbcquotas.1.html b/docs/htmldocs/smbcquotas.1.html index 334f08bbb9..478c03cdaa 100644 --- a/docs/htmldocs/smbcquotas.1.html +++ b/docs/htmldocs/smbcquotas.1.html @@ -1,391 +1,88 @@ - -smbcquotas

    smbcquotas

    Name

    smbcquotas -- Set or get QUOTAs of NTFS 5 shares

    Synopsis

    smbcquotas {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] [-N] [-k] [-A]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbcquotas program manipulates NT Quotas on SMB file shares.

    OPTIONS

    The following options are available to the smbcquotas program.

    -u user

    Specifies the user of whom the quotas are get or set. - By default the current user's username will be used.

    -L

    Lists all quota records of the share.

    -F

    Show the share quota status and default limits.

    -S QUOTA_SET_COMMAND

    This command set/modify quotas for a user or on the share, - depending on the QUOTA_SET_COMMAND parameter witch is described later

    -n

    This option displays all QUOTA information in numeric +smbcquotas

    Name

    smbcquotas — Set or get QUOTAs of NTFS 5 shares

    Synopsis

    smbcquotas {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] [-N] [-k] [-A]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbcquotas program manipulates NT Quotas on SMB file shares.

    OPTIONS

    The following options are available to the smbcquotas program.

    -u user

    Specifies the user of whom the quotas are get or set. + By default the current user's username will be used.

    -L

    Lists all quota records of the share.

    -F

    Show the share quota status and default limits.

    -S QUOTA_SET_COMMAND

    This command set/modify quotas for a user or on the share, + depending on the QUOTA_SET_COMMAND parameter witch is described later

    -n

    This option displays all QUOTA information in numeric format. The default is to convert SIDs to names and QUOTA limits - to a readable string format.

    -t

    Don't actually do anything, only validate the correctness of + to a readable string format.

    -t

    + Don't actually do anything, only validate the correctness of the arguments. -

    -v

    Be verbose. -

    -h|--help

    Print a summary of command line options.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -v

    + Be verbose. +

    -h|--help

    Print a summary of command line options. +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -N

    If specified, this parameter suppresses the normal +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -N

    If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when -accessing a service that does not require a password.

    Unless a password is specified on the command line or +accessing a service that does not require a password.

    Unless a password is specified on the command line or this parameter is specified, the client will request a -password.

    -k

    Try to authenticate with kerberos. Only useful in -an Active Directory environment.

    -A|--authfile=filename

    This option allows +password.

    -k

    +Try to authenticate with kerberos. Only useful in +an Active Directory environment. +

    -A|--authfile=filename

    This option allows you to specify a file from which to read the username and -password used in the connection. The format of the file is

    username = <value>
-password = <value>
-domain   = <value>

    Make certain that the permissions on the file restrict -access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The -client will first check the USER environment variable, then the -LOGNAME variable and if either exists, the +password used in the connection. The format of the file is +

    +username = <value>
+password = <value>
+domain   = <value>
+

    Make certain that the permissions on the file restrict +access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The +client will first check the USER environment variable, then the +LOGNAME variable and if either exists, the string is uppercased. If these environmental variables are not -found, the username GUEST is used.

    A third option is to use a credentials file which +found, the username GUEST is used.

    A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the --A for more details.

    Be cautious about including passwords in scripts. Also, on +-A for more details.

    Be cautious about including passwords in scripts. Also, on many systems the command line of a running process may be seen -via the ps command. To be safe always allow -rpcclient to prompt for a password and type -it in directly.

    QUOTA_SET_COMAND

    The format of an ACL is one or more ACL entries separated by - either commas or newlines. An ACL entry is one of the following:

    for user setting quotas for the specified by -u or the current username: -

    UQLIM:<username><softlimit><hardlimit> -

    for setting the share quota defaults limits: -

    FSQLIM:<softlimit><hardlimit> -

    for changing the share quota settings: -

    FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT -

    EXIT STATUS

    The smbcquotas program sets the exit status +via the ps command. To be safe always allow +rpcclient to prompt for a password and type +it in directly.

    QUOTA_SET_COMAND

    The format of an ACL is one or more ACL entries separated by + either commas or newlines. An ACL entry is one of the following:

    + for user setting quotas for the specified by -u or the current username: +

    + UQLIM:<username><softlimit><hardlimit> +

    + for setting the share quota defaults limits: +

    + FSQLIM:<softlimit><hardlimit> +

    + for changing the share quota settings: +

    + FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT +

    EXIT STATUS

    The smbcquotas program sets the exit status depending on the success or otherwise of the operations performed. - The exit status may be one of the following values.

    If the operation succeeded, smbcquotas returns an exit - status of 0. If smbcquotas couldn't connect to the specified server, + The exit status may be one of the following values.

    If the operation succeeded, smbcquotas returns an exit + status of 0. If smbcquotas couldn't connect to the specified server, or when there was an error getting or setting the quota(s), an exit status of 1 is returned. If there was an error parsing any command line - arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities + arguments, an exit status of 2 is returned.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    smbcacls was written by Stefan Metzmacher.

    \ No newline at end of file + to the way the Linux kernel is developed.

    smbcacls was written by Stefan Metzmacher.

    diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index afd70cbe03..2ae976c3e8 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -1,783 +1,183 @@ - -smbd

    smbd

    Name

    smbd -- server to provide SMB/CIFS services to clients

    Synopsis

    smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    smbd is the server daemon that +smbd

    Name

    smbd — server to provide SMB/CIFS services to clients

    Synopsis

    smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    smbd is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, - OS/2, DAVE for Macintosh, and smbfs for Linux.

    An extensive description of the services that the + OS/2, DAVE for Macintosh, and smbfs for Linux.

    An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those - services (see smb.conf(5). This man page will not describe the + services (see smb.conf(5). This man page will not describe the services, but will concentrate on the administrative aspects - of running the server.

    Please note that there are significant security - implications to running this server, and the smb.conf(5) manual page should be regarded as mandatory reading before - proceeding with installation.

    A session is created whenever a client requests one. + of running the server.

    Please note that there are significant security + implications to running this server, and the smb.conf(5) manual page should be regarded as mandatory reading before + proceeding with installation.

    A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all connections from its client are closed, - the copy of the server for that client terminates.

    The configuration file, and any files that it includes, + the copy of the server for that client terminates.

    The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to - disconnect from the service, or smbd killed and restarted.

    OPTIONS

    -D

    If specified, this parameter causes + disconnect from the service, or smbd killed and restarted.

    OPTIONS

    -D

    If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a - daemon is the recommended way of running smbd for + daemon is the recommended way of running smbd for servers that provide more than casual use file and - print services. This switch is assumed if smbd - is executed on the command line of a shell. -

    -F

    If specified, this parameter causes - the main smbd process to not daemonize, + print services. This switch is assumed if smbd + is executed on the command line of a shell. +

    -F

    If specified, this parameter causes + the main smbd process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running - smbd under process supervisors such - as supervise and svscan - from Daniel J. Bernstein's daemontools + smbd under process supervisors such + as supervise and svscan + from Daniel J. Bernstein's daemontools package, or the AIX process monitor. -

    -S

    If specified, this parameter causes - smbd to log to standard output rather - than a file.

    -i

    If this parameter is specified it causes the - server to run "interactively", not as a daemon, even if the +

    -S

    If specified, this parameter causes + smbd to log to standard output rather + than a file.

    -i

    If this parameter is specified it causes the + server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell. Setting this parameter negates the implicit deamon mode when run from the - command line. smbd also logs to standard - output, as if the -S parameter had been + command line. smbd also logs to standard + output, as if the -S parameter had been given. -

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -h|--help

    Print a summary of command line options.

    -b

    Prints information about how - Samba was built.

    -l <log directory>

    If specified, - log directory - specifies a log directory into which the "log.smbd" log +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -h|--help

    Print a summary of command line options. +

    -b

    Prints information about how + Samba was built.

    -l <log directory>

    If specified, + log directory + specifies a log directory into which the "log.smbd" log file will be created for informational and debug messages from the running server. The log file generated is never removed by the server although - its size may be controlled by the max log size - option in the smb.conf(5) file. Beware: - If the directory specified does not exist, smbd + its size may be controlled by the max log size + option in the smb.conf(5) file. Beware: + If the directory specified does not exist, smbd will log to the default debug log location defined at compile time. -

    The default log directory is specified at - compile time.

    -p <port number>

    port number is a positive integer +

    The default log directory is specified at + compile time.

    -p <port number>

    port number is a positive integer value. The default value if this parameter is not - specified is 139.

    This number is the port number that will be + specified is 139.

    This number is the port number that will be used when making connections to the server from client software. The standard (well-known) port number for the SMB over TCP is 139, hence the default. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator - for help if you are in this situation.

    In order for the server to be useful by most + for help if you are in this situation.

    In order for the server to be useful by most clients, should you configure it on a port other than 139, you will require port redirection services on port 139, details of which are outlined in rfc1002.txt - section 4.3.5.

    This parameter is not normally specified except - in the above situation.

    FILES

    /etc/inetd.conf

    If the server is to be run by the - inetd meta-daemon, this file + section 4.3.5.

    This parameter is not normally specified except + in the above situation.

    FILES

    /etc/inetd.conf

    If the server is to be run by the + inetd meta-daemon, this file must contain suitable startup information for the - meta-daemon. See the "How to Install and Test SAMBA" + meta-daemon. See the "How to Install and Test SAMBA" document for details. -

    /etc/rc

    or whatever initialization script your - system uses).

    If running the server as a daemon at startup, +

    /etc/rc

    or whatever initialization script your + system uses).

    If running the server as a daemon at startup, this file will need to contain an appropriate startup - sequence for the server. See the "How to Install and Test SAMBA" - document for details.

    /etc/services

    If running the server via the - meta-daemon inetd, this file + sequence for the server. See the "How to Install and Test SAMBA" + document for details.

    /etc/services

    If running the server via the + meta-daemon inetd, this file must contain a mapping of service name (e.g., netbios-ssn) to service port (e.g., 139) and protocol type (e.g., tcp). - See the "How to Install and Test SAMBA" - document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file. Other common places that systems - install this file are /usr/samba/lib/smb.conf - and /etc/samba/smb.conf.

    This file describes all the services the server - is to make available to clients. See smb.conf(5) for more information.

    LIMITATIONS

    On some systems smbd cannot change uid back + See the "How to Install and Test SAMBA" + document for details.

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file. Other common places that systems + install this file are /usr/samba/lib/smb.conf + and /etc/samba/smb.conf.

    This file describes all the services the server + is to make available to clients. See smb.conf(5) for more information.

    LIMITATIONS

    On some systems smbd cannot change uid back to root after a setuid() call. Such systems are called trapdoor uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or - similar.

    ENVIRONMENT VARIABLES

    PRINTER

    If no printer name is specified to + similar.

    ENVIRONMENT VARIABLES

    PRINTER

    If no printer name is specified to printable services, most systems will use the value of - this variable (or lp if this variable is + this variable (or lp if this variable is not defined) as the name of the printer to use. This - is not specific to the server, however.

    PAM INTERACTION

    Samba uses PAM for authentication (when presented with a plaintext + is not specific to the server, however.

    PAM INTERACTION

    Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted - by the limitations of the SMB protocol and the obey - pam restricions smb.conf(5) paramater. When this is set, the following restrictions apply: -

    • Account Validation: All accesses to a + by the limitations of the SMB protocol and the obey + pam restricions smb.conf(5) paramater. When this is set, the following restrictions apply: +

      • Account Validation: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time. This also applies to encrypted logins. -

      • Session Management: When not using share +

      • Session Management: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support. -

      VERSION

      This man page is correct for version 3.0 of - the Samba suite.

      DIAGNOSTICS

      Most diagnostics issued by the server are logged +

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    DIAGNOSTICS

    Most diagnostics issued by the server are logged in a specified log file. The log file name is specified - at compile time, but may be overridden on the command line.

    The number and nature of diagnostics available depends + at compile time, but may be overridden on the command line.

    The number and nature of diagnostics available depends on the debug level used by the server. If you have problems, set - the debug level to 3 and peruse the log files.

    Most messages are reasonably self-explanatory. Unfortunately, + the debug level to 3 and peruse the log files.

    Most messages are reasonably self-explanatory. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the - diagnostics you are seeing.

    SIGNALS

    Sending the smbd a SIGHUP will cause it to - reload its smb.conf configuration - file within a short period of time.

    To shut down a user's smbd process it is recommended - that SIGKILL (-9) NOT + diagnostics you are seeing.

    SIGNALS

    Sending the smbd a SIGHUP will cause it to + reload its smb.conf configuration + file within a short period of time.

    To shut down a user's smbd process it is recommended + that SIGKILL (-9) NOT be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate - an smbd is to send it a SIGTERM (-15) signal and wait for - it to die on its own.

    The debug log level of smbd may be raised - or lowered using smbcontrol(1) program (SIGUSR[1|2] signals are no longer + an smbd is to send it a SIGTERM (-15) signal and wait for + it to die on its own.

    The debug log level of smbd may be raised + or lowered using smbcontrol(1) program (SIGUSR[1|2] signals are no longer used since Samba 2.2). This is to allow transient problems to be diagnosed, - whilst still running at a normally low log level.

    Note that as the signal handlers send a debug write, - they are not re-entrant in smbd. This you should wait until - smbd is in a state of waiting for an incoming SMB before + whilst still running at a normally low log level.

    Note that as the signal handlers send a debug write, + they are not re-entrant in smbd. This you should wait until + smbd is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking - them after, however this would affect performance.

    SEE ALSO

    hosts_access(5), inetd(8), nmbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the - Internet RFC's rfc1001.txt, rfc1002.txt. + them after, however this would affect performance.

    SEE ALSO

    hosts_access(5), inetd(8), nmbd(8), smb.conf(5), smbclient(1), testparm(1), testprns(1), and the + Internet RFC's rfc1001.txt, rfc1002.txt. In addition the CIFS (formerly SMB) specification is available - as a link from the Web page - http://samba.org/cifs/.

    AUTHOR

    The original Samba software and related utilities + as a link from the Web page + http://samba.org/cifs/.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index 28be79c391..d577a6a3a7 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -1,184 +1,24 @@ - -smbmnt

    smbmnt

    Name

    smbmnt -- helper utility for mounting SMB filesystems

    Synopsis

    smbmnt {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]

    DESCRIPTION

    smbmnt is a helper application used +smbmnt

    Name

    smbmnt — helper utility for mounting SMB filesystems

    Synopsis

    smbmnt {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]

    DESCRIPTION

    smbmnt is a helper application used by the smbmount program to do the actual mounting of SMB shares. - smbmnt can be installed setuid root if you want - normal users to be able to mount their SMB shares.

    A setuid smbmnt will only allow mounts on directories owned - by the user, and that the user has write permission on.

    The smbmnt program is normally invoked - by smbmount(8). It should not be invoked directly by users.

    smbmount searches the normal PATH for smbmnt. You must ensure - that the smbmnt version in your path matches the smbmount used.

    OPTIONS

    -r

    mount the filesystem read-only -

    -u uid

    specify the uid that the files will - be owned by

    -g gid

    specify the gid that the files will be - owned by

    -f mask

    specify the octal file mask applied -

    -d mask

    specify the octal directory mask - applied

    -o options

    list of options that are passed as-is to smbfs, if this + smbmnt can be installed setuid root if you want + normal users to be able to mount their SMB shares.

    A setuid smbmnt will only allow mounts on directories owned + by the user, and that the user has write permission on.

    The smbmnt program is normally invoked + by smbmount(8). It should not be invoked directly by users.

    smbmount searches the normal PATH for smbmnt. You must ensure + that the smbmnt version in your path matches the smbmount used.

    OPTIONS

    -r

    mount the filesystem read-only +

    -u uid

    specify the uid that the files will + be owned by

    -g gid

    specify the gid that the files will be + owned by

    -f mask

    specify the octal file mask applied +

    -d mask

    specify the octal directory mask + applied

    -o options

    + list of options that are passed as-is to smbfs, if this command is run on a 2.4 or higher Linux kernel. -

    -h|--help

    Print a summary of command line options.

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.

    The current maintainer of smbfs and the userspace - tools smbmount, smbumount, - and smbmnt is Urban Widmark. - The SAMBA Mailing list +

    -h|--help

    Print a summary of command line options. +

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.

    The current maintainer of smbfs and the userspace + tools smbmount, smbumount, + and smbmnt is Urban Widmark. + The SAMBA Mailing list is the preferred place to ask questions regarding these programs. -

    The conversion of this manpage for Samba 2.2 was performed +

    The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.

    \ No newline at end of file + was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index 5ea2935a3f..94560fba66 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -1,329 +1,70 @@ - -smbmount

    smbmount

    Name

    smbmount -- mount an smbfs filesystem

    Synopsis

    smbmount {service} {mount-point} [-o options]

    DESCRIPTION

    smbmount mounts a Linux SMB filesystem. It - is usually invoked as mount.smbfs by - the mount(8) command when using the - "-t smbfs" option. This command only works in Linux, and the kernel must - support the smbfs filesystem.

    Options to smbmount are specified as a comma-separated +smbmount

    Name

    smbmount — mount an smbfs filesystem

    Synopsis

    smbmount {service} {mount-point} [-o options]

    DESCRIPTION

    smbmount mounts a Linux SMB filesystem. It + is usually invoked as mount.smbfs by + the mount(8) command when using the + "-t smbfs" option. This command only works in Linux, and the kernel must + support the smbfs filesystem.

    Options to smbmount are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on - unknown options.

    smbmount is a daemon. After mounting it keeps running until + unknown options.

    smbmount is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen - when in daemon mode using the "machine name" smbmount, so - typically this output will end up in log.smbmount. The smbmount process may also be called mount.smbfs.

    NOTE: smbmount - calls smbmnt(8) to do the actual mount. You - must make sure that smbmnt is in the path so - that it can be found.

    OPTIONS

    username=<arg>

    specifies the username to connect as. If - this is not given, then the environment variable USER is used. This option can also take the - form "user%password" or "user/workgroup" or - "user/workgroup%password" to allow the password and workgroup - to be specified as part of the username.

    password=<arg>

    specifies the SMB password. If this + when in daemon mode using the "machine name" smbmount, so + typically this output will end up in log.smbmount. The + smbmount process may also be called mount.smbfs.

    NOTE: smbmount + calls smbmnt(8) to do the actual mount. You + must make sure that smbmnt is in the path so + that it can be found.

    OPTIONS

    username=<arg>

    specifies the username to connect as. If + this is not given, then the environment variable + USER is used. This option can also take the + form "user%password" or "user/workgroup" or + "user/workgroup%password" to allow the password and workgroup + to be specified as part of the username.

    password=<arg>

    specifies the SMB password. If this option is not given then the environment variable - PASSWD is used. If it can find - no password smbmount will prompt + PASSWD is used. If it can find + no password smbmount will prompt for a passeword, unless the guest option is - given.

    Note that passwords which contain the argument delimiter + given.

    + Note that passwords which contain the argument delimiter character (i.e. a comma ',') will failed to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly. -

    credentials=<filename>

    specifies a file that contains a username and/or password. +

    credentials=<filename>

    specifies a file that contains a username and/or password. The format of the file is: -

    username = <value>
-password = <value>

    This is preferred over having passwords in plaintext in a - shared file, such as /etc/fstab. Be sure to protect any +

    +username = <value>
+password = <value>
+

    This is preferred over having passwords in plaintext in a + shared file, such as /etc/fstab. Be sure to protect any credentials file properly. -

    krb

    Use kerberos (Active Directory).

    netbiosname=<arg>

    sets the source NetBIOS name. It defaults - to the local hostname.

    uid=<arg>

    sets the uid that will own all files on +

    krb

    Use kerberos (Active Directory).

    netbiosname=<arg>

    sets the source NetBIOS name. It defaults + to the local hostname.

    uid=<arg>

    sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid. -

    gid=<arg>

    sets the gid that will own all files on +

    gid=<arg>

    sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric - gid.

    port=<arg>

    sets the remote SMB port number. The default - is 139.

    fmask=<arg>

    sets the file mask. This determines the + gid.

    port=<arg>

    sets the remote SMB port number. The default + is 139.

    fmask=<arg>

    sets the file mask. This determines the permissions that remote files have in the local filesystem. - The default is based on the current umask.

    dmask=<arg>

    Sets the directory mask. This determines the + The default is based on the current umask.

    dmask=<arg>

    Sets the directory mask. This determines the permissions that remote directories have in the local filesystem. - The default is based on the current umask.

    debug=<arg>

    Sets the debug level. This is useful for + The default is based on the current umask.

    debug=<arg>

    Sets the debug level. This is useful for tracking down SMB connection problems. A suggested value to start with is 4. If set too high there will be a lot of - output, possibly hiding the useful output.

    ip=<arg>

    Sets the destination host or IP address. -

    workgroup=<arg>

    Sets the workgroup on the destination

    sockopt=<arg>

    Sets the TCP socket options. See the smb.conf(5) socket options option. -

    scope=<arg>

    Sets the NetBIOS scope

    guest

    Don't prompt for a password

    ro

    mount read-only

    rw

    mount read-write

    iocharset=<arg>

    sets the charset used by the Linux side for codepage + output, possibly hiding the useful output.

    ip=<arg>

    Sets the destination host or IP address. +

    workgroup=<arg>

    Sets the workgroup on the destination

    sockopt=<arg>

    Sets the TCP socket options. See the smb.conf(5) socket options option. +

    scope=<arg>

    Sets the NetBIOS scope

    guest

    Don't prompt for a password

    ro

    mount read-only

    rw

    mount read-write

    iocharset=<arg>

    + sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later) -

    codepage=<arg>

    sets the codepage the server uses. See the iocharset +

    codepage=<arg>

    + sets the codepage the server uses. See the iocharset option. Example value cp850. (Note: only kernel 2.4.0 or later) -

    ttl=<arg>

    sets how long a directory listing is cached in milliseconds +

    ttl=<arg>

    + sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes). A higher value means that changes on the server take longer to be noticed but it can give @@ -332,139 +73,34 @@ CLASS="PARAMETER" like 10000ms (10 seconds) is probably more reasonable in many cases. (Note: only kernel 2.4.2 or later) -

    ENVIRONMENT VARIABLES

    The variable USER may contain the username of the +

    ENVIRONMENT VARIABLES

    The variable USER may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. The variable can be used to set both username and - password by using the format username%password.

    The variable PASSWD may contain the password of the + password by using the format username%password.

    The variable PASSWD may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level - passwords.

    The variable PASSWD_FILE may contain the pathname + passwords.

    The variable PASSWD_FILE may contain the pathname of a file to read the password from. A single line of input is - read and used as the password.

    BUGS

    Passwords and other options containing , can not be handled. + read and used as the password.

    BUGS

    Passwords and other options containing , can not be handled. For passwords an alternative way of passing them is in a credentials - file or in the PASSWD environment.

    The credentials file does not handle usernames or passwords with - leading space.

    One smbfs bug is important enough to mention here, even if it - is a bit misplaced:

    • Mounts sometimes stop working. This is usually + file or in the PASSWD environment.

      The credentials file does not handle usernames or passwords with + leading space.

      One smbfs bug is important enough to mention here, even if it + is a bit misplaced:

      • Mounts sometimes stop working. This is usually caused by smbmount terminating. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead. An umount/mount normally fixes this. At least 2 ways to - trigger this bug are known.

      Note that the typical response to a bug report is suggestion + trigger this bug are known.

    Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software - when reporting bugs (minimum: samba, kernel, distribution)

    SEE ALSO

    Documentation/filesystems/smbfs.txt in the linux kernel - source tree may contain additional options and information.

    FreeBSD also has a smbfs, but it is not related to smbmount

    For Solaris, HP-UX and others you may want to look at smbsh(1) or at other solutions, such as - Sharity or perhaps replacing the SMB server with a NFS server.

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.

    The current maintainer of smbfs and the userspace - tools smbmount, smbumount, - and smbmnt is Urban Widmark. - The SAMBA Mailing list + when reporting bugs (minimum: samba, kernel, distribution)

    SEE ALSO

    Documentation/filesystems/smbfs.txt in the linux kernel + source tree may contain additional options and information.

    FreeBSD also has a smbfs, but it is not related to smbmount

    For Solaris, HP-UX and others you may want to look at smbsh(1) or at other solutions, such as + Sharity or perhaps replacing the SMB server with a NFS server.

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.

    The current maintainer of smbfs and the userspace + tools smbmount, smbumount, + and smbmnt is Urban Widmark. + The SAMBA Mailing list is the preferred place to ask questions regarding these programs. -

    The conversion of this manpage for Samba 2.2 was performed +

    The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.

    \ No newline at end of file + was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 61b60d7d82..82cb3450e9 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -1,358 +1,89 @@ - -smbpasswd

    smbpasswd

    Name

    smbpasswd -- The Samba encrypted password file

    Synopsis

    smbpasswd

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbpasswd is the Samba encrypted password file. It contains +smbpasswd

    Name

    smbpasswd — The Samba encrypted password file

    Synopsis

    smbpasswd

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with - Samba and has had several different formats in the past.

    FILE FORMAT

    The format of the smbpasswd file used by Samba 2.2 - is very similar to the familiar Unix passwd(5) + Samba and has had several different formats in the past.

    FILE FORMAT

    The format of the smbpasswd file used by Samba 2.2 + is very similar to the familiar Unix passwd(5) file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The smbpasswd file contains the - following information for each user:

    name

    This is the user name. It must be a name that - already exists in the standard UNIX passwd file.

    uid

    This is the UNIX uid. It must match the uid + following information for each user:

    name

    This is the user name. It must be a name that + already exists in the standard UNIX passwd file.

    uid

    This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user. -

    Lanman Password Hash

    This is the LANMAN hash of the user's password, +

    Lanman Password Hash

    This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password - is not "salted" as the UNIX password is). If the user has a - null password this field will contain the characters "NO PASSWORD" + is not "salted" as the UNIX password is). If the user has a + null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as - disabled and the user will not be able to - log onto the Samba server.

    WARNING !! Note that, due to + disabled and the user will not be able to + log onto the Samba server.

    WARNING !! Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this - reason these hashes are known as plain text - equivalents and must NOT be made + reason these hashes are known as plain text + equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no - other access.

    NT Password Hash

    This is the Windows NT hash of the user's + other access.

    NT Password Hash

    This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 - (internet rfc1321) hashing algorithm to it.

    This password hash is considered more secure than + (internet rfc1321) hashing algorithm to it.

    This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is - not "salted" as the UNIX password is).

    WARNING !!. Note that, due to + not "salted" as the UNIX password is).

    WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this - reason these hashes are known as plain text - equivalents and must NOT be made + reason these hashes are known as plain text + equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no - other access.

    Account Flags

    This section contains flags that describe + other access.

    Account Flags

    This section contains flags that describe the attributes of the users account. In the Samba 2.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters: -

    • U - This means - this is a "User" account, i.e. an ordinary user. Only User +

      • U - This means + this is a "User" account, i.e. an ordinary user. Only User and Workstation Trust accounts are currently supported - in the smbpasswd file.

      • N - This means the + in the smbpasswd file.

      • N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this - will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(5) config file.

      • D - This means the account - is disabled and no SMB/CIFS logins will be allowed for this user.

      • W - This means this account - is a "Workstation Trust" account. This kind of account is used + will only allow users to log on with no password if the + null passwords parameter is set in the smb.conf(5) config file.

      • D - This means the account + is disabled and no SMB/CIFS logins will be allowed for this user.

      • W - This means this account + is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations - and Servers to join a Domain hosted by a Samba PDC.

      Other flags may be added as the code is extended in future. - The rest of this field space is filled in with spaces.

    Last Change Time

    This field consists of the time the account was + and Servers to join a Domain hosted by a Samba PDC.

    Other flags may be added as the code is extended in future. + The rest of this field space is filled in with spaces.

    Last Change Time

    This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for - "Last Change Time") followed by a numeric encoding of the UNIX time + "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made. -

    All other colon separated fields are ignored at this time.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    smbpasswd(8), Samba(7), and +

    All other colon separated fields are ignored at this time.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm. -

    AUTHOR

    The original Samba software and related utilities +

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 6b227f9d1e..44a1089e13 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -1,640 +1,163 @@ - -smbpasswd

    smbpasswd

    Name

    smbpasswd -- change a user's SMB password

    Synopsis

    smbpasswd [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbpasswd program has several different - functions, depending on whether it is run by the root user +smbpasswd

    Name

    smbpasswd — change a user's SMB password

    Synopsis

    smbpasswd [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The smbpasswd program has several different + functions, depending on whether it is run by the root user or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store - SMB passwords.

    By default (when run with no arguments) it will attempt to + SMB passwords.

    By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine. This is - similar to the way the passwd(1) program works. smbpasswd differs from how the passwd program works - however in that it is not setuid root but works in + similar to the way the passwd(1) program works. + smbpasswd differs from how the passwd program works + however in that it is not setuid root but works in a client-server mode and communicates with a - locally running smbd(8). As a consequence in order for this to + locally running smbd(8). As a consequence in order for this to succeed the smbd daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in - the smbpasswd(5) file.

    When run by an ordinary user with no options, smbpasswd + the smbpasswd(5) file.

    When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by - the string "NO PASSWORD" in the smbpasswd file) then just press - the <Enter> key when asked for your old password.

    smbpasswd can also be used by a normal user to change their + the string "NO PASSWORD" in the smbpasswd file) then just press + the <Enter> key when asked for your old password.

    smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain - Controllers. See the (-r) and -U options - below.

    When run by root, smbpasswd allows new users to be added + Controllers. See the (-r) and -U options + below.

    When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to - the attributes of the user in this file to be made. When run by root, smbpasswd accesses the local smbpasswd file + the attributes of the user in this file to be made. When run by root, + smbpasswd accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not - running.

    OPTIONS

    -a

    This option specifies that the username + running.

    OPTIONS

    -a

    This option specifies that the username following should be added to the local smbpasswd file, with the - new password typed (type <Enter> for the old password). This + new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command. Note that the default passdb backends require the user to already exist in the system password file (usually - /etc/passwd), else the request to add the - user will fail.

    This option is only available when running smbpasswd - as root.

    -x

    This option specifies that the username + /etc/passwd), else the request to add the + user will fail.

    This option is only available when running smbpasswd + as root.

    -x

    This option specifies that the username following should be deleted from the local smbpasswd file. -

    This option is only available when running smbpasswd as - root.

    -d

    This option specifies that the username following - should be disabled in the local smbpasswd - file. This is done by writing a 'D' flag +

    This option is only available when running smbpasswd as + root.

    -d

    This option specifies that the username following + should be disabled in the local smbpasswd + file. This is done by writing a 'D' flag into the account control space in the smbpasswd file. Once this is done all attempts to authenticate via SMB using this username - will fail.

    If the smbpasswd file is in the 'old' format (pre-Samba 2.0 + will fail.

    If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write - this information and the command will FAIL. See smbpasswd(5) for details on the 'old' and new password file formats. -

    This option is only available when running smbpasswd as - root.

    -e

    This option specifies that the username following - should be enabled in the local smbpasswd file, + this information and the command will FAIL. See smbpasswd(5) for details on the 'old' and new password file formats. +

    This option is only available when running smbpasswd as + root.

    -e

    This option specifies that the username following + should be enabled in the local smbpasswd file, if the account was previously disabled. If the account was not disabled this option has no effect. Once the account is enabled then - the user will be able to authenticate via SMB once again.

    If the smbpasswd file is in the 'old' format, then smbpasswd will FAIL to enable the account. - See smbpasswd(5) for - details on the 'old' and new password file formats.

    This option is only available when running smbpasswd as root. -

    -D debuglevel

    debuglevel is an integer + the user will be able to authenticate via SMB once again.

    If the smbpasswd file is in the 'old' format, then + smbpasswd will FAIL to enable the account. + See smbpasswd(5) for + details on the 'old' and new password file formats.

    This option is only available when running smbpasswd as root. +

    -D debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is not specified - is zero.

    The higher this value, the more detail will be logged to the + is zero.

    The higher this value, the more detail will be logged to the log files about the activities of smbpasswd. At level 0, only - critical errors and serious warnings will be logged.

    Levels above 1 will generate considerable amounts of log + critical errors and serious warnings will be logged.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. -

    -n

    This option specifies that the username following +

    -n

    This option specifies that the username following should have their password set to null (i.e. a blank password) in - the local smbpasswd file. This is done by writing the string "NO - PASSWORD" as the first part of the first password stored in the - smbpasswd file.

    Note that to allow users to logon to a Samba server once - the password has been set to "NO PASSWORD" in the smbpasswd + the local smbpasswd file. This is done by writing the string "NO + PASSWORD" as the first part of the first password stored in the + smbpasswd file.

    Note that to allow users to logon to a Samba server once + the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] - section of the smb.conf file :

    null passwords = yes

    This option is only available when running smbpasswd as - root.

    -r remote machine name

    This option allows a user to specify what machine + section of the smb.conf file :

    null passwords = yes

    This option is only available when running smbpasswd as + root.

    -r remote machine name

    This option allows a user to specify what machine they wish to change their password on. Without this parameter - smbpasswd defaults to the local host. The remote - machine name is the NetBIOS name of the SMB/CIFS + smbpasswd defaults to the local host. The remote + machine name is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change. This name is resolved into an IP address using the standard name resolution - mechanism in all programs of the Samba suite. See the -R - name resolve order parameter for details on changing - this resolving mechanism.

    The username whose password is changed is that of the - current UNIX logged on user. See the -U username + mechanism in all programs of the Samba suite. See the -R + name resolve order parameter for details on changing + this resolving mechanism.

    The username whose password is changed is that of the + current UNIX logged on user. See the -U username parameter for details on changing the password for a different - username.

    Note that if changing a Windows NT Domain password the + username.

    Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read-only copy of the user account database and will not allow the password - change).

    Note that Windows 95/98 do not have + change).

    Note that Windows 95/98 do not have a real password database so it is not possible to change passwords - specifying a Win95/98 machine as remote machine target.

    -R name resolve order

    This option allows the user of smbpasswd to determine + specifying a Win95/98 machine as remote machine target.

    -R name resolve order

    This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS - name of the host being connected to.

    The options are :"lmhosts", "host", "wins" and "bcast". They - cause names to be resolved as follows:

    • lmhosts: Lookup an IP + name of the host being connected to.

      The options are :"lmhosts", "host", "wins" and "bcast". They + cause names to be resolved as follows:

      • lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has - no name type attached to the NetBIOS name (see the lmhosts(5) for details) then - any name type matches for lookup.

      • host: Do a standard host - name to IP address resolution, using the system /etc/hosts - , NIS, or DNS lookups. This method of name resolution + no name type attached to the NetBIOS name (see the lmhosts(5) for details) then + any name type matches for lookup.

      • host: Do a standard host + name to IP address resolution, using the system /etc/hosts + , NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this - may be controlled by the /etc/nsswitch.conf + may be controlled by the /etc/nsswitch.conf file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise - it is ignored.

      • wins: Query a name with - the IP address listed in the wins server + it is ignored.

      • wins: Query a name with + the IP address listed in the wins server parameter. If no WINS server has been specified this method - will be ignored.

      • bcast: Do a broadcast on + will be ignored.

      • bcast: Do a broadcast on each of the known local interfaces listed in the - interfaces parameter. This is the least + interfaces parameter. This is the least reliable of the name resolution methods as it depends on the - target host being on a locally connected subnet.

      The default order is lmhosts, host, wins, bcast - and without this parameter or any entry in the smb.conf(5) file the name resolution methods will - be attempted in this order.

    -m

    This option tells smbpasswd that the account + target host being on a locally connected subnet.

    The default order is lmhosts, host, wins, bcast + and without this parameter or any entry in the smb.conf(5) file the name resolution methods will + be attempted in this order.

    -m

    This option tells smbpasswd that the account being changed is a MACHINE account. Currently this is used - when Samba is being used as an NT Primary Domain Controller.

    This option is only available when running smbpasswd as root. -

    -U username

    This option may only be used in conjunction - with the -r option. When changing + when Samba is being used as an NT Primary Domain Controller.

    This option is only available when running smbpasswd as root. +

    -U username

    This option may only be used in conjunction + with the -r option. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed. It is present to allow users who have different user names on - different systems to change these passwords.

    -h

    This option prints the help string for smbpasswd, selecting the correct one for running as root - or as an ordinary user.

    -s

    This option causes smbpasswd to be silent (i.e. + different systems to change these passwords.

    -h

    This option prints the help string for + smbpasswd, selecting the correct one for running as root + or as an ordinary user.

    -s

    This option causes smbpasswd to be silent (i.e. not issue prompts) and to read its old and new passwords from - standard input, rather than from /dev/tty - (like the passwd(1) program does). This option - is to aid people writing scripts to drive smbpasswd

    -w password

    This parameter is only available if Samba + standard input, rather than from /dev/tty + (like the passwd(1) program does). This option + is to aid people writing scripts to drive smbpasswd

    -w password

    This parameter is only available if Samba has been configured to use the experimental - --with-ldapsam option. The -w + --with-ldapsam option. The -w switch is used to specify the password to be used with the - ldap admin - dn. Note that the password is stored in - the secrets.tdb and is keyed off - of the admin's DN. This means that if the value of ldap - admin dn ever changes, the password will need to be + ldap admin + dn. Note that the password is stored in + the secrets.tdb and is keyed off + of the admin's DN. This means that if the value of ldap + admin dn ever changes, the password will need to be manually updated as well. -

    -i

    This option tells smbpasswd that the account +

    -i

    This option tells smbpasswd that the account being changed is an interdomain trust account. Currently this is used when Samba is being used as an NT Primary Domain Controller. - The account contains the info about another trusted domain.

    This option is only available when running smbpasswd as root. -

    -L

    Run in local mode.

    username

    This specifies the username for all of the - root only options to operate on. Only root + The account contains the info about another trusted domain.

    This option is only available when running smbpasswd as root. +

    -L

    Run in local mode.

    username

    This specifies the username for all of the + root only options to operate on. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file. -

    NOTES

    Since smbpasswd works in client-server +

    NOTES

    Since smbpasswd works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work. A common problem - is to add a restriction to the hosts that may access the smbd running on the local machine by specifying either allow - hosts or deny hosts entry in - the smb.conf(5) file and neglecting to - allow "localhost" access to the smbd.

    In addition, the smbpasswd command is only useful if Samba - has been set up to use encrypted passwords. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details - on how to do this.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbpasswd(5), Samba(7).

    AUTHOR

    The original Samba software and related utilities + is to add a restriction to the hosts that may access the + smbd running on the local machine by specifying either allow + hosts or deny hosts entry in + the smb.conf(5) file and neglecting to + allow "localhost" access to the smbd.

    In addition, the smbpasswd command is only useful if Samba + has been set up to use encrypted passwords. See the document + "LanMan and NT Password Encryption in Samba" in the docs directory for details + on how to do this.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbpasswd(5), Samba(7).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 0ed7722b71..942f617920 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -1,479 +1,110 @@ - -smbsh

    smbsh

    Name

    smbsh -- Allows access to Windows NT filesystem - using UNIX commands

    Synopsis

    smbsh [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbsh allows you to access an NT filesystem - using UNIX commands such as ls, egrep, and rcp. You must use a - shell that is dynamically linked in order for smbsh - to work correctly.

    OPTIONS

    -W WORKGROUP

    Override the default workgroup specified in the - workgroup parameter of the smb.conf(5) file +smbsh

    Name

    smbsh — Allows access to Windows NT filesystem + using UNIX commands

    Synopsis

    smbsh [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbsh allows you to access an NT filesystem + using UNIX commands such as ls, + egrep, and rcp. You must use a + shell that is dynamically linked in order for smbsh + to work correctly.

    OPTIONS

    -W WORKGROUP

    Override the default workgroup specified in the + workgroup parameter of the smb.conf(5) file for this session. This may be needed to connect to some - servers.

    -U username[%pass]

    Sets the SMB username or username and password. + servers.

    -U username[%pass]

    Sets the SMB username or username and password. If this option is not specified, the user will be prompted for both the username and the password. If %pass is not specified, the user will be prompted for the password. -

    -P prefix

    This option allows +

    -P prefix

    This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is - smb. -

    -s <configuration file>

    The file specified contains the + smb. +

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -R <name resolve order>

    This option is used to determine what naming +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -R <name resolve order>

    This option is used to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated -string of different name resolution options.

    The options are: "lmhosts", "host", "wins" and "bcast". -They cause names to be resolved as follows :

    • lmhosts: +string of different name resolution options.

      The options are: "lmhosts", "host", "wins" and "bcast". +They cause names to be resolved as follows :

      • lmhosts: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name -(see the lmhosts(5) for details) -then any name type matches for lookup.

      • host: +(see the lmhosts(5) for details) +then any name type matches for lookup. +

      • host: Do a standard host name to IP address resolution, using -the system /etc/hosts, NIS, or DNS +the system /etc/hosts, NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this -may be controlled by the /etc/nsswitch.conf file). Note that this method is only used +may be controlled by the /etc/nsswitch.conf + file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 -(server) name type, otherwise it is ignored.

      • wins: +(server) name type, otherwise it is ignored. +

      • wins: Query a name with the IP address listed in the -wins server parameter. If no +wins server parameter. If no WINS server has been specified this method will be -ignored.

      • bcast: +ignored. +

      • bcast: Do a broadcast on each of the known local interfaces -listed in the interfaces +listed in the interfaces parameter. This is the least reliable of the name resolution methods as it depends on the target host -being on a locally connected subnet.

      If this parameter is not set then the name resolve order -defined in the smb.conf(5) file parameter -(name resolve order) will be used.

      The default order is lmhosts, host, wins, bcast. Without -this parameter or any entry in the name resolve order parameter of the smb.conf(5) file, the name resolution methods -will be attempted in this order.

    -L libdir

    This parameter specifies the location of the - shared libraries used by smbsh. The default +being on a locally connected subnet. +

    If this parameter is not set then the name resolve order +defined in the smb.conf(5) file parameter +(name resolve order) will be used.

    The default order is lmhosts, host, wins, bcast. Without +this parameter or any entry in the name resolve order + parameter of the smb.conf(5) file, the name resolution methods +will be attempted in this order.

    -L libdir

    This parameter specifies the location of the + shared libraries used by smbsh. The default value is specified at compile time. -

    EXAMPLES

    To use the smbsh command, execute smbsh from the prompt and enter the username and password +

    EXAMPLES

    To use the smbsh command, execute + smbsh from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system. -

    system% smbsh
-Username: user
-Password: XXXXXXX

    Any dynamically linked command you execute from - this shell will access the /smb directory - using the smb protocol. For example, the command ls /smb - will show a list of workgroups. The command - ls /smb/MYGROUP will show all the machines in +

    +system% smbsh
+Username: user
+Password: XXXXXXX
+

    Any dynamically linked command you execute from + this shell will access the /smb directory + using the smb protocol. For example, the command ls /smb + will show a list of workgroups. The command + ls /smb/MYGROUP will show all the machines in the workgroup MYGROUP. The command - ls /smb/MYGROUP/<machine-name> will show the share - names for that machine. You could then, for example, use the cd command to change directories, vi to - edit files, and rcp to copy files.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    BUGS

    smbsh works by intercepting the standard - libc calls with the dynamically loaded versions in smbwrapper.o. Not all calls have been "wrapped", so - some programs may not function correctly under smbsh - .

    Programs which are not dynamically linked cannot make - use of smbsh's functionality. Most versions - of UNIX have a file command that will - describe how a program was linked.

    SEE ALSO

    smbd(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities + ls /smb/MYGROUP/<machine-name> will show the share + names for that machine. You could then, for example, use the + cd command to change directories, vi to + edit files, and rcp to copy files.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    BUGS

    smbsh works by intercepting the standard + libc calls with the dynamically loaded versions in + smbwrapper.o. Not all calls have been "wrapped", so + some programs may not function correctly under smbsh + .

    Programs which are not dynamically linked cannot make + use of smbsh's functionality. Most versions + of UNIX have a file command that will + describe how a program was linked.

    SEE ALSO

    smbd(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index fb2c8b25e0..fffd779dcf 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -1,226 +1,35 @@ - -smbspool

    smbspool

    Name

    smbspool -- send a print file to an SMB printer

    Synopsis

    smbspool {job} {user} {title} {copies} {options} [filename]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbspool is a very small print spooling program that +smbspool

    Name

    smbspool — send a print file to an SMB printer

    Synopsis

    smbspool {job} {user} {title} {copies} {options} [filename]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbspool is a very small print spooling program that sends a print file to an SMB printer. The command-line arguments are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system - or from a program or script.

    DEVICE URI

    smbspool specifies the destination using a Uniform Resource - Identifier ("URI") with a method of "smb". This string can take - a number of forms:

    • smb://server/printer

    • smb://workgroup/server/printer

    • smb://username:password@server/printer

    • smb://username:password@workgroup/server/printer

    smbspool tries to get the URI from argv[0]. If argv[0] - contains the name of the program then it looks in the DEVICE_URI environment variable.

    Programs using the exec(2) functions can + or from a program or script.

    DEVICE URI

    smbspool specifies the destination using a Uniform Resource + Identifier ("URI") with a method of "smb". This string can take + a number of forms:

    • smb://server/printer

    • smb://workgroup/server/printer

    • smb://username:password@server/printer

    • smb://username:password@workgroup/server/printer

    smbspool tries to get the URI from argv[0]. If argv[0] + contains the name of the program then it looks in the + DEVICE_URI environment variable.

    Programs using the exec(2) functions can pass the URI in argv[0], while shell scripts must set the - DEVICE_URI environment variable prior to - running smbspool.

    OPTIONS

    • The job argument (argv[1]) contains the + DEVICE_URI environment variable prior to + running smbspool.

    OPTIONS

    • The job argument (argv[1]) contains the job ID number and is presently not used by smbspool. -

    • The user argument (argv[2]) contains the +

    • The user argument (argv[2]) contains the print user's name and is presently not used by smbspool. -

    • The title argument (argv[3]) contains the +

    • The title argument (argv[3]) contains the job title string and is passed as the remote file name - when sending the print job.

    • The copies argument (argv[4]) contains + when sending the print job.

    • The copies argument (argv[4]) contains the number of copies to be printed of the named file. If no filename is provided then this argument is not used by - smbspool.

    • The options argument (argv[5]) contains + smbspool.

    • The options argument (argv[5]) contains the print options in a single string and is currently - not used by smbspool.

    • The filename argument (argv[6]) contains the + not used by smbspool.

    • The filename argument (argv[6]) contains the name of the file to print. If this argument is not specified - then the print file is read from the standard input.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbd(8) and Samba(7).

    AUTHOR

    smbspool was written by Michael Sweet - at Easy Software Products.

    The original Samba software and related utilities + then the print file is read from the standard input.

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    smbd(8) and Samba(7).

    AUTHOR

    smbspool was written by Michael Sweet + at Easy Software Products.

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbstatus.1.html b/docs/htmldocs/smbstatus.1.html index 23b82759ea..a8ae9132ec 100644 --- a/docs/htmldocs/smbstatus.1.html +++ b/docs/htmldocs/smbstatus.1.html @@ -1,286 +1,44 @@ - -smbstatus

    smbstatus

    Name

    smbstatus -- report on current Samba connections

    Synopsis

    smbstatus [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbstatus is a very simple program to - list the current Samba connections.

    OPTIONS

    -P|--profile

    If samba has been compiled with the +smbstatus

    Name

    smbstatus — report on current Samba connections

    Synopsis

    smbstatus [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbstatus is a very simple program to + list the current Samba connections.

    OPTIONS

    -P|--profile

    If samba has been compiled with the profiling option, print only the contents of the profiling - shared memory area.

    -b|--brief

    gives brief output.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + shared memory area.

    -b|--brief

    gives brief output.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -v|--verbose

    gives verbose output.

    -L|--locks

    causes smbstatus to only list locks.

    -B|--byterange

    causes smbstatus to include byte range locks. -

    -p|--processes

    print a list of smbd(8) processes and exit. - Useful for scripting.

    -S|--shares

    causes smbstatus to only list shares.

    -h|--help

    Print a summary of command line options.

    -u|--user=<username>

    selects information relevant to - username only.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    smbd(8) and smb.conf(5).

    AUTHOR

    The original Samba software and related utilities +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -v|--verbose

    gives verbose output.

    -L|--locks

    causes smbstatus to only list locks.

    -B|--byterange

    causes smbstatus to include byte range locks. +

    -p|--processes

    print a list of smbd(8) processes and exit. + Useful for scripting.

    -S|--shares

    causes smbstatus to only list shares.

    -h|--help

    Print a summary of command line options. +

    -u|--user=<username>

    selects information relevant to + username only.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    smbd(8) and smb.conf(5).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbtar.1.html b/docs/htmldocs/smbtar.1.html index 87026c35b5..35802edb90 100644 --- a/docs/htmldocs/smbtar.1.html +++ b/docs/htmldocs/smbtar.1.html @@ -1,351 +1,39 @@ - -smbtar

    smbtar

    Name

    smbtar -- shell script for backing up SMB/CIFS shares - directly to UNIX tape drives

    Synopsis

    smbtar [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbtar is a very small shell script on top - of smbclient(1) which dumps SMB shares directly to tape.

    OPTIONS

    -s server

    The SMB/CIFS server that the share resides - upon.

    -x service

    The share name on the server to connect to. - The default is "backup".

    -X

    Exclude mode. Exclude filenames... from tar - create or restore.

    -d directory

    Change to initial directory - before restoring / backing up files.

    -v

    Verbose mode.

    -p password

    The password to use to access a share. - Default: none

    -u user

    The user id to connect as. Default: - UNIX login name.

    -a

    Reset DOS archive bit mode to - indicate file has been archived.

    -t tape

    Tape device. May be regular file or tape - device. Default: $TAPE environmental - variable; if not set, a file called tar.out - .

    -b blocksize

    Blocking factor. Defaults to 20. See - tar(1) for a fuller explanation.

    -N filename

    Backup only files newer than filename. Could +smbtar

    Name

    smbtar — shell script for backing up SMB/CIFS shares + directly to UNIX tape drives

    Synopsis

    smbtar [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbtar is a very small shell script on top + of smbclient(1) which dumps SMB shares directly to tape.

    OPTIONS

    -s server

    The SMB/CIFS server that the share resides + upon.

    -x service

    The share name on the server to connect to. + The default is "backup".

    -X

    Exclude mode. Exclude filenames... from tar + create or restore.

    -d directory

    Change to initial directory + before restoring / backing up files.

    -v

    Verbose mode.

    -p password

    The password to use to access a share. + Default: none

    -u user

    The user id to connect as. Default: + UNIX login name.

    -a

    Reset DOS archive bit mode to + indicate file has been archived.

    -t tape

    Tape device. May be regular file or tape + device. Default: $TAPE environmental + variable; if not set, a file called tar.out + .

    -b blocksize

    Blocking factor. Defaults to 20. See + tar(1) for a fuller explanation.

    -N filename

    Backup only files newer than filename. Could be used (for example) on a log file to implement incremental - backups.

    -i

    Incremental mode; tar files are only backed + backups.

    -i

    Incremental mode; tar files are only backed up if they have the archive bit set. The archive bit is reset - after each file is read.

    -r

    Restore. Files are restored to the share - from the tar file.

    -l log level

    Log (debug) level. Corresponds to the - -d flag of smbclient(1).

    ENVIRONMENT VARIABLES

    The $TAPE variable specifies the + after each file is read.

    -r

    Restore. Files are restored to the share + from the tar file.

    -l log level

    Log (debug) level. Corresponds to the + -d flag of smbclient(1).

    ENVIRONMENT VARIABLES

    The $TAPE variable specifies the default tape device to write to. May be overridden - with the -t option.

    BUGS

    The smbtar script has different - options from ordinary tar and from smbclient's tar command.

    CAVEATS

    Sites that are more careful about security may not like + with the -t option.

    BUGS

    The smbtar script has different + options from ordinary tar and from smbclient's tar command.

    CAVEATS

    Sites that are more careful about security may not like the way the script handles PC passwords. Backup and restore work on entire shares; should work on file lists. smbtar works best - with GNU tar and may not work well with other versions.

    DIAGNOSTICS

    See the DIAGNOSTICS section for the smbclient(1) command.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    smbd(8), smbclient(1), smb.conf(5).

    AUTHOR

    The original Samba software and related utilities + with GNU tar and may not work well with other versions.

    DIAGNOSTICS

    See the DIAGNOSTICS section for the smbclient(1) command.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    smbd(8), smbclient(1), smb.conf(5).

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    Ricky Poulten - wrote the tar extension and this man page. The smbtar - script was heavily rewritten and improved by Martin Kraemer. Many + to the way the Linux kernel is developed.

    Ricky Poulten + wrote the tar extension and this man page. The smbtar + script was heavily rewritten and improved by Martin Kraemer. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/smbtree.1.html b/docs/htmldocs/smbtree.1.html index e3edbc8681..0d9a845d70 100644 --- a/docs/htmldocs/smbtree.1.html +++ b/docs/htmldocs/smbtree.1.html @@ -1,304 +1,74 @@ - -smbtree

    smbtree

    Name

    smbtree -- A text based smb network browser -

    Synopsis

    smbtree [-b] [-D] [-S]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbtree is a smb browser program - in text mode. It is similar to the "Network Neighborhood" found +smbtree

    Name

    smbtree — A text based smb network browser +

    Synopsis

    smbtree [-b] [-D] [-S]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    smbtree is a smb browser program + in text mode. It is similar to the "Network Neighborhood" found on Windows computers. It prints a tree with all the known domains, the servers in those domains and the shares on the servers. -

    OPTIONS

    -b

    Query network nodes by sending requests +

    OPTIONS

    -b

    Query network nodes by sending requests as broadcasts instead of querying the (domain) master browser. -

    -D

    Only print a list of all +

    -D

    Only print a list of all the domains known on broadcast or by the - master browser

    -S

    Only print a list of + master browser

    -S

    Only print a list of all the domains and servers responding on broadcast or known by the master browser. -

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -N

    If specified, this parameter suppresses the normal +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -N

    If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when -accessing a service that does not require a password.

    Unless a password is specified on the command line or +accessing a service that does not require a password.

    Unless a password is specified on the command line or this parameter is specified, the client will request a -password.

    -k

    Try to authenticate with kerberos. Only useful in -an Active Directory environment.

    -A|--authfile=filename

    This option allows +password.

    -k

    +Try to authenticate with kerberos. Only useful in +an Active Directory environment. +

    -A|--authfile=filename

    This option allows you to specify a file from which to read the username and -password used in the connection. The format of the file is

    username = <value>
-password = <value>
-domain   = <value>

    Make certain that the permissions on the file restrict -access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The -client will first check the USER environment variable, then the -LOGNAME variable and if either exists, the +password used in the connection. The format of the file is +

    +username = <value>
+password = <value>
+domain   = <value>
+

    Make certain that the permissions on the file restrict +access from unwanted users.

    -U|--user=username[%password]

    Sets the SMB username or username and password.

    If %password is not specified, the user will be prompted. The +client will first check the USER environment variable, then the +LOGNAME variable and if either exists, the string is uppercased. If these environmental variables are not -found, the username GUEST is used.

    A third option is to use a credentials file which +found, the username GUEST is used.

    A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the --A for more details.

    Be cautious about including passwords in scripts. Also, on +-A for more details.

    Be cautious about including passwords in scripts. Also, on many systems the command line of a running process may be seen -via the ps command. To be safe always allow -rpcclient to prompt for a password and type -it in directly.

    -h|--help

    Print a summary of command line options.

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +via the ps command. To be safe always allow +rpcclient to prompt for a password and type +it in directly.

    -h|--help

    Print a summary of command line options. +

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The smbtree man page was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The smbtree man page was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 15ec19d7fc..e297d448e3 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -1,140 +1,16 @@ - -smbumount

    smbumount

    Name

    smbumount -- smbfs umount for normal users

    Synopsis

    smbumount {mount-point}

    DESCRIPTION

    With this program, normal users can unmount smb-filesystems, - provided that it is suid root. smbumount has +smbumount

    Name

    smbumount — smbfs umount for normal users

    Synopsis

    smbumount {mount-point}

    DESCRIPTION

    With this program, normal users can unmount smb-filesystems, + provided that it is suid root. smbumount has been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount program works perfectly well, but it would certainly be problematic - to make umount setuid root.

    OPTIONS

    mount-point

    The directory to unmount.

    SEE ALSO

    smbmount(8)

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield - and others.

    The current maintainer of smbfs and the userspace - tools smbmount, smbumount, - and smbmnt is Urban Widmark. - The SAMBA Mailing list + to make umount setuid root.

    OPTIONS

    mount-point

    The directory to unmount.

    SEE ALSO

    smbmount(8)

    AUTHOR

    Volker Lendecke, Andrew Tridgell, Michael H. Warfield + and others.

    The current maintainer of smbfs and the userspace + tools smbmount, smbumount, + and smbmnt is Urban Widmark. + The SAMBA Mailing list is the preferred place to ask questions regarding these programs. -

    The conversion of this manpage for Samba 2.2 was performed +

    The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 - was done by Alexander Bokovoy.

    \ No newline at end of file + was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/speed.html b/docs/htmldocs/speed.html index c1cccd1fe8..d2e1f2c15b 100644 --- a/docs/htmldocs/speed.html +++ b/docs/htmldocs/speed.html @@ -1,499 +1,108 @@ - -Samba performance issues
    SAMBA Project Documentation
    PrevNext

    Chapter 32. Samba performance issues

    Table of Contents
    32.1. Comparisons
    32.2. Socket options
    32.3. Read size
    32.4. Max xmit
    32.5. Log level
    32.6. Read raw
    32.7. Write raw
    32.8. Slow Clients
    32.9. Slow Logins
    32.10. Client tuning

    32.1. Comparisons

    The Samba server uses TCP to talk to the client. Thus if you are + +Chapter35.Samba performance issues

    Chapter35.Samba performance issues
    PrevPartV.Appendixes

    Chapter35.Samba performance issues

    Paul Cochrane

    Dundee Limb Fitting Centre

    <paulc@dth.scot.nhs.uk>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    Table of Contents

    Comparisons
    Socket options
    Read size
    Max xmit
    Log level
    Read raw
    Write raw
    Slow Logins
    Client tuning

    Comparisons

    +The Samba server uses TCP to talk to the client. Thus if you are trying to see if it performs well you should really compare it to programs that use the same protocol. The most readily available programs for file transfer that use TCP are ftp or another TCP based -SMB server.

    If you want to test against something like a NT or WfWg server then +SMB server. +

    +If you want to test against something like a NT or WfWg server then you will have to disable all but TCP on either the client or server. Otherwise you may well be using a totally different protocol -(such as Netbeui) and comparisons may not be valid.

    Generally you should find that Samba performs similarly to ftp at raw +(such as Netbeui) and comparisons may not be valid. +

    +Generally you should find that Samba performs similarly to ftp at raw transfer speed. It should perform quite a bit faster than NFS, -although this very much depends on your system.

    Several people have done comparisons between Samba and Novell, NFS or +although this very much depends on your system. +

    +Several people have done comparisons between Samba and Novell, NFS or WinNT. In some cases Samba performed the best, in others the worst. I suspect the biggest factor is not Samba vs some other system but the hardware and drivers used on the various systems. Given similar hardware Samba should certainly be competitive in speed with other -systems.

    32.2. Socket options

    There are a number of socket options that can greatly affect the -performance of a TCP based server like Samba.

    The socket options that Samba uses are settable both on the command -line with the -O option, or in the smb.conf file.

    The "socket options" section of the smb.conf manual page describes how -to set these and gives recommendations.

    Getting the socket options right can make a big difference to your +systems. +

    Socket options

    +There are a number of socket options that can greatly affect the +performance of a TCP based server like Samba. +

    +The socket options that Samba uses are settable both on the command +line with the -O option, or in the smb.conf file. +

    +The socket options section of the smb.conf manual page describes how +to set these and gives recommendations. +

    +Getting the socket options right can make a big difference to your performance, but getting them wrong can degrade it by just as -much. The correct settings are very dependent on your local network.

    The socket option TCP_NODELAY is the one that seems to make the +much. The correct settings are very dependent on your local network. +

    +The socket option TCP_NODELAY is the one that seems to make the biggest single difference for most networks. Many people report that -adding "socket options = TCP_NODELAY" doubles the read performance of -a Samba drive. The best explanation I have seen for this is that the -Microsoft TCP/IP stack is slow in sending tcp ACKs.

    32.3. Read size

    The option "read size" affects the overlap of disk reads/writes with -network reads/writes. If the amount of data being transferred in -several of the SMB commands (currently SMBwrite, SMBwriteX and +adding socket options = TCP_NODELAY doubles the read +performance of a Samba drive. The best explanation I have seen for this is +that the Microsoft TCP/IP stack is slow in sending tcp ACKs. +

    Read size

    +The option read size affects the overlap of disk +reads/writes with network reads/writes. If the amount of data being +transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing the data before it has received the whole packet from the network, or in the case of SMBreadbraw, it begins writing to the network before -all the data has been read from disk.

    This overlapping works best when the speeds of disk and network access +all the data has been read from disk. +

    +This overlapping works best when the speeds of disk and network access are similar, having very little effect when the speed of one is much -greater than the other.

    The default value is 16384, but very little experimentation has been +greater than the other. +

    +The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway. A value over 65536 is -pointless and will cause you to allocate memory unnecessarily.

    32.4. Max xmit

    At startup the client and server negotiate a "maximum transmit" size, +pointless and will cause you to allocate memory unnecessarily. +

    Max xmit

    +At startup the client and server negotiate a maximum transmit size, which limits the size of nearly all SMB commands. You can set the -maximum size that Samba will negotiate using the "max xmit = " option -in smb.conf. Note that this is the maximum size of SMB request that +maximum size that Samba will negotiate using the max xmit = option +in smb.conf. Note that this is the maximum size of SMB requests that Samba will accept, but not the maximum size that the *client* will accept. The client maximum receive size is sent to Samba by the client and Samba -honours this limit.

    It defaults to 65536 bytes (the maximum), but it is possible that some +honours this limit. +

    +It defaults to 65536 bytes (the maximum), but it is possible that some clients may perform better with a smaller transmit unit. Trying values -of less than 2048 is likely to cause severe problems.

    In most cases the default is the best option.

    32.5. Log level

    If you set the log level (also known as "debug level") higher than 2 +of less than 2048 is likely to cause severe problems. +

    +In most cases the default is the best option. +

    Log level

    +If you set the log level (also known as debug level) higher than 2 then you may suffer a large drop in performance. This is because the server flushes the log file after each operation, which can be very -expensive.

    32.6. Read raw

    The "read raw" operation is designed to be an optimised, low-latency +expensive. +

    Read raw

    +The read raw operation is designed to be an optimised, low-latency file read operation. A server may choose to not support it, -however. and Samba makes support for "read raw" optional, with it -being enabled by default.

    In some cases clients don't handle "read raw" very well and actually +however. and Samba makes support for read raw optional, with it +being enabled by default. +

    +In some cases clients don't handle read raw very well and actually get lower performance using it than they get using the conventional -read operations.

    So you might like to try "read raw = no" and see what happens on your +read operations. +

    +So you might like to try read raw = no and see what happens on your network. It might lower, raise or not affect your performance. Only -testing can really tell.

    32.7. Write raw

    The "write raw" operation is designed to be an optimised, low-latency +testing can really tell. +

    Write raw

    +The write raw operation is designed to be an optimised, low-latency file write operation. A server may choose to not support it, -however. and Samba makes support for "write raw" optional, with it -being enabled by default.

    Some machines may find "write raw" slower than normal write, in which -case you may wish to change this option.

    32.8. Slow Clients

    One person has reported that setting the protocol to COREPLUS rather -than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).

    I suspect that his PC's (386sx16 based) were asking for more data than -they could chew. I suspect a similar speed could be had by setting -"read raw = no" and "max xmit = 2048", instead of changing the -protocol. Lowering the "read size" might also help.

    32.9. Slow Logins

    Slow logins are almost always due to the password checking time. Using -the lowest practical "password level" will improve things a lot. You -could also enable the "UFC crypt" option in the Makefile.

    32.10. Client tuning

    Often a speed problem can be traced to the client. The client (for +however. and Samba makes support for write raw optional, with it +being enabled by default. +

    +Some machines may find write raw slower than normal write, in which +case you may wish to change this option. +

    Slow Logins

    +Slow logins are almost always due to the password checking time. Using +the lowest practical password level will improve things. +

    Client tuning

    +Often a speed problem can be traced to the client. The client (for example Windows for Workgroups) can often be tuned for better TCP -performance.

    See your client docs for details. In particular, I have heard rumours -that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a -large impact on performance.

    Also note that some people have found that setting DefaultRcvWindow in -the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a -big improvement. I don't know why.

    My own experience wth DefaultRcvWindow is that I get much better -performance with a large value (16384 or larger). Other people have -reported that anything over 3072 slows things down enourmously. One -person even reported a speed drop of a factor of 30 when he went from -3072 to 8192. I don't know why.

    It probably depends a lot on your hardware, and the type of unix box -you have at the other end of the link.

    Paul Cochrane has done some testing on client side tuning and come -to the following conclusions:

    Install the W2setup.exe file from www.microsoft.com. This is an -update for the winsock stack and utilities which improve performance.

    Configure the win95 TCPIP registry settings to give better -perfomance. I use a program called MTUSPEED.exe which I got off the -net. There are various other utilities of this type freely available. -The setting which give the best performance for me are:

    1. MaxMTU Remove

    2. RWIN Remove

    3. MTUAutoDiscover Disable

    4. MTUBlackHoleDetect Disable

    5. Time To Live Enabled

    6. Time To Live - HOPS 32

    7. NDI Cache Size 0

    I tried virtually all of the items mentioned in the document and -the only one which made a difference to me was the socket options. It -turned out I was better off without any!!!!!

    In terms of overall speed of transfer, between various win95 clients -and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE -drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.

    The figures are:          Put              Get 
-P166 client 3Com card:    420-440kB/s      500-520kB/s
-P100 client 3Com card:    390-410kB/s      490-510kB/s
-DX4-75 client NE2000:     370-380kB/s      330-350kB/s

    I based these test on transfer two files a 4.5MB text file and a 15MB -textfile. The results arn't bad considering the hardware Samba is -running on. It's a crap machine!!!!

    The updates mentioned in 1 and 2 brought up the transfer rates from -just over 100kB/s in some clients.

    A new client is a P333 connected via a 100MB/s card and hub. The -transfer rates from this were good: 450-500kB/s on put and 600+kB/s -on get.

    Looking at standard FTP throughput, Samba is a bit slower (100kB/s -upwards). I suppose there is more going on in the samba protocol, but -if it could get up to the rate of FTP the perfomance would be quite -staggering.

    PrevHomeNext
    SWAT - The Samba Web Admininistration ToolUpThe samba checklist
    \ No newline at end of file +performance. Check the sections on the various clients in +Samba and Other Clients. +

    PrevUp
    Chapter34.SWAT - The Samba Web Admininistration ToolHome
    diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index 2abd049b71..c5a5ab271b 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -1,518 +1,87 @@ - -swat

    swat

    Name

    swat -- Samba Web Administration Tool

    Synopsis

    swat [-s <smb config file>] [-a]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    swat allows a Samba administrator to - configure the complex smb.conf(5) file via a Web browser. In addition, - a swat configuration page has help links - to all the configurable options in the smb.conf file allowing an - administrator to easily look up the effects of any change.

    swat is run from inetd

    OPTIONS

    -s smb configuration file

    The default configuration file path is +swat

    Name

    swat — Samba Web Administration Tool

    Synopsis

    swat [-s <smb config file>] [-a]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    swat allows a Samba administrator to + configure the complex smb.conf(5) file via a Web browser. In addition, + a swat configuration page has help links + to all the configurable options in the smb.conf file allowing an + administrator to easily look up the effects of any change.

    swat is run from inetd

    OPTIONS

    -s smb configuration file

    The default configuration file path is determined at compile time. The file specified contains - the configuration details required by the smbd(8) server. This is the file - that swat will modify. + the configuration details required by the smbd(8) server. This is the file + that swat will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. - See smb.conf for more information. -

    -a

    This option disables authentication and puts - swat in demo mode. In that mode anyone will be able to modify - the smb.conf file.

    WARNING: Do NOT enable this option on a production - server.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the + See smb.conf for more information. +

    -a

    This option disables authentication and puts + swat in demo mode. In that mode anyone will be able to modify + the smb.conf file.

    WARNING: Do NOT enable this option on a production + server.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -h|--help

    Print a summary of command line options.

    INSTALLATION

    Swat is included as binary package with most distributions. The +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -h|--help

    Print a summary of command line options. +

    INSTALLATION

    Swat is included as binary package with most distributions. The package manager in this case takes care of the installation and configuration. This section is only for those who have compiled swat from scratch. -

    After you compile SWAT you need to run make install - to install the swat binary +

    After you compile SWAT you need to run make install + to install the swat binary and the various help files and images. A default install would put - these in:

    • /usr/local/samba/bin/swat

    • /usr/local/samba/swat/images/*

    • /usr/local/samba/swat/help/*

    Inetd Installation

    You need to edit your /etc/inetd.conf - and /etc/services - to enable SWAT to be launched via inetd.

    In /etc/services you need to - add a line like this:

    swat 901/tcp

    Note for NIS/YP and LDAP users - you may need to rebuild the - NIS service maps rather than alter your local /etc/services file.

    the choice of port number isn't really important + these in:

    • /usr/local/samba/bin/swat

    • /usr/local/samba/swat/images/*

    • /usr/local/samba/swat/help/*

    Inetd Installation

    You need to edit your /etc/inetd.conf + and /etc/services + to enable SWAT to be launched via inetd.

    In /etc/services you need to + add a line like this:

    swat 901/tcp

    Note for NIS/YP and LDAP users - you may need to rebuild the + NIS service maps rather than alter your local + /etc/services file.

    the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your - inetd daemon).

    In /etc/inetd.conf you should - add a line like this:

    swat stream tcp nowait.400 root - /usr/local/samba/bin/swat swat

    One you have edited /etc/services - and /etc/inetd.conf you need to send a - HUP signal to inetd. To do this use kill -1 PID - where PID is the process ID of the inetd daemon.

    LAUNCHING

    To launch SWAT just run your favorite web browser and - point it at "http://localhost:901/".

    Note that you can attach to SWAT from any IP connected + inetd daemon).

    In /etc/inetd.conf you should + add a line like this:

    swat stream tcp nowait.400 root + /usr/local/samba/bin/swat swat

    One you have edited /etc/services + and /etc/inetd.conf you need to send a + HUP signal to inetd. To do this use kill -1 PID + where PID is the process ID of the inetd daemon.

    LAUNCHING

    To launch SWAT just run your favorite web browser and + point it at "http://localhost:901/".

    Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent - in the clear over the wire.

    FILES

    /etc/inetd.conf

    This file must contain suitable startup - information for the meta-daemon.

    /etc/services

    This file must contain a mapping of service name + in the clear over the wire.

    FILES

    /etc/inetd.conf

    This file must contain suitable startup + information for the meta-daemon.

    /etc/services

    This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type - (e.g., tcp).

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file that swat edits. Other - common places that systems install this file are /usr/samba/lib/smb.conf and /etc/smb.conf - . This file describes all the services the server - is to make available to clients.

    WARNINGS

    swat will rewrite your smb.conf(5) file. It will rearrange the entries and delete all - comments, include= and copy= - options. If you have a carefully crafted smb.conf then back it up or don't use swat!

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    inetd(5), smbd(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities + (e.g., tcp).

    /usr/local/samba/lib/smb.conf

    This is the default location of the smb.conf(5) server configuration file that swat edits. Other + common places that systems install this file are + /usr/samba/lib/smb.conf and /etc/smb.conf + . This file describes all the services the server + is to make available to clients.

    WARNINGS

    swat will rewrite your smb.conf(5) file. It will rearrange the entries and delete all + comments, include= and copy= + options. If you have a carefully crafted + smb.conf then back it up or don't use swat!

    VERSION

    This man page is correct for version 3.0 of the Samba suite.

    SEE ALSO

    inetd(5), smbd(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 261f522341..55779a2ad8 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -1,340 +1,51 @@ - -testparm

    testparm

    Name

    testparm -- check an smb.conf configuration file for - internal correctness

    Synopsis

    testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    testparm is a very simple test program - to check an smbd(8) configuration file for +testparm

    Name

    testparm — check an smb.conf configuration file for + internal correctness

    Synopsis

    testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    testparm is a very simple test program + to check an smbd(8) configuration file for internal correctness. If this program reports no problems, you - can use the configuration file with confidence that smbd - will successfully load the configuration file.

    Note that this is NOT a guarantee that + can use the configuration file with confidence that smbd + will successfully load the configuration file.

    Note that this is NOT a guarantee that the services specified in the configuration file will be - available or will operate as expected.

    If the optional host name and host IP address are + available or will operate as expected.

    If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host - has access to each service.

    If testparm finds an error in the smb.conf file it returns an exit code of 1 to the calling + has access to each service.

    If testparm finds an error in the + smb.conf file it returns an exit code of 1 to the calling program, else it returns an exit code of 0. This allows shell scripts - to test the output from testparm.

    OPTIONS

    -s

    Without this option, testparm + to test the output from testparm.

    OPTIONS

    -s

    Without this option, testparm will prompt for a carriage return after printing the service - names and before dumping the service definitions.

    -h|--help

    Print a summary of command line options.

    -V

    Prints the version number for -smbd.

    -L servername

    Sets the value of the %L macro to servername. + names and before dumping the service definitions.

    -h|--help

    Print a summary of command line options. +

    -V

    Prints the version number for +smbd.

    -L servername

    Sets the value of the %L macro to servername. This is useful for testing include files specified with the - %L macro.

    -v

    If this option is specified, testparm - will also output all options that were not used in smb.conf(5) and are thus set to their defaults.

    -t encoding

    Output data in specified encoding. -

    configfilename

    This is the name of the configuration file + %L macro.

    -v

    If this option is specified, testparm + will also output all options that were not used in smb.conf(5) and are thus set to their defaults.

    -t encoding

    + Output data in specified encoding. +

    configfilename

    This is the name of the configuration file to check. If this parameter is not present then the - default smb.conf(5) file will be checked. -

    hostname

    If this parameter and the following are - specified, then testparm will examine the hosts - allow and hosts deny - parameters in the smb.conf(5) file to + default smb.conf(5) file will be checked. +

    hostname

    If this parameter and the following are + specified, then testparm will examine the hosts + allow and hosts deny + parameters in the smb.conf(5) file to determine if the hostname with this IP address would be - allowed access to the smbd server. If + allowed access to the smbd server. If this parameter is supplied, the hostIP parameter must also - be supplied.

    hostIP

    This is the IP address of the host specified + be supplied.

    hostIP

    This is the IP address of the host specified in the previous parameter. This address must be supplied - if the hostname parameter is supplied.

    FILES

    smb.conf(5)

    This is usually the name of the configuration - file used by smbd(8). -

    DIAGNOSTICS

    The program will issue a message saying whether the + if the hostname parameter is supplied.

    FILES

    smb.conf(5)

    This is usually the name of the configuration + file used by smbd(8). +

    DIAGNOSTICS

    The program will issue a message saying whether the configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details - to stdout.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    smb.conf(5), smbd(8)

    AUTHOR

    The original Samba software and related utilities + to stdout.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    smb.conf(5), smbd(8)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/testprns.1.html b/docs/htmldocs/testprns.1.html index 02eea8c57b..16784fcc25 100644 --- a/docs/htmldocs/testprns.1.html +++ b/docs/htmldocs/testprns.1.html @@ -1,252 +1,38 @@ - -testprns

    testprns

    Name

    testprns -- check printer name for validity with smbd

    Synopsis

    testprns {printername} [printcapname]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    testprns is a very simple test program +testprns

    Name

    testprns — check printer name for validity with smbd

    Synopsis

    testprns {printername} [printcapname]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    testprns is a very simple test program to determine whether a given printer name is valid for use in - a service to be provided by smbd(8).

    "Valid" in this context means "can be found in the - printcap specified". This program is very stupid - so stupid in + a service to be provided by smbd(8).

    "Valid" in this context means "can be found in the + printcap specified". This program is very stupid - so stupid in fact that it would be wisest to always specify the printcap file - to use.

    OPTIONS

    printername

    The printer name to validate.

    Printer names are taken from the first field in each + to use.

    OPTIONS

    printername

    The printer name to validate.

    Printer names are taken from the first field in each record in the printcap file, single printer names and sets - of aliases separated by vertical bars ("|") are recognized. + of aliases separated by vertical bars ("|") are recognized. Note that no validation or checking of the printcap syntax is done beyond that required to extract the printer name. It may be that the print spooling system is more forgiving or less - forgiving than testprns. However, if - testprns finds the printer then smbd(8) should do so as well.

    printcapname

    This is the name of the printcap file within - which to search for the given printer name.

    If no printcap name is specified testprns - will attempt to scan the printcap file name - specified at compile time.

    FILES

    /etc/printcap

    This is usually the default printcap - file to scan. See printcap (5). -

    DIAGNOSTICS

    If a printer is found to be valid, the message - "Printer name <printername> is valid" will be - displayed.

    If a printer is found to be invalid, the message - "Printer name <printername> is not valid" will be - displayed.

    All messages that would normally be logged during + forgiving than testprns. However, if + testprns finds the printer then smbd(8) should do so as well.

    printcapname

    This is the name of the printcap file within + which to search for the given printer name.

    If no printcap name is specified testprns + will attempt to scan the printcap file name + specified at compile time.

    FILES

    /etc/printcap

    This is usually the default printcap + file to scan. See printcap (5). +

    DIAGNOSTICS

    If a printer is found to be valid, the message + "Printer name <printername> is valid" will be + displayed.

    If a printer is found to be invalid, the message + "Printer name <printername> is not valid" will be + displayed.

    All messages that would normally be logged during operation of the Samba daemons are logged by this program to the - file test.log in the current directory. The + file test.log in the current directory. The program runs at debuglevel 3, so quite extensive logging information is written. The log should be checked carefully - for errors and warnings.

    Other messages are self-explanatory.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    printcap(5), - smbd(8), smbclient(1)

    AUTHOR

    The original Samba software and related utilities + for errors and warnings.

    Other messages are self-explanatory.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    printcap(5), + smbd(8), smbclient(1)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. + to the way the Linux kernel is developed.

    The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another - excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 + excellent piece of Open Source software, available at + ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 - for Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + for Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/type.html b/docs/htmldocs/type.html index c29cf875b3..3524abc962 100644 --- a/docs/htmldocs/type.html +++ b/docs/htmldocs/type.html @@ -1,151 +1,16 @@ - -Type of installation
    SAMBA Project Documentation
    PrevNext

    II. Type of installation

    Introduction

    Samba can operate in various SMB networks. This part contains information on configuring samba -for various environments.

    PrevHomeNext
    User information database Nomenclature of Server Types
    \ No newline at end of file + +PartII.Server Configuration Basics
    PartII.Server Configuration Basics
    PrevNext

    Server Configuration Basics

    First Steps in Server Configuration

    +Samba can operate in various modes within SMB networks. This HOWTO section contains information on +configuring samba to function as the type of server your network requires. Please read this +section carefully. +

    Table of Contents

    3. Nomenclature of Server Types
    Stand Alone Server
    Domain Member Server
    Domain Controller
    Domain Controller Types
    4. Samba as Stand-Alone Server
    User and Share security level
    User Level Security
    Share Level Security
    Server Level Security
    Domain Level Security
    ADS Level Security
    5. +Samba as an NT4 or Win2k Primary Domain Controller +
    Prerequisite Reading
    +Background +
    Configuring the Samba Domain Controller
    Creating Machine Trust Accounts and Joining Clients to the Domain
    Manual Creation of Machine Trust Accounts
    "On-the-Fly" Creation of Machine Trust Accounts
    Joining the Client to the Domain
    Common Problems and Errors
    I cannot include a '$' in a machine name
    I get told "You already have a connection to the Domain...." +or "Cannot join domain, the credentials supplied conflict with an +existing set.." when creating a machine trust account.
    The system can not log you on (C000019B)....
    The machine trust account for this computer either does not +exist or is not accessible.
    When I attempt to login to a Samba Domain from a NT4/W2K workstation, +I get a message about my account being disabled.
    Domain Control for Windows 9x/ME
    Configuration Instructions: Network Logons
    6. +Samba Backup Domain Controller to Samba Domain Control +
    Prerequisite Reading
    Background
    What qualifies a Domain Controller on the network?
    How does a Workstation find its domain controller?
    When is the PDC needed?
    Can Samba be a Backup Domain Controller to an NT PDC?
    How do I set up a Samba BDC?
    How do I replicate the smbpasswd file?
    Can I do this all with LDAP?
    7. Samba as a ADS domain member
    Setup your smb.conf
    Setup your /etc/krb5.conf
    Create the computer account
    Possible errors
    Test your server setup
    Testing with smbclient
    Notes
    8. Samba as a NT4 or Win2k domain member
    Joining an NT Domain with Samba 3.0
    Why is this better than security = server?
    PrevUpNext
    Chapter2.How to Install and Test SAMBAHomeChapter3.Nomenclature of Server Types
    diff --git a/docs/htmldocs/unicode.html b/docs/htmldocs/unicode.html index d11c9e1c34..0c5bb01d13 100644 --- a/docs/htmldocs/unicode.html +++ b/docs/htmldocs/unicode.html @@ -1,370 +1,60 @@ - -Unicode/Charsets
    SAMBA Project Documentation
    PrevNext

    Chapter 26. Unicode/Charsets

    26.1. What are charsets and unicode?

    Computers communicate in numbers. In texts, each number will be + +Chapter25.Unicode/Charsets

    Chapter25.Unicode/Charsets
    PrevPartIII.Advanced ConfigurationNext

    Chapter25.Unicode/Charsets

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    TAKAHASHI Motonobu

    <monyo@home.monyo.com>

    25 March 2003

    Table of Contents

    What are charsets and unicode?
    Samba and charsets
    Conversion from old names
    Japanese charsets

    What are charsets and unicode?

    +Computers communicate in numbers. In texts, each number will be translated to a corresponding letter. The meaning that will be assigned -to a certain number depends on the character set(charset) that is used. +to a certain number depends on the character set(charset) + that is used. A charset can be seen as a table that is used to translate numbers to letters. Not all computers use the same charset (there are charsets with German umlauts, Japanese characters, etc). Usually a charset contains 256 characters, which means that storing a character with it takes -exactly one byte.

    There are also charsets that support even more characters, +exactly one byte.

    +There are also charsets that support even more characters, but those need twice(or even more) as much storage space. These -charsets can contain 256 * 256 = 65536 characters, which +charsets can contain 256 * 256 = 65536 characters, which is more then all possible characters one could think of. They are called multibyte charsets (because they use more then one byte to -store one character).

    A standardised multibyte charset is unicode, info available at -www.unicode.org. -Big advantage of using a multibyte charset is that you only need one; no +store one character). +

    +A standardised multibyte charset is unicode, info is available at +www.unicode.org. +A big advantage of using a multibyte charset is that you only need one; no need to make sure two computers use the same charset when they are -communicating.

    Old windows clients used to use single-byte charsets, named +communicating. +

    Old windows clients used to use single-byte charsets, named 'codepages' by microsoft. However, there is no support for negotiating the charset to be used in the smb protocol. Thus, you have to make sure you are using the same charset when talking to an old client. -Newer clients (Windows NT, 2K, XP) talk unicode over the wire.

    26.2. Samba and charsets

    As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, -samba knows of three kinds of character sets:

    unix charset

    This is the charset used internally by your operating system. - The default is ASCII, which is fine for most +Newer clients (Windows NT, 2K, XP) talk unicode over the wire. +

    Samba and charsets

    +As of samba 3.0, samba can (and will) talk unicode over the wire. Internally, +samba knows of three kinds of character sets: +

    unix charset

    + This is the charset used internally by your operating system. + The default is ASCII, which is fine for most systems. -

    display charset

    This is the charset samba will use to print messages - on your screen. It should generally be the same as the unix charset. -

    dos charset

    This is the charset samba uses when communicating with +

    display charset

    This is the charset samba will use to print messages + on your screen. It should generally be the same as the unix charset. +

    dos charset

    This is the charset samba uses when communicating with DOS and Windows 9x clients. It will talk unicode to all newer clients. The default depends on the charsets you have installed on your system. - Run testparm -v | grep "dos charset" to see + Run testparm -v | grep "dos charset" to see what the default is on your system. -

    26.3. Conversion from old names

    Because previous samba versions did not do any charset conversion, +

    Conversion from old names

    Because previous samba versions did not do any charset conversion, characters in filenames are usually not correct in the unix charset but only -for the local charset used by the DOS/Windows clients.

    The following script from Steve Langasek converts all -filenames from CP850 to the iso8859-15 charset.

    #find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ - -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;

    26.4. Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:

    You should set mangling method = hash
    There are various iconv() implementations around and not all of -them work equally well. glibc2's iconv() has a critical problem in CP932. -libiconv-1.8 works with CP932 but still has some problems and does not -work with EUC-JP.
    You should set dos charset = CP932, not Shift_JIS, SJIS...
    Currently only unix charset = CP932 will work (but still has some problems...) because of iconv() issues. unix charset = EUC-JP doesn't work well because of iconv() issues.
    Currently Samba 3.0 does not support unix charset = UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    PrevHomeNext
    Securing SambaUpAppendixes
    \ No newline at end of file +for the local charset used by the DOS/Windows clients.

    The following script from Steve Langasek converts all +filenames from CP850 to the iso8859-15 charset.

    +#find /path/to/share -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \ + -t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \; + +

    Japanese charsets

    Samba doesn't work correctly with Japanese charsets yet. Here are +points of attention when setting it up:

    • You should set mangling method = +hash

    • There are various iconv() implementations around and not +all of them work equally well. glibc2's iconv() has a critical problem +in CP932. libiconv-1.8 works with CP932 but still has some problems and +does not work with EUC-JP.

    • You should set dos charset = CP932, not +Shift_JIS, SJIS...

    • Currently only unix charset = CP932 +will work (but still has some problems...) because of iconv() issues. +unix charset = EUC-JP doesn't work well because of +iconv() issues.

    • Currently Samba 3.0 does not support unix charset += UTF8-MAC/CAP/HEX/JIS*

    More information (in Japanese) is available at: http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html.

    PrevUpNext
    Chapter24.Securing SambaHomeChapter26.File and Record Locking
    diff --git a/docs/htmldocs/unix-permissions.html b/docs/htmldocs/unix-permissions.html index 4c4724afea..e9a3b5e671 100644 --- a/docs/htmldocs/unix-permissions.html +++ b/docs/htmldocs/unix-permissions.html @@ -1,889 +1,194 @@ - -UNIX Permission Bits and Windows NT Access Control Lists
    SAMBA Project Documentation
    PrevNext

    Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists

    11.1. Viewing and changing UNIX permissions using the NT - security dialogs

    Windows NT clients can use their native security settings - dialog box to view and modify the underlying UNIX permissions.

    Note that this ability is careful not to compromise + +Chapter11.UNIX Permission Bits and Windows NT Access Control Lists

    Chapter11.UNIX Permission Bits and Windows NT Access Control Lists
    PrevPartIII.Advanced ConfigurationNext

    Chapter11.UNIX Permission Bits and Windows NT Access Control Lists

    Jeremy Allison

    Samba Team

    <jra@samba.org>

    12 Apr 1999

    Table of Contents

    Viewing and changing UNIX permissions using the NT + security dialogs
    How to view file security on a Samba share
    Viewing file ownership
    Viewing file or directory permissions
    File Permissions
    Directory Permissions
    Modifying file or directory permissions
    Interaction with the standard Samba create mask + parameters
    Interaction with the standard Samba file attribute + mapping

    Viewing and changing UNIX permissions using the NT + security dialogs

    Windows NT clients can use their native security settings + dialog box to view and modify the underlying UNIX permissions.

    Note that this ability is careful not to compromise the security of the UNIX host Samba is running on, and still obeys all the file permission rules that a Samba - administrator can set.

    All access to Unix/Linux system file via Samba is controlled at + administrator can set.

    Note

    + All access to Unix/Linux system file via Samba is controlled at the operating system file access control level. When trying to figure out file access problems it is vitally important to identify the identity of the Windows user as it is presented by Samba at the point of file access. This can best be determined from the Samba log files. -

    11.2. How to view file security on a Samba share

    From an NT4/2000/XP client, single-click with the right +

    How to view file security on a Samba share

    From an NT4/2000/XP client, single-click with the right mouse button on any file or directory in a Samba mounted drive letter or UNC path. When the menu pops-up, click - on the Properties entry at the bottom of + on the Properties entry at the bottom of the menu. This brings up the file properties dialog - box. Click on the tab Security and you - will see three buttons, Permissions, - Auditing, and Ownership. - The Auditing button will cause either - an error message A requested privilege is not held - by the client to appear if the user is not the + box. Click on the tab Security and you + will see three buttons, Permissions, + Auditing, and Ownership. + The Auditing button will cause either + an error message A requested privilege is not held + by the client to appear if the user is not the NT Administrator, or a dialog which is intended to allow an Administrator to add auditing requirements to a file if the user is logged on as the NT Administrator. This dialog is non-functional with a Samba share at this time, as the only - useful button, the Add button will not currently - allow a list of users to be seen.

    11.3. Viewing file ownership

    Clicking on the "Ownership" button + useful button, the Add button will not currently + allow a list of users to be seen.

    Viewing file ownership

    Clicking on the "Ownership" button brings up a dialog box telling you who owns the given file. The - owner name will be of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) + owner name will be of the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of + the Samba server, user is the user name of + the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the Close - button to remove this dialog.

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone".

    The Take Ownership button will not allow + GECOS field of the UNIX password database). Click on the Close + button to remove this dialog.

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone".

    The Take Ownership button will not allow you to change the ownership of this file to yourself (clicking on it will display a dialog box complaining that the user you are currently logged onto the NT client cannot be found). The reason for this is that changing the ownership of a file is a privileged - operation in UNIX, available only to the root + operation in UNIX, available only to the root user. As clicking on this button causes NT to attempt to change the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba + client this will not work with Samba at this time.

    There is an NT chown command that will work with Samba and allow a user with Administrator privilege connected to a Samba server as root to change the ownership of files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the Seclib - NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.

    11.4. Viewing file or directory permissions

    The third button is the "Permissions" + or Samba drive. This is available as part of the Seclib + NT security library written by Jeremy Allison of + the Samba Team, available from the main Samba ftp site.

    Viewing file or directory permissions

    The third button is the "Permissions" button. Clicking on this brings up a dialog box that shows both the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of - the Samba server, user is the user name of - the UNIX user who owns the file, and (Long name) + The owner is displayed in the form :

    "SERVER\user (Long name)"

    Where SERVER is the NetBIOS name of + the Samba server, user is the user name of + the UNIX user who owns the file, and (Long name) is the descriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).

    If the parameter nt acl support - is set to false then the file owner will - be shown as the NT user "Everyone" and the - permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files + GECOS field of the UNIX password database).

    If the parameter nt acl support + is set to false then the file owner will + be shown as the NT user "Everyone" and the + permissions will be shown as NT "Full Control".

    The permissions field is displayed differently for files and directories, so I'll describe the way file permissions - are displayed first.

    11.4.1. File Permissions

    The standard UNIX user/group/world triple and - the corresponding "read", "write", "execute" permissions + are displayed first.

    File Permissions

    The standard UNIX user/group/world triple and + the corresponding "read", "write", "execute" permissions triples are mapped by Samba into a three element NT ACL with the 'r', 'w', and 'x' bits mapped into the corresponding NT permissions. The UNIX world permissions are mapped into - the global NT group Everyone, followed + the global NT group Everyone, followed by the list of permissions allowed for UNIX world. The UNIX owner and group permissions are displayed as an NT - user icon and an NT local - group icon respectively followed by the list - of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common - NT names such as "read", "change" or "full control" then - usually the permissions will be prefixed by the words "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed + user icon and an NT local + group icon respectively followed by the list + of permissions allowed for the UNIX user and group.

    As many UNIX permission sets don't map into common + NT names such as "read", + "change" or "full control" then + usually the permissions will be prefixed by the words + "Special Access" in the NT display list.

    But what happens if the file has no permissions allowed for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT "Take Ownership" ACL attribute + to allow "no permissions" to be seen and modified then Samba + overloads the NT "Take Ownership" ACL attribute (which has no meaning in UNIX) and reports a component with - no permissions as having the NT "O" bit set. + no permissions as having the NT "O" bit set. This was chosen of course to make it look like a zero, meaning zero permissions. More details on the decision behind this will - be given below.

    11.4.2. Directory Permissions

    Directories on an NT NTFS file system have two + be given below.

    Directory Permissions

    Directories on an NT NTFS file system have two different sets of permissions. The first set of permissions is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal "RW" + in the first set of parentheses in the normal "RW" NT style. This first set of permissions is created by Samba in exactly the same way as normal file permissions are, described - above, and is displayed in the same way.

    The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the "inherited" permissions that any file created within - this directory would inherit.

    Samba synthesises these inherited permissions for NT by + above, and is displayed in the same way.

    The second set of directory permissions has no real meaning + in the UNIX permissions world and represents the + "inherited" permissions that any file created within + this directory would inherit.

    Samba synthesises these inherited permissions for NT by returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.

    11.5. Modifying file or directory permissions

    Modifying file and directory permissions is as simple + created by Samba on this share would receive.

    Modifying file or directory permissions

    Modifying file and directory permissions is as simple as changing the displayed permissions in the dialog box, and - clicking the OK button. However, there are + clicking the OK button. However, there are limitations that a user needs to be aware of, and also interactions with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.

    If the parameter nt acl support - is set to false then any attempt to set - security permissions will fail with an "Access Denied" - message.

    The first thing to note is that the "Add" + attributes that need to also be taken into account.

    If the parameter nt acl support + is set to false then any attempt to set + security permissions will fail with an "Access Denied" + message.

    The first thing to note is that the "Add" button will not return a list of users in Samba (it will give - an error message of "The remote procedure call failed - and did not execute"). This means that you can only + an error message of "The remote procedure call failed + and did not execute"). This means that you can only manipulate the current user/group/world permissions listed in the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.

    If a permission triple (either user, group, or world) + only permissions that UNIX actually has.

    If a permission triple (either user, group, or world) is removed from the list of permissions in the NT dialog box, - then when the "OK" button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT "O" flag, as described above. This + then when the "OK" button is pressed it will + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT "O" flag, as described above. This allows you to add permissions back to a file or directory once - you have removed them from a triple component.

    As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.

    When setting permissions on a directory the second + you have removed them from a triple component.

    As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on + the Samba server.

    When setting permissions on a directory the second set of permissions (in the second set of parentheses) is by default applied to all files within that directory. If this - is not what you want you must uncheck the "Replace - permissions on existing files" checkbox in the NT - dialog before clicking "OK".

    If you wish to remove all permissions from a + is not what you want you must uncheck the "Replace + permissions on existing files" checkbox in the NT + dialog before clicking "OK".

    If you wish to remove all permissions from a user/group/world component then you may either highlight the - component and click the "Remove" button, - or set the component to only have the special "Take - Ownership" permission (displayed as "O" - ) highlighted.

    11.6. Interaction with the standard Samba create mask - parameters

    There are four parameters + component and click the "Remove" button, + or set the component to only have the special "Take + Ownership" permission (displayed as "O" + ) highlighted.

    Interaction with the standard Samba create mask + parameters

    There are four parameters to control interaction with the standard Samba create mask parameters. - These are :

    security mask

    force security mode

    directory security mask

    force directory security mode

    Once a user clicks "OK" to apply the + These are :

    security mask

    force security mode

    directory security mask

    force directory security mode

    Once a user clicks "OK" to apply the permissions Samba maps the given permissions into a user/group/world r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the - security mask parameter. Any bits that + file against the bits set in the + security mask parameter. Any bits that were changed that are not set to '1' in this parameter are left alone - in the file permissions.

    Essentially, zero bits in the security mask - mask may be treated as a set of bits the user is not + in the file permissions.

    Essentially, zero bits in the security mask + mask may be treated as a set of bits the user is not allowed to change, and one bits are those the user is allowed to change. -

    If not set explicitly this parameter is set to the same value as - the create mask - parameter. To allow a user to modify all the +

    If not set explicitly this parameter is set to the same value as + the create mask + parameter. To allow a user to modify all the user/group/world permissions on a file, set this parameter - to 0777.

    Next Samba checks the changed permissions for a file against - the bits set in the force security mode parameter. Any bits + to 0777.

    Next Samba checks the changed permissions for a file against + the bits set in the + force security mode parameter. Any bits that were changed that correspond to bits set to '1' in this parameter - are forced to be set.

    Essentially, bits set in the force security mode - parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value - as the force - create mode parameter. + are forced to be set.

    Essentially, bits set in the force security mode + parameter may be treated as a set of bits that, when + modifying security on a file, the user has always set to be 'on'.

    If not set explicitly this parameter is set to the same value + as the force + create mode parameter. To allow a user to modify all the user/group/world permissions on a file - with no restrictions set this parameter to 000.

    The security mask and force - security mode parameters are applied to the change - request in that order.

    For a directory Samba will perform the same operations as - described above for a file except using the parameter directory security mask instead of security - mask, and force directory security mode - parameter instead of force security mode - .

    The directory security mask parameter - by default is set to the same value as the directory mask - parameter and the force directory security - mode parameter by default is set to the same value as - the force directory mode parameter.

    In this way Samba enforces the permission restrictions that + with no restrictions set this parameter to 000.

    The security mask and force + security mode parameters are applied to the change + request in that order.

    For a directory Samba will perform the same operations as + described above for a file except using the parameter + directory security mask instead of security + mask, and force directory security mode + parameter instead of force security mode + .

    The directory security mask parameter + by default is set to the same value as the directory mask + parameter and the force directory security + mode parameter by default is set to the same value as + the force directory mode parameter.

    In this way Samba enforces the permission restrictions that an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control + to modify the permission bits within that restriction.

    If you want to set up a share that allows users full control in modifying the permission bits on their files and directories and doesn't force any particular bits to be set 'on', then set the following - parameters in the smb.conf file in that share specific section :

    security mask = 0777

    force security mode = 0

    directory security mask = 0777

    force directory security mode = 0

    11.7. Interaction with the standard Samba file attribute - mapping

    Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can + parameters in the smb.conf file in that share specific section :

    security mask = 0777

    force security mode = 0

    directory security mask = 0777

    force directory security mode = 0

    Interaction with the standard Samba file attribute + mapping

    Samba maps some of the DOS attribute bits (such as "read + only") into the UNIX permissions of a file. This means there can be a conflict between the permission bits set via the security dialog and the permission bits set by the file attribute mapping. -

    One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard +

    One way this can show up is if a file has no UNIX read access + for the owner it will show up as "read only" in the standard file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions + the same one that contains the security info in another tab.

    What this can mean is that if the owner changes the permissions to allow themselves read access using the security dialog, clicks - "OK" to get back to the standard attributes tab - dialog, and then clicks "OK" on that dialog, then + "OK" to get back to the standard attributes tab + dialog, and then clicks "OK" on that dialog, then NT will set the file permissions back to read-only (as that is what the attributes still say in the dialog). This means that after setting - permissions and clicking "OK" to get back to the - attributes dialog you should always hit "Cancel" - rather than "OK" to ensure that your changes - are not overridden.

    PrevHomeNext
    Advanced ConfigurationUpConfiguring Group Mapping
    \ No newline at end of file + permissions and clicking "OK" to get back to the + attributes dialog you should always hit "Cancel" + rather than "OK" to ensure that your changes + are not overridden.

    PrevUpNext
    Chapter10.User information databaseHomeChapter12.Configuring Group Mapping
    diff --git a/docs/htmldocs/vfstest.1.html b/docs/htmldocs/vfstest.1.html index 229f132ca8..8c5565f02b 100644 --- a/docs/htmldocs/vfstest.1.html +++ b/docs/htmldocs/vfstest.1.html @@ -1,537 +1,43 @@ - -vfstest

    vfstest

    Name

    vfstest -- tool for testing samba VFS modules

    Synopsis

    vfstest [-d debuglevel] [-c command] [-l logfile] [-h]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    vfstest is a small command line +vfstest

    Name

    vfstest — tool for testing samba VFS modules

    Synopsis

    vfstest [-d debuglevel] [-c command] [-l logfile] [-h]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    vfstest is a small command line utility that has the ability to test dso samba VFS modules. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules. -

    OPTIONS

    -c|--command=command

    Execute the specified (colon-separated) commands. +

    OPTIONS

    -c|--command=command

    Execute the specified (colon-separated) commands. See below for the commands that are available. -

    -h|--help

    Print a summary of command line options.

    -l|--logfile=logbasename

    File name for log/debug files. The extension - '.client' will be appended. The log file is never removed +

    -h|--help

    Print a summary of command line options. +

    -l|--logfile=logbasename

    File name for log/debug files. The extension + '.client' will be appended. The log file is never removed by the client. -

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    COMMANDS

    VFS COMMANDS

    • load <module.so> - Load specified VFS module

    • populate <char> <size> - Populate a data buffer with the specified data -

    • showdata [<offset> <len>] - Show data currently in data buffer -

    • connect - VFS connect()

    • disconnect - VFS disconnect()

    • disk_free - VFS disk_free()

    • opendir - VFS opendir()

    • readdir - VFS readdir()

    • mkdir - VFS mkdir()

    • rmdir - VFS rmdir()

    • closedir - VFS closedir()

    • open - VFS open()

    • close - VFS close()

    • read - VFS read()

    • write - VFS write()

    • lseek - VFS lseek()

    • rename - VFS rename()

    • fsync - VFS fsync()

    • stat - VFS stat()

    • fstat - VFS fstat()

    • lstat - VFS lstat()

    • unlink - VFS unlink()

    • chmod - VFS chmod()

    • fchmod - VFS fchmod()

    • chown - VFS chown()

    • fchown - VFS fchown()

    • chdir - VFS chdir()

    • getwd - VFS getwd()

    • utime - VFS utime()

    • ftruncate - VFS ftruncate()

    • lock - VFS lock()

    • symlink - VFS symlink()

    • readlink - VFS readlink()

    • link - VFS link()

    • mknod - VFS mknod()

    • realpath - VFS realpath()

    GENERAL COMMANDS

    • conf <smb.conf> - Load a different configuration file

    • help [<command>] - Get list of commands or info about specified command

    • debuglevel <level> - Set debug level

    • freemem - Free memory currently in use

    • exit - Exit vfstest

    VERSION

    This man page is correct for version 3.0 of the Samba - suite.

    AUTHOR

    The original Samba software and related utilities +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    COMMANDS

    VFS COMMANDS

    • load <module.so> - Load specified VFS module

    • populate <char> <size> - Populate a data buffer with the specified data +

    • showdata [<offset> <len>] - Show data currently in data buffer +

    • connect - VFS connect()

    • disconnect - VFS disconnect()

    • disk_free - VFS disk_free()

    • opendir - VFS opendir()

    • readdir - VFS readdir()

    • mkdir - VFS mkdir()

    • rmdir - VFS rmdir()

    • closedir - VFS closedir()

    • open - VFS open()

    • close - VFS close()

    • read - VFS read()

    • write - VFS write()

    • lseek - VFS lseek()

    • rename - VFS rename()

    • fsync - VFS fsync()

    • stat - VFS stat()

    • fstat - VFS fstat()

    • lstat - VFS lstat()

    • unlink - VFS unlink()

    • chmod - VFS chmod()

    • fchmod - VFS fchmod()

    • chown - VFS chown()

    • fchown - VFS fchown()

    • chdir - VFS chdir()

    • getwd - VFS getwd()

    • utime - VFS utime()

    • ftruncate - VFS ftruncate()

    • lock - VFS lock()

    • symlink - VFS symlink()

    • readlink - VFS readlink()

    • link - VFS link()

    • mknod - VFS mknod()

    • realpath - VFS realpath()

    GENERAL COMMANDS

    • conf <smb.conf> - Load a different configuration file

    • help [<command>] - Get list of commands or info about specified command

    • debuglevel <level> - Set debug level

    • freemem - Free memory currently in use

    • exit - Exit vfstest

    VERSION

    This man page is correct for version 3.0 of the Samba + suite.

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    The vfstest man page was written by Jelmer Vernooij.

    \ No newline at end of file + to the way the Linux kernel is developed.

    The vfstest man page was written by Jelmer Vernooij.

    diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 9833239078..fc72b333a8 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -1,444 +1,71 @@ - -wbinfo

    wbinfo

    Name

    wbinfo -- Query information from winbind daemon

    Synopsis

    wbinfo [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The wbinfo program queries and returns information - created and used by the winbindd(8) daemon.

    The winbindd(8) daemon must be configured - and running for the wbinfo program to be able - to return information.

    OPTIONS

    -u

    This option will list all users available - in the Windows NT domain for which the winbindd(8) daemon is operating in. Users in all trusted domains +wbinfo

    Name

    wbinfo — Query information from winbind daemon

    Synopsis

    wbinfo [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]

    DESCRIPTION

    This tool is part of the Samba(7) suite.

    The wbinfo program queries and returns information + created and used by the winbindd(8) daemon.

    The winbindd(8) daemon must be configured + and running for the wbinfo program to be able + to return information.

    OPTIONS

    -u

    This option will list all users available + in the Windows NT domain for which the winbindd(8) daemon is operating in. Users in all trusted domains will also be listed. Note that this operation does not assign - user ids to any users that have not already been seen by winbindd(8) - .

    -g

    This option will list all groups available - in the Windows NT domain for which the Samba(7) daemon is operating in. Groups in all trusted domains + user ids to any users that have not already been seen by winbindd(8) + .

    -g

    This option will list all groups available + in the Windows NT domain for which the Samba(7) daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign group ids to any groups that have not already been - seen by winbindd(8).

    -N name

    The -N option - queries winbindd(8) to query the WINS + seen by winbindd(8).

    -N name

    The -N option + queries winbindd(8) to query the WINS server for the IP address associated with the NetBIOS name - specified by the name parameter. -

    -I ip

    The -I option - queries winbindd(8) to send a node status + specified by the name parameter. +

    -I ip

    The -I option + queries winbindd(8) to send a node status request to get the NetBIOS name associated with the IP address - specified by the ip parameter. -

    -n name

    The -n option - queries winbindd(8) for the SID + specified by the ip parameter. +

    -n name

    The -n option + queries winbindd(8) for the SID associated with the name specified. Domain names can be specified before the user name by using the winbind separator character. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the - domain used is the one specified in the smb.conf(5) workgroup - parameter.

    -s sid

    Use -s to resolve - a SID to a name. This is the inverse of the -n - option above. SIDs must be specified as ASCII strings + domain used is the one specified in the smb.conf(5) workgroup + parameter.

    -s sid

    Use -s to resolve + a SID to a name. This is the inverse of the -n + option above. SIDs must be specified as ASCII strings in the traditional Microsoft format. For example, - S-1-5-21-1455342024-3071081365-2475485837-500.

    -U uid

    Try to convert a UNIX user id to a Windows NT + S-1-5-21-1455342024-3071081365-2475485837-500.

    -U uid

    Try to convert a UNIX user id to a Windows NT SID. If the uid specified does not refer to one within - the winbind uid range then the operation will fail.

    -G gid

    Try to convert a UNIX group id to a Windows + the winbind uid range then the operation will fail.

    -G gid

    Try to convert a UNIX group id to a Windows NT SID. If the gid specified does not refer to one within - the winbind gid range then the operation will fail.

    -S sid

    Convert a SID to a UNIX user id. If the SID - does not correspond to a UNIX user mapped by winbindd(8) then the operation will fail.

    -Y sid

    Convert a SID to a UNIX group id. If the SID - does not correspond to a UNIX group mapped by winbindd(8) then - the operation will fail.

    -t

    Verify that the workstation trust account + the winbind gid range then the operation will fail.

    -S sid

    Convert a SID to a UNIX user id. If the SID + does not correspond to a UNIX user mapped by winbindd(8) then the operation will fail.

    -Y sid

    Convert a SID to a UNIX group id. If the SID + does not correspond to a UNIX group mapped by winbindd(8) then + the operation will fail.

    -t

    Verify that the workstation trust account created when the Samba server is added to the Windows NT - domain is working.

    -m

    Produce a list of domains trusted by the - Windows NT server winbindd(8) contacts + domain is working.

    -m

    Produce a list of domains trusted by the + Windows NT server winbindd(8) contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for. -

    --sequence

    Show sequence numbers of - all known domains

    -r username

    Try to obtain the list of UNIX group ids +

    --sequence

    Show sequence numbers of + all known domains

    -r username

    Try to obtain the list of UNIX group ids to which the user belongs. This only works for users defined on a Domain Controller. -

    -a username%password

    Attempt to authenticate a user via winbindd. +

    -a username%password

    Attempt to authenticate a user via winbindd. This checks both authenticaion methods and reports its results. -

    -A username%password

    Store username and password used by winbindd +

    -A username%password

    Store username and password used by winbindd during session setup to a domain controller. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a.k.a. Permissions compatiable with Windows 2000 servers only). -

    --get-auth-user

    Print username and password used by winbindd +

    --get-auth-user

    Print username and password used by winbindd during session setup to a domain controller. Username and password can be set using '-A'. Only available for - root.

    -p

    Check whether winbindd is still alive. + root.

    -p

    Check whether winbindd is still alive. Prints out either 'succeeded' or 'failed'. -

    -V

    Prints the version number for -smbd.

    -h|--help

    Print a summary of command line options.

    EXIT STATUS

    The wbinfo program returns 0 if the operation - succeeded, or 1 if the operation failed. If the winbindd(8) daemon is not working wbinfo will always return - failure.

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    winbindd(8)

    AUTHOR

    The original Samba software and related utilities +

    -V

    Prints the version number for +smbd.

    -h|--help

    Print a summary of command line options. +

    EXIT STATUS

    The wbinfo program returns 0 if the operation + succeeded, or 1 if the operation failed. If the winbindd(8) daemon is not working wbinfo will always return + failure.

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    winbindd(8)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    wbinfo and winbindd - were written by Tim Potter.

    The conversion to DocBook for Samba 2.2 was done + to the way the Linux kernel is developed.

    wbinfo and winbindd + were written by Tim Potter.

    The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba - 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 63d8e144ba..3672fa0717 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -1,397 +1,75 @@ - -Unified Logons between Windows NT and UNIX using Winbind
    SAMBA Project Documentation
    PrevNext

    Chapter 15. Unified Logons between Windows NT and UNIX using Winbind

    15.1. Abstract

    Integration of UNIX and Microsoft Windows NT through - a unified logon has been considered a "holy grail" in heterogeneous + +Chapter15.Unified Logons between Windows NT and UNIX using Winbind

    Chapter15.Unified Logons between Windows NT and UNIX using Winbind
    PrevPartIII.Advanced ConfigurationNext

    Chapter15.Unified Logons between Windows NT and UNIX using Winbind

    Tim Potter

    Samba Team

    <tpot@linuxcare.com.au>

    Andrew Tridgell

    Samba Team

    <tridge@samba.org>

    John H. Terpstra

    Samba Team

    <jht@samba.org>

    Naag Mummaneni

    <getnag@rediffmail.com>

    Jelmer R. Vernooij

    The Samba Team

    <jelmer@samba.org>

    27 June 2002

    Table of Contents

    Abstract
    Introduction
    What Winbind Provides
    Target Uses
    How Winbind Works
    Microsoft Remote Procedure Calls
    Microsoft Active Directory Services
    Name Service Switch
    Pluggable Authentication Modules
    User and Group ID Allocation
    Result Caching
    Installation and Configuration
    Introduction
    Requirements
    Testing Things Out
    Limitations
    Conclusion

    Abstract

    Integration of UNIX and Microsoft Windows NT through + a unified logon has been considered a "holy grail" in heterogeneous computing environments for a long time. We present - winbind, a component of the Samba suite + winbind, a component of the Samba suite of programs as a solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind system, explaining the functionality it provides, how it is configured, - and how it works internally.

    15.2. Introduction

    It is well known that UNIX and Microsoft Windows NT have + and how it works internally.

    Introduction

    It is well known that UNIX and Microsoft Windows NT have different models for representing user and group information and use different technologies for implementing them. This fact has made it difficult to integrate the two systems in a satisfactory - manner.

    One common solution in use today has been to create + manner.

    One common solution in use today has been to create identically named user accounts on both the UNIX and Windows systems and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore and two sets of passwords are required both of which can lead to synchronization problems between the UNIX and Windows - systems and confusion for users.

    We divide the unified logon problem for UNIX machines into - three smaller problems:

    • Obtaining Windows NT user and group information -

    • Authenticating Windows NT users -

    • Password changing for Windows NT users -

    Ideally, a prospective solution to the unified logon problem + systems and confusion for users.

    We divide the unified logon problem for UNIX machines into + three smaller problems:

    • Obtaining Windows NT user and group information +

    • Authenticating Windows NT users +

    • Password changing for Windows NT users +

    Ideally, a prospective solution to the unified logon problem would satisfy all the above components without duplication of information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple and elegant solution to all three components of the unified logon - problem.

    15.3. What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by + problem.

    What Winbind Provides

    Winbind unifies UNIX and Windows NT account management by allowing a UNIX box to become a full member of a NT domain. Once this is done the UNIX box will see NT users and groups as if they were native UNIX users and groups, allowing the NT domain to be used in much the same manner that NIS+ is used within - UNIX-only environments.

    The end result is that whenever any + UNIX-only environments.

    The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely - transparent.

    Users on the UNIX machine can then use NT user and group - names as they would use "native" UNIX names. They can chown files + transparent.

    Users on the UNIX machine can then use NT user and group + names as they would use "native" UNIX names. They can chown files so that they are owned by NT domain users or even login to the - UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is + UNIX machine and run a UNIX X-Window session as a domain user.

    The only obvious indication that Winbind is being used is that user and group names take the form DOMAIN\user and DOMAIN\group. This is necessary as it allows Winbind to determine that redirection to a domain controller is wanted for a particular - lookup and which trusted domain is being referenced.

    Additionally, Winbind provides an authentication service + lookup and which trusted domain is being referenced.

    Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing passwords between systems since all passwords are stored in a single - location (on the domain controller).

    15.3.1. Target Uses

    Winbind is targeted at organizations that have an + location (on the domain controller).

    Target Uses

    Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to maintain a separate account infrastructure. This greatly simplifies the administrative overhead of deploying UNIX - workstations into a NT based organization.

    Another interesting way in which we expect Winbind to + workstations into a NT based organization.

    Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances that provide file and print services to Microsoft based networks will be able to use Winbind to provide seamless integration of - the appliance into the domain.

    15.4. How Winbind Works

    The winbind system is designed around a client/server - architecture. A long running winbindd daemon + the appliance into the domain.

    How Winbind Works

    The winbind system is designed around a client/server + architecture. A long running winbindd daemon listens on a UNIX domain socket waiting for requests to arrive. These requests are generated by the NSS and PAM - clients and processed sequentially.

    The technologies used to implement winbind are described - in detail below.

    15.4.1. Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway + clients and processed sequentially.

    The technologies used to implement winbind are described + in detail below.

    Microsoft Remote Procedure Calls

    Over the last few years, efforts have been underway by various Samba Team members to decode various aspects of the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network related operations between @@ -399,25 +77,13 @@ NAME="AEN2548" and print spooling. Although initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in Samba, it has also yielded a body of code which - can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users + can be used for other purposes.

    Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user passwords. By directly querying a Windows PDC for user and group information, winbind maps the - NT account information onto UNIX user and group names.

    15.4.2. Microsoft Active Directory Services

    Since late 2001, Samba has gained the ability to + NT account information onto UNIX user and group names.

    Microsoft Active Directory Services

    + Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its 'Native Mode' protocols, rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running @@ -425,18 +91,7 @@ NAME="AEN2552" same way as a Win2k client would, and in so doing provide a much more efficient and effective winbind implementation. -

    15.4.3. Name Service Switch

    The Name Service Switch, or NSS, is a feature that is +

    Name Service Switch

    The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information to be resolved from different sources. For example, a standalone @@ -444,9 +99,7 @@ NAME="AEN2555" flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, and then consult a NIS database for user information or a DNS server - for hostname information.

    The NSS application programming interface allows winbind + for hostname information.

    The NSS application programming interface allows winbind to present itself as a source of system information when resolving UNIX usernames and groups. Winbind uses this interface, and information obtained from a Windows NT server using MSRPC @@ -454,69 +107,26 @@ NAME="AEN2555" UNIX library calls, one can enumerate the users and groups on a UNIX machine running winbind and see all users and groups in a NT domain plus any trusted domain as though they were local - users and groups.

    The primary control file for NSS is - /etc/nsswitch.conf. + users and groups.

    The primary control file for NSS is + /etc/nsswitch.conf. When a UNIX application makes a request to do a lookup - the C library looks in /etc/nsswitch.conf + the C library looks in /etc/nsswitch.conf for a line which matches the service type being requested, for - example the "passwd" service type is used when user or group names + example the "passwd" service type is used when user or group names are looked up. This config line species which implementations of that service should be tried and in what order. If the passwd - config line is:

    passwd: files example

    then the C library will first load a module called - /lib/libnss_files.so followed by - the module /lib/libnss_example.so. The + config line is:

    passwd: files example

    then the C library will first load a module called + /lib/libnss_files.so followed by + the module /lib/libnss_example.so. The C library will dynamically load each of these modules in turn and call resolver functions within the modules to try to resolve the request. Once the request is resolved the C library returns the - result to the application.

    This NSS interface provides a very easy way for Winbind + result to the application.

    This NSS interface provides a very easy way for Winbind to hook into the operating system. All that needs to be done - is to put libnss_winbind.so in /lib/ - then add "winbind" into /etc/nsswitch.conf at + is to put libnss_winbind.so in /lib/ + then add "winbind" into /etc/nsswitch.conf at the appropriate place. The C library will then call Winbind to - resolve user and group names.

    15.4.4. Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, + resolve user and group names.

    Pluggable Authentication Modules

    Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different authentication methods for different system applications without @@ -524,48 +134,24 @@ NAME="AEN2571" for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users stored in the local password file but only allow users resolved from - a NIS database to log in over the network.

    Winbind uses the authentication management and password + a NIS database to log in over the network.

    Winbind uses the authentication management and password management PAM interface to integrate Windows NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have this change take effect directly on the Primary Domain Controller. -

    PAM is configured by providing control files in the directory - /etc/pam.d/ for each of the services that +

    PAM is configured by providing control files in the directory + /etc/pam.d/ for each of the services that require authentication. When an authentication request is made by an application the PAM code in the C library looks up this control file to determine what modules to load to do the authentication check and in what order. This interface makes adding a new authentication service for Winbind very easy, all that needs - to be done is that the pam_winbind.so module - is copied to /lib/security/ and the PAM + to be done is that the pam_winbind.so module + is copied to /lib/security/ and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation - for more details.

    15.4.5. User and Group ID Allocation

    When a user or group is created under Windows NT + for more details.

    User and Group ID Allocation

    When a user or group is created under Windows NT is it allocated a numerical relative identifier (RID). This is slightly different to UNIX which has a range of numbers that are used to identify users, and the same range in which to identify @@ -576,22 +162,9 @@ NAME="AEN2579" resolved for the first time, it is allocated the next UNIX id from the range. The same process applies for Windows NT groups. Over time, winbind will have mapped all Windows NT users and groups - to UNIX user ids and group ids.

    The results of this mapping are stored persistently in + to UNIX user ids and group ids.

    The results of this mapping are stored persistently in an ID mapping database held in a tdb database). This ensures that - RIDs are mapped to UNIX IDs in a consistent way.

    15.4.6. Result Caching

    An active system can generate a lot of user and group + RIDs are mapped to UNIX IDs in a consistent way.

    Result Caching

    An active system can generate a lot of user and group name lookups. To reduce the network cost of these lookups winbind uses a caching scheme based on the SAM sequence number supplied by NT domain controllers. User or group information returned @@ -602,1243 +175,559 @@ NAME="AEN2583" the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information is discarded and up to date information is requested directly - from the PDC.

    15.5. Installation and Configuration

    Many thanks to John Trostel jtrostel@snapserver.com -for providing the HOWTO for this section.

    This HOWTO describes how to get winbind services up and running + from the PDC.

    Installation and Configuration

    +Many thanks to John Trostel jtrostel@snapserver.com +for providing the HOWTO for this section. +

    +This HOWTO describes how to get winbind services up and running to control access and authenticate users on your Linux box using -the winbind services which come with SAMBA 2.2.2.

    15.5.1. Introduction

    This HOWTO describes the procedures used to get winbind up and +the winbind services which come with SAMBA 3.0. +

    Introduction

    +This HOWTO describes the procedures used to get winbind up and running on my RedHat 7.1 system. Winbind is capable of providing access and authentication control for Windows Domain users through an NT or Win2K PDC for 'regular' services, such as telnet a nd ftp, as -well for SAMBA services.

    This HOWTO has been written from a 'RedHat-centric' perspective, so if +well for SAMBA services. +

    +This HOWTO has been written from a 'RedHat-centric' perspective, so if you are using another distribution, you may have to modify the instructions -somewhat to fit the way your distribution works.

    • Why should I to this? -

      This allows the SAMBA administrator to rely on the +somewhat to fit the way your distribution works. +

      • + Why should I to this? +

        This allows the SAMBA administrator to rely on the authentication mechanisms on the NT/Win2K PDC for the authentication of domain members. NT/Win2K users no longer need to have separate accounts on the SAMBA server. -

      • Who should be reading this document? -

        This HOWTO is designed for system administrators. If you are +

      • + Who should be reading this document? +

        + This HOWTO is designed for system administrators. If you are implementing SAMBA on a file server and wish to (fairly easily) integrate existing NT/Win2K users from your PDC onto the SAMBA server, this HOWTO is for you. That said, I am no NT or PAM expert, so you may find a better or easier way to accomplish these tasks. -

      15.5.2. Requirements

      If you have a samba configuration file that you are currently -using... BACK IT UP! If your system already uses PAM, -back up the /etc/pam.d directory -contents! If you haven't already made a boot disk, -MAKE ONE NOW!

      Messing with the pam configuration files can make it nearly impossible +

    Requirements

    +If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, +back up the /etc/pam.d directory +contents! If you haven't already made a boot disk, +MAKE ONE NOW! +

    +Messing with the pam configuration files can make it nearly impossible to log in to yourmachine. That's why you want to be able to boot back into your machine in single user mode and restore your -/etc/pam.d back to the original state they were in if -you get frustrated with the way things are going. ;-)

    The latest version of SAMBA (version 3.0 as of this writing), now +/etc/pam.d back to the original state they were in if +you get frustrated with the way things are going. ;-) +

    +The latest version of SAMBA (version 3.0 as of this writing), now includes a functioning winbindd daemon. Please refer to the -main SAMBA web page or, +main SAMBA web page or, better yet, your closest SAMBA mirror site for instructions on -downloading the source code.

    To allow Domain users the ability to access SAMBA shares and +downloading the source code. +

    +To allow Domain users the ability to access SAMBA shares and files, as well as potentially other services provided by your SAMBA machine, PAM (pluggable authentication modules) must be setup properly on your machine. In order to compile the winbind modules, you should have at least the pam libraries resident on your system. For recent RedHat systems (7.1, for instance), that -means pam-0.74-22. For best results, it is helpful to also -install the development packages in pam-devel-0.74-22.

    15.5.3. Testing Things Out

    Before starting, it is probably best to kill off all the SAMBA -related daemons running on your server. Kill off all smbd, -nmbd, and winbindd processes that may +means pam-0.74-22. For best results, it is helpful to also +install the development packages in pam-devel-0.74-22. +

    Testing Things Out

    +Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all smbd, +nmbd, and winbindd processes that may be running. To use PAM, you will want to make sure that you have the -standard PAM package (for RedHat) which supplies the /etc/pam.d +standard PAM package (for RedHat) which supplies the /etc/pam.d directory structure, including the pam modules are used by pam-aware -services, several pam libraries, and the /usr/doc -and /usr/man entries for pam. Winbind built better +services, several pam libraries, and the /usr/doc +and /usr/man entries for pam. Winbind built better in SAMBA if the pam-devel package was also installed. This package includes the header files needed to compile pam-aware applications. For instance, -my RedHat system has both pam-0.74-22 and -pam-devel-0.74-22 RPMs installed.

    15.5.3.1. Configure and compile SAMBA

    The configuration and compilation of SAMBA is pretty straightforward. +my RedHat system has both pam-0.74-22 and +pam-devel-0.74-22 RPMs installed. +

    Configure and compile SAMBA

    +The configuration and compilation of SAMBA is pretty straightforward. The first three steps may not be necessary depending upon -whether or not you have previously built the Samba binaries.

    root# autoconf
-root# make clean
-root# rm config.cache
-root# ./configure
-root# make
-root# make install

    This will, by default, install SAMBA in /usr/local/samba. +whether or not you have previously built the Samba binaries. +

    +root# autoconf
+root# make clean
+root# rm config.cache
+root# ./configure
+root# make
+root# make install
+

    +This will, by default, install SAMBA in /usr/local/samba. See the main SAMBA documentation if you want to install SAMBA somewhere else. -It will also build the winbindd executable and libraries.

    15.5.3.2. Configure nsswitch.conf and the -winbind libraries

    The libraries needed to run the winbindd daemon -through nsswitch need to be copied to their proper locations, so

    root# cp ../samba/source/nsswitch/libnss_winbind.so /lib

    I also found it necessary to make the following symbolic link:

    root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2

    And, in the case of Sun solaris:

    root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 -root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2

    Now, as root you need to edit /etc/nsswitch.conf to -allow user and group entries to be visible from the winbindd -daemon. My /etc/nsswitch.conf file look like -this after editing:

    	passwd:     files winbind
+It will also build the winbindd executable and libraries. 
+

    Configure nsswitch.conf and the +winbind libraries on Linux and Solaris

    +The libraries needed to run the winbindd daemon +through nsswitch need to be copied to their proper locations, so +

    +root# cp ../samba/source/nsswitch/libnss_winbind.so /lib +

    +I also found it necessary to make the following symbolic link: +

    +root# ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 +

    And, in the case of Sun solaris:

    +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1 +root# ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2 +

    +Now, as root you need to edit /etc/nsswitch.conf to +allow user and group entries to be visible from the winbindd +daemon. My /etc/nsswitch.conf file look like +this after editing: +

    +	passwd:     files winbind
 	shadow:     files 
-	group:      files winbind

    + group: files winbind +

    The libraries needed by the winbind daemon will be automatically -entered into the ldconfig cache the next time +entered into the ldconfig cache the next time your system reboots, but it -is faster (and you don't need to reboot) if you do it manually:

    root# /sbin/ldconfig -v | grep winbind

    This makes libnss_winbind available to winbindd -and echos back a check to you.

    15.5.3.3. Configure smb.conf

    Several parameters are needed in the smb.conf file to control -the behavior of winbindd. Configure -smb.conf These are described in more detail in -the winbindd(8) man page. My -smb.conf file was modified to -include the following entries in the [global] section:

    [global]
-     <...>
+is faster (and you don't need to reboot) if you do it manually:
+
    
+root# /sbin/ldconfig -v | grep winbind
+
    
+This makes libnss_winbind available to winbindd 
+and echos back a check to you.
+

    NSS Winbind on AIX

    (This section is only for those running AIX)

    +The winbind AIX identification module gets built as libnss_winbind.so in the +nsswitch directory of the samba source. This file can be copied to +/usr/lib/security, and the AIX naming convention would indicate that it +should be named WINBIND. A stanza like the following: +

    +WINBIND:
+        program = /usr/lib/security/WINBIND
+        options = authonly
+

    can then be added to +/usr/lib/security/methods.cfg. This module only +supports identification, but there have been success reports using the +standard winbind pam module for authentication. Use caution configuring +loadable authentication modules as it is possible to make it impossible +to logon to the system. More information about the AIX authentication +module API can be found at "Kernel Extensions and Device Support +Programming Concepts for AIX": +Chapter 18. Loadable Authentication Module Programming Interface +and more information on administering the modules at +"System Management Guide: Operating System and Devices". +

    Configure smb.conf

    +Several parameters are needed in the smb.conf file to control +the behavior of winbindd. Configure +smb.conf These are described in more detail in +the winbindd(8) man page. My +smb.conf file was modified to +include the following entries in the [global] section: +

    +[global]
+     <...>
      # separate domain and username with '+', like DOMAIN+username
-     winbind separator = +
+     winbind separator = +
      # use uids from 10000 to 20000 for domain users
-     winbind uid = 10000-20000
+     winbind uid = 10000-20000
      # use gids from 10000 to 20000 for domain groups
-     winbind gid = 10000-20000
+     winbind gid = 10000-20000
      # allow enumeration of winbind users and groups
-     winbind enum users = yes
-     winbind enum groups = yes
+     winbind enum users = yes
+     winbind enum groups = yes
      # give winbind users a real shell (only needed if they have telnet access)
-     template homedir = /home/winnt/%D/%U
-     template shell = /bin/bash

    15.5.3.4. Join the SAMBA server to the PDC domain

    Enter the following command to make the SAMBA server join the -PDC domain, where DOMAIN is the name of -your Windows domain and Administrator is -a domain user who has administrative privileges in the domain.

    root# /usr/local/samba/bin/net join -S PDC -U Administrator

    The proper response to the command should be: "Joined the domain -DOMAIN" where DOMAIN -is your DOMAIN name.

    15.5.3.5. Start up the winbindd daemon and test it!

    Eventually, you will want to modify your smb startup script to + template homedir = /home/winnt/%D/%U + template shell = /bin/bash +

    Join the SAMBA server to the PDC domain

    +Enter the following command to make the SAMBA server join the +PDC domain, where DOMAIN is the name of +your Windows domain and Administrator is +a domain user who has administrative privileges in the domain. +

    +root# /usr/local/samba/bin/net join -S PDC -U Administrator +

    +The proper response to the command should be: "Joined the domain +DOMAIN" where DOMAIN +is your DOMAIN name. +

    Start up the winbindd daemon and test it!

    +Eventually, you will want to modify your smb startup script to automatically invoke the winbindd daemon when the other parts of SAMBA start, but it is possible to test out just the winbind portion first. To start up winbind services, enter the following -command as root:

    root# /usr/local/samba/bin/winbindd

    Winbindd can now also run in 'dual daemon mode'. This will make it +command as root: +

    +root# /usr/local/samba/bin/winbindd +

    +Winbindd can now also run in 'dual daemon mode'. This will make it run as 2 processes. The first will answer all requests from the cache, thus making responses to clients faster. The other will update the cache for the query that the first has just responded. Advantage of this is that responses stay accurate and are faster. -You can enable dual daemon mode by adding '-B' to the commandline:

    root# /usr/local/samba/bin/winbindd -B

    I'm always paranoid and like to make sure the daemon -is really running...

    root# ps -ae | grep winbindd

    This command should produce output like this, if the daemon is running

    3025 ? 00:00:00 winbindd

    Now... for the real test, try to get some information about the -users on your PDC

    root# /usr/local/samba/bin/wbinfo -u

    +You can enable dual daemon mode by adding '-B' to the commandline: +

    +root# /usr/local/samba/bin/winbindd -B +

    +I'm always paranoid and like to make sure the daemon +is really running... +

    +root# ps -ae | grep winbindd +

    +This command should produce output like this, if the daemon is running +

    +3025 ? 00:00:00 winbindd +

    +Now... for the real test, try to get some information about the +users on your PDC +

    +root# /usr/local/samba/bin/wbinfo -u +

    This should echo back a list of users on your Windows users on -your PDC. For example, I get the following response:

    CEO+Administrator
-CEO+burdell
-CEO+Guest
-CEO+jt-ad
-CEO+krbtgt
-CEO+TsInternetUser

    Obviously, I have named my domain 'CEO' and my winbind -separator is '+'.

    You can do the same sort of thing to get group information from -the PDC:

    root# /usr/local/samba/bin/wbinfo -g
-CEO+Domain Admins
-CEO+Domain Users
-CEO+Domain Guests
-CEO+Domain Computers
-CEO+Domain Controllers
-CEO+Cert Publishers
-CEO+Schema Admins
-CEO+Enterprise Admins
-CEO+Group Policy Creator Owners

    The function 'getent' can now be used to get unified +your PDC. For example, I get the following response: +

    +	CEO+Administrator
+	CEO+burdell
+	CEO+Guest
+	CEO+jt-ad
+	CEO+krbtgt
+	CEO+TsInternetUser
+

    +Obviously, I have named my domain 'CEO' and my winbind +separator is '+'. +

    +You can do the same sort of thing to get group information from +the PDC: +

    +root# /usr/local/samba/bin/wbinfo -g
+	CEO+Domain Admins
+	CEO+Domain Users
+	CEO+Domain Guests
+	CEO+Domain Computers
+	CEO+Domain Controllers
+	CEO+Cert Publishers
+	CEO+Schema Admins
+	CEO+Enterprise Admins
+	CEO+Group Policy Creator Owners
+

    +The function 'getent' can now be used to get unified lists of both local and PDC users and groups. -Try the following command:

    root# getent passwd

    You should get a list that looks like your /etc/passwd +Try the following command: +

    +root# getent passwd +

    +You should get a list that looks like your /etc/passwd list followed by the domain users with their new uids, gids, home -directories and default shells.

    The same thing can be done for groups with the command

    root# getent group

    15.5.3.6. Fix the init.d startup scripts

    15.5.3.6.1. Linux

    The winbindd daemon needs to start up after the -smbd and nmbd daemons are running. -To accomplish this task, you need to modify the startup scripts of your system. They are located at /etc/init.d/smb in RedHat and -/etc/init.d/samba in Debian. +directories and default shells. +

    +The same thing can be done for groups with the command +

    +root# getent group +

    Fix the init.d startup scripts

    Linux

    +The winbindd daemon needs to start up after the +smbd and nmbd daemons are running. +To accomplish this task, you need to modify the startup scripts of your system. +They are located at /etc/init.d/smb in RedHat and +/etc/init.d/samba in Debian. script to add commands to invoke this daemon in the proper sequence. My -startup script starts up smbd, -nmbd, and winbindd from the -/usr/local/samba/bin directory directly. The 'start' -function in the script looks like this:

    start() {
-        KIND="SMB"
-        echo -n $"Starting $KIND services: "
+startup script starts up smbd, 
+nmbd, and winbindd from the 
+/usr/local/samba/bin directory directly.  The 'start' 
+function in the script looks like this:
+
    +start() {
+        KIND="SMB"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/smbd $SMBDOPTIONS
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Starting $KIND services: "
+        KIND="NMB"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Starting $KIND services: "
+        KIND="Winbind"
+        echo -n $"Starting $KIND services: "
         daemon /usr/local/samba/bin/winbindd
         RETVAL3=$?
         echo
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \
-           RETVAL=1
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
+		touch /var/lock/subsys/smb || RETVAL=1
         return $RETVAL
-}
    If you would like to run winbindd in dual daemon mode, replace 
+}
+

    If you would like to run winbindd in dual daemon mode, replace the line -

            daemon /usr/local/samba/bin/winbindd
    +

    +        daemon /usr/local/samba/bin/winbindd
+

    in the example above with: -

            daemon /usr/local/samba/bin/winbindd -B
    .

    The 'stop' function has a corresponding entry to shut down the -services and looks like this:

    stop() {
-        KIND="SMB"
-        echo -n $"Shutting down $KIND services: "
+
    +        daemon /usr/local/samba/bin/winbindd -B
+
    .
+
    
+The 'stop' function has a corresponding entry to shut down the 
+services and looks like this:
+
    +stop() {
+        KIND="SMB"
+        echo -n $"Shutting down $KIND services: "
         killproc smbd
         RETVAL=$?
         echo
-        KIND="NMB"
-        echo -n $"Shutting down $KIND services: "
+        KIND="NMB"
+        echo -n $"Shutting down $KIND services: "
         killproc nmbd
         RETVAL2=$?
         echo
-        KIND="Winbind"
-        echo -n $"Shutting down $KIND services: "
+        KIND="Winbind"
+        echo -n $"Shutting down $KIND services: "
         killproc winbindd
         RETVAL3=$?
-        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb
-        echo ""
+        [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \
+		 rm -f /var/lock/subsys/smb
+        echo ""
         return $RETVAL
-}

    15.5.3.6.2. Solaris

    On solaris, you need to modify the -/etc/init.d/samba.server startup script. It usually +} +

    Solaris

    Winbind doesn't work on solaris 9, see the Portability chapter for details.

    On solaris, you need to modify the +/etc/init.d/samba.server startup script. It usually only starts smbd and nmbd but should now start winbindd too. If you -have samba installed in /usr/local/samba/bin, -the file could contains something like this:

    ##
-## samba.server
-##
+have samba installed in /usr/local/samba/bin, 
+the file could contains something like this:
+
    +	##
+	## samba.server
+	##
 
-if [ ! -d /usr/bin ]
-then                    # /usr not mounted
-        exit
-fi
+	if [ ! -d /usr/bin ]
+	then                    # /usr not mounted
+		exit
+	fi
 
-killproc() {            # kill the named process(es)
-        pid=`/usr/bin/ps -e |
-             /usr/bin/grep -w $1 |
-             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
-        [ "$pid" != "" ] && kill $pid
-}
- 
-# Start/stop processes required for samba server
+	killproc() {            # kill the named process(es)
+		pid=`/usr/bin/ps -e |
+		     /usr/bin/grep -w $1 |
+		     /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
+		[ "$pid" != "" ] && kill $pid
+	}
+	 
+	# Start/stop processes required for samba server
 
-case "$1" in
+	case "$1" in
 
-'start')
-#
-# Edit these lines to suit your installation (paths, workgroup, host)
-#
-echo Starting SMBD
-   /usr/local/samba/bin/smbd -D -s \
-	/usr/local/samba/smb.conf
+	'start')
+	#
+	# Edit these lines to suit your installation (paths, workgroup, host)
+	#
+	echo Starting SMBD
+	   /usr/local/samba/bin/smbd -D -s \
+		/usr/local/samba/smb.conf
 
-echo Starting NMBD
-   /usr/local/samba/bin/nmbd -D -l \
-	/usr/local/samba/var/log -s /usr/local/samba/smb.conf
+	echo Starting NMBD
+	   /usr/local/samba/bin/nmbd -D -l \
+		/usr/local/samba/var/log -s /usr/local/samba/smb.conf
 
-echo Starting Winbind Daemon
-   /usr/local/samba/bin/winbindd
-   ;;
+	echo Starting Winbind Daemon
+	   /usr/local/samba/bin/winbindd
+	   ;;
 
-'stop')
-   killproc nmbd
-   killproc smbd
-   killproc winbindd
-   ;;
+	'stop')
+	   killproc nmbd
+	   killproc smbd
+	   killproc winbindd
+	   ;;
 
-*)
-   echo "Usage: /etc/init.d/samba.server { start | stop }"
-   ;;
-esac
    Again, if you would like to run samba in dual daemon mode, replace 
-
       /usr/local/samba/bin/winbindd
    
+	*)
+	   echo "Usage: /etc/init.d/samba.server { start | stop }"
+	   ;;
+	esac
+

    +Again, if you would like to run samba in dual daemon mode, replace +

    +	/usr/local/samba/bin/winbindd
+

    in the script above with: -

       /usr/local/samba/bin/winbindd -B

    15.5.3.6.3. Restarting

    If you restart the smbd, nmbd, -and winbindd daemons at this point, you +

    +	/usr/local/samba/bin/winbindd -B
+

    +

    Restarting

    +If you restart the smbd, nmbd, +and winbindd daemons at this point, you should be able to connect to the samba server as a domain member just as -if you were a local user.

    15.5.3.7. Configure Winbind and PAM

    If you have made it this far, you know that winbindd and samba are working +if you were a local user. +

    Configure Winbind and PAM

    +If you have made it this far, you know that winbindd and samba are working together. If you want to use winbind to provide authentication for other services, keep reading. The pam configuration files need to be altered in this step. (Did you remember to make backups of your original -/etc/pam.d files? If not, do it now.)

    You will need a pam module to use winbindd with these other services. This -module will be compiled in the ../source/nsswitch directory -by invoking the command

    root# make nsswitch/pam_winbind.so

    from the ../source directory. The -pam_winbind.so file should be copied to the location of +/etc/pam.d files? If not, do it now.) +

    +You will need a pam module to use winbindd with these other services. This +module will be compiled in the ../source/nsswitch directory +by invoking the command +

    +root# make nsswitch/pam_winbind.so +

    +from the ../source directory. The +pam_winbind.so file should be copied to the location of your other pam security modules. On my RedHat system, this was the -/lib/security directory. On Solaris, the pam security -modules reside in /usr/lib/security.

    root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security

    15.5.3.7.1. Linux/FreeBSD-specific PAM configuration

    The /etc/pam.d/samba file does not need to be changed. I -just left this fileas it was:

    auth    required        /lib/security/pam_stack.so service=system-auth
-account required        /lib/security/pam_stack.so service=system-auth

    The other services that I modified to allow the use of winbind +/lib/security directory. On Solaris, the pam security +modules reside in /usr/lib/security. +

    +root# cp ../samba/source/nsswitch/pam_winbind.so /lib/security +

    Linux/FreeBSD-specific PAM configuration

    +The /etc/pam.d/samba file does not need to be changed. I +just left this fileas it was: +

    +	auth    required        /lib/security/pam_stack.so service=system-auth
+	account required        /lib/security/pam_stack.so service=system-auth
+

    +The other services that I modified to allow the use of winbind as an authentication service were the normal login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these services, you may first need to change the entries in -/etc/xinetd.d (or /etc/inetd.conf). +/etc/xinetd.d (or /etc/inetd.conf). RedHat 7.1 uses the new xinetd.d structure, in this case you need -to change the lines in /etc/xinetd.d/telnet -and /etc/xinetd.d/wu-ftp from 

    enable = no

    to

    enable = yes

    +to change the lines in /etc/xinetd.d/telnet +and /etc/xinetd.d/wu-ftp from +

    +	enable = no
+

    +to +

    +	enable = yes
+

    For ftp services to work properly, you will also need to either have individual directories for the domain users already present on the server, or change the home directory template to a general directory for all domain users. These can be easily set using -the smb.conf global entry -template homedir.

    The /etc/pam.d/ftp file can be changed +the smb.conf global entry +template homedir. +

    +The /etc/pam.d/ftp file can be changed to allow winbind ftp access in a manner similar to the -samba file. My /etc/pam.d/ftp file was -changed to look like this:

    auth       required     /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
-auth       sufficient   /lib/security/pam_winbind.so
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_shells.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth

    The /etc/pam.d/login file can be changed nearly the -same way. It now looks like this:

    auth       required     /lib/security/pam_securetty.so
-auth       sufficient   /lib/security/pam_winbind.so
-auth       sufficient   /lib/security/pam_unix.so use_first_pass
-auth       required     /lib/security/pam_stack.so service=system-auth
-auth       required     /lib/security/pam_nologin.so
-account    sufficient   /lib/security/pam_winbind.so
-account    required     /lib/security/pam_stack.so service=system-auth
-password   required     /lib/security/pam_stack.so service=system-auth
-session    required     /lib/security/pam_stack.so service=system-auth
-session    optional     /lib/security/pam_console.so

    In this case, I added the auth sufficient /lib/security/pam_winbind.so -lines as before, but also added the required pam_securetty.so +samba file. My /etc/pam.d/ftp file was +changed to look like this: +

    +	auth       required     /lib/security/pam_listfile.so item=user sense=deny \
+		 file=/etc/ftpusers onerr=succeed
+	auth       sufficient   /lib/security/pam_winbind.so
+	auth       required     /lib/security/pam_stack.so service=system-auth
+	auth       required     /lib/security/pam_shells.so
+	account    sufficient   /lib/security/pam_winbind.so
+	account    required     /lib/security/pam_stack.so service=system-auth
+	session    required     /lib/security/pam_stack.so service=system-auth
+

    +The /etc/pam.d/login file can be changed nearly the +same way. It now looks like this: +

    +	auth       required     /lib/security/pam_securetty.so
+	auth       sufficient   /lib/security/pam_winbind.so
+	auth       sufficient   /lib/security/pam_unix.so use_first_pass
+	auth       required     /lib/security/pam_stack.so service=system-auth
+	auth       required     /lib/security/pam_nologin.so
+	account    sufficient   /lib/security/pam_winbind.so
+	account    required     /lib/security/pam_stack.so service=system-auth
+	password   required     /lib/security/pam_stack.so service=system-auth
+	session    required     /lib/security/pam_stack.so service=system-auth
+	session    optional     /lib/security/pam_console.so
+

    +In this case, I added the auth sufficient /lib/security/pam_winbind.so +lines as before, but also added the required pam_securetty.so above it, to disallow root logins over the network. I also added a -sufficient /lib/security/pam_unix.so use_first_pass -line after the winbind.so line to get rid of annoying -double prompts for passwords.

    15.5.3.7.2. Solaris-specific configuration

    The /etc/pam.conf needs to be changed. I changed this file so that my Domain +sufficient /lib/security/pam_unix.so use_first_pass +line after the winbind.so line to get rid of annoying +double prompts for passwords. +

    Solaris-specific configuration

    +The /etc/pam.conf needs to be changed. I changed this file so that my Domain users can logon both locally as well as telnet.The following are the changes that I made.You can customize the pam.conf file as per your requirements,but be sure of those changes because in the worst case it will leave your system -nearly impossible to boot.

    #
-#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
-#
-# Copyright (c) 1996-1999, Sun Microsystems, Inc.
-# All Rights Reserved.
-#
-# PAM configuration
-#
-# Authentication management
-#
-login   auth required   /usr/lib/security/pam_winbind.so
-login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
-login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
-#
-rlogin  auth sufficient /usr/lib/security/pam_winbind.so
-rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
-rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-dtlogin auth sufficient /usr/lib/security/pam_winbind.so
-dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
-other   auth sufficient /usr/lib/security/pam_winbind.so
-other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
-#
-# Account management
-#
-login   account sufficient      /usr/lib/security/pam_winbind.so
-login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-dtlogin account sufficient      /usr/lib/security/pam_winbind.so
-dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-other   account sufficient      /usr/lib/security/pam_winbind.so
-other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
-other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Session management
-#
-other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
-#
-# Password management
-#
-#other   password sufficient     /usr/lib/security/pam_winbind.so
-other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
-dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
-#
-# Support for Kerberos V5 authentication (uncomment to use Kerberos)
-#
-#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
-#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
-#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

    I also added a try_first_pass line after the winbind.so line to get rid of -annoying double prompts for passwords.

    Now restart your Samba and try connecting through your application that you -configured in the pam.conf.

    15.6. Limitations

    Winbind has a number of limitations in its current +nearly impossible to boot. +

    +	#
+	#ident	"@(#)pam.conf	1.14	99/09/16 SMI"
+	#
+	# Copyright (c) 1996-1999, Sun Microsystems, Inc.
+	# All Rights Reserved.
+	#
+	# PAM configuration
+	#
+	# Authentication management
+	#
+	login   auth required   /usr/lib/security/pam_winbind.so
+	login	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass 
+	login	auth required 	/usr/lib/security/$ISA/pam_dial_auth.so.1 try_first_pass 
+	#
+	rlogin  auth sufficient /usr/lib/security/pam_winbind.so
+	rlogin  auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1
+	rlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	dtlogin auth sufficient /usr/lib/security/pam_winbind.so
+	dtlogin	auth required 	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	rsh	auth required	/usr/lib/security/$ISA/pam_rhosts_auth.so.1
+	other   auth sufficient /usr/lib/security/pam_winbind.so
+	other	auth required	/usr/lib/security/$ISA/pam_unix.so.1 try_first_pass
+	#
+	# Account management
+	#
+	login   account sufficient      /usr/lib/security/pam_winbind.so
+	login	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	login	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	dtlogin account sufficient      /usr/lib/security/pam_winbind.so
+	dtlogin	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	dtlogin	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	other   account sufficient      /usr/lib/security/pam_winbind.so
+	other	account requisite	/usr/lib/security/$ISA/pam_roles.so.1 
+	other	account required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	# Session management
+	#
+	other	session required	/usr/lib/security/$ISA/pam_unix.so.1 
+	#
+	# Password management
+	#
+	#other   password sufficient     /usr/lib/security/pam_winbind.so
+	other	password required	/usr/lib/security/$ISA/pam_unix.so.1 
+	dtsession auth required	/usr/lib/security/$ISA/pam_unix.so.1
+	#
+	# Support for Kerberos V5 authentication (uncomment to use Kerberos)
+	#
+	#rlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#login	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#dtlogin	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#other	auth optional	/usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+	#dtlogin	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	account optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	session optional /usr/lib/security/$ISA/pam_krb5.so.1
+	#other	password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass
+

    +I also added a try_first_pass line after the winbind.so line to get rid of +annoying double prompts for passwords. +

    +Now restart your Samba and try connecting through your application that you +configured in the pam.conf. +

    Limitations

    Winbind has a number of limitations in its current released version that we hope to overcome in future - releases:

    • Winbind is currently only available for + releases:

      • Winbind is currently only available for the Linux, Solaris and IRIX operating systems, although ports to other operating systems are certainly possible. For such ports to be feasible, we require the C library of the target operating system to support the Name Service Switch and Pluggable Authentication Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.

      • The mappings of Windows NT RIDs to UNIX ids + PAM gain support among UNIX vendors.

      • The mappings of Windows NT RIDs to UNIX ids is not made algorithmically and depends on the order in which unmapped users or groups are seen by winbind. It may be difficult to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.

      • Currently the winbind PAM module does not take + containing this information is corrupted or destroyed.

      • Currently the winbind PAM module does not take into account possible workstation and logon time restrictions that may be been set for Windows NT users, this is - instead up to the PDC to enforce.

      15.7. Conclusion

      The winbind system, through the use of the Name Service + instead up to the PDC to enforce.

    Conclusion

    The winbind system, through the use of the Name Service Switch, Pluggable Authentication Modules, and appropriate Microsoft RPC calls have allowed us to provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.

    PrevHomeNext
    CUPS Printing SupportUpAdvanced Network Manangement
    \ No newline at end of file + cost of running a mixed UNIX and NT network.

    PrevUpNext
    Chapter14.CUPS Printing SupportHomeChapter16.Advanced Network Manangement
    diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index df490a054b..b1260df500 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -1,648 +1,153 @@ - -winbindd

    winbindd

    Name

    winbindd -- Name Service Switch daemon for resolving names - from NT servers

    Synopsis

    winbindd [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    winbindd is a daemon that provides +winbindd

    Name

    winbindd — Name Service Switch daemon for resolving names + from NT servers

    Synopsis

    winbindd [-F] [-S] [-i] [-B] [-d <debug level>] [-s <smb config file>] [-n]

    DESCRIPTION

    This program is part of the Samba(7) suite.

    winbindd is a daemon that provides a service for the Name Service Switch capability that is present in most modern C libraries. The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS. The exact behaviour can be configured - throught the /etc/nsswitch.conf file. + throught the /etc/nsswitch.conf file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the - Samba system.

    The service provided by winbindd is called `winbind' and + Samba system.

    The service provided by winbindd is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication - services via an associated PAM module.

    The pam_winbind module in the 2.2.2 release only - supports the auth and account + services via an associated PAM module.

    + The pam_winbind module in the 2.2.2 release only + supports the auth and account module-types. The latter simply performs a getpwnam() to verify that the system can obtain a uid for the - user. If the libnss_winbind library has been correctly + user. If the libnss_winbind library has been correctly installed, this should always succeed. -

    The following nsswitch databases are implemented by - the winbindd service:

    hosts

    User information traditionally stored in - the hosts(5) file and used by - gethostbyname(3) functions. Names are +

    The following nsswitch databases are implemented by + the winbindd service:

    hosts

    User information traditionally stored in + the hosts(5) file and used by + gethostbyname(3) functions. Names are resolved through the WINS server or by broadcast. -

    passwd

    User information traditionally stored in - the passwd(5) file and used by - getpwent(3) functions.

    group

    Group information traditionally stored in - the group(5) file and used by - getgrent(3) functions.

    For example, the following simple configuration in the - /etc/nsswitch.conf file can be used to initially - resolve user and group information from /etc/passwd - and /etc/group and then from the +

    passwd

    User information traditionally stored in + the passwd(5) file and used by + getpwent(3) functions.

    group

    Group information traditionally stored in + the group(5) file and used by + getgrent(3) functions.

    For example, the following simple configuration in the + /etc/nsswitch.conf file can be used to initially + resolve user and group information from /etc/passwd + and /etc/group and then from the Windows NT server. -

    passwd:         files winbind
-group:          files winbind

    The following simple configuration in the - /etc/nsswitch.conf file can be used to initially - resolve hostnames from /etc/hosts and then from the - WINS server.

    OPTIONS

    -F

    If specified, this parameter causes - the main winbindd process to not daemonize, +

    +passwd:         files winbind
+group:          files winbind
+

    The following simple configuration in the + /etc/nsswitch.conf file can be used to initially + resolve hostnames from /etc/hosts and then from the + WINS server.

    OPTIONS

    -F

    If specified, this parameter causes + the main winbindd process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running - winbindd under process supervisors such - as supervise and svscan - from Daniel J. Bernstein's daemontools + winbindd under process supervisors such + as supervise and svscan + from Daniel J. Bernstein's daemontools package, or the AIX process monitor. -

    -S

    If specified, this parameter causes - winbindd to log to standard output rather - than a file.

    -V

    Prints the version number for -smbd.

    -s <configuration file>

    The file specified contains the +

    -S

    If specified, this parameter causes + winbindd to log to standard output rather + than a file.

    -V

    Prints the version number for +smbd.

    -s <configuration file>

    The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is -to provide. See smb.conf(5) for more information. +to provide. See +smb.conf(5) for more information. The default configuration file name is determined at -compile time.

    -d|--debug=debuglevel

    debuglevel is an integer +compile time.

    -d|--debug=debuglevel

    debuglevel is an integer from 0 to 10. The default value if this parameter is -not specified is zero.

    The higher this value, the more detail will be +not specified is zero.

    The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of -information about operations carried out.

    Levels above 1 will generate considerable +information about operations carried out.

    Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic.

    Note that specifying this parameter here will -override the log -level parameter in the smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client.

    -h|--help

    Print a summary of command line options.

    -i

    Tells winbindd to not +data, most of which is extremely cryptic.

    Note that specifying this parameter here will +override the log +level parameter in the +smb.conf(5) file.

    -l|--logfile=logbasename

    File name for log/debug files. The extension +".client" will be appended. The log file is +never removed by the client. +

    -h|--help

    Print a summary of command line options. +

    -i

    Tells winbindd to not become a daemon and detach from the current terminal. This option is used by developers when interactive debugging - of winbindd is required. - winbindd also logs to standard output, - as if the -S parameter had been given. -

    -n

    Disable caching. This means winbindd will + of winbindd is required. + winbindd also logs to standard output, + as if the -S parameter had been given. +

    -n

    Disable caching. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower. The results will however be more accurate, since results from the cache might not be up-to-date. This might also temporarily hang winbindd if the DC doesn't respond. -

    -B

    Dual daemon mode. This means winbindd will run +

    -B

    Dual daemon mode. This means winbindd will run as 2 threads. The first will answer all requests from the cache, thus making responses to clients faster. The other will update the cache for the query that the first has just responded. Advantage of this is that responses stay accurate and are faster. -

    NAME AND ID RESOLUTION

    Users and groups on a Windows NT server are assigned +

    NAME AND ID RESOLUTION

    Users and groups on a Windows NT server are assigned a relative id (rid) which is unique for the domain when the user or group is created. To convert the Windows NT user or group into a unix user or group, a mapping between rids and unix user - and group ids is required. This is one of the jobs that winbindd performs.

    As winbindd users and groups are resolved from a server, user + and group ids is required. This is one of the jobs that + winbindd performs.

    As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command. The allocated unix ids are stored in a database file under the Samba lock directory and will be - remembered.

    WARNING: The rid to unix id database is the only location + remembered.

    WARNING: The rid to unix id database is the only location where the user and group mappings are stored by winbindd. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user - and group rids.

    CONFIGURATION

    Configuration of the winbindd daemon - is done through configuration parameters in the smb.conf(5) file. All parameters should be specified in the - [global] section of smb.conf.

    EXAMPLE SETUP

    To setup winbindd for user and group lookups plus + and group rids.

    CONFIGURATION

    Configuration of the winbindd daemon + is done through configuration parameters in the smb.conf(5) file. All parameters should be specified in the + [global] section of smb.conf.

    EXAMPLE SETUP

    To setup winbindd for user and group lookups plus authentication from a domain controller use something like the - following setup. This was tested on a RedHat 6.2 Linux box.

    In /etc/nsswitch.conf put the + following setup. This was tested on a RedHat 6.2 Linux box.

    In /etc/nsswitch.conf put the following: -

    passwd:     files winbind
-group:      files winbind

    In /etc/pam.d/* replace the auth lines with something like this: -

    auth       required	/lib/security/pam_securetty.so
+
    +passwd:     files winbind
+group:      files winbind
+
    In /etc/pam.d/* replace the 
+	auth lines with something like this:
+
    +auth       required	/lib/security/pam_securetty.so
 auth       required	/lib/security/pam_nologin.so
 auth       sufficient	/lib/security/pam_winbind.so
-auth       required     /lib/security/pam_pwdb.so use_first_pass shadow nullok
    Note in particular the use of the sufficient
-	 keyword and the use_first_pass keyword. 
    Now replace the account lines with this: 
    account    required	/lib/security/pam_winbind.so
-	
    The next step is to join the domain. To do that use the 
-	net program like this:  
    net join -S PDC -U Administrator
    The username after the -U can be any
+auth       required     /lib/security/pam_pwdb.so use_first_pass shadow nullok
+

    Note in particular the use of the sufficient + keyword and the use_first_pass keyword.

    Now replace the account lines with this:

    account required /lib/security/pam_winbind.so +

    The next step is to join the domain. To do that use the + net program like this:

    net join -S PDC -U Administrator

    The username after the -U can be any Domain user that has administrator privileges on the machine. - Substitute the name or IP of your PDC for "PDC".

    Next copy libnss_winbind.so to - /lib and pam_winbind.so - to /lib/security. A symbolic link needs to be - made from /lib/libnss_winbind.so to - /lib/libnss_winbind.so.2. If you are using an + Substitute the name or IP of your PDC for "PDC".

    Next copy libnss_winbind.so to + /lib and pam_winbind.so + to /lib/security. A symbolic link needs to be + made from /lib/libnss_winbind.so to + /lib/libnss_winbind.so.2. If you are using an older version of glibc then the target of the link should be - /lib/libnss_winbind.so.1.

    Finally, setup a smb.conf(5) containing directives like the + /lib/libnss_winbind.so.1.

    Finally, setup a smb.conf(5) containing directives like the following: -

    [global]
+
    +[global]
 	winbind separator = +
         winbind cache time = 10
         template shell = /bin/bash
@@ -651,296 +156,59 @@ CLASS="PROGRAMLISTING"
         winbind gid = 10000-20000
         workgroup = DOMAIN
         security = domain
-        password server = *
    Now start winbindd and you should find that your user and 
+        password server = *
+

    Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username. You may wish to use the - commands getent passwd and getent group - to confirm the correct operation of winbindd.

    NOTES

    The following notes are useful when configuring and - running winbindd:

    nmbd(8) must be running on the local machine - for winbindd to work. winbindd queries + commands getent passwd and getent group + to confirm the correct operation of winbindd.

    NOTES

    The following notes are useful when configuring and + running winbindd:

    nmbd(8) must be running on the local machine + for winbindd to work. winbindd queries the list of trusted domains for the Windows NT server - on startup and when a SIGHUP is received. Thus, for a running winbindd to become aware of new trust relationships between - servers, it must be sent a SIGHUP signal.

    PAM is really easy to misconfigure. Make sure you know what + on startup and when a SIGHUP is received. Thus, for a running + winbindd to become aware of new trust relationships between + servers, it must be sent a SIGHUP signal.

    PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible - to set up PAM such that you can no longer log into your system.

    If more than one UNIX machine is running winbindd, + to set up PAM such that you can no longer log into your system.

    If more than one UNIX machine is running winbindd, then in general the user and groups ids allocated by winbindd will not be the same. The user and group ids will only be valid for the local - machine.

    If the the Windows NT RID to UNIX user and group id mapping - file is damaged or destroyed then the mappings will be lost.

    SIGNALS

    The following signals can be used to manipulate the - winbindd daemon.

    SIGHUP

    Reload the smb.conf(5) file and + machine.

    If the the Windows NT RID to UNIX user and group id mapping + file is damaged or destroyed then the mappings will be lost.

    SIGNALS

    The following signals can be used to manipulate the + winbindd daemon.

    SIGHUP

    Reload the smb.conf(5) file and apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted - by winbindd is also reloaded.

    SIGUSR1

    The SIGUSR1 signal will cause winbindd to write status information to the winbind + by winbindd is also reloaded.

    SIGUSR1

    The SIGUSR1 signal will cause + winbindd to write status information to the winbind log file including information about the number of user and - group ids allocated by winbindd.

    Log files are stored in the filename specified by the - log file parameter.

    FILES

    /etc/nsswitch.conf(5)

    Name service switch configuration file.

    /tmp/.winbindd/pipe

    The UNIX pipe over which clients communicate with - the winbindd program. For security reasons, the + group ids allocated by winbindd.

    Log files are stored in the filename specified by the + log file parameter.

    FILES

    /etc/nsswitch.conf(5)

    Name service switch configuration file.

    /tmp/.winbindd/pipe

    The UNIX pipe over which clients communicate with + the winbindd program. For security reasons, the winbind client will only attempt to connect to the winbindd daemon - if both the /tmp/.winbindd directory - and /tmp/.winbindd/pipe file are owned by - root.

    $LOCKDIR/winbindd_privilaged/pipe

    The UNIX pipe over which 'privilaged' clients - communicate with the winbindd program. For security + if both the /tmp/.winbindd directory + and /tmp/.winbindd/pipe file are owned by + root.

    $LOCKDIR/winbindd_privilaged/pipe

    The UNIX pipe over which 'privilaged' clients + communicate with the winbindd program. For security reasons, access to some winbindd functions - like those needed by - the ntlm_auth utility - is restricted. By default, + the ntlm_auth utility - is restricted. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privilaged to allow programs like 'squid' to use ntlm_auth. Note that the winbind client will only attempt to connect to the winbindd daemon - if both the $LOCKDIR/winbindd_privilaged directory - and $LOCKDIR/winbindd_privilaged/pipe file are owned by - root.

    /lib/libnss_winbind.so.X

    Implementation of name service switch library. -

    $LOCKDIR/winbindd_idmap.tdb

    Storage for the Windows NT rid to UNIX user/group + if both the $LOCKDIR/winbindd_privilaged directory + and $LOCKDIR/winbindd_privilaged/pipe file are owned by + root.

    /lib/libnss_winbind.so.X

    Implementation of name service switch library. +

    $LOCKDIR/winbindd_idmap.tdb

    Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially - compiled using the --with-lockdir option. - This directory is by default /usr/local/samba/var/locks - .

    $LOCKDIR/winbindd_cache.tdb

    Storage for cached user and group information. -

    VERSION

    This man page is correct for version 3.0 of - the Samba suite.

    SEE ALSO

    nsswitch.conf(5), Samba(7), wbinfo(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities + compiled using the --with-lockdir option. + This directory is by default /usr/local/samba/var/locks + .

    $LOCKDIR/winbindd_cache.tdb

    Storage for cached user and group information. +

    VERSION

    This man page is correct for version 3.0 of + the Samba suite.

    SEE ALSO

    nsswitch.conf(5), Samba(7), wbinfo(8), smb.conf(5)

    AUTHOR

    The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar - to the way the Linux kernel is developed.

    wbinfo and winbindd were - written by Tim Potter.

    The conversion to DocBook for Samba 2.2 was done + to the way the Linux kernel is developed.

    wbinfo and winbindd were + written by Tim Potter.

    The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for - Samba 3.0 was done by Alexander Bokovoy.

    \ No newline at end of file + Samba 3.0 was done by Alexander Bokovoy.

    diff --git a/docs/manpages/editreg.1 b/docs/manpages/editreg.1 index f2c7ed52e8..6f418a28dc 100644 --- a/docs/manpages/editreg.1 +++ b/docs/manpages/editreg.1 @@ -1,45 +1,71 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "EDITREG" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "EDITREG" 1 "" "" "" .SH NAME editreg \- A utility to report and change SIDs in registry files -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBeditreg\fR [ \fB-v\fR ] [ \fB-c file\fR ] \fBfile\fR +.nf +\fBeditreg\fR [-v] [-c file] {file} +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBeditreg\fR is a utility that -can visualize windows registry files (currently only NT4) and apply -so-called commandfiles to them. +\fBeditreg\fR is a utility that can visualize windows registry files (currently only NT4) and apply so-called commandfiles to them\&. + .SH "OPTIONS" + .TP -\fBregistry_file\fR -Registry file to view or edit. +registry_file +Registry file to view or edit\&. + + .TP -\fB-v,--verbose\fR -Increases verbosity of messages. +-v,--verbose +Increases verbosity of messages\&. + + .TP -\fB-c commandfile\fR -Read commands to execute on \fIregistry_file\fR from \fIcommandfile\fR. Currently not yet supported! +-c commandfile +Read commands to execute on \fIregistry_file\fR from \fIcommandfile\fR\&. Currently not yet supported! + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The editreg man page was written by Jelmer Vernooij. +The editreg man page was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/findsmb.1 b/docs/manpages/findsmb.1 index ab79307106..bd9ba62b05 100644 --- a/docs/manpages/findsmb.1 +++ b/docs/manpages/findsmb.1 @@ -1,103 +1,95 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "FINDSMB" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "FINDSMB" 1 "" "" "" .SH NAME -findsmb \- list info about machines that respond to SMB name queries on a subnet -.SH SYNOPSIS +findsmb \- list info about machines that respond to SMB name queries on a subnet +.SH "SYNOPSIS" -\fBfindsmb\fR [ \fBsubnet broadcast address\fR ] +.nf +\fBfindsmb\fR [subnet broadcast address] +.fi .SH "DESCRIPTION" + .PP -This perl script is part of the \fBSamba\fR(7) -suite. +This perl script is part of the \fBSamba\fR(7) suite\&. + .PP -\fBfindsmb\fR is a perl script that -prints out several pieces of information about machines -on a subnet that respond to SMB name query requests. -It uses \fBnmblookup\fR(1) -and \fBsmbclient\fR(1) -to obtain this information. +\fBfindsmb\fR is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests\&. It uses \fBnmblookup\fR(1) and \fBsmbclient\fR(1) to obtain this information\&. + .SH "OPTIONS" + .TP -\fB-r\fR -Controls whether \fBfindsmb\fR takes -bugs in Windows95 into account when trying to find a Netbios name -registered of the remote machine. This option is disabled by default -because it is specific to Windows 95 and Windows 95 machines only. -If set, \fBnmblookup\fR(1) -will be called with -B option. +-r +Controls whether \fBfindsmb\fR takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine\&. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only\&. If set, \fBnmblookup\fR(1) will be called with \fB-B\fR option\&. + + .TP -\fBsubnet broadcast address\fR -Without this option, \fBfindsmb -\fR will probe the subnet of the machine where -\fBfindsmb\fR(1) -is run. This value is passed to -\fBnmblookup\fR(1) -as part of the -B option. +subnet broadcast address +Without this option, \fBfindsmb \fR will probe the subnet of the machine where \fBfindsmb\fR(1) is run\&. This value is passed to \fBnmblookup\fR(1) as part of the \fB-B\fR option\&. + + .SH "EXAMPLES" + .PP -The output of \fBfindsmb\fR lists the following -information for all machines that respond to the initial -\fBnmblookup\fR for any name: IP address, NetBIOS name, -Workgroup name, operating system, and SMB server version. -.PP -There will be a '+' in front of the workgroup name for -machines that are local master browsers for that workgroup. There -will be an '*' in front of the workgroup name for -machines that are the domain master browser for that workgroup. -Machines that are running Windows, Windows 95 or Windows 98 will -not show any information about the operating system or server -version. +The output of \fBfindsmb\fR lists the following information for all machines that respond to the initial\fBnmblookup\fR for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version\&. + .PP -The command with -r option -must be run on a system without \fBnmbd\fR(8) running. -If \fBnmbd\fR is running on the system, you will -only get the IP address and the DNS name of the machine. To -get proper responses from Windows 95 and Windows 98 machines, -the command must be run as root and with -r -option on a machine without \fBnmbd\fR running. +There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup\&. There will be an '*' in front of the workgroup name for machines that are the domain master browser for that workgroup\&. Machines that are running Windows, Windows 95 or Windows 98 will not show any information about the operating system or server version\&. + .PP -For example, running \fBfindsmb\fR -without -r option set would yield output similar -to the following +The command with \fB-r\fR option must be run on a system without \fBnmbd\fR(8)running\&. If \fBnmbd\fR is running on the system, you will only get the IP address and the DNS name of the machine\&. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with \fB-r\fR option on a machine without \fBnmbd\fR running\&. +.PP +For example, running \fBfindsmb\fR without \fB-r\fR option set would yield output similar to the following .nf + IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION --------------------------------------------------------------------- -192.168.35.10 MINESET-TEST1 [DMVENGR] -192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6] -192.168.35.56 HERBNT2 [HERB-NT] -192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX] -192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10] -192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX] -192.168.35.78 HERBDHCP1 +[HERB] -192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0] -192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager] -192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0] +192\&.168\&.35\&.10 MINESET-TEST1 [DMVENGR] +192\&.168\&.35\&.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2\&.0\&.6] +192\&.168\&.35\&.56 HERBNT2 [HERB-NT] +192\&.168\&.35\&.63 GANDALF [MVENGR] [Unix] [Samba 2\&.0\&.5a for IRIX] +192\&.168\&.35\&.65 SAUNA [WORKGROUP] [Unix] [Samba 1\&.9\&.18p10] +192\&.168\&.35\&.71 FROGSTAR [ENGR] [Unix] [Samba 2\&.0\&.0 for IRIX] +192\&.168\&.35\&.78 HERBDHCP1 +[HERB] +192\&.168\&.35\&.88 SCNT2 +[MVENGR] [Windows NT 4\&.0] [NT LAN Manager 4\&.0] +192\&.168\&.35\&.93 FROGSTAR-PC [MVENGR] [Windows 5\&.0] [Windows 2000 LAN Manager] +192\&.168\&.35\&.97 HERBNT1 *[HERB-NT] [Windows NT 4\&.0] [NT LAN Manager 4\&.0] .fi + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBnmbd\fR(8), -\fBsmbclient\fR(1), and \fBnmblookup\fR(1) +\fBnmbd\fR(8),\fBsmbclient\fR(1), and \fBnmblookup\fR(1) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) -and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook -XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/lmhosts.5 b/docs/manpages/lmhosts.5 index 2ec8c256d4..47bedda12a 100644 --- a/docs/manpages/lmhosts.5 +++ b/docs/manpages/lmhosts.5 @@ -1,84 +1,92 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "LMHOSTS" "5" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "LMHOSTS" 5 "" "" "" .SH NAME lmhosts \- The Samba NetBIOS hosts file -.SH SYNOPSIS +.SH "SYNOPSIS" + .PP -\fIlmhosts\fR is the \fBSamba\fR(7) NetBIOS name to IP address mapping file. +\fIlmhosts\fR is the \fBSamba\fR(7) NetBIOS name to IP address mapping file\&. + .SH "DESCRIPTION" + .PP -This file is part of the \fBSamba\fR(7) suite. +This file is part of the \fBSamba\fR(7) suite\&. + .PP -\fIlmhosts\fR is the \fBSamba -\fR NetBIOS name to IP address mapping file. It -is very similar to the \fI/etc/hosts\fR file -format, except that the hostname component must correspond -to the NetBIOS naming format. +\fIlmhosts\fR is the \fBSamba \fR NetBIOS name to IP address mapping file\&. It is very similar to the \fI/etc/hosts\fR file format, except that the hostname component must correspond to the NetBIOS naming format\&. + .SH "FILE FORMAT" + .PP -It is an ASCII file containing one line for NetBIOS name. -The two fields on each line are separated from each other by -white space. Any entry beginning with '#' is ignored. Each line -in the lmhosts file contains the following information: -.TP 0.2i +It is an ASCII file containing one line for NetBIOS name\&. The two fields on each line are separated from each other by white space\&. Any entry beginning with '#' is ignored\&. Each line in the lmhosts file contains the following information: + +.TP 3 \(bu -IP Address - in dotted decimal format. -.TP 0.2i +IP Address - in dotted decimal format\&. + +.TP \(bu -NetBIOS Name - This name format is a -maximum fifteen character host name, with an optional -trailing '#' character followed by the NetBIOS name type -as two hexadecimal digits. - -If the trailing '#' is omitted then the given IP -address will be returned for all names that match the given -name, whatever the NetBIOS name type in the lookup. +NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type as two hexadecimal digits\&. + + +If the trailing '#' is omitted then the given IP address will be returned for all names that match the given name, whatever the NetBIOS name type in the lookup\&. + +.LP + .PP An example follows: - .nf + # -# Sample Samba lmhosts file. +# Sample Samba lmhosts file\&. # -192.9.200.1 TESTPC -192.9.200.20 NTSERVER#20 -192.9.200.21 SAMBASERVER - -.fi +192\&.9\&.200\&.1 TESTPC +192\&.9\&.200\&.20 NTSERVER#20 +192\&.9\&.200\&.21 SAMBASERVER + .fi + .PP -Contains three IP to NetBIOS name mappings. The first -and third will be returned for any queries for the names "TESTPC" -and "SAMBASERVER" respectively, whatever the type component of -the NetBIOS name requested. +Contains three IP to NetBIOS name mappings\&. The first and third will be returned for any queries for the names "TESTPC" and "SAMBASERVER" respectively, whatever the type component of the NetBIOS name requested\&. + .PP -The second mapping will be returned only when the "0x20" name -type for a name "NTSERVER" is queried. Any other name type will not -be resolved. +The second mapping will be returned only when the "0x20" name type for a name "NTSERVER" is queried\&. Any other name type will not be resolved\&. + .PP -The default location of the \fIlmhosts\fR file -is in the same directory as the \fBsmb.conf\fR(5) file. +The default location of the \fIlmhosts\fR file is in the same directory as the \fBsmb.conf\fR(5) file\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbclient\fR(1), \fBsmb.conf\fR(5), and \fBsmbpasswd\fR(8) +\fBsmbclient\fR(1), \fBsmb.conf\fR(5), and \fBsmbpasswd\fR(8) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at -ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook -XML 4.2 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available atftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/net.8 b/docs/manpages/net.8 index ce864d0d70..d473503792 100644 --- a/docs/manpages/net.8 +++ b/docs/manpages/net.8 @@ -1,441 +1,549 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "NET" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "NET" 8 "" "" "" .SH NAME net \- Tool for administration of Samba and remote CIFS servers. -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBnet\fR \fB\fR [ \fB-h\fR ] [ \fB-w workgroup\fR ] [ \fB-W myworkgroup\fR ] [ \fB-U user\fR ] [ \fB-I ip-address\fR ] [ \fB-p port\fR ] [ \fB-n myname\fR ] [ \fB-s conffile\fR ] [ \fB-S server\fR ] [ \fB-l\fR ] [ \fB-P\fR ] [ \fB-D debuglevel\fR ] +.nf +\fBnet\fR {} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] + [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel] + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The samba net utility is meant to work just like the net utility -available for windows and DOS. The first argument should be used -to specify the protocol to use when executing a certain command. -ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) -clients and RPC can be used for NT4 and Windows 2000. If this -argument is omitted, net will try to determine it automatically. -Not all commands are available on all protocols. +The samba net utility is meant to work just like the net utility available for windows and DOS\&. The first argument should be used to specify the protocol to use when executing a certain command\&. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000\&. If this argument is omitted, net will try to determine it automatically\&. Not all commands are available on all protocols\&. + .SH "OPTIONS" + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-w target-workgroup\fR -Sets target workgroup or domain. You have to specify -either this option or the IP address or the name of a server. +-w target-workgroup +Sets target workgroup or domain\&. You have to specify either this option or the IP address or the name of a server\&. + + .TP -\fB-W workgroup\fR +-W workgroup Sets client workgroup or domain + + .TP -\fB-U user\fR +-U user User name to use + + .TP -\fB-I ip-address\fR -IP address of target server to use. You have to -specify either this option or a target workgroup or -a target server. +-I ip-address +IP address of target server to use\&. You have to specify either this option or a target workgroup or a target server\&. + + .TP -\fB-p port\fR -Port on the target server to connect to (usually 139 or 445). -Defaults to trying 445 first, then 139. +-p port +Port on the target server to connect to (usually 139 or 445)\&. Defaults to trying 445 first, then 139\&. + + .TP -\fB-n \fR -This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the \fINetBIOS -name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command -line setting will take precedence over settings in -\fBsmb.conf\fR(5). +-n +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-S server\fR -Name of target server. You should specify either -this option or a target workgroup or a target IP address. +-S server +Name of target server\&. You should specify either this option or a target workgroup or a target IP address\&. + + .TP -\fB-l\fR -When listing data, give more information on each item. +-l +When listing data, give more information on each item\&. + + .TP -\fB-P\fR -Make queries to the external server using the machine account of the local server. +-P +Make queries to the external server using the machine account of the local server\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .SH "COMMANDS" + .SS "TIME" + .PP -The \fBNET TIME\fR command allows you to view the time on a remote server -or synchronise the time on the local server with the time on the remote server. -.SS "TIME" +The \fBNET TIME\fR command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server\&. + .PP -Without any options, the \fBNET TIME\fR command -displays the time on the remote server. -.SS "TIME SYSTEM" +Without any options, the \fBNET TIME\fR command displays the time on the remote server\&. + .PP Displays the time on the remote server in a format ready for \fB/bin/date\fR -.SS "TIME SET" + .PP -Tries to set the date and time of the local server to that on -the remote server using \fB/bin/date\fR. -.SS "TIME ZONE" +Tries to set the date and time of the local server to that on the remote server using \fB/bin/date\fR\&. + .PP -Displays the timezone in hours from GMT on the remote computer. -.SS "[RPC|ADS] JOIN [TYPE] [-U USERNAME[%PASSWORD]] [OPTIONS]" +Displays the timezone in hours from GMT on the remote computer\&. + +.SS "[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]" + .PP -Join a domain. If the account already exists on the server, and -[TYPE] is MEMBER, the machine will attempt to join automatically. -(Assuming that the machine has been created in server manager) -Otherwise, a password will be prompted for, and a new account may -be created. +Join a domain\&. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically\&. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may be created\&. + .PP -[TYPE] may be PDC, BDC or MEMBER to specify the type of server -joining the domain. -.SS "[RPC] OLDJOIN [OPTIONS]" +[TYPE] may be PDC, BDC or MEMBER to specify the type of server joining the domain\&. + +.SS "[RPC] OLDJOIN [options]" + .PP -Join a domain. Use the OLDJOIN option to join the domain -using the old style of domain joining - you need to create a trust -account in server manager first. +Join a domain\&. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust account in server manager first\&. + .SS "[RPC|ADS] USER" -.SS "[RPC|ADS] USER DELETE TARGET" + .PP Delete specified user -.SS "[RPC|ADS] USER LIST" + .PP List all users -.SS "[RPC|ADS] USER INFO TARGET" + .PP -List the domain groups of a the specified user. -.SS "[RPC|ADS] USER ADD NAME [PASSWORD] [-F USER FLAGS] [-C COMMENT]" +List the domain groups of a the specified user\&. + .PP -Add specified user. +Add specified user\&. + .SS "[RPC|ADS] GROUP" -.SS "[RPC|ADS] GROUP [MISC OPTIONS] [TARGETS]" + .PP -List user groups. -.SS "[RPC|ADS] GROUP DELETE NAME [MISC. OPTIONS]" +List user groups\&. + .PP -Delete specified group. -.SS "[RPC|ADS] GROUP ADD NAME [-C COMMENT]" +Delete specified group\&. + .PP -Create specified group. +Create specified group\&. + .SS "[RAP|RPC] SHARE" -.SS "[RAP|RPC] SHARE [MISC. OPTIONS] [TARGETS]" + .PP -Enumerates all exported resources (network shares) on target server. -.SS "[RAP|RPC] SHARE ADD NAME=SERVERPATH [-C COMMENT] [-M MAXUSERS] [TARGETS]" +Enumerates all exported resources (network shares) on target server\&. + .PP -Adds a share from a server (makes the export active). Maxusers -specifies the number of users that can be connected to the -share simultaneously. -.SS "SHARE DELETE SHARENAM" +Adds a share from a server (makes the export active)\&. Maxusers specifies the number of users that can be connected to the share simultaneously\&. + .PP -Delete specified share. -.SS "[RPC|RAP] FILE" +Delete specified share\&. + .SS "[RPC|RAP] FILE" + .PP -List all open files on remote server. -.SS "[RPC|RAP] FILE CLOSE FILEID" +List all open files on remote server\&. + .PP -Close file with specified \fIfileid\fR on -remote server. -.SS "[RPC|RAP] FILE INFO FILEID" +Close file with specified \fIfileid\fR on remote server\&. + .PP -Print information on specified \fIfileid\fR. -Currently listed are: file-id, username, locks, path, permissions. -.SS "[RAP|RPC] FILE USER" -.sp +Print information on specified \fIfileid\fR\&. Currently listed are: file-id, username, locks, path, permissions\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE + .SS "SESSION" -.SS "RAP SESSION" + .PP -Without any other options, SESSION enumerates all active SMB/CIFS -sessions on the target server. -.SS "RAP SESSION DELETE|CLOSE CLIENT_NAME" +Without any other options, SESSION enumerates all active SMB/CIFS sessions on the target server\&. + .PP -Close the specified sessions. -.SS "RAP SESSION INFO CLIENT_NAME" +Close the specified sessions\&. + .PP -Give a list with all the open files in specified session. +Give a list with all the open files in specified session\&. + .SS "RAP SERVER DOMAIN" + .PP -List all servers in specified domain or workgroup. Defaults -to local domain. +List all servers in specified domain or workgroup\&. Defaults to local domain\&. + .SS "RAP DOMAIN" + .PP -Lists all domains and workgroups visible on the -current network. +Lists all domains and workgroups visible on the current network\&. + .SS "RAP PRINTQ" -.SS "RAP PRINTQ LIST QUEUE_NAME" + .PP -Lists the specified print queue and print jobs on the server. -If the \fIQUEUE_NAME\fR is omitted, all -queues are listed. -.SS "RAP PRINTQ DELETE JOBID" +Lists the specified print queue and print jobs on the server\&. If the \fIQUEUE_NAME\fR is omitted, all queues are listed\&. + .PP -Delete job with specified id. -.SS "RAP VALIDATE USER [PASSWORD]" +Delete job with specified id\&. + +.SS "RAP VALIDATE user [password]" + .PP -Validate whether the specified user can log in to the -remote server. If the password is not specified on the commandline, it -will be prompted. -.sp +Validate whether the specified user can log in to the remote server\&. If the password is not specified on the commandline, it will be prompted\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE + .SS "RAP GROUPMEMBER" -.SS "RAP GROUPMEMBER LIST GROUP" + .PP -List all members of the specified group. -.SS "RAP GROUPMEMBER DELETE GROUP USER" +List all members of the specified group\&. + .PP -Delete member from group. -.SS "RAP GROUPMEMBER ADD GROUP USER" +Delete member from group\&. + .PP -Add member to group. -.SS "RAP ADMIN COMMAND" +Add member to group\&. + +.SS "RAP ADMIN command" + .PP -Execute the specified \fIcommand\fR on -the remote server. Only works with OS/2 servers. -.sp +Execute the specified \fIcommand\fR on the remote server\&. Only works with OS/2 servers\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE + .SS "RAP SERVICE" -.SS "RAP SERVICE START NAME [ARGUMENTS...]" + .PP -Start the specified service on the remote server. Not implemented yet. -.sp +Start the specified service on the remote server\&. Not implemented yet\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE -.SS "RAP SERVICE STOP" + .PP -Stop the specified service on the remote server. -.sp +Stop the specified service on the remote server\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE + .SS "RAP PASSWORD USER OLDPASS NEWPASS" + .PP -Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR. +Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR\&. + .SS "LOOKUP" -.SS "LOOKUP HOST HOSTNAME [TYPE]" + .PP -Lookup the IP address of the given host with the specified type (netbios suffix). -The type defaults to 0x20 (workstation). -.SS "LOOKUP LDAP [DOMAIN" +Lookup the IP address of the given host with the specified type (netbios suffix)\&. The type defaults to 0x20 (workstation)\&. + .PP -Give IP address of LDAP server of specified \fIDOMAIN\fR. Defaults to local domain. -.SS "LOOKUP KDC [REALM]" +Give IP address of LDAP server of specified \fIDOMAIN\fR\&. Defaults to local domain\&. + .PP -Give IP address of KDC for the specified \fIREALM\fR. -Defaults to local realm. -.SS "LOOKUP DC [DOMAIN]" +Give IP address of KDC for the specified \fIREALM\fR\&. Defaults to local realm\&. + .PP -Give IP's of Domain Controllers for specified \fIDOMAIN\fR. Defaults to local domain. -.SS "LOOKUP MASTER DOMAIN" +Give IP's of Domain Controllers for specified \fI DOMAIN\fR\&. Defaults to local domain\&. + .PP -Give IP of master browser for specified \fIDOMAIN\fR -or workgroup. Defaults to local domain. +Give IP of master browser for specified \fIDOMAIN\fR or workgroup\&. Defaults to local domain\&. + .SS "CACHE" + +.PP +Samba uses a general caching interface called 'gencache'\&. It can be controlled using 'NET CACHE'\&. + +.PP +All the timeout parameters support the suffixes: s - Secondsm - Minutesh - Hoursd - Daysw - Weeks + +.PP +Add specified key+data to the cache with the given timeout\&. + +.PP +Delete key from the cache\&. + +.PP +Update data of existing cache entry\&. + +.PP +Search for the specified pattern in the cache data\&. + +.PP +List all current items in the cache\&. + +.PP +Remove all the current items from the cache\&. + +.SS "GETLOCALSID [DOMAIN]" + .PP -Samba uses a general caching interface called 'gencache'. It -can be controlled using 'NET CACHE'. +Print the SID of the specified domain, or if the parameter is omitted, the SID of the domain the local server is in\&. + +.SS "SETLOCALSID S-1-5-21-x-y-z" + .PP -All the timeout parameters support the suffixes: +Sets domain sid for the local server to the specified SID\&. + +.SS "GROUPMAP" + +.PP +Manage the mappings between Windows group SIDs and UNIX groups\&. Parameters take the for "parameter=value"\&. Common options include: + +.TP 3 +\(bu +unixgroup - Name of the UNIX group + +.TP +\(bu +ntgroup - Name of the Windows NT group (must be resolvable to a SID -s - Seconds +.TP +\(bu +rid - Unsigned 32-bit integer -m - Minutes +.TP +\(bu +sid - Full SID in the form of "S-1-\&.\&.\&." -h - Hours +.TP +\(bu +type - Type of the group; either 'domain', 'local', or 'builtin' -d - Days +.TP +\(bu +comment - Freeform text description of the group + +.LP -w - Weeks -.SS "CACHE ADD KEY DATA TIME-OUT" .PP -Add specified key+data to the cache with the given timeout. -.SS "CACHE DEL KEY" +Add a new group mapping entry + .PP -Delete key from the cache. -.SS "CACHE SET KEY DATA TIME-OUT" +net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string] + .PP -Update data of existing cache entry. -.SS "CACHE SEARCH PATTERN" +Delete a group mapping entry + .PP -Search for the specified pattern in the cache data. -.SS "CACHE LIST" +net groupmap delete {ntgroup=string|sid=SID} + .PP -List all current items in the cache. -.SS "CACHE FLUSH" +Update en existing group entry + .PP -Remove all the current items from the cache. -.SS "GETLOCALSID [DOMAIN]" +net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local} + .PP -Print the SID of the specified domain, or if the parameter is -omitted, the SID of the domain the local server is in. -.SS "SETLOCALSID S-1-5-21-X-Y-Z" +List existing group mapping entries + .PP -Sets domain sid for the local server to the specified SID. +net groupmap list [verbose] [ntgroup=string] [sid=SID] + .SS "MAXRID" + .PP -Prints out the highest RID currently in use on the local -server (by the active 'passdb backend'). +Prints out the highest RID currently in use on the local server (by the active 'passdb backend')\&. + .SS "RPC INFO" + .PP -Print information about the domain of the remote server, -such as domain name, domain sid and number of users and groups. +Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups\&. + .SS "[RPC|ADS] TESTJOIN" + .PP -Check whether participation in a domain is still valid. +Check whether participation in a domain is still valid\&. + .SS "[RPC|ADS] CHANGETRUSTPW" + .PP -Force change of domain trust password. +Force change of domain trust password\&. + .SS "RPC TRUSTDOM" -.SS "RPC TRUSTDOM ADD DOMAIN" + .PP -Add a interdomain trust account for -\fIDOMAIN\fR to the remote server. -.SS "RPC TRUSTDOM DEL DOMAIM" +Add a interdomain trust account for \fIDOMAIN\fR to the remote server\&. + .PP -Remove interdomain trust account for -\fIDOMAIN\fR from the remote server. -.sp +Remove interdomain trust account for \fIDOMAIN\fR from the remote server\&. + .RS -.B "Note:" -Currently NOT implemented. +.Sh "Note" + +.PP +Currently NOT implemented\&. + .RE -.SS "RPC TRUSTDOM ESTABLISH DOMAIN" + .PP -Establish a trust relationship to a trusting domain. -Interdomain account must already be created on the remote PDC. -.SS "RPC TRUSTDOM REVOKE DOMAIN" +Establish a trust relationship to a trusting domain\&. Interdomain account must already be created on the remote PDC\&. + .PP Abandon relationship to trusted domain -.SS "RPC TRUSTDOM LIST" + .PP -List all current interdomain trust relationships. +List all current interdomain trust relationships\&. + .SS "RPC ABORTSHUTDOWN" + .PP -Abort the shutdown of a remote server. -.SS "SHUTDOWN [-T TIMEOUT] [-R] [-F] [-C MESSAGE]" +Abort the shutdown of a remote server\&. + +.SS "SHUTDOWN [-t timeout] [-r] [-f] [-C message]" + .PP -Shut down the remote server. +Shut down the remote server\&. + .TP -\fB-r\fR -Reboot after shutdown. +-r +Reboot after shutdown\&. + + .TP -\fB-f\fR -Force shutting down all applications. +-f +Force shutting down all applications\&. + + .TP -\fB-t timeout\fR -Timeout before system will be shut down. An interactive -user of the system can use this time to cancel the shutdown. +-t timeout +Timeout before system will be shut down\&. An interactive user of the system can use this time to cancel the shutdown\&. + + .TP -\fB-C message\fR -Display the specified message on the screen to -announce the shutdown. +-C message +Display the specified message on the screen to announce the shutdown\&. + + .SS "SAMDUMP" + .PP -Print out sam database of remote server. You need -to run this on either a BDC. +Print out sam database of remote server\&. You need to run this on either a BDC\&. + .SS "VAMPIRE" + .PP -Export users, aliases and groups from remote server to -local server. Can only be run an a BDC. +Export users, aliases and groups from remote server to local server\&. Can only be run an a BDC\&. + .SS "GETSID" + .PP -Fetch domain SID and store it in the local \fIsecrets.tdb\fR. +Fetch domain SID and store it in the local \fIsecrets\&.tdb\fR\&. + .SS "ADS LEAVE" + .PP -Make the remote host leave the domain it is part of. +Make the remote host leave the domain it is part of\&. + .SS "ADS STATUS" + .PP -Print out status of machine account of the local machine in ADS. -Prints out quite some debug info. Aimed at developers, regular -users should use \fBNET ADS TESTJOIN\fR. +Print out status of machine account of the local machine in ADS\&. Prints out quite some debug info\&. Aimed at developers, regular users should use \fBNET ADS TESTJOIN\fR\&. + .SS "ADS PRINTER" -.SS "ADS PRINTER INFO [PRINTER] [SERVER]" + .PP -Lookup info for \fIPRINTER\fR on \fISERVER\fR. The printer name defaults to "*", the -server name defaults to the local host. -.SS "ADS PRINTER PUBLISH PRINTER" +Lookup info for \fIPRINTER\fR on \fISERVER\fR\&. The printer name defaults to "*", the server name defaults to the local host\&. + .PP -Publish specified printer using ADS. -.SS "ADS PRINTER REMOVE PRINTER" +Publish specified printer using ADS\&. + .PP -Remove specified printer from ADS directory. +Remove specified printer from ADS directory\&. + .SS "ADS SEARCH EXPRESSION ATTRIBUTES..." + .PP -Perform a raw LDAP search on a ADS server and dump the results. The -expression is a standard LDAP search expression, and the -attributes are a list of LDAP fields to show in the results. +Perform a raw LDAP search on a ADS server and dump the results\&. The expression is a standard LDAP search expression, and the attributes are a list of LDAP fields to show in the results\&. + .PP -Example: \fBnet ads search '(objectCategory=group)' sAMAccountName\fR -.SS "ADS DN DN (ATTRIBUTES)" +Example: \fBnet ads search '(objectCategory=group)' sAMAccountName\fR + +.SS "ADS DN DN (attributes)" + .PP -Perform a raw LDAP search on a ADS server and dump the results. The -DN standard LDAP DN, and the attributes are a list of LDAP fields -to show in the result. +Perform a raw LDAP search on a ADS server and dump the results\&. The DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result\&. + .PP Example: \fBnet ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName\fR + .SS "WORKGROUP" + .PP -Print out workgroup name for specified kerberos realm. +Print out workgroup name for specified kerberos realm\&. + .SS "HELP [COMMAND]" + .PP -Gives usage information for the specified command. +Gives usage information for the specified command\&. + .SH "VERSION" + .PP -This man page is incomplete for version 3.0 of the Samba -suite. +This man page is complete for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The net manpage was written by Jelmer Vernooij. +The net manpage was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8 index b50356b82c..096876bfde 100644 --- a/docs/manpages/nmbd.8 +++ b/docs/manpages/nmbd.8 @@ -1,245 +1,178 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "NMBD" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "NMBD" 8 "" "" "" .SH NAME -nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients -.SH SYNOPSIS +nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients +.SH "SYNOPSIS" -\fBnmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-a\fR ] [ \fB-i\fR ] [ \fB-o\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-d \fR ] [ \fB-H \fR ] [ \fB-l \fR ] [ \fB-n \fR ] [ \fB-p \fR ] [ \fB-s \fR ] +.nf +\fBnmbd\fR [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d ] [-H ] [-l ] [-n ] [-p ] [-s ] + +.fi .SH "DESCRIPTION" + .PP -This program is part of the \fBSamba\fR(7) suite. +This program is part of the \fBSamba\fR(7) suite\&. + .PP -\fBnmbd\fR is a server that understands -and can reply to NetBIOS over IP name service requests, like -those produced by SMB/CIFS clients such as Windows 95/98/ME, -Windows NT, Windows 2000, Windows XP and LanManager clients. It also -participates in the browsing protocols which make up the -Windows "Network Neighborhood" view. +\fBnmbd\fR is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients\&. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view\&. + .PP -SMB/CIFS clients, when they start up, may wish to -locate an SMB/CIFS server. That is, they wish to know what -IP number a specified host is using. +SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server\&. That is, they wish to know what IP number a specified host is using\&. + .PP -Amongst other services, \fBnmbd\fR will -listen for such requests, and if its own NetBIOS name is -specified it will respond with the IP number of the host it -is running on. Its "own NetBIOS name" is by -default the primary DNS name of the host it is running on, -but this can be overridden with the \fB-n\fR -option (see OPTIONS below). Thus \fBnmbd\fR will -reply to broadcast queries for its own name(s). Additional -names for \fBnmbd\fR to respond on can be set -via parameters in the \fBsmb.conf\fR(5) configuration file. +Amongst other services, \fBnmbd\fR will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on\&. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden with the \fB-n\fR option (see OPTIONS below)\&. Thus \fBnmbd\fR will reply to broadcast queries for its own name(s)\&. Additional names for \fBnmbd\fR to respond on can be set via parameters in the \fBsmb.conf\fR(5) configuration file\&. + .PP -\fBnmbd\fR can also be used as a WINS -(Windows Internet Name Server) server. What this basically means -is that it will act as a WINS database server, creating a -database from name registration requests that it receives and -replying to queries from clients for these names. +\fBnmbd\fR can also be used as a WINS (Windows Internet Name Server) server\&. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names\&. + .PP -In addition, \fBnmbd\fR can act as a WINS -proxy, relaying broadcast queries from clients that do -not understand how to talk the WINS protocol to a WINS -server. +In addition, \fBnmbd\fR can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server\&. + .SH "OPTIONS" + .TP -\fB-D\fR -If specified, this parameter causes -\fBnmbd\fR to operate as a daemon. That is, -it detaches itself and runs in the background, fielding -requests on the appropriate port. By default, \fBnmbd\fR -will operate as a daemon if launched from a command shell. -nmbd can also be operated from the \fBinetd\fR -meta-daemon, although this is not recommended. +-D +If specified, this parameter causes \fBnmbd\fR to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. By default, \fBnmbd\fR will operate as a daemon if launched from a command shell\&. nmbd can also be operated from the \fBinetd\fR meta-daemon, although this is not recommended\&. + + .TP -\fB-F\fR -If specified, this parameter causes -the main \fBnmbd\fR process to not daemonize, -i.e. double-fork and disassociate with the terminal. -Child processes are still created as normal to service -each connection request, but the main process does not -exit. This operation mode is suitable for running -\fBnmbd\fR under process supervisors such -as \fBsupervise\fR and \fBsvscan\fR -from Daniel J. Bernstein's \fBdaemontools\fR -package, or the AIX process monitor. +-F +If specified, this parameter causes the main \fBnmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBnmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&. + + .TP -\fB-S\fR -If specified, this parameter causes -\fBnmbd\fR to log to standard output rather -than a file. +-S +If specified, this parameter causes \fBnmbd\fR to log to standard output rather than a file\&. + + .TP -\fB-i\fR -If this parameter is specified it causes the -server to run "interactively", not as a daemon, even if the -server is executed on the command line of a shell. Setting this -parameter negates the implicit daemon mode when run from the -command line. \fBnmbd\fR also logs to standard -output, as if the -S parameter had been -given. +-i +If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&. \fBnmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-H \fR -NetBIOS lmhosts file. The lmhosts -file is a list of NetBIOS names to IP addresses that -is loaded by the nmbd server and used via the name -resolution mechanism \fIname resolve -order\fR described in \fBsmb.conf\fR(5) to resolve any -NetBIOS name queries needed by the server. Note -that the contents of this file are \fBNOT\fR -used by \fBnmbd\fR to answer any name queries. -Adding a line to this file affects name NetBIOS resolution -from this host \fBONLY\fR. - -The default path to this file is compiled into -Samba as part of the build process. Common defaults -are \fI/usr/local/samba/lib/lmhosts\fR, -\fI/usr/samba/lib/lmhosts\fR or -\fI/etc/samba/lmhosts\fR. See the \fBlmhosts\fR(5) man page for details on the contents of this file. +-H +NetBIOS lmhosts file\&. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism \fIname resolve order\fR described in \fBsmb.conf\fR(5) to resolve any NetBIOS name queries needed by the server\&. Note that the contents of this file are \fBNOT\fR used by \fBnmbd\fR to answer any name queries\&. Adding a line to this file affects name NetBIOS resolution from this host \fBONLY\fR\&. + + +The default path to this file is compiled into Samba as part of the build process\&. Common defaults are \fI/usr/local/samba/lib/lmhosts\fR, \fI/usr/samba/lib/lmhosts\fR or \fI/etc/samba/lmhosts\fR\&. See the \fBlmhosts\fR(5) man page for details on the contents of this file\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-p \fR -UDP port number is a positive integer value. -This option changes the default UDP port number (normally 137) -that \fBnmbd\fR responds to name queries on. Don't -use this option unless you are an expert, in which case you -won't need help! +-p +UDP port number is a positive integer value\&. This option changes the default UDP port number (normally 137) that \fBnmbd\fR responds to name queries on\&. Don't use this option unless you are an expert, in which case you won't need help! + + .SH "FILES" + .TP -\fB\fI/etc/inetd.conf\fB\fR -If the server is to be run by the -\fBinetd\fR meta-daemon, this file -must contain suitable startup information for the -meta-daemon. See the install document -for details. +\fI/etc/inetd\&.conf\fR +If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the install document for details\&. + + .TP -\fB\fI/etc/rc\fB\fR -or whatever initialization script your -system uses). - -If running the server as a daemon at startup, -this file will need to contain an appropriate startup -sequence for the server. See the "How to Install and Test SAMBA" document -for details. +\fI/etc/rc\fR +or whatever initialization script your system uses)\&. + + +If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&. + + .TP -\fB\fI/etc/services\fB\fR -If running the server via the -meta-daemon \fBinetd\fR, this file -must contain a mapping of service name (e.g., netbios-ssn) -to service port (e.g., 139) and protocol type (e.g., tcp). -See the "How to Install and Test SAMBA" -document for details. +\fI/etc/services\fR +If running the server via the meta-daemon \fBinetd\fR, this file must contain a mapping of service name (e\&.g\&., netbios-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&. See the "How to Install and Test SAMBA" document for details\&. + + .TP -\fB\fI/usr/local/samba/lib/smb.conf\fB\fR -This is the default location of -the \fBsmb.conf\fR(5) server -configuration file. Other common places that systems -install this file are \fI/usr/samba/lib/smb.conf\fR -and \fI/etc/samba/smb.conf\fR. - -When run as a WINS server (see the -wins support -parameter in the \fBsmb.conf\fR(5) man page), -\fBnmbd\fR -will store the WINS database in the file \fIwins.dat\fR -in the \fIvar/locks\fR directory configured under -wherever Samba was configured to install itself. - -If \fBnmbd\fR is acting as a \fB browse master\fR (see the local master -parameter in the \fBsmb.conf\fR(5) man page, \fBnmbd\fR -will store the browsing database in the file \fIbrowse.dat -\fR in the \fIvar/locks\fR directory -configured under wherever Samba was configured to install itself. +\fI/usr/local/samba/lib/smb\&.conf\fR +This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&. + + +When run as a WINS server (see the \fBwins support\fR parameter in the \fBsmb.conf\fR(5) man page), \fBnmbd\fR will store the WINS database in the file \fIwins\&.dat\fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&. + + +If \fBnmbd\fR is acting as a \fB browse master\fR (see the \fBlocal master\fR parameter in the \fBsmb.conf\fR(5) man page, \fBnmbd\fR will store the browsing database in the file \fIbrowse\&.dat \fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&. + + .SH "SIGNALS" + .PP -To shut down an \fBnmbd\fR process it is recommended -that SIGKILL (-9) \fBNOT\fR be used, except as a last -resort, as this may leave the name database in an inconsistent state. -The correct way to terminate \fBnmbd\fR is to send it -a SIGTERM (-15) signal and wait for it to die on its own. +To shut down an \fBnmbd\fR process it is recommended that SIGKILL (-9) \fBNOT\fR be used, except as a last resort, as this may leave the name database in an inconsistent state\&. The correct way to terminate \fBnmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&. + .PP -\fBnmbd\fR will accept SIGHUP, which will cause -it to dump out its namelists into the file \fInamelist.debug -\fR in the \fI/usr/local/samba/var/locks\fR -directory (or the \fIvar/locks\fR directory configured -under wherever Samba was configured to install itself). This will also -cause \fBnmbd\fR to dump out its server database in -the \fIlog.nmb\fR file. +\fBnmbd\fR will accept SIGHUP, which will cause it to dump out its namelists into the file \fInamelist\&.debug \fR in the \fI/usr/local/samba/var/locks\fR directory (or the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself)\&. This will also cause \fBnmbd\fR to dump out its server database in the \fIlog\&.nmb\fR file\&. + .PP -The debug log level of nmbd may be raised or lowered -using \fBsmbcontrol\fR(1) (SIGUSR[1|2] signals -are no longer used since Samba 2.2). This is to allow -transient problems to be diagnosed, whilst still running -at a normally low log level. +The debug log level of nmbd may be raised or lowered using \fBsmbcontrol\fR(1) (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBinetd\fR(8), \fBsmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet -RFC's \fIrfc1001.txt\fR, \fIrfc1002.txt\fR. -In addition the CIFS (formerly SMB) specification is available -as a link from the Web page -http://samba.org/cifs/ . +\fBinetd\fR(8), \fBsmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's \fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook -XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/nmblookup.1 b/docs/manpages/nmblookup.1 index 6154528a9a..2f16025593 100644 --- a/docs/manpages/nmblookup.1 +++ b/docs/manpages/nmblookup.1 @@ -1,198 +1,185 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "NMBLOOKUP" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "NMBLOOKUP" 1 "" "" "" .SH NAME -nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names -.SH SYNOPSIS +nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names +.SH "SYNOPSIS" -\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B \fR ] [ \fB-U \fR ] [ \fB-d \fR ] [ \fB-s \fR ] [ \fB-i \fR ] [ \fB-T\fR ] [ \fB-f\fR ] \fBname\fR +.nf +\fBnmblookup\fR [-M] [-R] [-S] [-r] [-A] [-h] [-B ] [-U ] [-d ] [-s ] [-i ] + [-T] [-f] {name} +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBnmblookup\fR is used to query NetBIOS names -and map them to IP addresses in a network using NetBIOS over TCP/IP -queries. The options allow the name queries to be directed at a -particular IP broadcast area or to a particular machine. All queries -are done over UDP. +\fBnmblookup\fR is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries\&. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine\&. All queries are done over UDP\&. + .SH "OPTIONS" + +.TP +-M +Searches for a master browser by looking up the NetBIOS name \fIname\fR with a type of \fB0x1d\fR\&. If \fI name\fR is "-" then it does a lookup on the special name \fB__MSBROWSE__\fR\&. Please note that in order to use the name "-", you need to make sure "-" isn't parsed as an argument, e\&.g\&. use : \fBnmblookup -M -- -\fR\&. + + +.TP +-R +Set the recursion desired bit in the packet to do a recursive lookup\&. This is used when sending a name query to a machine running a WINS server and the user wishes to query the names in the WINS server\&. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead\&. See RFC1001, RFC1002 for details\&. + + +.TP +-S +Once the name query has returned an IP address then do a node status query as well\&. A node status query returns the NetBIOS names registered by a host\&. + + +.TP +-r +Try and bind to UDP port 137 to send and receive UDP datagrams\&. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137\&. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and in addition, if the \fBnmbd\fR(8) daemon is running on this machine it also binds to this port\&. + + +.TP +-A +Interpret \fIname\fR as an IP Address and do a node status query on this address\&. + + +.TP +-n +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&. + + +.TP +-i +This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&. + + +.TP +-W|--workgroup=domain +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&. + + +.TP +-O socket options +TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + +.TP +-B +Send the query to the given broadcast address\&. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as either auto-detected or defined in the \fIinterfaces\fR parameter of the \fBsmb.conf\fR(5) file\&. + + +.TP +-U +Do a unicast query to the specified address or host \fIunicast address\fR\&. This option (along with the \fI-R\fR option) is needed to query a WINS server\&. + + .TP -\fB-M\fR -Searches for a master browser by looking -up the NetBIOS name \fIname\fR with a -type of 0x1d. If \fI name\fR is "-" then it does a lookup on the special name -__MSBROWSE__. -.TP -\fB-R\fR -Set the recursion desired bit in the packet -to do a recursive lookup. This is used when sending a name -query to a machine running a WINS server and the user wishes -to query the names in the WINS server. If this bit is unset -the normal (broadcast responding) NetBIOS processing code -on a machine is used instead. See RFC1001, RFC1002 for details. -.TP -\fB-S\fR -Once the name query has returned an IP -address then do a node status query as well. A node status -query returns the NetBIOS names registered by a host. -.TP -\fB-r\fR -Try and bind to UDP port 137 to send and receive UDP -datagrams. The reason for this option is a bug in Windows 95 -where it ignores the source port of the requesting packet -and only replies to UDP port 137. Unfortunately, on most UNIX -systems root privilege is needed to bind to this port, and -in addition, if the \fBnmbd\fR(8) daemon is running on this machine it also binds to this port. -.TP -\fB-A\fR -Interpret \fIname\fR as -an IP Address and do a node status query on this address. -.TP -\fB-n \fR -This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the \fINetBIOS -name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command -line setting will take precedence over settings in -\fBsmb.conf\fR(5). -.TP -\fB-i \fR -This specifies a NetBIOS scope that -\fBnmblookup\fR will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -\fBvery\fR rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with. -.TP -\fB-W|--workgroup=domain\fR -Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). -.TP -\fB-O socket options\fR -TCP socket options to set on the client -socket. See the socket options parameter in -the \fBsmb.conf\fR(5) manual page for the list of valid -options. -.TP -\fB-h|--help\fR -Print a summary of command line options. -.TP -\fB-B \fR -Send the query to the given broadcast address. Without -this option the default behavior of nmblookup is to send the -query to the broadcast address of the network interfaces as -either auto-detected or defined in the \fIinterfaces\fR - parameter of the \fBsmb.conf\fR(5) file. -.TP -\fB-U \fR -Do a unicast query to the specified address or -host \fIunicast address\fR. This option -(along with the \fI-R\fR option) is needed to -query a WINS server. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. -.TP -\fB-T\fR -This causes any IP addresses found in the -lookup to be looked up via a reverse DNS lookup into a -DNS name, and printed out before each - -\fBIP address .... NetBIOS name\fR - -pair that is the normal output. -.TP -\fB-f\fR -Show which flags apply to the name that has been looked up. Possible -answers are zero or more of: Response, Authoritative, -Truncated, Recursion_Desired, Recursion_Available, Broadcast. -.TP -\fBname\fR -This is the NetBIOS name being queried. Depending -upon the previous options this may be a NetBIOS name or IP address. -If a NetBIOS name then the different name types may be specified -by appending '#' to the name. This name may also be -\&'*', which will return all registered names within a broadcast -area. +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + +.TP +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + +.TP +-T +This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a DNS name, and printed out before each + + +\fBIP address \&.\&.\&.\&. NetBIOS name\fR + + +pair that is the normal output\&. + + +.TP +-f +Show which flags apply to the name that has been looked up\&. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast\&. + + +.TP +name +This is the NetBIOS name being queried\&. Depending upon the previous options this may be a NetBIOS name or IP address\&. If a NetBIOS name then the different name types may be specified by appending '#' to the name\&. This name may also be '*', which will return all registered names within a broadcast area\&. + + .SH "EXAMPLES" + .PP -\fBnmblookup\fR can be used to query -a WINS server (in the same way \fBnslookup\fR is -used to query DNS servers). To query a WINS server, \fBnmblookup\fR -must be called like this: +\fBnmblookup\fR can be used to query a WINS server (in the same way \fBnslookup\fR is used to query DNS servers)\&. To query a WINS server, \fBnmblookup\fR must be called like this: + .PP \fBnmblookup -U server -R 'name'\fR + .PP For example, running : + .PP \fBnmblookup -U samba.org -R 'IRIX#1B'\fR + .PP -would query the WINS server samba.org for the domain -master browser (1B name type) for the IRIX workgroup. +would query the WINS server samba\&.org for the domain master browser (1B name type) for the IRIX workgroup\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBnmbd\fR(8), \fBsamba\fR(7), and \fBsmb.conf\fR(5). +\fBnmbd\fR(8), \fBsamba\fR(7), and \fBsmb.conf\fR(5)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook -XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/ntlm_auth.1 b/docs/manpages/ntlm_auth.1 index 8cc6061ebb..082d9422c8 100644 --- a/docs/manpages/ntlm_auth.1 +++ b/docs/manpages/ntlm_auth.1 @@ -1,109 +1,135 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "NTLM_AUTH" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "NTLM_AUTH" 1 "" "" "" .SH NAME ntlm_auth \- tool to allow external access to Winbind's NTLM authentication function -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBntlm_auth\fR [ \fB-d debuglevel\fR ] [ \fB-l logfile\fR ] [ \fB-s \fR ] +.nf +\fBntlm_auth\fR [-d debuglevel] [-l logfile] [-s ] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBntlm_auth\fR is a helper utility that authenticates -users using NT/LM authentication. It returns 0 if the users is authenticated -successfully and 1 if access was denied. ntlm_auth uses winbind to access -the user and authentication data for a domain. This utility -is only to be used by other programs (currently squid). +\fBntlm_auth\fR is a helper utility that authenticates users using NT/LM authentication\&. It returns 0 if the users is authenticated successfully and 1 if access was denied\&. ntlm_auth uses winbind to access the user and authentication data for a domain\&. This utility is only to be used by other programs (currently squid)\&. + .SH "OPTIONS" + .TP -\fB--helper-protocol=PROTO\fR +--helper-protocol=PROTO Operate as a stdio-based helper + + .TP -\fB--username=USERNAME\fR +--username=USERNAME Specify username of user to authenticate + + .TP -\fB--domain=DOMAIN\fR +--domain=DOMAIN Specify domain of user to authenticate + + .TP -\fB--workstation=WORKSTATION\fR +--workstation=WORKSTATION Specify the workstation the user authenticated from + + .TP -\fB--challenge=STRING\fR +--challenge=STRING challenge (HEX encoded) + + .TP -\fB--lm-response=RESPONSE\fR +--lm-response=RESPONSE LM Response to the challenge (HEX encoded) + + .TP -\fB--nt-response=RESPONSE\fR +--nt-response=RESPONSE NT or NTLMv2 Response to the challenge (HEX encoded) + + .TP -\fB--password=PASSWORD\fR +--password=PASSWORD User's plaintext password + + .TP -\fB--request-lm-key\fR +--request-lm-key Retreive LM session key + + .TP -\fB--request-nt-key\fR +--request-nt-key Request NT key + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The ntlm_auth manpage was written by Jelmer Vernooij. +The ntlm_auth manpage was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/pdbedit.8 b/docs/manpages/pdbedit.8 index 02046dc58e..51dcf44bf0 100644 --- a/docs/manpages/pdbedit.8 +++ b/docs/manpages/pdbedit.8 @@ -1,56 +1,75 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "PDBEDIT" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "PDBEDIT" 8 "" "" "" .SH NAME pdbedit \- manage the SAM database -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBpdbedit\fR [ \fB-l\fR ] [ \fB-v\fR ] [ \fB-w\fR ] [ \fB-u username\fR ] [ \fB-f fullname\fR ] [ \fB-h homedir\fR ] [ \fB-D drive\fR ] [ \fB-S script\fR ] [ \fB-p profile\fR ] [ \fB-a\fR ] [ \fB-m\fR ] [ \fB-x\fR ] [ \fB-i passdb-backend\fR ] [ \fB-e passdb-backend\fR ] [ \fB-g\fR ] [ \fB-b passdb-backend\fR ] [ \fB-g\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-P account-policy\fR ] [ \fB-C value\fR ] +.nf +\fBpdbedit\fR [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S + script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] + [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] + [-C value] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The pdbedit program is used to manage the users accounts -stored in the sam database and can only be run by root. +The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root\&. + .PP -The pdbedit tool uses the passdb modular interface and is -independent from the kind of users database used (currently there -are smbpasswd, ldap, nis+ and tdb based and more can be added -without changing the tool). +The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added without changing the tool)\&. + .PP -There are five main ways to use pdbedit: adding a user account, -removing a user account, modifing a user account, listing user -accounts, importing users accounts. +There are five main ways to use pdbedit: adding a user account, removing a user account, modifing a user account, listing user accounts, importing users accounts\&. + .SH "OPTIONS" + .TP -\fB-l\fR -This option lists all the user accounts -present in the users database. -This option prints a list of user/uid pairs separated by -the ':' character. +-l +This option lists all the user accounts present in the users database\&. This option prints a list of user/uid pairs separated by the ':' character\&. + Example: \fBpdbedit -l\fR .nf + sorce:500:Simo Sorce samba:45:Test User .fi + + .TP -\fB-v\fR -This option enables the verbose listing format. -It causes pdbedit to list the users in the database, printing -out the account fields in a descriptive format. +-v +This option enables the verbose listing format\&. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format\&. + Example: \fBpdbedit -l -v\fR .nf + --------------- username: sorce user ID/Group: 500/500 @@ -58,7 +77,7 @@ user RID/GRID: 2000/2001 Full Name: Simo Sorce Home Directory: \\\\BERSERKER\\sorce HomeDir Drive: H: -Logon Script: \\\\BERSERKER\\netlogon\\sorce.bat +Logon Script: \\\\BERSERKER\\netlogon\\sorce\&.bat Profile Path: \\\\BERSERKER\\profile --------------- username: samba @@ -70,222 +89,225 @@ HomeDir Drive: Logon Script: Profile Path: \\\\BERSERKER\\profile .fi + + .TP -\fB-w\fR -This option sets the "smbpasswd" listing format. -It will make pdbedit list the users in the database, printing -out the account fields in a format compatible with the -\fIsmbpasswd\fR file format. (see the -\fBsmbpasswd\fR(5) for details) +-w +This option sets the "smbpasswd" listing format\&. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the \fIsmbpasswd\fR file format\&. (see the \fBsmbpasswd\fR(5) for details) + Example: \fBpdbedit -l -w\fR -.nf + sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000: samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D: -.fi + .TP -\fB-u username\fR -This option specifies the username to be -used for the operation requested (listing, adding, removing). -It is \fBrequired\fR in add, remove and modify -operations and \fBoptional\fR in list -operations. +-u username +This option specifies the username to be used for the operation requested (listing, adding, removing)\&. It is \fBrequired\fR in add, remove and modify operations and \fBoptional\fR in list operations\&. + + .TP -\fB-f fullname\fR -This option can be used while adding or -modifing a user account. It will specify the user's full -name. +-f fullname +This option can be used while adding or modifing a user account\&. It will specify the user's full name\&. + Example: \fB-f "Simo Sorce"\fR + + .TP -\fB-h homedir\fR -This option can be used while adding or -modifing a user account. It will specify the user's home -directory network path. +-h homedir +This option can be used while adding or modifing a user account\&. It will specify the user's home directory network path\&. + + +Example: \fB-h "\\\\BERSERKER\\sorce"\fR + -Example: \fB-h "\\\\\\\\BERSERKER\\\\sorce"\fR .TP -\fB-D drive\fR -This option can be used while adding or -modifing a user account. It will specify the windows drive -letter to be used to map the home directory. +-D drive +This option can be used while adding or modifing a user account\&. It will specify the windows drive letter to be used to map the home directory\&. + Example: \fB-d "H:"\fR + + .TP -\fB-S script\fR -This option can be used while adding or -modifing a user account. It will specify the user's logon -script path. +-S script +This option can be used while adding or modifing a user account\&. It will specify the user's logon script path\&. + + +Example: \fB-s "\\\\BERSERKER\\netlogon\\sorce.bat"\fR + -Example: \fB-s "\\\\\\\\BERSERKER\\\\netlogon\\\\sorce.bat"\fR .TP -\fB-p profile\fR -This option can be used while adding or -modifing a user account. It will specify the user's profile -directory. +-p profile +This option can be used while adding or modifing a user account\&. It will specify the user's profile directory\&. + + +Example: \fB-p "\\\\BERSERKER\\netlogon"\fR + -Example: \fB-p "\\\\\\\\BERSERKER\\\\netlogon"\fR .TP -\fB-a\fR -This option is used to add a user into the -database. This command needs a user name specified with -the -u switch. When adding a new user, pdbedit will also -ask for the password to be used. +-a +This option is used to add a user into the database\&. This command needs a user name specified with the -u switch\&. When adding a new user, pdbedit will also ask for the password to be used\&. -Example: \fBpdbedit -a -u sorce\fR +Example: \fBpdbedit -a -u sorce\fR .nf new password: retype new password .fi + + + .TP -\fB-m\fR -This option may only be used in conjunction -with the \fI-a\fR option. It will make -pdbedit to add a machine trust account instead of a user -account (-u username will provide the machine name). +-m +This option may only be used in conjunction with the \fI-a\fR option\&. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name)\&. + Example: \fBpdbedit -a -m -u w2k-wks\fR + + .TP -\fB-x\fR -This option causes pdbedit to delete an account -from the database. It needs a username specified with the --u switch. +-x +This option causes pdbedit to delete an account from the database\&. It needs a username specified with the -u switch\&. + Example: \fBpdbedit -x -u bob\fR + + .TP -\fB-i passdb-backend\fR -Use a different passdb backend to retrieve users -than the one specified in smb.conf. Can be used to import data into -your local user database. +-i passdb-backend +Use a different passdb backend to retrieve users than the one specified in smb\&.conf\&. Can be used to import data into your local user database\&. + + +This option will ease migration from one passdb backend to another\&. + + +Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old \fR -This option will ease migration from one passdb backend to -another. -Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old -\fR .TP -\fB-e passdb-backend\fR -Exports all currently available users to the -specified password database backend. +-e passdb-backend +Exports all currently available users to the specified password database backend\&. + + +This option will ease migration from one passdb backend to another and will ease backing up\&. -This option will ease migration from one passdb backend to -another and will ease backing up. Example: \fBpdbedit -e smbpasswd:/root/samba-users.backup\fR + + .TP -\fB-g\fR -If you specify \fI-g\fR, -then \fI-i in-backend -e out-backend\fR -applies to the group mapping instead of the user database. +-g +If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&. + + +This option will ease migration from one passdb backend to another and will ease backing up\&. + -This option will ease migration from one passdb backend to -another and will ease backing up. .TP -\fB-g\fR -If you specify \fI-g\fR, -then \fI-i in-backend -e out-backend\fR -applies to the group mapping instead of the user database. +-g +If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&. + + +This option will ease migration from one passdb backend to another and will ease backing up\&. + -This option will ease migration from one passdb backend to -another and will ease backing up. .TP -\fB-b passdb-backend\fR -Use a different default passdb backend. +-b passdb-backend +Use a different default passdb backend\&. + Example: \fBpdbedit -b xml:/root/pdb-backup.xml -l\fR + + .TP -\fB-P account-policy\fR +-P account-policy Display an account policy -Valid policies are: minimum password age, reset count minutes, disconnect time, -user must logon to change password, password history, lockout duration, min password length, -maximum password age and bad lockout attempt. + +Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, maximum password age and bad lockout attempt\&. + Example: \fBpdbedit -P "bad lockout attempt"\fR .nf + account policy value for bad lockout attempt is 0 .fi + + .TP -\fB-C account-policy-value\fR -Sets an account policy to a specified value. -This option may only be used in conjunction -with the \fI-P\fR option. +-C account-policy-value +Sets an account policy to a specified value\&. This option may only be used in conjunction with the \fI-P\fR option\&. + Example: \fBpdbedit -P "bad lockout attempt" -C 3\fR .nf + account policy value for bad lockout attempt was 0 account policy value for bad lockout attempt is now 3 .fi + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .SH "NOTES" + .PP -This command may be used only by root. +This command may be used only by root\&. + .SH "VERSION" + .PP -This man page is correct for version 2.2 of -the Samba suite. +This man page is correct for version 2\&.2 of the Samba suite\&. + .SH "SEE ALSO" + .PP \fBsmbpasswd\fR(5), \fBsamba\fR(7) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook -XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/profiles.1 b/docs/manpages/profiles.1 index 2aef96aa03..1c53c74a03 100644 --- a/docs/manpages/profiles.1 +++ b/docs/manpages/profiles.1 @@ -1,45 +1,71 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "PROFILES" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "PROFILES" 1 "" "" "" .SH NAME profiles \- A utility to report and change SIDs in registry files -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBprofiles\fR [ \fB-v\fR ] [ \fB-c SID\fR ] [ \fB-n SID\fR ] \fBfile\fR +.nf +\fBprofiles\fR [-v] [-c SID] [-n SID] {file} +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBprofiles\fR is a utility that -reports and changes SIDs in windows registry files. It currently only -supports NT. +\fBprofiles\fR is a utility that reports and changes SIDs in windows registry files\&. It currently only supports NT\&. + .SH "OPTIONS" + .TP -\fBfile\fR -Registry file to view or edit. +file +Registry file to view or edit\&. + + .TP -\fB-v,--verbose\fR -Increases verbosity of messages. +-v,--verbose +Increases verbosity of messages\&. + + .TP -\fB-c SID1 -n SID2\fR -Change all occurences of SID1 in \fIfile\fR by SID2. +-c SID1 -n SID2 +Change all occurences of SID1 in \fIfile\fR by SID2\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The profiles man page was written by Jelmer Vernooij. +The profiles man page was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/rpcclient.1 b/docs/manpages/rpcclient.1 index e20b9a8029..7655d6c312 100644 --- a/docs/manpages/rpcclient.1 +++ b/docs/manpages/rpcclient.1 @@ -1,330 +1,403 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "RPCCLIENT" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "RPCCLIENT" 1 "" "" "" .SH NAME -rpcclient \- tool for executing client side MS-RPC functions -.SH SYNOPSIS +rpcclient \- tool for executing client side MS-RPC functions +.SH "SYNOPSIS" -\fBrpcclient\fR [ \fB-A authfile\fR ] [ \fB-c \fR ] [ \fB-d debuglevel\fR ] [ \fB-h\fR ] [ \fB-l logfile\fR ] [ \fB-N\fR ] [ \fB-s \fR ] [ \fB-U username[%password]\fR ] [ \fB-W workgroup\fR ] [ \fB-N\fR ] [ \fB-I destinationIP\fR ] \fBserver\fR +.nf +\fBrpcclient\fR [-A authfile] [-c ] [-d debuglevel] [-h] [-l logfile] + [-N] [-s ] [-U username[%password]] [-W workgroup] + [-N] [-I destinationIP] {server} +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBrpcclient\fR is a utility initially developed -to test MS-RPC functionality in Samba itself. It has undergone -several stages of development and stability. Many system administrators -have now written scripts around it to manage Windows NT clients from -their UNIX workstation. +\fBrpcclient\fR is a utility initially developed to test MS-RPC functionality in Samba itself\&. It has undergone several stages of development and stability\&. Many system administrators have now written scripts around it to manage Windows NT clients from their UNIX workstation\&. + .SH "OPTIONS" + +.TP +server +NetBIOS name of Server to which to connect\&. The server can be any SMB/CIFS server\&. The name is resolved using the \fIname resolve order\fR line from \fBsmb.conf\fR(5)\&. + + +.TP +-c|--command='command string' +execute semicolon separated commands (listed below)) + + +.TP +-I IP-address +\fIIP address\fR is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&. + + +Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the \fIname resolve order\fR parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&. + + +There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&. + + .TP -\fBserver\fR -NetBIOS name of Server to which to connect. -The server can be any SMB/CIFS server. The name is -resolved using the \fIname resolve order\fR line from \fBsmb.conf\fR(5). -.TP -\fB-c|--command='command string'\fR -execute semicolon separated commands (listed -below)) -.TP -\fB-I IP-address\fR -\fIIP address\fR is the address of the server to connect to. -It should be specified in standard "a.b.c.d" notation. - -Normally the client would attempt to locate a named -SMB/CIFS server by looking it up via the NetBIOS name resolution -mechanism described above in the \fIname resolve order\fR -parameter above. Using this parameter will force the client -to assume that the server is on the machine with the specified IP -address and the NetBIOS name component of the resource being -connected to will be ignored. - -There is no default for this parameter. If not supplied, -it will be determined automatically by the client as described -above. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. -.TP -\fB-N\fR -If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. - -Unless a password is specified on the command line or -this parameter is specified, the client will request a -password. -.TP -\fB-k\fR -Try to authenticate with kerberos. Only useful in -an Active Directory environment. -.TP -\fB-A|--authfile=filename\fR -This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + +.TP +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + +.TP +-N +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&. + + +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&. + + +.TP +-k +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&. + + +.TP +-A|--authfile=filename +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is .nf + username = password = domain = .fi -Make certain that the permissions on the file restrict -access from unwanted users. -.TP -\fB-U|--user=username[%password]\fR -Sets the SMB username or username and password. - -If %password is not specified, the user will be prompted. The -client will first check the \fBUSER\fR environment variable, then the -\fBLOGNAME\fR variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username GUEST is used. - -A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -\fI-A\fR for more details. - -Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the \fBps\fR command. To be safe always allow -\fBrpcclient\fR to prompt for a password and type -it in directly. -.TP -\fB-n \fR -This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the \fINetBIOS -name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command -line setting will take precedence over settings in -\fBsmb.conf\fR(5). -.TP -\fB-i \fR -This specifies a NetBIOS scope that -\fBnmblookup\fR will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -\fBvery\fR rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with. -.TP -\fB-W|--workgroup=domain\fR -Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). -.TP -\fB-O socket options\fR -TCP socket options to set on the client -socket. See the socket options parameter in -the \fBsmb.conf\fR(5) manual page for the list of valid -options. -.TP -\fB-h|--help\fR -Print a summary of command line options. + +Make certain that the permissions on the file restrict access from unwanted users\&. + + +.TP +-U|--user=username[%password] +Sets the SMB username or username and password\&. + + +If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&. + + +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&. + + +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&. + + +.TP +-n +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&. + + +.TP +-i +This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&. + + +.TP +-W|--workgroup=domain +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&. + + +.TP +-O socket options +TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + .SH "COMMANDS" + .SS "LSARPC" + .TP -\fBlsaquery\fR +lsaquery Query info policy + + .TP -\fBlookupsids\fR -Resolve a list -of SIDs to usernames. +lookupsids +Resolve a list of SIDs to usernames\&. + + .TP -\fBlookupnames\fR -Resolve a list -of usernames to SIDs. +lookupnames +Resolve a list of usernames to SIDs\&. + + .TP -\fBenumtrusts\fR +enumtrusts Enumerate trusted domains + + .TP -\fBenumprivs\fR +enumprivs Enumerate privileges + + .TP -\fBgetdispname\fR +getdispname Get the privilege name + + .TP -\fBlsaenumsid\fR +lsaenumsid Enumerate the LSA SIDS + + .TP -\fBlsaenumprivsaccount\fR +lsaenumprivsaccount Enumerate the privileges of an SID + + .TP -\fBlsaenumacctrights\fR +lsaenumacctrights Enumerate the rights of an SID + + .TP -\fBlsaenumacctwithright\fR +lsaenumacctwithright Enumerate accounts with a right + + .TP -\fBlsaaddacctrights\fR +lsaaddacctrights Add rights to an account + + .TP -\fBlsaremoveacctrights\fR +lsaremoveacctrights Remove rights from an account + + .TP -\fBlsalookupprivvalue\fR +lsalookupprivvalue Get a privilege value given its name + + .TP -\fBlsaquerysecobj\fR +lsaquerysecobj Query LSA security object + + .SS "LSARPC-DS" + .TP -\fBdsroledominfo\fR +dsroledominfo Get Primary Domain Information + + .PP + + .PP \fBDFS\fR + .TP -\fBdfsexist\fR +dfsexist Query DFS support + + .TP -\fBdfsadd\fR +dfsadd Add a DFS share + + .TP -\fBdfsremove\fR +dfsremove Remove a DFS share + + .TP -\fBdfsgetinfo\fR +dfsgetinfo Query DFS share info + + .TP -\fBdfsenum\fR +dfsenum Enumerate dfs shares + + .SS "REG" + .TP -\fBshutdown\fR +shutdown Remote Shutdown + + .TP -\fBabortshutdown\fR +abortshutdown Abort Shutdown + + .SS "SRVSVC" + .TP -\fBsrvinfo\fR +srvinfo Server query info + + .TP -\fBnetshareenum\fR +netshareenum Enumerate shares + + .TP -\fBnetfileenum\fR +netfileenum Enumerate open files + + .TP -\fBnetremotetod\fR +netremotetod Fetch remote time of day + + .SS "SAMR" + .TP -\fBqueryuser\fR +queryuser Query user info + + .TP -\fBquerygroup\fR +querygroup Query group info + + .TP -\fBqueryusergroups\fR +queryusergroups Query user groups + + .TP -\fBquerygroupmem\fR +querygroupmem Query group membership + + .TP -\fBqueryaliasmem\fR +queryaliasmem Query alias membership + + .TP -\fBquerydispinfo\fR +querydispinfo Query display info + + .TP -\fBquerydominfo\fR +querydominfo Query domain info + + .TP -\fBenumdomusers\fR +enumdomusers Enumerate domain users + + .TP -\fBenumdomgroups\fR +enumdomgroups Enumerate domain groups + + .TP -\fBenumalsgroups\fR +enumalsgroups Enumerate alias groups + + .TP -\fBcreatedomuser\fR +createdomuser Create domain user + + .TP -\fBsamlookupnames\fR +samlookupnames Look up names + + .TP -\fBsamlookuprids\fR +samlookuprids Look up names + + .TP -\fBdeletedomuser\fR +deletedomuser Delete domain user + + .TP -\fBsamquerysecobj\fR +samquerysecobj Query SAMR security object + + .TP -\fBgetdompwinfo\fR +getdompwinfo Retrieve domain password info + + .TP -\fBlookupdomain\fR +lookupdomain Look up domain + + .SS "SPOOLSS" + .TP -\fBadddriver \fR -Execute an AddPrinterDriver() RPC to install the printer driver -information on the server. Note that the driver files should -already exist in the directory returned by -\fBgetdriverdir\fR. Possible values for -\fIarch\fR are the same as those for -the \fBgetdriverdir\fR command. -The \fIconfig\fR parameter is defined as -follows: +adddriver +Execute an AddPrinterDriver() RPC to install the printer driver information on the server\&. Note that the driver files should already exist in the directory returned by \fBgetdriverdir\fR\&. Possible values for \fIarch\fR are the same as those for the \fBgetdriverdir\fR command\&. The \fIconfig\fR parameter is defined as follows: .nf + Long Printer Name:\\ Driver File Name:\\ Data File Name:\\ @@ -335,193 +408,209 @@ Default Data Type:\\ Comma Separated list of Files .fi -Any empty fields should be enter as the string "NULL". - -Samba does not need to support the concept of Print Monitors -since these only apply to local printers whose driver can make -use of a bi-directional link for communication. This field should -be "NULL". On a remote NT print server, the Print Monitor for a -driver must already be installed prior to adding the driver or -else the RPC will fail. -.TP -\fBaddprinter \fR -Add a printer on the remote server. This printer -will be automatically shared. Be aware that the printer driver -must already be installed on the server (see \fBadddriver\fR) -and the \fIport\fRmust be a valid port name (see -\fBenumports\fR. -.TP -\fBdeldriver\fR -Delete the -specified printer driver for all architectures. This -does not delete the actual driver files from the server, -only the entry from the server's list of drivers. -.TP -\fBenumdata\fR -Enumerate all -printer setting data stored on the server. On Windows NT clients, -these values are stored in the registry, while Samba servers -store them in the printers TDB. This command corresponds -to the MS Platform SDK GetPrinterData() function (* This -command is currently unimplemented). -.TP -\fBenumdataex\fR + +Any empty fields should be enter as the string "NULL"\&. + + +Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi-directional link for communication\&. This field should be "NULL"\&. On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail\&. + + +.TP +addprinter +Add a printer on the remote server\&. This printer will be automatically shared\&. Be aware that the printer driver must already be installed on the server (see \fBadddriver\fR) and the \fIport\fRmust be a valid port name (see \fBenumports\fR\&. + + +.TP +deldriver +Delete the specified printer driver for all architectures\&. This does not delete the actual driver files from the server, only the entry from the server's list of drivers\&. + + +.TP +enumdata +Enumerate all printer setting data stored on the server\&. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB\&. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented)\&. + + +.TP +enumdataex Enumerate printer data for a key + + .TP -\fBenumjobs \fR -List the jobs and status of a given printer. -This command corresponds to the MS Platform SDK EnumJobs() -function +enumjobs +List the jobs and status of a given printer\&. This command corresponds to the MS Platform SDK EnumJobs() function + + .TP -\fBenumkey\fR +enumkey Enumerate printer keys + + +.TP +enumports [level] +Executes an EnumPorts() call using the specified info level\&. Currently only info levels 1 and 2 are supported\&. + + +.TP +enumdrivers [level] +Execute an EnumPrinterDrivers() call\&. This lists the various installed printer drivers for all architectures\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 1, 2, and 3\&. + + +.TP +enumprinters [level] +Execute an EnumPrinters() call\&. This lists the various installed and share printers\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 0, 1, and 2\&. + + +.TP +getdata +Retrieve the data for a given printer setting\&. See the \fBenumdata\fR command for more information\&. This command corresponds to the GetPrinterData() MS Platform SDK function\&. + + .TP -\fBenumports [level]\fR -Executes an EnumPorts() call using the specified -info level. Currently only info levels 1 and 2 are supported. -.TP -\fBenumdrivers [level]\fR -Execute an EnumPrinterDrivers() call. This lists the various installed -printer drivers for all architectures. Refer to the MS Platform SDK -documentation for more details of the various flags and calling -options. Currently supported info levels are 1, 2, and 3. -.TP -\fBenumprinters [level]\fR -Execute an EnumPrinters() call. This lists the various installed -and share printers. Refer to the MS Platform SDK documentation for -more details of the various flags and calling options. Currently -supported info levels are 0, 1, and 2. -.TP -\fBgetdata \fR -Retrieve the data for a given printer setting. See -the \fBenumdata\fR command for more information. -This command corresponds to the GetPrinterData() MS Platform -SDK function. -.TP -\fBgetdataex\fR +getdataex Get printer driver data with keyname + + .TP -\fBgetdriver \fR -Retrieve the printer driver information (such as driver file, -config file, dependent files, etc...) for -the given printer. This command corresponds to the GetPrinterDriver() -MS Platform SDK function. Currently info level 1, 2, and 3 are supported. -.TP -\fBgetdriverdir \fR -Execute a GetPrinterDriverDirectory() -RPC to retrieve the SMB share name and subdirectory for -storing printer driver files for a given architecture. Possible -values for \fIarch\fR are "Windows 4.0" -(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows -Alpha_AXP", and "Windows NT R4000". -.TP -\fBgetprinter \fR -Retrieve the current printer information. This command -corresponds to the GetPrinter() MS Platform SDK function. -.TP -\fBgetprintprocdir\fR +getdriver +Retrieve the printer driver information (such as driver file, config file, dependent files, etc\&.\&.\&.) for the given printer\&. This command corresponds to the GetPrinterDriver() MS Platform SDK function\&. Currently info level 1, 2, and 3 are supported\&. + + +.TP +getdriverdir +Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture\&. Possible values for \fIarch\fR are "Windows 4\&.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000"\&. + + +.TP +getprinter +Retrieve the current printer information\&. This command corresponds to the GetPrinter() MS Platform SDK function\&. + + +.TP +getprintprocdir Get print processor directory + + .TP -\fBopenprinter \fR -Execute an OpenPrinterEx() and ClosePrinter() RPC -against a given printer. +openprinter +Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\&. + + .TP -\fBsetdriver \fR -Execute a SetPrinter() command to update the printer driver -associated with an installed printer. The printer driver must -already be correctly installed on the print server. +setdriver +Execute a SetPrinter() command to update the printer driver associated with an installed printer\&. The printer driver must already be correctly installed on the print server\&. + + +See also the \fBenumprinters\fR and \fBenumdrivers\fR commands for obtaining a list of of installed printers and drivers\&. + -See also the \fBenumprinters\fR and -\fBenumdrivers\fR commands for obtaining a list of -of installed printers and drivers. .TP -\fBaddform\fR +addform Add form + + .TP -\fBsetform\fR +setform Set form + + .TP -\fBgetform\fR +getform Get form + + .TP -\fBdeleteform\fR +deleteform Delete form + + .TP -\fBenumforms\fR +enumforms Enumerate form + + .TP -\fBsetprinter\fR +setprinter Set printer comment + + .TP -\fBsetprinterdata\fR +setprinterdata Set REG_SZ printer data + + .TP -\fBrffpcnex\fR +rffpcnex Rffpcnex test + + .SS "NETLOGON" + .TP -\fBlogonctrl2\fR +logonctrl2 Logon Control 2 + + .TP -\fBlogonctrl\fR +logonctrl Logon Control + + .TP -\fBsamsync\fR +samsync Sam Synchronisation + + .TP -\fBsamdeltas\fR +samdeltas Query Sam Deltas + + .TP -\fBsamlogon\fR +samlogon Sam Logon + + .SS "GENERAL COMMANDS" + .TP -\fBdebuglevel\fR -Set the current -debug level used to log information. +debuglevel +Set the current debug level used to log information\&. + + .TP -\fBhelp (?)\fR -Print a listing of all -known commands or extended help on a particular command. +help (?) +Print a listing of all known commands or extended help on a particular command\&. + + .TP -\fBquit (exit)\fR -Exit \fBrpcclient -\fR. +quit (exit) +Exit \fBrpcclient \fR\&. + + .SH "BUGS" + .PP -\fBrpcclient\fR is designed as a developer testing tool -and may not be robust in certain areas (such as command line parsing). -It has been known to generate a core dump upon failures when invalid -parameters where passed to the interpreter. +\fBrpcclient\fR is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing)\&. It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter\&. + .PP From Luke Leighton's original rpcclient man page: + .PP -\fBWARNING!\fR The MSRPC over SMB code has -been developed from examining Network traces. No documentation is -available from the original creators (Microsoft) on how MSRPC over -SMB works, or how the individual MSRPC services work. Microsoft's -implementation of these services has been demonstrated (and reported) -to be... a bit flaky in places. +\fBWARNING!\fR The MSRPC over SMB code has been developed from examining Network traces\&. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work\&. Microsoft's implementation of these services has been demonstrated (and reported) to be\&.\&.\&. a bit flaky in places\&. + .PP -The development of Samba's implementation is also a bit rough, -and as more of the services are understood, it can even result in -versions of \fBsmbd\fR(8) and \fBrpcclient\fR(1) that are incompatible for some commands or services. Additionally, -the developers are sending reports to Microsoft, and problems found -or reported to Microsoft are fixed in Service Packs, which may -result in incompatibilities. +The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in versions of \fBsmbd\fR(8) and \fBrpcclient\fR(1) that are incompatible for some commands or services\&. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original rpcclient man page was written by Matthew -Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. -The conversion to DocBook for Samba 2.2 was done by Gerald -Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was -done by Alexander Bokovoy. +The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5 index 7560ea57f8..74716bf1bd 100644 --- a/docs/manpages/smb.conf.5 +++ b/docs/manpages/smb.conf.5 @@ -1,7369 +1,6520 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMB.CONF" "5" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMB.CONF" 5 "" "" "" .SH NAME smb.conf \- The configuration file for the Samba suite .SH "SYNOPSIS" + .PP -The \fIsmb.conf\fR file is a configuration -file for the Samba suite. \fIsmb.conf\fR contains -runtime configuration information for the Samba programs. The \fIsmb.conf\fR file -is designed to be configured and administered by the \fBswat\fR(8) program. The complete -description of the file format and possible parameters held within -are here for reference purposes. +The \fIsmb\&.conf\fR file is a configuration file for the Samba suite\&. \fIsmb\&.conf\fR contains runtime configuration information for the Samba programs\&. The \fIsmb\&.conf\fR file is designed to be configured and administered by the \fBswat\fR(8) program\&. The complete description of the file format and possible parameters held within are here for reference purposes\&. + .SH "FILE FORMAT" + .PP -The file consists of sections and parameters. A section -begins with the name of the section in square brackets and continues -until the next section begins. Sections contain parameters of the -form +The file consists of sections and parameters\&. A section begins with the name of the section in square brackets and continues until the next section begins\&. Sections contain parameters of the form + .PP -\fIname\fR = \fIvalue -\fR +\fIname\fR = \fIvalue \fR + .PP -The file is line-based - that is, each newline-terminated -line represents either a comment, a section name or a parameter. +The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter\&. + .PP -Section and parameter names are not case sensitive. +Section and parameter names are not case sensitive\&. + .PP -Only the first equals sign in a parameter is significant. -Whitespace before or after the first equals sign is discarded. -Leading, trailing and internal whitespace in section and parameter -names is irrelevant. Leading and trailing whitespace in a parameter -value is discarded. Internal whitespace within a parameter value -is retained verbatim. +Only the first equals sign in a parameter is significant\&. Whitespace before or after the first equals sign is discarded\&. Leading, trailing and internal whitespace in section and parameter names is irrelevant\&. Leading and trailing whitespace in a parameter value is discarded\&. Internal whitespace within a parameter value is retained verbatim\&. + .PP -Any line beginning with a semicolon (';') or a hash ('#') -character is ignored, as are lines containing only whitespace. +Any line beginning with a semicolon (';') or a hash ('#') character is ignored, as are lines containing only whitespace\&. + .PP -Any line ending in a '\\' is continued -on the next line in the customary UNIX fashion. +Any line ending in a '\\' is continued on the next line in the customary UNIX fashion\&. + .PP -The values following the equals sign in parameters are all -either a string (no quotes needed) or a boolean, which may be given -as yes/no, 0/1 or true/false. Case is not significant in boolean -values, but is preserved in string values. Some items such as -create modes are numeric. +The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or true/false\&. Case is not significant in boolean values, but is preserved in string values\&. Some items such as create modes are numeric\&. + .SH "SECTION DESCRIPTIONS" + .PP -Each section in the configuration file (except for the -[global] section) describes a shared resource (known -as a "share"). The section name is the name of the -shared resource and the parameters within the section define -the shares attributes. -.PP -There are three special sections, [global], -[homes] and [printers], which are -described under \fBspecial sections\fR. The -following notes apply to ordinary section descriptions. +Each section in the configuration file (except for the [global] section) describes a shared resource (known as a "share")\&. The section name is the name of the shared resource and the parameters within the section define the shares attributes\&. + .PP -A share consists of a directory to which access is being -given plus a description of the access rights which are granted -to the user of the service. Some housekeeping options are -also specifiable. +There are three special sections, [global], [homes] and [printers], which are described under \fBspecial sections\fR\&. The following notes apply to ordinary section descriptions\&. + .PP -Sections are either file share services (used by the -client as an extension of their native file systems) or -printable services (used by the client to access print services -on the host running the server). +A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service\&. Some housekeeping options are also specifiable\&. + .PP -Sections may be designated \fBguest\fR services, -in which case no password is required to access them. A specified -UNIX \fBguest account\fR is used to define access -privileges in this case. +Sections are either file share services (used by the client as an extension of their native file systems) or printable services (used by the client to access print services on the host running the server)\&. + .PP -Sections other than guest services will require a password -to access them. The client provides the username. As older clients -only provide passwords and not usernames, you may specify a list -of usernames to check against the password using the "user =" -option in the share definition. For modern clients such as -Windows 95/98/ME/NT/2000, this should not be necessary. +Sections may be designated \fBguest\fR services, in which case no password is required to access them\&. A specified UNIX \fBguest account\fR is used to define access privileges in this case\&. + .PP -Note that the access rights granted by the server are -masked by the access rights granted to the specified or guest -UNIX user by the host system. The server does not grant more -access than the host system grants. +Sections other than guest services will require a password to access them\&. The client provides the username\&. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the "user =" option in the share definition\&. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary\&. + .PP -The following sample section defines a file space share. -The user has write access to the path \fI/home/bar\fR. -The share is accessed via the share name "foo": +Note that the access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system\&. The server does not grant more access than the host system grants\&. +.PP +The following sample section defines a file space share\&. The user has write access to the path \fI/home/bar\fR\&. The share is accessed via the share name "foo": .nf + + [foo] path = /home/bar read only = no + .fi -.PP -The following sample section defines a printable share. -The share is readonly, but printable. That is, the only write -access permitted is via calls to open, write to and close a -spool file. The \fBguest ok\fR parameter means -access will be permitted as the default guest user (specified -elsewhere): +.PP +The following sample section defines a printable share\&. The share is readonly, but printable\&. That is, the only write access permitted is via calls to open, write to and close a spool file\&. The \fBguest ok\fR parameter means access will be permitted as the default guest user (specified elsewhere): .nf + + [aprinter] path = /usr/spool/public read only = yes printable = yes guest ok = yes + .fi + .SH "SPECIAL SECTIONS" -.SS "THE [GLOBAL] SECTION" + +.SS "The [global] section" + .PP -parameters in this section apply to the server -as a whole, or are defaults for sections which do not -specifically define certain items. See the notes -under PARAMETERS for more information. -.SS "THE [HOMES] SECTION" +parameters in this section apply to the server as a whole, or are defaults for sections which do not specifically define certain items\&. See the notes under PARAMETERS for more information\&. + +.SS "The [homes] section" + .PP -If a section called homes is included in the -configuration file, services connecting clients to their -home directories can be created on the fly by the server. +If a section called homes is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server\&. + .PP -When the connection request is made, the existing -sections are scanned. If a match is found, it is used. If no -match is found, the requested section name is treated as a -user name and looked up in the local password file. If the -name exists and the correct password has been given, a share is -created by cloning the [homes] section. +When the connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, the requested section name is treated as a user name and looked up in the local password file\&. If the name exists and the correct password has been given, a share is created by cloning the [homes] section\&. + .PP -Some modifications are then made to the newly -created share: -.TP 0.2i +Some modifications are then made to the newly created share: + +.TP 3 \(bu -The share name is changed from homes to -the located username. -.TP 0.2i +The share name is changed from homes to the located username\&. + +.TP \(bu -If no path was given, the path is set to -the user's home directory. +If no path was given, the path is set to the user's home directory\&. + +.LP + .PP -If you decide to use a \fBpath =\fR line -in your [homes] section then you may find it useful -to use the %S macro. For example : +If you decide to use a \fBpath =\fR line in your [homes] section then you may find it useful to use the %S macro\&. For example : + .PP \fBpath = /data/pchome/%S\fR + .PP -would be useful if you have different home directories -for your PCs than for UNIX access. -.PP -This is a fast and simple way to give a large number -of clients access to their home directories with a minimum -of fuss. +would be useful if you have different home directories for your PCs than for UNIX access\&. + .PP -A similar process occurs if the requested section -name is "homes", except that the share name is not -changed to that of the requesting user. This method of using -the [homes] section works well if different users share -a client PC. +This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss\&. + .PP -The [homes] section can specify all the parameters -a normal service section can specify, though some make more sense -than others. The following is a typical and suitable [homes] -section: +A similar process occurs if the requested section name is "homes", except that the share name is not changed to that of the requesting user\&. This method of using the [homes] section works well if different users share a client PC\&. +.PP +The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others\&. The following is a typical and suitable [homes] section: .nf + + [homes] read only = no + .fi + .PP -An important point is that if guest access is specified -in the [homes] section, all home directories will be -visible to all clients \fBwithout a password\fR. -In the very unlikely event that this is actually desirable, it -would be wise to also specify \fBread only -access\fR. +An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients \fBwithout a password\fR\&. In the very unlikely event that this is actually desirable, it would be wise to also specify \fBread only access\fR\&. + .PP -Note that the \fBbrowseable\fR flag for -auto home directories will be inherited from the global browseable -flag, not the [homes] browseable flag. This is useful as -it means setting \fBbrowseable = no\fR in -the [homes] section will hide the [homes] share but make -any auto home directories visible. -.SS "THE [PRINTERS] SECTION" +Note that the \fBbrowseable\fR flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag\&. This is useful as it means setting \fBbrowseable = no\fR in the [homes] section will hide the [homes] share but make any auto home directories visible\&. + +.SS "The [printers] section" + .PP -This section works like [homes], -but for printers. +This section works like [homes], but for printers\&. + .PP -If a [printers] section occurs in the -configuration file, users are able to connect to any printer -specified in the local host's printcap file. +If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host's printcap file\&. + .PP -When a connection request is made, the existing sections -are scanned. If a match is found, it is used. If no match is found, -but a [homes] section exists, it is used as described -above. Otherwise, the requested section name is treated as a -printer name and the appropriate printcap file is scanned to see -if the requested section name is a valid printer share name. If -a match is found, a new printer share is created by cloning -the [printers] section. +When a connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, but a [homes] section exists, it is used as described above\&. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name\&. If a match is found, a new printer share is created by cloning the [printers] section\&. + .PP -A few modifications are then made to the newly created -share: -.TP 0.2i +A few modifications are then made to the newly created share: + +.TP 3 \(bu -The share name is set to the located printer -name -.TP 0.2i +The share name is set to the located printer name + +.TP \(bu -If no printer name was given, the printer name -is set to the located printer name -.TP 0.2i +If no printer name was given, the printer name is set to the located printer name + +.TP \(bu -If the share does not permit guest access and -no username was given, the username is set to the located -printer name. -.PP -Note that the [printers] service MUST be -printable - if you specify otherwise, the server will refuse -to load the configuration file. +If the share does not permit guest access and no username was given, the username is set to the located printer name\&. + +.LP + .PP -Typically the path specified would be that of a -world-writeable spool directory with the sticky bit set on -it. A typical [printers] entry would look like -this: +Note that the [printers] service MUST be printable - if you specify otherwise, the server will refuse to load the configuration file\&. +.PP +Typically the path specified would be that of a world-writeable spool directory with the sticky bit set on it\&. A typical [printers] entry would look like this: .nf + [printers] path = /usr/spool/public guest ok = yes printable = yes .fi -.PP -All aliases given for a printer in the printcap file -are legitimate printer names as far as the server is concerned. -If your printing subsystem doesn't work like that, you will have -to set up a pseudo-printcap. This is a file consisting of one or -more lines like this: +.PP +All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned\&. If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap\&. This is a file consisting of one or more lines like this: .nf -alias|alias|alias|alias... + + +alias|alias|alias|alias\&.\&.\&. + .fi + .PP -Each alias should be an acceptable printer name for -your printing subsystem. In the [global] section, specify -the new file as your printcap. The server will then only recognize -names found in your pseudo-printcap, which of course can contain -whatever aliases you like. The same technique could be used -simply to limit access to a subset of your local printers. +Each alias should be an acceptable printer name for your printing subsystem\&. In the [global] section, specify the new file as your printcap\&. The server will then only recognize names found in your pseudo-printcap, which of course can contain whatever aliases you like\&. The same technique could be used simply to limit access to a subset of your local printers\&. + .PP -An alias, by the way, is defined as any component of the -first entry of a printcap record. Records are separated by newlines, -components (if there are more than one) are separated by vertical -bar symbols ('|'). -.sp +An alias, by the way, is defined as any component of the first entry of a printcap record\&. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols ('|')\&. + .RS -.B "Note:" -On SYSV systems which use lpstat to determine what -printers are defined on the system you may be able to use -"printcap name = lpstat" to automatically obtain a list -of printers. See the "printcap name" option -for more details. +.Sh "Note" + +.PP +On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use "printcap name = lpstat" to automatically obtain a list of printers\&. See the "printcap name" option for more details\&. + .RE + .SH "PARAMETERS" + .PP -parameters define the specific attributes of sections. +parameters define the specific attributes of sections\&. + .PP -Some parameters are specific to the [global] section -(e.g., \fBsecurity\fR). Some parameters are usable -in all sections (e.g., \fBcreate mode\fR). All others -are permissible only in normal sections. For the purposes of the -following descriptions the [homes] and [printers] -sections will be considered normal. The letter \fBG\fR -in parentheses indicates that a parameter is specific to the -[global] section. The letter \fBS\fR -indicates that a parameter can be specified in a service specific -section. Note that all \fBS\fR parameters can also be specified in -the [global] section - in which case they will define -the default behavior for all services. +Some parameters are specific to the [global] section (e\&.g\&., \fBsecurity\fR)\&. Some parameters are usable in all sections (e\&.g\&., \fBcreate mode\fR)\&. All others are permissible only in normal sections\&. For the purposes of the following descriptions the [homes] and [printers] sections will be considered normal\&. The letter \fBG\fR in parentheses indicates that a parameter is specific to the [global] section\&. The letter \fBS\fR indicates that a parameter can be specified in a service specific section\&. Note that all \fBS\fR parameters can also be specified in the [global] section - in which case they will define the default behavior for all services\&. + .PP -parameters are arranged here in alphabetical order - this may -not create best bedfellows, but at least you can find them! Where -there are synonyms, the preferred synonym is described, others refer -to the preferred synonym. +parameters are arranged here in alphabetical order - this may not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred synonym\&. + .SH "VARIABLE SUBSTITUTIONS" + .PP -Many of the strings that are settable in the config file -can take substitutions. For example the option "path = -/tmp/%u" would be interpreted as "path = -/tmp/john" if the user connected with the username john. +Many of the strings that are settable in the config file can take substitutions\&. For example the option "path = /tmp/%u" would be interpreted as "path = /tmp/john" if the user connected with the username john\&. + .PP -These substitutions are mostly noted in the descriptions below, -but there are some general substitutions which apply whenever they -might be relevant. These are: -.TP -\fB%U\fR -session user name (the user name that the client -wanted, not necessarily the same as the one they got). -.TP -\fB%G\fR -primary group name of %U. -.TP -\fB%h\fR -the Internet hostname that Samba is running -on. -.TP -\fB%m\fR -the NetBIOS name of the client machine -(very useful). -.TP -\fB%L\fR -the NetBIOS name of the server. This allows you -to change your config based on what the client calls you. Your -server can have a "dual personality". - -Note that this parameter is not available when Samba listens -on port 445, as clients no longer send this information -.TP -\fB%M\fR -the Internet name of the client machine. -.TP -\fB%R\fR -the selected protocol level after -protocol negotiation. It can be one of CORE, COREPLUS, -LANMAN1, LANMAN2 or NT1. -.TP -\fB%d\fR -The process id of the current server -process. -.TP -\fB%a\fR -the architecture of the remote -machine. Only some are recognized, and those may not be -100% reliable. It currently recognizes Samba, WfWg, Win95, -WinNT and Win2k. Anything else will be known as -"UNKNOWN". If it gets it wrong then sending a level -3 log to samba@samba.org - should allow it to be fixed. -.TP -\fB%I\fR -The IP address of the client machine. -.TP -\fB%T\fR -the current date and time. -.TP -\fB%D\fR -Name of the domain or workgroup of the current user. -.TP -\fB%$(\fIenvvar\fB)\fR -The value of the environment variable -\fIenvar\fR. +These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant\&. These are: + +.TP +%U +session user name (the user name that the client wanted, not necessarily the same as the one they got)\&. + + +.TP +%G +primary group name of %U\&. + + +.TP +%h +the Internet hostname that Samba is running on\&. + + +.TP +%m +the NetBIOS name of the client machine (very useful)\&. + + +.TP +%L +the NetBIOS name of the server\&. This allows you to change your config based on what the client calls you\&. Your server can have a "dual personality"\&. + + +Note that this parameter is not available when Samba listens on port 445, as clients no longer send this information + + +.TP +%M +the Internet name of the client machine\&. + + +.TP +%R +the selected protocol level after protocol negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\&. + + +.TP +%d +The process id of the current server process\&. + + +.TP +%a +the architecture of the remote machine\&. Only some are recognized, and those may not be 100% reliable\&. It currently recognizes Samba, WfWg, Win95, WinNT and Win2k\&. Anything else will be known as "UNKNOWN"\&. If it gets it wrong then sending a level 3 log to samba@samba\&.org should allow it to be fixed\&. + + +.TP +%I +The IP address of the client machine\&. + + +.TP +%T +the current date and time\&. + + +.TP +%D +Name of the domain or workgroup of the current user\&. + + +.TP +%$(\fIenvvar\fR) +The value of the environment variable \fIenvar\fR\&. + + .PP -The following substitutes apply only to some configuration options(only those -that are used when a connection has been established): +The following substitutes apply only to some configuration options(only those that are used when a connection has been established): + .TP -\fB%S\fR -the name of the current service, if any. +%S +the name of the current service, if any\&. + + .TP -\fB%P\fR -the root directory of the current service, -if any. +%P +the root directory of the current service, if any\&. + + .TP -\fB%u\fR -user name of the current service, if any. +%u +user name of the current service, if any\&. + + .TP -\fB%g\fR -primary group name of %u. +%g +primary group name of %u\&. + + .TP -\fB%H\fR -the home directory of the user given -by %u. +%H +the home directory of the user given by %u\&. + + .TP -\fB%N\fR -the name of your NIS home directory server. -This is obtained from your NIS auto.map entry. If you have -not compiled Samba with the \fB--with-automount\fR -option then this value will be the same as %L. +%N +the name of your NIS home directory server\&. This is obtained from your NIS auto\&.map entry\&. If you have not compiled Samba with the \fB--with-automount\fR option then this value will be the same as %L\&. + + .TP -\fB%p\fR -the path of the service's home directory, -obtained from your NIS auto.map entry. The NIS auto.map entry -is split up as "%N:%p". +%p +the path of the service's home directory, obtained from your NIS auto\&.map entry\&. The NIS auto\&.map entry is split up as "%N:%p"\&. + + .PP -There are some quite creative things that can be done -with these substitutions and other smb.conf options. +There are some quite creative things that can be done with these substitutions and other smb\&.conf options\&. + .SH "NAME MANGLING" + .PP -Samba supports "name mangling" so that DOS and -Windows clients can use files that don't conform to the 8.3 format. -It can also be set to adjust the case of 8.3 format filenames. +Samba supports "name mangling" so that DOS and Windows clients can use files that don't conform to the 8\&.3 format\&. It can also be set to adjust the case of 8\&.3 format filenames\&. + .PP -There are several options that control the way mangling is -performed, and they are grouped here rather than listed separately. -For the defaults look at the output of the testparm program. +There are several options that control the way mangling is performed, and they are grouped here rather than listed separately\&. For the defaults look at the output of the testparm program\&. + .PP -All of these options can be set separately for each service -(or globally, of course). +All of these options can be set separately for each service (or globally, of course)\&. + .PP -The options are: -.TP -\fBmangle case = yes/no\fR -controls if names that have characters that -aren't of the "default" case are mangled. For example, -if this is yes then a name like "Mail" would be mangled. -Default \fBno\fR. -.TP -\fBcase sensitive = yes/no\fR -controls whether filenames are case sensitive. If -they aren't then Samba must do a filename search and match on passed -names. Default \fBno\fR. -.TP -\fBdefault case = upper/lower\fR -controls what the default case is for new -filenames. Default \fBlower\fR. -.TP -\fBpreserve case = yes/no\fR -controls if new files are created with the -case that the client passes, or if they are forced to be the -"default" case. Default \fByes\fR. -.TP -\fBshort preserve case = yes/no\fR -controls if new files which conform to 8.3 syntax, -that is all in upper case and of suitable length, are created -upper case, or if they are forced to be the "default" -case. This option can be use with "preserve case = yes" -to permit long filenames to retain their case, while short names -are lowercased. Default \fByes\fR. +The options are: + +.TP +mangle case = yes/no +controls if names that have characters that aren't of the "default" case are mangled\&. For example, if this is yes then a name like "Mail" would be mangled\&. Default \fBno\fR\&. + + +.TP +case sensitive = yes/no +controls whether filenames are case sensitive\&. If they aren't then Samba must do a filename search and match on passed names\&. Default \fBno\fR\&. + + +.TP +default case = upper/lower +controls what the default case is for new filenames\&. Default \fBlower\fR\&. + + +.TP +preserve case = yes/no +controls if new files are created with the case that the client passes, or if they are forced to be the "default" case\&. Default \fByes\fR\&. + + +.TP +short preserve case = yes/no +controls if new files which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the "default" case\&. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names are lowercased\&. Default \fByes\fR\&. + + .PP -By default, Samba 3.0 has the same semantics as a Windows -NT server, in that it is case insensitive but case preserving. +By default, Samba 3\&.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving\&. + .SH "NOTE ABOUT USERNAME/PASSWORD VALIDATION" + .PP -There are a number of ways in which a user can connect -to a service. The server uses the following steps in determining -if it will allow a connection to a specified service. If all the -steps fail, then the connection request is rejected. However, if one of the -steps succeeds, then the following steps are not checked. +There are a number of ways in which a user can connect to a service\&. The server uses the following steps in determining if it will allow a connection to a specified service\&. If all the steps fail, then the connection request is rejected\&. However, if one of the steps succeeds, then the following steps are not checked\&. + .PP -If the service is marked "guest only = yes" and the -server is running with share-level security ("security = share") -then steps 1 to 5 are skipped. -.TP 3 -1. -If the client has passed a username/password -pair and that username/password pair is validated by the UNIX -system's password programs then the connection is made as that -username. Note that this includes the -\\\\server\\service%\fIusername\fR method of passing -a username. -.TP 3 -2. -If the client has previously registered a username -with the system and now supplies a correct password for that -username then the connection is allowed. -.TP 3 -3. -The client's NetBIOS name and any previously -used user names are checked against the supplied password, if -they match then the connection is allowed as the corresponding -user. -.TP 3 -4. -If the client has previously validated a -username/password pair with the server and the client has passed -the validation token then that username is used. -.TP 3 -5. -If a "user = " field is given in the -\fIsmb.conf\fR file for the service and the client -has supplied a password, and that password matches (according to -the UNIX system's password checking) with one of the usernames -from the "user =" field then the connection is made as -the username in the "user =" line. If one -of the username in the "user =" list begins with a -\&'@' then that name expands to a list of names in -the group of the same name. +If the service is marked "guest only = yes" and the server is running with share-level security ("security = share") then steps 1 to 5 are skipped\&. + .TP 3 -6. -If the service is a guest service then a -connection is made as the username given in the "guest -account =" for the service, irrespective of the -supplied password. +1. +If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs then the connection is made as that username\&. Note that this includes the \\\\server\\service%\fIusername\fR method of passing a username\&. + +.TP +2. +If the client has previously registered a username with the system and now supplies a correct password for that username then the connection is allowed\&. + +.TP +3. +The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user\&. + +.TP +4. +If the client has previously validated a username/password pair with the server and the client has passed the validation token then that username is used\&. + +.TP +5. +If a "user = " field is given in the \fIsmb\&.conf\fR file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password checking) with one of the usernames from the "user =" field then the connection is made as the username in the "user =" line\&. If one of the username in the "user =" list begins with a '@' then that name expands to a list of names in the group of the same name\&. + +.TP +6. +If the service is a guest service then a connection is made as the username given in the "guest account =" for the service, irrespective of the supplied password\&. + +.LP + .SH "COMPLETE LIST OF GLOBAL PARAMETERS" + .PP -Here is a list of all global parameters. See the section of -each parameter for details. Note that some are synonyms. -.TP 0.2i +Here is a list of all global parameters\&. See the section of each parameter for details\&. Note that some are synonyms\&. + +.TP 3 \(bu \fIabort shutdown script\fR -.TP 0.2i + +.TP \(bu \fIadd group script\fR -.TP 0.2i + +.TP +\(bu +\fIadd machine script\fR + +.TP \(bu \fIaddprinter command\fR -.TP 0.2i + +.TP \(bu \fIadd share command\fR -.TP 0.2i + +.TP \(bu \fIadd user script\fR -.TP 0.2i + +.TP \(bu \fIadd user to group script\fR -.TP 0.2i -\(bu -\fIadd machine script\fR -.TP 0.2i -\(bu -\fIdelete group script\fR -.TP 0.2i + +.TP \(bu \fIads server\fR -.TP 0.2i + +.TP \(bu \fIalgorithmic rid base\fR -.TP 0.2i + +.TP \(bu \fIallow trusted domains\fR -.TP 0.2i + +.TP \(bu \fIannounce as\fR -.TP 0.2i + +.TP \(bu \fIannounce version\fR -.TP 0.2i + +.TP \(bu \fIauth methods\fR -.TP 0.2i + +.TP \(bu \fIauto services\fR -.TP 0.2i + +.TP \(bu \fIbind interfaces only\fR -.TP 0.2i + +.TP \(bu \fIbrowse list\fR -.TP 0.2i + +.TP \(bu \fIchange notify timeout\fR -.TP 0.2i + +.TP \(bu \fIchange share command\fR -.TP 0.2i + +.TP \(bu \fIconfig file\fR -.TP 0.2i + +.TP \(bu -\fIdeadtime\fR -.TP 0.2i +\fIdead time\fR + +.TP \(bu \fIdebug hires timestamp\fR -.TP 0.2i + +.TP +\(bu +\fIdebug level\fR + +.TP \(bu \fIdebug pid\fR -.TP 0.2i + +.TP \(bu \fIdebug timestamp\fR -.TP 0.2i + +.TP \(bu \fIdebug uid\fR -.TP 0.2i + +.TP \(bu -\fIdebuglevel\fR -.TP 0.2i +\fIdefault service\fR + +.TP \(bu \fIdefault\fR -.TP 0.2i -\(bu -\fIdefault service\fR -.TP 0.2i + +.TP \(bu -\fIdeleteprinter command\fR -.TP 0.2i +\fIdelete group script\fR + +.TP \(bu -\fIdelete share command\fR -.TP 0.2i +\fIdeleteprinter command\fR + +.TP \(bu -\fIdelete user script\fR -.TP 0.2i +\fIdelete share command\fR + +.TP \(bu \fIdelete user from group script\fR -.TP 0.2i + +.TP +\(bu +\fIdelete user script\fR + +.TP \(bu \fIdfree command\fR -.TP 0.2i + +.TP \(bu \fIdisable netbios\fR -.TP 0.2i + +.TP \(bu \fIdisable spoolss\fR -.TP 0.2i + +.TP \(bu \fIdisplay charset\fR -.TP 0.2i + +.TP \(bu \fIdns proxy\fR -.TP 0.2i + +.TP \(bu \fIdomain logons\fR -.TP 0.2i + +.TP \(bu \fIdomain master\fR -.TP 0.2i + +.TP \(bu \fIdos charset\fR -.TP 0.2i + +.TP \(bu \fIencrypt passwords\fR -.TP 0.2i + +.TP \(bu \fIenhanced browsing\fR -.TP 0.2i + +.TP \(bu \fIenumports command\fR -.TP 0.2i + +.TP \(bu \fIgetwd cache\fR -.TP 0.2i -\(bu -\fIhide local users\fR -.TP 0.2i -\(bu -\fIhide unreadable\fR -.TP 0.2i + +.TP \(bu -\fIhide unwriteable files\fR -.TP 0.2i +\fIguest account\fR + +.TP \(bu -\fIhide special files\fR -.TP 0.2i +\fIhide local users\fR + +.TP \(bu \fIhomedir map\fR -.TP 0.2i + +.TP \(bu \fIhost msdfs\fR -.TP 0.2i + +.TP \(bu \fIhostname lookups\fR -.TP 0.2i + +.TP \(bu \fIhosts equiv\fR -.TP 0.2i + +.TP +\(bu +\fIinclude\fR + +.TP \(bu \fIinterfaces\fR -.TP 0.2i + +.TP \(bu \fIkeepalive\fR -.TP 0.2i + +.TP \(bu \fIkernel oplocks\fR -.TP 0.2i + +.TP \(bu \fIlanman auth\fR -.TP 0.2i + +.TP \(bu \fIlarge readwrite\fR -.TP 0.2i + +.TP \(bu \fIldap admin dn\fR -.TP 0.2i + +.TP \(bu \fIldap delete dn\fR -.TP 0.2i + +.TP \(bu \fIldap filter\fR -.TP 0.2i + +.TP +\(bu +\fIldap machine suffix\fR + +.TP +\(bu +\fIldap passwd sync\fR + +.TP \(bu \fIldap port\fR -.TP 0.2i + +.TP \(bu \fIldap server\fR -.TP 0.2i + +.TP \(bu \fIldap ssl\fR -.TP 0.2i + +.TP \(bu \fIldap suffix\fR -.TP 0.2i -\(bu -\fIldap user suffix\fR -.TP 0.2i -\(bu -\fIldap machine suffix\fR -.TP 0.2i -\(bu -\fIldap passwd sync\fR -.TP 0.2i + +.TP \(bu \fIldap trust ids\fR -.TP 0.2i + +.TP +\(bu +\fIldap user suffix\fR + +.TP \(bu \fIlm announce\fR -.TP 0.2i + +.TP \(bu \fIlm interval\fR -.TP 0.2i + +.TP \(bu \fIload printers\fR -.TP 0.2i + +.TP \(bu \fIlocal master\fR -.TP 0.2i -\(bu -\fIlock dir\fR -.TP 0.2i + +.TP \(bu \fIlock directory\fR -.TP 0.2i + +.TP +\(bu +\fIlock dir\fR + +.TP \(bu \fIlock spin count\fR -.TP 0.2i + +.TP \(bu \fIlock spin time\fR -.TP 0.2i -\(bu -\fIpid directory\fR -.TP 0.2i + +.TP \(bu \fIlog file\fR -.TP 0.2i + +.TP \(bu \fIlog level\fR -.TP 0.2i + +.TP \(bu \fIlogon drive\fR -.TP 0.2i + +.TP \(bu \fIlogon home\fR -.TP 0.2i + +.TP \(bu \fIlogon path\fR -.TP 0.2i + +.TP \(bu \fIlogon script\fR -.TP 0.2i + +.TP \(bu \fIlpq cache time\fR -.TP 0.2i + +.TP \(bu \fImachine password timeout\fR -.TP 0.2i + +.TP +\(bu +\fImangling stack\fR + +.TP \(bu -\fImangle prefix\fR -.TP 0.2i +\fImangling prefix\fR + +.TP \(bu -\fImangled stack\fR -.TP 0.2i +\fImangling method\fR + +.TP \(bu \fImap to guest\fR -.TP 0.2i + +.TP \(bu \fImax disk size\fR -.TP 0.2i + +.TP \(bu \fImax log size\fR -.TP 0.2i + +.TP \(bu \fImax mux\fR -.TP 0.2i + +.TP \(bu \fImax open files\fR -.TP 0.2i + +.TP \(bu \fImax protocol\fR -.TP 0.2i + +.TP \(bu \fImax smbd processes\fR -.TP 0.2i + +.TP \(bu \fImax ttl\fR -.TP 0.2i + +.TP \(bu \fImax wins ttl\fR -.TP 0.2i + +.TP \(bu \fImax xmit\fR -.TP 0.2i + +.TP \(bu \fImessage command\fR -.TP 0.2i + +.TP \(bu \fImin passwd length\fR -.TP 0.2i + +.TP \(bu \fImin password length\fR -.TP 0.2i + +.TP \(bu \fImin protocol\fR -.TP 0.2i + +.TP \(bu \fImin wins ttl\fR -.TP 0.2i + +.TP \(bu \fIname cache timeout\fR -.TP 0.2i + +.TP \(bu \fIname resolve order\fR -.TP 0.2i + +.TP \(bu \fInetbios aliases\fR -.TP 0.2i + +.TP \(bu \fInetbios name\fR -.TP 0.2i + +.TP \(bu \fInetbios scope\fR -.TP 0.2i + +.TP \(bu \fInis homedir\fR -.TP 0.2i -\(bu -\fIntlm auth\fR -.TP 0.2i + +.TP \(bu \fInon unix account range\fR -.TP 0.2i + +.TP +\(bu +\fIntlm auth\fR + +.TP \(bu \fInt pipe support\fR -.TP 0.2i + +.TP \(bu \fInt status support\fR -.TP 0.2i + +.TP \(bu \fInull passwords\fR -.TP 0.2i + +.TP \(bu \fIobey pam restrictions\fR -.TP 0.2i + +.TP \(bu \fIoplock break wait time\fR -.TP 0.2i -\(bu -\fIos level\fR -.TP 0.2i + +.TP \(bu \fIos2 driver map\fR -.TP 0.2i + +.TP +\(bu +\fIos level\fR + +.TP \(bu \fIpam password change\fR -.TP 0.2i + +.TP \(bu \fIpanic action\fR -.TP 0.2i + +.TP \(bu \fIparanoid server security\fR -.TP 0.2i + +.TP \(bu \fIpassdb backend\fR -.TP 0.2i -\(bu -\fIpasswd chat\fR -.TP 0.2i + +.TP \(bu \fIpasswd chat debug\fR -.TP 0.2i + +.TP +\(bu +\fIpasswd chat\fR + +.TP \(bu \fIpasswd program\fR -.TP 0.2i + +.TP \(bu \fIpassword level\fR -.TP 0.2i + +.TP \(bu \fIpassword server\fR -.TP 0.2i + +.TP +\(bu +\fIpid directory\fR + +.TP \(bu \fIprefered master\fR -.TP 0.2i + +.TP \(bu \fIpreferred master\fR -.TP 0.2i -\(bu -\fIpreload\fR -.TP 0.2i + +.TP \(bu \fIpreload modules\fR -.TP 0.2i -\(bu -\fIprintcap\fR -.TP 0.2i + +.TP \(bu -\fIprintcap name\fR -.TP 0.2i +\fIpreload\fR + +.TP +\(bu +\fIprintcap\fR + +.TP \(bu \fIprivate dir\fR -.TP 0.2i + +.TP \(bu \fIprotocol\fR -.TP 0.2i + +.TP \(bu \fIread bmpx\fR -.TP 0.2i + +.TP \(bu \fIread raw\fR -.TP 0.2i + +.TP \(bu \fIread size\fR -.TP 0.2i + +.TP \(bu \fIrealm\fR -.TP 0.2i + +.TP \(bu \fIremote announce\fR -.TP 0.2i + +.TP \(bu \fIremote browse sync\fR -.TP 0.2i + +.TP \(bu \fIrestrict anonymous\fR -.TP 0.2i + +.TP \(bu -\fIroot\fR -.TP 0.2i +\fIroot directory\fR + +.TP \(bu \fIroot dir\fR -.TP 0.2i + +.TP \(bu -\fIroot directory\fR -.TP 0.2i +\fIroot\fR + +.TP \(bu \fIsecurity\fR -.TP 0.2i + +.TP \(bu \fIserver schannel\fR -.TP 0.2i + +.TP \(bu \fIserver string\fR -.TP 0.2i + +.TP \(bu \fIset primary group script\fR -.TP 0.2i + +.TP \(bu \fIshow add printer wizard\fR -.TP 0.2i + +.TP \(bu \fIshutdown script\fR -.TP 0.2i + +.TP \(bu \fIsmb passwd file\fR -.TP 0.2i + +.TP \(bu \fIsmb ports\fR -.TP 0.2i + +.TP \(bu \fIsocket address\fR -.TP 0.2i + +.TP \(bu \fIsocket options\fR -.TP 0.2i + +.TP \(bu \fIsource environment\fR -.TP 0.2i + +.TP \(bu -\fIuse spnego\fR -.TP 0.2i +\fIstat cache size\fR + +.TP \(bu \fIstat cache\fR -.TP 0.2i -\(bu -\fIstat cache size\fR -.TP 0.2i + +.TP \(bu \fIstrip dot\fR -.TP 0.2i -\(bu -\fIsyslog\fR -.TP 0.2i + +.TP \(bu \fIsyslog only\fR -.TP 0.2i + +.TP +\(bu +\fIsyslog\fR + +.TP \(bu \fItemplate homedir\fR -.TP 0.2i + +.TP \(bu \fItemplate shell\fR -.TP 0.2i + +.TP \(bu \fItime offset\fR -.TP 0.2i + +.TP \(bu \fItime server\fR -.TP 0.2i + +.TP \(bu \fItimestamp logs\fR -.TP 0.2i + +.TP \(bu \fItotal print jobs\fR -.TP 0.2i + +.TP \(bu \fIunicode\fR -.TP 0.2i + +.TP \(bu \fIunix charset\fR -.TP 0.2i + +.TP \(bu \fIunix extensions\fR -.TP 0.2i + +.TP \(bu \fIunix password sync\fR -.TP 0.2i + +.TP \(bu \fIupdate encrypted\fR -.TP 0.2i + +.TP \(bu \fIuse mmap\fR -.TP 0.2i -\(bu -\fIuse sendfile\fR -.TP 0.2i + +.TP \(bu \fIusername level\fR -.TP 0.2i + +.TP \(bu \fIusername map\fR -.TP 0.2i + +.TP \(bu -\fIutmp\fR -.TP 0.2i +\fIuse spnego\fR + +.TP \(bu \fIutmp directory\fR -.TP 0.2i + +.TP \(bu -\fIwtmp directory\fR -.TP 0.2i +\fIutmp\fR + +.TP \(bu \fIwinbind cache time\fR -.TP 0.2i -\(bu -\fIwinbind enum users\fR -.TP 0.2i + +.TP \(bu \fIwinbind enum groups\fR -.TP 0.2i + +.TP +\(bu +\fIwinbind enum users\fR + +.TP \(bu \fIwinbind gid\fR -.TP 0.2i + +.TP \(bu \fIwinbind separator\fR -.TP 0.2i + +.TP \(bu \fIwinbind uid\fR -.TP 0.2i + +.TP \(bu -\fIwinbind use default domain\fR -.TP 0.2i +\fIwinbind used default domain\fR + +.TP \(bu \fIwins hook\fR -.TP 0.2i + +.TP \(bu -\fIwins partners\fR -.TP 0.2i +\fIwins partner\fR + +.TP \(bu \fIwins proxy\fR -.TP 0.2i + +.TP \(bu \fIwins server\fR -.TP 0.2i + +.TP \(bu \fIwins support\fR -.TP 0.2i + +.TP \(bu \fIworkgroup\fR -.TP 0.2i + +.TP \(bu \fIwrite raw\fR + +.TP +\(bu +\fIwtmp directory\fR + +.LP + .SH "COMPLETE LIST OF SERVICE PARAMETERS" + .PP -Here is a list of all service parameters. See the section on -each parameter for details. Note that some are synonyms. -.TP 0.2i +Here is a list of all service parameters\&. See the section on each parameter for details\&. Note that some are synonyms\&. + +.TP 3 \(bu \fIadmin users\fR -.TP 0.2i + +.TP \(bu \fIallow hosts\fR -.TP 0.2i + +.TP \(bu \fIavailable\fR -.TP 0.2i + +.TP \(bu \fIblocking locks\fR -.TP 0.2i + +.TP \(bu \fIblock size\fR -.TP 0.2i + +.TP \(bu \fIbrowsable\fR -.TP 0.2i + +.TP \(bu \fIbrowseable\fR -.TP 0.2i + +.TP \(bu \fIcase sensitive\fR -.TP 0.2i + +.TP \(bu \fIcasesignames\fR -.TP 0.2i + +.TP \(bu \fIcomment\fR -.TP 0.2i + +.TP \(bu \fIcopy\fR -.TP 0.2i + +.TP \(bu \fIcreate mask\fR -.TP 0.2i + +.TP \(bu \fIcreate mode\fR -.TP 0.2i + +.TP \(bu \fIcsc policy\fR -.TP 0.2i + +.TP \(bu \fIdefault case\fR -.TP 0.2i + +.TP \(bu \fIdefault devmode\fR -.TP 0.2i + +.TP \(bu \fIdelete readonly\fR -.TP 0.2i + +.TP \(bu \fIdelete veto files\fR -.TP 0.2i + +.TP \(bu \fIdeny hosts\fR -.TP 0.2i -\(bu -\fIdirectory\fR -.TP 0.2i + +.TP \(bu \fIdirectory mask\fR -.TP 0.2i + +.TP \(bu \fIdirectory mode\fR -.TP 0.2i + +.TP \(bu \fIdirectory security mask\fR -.TP 0.2i + +.TP +\(bu +\fIdirectory\fR + +.TP \(bu \fIdont descend\fR -.TP 0.2i + +.TP \(bu \fIdos filemode\fR -.TP 0.2i + +.TP \(bu \fIdos filetime resolution\fR -.TP 0.2i + +.TP \(bu \fIdos filetimes\fR -.TP 0.2i + +.TP \(bu \fIexec\fR -.TP 0.2i + +.TP \(bu \fIfake directory create times\fR -.TP 0.2i + +.TP \(bu \fIfake oplocks\fR -.TP 0.2i + +.TP \(bu \fIfollow symlinks\fR -.TP 0.2i + +.TP \(bu \fIforce create mode\fR -.TP 0.2i + +.TP \(bu \fIforce directory mode\fR -.TP 0.2i + +.TP \(bu \fIforce directory security mode\fR -.TP 0.2i + +.TP \(bu \fIforce group\fR -.TP 0.2i + +.TP \(bu \fIforce security mode\fR -.TP 0.2i + +.TP \(bu \fIforce user\fR -.TP 0.2i + +.TP \(bu \fIfstype\fR -.TP 0.2i + +.TP \(bu \fIgroup\fR -.TP 0.2i + +.TP \(bu \fIguest account\fR -.TP 0.2i + +.TP \(bu \fIguest ok\fR -.TP 0.2i + +.TP \(bu \fIguest only\fR -.TP 0.2i + +.TP \(bu \fIhide dot files\fR -.TP 0.2i + +.TP \(bu \fIhide files\fR -.TP 0.2i -\(bu -\fIhosts allow\fR -.TP 0.2i + +.TP \(bu -\fIhosts deny\fR -.TP 0.2i +\fIhide special files\fR + +.TP \(bu -\fIinclude\fR -.TP 0.2i +\fIhide unreadable\fR + +.TP +\(bu +\fIhide unwriteable files\fR + +.TP +\(bu +\fIhosts allow\fR + +.TP +\(bu +\fIhosts deny\fR + +.TP \(bu \fIinherit acls\fR -.TP 0.2i + +.TP \(bu \fIinherit permissions\fR -.TP 0.2i + +.TP \(bu \fIinvalid users\fR -.TP 0.2i + +.TP \(bu \fIlevel2 oplocks\fR -.TP 0.2i + +.TP \(bu \fIlocking\fR -.TP 0.2i + +.TP \(bu \fIlppause command\fR -.TP 0.2i + +.TP \(bu \fIlpq command\fR -.TP 0.2i + +.TP \(bu \fIlpresume command\fR -.TP 0.2i + +.TP \(bu \fIlprm command\fR -.TP 0.2i + +.TP \(bu \fImagic output\fR -.TP 0.2i + +.TP \(bu \fImagic script\fR -.TP 0.2i + +.TP \(bu \fImangle case\fR -.TP 0.2i + +.TP \(bu \fImangled map\fR -.TP 0.2i + +.TP \(bu \fImangled names\fR -.TP 0.2i + +.TP \(bu \fImangling char\fR -.TP 0.2i -\(bu -\fImangling method\fR -.TP 0.2i + +.TP \(bu \fImap archive\fR -.TP 0.2i + +.TP \(bu \fImap hidden\fR -.TP 0.2i + +.TP \(bu \fImap system\fR -.TP 0.2i + +.TP \(bu \fImax connections\fR -.TP 0.2i + +.TP \(bu \fImax print jobs\fR -.TP 0.2i + +.TP \(bu \fImin print space\fR -.TP 0.2i + +.TP \(bu \fImsdfs proxy\fR -.TP 0.2i + +.TP \(bu \fImsdfs root\fR -.TP 0.2i + +.TP \(bu \fInt acl support\fR -.TP 0.2i + +.TP \(bu \fIonly guest\fR -.TP 0.2i + +.TP \(bu \fIonly user\fR -.TP 0.2i + +.TP \(bu \fIoplock contention limit\fR -.TP 0.2i + +.TP \(bu \fIoplocks\fR -.TP 0.2i + +.TP \(bu \fIpath\fR -.TP 0.2i + +.TP \(bu \fIposix locking\fR -.TP 0.2i + +.TP \(bu \fIpostexec\fR -.TP 0.2i -\(bu -\fIpreexec\fR -.TP 0.2i + +.TP \(bu \fIpreexec close\fR -.TP 0.2i -\(bu -\fIpreserve case\fR -.TP 0.2i + +.TP \(bu -\fIprint command\fR -.TP 0.2i +\fIpreexec\fR + +.TP \(bu -\fIprint ok\fR -.TP 0.2i +\fIpreserve case\fR + +.TP \(bu \fIprintable\fR -.TP 0.2i + +.TP \(bu -\fIprinter\fR -.TP 0.2i +\fIprintcap name\fR + +.TP +\(bu +\fIprint command\fR + +.TP \(bu \fIprinter admin\fR -.TP 0.2i + +.TP \(bu \fIprinter name\fR -.TP 0.2i + +.TP +\(bu +\fIprinter\fR + +.TP \(bu \fIprinting\fR -.TP 0.2i + +.TP +\(bu +\fIprint ok\fR + +.TP \(bu \fIpublic\fR -.TP 0.2i + +.TP \(bu \fIqueuepause command\fR -.TP 0.2i + +.TP \(bu \fIqueueresume command\fR -.TP 0.2i + +.TP \(bu \fIread list\fR -.TP 0.2i + +.TP \(bu \fIread only\fR -.TP 0.2i + +.TP \(bu \fIroot postexec\fR -.TP 0.2i -\(bu -\fIroot preexec\fR -.TP 0.2i + +.TP \(bu \fIroot preexec close\fR -.TP 0.2i + +.TP +\(bu +\fIroot preexec\fR + +.TP \(bu \fIsecurity mask\fR -.TP 0.2i + +.TP \(bu \fIset directory\fR -.TP 0.2i + +.TP \(bu \fIshare modes\fR -.TP 0.2i + +.TP \(bu \fIshort preserve case\fR -.TP 0.2i + +.TP \(bu \fIstrict allocate\fR -.TP 0.2i + +.TP \(bu \fIstrict locking\fR -.TP 0.2i + +.TP \(bu \fIstrict sync\fR -.TP 0.2i + +.TP \(bu \fIsync always\fR -.TP 0.2i + +.TP \(bu \fIuse client driver\fR -.TP 0.2i -\(bu -\fIuser\fR -.TP 0.2i + +.TP \(bu \fIusername\fR -.TP 0.2i + +.TP \(bu \fIusers\fR -.TP 0.2i + +.TP +\(bu +\fIuser\fR + +.TP +\(bu +\fIuse sendfile\fR + +.TP \(bu \fIvalid users\fR -.TP 0.2i + +.TP \(bu \fIveto files\fR -.TP 0.2i + +.TP \(bu \fIveto oplock files\fR -.TP 0.2i -\(bu -\fIvfs path\fR -.TP 0.2i + +.TP \(bu \fIvfs object\fR -.TP 0.2i + +.TP \(bu \fIvfs options\fR -.TP 0.2i + +.TP +\(bu +\fIvfs path\fR + +.TP \(bu \fIvolume\fR -.TP 0.2i + +.TP \(bu \fIwide links\fR -.TP 0.2i + +.TP \(bu \fIwritable\fR -.TP 0.2i + +.TP +\(bu +\fIwriteable\fR + +.TP \(bu \fIwrite cache size\fR -.TP 0.2i + +.TP \(bu \fIwrite list\fR -.TP 0.2i + +.TP \(bu \fIwrite ok\fR -.TP 0.2i -\(bu -\fIwriteable\fR + +.LP + .SH "EXPLANATION OF EACH PARAMETER" + +.TP +abort shutdown script (G) +\fBThis parameter only exists in the HEAD cvs branch\fR This a full path name to a script called by \fBsmbd\fR(8) that should stop a shutdown procedure issued by the \fIshutdown script\fR\&. + + +This command will be run as user\&. + + +Default: \fBNone\fR\&. + + +Example: \fBabort shutdown script = /sbin/shutdown -c\fR + + +.TP +add group script (G) +This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd\fR(8) when a new group is requested\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&. The script is free to create a group with an arbitrary name to circumvent unix group name restrictions\&. In that case the script must print the numeric gid of the created group on stdout\&. + + +.TP +add machine script (G) +This is the full pathname to a script that will be run by \fBsmbd\fR(8) when a machine is added to it's domain using the administrator username and password method\&. + + +This option is only required when using sam back-ends tied to the Unix uid method of RID calculation such as smbpasswd\&. This option is only available in Samba 3\&.0\&. + + +Default: \fBadd machine script = \fR + + +Example: \fBadd machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u\fR + + .TP -\fB>abort shutdown script (G)\fR -\fBThis parameter only exists in the HEAD cvs branch\fR -This a full path name to a script called by \fBsmbd\fR(8) that -should stop a shutdown procedure issued by the \fIshutdown script\fR. +addprinter command (G) +With the introduction of MS-RPC based printing support for Windows NT/2000 clients in Samba 2\&.2, The MS Add Printer Wizard (APW) icon is now also available in the "Printers\&.\&.\&." folder displayed a share listing\&. The APW allows for printers to be add remotely to a Samba or Windows NT/2000 print server\&. + + +For a Samba host this means that the printer must be physically added to the underlying printing system\&. The \fIadd printer command\fR defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the \fIsmb\&.conf\fR file in order that it can be shared by \fBsmbd\fR(8)\&. + + +The \fIaddprinter command\fR is automatically invoked with the following parameter (in order): + + +\fIprinter name\fR + +\fIshare name\fR + +\fIport name\fR + +\fIdriver name\fR + +\fIlocation\fR + +\fIWindows 9x driver location\fR + +All parameters are filled in from the PRINTER_INFO_2 structure sent by the Windows NT/2000 client with one exception\&. The "Windows 9x driver location" parameter is included for backwards compatibility only\&. The remaining fields in the structure are generated from answers to the APW questions\&. + + +Once the \fIaddprinter command\fR has been executed, \fBsmbd\fR will reparse the \fI smb\&.conf\fR to determine if the share defined by the APW exists\&. If the sharename is still invalid, then \fBsmbd \fR will return an ACCESS_DENIED error to the client\&. + + +The "add printer command" program can output a single line of text, which Samba will set as the port the new printer is connected to\&. If this line isn't output, Samba won't reload its printer shares\&. + + +See also \fI deleteprinter command\fR, \fIprinting\fR, \fIshow add printer wizard\fR + + +Default: \fBnone\fR + + +Example: \fBaddprinter command = /usr/bin/addprinter\fR + + +.TP +add share command (G) +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIadd share command\fR is used to define an external program or script which will add a new service definition to \fIsmb\&.conf\fR\&. In order to successfully execute the \fIadd share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&. + + +When executed, \fBsmbd\fR will automatically invoke the \fIadd share command\fR with four parameters\&. + + +\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&. + +\fIshareName\fR - the name of the new share\&. + +\fIpathName\fR - path to an **existing** directory on disk\&. + +\fIcomment\fR - comment string to associate with the new share\&. + +This parameter is only used for add file shares\&. To add printer shares, see the \fIaddprinter command\fR\&. + + +See also \fIchange share command\fR, \fIdelete share command\fR\&. + + +Default: \fBnone\fR + + +Example: \fBadd share command = /usr/local/bin/addshare\fR + + +.TP +add user script (G) +This is the full pathname to a script that will be run \fBAS ROOT\fR by \fBsmbd\fR(8) under special circumstances described below\&. + + +Normally, a Samba server requires that UNIX users are created for all users accessing files on this server\&. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task\&. This option allows smbd to create the required UNIX users \fBON DEMAND\fR when a user accesses the Samba server\&. + + +In order to use this option, \fBsmbd\fR(8) must \fBNOT\fR be set to \fIsecurity = share\fR and \fIadd user script\fR must be set to a full pathname for a script that will create a UNIX user given one argument of \fI%u\fR, which expands into the UNIX user name to create\&. + + +When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time, \fBsmbd\fR(8) contacts the \fIpassword server\fR and attempts to authenticate the given user with the given password\&. If the authentication succeeds then \fBsmbd\fR attempts to find a UNIX user in the UNIX password database to map the Windows user into\&. If this lookup fails, and \fIadd user script \fR is set then \fBsmbd\fR will call the specified script \fBAS ROOT\fR, expanding any \fI%u\fR argument to be the user name to create\&. + + +If this script successfully creates the user then \fBsmbd \fR will continue on as though the UNIX user already existed\&. In this way, UNIX users are dynamically created to match existing Windows NT accounts\&. + + +See also \fI security\fR, \fIpassword server\fR, \fIdelete user script\fR\&. + + +Default: \fBadd user script = \fR + + +Example: \fBadd user script = /usr/local/samba/bin/add_user %u\fR + + +.TP +add user to group script (G) +Full path to the script that will be called when a user is added to a group using the Windows NT domain administration tools\&. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR\&. Any \fI%g\fR will be replaced with the group name and any \fI%u\fR will be replaced with the user name\&. + + +Default: \fBadd user to group script = \fR + + +Example: \fBadd user to group script = /usr/sbin/adduser %u %g\fR + + +.TP +admin users (S) +This is a list of users who will be granted administrative privileges on the share\&. This means that they will do all file operations as the super-user (root)\&. + + +You should use this option very carefully, as any user in this list will be able to do anything they like on the share, irrespective of file permissions\&. + + +Default: \fBno admin users\fR + + +Example: \fBadmin users = jason\fR + + +.TP +ads server (G) +If this option is specified, samba does not try to figure out what ads server to use itself, but uses the specified ads server\&. Either one DNS name or IP address can be used\&. + + +Default: \fBads server = \fR + + +Example: \fBads server = 192.168.1.2\fR + + +.TP +algorithmic rid base (G) +This determines how Samba will use its algorithmic mapping from uids/gid to the RIDs needed to construct NT Security Identifiers\&. + + +Setting this option to a larger value could be useful to sites transitioning from WinNT and Win2k, as existing user and group rids would otherwise clash with sytem users etc\&. + + +All UIDs and GIDs must be able to be resolved into SIDs for the correct operation of ACLs on the server\&. As such the algorithmic mapping can't be 'turned off', but pushing it 'out of the way' should resolve the issues\&. Users and groups can then be assigned 'low' RIDs in arbitary-rid supporting backends\&. + + +Default: \fBalgorithmic rid base = 1000\fR + + +Example: \fBalgorithmic rid base = 100000\fR + + +.TP +allow hosts (S) +Synonym for \fIhosts allow\fR\&. + + +.TP +allow trusted domains (G) +This option only takes effect when the \fIsecurity\fR option is set to \fBserver\fR or \fBdomain\fR\&. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication\&. + + +This is useful if you only want your Samba server to serve resources to users in the domain it is a member of\&. As an example, suppose that there are two domains DOMA and DOMB\&. DOMB is trusted by DOMA, which contains the Samba server\&. Under normal circumstances, a user with an account in DOMB can then access the resources of a UNIX account with the same account name on the Samba server even if they do not have an account in DOMA\&. This can make implementing a security boundary difficult\&. + + +Default: \fBallow trusted domains = yes\fR + + +.TP +announce as (G) +This specifies what type of server \fBnmbd\fR(8) will announce itself as, to a network neighborhood browse list\&. By default this is set to Windows NT\&. The valid options are : "NT Server" (which can also be written as "NT"), "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, Windows NT Workstation, Windows 95 and Windows for Workgroups respectively\&. Do not change this parameter unless you have a specific need to stop Samba appearing as an NT server as this may prevent Samba servers from participating as browser servers correctly\&. + + +Default: \fBannounce as = NT Server\fR + + +Example: \fBannounce as = Win95\fR + + +.TP +announce version (G) +This specifies the major and minor version numbers that nmbd will use when announcing itself as a server\&. The default is 4\&.9\&. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server\&. + + +Default: \fBannounce version = 4.9\fR + + +Example: \fBannounce version = 2.0\fR + + +.TP +auth methods (G) +This option allows the administrator to chose what authentication methods \fBsmbd\fR will use when authenticating a user\&. This option defaults to sensible values based on \fIsecurity\fR\&. + + +Each entry in the list attempts to authenticate the user in turn, until the user authenticates\&. In practice only one method will ever actually be able to complete the authentication\&. + + +Default: \fBauth methods = \fR + + +Example: \fBauth methods = guest sam ntdomain\fR + + +.TP +auto services (G) +This is a synonym for the \fIpreload\fR\&. + + +.TP +available (S) +This parameter lets you "turn off" a service\&. If \fIavailable = no\fR, then \fBALL\fR attempts to connect to the service will fail\&. Such failures are logged\&. + + +Default: \fBavailable = yes\fR + + +.TP +bind interfaces only (G) +This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests\&. It affects file service \fBsmbd\fR(8) and name service \fBnmbd\fR(8) in a slightly different ways\&. + + +For name service it causes \fBnmbd\fR to bind to ports 137 and 138 on the interfaces listed in the interfaces parameter\&. \fBnmbd\fR also binds to the "all addresses" interface (0\&.0\&.0\&.0) on ports 137 and 138 for the purposes of reading broadcast messages\&. If this option is not set then \fBnmbd\fR will service name requests on all of these sockets\&. If \fIbind interfaces only\fR is set then \fBnmbd\fR will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the \fIinterfaces\fR parameter list\&. As unicast packets are received on the other sockets it allows \fBnmbd\fR to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the \fIinterfaces\fR list\&. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for \fBnmbd\fR\&. + + +For file service it causes \fBsmbd\fR(8) to bind only to the interface list given in the interfaces parameter\&. This restricts the networks that \fBsmbd\fR will serve to packets coming in those interfaces\&. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non-permanent interfaces\&. + + +If \fIbind interfaces only\fR is set then unless the network address \fB127\&.0\&.0\&.1\fR is added to the \fIinterfaces\fR parameter list \fBsmbpasswd\fR(8) and \fBswat\fR(8) may not work as expected due to the reasons covered below\&. + + +To change a users SMB password, the \fBsmbpasswd\fR by default connects to the \fBlocalhost - 127\&.0\&.0\&.1\fR address as an SMB client to issue the password change request\&. If \fIbind interfaces only\fR is set then unless the network address \fB127\&.0\&.0\&.1\fR is added to the \fIinterfaces\fR parameter list then \fB smbpasswd\fR will fail to connect in it's default mode\&. \fBsmbpasswd\fR can be forced to use the primary IP interface of the local host by using its \fBsmbpasswd\fR(8) \fI-r remote machine\fR parameter, with \fIremote machine\fR set to the IP name of the primary interface of the local host\&. + + +The \fBswat\fR status page tries to connect with \fBsmbd\fR and \fBnmbd\fR at the address \fB127\&.0\&.0\&.1\fR to determine if they are running\&. Not adding \fB127\&.0\&.0\&.1\fR will cause \fB smbd\fR and \fBnmbd\fR to always show "not running" even if they really are\&. This can prevent \fB swat\fR from starting/stopping/restarting \fBsmbd\fR and \fBnmbd\fR\&. + + +Default: \fBbind interfaces only = no\fR + + +.TP +blocking locks (S) +This parameter controls the behavior of \fBsmbd\fR(8) when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it\&. + + +If this parameter is set and the lock range requested cannot be immediately satisfied, samba will internally queue the lock request, and periodically attempt to obtain the lock until the timeout period expires\&. + + +If this parameter is set to \fBno\fR, then samba will behave as previous versions of Samba would and will fail the lock request immediately if the lock range cannot be obtained\&. + + +Default: \fBblocking locks = yes\fR + + +.TP +block size (S) +This parameter controls the behavior of \fBsmbd\fR(8) when reporting disk free sizes\&. By default, this reports a disk block size of 1024 bytes\&. + + +Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed\&. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re-compiling the code\&. As this is an experimental option it may be removed in a future release\&. + + +Changing this option does not change the disk free reporting size, just the block size unit reported to the client\&. + + +.TP +browsable (S) +See the \fIbrowseable\fR\&. + + +.TP +browseable (S) +This controls whether this share is seen in the list of available shares in a net view and in the browse list\&. + + +Default: \fBbrowseable = yes\fR + + +.TP +browse list (G) +This controls whether \fBsmbd\fR(8) will serve a browse list to a client doing a \fBNetServerEnum\fR call\&. Normally set to \fByes\fR\&. You should never need to change this\&. + + +Default: \fBbrowse list = yes\fR + + +.TP +case sensitive (S) +See the discussion in the section NAME MANGLING\&. + + +Default: \fBcase sensitive = no\fR + + +.TP +casesignames (S) +Synonym for case sensitive\&. + + +.TP +change notify timeout (G) +This SMB allows a client to tell a server to "watch" a particular directory for any changes and only reply to the SMB request when a change has occurred\&. Such constant scanning of a directory is expensive under UNIX, hence an \fBsmbd\fR(8) daemon only performs such a scan on each requested directory once every \fIchange notify timeout\fR seconds\&. + + +Default: \fBchange notify timeout = 60\fR + + +Example: \fBchange notify timeout = 300\fR + + +Would change the scan time to every 5 minutes\&. + + +.TP +change share command (G) +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIchange share command\fR is used to define an external program or script which will modify an existing service definition in \fIsmb\&.conf\fR\&. In order to successfully execute the \fIchange share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&. + + +When executed, \fBsmbd\fR will automatically invoke the \fIchange share command\fR with four parameters\&. + + +\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&. + +\fIshareName\fR - the name of the new share\&. + +\fIpathName\fR - path to an **existing** directory on disk\&. + +\fIcomment\fR - comment string to associate with the new share\&. + +This parameter is only used modify existing file shares definitions\&. To modify printer shares, use the "Printers\&.\&.\&." folder as seen when browsing the Samba host\&. + + +See also \fIadd share command\fR, \fIdelete share command\fR\&. + + +Default: \fBnone\fR + + +Example: \fBchange share command = /usr/local/bin/addshare\fR + + +.TP +comment (S) +This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via \fBnet view\fR to list what shares are available\&. + + +If you want to set the string that is displayed next to the machine name then see the \fI server string\fR parameter\&. + + +Default: \fBNo comment string\fR + + +Example: \fBcomment = Fred's Files\fR + + +.TP +config file (G) +This allows you to override the config file to use, instead of the default (usually \fIsmb\&.conf\fR)\&. There is a chicken and egg problem here as this option is set in the config file! + + +For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file\&. + + +This option takes the usual substitutions, which can be very useful\&. + + +If the config file doesn't exist then it won't be loaded (allowing you to special case the config files of just a few clients)\&. + + +Example: \fBconfig file = /usr/local/samba/lib/smb.conf.%m\fR + + +.TP +copy (S) +This parameter allows you to "clone" service entries\&. The specified service is simply duplicated under the current service's name\&. Any parameters specified in the current section will override those in the section being copied\&. + + +This feature lets you set up a 'template' service and create similar services easily\&. Note that the service being copied must occur earlier in the configuration file than the service doing the copying\&. + + +Default: \fBno value\fR + + +Example: \fBcopy = otherservice\fR + + +.TP +create mask (S) +A synonym for this parameter is \fIcreate mode\fR \&. + + +When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter\&. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file\&. Any bit \fBnot\fR set here will be removed from the modes set on a file when it is created\&. + + +The default value of this parameter removes the 'group' and 'other' write and execute bits from the UNIX modes\&. + + +Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the \fIforce create mode\fR parameter which is set to 000 by default\&. + + +This parameter does not affect directory modes\&. See the parameter \fIdirectory mode \fR for details\&. + + +See also the \fIforce create mode\fR parameter for forcing particular mode bits to be set on created files\&. See also the \fIdirectory mode\fR parameter for masking mode bits on created directories\&. See also the \fIinherit permissions\fR parameter\&. + + +Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\&. If the administrator wishes to enforce a mask on access control lists also, they need to set the \fIsecurity mask\fR\&. + + +Default: \fBcreate mask = 0744\fR + + +Example: \fBcreate mask = 0775\fR + + +.TP +create mode (S) +This is a synonym for \fI create mask\fR\&. + + +.TP +csc policy (S) +This stands for \fBclient-side caching policy\fR, and specifies how clients capable of offline caching will cache the files in the share\&. The valid values are: manual, documents, programs, disable\&. + + +These values correspond to those used on Windows servers\&. + + +For example, shares containing roaming profiles can have offline caching disabled using \fBcsc policy = disable\fR\&. + + +Default: \fBcsc policy = manual\fR + + +Example: \fBcsc policy = programs\fR + + +.TP +dead time (G) +The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected\&. The deadtime only takes effect if the number of open files is zero\&. + + +This is useful to stop a server's resources being exhausted by a large number of inactive connections\&. + + +Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users\&. + + +Using this parameter with a timeout of a few minutes is recommended for most systems\&. + + +A deadtime of zero indicates that no auto-disconnection should be performed\&. + + +Default: \fBdeadtime = 0\fR + + +Example: \fBdeadtime = 15\fR + + +.TP +debug hires timestamp (G) +Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp message header when turned on\&. + + +Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&. + + +Default: \fBdebug hires timestamp = no\fR + + +.TP +debug level (G) +Synonym for \fI log level\fR\&. + + +.TP +debug pid (G) +When using only one log file for more then one forked \fBsmbd\fR(8)-process there may be hard to follow which process outputs which message\&. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on\&. + + +Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&. + + +Default: \fBdebug pid = no\fR + + +.TP +debug timestamp (G) +Samba debug log messages are timestamped by default\&. If you are running at a high \fIdebug level\fR these timestamps can be distracting\&. This boolean parameter allows timestamping to be turned off\&. + + +Default: \fBdebug timestamp = yes\fR + + +.TP +debug uid (G) +Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on\&. + + +Note that the parameter \fI debug timestamp\fR must be on for this to have an effect\&. + + +Default: \fBdebug uid = no\fR + + +.TP +default case (S) +See the section on NAME MANGLING\&. Also note the \fIshort preserve case\fR parameter\&. + + +Default: \fBdefault case = lower\fR + + +.TP +default devmode (S) +This parameter is only applicable to printable services\&. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings\&. The device mode can only correctly be generated by the printer driver itself (which can only be executed on a Win32 platform)\&. Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL\&. + + +Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode\&. Certain drivers will do things such as crashing the client's Explorer\&.exe with a NULL devmode\&. However, other printer drivers can cause the client's spooler service (spoolsv\&.exe) to die if the devmode was not created by the driver itself (i\&.e\&. smbd generates a default devmode)\&. + + +This parameter should be used with care and tested with the printer driver in question\&. It is better to leave the device mode to NULL and let the Windows client set the correct values\&. Because drivers do not do this all the time, setting \fBdefault devmode = yes\fR will instruct smbd to generate a default one\&. + + +For more information on Windows NT/2k printing and Device Modes, see the MSDN documentation\&. + + +Default: \fBdefault devmode = no\fR + + +.TP +default service (G) +This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found\&. Note that the square brackets are \fBNOT\fR given in the parameter value (see example below)\&. + + +There is no default value for this parameter\&. If this parameter is not given, attempting to connect to a nonexistent service results in an error\&. + + +Typically the default service would be a \fIguest ok\fR, \fIread-only\fR service\&. + + +Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like \fI%S\fR to make a wildcard service\&. + + +Note also that any "_" characters in the name of the service used in the default service will get mapped to a "/"\&. This allows for interesting things\&. + + +Example: + + +.nf + +[global] + default service = pub + +[pub] + path = /%S +.fi + + +.TP +default (G) +A synonym for \fI default service\fR\&. + + +.TP +delete group script (G) +This is the full pathname to a script that will be run \fBAS ROOT\fR \fBsmbd\fR(8) when a group is requested to be deleted\&. It will expand any \fI%g\fR to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&. + + +.TP +deleteprinter command (G) +With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2\&.2, it is now possible to delete printer at run time by issuing the DeletePrinter() RPC call\&. + + +For a Samba host this means that the printer must be physically deleted from underlying printing system\&. The \fI deleteprinter command\fR defines a script to be run which will perform the necessary operations for removing the printer from the print system and from \fIsmb\&.conf\fR\&. + + +The \fIdeleteprinter command\fR is automatically called with only one parameter: \fI "printer name"\fR\&. + + +Once the \fIdeleteprinter command\fR has been executed, \fBsmbd\fR will reparse the \fI smb\&.conf\fR to associated printer no longer exists\&. If the sharename is still valid, then \fBsmbd \fR will return an ACCESS_DENIED error to the client\&. + + +See also \fI addprinter command\fR, \fIprinting\fR, \fIshow add printer wizard\fR + + +Default: \fBnone\fR + + +Example: \fBdeleteprinter command = /usr/bin/removeprinter\fR + + +.TP +delete readonly (S) +This parameter allows readonly files to be deleted\&. This is not normal DOS semantics, but is allowed by UNIX\&. + + +This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file\&. + + +Default: \fBdelete readonly = no\fR + + +.TP +delete share command (G) +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The \fIdelete share command\fR is used to define an external program or script which will remove an existing service definition from \fIsmb\&.conf\fR\&. In order to successfully execute the \fIdelete share command\fR, \fBsmbd\fR requires that the administrator be connected using a root account (i\&.e\&. uid == 0)\&. + + +When executed, \fBsmbd\fR will automatically invoke the \fIdelete share command\fR with two parameters\&. + + +\fIconfigFile\fR - the location of the global \fIsmb\&.conf\fR file\&. + +\fIshareName\fR - the name of the existing service\&. + +This parameter is only used to remove file shares\&. To delete printer shares, see the \fIdeleteprinter command\fR\&. + + +See also \fIadd share command\fR, \fIchange share command\fR\&. + + +Default: \fBnone\fR + + +Example: \fBdelete share command = /usr/local/bin/delshare\fR + + +.TP +delete user from group script (G) +Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools\&. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR\&. Any \fI%g\fR will be replaced with the group name and any \fI%u\fR will be replaced with the user name\&. + + +Default: \fBdelete user from group script = \fR + + +Example: \fBdelete user from group script = /usr/sbin/deluser %u %g\fR + + +.TP +delete user script (G) +This is the full pathname to a script that will be run by \fBsmbd\fR(8) when managing users with remote RPC (NT) tools\&. + + +This script is called when a remote client removes a user from the server, normally using 'User Manager for Domains' or \fBrpcclient\fR\&. + + +This script should delete the given UNIX username\&. + + +Default: \fBdelete user script = \fR + + +Example: \fBdelete user script = /usr/local/samba/bin/del_user %u\fR + + +.TP +delete veto files (S) +This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the \fIveto files\fR option)\&. If this option is set to \fBno\fR (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail\&. This is usually what you want\&. + + +If this option is set to \fByes\fR, then Samba will attempt to recursively delete any files and directories within the vetoed directory\&. This can be useful for integration with file serving systems such as NetAtalk which create meta-files within directories you might normally veto DOS/Windows users from seeing (e\&.g\&. \fI\&.AppleDouble\fR) + + +Setting \fBdelete veto files = yes\fR allows these directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so)\&. + + +See also the \fIveto files\fR parameter\&. + + +Default: \fBdelete veto files = no\fR + + +.TP +deny hosts (S) +Synonym for \fIhosts deny\fR\&. + + +.TP +dfree command (G) +The \fIdfree command\fR setting should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&. + + +This setting allows the replacement of the internal routines to calculate the total disk space and amount available with an external routine\&. The example below gives a possible script that might fulfill this function\&. + + +The external program will be passed a single parameter indicating a directory in the filesystem being queried\&. This will typically consist of the string \fI\&./\fR\&. The script should return two integers in ASCII\&. The first should be the total disk space in blocks, and the second should be the number of available blocks\&. An optional third return value can give the block size in bytes\&. The default blocksize is 1024 bytes\&. + + +Note: Your script should \fBNOT\fR be setuid or setgid and should be owned by (and writeable only by) root! + + +Default: \fBBy default internal routines for determining the disk capacity and remaining space will be used\&. \fR + + +Example: \fBdfree command = /usr/local/samba/bin/dfree\fR + + +Where the script dfree (which must be made executable) could be: + + +.nf + +#!/bin/sh +df $1 | tail -1 | awk '{print $2" "$4}' +.fi + + +or perhaps (on Sys V based systems): + + +.nf + +#!/bin/sh +/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' +.fi + + +Note that you may have to replace the command names with full path names on some systems\&. + + +.TP +directory mask (S) +This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&. + + +When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter\&. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a directory\&. Any bit \fBnot\fR set here will be removed from the modes set on a directory when it is created\&. + + +The default value of this parameter removes the 'group' and 'other' write bits from the UNIX mode, allowing only the user who owns the directory to modify it\&. + + +Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the \fIforce directory mode\fR parameter\&. This parameter is set to 000 by default (i\&.e\&. no extra mode bits are added)\&. + + +Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\&. If the administrator wishes to enforce a mask on access control lists also, they need to set the \fIdirectory security mask\fR\&. + + +See the \fIforce directory mode\fR parameter to cause particular mode bits to always be set on created directories\&. + + +See also the \fIcreate mode \fR parameter for masking mode bits on created files, and the \fIdirectory security mask\fR parameter\&. + + +Also refer to the \fI inherit permissions\fR parameter\&. + + +Default: \fBdirectory mask = 0755\fR + + +Example: \fBdirectory mask = 0775\fR + + +.TP +directory mode (S) +Synonym for \fI directory mask\fR + + +.TP +directory security mask (S) +This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&. + + +This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&. + + +If not set explicitly this parameter is set to 0777 meaning a user is allowed to modify all the user/group/world permissions on a directory\&. + + +\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it as the default of \fB0777\fR\&. + + +See also the \fI force directory security mode\fR, \fIsecurity mask\fR, \fIforce security mode \fR parameters\&. + + +Default: \fBdirectory security mask = 0777\fR + + +Example: \fBdirectory security mask = 0700\fR + + +.TP +directory (S) +Synonym for \fIpath\fR\&. + + +.TP +disable netbios (G) +Enabling this parameter will disable netbios support in Samba\&. Netbios is the only available form of browsing in all windows versions except for 2000 and XP\&. + + +Note that clients that only support netbios won't be able to see your samba server when netbios support is disabled\&. + +Default: \fBdisable netbios = no\fR + + +Example: \fBdisable netbios = yes\fR + + +.TP +disable spoolss (G) +Enabling this parameter will disable Samba's support for the SPOOLSS set of MS-RPC's and will yield identical behavior as Samba 2\&.0\&.x\&. Windows NT/2000 clients will downgrade to using Lanman style printing commands\&. Windows 9x/ME will be uneffected by the parameter\&. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window\&. It will also disable the capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand\&. \fBBe very careful about enabling this parameter\&.\fR + + +See also use client driver + + +Default : \fBdisable spoolss = no\fR + + +.TP +display charset (G) +Specifies the charset that samba will use to print messages to stdout and stderr and SWAT will use\&. Should generally be the same as the \fBunix charset\fR\&. + + +Default: \fBdisplay charset = ASCII\fR + + +Example: \fBdisplay charset = UTF8\fR + + +.TP +dns proxy (G) +Specifies that \fBnmbd\fR(8) when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name-querying client\&. + + +Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum\&. + + +\fBnmbd\fR spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action\&. + + +See also the parameter \fI wins support\fR\&. + + +Default: \fBdns proxy = yes\fR + + +.TP +domain logons (G) +If set to \fByes\fR, the Samba server will serve Windows 95/98 Domain logons for the \fIworkgroup\fR it is in\&. Samba 2\&.2 has limited capability to act as a domain controller for Windows NT 4 Domains\&. For more details on setting up this feature see the Samba-PDC-HOWTO included in the Samba documentation\&. + + +Default: \fBdomain logons = no\fR + + +.TP +domain master (G) +Tell \fBsmbd\fR(8) to enable WAN-wide browse list collation\&. Setting this option causes \fBnmbd\fR to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given \fIworkgroup\fR\&. Local master browsers in the same \fIworkgroup\fR on broadcast-isolated subnets will give this \fBnmbd\fR their local browse lists, and then ask \fBsmbd\fR(8) for a complete copy of the browse list for the whole wide area network\&. Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet\&. + + +Note that Windows NT Primary Domain Controllers expect to be able to claim this \fIworkgroup\fR specific special NetBIOS name that identifies them as domain master browsers for that \fIworkgroup\fR by default (i\&.e\&. there is no way to prevent a Windows NT PDC from attempting to do this)\&. This means that if this parameter is set and \fBnmbd\fR claims the special name for a \fIworkgroup\fR before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail\&. + + +If \fBdomain logons = yes\fR , then the default behavior is to enable the \fIdomain master\fR parameter\&. If \fIdomain logons\fR is not enabled (the default setting), then neither will \fIdomain master\fR be enabled by default\&. + + +Default: \fBdomain master = auto\fR + + +.TP +dont descend (S) +There are certain directories on some systems (e\&.g\&., the \fI/proc\fR tree under Linux) that are either not of interest to clients or are infinitely deep (recursive)\&. This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty\&. + + +Note that Samba can be very fussy about the exact format of the "dont descend" entries\&. For example you may need \fI \&./proc\fR instead of just \fI/proc\fR\&. Experimentation is the best policy :-) + + +Default: \fBnone (i\&.e\&., all directories are OK to descend)\fR + + +Example: \fBdont descend = /proc,/dev\fR + + +.TP +dos charset (G) +DOS SMB clients assume the server has the same charset as they do\&. This option specifies which charset Samba should talk to DOS clients\&. + + +The default depends on which charsets you have installed\&. Samba tries to use charset 850 but falls back to ASCII in case it is not available\&. Run \fBtestparm\fR(1) to check the default on your system\&. + + +.TP +dos filemode (S) +The default behavior in Samba is to provide UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it\&. However, this behavior is often confusing to DOS/Windows users\&. Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions on it\&. Note that a user belonging to the group owning the file will not be allowed to change permissions if the group is only granted read access\&. Ownership of the file/directory is not changed, only the permissions are modified\&. + + +Default: \fBdos filemode = no\fR + + +.TP +dos filetime resolution (S) +Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds\&. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to \fBsmbd\fR(8)\&. + + +This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. If oplocks are enabled on a share, Visual C++ uses two different time reading calls to check if a file has changed since it was last read\&. One of these calls uses a one-second granularity, the other uses a two second granularity\&. As the two second call rounds any odd second down, then if the file has a timestamp of an odd number of seconds then the two timestamps will not match and Visual C++ will keep reporting the file has changed\&. Setting this option causes the two timestamps to match, and Visual C++ is happy\&. + + +Default: \fBdos filetime resolution = no\fR + + +.TP +dos filetimes (S) +Under DOS and Windows, if a user can write to a file they can change the timestamp on it\&. Under POSIX semantics, only the owner of the file or root may change the timestamp\&. By default, Samba runs with POSIX semantics and refuses to change the timestamp on a file if the user \fBsmbd\fR is acting on behalf of is not the file owner\&. Setting this option to \fB yes\fR allows DOS semantics and \fBsmbd\fR(8) will change the file timestamp as DOS requires\&. + + +Default: \fBdos filetimes = no\fR + + +.TP +encrypt passwords (G) +This boolean controls whether encrypted passwords will be negotiated with the client\&. Note that Windows NT 4\&.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed\&. To use encrypted passwords in Samba see the chapter "User Database" in the Samba HOWTO Collection\&. + + +In order for encrypted passwords to work correctly \fBsmbd\fR(8) must either have access to a local \fBsmbpasswd\fR(5) file (see the \fBsmbpasswd\fR(8) program for information on how to set up and maintain this file), or set the security = [server|domain|ads] parameter which causes \fBsmbd\fR to authenticate against another server\&. + + +Default: \fBencrypt passwords = yes\fR + + +.TP +enhanced browsing (G) +This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations\&. + + +The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs\&. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs\&. + + +You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists\&. Due to the restrictions of the browse protocols these enhancements can cause a empty workgroup to stay around forever which can be annoying\&. + + +In general you should leave this option enabled as it makes cross-subnet browse propagation much more reliable\&. + + +Default: \fBenhanced browsing = yes\fR + + +.TP +enumports command (G) +The concept of a "port" is fairly foreign to UNIX hosts\&. Under Windows NT/2000 print servers, a port is associated with a port monitor and generally takes the form of a local port (i\&.e\&. LPT1:, COM1:, FILE:) or a remote port (i\&.e\&. LPD Port Monitor, etc\&.\&.\&.)\&. By default, Samba has only one port defined--\fB"Samba Printer Port"\fR\&. Under Windows NT/2000, all printers must have a valid port name\&. If you wish to have a list of ports displayed (\fBsmbd \fR does not use a port name for anything) other than the default \fB"Samba Printer Port"\fR, you can define \fIenumports command\fR to point to a program which should generate a list of ports, one per line, to standard output\&. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC\&. + + +Default: \fBno enumports command\fR + + +Example: \fBenumports command = /usr/bin/listports\fR + + +.TP +exec (S) +This is a synonym for \fIpreexec\fR\&. + + +.TP +fake directory create times (S) +NTFS and Windows VFAT file systems keep a create time for all files and directories\&. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep\&. Setting this parameter for a share causes Samba to always report midnight 1-1-1980 as the create time for directories\&. + + +This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. Visual C++ generated makefiles have the object directory as a dependency for each object file, and a make rule to create the directory\&. Also, when NMAKE compares timestamps it uses the creation time when examining a directory\&. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains\&. + + +However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or or deleted in the directory\&. NMAKE finds all object files in the object directory\&. The timestamp of the last one built is then compared to the timestamp of the object directory\&. If the directory's timestamp if newer, then all object files will be rebuilt\&. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected\&. + + +Default: \fBfake directory create times = no\fR + + +.TP +fake oplocks (S) +Oplocks are the way that SMB clients get permission from a server to locally cache file operations\&. If a server grants an oplock (opportunistic lock) then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data\&. With some oplock types the client may even cache file open/close operations\&. This can give enormous performance benefits\&. + + +When you set \fBfake oplocks = yes\fR, \fBsmbd\fR(8) will always grant oplock requests no matter how many clients are using the file\&. + + +It is generally much better to use the real \fIoplocks\fR support rather than this parameter\&. + + +If you enable this option on all read-only shares or shares that you know will only be accessed from one client at a time such as physically read-only media like CDROMs, you will see a big performance improvement on many operations\&. If you enable this option on shares where multiple clients may be accessing the files read-write at the same time you can get data corruption\&. Use this option carefully! + + +Default: \fBfake oplocks = no\fR + + +.TP +follow symlinks (S) +This parameter allows the Samba administrator to stop \fBsmbd\fR(8) from following symbolic links in a particular share\&. Setting this parameter to \fBno\fR prevents any file or directory that is a symbolic link from being followed (the user will get an error)\&. This option is very useful to stop users from adding a symbolic link to \fI/etc/passwd\fR in their home directory for instance\&. However it will slow filename lookups down slightly\&. + + +This option is enabled (i\&.e\&. \fBsmbd\fR will follow symbolic links) by default\&. + + +Default: \fBfollow symlinks = yes\fR + + +.TP +force create mode (S) +This parameter specifies a set of UNIX mode bit permissions that will \fBalways\fR be set on a file created by Samba\&. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its permissions changed\&. The default for this parameter is (in octal) 000\&. The modes in this parameter are bitwise 'OR'ed onto the file mode after the mask set in the \fIcreate mask\fR parameter is applied\&. + + +See also the parameter \fIcreate mask\fR for details on masking mode bits on files\&. + + +See also the \fIinherit permissions\fR parameter\&. + + +Default: \fBforce create mode = 000\fR + + +Example: \fBforce create mode = 0755\fR + + +would force all created files to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'\&. + + +.TP +force directory mode (S) +This parameter specifies a set of UNIX mode bit permissions that will \fBalways\fR be set on a directory created by Samba\&. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created\&. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory\&. This operation is done after the mode mask in the parameter \fIdirectory mask\fR is applied\&. + + +See also the parameter \fI directory mask\fR for details on masking mode bits on created directories\&. + + +See also the \fI inherit permissions\fR parameter\&. + + +Default: \fBforce directory mode = 000\fR + + +Example: \fBforce directory mode = 0755\fR + + +would force all created directories to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'\&. + + +.TP +force directory security mode (S) +This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\&. + + +This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a directory, the user has always set to be 'on'\&. + + +If not set explicitly this parameter is 000, which allows a user to modify all the user/group/world permissions on a directory without restrictions\&. + + +\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set as 0000\&. + + +See also the \fI directory security mask\fR, \fIsecurity mask\fR, \fIforce security mode \fR parameters\&. + + +Default: \fBforce directory security mode = 0\fR + + +Example: \fBforce directory security mode = 700\fR + + +.TP +force group (S) +This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service\&. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking\&. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files\&. + + +In Samba 2\&.0\&.5 and above this parameter has extended functionality in the following way\&. If the group name listed here has a '+' character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group\&. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group\&. This gives a finer granularity of ownership assignment\&. For example, the setting \fIforce group = +sys\fR means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share\&. All other users will retain their ordinary primary group\&. + + +If the \fIforce user\fR parameter is also set the group specified in \fIforce group\fR will override the primary group set in \fIforce user\fR\&. + + +See also \fIforce user\fR\&. + + +Default: \fBno forced group\fR + + +Example: \fBforce group = agroup\fR + + +.TP +force security mode (S) +This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&. + + +This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\&. Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be 'on'\&. + + +If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world permissions on a file, with no restrictions\&. + + +\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave this set to 0000\&. + + +See also the \fI force directory security mode\fR, \fIdirectory security mask\fR, \fI security mask\fR parameters\&. + + +Default: \fBforce security mode = 0\fR + + +Example: \fBforce security mode = 700\fR + + +.TP +force user (S) +This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service\&. This is useful for sharing files\&. You should also use it carefully as using it incorrectly can cause security problems\&. + + +This user name only gets used once a connection is established\&. Thus clients still need to connect as a valid user and supply a valid password\&. Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as\&. This can be very useful\&. + + +In Samba 2\&.0\&.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity\&. Prior to 2\&.0\&.5 the primary group was left as the primary group of the connecting user (this was a bug)\&. + + +See also \fIforce group\fR + + +Default: \fBno forced user\fR + + +Example: \fBforce user = auser\fR + + +.TP +fstype (S) +This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by \fBsmbd\fR(8) when a client queries the filesystem type for a share\&. The default type is \fBNTFS\fR for compatibility with Windows NT but this can be changed to other strings such as \fBSamba\fR or \fBFAT \fR if required\&. + + +Default: \fBfstype = NTFS\fR + + +Example: \fBfstype = Samba\fR + + +.TP +getwd cache (G) +This is a tuning option\&. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls\&. This can have a significant impact on performance, especially when the \fIwide links\fR parameter is set to \fBno\fR\&. + + +Default: \fBgetwd cache = yes\fR + + +.TP +group (S) +Synonym for \fIforce group\fR\&. + + +.TP +guest account (G,S) +This is a username which will be used for access to services which are specified as \fI guest ok\fR (see below)\&. Whatever privileges this user has will be available to any client connecting to the guest service\&. Typically this user will exist in the password file, but will not have a valid login\&. The user account "ftp" is often a good choice for this parameter\&. If a username is specified in a given service, the specified username overrides this one\&. + + +One some systems the default guest account "nobody" may not be able to print\&. Use another account in this case\&. You should test this by trying to log in as your guest user (perhaps by using the \fBsu -\fR command) and trying to print using the system print command such as \fBlpr(1)\fR or \fB lp(1)\fR\&. + + +This parameter does not accept % macros, because many parts of the system require this value to be constant for correct operation\&. + + +Default: \fBspecified at compile time, usually "nobody"\fR + + +Example: \fBguest account = ftp\fR + + +.TP +guest ok (S) +If this parameter is \fByes\fR for a service, then no password is required to connect to the service\&. Privileges will be those of the \fI guest account\fR\&. + + +This paramater nullifies the benifits of setting \fIrestrict anonymous\fR = 2 + + +See the section below on \fI security\fR for more information about this option\&. + + +Default: \fBguest ok = no\fR + + +.TP +guest only (S) +If this parameter is \fByes\fR for a service, then only guest connections to the service are permitted\&. This parameter will have no effect if \fIguest ok\fR is not set for the service\&. + + +See the section below on \fI security\fR for more information about this option\&. + + +Default: \fBguest only = no\fR + + +.TP +hide dot files (S) +This is a boolean parameter that controls whether files starting with a dot appear as hidden files\&. + + +Default: \fBhide dot files = yes\fR + + +.TP +hide files (S) +This is a list of files or directories that are not visible but are accessible\&. The DOS 'hidden' attribute is applied to any files or directories that match\&. + + +Each entry in the list must be separated by a '/', which allows spaces to be included in the entry\&. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards\&. + + +Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator '/'\&. + + +Note that the case sensitivity option is applicable in hiding files\&. + + +Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned\&. + + +See also \fIhide dot files\fR, \fI veto files\fR and \fIcase sensitive\fR\&. + + +Default: \fBno file are hidden\fR + + +Example: \fBhide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/\fR + + +The above example is based on files that the Macintosh SMB client (DAVE) available from Thursby creates for internal use, and also still hides all files beginning with a dot\&. + + +.TP +hide local users (G) +This parameter toggles the hiding of local UNIX users (root, wheel, floppy, etc) from remote clients\&. + + +Default: \fBhide local users = no\fR + + +.TP +hide special files (S) +This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings\&. + + +Default: \fBhide special files = no\fR + + +.TP +hide unreadable (S) +This parameter prevents clients from seeing the existance of files that cannot be read\&. Defaults to off\&. + + +Default: \fBhide unreadable = no\fR + + +.TP +hide unwriteable files (S) +This parameter prevents clients from seeing the existance of files that cannot be written to\&. Defaults to off\&. Note that unwriteable directories are shown as usual\&. + + +Default: \fBhide unwriteable = no\fR + + +.TP +homedir map (G) +If\fInis homedir \fR is \fByes\fR, and \fBsmbd\fR(8) is also acting as a Win95/98 \fIlogon server\fR then this parameter specifies the NIS (or YP) map from which the server for the user's home directory should be extracted\&. At present, only the Sun auto\&.home map format is understood\&. The form of the map is: + + +\fBusername server:/some/file/system\fR + + +and the program will extract the servername from before the first ':'\&. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\&. + + +A working NIS client is required on the system for this option to work\&. + +See also \fInis homedir\fR , \fIdomain logons\fR \&. + + +Default: \fBhomedir map = \fR + + +Example: \fBhomedir map = amd.homedir\fR + + +.TP +host msdfs (G) +This boolean parameter is only available if Samba has been configured and compiled with the \fB --with-msdfs\fR option\&. If set to \fByes\fR, Samba will act as a Dfs server, and allow Dfs-aware clients to browse Dfs trees hosted on the server\&. + + +See also the \fI msdfs root\fR share level parameter\&. For more information on setting up a Dfs tree on Samba, refer to msdfs_setup\&.html\&. + + +Default: \fBhost msdfs = no\fR + + +.TP +hostname lookups (G) +Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead\&. An example place where hostname lookups are currently used is when checking the \fBhosts deny\fR and \fBhosts allow\fR\&. + + +Default: \fBhostname lookups = yes\fR + + +Example: \fBhostname lookups = no\fR + + +.TP +hosts allow (S) +A synonym for this parameter is \fIallow hosts\fR\&. + + +This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service\&. + + +If specified in the [global] section then it will apply to all services, regardless of whether the individual service has a different setting\&. + + +You can specify the hosts by name or IP number\&. For example, you could restrict access to only the hosts on a Class C subnet with something like \fBallow hosts = 150.203.5. \fR\&. The full syntax of the list is described in the man page \fIhosts_access(5)\fR\&. Note that this man page may not be present on your system, so a brief description will be given here also\&. + + +Note that the localhost address 127\&.0\&.0\&.1 will always be allowed access unless specifically denied by a \fIhosts deny\fR option\&. + + +You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups\&. The \fBEXCEPT\fR keyword can also be used to limit a wildcard list\&. The following examples may provide some help: + + +Example 1: allow all IPs in 150\&.203\&.*\&.*; except one + + +\fBhosts allow = 150.203. EXCEPT 150.203.6.66\fR + + +Example 2: allow hosts that match the given network/netmask + + +\fBhosts allow = 150.203.15.0/255.255.255.0\fR + + +Example 3: allow a couple of hosts + + +\fBhosts allow = lapland, arvidsjaur\fR + + +Example 4: allow only hosts in NIS netgroup "foonet", but deny access from one particular host + + +\fBhosts allow = @foonet\fR + + +\fBhosts deny = pirate\fR + + +Note that access still requires suitable user-level passwords\&. + +See \fBtestparm\fR(1) for a way of testing your host access to see if it does what you expect\&. + + +Default: \fBnone (i\&.e\&., all hosts permitted access)\fR + + +Example: \fBallow hosts = 150.203.5. myhost.mynet.edu.au\fR + + +.TP +hosts deny (S) +The opposite of \fIhosts allow\fR - hosts listed here are \fBNOT\fR permitted access to services unless the specific services have their own lists to override this one\&. Where the lists conflict, the \fIallow\fR list takes precedence\&. + + +Default: \fBnone (i\&.e\&., no hosts specifically excluded)\fR + + +Example: \fBhosts deny = 150.203.4. badhost.mynet.edu.au\fR + + +.TP +hosts equiv (G) +If this global parameter is a non-null string, it specifies the name of a file to read for the names of hosts and users who will be allowed access without specifying a password\&. + + +This is not be confused with \fIhosts allow\fR which is about hosts access to services and is more useful for guest services\&. \fI hosts equiv\fR may be useful for NT clients which will not supply passwords to Samba\&. + + +The use of \fIhosts equiv \fR can be a major security hole\&. This is because you are trusting the PC to supply the correct username\&. It is very easy to get a PC to supply a false username\&. I recommend that the \fIhosts equiv\fR option be only used if you really know what you are doing, or perhaps on a home network where you trust your spouse and kids\&. And only if you \fBreally\fR trust them :-)\&. + +Default: \fBno host equivalences\fR + + +Example: \fBhosts equiv = /etc/hosts.equiv\fR + + +.TP +include (G) +This allows you to include one config file inside another\&. The file is included literally, as though typed in place\&. + + +It takes the standard substitutions, except \fI%u \fR, \fI%P\fR and \fI%S\fR\&. + + +Default: \fBno file included\fR + + +Example: \fBinclude = /usr/local/samba/lib/admin_smb.conf\fR + + +.TP +inherit acls (S) +This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a subdirectory\&. The default behavior is to use the mode specified when creating the directory\&. Enabling this option sets the mode to 0777, thus guaranteeing that default directory acls are propagated\&. + + +Default: \fBinherit acls = no\fR + + +.TP +inherit permissions (S) +The permissions on new files and directories are normally governed by \fI create mask\fR, \fIdirectory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR but the boolean inherit permissions parameter overrides this\&. + + +New directories inherit the mode of the parent directory, including bits such as setgid\&. + + +New files inherit their read/write bits from the parent directory\&. Their execute bits continue to be determined by \fImap archive\fR , \fImap hidden\fR and \fImap system\fR as usual\&. + + +Note that the setuid bit is \fBnever\fR set via inheritance (the code explicitly prohibits this)\&. + + +This can be particularly useful on large systems with many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user\&. + + +See also \fIcreate mask \fR, \fI directory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR \&. + + +Default: \fBinherit permissions = no\fR + + +.TP +interfaces (G) +This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT traffic\&. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127\&.0\&.0\&.1 that are broadcast capable\&. + + +The option takes a list of interface strings\&. Each string can be in any of the following forms: + + +a network interface name (such as eth0)\&. This may include shell-like wildcards so eth* will match any interface starting with the substring "eth" + +an IP address\&. In this case the netmask is determined from the list of interfaces obtained from the kernel + +an IP/mask pair\&. + +a broadcast/mask pair\&. + +The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form\&. + + +The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms\&. + + +For example, the following line: + + +\fBinterfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0\fR + + +would configure three network interfaces corresponding to the eth0 device and IP addresses 192\&.168\&.2\&.10 and 192\&.168\&.3\&.10\&. The netmasks of the latter two interfaces would be set to 255\&.255\&.255\&.0\&. + + +See also \fIbind interfaces only\fR\&. + + +Default: \fBall active interfaces except 127\&.0\&.0\&.1 that are broadcast capable\fR + + +.TP +invalid users (S) +This is a list of users that should not be allowed to login to this service\&. This is really a \fBparanoid\fR check to absolutely ensure an improper setting does not breach your security\&. + + +A name starting with a '@' is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database\&. + + +A name starting with '+' is interpreted only by looking in the UNIX group database\&. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\&. The characters '+' and '&' may be used at the start of the name in either order so the value \fI+&group\fR means check the UNIX group database, followed by the NIS netgroup database, and the value \fI&+group\fR means check the NIS netgroup database, followed by the UNIX group database (the same as the '@' prefix)\&. + + +The current servicename is substituted for \fI%S\fR\&. This is useful in the [homes] section\&. + + +See also \fIvalid users \fR\&. + + +Default: \fBno invalid users\fR + + +Example: \fBinvalid users = root fred admin @wheel\fR + + +.TP +keepalive (G) +The value of the parameter (an integer) represents the number of seconds between \fIkeepalive\fR packets\&. If this parameter is zero, no keepalive packets will be sent\&. Keepalive packets, if sent, allow the server to tell whether a client is still present and responding\&. + + +Keepalives should, in general, not be needed if the socket being used has the SO_KEEPALIVE attribute set on it (see \fIsocket options\fR)\&. Basically you should only use this option if you strike difficulties\&. + + +Default: \fBkeepalive = 300\fR + + +Example: \fBkeepalive = 600\fR + + +.TP +kernel oplocks (G) +For UNIXes that support kernel based \fIoplocks\fR (currently only IRIX and the Linux 2\&.4 kernel), this parameter allows the use of them to be turned on or off\&. + + +Kernel oplocks support allows Samba \fIoplocks \fR to be broken whenever a local UNIX process or NFS operation accesses a file that \fBsmbd\fR(8) has oplocked\&. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a \fBvery\fR cool feature :-)\&. + + +This parameter defaults to \fBon\fR, but is translated to a no-op on systems that no not have the necessary kernel support\&. You should never need to touch this parameter\&. + + +See also the \fIoplocks\fR and \fIlevel2 oplocks \fR parameters\&. + + +Default: \fBkernel oplocks = yes\fR + + +.TP +lanman auth (G) +This parameter determines whether or not \fBsmbd\fR(8) will attempt to authenticate users using the LANMAN password hash\&. If disabled, only clients which support NT password hashes (e\&.g\&. Windows NT/2000 clients, smbclient, etc\&.\&.\&. but not Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host\&. + + +Default : \fBlanman auth = yes\fR + + +.TP +large readwrite (G) +This parameter determines whether or not \fBsmbd\fR(8) supports the new 64k streaming read and write varient SMB requests introduced with Windows 2000\&. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64-bit capable operating system such as IRIX, Solaris or a Linux 2\&.4 kernel\&. Can improve performance by 10% with Windows 2000 clients\&. Defaults to on\&. Not as tested as some other Samba code paths\&. + + +Default: \fBlarge readwrite = yes\fR + + +.TP +ldap admin dn (G) +The \fIldap admin dn\fR defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information\&. The \fIldap admin dn\fR is used in conjunction with the admin dn password stored in the \fIprivate/secrets\&.tdb\fR file\&. See the \fBsmbpasswd\fR(8) man page for more information on how to accmplish this\&. + + +.TP +ldap delete dn (G) +This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba\&. + + +Default: \fBldap delete dn = no\fR + + +.TP +ldap filter (G) +This parameter specifies the RFC 2254 compliant LDAP search filter\&. The default is to match the login name with the \fBuid\fR attribute for all entries matching the \fBsambaAccount\fR objectclass\&. Note that this filter should only return one entry\&. + + +Default: \fBldap filter = (&(uid=%u)(objectclass=sambaAccount))\fR + + +.TP +ldap machine suffix (G) +It specifies where machines should be added to the ldap tree\&. + + +Default: \fBnone\fR + + +.TP +ldap passwd sync (G) +This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password change via SAMBA\&. + + +The \fIldap passwd sync\fR can be set to one of three values: + + +\fIYes\fR = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time\&. + +\fINo\fR = Update NT and LM passwords and update the pwdLastSet time\&. + +\fIOnly\fR = Only update the LDAP password and let the LDAP server do the rest\&. + +Default: \fBldap passwd sync = no\fR + + +.TP +ldap port (G) +This parameter is only available if Samba has been configure to include the \fB--with-ldapsam\fR option at compile time\&. + + +This option is used to control the tcp port number used to contact the \fIldap server\fR\&. The default is to use the stand LDAPS port 636\&. + + +See Also: ldap ssl + + +Default : \fBldap port = 636 ; if ldap ssl = on\fR + + +Default : \fBldap port = 389 ; if ldap ssl = off\fR + + +.TP +ldap server (G) +This parameter is only available if Samba has been configure to include the \fB--with-ldapsam\fR option at compile time\&. + + +This parameter should contain the FQDN of the ldap directory server which should be queried to locate user account information\&. + + +Default : \fBldap server = localhost\fR + + +.TP +ldap ssl (G) +This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is \fBNOT\fR related to Samba's previous SSL support which was enabled by specifying the \fB--with-ssl\fR option to the \fIconfigure\fR script\&. + + +The \fIldap ssl\fR can be set to one of three values: + + +\fIOff\fR = Never use SSL when querying the directory\&. + +\fIStart_tls\fR = Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server\&. + +\fIOn\fR = Use SSL on the ldaps port when contacting the \fIldap server\fR\&. Only available when the backwards-compatiblity \fB--with-ldapsam\fR option is specified to configure\&. See \fIpassdb backend\fR + +Default : \fBldap ssl = start_tls\fR + + +.TP +ldap suffix (G) +Specifies where user and machine accounts are added to the tree\&. Can be overriden by \fBldap user suffix\fR and \fBldap machine suffix\fR\&. It also used as the base dn for all ldap searches\&. + + +Default: \fBnone\fR + + +.TP +ldap trust ids (G) +Normally, Samba validates each entry in the LDAP server against getpwnam()\&. This allows LDAP to be used for Samba with the unix system using NIS (for example) and also ensures that Samba does not present accounts that do not otherwise exist\&. + + +This option is used to disable this functionality, and instead to rely on the presence of the appropriate attributes in LDAP directly, which can result in a significant performance boost in some situations\&. Setting this option to yes effectivly assumes that the local machine is running \fBnss_ldap\fR against the same LDAP server\&. + + +Default: \fBldap trust ids = No\fR + + +.TP +ldap user suffix (G) +It specifies where users are added to the tree\&. + + +Default: \fBnone\fR + + +.TP +level2 oplocks (S) +This parameter controls whether Samba supports level2 (read-only) oplocks on a share\&. + + +Level2, or read-only oplocks allow Windows NT clients that have an oplock on a file to downgrade from a read-write oplock to a read-only oplock once a second client opens the file (instead of releasing all oplocks on a second open, as in traditional, exclusive oplocks)\&. This allows all openers of the file that support level2 oplocks to cache the file for read-ahead only (ie\&. they may not cache writes or lock requests) and increases performance for many accesses of files that are not commonly written (such as application \&.EXE files)\&. + + +Once one of the clients which have a read-only oplock writes to the file all clients are notified (no reply is needed or waited for) and told to break their oplocks to "none" and delete any read-ahead caches\&. + + +It is recommended that this parameter be turned on to speed access to shared executables\&. + + +For more discussions on level2 oplocks see the CIFS spec\&. + + +Currently, if \fIkernel oplocks\fR are supported then level2 oplocks are not granted (even if this parameter is set to \fByes\fR)\&. Note also, the \fIoplocks\fR parameter must be set to \fByes\fR on this share in order for this parameter to have any effect\&. + + +See also the \fIoplocks\fR and \fIkernel oplocks\fR parameters\&. + + +Default: \fBlevel2 oplocks = yes\fR + + +.TP +lm announce (G) +This parameter determines if \fBnmbd\fR(8) will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list\&. This parameter can have three values, \fByes\fR, \fBno\fR, or \fBauto\fR\&. The default is \fBauto\fR\&. If set to \fBno\fR Samba will never produce these broadcasts\&. If set to \fByes\fR Samba will produce Lanman announce broadcasts at a frequency set by the parameter \fIlm interval\fR\&. If set to \fBauto\fR Samba will not send Lanman announce broadcasts by default but will listen for them\&. If it hears such a broadcast on the wire it will then start sending them at a frequency set by the parameter \fIlm interval\fR\&. + + +See also \fIlm interval\fR\&. + + +Default: \fBlm announce = auto\fR + + +Example: \fBlm announce = yes\fR + + +.TP +lm interval (G) +If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the \fIlm announce\fR parameter) then this parameter defines the frequency in seconds with which they will be made\&. If this is set to zero then no Lanman announcements will be made despite the setting of the \fIlm announce\fR parameter\&. + + +See also \fIlm announce\fR\&. + + +Default: \fBlm interval = 60\fR + + +Example: \fBlm interval = 120\fR + + +.TP +load printers (G) +A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default\&. See the printers section for more details\&. + + +Default: \fBload printers = yes\fR + + +.TP +local master (G) +This option allows \fBnmbd\fR(8) to try and become a local master browser on a subnet\&. If set to \fBno\fR then \fB nmbd\fR will not attempt to become a local master browser on a subnet and will also lose in all browsing elections\&. By default this value is set to \fByes\fR\&. Setting this value to \fByes\fR doesn't mean that Samba will \fBbecome\fR the local master browser on a subnet, just that \fBnmbd\fR will \fBparticipate\fR in elections for local master browser\&. + + +Setting this value to \fBno\fR will cause \fBnmbd\fR \fBnever\fR to become a local master browser\&. + + +Default: \fBlocal master = yes\fR + + +.TP +lock directory (G) +This option specifies the directory where lock files will be placed\&. The lock files are used to implement the \fImax connections\fR option\&. + + +Default: \fBlock directory = ${prefix}/var/locks\fR + + +Example: \fBlock directory = /var/run/samba/locks\fR + + +.TP +lock dir (G) +Synonym for \fI lock directory\fR\&. + + +.TP +locking (S) +This controls whether or not locking will be performed by the server in response to lock requests from the client\&. + + +If \fBlocking = no\fR, all lock and unlock requests will appear to succeed and all lock queries will report that the file in question is available for locking\&. + + +If \fBlocking = yes\fR, real locking will be performed by the server\&. + + +This option \fBmay\fR be useful for read-only filesystems which \fBmay\fR not need locking (such as CDROM drives), although setting this parameter of \fBno\fR is not really recommended even in this case\&. + + +Be careful about disabling locking either globally or in a specific service, as lack of locking may result in data corruption\&. You should never need to set this parameter\&. + + +Default: \fBlocking = yes\fR + + +.TP +lock spin count (G) +This parameter controls the number of times that smbd should attempt to gain a byte range lock on the behalf of a client request\&. Experiments have shown that Windows 2k servers do not reply with a failure if the lock could not be immediately granted, but try a few more times in case the lock could later be aquired\&. This behavior is used to support PC database formats such as MS Access and FoxPro\&. + + +Default: \fBlock spin count = 2\fR + + +.TP +lock spin time (G) +The time in microseconds that smbd should pause before attempting to gain a failed lock\&. See \fIlock spin count\fR for more details\&. + + +Default: \fBlock spin time = 10\fR + + +.TP +log file (G) +This option allows you to override the name of the Samba log file (also known as the debug file)\&. + + +This option takes the standard substitutions, allowing you to have separate log files for each user or machine\&. + + +Example: \fBlog file = /usr/local/samba/var/log.%m\fR + + +.TP +log level (G) +The value of the parameter (a astring) allows the debug level (logging level) to be specified in the \fIsmb\&.conf\fR file\&. This parameter has been extended since the 2\&.2\&.x series, now it allow to specify the debug level for multiple debug classes\&. This is to give greater flexibility in the configuration of the system\&. + + +The default will be the log level specified on the command line or level zero if none was specified\&. + + +Example: \fBlog level = 3 passdb:5 auth:10 winbind:2\fR + + +.TP +logon drive (G) +This parameter specifies the local path to which the home directory will be connected (see \fIlogon home\fR) and is only used by NT Workstations\&. + + +Note that this option is only useful if Samba is set up as a logon server\&. + + +Default: \fBlogon drive = z:\fR + + +Example: \fBlogon drive = h:\fR + + +.TP +logon home (G) +This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC\&. It allows you to do + + +C:\\> \fBNET USE H: /HOME\fR + + +from a command prompt, for example\&. + + +This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. + + +This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user's home directory\&. This is done in the following way: + + +\fBlogon home = \\%N\%U\profile\fR + + +This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request\&. Win9X clients truncate the info to \\\\server\\share when a user does \fBnet use /home\fR but use the whole string when dealing with profiles\&. + + +Note that in prior versions of Samba, the \fIlogon path\fR was returned rather than \fIlogon home\fR\&. This broke \fBnet use /home\fR but allowed profiles outside the home directory\&. The current implementation is correct, and can be used for profiles if you use the above trick\&. + + +This option is only useful if Samba is set up as a logon server\&. + + +Default: \fBlogon home = "\\%N\%U"\fR + + +Example: \fBlogon home = "\\remote_smb_server\%U"\fR + + +.TP +logon path (G) +This parameter specifies the home directory where roaming profiles (NTuser\&.dat etc files for Windows NT) are stored\&. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles\&. To find out how to handle roaming profiles for Win 9X system, see the \fIlogon home\fR parameter\&. + + +This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. It also specifies the directory from which the "Application Data", (\fIdesktop\fR, \fIstart menu\fR, \fInetwork neighborhood\fR, \fIprograms\fR and other folders, and their contents, are loaded and displayed on your Windows NT client\&. + + +The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client\&. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser\&.dat and other directories\&. + + +Thereafter, the directories and any of the contents can, if required, be made read-only\&. It is not advisable that the NTuser\&.dat file be made read-only - rename it to NTuser\&.man to achieve the desired effect (a \fBMAN\fRdatory profile)\&. + + +Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in\&. Therefore, it is vital that the logon path does not include a reference to the homes share (i\&.e\&. setting this parameter to \\%N\\%U\\profile_path will cause problems)\&. + + +This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. + + +Note that this option is only useful if Samba is set up as a logon server\&. + + +Default: \fBlogon path = \\%N\%U\profile\fR + + +Example: \fBlogon path = \\PROFILESERVER\PROFILE\%U\fR + + +.TP +logon script (G) +This parameter specifies the batch file (\&.bat) or NT command file (\&.cmd) to be downloaded and run on a machine when a user successfully logs in\&. The file must contain the DOS style CR/LF line endings\&. Using a DOS-style editor to create the file is recommended\&. + + +The script must be a relative path to the [netlogon] service\&. If the [netlogon] service specifies a \fIpath\fR of \fI/usr/local/samba/netlogon\fR, and \fBlogon script = STARTUP.BAT\fR, then the file that will be downloaded is: + + +\fI/usr/local/samba/netlogon/STARTUP\&.BAT\fR + + +The contents of the batch file are entirely your choice\&. A suggested command would be to add \fBNET TIME \\SERVER /SET /YES\fR, to force every machine to synchronize clocks with the same time server\&. Another use would be to add \fBNET USE U: \\SERVER\UTILS\fR for commonly used utilities, or \fB NET USE Q: \\SERVER\ISO9001_QA\fR for example\&. + + +Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached\&. + + +This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\&. + + +This option is only useful if Samba is set up as a logon server\&. + + +Default: \fBno logon script defined\fR + + +Example: \fBlogon script = scripts\%U.bat\fR + + +.TP +lppause command (S) +This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job\&. + + +This command should be a program or script which takes a printer name and job number to pause the print job\&. One way of implementing this is by using job priorities, where jobs having a too low priority won't be sent to the printer\&. + + +If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&. On HPUX (see \fIprinting=hpux \fR), if the \fI-p%p\fR option is added to the lpq command, the job will show up with the correct status, i\&.e\&. if the job priority is lower than the set fence priority it will have the PAUSED status, whereas if the priority is equal or higher it will have the SPOOLED or PRINTING status\&. + + +Note that it is good practice to include the absolute path in the lppause command as the PATH may not be available to the server\&. + + +See also the \fIprinting \fR parameter\&. + + +Default: Currently no default value is given to this string, unless the value of the \fIprinting\fR parameter is \fBSYSV\fR, in which case the default is : + + +\fBlp -i %p-%j -H hold\fR + + +or if the value of the \fIprinting\fR parameter is \fBSOFTQ\fR, then the default is: + + +\fBqstat -s -j%j -h\fR + + +Example for HPUX: \fBlppause command = /usr/bin/lpalt %p-%j -p0\fR + + +.TP +lpq cache time (G) +This controls how long lpq info will be cached for to prevent the \fBlpq\fR command being called too often\&. A separate cache is kept for each variation of the \fB lpq\fR command used by the system, so if you use different \fBlpq\fR commands for different users then they won't share cache information\&. + + +The cache files are stored in \fI/tmp/lpq\&.xxxx\fR where xxxx is a hash of the \fBlpq\fR command in use\&. + + +The default is 10 seconds, meaning that the cached results of a previous identical \fBlpq\fR command will be used if the cached data is less than 10 seconds old\&. A large value may be advisable if your \fBlpq\fR command is very slow\&. + + +A value of 0 will disable caching completely\&. + + +See also the \fIprinting\fR parameter\&. + + +Default: \fBlpq cache time = 10\fR + + +Example: \fBlpq cache time = 30\fR + + +.TP +lpq command (S) +This parameter specifies the command to be executed on the server host in order to obtain \fBlpq \fR-style printer status information\&. + + +This command should be a program or script which takes a printer name as its only parameter and outputs printer status information\&. + + +Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ\&. This covers most UNIX systems\&. You control which type is expected using the \fIprinting =\fR option\&. + + +Some clients (notably Windows for Workgroups) may not correctly send the connection number for the printer they are requesting status information about\&. To get around this, the server reports on the first printer service connected to by the client\&. This only happens if the connection number sent is invalid\&. + + +If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&. + + +Note that it is good practice to include the absolute path in the \fIlpq command\fR as the \fB$PATH \fR may not be available to the server\&. When compiled with the CUPS libraries, no \fIlpq command\fR is needed because smbd will make a library call to obtain the print queue listing\&. + + +See also the \fIprinting \fR parameter\&. + + +Default: \fBdepends on the setting of \fI printing\fR\fR + + +Example: \fBlpq command = /usr/bin/lpq -P%p\fR + + +.TP +lpresume command (S) +This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job\&. + + +This command should be a program or script which takes a printer name and job number to resume the print job\&. See also the \fIlppause command \fR parameter\&. + + +If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&. + + +Note that it is good practice to include the absolute path in the \fIlpresume command\fR as the PATH may not be available to the server\&. + + +See also the \fIprinting \fR parameter\&. + + +Default: Currently no default value is given to this string, unless the value of the \fIprinting\fR parameter is \fBSYSV\fR, in which case the default is : + + +\fBlp -i %p-%j -H resume\fR + + +or if the value of the \fIprinting\fR parameter is \fBSOFTQ\fR, then the default is: + + +\fBqstat -s -j%j -r\fR + + +Example for HPUX: \fBlpresume command = /usr/bin/lpalt %p-%j -p2\fR + + +.TP +lprm command (S) +This parameter specifies the command to be executed on the server host in order to delete a print job\&. + + +This command should be a program or script which takes a printer name and job number, and deletes the print job\&. + + +If a \fI%p\fR is given then the printer name is put in its place\&. A \fI%j\fR is replaced with the job number (an integer)\&. + + +Note that it is good practice to include the absolute path in the \fIlprm command\fR as the PATH may not be available to the server\&. + + +See also the \fIprinting \fR parameter\&. + + +Default: \fBdepends on the setting of \fIprinting \fR\fR + + +Example 1: \fBlprm command = /usr/bin/lprm -P%p %j\fR + + +Example 2: \fBlprm command = /usr/bin/cancel %p-%j\fR + + +.TP +machine password timeout (G) +If a Samba server is a member of a Windows NT Domain (see the security = domain) parameter) then periodically a running smbd(8) process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called \fIprivate/secrets\&.tdb \fR\&. This parameter specifies how often this password will be changed, in seconds\&. The default is one week (expressed in seconds), the same as a Windows NT Domain member server\&. + + +See also \fBsmbpasswd\fR(8), and the security = domain) parameter\&. + + +Default: \fBmachine password timeout = 604800\fR + + +.TP +magic output (S) +This parameter specifies the name of a file which will contain output created by a magic script (see the \fImagic script\fR parameter below)\&. + + +Warning: If two clients use the same \fImagic script \fR in the same directory the output file content is undefined\&. + + +Default: \fBmagic output = .out\fR + + +Example: \fBmagic output = myfile.txt\fR + + +.TP +magic script (S) +This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed\&. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user\&. + + +Scripts executed in this way will be deleted upon completion assuming that the user has the appropriate level of privilege and the file permissions allow the deletion\&. + + +If the script generates output, output will be sent to the file specified by the \fI magic output\fR parameter (see above)\&. + + +Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker\&. Magic scripts must be executable \fBas is\fR on the host, which for some hosts and some shells will require filtering at the DOS end\&. + + +Magic scripts are \fBEXPERIMENTAL\fR and should \fBNOT\fR be relied upon\&. + + +Default: \fBNone\&. Magic scripts disabled\&.\fR + + +Example: \fBmagic script = user.csh\fR + + +.TP +mangle case (S) +See the section on NAME MANGLING + + +Default: \fBmangle case = no\fR + + +.TP +mangled map (S) +This is for those who want to directly map UNIX file names which cannot be represented on Windows/DOS\&. The mangling of names is not always what is needed\&. In particular you may have documents with file extensions that differ between DOS and UNIX\&. For example, under UNIX it is common to use \fI\&.html\fR for HTML files, whereas under Windows/DOS \fI\&.htm\fR is more commonly used\&. + + +So to map \fIhtml\fR to \fIhtm\fR you would use: + + +\fBmangled map = (*.html *.htm)\fR + + +One very useful case is to remove the annoying \fI;1 \fR off the ends of filenames on some CDROMs (only visible under some UNIXes)\&. To do this use a map of (*;1 *;)\&. + + +Default: \fBno mangled map\fR + + +Example: \fBmangled map = (*;1 *;)\fR + + +.TP +mangled names (S) +This controls whether non-DOS names under UNIX should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored\&. + + +See the section on NAME MANGLING for details on how to control the mangling process\&. + + +If mangling is used then the mangling algorithm is as follows: + + +The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters of the mangled name\&. + +A tilde "~" is appended to the first part of the mangled name, followed by a two-character unique sequence, based on the original root name (i\&.e\&., the original filename minus its final extension)\&. The final extension is included in the hash calculation only if it contains any upper case characters or is longer than three characters\&. + + +Note that the character to use may be specified using the \fImangling char\fR option, if you don't like '~'\&. + +The first three alphanumeric characters of the final extension are preserved, forced to upper case and appear as the extension of the mangled name\&. The final extension is defined as that part of the original filename after the rightmost dot\&. If there are no dots in the filename, the mangled name will have no extension (except in the case of "hidden files" - see below)\&. + +Files whose UNIX name begins with a dot will be presented as DOS hidden files\&. The mangled name will be created as for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that's three underscores)\&. + +The two-digit hash value consists of upper case alphanumeric characters\&. + + +This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters\&. The probability of such a clash is 1/1300\&. + + +The name mangling (if enabled) allows a file to be copied between UNIX directories from Windows/DOS while retaining the long UNIX filename\&. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename\&. Mangled names do not change between sessions\&. + + +Default: \fBmangled names = yes\fR + + +.TP +mangling stack (G) +This parameter controls the number of mangled names that should be cached in the Samba server \fBsmbd\fR(8)\&. + + +This stack is a list of recently mangled base names (extensions are only maintained if they are longer than 3 characters or contains upper case characters)\&. + + +The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names\&. However, large stack sizes will slow most directory accesses\&. Smaller stacks save memory in the server (each stack element costs 256 bytes)\&. + + +It is not possible to absolutely guarantee correct long filenames, so be prepared for some surprises! + + +Default: \fBmangled stack = 50\fR + + +Example: \fBmangled stack = 100\fR + + +.TP +mangling prefix (G) +controls the number of prefix characters from the original name used when generating the mangled names\&. A larger value will give a weaker hash and therefore more name collisions\&. The minimum value is 1 and the maximum value is 6\&. + + +Default: \fBmangle prefix = 1\fR + + +Example: \fBmangle prefix = 4\fR + + +.TP +mangling char (S) +This controls what character is used as the \fBmagic\fR character in name mangling\&. The default is a '~' but this may interfere with some software\&. Use this option to set it to whatever you prefer\&. + + +Default: \fBmangling char = ~\fR + + +Example: \fBmangling char = ^\fR + + +.TP +mangling method (G) +controls the algorithm used for the generating the mangled names\&. Can take two different values, "hash" and "hash2"\&. "hash" is the default and is the algorithm that has been used in Samba for many years\&. "hash2" is a newer and considered a better algorithm (generates less collisions) in the names\&. However, many Win32 applications store the mangled names and so changing to the new algorithm must not be done lightly as these applications may break unless reinstalled\&. + + +Default: \fBmangling method = hash2\fR + + +Example: \fBmangling method = hash\fR + + +.TP +map archive (S) +This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit\&. The DOS archive bit is set when a file has been modified since its last backup\&. One motivation for this option it to keep Samba/your PC from making any file it touches from becoming executable under UNIX\&. This can be quite annoying for shared source code, documents, etc\&.\&.\&. + + +Note that this requires the \fIcreate mask\fR parameter to be set such that owner execute bit is not masked out (i\&.e\&. it must include 100)\&. See the parameter \fIcreate mask\fR for details\&. + + +Default: \fBmap archive = yes\fR + + +.TP +map hidden (S) +This controls whether DOS style hidden files should be mapped to the UNIX world execute bit\&. + + +Note that this requires the \fIcreate mask\fR to be set such that the world execute bit is not masked out (i\&.e\&. it must include 001)\&. See the parameter \fIcreate mask\fR for details\&. + + +Default: \fBmap hidden = no\fR + + +.TP +map system (S) +This controls whether DOS style system files should be mapped to the UNIX group execute bit\&. + + +Note that this requires the \fIcreate mask\fR to be set such that the group execute bit is not masked out (i\&.e\&. it must include 010)\&. See the parameter \fIcreate mask\fR for details\&. + + +Default: \fBmap system = no\fR + + +.TP +map to guest (G) +This parameter is only useful in security modes other than \fIsecurity = share\fR - i\&.e\&. \fBuser\fR, \fBserver\fR, and \fBdomain\fR\&. + + +This parameter can take three different values, which tell \fBsmbd\fR(8) what to do with user login requests that don't match a valid UNIX user in some way\&. + + +The three settings are : + + +\fBNever\fR - Means user login requests with an invalid password are rejected\&. This is the default\&. + +\fBBad User\fR - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the \fI guest account\fR\&. + +\fBBad Password\fR - Means user logins with an invalid password are treated as a guest login and mapped into the guest account\&. Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong\&. Helpdesk services will \fBhate\fR you if you set the \fImap to guest\fR parameter this way :-)\&. + +Note that this parameter is needed to set up "Guest" share services when using \fIsecurity\fR modes other than share\&. This is because in these modes the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for "Guest" shares\&. + + +For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the \fB GUEST_SESSSETUP\fR value in local\&.h\&. + + +Default: \fBmap to guest = Never\fR + + +Example: \fBmap to guest = Bad User\fR + + +.TP +max connections (S) +This option allows the number of simultaneous connections to a service to be limited\&. If \fImax connections\fR is greater than 0 then connections will be refused if this number of connections to the service are already open\&. A value of zero mean an unlimited number of connections may be made\&. + + +Record lock files are used to implement this feature\&. The lock files will be stored in the directory specified by the \fIlock directory\fR option\&. + + +Default: \fBmax connections = 0\fR + + +Example: \fBmax connections = 10\fR + + +.TP +max disk size (G) +This option allows you to put an upper limit on the apparent size of disks\&. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size\&. + + +Note that this option does not limit the amount of data you can put on the disk\&. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in \fImax disk size\fR\&. + + +This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size\&. + + +A \fImax disk size\fR of 0 means no limit\&. + + +Default: \fBmax disk size = 0\fR + + +Example: \fBmax disk size = 1000\fR + + +.TP +max log size (G) +This option (an integer in kilobytes) specifies the max size the log file should grow to\&. Samba periodically checks the size and if it is exceeded it will rename the file, adding a \fI\&.old\fR extension\&. + + +A size of 0 means no limit\&. + + +Default: \fBmax log size = 5000\fR + + +Example: \fBmax log size = 1000\fR + + +.TP +max mux (G) +This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow\&. You should never need to set this parameter\&. + + +Default: \fBmax mux = 50\fR + + +.TP +max open files (G) +This parameter limits the maximum number of open files that one \fBsmbd\fR(8) file serving process may have open for a client at any one time\&. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file\&. + + +The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter\&. + + +Default: \fBmax open files = 10000\fR + + +.TP +max print jobs (S) +This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment\&. If this number is exceeded, \fBsmbd\fR(8) will remote "Out of Space" to the client\&. See all \fItotal print jobs\fR\&. + + +Default: \fBmax print jobs = 1000\fR + + +Example: \fBmax print jobs = 5000\fR + + +.TP +max protocol (G) +The value of the parameter (a string) is the highest protocol level that will be supported by the server\&. + + +Possible values are : + + +\fBCORE\fR: Earliest version\&. No concept of user names\&. + +\fBCOREPLUS\fR: Slight improvements on CORE for efficiency\&. + +\fBLANMAN1\fR: First \fB modern\fR version of the protocol\&. Long filename support\&. + +\fBLANMAN2\fR: Updates to Lanman1 protocol\&. + +\fBNT1\fR: Current up to date version of the protocol\&. Used by Windows NT\&. Known as CIFS\&. + +Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol\&. + + +See also \fImin protocol\fR + + +Default: \fBmax protocol = NT1\fR + + +Example: \fBmax protocol = LANMAN1\fR + + +.TP +max smbd processes (G) +This parameter limits the maximum number of \fBsmbd\fR(8) processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections\&. Remember that under normal operating conditions, each user will have an \fBsmbd\fR(8) associated with him or her to handle connections to all shares from a given host\&. + + +Default: \fBmax smbd processes = 0\fR ## no limit + + +Example: \fBmax smbd processes = 1000\fR + + +.TP +max ttl (G) +This option tells \fBnmbd\fR(8) what the default 'time to live' of NetBIOS names should be (in seconds) when \fBnmbd\fR is requesting a name using either a broadcast packet or from a WINS server\&. You should never need to change this parameter\&. The default is 3 days\&. + + +Default: \fBmax ttl = 259200\fR + + +.TP +max wins ttl (G) +This option tells \fBsmbd\fR(8) when acting as a WINS server ( \fIwins support = yes\fR) what the maximum 'time to live' of NetBIOS names that \fBnmbd\fR will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 days (518400 seconds)\&. + + +See also the \fImin wins ttl\fR parameter\&. + + +Default: \fBmax wins ttl = 518400\fR + + +.TP +max xmit (G) +This option controls the maximum packet size that will be negotiated by Samba\&. The default is 65535, which is the maximum\&. In some cases you may find you get better performance with a smaller value\&. A value below 2048 is likely to cause problems\&. + + +Default: \fBmax xmit = 65535\fR + + +Example: \fBmax xmit = 8192\fR + + +.TP +message command (G) +This specifies what command to run when the server receives a WinPopup style message\&. + + +This would normally be a command that would deliver the message somehow\&. How this is to be done is up to your imagination\&. + + +An example is: + + +\fBmessage command = csh -c 'xedit %s;rm %s' &\fR + + +This delivers the message using \fBxedit\fR, then removes it afterwards\&. \fBNOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR\&. That's why I have the '&' on the end\&. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully)\&. + + +All messages are delivered as the global guest user\&. The command takes the standard substitutions, although \fI %u\fR won't work (\fI%U\fR may be better in this case)\&. + + +Apart from the standard substitutions, some additional ones apply\&. In particular: + + +\fI%s\fR = the filename containing the message\&. + +\fI%t\fR = the destination that the message was sent to (probably the server name)\&. + +\fI%f\fR = who the message is from\&. + +You could make this command send mail, or whatever else takes your fancy\&. Please let us know of any really interesting ideas you have\&. + + +Here's a way of sending the messages as mail to root: + + +\fBmessage command = /bin/mail -s 'message from %f on %m' root < %s; rm %s\fR + + +If you don't have a message command then the message won't be delivered and Samba will tell the sender there was an error\&. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered\&. + + +If you want to silently delete it then try: + + +\fBmessage command = rm %s\fR + + +Default: \fBno message command\fR + + +Example: \fBmessage command = csh -c 'xedit %s; rm %s' &\fR + + +.TP +min passwd length (G) +Synonym for \fImin password length\fR\&. + + +.TP +min password length (G) +This option sets the minimum length in characters of a plaintext password that \fBsmbd\fR will accept when performing UNIX password changing\&. + + +See also \fIunix password sync\fR, \fIpasswd program\fR and \fIpasswd chat debug\fR\&. + + +Default: \fBmin password length = 5\fR + + +.TP +min print space (S) +This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job\&. It is specified in kilobytes\&. The default is 0, which means a user can always spool a print job\&. + + +See also the \fIprinting \fR parameter\&. + + +Default: \fBmin print space = 0\fR + + +Example: \fBmin print space = 2000\fR + + +.TP +min protocol (G) +The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support\&. Please refer to the \fImax protocol\fR parameter for a list of valid protocol names and a brief description of each\&. You may also wish to refer to the C source code in \fIsource/smbd/negprot\&.c\fR for a listing of known protocol dialects supported by clients\&. + + +If you are viewing this parameter as a security measure, you should also refer to the \fIlanman auth\fR parameter\&. Otherwise, you should never need to change this parameter\&. + + +Default : \fBmin protocol = CORE\fR + + +Example : \fBmin protocol = NT1\fR # disable DOS clients + + +.TP +min wins ttl (G) +This option tells \fBnmbd\fR(8) when acting as a WINS server (\fI wins support = yes\fR) what the minimum 'time to live' of NetBIOS names that \fBnmbd\fR will grant will be (in seconds)\&. You should never need to change this parameter\&. The default is 6 hours (21600 seconds)\&. + + +Default: \fBmin wins ttl = 21600\fR + + +.TP +msdfs proxy (S) +This parameter indicates that the share is a stand-in for another CIFS share whose location is specified by the value of the parameter\&. When clients attempt to connect to this share, they are redirected to the proxied share using the SMB-Dfs protocol\&. + + +Only Dfs roots can act as proxy shares\&. Take a look at the \fImsdfs root\fR and \fIhost msdfs\fR options to find out how to set up a Dfs root share\&. + + +Example: \fBmsdfs proxy = \\\\otherserver\\someshare\fR + + +.TP +msdfs root (S) +This boolean parameter is only available if Samba is configured and compiled with the \fB --with-msdfs\fR option\&. If set to \fByes\fR, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory\&. Dfs links are specified in the share directory by symbolic links of the form \fImsdfs:serverA\\\\shareA,serverB\\\\shareB\fR and so on\&. For more information on setting up a Dfs tree on Samba, refer to "Hosting a Microsoft Distributed File System tree on Samba" document\&. + + +See also \fIhost msdfs\fR + + +Default: \fBmsdfs root = no\fR + + +.TP +name cache timeout (G) +Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out\&. If the timeout is set to 0\&. the caching is disabled\&. + + +Default: \fBname cache timeout = 660\fR + + +Example: \fBname cache timeout = 0\fR + + +.TP +name resolve order (G) +This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses\&. The option takes a space separated string of name resolution options\&. + + +The options are: "lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows: + + +\fBlmhosts\fR : Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the lmhosts(5) for details) then any name type matches for lookup\&. + +\fBhost\fR : Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&. + +\fBwins\fR : Query a name with the IP address listed in the \fI wins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&. + +\fBbcast\fR : Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. + +Default: \fBname resolve order = lmhosts host wins bcast\fR + + +Example: \fBname resolve order = lmhosts bcast host\fR + + +This will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup\&. + + +.TP +netbios aliases (G) +This is a list of NetBIOS names that nmbd(8) will advertise as additional names by which the Samba server is known\&. This allows one machine to appear in browse lists under multiple names\&. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities\&. + + +See also \fInetbios name\fR\&. + + +Default: \fBempty string (no additional names)\fR + + +Example: \fBnetbios aliases = TEST TEST1 TEST2\fR + + +.TP +netbios name (G) +This sets the NetBIOS name by which a Samba server is known\&. By default it is the same as the first component of the host's DNS name\&. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under\&. + + +See also \fInetbios aliases\fR\&. + + +Default: \fBmachine DNS name\fR + + +Example: \fBnetbios name = MYNAME\fR + + +.TP +netbios scope (G) +This sets the NetBIOS scope that Samba will operate under\&. This should not be set unless every machine on your LAN also sets this value\&. + + +.TP +nis homedir (G) +Get the home share server from a NIS map\&. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server\&. + + +When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS)\&. This can be very slow\&. + + +This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server\&. When Samba is returning the home share to the client, it will consult the NIS map specified in \fIhomedir map\fR and return the server listed there\&. + + +Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server\&. + + +Default: \fBnis homedir = no\fR + + +.TP +non unix account range (G) +The non unix account range parameter specifies the range of 'user ids' that are allocated by the various 'non unix account' passdb backends\&. These backends allow the storage of passwords for users who don't exist in /etc/passwd\&. This is most often used for machine account creation\&. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\&. + + +These userids never appear on the system and Samba will never 'become' these users\&. They are used only to ensure that the algorithmic RID mapping does not conflict with normal users\&. + +Default: \fBnon unix account range = \fR + + +Example: \fBnon unix account range = 10000-20000\fR + + +.TP +nt acl support (S) +This boolean parameter controls whether \fBsmbd\fR(8) will attempt to map UNIX permissions into Windows NT access control lists\&. This parameter was formally a global parameter in releases prior to 2\&.2\&.2\&. + + +Default: \fBnt acl support = yes\fR + + +.TP +ntlm auth (G) +This parameter determines whether or not \fBsmbd\fR(8) will attempt to authenticate users using the NTLM password hash\&. If disabled, only the lanman password hashes will be used\&. + + +Please note that at least this option or \fBlanman auth\fR should be enabled in order to be able to log in\&. + + +Default : \fBntlm auth = yes\fR + + +.TP +nt pipe support (G) +This boolean parameter controls whether \fBsmbd\fR(8) will allow Windows NT clients to connect to the NT SMB specific \fBIPC$\fR pipes\&. This is a developer debugging option and can be left alone\&. + + +Default: \fBnt pipe support = yes\fR + + +.TP +nt status support (G) +This boolean parameter controls whether \fBsmbd\fR(8) will negotiate NT specific status support with Windows NT/2k/XP clients\&. This is a developer debugging option and should be left alone\&. If this option is set to \fBno\fR then Samba offers exactly the same DOS error codes that versions prior to Samba 2\&.2\&.3 reported\&. + + +You should not need to ever disable this parameter\&. + + +Default: \fBnt status support = yes\fR + + +.TP +null passwords (G) +Allow or disallow client access to accounts that have null passwords\&. + + +See also \fBsmbpasswd\fR(5)\&. + + +Default: \fBnull passwords = no\fR + + +.TP +obey pam restrictions (G) +When Samba 3\&.0 is configured to enable PAM support (i\&.e\&. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives\&. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management\&. Note that Samba always ignores PAM for authentication in the case of \fIencrypt passwords = yes\fR\&. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption\&. + + +Default: \fBobey pam restrictions = no\fR + + +.TP +only guest (S) +A synonym for \fI guest only\fR\&. + + +.TP +only user (S) +This is a boolean option that controls whether connections with usernames not in the \fIuser\fR list will be allowed\&. By default this option is disabled so that a client can supply a username to be used by the server\&. Enabling this parameter will force the server to only use the login names from the \fIuser\fR list and is only really useful in share level security\&. + + +Note that this also means Samba won't try to deduce usernames from the service name\&. This can be annoying for the [homes] section\&. To get around this you could use \fBuser = %S\fR which means your \fIuser\fR list will be just the service name, which for home directories is the name of the user\&. + + +See also the \fIuser\fR parameter\&. + + +Default: \fBonly user = no\fR + + +.TP +oplock break wait time (G) +This is a tuning parameter added due to bugs in both Windows 9x and WinNT\&. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request\&. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients\&. + + +\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR\&. + + +Default: \fBoplock break wait time = 0\fR + + +.TP +oplock contention limit (S) +This is a \fBvery\fR advanced \fBsmbd\fR(8) tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file\&. + + +In brief it specifies a number, which causes \fBsmbd\fR(8)not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit\&. This causes \fBsmbd\fR to behave in a similar way to Windows NT\&. + + +\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR\&. + + +Default: \fBoplock contention limit = 2\fR + + +.TP +oplocks (S) +This boolean option tells \fBsmbd\fR whether to issue oplocks (opportunistic locks) to file open requests on this share\&. The oplock code can dramatically (approx\&. 30% or more) improve the speed of access to files on Samba servers\&. It allows the clients to aggressively cache files locally and you may want to disable this option for unreliable network environments (it is turned on by default in Windows NT Servers)\&. For more information see the file \fISpeed\&.txt\fR in the Samba \fIdocs/\fR directory\&. + + +Oplocks may be selectively turned off on certain files with a share\&. See the \fI veto oplock files\fR parameter\&. On some systems oplocks are recognized by the underlying operating system\&. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process\&. See the \fIkernel oplocks\fR parameter for details\&. + + +See also the \fIkernel oplocks\fR and \fI level2 oplocks\fR parameters\&. + + +Default: \fBoplocks = yes\fR + + +.TP +os2 driver map (G) +The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names\&. The format is: + + + = \&. + + +For example, a valid entry using the HP LaserJet 5 printer driver would appear as \fBHP LaserJet 5L = LASERJET.HP LaserJet 5L\fR\&. + + +The need for the file is due to the printer driver namespace problem described in the Samba Printing HOWTO\&. For more details on OS/2 clients, please refer to the OS2-Client-HOWTO containing in the Samba documentation\&. + + +Default: \fBos2 driver map = \fR + + +.TP +os level (G) +This integer value controls what level Samba advertises itself as for browse elections\&. The value of this parameter determines whether \fBnmbd\fR(8) has a chance of becoming a local master browser for the \fI WORKGROUP\fR in the local broadcast area\&. + + +\fBNote :\fRBy default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4\&.0/2000 Domain Controller\&. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes\&. See \fIBROWSING\&.txt \fR in the Samba \fIdocs/\fR directory for details\&. + + +Default: \fBos level = 20\fR + + +Example: \fBos level = 65 \fR + + +.TP +pam password change (G) +With the addition of better PAM support in Samba 2\&.2, this parameter, it is possible to use PAM's password change control flag for Samba\&. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in \fIpasswd program\fR\&. It should be possible to enable this without changing your \fIpasswd chat\fR parameter for most setups\&. + + +Default: \fBpam password change = no\fR + + +.TP +panic action (G) +This is a Samba developer option that allows a system command to be called when either \fBsmbd\fR(8) or \fBsmbd\fR(8) crashes\&. This is usually used to draw attention to the fact that a problem occurred\&. + + +Default: \fBpanic action = \fR + + +Example: \fBpanic action = "/bin/sleep 90000"\fR + + +.TP +paranoid server security (G) +Some version of NT 4\&.x allow non-guest users with a bad passowrd\&. When this option is enabled, samba will not use a broken NT 4\&.x server as password server, but instead complain to the logs and exit\&. + + +Disabling this option prevents Samba from making this check, which involves deliberatly attempting a bad logon to the remote server\&. + + +Default: \fBparanoid server security = yes\fR + + +.TP +passdb backend (G) +This option allows the administrator to chose which backends to retrieve and store passwords with\&. This allows (for example) both smbpasswd and tdbsam to be used without a recompile\&. Multiple backends can be specified, separated by spaces\&. The backends will be searched in the order they are specified\&. New users are always added to the first backend specified\&. + + +This parameter is in two parts, the backend's name, and a 'location' string that has meaning only to that particular backed\&. These are separated by a : character\&. + + +Available backends can include: .TP 3 \(bu \fBsmbpasswd\fR - The default smbpasswd backend\&. Takes a path to the smbpasswd file as an optional argument\&. .TP \(bu \fBsmbpasswd_nua\fR - The smbpasswd backend, but with support for 'not unix accounts'\&. Takes a path to the smbpasswd file as an optional argument\&. See also \fInon unix account range\fR .TP \(bu \fBtdbsam\fR - The TDB based password storage backend\&. Takes a path to the TDB as an optional argument (defaults to passdb\&.tdb in the \fIprivate dir\fR directory\&. .TP \(bu \fBtdbsam_nua\fR - The TDB based password storage backend, with non unix account support\&. Takes a path to the TDB as an optional argument (defaults to passdb\&.tdb in the \fIprivate dir\fR directory\&. See also \fInon unix account range\fR .TP \(bu \fBldapsam\fR - The LDAP based passdb backend\&. Takes an LDAP URL as an optional argument (defaults to \fBldap://localhost\fR) .TP \(bu \fBldapsam_nua\fR - The LDAP based passdb backend, with non unix account support\&. Takes an LDAP URL as an optional argument (defaults to \fBldap://localhost\fR) Note: In this module, any account without a matching POSIX account is regarded as 'non unix'\&. See also \fInon unix account range\fR LDAP connections should be secured where possible\&. This may be done using either Start-TLS (see \fIldap ssl\fR) or by specifying \fIldaps://\fR in the URL argument\&. .TP \(bu \fBnisplussam\fR - The NIS+ based passdb backend\&. Takes name NIS domain as an optional argument\&. Only works with sun NIS+ servers\&. .LP + + +Default: \fBpassdb backend = smbpasswd unixsam\fR + + +Example: \fBpassdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd guest\fR + + +Example: \fBpassdb backend = ldapsam_nua:ldaps://ldap.example.com guest\fR + + +Example: \fBpassdb backend = mysql:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb\fR + + +.TP +passwd chat debug (G) +This boolean specifies if the passwd chat script parameter is run in \fBdebug\fR mode\&. In this mode the strings passed to and received from the passwd chat are printed in the \fBsmbd\fR(8) log with a \fIdebug level\fR of 100\&. This is a dangerous option as it will allow plaintext passwords to be seen in the \fBsmbd\fR log\&. It is available to help Samba admins debug their \fIpasswd chat\fR scripts when calling the \fIpasswd program\fR and should be turned off after this has been done\&. This option has no effect if the \fIpam password change\fR paramter is set\&. This parameter is off by default\&. + + +See also \fIpasswd chat\fR , \fIpam password change\fR , \fIpasswd program\fR \&. + + +Default: \fBpasswd chat debug = no\fR + + +.TP +passwd chat (G) +This string controls the \fB"chat"\fR conversation that takes places between \fBsmbd\fR(8) and the local password changing program to change the user's password\&. The string describes a sequence of response-receive pairs that \fBsmbd\fR(8) uses to determine what to send to the \fIpasswd program\fR and what to expect back\&. If the expected output is not received then the password is not changed\&. + + +This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc)\&. + + +Note that this parameter only is only used if the \fIunix password sync\fR parameter is set to \fByes\fR\&. This sequence is then called \fBAS ROOT\fR when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext\&. This means that root must be able to reset the user's password without knowing the text of the previous password\&. In the presence of NIS/YP, this means that the passwd program must be executed on the NIS master\&. + + +The string can contain the macro \fI%n\fR which is substituted for the new password\&. The chat sequence can also contain the standard macros \fB\\\\n\fR, \fB\\\\r\fR, \fB\\\\t\fR and \fB\\\\s\fR to give line-feed, carriage-return, tab and space\&. The chat sequence string can also contain a '*' which matches any sequence of characters\&. Double quotes can be used to collect strings with spaces in them into a single string\&. + + +If the send string in any part of the chat sequence is a full stop "\&.", then no string is sent\&. Similarly, if the expect string is a full stop then no string is expected\&. + + +If the \fIpam password change\fR parameter is set to \fByes\fR, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output\&. The \\n macro is ignored for PAM conversions\&. + + +See also \fIunix password sync\fR, \fI passwd program\fR , \fIpasswd chat debug\fR and \fIpam password change\fR\&. + + +Default: \fBpasswd chat = *new*password* %n\\n *new*password* %n\\n *changed*\fR + + +Example: \fBpasswd chat = "*Enter OLD password*" %o\\n "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password changed*"\fR + + +.TP +passwd program (G) +The name of a program that can be used to set UNIX user passwords\&. Any occurrences of \fI%u\fR will be replaced with the user name\&. The user name is checked for existence before calling the password changing program\&. + + +Also note that many passwd programs insist in \fBreasonable \fR passwords, such as a minimum length, or the inclusion of mixed case chars and digits\&. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it\&. + + +\fBNote\fR that if the \fIunix password sync\fR parameter is set to \fByes \fR then this program is called \fBAS ROOT\fR before the SMB password in the \fBsmbpasswd\fR(5) file is changed\&. If this UNIX password change fails, then \fBsmbd\fR will fail to change the SMB password also (this is by design)\&. + + +If the \fIunix password sync\fR parameter is set this parameter \fBMUST USE ABSOLUTE PATHS\fR for \fBALL\fR programs called, and must be examined for security implications\&. Note that by default \fIunix password sync\fR is set to \fBno\fR\&. + + +See also \fIunix password sync\fR\&. + + +Default: \fBpasswd program = /bin/passwd\fR + + +Example: \fBpasswd program = /sbin/npasswd %u\fR + + +.TP +password level (G) +Some client/server combinations have difficulty with mixed-case passwords\&. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems\&. These clients upper case clear text passwords even when NT LM 0\&.12 selected by the protocol negotiation request/response\&. + + +This parameter defines the maximum number of characters that may be upper case in passwords\&. + + +For example, say the password given was "FRED"\&. If \fI password level\fR is set to 1, the following combinations would be tried if "FRED" failed: + + +"Fred", "fred", "fRed", "frEd","freD" + + +If \fIpassword level\fR was set to 2, the following combinations would also be tried: + + +"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", \&.\&. + + +And so on\&. + + +The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password\&. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection\&. + + +A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case\&. + + +Default: \fBpassword level = 0\fR + + +Example: \fBpassword level = 4\fR + + +.TP +password server (G) +By specifying the name of another SMB server (such as a WinNT box) with this option, and using \fBsecurity = domain \fR or \fBsecurity = server\fR you can get Samba to do all its username/password validation via a remote server\&. + + +This option sets the name of the password server to use\&. It must be a NetBIOS name, so if the machine's NetBIOS name is different from its Internet name then you may have to add its NetBIOS name to the lmhosts file which is stored in the same directory as the \fIsmb\&.conf\fR file\&. + + +The name of the password server is looked up using the parameter \fIname resolve order\fR and so may resolved by any method and order described in that parameter\&. + + +The password server must be a machine capable of using the "LM1\&.2X002" or the "NT LM 0\&.12" protocol, and it must be in user level security mode\&. + + +Using a password server means your UNIX box (running Samba) is only as secure as your password server\&. \fBDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST\fR\&. + +Never point a Samba server at itself for password serving\&. This will cause a loop and could lock up your Samba server! + + +The name of the password server takes the standard substitutions, but probably the only useful one is \fI%m \fR, which means the Samba server will use the incoming client as the password server\&. If you use this then you better trust your clients, and you had better restrict them with hosts allow! + + +If the \fIsecurity\fR parameter is set to \fBdomain\fR, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character '*', as the Samba server is effectively in that domain, and will use cryptographically authenticated RPC calls to authenticate the user logging on\&. The advantage of using \fB security = domain\fR is that if you list several hosts in the \fIpassword server\fR option then \fBsmbd \fR will try each in turn till it finds one that responds\&. This is useful in case your primary server goes down\&. + + +If the \fIpassword server\fR option is set to the character '*', then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name \fBWORKGROUP<1C>\fR and then contacting each server returned in the list of IP addresses from the name resolution source\&. + + +If the list of servers contains both names and the '*' character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC's will be added to the list as well\&. Samba will not attempt to optimize this list by locating the closest DC\&. + + +If the \fIsecurity\fR parameter is set to \fBserver\fR, then there are different restrictions that \fBsecurity = domain\fR doesn't suffer from: + + +You may list several password servers in the \fIpassword server\fR parameter, however if an \fBsmbd\fR makes a connection to a password server, and then the password server fails, no more users will be able to be authenticated from this \fBsmbd\fR\&. This is a restriction of the SMB/CIFS protocol when in \fBsecurity = server \fR mode and cannot be fixed in Samba\&. + +If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in \fB security = server\fR mode the network logon will appear to come from there rather than from the users workstation\&. + +See also the \fIsecurity \fR parameter\&. + + +Default: \fBpassword server = \fR + + +Example: \fBpassword server = NT-PDC, NT-BDC1, NT-BDC2, *\fR + + +Example: \fBpassword server = *\fR + + +.TP +path (S) +This parameter specifies a directory to which the user of the service is to be given access\&. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing\&. + + +For a printable service offering guest access, the service should be readonly and the path should be world-writeable and have the sticky bit set\&. This is not mandatory of course, but you probably won't get the results you expect if you do otherwise\&. + + +Any occurrences of \fI%u\fR in the path will be replaced with the UNIX username that the client is using on this connection\&. Any occurrences of \fI%m\fR will be replaced by the NetBIOS name of the machine they are connecting from\&. These replacements are very useful for setting up pseudo home directories for users\&. + + +Note that this path will be based on \fIroot dir\fR if one was specified\&. + + +Default: \fBnone\fR + + +Example: \fBpath = /home/fred\fR + + +.TP +pid directory (G) +This option specifies the directory where pid files will be placed\&. + + +Default: \fBpid directory = ${prefix}/var/locks\fR + + +Example: \fBpid directory = /var/run/\fR + + +.TP +posix locking (S) +The \fBsmbd\fR(8) daemon maintains an database of file locks obtained by SMB clients\&. The default behavior is to map this internal database to POSIX locks\&. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non-SMB method (e\&.g\&. NFS or local file access)\&. You should never need to disable this parameter\&. + + +Default: \fBposix locking = yes\fR + + +.TP +postexec (S) +This option specifies a command to be run whenever the service is disconnected\&. It takes the usual substitutions\&. The command may be run as the root on some systems\&. + + +An interesting example may be to unmount server resources: + + +\fBpostexec = /etc/umount /cdrom\fR + + +See also \fIpreexec\fR\&. + + +Default: \fBnone (no command executed)\fR + + +Example: \fBpostexec = echo \"%u disconnected from %S from %m (%I)\" >> /tmp/log\fR + + +.TP +preexec close (S) +This boolean option controls whether a non-zero return code from \fIpreexec \fR should close the service being connected to\&. + + +Default: \fBpreexec close = no\fR + + +.TP +preexec (S) +This option specifies a command to be run whenever the service is connected to\&. It takes the usual substitutions\&. + + +An interesting example is to send the users a welcome message every time they log in\&. Maybe a message of the day? Here is an example: + + +\fBpreexec = csh -c 'echo \"Welcome to %S!\" | /usr/local/samba/bin/smbclient -M %m -I %I' & \fR + + +Of course, this could get annoying after a while :-) + + +See also \fIpreexec close\fR and \fIpostexec \fR\&. + + +Default: \fBnone (no command executed)\fR + + +Example: \fBpreexec = echo \"%u connected to %S from %m (%I)\" >> /tmp/log\fR + + +.TP +prefered master (G) +Synonym for \fI preferred master\fR for people who cannot spell :-)\&. + + +.TP +preferred master (G) +This boolean parameter controls if \fBnmbd\fR(8) is a preferred master browser for its workgroup\&. + + +If this is set to \fByes\fR, on startup, \fBnmbd\fR will force an election, and it will have a slight advantage in winning the election\&. It is recommended that this parameter is used in conjunction with \fB domain master = yes\fR, so that \fBnmbd\fR can guarantee becoming a domain master\&. -This command will be run as user. -Default: \fBNone\fR. +Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser\&. This will result in unnecessary broadcast traffic and reduced browsing capabilities\&. -Example: \fBabort shutdown script = /sbin/shutdown -c\fR -.TP -\fB>addprinter command (G)\fR -With the introduction of MS-RPC based printing -support for Windows NT/2000 clients in Samba 2.2, The MS Add -Printer Wizard (APW) icon is now also available in the -"Printers..." folder displayed a share listing. The APW -allows for printers to be add remotely to a Samba or Windows -NT/2000 print server. - -For a Samba host this means that the printer must be -physically added to the underlying printing system. The \fIadd -printer command\fR defines a script to be run which -will perform the necessary operations for adding the printer -to the print system and to add the appropriate service definition -to the \fIsmb.conf\fR file in order that it can be -shared by \fBsmbd\fR(8). - -The \fIaddprinter command\fR is -automatically invoked with the following parameter (in -order): -.RS -.TP 0.2i -\(bu -\fIprinter name\fR -.TP 0.2i -\(bu -\fIshare name\fR -.TP 0.2i -\(bu -\fIport name\fR -.TP 0.2i -\(bu -\fIdriver name\fR -.TP 0.2i -\(bu -\fIlocation\fR -.TP 0.2i -\(bu -\fIWindows 9x driver location\fR -.RE -All parameters are filled in from the PRINTER_INFO_2 structure sent -by the Windows NT/2000 client with one exception. The "Windows 9x -driver location" parameter is included for backwards compatibility -only. The remaining fields in the structure are generated from answers -to the APW questions. +See also \fIos level\fR\&. -Once the \fIaddprinter command\fR has -been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to determine if the share defined by the APW -exists. If the sharename is still invalid, then \fBsmbd -\fR will return an ACCESS_DENIED error to the client. -The "add printer command" program can output a single line of text, -which Samba will set as the port the new printer is connected to. -If this line isn't output, Samba won't reload its printer shares. +Default: \fBpreferred master = auto\fR -See also \fI deleteprinter command\fR, \fIprinting\fR, -\fIshow add -printer wizard\fR -Default: \fBnone\fR +.TP +preload modules (G) +This is a list of paths to modules that should be loaded into smbd before a client connects\&. This improves the speed of smbd when reacting to new connections somewhat\&. -Example: \fBaddprinter command = /usr/bin/addprinter -\fR -.TP -\fB>add share command (G)\fR -Samba 2.2.0 introduced the ability to dynamically -add and delete shares via the Windows NT 4.0 Server Manager. The -\fIadd share command\fR is used to define an -external program or script which will add a new service definition -to \fIsmb.conf\fR. In order to successfully -execute the \fIadd share command\fR, \fBsmbd\fR -requires that the administrator be connected using a root account (i.e. -uid == 0). - -When executed, \fBsmbd\fR will automatically invoke the -\fIadd share command\fR with four parameters. -.RS -.TP 0.2i -\(bu -\fIconfigFile\fR - the location -of the global \fIsmb.conf\fR file. -.TP 0.2i -\(bu -\fIshareName\fR - the name of the new -share. -.TP 0.2i -\(bu -\fIpathName\fR - path to an **existing** -directory on disk. -.TP 0.2i -\(bu -\fIcomment\fR - comment string to associate -with the new share. -.RE -This parameter is only used for add file shares. To add printer shares, -see the \fIaddprinter -command\fR. +It is recommended to only use this option on heavy-performance servers\&. -See also \fIchange share -command\fR, \fIdelete share -command\fR. -Default: \fBnone\fR +Default: \fBpreload modules = \fR -Example: \fBadd share command = /usr/local/bin/addshare\fR -.TP -\fB>add machine script (G)\fR -This is the full pathname to a script that will -be run by \fBsmbd\fR(8) when a machine is added -to it's domain using the administrator username and password method. -This option is only required when using sam back-ends tied to the -Unix uid method of RID calculation such as smbpasswd. This option is only -available in Samba 3.0. +Example: \fBpreload modules = /usr/lib/samba/passdb/mysql.so+++ \fR -Default: \fBadd machine script = -\fR -Example: \fBadd machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u -\fR .TP -\fB>ads server (G)\fR -If this option is specified, samba does -not try to figure out what ads server to use itself, but -uses the specified ads server. Either one DNS name or IP -address can be used. +preload (G) +This is a list of services that you want to be automatically added to the browse lists\&. This is most useful for homes and printers services that would otherwise not be visible\&. -Default: \fBads server = \fR -Example: \fBads server = 192.168.1.2\fR -.TP -\fB>add user script (G)\fR -This is the full pathname to a script that will -be run \fBAS ROOT\fR by \fBsmbd\fR(8) under special circumstances described below. - -Normally, a Samba server requires that UNIX users are -created for all users accessing files on this server. For sites -that use Windows NT account databases as their primary user database -creating these users and keeping the user list in sync with the -Windows NT PDC is an onerous task. This option allows smbd to create the required UNIX users -\fBON DEMAND\fR when a user accesses the Samba server. - -In order to use this option, \fBsmbd\fR(8) must \fBNOT\fR be set to \fIsecurity = share\fR -and \fIadd user script\fR -must be set to a full pathname for a script that will create a UNIX -user given one argument of \fI%u\fR, which expands into -the UNIX user name to create. - -When the Windows user attempts to access the Samba server, -at login (session setup in the SMB protocol) time, \fBsmbd\fR(8) contacts the \fIpassword server\fR and -attempts to authenticate the given user with the given password. If the -authentication succeeds then \fBsmbd\fR -attempts to find a UNIX user in the UNIX password database to map the -Windows user into. If this lookup fails, and \fIadd user script -\fR is set then \fBsmbd\fR will -call the specified script \fBAS ROOT\fR, expanding -any \fI%u\fR argument to be the user name to create. - -If this script successfully creates the user then \fBsmbd -\fR will continue on as though the UNIX user -already existed. In this way, UNIX users are dynamically created to -match existing Windows NT accounts. - -See also \fI security\fR, \fIpassword server\fR, -\fIdelete user -script\fR. - -Default: \fBadd user script = -\fR - -Example: \fBadd user script = /usr/local/samba/bin/add_user -%u\fR -.TP -\fB>add group script (G)\fR -This is the full pathname to a script that will -be run \fBAS ROOT\fR by \fBsmbd\fR(8) when a new group is -requested. It will expand any -\fI%g\fR to the group name passed. -This script is only useful for installations using the -Windows NT domain administration tools. The script is -free to create a group with an arbitrary name to -circumvent unix group name restrictions. In that case -the script must print the numeric gid of the created -group on stdout. -.TP -\fB>admin users (S)\fR -This is a list of users who will be granted -administrative privileges on the share. This means that they -will do all file operations as the super-user (root). - -You should use this option very carefully, as any user in -this list will be able to do anything they like on the share, -irrespective of file permissions. +Note that if you just want all printers in your printcap file loaded then the \fIload printers\fR option is easier\&. -Default: \fBno admin users\fR -Example: \fBadmin users = jason\fR -.TP -\fB>add user to group script (G)\fR -Full path to the script that will be called when -a user is added to a group using the Windows NT domain administration -tools. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR. -Any \fI%g\fR will be replaced with the group name and -any \fI%u\fR will be replaced with the user name. +Default: \fBno preloaded services\fR + + +Example: \fBpreload = fred lp colorlp\fR -Default: \fBadd user to group script = \fR -Example: \fBadd user to group script = /usr/sbin/adduser %u %g\fR -.TP -\fB>allow hosts (S)\fR -Synonym for \fIhosts allow\fR. .TP -\fB>algorithmic rid base (G)\fR -This determines how Samba will use its -algorithmic mapping from uids/gid to the RIDs needed to construct -NT Security Identifiers. +preserve case (S) +This controls if new filenames are created with the case that the client passes, or if they are forced to be the \fIdefault case \fR\&. -Setting this option to a larger value could be useful to sites -transitioning from WinNT and Win2k, as existing user and -group rids would otherwise clash with sytem users etc. -All UIDs and GIDs must be able to be resolved into SIDs for -the correct operation of ACLs on the server. As such the algorithmic -mapping can't be 'turned off', but pushing it 'out of the way' should -resolve the issues. Users and groups can then be assigned 'low' RIDs -in arbitary-rid supporting backends. +Default: \fBpreserve case = yes\fR -Default: \fBalgorithmic rid base = 1000\fR -Example: \fBalgorithmic rid base = 100000\fR -.TP -\fB>allow trusted domains (G)\fR -This option only takes effect when the \fIsecurity\fR option is set to -server or domain. -If it is set to no, then attempts to connect to a resource from -a domain or workgroup other than the one which smbd is running -in will fail, even if that domain is trusted by the remote server -doing the authentication. - -This is useful if you only want your Samba server to -serve resources to users in the domain it is a member of. As -an example, suppose that there are two domains DOMA and DOMB. DOMB -is trusted by DOMA, which contains the Samba server. Under normal -circumstances, a user with an account in DOMB can then access the -resources of a UNIX account with the same account name on the -Samba server even if they do not have an account in DOMA. This -can make implementing a security boundary difficult. +See the section on NAME MANGLING for a fuller discussion\&. + -Default: \fBallow trusted domains = yes\fR .TP -\fB>announce as (G)\fR -This specifies what type of server \fBnmbd\fR(8) will announce itself as, to a network neighborhood browse -list. By default this is set to Windows NT. The valid options -are : "NT Server" (which can also be written as "NT"), -"NT Workstation", "Win95" or "WfW" meaning Windows NT Server, -Windows NT Workstation, Windows 95 and Windows for Workgroups -respectively. Do not change this parameter unless you have a -specific need to stop Samba appearing as an NT server as this -may prevent Samba servers from participating as browser servers -correctly. +printable (S) +If this parameter is \fByes\fR, then clients may open, write to and submit spool files on the directory specified for the service\&. -Default: \fBannounce as = NT Server\fR -Example: \fBannounce as = Win95\fR -.TP -\fB>announce version (G)\fR -This specifies the major and minor version numbers -that nmbd will use when announcing itself as a server. The default -is 4.9. Do not change this parameter unless you have a specific -need to set a Samba server to be a downlevel server. +Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data\&. The \fIread only \fR parameter controls only non-printing access to the resource\&. -Default: \fBannounce version = 4.9\fR -Example: \fBannounce version = 2.0\fR -.TP -\fB>auto services (G)\fR -This is a synonym for the \fIpreload\fR. -.TP -\fB>auth methods (G)\fR -This option allows the administrator to chose what -authentication methods \fBsmbd\fR will use when authenticating -a user. This option defaults to sensible values based on \fI security\fR. -Each entry in the list attempts to authenticate the user in turn, until -the user authenticates. In practice only one method will ever actually -be able to complete the authentication. +Default: \fBprintable = no\fR -Default: \fBauth methods = \fR -Example: \fBauth methods = guest sam ntdomain\fR .TP -\fB>available (S)\fR -This parameter lets you "turn off" a service. If -\fIavailable = no\fR, then \fBALL\fR -attempts to connect to the service will fail. Such failures are -logged. +printcap name (S) +This parameter may be used to override the compiled-in default printcap name used by the server (usually \fI /etc/printcap\fR)\&. See the discussion of the [printers] section above for reasons why you might want to do this\&. -Default: \fBavailable = yes\fR -.TP -\fB>bind interfaces only (G)\fR -This global parameter allows the Samba admin -to limit what interfaces on a machine will serve SMB requests. It -affects file service \fBsmbd\fR(8) and name service \fBnmbd\fR(8) in a slightly different ways. - -For name service it causes \fBnmbd\fR to bind -to ports 137 and 138 on the interfaces listed in the interfaces parameter. \fBnmbd -\fR also binds to the "all addresses" interface (0.0.0.0) -on ports 137 and 138 for the purposes of reading broadcast messages. -If this option is not set then \fBnmbd\fR will service -name requests on all of these sockets. If \fIbind interfaces -only\fR is set then \fBnmbd\fR will check the -source address of any packets coming in on the broadcast sockets -and discard any that don't match the broadcast addresses of the -interfaces in the \fIinterfaces\fR parameter list. -As unicast packets are received on the other sockets it allows -\fBnmbd\fR to refuse to serve names to machines that -send packets that arrive through any interfaces not listed in the -\fIinterfaces\fR list. IP Source address spoofing -does defeat this simple check, however, so it must not be used -seriously as a security feature for \fBnmbd\fR. - -For file service it causes \fBsmbd\fR(8) to bind only to the interface list -given in the interfaces parameter. This restricts the networks that -\fBsmbd\fR will serve to packets coming in those -interfaces. Note that you should not use this parameter for machines -that are serving PPP or other intermittent or non-broadcast network -interfaces as it will not cope with non-permanent interfaces. - -If \fIbind interfaces only\fR is set then -unless the network address \fB127.0.0.1\fR is added -to the \fIinterfaces\fR parameter list \fBsmbpasswd\fR(8) and \fBswat\fR(8) may not work as expected due to the reasons covered below. - -To change a users SMB password, the \fBsmbpasswd\fR -by default connects to the \fBlocalhost - 127.0.0.1\fR -address as an SMB client to issue the password change request. If -\fIbind interfaces only\fR is set then unless the -network address \fB127.0.0.1\fR is added to the -\fIinterfaces\fR parameter list then \fB smbpasswd\fR will fail to connect in it's default mode. -\fBsmbpasswd\fR can be forced to use the primary IP interface -of the local host by using its \fBsmbpasswd\fR(8) \fI-r remote machine\fR -parameter, with \fIremote machine\fR set -to the IP name of the primary interface of the local host. - -The \fBswat\fR status page tries to connect with -\fBsmbd\fR and \fBnmbd\fR at the address -\fB127.0.0.1\fR to determine if they are running. -Not adding \fB127.0.0.1\fR will cause \fB smbd\fR and \fBnmbd\fR to always show -"not running" even if they really are. This can prevent \fB swat\fR from starting/stopping/restarting \fBsmbd\fR -and \fBnmbd\fR. -Default: \fBbind interfaces only = no\fR -.TP -\fB>blocking locks (S)\fR -This parameter controls the behavior -of \fBsmbd\fR(8) when given a request by a client -to obtain a byte range lock on a region of an open file, and the -request has a time limit associated with it. +To use the CUPS printing interface set \fBprintcap name = cups \fR\&. This should be supplemented by an addtional setting printing = cups in the [global] section\&. \fBprintcap name = cups\fR will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file\&. -If this parameter is set and the lock range requested -cannot be immediately satisfied, samba will internally -queue the lock request, and periodically attempt to obtain -the lock until the timeout period expires. -If this parameter is set to no, then -samba will behave as previous versions of Samba would and -will fail the lock request immediately if the lock range -cannot be obtained. +On System V systems that use \fBlpstat\fR to list available printers you can use \fBprintcap name = lpstat \fR to automatically obtain lists of available printers\&. This is the default for systems that define SYSV at configure time in Samba (this includes most System V based systems)\&. If \fI printcap name\fR is set to \fBlpstat\fR on these systems then Samba will launch \fBlpstat -v\fR and attempt to parse the output to obtain a printer list\&. -Default: \fBblocking locks = yes\fR -.TP -\fB>block size (S)\fR -This parameter controls the behavior of \fBsmbd\fR(8) when reporting disk free -sizes. By default, this reports a disk block size of 1024 bytes. -Changing this parameter may have some effect on the -efficiency of client writes, this is not yet confirmed. This -parameter was added to allow advanced administrators to change -it (usually to a higher value) and test the effect it has on -client write performance without re-compiling the code. As this -is an experimental option it may be removed in a future release. +A minimal printcap file would look something like this: -Changing this option does not change the disk free reporting -size, just the block size unit reported to the client. -.TP -\fB>browsable (S)\fR -See the \fI browseable\fR. -.TP -\fB>browse list (G)\fR -This controls whether \fBsmbd\fR(8) will serve a browse list to -a client doing a \fBNetServerEnum\fR call. Normally -set to yes. You should never need to change -this. -Default: \fBbrowse list = yes\fR -.TP -\fB>browseable (S)\fR -This controls whether this share is seen in -the list of available shares in a net view and in the browse list. +.nf + +print1|My Printer 1 +print2|My Printer 2 +print3|My Printer 3 +print4|My Printer 4 +print5|My Printer 5 +.fi + + +where the '|' separates aliases of a printer\&. The fact that the second alias has a space in it gives a hint to Samba that it's a comment\&. + + +Under AIX the default printcap name is \fI/etc/qconfig\fR\&. Samba will assume the file is in AIX \fIqconfig\fR format if the string \fIqconfig\fR appears in the printcap filename\&. + +Default: \fBprintcap name = /etc/printcap\fR + + +Example: \fBprintcap name = /etc/myprintcap\fR -Default: \fBbrowseable = yes\fR -.TP -\fB>case sensitive (S)\fR -See the discussion in the section NAME MANGLING. -Default: \fBcase sensitive = no\fR .TP -\fB>casesignames (S)\fR -Synonym for case -sensitive. +printcap (G) +Synonym for \fI printcap name\fR\&. + + .TP -\fB>change notify timeout (G)\fR -This SMB allows a client to tell a server to -"watch" a particular directory for any changes and only reply to -the SMB request when a change has occurred. Such constant scanning of -a directory is expensive under UNIX, hence an \fBsmbd\fR(8) daemon only performs such a scan -on each requested directory once every \fIchange notify -timeout\fR seconds. +print command (S) +After a print job has finished spooling to a service, this command will be used via a \fBsystem()\fR call to process the spool file\&. Typically the command specified will submit the spool file to the host's printing subsystem, but there is no requirement that this be the case\&. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\&. -Default: \fBchange notify timeout = 60\fR -Example: \fBchange notify timeout = 300\fR +The print command is simply a text string\&. It will be used verbatim after macro substitutions have been made: -Would change the scan time to every 5 minutes. -.TP -\fB>change share command (G)\fR -Samba 2.2.0 introduced the ability to dynamically -add and delete shares via the Windows NT 4.0 Server Manager. The -\fIchange share command\fR is used to define an -external program or script which will modify an existing service definition -in \fIsmb.conf\fR. In order to successfully -execute the \fIchange share command\fR, \fBsmbd\fR -requires that the administrator be connected using a root account (i.e. -uid == 0). -When executed, \fBsmbd\fR will automatically invoke the -\fIchange share command\fR with four parameters. -.RS -.TP 0.2i -\(bu -\fIconfigFile\fR - the location -of the global \fIsmb.conf\fR file. -.TP 0.2i -\(bu -\fIshareName\fR - the name of the new -share. -.TP 0.2i -\(bu -\fIpathName\fR - path to an **existing** -directory on disk. -.TP 0.2i -\(bu -\fIcomment\fR - comment string to associate -with the new share. -.RE +%s, %p - the path to the spool file name -This parameter is only used modify existing file shares definitions. To modify -printer shares, use the "Printers..." folder as seen when browsing the Samba host. -See also \fIadd share -command\fR, \fIdelete -share command\fR. +%p - the appropriate printer name -Default: \fBnone\fR -Example: \fBchange share command = /usr/local/bin/addshare\fR -.TP -\fB>comment (S)\fR -This is a text field that is seen next to a share -when a client does a queries the server, either via the network -neighborhood or via \fBnet view\fR to list what shares -are available. +%J - the job name as transmitted by the client\&. -If you want to set the string that is displayed next to the -machine name then see the \fI server string\fR parameter. -Default: \fBNo comment string\fR +%c - The number of printed pages of the spooled job (if known)\&. -Example: \fBcomment = Fred's Files\fR -.TP -\fB>config file (G)\fR -This allows you to override the config file -to use, instead of the default (usually \fIsmb.conf\fR). -There is a chicken and egg problem here as this option is set -in the config file! -For this reason, if the name of the config file has changed -when the parameters are loaded then it will reload them from -the new config file. +%z - the size of the spooled print job (in bytes) -This option takes the usual substitutions, which can -be very useful. -If the config file doesn't exist then it won't be loaded -(allowing you to special case the config files of just a few -clients). +The print command \fBMUST\fR contain at least one occurrence of \fI%s\fR or \fI%f \fR - the \fI%p\fR is optional\&. At the time a job is submitted, if no printer name is supplied the \fI%p \fR will be silently removed from the printer command\&. -Example: \fBconfig file = /usr/local/samba/lib/smb.conf.%m -\fR -.TP -\fB>copy (S)\fR -This parameter allows you to "clone" service -entries. The specified service is simply duplicated under the -current service's name. Any parameters specified in the current -section will override those in the section being copied. -This feature lets you set up a 'template' service and -create similar services easily. Note that the service being -copied must occur earlier in the configuration file than the -service doing the copying. +If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified\&. -Default: \fBno value\fR -Example: \fBcopy = otherservice\fR -.TP -\fB>create mask (S)\fR -A synonym for this parameter is -\fIcreate mode\fR -\&. +If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed and (most importantly) not removed\&. -When a file is created, the necessary permissions are -calculated according to the mapping from DOS modes to UNIX -permissions, and the resulting UNIX mode is then bit-wise 'AND'ed -with this parameter. This parameter may be thought of as a bit-wise -MASK for the UNIX modes of a file. Any bit \fBnot\fR -set here will be removed from the modes set on a file when it is -created. -The default value of this parameter removes the -\&'group' and 'other' write and execute bits from the UNIX modes. +Note that printing may fail on some UNIXes from the \fBnobody\fR account\&. If this happens then create an alternative guest account that can print and set the \fIguest account\fR in the [global] section\&. -Following this Samba will bit-wise 'OR' the UNIX mode created -from this parameter with the value of the \fIforce create mode\fR -parameter which is set to 000 by default. -This parameter does not affect directory modes. See the -parameter \fIdirectory mode -\fR for details. +You can form quite complex print commands by realizing that they are just passed to a shell\&. For example the following will log a print job, print the file, then remove it\&. Note that ';' is the usual separator for command in shell scripts\&. -See also the \fIforce -create mode\fR parameter for forcing particular mode -bits to be set on created files. See also the \fIdirectory mode\fR parameter for masking -mode bits on created directories. See also the \fIinherit permissions\fR parameter. -Note that this parameter does not apply to permissions -set by Windows NT/2000 ACL editors. If the administrator wishes to enforce -a mask on access control lists also, they need to set the \fIsecurity mask\fR. +\fBprint command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s\fR -Default: \fBcreate mask = 0744\fR -Example: \fBcreate mask = 0775\fR -.TP -\fB>create mode (S)\fR -This is a synonym for \fI create mask\fR. -.TP -\fB>csc policy (S)\fR -This stands for \fBclient-side caching -policy\fR, and specifies how clients capable of offline -caching will cache the files in the share. The valid values -are: manual, documents, programs, disable. +You may have to vary this command considerably depending on how you normally print files on your system\&. The default for the parameter varies depending on the setting of the \fIprinting\fR parameter\&. -These values correspond to those used on Windows -servers. -For example, shares containing roaming profiles can have -offline caching disabled using \fBcsc policy = disable -\fR. +Default: For \fBprinting = BSD, AIX, QNX, LPRNG or PLP :\fR -Default: \fBcsc policy = manual\fR -Example: \fBcsc policy = programs\fR -.TP -\fB>deadtime (G)\fR -The value of the parameter (a decimal integer) -represents the number of minutes of inactivity before a connection -is considered dead, and it is disconnected. The deadtime only takes -effect if the number of open files is zero. +\fBprint command = lpr -r -P%p %s\fR -This is useful to stop a server's resources being -exhausted by a large number of inactive connections. -Most clients have an auto-reconnect feature when a -connection is broken so in most cases this parameter should be -transparent to users. +For \fBprinting = SYSV or HPUX :\fR -Using this parameter with a timeout of a few minutes -is recommended for most systems. -A deadtime of zero indicates that no auto-disconnection -should be performed. +\fBprint command = lp -c -d%p %s; rm %s\fR -Default: \fBdeadtime = 0\fR -Example: \fBdeadtime = 15\fR -.TP -\fB>debug hires timestamp (G)\fR -Sometimes the timestamps in the log messages -are needed with a resolution of higher that seconds, this -boolean parameter adds microsecond resolution to the timestamp -message header when turned on. +For \fBprinting = SOFTQ :\fR -Note that the parameter \fI debug timestamp\fR must be on for this to have an -effect. -Default: \fBdebug hires timestamp = no\fR -.TP -\fB>debug pid (G)\fR -When using only one log file for more then one -forked smbdprocess there may be hard to follow which process -outputs which message. This boolean parameter is adds the process-id -to the timestamp message headers in the logfile when turned on. +\fBprint command = lp -d%p -s %s; rm %s\fR -Note that the parameter \fI debug timestamp\fR must be on for this to have an -effect. -Default: \fBdebug pid = no\fR -.TP -\fB>debug timestamp (G)\fR -Samba debug log messages are timestamped -by default. If you are running at a high \fIdebug level\fR these timestamps -can be distracting. This boolean parameter allows timestamping -to be turned off. +For printing = CUPS : If SAMBA is compiled against libcups, then printcap = cups uses the CUPS API to submit jobs, etc\&. Otherwise it maps to the System V commands with the -oraw option for printing, i\&.e\&. it uses \fBlp -c -d%p -oraw; rm %s\fR\&. With \fBprinting = cups\fR, and if SAMBA is compiled against libcups, any manually set print command will be ignored\&. -Default: \fBdebug timestamp = yes\fR -.TP -\fB>debug uid (G)\fR -Samba is sometimes run as root and sometime -run as the connected user, this boolean parameter inserts the -current euid, egid, uid and gid to the timestamp message headers -in the log file if turned on. -Note that the parameter \fI debug timestamp\fR must be on for this to have an -effect. +Example: \fBprint command = /usr/local/samba/bin/myprintscript %p %s\fR -Default: \fBdebug uid = no\fR -.TP -\fB>debuglevel (G)\fR -Synonym for \fI log level\fR. -.TP -\fB>default (G)\fR -A synonym for \fI default service\fR. -.TP -\fB>default case (S)\fR -See the section on NAME MANGLING. Also note the \fIshort preserve case\fR parameter. -Default: \fBdefault case = lower\fR .TP -\fB>default devmode (S)\fR -This parameter is only applicable to printable services. When smbd is serving -Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba -server has a Device Mode which defines things such as paper size and -orientation and duplex settings. The device mode can only correctly be -generated by the printer driver itself (which can only be executed on a -Win32 platform). Because smbd is unable to execute the driver code -to generate the device mode, the default behavior is to set this field -to NULL. - -Most problems with serving printer drivers to Windows NT/2k/XP clients -can be traced to a problem with the generated device mode. Certain drivers -will do things such as crashing the client's Explorer.exe with a NULL devmode. -However, other printer drivers can cause the client's spooler service -(spoolsv.exe) to die if the devmode was not created by the driver itself -(i.e. smbd generates a default devmode). - -This parameter should be used with care and tested with the printer -driver in question. It is better to leave the device mode to NULL -and let the Windows client set the correct values. Because drivers do not -do this all the time, setting \fBdefault devmode = yes\fR -will instruct smbd to generate a default one. - -For more information on Windows NT/2k printing and Device Modes, -see the MSDN documentation . +printer admin (S) +This is a list of users that can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation)\&. Note that the root user always has admin rights\&. + + +Default: \fBprinter admin = \fR + + +Example: \fBprinter admin = admin, @staff\fR + -Default: \fBdefault devmode = no\fR .TP -\fB>default service (G)\fR -This parameter specifies the name of a service -which will be connected to if the service actually requested cannot -be found. Note that the square brackets are \fBNOT\fR -given in the parameter value (see example below). +printer name (S) +This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent\&. -There is no default value for this parameter. If this -parameter is not given, attempting to connect to a nonexistent -service results in an error. -Typically the default service would be a \fIguest ok\fR, \fIread-only\fR service. +If specified in the [global] section, the printer name given will be used for any printable service that does not have its own printer name specified\&. -Also note that the apparent service name will be changed -to equal that of the requested service, this is very useful as it -allows you to use macros like \fI%S\fR to make -a wildcard service. -Note also that any "_" characters in the name of the service -used in the default service will get mapped to a "/". This allows for -interesting things. +Default: \fBnone (but may be \fBlp\fR on many systems)\fR -Example: + +Example: \fBprinter name = laserwriter\fR -.nf -[global] - default service = pub - -[pub] - path = /%S -.fi .TP -\fB>delete group script (G)\fR -This is the full pathname to a script that will -be run \fBAS ROOT\fR \fBsmbd\fR(8) when a group is requested to be deleted. -It will expand any \fI%g\fR to the group name passed. -This script is only useful for installations using the Windows NT domain administration tools. +printer (S) +Synonym for \fI printer name\fR\&. + + .TP -\fB>deleteprinter command (G)\fR -With the introduction of MS-RPC based printer -support for Windows NT/2000 clients in Samba 2.2, it is now -possible to delete printer at run time by issuing the -DeletePrinter() RPC call. +printing (S) +This parameters controls how printer status information is interpreted on your system\&. It also affects the default values for the \fIprint command\fR, \fIlpq command\fR, \fIlppause command \fR, \fIlpresume command\fR, and \fIlprm command\fR if specified in the [global] section\&. -For a Samba host this means that the printer must be -physically deleted from underlying printing system. The \fI deleteprinter command\fR defines a script to be run which -will perform the necessary operations for removing the printer -from the print system and from \fIsmb.conf\fR. -The \fIdeleteprinter command\fR is -automatically called with only one parameter: \fI "printer name"\fR. +Currently nine printing styles are supported\&. They are \fBBSD\fR, \fBAIX\fR, \fBLPRNG\fR, \fBPLP\fR, \fBSYSV\fR, \fBHPUX\fR, \fBQNX\fR, \fBSOFTQ\fR, and \fBCUPS\fR\&. -Once the \fIdeleteprinter command\fR has -been executed, \fBsmbd\fR will reparse the \fI smb.conf\fR to associated printer no longer exists. -If the sharename is still valid, then \fBsmbd -\fR will return an ACCESS_DENIED error to the client. -See also \fI addprinter command\fR, \fIprinting\fR, -\fIshow add -printer wizard\fR +To see what the defaults are for the other print commands when using the various options use the \fBtestparm\fR(1) program\&. + + +This option can be set on a per printer basis + + +See also the discussion in the [printers] section\&. -Default: \fBnone\fR -Example: \fBdeleteprinter command = /usr/bin/removeprinter -\fR .TP -\fB>delete readonly (S)\fR -This parameter allows readonly files to be deleted. -This is not normal DOS semantics, but is allowed by UNIX. +print ok (S) +Synonym for \fIprintable\fR\&. -This option may be useful for running applications such -as rcs, where UNIX file ownership prevents changing file -permissions, and DOS semantics prevent deletion of a read only file. -Default: \fBdelete readonly = no\fR .TP -\fB>delete share command (G)\fR -Samba 2.2.0 introduced the ability to dynamically -add and delete shares via the Windows NT 4.0 Server Manager. The -\fIdelete share command\fR is used to define an -external program or script which will remove an existing service -definition from \fIsmb.conf\fR. In order to successfully -execute the \fIdelete share command\fR, \fBsmbd\fR -requires that the administrator be connected using a root account (i.e. -uid == 0). - -When executed, \fBsmbd\fR will automatically invoke the -\fIdelete share command\fR with two parameters. -.RS -.TP 0.2i -\(bu -\fIconfigFile\fR - the location -of the global \fIsmb.conf\fR file. -.TP 0.2i -\(bu -\fIshareName\fR - the name of -the existing service. -.RE +private dir (G) +This parameters defines the directory smbd will use for storing such files as \fIsmbpasswd\fR and \fIsecrets\&.tdb\fR\&. -This parameter is only used to remove file shares. To delete printer shares, -see the \fIdeleteprinter -command\fR. -See also \fIadd share -command\fR, \fIchange -share command\fR. +Default :\fBprivate dir = ${prefix}/private\fR -Default: \fBnone\fR -Example: \fBdelete share command = /usr/local/bin/delshare\fR .TP -\fB>delete user script (G)\fR -This is the full pathname to a script that will -be run by \fBsmbd\fR(8) when managing users -with remote RPC (NT) tools. +protocol (G) +Synonym for \fImax protocol\fR\&. -This script is called when a remote client removes a user -from the server, normally using 'User Manager for Domains' or -\fBrpcclient\fR. -This script should delete the given UNIX username. +.TP +public (S) +Synonym for \fIguest ok\fR\&. -Default: \fBdelete user script = -\fR -Example: \fBdelete user script = /usr/local/samba/bin/del_user -%u\fR .TP -\fB>delete user from group script (G)\fR -Full path to the script that will be called when -a user is removed from a group using the Windows NT domain administration -tools. It will be run by \fBsmbd\fR(8) \fBAS ROOT\fR. -Any \fI%g\fR will be replaced with the group name and -any \fI%u\fR will be replaced with the user name. +queuepause command (S) +This parameter specifies the command to be executed on the server host in order to pause the printer queue\&. -Default: \fBdelete user from group script = \fR -Example: \fBdelete user from group script = /usr/sbin/deluser %u %g\fR -.TP -\fB>delete veto files (S)\fR -This option is used when Samba is attempting to -delete a directory that contains one or more vetoed directories -(see the \fIveto files\fR -option). If this option is set to no (the default) then if a vetoed -directory contains any non-vetoed files or directories then the -directory delete will fail. This is usually what you want. +This command should be a program or script which takes a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer\&. -If this option is set to yes, then Samba -will attempt to recursively delete any files and directories within -the vetoed directory. This can be useful for integration with file -serving systems such as NetAtalk which create meta-files within -directories you might normally veto DOS/Windows users from seeing -(e.g. \fI.AppleDouble\fR) -Setting \fBdelete veto files = yes\fR allows these -directories to be transparently deleted when the parent directory -is deleted (so long as the user has permissions to do so). +This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\&. -See also the \fIveto -files\fR parameter. -Default: \fBdelete veto files = no\fR -.TP -\fB>deny hosts (S)\fR -Synonym for \fIhosts -deny\fR. -.TP -\fB>dfree command (G)\fR -The \fIdfree command\fR setting should -only be used on systems where a problem occurs with the internal -disk space calculations. This has been known to happen with Ultrix, -but may occur with other operating systems. The symptom that was -seen was an error of "Abort Retry Ignore" at the end of each -directory listing. - -This setting allows the replacement of the internal routines to -calculate the total disk space and amount available with an external -routine. The example below gives a possible script that might fulfill -this function. - -The external program will be passed a single parameter indicating -a directory in the filesystem being queried. This will typically consist -of the string \fI./\fR. The script should return two -integers in ASCII. The first should be the total disk space in blocks, -and the second should be the number of available blocks. An optional -third return value can give the block size in bytes. The default -blocksize is 1024 bytes. - -Note: Your script should \fBNOT\fR be setuid or -setgid and should be owned by (and writeable only by) root! - -Default: \fBBy default internal routines for -determining the disk capacity and remaining space will be used. -\fR - -Example: \fBdfree command = /usr/local/samba/bin/dfree -\fR +If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&. -Where the script dfree (which must be made executable) could be: +Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\&. -.nf - -#!/bin/sh -df $1 | tail -1 | awk '{print $2" "$4}' -.fi -or perhaps (on Sys V based systems): +Default: \fBdepends on the setting of \fIprinting\fR\fR -.nf - -#!/bin/sh -/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}' -.fi +Example: \fBqueuepause command = disable %p\fR + -Note that you may have to replace the command names -with full path names on some systems. -.TP -\fB>directory (S)\fR -Synonym for \fIpath -\fR. .TP -\fB>directory mask (S)\fR -This parameter is the octal modes which are -used when converting DOS modes to UNIX modes when creating UNIX -directories. +queueresume command (S) +This parameter specifies the command to be executed on the server host in order to resume the printer queue\&. It is the command to undo the behavior that is caused by the previous parameter (\fI queuepause command\fR)\&. -When a directory is created, the necessary permissions are -calculated according to the mapping from DOS modes to UNIX permissions, -and the resulting UNIX mode is then bit-wise 'AND'ed with this -parameter. This parameter may be thought of as a bit-wise MASK for -the UNIX modes of a directory. Any bit \fBnot\fR set -here will be removed from the modes set on a directory when it is -created. -The default value of this parameter removes the 'group' -and 'other' write bits from the UNIX mode, allowing only the -user who owns the directory to modify it. +This command should be a program or script which takes a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer\&. -Following this Samba will bit-wise 'OR' the UNIX mode -created from this parameter with the value of the \fIforce directory mode -\fR parameter. This parameter is set to 000 by -default (i.e. no extra mode bits are added). -Note that this parameter does not apply to permissions -set by Windows NT/2000 ACL editors. If the administrator wishes to enforce -a mask on access control lists also, they need to set the \fIdirectory security mask\fR. +This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\&. -See the \fIforce -directory mode\fR parameter to cause particular mode -bits to always be set on created directories. -See also the \fIcreate mode -\fR parameter for masking mode bits on created files, -and the \fIdirectory -security mask\fR parameter. +If a \fI%p\fR is given then the printer name is put in its place\&. Otherwise it is placed at the end of the command\&. -Also refer to the \fI inherit permissions\fR parameter. -Default: \fBdirectory mask = 0755\fR +Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\&. + + +Default: \fBdepends on the setting of \fIprinting\fR\fR + + +Example: \fBqueuepause command = enable %p\fR + -Example: \fBdirectory mask = 0775\fR .TP -\fB>directory mode (S)\fR -Synonym for \fI directory mask\fR +read bmpx (G) +This boolean parameter controls whether \fBsmbd\fR(8) will support the "Read Block Multiplex" SMB\&. This is now rarely used and defaults to \fBno\fR\&. You should never need to set this parameter\&. + + +Default: \fBread bmpx = no\fR + + .TP -\fB>directory security mask (S)\fR -This parameter controls what UNIX permission bits -can be modified when a Windows NT client is manipulating the UNIX -permission on a directory using the native NT security dialog -box. +read list (S) +This is a list of users that are given read-only access to a service\&. If the connecting user is in this list then they will not be given write access, no matter what the \fIread only\fR option is set to\&. The list can include group names using the syntax described in the \fI invalid users\fR parameter\&. -This parameter is applied as a mask (AND'ed with) to -the changed permission bits, thus preventing any bits not in -this mask from being modified. Essentially, zero bits in this -mask may be treated as a set of bits the user is not allowed -to change. -If not set explicitly this parameter is set to 0777 -meaning a user is allowed to modify all the user/group/world -permissions on a directory. +See also the \fI write list\fR parameter and the \fIinvalid users\fR parameter\&. -\fBNote\fR that users who can access the -Samba server through other means can easily bypass this restriction, -so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to leave -it as the default of 0777. -See also the \fI force directory security mode\fR, \fIsecurity mask\fR, -\fIforce security mode -\fR parameters. +Default: \fBread list = \fR + + +Example: \fBread list = mary, @students\fR -Default: \fBdirectory security mask = 0777\fR -Example: \fBdirectory security mask = 0700\fR .TP -\fB>disable netbios (G)\fR -Enabling this parameter will disable netbios support -in Samba. Netbios is the only available form of browsing in -all windows versions except for 2000 and XP. +read only (S) +An inverted synonym is \fIwriteable\fR\&. -Note that clients that only support netbios won't be able to -see your samba server when netbios support is disabled. -Default: \fBdisable netbios = no\fR +If this parameter is \fByes\fR, then users of a service may not create or modify files in the service's directory\&. -Example: \fBdisable netbios = yes\fR -.TP -\fB>disable spoolss (G)\fR -Enabling this parameter will disable Samba's support -for the SPOOLSS set of MS-RPC's and will yield identical behavior -as Samba 2.0.x. Windows NT/2000 clients will downgrade to using -Lanman style printing commands. Windows 9x/ME will be uneffected by -the parameter. However, this will also disable the ability to upload -printer drivers to a Samba server via the Windows NT Add Printer -Wizard or by using the NT printer properties dialog window. It will -also disable the capability of Windows NT/2000 clients to download -print drivers from the Samba host upon demand. -\fBBe very careful about enabling this parameter.\fR -See also use client driver +Note that a printable service (\fBprintable = yes\fR) will \fBALWAYS\fR allow writing to the directory (user privileges permitting), but only via spooling operations\&. -Default : \fBdisable spoolss = no\fR -.TP -\fB>display charset (G)\fR -Specifies the charset that samba will use -to print messages to stdout and stderr and SWAT will use. -Should generally be the same as the \fBunix charset\fR. -Default: \fBdisplay charset = ASCII\fR +Default: \fBread only = yes\fR + -Example: \fBdisplay charset = UTF8\fR .TP -\fB>dns proxy (G)\fR -Specifies that \fBnmbd\fR(8) when acting as a WINS server and -finding that a NetBIOS name has not been registered, should treat the -NetBIOS name word-for-word as a DNS name and do a lookup with the DNS server -for that name on behalf of the name-querying client. +read raw (G) +This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients\&. -Note that the maximum length for a NetBIOS name is 15 -characters, so the DNS name (or DNS alias) can likewise only be -15 characters, maximum. -\fBnmbd\fR spawns a second copy of itself to do the -DNS name lookup requests, as doing a name lookup is a blocking -action. +If enabled, raw reads allow reads of 65535 bytes in one packet\&. This typically provides a major performance benefit\&. -See also the parameter \fI wins support\fR. -Default: \fBdns proxy = yes\fR -.TP -\fB>domain logons (G)\fR -If set to yes, the Samba server will serve -Windows 95/98 Domain logons for the \fIworkgroup\fR it is in. Samba 2.2 -has limited capability to act as a domain controller for Windows -NT 4 Domains. For more details on setting up this feature see -the Samba-PDC-HOWTO included in the \fIhtmldocs/\fR -directory shipped with the source code. +However, some clients either negotiate the allowable block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads\&. -Default: \fBdomain logons = no\fR -.TP -\fB>domain master (G)\fR -Tell \fBsmbd\fR(8) to enable WAN-wide browse list -collation. Setting this option causes \fBnmbd\fR to -claim a special domain specific NetBIOS name that identifies -it as a domain master browser for its given \fIworkgroup\fR. Local master browsers -in the same \fIworkgroup\fR on broadcast-isolated -subnets will give this \fBnmbd\fR their local browse lists, -and then ask \fBsmbd\fR(8) for a complete copy of the browse -list for the whole wide area network. Browser clients will then contact -their local master browser, and will receive the domain-wide browse list, -instead of just the list for their broadcast-isolated subnet. - -Note that Windows NT Primary Domain Controllers expect to be -able to claim this \fIworkgroup\fR specific special -NetBIOS name that identifies them as domain master browsers for -that \fIworkgroup\fR by default (i.e. there is no -way to prevent a Windows NT PDC from attempting to do this). This -means that if this parameter is set and \fBnmbd\fR claims -the special name for a \fIworkgroup\fR before a Windows -NT PDC is able to do so then cross subnet browsing will behave -strangely and may fail. - -If \fBdomain logons = yes\fR -, then the default behavior is to enable the \fIdomain -master\fR parameter. If \fIdomain logons\fR is -not enabled (the default setting), then neither will \fIdomain -master\fR be enabled by default. -Default: \fBdomain master = auto\fR -.TP -\fB>dont descend (S)\fR -There are certain directories on some systems -(e.g., the \fI/proc\fR tree under Linux) that are either not -of interest to clients or are infinitely deep (recursive). This -parameter allows you to specify a comma-delimited list of directories -that the server should always show as empty. +In general this parameter should be viewed as a system tuning tool and left severely alone\&. See also \fIwrite raw\fR\&. -Note that Samba can be very fussy about the exact format -of the "dont descend" entries. For example you may need \fI ./proc\fR instead of just \fI/proc\fR. -Experimentation is the best policy :-) -Default: \fBnone (i.e., all directories are OK -to descend)\fR +Default: \fBread raw = yes\fR -Example: \fBdont descend = /proc,/dev\fR -.TP -\fB>dos charset (G)\fR -DOS SMB clients assume the server has -the same charset as they do. This option specifies which -charset Samba should talk to DOS clients. - -The default depends on which charsets you have installed. -Samba tries to use charset 850 but falls back to ASCII in -case it is not available. Run \fBtestparm\fR(1) to check the default on your system. -.TP -\fB>dos filemode (S)\fR -The default behavior in Samba is to provide -UNIX-like behavior where only the owner of a file/directory is -able to change the permissions on it. However, this behavior -is often confusing to DOS/Windows users. Enabling this parameter -allows a user who has write access to the file (by whatever -means) to modify the permissions on it. Note that a user -belonging to the group owning the file will not be allowed to -change permissions if the group is only granted read access. -Ownership of the file/directory is not changed, only the permissions -are modified. -Default: \fBdos filemode = no\fR .TP -\fB>dos filetime resolution (S)\fR -Under the DOS and Windows FAT filesystem, the finest -granularity on time resolution is two seconds. Setting this parameter -for a share causes Samba to round the reported time down to the -nearest two second boundary when a query call that requires one second -resolution is made to \fBsmbd\fR(8). - -This option is mainly used as a compatibility option for Visual -C++ when used against Samba shares. If oplocks are enabled on a -share, Visual C++ uses two different time reading calls to check if a -file has changed since it was last read. One of these calls uses a -one-second granularity, the other uses a two second granularity. As -the two second call rounds any odd second down, then if the file has a -timestamp of an odd number of seconds then the two timestamps will not -match and Visual C++ will keep reporting the file has changed. Setting -this option causes the two timestamps to match, and Visual C++ is -happy. +read size (G) +The option \fIread size\fR affects the overlap of disk reads/writes with network reads/writes\&. If the amount of data being transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger than this value then the server begins writing the data before it has received the whole packet from the network, or in the case of SMBreadbraw, it begins writing to the network before all the data has been read from disk\&. + + +This overlapping works best when the speeds of disk and network access are similar, having very little effect when the speed of one is much greater than the other\&. + + +The default value is 16384, but very little experimentation has been done yet to determine the optimal value, and it is likely that the best value will vary greatly between systems anyway\&. A value over 65536 is pointless and will cause you to allocate memory unnecessarily\&. + + +Default: \fBread size = 16384\fR + + +Example: \fBread size = 8192\fR + -Default: \fBdos filetime resolution = no\fR .TP -\fB>dos filetimes (S)\fR -Under DOS and Windows, if a user can write to a -file they can change the timestamp on it. Under POSIX semantics, -only the owner of the file or root may change the timestamp. By -default, Samba runs with POSIX semantics and refuses to change the -timestamp on a file if the user \fBsmbd\fR is acting -on behalf of is not the file owner. Setting this option to yes allows DOS semantics and \fBsmbd\fR(8) will change the file -timestamp as DOS requires. +realm (G) +This option specifies the kerberos realm to use\&. The realm is used as the ADS equivalent of the NT4 \fBdomain\fR\&. It is usually set to the DNS name of the kerberos server\&. + + +Default: \fBrealm = \fR + + +Example: \fBrealm = mysambabox.mycompany.com\fR + -Default: \fBdos filetimes = no\fR .TP -\fB>encrypt passwords (G)\fR -This boolean controls whether encrypted passwords -will be negotiated with the client. Note that Windows NT 4.0 SP3 and -above and also Windows 98 will by default expect encrypted passwords -unless a registry entry is changed. To use encrypted passwords in -Samba see the chapter User Database in the Samba HOWTO Collection. +remote announce (G) +This option allows you to setup \fBnmbd\fR(8)to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name\&. + + +This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don't work\&. The remote workgroup can be anywhere that you can send IP packets to\&. + + +For example: + -In order for encrypted passwords to work correctly -\fBsmbd\fR(8) must either -have access to a local \fBsmbpasswd\fR(5) file (see the \fBsmbpasswd\fR(8) program for information on how to set up -and maintain this file), or set the security = [server|domain|ads] parameter which -causes \fBsmbd\fR to authenticate against another -server. +\fBremote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF\fR -Default: \fBencrypt passwords = yes\fR -.TP -\fB>enhanced browsing (G)\fR -This option enables a couple of enhancements to -cross-subnet browse propagation that have been added in Samba -but which are not standard in Microsoft implementations. -The first enhancement to browse propagation consists of a regular -wildcard query to a Samba WINS server for all Domain Master Browsers, -followed by a browse synchronization with each of the returned -DMBs. The second enhancement consists of a regular randomised browse -synchronization with all currently known DMBs. +the above line would cause \fBnmbd\fR to announce itself to the two given IP addresses using the given workgroup names\&. If you leave out the workgroup name then the one given in the \fIworkgroup\fR parameter is used instead\&. -You may wish to disable this option if you have a problem with empty -workgroups not disappearing from browse lists. Due to the restrictions -of the browse protocols these enhancements can cause a empty workgroup -to stay around forever which can be annoying. -In general you should leave this option enabled as it makes -cross-subnet browse propagation much more reliable. +The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\&. -Default: \fBenhanced browsing = yes\fR -.TP -\fB>enumports command (G)\fR -The concept of a "port" is fairly foreign -to UNIX hosts. Under Windows NT/2000 print servers, a port -is associated with a port monitor and generally takes the form of -a local port (i.e. LPT1:, COM1:, FILE:) or a remote port -(i.e. LPD Port Monitor, etc...). By default, Samba has only one -port defined--"Samba Printer Port". Under -Windows NT/2000, all printers must have a valid port name. -If you wish to have a list of ports displayed (\fBsmbd -\fR does not use a port name for anything) other than -the default "Samba Printer Port", you -can define \fIenumports command\fR to point to -a program which should generate a list of ports, one per line, -to standard output. This listing will then be used in response -to the level 1 and 2 EnumPorts() RPC. -Default: \fBno enumports command\fR +See the documentation file BROWSING in the \fIdocs/\fR directory\&. -Example: \fBenumports command = /usr/bin/listports -\fR -.TP -\fB>exec (S)\fR -This is a synonym for \fIpreexec\fR. -.TP -\fB>fake directory create times (S)\fR -NTFS and Windows VFAT file systems keep a create -time for all files and directories. This is not the same as the -ctime - status change time - that Unix keeps, so Samba by default -reports the earliest of the various times Unix does keep. Setting -this parameter for a share causes Samba to always report midnight -1-1-1980 as the create time for directories. - -This option is mainly used as a compatibility option for -Visual C++ when used against Samba shares. Visual C++ generated -makefiles have the object directory as a dependency for each object -file, and a make rule to create the directory. Also, when NMAKE -compares timestamps it uses the creation time when examining a -directory. Thus the object directory will be created if it does not -exist, but once it does exist it will always have an earlier -timestamp than the object files it contains. - -However, Unix time semantics mean that the create time -reported by Samba will be updated whenever a file is created or -or deleted in the directory. NMAKE finds all object files in -the object directory. The timestamp of the last one built is then -compared to the timestamp of the object directory. If the -directory's timestamp if newer, then all object files -will be rebuilt. Enabling this option -ensures directories always predate their contents and an NMAKE build -will proceed as expected. -Default: \fBfake directory create times = no\fR -.TP -\fB>fake oplocks (S)\fR -Oplocks are the way that SMB clients get permission -from a server to locally cache file operations. If a server grants -an oplock (opportunistic lock) then the client is free to assume -that it is the only one accessing the file and it will aggressively -cache file data. With some oplock types the client may even cache -file open/close operations. This can give enormous performance benefits. - -When you set \fBfake oplocks = yes\fR, \fBsmbd(8)\fR will -always grant oplock requests no matter how many clients are using -the file. - -It is generally much better to use the real \fIoplocks\fR support rather -than this parameter. - -If you enable this option on all read-only shares or -shares that you know will only be accessed from one client at a -time such as physically read-only media like CDROMs, you will see -a big performance improvement on many operations. If you enable -this option on shares where multiple clients may be accessing the -files read-write at the same time you can get data corruption. Use -this option carefully! +Default: \fBremote announce = \fR + -Default: \fBfake oplocks = no\fR .TP -\fB>follow symlinks (S)\fR -This parameter allows the Samba administrator -to stop \fBsmbd\fR(8) from following symbolic -links in a particular share. Setting this -parameter to no prevents any file or directory -that is a symbolic link from being followed (the user will get an -error). This option is very useful to stop users from adding a -symbolic link to \fI/etc/passwd\fR in their home -directory for instance. However it will slow filename lookups -down slightly. +remote browse sync (G) +This option allows you to setup \fBnmbd\fR(8) to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment\&. This option will allow you to gain browse lists for multiple workgroups across routed networks\&. This is done in a manner that does not work with any non-Samba servers\&. -This option is enabled (i.e. \fBsmbd\fR will -follow symbolic links) by default. -Default: \fBfollow symlinks = yes\fR -.TP -\fB>force create mode (S)\fR -This parameter specifies a set of UNIX mode bit -permissions that will \fBalways\fR be set on a -file created by Samba. This is done by bitwise 'OR'ing these bits onto -the mode bits of a file that is being created or having its -permissions changed. The default for this parameter is (in octal) -000. The modes in this parameter are bitwise 'OR'ed onto the file -mode after the mask set in the \fIcreate mask\fR -parameter is applied. +This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work\&. The remote workgroup can be anywhere that you can send IP packets to\&. -See also the parameter \fIcreate -mask\fR for details on masking mode bits on files. -See also the \fIinherit -permissions\fR parameter. +For example: -Default: \fBforce create mode = 000\fR -Example: \fBforce create mode = 0755\fR +\fBremote browse sync = 192.168.2.255 192.168.4.255\fR -would force all created files to have read and execute -permissions set for 'group' and 'other' as well as the -read/write/execute bits set for the 'user'. -.TP -\fB>force directory mode (S)\fR -This parameter specifies a set of UNIX mode bit -permissions that will \fBalways\fR be set on a directory -created by Samba. This is done by bitwise 'OR'ing these bits onto the -mode bits of a directory that is being created. The default for this -parameter is (in octal) 0000 which will not add any extra permission -bits to a created directory. This operation is done after the mode -mask in the parameter \fIdirectory mask\fR is -applied. -See also the parameter \fI directory mask\fR for details on masking mode bits -on created directories. +the above line would cause \fBnmbd\fR to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server\&. -See also the \fI inherit permissions\fR parameter. -Default: \fBforce directory mode = 000\fR +The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\&. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment\&. -Example: \fBforce directory mode = 0755\fR -would force all created directories to have read and execute -permissions set for 'group' and 'other' as well as the -read/write/execute bits set for the 'user'. -.TP -\fB>force directory security mode (S)\fR -This parameter controls what UNIX permission bits -can be modified when a Windows NT client is manipulating the UNIX -permission on a directory using the native NT security dialog box. +Default: \fBremote browse sync = \fR -This parameter is applied as a mask (OR'ed with) to the -changed permission bits, thus forcing any bits in this mask that -the user may have modified to be on. Essentially, one bits in this -mask may be treated as a set of bits that, when modifying security -on a directory, the user has always set to be 'on'. -If not set explicitly this parameter is 000, which -allows a user to modify all the user/group/world permissions on a -directory without restrictions. +.TP +restrict anonymous (G) +This is a integer parameter, and mirrors as much as possible the functinality the \fBRestrictAnonymous\fR registry key does on NT/Win2k\&. -\fBNote\fR that users who can access the -Samba server through other means can easily bypass this restriction, -so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to leave -it set as 0000. -See also the \fI directory security mask\fR, \fIsecurity mask\fR, -\fIforce security mode -\fR parameters. +Default: \fBrestrict anonymous = 0\fR -Default: \fBforce directory security mode = 0\fR -Example: \fBforce directory security mode = 700\fR .TP -\fB>force group (S)\fR -This specifies a UNIX group name that will be -assigned as the default primary group for all users connecting -to this service. This is useful for sharing files by ensuring -that all access to files on service will use the named group for -their permissions checking. Thus, by assigning permissions for this -group to the files and directories within this service the Samba -administrator can restrict or allow sharing of these files. - -In Samba 2.0.5 and above this parameter has extended -functionality in the following way. If the group name listed here -has a '+' character prepended to it then the current user accessing -the share only has the primary group default assigned to this group -if they are already assigned as a member of that group. This allows -an administrator to decide that only users who are already in a -particular group will create files with group ownership set to that -group. This gives a finer granularity of ownership assignment. For -example, the setting \fIforce group = +sys\fR means -that only users who are already in group sys will have their default -primary group assigned to sys when accessing this Samba share. All -other users will retain their ordinary primary group. - -If the \fIforce user -\fR parameter is also set the group specified in -\fIforce group\fR will override the primary group -set in \fIforce user\fR. - -See also \fIforce -user\fR. +root directory (G) +The server will \fBchroot()\fR (i\&.e\&. Change its root directory) to this directory on startup\&. This is not strictly necessary for secure operation\&. Even without it the server will deny access to files not in one of the service entries\&. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use "\&.\&." in file names to access other directories (depending on the setting of the \fIwide links\fR parameter)\&. -Default: \fBno forced group\fR -Example: \fBforce group = agroup\fR -.TP -\fB>force security mode (S)\fR -This parameter controls what UNIX permission -bits can be modified when a Windows NT client is manipulating -the UNIX permission on a file using the native NT security dialog -box. +Adding a \fIroot directory\fR entry other than "/" adds an extra level of security, but at a price\&. It absolutely ensures that no access is given to files not in the sub-tree specified in the \fIroot directory\fR option, \fBincluding\fR some files needed for complete operation of the server\&. To maintain full operability of the server you will need to mirror some system files into the \fIroot directory\fR tree\&. In particular you will need to mirror \fI/etc/passwd\fR (or a subset of it), and any binaries or configuration files needed for printing (if required)\&. The set of files that must be mirrored is operating system dependent\&. -This parameter is applied as a mask (OR'ed with) to the -changed permission bits, thus forcing any bits in this mask that -the user may have modified to be on. Essentially, one bits in this -mask may be treated as a set of bits that, when modifying security -on a file, the user has always set to be 'on'. -If not set explicitly this parameter is set to 0, -and allows a user to modify all the user/group/world permissions on a file, -with no restrictions. +Default: \fBroot directory = /\fR -\fBNote\fR that users who can access -the Samba server through other means can easily bypass this restriction, -so it is primarily useful for standalone "appliance" systems. -Administrators of most normal systems will probably want to leave -this set to 0000. -See also the \fI force directory security mode\fR, -\fIdirectory security -mask\fR, \fI security mask\fR parameters. +Example: \fBroot directory = /homes/smb\fR -Default: \fBforce security mode = 0\fR -Example: \fBforce security mode = 700\fR .TP -\fB>force user (S)\fR -This specifies a UNIX user name that will be -assigned as the default user for all users connecting to this service. -This is useful for sharing files. You should also use it carefully -as using it incorrectly can cause security problems. +root dir (G) +Synonym for \fIroot directory"\fR\&. -This user name only gets used once a connection is established. -Thus clients still need to connect as a valid user and supply a -valid password. Once connected, all file operations will be performed -as the "forced user", no matter what username the client connected -as. This can be very useful. -In Samba 2.0.5 and above this parameter also causes the -primary group of the forced user to be used as the primary group -for all file activity. Prior to 2.0.5 the primary group was left -as the primary group of the connecting user (this was a bug). +.TP +root postexec (S) +This is the same as the \fIpostexec\fR parameter except that the command is run as root\&. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed\&. -See also \fIforce group -\fR -Default: \fBno forced user\fR +See also \fI postexec\fR\&. -Example: \fBforce user = auser\fR -.TP -\fB>fstype (S)\fR -This parameter allows the administrator to -configure the string that specifies the type of filesystem a share -is using that is reported by \fBsmbd\fR(8) when a client queries the filesystem type -for a share. The default type is NTFS for -compatibility with Windows NT but this can be changed to other -strings such as Samba or FAT -if required. -Default: \fBfstype = NTFS\fR +Default: \fBroot postexec = \fR -Example: \fBfstype = Samba\fR -.TP -\fB>getwd cache (G)\fR -This is a tuning option. When this is enabled a -caching algorithm will be used to reduce the time taken for getwd() -calls. This can have a significant impact on performance, especially -when the \fIwide links\fR -parameter is set to no. -Default: \fBgetwd cache = yes\fR -.TP -\fB>group (S)\fR -Synonym for \fIforce -group\fR. .TP -\fB>guest account (S)\fR -This is a username which will be used for access -to services which are specified as \fI guest ok\fR (see below). Whatever privileges this -user has will be available to any client connecting to the guest service. -Typically this user will exist in the password file, but will not -have a valid login. The user account "ftp" is often a good choice -for this parameter. If a username is specified in a given service, -the specified username overrides this one. +root preexec close (S) +This is the same as the \fIpreexec close \fR parameter except that the command is run as root\&. -One some systems the default guest account "nobody" may not -be able to print. Use another account in this case. You should test -this by trying to log in as your guest user (perhaps by using the -\fBsu -\fR command) and trying to print using the -system print command such as \fBlpr(1)\fR or \fB lp(1)\fR. -This parameter does not accept % macros, because -many parts of the system require this value to be -constant for correct operation. +See also \fI preexec\fR and \fIpreexec close\fR\&. + + +Default: \fBroot preexec close = no\fR -Default: \fBspecified at compile time, usually -"nobody"\fR -Example: \fBguest account = ftp\fR .TP -\fB>guest ok (S)\fR -If this parameter is yes for -a service, then no password is required to connect to the service. -Privileges will be those of the \fI guest account\fR. +root preexec (S) +This is the same as the \fIpreexec\fR parameter except that the command is run as root\&. This is useful for mounting filesystems (such as CDROMs) when a connection is opened\&. -This paramater nullifies the benifits of setting -\fIrestrict -anonymous\fR = 2 -See the section below on \fI security\fR for more information about this option. +See also \fI preexec\fR and \fIpreexec close\fR\&. -Default: \fBguest ok = no\fR -.TP -\fB>guest only (S)\fR -If this parameter is yes for -a service, then only guest connections to the service are permitted. -This parameter will have no effect if \fIguest ok\fR is not set for the service. -See the section below on \fI security\fR for more information about this option. +Default: \fBroot preexec = \fR + -Default: \fBguest only = no\fR .TP -\fB>hide dot files (S)\fR -This is a boolean parameter that controls whether -files starting with a dot appear as hidden files. +root (G) +Synonym for \fIroot directory"\fR\&. + -Default: \fBhide dot files = yes\fR .TP -\fB>hide files(S)\fR -This is a list of files or directories that are not -visible but are accessible. The DOS 'hidden' attribute is applied -to any files or directories that match. +security mask (S) +This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\&. -Each entry in the list must be separated by a '/', -which allows spaces to be included in the entry. '*' -and '?' can be used to specify multiple files or directories -as in DOS wildcards. -Each entry must be a Unix path, not a DOS path and must -not include the Unix directory separator '/'. +This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified\&. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change\&. -Note that the case sensitivity option is applicable -in hiding files. -Setting this parameter will affect the performance of Samba, -as it will be forced to check all files and directories for a match -as they are scanned. +If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file\&. -See also \fIhide -dot files\fR, \fI veto files\fR and \fIcase sensitive\fR. -Default: \fBno file are hidden\fR +\fBNote\fR that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\&. Administrators of most normal systems will probably want to leave it set to \fB0777\fR\&. -Example: \fBhide files = -/.*/DesktopFolderDB/TrashFor%m/resource.frk/\fR -The above example is based on files that the Macintosh -SMB client (DAVE) available from -Thursby creates for internal use, and also still hides -all files beginning with a dot. -.TP -\fB>hide local users(G)\fR -This parameter toggles the hiding of local UNIX -users (root, wheel, floppy, etc) from remote clients. +See also the \fIforce directory security mode\fR, \fIdirectory security mask\fR, \fIforce security mode\fR parameters\&. -Default: \fBhide local users = no\fR -.TP -\fB>hide unreadable (G)\fR -This parameter prevents clients from seeing the -existance of files that cannot be read. Defaults to off. -Default: \fBhide unreadable = no\fR -.TP -\fB>hide unwriteable files (G)\fR -This parameter prevents clients from seeing -the existance of files that cannot be written to. Defaults to off. -Note that unwriteable directories are shown as usual. +Default: \fBsecurity mask = 0777\fR + + +Example: \fBsecurity mask = 0770\fR -Default: \fBhide unwriteable = no\fR -.TP -\fB>hide special files (G)\fR -This parameter prevents clients from seeing -special files such as sockets, devices and fifo's in directory -listings. -Default: \fBhide special files = no\fR .TP -\fB>homedir map (G)\fR -If\fInis homedir -\fR is yes, and \fBsmbd\fR(8) is also acting -as a Win95/98 \fIlogon server\fR then this parameter -specifies the NIS (or YP) map from which the server for the user's -home directory should be extracted. At present, only the Sun -auto.home map format is understood. The form of the map is: +security (G) +This option affects how clients respond to Samba and is one of the most important settings in the \fI smb\&.conf\fR file\&. -\fBusername server:/some/file/system\fR -and the program will extract the servername from before -the first ':'. There should probably be a better parsing system -that copes with different map formats and also Amd (another -automounter) maps. -.sp -.RS -.B "Note:" -A working NIS client is required on -the system for this option to work. -.RE +The option sets the "security mode bit" in replies to protocol negotiations with \fBsmbd\fR(8) to turn share level security on or off\&. Clients decide based on this bit whether (and how) to transfer user and password information to the server\&. -See also \fInis homedir\fR -, \fIdomain logons\fR -\&. -Default: \fBhomedir map = \fR +The default is \fBsecurity = user\fR, as this is the most common setting needed when talking to Windows 98 and Windows NT\&. -Example: \fBhomedir map = amd.homedir\fR -.TP -\fB>host msdfs (G)\fR -This boolean parameter is only available -if Samba has been configured and compiled with the \fB --with-msdfs\fR option. If set to yes, -Samba will act as a Dfs server, and allow Dfs-aware clients -to browse Dfs trees hosted on the server. -See also the \fI msdfs root\fR share level parameter. For -more information on setting up a Dfs tree on Samba, -refer to msdfs_setup.html +The alternatives are \fBsecurity = share\fR, \fBsecurity = server\fR or \fBsecurity = domain \fR\&. -Default: \fBhost msdfs = no\fR -.TP -\fB>hostname lookups (G)\fR -Specifies whether samba should use (expensive) -hostname lookups or use the ip addresses instead. An example place -where hostname lookups are currently used is when checking -the \fBhosts deny\fR and \fBhosts allow\fR. -Default: \fBhostname lookups = yes\fR +In versions of Samba prior to 2\&.0\&.0, the default was \fBsecurity = share\fR mainly because that was the only option at one stage\&. -Example: \fBhostname lookups = no\fR -.TP -\fB>hosts allow (S)\fR -A synonym for this parameter is \fIallow -hosts\fR. -This parameter is a comma, space, or tab delimited -set of hosts which are permitted to access a service. +There is a bug in WfWg that has relevance to this setting\&. When in user or server level security a WfWg client will totally ignore the password you type in the "connect drive" dialog box\&. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as\&. -If specified in the [global] section then it will -apply to all services, regardless of whether the individual -service has a different setting. -You can specify the hosts by name or IP number. For -example, you could restrict access to only the hosts on a -Class C subnet with something like \fBallow hosts = 150.203.5. -\fR. The full syntax of the list is described in the man -page \fIhosts_access(5)\fR. Note that this man -page may not be present on your system, so a brief description will -be given here also. +If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use \fBsecurity = user\fR\&. If you mostly use usernames that don't exist on the UNIX box then use \fBsecurity = share\fR\&. -Note that the localhost address 127.0.0.1 will always -be allowed access unless specifically denied by a \fIhosts deny\fR option. -You can also specify hosts by network/netmask pairs and -by netgroup names if your system supports netgroups. The -\fBEXCEPT\fR keyword can also be used to limit a -wildcard list. The following examples may provide some help: +You should also use \fBsecurity = share\fR if you want to mainly setup shares without a password (guest shares)\&. This is commonly used for a shared printer server\&. It is more difficult to setup guest shares with \fBsecurity = user\fR, see the \fImap to guest\fR parameter for details\&. -Example 1: allow all IPs in 150.203.*.*; except one -\fBhosts allow = 150.203. EXCEPT 150.203.6.66\fR +It is possible to use \fBsmbd\fR in a \fB hybrid mode\fR where it is offers both user and share level security under different \fINetBIOS aliases\fR\&. -Example 2: allow hosts that match the given network/netmask -\fBhosts allow = 150.203.15.0/255.255.255.0\fR +The different settings will now be explained\&. -Example 3: allow a couple of hosts -\fBhosts allow = lapland, arvidsjaur\fR +\fBSECURITY = SHARE\fR -Example 4: allow only hosts in NIS netgroup "foonet", but -deny access from one particular host -\fBhosts allow = @foonet\fR +When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a \fBsecurity = share \fR server)\&. Instead, the clients send authentication information (passwords) on a per-share basis, at the time they attempt to connect to that share\&. -\fBhosts deny = pirate\fR -Note that access still requires suitable user-level passwords. +Note that \fBsmbd\fR \fBALWAYS\fR uses a valid UNIX user to act on behalf of the client, even in \fBsecurity = share\fR level security\&. -See \fBtestparm\fR(1) for a way of testing your host access -to see if it does what you expect. -Default: \fBnone (i.e., all hosts permitted access) -\fR +As clients are not required to send a username to the server in share level security, \fBsmbd\fR uses several techniques to determine the correct UNIX user to use on behalf of the client\&. -Example: \fBallow hosts = 150.203.5. myhost.mynet.edu.au -\fR -.TP -\fB>hosts deny (S)\fR -The opposite of \fIhosts allow\fR -- hosts listed here are \fBNOT\fR permitted access to -services unless the specific services have their own lists to override -this one. Where the lists conflict, the \fIallow\fR -list takes precedence. -Default: \fBnone (i.e., no hosts specifically excluded) -\fR +A list of possible UNIX usernames to match with the given client password is constructed using the following methods : -Example: \fBhosts deny = 150.203.4. badhost.mynet.edu.au -\fR -.TP -\fB>hosts equiv (G)\fR -If this global parameter is a non-null string, -it specifies the name of a file to read for the names of hosts -and users who will be allowed access without specifying a password. -This is not be confused with \fIhosts allow\fR which is about hosts -access to services and is more useful for guest services. \fI hosts equiv\fR may be useful for NT clients which will -not supply passwords to Samba. -.sp -.RS -.B "Note:" -The use of \fIhosts equiv -\fR can be a major security hole. This is because you are -trusting the PC to supply the correct username. It is very easy to -get a PC to supply a false username. I recommend that the -\fIhosts equiv\fR option be only used if you really -know what you are doing, or perhaps on a home network where you trust -your spouse and kids. And only if you \fBreally\fR trust -them :-). -.RE +If the \fIguest only\fR parameter is set, then all the other stages are missed and only the \fIguest account\fR username is checked\&. -Default: \fBno host equivalences\fR +Is a username is sent with the share connection request, then this username (after mapping - see \fIusername map\fR), is added as a potential username\&. -Example: \fBhosts equiv = /etc/hosts.equiv\fR -.TP -\fB>include (G)\fR -This allows you to include one config file -inside another. The file is included literally, as though typed -in place. +If the client did a previous \fBlogon \fR request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username\&. -It takes the standard substitutions, except \fI%u -\fR, \fI%P\fR and \fI%S\fR. +The name of the service the client requested is added as a potential username\&. -Default: \fBno file included\fR +The NetBIOS name of the client is added to the list as a potential username\&. -Example: \fBinclude = /usr/local/samba/lib/admin_smb.conf -\fR -.TP -\fB>inherit acls (S)\fR -This parameter can be used to ensure -that if default acls exist on parent directories, -they are always honored when creating a subdirectory. -The default behavior is to use the mode specified -when creating the directory. Enabling this option -sets the mode to 0777, thus guaranteeing that -default directory acls are propagated. +Any users on the \fI user\fR list are added as potential usernames\&. -Default: \fBinherit acls = no\fR -.TP -\fB>inherit permissions (S)\fR -The permissions on new files and directories -are normally governed by \fI create mask\fR, \fIdirectory mask\fR, \fIforce create mode\fR -and \fIforce -directory mode\fR but the boolean inherit -permissions parameter overrides this. +If the \fIguest only\fR parameter is not set, then this list is then tried with the supplied password\&. The first user for whom the password matches will be used as the UNIX user\&. -New directories inherit the mode of the parent directory, -including bits such as setgid. -New files inherit their read/write bits from the parent -directory. Their execute bits continue to be determined by -\fImap archive\fR -, \fImap hidden\fR -and \fImap system\fR -as usual. +If the \fIguest only\fR parameter is set, or no username can be determined then if the share is marked as available to the \fIguest account\fR, then this guest user will be used, otherwise access is denied\&. -Note that the setuid bit is \fBnever\fR set via -inheritance (the code explicitly prohibits this). -This can be particularly useful on large systems with -many users, perhaps several thousand, to allow a single [homes] -share to be used flexibly by each user. +Note that it can be \fBvery\fR confusing in share-level security as to which UNIX username will eventually be used in granting access\&. -See also \fIcreate mask -\fR, \fI directory mask\fR, \fIforce create mode\fR and \fIforce directory mode\fR -\&. -Default: \fBinherit permissions = no\fR -.TP -\fB>interfaces (G)\fR -This option allows you to override the default -network interfaces list that Samba will use for browsing, name -registration and other NBT traffic. By default Samba will query -the kernel for the list of all active interfaces and use any -interfaces except 127.0.0.1 that are broadcast capable. +See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&. -The option takes a list of interface strings. Each string -can be in any of the following forms: -.RS -.TP 0.2i -\(bu -a network interface name (such as eth0). -This may include shell-like wildcards so eth* will match -any interface starting with the substring "eth" -.TP 0.2i -\(bu -an IP address. In this case the netmask is -determined from the list of interfaces obtained from the -kernel -.TP 0.2i -\(bu -an IP/mask pair. -.TP 0.2i -\(bu -a broadcast/mask pair. -.RE -The "mask" parameters can either be a bit length (such -as 24 for a C class network) or a full netmask in dotted -decimal form. +\fBSECURITY = USER\fR -The "IP" parameters above can either be a full dotted -decimal IP address or a hostname which will be looked up via -the OS's normal hostname resolution mechanisms. -For example, the following line: +This is the default security setting in Samba 3\&.0\&. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the \fIusername map\fR parameter)\&. Encrypted passwords (see the \fIencrypted passwords\fR parameter) can also be used in this security mode\&. Parameters such as \fIuser\fR and \fIguest only\fR if set are then applied and may change the UNIX user to use on this connection, but only after the user has been successfully authenticated\&. -\fBinterfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 -\fR -would configure three network interfaces corresponding -to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. -The netmasks of the latter two interfaces would be set to 255.255.255.0. +\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&. -See also \fIbind -interfaces only\fR. -Default: \fBall active interfaces except 127.0.0.1 -that are broadcast capable\fR -.TP -\fB>invalid users (S)\fR -This is a list of users that should not be allowed -to login to this service. This is really a \fBparanoid\fR -check to absolutely ensure an improper setting does not breach -your security. +See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&. -A name starting with a '@' is interpreted as an NIS -netgroup first (if your system supports NIS), and then as a UNIX -group if the name was not found in the NIS netgroup database. -A name starting with '+' is interpreted only -by looking in the UNIX group database. A name starting with -\&'&' is interpreted only by looking in the NIS netgroup database -(this requires NIS to be working on your system). The characters -\&'+' and '&' may be used at the start of the name in either order -so the value \fI+&group\fR means check the -UNIX group database, followed by the NIS netgroup database, and -the value \fI&+group\fR means check the NIS -netgroup database, followed by the UNIX group database (the -same as the '@' prefix). +\fBSECURITY = DOMAIN\fR -The current servicename is substituted for \fI%S\fR. -This is useful in the [homes] section. -See also \fIvalid users -\fR. +This mode will only work correctly if \fBnet\fR(8) has been used to add this machine into a Windows NT Domain\&. It expects the \fIencrypted passwords\fR parameter to be set to \fByes\fR\&. In this mode Samba will try to validate the username/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do\&. -Default: \fBno invalid users\fR -Example: \fBinvalid users = root fred admin @wheel -\fR -.TP -\fB>keepalive (G)\fR -The value of the parameter (an integer) represents -the number of seconds between \fIkeepalive\fR -packets. If this parameter is zero, no keepalive packets will be -sent. Keepalive packets, if sent, allow the server to tell whether -a client is still present and responding. +\fBNote\fR that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to\&. -Keepalives should, in general, not be needed if the socket -being used has the SO_KEEPALIVE attribute set on it (see \fIsocket options\fR). -Basically you should only use this option if you strike difficulties. -Default: \fBkeepalive = 300\fR +\fBNote\fR that from the client's point of view \fBsecurity = domain\fR is the same as \fBsecurity = user\fR\&. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\&. -Example: \fBkeepalive = 600\fR -.TP -\fB>kernel oplocks (G)\fR -For UNIXes that support kernel based \fIoplocks\fR -(currently only IRIX and the Linux 2.4 kernel), this parameter -allows the use of them to be turned on or off. -Kernel oplocks support allows Samba \fIoplocks -\fR to be broken whenever a local UNIX process or NFS operation -accesses a file that \fBsmbd\fR(8) has oplocked. This allows complete -data consistency between SMB/CIFS, NFS and local file access (and is -a \fBvery\fR cool feature :-). +\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&. -This parameter defaults to on, but is translated -to a no-op on systems that no not have the necessary kernel support. -You should never need to touch this parameter. -See also the \fIoplocks\fR -and \fIlevel2 oplocks -\fR parameters. +See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&. -Default: \fBkernel oplocks = yes\fR -.TP -\fB>lanman auth (G)\fR -This parameter determines whether or not \fBsmbd\fR(8) will attempt to authenticate users -using the LANMAN password hash. If disabled, only clients which support NT -password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not -Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host. -Default : \fBlanman auth = yes\fR -.TP -\fB>large readwrite (G)\fR -This parameter determines whether or not \fBsmbd\fR(8) supports the new 64k streaming -read and write varient SMB requests introduced -with Windows 2000. Note that due to Windows 2000 client redirector bugs -this requires Samba to be running on a 64-bit capable operating system such -as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with -Windows 2000 clients. Defaults to on. Not as tested as some other Samba -code paths. - -Default : \fBlarge readwrite = yes\fR -.TP -\fB>ldap admin dn (G)\fR -The \fIldap admin dn\fR defines the Distinguished -Name (DN) name used by Samba to contact the ldap server when retreiving -user account information. The \fIldap -admin dn\fR is used in conjunction with the admin dn password -stored in the \fIprivate/secrets.tdb\fR file. See the -\fBsmbpasswd\fR(8) man page for more information on how -to accmplish this. -.TP -\fB>ldap delete dn (G)\fR -This parameter specifies whether a delete -operation in the ldapsam deletes the complete entry or only the attributes -specific to Samba. - -Default : \fBldap delete dn = no\fR -.TP -\fB>ldap filter (G)\fR -This parameter specifies the RFC 2254 compliant LDAP search filter. -The default is to match the login name with the uid -attribute for all entries matching the sambaAccount -objectclass. Note that this filter should only return one entry. - -Default : \fBldap filter = (&(uid=%u)(objectclass=sambaAccount))\fR -.TP -\fB>ldap port (G)\fR -This parameter is only available if Samba has been -configure to include the \fB--with-ldapsam\fR option -at compile time. - -This option is used to control the tcp port number used to contact -the \fIldap server\fR. -The default is to use the stand LDAPS port 636. +See also the \fIpassword server\fR parameter and the \fIencrypted passwords\fR parameter\&. -See Also: ldap ssl -Default : \fBldap port = 636 ; if ldap ssl = on\fR +\fBSECURITY = SERVER\fR -Default : \fBldap port = 389 ; if ldap ssl = off\fR -.TP -\fB>ldap server (G)\fR -This parameter is only available if Samba has been -configure to include the \fB--with-ldapsam\fR option -at compile time. -This parameter should contain the FQDN of the ldap directory -server which should be queried to locate user account information. +In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box\&. If this fails it will revert to \fBsecurity = user\fR\&. It expects the \fIencrypted passwords\fR parameter to be set to \fByes\fR, unless the remote server does not support them\&. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid \fIsmbpasswd\fR file to check users against\&. See the documentation file in the \fIdocs/\fR directory \fIENCRYPTION\&.txt\fR for details on how to set this up\&. -Default : \fBldap server = localhost\fR -.TP -\fB>ldap ssl (G)\fR -This option is used to define whether or not Samba should -use SSL when connecting to the ldap server -This is \fBNOT\fR related to -Samba's previous SSL support which was enabled by specifying the -\fB--with-ssl\fR option to the \fIconfigure\fR -script. -The \fIldap ssl\fR can be set to one of three values: -.RS -.TP 0.2i -\(bu -\fIOff\fR = Never use SSL when querying the directory. -.TP 0.2i -\(bu -\fIStart_tls\fR = Use the LDAPv3 StartTLS extended operation -(RFC2830) for communicating with the directory server. -.TP 0.2i -\(bu -\fIOn\fR = -Use SSL on the ldaps port when contacting the -\fIldap server\fR. Only -available when the backwards-compatiblity \fB --with-ldapsam\fR option is specified -to configure. See \fIpassdb backend\fR -.RE +\fBNote\fR this mode of operation has significant pitfalls, due to the fact that is activly initiates a man-in-the-middle attack on the remote SMB server\&. In particular, this mode of operation can cause significant resource consuption on the PDC, as it must maintain an active connection for the duration of the user's session\&. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authenticaions to the Samba server may fail\&. (From a single client, till it disconnects)\&. -Default : \fBldap ssl = start_tls\fR -.TP -\fB>ldap suffix (G)\fR -Specifies where user and machine accounts are added to the tree. Can be overriden by \fBldap user suffix\fR and \fBldap machine suffix\fR. It also used as the base dn for all ldap searches. -Default : \fBnone\fR -.TP -\fB>ldap user suffix (G)\fR -It specifies where users are added to the tree. +\fBNote\fR that from the client's point of view \fBsecurity = server\fR is the same as \fBsecurity = user\fR\&. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\&. -Default : \fBnone\fR -.TP -\fB>ldap machine suffix (G)\fR -It specifies where machines should be -added to the ldap tree. -Default : \fBnone\fR -.TP -\fB>ldap passwd sync (G)\fR -This option is used to define whether -or not Samba should sync the LDAP password with the NT -and LM hashes for normal accounts (NOT for -workstation, server or domain trusts) on a password -change via SAMBA. +\fBNote\fR that the name of the resource being requested is \fBnot\fR sent to the server until after the server has successfully authenticated the client\&. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the \fIguest account\fR\&. See the \fImap to guest\fR parameter for details on doing this\&. -The \fIldap passwd sync\fR can be set to one of three values: -.RS -.TP 0.2i -\(bu -\fIYes\fR = Try to update the LDAP, NT and LM passwords and update the pwdLastSet time. -.TP 0.2i -\(bu -\fINo\fR = Update NT and LM passwords and update the pwdLastSet time. -.TP 0.2i -\(bu -\fIOnly\fR = Only update the LDAP password and let the LDAP server do the rest. -.RE -Default : \fBldap passwd sync = no\fR -.TP -\fB>ldap trust ids (G)\fR -Normally, Samba validates each entry -in the LDAP server against getpwnam(). This allows -LDAP to be used for Samba with the unix system using -NIS (for example) and also ensures that Samba does not -present accounts that do not otherwise exist. +See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION\&. -This option is used to disable this functionality, and -instead to rely on the presence of the appropriate -attributes in LDAP directly, which can result in a -significant performance boost in some situations. -Setting this option to yes effectivly assumes -that the local machine is running \fBnss_ldap\fR against the -same LDAP server. -Default: \fBldap trust ids = No\fR -.TP -\fB>level2 oplocks (S)\fR -This parameter controls whether Samba supports -level2 (read-only) oplocks on a share. - -Level2, or read-only oplocks allow Windows NT clients -that have an oplock on a file to downgrade from a read-write oplock -to a read-only oplock once a second client opens the file (instead -of releasing all oplocks on a second open, as in traditional, -exclusive oplocks). This allows all openers of the file that -support level2 oplocks to cache the file for read-ahead only (ie. -they may not cache writes or lock requests) and increases performance -for many accesses of files that are not commonly written (such as -application .EXE files). - -Once one of the clients which have a read-only oplock -writes to the file all clients are notified (no reply is needed -or waited for) and told to break their oplocks to "none" and -delete any read-ahead caches. - -It is recommended that this parameter be turned on -to speed access to shared executables. - -For more discussions on level2 oplocks see the CIFS spec. - -Currently, if \fIkernel -oplocks\fR are supported then level2 oplocks are -not granted (even if this parameter is set to yes). -Note also, the \fIoplocks\fR -parameter must be set to yes on this share in order for -this parameter to have any effect. - -See also the \fIoplocks\fR -and \fIkernel oplocks\fR -parameters. +See also the \fIpassword server\fR parameter and the \fIencrypted passwords\fR parameter\&. -Default: \fBlevel2 oplocks = yes\fR -.TP -\fB>lm announce (G)\fR -This parameter determines if \fBnmbd\fR(8) will produce Lanman announce -broadcasts that are needed by OS/2 clients in order for them to see -the Samba server in their browse list. This parameter can have three -values, yes, no, or -auto. The default is auto. -If set to no Samba will never produce these -broadcasts. If set to yes Samba will produce -Lanman announce broadcasts at a frequency set by the parameter -\fIlm interval\fR. If set to auto -Samba will not send Lanman announce broadcasts by default but will -listen for them. If it hears such a broadcast on the wire it will -then start sending them at a frequency set by the parameter -\fIlm interval\fR. - -See also \fIlm interval -\fR. -Default: \fBlm announce = auto\fR +Default: \fBsecurity = USER\fR -Example: \fBlm announce = yes\fR -.TP -\fB>lm interval (G)\fR -If Samba is set to produce Lanman announce -broadcasts needed by OS/2 clients (see the \fIlm announce\fR parameter) then this -parameter defines the frequency in seconds with which they will be -made. If this is set to zero then no Lanman announcements will be -made despite the setting of the \fIlm announce\fR -parameter. -See also \fIlm -announce\fR. +Example: \fBsecurity = DOMAIN\fR -Default: \fBlm interval = 60\fR -Example: \fBlm interval = 120\fR .TP -\fB>load printers (G)\fR -A boolean variable that controls whether all -printers in the printcap will be loaded for browsing by default. -See the printers section for -more details. +server schannel (G) +This controls whether the server offers or even demands the use of the netlogon schannel\&. \fIserver schannel = no\fR does not offer the schannel, \fIserver schannel = auto\fR offers the schannel but does not enforce it, and \fIserver schannel = yes\fR denies access if the client is not able to speak netlogon schannel\&. This is only the case for Windows NT4 before SP4\&. -Default: \fBload printers = yes\fR -.TP -\fB>local master (G)\fR -This option allows \fBnmbd\fR(8) to try and become a local master browser -on a subnet. If set to no then \fB nmbd\fR will not attempt to become a local master browser -on a subnet and will also lose in all browsing elections. By -default this value is set to yes. Setting this value to yes doesn't -mean that Samba will \fBbecome\fR the local master -browser on a subnet, just that \fBnmbd\fR will \fB participate\fR in elections for local master browser. -Setting this value to no will cause \fBnmbd\fR -\fBnever\fR to become a local master browser. +Please note that with this set to \fIno\fR you will have to apply the WindowsXP requireSignOrSeal-Registry patch found in the docs/Registry subdirectory\&. -Default: \fBlocal master = yes\fR -.TP -\fB>lock dir (G)\fR -Synonym for \fI lock directory\fR. -.TP -\fB>lock directory (G)\fR -This option specifies the directory where lock -files will be placed. The lock files are used to implement the -\fImax connections\fR -option. -Default: \fBlock directory = ${prefix}/var/locks\fR +Default: \fBserver schannel = auto\fR -Example: \fBlock directory = /var/run/samba/locks\fR -.TP -\fB>lock spin count (G)\fR -This parameter controls the number of times -that smbd should attempt to gain a byte range lock on the -behalf of a client request. Experiments have shown that -Windows 2k servers do not reply with a failure if the lock -could not be immediately granted, but try a few more times -in case the lock could later be aquired. This behavior -is used to support PC database formats such as MS Access -and FoxPro. -Default: \fBlock spin count = 2\fR -.TP -\fB>lock spin time (G)\fR -The time in microseconds that smbd should -pause before attempting to gain a failed lock. See -\fIlock spin -count\fR for more details. +Example: \fBserver schannel = yes\fR + -Default: \fBlock spin time = 10\fR .TP -\fB>locking (S)\fR -This controls whether or not locking will be -performed by the server in response to lock requests from the -client. +server string (G) +This controls what string will show up in the printer comment box in print manager and next to the IPC connection in \fBnet view\fR\&. It can be any string that you wish to show to your users\&. -If \fBlocking = no\fR, all lock and unlock -requests will appear to succeed and all lock queries will report -that the file in question is available for locking. -If \fBlocking = yes\fR, real locking will be performed -by the server. +It also sets what will appear in browse lists next to the machine name\&. -This option \fBmay\fR be useful for read-only -filesystems which \fBmay\fR not need locking (such as -CDROM drives), although setting this parameter of no -is not really recommended even in this case. -Be careful about disabling locking either globally or in a -specific service, as lack of locking may result in data corruption. -You should never need to set this parameter. +A \fI%v\fR will be replaced with the Samba version number\&. -Default: \fBlocking = yes\fR -.TP -\fB>log file (G)\fR -This option allows you to override the name -of the Samba log file (also known as the debug file). -This option takes the standard substitutions, allowing -you to have separate log files for each user or machine. +A \fI%h\fR will be replaced with the hostname\&. -Example: \fBlog file = /usr/local/samba/var/log.%m -\fR -.TP -\fB>log level (G)\fR -The value of the parameter (a astring) allows -the debug level (logging level) to be specified in the -\fIsmb.conf\fR file. This parameter has been -extended since the 2.2.x series, now it allow to specify the debug -level for multiple debug classes. This is to give greater -flexibility in the configuration of the system. -The default will be the log level specified on -the command line or level zero if none was specified. +Default: \fBserver string = Samba %v\fR -Example: \fBlog level = 3 passdb:5 auth:10 winbind:2 -\fR -.TP -\fB>logon drive (G)\fR -This parameter specifies the local path to -which the home directory will be connected (see \fIlogon home\fR) -and is only used by NT Workstations. -Note that this option is only useful if Samba is set up as a -logon server. +Example: \fBserver string = University of GNUs Samba Server\fR -Default: \fBlogon drive = z:\fR -Example: \fBlogon drive = h:\fR .TP -\fB>logon home (G)\fR -This parameter specifies the home directory -location when a Win95/98 or NT Workstation logs into a Samba PDC. -It allows you to do - -C:\\> \fBNET USE H: /HOME\fR +set directory (S) +If \fBset directory = no\fR, then users of the service may not use the setdir command to change directory\&. -from a command prompt, for example. -This option takes the standard substitutions, allowing -you to have separate logon scripts for each user or machine. +The \fBsetdir\fR command is only implemented in the Digital Pathworks client\&. See the Pathworks documentation for details\&. -This parameter can be used with Win9X workstations to ensure -that roaming profiles are stored in a subdirectory of the user's -home directory. This is done in the following way: -\fBlogon home = \\\\%N\\%U\\profile\fR +Default: \fBset directory = no\fR -This tells Samba to return the above string, with -substitutions made when a client requests the info, generally -in a NetUserGetInfo request. Win9X clients truncate the info to -\\\\server\\share when a user does \fBnet use /home\fR -but use the whole string when dealing with profiles. -Note that in prior versions of Samba, the \fIlogon path\fR was returned rather than -\fIlogon home\fR. This broke \fBnet use -/home\fR but allowed profiles outside the home directory. -The current implementation is correct, and can be used for -profiles if you use the above trick. +.TP +set primary group script (G) +Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups\&. This script sets the primary group in the unix userdatase when an administrator sets the primary group from the windows user manager or when fetching a SAM with \fBnet rpc vampire\fR\&. \fI%u\fR will be replaced with the user whose primary group is to be set\&. \fI%g\fR will be replaced with the group to set\&. -This option is only useful if Samba is set up as a logon -server. -Default: \fBlogon home = "\\\\%N\\%U"\fR +Default: \fBNo default value\fR -Example: \fBlogon home = "\\\\remote_smb_server\\%U"\fR -.TP -\fB>logon path (G)\fR -This parameter specifies the home directory -where roaming profiles (NTuser.dat etc files for Windows NT) are -stored. Contrary to previous versions of these manual pages, it has -nothing to do with Win 9X roaming profiles. To find out how to -handle roaming profiles for Win 9X system, see the \fIlogon home\fR parameter. -This option takes the standard substitutions, allowing you -to have separate logon scripts for each user or machine. It also -specifies the directory from which the "Application Data", -(\fIdesktop\fR, \fIstart menu\fR, -\fInetwork neighborhood\fR, \fIprograms\fR -and other folders, and their contents, are loaded and displayed on -your Windows NT client. +Example: \fBset primary group script = /usr/sbin/usermod -g '%g' '%u'\fR -The share and the path must be readable by the user for -the preferences and directories to be loaded onto the Windows NT -client. The share must be writeable when the user logs in for the first -time, in order that the Windows NT client can create the NTuser.dat -and other directories. -Thereafter, the directories and any of the contents can, -if required, be made read-only. It is not advisable that the -NTuser.dat file be made read-only - rename it to NTuser.man to -achieve the desired effect (a \fBMAN\fRdatory -profile). +.TP +share modes (S) +This enables or disables the honoring of the \fIshare modes\fR during a file open\&. These modes are used by clients to gain exclusive read or write access to a file\&. -Windows clients can sometimes maintain a connection to -the [homes] share, even though there is no user logged in. -Therefore, it is vital that the logon path does not include a -reference to the homes share (i.e. setting this parameter to -\\%N\\%U\\profile_path will cause problems). -This option takes the standard substitutions, allowing -you to have separate logon scripts for each user or machine. +These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared memory (almost all do)\&. -Note that this option is only useful if Samba is set up -as a logon server. -Default: \fBlogon path = \\\\%N\\%U\\profile\fR +The share modes that are enabled by this option are \fBDENY_DOS\fR, \fBDENY_ALL\fR, \fBDENY_READ\fR, \fBDENY_WRITE\fR, \fBDENY_NONE\fR and \fBDENY_FCB\fR\&. -Example: \fBlogon path = \\\\PROFILESERVER\\PROFILE\\%U\fR -.TP -\fB>logon script (G)\fR -This parameter specifies the batch file (.bat) or -NT command file (.cmd) to be downloaded and run on a machine when -a user successfully logs in. The file must contain the DOS -style CR/LF line endings. Using a DOS-style editor to create the -file is recommended. -The script must be a relative path to the [netlogon] -service. If the [netlogon] service specifies a \fIpath\fR of \fI/usr/local/samba/netlogon -\fR, and \fBlogon script = STARTUP.BAT\fR, then -the file that will be downloaded is: +This option gives full share compatibility and enabled by default\&. -\fI/usr/local/samba/netlogon/STARTUP.BAT\fR -The contents of the batch file are entirely your choice. A -suggested command would be to add \fBNET TIME \\\\SERVER /SET -/YES\fR, to force every machine to synchronize clocks with -the same time server. Another use would be to add \fBNET USE -U: \\\\SERVER\\UTILS\fR for commonly used utilities, or \fB NET USE Q: \\\\SERVER\\ISO9001_QA\fR for example. +You should \fBNEVER\fR turn this parameter off as many Windows applications will break if you do so\&. -Note that it is particularly important not to allow write -access to the [netlogon] share, or to grant users write permission -on the batch files in a secure environment, as this would allow -the batch files to be arbitrarily modified and security to be -breached. -This option takes the standard substitutions, allowing you -to have separate logon scripts for each user or machine. - -This option is only useful if Samba is set up as a logon -server. +Default: \fBshare modes = yes\fR -Default: \fBno logon script defined\fR -Example: \fBlogon script = scripts\\%U.bat\fR .TP -\fB>lppause command (S)\fR -This parameter specifies the command to be -executed on the server host in order to stop printing or spooling -a specific print job. +short preserve case (S) +This boolean parameter controls if new files which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the \fIdefault case \fR\&. This option can be use with \fBpreserve case = yes\fR to permit long filenames to retain their case, while short names are lowered\&. -This command should be a program or script which takes -a printer name and job number to pause the print job. One way -of implementing this is by using job priorities, where jobs -having a too low priority won't be sent to the printer. -If a \fI%p\fR is given then the printer name -is put in its place. A \fI%j\fR is replaced with -the job number (an integer). On HPUX (see \fIprinting=hpux -\fR), if the \fI-p%p\fR option is added -to the lpq command, the job will show up with the correct status, i.e. -if the job priority is lower than the set fence priority it will -have the PAUSED status, whereas if the priority is equal or higher it -will have the SPOOLED or PRINTING status. +See the section on NAME MANGLING\&. -Note that it is good practice to include the absolute path -in the lppause command as the PATH may not be available to the server. -See also the \fIprinting -\fR parameter. +Default: \fBshort preserve case = yes\fR -Default: Currently no default value is given to -this string, unless the value of the \fIprinting\fR -parameter is SYSV, in which case the default is : -\fBlp -i %p-%j -H hold\fR +.TP +show add printer wizard (G) +With the introduction of MS-RPC based printing support for Windows NT/2000 client in Samba 2\&.2, a "Printers\&.\&.\&." folder will appear on Samba hosts in the share listing\&. Normally this folder will contain an icon for the MS Add Printer Wizard (APW)\&. However, it is possible to disable this feature regardless of the level of privilege of the connected user\&. -or if the value of the \fIprinting\fR parameter -is SOFTQ, then the default is: -\fBqstat -s -j%j -h\fR +Under normal circumstances, the Windows NT/2000 client will open a handle on the printer server with OpenPrinterEx() asking for Administrator privileges\&. If the user does not have administrative access on the print server (i\&.e is not root or a member of the \fIprinter admin\fR group), the OpenPrinterEx() call fails and the client makes another open call with a request for a lower privilege level\&. This should succeed, however the APW icon will not be displayed\&. -Example for HPUX: \fBlppause command = /usr/bin/lpalt -%p-%j -p0\fR -.TP -\fB>lpq cache time (G)\fR -This controls how long lpq info will be cached -for to prevent the \fBlpq\fR command being called too -often. A separate cache is kept for each variation of the \fB lpq\fR command used by the system, so if you use different -\fBlpq\fR commands for different users then they won't -share cache information. -The cache files are stored in \fI/tmp/lpq.xxxx\fR -where xxxx is a hash of the \fBlpq\fR command in use. +Disabling the \fIshow add printer wizard\fR parameter will always cause the OpenPrinterEx() on the server to fail\&. Thus the APW icon will never be displayed\&. \fB Note :\fRThis does not prevent the same user from having administrative privilege on an individual printer\&. -The default is 10 seconds, meaning that the cached results -of a previous identical \fBlpq\fR command will be used -if the cached data is less than 10 seconds old. A large value may -be advisable if your \fBlpq\fR command is very slow. -A value of 0 will disable caching completely. +See also \fIaddprinter command\fR, \fIdeleteprinter command\fR, \fIprinter admin\fR -See also the \fIprinting -\fR parameter. -Default: \fBlpq cache time = 10\fR +Default :\fBshow add printer wizard = yes\fR + -Example: \fBlpq cache time = 30\fR .TP -\fB>lpq command (S)\fR -This parameter specifies the command to be -executed on the server host in order to obtain \fBlpq -\fR-style printer status information. +shutdown script (G) +\fBThis parameter only exists in the HEAD cvs branch\fR This a full path name to a script called by \fBsmbd\fR(8) that should start a shutdown procedure\&. -This command should be a program or script which -takes a printer name as its only parameter and outputs printer -status information. -Currently nine styles of printer status information -are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. -This covers most UNIX systems. You control which type is expected -using the \fIprinting =\fR option. +This command will be run as the user connected to the server\&. -Some clients (notably Windows for Workgroups) may not -correctly send the connection number for the printer they are -requesting status information about. To get around this, the -server reports on the first printer service connected to by the -client. This only happens if the connection number sent is invalid. -If a \fI%p\fR is given then the printer name -is put in its place. Otherwise it is placed at the end of the -command. +%m %t %r %f parameters are expanded: -Note that it is good practice to include the absolute path -in the \fIlpq command\fR as the \fB$PATH -\fR may not be available to the server. When compiled with -the CUPS libraries, no \fIlpq command\fR is -needed because smbd will make a library call to obtain the -print queue listing. -See also the \fIprinting -\fR parameter. +\fI%m\fR will be substituted with the shutdown message sent to the server\&. -Default: \fBdepends on the setting of \fI printing\fB\fR +\fI%t\fR will be substituted with the number of seconds to wait before effectively starting the shutdown procedure\&. -Example: \fBlpq command = /usr/bin/lpq -P%p\fR -.TP -\fB>lpresume command (S)\fR -This parameter specifies the command to be -executed on the server host in order to restart or continue -printing or spooling a specific print job. +\fI%r\fR will be substituted with the switch \fB-r\fR\&. It means reboot after shutdown for NT\&. -This command should be a program or script which takes -a printer name and job number to resume the print job. See -also the \fIlppause command -\fR parameter. +\fI%f\fR will be substituted with the switch \fB-f\fR\&. It means force the shutdown even if applications do not respond for NT\&. -If a \fI%p\fR is given then the printer name -is put in its place. A \fI%j\fR is replaced with -the job number (an integer). +Default: \fBNone\fR\&. -Note that it is good practice to include the absolute path -in the \fIlpresume command\fR as the PATH may not -be available to the server. -See also the \fIprinting -\fR parameter. +Example: \fBabort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f\fR -Default: Currently no default value is given -to this string, unless the value of the \fIprinting\fR -parameter is SYSV, in which case the default is : -\fBlp -i %p-%j -H resume\fR +Shutdown script example: +.nf -or if the value of the \fIprinting\fR parameter -is SOFTQ, then the default is: +#!/bin/bash + +$time=0 +let "time/60" +let "time++" -\fBqstat -s -j%j -r\fR +/sbin/shutdown $3 $4 +$time $1 & +.fi -Example for HPUX: \fBlpresume command = /usr/bin/lpalt -%p-%j -p2\fR -.TP -\fB>lprm command (S)\fR -This parameter specifies the command to be -executed on the server host in order to delete a print job. +Shutdown does not return so we need to launch it in background\&. -This command should be a program or script which takes -a printer name and job number, and deletes the print job. -If a \fI%p\fR is given then the printer name -is put in its place. A \fI%j\fR is replaced with -the job number (an integer). +See also \fIabort shutdown script\fR\&. -Note that it is good practice to include the absolute -path in the \fIlprm command\fR as the PATH may not be -available to the server. -See also the \fIprinting -\fR parameter. +.TP +smb passwd file (G) +This option sets the path to the encrypted smbpasswd file\&. By default the path to the smbpasswd file is compiled into Samba\&. -Default: \fBdepends on the setting of \fIprinting -\fB\fR -Example 1: \fBlprm command = /usr/bin/lprm -P%p %j -\fR +Default: \fBsmb passwd file = ${prefix}/private/smbpasswd\fR -Example 2: \fBlprm command = /usr/bin/cancel %p-%j -\fR -.TP -\fB>machine password timeout (G)\fR -If a Samba server is a member of a Windows -NT Domain (see the security = domain) -parameter) then periodically a running smbd(8) process will try and change the MACHINE ACCOUNT -PASSWORD stored in the TDB called \fIprivate/secrets.tdb -\fR. This parameter specifies how often this password -will be changed, in seconds. The default is one week (expressed in -seconds), the same as a Windows NT Domain member server. -See also \fBsmbpasswd\fR(8), and the security = domain) parameter. +Example: \fBsmb passwd file = /etc/samba/smbpasswd\fR + -Default: \fBmachine password timeout = 604800\fR .TP -\fB>magic output (S)\fR -This parameter specifies the name of a file -which will contain output created by a magic script (see the -\fImagic script\fR -parameter below). +smb ports (G) +Specifies which ports the server should listen on for SMB traffic\&. -Warning: If two clients use the same \fImagic script -\fR in the same directory the output file content -is undefined. -Default: \fBmagic output = .out -\fR +Default: \fBsmb ports = 445 139\fR -Example: \fBmagic output = myfile.txt\fR -.TP -\fB>magic script (S)\fR -This parameter specifies the name of a file which, -if opened, will be executed by the server when the file is closed. -This allows a UNIX script to be sent to the Samba host and -executed on behalf of the connected user. -Scripts executed in this way will be deleted upon -completion assuming that the user has the appropriate level -of privilege and the file permissions allow the deletion. +.TP +socket address (G) +This option allows you to control what address Samba will listen for connections on\&. This is used to support multiple virtual interfaces on the one server, each with a different configuration\&. -If the script generates output, output will be sent to -the file specified by the \fI magic output\fR parameter (see above). -Note that some shells are unable to interpret scripts -containing CR/LF instead of CR as -the end-of-line marker. Magic scripts must be executable -\fBas is\fR on the host, which for some hosts and -some shells will require filtering at the DOS end. +By default Samba will accept connections on any address\&. -Magic scripts are \fBEXPERIMENTAL\fR and -should \fBNOT\fR be relied upon. -Default: \fBNone. Magic scripts disabled.\fR +Example: \fBsocket address = 192.168.2.20\fR -Example: \fBmagic script = user.csh\fR -.TP -\fB>mangle case (S)\fR -See the section on NAME MANGLING -Default: \fBmangle case = no\fR .TP -\fB>mangled map (S)\fR -This is for those who want to directly map UNIX -file names which cannot be represented on Windows/DOS. The mangling -of names is not always what is needed. In particular you may have -documents with file extensions that differ between DOS and UNIX. -For example, under UNIX it is common to use \fI.html\fR -for HTML files, whereas under Windows/DOS \fI.htm\fR -is more commonly used. +socket options (G) +This option allows you to set socket options to be used when talking with the client\&. -So to map \fIhtml\fR to \fIhtm\fR -you would use: -\fBmangled map = (*.html *.htm)\fR +Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned\&. -One very useful case is to remove the annoying \fI;1 -\fR off the ends of filenames on some CDROMs (only visible -under some UNIXes). To do this use a map of (*;1 *;). -Default: \fBno mangled map\fR +This option will typically be used to tune your Samba server for optimal performance for your local network\&. There is no way that Samba can know what the optimal parameters are for your net, so you must experiment and choose them yourself\&. We strongly suggest you read the appropriate documentation for your operating system first (perhaps \fBman setsockopt\fR will help)\&. -Example: \fBmangled map = (*;1 *;)\fR -.TP -\fB>mangled names (S)\fR -This controls whether non-DOS names under UNIX -should be mapped to DOS-compatible names ("mangled") and made visible, -or whether non-DOS names should simply be ignored. -See the section on NAME MANGLING for details on how to control the mangling process. +You may find that on some systems Samba will say "Unknown socket option" when you supply an option\&. This means you either incorrectly typed it or you need to add an include file to includes\&.h for your OS\&. If the latter is the case please send the patch to samba-technical@samba\&.org\&. -If mangling is used then the mangling algorithm is as follows: -.RS -.TP 0.2i -\(bu -The first (up to) five alphanumeric characters -before the rightmost dot of the filename are preserved, forced -to upper case, and appear as the first (up to) five characters -of the mangled name. -.TP 0.2i -\(bu -A tilde "~" is appended to the first part of the mangled -name, followed by a two-character unique sequence, based on the -original root name (i.e., the original filename minus its final -extension). The final extension is included in the hash calculation -only if it contains any upper case characters or is longer than three -characters. - -Note that the character to use may be specified using -the \fImangling char\fR -option, if you don't like '~'. -.TP 0.2i -\(bu -The first three alphanumeric characters of the final -extension are preserved, forced to upper case and appear as the -extension of the mangled name. The final extension is defined as that -part of the original filename after the rightmost dot. If there are no -dots in the filename, the mangled name will have no extension (except -in the case of "hidden files" - see below). -.TP 0.2i -\(bu -Files whose UNIX name begins with a dot will be -presented as DOS hidden files. The mangled name will be created as -for other filenames, but with the leading dot removed and "___" as -its extension regardless of actual original extension (that's three -underscores). -.RE -The two-digit hash value consists of upper case -alphanumeric characters. +Any of the supported socket options may be combined in any way you like, as long as your OS allows it\&. -This algorithm can cause name collisions only if files -in a directory share the same first five alphanumeric characters. -The probability of such a clash is 1/1300. -The name mangling (if enabled) allows a file to be -copied between UNIX directories from Windows/DOS while retaining -the long UNIX filename. UNIX files can be renamed to a new extension -from Windows/DOS and will retain the same basename. Mangled names -do not change between sessions. +This is the list of socket options currently settable using this option: -Default: \fBmangled names = yes\fR -.TP -\fB>mangling method (G)\fR -controls the algorithm used for the generating -the mangled names. Can take two different values, "hash" and -"hash2". "hash" is the default and is the algorithm that has been -used in Samba for many years. "hash2" is a newer and considered -a better algorithm (generates less collisions) in the names. -However, many Win32 applications store the mangled names and so -changing to the new algorithm must not be done -lightly as these applications may break unless reinstalled. -Default: \fBmangling method = hash2\fR +SO_KEEPALIVE -Example: \fBmangling method = hash\fR -.TP -\fB>mangle prefix (G)\fR -controls the number of prefix -characters from the original name used when generating -the mangled names. A larger value will give a weaker -hash and therefore more name collisions. The minimum -value is 1 and the maximum value is 6. +SO_REUSEADDR -Default: \fBmangle prefix = 1\fR +SO_BROADCAST -Example: \fBmangle prefix = 4\fR -.TP -\fB>mangled stack (G)\fR -This parameter controls the number of mangled names -that should be cached in the Samba server \fBsmbd\fR(8). +TCP_NODELAY -This stack is a list of recently mangled base names -(extensions are only maintained if they are longer than 3 characters -or contains upper case characters). +IPTOS_LOWDELAY -The larger this value, the more likely it is that mangled -names can be successfully converted to correct long UNIX names. -However, large stack sizes will slow most directory accesses. Smaller -stacks save memory in the server (each stack element costs 256 bytes). +IPTOS_THROUGHPUT -It is not possible to absolutely guarantee correct long -filenames, so be prepared for some surprises! +SO_SNDBUF * -Default: \fBmangled stack = 50\fR +SO_RCVBUF * -Example: \fBmangled stack = 100\fR -.TP -\fB>mangling char (S)\fR -This controls what character is used as -the \fBmagic\fR character in name mangling. The default is a '~' -but this may interfere with some software. Use this option to set -it to whatever you prefer. +SO_SNDLOWAT * -Default: \fBmangling char = ~\fR +SO_RCVLOWAT * -Example: \fBmangling char = ^\fR -.TP -\fB>map archive (S)\fR -This controls whether the DOS archive attribute -should be mapped to the UNIX owner execute bit. The DOS archive bit -is set when a file has been modified since its last backup. One -motivation for this option it to keep Samba/your PC from making -any file it touches from becoming executable under UNIX. This can -be quite annoying for shared source code, documents, etc... +Those marked with a \fB'*'\fR take an integer argument\&. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don't specify 1 or 0\&. -Note that this requires the \fIcreate mask\fR -parameter to be set such that owner execute bit is not masked out -(i.e. it must include 100). See the parameter \fIcreate mask\fR for details. -Default: \fBmap archive = yes\fR -.TP -\fB>map hidden (S)\fR -This controls whether DOS style hidden files -should be mapped to the UNIX world execute bit. +To specify an argument use the syntax SOME_OPTION = VALUE for example \fBSO_SNDBUF = 8192\fR\&. Note that you must not have any spaces before or after the = sign\&. -Note that this requires the \fIcreate mask\fR -to be set such that the world execute bit is not masked out (i.e. -it must include 001). See the parameter \fIcreate mask\fR for details. -Default: \fBmap hidden = no\fR -.TP -\fB>map system (S)\fR -This controls whether DOS style system files -should be mapped to the UNIX group execute bit. +If you are on a local network then a sensible option might be: -Note that this requires the \fIcreate mask\fR -to be set such that the group execute bit is not masked out (i.e. -it must include 010). See the parameter \fIcreate mask\fR for details. -Default: \fBmap system = no\fR -.TP -\fB>map to guest (G)\fR -This parameter is only useful in security modes other than \fIsecurity = share\fR -- i.e. user, server, -and domain. +\fBsocket options = IPTOS_LOWDELAY\fR -This parameter can take three different values, which tell -\fBsmbd\fR(8) what to do with user -login requests that don't match a valid UNIX user in some way. -The three settings are : -.RS -.TP 0.2i -\(bu -Never - Means user login -requests with an invalid password are rejected. This is the -default. -.TP 0.2i -\(bu -Bad User - Means user -logins with an invalid password are rejected, unless the username -does not exist, in which case it is treated as a guest login and -mapped into the \fI guest account\fR. -.TP 0.2i -\(bu -Bad Password - Means user logins -with an invalid password are treated as a guest login and mapped -into the guest account. Note that -this can cause problems as it means that any user incorrectly typing -their password will be silently logged on as "guest" - and -will not know the reason they cannot access files they think -they should - there will have been no message given to them -that they got their password wrong. Helpdesk services will -\fBhate\fR you if you set the \fImap to -guest\fR parameter this way :-). -.RE +If you have a local network then you could try: -Note that this parameter is needed to set up "Guest" -share services when using \fIsecurity\fR modes other than -share. This is because in these modes the name of the resource being -requested is \fBnot\fR sent to the server until after -the server has successfully authenticated the client so the server -cannot make authentication decisions at the correct time (connection -to the share) for "Guest" shares. -For people familiar with the older Samba releases, this -parameter maps to the old compile-time setting of the GUEST_SESSSETUP value in local.h. +\fBsocket options = IPTOS_LOWDELAY TCP_NODELAY\fR -Default: \fBmap to guest = Never\fR -Example: \fBmap to guest = Bad User\fR -.TP -\fB>max connections (S)\fR -This option allows the number of simultaneous -connections to a service to be limited. If \fImax connections -\fR is greater than 0 then connections will be refused if -this number of connections to the service are already open. A value -of zero mean an unlimited number of connections may be made. +If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT\&. -Record lock files are used to implement this feature. The -lock files will be stored in the directory specified by the \fIlock directory\fR -option. -Default: \fBmax connections = 0\fR +Note that several of the options may cause your Samba server to fail completely\&. Use these options with caution! -Example: \fBmax connections = 10\fR -.TP -\fB>max disk size (G)\fR -This option allows you to put an upper limit -on the apparent size of disks. If you set this option to 100 -then all shares will appear to be not larger than 100 MB in -size. -Note that this option does not limit the amount of -data you can put on the disk. In the above case you could still -store much more than 100 MB on the disk, but if a client ever asks -for the amount of free disk space or the total disk size then the -result will be bounded by the amount specified in \fImax -disk size\fR. +Default: \fBsocket options = TCP_NODELAY\fR -This option is primarily useful to work around bugs -in some pieces of software that can't handle very large disks, -particularly disks over 1GB in size. -A \fImax disk size\fR of 0 means no limit. +Example: \fBsocket options = IPTOS_LOWDELAY\fR -Default: \fBmax disk size = 0\fR -Example: \fBmax disk size = 1000\fR .TP -\fB>max log size (G)\fR -This option (an integer in kilobytes) specifies -the max size the log file should grow to. Samba periodically checks -the size and if it is exceeded it will rename the file, adding -a \fI.old\fR extension. +source environment (G) +This parameter causes Samba to set environment variables as per the content of the file named\&. -A size of 0 means no limit. -Default: \fBmax log size = 5000\fR +If the value of this parameter starts with a "|" character then Samba will treat that value as a pipe command to open and will set the environment variables from the output of the pipe\&. -Example: \fBmax log size = 1000\fR -.TP -\fB>max mux (G)\fR -This option controls the maximum number of -outstanding simultaneous SMB operations that Samba tells the client -it will allow. You should never need to set this parameter. -Default: \fBmax mux = 50\fR -.TP -\fB>max open files (G)\fR -This parameter limits the maximum number of -open files that one \fBsmbd\fR(8) file -serving process may have open for a client at any one time. The -default for this parameter is set very high (10,000) as Samba uses -only one bit per unopened file. +The contents of the file or the output of the pipe should be formatted as the output of the standard Unix \fBenv(1)\fR command\&. This is of the form: -The limit of the number of open files is usually set -by the UNIX per-process file descriptor limit rather than -this parameter so you should never need to touch this parameter. -Default: \fBmax open files = 10000\fR -.TP -\fB>max print jobs (S)\fR -This parameter limits the maximum number of -jobs allowable in a Samba printer queue at any given moment. -If this number is exceeded, \fBsmbd\fR(8) will remote "Out of Space" to the client. -See all \fItotal -print jobs\fR. +Example environment entry: -Default: \fBmax print jobs = 1000\fR -Example: \fBmax print jobs = 5000\fR -.TP -\fB>max protocol (G)\fR -The value of the parameter (a string) is the highest -protocol level that will be supported by the server. +\fBSAMBA_NETBIOS_NAME = myhostname\fR -Possible values are : -.RS -.TP 0.2i -\(bu -CORE: Earliest version. No -concept of user names. -.TP 0.2i -\(bu -COREPLUS: Slight improvements on -CORE for efficiency. -.TP 0.2i -\(bu -LANMAN1: First \fB modern\fR version of the protocol. Long filename -support. -.TP 0.2i -\(bu -LANMAN2: Updates to Lanman1 protocol. -.TP 0.2i -\(bu -NT1: Current up to date version of -the protocol. Used by Windows NT. Known as CIFS. -.RE -Normally this option should not be set as the automatic -negotiation phase in the SMB protocol takes care of choosing -the appropriate protocol. +Default: \fBNo default value\fR -See also \fImin -protocol\fR -Default: \fBmax protocol = NT1\fR +Examples: \fBsource environment = |/etc/smb.conf.sh\fR -Example: \fBmax protocol = LANMAN1\fR -.TP -\fB>max smbd processes (G)\fR -This parameter limits the maximum number of -\fBsmbd(8)\fR -processes concurrently running on a system and is intended -as a stopgap to prevent degrading service to clients in the event -that the server has insufficient resources to handle more than this -number of connections. Remember that under normal operating -conditions, each user will have an \fBsmbd\fR(8) associated with him or her -to handle connections to all shares from a given host. -Default: \fBmax smbd processes = 0\fR ## no limit +Example: \fBsource environment = /usr/local/smb_env_vars\fR -Example: \fBmax smbd processes = 1000\fR -.TP -\fB>max ttl (G)\fR -This option tells \fBnmbd\fR(8) -what the default 'time to live' of NetBIOS names should be (in seconds) -when \fBnmbd\fR is requesting a name using either a -broadcast packet or from a WINS server. You should never need to -change this parameter. The default is 3 days. -Default: \fBmax ttl = 259200\fR .TP -\fB>max wins ttl (G)\fR -This option tells \fBsmbd\fR(8) when acting as a WINS server ( \fIwins support = yes\fR) what the maximum -\&'time to live' of NetBIOS names that \fBnmbd\fR -will grant will be (in seconds). You should never need to change this -parameter. The default is 6 days (518400 seconds). +stat cache size (G) +This parameter determines the number of entries in the \fIstat cache\fR\&. You should never need to change this parameter\&. -See also the \fImin -wins ttl\fR parameter. -Default: \fBmax wins ttl = 518400\fR -.TP -\fB>max xmit (G)\fR -This option controls the maximum packet size -that will be negotiated by Samba. The default is 65535, which -is the maximum. In some cases you may find you get better performance -with a smaller value. A value below 2048 is likely to cause problems. +Default: \fBstat cache size = 50\fR -Default: \fBmax xmit = 65535\fR -Example: \fBmax xmit = 8192\fR .TP -\fB>message command (G)\fR -This specifies what command to run when the -server receives a WinPopup style message. +stat cache (G) +This parameter determines if \fBsmbd\fR(8) will use a cache in order to speed up case insensitive name mappings\&. You should never need to change this parameter\&. -This would normally be a command that would -deliver the message somehow. How this is to be done is -up to your imagination. -An example is: +Default: \fBstat cache = yes\fR -\fBmessage command = csh -c 'xedit %s;rm %s' &\fR -This delivers the message using \fBxedit\fR, then -removes it afterwards. \fBNOTE THAT IT IS VERY IMPORTANT -THAT THIS COMMAND RETURN IMMEDIATELY\fR. That's why I -have the '&' on the end. If it doesn't return immediately then -your PCs may freeze when sending messages (they should recover -after 30 seconds, hopefully). +.TP +strict allocate (S) +This is a boolean that controls the handling of disk space allocation in the server\&. When this is set to \fByes\fR the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size\&. In UNIX terminology this means that Samba will stop creating sparse files\&. This can be slow on some systems\&. -All messages are delivered as the global guest user. -The command takes the standard substitutions, although \fI %u\fR won't work (\fI%U\fR may be better -in this case). -Apart from the standard substitutions, some additional -ones apply. In particular: -.RS -.TP 0.2i -\(bu -\fI%s\fR = the filename containing -the message. -.TP 0.2i -\(bu -\fI%t\fR = the destination that -the message was sent to (probably the server name). -.TP 0.2i -\(bu -\fI%f\fR = who the message -is from. -.RE +When strict allocate is \fBno\fR the server does sparse disk block allocation when a file is extended\&. -You could make this command send mail, or whatever else -takes your fancy. Please let us know of any really interesting -ideas you have. -Here's a way of sending the messages as mail to root: +Setting this to \fByes\fR can help Samba return out of quota messages on systems that are restricting the disk quota of users\&. -\fBmessage command = /bin/mail -s 'message from %f on -%m' root < %s; rm %s\fR -If you don't have a message command then the message -won't be delivered and Samba will tell the sender there was -an error. Unfortunately WfWg totally ignores the error code -and carries on regardless, saying that the message was delivered. +Default: \fBstrict allocate = no\fR -If you want to silently delete it then try: -\fBmessage command = rm %s\fR +.TP +strict locking (S) +This is a boolean that controls the handling of file locking in the server\&. When this is set to \fByes\fR the server will check every read and write access for file locks, and deny access if locks exist\&. This can be slow on some systems\&. -Default: \fBno message command\fR -Example: \fBmessage command = csh -c 'xedit %s; -rm %s' &\fR -.TP -\fB>min passwd length (G)\fR -Synonym for \fImin password length\fR. -.TP -\fB>min password length (G)\fR -This option sets the minimum length in characters -of a plaintext password that \fBsmbd\fR will accept when performing -UNIX password changing. +When strict locking is \fBno\fR the server does file lock checks only when the client explicitly asks for them\&. -See also \fIunix -password sync\fR, \fIpasswd program\fR and \fIpasswd chat debug\fR -\&. -Default: \fBmin password length = 5\fR -.TP -\fB>min print space (S)\fR -This sets the minimum amount of free disk -space that must be available before a user will be able to spool -a print job. It is specified in kilobytes. The default is 0, which -means a user can always spool a print job. +Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases \fBstrict locking = no\fR is preferable\&. -See also the \fIprinting -\fR parameter. -Default: \fBmin print space = 0\fR +Default: \fBstrict locking = no\fR + -Example: \fBmin print space = 2000\fR .TP -\fB>min protocol (G)\fR -The value of the parameter (a string) is the -lowest SMB protocol dialect than Samba will support. Please refer -to the \fImax protocol\fR -parameter for a list of valid protocol names and a brief description -of each. You may also wish to refer to the C source code in -\fIsource/smbd/negprot.c\fR for a listing of known protocol -dialects supported by clients. +strict sync (S) +Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk\&. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in kernel disk buffers has been safely stored onto stable storage\&. This is very slow and should only be done rarely\&. Setting this parameter to \fBno\fR (the default) means that \fBsmbd\fR(8) ignores the Windows applications requests for a sync call\&. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting\&. In addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies\&. -If you are viewing this parameter as a security measure, you should -also refer to the \fIlanman -auth\fR parameter. Otherwise, you should never need -to change this parameter. -Default : \fBmin protocol = CORE\fR +See also the \fIsync always\fR parameter\&. -Example : \fBmin protocol = NT1\fR # disable DOS -clients -.TP -\fB>min wins ttl (G)\fR -This option tells \fBnmbd\fR(8) -when acting as a WINS server (\fI wins support = yes\fR) what the minimum 'time to live' -of NetBIOS names that \fBnmbd\fR will grant will be (in -seconds). You should never need to change this parameter. The default -is 6 hours (21600 seconds). -Default: \fBmin wins ttl = 21600\fR -.TP -\fB>msdfs proxy (S)\fR -This parameter indicates that the share is a -stand-in for another CIFS share whose location is specified by -the value of the parameter. When clients attempt to connect to -this share, they are redirected to the proxied share using -the SMB-Dfs protocol. +Default: \fBstrict sync = no\fR -Only Dfs roots can act as proxy shares. Take a look at the -\fImsdfs root\fR -and -\fIhost msdfs\fR -options to find out how to set up a Dfs root share. -Example: \fBmsdfs proxy = \\\\\\\\otherserver\\\\someshare\fR .TP -\fB>msdfs root (S)\fR -This boolean parameter is only available if -Samba is configured and compiled with the \fB --with-msdfs\fR option. If set to yes, -Samba treats the share as a Dfs root and allows clients to browse -the distributed file system tree rooted at the share directory. -Dfs links are specified in the share directory by symbolic -links of the form \fImsdfs:serverA\\\\shareA,serverB\\\\shareB\fR -and so on. For more information on setting up a Dfs tree -on Samba, refer to "Hosting a Microsoft -Distributed File System tree on Samba" document. +strip dot (G) +This is a boolean that controls whether to strip trailing dots off UNIX filenames\&. This helps with some CDROMs that have filenames ending in a single dot\&. -See also \fIhost msdfs -\fR -Default: \fBmsdfs root = no\fR -.TP -\fB>name cache timeout (G)\fR -Specifies the number of seconds it takes before -entries in samba's hostname resolve cache time out. If -the timeout is set to 0. the caching is disabled. +Default: \fBstrip dot = no\fR -Default: \fBname cache timeout = 660\fR -Example: \fBname cache timeout = 0\fR .TP -\fB>name resolve order (G)\fR -This option is used by the programs in the Samba -suite to determine what naming services to use and in what order -to resolve host names to IP addresses. The option takes a space -separated string of name resolution options. - -The options are :"lmhosts", "host", "wins" and "bcast". They -cause names to be resolved as follows : -.RS -.TP 0.2i -\(bu -lmhosts : Lookup an IP -address in the Samba lmhosts file. If the line in lmhosts has -no name type attached to the NetBIOS name (see the lmhosts(5) for details) then -any name type matches for lookup. -.TP 0.2i -\(bu -host : Do a standard host -name to IP address resolution, using the system \fI/etc/hosts -\fR, NIS, or DNS lookups. This method of name resolution -is operating system depended for instance on IRIX or Solaris this -may be controlled by the \fI/etc/nsswitch.conf\fR -file. Note that this method is only used if the NetBIOS name -type being queried is the 0x20 (server) name type, otherwise -it is ignored. -.TP 0.2i -\(bu -wins : Query a name with -the IP address listed in the \fI wins server\fR parameter. If no WINS server has -been specified this method will be ignored. -.TP 0.2i -\(bu -bcast : Do a broadcast on -each of the known local interfaces listed in the \fIinterfaces\fR -parameter. This is the least reliable of the name resolution -methods as it depends on the target host being on a locally -connected subnet. -.RE +sync always (S) +This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns\&. If this is \fBno\fR then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous)\&. If this is \fByes\fR then every write will be followed by a \fBfsync() \fR call to ensure the data is written to disk\&. Note that the \fIstrict sync\fR parameter must be set to \fByes\fR in order for this parameter to have any affect\&. -Default: \fBname resolve order = lmhosts host wins bcast -\fR -Example: \fBname resolve order = lmhosts bcast host -\fR +See also the \fIstrict sync\fR parameter\&. -This will cause the local lmhosts file to be examined -first, followed by a broadcast attempt, followed by a normal -system hostname lookup. -.TP -\fB>netbios aliases (G)\fR -This is a list of NetBIOS names that nmbd(8) will advertise as additional -names by which the Samba server is known. This allows one machine -to appear in browse lists under multiple names. If a machine is -acting as a browse server or logon server none -of these names will be advertised as either browse server or logon -servers, only the primary name of the machine will be advertised -with these capabilities. -See also \fInetbios -name\fR. +Default: \fBsync always = no\fR -Default: \fBempty string (no additional names)\fR -Example: \fBnetbios aliases = TEST TEST1 TEST2\fR .TP -\fB>netbios name (G)\fR -This sets the NetBIOS name by which a Samba -server is known. By default it is the same as the first component -of the host's DNS name. If a machine is a browse server or -logon server this name (or the first component -of the hosts DNS name) will be the name that these services are -advertised under. +syslog only (G) +If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files\&. -See also \fInetbios -aliases\fR. -Default: \fBmachine DNS name\fR +Default: \fBsyslog only = no\fR -Example: \fBnetbios name = MYNAME\fR -.TP -\fB>netbios scope (G)\fR -This sets the NetBIOS scope that Samba will -operate under. This should not be set unless every machine -on your LAN also sets this value. -.TP -\fB>nis homedir (G)\fR -Get the home share server from a NIS map. For -UNIX systems that use an automounter, the user's home directory -will often be mounted on a workstation on demand from a remote -server. - -When the Samba logon server is not the actual home directory -server, but is mounting the home directories via NFS then two -network hops would be required to access the users home directory -if the logon server told the client to use itself as the SMB server -for home directories (one over SMB and one over NFS). This can -be very slow. - -This option allows Samba to return the home share as -being on a different server to the logon server and as -long as a Samba daemon is running on the home directory server, -it will be mounted on the Samba client directly from the directory -server. When Samba is returning the home share to the client, it -will consult the NIS map specified in \fIhomedir map\fR and return the server -listed there. - -Note that for this option to work there must be a working -NIS system and the Samba server with this option must also -be a logon server. -Default: \fBnis homedir = no\fR .TP -\fB>non unix account range (G)\fR -The non unix account range parameter specifies -the range of 'user ids' that are allocated by the various 'non unix -account' passdb backends. These backends allow -the storage of passwords for users who don't exist in /etc/passwd. -This is most often used for machine account creation. -This range of ids should have no existing local or NIS users within -it as strange conflicts can occur otherwise. -.sp -.RS -.B "Note:" -These userids never appear on the system and Samba will never -\&'become' these users. They are used only to ensure that the algorithmic -RID mapping does not conflict with normal users. -.RE +syslog (G) +This parameter maps how Samba debug messages are logged onto the system syslog logging levels\&. Samba debug level zero maps onto syslog \fBLOG_ERR\fR, debug level one maps onto \fBLOG_WARNING\fR, debug level two maps onto \fBLOG_NOTICE\fR, debug level three maps onto LOG_INFO\&. All higher levels are mapped to \fB LOG_DEBUG\fR\&. -Default: \fBnon unix account range = -\fR -Example: \fBnon unix account range = 10000-20000\fR -.TP -\fB>nt acl support (S)\fR -This boolean parameter controls whether -smbd(8) will attempt to map -UNIX permissions into Windows NT access control lists. -This parameter was formally a global parameter in releases -prior to 2.2.2. +This parameter sets the threshold for sending messages to syslog\&. Only messages with debug level less than this value will be sent to syslog\&. -Default: \fBnt acl support = yes\fR -.TP -\fB>nt pipe support (G)\fR -This boolean parameter controls whether -\fBsmbd\fR(8) will allow Windows NT -clients to connect to the NT SMB specific IPC$ -pipes. This is a developer debugging option and can be left -alone. -Default: \fBnt pipe support = yes\fR -.TP -\fB>nt status support (G)\fR -This boolean parameter controls whether smbd(8) will negotiate NT specific status -support with Windows NT/2k/XP clients. This is a developer -debugging option and should be left alone. -If this option is set to no then Samba offers -exactly the same DOS error codes that versions prior to Samba 2.2.3 -reported. +Default: \fBsyslog = 1\fR -You should not need to ever disable this parameter. -Default: \fBnt status support = yes\fR .TP -\fB>null passwords (G)\fR -Allow or disallow client access to accounts -that have null passwords. +template homedir (G) +When filling out the user information for a Windows NT user, the \fBwinbindd\fR(8) daemon uses this parameter to fill in the home directory for that user\&. If the string \fI%D\fR is present it is substituted with the user's Windows NT domain name\&. If the string \fI%U\fR is present it is substituted with the user's Windows NT user name\&. -See also \fBsmbpasswd\fR(5). -Default: \fBnull passwords = no\fR -.TP -\fB>obey pam restrictions (G)\fR -When Samba 2.2 is configured to enable PAM support -(i.e. --with-pam), this parameter will control whether or not Samba -should obey PAM's account and session management directives. The -default behavior is to use PAM for clear text authentication only -and to ignore any account or session management. Note that Samba -always ignores PAM for authentication in the case of \fIencrypt passwords = yes\fR -\&. The reason is that PAM modules cannot support the challenge/response -authentication mechanism needed in the presence of SMB password encryption. +Default: \fBtemplate homedir = /home/%D/%U\fR -Default: \fBobey pam restrictions = no\fR -.TP -\fB>only user (S)\fR -This is a boolean option that controls whether -connections with usernames not in the \fIuser\fR -list will be allowed. By default this option is disabled so that a -client can supply a username to be used by the server. Enabling -this parameter will force the server to only use the login -names from the \fIuser\fR list and is only really -useful in share level -security. - -Note that this also means Samba won't try to deduce -usernames from the service name. This can be annoying for -the [homes] section. To get around this you could use \fBuser = -%S\fR which means your \fIuser\fR list -will be just the service name, which for home directories is the -name of the user. - -See also the \fIuser\fR -parameter. -Default: \fBonly user = no\fR .TP -\fB>only guest (S)\fR -A synonym for \fI guest only\fR. -.TP -\fB>oplock break wait time (G)\fR -This is a tuning parameter added due to bugs in -both Windows 9x and WinNT. If Samba responds to a client too -quickly when that client issues an SMB that can cause an oplock -break request, then the network client can fail and not respond -to the break request. This tuning parameter (which is set in milliseconds) -is the amount of time Samba will wait before sending an oplock break -request to such (broken) clients. +template shell (G) +When filling out the user information for a Windows NT user, the \fBwinbindd\fR(8) daemon uses this parameter to fill in the login shell for that user\&. + + +Default: \fBtemplate shell = /bin/false\fR -\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ -AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR. -Default: \fBoplock break wait time = 0\fR .TP -\fB>oplock contention limit (S)\fR -This is a \fBvery\fR advanced -smbd(8) tuning option to -improve the efficiency of the granting of oplocks under multiple -client contention for the same file. +time offset (G) +This parameter is a setting in minutes to add to the normal GMT to local time conversion\&. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling\&. -In brief it specifies a number, which causes \fBsmbd\fR(8)not to grant an oplock even when requested -if the approximate number of clients contending for an oplock on the same file goes over this -limit. This causes \fBsmbd\fR to behave in a similar -way to Windows NT. -\fBDO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ -AND UNDERSTOOD THE SAMBA OPLOCK CODE\fR. +Default: \fBtime offset = 0\fR -Default: \fBoplock contention limit = 2\fR -.TP -\fB>oplocks (S)\fR -This boolean option tells \fBsmbd\fR whether to -issue oplocks (opportunistic locks) to file open requests on this -share. The oplock code can dramatically (approx. 30% or more) improve -the speed of access to files on Samba servers. It allows the clients -to aggressively cache files locally and you may want to disable this -option for unreliable network environments (it is turned on by -default in Windows NT Servers). For more information see the file -\fISpeed.txt\fR in the Samba \fIdocs/\fR -directory. - -Oplocks may be selectively turned off on certain files with a -share. See the \fI veto oplock files\fR parameter. On some systems -oplocks are recognized by the underlying operating system. This -allows data synchronization between all access to oplocked files, -whether it be via Samba or NFS or a local UNIX process. See the -\fIkernel oplocks\fR parameter for details. - -See also the \fIkernel -oplocks\fR and \fI level2 oplocks\fR parameters. -Default: \fBoplocks = yes\fR -.TP -\fB>ntlm auth (G)\fR -This parameter determines -whether or not \fBsmbd\fR(8) will -attempt to authenticate users using the NTLM password hash. -If disabled, only the lanman password hashes will be used. +Example: \fBtime offset = 60\fR -Please note that at least this option or \fBlanman auth\fR should -be enabled in order to be able to log in. -Default : \fBntlm auth = yes\fR .TP -\fB>os level (G)\fR -This integer value controls what level Samba -advertises itself as for browse elections. The value of this -parameter determines whether \fBnmbd\fR(8) -has a chance of becoming a local master browser for the \fI WORKGROUP\fR in the local broadcast area. +time server (G) +This parameter determines if \fBnmbd\fR(8) advertises itself as a time server to Windows clients\&. -\fBNote :\fRBy default, Samba will win -a local master browsing election over all Microsoft operating -systems except a Windows NT 4.0/2000 Domain Controller. This -means that a misconfigured Samba host can effectively isolate -a subnet for browsing purposes. See \fIBROWSING.txt -\fR in the Samba \fIdocs/\fR directory -for details. -Default: \fBos level = 20\fR +Default: \fBtime server = no\fR -Example: \fBos level = 65 \fR -.TP -\fB>os2 driver map (G)\fR -The parameter is used to define the absolute -path to a file containing a mapping of Windows NT printer driver -names to OS/2 printer driver names. The format is: - - = . - -For example, a valid entry using the HP LaserJet 5 -printer driver would appear as \fBHP LaserJet 5L = LASERJET.HP -LaserJet 5L\fR. - -The need for the file is due to the printer driver namespace -problem described in the Samba -Printing HOWTO For more details on OS/2 clients, please -refer to the OS2-Client-HOWTO containing in the Samba documentation. - -Default: \fBos2 driver map = -\fR -.TP -\fB>pam password change (G)\fR -With the addition of better PAM support in Samba 2.2, -this parameter, it is possible to use PAM's password change control -flag for Samba. If enabled, then PAM will be used for password -changes when requested by an SMB client instead of the program listed in -\fIpasswd program\fR. -It should be possible to enable this without changing your -\fIpasswd chat\fR -parameter for most setups. -Default: \fBpam password change = no\fR .TP -\fB>panic action (G)\fR -This is a Samba developer option that allows a -system command to be called when either \fBsmbd\fR(8) or \fBsmbd\fR(8) crashes. This is usually used to -draw attention to the fact that a problem occurred. +timestamp logs (G) +Synonym for \fI debug timestamp\fR\&. -Default: \fBpanic action = \fR -Example: \fBpanic action = "/bin/sleep 90000"\fR .TP -\fB>paranoid server security (G)\fR -Some version of NT 4.x allow non-guest -users with a bad passowrd. When this option is enabled, samba will not -use a broken NT 4.x server as password server, but instead complain -to the logs and exit. +total print jobs (G) +This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time\&. If a print job is submitted by a client which will exceed this number, then \fBsmbd\fR(8) will return an error indicating that no space is available on the server\&. The default value of 0 means that no such limit exists\&. This parameter can be used to prevent a server from exceeding its capacity and is designed as a printing throttle\&. See also \fImax print jobs\fR\&. -Disabling this option prevents Samba from making -this check, which involves deliberatly attempting a -bad logon to the remote server. -Default: \fBparanoid server security = yes\fR -.TP -\fB>passdb backend (G)\fR -This option allows the administrator to chose which backends to retrieve and store passwords with. This allows (for example) both -smbpasswd and tdbsam to be used without a recompile. -Multiple backends can be specified, separated by spaces. The backends will be searched in the order they are specified. New users are always added to the first backend specified. -Experimental backends must still be selected -(eg --with-tdbsam) at configure time. +Default: \fBtotal print jobs = 0\fR -This parameter is in two parts, the backend's name, and a 'location' -string that has meaning only to that particular backed. These are separated -by a : character. -Available backends can include: -.RS -.TP 0.2i -\(bu -\fBsmbpasswd\fR - The default smbpasswd -backend. Takes a path to the smbpasswd file as an optional argument. -.TP 0.2i -\(bu -\fBsmbpasswd_nua\fR - The smbpasswd -backend, but with support for 'not unix accounts'. -Takes a path to the smbpasswd file as an optional argument. +Example: \fBtotal print jobs = 5000\fR -See also \fInon unix account range\fR -.TP 0.2i -\(bu -\fBtdbsam\fR - The TDB based password storage -backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb -in the \fIprivate dir\fR directory. -.TP 0.2i -\(bu -\fBtdbsam_nua\fR - The TDB based password storage -backend, with non unix account support. Takes a path to the TDB as an optional argument (defaults to passdb.tdb -in the \fIprivate dir\fR directory. -See also \fInon unix account range\fR -.TP 0.2i -\(bu -\fBldapsam\fR - The LDAP based passdb -backend. Takes an LDAP URL as an optional argument (defaults to -\fBldap://localhost\fR) -.TP 0.2i -\(bu -\fBldapsam_nua\fR - The LDAP based passdb -backend, with non unix account support. Takes an LDAP URL as an optional argument (defaults to -\fBldap://localhost\fR) +.TP +unicode (G) +Specifies whether Samba should try to use unicode on the wire by default\&. Note: This does NOT mean that samba will assume that the unix machine uses unicode! -Note: In this module, any account without a matching POSIX account is regarded -as 'non unix'. -See also \fInon unix account -range\fR +Default: \fBunicode = yes\fR -LDAP connections should be secured where -possible. This may be done using either -Start-TLS (see \fIldap ssl\fR) or by -specifying \fIldaps://\fR in -the URL argument. -.TP 0.2i -\(bu -\fBnisplussam\fR - The NIS+ based passdb backend. Takes name NIS domain as an optional argument. Only works with sun NIS+ servers. -.TP 0.2i -\(bu -\fBplugin\fR - Allows Samba to load an -arbitary passdb backend from the .so specified as a compulsary argument. -Any characters after the (optional) second : are passed to the plugin -for its own processing -.TP 0.2i -\(bu -\fBunixsam\fR - Allows samba to map all (other) available unix users +.TP +unix charset (G) +Specifies the charset the unix machine Samba runs on uses\&. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use\&. -This backend uses the standard unix database for retrieving users. Users included -in this pdb are NOT listed in samba user listings and users included in this pdb won't be -able to login. The use of this backend is to always be able to display the owner of a file -on the samba server - even when the user doesn't have a 'real' samba account in one of the -other passdb backends. -This backend should always be the last backend listed, since it contains all users in -the unix passdb and might 'override' mappings if specified earlier. It's meant to only return -accounts for users that aren't covered by the previous backends. -.RE +Default: \fBunix charset = UTF8\fR -Default: \fBpassdb backend = smbpasswd unixsam\fR -Example: \fBpassdb backend = tdbsam:/etc/samba/private/passdb.tdb smbpasswd:/etc/samba/smbpasswd unixsam\fR +Example: \fBunix charset = ASCII\fR -Example: \fBpassdb backend = ldapsam_nua:ldaps://ldap.example.com unixsam\fR -Example: \fBpassdb backend = plugin:/usr/local/samba/lib/my_passdb.so:my_plugin_args tdbsam:/etc/samba/private/passdb.tdb\fR .TP -\fB>passwd chat (G)\fR -This string controls the \fB"chat"\fR -conversation that takes places between \fBsmbd\fR(8) and the local password changing -program to change the user's password. The string describes a -sequence of response-receive pairs that \fBsmbd\fR(8) uses to determine what to send to the -\fIpasswd program\fR -and what to expect back. If the expected output is not -received then the password is not changed. - -This chat sequence is often quite site specific, depending -on what local methods are used for password control (such as NIS -etc). - -Note that this parameter only is only used if the \fIunix -password sync\fR parameter is set to yes. This -sequence is then called \fBAS ROOT\fR when the SMB password -in the smbpasswd file is being changed, without access to the old -password cleartext. This means that root must be able to reset the user's password -without knowing the text of the previous password. In the presence of NIS/YP, -this means that the passwd program must be -executed on the NIS master. - -The string can contain the macro \fI%n\fR which is substituted -for the new password. The chat sequence can also contain the standard -macros \\\\n, \\\\r, \\\\t and \\\\s to give line-feed, -carriage-return, tab and space. The chat sequence string can also contain -a '*' which matches any sequence of characters. -Double quotes can be used to collect strings with spaces -in them into a single string. - -If the send string in any part of the chat sequence -is a full stop ".", then no string is sent. Similarly, -if the expect string is a full stop then no string is expected. - -If the \fIpam -password change\fR parameter is set to yes, the chat pairs -may be matched in any order, and success is determined by the PAM result, -not any particular output. The \\n macro is ignored for PAM conversions. - -See also \fIunix password -sync\fR, \fI passwd program\fR , \fIpasswd chat debug\fR and \fIpam password change\fR. - -Default: \fBpasswd chat = *new*password* %n\\\\n -*new*password* %n\\\\n *changed*\fR - -Example: \fBpasswd chat = "*Enter OLD password*" %o\\\\n -"*Enter NEW password*" %n\\\\n "*Reenter NEW password*" %n\\\\n "*Password -changed*"\fR -.TP -\fB>passwd chat debug (G)\fR -This boolean specifies if the passwd chat script -parameter is run in \fBdebug\fR mode. In this mode the -strings passed to and received from the passwd chat are printed -in the \fBsmbd\fR(8) log with a -\fIdebug level\fR -of 100. This is a dangerous option as it will allow plaintext passwords -to be seen in the \fBsmbd\fR log. It is available to help -Samba admins debug their \fIpasswd chat\fR scripts -when calling the \fIpasswd program\fR and should -be turned off after this has been done. This option has no effect if the -\fIpam password change\fR -paramter is set. This parameter is off by default. +unix extensions (G) +This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP\&. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc\&.\&.\&. These extensions require a similarly enabled client, and are of no current use to Windows clients\&. -See also \fIpasswd chat\fR -, \fIpam password change\fR -, \fIpasswd program\fR -\&. -Default: \fBpasswd chat debug = no\fR -.TP -\fB>passwd program (G)\fR -The name of a program that can be used to set -UNIX user passwords. Any occurrences of \fI%u\fR -will be replaced with the user name. The user name is checked for -existence before calling the password changing program. - -Also note that many passwd programs insist in \fBreasonable -\fR passwords, such as a minimum length, or the inclusion -of mixed case chars and digits. This can pose a problem as some clients -(such as Windows for Workgroups) uppercase the password before sending -it. - -\fBNote\fR that if the \fIunix -password sync\fR parameter is set to yes -then this program is called \fBAS ROOT\fR -before the SMB password in the smbpasswd(5) - file is changed. If this UNIX password change fails, then -\fBsmbd\fR will fail to change the SMB password also -(this is by design). - -If the \fIunix password sync\fR parameter -is set this parameter \fBMUST USE ABSOLUTE PATHS\fR -for \fBALL\fR programs called, and must be examined -for security implications. Note that by default \fIunix -password sync\fR is set to no. - -See also \fIunix -password sync\fR. +Default: \fBunix extensions = no\fR -Default: \fBpasswd program = /bin/passwd\fR -Example: \fBpasswd program = /sbin/npasswd %u\fR .TP -\fB>password level (G)\fR -Some client/server combinations have difficulty -with mixed-case passwords. One offending client is Windows for -Workgroups, which for some reason forces passwords to upper -case when using the LANMAN1 protocol, but leaves them alone when -using COREPLUS! Another problem child is the Windows 95/98 -family of operating systems. These clients upper case clear -text passwords even when NT LM 0.12 selected by the protocol -negotiation request/response. +unix password sync (G) +This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed\&. If this is set to \fByes\fR the program specified in the \fIpasswd program\fRparameter is called \fBAS ROOT\fR - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new)\&. -This parameter defines the maximum number of characters -that may be upper case in passwords. -For example, say the password given was "FRED". If \fI password level\fR is set to 1, the following combinations -would be tried if "FRED" failed: - -"Fred", "fred", "fRed", "frEd","freD" +See also \fIpasswd program\fR, \fI passwd chat\fR\&. -If \fIpassword level\fR was set to 2, -the following combinations would also be tried: -"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", .. +Default: \fBunix password sync = no\fR -And so on. -The higher value this parameter is set to the more likely -it is that a mixed case password will be matched against a single -case password. However, you should be aware that use of this -parameter reduces security and increases the time taken to -process a new connection. +.TP +update encrypted (G) +This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on\&. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the wire, and are checked against a UNIX account database) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re-enter their passwords via smbpasswd at the time the change is made\&. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period\&. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to \fBno\fR\&. -A value of zero will cause only two attempts to be -made - the password as is and the password in all-lower case. -Default: \fBpassword level = 0\fR +In order for this parameter to work correctly the \fIencrypt passwords\fR parameter must be set to \fBno\fR when this parameter is set to \fByes\fR\&. -Example: \fBpassword level = 4\fR -.TP -\fB>password server (G)\fR -By specifying the name of another SMB server (such -as a WinNT box) with this option, and using \fBsecurity = domain -\fR or \fBsecurity = server\fR you can get Samba -to do all its username/password validation via a remote server. - -This option sets the name of the password server to use. -It must be a NetBIOS name, so if the machine's NetBIOS name is -different from its Internet name then you may have to add its NetBIOS -name to the lmhosts file which is stored in the same directory -as the \fIsmb.conf\fR file. - -The name of the password server is looked up using the -parameter \fIname -resolve order\fR and so may resolved -by any method and order described in that parameter. - -The password server must be a machine capable of using -the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in -user level security mode. -.sp -.RS -.B "Note:" -Using a password server -means your UNIX box (running Samba) is only as secure as your -password server. \fBDO NOT CHOOSE A PASSWORD SERVER THAT -YOU DON'T COMPLETELY TRUST\fR. -.RE -Never point a Samba server at itself for password -serving. This will cause a loop and could lock up your Samba -server! - -The name of the password server takes the standard -substitutions, but probably the only useful one is \fI%m -\fR, which means the Samba server will use the incoming -client as the password server. If you use this then you better -trust your clients, and you had better restrict them with hosts allow! - -If the \fIsecurity\fR parameter is set to -domain, then the list of machines in this -option must be a list of Primary or Backup Domain controllers for the -Domain or the character '*', as the Samba server is effectively -in that domain, and will use cryptographically authenticated RPC calls -to authenticate the user logging on. The advantage of using \fB security = domain\fR is that if you list several hosts in the -\fIpassword server\fR option then \fBsmbd -\fR will try each in turn till it finds one that responds. This -is useful in case your primary server goes down. - -If the \fIpassword server\fR option is set -to the character '*', then Samba will attempt to auto-locate the -Primary or Backup Domain controllers to authenticate against by -doing a query for the name WORKGROUP<1C> -and then contacting each server returned in the list of IP -addresses from the name resolution source. - -If the list of servers contains both names and the '*' -character, the list is treated as a list of preferred -domain controllers, but an auto lookup of all remaining DC's -will be added to the list as well. Samba will not attempt to optimize -this list by locating the closest DC. - -If the \fIsecurity\fR parameter is -set to server, then there are different -restrictions that \fBsecurity = domain\fR doesn't -suffer from: -.RS -.TP 0.2i -\(bu -You may list several password servers in -the \fIpassword server\fR parameter, however if an -\fBsmbd\fR makes a connection to a password server, -and then the password server fails, no more users will be able -to be authenticated from this \fBsmbd\fR. This is a -restriction of the SMB/CIFS protocol when in \fBsecurity = server -\fR mode and cannot be fixed in Samba. -.TP 0.2i -\(bu -If you are using a Windows NT server as your -password server then you will have to ensure that your users -are able to login from the Samba server, as when in \fB security = server\fR mode the network logon will appear to -come from there rather than from the users workstation. -.RE +Note that even when this parameter is set a user authenticating to \fBsmbd\fR must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords\&. -See also the \fIsecurity -\fR parameter. -Default: \fBpassword server = \fR +Default: \fBupdate encrypted = no\fR -Example: \fBpassword server = NT-PDC, NT-BDC1, NT-BDC2, * -\fR -Example: \fBpassword server = *\fR .TP -\fB>path (S)\fR -This parameter specifies a directory to which -the user of the service is to be given access. In the case of -printable services, this is where print data will spool prior to -being submitted to the host for printing. +use client driver (S) +This parameter applies only to Windows NT/2000 clients\&. It has no affect on Windows 95/98/ME clients\&. When serving a printer to Windows NT/2000 clients without first installing a valid printer driver on the Samba host, the client will be required to install a local printer driver\&. From this point on, the client will treat the print as a local printer and not a network printer connection\&. This is much the same behavior that will occur when \fBdisable spoolss = yes\fR\&. -For a printable service offering guest access, the service -should be readonly and the path should be world-writeable and -have the sticky bit set. This is not mandatory of course, but -you probably won't get the results you expect if you do -otherwise. -Any occurrences of \fI%u\fR in the path -will be replaced with the UNIX username that the client is using -on this connection. Any occurrences of \fI%m\fR -will be replaced by the NetBIOS name of the machine they are -connecting from. These replacements are very useful for setting -up pseudo home directories for users. +The differentiating factor is that under normal circumstances, the NT/2000 client will attempt to open the network printer using MS-RPC\&. The problem is that because the client considers the printer to be local, it will attempt to issue the OpenPrinterEx() call requesting access rights associated with the logged on user\&. If the user possesses local administator rights but not root privilegde on the Samba host (often the case), the OpenPrinterEx() call will fail\&. The result is that the client will now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed)\&. -Note that this path will be based on \fIroot dir\fR if one was specified. -Default: \fBnone\fR +If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead\&. Thus allowing the OpenPrinterEx() call to succeed\&. \fBThis parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server\&.\fR -Example: \fBpath = /home/fred\fR -.TP -\fB>pid directory (G)\fR -This option specifies the directory where pid -files will be placed. -Default: \fBpid directory = ${prefix}/var/locks\fR +See also \fIdisable spoolss\fR -Example: \fBpid directory = /var/run/\fR -.TP -\fB>posix locking (S)\fR -The \fBsmbd\fR(8) -daemon maintains an database of file locks obtained by SMB clients. -The default behavior is to map this internal database to POSIX -locks. This means that file locks obtained by SMB clients are -consistent with those seen by POSIX compliant applications accessing -the files via a non-SMB method (e.g. NFS or local file access). -You should never need to disable this parameter. -Default: \fBposix locking = yes\fR -.TP -\fB>postexec (S)\fR -This option specifies a command to be run -whenever the service is disconnected. It takes the usual -substitutions. The command may be run as the root on some -systems. +Default: \fBuse client driver = no\fR -An interesting example may be to unmount server -resources: -\fBpostexec = /etc/umount /cdrom\fR +.TP +use mmap (G) +This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system\&. Samba requires a coherent mmap/read-write system memory cache\&. Currently only HPUX does not have such a coherent cache, and so this parameter is set to \fBno\fR by default on HPUX\&. On all other systems this parameter should be left alone\&. This parameter is provided to help the Samba developers track down problems with the tdb internal code\&. -See also \fIpreexec\fR -\&. -Default: \fBnone (no command executed)\fR +Default: \fBuse mmap = yes\fR + -Example: \fBpostexec = echo \\"%u disconnected from %S -from %m (%I)\\" >> /tmp/log\fR .TP -\fB>preexec (S)\fR -This option specifies a command to be run whenever -the service is connected to. It takes the usual substitutions. +username level (G) +This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username\&. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine\&. -An interesting example is to send the users a welcome -message every time they log in. Maybe a message of the day? Here -is an example: -\fBpreexec = csh -c 'echo \\"Welcome to %S!\\" | -/usr/local/samba/bin/smbclient -M %m -I %I' & \fR +If this parameter is set to non-zero the behavior changes\&. This parameter is a number that specifies the number of uppercase combinations to try while trying to determine the UNIX user name\&. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be\&. Use this parameter when you have strange usernames on your UNIX machine, such as \fBAstrangeUser \fR\&. -Of course, this could get annoying after a while :-) -See also \fIpreexec close -\fR and \fIpostexec -\fR. +Default: \fBusername level = 0\fR + -Default: \fBnone (no command executed)\fR +Example: \fBusername level = 5\fR -Example: \fBpreexec = echo \\"%u connected to %S from %m -(%I)\\" >> /tmp/log\fR -.TP -\fB>preexec close (S)\fR -This boolean option controls whether a non-zero -return code from \fIpreexec -\fR should close the service being connected to. -Default: \fBpreexec close = no\fR .TP -\fB>preferred master (G)\fR -This boolean parameter controls if nmbd(8) is a preferred master browser -for its workgroup. +username map (G) +This option allows you to specify a file containing a mapping of usernames from the clients to the server\&. This can be used for several purposes\&. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses\&. The other is to map multiple users to a single username so that they can more easily share files\&. -If this is set to yes, on startup, \fBnmbd\fR -will force an election, and it will have a slight advantage in -winning the election. It is recommended that this parameter is -used in conjunction with \fB\fI domain master\fB = yes\fR, so that \fB nmbd\fR can guarantee becoming a domain master. -Use this option with caution, because if there are several -hosts (whether Samba servers, Windows 95 or NT) that are preferred -master browsers on the same subnet, they will each periodically -and continuously attempt to become the local master browser. -This will result in unnecessary broadcast traffic and reduced browsing -capabilities. +The map file is parsed line by line\&. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right\&. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group\&. The special client name '*' is a wildcard and matches any name\&. Each line of the map file may be up to 1023 characters long\&. -See also \fIos level\fR -\&. -Default: \fBpreferred master = auto\fR -.TP -\fB>prefered master (G)\fR -Synonym for \fI preferred master\fR for people who cannot spell :-). -.TP -\fB>preload (G)\fR -This is a list of services that you want to be -automatically added to the browse lists. This is most useful -for homes and printers services that would otherwise not be -visible. +The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs\&. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left\&. Processing then continues with the next line\&. -Note that if you just want all printers in your -printcap file loaded then the \fIload printers\fR option is easier. -Default: \fBno preloaded services\fR +If any line begins with a '#' or a ';' then it is ignored -Example: \fBpreload = fred lp colorlp\fR -.TP -\fB>preload modules (G)\fR -This is a list of paths to modules that should -be loaded into smbd before a client connects. This improves -the speed of smbd when reacting to new connections somewhat. -It is recommended to only use this option on heavy-performance -servers. +If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line\&. Otherwise mapping continues with every line being processed\&. Using '!' is most useful when you have a wildcard mapping line later in the file\&. -Default: \fBpreload modules = \fR -Example: \fBpreload modules = /usr/lib/samba/passdb/mysql.so\fR -.TP -\fB>preserve case (S)\fR -This controls if new filenames are created -with the case that the client passes, or if they are forced to -be the \fIdefault case -\fR. +For example to map from the name \fBadmin\fR or \fBadministrator\fR to the UNIX name \fB root\fR you would use: -Default: \fBpreserve case = yes\fR -See the section on NAME -MANGLING for a fuller discussion. -.TP -\fB>print command (S)\fR -After a print job has finished spooling to -a service, this command will be used via a \fBsystem()\fR -call to process the spool file. Typically the command specified will -submit the spool file to the host's printing subsystem, but there -is no requirement that this be the case. The server will not remove -the spool file, so whatever command you specify should remove the -spool file when it has been processed, otherwise you will need to -manually remove old spool files. +\fBroot = admin administrator\fR -The print command is simply a text string. It will be used -verbatim after macro substitutions have been made: -s, %p - the path to the spool -file name +Or to map anyone in the UNIX group \fBsystem\fR to the UNIX name \fBsys\fR you would use: -%p - the appropriate printer -name -%J - the job -name as transmitted by the client. +\fBsys = @system\fR -%c - The number of printed pages -of the spooled job (if known). -%z - the size of the spooled -print job (in bytes) +You can have as many mappings as you like in a username map file\&. -The print command \fBMUST\fR contain at least -one occurrence of \fI%s\fR or \fI%f -\fR - the \fI%p\fR is optional. At the time -a job is submitted, if no printer name is supplied the \fI%p -\fR will be silently removed from the printer command. -If specified in the [global] section, the print command given -will be used for any printable service that does not have its own -print command specified. +If your system supports the NIS NETGROUP option then the netgroup database is checked before the \fI/etc/group \fR database for matching groups\&. -If there is neither a specified print command for a -printable service nor a global print command, spool files will -be created but not processed and (most importantly) not removed. -Note that printing may fail on some UNIXes from the -nobody account. If this happens then create -an alternative guest account that can print and set the \fIguest account\fR -in the [global] section. +You can map Windows usernames that have spaces in them by using double quotes around the name\&. For example: -You can form quite complex print commands by realizing -that they are just passed to a shell. For example the following -will log a print job, print the file, then remove it. Note that -\&';' is the usual separator for command in shell scripts. -\fBprint command = echo Printing %s >> -/tmp/print.log; lpr -P %p %s; rm %s\fR +\fBtridge = "Andrew Tridgell"\fR -You may have to vary this command considerably depending -on how you normally print files on your system. The default for -the parameter varies depending on the setting of the \fIprinting\fR parameter. -Default: For \fBprinting = BSD, AIX, QNX, LPRNG -or PLP :\fR +would map the windows username "Andrew Tridgell" to the unix username "tridge"\&. -\fBprint command = lpr -r -P%p %s\fR -For \fBprinting = SYSV or HPUX :\fR +The following example would map mary and fred to the unix user sys, and map the rest to guest\&. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line\&. -\fBprint command = lp -c -d%p %s; rm %s\fR -For \fBprinting = SOFTQ :\fR +.nf -\fBprint command = lp -d%p -s %s; rm %s\fR +!sys = mary fred +guest = * +.fi -For printing = CUPS : If SAMBA is compiled against -libcups, then printcap = cups -uses the CUPS API to -submit jobs, etc. Otherwise it maps to the System V -commands with the -oraw option for printing, i.e. it -uses \fBlp -c -d%p -oraw; rm %s\fR. -With \fBprinting = cups\fR, -and if SAMBA is compiled against libcups, any manually -set print command will be ignored. - -Example: \fBprint command = /usr/local/samba/bin/myprintscript -%p %s\fR -.TP -\fB>print ok (S)\fR -Synonym for \fIprintable\fR. -.TP -\fB>printable (S)\fR -If this parameter is yes, then -clients may open, write to and submit spool files on the directory -specified for the service. - -Note that a printable service will ALWAYS allow writing -to the service path (user privileges permitting) via the spooling -of print data. The \fIread only -\fR parameter controls only non-printing access to -the resource. -Default: \fBprintable = no\fR -.TP -\fB>printcap (G)\fR -Synonym for \fI printcap name\fR. -.TP -\fB>printcap name (G)\fR -This parameter may be used to override the -compiled-in default printcap name used by the server (usually \fI /etc/printcap\fR). See the discussion of the [printers] section above for reasons -why you might want to do this. - -To use the CUPS printing interface set \fBprintcap name = cups -\fR. This should be supplemented by an addtional setting -printing = cups in the [global] -section. \fBprintcap name = cups\fR will use the -"dummy" printcap created by CUPS, as specified in your CUPS -configuration file. - -On System V systems that use \fBlpstat\fR to -list available printers you can use \fBprintcap name = lpstat -\fR to automatically obtain lists of available printers. This -is the default for systems that define SYSV at configure time in -Samba (this includes most System V based systems). If \fI printcap name\fR is set to \fBlpstat\fR on -these systems then Samba will launch \fBlpstat -v\fR and -attempt to parse the output to obtain a printer list. +Note that the remapping is applied to all occurrences of usernames\&. Thus if you connect to \\\\server\\fred and \fB fred\fR is remapped to \fBmary\fR then you will actually be connecting to \\\\server\\mary and will need to supply a password suitable for \fBmary\fR not \fBfred\fR\&. The only exception to this is the username passed to the \fI password server\fR (if you have one)\&. The password server will receive whatever username the client supplies without modification\&. -A minimal printcap file would look something like this: +Also note that no reverse mapping is done\&. The main effect this has is with printing\&. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job\&. -.nf -print1|My Printer 1 -print2|My Printer 2 -print3|My Printer 3 -print4|My Printer 4 -print5|My Printer 5 -.fi -where the '|' separates aliases of a printer. The fact -that the second alias has a space in it gives a hint to Samba -that it's a comment. -.sp -.RS -.B "Note:" -Under AIX the default printcap -name is \fI/etc/qconfig\fR. Samba will assume the -file is in AIX \fIqconfig\fR format if the string -\fIqconfig\fR appears in the printcap filename. -.RE +Default: \fBno username map\fR -Default: \fBprintcap name = /etc/printcap\fR -Example: \fBprintcap name = /etc/myprintcap\fR -.TP -\fB>printer admin (S)\fR -This is a list of users that can do anything to -printers via the remote administration interfaces offered by MS-RPC -(usually using a NT workstation). Note that the root user always -has admin rights. +Example: \fBusername map = /usr/local/samba/lib/users.map\fR -Default: \fBprinter admin = \fR -Example: \fBprinter admin = admin, @staff\fR .TP -\fB>printer name (S)\fR -This parameter specifies the name of the printer -to which print jobs spooled through a printable service will be sent. +username (S) +Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\&. -If specified in the [global] section, the printer -name given will be used for any printable service that does -not have its own printer name specified. -Default: \fBnone (but may be lp -on many systems)\fR +The \fIusername\fR line is needed only when the PC is unable to supply its own username\&. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\&. In both these cases you may also be better using the \\\\server\\share%user syntax instead\&. -Example: \fBprinter name = laserwriter\fR -.TP -\fB>printer (S)\fR -Synonym for \fI printer name\fR. -.TP -\fB>printing (S)\fR -This parameters controls how printer status -information is interpreted on your system. It also affects the -default values for the \fIprint command\fR, -\fIlpq command\fR, \fIlppause command -\fR, \fIlpresume command\fR, and -\fIlprm command\fR if specified in the -[global] section. -Currently nine printing styles are supported. They are -BSD, AIX, -LPRNG, PLP, -SYSV, HPUX, -QNX, SOFTQ, -and CUPS. +The \fIusername\fR line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the \fIusername\fR line in turn\&. This is slow and a bad idea for lots of users in case of duplicate passwords\&. You may get timeouts or security breaches using this parameter unwisely\&. -To see what the defaults are for the other print -commands when using the various options use the testparm(1) program. -This option can be set on a per printer basis +Samba relies on the underlying UNIX security\&. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password\&. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session\&. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do\&. -See also the discussion in the [printers] section. -.TP -\fB>private dir (G)\fR -This parameters defines the directory -smbd will use for storing such files as \fIsmbpasswd\fR -and \fIsecrets.tdb\fR. -Default :\fBprivate dir = ${prefix}/private\fR -.TP -\fB>protocol (G)\fR -Synonym for \fImax protocol\fR. -.TP -\fB>public (S)\fR -Synonym for \fIguest -ok\fR. -.TP -\fB>queuepause command (S)\fR -This parameter specifies the command to be -executed on the server host in order to pause the printer queue. +To restrict a service to a particular set of users you can use the \fIvalid users \fR parameter\&. -This command should be a program or script which takes -a printer name as its only parameter and stops the printer queue, -such that no longer jobs are submitted to the printer. -This command is not supported by Windows for Workgroups, -but can be issued from the Printers window under Windows 95 -and NT. +If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\&. -If a \fI%p\fR is given then the printer name -is put in its place. Otherwise it is placed at the end of the command. -Note that it is good practice to include the absolute -path in the command as the PATH may not be available to the -server. +If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\&. -Default: \fBdepends on the setting of \fIprinting -\fB\fR -Example: \fBqueuepause command = disable %p\fR -.TP -\fB>queueresume command (S)\fR -This parameter specifies the command to be -executed on the server host in order to resume the printer queue. It -is the command to undo the behavior that is caused by the -previous parameter (\fI queuepause command\fR). +If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\&. -This command should be a program or script which takes -a printer name as its only parameter and resumes the printer queue, -such that queued jobs are resubmitted to the printer. -This command is not supported by Windows for Workgroups, -but can be issued from the Printers window under Windows 95 -and NT. +Note that searching though a groups database can take quite some time, and some clients may time out during the search\&. -If a \fI%p\fR is given then the printer name -is put in its place. Otherwise it is placed at the end of the -command. -Note that it is good practice to include the absolute -path in the command as the PATH may not be available to the -server. +See the section NOTE ABOUT USERNAME/PASSWORD VALIDATION for more information on how this parameter determines access to the services\&. -Default: \fBdepends on the setting of \fIprinting\fB\fR -Example: \fBqueuepause command = enable %p -\fR -.TP -\fB>read bmpx (G)\fR -This boolean parameter controls whether smbd(8) will support the "Read -Block Multiplex" SMB. This is now rarely used and defaults to -no. You should never need to set this -parameter. +Default: \fBThe guest account if a guest service, else .\fR -Default: \fBread bmpx = no\fR -.TP -\fB>read list (S)\fR -This is a list of users that are given read-only -access to a service. If the connecting user is in this list then -they will not be given write access, no matter what the \fIread only\fR -option is set to. The list can include group names using the -syntax described in the \fI invalid users\fR parameter. -See also the \fI write list\fR parameter and the \fIinvalid users\fR -parameter. +Examples:\fBusername = fred, mary, jack, jane, @users, @pcgroup\fR -Default: \fBread list = \fR -Example: \fBread list = mary, @students\fR .TP -\fB>read only (S)\fR -An inverted synonym is \fIwriteable\fR. +users (S) +Synonym for \fI username\fR\&. + -If this parameter is yes, then users -of a service may not create or modify files in the service's -directory. +.TP +user (S) +Synonym for \fIusername\fR\&. -Note that a printable service (\fBprintable = yes\fR) -will \fBALWAYS\fR allow writing to the directory -(user privileges permitting), but only via spooling operations. -Default: \fBread only = yes\fR .TP -\fB>read raw (G)\fR -This parameter controls whether or not the server -will support the raw read SMB requests when transferring data -to clients. +use sendfile (S) +If this parameter is \fByes\fR, and Samba was built with the --with-sendfile-support option, and the underlying operating system supports sendfile system call, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\&. This may make more efficient use of the system CPU's and cause Samba to be faster\&. This is off by default as it's effects are unknown as yet\&. -If enabled, raw reads allow reads of 65535 bytes in -one packet. This typically provides a major performance benefit. -However, some clients either negotiate the allowable -block size incorrectly or are incapable of supporting larger block -sizes, and for these clients you may need to disable raw reads. +Default: \fBuse sendfile = no\fR -In general this parameter should be viewed as a system tuning -tool and left severely alone. See also \fIwrite raw\fR. -Default: \fBread raw = yes\fR .TP -\fB>read size (G)\fR -The option \fIread size\fR -affects the overlap of disk reads/writes with network reads/writes. -If the amount of data being transferred in several of the SMB -commands (currently SMBwrite, SMBwriteX and SMBreadbraw) is larger -than this value then the server begins writing the data before it -has received the whole packet from the network, or in the case of -SMBreadbraw, it begins writing to the network before all the data -has been read from disk. - -This overlapping works best when the speeds of disk and -network access are similar, having very little effect when the -speed of one is much greater than the other. - -The default value is 16384, but very little experimentation -has been done yet to determine the optimal value, and it is likely -that the best value will vary greatly between systems anyway. -A value over 65536 is pointless and will cause you to allocate -memory unnecessarily. +use spnego (G) +This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism\&. Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled\&. -Default: \fBread size = 16384\fR -Example: \fBread size = 8192\fR -.TP -\fB>realm (G)\fR -This option specifies the kerberos realm to use. The realm is -used as the ADS equivalent of the NT4\fBdomain\fR. It -is usually set to the DNS name of the kerberos server. +Default: \fBuse spnego = yes\fR -Default: \fBrealm = \fR -Example: \fBrealm = mysambabox.mycompany.com\fR .TP -\fB>remote announce (G)\fR -This option allows you to setup nmbd(8) to periodically announce itself -to arbitrary IP addresses with an arbitrary workgroup name. - -This is useful if you want your Samba server to appear -in a remote workgroup for which the normal browse propagation -rules don't work. The remote workgroup can be anywhere that you -can send IP packets to. +utmp directory (G) +This parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server\&. See also the \fIutmp\fR parameter\&. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually \fI/var/run/utmp\fR on Linux)\&. -For example: -\fBremote announce = 192.168.2.255/SERVERS -192.168.4.255/STAFF\fR +Default: \fBno utmp directory\fR -the above line would cause \fBnmbd\fR to announce itself -to the two given IP addresses using the given workgroup names. -If you leave out the workgroup name then the one given in -the \fIworkgroup\fR -parameter is used instead. -The IP addresses you choose would normally be the broadcast -addresses of the remote networks, but can also be the IP addresses -of known browse masters if your network config is that stable. +Example: \fButmp directory = /var/run/utmp\fR -See the documentation file BROWSING -in the \fIdocs/\fR directory. -Default: \fBremote announce = -\fR .TP -\fB>remote browse sync (G)\fR -This option allows you to setup nmbd(8) to periodically request -synchronization of browse lists with the master browser of a Samba -server that is on a remote segment. This option will allow you to -gain browse lists for multiple workgroups across routed networks. This -is done in a manner that does not work with any non-Samba servers. +utmp (G) +This boolean parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. If set to \fByes\fR then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server\&. Sites may use this to record the user connecting to a Samba share\&. -This is useful if you want your Samba server and all local -clients to appear in a remote workgroup for which the normal browse -propagation rules don't work. The remote workgroup can be anywhere -that you can send IP packets to. -For example: +Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user\&. Enabling this option creates an n^2 algorithm to find this number\&. This may impede performance on large installations\&. -\fBremote browse sync = 192.168.2.255 192.168.4.255 -\fR -the above line would cause \fBnmbd\fR to request -the master browser on the specified subnets or addresses to -synchronize their browse lists with the local server. +See also the \fI utmp directory\fR parameter\&. -The IP addresses you choose would normally be the broadcast -addresses of the remote networks, but can also be the IP addresses -of known browse masters if your network config is that stable. If -a machine IP address is given Samba makes NO attempt to validate -that the remote machine is available, is listening, nor that it -is in fact the browse master on its segment. -Default: \fBremote browse sync = -\fR -.TP -\fB>restrict anonymous (G)\fR -This is a integer parameter, and -mirrors as much as possible the functinality the -RestrictAnonymous -registry key does on NT/Win2k. +Default: \fButmp = no\fR + -Default: \fBrestrict anonymous = 0\fR .TP -\fB>root (G)\fR -Synonym for \fIroot directory"\fR. -.TP -\fB>root dir (G)\fR -Synonym for \fIroot directory"\fR. -.TP -\fB>root directory (G)\fR -The server will \fBchroot()\fR (i.e. -Change its root directory) to this directory on startup. This is -not strictly necessary for secure operation. Even without it the -server will deny access to files not in one of the service entries. -It may also check for, and deny access to, soft links to other -parts of the filesystem, or attempts to use ".." in file names -to access other directories (depending on the setting of the \fIwide links\fR -parameter). - -Adding a \fIroot directory\fR entry other -than "/" adds an extra level of security, but at a price. It -absolutely ensures that no access is given to files not in the -sub-tree specified in the \fIroot directory\fR -option, \fBincluding\fR some files needed for -complete operation of the server. To maintain full operability -of the server you will need to mirror some system files -into the \fIroot directory\fR tree. In particular -you will need to mirror \fI/etc/passwd\fR (or a -subset of it), and any binaries or configuration files needed for -printing (if required). The set of files that must be mirrored is -operating system dependent. +valid users (S) +This is a list of users that should be allowed to login to this service\&. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the \fIinvalid users\fR parameter\&. -Default: \fBroot directory = /\fR -Example: \fBroot directory = /homes/smb\fR -.TP -\fB>root postexec (S)\fR -This is the same as the \fIpostexec\fR -parameter except that the command is run as root. This -is useful for unmounting filesystems -(such as CDROMs) after a connection is closed. +If this is empty (the default) then any user can login\&. If a username is in both this list and the \fIinvalid users\fR list then access is denied for that user\&. -See also \fI postexec\fR. -Default: \fBroot postexec = -\fR -.TP -\fB>root preexec (S)\fR -This is the same as the \fIpreexec\fR -parameter except that the command is run as root. This -is useful for mounting filesystems (such as CDROMs) when a -connection is opened. +The current servicename is substituted for \fI%S \fR\&. This is useful in the [homes] section\&. -See also \fI preexec\fR and \fIpreexec close\fR. -Default: \fBroot preexec = -\fR -.TP -\fB>root preexec close (S)\fR -This is the same as the \fIpreexec close -\fR parameter except that the command is run as root. +See also \fIinvalid users \fR -See also \fI preexec\fR and \fIpreexec close\fR. -Default: \fBroot preexec close = no\fR -.TP -\fB>security (G)\fR -This option affects how clients respond to -Samba and is one of the most important settings in the \fI smb.conf\fR file. - -The option sets the "security mode bit" in replies to -protocol negotiations with \fBsmbd\fR(8) to turn share level security on or off. Clients decide -based on this bit whether (and how) to transfer user and password -information to the server. - -The default is \fBsecurity = user\fR, as this is -the most common setting needed when talking to Windows 98 and -Windows NT. - -The alternatives are \fBsecurity = share\fR, -\fBsecurity = server\fR or \fBsecurity = domain -\fR. - -In versions of Samba prior to 2.0.0, the default was -\fBsecurity = share\fR mainly because that was -the only option at one stage. - -There is a bug in WfWg that has relevance to this -setting. When in user or server level security a WfWg client -will totally ignore the password you type in the "connect -drive" dialog box. This makes it very difficult (if not impossible) -to connect to a Samba service as anyone except the user that -you are logged into WfWg as. - -If your PCs use usernames that are the same as their -usernames on the UNIX machine then you will want to use -\fBsecurity = user\fR. If you mostly use usernames -that don't exist on the UNIX box then use \fBsecurity = -share\fR. - -You should also use \fBsecurity = share\fR if you -want to mainly setup shares without a password (guest shares). This -is commonly used for a shared printer server. It is more difficult -to setup guest shares with \fBsecurity = user\fR, see -the \fImap to guest\fR -parameter for details. - -It is possible to use \fBsmbd\fR in a \fB hybrid mode\fR where it is offers both user and share -level security under different \fINetBIOS aliases\fR. - -The different settings will now be explained. - ->\fBSECURITY = SHARE -\fR - -When clients connect to a share level security server they -need not log onto the server with a valid username and password before -attempting to connect to a shared resource (although modern clients -such as Windows 95/98 and Windows NT will send a logon request with -a username but no password when talking to a \fBsecurity = share -\fR server). Instead, the clients send authentication information -(passwords) on a per-share basis, at the time they attempt to connect -to that share. - -Note that \fBsmbd\fR \fBALWAYS\fR -uses a valid UNIX user to act on behalf of the client, even in -\fBsecurity = share\fR level security. - -As clients are not required to send a username to the server -in share level security, \fBsmbd\fR uses several -techniques to determine the correct UNIX user to use on behalf -of the client. - -A list of possible UNIX usernames to match with the given -client password is constructed using the following methods : -.RS -.TP 0.2i -\(bu -If the \fIguest -only\fR parameter is set, then all the other -stages are missed and only the \fIguest account\fR username is checked. -.TP 0.2i -\(bu -Is a username is sent with the share connection -request, then this username (after mapping - see \fIusername map\fR), -is added as a potential username. -.TP 0.2i -\(bu -If the client did a previous \fBlogon -\fR request (the SessionSetup SMB call) then the -username sent in this SMB will be added as a potential username. -.TP 0.2i -\(bu -The name of the service the client requested is -added as a potential username. -.TP 0.2i -\(bu -The NetBIOS name of the client is added to -the list as a potential username. -.TP 0.2i -\(bu -Any users on the \fI user\fR list are added as potential usernames. -.RE +Default: \fBNo valid users list (anyone can login) \fR -If the \fIguest only\fR parameter is -not set, then this list is then tried with the supplied password. -The first user for whom the password matches will be used as the -UNIX user. - -If the \fIguest only\fR parameter is -set, or no username can be determined then if the share is marked -as available to the \fIguest account\fR, then this -guest user will be used, otherwise access is denied. - -Note that it can be \fBvery\fR confusing -in share-level security as to which UNIX username will eventually -be used in granting access. - -See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. - ->\fBSECURITY = USER -\fR - -This is the default security setting in Samba 3.0. -With user-level security a client must first "log-on" with a -valid username and password (which can be mapped using the \fIusername map\fR -parameter). Encrypted passwords (see the \fIencrypted passwords\fR parameter) can also -be used in this security mode. Parameters such as \fIuser\fR and \fIguest only\fR if set are then applied and -may change the UNIX user to use on this connection, but only after -the user has been successfully authenticated. - -\fBNote\fR that the name of the resource being -requested is \fBnot\fR sent to the server until after -the server has successfully authenticated the client. This is why -guest shares don't work in user level security without allowing -the server to automatically map unknown users into the \fIguest account\fR. -See the \fImap to guest\fR -parameter for details on doing this. - -See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. - ->\fBSECURITY = DOMAIN -\fR - -This mode will only work correctly if \fBnet\fR(8) has been used to add this -machine into a Windows NT Domain. It expects the \fIencrypted passwords\fR -parameter to be set to yes. In this -mode Samba will try to validate the username/password by passing -it to a Windows NT Primary or Backup Domain Controller, in exactly -the same way that a Windows NT Server would do. - -\fBNote\fR that a valid UNIX user must still -exist as well as the account on the Domain Controller to allow -Samba to have a valid UNIX account to map file access to. - -\fBNote\fR that from the client's point -of view \fBsecurity = domain\fR is the same as \fBsecurity = user -\fR. It only affects how the server deals with the authentication, -it does not in any way affect what the client sees. - -\fBNote\fR that the name of the resource being -requested is \fBnot\fR sent to the server until after -the server has successfully authenticated the client. This is why -guest shares don't work in user level security without allowing -the server to automatically map unknown users into the \fIguest account\fR. -See the \fImap to guest\fR -parameter for details on doing this. - -See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. - -See also the \fIpassword -server\fR parameter and the \fIencrypted passwords\fR -parameter. - ->\fBSECURITY = SERVER -\fR - -In this mode Samba will try to validate the username/password -by passing it to another SMB server, such as an NT box. If this -fails it will revert to \fBsecurity = -user\fR. It expects the \fIencrypted passwords\fR -parameter to be set to -yes, unless the remote server -does not support them. However note -that if encrypted passwords have been negotiated then Samba cannot -revert back to checking the UNIX password file, it must have a valid -\fIsmbpasswd\fR file to check users against. See the -documentation file in the \fIdocs/\fR directory -\fIENCRYPTION.txt\fR for details on how to set this -up. - -\fBNote\fR this mode of operation -has significant pitfalls, due to the fact that is -activly initiates a man-in-the-middle attack on the -remote SMB server. In particular, this mode of -operation can cause significant resource consuption on -the PDC, as it must maintain an active connection for -the duration of the user's session. Furthermore, if -this connection is lost, there is no way to -reestablish it, and futher authenticaions to the Samba -server may fail. (From a single client, till it -disconnects). - -\fBNote\fR that from the client's point of -view \fBsecurity = server\fR is the same as \fB security = user\fR. It only affects how the server deals -with the authentication, it does not in any way affect what the -client sees. - -\fBNote\fR that the name of the resource being -requested is \fBnot\fR sent to the server until after -the server has successfully authenticated the client. This is why -guest shares don't work in user level security without allowing -the server to automatically map unknown users into the \fIguest account\fR. -See the \fImap to guest\fR -parameter for details on doing this. - -See also the section NOTE ABOUT USERNAME/PASSWORD VALIDATION. - -See also the \fIpassword -server\fR parameter and the \fIencrypted passwords\fR -parameter. -Default: \fBsecurity = USER\fR +Example: \fBvalid users = greg, @pcusers\fR + -Example: \fBsecurity = DOMAIN\fR .TP -\fB>security mask (S)\fR -This parameter controls what UNIX permission -bits can be modified when a Windows NT client is manipulating -the UNIX permission on a file using the native NT security -dialog box. +veto files (S) +This is a list of files and directories that are neither visible nor accessible\&. Each entry in the list must be separated by a '/', which allows spaces to be included in the entry\&. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards\&. -This parameter is applied as a mask (AND'ed with) to -the changed permission bits, thus preventing any bits not in -this mask from being modified. Essentially, zero bits in this -mask may be treated as a set of bits the user is not allowed -to change. -If not set explicitly this parameter is 0777, allowing -a user to modify all the user/group/world permissions on a file. +Each entry must be a unix path, not a DOS path and must \fBnot\fR include the unix directory separator '/'\&. -\fBNote\fR that users who can access the -Samba server through other means can easily bypass this -restriction, so it is primarily useful for standalone -"appliance" systems. Administrators of most normal systems will -probably want to leave it set to 0777. -See also the \fIforce directory security mode\fR, -\fIdirectory -security mask\fR, \fIforce security mode\fR parameters. +Note that the \fIcase sensitive\fR option is applicable in vetoing files\&. -Default: \fBsecurity mask = 0777\fR -Example: \fBsecurity mask = 0770\fR -.TP -\fB>server schannel (G)\fR -This controls whether the server offers or even -demands the use of the netlogon schannel. -\fIserver schannel = no\fR does not -offer the schannel, \fIserver schannel = -auto\fR offers the schannel but does not -enforce it, and \fIserver schannel = -yes\fR denies access if the client is not -able to speak netlogon schannel. This is only the case -for Windows NT4 before SP4. - -Please note that with this set to -\fIno\fR you will have to apply the -WindowsXP requireSignOrSeal-Registry patch found in -the docs/Registry subdirectory. +One feature of the veto files parameter that it is important to be aware of is Samba's behaviour when trying to delete a directory\&. If a directory that is to be deleted contains nothing but veto files this deletion will \fBfail\fR unless you also set the \fIdelete veto files\fR parameter to \fIyes\fR\&. -Default: \fBserver schannel = auto\fR -Example: \fBserver schannel = yes\fR/para> -.TP -\fB>server string (G)\fR -This controls what string will show up in the -printer comment box in print manager and next to the IPC connection -in \fBnet view\fR. It can be any string that you wish -to show to your users. +Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned\&. -It also sets what will appear in browse lists next -to the machine name. -A \fI%v\fR will be replaced with the Samba -version number. +See also \fIhide files \fR and \fI case sensitive\fR\&. -A \fI%h\fR will be replaced with the -hostname. -Default: \fBserver string = Samba %v\fR +Default: \fBNo files or directories are vetoed\&. \fR -Example: \fBserver string = University of GNUs Samba -Server\fR -.TP -\fB>set primary group script (G)\fR -Thanks to the Posix subsystem in NT a -Windows User has a primary group in addition to the -auxiliary groups. This script sets the primary group -in the unix userdatase when an administrator sets the -primary group from the windows user manager or when -fetching a SAM with \fBnet rpc -vampire\fR. \fI%u\fR will be -replaced with the user whose primary group is to be -set. \fI%g\fR will be replaced with -the group to set. -Default: \fBNo default value\fR +Examples: +.nf -Example: \fBset primary group script = /usr/sbin/usermod -g '%g' '%u'\fR -.TP -\fB>set directory (S)\fR -If \fBset directory = no\fR, then -users of the service may not use the setdir command to change -directory. +; Veto any files containing the word Security, +; any ending in \&.tmp, and any directory containing the +; word root\&. +veto files = /*Security*/*\&.tmp/*root*/ + +; Veto the Apple specific files that a NetAtalk server +; creates\&. +veto files = /\&.AppleDouble/\&.bin/\&.AppleDesktop/Network Trash Folder/ +.fi -The \fBsetdir\fR command is only implemented -in the Digital Pathworks client. See the Pathworks documentation -for details. -Default: \fBset directory = no\fR .TP -\fB>share modes (S)\fR -This enables or disables the honoring of -the \fIshare modes\fR during a file open. These -modes are used by clients to gain exclusive read or write access -to a file. +veto oplock files (S) +This parameter is only valid when the \fIoplocks\fR parameter is turned on for a share\&. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that match a wildcarded list, similar to the wildcarded list used in the \fIveto files\fR parameter\&. -These open modes are not directly supported by UNIX, so -they are simulated using shared memory, or lock files if your -UNIX doesn't support shared memory (almost all do). -The share modes that are enabled by this option are -DENY_DOS, DENY_ALL, -DENY_READ, DENY_WRITE, -DENY_NONE and DENY_FCB. +Default: \fBNo files are vetoed for oplock grants\fR -This option gives full share compatibility and enabled -by default. -You should \fBNEVER\fR turn this parameter -off as many Windows applications will break if you do so. +You might want to do this on files that you know will be heavily contended for by clients\&. A good example of this is in the NetBench SMB benchmark program, which causes heavy client contention for files ending in \fI\&.SEM\fR\&. To cause Samba not to grant oplocks on these files you would use the line (either in the [global] section or in the section for the particular NetBench share : -Default: \fBshare modes = yes\fR -.TP -\fB>short preserve case (S)\fR -This boolean parameter controls if new files -which conform to 8.3 syntax, that is all in upper case and of -suitable length, are created upper case, or if they are forced -to be the \fIdefault case -\fR. This option can be use with \fBpreserve case = yes\fR -to permit long filenames to retain their case, while short -names are lowered. -See the section on NAME MANGLING. +Example: \fBveto oplock files = /*.SEM/\fR -Default: \fBshort preserve case = yes\fR -.TP -\fB>show add printer wizard (G)\fR -With the introduction of MS-RPC based printing support -for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will -appear on Samba hosts in the share listing. Normally this folder will -contain an icon for the MS Add Printer Wizard (APW). However, it is -possible to disable this feature regardless of the level of privilege -of the connected user. - -Under normal circumstances, the Windows NT/2000 client will -open a handle on the printer server with OpenPrinterEx() asking for -Administrator privileges. If the user does not have administrative -access on the print server (i.e is not root or a member of the -\fIprinter admin\fR group), the OpenPrinterEx() -call fails and the client makes another open call with a request for -a lower privilege level. This should succeed, however the APW -icon will not be displayed. - -Disabling the \fIshow add printer wizard\fR -parameter will always cause the OpenPrinterEx() on the server -to fail. Thus the APW icon will never be displayed. \fB Note :\fRThis does not prevent the same user from having -administrative privilege on an individual printer. - -See also \fIaddprinter -command\fR, \fIdeleteprinter command\fR, \fIprinter admin\fR -Default :\fBshow add printer wizard = yes\fR .TP -\fB>shutdown script (G)\fR -\fBThis parameter only exists in the HEAD cvs branch\fR -This a full path name to a script called by -\fBsmbd(8)\fR that -should start a shutdown procedure. +vfs object (S) +This parameter specifies a shared object files that are used for Samba VFS I/O operations\&. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects\&. -This command will be run as the user connected to the -server. -%m %t %r %f parameters are expanded +Default: \fBno value\fR -\fI%m\fR will be substituted with the -shutdown message sent to the server. -\fI%t\fR will be substituted with the -number of seconds to wait before effectively starting the -shutdown procedure. +.TP +vfs options (S) +This parameter allows parameters to be passed to the vfs layer at initialization time\&. See also \fI vfs object\fR\&. -\fI%r\fR will be substituted with the -switch \fB-r\fR. It means reboot after shutdown -for NT. -\fI%f\fR will be substituted with the -switch \fB-f\fR. It means force the shutdown -even if applications do not respond for NT. +Default: \fBno value\fR -Default: \fBNone\fR. -Example: \fBabort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f\fR +.TP +vfs path (S) +This parameter specifies the directory to look in for vfs modules\&. The name of every \fBvfs object \fR will be prepended by this directory\&. -Shutdown script example: -.nf -#!/bin/bash - -$time=0 -let "time/60" -let "time++" +Default: \fBvfs path = \fR -/sbin/shutdown $3 $4 +$time $1 & -.fi -Shutdown does not return so we need to launch it in background. -See also \fIabort shutdown script\fR. -.TP -\fB>smb passwd file (G)\fR -This option sets the path to the encrypted -smbpasswd file. By default the path to the smbpasswd file -is compiled into Samba. +Example: \fBvfs path = /usr/lib/samba/vfs\fR -Default: \fBsmb passwd file = ${prefix}/private/smbpasswd -\fR -Example: \fBsmb passwd file = /etc/samba/smbpasswd -\fR .TP -\fB>smb ports (G)\fR -Specifies which ports the server should listen on -for SMB traffic. +volume (S) +This allows you to override the volume label returned for a share\&. Useful for CDROMs with installation programs that insist on a particular volume label\&. -Default: \fBsmb ports = 445 139\fR -.TP -\fB>socket address (G)\fR -This option allows you to control what -address Samba will listen for connections on. This is used to -support multiple virtual interfaces on the one server, each -with a different configuration. -By default Samba will accept connections on any -address. +Default: \fBthe name of the share\fR + -Example: \fBsocket address = 192.168.2.20\fR .TP -\fB>socket options (G)\fR -This option allows you to set socket options -to be used when talking with the client. - -Socket options are controls on the networking layer -of the operating systems which allow the connection to be -tuned. - -This option will typically be used to tune your Samba -server for optimal performance for your local network. There is -no way that Samba can know what the optimal parameters are for -your net, so you must experiment and choose them yourself. We -strongly suggest you read the appropriate documentation for your -operating system first (perhaps \fBman setsockopt\fR -will help). - -You may find that on some systems Samba will say -"Unknown socket option" when you supply an option. This means you -either incorrectly typed it or you need to add an include file -to includes.h for your OS. If the latter is the case please -send the patch to samba@samba.org . - -Any of the supported socket options may be combined -in any way you like, as long as your OS allows it. - -This is the list of socket options currently settable -using this option: -.RS -.TP 0.2i -\(bu -SO_KEEPALIVE -.TP 0.2i -\(bu -SO_REUSEADDR -.TP 0.2i -\(bu -SO_BROADCAST -.TP 0.2i -\(bu -TCP_NODELAY -.TP 0.2i -\(bu -IPTOS_LOWDELAY -.TP 0.2i -\(bu -IPTOS_THROUGHPUT -.TP 0.2i -\(bu -SO_SNDBUF * -.TP 0.2i -\(bu -SO_RCVBUF * -.TP 0.2i -\(bu -SO_SNDLOWAT * -.TP 0.2i -\(bu -SO_RCVLOWAT * -.RE +wide links (S) +This parameter controls whether or not links in the UNIX file system may be followed by the server\&. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only to areas that are outside the directory tree being exported\&. -Those marked with a \fB'*'\fR take an integer -argument. The others can optionally take a 1 or 0 argument to enable -or disable the option, by default they will be enabled if you -don't specify 1 or 0. -To specify an argument use the syntax SOME_OPTION = VALUE -for example \fBSO_SNDBUF = 8192\fR. Note that you must -not have any spaces before or after the = sign. +Note that setting this parameter can have a negative effect on your server performance due to the extra system calls that Samba has to do in order to perform the link checks\&. -If you are on a local network then a sensible option -might be -\fBsocket options = IPTOS_LOWDELAY\fR +Default: \fBwide links = yes\fR -If you have a local network then you could try: -\fBsocket options = IPTOS_LOWDELAY TCP_NODELAY\fR +.TP +winbind cache time (G) +This parameter specifies the number of seconds the \fBwinbindd\fR(8) daemon will cache user and group information before querying a Windows NT server again\&. -If you are on a wide area network then perhaps try -setting IPTOS_THROUGHPUT. -Note that several of the options may cause your Samba -server to fail completely. Use these options with caution! +Default: \fBwinbind cache type = 15\fR -Default: \fBsocket options = TCP_NODELAY\fR -Example: \fBsocket options = IPTOS_LOWDELAY\fR .TP -\fB>source environment (G)\fR -This parameter causes Samba to set environment -variables as per the content of the file named. +winbind enum groups (G) +On large installations using \fBwinbindd\fR(8) it may be necessary to suppress the enumeration of groups through the \fBsetgrent()\fR, \fBgetgrent()\fR and \fBendgrent()\fR group of system calls\&. If the \fIwinbind enum groups\fR parameter is \fBno\fR, calls to the \fBgetgrent()\fR system call will not return any data\&. -If the value of this parameter starts with a "|" character -then Samba will treat that value as a pipe command to open and -will set the environment variables from the output of the pipe. -The contents of the file or the output of the pipe should -be formatted as the output of the standard Unix \fBenv(1) -\fR command. This is of the form : +\fBWarning:\fR Turning off group enumeration may cause some programs to behave oddly\&. -Example environment entry: - -\fBSAMBA_NETBIOS_NAME = myhostname\fR -Default: \fBNo default value\fR +Default: \fBwinbind enum groups = yes \fR -Examples: \fBsource environment = |/etc/smb.conf.sh -\fR -Example: \fBsource environment = -/usr/local/smb_env_vars\fR .TP -\fB>use spnego (G)\fR -This variable controls controls whether samba will try -to use Simple and Protected NEGOciation (as specified by rfc2478) with -WindowsXP and Windows2000sp2 clients to agree upon an authentication mechanism. -Unless further issues are discovered with our SPNEGO -implementation, there is no reason this should ever be -disabled. +winbind enum users (G) +On large installations using \fBwinbindd\fR(8) it may be necessary to suppress the enumeration of users through the \fBsetpwent()\fR, \fBgetpwent()\fR and \fBendpwent()\fR group of system calls\&. If the \fIwinbind enum users\fR parameter is \fBno\fR, calls to the \fBgetpwent\fR system call will not return any data\&. -Default: \fBuse spnego = yes\fR -.TP -\fB>stat cache (G)\fR -This parameter determines if \fBsmbd\fR(8) will use a cache in order to -speed up case insensitive name mappings. You should never need -to change this parameter. -Default: \fBstat cache = yes\fR -.TP -\fB>stat cache size (G)\fR -This parameter determines the number of -entries in the \fIstat cache\fR. You should -never need to change this parameter. +\fBWarning:\fR Turning off user enumeration may cause some programs to behave oddly\&. For example, the finger program relies on having access to the full user list when searching for matching usernames\&. -Default: \fBstat cache size = 50\fR -.TP -\fB>strict allocate (S)\fR -This is a boolean that controls the handling of -disk space allocation in the server. When this is set to yes -the server will change from UNIX behaviour of not committing real -disk storage blocks when a file is extended to the Windows behaviour -of actually forcing the disk system to allocate real storage blocks -when a file is created or extended to be a given size. In UNIX -terminology this means that Samba will stop creating sparse files. -This can be slow on some systems. -When strict allocate is no the server does sparse -disk block allocation when a file is extended. +Default: \fBwinbind enum users = yes \fR -Setting this to yes can help Samba return -out of quota messages on systems that are restricting the disk quota -of users. -Default: \fBstrict allocate = no\fR .TP -\fB>strict locking (S)\fR -This is a boolean that controls the handling of -file locking in the server. When this is set to yes -the server will check every read and write access for file locks, and -deny access if locks exist. This can be slow on some systems. +winbind gid (G) +The winbind gid parameter specifies the range of group ids that are allocated by the \fBwinbindd\fR(8) daemon\&. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise\&. -When strict locking is no the server does file -lock checks only when the client explicitly asks for them. -Well-behaved clients always ask for lock checks when it -is important, so in the vast majority of cases \fBstrict -locking = no\fR is preferable. +Default: \fBwinbind gid = \fR -Default: \fBstrict locking = no\fR -.TP -\fB>strict sync (S)\fR -Many Windows applications (including the Windows -98 explorer shell) seem to confuse flushing buffer contents to -disk with doing a sync to disk. Under UNIX, a sync call forces -the process to be suspended until the kernel has ensured that -all outstanding data in kernel disk buffers has been safely stored -onto stable storage. This is very slow and should only be done -rarely. Setting this parameter to no (the -default) means that \fBsmbd\fR(8) ignores the Windows applications requests for -a sync call. There is only a possibility of losing data if the -operating system itself that Samba is running on crashes, so there is -little danger in this default setting. In addition, this fixes many -performance problems that people have reported with the new Windows98 -explorer shell file copies. - -See also the \fIsync -always>\fR parameter. -Default: \fBstrict sync = no\fR -.TP -\fB>strip dot (G)\fR -This is a boolean that controls whether to -strip trailing dots off UNIX filenames. This helps with some -CDROMs that have filenames ending in a single dot. +Example: \fBwinbind gid = 10000-20000\fR -Default: \fBstrip dot = no\fR -.TP -\fB>sync always (S)\fR -This is a boolean parameter that controls -whether writes will always be written to stable storage before -the write call returns. If this is no then the server will be -guided by the client's request in each write call (clients can -set a bit indicating that a particular write should be synchronous). -If this is yes then every write will be followed by a \fBfsync() -\fR call to ensure the data is written to disk. Note that -the \fIstrict sync\fR parameter must be set to -yes in order for this parameter to have -any affect. - -See also the \fIstrict -sync\fR parameter. -Default: \fBsync always = no\fR .TP -\fB>syslog (G)\fR -This parameter maps how Samba debug messages -are logged onto the system syslog logging levels. Samba debug -level zero maps onto syslog LOG_ERR, debug -level one maps onto LOG_WARNING, debug level -two maps onto LOG_NOTICE, debug level three -maps onto LOG_INFO. All higher levels are mapped to LOG_DEBUG. +winbind separator (G) +This parameter allows an admin to define the character used when listing a username of the form of \fIDOMAIN \fR\\\fIuser\fR\&. This parameter is only applicable when using the \fIpam_winbind\&.so\fR and \fInss_winbind\&.so\fR modules for UNIX services\&. -This parameter sets the threshold for sending messages -to syslog. Only messages with debug level less than this value -will be sent to syslog. -Default: \fBsyslog = 1\fR -.TP -\fB>syslog only (G)\fR -If this parameter is set then Samba debug -messages are logged into the system syslog only, and not to -the debug log files. +Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group\&. -Default: \fBsyslog only = no\fR -.TP -\fB>template homedir (G)\fR -When filling out the user information for a Windows NT -user, the winbindd(8) daemon -uses this parameter to fill in the home directory for that user. -If the string \fI%D\fR is present it is substituted -with the user's Windows NT domain name. If the string \fI%U -\fR is present it is substituted with the user's Windows -NT user name. -Default: \fBtemplate homedir = /home/%D/%U\fR -.TP -\fB>template shell (G)\fR -When filling out the user information for a Windows NT -user, the \fBwinbindd\fR(8) daemon -uses this parameter to fill in the login shell for that user. +Default: \fBwinbind separator = '\'\fR -Default: \fBtemplate shell = /bin/false\fR -.TP -\fB>time offset (G)\fR -This parameter is a setting in minutes to add -to the normal GMT to local time conversion. This is useful if -you are serving a lot of PCs that have incorrect daylight -saving time handling. -Default: \fBtime offset = 0\fR +Example: \fBwinbind separator = +\fR -Example: \fBtime offset = 60\fR -.TP -\fB>time server (G)\fR -This parameter determines if \fBnmbd\fR(8) advertises itself as a time server to Windows -clients. -Default: \fBtime server = no\fR -.TP -\fB>timestamp logs (G)\fR -Synonym for \fI debug timestamp\fR. .TP -\fB>total print jobs (G)\fR -This parameter accepts an integer value which defines -a limit on the maximum number of print jobs that will be accepted -system wide at any given time. If a print job is submitted -by a client which will exceed this number, then \fBsmbd\fR(8) will return an -error indicating that no space is available on the server. The -default value of 0 means that no such limit exists. This parameter -can be used to prevent a server from exceeding its capacity and is -designed as a printing throttle. See also -\fImax print jobs\fR. +winbind uid (G) +The winbind gid parameter specifies the range of group ids that are allocated by the \fBwinbindd\fR(8) daemon\&. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\&. -Default: \fBtotal print jobs = 0\fR -Example: \fBtotal print jobs = 5000\fR -.TP -\fB>unicode (G)\fR -Specifies whether Samba should try -to use unicode on the wire by default. Note: This does NOT -mean that samba will assume that the unix machine uses unicode! +Default: \fBwinbind uid = \fR -Default: \fBunicode = yes\fR -.TP -\fB>unix charset (G)\fR -Specifies the charset the unix machine -Samba runs on uses. Samba needs to know this in order to be able to -convert text to the charsets other SMB clients use. -Default: \fBunix charset = UTF8\fR +Example: \fBwinbind uid = 10000-20000\fR -Example: \fBunix charset = ASCII\fR -.TP -\fB>unix extensions(G)\fR -This boolean parameter controls whether Samba -implments the CIFS UNIX extensions, as defined by HP. -These extensions enable Samba to better serve UNIX CIFS clients -by supporting features such as symbolic links, hard links, etc... -These extensions require a similarly enabled client, and are of -no current use to Windows clients. -Default: \fBunix extensions = no\fR .TP -\fB>unix password sync (G)\fR -This boolean parameter controls whether Samba -attempts to synchronize the UNIX password with the SMB password -when the encrypted SMB password in the smbpasswd file is changed. -If this is set to yes the program specified in the \fIpasswd -program\fRparameter is called \fBAS ROOT\fR - -to allow the new UNIX password to be set without access to the -old UNIX password (as the SMB password change code has no -access to the old password cleartext, only the new). +winbind used default domain (G) +This parameter specifies whether the \fBwinbindd\fR(8) daemon should operate on users without domain component in their username\&. Users without a domain component are treated as is part of the winbindd server's own domain\&. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system\&. -See also \fIpasswd -program\fR, \fI passwd chat\fR. -Default: \fBunix password sync = no\fR -.TP -\fB>update encrypted (G)\fR -This boolean parameter allows a user logging -on with a plaintext password to have their encrypted (hashed) -password in the smbpasswd file to be updated automatically as -they log on. This option allows a site to migrate from plaintext -password authentication (users authenticate with plaintext -password over the wire, and are checked against a UNIX account -database) to encrypted password authentication (the SMB -challenge/response authentication mechanism) without forcing -all users to re-enter their passwords via smbpasswd at the time the -change is made. This is a convenience option to allow the change over -to encrypted passwords to be made over a longer period. Once all users -have encrypted representations of their passwords in the smbpasswd -file this parameter should be set to no. - -In order for this parameter to work correctly the \fIencrypt passwords\fR -parameter must be set to no when -this parameter is set to yes. - -Note that even when this parameter is set a user -authenticating to \fBsmbd\fR must still enter a valid -password in order to connect correctly, and to update their hashed -(smbpasswd) passwords. - -Default: \fBupdate encrypted = no\fR -.TP -\fB>use client driver (S)\fR -This parameter applies only to Windows NT/2000 -clients. It has no affect on Windows 95/98/ME clients. When -serving a printer to Windows NT/2000 clients without first installing -a valid printer driver on the Samba host, the client will be required -to install a local printer driver. From this point on, the client -will treat the print as a local printer and not a network printer -connection. This is much the same behavior that will occur -when \fBdisable spoolss = yes\fR. - -The differentiating -factor is that under normal circumstances, the NT/2000 client will -attempt to open the network printer using MS-RPC. The problem is that -because the client considers the printer to be local, it will attempt -to issue the OpenPrinterEx() call requesting access rights associated -with the logged on user. If the user possesses local administator rights -but not root privilegde on the Samba host (often the case), the OpenPrinterEx() -call will fail. The result is that the client will now display an "Access -Denied; Unable to connect" message in the printer queue window (even though -jobs may successfully be printed). - -If this parameter is enabled for a printer, then any attempt -to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped -to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() -call to succeed. \fBThis parameter MUST not be able enabled -on a print share which has valid print driver installed on the Samba -server.\fR - -See also disable spoolss +Default: \fBwinbind use default domain = \fR -Default: \fBuse client driver = no\fR -.TP -\fB>use mmap (G)\fR -This global parameter determines if the tdb internals of Samba can -depend on mmap working correctly on the running system. Samba requires a coherent -mmap/read-write system memory cache. Currently only HPUX does not have such a -coherent cache, and so this parameter is set to no by -default on HPUX. On all other systems this parameter should be left alone. This -parameter is provided to help the Samba developers track down problems with -the tdb internal code. -Default: \fBuse mmap = yes\fR -.TP -\fB>user (S)\fR -Synonym for \fI username\fR. -.TP -\fB>users (S)\fR -Synonym for \fI username\fR. -.TP -\fB>username (S)\fR -Multiple users may be specified in a comma-delimited -list, in which case the supplied password will be tested against -each username in turn (left to right). - -The \fIusername\fR line is needed only when -the PC is unable to supply its own username. This is the case -for the COREPLUS protocol or where your users have different WfWg -usernames to UNIX usernames. In both these cases you may also be -better using the \\\\server\\share%user syntax instead. - -The \fIusername\fR line is not a great -solution in many cases as it means Samba will try to validate -the supplied password against each of the usernames in the -\fIusername\fR line in turn. This is slow and -a bad idea for lots of users in case of duplicate passwords. -You may get timeouts or security breaches using this parameter -unwisely. - -Samba relies on the underlying UNIX security. This -parameter does not restrict who can login, it just offers hints -to the Samba server as to what usernames might correspond to the -supplied password. Users can login as whoever they please and -they will be able to do no more damage than if they started a -telnet session. The daemon runs as the user that they log in as, -so they cannot do anything that user cannot do. - -To restrict a service to a particular set of users you -can use the \fIvalid users -\fR parameter. - -If any of the usernames begin with a '@' then the name -will be looked up first in the NIS netgroups list (if Samba -is compiled with netgroup support), followed by a lookup in -the UNIX groups database and will expand to a list of all users -in the group of that name. - -If any of the usernames begin with a '+' then the name -will be looked up only in the UNIX groups database and will -expand to a list of all users in the group of that name. - -If any of the usernames begin with a '&' then the name -will be looked up only in the NIS netgroups database (if Samba -is compiled with netgroup support) and will expand to a list -of all users in the netgroup group of that name. - -Note that searching though a groups database can take -quite some time, and some clients may time out during the -search. - -See the section NOTE ABOUT -USERNAME/PASSWORD VALIDATION for more information on how -this parameter determines access to the services. - -Default: \fBThe guest account if a guest service, -else .\fR - -Examples:\fBusername = fred, mary, jack, jane, -@users, @pcgroup\fR -.TP -\fB>username level (G)\fR -This option helps Samba to try and 'guess' at -the real UNIX username, as many DOS clients send an all-uppercase -username. By default Samba tries all lowercase, followed by the -username with the first letter capitalized, and fails if the -username is not found on the UNIX machine. - -If this parameter is set to non-zero the behavior changes. -This parameter is a number that specifies the number of uppercase -combinations to try while trying to determine the UNIX user name. The -higher the number the more combinations will be tried, but the slower -the discovery of usernames will be. Use this parameter when you have -strange usernames on your UNIX machine, such as AstrangeUser -\&. +Example: \fBwinbind use default domain = yes\fR -Default: \fBusername level = 0\fR -Example: \fBusername level = 5\fR .TP -\fB>username map (G)\fR -This option allows you to specify a file containing -a mapping of usernames from the clients to the server. This can be -used for several purposes. The most common is to map usernames -that users use on DOS or Windows machines to those that the UNIX -box uses. The other is to map multiple users to a single username -so that they can more easily share files. - -The map file is parsed line by line. Each line should -contain a single UNIX username on the left then a '=' followed -by a list of usernames on the right. The list of usernames on the -right may contain names of the form @group in which case they -will match any UNIX username in that group. The special client -name '*' is a wildcard and matches any name. Each line of the -map file may be up to 1023 characters long. - -The file is processed on each line by taking the -supplied username and comparing it with each username on the right -hand side of the '=' signs. If the supplied name matches any of -the names on the right hand side then it is replaced with the name -on the left. Processing then continues with the next line. - -If any line begins with a '#' or a ';' then it is -ignored - -If any line begins with an '!' then the processing -will stop after that line if a mapping was done by the line. -Otherwise mapping continues with every line being processed. -Using '!' is most useful when you have a wildcard mapping line -later in the file. - -For example to map from the name admin -or administrator to the UNIX name root you would use: +wins hook (G) +When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database\&. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS\&. -\fBroot = admin administrator\fR -Or to map anyone in the UNIX group system -to the UNIX name sys you would use: +The wins hook parameter specifies the name of a script or executable that will be called as follows: -\fBsys = @system\fR -You can have as many mappings as you like in a username -map file. +\fBwins_hook operation name nametype ttl IP_list\fR -If your system supports the NIS NETGROUP option then -the netgroup database is checked before the \fI/etc/group -\fR database for matching groups. -You can map Windows usernames that have spaces in them -by using double quotes around the name. For example: +The first argument is the operation and is one of "add", "delete", or "refresh"\&. In most cases the operation can be ignored as the rest of the parameters provide sufficient information\&. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add\&. -\fBtridge = "Andrew Tridgell"\fR +The second argument is the NetBIOS name\&. If the name is not a legal name then the wins hook is not called\&. Legal names contain only letters, digits, hyphens, underscores and periods\&. -would map the windows username "Andrew Tridgell" to the -unix username "tridge". +The third argument is the NetBIOS name type as a 2 digit hexadecimal number\&. -The following example would map mary and fred to the -unix user sys, and map the rest to guest. Note the use of the -\&'!' to tell Samba to stop processing if it gets a match on -that line. +The fourth argument is the TTL (time to live) for the name in seconds\&. +The fifth and subsequent arguments are the IP addresses currently registered for that name\&. If this list is empty then the name should be deleted\&. -.nf -!sys = mary fred -guest = * -.fi +An example script that calls the BIND dynamic DNS update program \fBnsupdate\fR is provided in the examples directory of the Samba source code\&. -Note that the remapping is applied to all occurrences -of usernames. Thus if you connect to \\\\server\\fred and fred is remapped to mary then you -will actually be connecting to \\\\server\\mary and will need to -supply a password suitable for mary not -fred. The only exception to this is the -username passed to the \fI password server\fR (if you have one). The password -server will receive whatever username the client supplies without -modification. -Also note that no reverse mapping is done. The main effect -this has is with printing. Users who have been mapped may have -trouble deleting print jobs as PrintManager under WfWg will think -they don't own the print job. +.TP +wins partner (G) +A space separated list of partners' IP addresses for WINS replication\&. WINS partners are always defined as push/pull partners as defining only one way WINS replication is unreliable\&. WINS replication is currently experimental and unreliable between samba servers\&. -Default: \fBno username map\fR -Example: \fBusername map = /usr/local/samba/lib/users.map -\fR -.TP -\fB>use sendfile (S)\fR -If this parameter is yes, and Samba -was built with the --with-sendfile-support option, and the underlying operating -system supports sendfile system call, then some SMB read calls (mainly ReadAndX -and ReadRaw) will use the more efficient sendfile system call for files that -are exclusively oplocked. This may make more efficient use of the system CPU's -and cause Samba to be faster. This is off by default as it's effects are unknown -as yet. +Default: \fBwins partners = \fR -Default: \fBuse sendfile = no\fR -.TP -\fB>utmp (G)\fR -This boolean parameter is only available if -Samba has been configured and compiled with the option \fB --with-utmp\fR. If set to yes then Samba will attempt -to add utmp or utmpx records (depending on the UNIX system) whenever a -connection is made to a Samba server. Sites may use this to record the -user connecting to a Samba share. -Due to the requirements of the utmp record, we -are required to create a unique identifier for the -incoming user. Enabling this option creates an n^2 -algorithm to find this number. This may impede -performance on large installations. +Example: \fBwins partners = 192.168.0.1 172.16.1.2\fR -See also the \fI utmp directory\fR parameter. -Default: \fButmp = no\fR .TP -\fB>utmp directory(G)\fR -This parameter is only available if Samba has -been configured and compiled with the option \fB --with-utmp\fR. It specifies a directory pathname that is -used to store the utmp or utmpx files (depending on the UNIX system) that -record user connections to a Samba server. See also the \fIutmp\fR parameter. By default this is -not set, meaning the system will use whatever utmp file the -native system is set to use (usually -\fI/var/run/utmp\fR on Linux). +wins proxy (G) +This is a boolean that controls if \fBnmbd\fR(8) will respond to broadcast name queries on behalf of other hosts\&. You may need to set this to \fByes\fR for some older clients\&. -Default: \fBno utmp directory\fR -Example: \fButmp directory = /var/run/utmp\fR -.TP -\fB>wtmp directory(G)\fR -This parameter is only available if Samba has -been configured and compiled with the option \fB --with-utmp\fR. It specifies a directory pathname that is -used to store the wtmp or wtmpx files (depending on the UNIX system) that -record user connections to a Samba server. The difference with -the utmp directory is the fact that user info is kept after a user -has logged out. -See also the \fIutmp\fR parameter. By default this is -not set, meaning the system will use whatever utmp file the -native system is set to use (usually -\fI/var/run/wtmp\fR on Linux). +Default: \fBwins proxy = no\fR -Default: \fBno wtmp directory\fR -Example: \fBwtmp directory = /var/log/wtmp\fR .TP -\fB>valid users (S)\fR -This is a list of users that should be allowed -to login to this service. Names starting with '@', '+' and '&' -are interpreted using the same rules as described in the -\fIinvalid users\fR parameter. +wins server (G) +This specifies the IP address (or DNS name: IP address for preference) of the WINS server that \fBnmbd\fR(8) should register with\&. If you have a WINS server on your network then you should set this to the WINS server's IP\&. -If this is empty (the default) then any user can login. -If a username is in both this list and the \fIinvalid -users\fR list then access is denied for that user. -The current servicename is substituted for \fI%S -\fR. This is useful in the [homes] section. +You should point this at your WINS server if you have a multi-subnetted network\&. -See also \fIinvalid users -\fR -Default: \fBNo valid users list (anyone can login) -\fR +If you want to work in multiple namespaces, you can give every wins server a 'tag'\&. For each tag, only one (working) server will be queried for a name\&. The tag should be seperated from the ip address by a colon\&. -Example: \fBvalid users = greg, @pcusers\fR -.TP -\fB>veto files(S)\fR -This is a list of files and directories that -are neither visible nor accessible. Each entry in the list must -be separated by a '/', which allows spaces to be included -in the entry. '*' and '?' can be used to specify multiple files -or directories as in DOS wildcards. -Each entry must be a unix path, not a DOS path and -must \fBnot\fR include the unix directory -separator '/'. +You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly\&. -Note that the \fIcase sensitive\fR option -is applicable in vetoing files. +See the documentation file Browsing in the samba howto collection\&. -One feature of the veto files parameter that it -is important to be aware of is Samba's behaviour when -trying to delete a directory. If a directory that is -to be deleted contains nothing but veto files this -deletion will \fBfail\fR unless you also set -the \fIdelete veto files\fR parameter to -\fIyes\fR. -Setting this parameter will affect the performance -of Samba, as it will be forced to check all files and directories -for a match as they are scanned. +Default: \fBnot enabled\fR -See also \fIhide files -\fR and \fI case sensitive\fR. -Default: \fBNo files or directories are vetoed. -\fR +Example: \fBwins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61\fR -Examples: -.nf -; Veto any files containing the word Security, -; any ending in .tmp, and any directory containing the -; word root. -veto files = /*Security*/*.tmp/*root*/ +For this example when querying a certain name, 192\&.19\&.200\&.1 will be asked first and if that doesn't respond 192\&.168\&.2\&.61\&. If either of those doesn't know the name 192\&.168\&.3\&.199 will be queried\&. -; Veto the Apple specific files that a NetAtalk server -; creates. -veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/ -.fi -.TP -\fB>veto oplock files (S)\fR -This parameter is only valid when the \fIoplocks\fR -parameter is turned on for a share. It allows the Samba administrator -to selectively turn off the granting of oplocks on selected files that -match a wildcarded list, similar to the wildcarded list used in the -\fIveto files\fR -parameter. - -Default: \fBNo files are vetoed for oplock -grants\fR - -You might want to do this on files that you know will -be heavily contended for by clients. A good example of this -is in the NetBench SMB benchmark program, which causes heavy -client contention for files ending in \fI.SEM\fR. -To cause Samba not to grant oplocks on these files you would use -the line (either in the [global] section or in the section for -the particular NetBench share : - -Example: \fBveto oplock files = /*.SEM/ -\fR -.TP -\fB>vfs path (S)\fR -This parameter specifies the directory -to look in for vfs modules. The name of every \fBvfs object -\fR will be prepended by this directory -Default: \fBvfs path = \fR +Example: \fBwins server = 192.9.200.1 192.168.2.61\fR -Example: \fBvfs path = /usr/lib/samba/vfs\fR -.TP -\fB>vfs object (S)\fR -This parameter specifies a shared object files that -are used for Samba VFS I/O operations. By default, normal -disk I/O operations are used but these can be overloaded -with one or more VFS objects. -Default : \fBno value\fR .TP -\fB>vfs options (S)\fR -This parameter allows parameters to be passed -to the vfs layer at initialization time. -See also \fI vfs object\fR. +wins support (G) +This boolean controls if the \fBnmbd\fR(8) process in Samba will act as a WINS server\&. You should not set this to \fByes\fR unless you have a multi-subnetted network and you wish a particular \fBnmbd\fR to be your WINS server\&. Note that you should \fBNEVER\fR set this to \fByes\fR on more than one machine in your network\&. -Default : \fBno value\fR -.TP -\fB>volume (S)\fR -This allows you to override the volume label -returned for a share. Useful for CDROMs with installation programs -that insist on a particular volume label. -Default: \fBthe name of the share\fR -.TP -\fB>wide links (S)\fR -This parameter controls whether or not links -in the UNIX file system may be followed by the server. Links -that point to areas within the directory tree exported by the -server are always allowed; this parameter controls access only -to areas that are outside the directory tree being exported. +Default: \fBwins support = no\fR -Note that setting this parameter can have a negative -effect on your server performance due to the extra system calls -that Samba has to do in order to perform the link checks. -Default: \fBwide links = yes\fR .TP -\fB>winbind cache time (G)\fR -This parameter specifies the number of -seconds the \fBwinbindd\fR(8) daemon will cache -user and group information before querying a Windows NT server -again. +workgroup (G) +This controls what workgroup your server will appear to be in when queried by clients\&. Note that this parameter also controls the Domain name used with the \fBsecurity = domain\fR setting\&. + + +Default: \fBset at compile time to WORKGROUP\fR + + +Example: \fBworkgroup = MYGROUP\fR -Default: \fBwinbind cache type = 15\fR -.TP -\fB>winbind enum users (G)\fR -On large installations using \fBwinbindd\fR(8) it may be -necessary to suppress the enumeration of users through the \fBsetpwent()\fR, -\fBgetpwent()\fR and -\fBendpwent()\fR group of system calls. If -the \fIwinbind enum users\fR parameter is -no, calls to the \fBgetpwent\fR system call -will not return any data. - -\fBWarning:\fR Turning off user -enumeration may cause some programs to behave oddly. For -example, the finger program relies on having access to the -full user list when searching for matching -usernames. -Default: \fBwinbind enum users = yes \fR .TP -\fB>winbind enum groups (G)\fR -On large installations using \fBwinbindd\fR(8) it may be necessary to suppress -the enumeration of groups through the \fBsetgrent()\fR, -\fBgetgrent()\fR and -\fBendgrent()\fR group of system calls. If -the \fIwinbind enum groups\fR parameter is -no, calls to the \fBgetgrent()\fR system -call will not return any data. +writable (S) +Synonym for \fI writeable\fR for people who can't spell :-)\&. -\fBWarning:\fR Turning off group -enumeration may cause some programs to behave oddly. -Default: \fBwinbind enum groups = yes \fR .TP -\fB>winbind gid (G)\fR -The winbind gid parameter specifies the range of group -ids that are allocated by the \fBwinbindd\fR(8) daemon. This range of group ids should have no -existing local or NIS groups within it as strange conflicts can -occur otherwise. +writeable (S) +Inverted synonym for \fIread only\fR\&. -Default: \fBwinbind gid = -\fR -Example: \fBwinbind gid = 10000-20000\fR .TP -\fB>winbind separator (G)\fR -This parameter allows an admin to define the character -used when listing a username of the form of \fIDOMAIN -\fR\\\fIuser\fR. This parameter -is only applicable when using the \fIpam_winbind.so\fR -and \fInss_winbind.so\fR modules for UNIX services. +write cache size (S) +If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file (it does \fBnot\fR do this for non-oplocked files)\&. All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible\&. The cache is flushed onto disk when a write comes in whose offset would not fit into the cache or when the file is closed by the client\&. Reads for the file are also served from this cache if the data is stored within it\&. -Please note that setting this parameter to + causes problems -with group membership at least on glibc systems, as the character + -is used as a special character for NIS in /etc/group. -Default: \fBwinbind separator = '\\'\fR +This cache allows Samba to batch client writes into a more efficient write size for RAID disks (i\&.e\&. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs\&. -Example: \fBwinbind separator = +\fR -.TP -\fB>winbind uid (G)\fR -The winbind gid parameter specifies the range of group -ids that are allocated by the \fBwinbindd\fR(8) daemon. This range of ids should have no -existing local or NIS users within it as strange conflicts can -occur otherwise. -Default: \fBwinbind uid = -\fR +The integer parameter specifies the size of this cache (per oplocked file) in bytes\&. -Example: \fBwinbind uid = 10000-20000\fR -.TP -\fB>winbind use default domain (G)\fR -This parameter specifies whether the \fBwinbindd\fR(8) daemon should operate on users -without domain component in their username. -Users without a domain component are treated as is part of the winbindd server's -own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail -function in a way much closer to the way they would in a native unix system. -Default: \fBwinbind use default domain = -\fR +Default: \fBwrite cache size = 0\fR -Example: \fBwinbind use default domain = yes\fR -.TP -\fB>wins hook (G)\fR -When Samba is running as a WINS server this -allows you to call an external program for all changes to the -WINS database. The primary use for this option is to allow the -dynamic update of external name resolution databases such as -dynamic DNS. -The wins hook parameter specifies the name of a script -or executable that will be called as follows: +Example: \fBwrite cache size = 262144\fR -\fBwins_hook operation name nametype ttl IP_list -\fR -.RS -.TP 0.2i -\(bu -The first argument is the operation and is one -of "add", "delete", or "refresh". In most cases the operation can -be ignored as the rest of the parameters provide sufficient -information. Note that "refresh" may sometimes be called when the -name has not previously been added, in that case it should be treated -as an add. -.TP 0.2i -\(bu -The second argument is the NetBIOS name. If the -name is not a legal name then the wins hook is not called. -Legal names contain only letters, digits, hyphens, underscores -and periods. -.TP 0.2i -\(bu -The third argument is the NetBIOS name -type as a 2 digit hexadecimal number. -.TP 0.2i -\(bu -The fourth argument is the TTL (time to live) -for the name in seconds. -.TP 0.2i -\(bu -The fifth and subsequent arguments are the IP -addresses currently registered for that name. If this list is -empty then the name should be deleted. -.RE -An example script that calls the BIND dynamic DNS update -program \fBnsupdate\fR is provided in the examples -directory of the Samba source code. -.TP -\fB>wins proxy (G)\fR -This is a boolean that controls if nmbd(8) will respond to broadcast name -queries on behalf of other hosts. You may need to set this -to yes for some older clients. +for a 256k cache size per file\&. + -Default: \fBwins proxy = no\fR .TP -\fB>wins server (G)\fR -This specifies the IP address (or DNS name: IP -address for preference) of the WINS server that \fBnmbd\fR(8) should register with. If you have a WINS server on -your network then you should set this to the WINS server's IP. +write list (S) +This is a list of users that are given read-write access to a service\&. If the connecting user is in this list then they will be given write access, no matter what the \fIread only\fR option is set to\&. The list can include group names using the @group syntax\&. -You should point this at your WINS server if you have a -multi-subnetted network. -If you want to work in multiple namespaces, you can -give every wins server a 'tag'. For each tag, only one -(working) server will be queried for a name. The tag should be -seperated from the ip address by a colon. -.sp -.RS -.B "Note:" -You need to set up Samba to point -to a WINS server if you have multiple subnets and wish cross-subnet -browsing to work correctly. -.RE +Note that if a user is in both the read list and the write list then they will be given write access\&. -See the documentation file Browsing in the samba howto collection. -Default: \fBnot enabled\fR +See also the \fIread list \fR option\&. -Example: \fBwins server = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61\fR -For this example when querying a certain name, 192.19.200.1 will -be asked first and if that doesn't respond 192.168.2.61. If either -of those doesn't know the name 192.168.3.199 will be queried. +Default: \fBwrite list = \fR + + +Example: \fBwrite list = admin, root, @staff\fR -Example: \fBwins server = 192.9.200.1 192.168.2.61\fR -.TP -\fB>wins support (G)\fR -This boolean controls if the \fBnmbd\fR(8) process in Samba will act as a WINS server. You should -not set this to yes unless you have a multi-subnetted network and -you wish a particular \fBnmbd\fR to be your WINS server. -Note that you should \fBNEVER\fR set this to yes -on more than one machine in your network. -Default: \fBwins support = no\fR .TP -\fB>workgroup (G)\fR -This controls what workgroup your server will -appear to be in when queried by clients. Note that this parameter -also controls the Domain name used with the \fBsecurity = domain\fR -setting. +write ok (S) +Inverted synonym for \fIread only\fR\&. -Default: \fBset at compile time to WORKGROUP\fR -Example: \fBworkgroup = MYGROUP\fR .TP -\fB>writable (S)\fR -Synonym for \fI writeable\fR for people who can't spell :-). -.TP -\fB>write cache size (S)\fR -If this integer parameter is set to non-zero value, -Samba will create an in-memory cache for each oplocked file -(it does \fBnot\fR do this for -non-oplocked files). All writes that the client does not request -to be flushed directly to disk will be stored in this cache if possible. -The cache is flushed onto disk when a write comes in whose offset -would not fit into the cache or when the file is closed by the client. -Reads for the file are also served from this cache if the data is stored -within it. - -This cache allows Samba to batch client writes into a more -efficient write size for RAID disks (i.e. writes may be tuned to -be the RAID stripe size) and can improve performance on systems -where the disk subsystem is a bottleneck but there is free -memory for userspace programs. - -The integer parameter specifies the size of this cache -(per oplocked file) in bytes. +write raw (G) +This parameter controls whether or not the server will support raw write SMB's when transferring data from clients\&. You should never need to change this parameter\&. -Default: \fBwrite cache size = 0\fR -Example: \fBwrite cache size = 262144\fR +Default: \fBwrite raw = yes\fR + -for a 256k cache size per file. .TP -\fB>write list (S)\fR -This is a list of users that are given read-write -access to a service. If the connecting user is in this list then -they will be given write access, no matter what the \fIread only\fR -option is set to. The list can include group names using the -@group syntax. +wtmp directory (G) +This parameter is only available if Samba has been configured and compiled with the option \fB --with-utmp\fR\&. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server\&. The difference with the utmp directory is the fact that user info is kept after a user has logged out\&. -Note that if a user is in both the read list and the -write list then they will be given write access. -See also the \fIread list -\fR option. +See also the \fIutmp\fR parameter\&. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually \fI/var/run/wtmp\fR on Linux)\&. -Default: \fBwrite list = -\fR -Example: \fBwrite list = admin, root, @staff -\fR -.TP -\fB>wins partners (G)\fR -A space separated list of partners' IP addresses for -WINS replication. WINS partners are always defined as push/pull -partners as defining only one way WINS replication is unreliable. -WINS replication is currently experimental and unreliable between -samba servers. +Default: \fBno wtmp directory\fR -Default: \fBwins partners = \fR -Example: \fBwins partners = 192.168.0.1 172.16.1.2\fR -.TP -\fB>write ok (S)\fR -Inverted synonym for \fI read only\fR. -.TP -\fB>write raw (G)\fR -This parameter controls whether or not the server -will support raw write SMB's when transferring data from clients. -You should never need to change this parameter. +Example: \fBwtmp directory = /var/log/wtmp\fR + -Default: \fBwrite raw = yes\fR -.TP -\fB>writeable (S)\fR -Inverted synonym for \fI read only\fR. .SH "WARNINGS" + .PP -Although the configuration file permits service names -to contain spaces, your client software may not. Spaces will -be ignored in comparisons anyway, so it shouldn't be a -problem - but be aware of the possibility. +Although the configuration file permits service names to contain spaces, your client software may not\&. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility\&. + .PP -On a similar note, many clients - especially DOS clients - -limit service names to eight characters. \fBsmbd\fR(8) has no such limitation, but attempts to connect from such -clients will fail if they truncate the service names. For this reason -you should probably keep your service names down to eight characters -in length. +On a similar note, many clients - especially DOS clients - limit service names to eight characters\&. \fBsmbd\fR(8) has no such limitation, but attempts to connect from such clients will fail if they truncate the service names\&. For this reason you should probably keep your service names down to eight characters in length\&. + .PP -Use of the [homes] and [printers] special sections make life -for an administrator easy, but the various combinations of default -attributes can be tricky. Take extreme care when designing these -sections. In particular, ensure that the permissions on spool -directories are correct. +Use of the [homes] and [printers] special sections make life for an administrator easy, but the various combinations of default attributes can be tricky\&. Take extreme care when designing these sections\&. In particular, ensure that the permissions on spool directories are correct\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsamba\fR(7), \fBsmbpasswd\fR(8), \fBswat\fR(8), \fBsmbd\fR(8), \fBnmbd\fR(8), \fBsmbclient\fR(1), \fBnmblookup\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1). +\fBsamba\fR(7), \fBsmbpasswd\fR(8), \fBswat\fR(8), \fBsmbd\fR(8), \fBnmbd\fR(8), \fBsmbclient\fR(1), \fBnmblookup\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbcacls.1 b/docs/manpages/smbcacls.1 index 918c2386de..9df06dff9b 100644 --- a/docs/manpages/smbcacls.1 +++ b/docs/manpages/smbcacls.1 @@ -1,127 +1,135 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBCACLS" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBCACLS" 1 "" "" "" .SH NAME smbcacls \- Set or get ACLs on an NT file or directory names -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbcacls\fR \fB//server/share\fR \fBfilename\fR [ \fB-D acls\fR ] [ \fB-M acls\fR ] [ \fB-A acls\fR ] [ \fB-S acls\fR ] [ \fB-C name\fR ] [ \fB-G name\fR ] [ \fB-n\fR ] [ \fB-t\fR ] [ \fB-U username\fR ] [ \fB-h\fR ] [ \fB-d\fR ] +.nf +\fBsmbcacls\fR {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d] + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The \fBsmbcacls\fR program manipulates NT Access Control -Lists (ACLs) on SMB file shares. +The \fBsmbcacls\fR program manipulates NT Access Control Lists (ACLs) on SMB file shares\&. + .SH "OPTIONS" + .PP -The following options are available to the \fBsmbcacls\fR program. -The format of ACLs is described in the section ACL FORMAT -.TP -\fB-A acls\fR -Add the ACLs specified to the ACL list. Existing -access control entries are unchanged. -.TP -\fB-M acls\fR -Modify the mask value (permissions) for the ACLs -specified on the command line. An error will be printed for each -ACL specified that was not already present in the ACL list -.TP -\fB-D acls\fR -Delete any ACLs specified on the command line. -An error will be printed for each ACL specified that was not -already present in the ACL list. -.TP -\fB-S acls\fR -This command sets the ACLs on the file with -only the ones specified on the command line. All other ACLs are -erased. Note that the ACL specified must contain at least a revision, -type, owner and group for the call to succeed. -.TP -\fB-U username\fR -Specifies a username used to connect to the -specified service. The username may be of the form "username" in -which case the user is prompted to enter in a password and the -workgroup specified in the \fBsmb.conf\fR(5) file is -used, or "username%password" or "DOMAIN\\username%password" and the -password and workgroup names are used as provided. -.TP -\fB-C name\fR -The owner of a file or directory can be changed -to the name given using the \fI-C\fR option. -The name can be a sid in the form S-1-x-y-z or a name resolved -against the server specified in the first argument. - -This command is a shortcut for -M OWNER:name. -.TP -\fB-G name\fR -The group owner of a file or directory can -be changed to the name given using the \fI-G\fR -option. The name can be a sid in the form S-1-x-y-z or a name -resolved against the server specified n the first argument. - -This command is a shortcut for -M GROUP:name. -.TP -\fB-n\fR -This option displays all ACL information in numeric -format. The default is to convert SIDs to names and ACE types -and masks to a readable string format. -.TP -\fB-t\fR -Don't actually do anything, only validate the correctness of -the arguments. -.TP -\fB-h|--help\fR -Print a summary of command line options. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +The following options are available to the \fBsmbcacls\fR program\&. The format of ACLs is described in the section ACL FORMAT + +.TP +-A acls +Add the ACLs specified to the ACL list\&. Existing access control entries are unchanged\&. + + +.TP +-M acls +Modify the mask value (permissions) for the ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list + + +.TP +-D acls +Delete any ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list\&. + + +.TP +-S acls +This command sets the ACLs on the file with only the ones specified on the command line\&. All other ACLs are erased\&. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed\&. + + +.TP +-U username +Specifies a username used to connect to the specified service\&. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the \fBsmb.conf\fR(5) file is used, or "username%password" or "DOMAIN\\username%password" and the password and workgroup names are used as provided\&. + + +.TP +-C name +The owner of a file or directory can be changed to the name given using the \fI-C\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified in the first argument\&. + + +This command is a shortcut for -M OWNER:name\&. + + +.TP +-G name +The group owner of a file or directory can be changed to the name given using the \fI-G\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument\&. + + +This command is a shortcut for -M GROUP:name\&. + + +.TP +-n +This option displays all ACL information in numeric format\&. The default is to convert SIDs to names and ACE types and masks to a readable string format\&. + + +.TP +-t +Don't actually do anything, only validate the correctness of the arguments\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + +.TP +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + +.TP +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .SH "ACL FORMAT" + .PP -The format of an ACL is one or more ACL entries separated by -either commas or newlines. An ACL entry is one of the following: +The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following: + .PP .nf @@ -131,102 +139,108 @@ OWNER: GROUP: ACL::// .fi + + +.PP +The revision of the ACL specifies the internal Windows NT ACL revision for the security descriptor\&. If not specified it defaults to 1\&. Using values other than 1 may cause strange behaviour\&. + .PP -The revision of the ACL specifies the internal Windows -NT ACL revision for the security descriptor. -If not specified it defaults to 1. Using values other than 1 may -cause strange behaviour. -.PP -The owner and group specify the owner and group sids for the -object. If a SID in the format CWS-1-x-y-z is specified this is used, -otherwise the name specified is resolved using the server on which -the file or directory resides. -.PP -ACLs specify permissions granted to the SID. This SID again -can be specified in CWS-1-x-y-z format or as a name in which case -it is resolved against the server on which the file or directory -resides. The type, flags and mask values determine the type of -access granted to the SID. -.PP -The type can be either 0 or 1 corresponding to ALLOWED or -DENIED access to the SID. The flags values are generally -zero for file ACLs and either 9 or 2 for directory ACLs. Some -common flags are: -.TP 0.2i +The owner and group specify the owner and group sids for the object\&. If a SID in the format CWS-1-x-y-z is specified this is used, otherwise the name specified is resolved using the server on which the file or directory resides\&. + +.PP +ACLs specify permissions granted to the SID\&. This SID again can be specified in CWS-1-x-y-z format or as a name in which case it is resolved against the server on which the file or directory resides\&. The type, flags and mask values determine the type of access granted to the SID\&. + +.PP +The type can be either 0 or 1 corresponding to ALLOWED or DENIED access to the SID\&. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs\&. Some common flags are: + +.TP 3 \(bu -#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1 -.TP 0.2i +\fB#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1\fR + +.TP \(bu -#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2 -.TP 0.2i +\fB#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2\fR + +.TP \(bu -#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4 -.TP 0.2i +\fB#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4\fR + +.TP \(bu -#define SEC_ACE_FLAG_INHERIT_ONLY 0x8 +\fB#define SEC_ACE_FLAG_INHERIT_ONLY 0x8\fR + +.LP + .PP -At present flags can only be specified as decimal or -hexadecimal values. +At present flags can only be specified as decimal or hexadecimal values\&. + .PP -The mask is a value which expresses the access right -granted to the SID. It can be given as a decimal or hexadecimal value, -or by using one of the following text strings which map to the NT -file permissions of the same name. -.TP 0.2i +The mask is a value which expresses the access right granted to the SID\&. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT file permissions of the same name\&. + +.TP 3 \(bu -\fBR\fR - Allow read access -.TP 0.2i +\fBR\fR - Allow read access + +.TP \(bu \fBW\fR - Allow write access -.TP 0.2i + +.TP \(bu \fBX\fR - Execute permission on the object -.TP 0.2i + +.TP \(bu \fBD\fR - Delete the object -.TP 0.2i + +.TP \(bu \fBP\fR - Change permissions -.TP 0.2i + +.TP \(bu \fBO\fR - Take ownership + +.LP + .PP The following combined permissions can be specified: -.TP 0.2i + +.TP 3 \(bu -\fBREAD\fR - Equivalent to 'RX' -permissions -.TP 0.2i +\fBREAD\fR - Equivalent to 'RX' permissions + +.TP \(bu \fBCHANGE\fR - Equivalent to 'RXWD' permissions -.TP 0.2i + +.TP \(bu -\fBFULL\fR - Equivalent to 'RWXDPO' -permissions +\fBFULL\fR - Equivalent to 'RWXDPO' permissions + +.LP + .SH "EXIT STATUS" + .PP -The \fBsmbcacls\fR program sets the exit status -depending on the success or otherwise of the operations performed. -The exit status may be one of the following values. +The \fBsmbcacls\fR program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&. + .PP -If the operation succeeded, smbcacls returns and exit -status of 0. If \fBsmbcacls\fR couldn't connect to the specified server, -or there was an error getting or setting the ACLs, an exit status -of 1 is returned. If there was an error parsing any command line -arguments, an exit status of 2 is returned. +If the operation succeeded, smbcacls returns and exit status of 0\&. If \fBsmbcacls\fR couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -\fBsmbcacls\fR was written by Andrew Tridgell -and Tim Potter. +\fBsmbcacls\fR was written by Andrew Tridgell and Tim Potter\&. + .PP -The conversion to DocBook for Samba 2.2 was done -by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done -by Alexander Bokovoy. +The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbclient.1 b/docs/manpages/smbclient.1 index 8a70aed551..3f5718a2fa 100644 --- a/docs/manpages/smbclient.1 +++ b/docs/manpages/smbclient.1 @@ -1,808 +1,651 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBCLIENT" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBCLIENT" 1 "" "" "" .SH NAME -smbclient \- ftp-like client to access SMB/CIFS resources on servers -.SH SYNOPSIS +smbclient \- ftp-like client to access SMB/CIFS resources on servers +.SH "SYNOPSIS" -\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b \fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M \fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L \fR ] [ \fB-I destinationIP\fR ] [ \fB-E\fR ] [ \fB-c \fR ] [ \fB-i scope\fR ] [ \fB-O \fR ] [ \fB-p port\fR ] [ \fB-R \fR ] [ \fB-s \fR ] [ \fB-TIXFqgbNan\fR ] [ \fB-k\fR ] +.nf +\fBsmbclient\fR {servicename} [password] [-b ] [-d debuglevel] [-D Directory] + [-U username] [-W workgroup] [-M ] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L ] [-I destinationIP] [-E] [-c ] [-i scope] [-O ] [-p port] [-R ] [-s ] [-TIXFqgbNan] [-k] + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbclient\fR is a client that can -\&'talk' to an SMB/CIFS server. It offers an interface -similar to that of the ftp program (see \fBftp\fR(1)). -Operations include things like getting files from the server -to the local machine, putting files from the local machine to -the server, retrieving directory information from the server -and so on. +\fBsmbclient\fR is a client that can 'talk' to an SMB/CIFS server\&. It offers an interface similar to that of the ftp program (see \fBftp\fR(1))\&. Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on\&. + .SH "OPTIONS" + +.TP +servicename +servicename is the name of the service you want to use on the server\&. A service name takes the form \fI//server/service\fR where \fIserver \fR is the NetBIOS name of the SMB/CIFS server offering the desired service and \fIservice\fR is the name of the service offered\&. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", you would use the servicename \fI//smbserver/printer \fR + + +Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server\&. + + +The server name is looked up according to either the \fI-R\fR parameter to \fBsmbclient\fR or using the name resolve order parameter in the \fBsmb.conf\fR(5) file, allowing an administrator to change the order and methods by which server names are looked up\&. + + +.TP +password +The password required to access the specified service on the specified server\&. If this parameter is supplied, the \fI-N\fR option (suppress password prompt) is assumed\&. + + +There is no default password\&. If no password is supplied on the command line (either by using this parameter or adding a password to the \fI-U\fR option (see below)) and the \fI-N\fR option is not specified, the client will prompt for a password, even if the desired service does not require one\&. (If no password is required, simply press ENTER to provide a null password\&.) + + +Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password\&. Lowercase or mixed case passwords may be rejected by these servers\&. + + +Be cautious about including passwords in scripts\&. + + +.TP +-R +This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses\&. The option takes a space-separated string of different name resolution options\&. + + +The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows: + + +\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&. + +\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&. + +\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&. + +\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. + +If this parameter is not set then the name resolve order defined in the \fBsmb.conf\fR(5) file parameter (name resolve order) will be used\&. + + +The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the \fIname resolve order \fR parameter of the \fBsmb.conf\fR(5) file the name resolution methods will be attempted in this order\&. + + +.TP +-M NetBIOS name +This options allows you to send messages, using the "WinPopup" protocol, to another computer\&. Once a connection is established you then type your message, pressing ^D (control-D) to end\&. + + +If the receiving computer is running WinPopup the user will receive the message and probably a beep\&. If they are not running WinPopup the message will be lost, and no error message will occur\&. + + +The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol\&. + + +One useful trick is to cat the message through \fBsmbclient\fR\&. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will send the message in the file \fImymessage\&.txt\fR to the machine FRED\&. + + +You may also find the \fI-U\fR and \fI-I\fR options useful, as they allow you to control the FROM and TO parts of the message\&. + + +See the \fImessage command\fR parameter in the \fBsmb.conf\fR(5) for a description of how to handle incoming WinPopup messages in Samba\&. + + +\fBNote\fR: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages\&. + + +.TP +-p port +This number is the TCP port number that will be used when making connections to the server\&. The standard (well-known) TCP port number for an SMB/CIFS server is 139, which is the default\&. + + +.TP +-l logfilename +If specified, \fIlogfilename\fR specifies a base filename into which operational data from the running client will be logged\&. + + +The default base name is specified at compile time\&. + + +The base name is used to generate actual log file names\&. For example, if the name specified was "log", the debug file would be \fIlog\&.client\fR\&. + + +The log file generated is never removed by the client\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + +.TP +-I IP-address +\fIIP address\fR is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&. + + +Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the \fIname resolve order\fR parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&. + + +There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&. + + +.TP +-E +This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream\&. + + +By default, the client writes messages to standard output - typically the user's tty\&. + + +.TP +-L +This option allows you to look at what services are available on a server\&. You use it as \fBsmbclient -L host\fR and a list should appear\&. The \fI-I \fR option may be useful if your NetBIOS names don't match your TCP/IP DNS host names or if you are trying to reach a host on another network\&. + + +.TP +-t terminal code +This option tells \fBsmbclient\fR how to interpret filenames coming from the remote server\&. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example)\&. Setting this parameter will let \fBsmbclient\fR convert between the UNIX filenames and the SMB filenames correctly\&. This option has not been seriously tested and may have some problems\&. + + +The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet, CWhex, CWcap\&. This is not a complete list, check the Samba source code for the complete list\&. + + +.TP +-b buffersize +This option changes the transmit/send buffer size when getting or putting a file from/to the server\&. The default is 65520 bytes\&. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server\&. + + +.TP +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fBservicename\fR -servicename is the name of the service -you want to use on the server. A service name takes the form -\fI//server/service\fR where \fIserver -\fR is the NetBIOS name of the SMB/CIFS server -offering the desired service and \fIservice\fR -is the name of the service offered. Thus to connect to -the service "printer" on the SMB/CIFS server "smbserver", -you would use the servicename \fI//smbserver/printer -\fR - -Note that the server name required is NOT necessarily -the IP (DNS) host name of the server ! The name required is -a NetBIOS server name, which may or may not be the -same as the IP hostname of the machine running the server. - -The server name is looked up according to either -the \fI-R\fR parameter to \fBsmbclient\fR or -using the name resolve order parameter in -the \fBsmb.conf\fR(5) file, -allowing an administrator to change the order and methods -by which server names are looked up. -.TP -\fBpassword\fR -The password required to access the specified -service on the specified server. If this parameter is -supplied, the \fI-N\fR option (suppress -password prompt) is assumed. - -There is no default password. If no password is supplied -on the command line (either by using this parameter or adding -a password to the \fI-U\fR option (see -below)) and the \fI-N\fR option is not -specified, the client will prompt for a password, even if -the desired service does not require one. (If no password is -required, simply press ENTER to provide a null password.) - -Note: Some servers (including OS/2 and Windows for -Workgroups) insist on an uppercase password. Lowercase -or mixed case passwords may be rejected by these servers. - -Be cautious about including passwords in scripts. -.TP -\fB-R \fR -This option is used by the programs in the Samba -suite to determine what naming services and in what order to resolve -host names to IP addresses. The option takes a space-separated -string of different name resolution options. - -The options are :"lmhosts", "host", "wins" and "bcast". They -cause names to be resolved as follows: -.RS -.TP 0.2i -\(bu -lmhosts: Lookup an IP -address in the Samba lmhosts file. If the line in lmhosts has -no name type attached to the NetBIOS name (see -the \fBlmhosts\fR(5) for details) then -any name type matches for lookup. -.TP 0.2i -\(bu -host: Do a standard host -name to IP address resolution, using the system \fI/etc/hosts -\fR, NIS, or DNS lookups. This method of name resolution -is operating system dependent, for instance on IRIX or Solaris this -may be controlled by the \fI/etc/nsswitch.conf\fR -file). Note that this method is only used if the NetBIOS name -type being queried is the 0x20 (server) name type, otherwise -it is ignored. -.TP 0.2i -\(bu -wins: Query a name with -the IP address listed in the \fIwins server\fR -parameter. If no WINS server has -been specified this method will be ignored. -.TP 0.2i -\(bu -bcast: Do a broadcast on -each of the known local interfaces listed in the -\fIinterfaces\fR -parameter. This is the least reliable of the name resolution -methods as it depends on the target host being on a locally -connected subnet. -.RE - -If this parameter is not set then the name resolve order -defined in the \fBsmb.conf\fR(5) file parameter -(name resolve order) will be used. - -The default order is lmhosts, host, wins, bcast and without -this parameter or any entry in the \fIname resolve order -\fR parameter of the \fBsmb.conf\fR(5) file the name resolution -methods will be attempted in this order. -.TP -\fB-M NetBIOS name\fR -This options allows you to send messages, using -the "WinPopup" protocol, to another computer. Once a connection is -established you then type your message, pressing ^D (control-D) to -end. - -If the receiving computer is running WinPopup the user will -receive the message and probably a beep. If they are not running -WinPopup the message will be lost, and no error message will -occur. - -The message is also automatically truncated if the message -is over 1600 bytes, as this is the limit of the protocol. - -One useful trick is to cat the message through -\fBsmbclient\fR. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will -send the message in the file \fImymessage.txt\fR -to the machine FRED. - -You may also find the \fI-U\fR and -\fI-I\fR options useful, as they allow you to -control the FROM and TO parts of the message. - -See the \fImessage command\fR parameter in the \fBsmb.conf\fR(5) for a description of how to handle incoming -WinPopup messages in Samba. - -\fBNote\fR: Copy WinPopup into the startup group -on your WfWg PCs if you want them to always be able to receive -messages. -.TP -\fB-p port\fR -This number is the TCP port number that will be used -when making connections to the server. The standard (well-known) -TCP port number for an SMB/CIFS server is 139, which is the -default. -.TP -\fB-l logfilename\fR -If specified, \fIlogfilename\fR specifies a base filename -into which operational data from the running client will be -logged. - -The default base name is specified at compile time. - -The base name is used to generate actual log file names. -For example, if the name specified was "log", the debug file -would be \fIlog.client\fR. - -The log file generated is never removed by the client. -.TP -\fB-h|--help\fR -Print a summary of command line options. -.TP -\fB-I IP-address\fR -\fIIP address\fR is the address of the server to connect to. -It should be specified in standard "a.b.c.d" notation. - -Normally the client would attempt to locate a named -SMB/CIFS server by looking it up via the NetBIOS name resolution -mechanism described above in the \fIname resolve order\fR -parameter above. Using this parameter will force the client -to assume that the server is on the machine with the specified IP -address and the NetBIOS name component of the resource being -connected to will be ignored. - -There is no default for this parameter. If not supplied, -it will be determined automatically by the client as described -above. -.TP -\fB-E\fR -This parameter causes the client to write messages -to the standard error stream (stderr) rather than to the standard -output stream. - -By default, the client writes messages to standard output -- typically the user's tty. -.TP -\fB-L\fR -This option allows you to look at what services -are available on a server. You use it as \fBsmbclient -L -host\fR and a list should appear. The \fI-I -\fR option may be useful if your NetBIOS names don't -match your TCP/IP DNS host names or if you are trying to reach a -host on another network. -.TP -\fB-t terminal code\fR -This option tells \fBsmbclient\fR how to interpret -filenames coming from the remote server. Usually Asian language -multibyte UNIX implementations use different character sets than -SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example). Setting this parameter will let -\fBsmbclient\fR convert between the UNIX filenames and -the SMB filenames correctly. This option has not been seriously tested -and may have some problems. - -The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, -CWjunet, CWhex, CWcap. This is not a complete list, check the Samba -source code for the complete list. -.TP -\fB-b buffersize\fR -This option changes the transmit/send buffer -size when getting or putting a file from/to the server. The default -is 65520 bytes. Setting this value smaller (to 1200 bytes) has been -observed to speed up file transfers to and from a Win9x server. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. -.TP -\fB-N\fR -If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. - -Unless a password is specified on the command line or -this parameter is specified, the client will request a -password. -.TP -\fB-k\fR -Try to authenticate with kerberos. Only useful in -an Active Directory environment. -.TP -\fB-A|--authfile=filename\fR -This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + +.TP +-N +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&. + + +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&. + + +.TP +-k +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&. + + +.TP +-A|--authfile=filename +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is .nf + username = password = domain = .fi -Make certain that the permissions on the file restrict -access from unwanted users. -.TP -\fB-U|--user=username[%password]\fR -Sets the SMB username or username and password. - -If %password is not specified, the user will be prompted. The -client will first check the \fBUSER\fR environment variable, then the -\fBLOGNAME\fR variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username GUEST is used. - -A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -\fI-A\fR for more details. - -Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the \fBps\fR command. To be safe always allow -\fBrpcclient\fR to prompt for a password and type -it in directly. -.TP -\fB-n \fR -This option allows you to override -the NetBIOS name that Samba uses for itself. This is identical -to setting the \fINetBIOS -name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command -line setting will take precedence over settings in -\fBsmb.conf\fR(5). -.TP -\fB-i \fR -This specifies a NetBIOS scope that -\fBnmblookup\fR will use to communicate with when -generating NetBIOS names. For details on the use of NetBIOS -scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are -\fBvery\fR rarely used, only set this parameter -if you are the system administrator in charge of all the -NetBIOS systems you communicate with. -.TP -\fB-W|--workgroup=domain\fR -Set the SMB domain of the username. This -overrides the default domain which is the domain defined in -smb.conf. If the domain specified is the same as the servers -NetBIOS name, it causes the client to log on using the servers local -SAM (as opposed to the Domain SAM). -.TP -\fB-O socket options\fR -TCP socket options to set on the client -socket. See the socket options parameter in -the \fBsmb.conf\fR(5) manual page for the list of valid -options. -.TP -\fB-T tar options\fR -smbclient may be used to create \fBtar(1) -\fR compatible backups of all the files on an SMB/CIFS -share. The secondary tar flags that can be given to this option -are : -.RS -.TP 0.2i -\(bu -\fIc\fR - Create a tar file on UNIX. -Must be followed by the name of a tar file, tape device -or "-" for standard output. If using standard output you must -turn the log level to its lowest value -d0 to avoid corrupting -your tar file. This flag is mutually exclusive with the -\fIx\fR flag. -.TP 0.2i -\(bu -\fIx\fR - Extract (restore) a local -tar file back to a share. Unless the -D option is given, the tar -files will be restored from the top level of the share. Must be -followed by the name of the tar file, device or "-" for standard -input. Mutually exclusive with the \fIc\fR flag. -Restored files have their creation times (mtime) set to the -date saved in the tar file. Directories currently do not get -their creation dates restored properly. -.TP 0.2i -\(bu -\fII\fR - Include files and directories. -Is the default behavior when filenames are specified above. Causes -tar files to be included in an extract or create (and therefore -everything else to be excluded). See example below. Filename globbing -works in one of two ways. See r below. -.TP 0.2i -\(bu -\fIX\fR - Exclude files and directories. -Causes tar files to be excluded from an extract or create. See -example below. Filename globbing works in one of two ways now. -See \fIr\fR below. -.TP 0.2i -\(bu -\fIb\fR - Blocksize. Must be followed -by a valid (greater than zero) blocksize. Causes tar file to be -written out in blocksize*TBLOCK (usually 512 byte) blocks. -.TP 0.2i -\(bu -\fIg\fR - Incremental. Only back up -files that have the archive bit set. Useful only with the -\fIc\fR flag. -.TP 0.2i -\(bu -\fIq\fR - Quiet. Keeps tar from printing -diagnostics as it works. This is the same as tarmode quiet. -.TP 0.2i -\(bu -\fIr\fR - Regular expression include -or exclude. Uses regular expression matching for -excluding or excluding files if compiled with HAVE_REGEX_H. -However this mode can be very slow. If not compiled with -HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. -.TP 0.2i -\(bu -\fIN\fR - Newer than. Must be followed -by the name of a file whose date is compared against files found -on the share during a create. Only files newer than the file -specified are backed up to the tar file. Useful only with the -\fIc\fR flag. -.TP 0.2i -\(bu -\fIa\fR - Set archive bit. Causes the -archive bit to be reset when a file is backed up. Useful with the -\fIg\fR and \fIc\fR flags. -.RE + +Make certain that the permissions on the file restrict access from unwanted users\&. + + +.TP +-U|--user=username[%password] +Sets the SMB username or username and password\&. + + +If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&. + + +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&. + + +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&. + + +.TP +-n +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&. + + +.TP +-i +This specifies a NetBIOS scope that \fBnmblookup\fR will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&. + + +.TP +-W|--workgroup=domain +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&. + + +.TP +-O socket options +TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&. + + +.TP +-T tar options +smbclient may be used to create \fBtar(1) \fR compatible backups of all the files on an SMB/CIFS share\&. The secondary tar flags that can be given to this option are : + + +\fIc\fR - Create a tar file on UNIX\&. Must be followed by the name of a tar file, tape device or "-" for standard output\&. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file\&. This flag is mutually exclusive with the \fIx\fR flag\&. + +\fIx\fR - Extract (restore) a local tar file back to a share\&. Unless the -D option is given, the tar files will be restored from the top level of the share\&. Must be followed by the name of the tar file, device or "-" for standard input\&. Mutually exclusive with the \fIc\fR flag\&. Restored files have their creation times (mtime) set to the date saved in the tar file\&. Directories currently do not get their creation dates restored properly\&. + +\fII\fR - Include files and directories\&. Is the default behavior when filenames are specified above\&. Causes tar files to be included in an extract or create (and therefore everything else to be excluded)\&. See example below\&. Filename globbing works in one of two ways\&. See r below\&. + +\fIX\fR - Exclude files and directories\&. Causes tar files to be excluded from an extract or create\&. See example below\&. Filename globbing works in one of two ways now\&. See \fIr\fR below\&. + +\fIb\fR - Blocksize\&. Must be followed by a valid (greater than zero) blocksize\&. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks\&. + +\fIg\fR - Incremental\&. Only back up files that have the archive bit set\&. Useful only with the \fIc\fR flag\&. + +\fIq\fR - Quiet\&. Keeps tar from printing diagnostics as it works\&. This is the same as tarmode quiet\&. + +\fIr\fR - Regular expression include or exclude\&. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H\&. However this mode can be very slow\&. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'\&. + +\fIN\fR - Newer than\&. Must be followed by the name of a file whose date is compared against files found on the share during a create\&. Only files newer than the file specified are backed up to the tar file\&. Useful only with the \fIc\fR flag\&. + +\fIa\fR - Set archive bit\&. Causes the archive bit to be reset when a file is backed up\&. Useful with the \fIg\fR and \fIc\fR flags\&. \fBTar Long File Names\fR -\fBsmbclient\fR's tar option now supports long -file names both on backup and restore. However, the full path -name of the file must be less than 1024 bytes. Also, when -a tar archive is created, \fBsmbclient\fR's tar option places all -files in the archive with relative names, not absolute names. + +\fBsmbclient\fR's tar option now supports long file names both on backup and restore\&. However, the full path name of the file must be less than 1024 bytes\&. Also, when a tar archive is created, \fBsmbclient\fR's tar option places all files in the archive with relative names, not absolute names\&. + \fBTar Filenames\fR -All file names can be given as DOS path names (with '\\\\' -as the component separator) or as UNIX path names (with '/' as -the component separator). + +All file names can be given as DOS path names (with '\\\\' as the component separator) or as UNIX path names (with '/' as the component separator)\&. + \fBExamples\fR -Restore from tar file \fIbackup.tar\fR into myshare on mypc -(no password on share). -\fBsmbclient //mypc/yshare "" -N -Tx backup.tar -\fR +Restore from tar file \fIbackup\&.tar\fR into myshare on mypc (no password on share)\&. + + +\fBsmbclient //mypc/yshare "" -N -Tx backup.tar \fR + Restore everything except \fIusers/docs\fR -\fBsmbclient //mypc/myshare "" -N -TXx backup.tar -users/docs\fR -Create a tar file of the files beneath \fI users/docs\fR. +\fBsmbclient //mypc/myshare "" -N -TXx backup.tar users/docs\fR + + +Create a tar file of the files beneath \fI users/docs\fR\&. + + +\fBsmbclient //mypc/myshare "" -N -Tc backup.tar users/docs \fR + + +Create the same tar file as above, but now use a DOS path name\&. + + +\fBsmbclient //mypc/myshare "" -N -tc backup.tar users\edocs \fR + -\fBsmbclient //mypc/myshare "" -N -Tc -backup.tar users/docs \fR +Create a tar file of all the files and directories in the share\&. -Create the same tar file as above, but now use -a DOS path name. -\fBsmbclient //mypc/myshare "" -N -tc backup.tar -users\\edocs \fR +\fBsmbclient //mypc/myshare "" -N -Tc backup.tar * \fR -Create a tar file of all the files and directories in -the share. -\fBsmbclient //mypc/myshare "" -N -Tc backup.tar * -\fR .TP -\fB-D initial directory\fR -Change to initial directory before starting. Probably -only of any use with the tar -T option. +-D initial directory +Change to initial directory before starting\&. Probably only of any use with the tar -T option\&. + + .TP -\fB-c command string\fR -command string is a semicolon-separated list of -commands to be executed instead of prompting from stdin. \fI -N\fR is implied by \fI-c\fR. +-c command string +command string is a semicolon-separated list of commands to be executed instead of prompting from stdin\&. \fI -N\fR is implied by \fI-c\fR\&. + + +This is particularly useful in scripts and for printing stdin to the server, e\&.g\&. \fB-c 'print -'\fR\&. + -This is particularly useful in scripts and for printing stdin -to the server, e.g. \fB-c 'print -'\fR. .SH "OPERATIONS" + .PP -Once the client is running, the user is presented with -a prompt : +Once the client is running, the user is presented with a prompt : + .PP -smb:\\> +smb:\\> + .PP -The backslash ("\\\\") indicates the current working directory -on the server, and will change if the current working directory -is changed. +The backslash ("\\\\") indicates the current working directory on the server, and will change if the current working directory is changed\&. + .PP -The prompt indicates that the client is ready and waiting to -carry out a user command. Each command is a single word, optionally -followed by parameters specific to that command. Command and parameters -are space-delimited unless these notes specifically -state otherwise. All commands are case-insensitive. Parameters to -commands may or may not be case sensitive, depending on the command. +The prompt indicates that the client is ready and waiting to carry out a user command\&. Each command is a single word, optionally followed by parameters specific to that command\&. Command and parameters are space-delimited unless these notes specifically state otherwise\&. All commands are case-insensitive\&. Parameters to commands may or may not be case sensitive, depending on the command\&. + .PP -You can specify file names which have spaces in them by quoting -the name with double quotes, for example "a long file name". +You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name"\&. + .PP -Parameters shown in square brackets (e.g., "[parameter]") are -optional. If not given, the command will use suitable defaults. Parameters -shown in angle brackets (e.g., "") are required. +Parameters shown in square brackets (e\&.g\&., "[parameter]") are optional\&. If not given, the command will use suitable defaults\&. Parameters shown in angle brackets (e\&.g\&., "") are required\&. + .PP -Note that all commands operating on the server are actually -performed by issuing a request to the server. Thus the behavior may -vary from server to server, depending on how the server was implemented. +Note that all commands operating on the server are actually performed by issuing a request to the server\&. Thus the behavior may vary from server to server, depending on how the server was implemented\&. + .PP -The commands available are given here in alphabetical order. -.TP -\fB? [command]\fR -If \fIcommand\fR is specified, the ? command will display -a brief informative message about the specified command. If no -command is specified, a list of available commands will -be displayed. -.TP -\fB! [shell command]\fR -If \fIshell command\fR is specified, the ! -command will execute a shell locally and run the specified shell -command. If no command is specified, a local shell will be run. -.TP -\fBaltname file\fR -The client will request that the server return -the "alternate" name (the 8.3 name) for a file or directory. -.TP -\fBcancel jobid0 [jobid1] ... [jobidN]\fR -The client will request that the server cancel -the printjobs identified by the given numeric print job ids. -.TP -\fBchmod file mode in octal\fR -This command depends on the server supporting the CIFS -UNIX extensions and will fail if the server does not. The client requests that the server -change the UNIX permissions to the given octal mode, in standard UNIX format. -.TP -\fBchown file uid gid\fR -This command depends on the server supporting the CIFS -UNIX extensions and will fail if the server does not. The client requests that the server -change the UNIX user and group ownership to the given decimal values. Note there is -currently no way to remotely look up the UNIX uid and gid values for a given name. -This may be addressed in future versions of the CIFS UNIX extensions. -.TP -\fBcd [directory name]\fR -If "directory name" is specified, the current -working directory on the server will be changed to the directory -specified. This operation will fail if for any reason the specified -directory is inaccessible. - -If no directory name is specified, the current working -directory on the server will be reported. -.TP -\fBdel \fR -The client will request that the server attempt -to delete all files matching \fImask\fR from the current working -directory on the server. -.TP -\fBdir \fR -A list of the files matching \fImask\fR in the current -working directory on the server will be retrieved from the server -and displayed. -.TP -\fBexit\fR -Terminate the connection with the server and exit -from the program. -.TP -\fBget [local file name]\fR -Copy the file called \fIremote file name\fR from -the server to the machine running the client. If specified, name -the local copy \fIlocal file name\fR. Note that all transfers in -\fBsmbclient\fR are binary. See also the -lowercase command. -.TP -\fBhelp [command]\fR -See the ? command above. -.TP -\fBlcd [directory name]\fR -If \fIdirectory name\fR is specified, the current -working directory on the local machine will be changed to -the directory specified. This operation will fail if for any -reason the specified directory is inaccessible. - -If no directory name is specified, the name of the -current working directory on the local machine will be reported. -.TP -\fBlink source destination\fR -This command depends on the server supporting the CIFS -UNIX extensions and will fail if the server does not. The client requests that the server -create a hard link between the source and destination files. The source file -must not exist. -.TP -\fBlowercase\fR -Toggle lowercasing of filenames for the get and -mget commands. - -When lowercasing is toggled ON, local filenames are converted -to lowercase when using the get and mget commands. This is -often useful when copying (say) MSDOS files from a server, because -lowercase filenames are the norm on UNIX systems. -.TP -\fBls \fR -See the dir command above. -.TP -\fBmask \fR -This command allows the user to set up a mask -which will be used during recursive operation of the mget and -mput commands. - -The masks specified to the mget and mput commands act as -filters for directories rather than files when recursion is -toggled ON. - -The mask specified with the mask command is necessary -to filter files within those directories. For example, if the -mask specified in an mget command is "source*" and the mask -specified with the mask command is "*.c" and recursion is -toggled ON, the mget command will retrieve all files matching -"*.c" in all directories below and including all directories -matching "source*" in the current working directory. - -Note that the value for mask defaults to blank (equivalent -to "*") and remains so until the mask command is used to change it. -It retains the most recently specified value indefinitely. To -avoid unexpected results it would be wise to change the value of -mask back to "*" after using the mget or mput commands. -.TP -\fBmd \fR -See the mkdir command. -.TP -\fBmget \fR -Copy all files matching \fImask\fR from the server to -the machine running the client. - -Note that \fImask\fR is interpreted differently during recursive -operation and non-recursive operation - refer to the recurse and -mask commands for more information. Note that all transfers in -\fBsmbclient\fR are binary. See also the lowercase command. -.TP -\fBmkdir \fR -Create a new directory on the server (user access -privileges permitting) with the specified name. -.TP -\fBmput \fR -Copy all files matching \fImask\fR in the current working -directory on the local machine to the current working directory on -the server. - -Note that \fImask\fR is interpreted differently during recursive -operation and non-recursive operation - refer to the recurse and mask -commands for more information. Note that all transfers in \fBsmbclient\fR -are binary. -.TP -\fBprint \fR -Print the specified file from the local machine -through a printable service on the server. - -See also the printmode command. -.TP -\fBprintmode \fR -Set the print mode to suit either binary data -(such as graphical information) or text. Subsequent print -commands will use the currently set print mode. -.TP -\fBprompt\fR -Toggle prompting for filenames during operation -of the mget and mput commands. - -When toggled ON, the user will be prompted to confirm -the transfer of each file during these commands. When toggled -OFF, all specified files will be transferred without prompting. -.TP -\fBput [remote file name]\fR -Copy the file called \fIlocal file name\fR from the -machine running the client to the server. If specified, -name the remote copy \fIremote file name\fR. Note that all transfers -in \fBsmbclient\fR are binary. See also the lowercase command. -.TP -\fBqueue\fR -Displays the print queue, showing the job id, -name, size and current status. -.TP -\fBquit\fR -See the exit command. -.TP -\fBrd \fR -See the rmdir command. -.TP -\fBrecurse\fR -Toggle directory recursion for the commands mget -and mput. - -When toggled ON, these commands will process all directories -in the source directory (i.e., the directory they are copying -from ) and will recurse into any that match the mask specified -to the command. Only files that match the mask specified using -the mask command will be retrieved. See also the mask command. - -When recursion is toggled OFF, only files from the current -working directory on the source machine that match the mask specified -to the mget or mput commands will be copied, and any mask specified -using the mask command will be ignored. -.TP -\fBrm \fR -Remove all files matching \fImask\fR from the current -working directory on the server. -.TP -\fBrmdir \fR -Remove the specified directory (user access -privileges permitting) from the server. -.TP -\fBsetmode \fR -A version of the DOS attrib command to set -file permissions. For example: +The commands available are given here in alphabetical order\&. + +.TP +? [command] +If \fIcommand\fR is specified, the ? command will display a brief informative message about the specified command\&. If no command is specified, a list of available commands will be displayed\&. + + +.TP +! [shell command] +If \fIshell command\fR is specified, the ! command will execute a shell locally and run the specified shell command\&. If no command is specified, a local shell will be run\&. + + +.TP +altname file +The client will request that the server return the "alternate" name (the 8\&.3 name) for a file or directory\&. + + +.TP +cancel jobid0 [jobid1] \&.\&.\&. [jobidN] +The client will request that the server cancel the printjobs identified by the given numeric print job ids\&. + + +.TP +chmod file mode in octal +This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server change the UNIX permissions to the given octal mode, in standard UNIX format\&. + + +.TP +chown file uid gid +This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server change the UNIX user and group ownership to the given decimal values\&. Note there is currently no way to remotely look up the UNIX uid and gid values for a given name\&. This may be addressed in future versions of the CIFS UNIX extensions\&. + + +.TP +cd [directory name] +If "directory name" is specified, the current working directory on the server will be changed to the directory specified\&. This operation will fail if for any reason the specified directory is inaccessible\&. + + +If no directory name is specified, the current working directory on the server will be reported\&. + + +.TP +del +The client will request that the server attempt to delete all files matching \fImask\fR from the current working directory on the server\&. + + +.TP +dir +A list of the files matching \fImask\fR in the current working directory on the server will be retrieved from the server and displayed\&. + + +.TP +exit +Terminate the connection with the server and exit from the program\&. + + +.TP +get [local file name] +Copy the file called \fIremote file name\fR from the server to the machine running the client\&. If specified, name the local copy \fIlocal file name\fR\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&. + + +.TP +help [command] +See the ? command above\&. + + +.TP +lcd [directory name] +If \fIdirectory name\fR is specified, the current working directory on the local machine will be changed to the directory specified\&. This operation will fail if for any reason the specified directory is inaccessible\&. + + +If no directory name is specified, the name of the current working directory on the local machine will be reported\&. + + +.TP +link source destination +This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server create a hard link between the source and destination files\&. The source file must not exist\&. + + +.TP +lowercase +Toggle lowercasing of filenames for the get and mget commands\&. + + +When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands\&. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems\&. + + +.TP +ls +See the dir command above\&. + + +.TP +mask +This command allows the user to set up a mask which will be used during recursive operation of the mget and mput commands\&. + + +The masks specified to the mget and mput commands act as filters for directories rather than files when recursion is toggled ON\&. + + +The mask specified with the mask command is necessary to filter files within those directories\&. For example, if the mask specified in an mget command is "source*" and the mask specified with the mask command is "*\&.c" and recursion is toggled ON, the mget command will retrieve all files matching "*\&.c" in all directories below and including all directories matching "source*" in the current working directory\&. + + +Note that the value for mask defaults to blank (equivalent to "*") and remains so until the mask command is used to change it\&. It retains the most recently specified value indefinitely\&. To avoid unexpected results it would be wise to change the value of mask back to "*" after using the mget or mput commands\&. + + +.TP +md +See the mkdir command\&. + + +.TP +mget +Copy all files matching \fImask\fR from the server to the machine running the client\&. + + +Note that \fImask\fR is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&. + + +.TP +mkdir +Create a new directory on the server (user access privileges permitting) with the specified name\&. + + +.TP +mput +Copy all files matching \fImask\fR in the current working directory on the local machine to the current working directory on the server\&. + + +Note that \fImask\fR is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information\&. Note that all transfers in \fBsmbclient\fR are binary\&. + + +.TP +print +Print the specified file from the local machine through a printable service on the server\&. + + +See also the printmode command\&. + + +.TP +printmode +Set the print mode to suit either binary data (such as graphical information) or text\&. Subsequent print commands will use the currently set print mode\&. + + +.TP +prompt +Toggle prompting for filenames during operation of the mget and mput commands\&. + + +When toggled ON, the user will be prompted to confirm the transfer of each file during these commands\&. When toggled OFF, all specified files will be transferred without prompting\&. + + +.TP +put [remote file name] +Copy the file called \fIlocal file name\fR from the machine running the client to the server\&. If specified, name the remote copy \fIremote file name\fR\&. Note that all transfers in \fBsmbclient\fR are binary\&. See also the lowercase command\&. + + +.TP +queue +Displays the print queue, showing the job id, name, size and current status\&. + + +.TP +quit +See the exit command\&. + + +.TP +rd +See the rmdir command\&. + + +.TP +recurse +Toggle directory recursion for the commands mget and mput\&. + + +When toggled ON, these commands will process all directories in the source directory (i\&.e\&., the directory they are copying from ) and will recurse into any that match the mask specified to the command\&. Only files that match the mask specified using the mask command will be retrieved\&. See also the mask command\&. + + +When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mget or mput commands will be copied, and any mask specified using the mask command will be ignored\&. + + +.TP +rm +Remove all files matching \fImask\fR from the current working directory on the server\&. + + +.TP +rmdir +Remove the specified directory (user access privileges permitting) from the server\&. + + +.TP +setmode +A version of the DOS attrib command to set file permissions\&. For example: + \fBsetmode myfile +r \fR -would make myfile read only. -.TP -\fBsymlink source destination\fR -This command depends on the server supporting the CIFS -UNIX extensions and will fail if the server does not. The client requests that the server -create a symbolic hard link between the source and destination files. The source file -must not exist. Note that the server will not create a link to any path that lies -outside the currently connected share. This is enforced by the Samba server. -.TP -\fBtar [IXbgNa]\fR -Performs a tar operation - see the \fI-T -\fR command line option above. Behavior may be affected -by the tarmode command (see below). Using g (incremental) and N -(newer) will affect tarmode settings. Note that using the "-" option -with tar x may not work - use the command line option instead. -.TP -\fBblocksize \fR -Blocksize. Must be followed by a valid (greater -than zero) blocksize. Causes tar file to be written out in -\fIblocksize\fR*TBLOCK (usually 512 byte) blocks. -.TP -\fBtarmode \fR -Changes tar's behavior with regard to archive -bits. In full mode, tar will back up everything regardless of the -archive bit setting (this is the default mode). In incremental mode, -tar will only back up files with the archive bit set. In reset mode, -tar will reset the archive bit on all files it backs up (implies -read/write share). + +would make myfile read only\&. + + +.TP +symlink source destination +This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\&. The client requests that the server create a symbolic hard link between the source and destination files\&. The source file must not exist\&. Note that the server will not create a link to any path that lies outside the currently connected share\&. This is enforced by the Samba server\&. + + +.TP +tar [IXbgNa] +Performs a tar operation - see the \fI-T \fR command line option above\&. Behavior may be affected by the tarmode command (see below)\&. Using g (incremental) and N (newer) will affect tarmode settings\&. Note that using the "-" option with tar x may not work - use the command line option instead\&. + + +.TP +blocksize +Blocksize\&. Must be followed by a valid (greater than zero) blocksize\&. Causes tar file to be written out in \fIblocksize\fR*TBLOCK (usually 512 byte) blocks\&. + + +.TP +tarmode +Changes tar's behavior with regard to archive bits\&. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode)\&. In incremental mode, tar will only back up files with the archive bit set\&. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share)\&. + + .SH "NOTES" + .PP -Some servers are fussy about the case of supplied usernames, -passwords, share names (AKA service names) and machine names. -If you fail to connect try giving all parameters in uppercase. +Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names\&. If you fail to connect try giving all parameters in uppercase\&. + .PP -It is often necessary to use the -n option when connecting -to some types of servers. For example OS/2 LanManager insists -on a valid NetBIOS name being used, so you need to supply a valid -name that would be known to the server. +It is often necessary to use the -n option when connecting to some types of servers\&. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server\&. + .PP -smbclient supports long file names where the server -supports the LANMAN2 protocol or above. +smbclient supports long file names where the server supports the LANMAN2 protocol or above\&. + .SH "ENVIRONMENT VARIABLES" + .PP -The variable \fBUSER\fR may contain the -username of the person using the client. This information is -used only if the protocol level is high enough to support -session-level passwords. +The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. + .PP -The variable \fBPASSWD\fR may contain -the password of the person using the client. This information is -used only if the protocol level is high enough to support -session-level passwords. +The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. + .PP -The variable \fBLIBSMB_PROG\fR may contain -the path, executed with system(), which the client should connect -to instead of connecting to a server. This functionality is primarily -intended as a development aid, and works best when using a LMHOSTS -file +The variable \fBLIBSMB_PROG\fR may contain the path, executed with system(), which the client should connect to instead of connecting to a server\&. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS file + .SH "INSTALLATION" + .PP -The location of the client program is a matter for -individual system administrators. The following are thus -suggestions only. +The location of the client program is a matter for individual system administrators\&. The following are thus suggestions only\&. + .PP -It is recommended that the smbclient software be installed -in the \fI/usr/local/samba/bin/\fR or \fI /usr/samba/bin/\fR directory, this directory readable -by all, writeable only by root. The client program itself should -be executable by all. The client should \fBNOT\fR be -setuid or setgid! +It is recommended that the smbclient software be installed in the \fI/usr/local/samba/bin/\fR or \fI /usr/samba/bin/\fR directory, this directory readable by all, writeable only by root\&. The client program itself should be executable by all\&. The client should \fBNOT\fR be setuid or setgid! + .PP -The client log files should be put in a directory readable -and writeable only by the user. +The client log files should be put in a directory readable and writeable only by the user\&. + .PP -To test the client, you will need to know the name of a -running SMB/CIFS server. It is possible to run \fBsmbd\fR(8) as an ordinary user - running that server as a daemon -on a user-accessible port (typically any port number over 1024) -would provide a suitable test server. +To test the client, you will need to know the name of a running SMB/CIFS server\&. It is possible to run \fBsmbd\fR(8) as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server\&. + .SH "DIAGNOSTICS" + .PP -Most diagnostics issued by the client are logged in a -specified log file. The log file name is specified at compile time, -but may be overridden on the command line. +Most diagnostics issued by the client are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&. + .PP -The number and nature of diagnostics available depends -on the debug level used by the client. If you have problems, -set the debug level to 3 and peruse the log files. +The number and nature of diagnostics available depends on the debug level used by the client\&. If you have problems, set the debug level to 3 and peruse the log files\&. + .SH "VERSION" + .PP -This man page is correct for version 2.2 of the Samba suite. +This man page is correct for version 2\&.2 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 -was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbcontrol.1 b/docs/manpages/smbcontrol.1 index f865a6365f..44d419f919 100644 --- a/docs/manpages/smbcontrol.1 +++ b/docs/manpages/smbcontrol.1 @@ -1,189 +1,216 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBCONTROL" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBCONTROL" 1 "" "" "" .SH NAME smbcontrol \- send messages to smbd, nmbd or winbindd processes -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbcontrol\fR [ \fB-i\fR ] [ \fB-s\fR ] +.nf +\fBsmbcontrol\fR [-i] [-s] +.fi - -\fBsmbcontrol\fR [ \fBdestination\fR ] [ \fBmessage-type\fR ] [ \fBparameter\fR ] +.nf +\fBsmbcontrol\fR [destination] [message-type] [parameter] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbcontrol\fR is a very small program, which -sends messages to a \fBsmbd\fR(8), a \fBnmbd\fR(8), or a \fBwinbindd\fR(8) daemon running on the system. +\fBsmbcontrol\fR is a very small program, which sends messages to a \fBsmbd\fR(8), a \fBnmbd\fR(8), or a \fBwinbindd\fR(8) daemon running on the system\&. + .SH "OPTIONS" + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-i\fR -Run interactively. Individual commands -of the form destination message-type parameters can be entered -on STDIN. An empty command line or a "q" will quit the -program. +-i +Run interactively\&. Individual commands of the form destination message-type parameters can be entered on STDIN\&. An empty command line or a "q" will quit the program\&. + + .TP -\fBdestination\fR -One of \fInmbd\fR, \fIsmbd\fR or a process ID. +destination +One of \fInmbd\fR, \fIsmbd\fR or a process ID\&. + + +The \fIsmbd\fR destination causes the message to "broadcast" to all smbd daemons\&. + -The \fIsmbd\fR destination causes the -message to "broadcast" to all smbd daemons. +The \fInmbd\fR destination causes the message to be sent to the nmbd daemon specified in the \fInmbd\&.pid\fR file\&. + + +If a single process ID is given, the message is sent to only that process\&. -The \fInmbd\fR destination causes the -message to be sent to the nmbd daemon specified in the -\fInmbd.pid\fR file. -If a single process ID is given, the message is sent -to only that process. .TP -\fBmessage-type\fR -Type of message to send. See -the section MESSAGE-TYPES for details. +message-type +Type of message to send\&. See the section \fBMESSAGE-TYPES\fR for details\&. + + .TP -\fBparameters\fR +parameters any parameters required for the message-type + + .SH "MESSAGE-TYPES" + .PP Available message types are: + +.TP +close-share +Order smbd to close the client connections to the named share\&. Note that this doesn't affect client connections to any other shares\&. This message-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares\&. This may be useful if you made changes to the access controls on the share\&. This message can only be sent to \fBsmbd\fR\&. + + +.TP +debug +Set debug level to the value specified by the parameter\&. This can be sent to any of the destinations\&. + + +.TP +force-election +This message causes the \fBnmbd\fR daemon to force a new browse master election\&. + + +.TP +ping +Send specified number of "ping" messages and wait for the same number of reply "pong" messages\&. This can be sent to any of the destinations\&. + + +.TP +profile +Change profile settings of a daemon, based on the parameter\&. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats\&. This can be sent to any smbd or nmbd destinations\&. + + +.TP +debuglevel +Request debuglevel of a certain daemon and write it to stdout\&. This can be sent to any of the destinations\&. + + .TP -\fBclose-share\fR -Order smbd to close the client -connections to the named share. Note that this doesn't affect client -connections to any other shares. This message-type takes an argument of the -share name for which client connections will be closed, or the -"*" character which will close all currently open shares. -This may be useful if you made changes to the access controls on the share. -This message can only be sent to smbd. -.TP -\fBdebug\fR -Set debug level to the value specified by the -parameter. This can be sent to any of the destinations. -.TP -\fBforce-election\fR -This message causes the \fBnmbd\fR daemon to -force a new browse master election. -.TP -\fBping\fR -Send specified number of "ping" messages and -wait for the same number of reply "pong" messages. This can be sent to -any of the destinations. -.TP -\fBprofile\fR -Change profile settings of a daemon, based on the -parameter. The parameter can be "on" to turn on profile stats -collection, "off" to turn off profile stats collection, "count" -to enable only collection of count stats (time stats are -disabled), and "flush" to zero the current profile stats. This can -be sent to any smbd or nmbd destinations. -.TP -\fBdebuglevel\fR -Request debuglevel of a certain daemon and write it to stdout. This -can be sent to any of the destinations. -.TP -\fBprofilelevel\fR -Request profilelevel of a certain daemon and write it to stdout. -This can be sent to any smbd or nmbd destinations. -.TP -\fBprintnotify\fR -Order smbd to send a printer notify message to any Windows NT clients -connected to a printer. This message-type takes the following arguments: +profilelevel +Request profilelevel of a certain daemon and write it to stdout\&. This can be sent to any smbd or nmbd destinations\&. + + +.TP +printnotify +Order smbd to send a printer notify message to any Windows NT clients connected to a printer\&. This message-type takes the following arguments: + + + .RS + .TP -\fBqueuepause printername\fR -Send a queue pause change notify -message to the printer specified. +queuepause printername +Send a queue pause change notify message to the printer specified\&. + + .TP -\fBqueueresume printername\fR -Send a queue resume change notify -message for the printer specified. +queueresume printername +Send a queue resume change notify message for the printer specified\&. + + .TP -\fBjobpause printername unixjobid\fR -Send a job pause change notify -message for the printer and unix jobid -specified. +jobpause printername unixjobid +Send a job pause change notify message for the printer and unix jobid specified\&. + + .TP -\fBjobresume printername unixjobid\fR -Send a job resume change notify -message for the printer and unix jobid -specified. +jobresume printername unixjobid +Send a job resume change notify message for the printer and unix jobid specified\&. + + .TP -\fBjobdelete printername unixjobid\fR -Send a job delete change notify -message for the printer and unix jobid -specified. +jobdelete printername unixjobid +Send a job delete change notify message for the printer and unix jobid specified\&. + + .RE +Note that this message only sends notification that an event has occured\&. It doesn't actually cause the event to happen\&. + + +This message can only be sent to \fBsmbd\fR\&. -Note that this message only sends notification that an -event has occured. It doesn't actually cause the -event to happen. -This message can only be sent to smbd. .TP -\fBsamsync\fR -Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd. -.sp -.RS -.B "Note:" +samsync +Order smbd to synchronise sam database from PDC (being BDC)\&. Can only be sent to \fBsmbd\fR\&. + Not working at the moment -.RE + + .TP -\fBsamrepl\fR -Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually. +samrepl +Send sam replication message, with specified serial\&. Can only be sent to \fBsmbd\fR\&. Should not be used manually\&. + + .TP -\fBdmalloc-mark\fR -Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. +dmalloc-mark +Set a mark for dmalloc\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&. + + .TP -\fBdmalloc-log-changed\fR -Dump the pointers that have changed since the mark set by dmalloc-mark. -Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. +dmalloc-log-changed +Dump the pointers that have changed since the mark set by dmalloc-mark\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&. + + .TP -\fBshutdown\fR -Shut down specified daemon. Can be sent to both smbd and nmbd. +shutdown +Shut down specified daemon\&. Can be sent to both smbd and nmbd\&. + + .TP -\fBpool-usage\fR -Print a human-readable description of all -talloc(pool) memory usage by the specified daemon/process. Available -for both smbd and nmbd. +pool-usage +Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process\&. Available for both smbd and nmbd\&. + + .TP -\fBdrvupgrade\fR -Force clients of printers using specified driver -to update their local version of the driver. Can only be -sent to smbd. +drvupgrade +Force clients of printers using specified driver to update their local version of the driver\&. Can only be sent to smbd\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBnmbd\fR(8) and \fBsmbd\fR(8). +\fBnmbd\fR(8) and \fBsmbd\fR(8)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for -Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbcquotas.1 b/docs/manpages/smbcquotas.1 index a06895656a..e8288977f8 100644 --- a/docs/manpages/smbcquotas.1 +++ b/docs/manpages/smbcquotas.1 @@ -1,183 +1,199 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBCQUOTAS" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBCQUOTAS" 1 "" "" "" .SH NAME smbcquotas \- Set or get QUOTAs of NTFS 5 shares -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbcquotas\fR \fB//server/share\fR [ \fB-u user\fR ] [ \fB-L\fR ] [ \fB-F\fR ] [ \fB-S QUOTA_SET_COMMAND\fR ] [ \fB-n\fR ] [ \fB-t\fR ] [ \fB-v\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-l logfilebase\fR ] [ \fB-V\fR ] [ \fB-U username\fR ] [ \fB-N\fR ] [ \fB-k\fR ] [ \fB-A\fR ] +.nf +\fBsmbcquotas\fR {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] + [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] + [-N] [-k] [-A] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The \fBsmbcquotas\fR program manipulates NT Quotas on SMB file shares. +The \fBsmbcquotas\fR program manipulates NT Quotas on SMB file shares\&. + .SH "OPTIONS" + .PP -The following options are available to the \fBsmbcquotas\fR program. -.TP -\fB-u user\fR -Specifies the user of whom the quotas are get or set. -By default the current user's username will be used. -.TP -\fB-L\fR -Lists all quota records of the share. -.TP -\fB-F\fR -Show the share quota status and default limits. -.TP -\fB-S QUOTA_SET_COMMAND\fR -This command set/modify quotas for a user or on the share, -depending on the QUOTA_SET_COMMAND parameter witch is described later -.TP -\fB-n\fR -This option displays all QUOTA information in numeric -format. The default is to convert SIDs to names and QUOTA limits -to a readable string format. -.TP -\fB-t\fR -Don't actually do anything, only validate the correctness of -the arguments. -.TP -\fB-v\fR -Be verbose. -.TP -\fB-h|--help\fR -Print a summary of command line options. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. -.TP -\fB-N\fR -If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. - -Unless a password is specified on the command line or -this parameter is specified, the client will request a -password. -.TP -\fB-k\fR -Try to authenticate with kerberos. Only useful in -an Active Directory environment. -.TP -\fB-A|--authfile=filename\fR -This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is +The following options are available to the \fBsmbcquotas\fR program\&. + +.TP +-u user +Specifies the user of whom the quotas are get or set\&. By default the current user's username will be used\&. + + +.TP +-L +Lists all quota records of the share\&. + + +.TP +-F +Show the share quota status and default limits\&. + + +.TP +-S QUOTA_SET_COMMAND +This command set/modify quotas for a user or on the share, depending on the QUOTA_SET_COMMAND parameter witch is described later + + +.TP +-n +This option displays all QUOTA information in numeric format\&. The default is to convert SIDs to names and QUOTA limits to a readable string format\&. + + +.TP +-t +Don't actually do anything, only validate the correctness of the arguments\&. + + +.TP +-v +Be verbose\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + +.TP +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + +.TP +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + +.TP +-N +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&. + + +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&. + + +.TP +-k +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&. + + +.TP +-A|--authfile=filename +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is .nf + username = password = domain = .fi -Make certain that the permissions on the file restrict -access from unwanted users. -.TP -\fB-U|--user=username[%password]\fR -Sets the SMB username or username and password. - -If %password is not specified, the user will be prompted. The -client will first check the \fBUSER\fR environment variable, then the -\fBLOGNAME\fR variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username GUEST is used. - -A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -\fI-A\fR for more details. - -Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the \fBps\fR command. To be safe always allow -\fBrpcclient\fR to prompt for a password and type -it in directly. + +Make certain that the permissions on the file restrict access from unwanted users\&. + + +.TP +-U|--user=username[%password] +Sets the SMB username or username and password\&. + + +If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&. + + +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&. + + +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&. + + .SH "QUOTA_SET_COMAND" + .PP -The format of an ACL is one or more ACL entries separated by -either commas or newlines. An ACL entry is one of the following: +The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following: + .PP for user setting quotas for the specified by -u or the current username: + .PP -\fB UQLIM: -\fR +\fB UQLIM: \fR + .PP for setting the share quota defaults limits: + .PP -\fB FSQLIM: -\fR +\fB FSQLIM: \fR + .PP for changing the share quota settings: + .PP -\fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT -\fR +\fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT \fR + .SH "EXIT STATUS" + .PP -The \fBsmbcquotas\fR program sets the exit status -depending on the success or otherwise of the operations performed. -The exit status may be one of the following values. +The \fBsmbcquotas\fR program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&. + .PP -If the operation succeeded, smbcquotas returns an exit -status of 0. If \fBsmbcquotas\fR couldn't connect to the specified server, -or when there was an error getting or setting the quota(s), an exit status -of 1 is returned. If there was an error parsing any command line -arguments, an exit status of 2 is returned. +If the operation succeeded, smbcquotas returns an exit status of 0\&. If \fBsmbcquotas\fR couldn't connect to the specified server, or when there was an error getting or setting the quota(s), an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -\fBsmbcacls\fR was written by Stefan Metzmacher. +\fBsmbcacls\fR was written by Stefan Metzmacher\&. + diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8 index 17fd179d39..c7c0fac777 100644 --- a/docs/manpages/smbd.8 +++ b/docs/manpages/smbd.8 @@ -1,306 +1,230 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBD" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBD" 8 "" "" "" .SH NAME smbd \- server to provide SMB/CIFS services to clients -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-i\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-b\fR ] [ \fB-d \fR ] [ \fB-l \fR ] [ \fB-p \fR ] [ \fB-O \fR ] [ \fB-s \fR ] +.nf +\fBsmbd\fR [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d ] [-l ] + [-p ] [-O ] [-s ] +.fi .SH "DESCRIPTION" + .PP -This program is part of the \fBSamba\fR(7) suite. +This program is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbd\fR is the server daemon that -provides filesharing and printing services to Windows clients. -The server provides filespace and printer services to -clients using the SMB (or CIFS) protocol. This is compatible -with the LanManager protocol, and can service LanManager -clients. These include MSCLIENT 3.0 for DOS, Windows for -Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, -OS/2, DAVE for Macintosh, and smbfs for Linux. +\fBsmbd\fR is the server daemon that provides filesharing and printing services to Windows clients\&. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\&. This is compatible with the LanManager protocol, and can service LanManager clients\&. These include MSCLIENT 3\&.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\&. + .PP -An extensive description of the services that the -server can provide is given in the man page for the -configuration file controlling the attributes of those -services (see \fBsmb.conf\fR(5). This man page will not describe the -services, but will concentrate on the administrative aspects -of running the server. +An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see \fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&. + .PP -Please note that there are significant security -implications to running this server, and the \fBsmb.conf\fR(5) manual page should be regarded as mandatory reading before -proceeding with installation. +Please note that there are significant security implications to running this server, and the \fBsmb.conf\fR(5) manual page should be regarded as mandatory reading before proceeding with installation\&. + .PP -A session is created whenever a client requests one. -Each client gets a copy of the server for each session. This -copy then services all connections made by the client during -that session. When all connections from its client are closed, -the copy of the server for that client terminates. +A session is created whenever a client requests one\&. Each client gets a copy of the server for each session\&. This copy then services all connections made by the client during that session\&. When all connections from its client are closed, the copy of the server for that client terminates\&. + .PP -The configuration file, and any files that it includes, -are automatically reloaded every minute, if they change. You -can force a reload by sending a SIGHUP to the server. Reloading -the configuration file will not affect connections to any service -that is already established. Either the user will have to -disconnect from the service, or \fBsmbd\fR killed and restarted. +The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\&. You can force a reload by sending a SIGHUP to the server\&. Reloading the configuration file will not affect connections to any service that is already established\&. Either the user will have to disconnect from the service, or \fBsmbd\fR killed and restarted\&. + .SH "OPTIONS" + .TP -\fB-D\fR -If specified, this parameter causes -the server to operate as a daemon. That is, it detaches -itself and runs in the background, fielding requests -on the appropriate port. Operating the server as a -daemon is the recommended way of running \fBsmbd\fR for -servers that provide more than casual use file and -print services. This switch is assumed if \fBsmbd -\fR is executed on the command line of a shell. +-D +If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. Operating the server as a daemon is the recommended way of running \fBsmbd\fR for servers that provide more than casual use file and print services\&. This switch is assumed if \fBsmbd \fR is executed on the command line of a shell\&. + + .TP -\fB-F\fR -If specified, this parameter causes -the main \fBsmbd\fR process to not daemonize, -i.e. double-fork and disassociate with the terminal. -Child processes are still created as normal to service -each connection request, but the main process does not -exit. This operation mode is suitable for running -\fBsmbd\fR under process supervisors such -as \fBsupervise\fR and \fBsvscan\fR -from Daniel J. Bernstein's \fBdaemontools\fR -package, or the AIX process monitor. +-F +If specified, this parameter causes the main \fBsmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBsmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&. + + .TP -\fB-S\fR -If specified, this parameter causes -\fBsmbd\fR to log to standard output rather -than a file. +-S +If specified, this parameter causes \fBsmbd\fR to log to standard output rather than a file\&. + + .TP -\fB-i\fR -If this parameter is specified it causes the -server to run "interactively", not as a daemon, even if the -server is executed on the command line of a shell. Setting this -parameter negates the implicit deamon mode when run from the -command line. \fBsmbd\fR also logs to standard -output, as if the \fB-S\fR parameter had been -given. +-i +If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit deamon mode when run from the command line\&. \fBsmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-b\fR -Prints information about how -Samba was built. +-b +Prints information about how Samba was built\&. + + .TP -\fB-l \fR -If specified, -\fIlog directory\fR -specifies a log directory into which the "log.smbd" log -file will be created for informational and debug -messages from the running server. The log -file generated is never removed by the server although -its size may be controlled by the \fImax log size\fR -option in the \fBsmb.conf\fR(5) file. \fBBeware:\fR -If the directory specified does not exist, \fBsmbd\fR -will log to the default debug log location defined at compile time. - -The default log directory is specified at -compile time. +-l +If specified, \fIlog directory\fR specifies a log directory into which the "log\&.smbd" log file will be created for informational and debug messages from the running server\&. The log file generated is never removed by the server although its size may be controlled by the \fImax log size\fR option in the \fBsmb.conf\fR(5) file\&. \fBBeware:\fR If the directory specified does not exist, \fBsmbd\fR will log to the default debug log location defined at compile time\&. + + +The default log directory is specified at compile time\&. + + .TP -\fB-p \fR -\fIport number\fR is a positive integer -value. The default value if this parameter is not -specified is 139. - -This number is the port number that will be -used when making connections to the server from client -software. The standard (well-known) port number for the -SMB over TCP is 139, hence the default. If you wish to -run the server as an ordinary user rather than -as root, most systems will require you to use a port -number greater than 1024 - ask your system administrator -for help if you are in this situation. - -In order for the server to be useful by most -clients, should you configure it on a port other -than 139, you will require port redirection services -on port 139, details of which are outlined in rfc1002.txt -section 4.3.5. - -This parameter is not normally specified except -in the above situation. +-p +\fIport number\fR is a positive integer value\&. The default value if this parameter is not specified is 139\&. + + +This number is the port number that will be used when making connections to the server from client software\&. The standard (well-known) port number for the SMB over TCP is 139, hence the default\&. If you wish to run the server as an ordinary user rather than as root, most systems will require you to use a port number greater than 1024 - ask your system administrator for help if you are in this situation\&. + + +In order for the server to be useful by most clients, should you configure it on a port other than 139, you will require port redirection services on port 139, details of which are outlined in rfc1002\&.txt section 4\&.3\&.5\&. + + +This parameter is not normally specified except in the above situation\&. + + .SH "FILES" + .TP -\fB\fI/etc/inetd.conf\fB\fR -If the server is to be run by the -\fBinetd\fR meta-daemon, this file -must contain suitable startup information for the -meta-daemon. See the "How to Install and Test SAMBA" -document for details. +\fI/etc/inetd\&.conf\fR +If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the "How to Install and Test SAMBA" document for details\&. + + .TP -\fB\fI/etc/rc\fB\fR -or whatever initialization script your -system uses). - -If running the server as a daemon at startup, -this file will need to contain an appropriate startup -sequence for the server. See the "How to Install and Test SAMBA" -document for details. +\fI/etc/rc\fR +or whatever initialization script your system uses)\&. + + +If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&. + + .TP -\fB\fI/etc/services\fB\fR -If running the server via the -meta-daemon \fBinetd\fR, this file -must contain a mapping of service name (e.g., netbios-ssn) -to service port (e.g., 139) and protocol type (e.g., tcp). -See the "How to Install and Test SAMBA" -document for details. +\fI/etc/services\fR +If running the server via the meta-daemon \fBinetd\fR, this file must contain a mapping of service name (e\&.g\&., netbios-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&. See the "How to Install and Test SAMBA" document for details\&. + + .TP -\fB\fI/usr/local/samba/lib/smb.conf\fB\fR -This is the default location of the \fBsmb.conf\fR(5) server configuration file. Other common places that systems -install this file are \fI/usr/samba/lib/smb.conf\fR -and \fI/etc/samba/smb.conf\fR. +\fI/usr/local/samba/lib/smb\&.conf\fR +This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&. + + +This file describes all the services the server is to make available to clients\&. See \fBsmb.conf\fR(5) for more information\&. + -This file describes all the services the server -is to make available to clients. See \fBsmb.conf\fR(5) for more information. .SH "LIMITATIONS" + .PP -On some systems \fBsmbd\fR cannot change uid back -to root after a setuid() call. Such systems are called -trapdoor uid systems. If you have such a system, -you will be unable to connect from a client (such as a PC) as -two different users at once. Attempts to connect the -second user will result in access denied or -similar. +On some systems \fBsmbd\fR cannot change uid back to root after a setuid() call\&. Such systems are called trapdoor uid systems\&. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\&. Attempts to connect the second user will result in access denied or similar\&. + .SH "ENVIRONMENT VARIABLES" + .TP \fBPRINTER\fR -If no printer name is specified to -printable services, most systems will use the value of -this variable (or lp if this variable is -not defined) as the name of the printer to use. This -is not specific to the server, however. +If no printer name is specified to printable services, most systems will use the value of this variable (or \fBlp\fR if this variable is not defined) as the name of the printer to use\&. This is not specific to the server, however\&. + + .SH "PAM INTERACTION" + .PP -Samba uses PAM for authentication (when presented with a plaintext -password), for account checking (is this account disabled?) and for -session management. The degree too which samba supports PAM is restricted -by the limitations of the SMB protocol and the \fIobey -pam restricions\fR \fBsmb.conf\fR(5) paramater. When this is set, the following restrictions apply: -.TP 0.2i +Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\&. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the \fIobey pam restricions\fR \fBsmb.conf\fR(5) paramater\&. When this is set, the following restrictions apply: + +.TP 3 \(bu -\fBAccount Validation\fR: All accesses to a -samba server are checked -against PAM to see if the account is vaild, not disabled and is permitted to -login at this time. This also applies to encrypted logins. -.TP 0.2i +\fBAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\&. This also applies to encrypted logins\&. + +.TP \(bu -\fBSession Management\fR: When not using share -level secuirty, users must pass PAM's session checks before access -is granted. Note however, that this is bypassed in share level secuirty. -Note also that some older pam configuration files may need a line -added for session support. +\fBSession Management\fR: When not using share level secuirty, users must pass PAM's session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&. + +.LP + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "DIAGNOSTICS" + .PP -Most diagnostics issued by the server are logged -in a specified log file. The log file name is specified -at compile time, but may be overridden on the command line. +Most diagnostics issued by the server are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&. + .PP -The number and nature of diagnostics available depends -on the debug level used by the server. If you have problems, set -the debug level to 3 and peruse the log files. +The number and nature of diagnostics available depends on the debug level used by the server\&. If you have problems, set the debug level to 3 and peruse the log files\&. + .PP -Most messages are reasonably self-explanatory. Unfortunately, -at the time this man page was created, there are too many diagnostics -available in the source code to warrant describing each and every -diagnostic. At this stage your best bet is still to grep the -source code and inspect the conditions that gave rise to the -diagnostics you are seeing. +Most messages are reasonably self-explanatory\&. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\&. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\&. + .SH "SIGNALS" + .PP -Sending the \fBsmbd\fR a SIGHUP will cause it to -reload its \fIsmb.conf\fR configuration -file within a short period of time. +Sending the \fBsmbd\fR a SIGHUP will cause it to reload its \fIsmb\&.conf\fR configuration file within a short period of time\&. + .PP -To shut down a user's \fBsmbd\fR process it is recommended -that \fBSIGKILL (-9)\fR \fBNOT\fR -be used, except as a last resort, as this may leave the shared -memory area in an inconsistent state. The safe way to terminate -an \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for -it to die on its own. +To shut down a user's \fBsmbd\fR process it is recommended that \fBSIGKILL (-9)\fR \fBNOT\fR be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\&. The safe way to terminate an \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&. + .PP -The debug log level of \fBsmbd\fR may be raised -or lowered using \fBsmbcontrol\fR(1) program (SIGUSR[1|2] signals are no longer -used since Samba 2.2). This is to allow transient problems to be diagnosed, -whilst still running at a normally low log level. +The debug log level of \fBsmbd\fR may be raised or lowered using \fBsmbcontrol\fR(1) program (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&. + .PP -Note that as the signal handlers send a debug write, -they are not re-entrant in \fBsmbd\fR. This you should wait until -\fBsmbd\fR is in a state of waiting for an incoming SMB before -issuing them. It is possible to make the signal handlers safe -by un-blocking the signals before the select call and re-blocking -them after, however this would affect performance. +Note that as the signal handlers send a debug write, they are not re-entrant in \fBsmbd\fR\&. This you should wait until\fBsmbd\fR is in a state of waiting for an incoming SMB before issuing them\&. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance\&. + .SH "SEE ALSO" + .PP -\fBhosts_access\fR(5), \fBinetd\fR(8), \fBnmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the -Internet RFC's \fIrfc1001.txt\fR, \fIrfc1002.txt\fR. -In addition the CIFS (formerly SMB) specification is available -as a link from the Web page -http://samba.org/cifs/ . +\fBhosts_access\fR(5), \fBinetd\fR(8), \fBnmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's\fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for -Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbmnt.8 b/docs/manpages/smbmnt.8 index 6464567636..45515c593d 100644 --- a/docs/manpages/smbmnt.8 +++ b/docs/manpages/smbmnt.8 @@ -1,68 +1,91 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBMNT" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBMNT" 8 "" "" "" .SH NAME smbmnt \- helper utility for mounting SMB filesystems -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbmnt\fR \fBmount-point\fR [ \fB-s \fR ] [ \fB-r\fR ] [ \fB-u \fR ] [ \fB-g \fR ] [ \fB-f \fR ] [ \fB-d \fR ] [ \fB-o \fR ] [ \fB-h\fR ] +.nf +\fBsmbmnt\fR {mount-point} [-s ] [-r] [-u ] [-g ] [-f ] [-d ] [-o ] [-h] + +.fi .SH "DESCRIPTION" + .PP -\fBsmbmnt\fR is a helper application used -by the smbmount program to do the actual mounting of SMB shares. -\fBsmbmnt\fR can be installed setuid root if you want -normal users to be able to mount their SMB shares. +\fBsmbmnt\fR is a helper application used by the smbmount program to do the actual mounting of SMB shares\&.\fBsmbmnt\fR can be installed setuid root if you want normal users to be able to mount their SMB shares\&. + .PP -A setuid smbmnt will only allow mounts on directories owned -by the user, and that the user has write permission on. +A setuid smbmnt will only allow mounts on directories owned by the user, and that the user has write permission on\&. + .PP -The \fBsmbmnt\fR program is normally invoked -by \fBsmbmount\fR(8). It should not be invoked directly by users. +The \fBsmbmnt\fR program is normally invoked by \fBsmbmount\fR(8)\&. It should not be invoked directly by users\&. + .PP -smbmount searches the normal PATH for smbmnt. You must ensure -that the smbmnt version in your path matches the smbmount used. +smbmount searches the normal PATH for smbmnt\&. You must ensure that the smbmnt version in your path matches the smbmount used\&. + .SH "OPTIONS" + .TP -\fB-r\fR -mount the filesystem read-only +-r +mount the filesystem read-only + + .TP -\fB-u uid\fR -specify the uid that the files will -be owned by +-u uid +specify the uid that the files will be owned by + + .TP -\fB-g gid\fR -specify the gid that the files will be -owned by +-g gid +specify the gid that the files will be owned by + + .TP -\fB-f mask\fR +-f mask specify the octal file mask applied + + .TP -\fB-d mask\fR -specify the octal directory mask -applied +-d mask +specify the octal directory mask applied + + .TP -\fB-o options\fR -list of options that are passed as-is to smbfs, if this -command is run on a 2.4 or higher Linux kernel. +-o options +list of options that are passed as-is to smbfs, if this command is run on a 2\&.4 or higher Linux kernel\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "AUTHOR" + .PP -Volker Lendecke, Andrew Tridgell, Michael H. Warfield -and others. +Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&. + .PP -The current maintainer of smbfs and the userspace -tools \fBsmbmount\fR, \fBsmbumount\fR, -and \fBsmbmnt\fR is Urban Widmark . -The SAMBA Mailing list -is the preferred place to ask questions regarding these programs. +The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&. + .PP -The conversion of this manpage for Samba 2.2 was performed -by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 -was done by Alexander Bokovoy. +The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbmount.8 b/docs/manpages/smbmount.8 index 1e78bd3a3f..ccb776e7f1 100644 --- a/docs/manpages/smbmount.8 +++ b/docs/manpages/smbmount.8 @@ -1,214 +1,214 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBMOUNT" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBMOUNT" 8 "" "" "" .SH NAME smbmount \- mount an smbfs filesystem -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbmount\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR ] +.nf +\fBsmbmount\fR {service} {mount-point} [-o options] +.fi .SH "DESCRIPTION" + .PP -\fBsmbmount\fR mounts a Linux SMB filesystem. It -is usually invoked as \fBmount.smbfs\fR by -the \fBmount\fR(8) command when using the -"-t smbfs" option. This command only works in Linux, and the kernel must -support the smbfs filesystem. -.PP -Options to \fBsmbmount\fR are specified as a comma-separated -list of key=value pairs. It is possible to send options other -than those listed here, assuming that smbfs supports them. If -you get mount failures, check your kernel log for errors on -unknown options. -.PP -\fBsmbmount\fR is a daemon. After mounting it keeps running until -the mounted smbfs is umounted. It will log things that happen -when in daemon mode using the "machine name" smbmount, so -typically this output will end up in \fIlog.smbmount\fR. The \fB smbmount\fR process may also be called mount.smbfs. -.PP -\fBNOTE:\fR \fBsmbmount\fR -calls \fBsmbmnt\fR(8) to do the actual mount. You -must make sure that \fBsmbmnt\fR is in the path so -that it can be found. +\fBsmbmount\fR mounts a Linux SMB filesystem\&. It is usually invoked as \fBmount.smbfs\fR by the \fBmount\fR(8) command when using the "-t smbfs" option\&. This command only works in Linux, and the kernel must support the smbfs filesystem\&. + +.PP +Options to \fBsmbmount\fR are specified as a comma-separated list of key=value pairs\&. It is possible to send options other than those listed here, assuming that smbfs supports them\&. If you get mount failures, check your kernel log for errors on unknown options\&. + +.PP +\fBsmbmount\fR is a daemon\&. After mounting it keeps running until the mounted smbfs is umounted\&. It will log things that happen when in daemon mode using the "machine name" smbmount, so typically this output will end up in \fIlog\&.smbmount\fR\&. The \fB smbmount\fR process may also be called mount\&.smbfs\&. + +.PP +\fBNOTE:\fR \fBsmbmount\fR calls \fBsmbmnt\fR(8) to do the actual mount\&. You must make sure that \fBsmbmnt\fR is in the path so that it can be found\&. + .SH "OPTIONS" + .TP -\fBusername=\fR -specifies the username to connect as. If -this is not given, then the environment variable \fB USER\fR is used. This option can also take the -form "user%password" or "user/workgroup" or -"user/workgroup%password" to allow the password and workgroup -to be specified as part of the username. -.TP -\fBpassword=\fR -specifies the SMB password. If this -option is not given then the environment variable -\fBPASSWD\fR is used. If it can find -no password \fBsmbmount\fR will prompt -for a passeword, unless the guest option is -given. - -Note that passwords which contain the argument delimiter -character (i.e. a comma ',') will failed to be parsed correctly -on the command line. However, the same password defined -in the PASSWD environment variable or a credentials file (see -below) will be read correctly. -.TP -\fBcredentials=\fR -specifies a file that contains a username and/or password. -The format of the file is: +username= +specifies the username to connect as\&. If this is not given, then the environment variable \fB USER\fR is used\&. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username\&. + +.TP +password= +specifies the SMB password\&. If this option is not given then the environment variable \fBPASSWD\fR is used\&. If it can find no password \fBsmbmount\fR will prompt for a passeword, unless the guest option is given\&. + + +Note that passwords which contain the argument delimiter character (i\&.e\&. a comma ',') will failed to be parsed correctly on the command line\&. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly\&. + + +.TP +credentials= +specifies a file that contains a username and/or password\&. +The format of the file is: .nf + username = password = .fi -This is preferred over having passwords in plaintext in a -shared file, such as \fI/etc/fstab\fR. Be sure to protect any -credentials file properly. -.TP -\fBkrb\fR -Use kerberos (Active Directory). -.TP -\fBnetbiosname=\fR -sets the source NetBIOS name. It defaults -to the local hostname. -.TP -\fBuid=\fR -sets the uid that will own all files on -the mounted filesystem. -It may be specified as either a username or a numeric uid. -.TP -\fBgid=\fR -sets the gid that will own all files on -the mounted filesystem. -It may be specified as either a groupname or a numeric -gid. -.TP -\fBport=\fR -sets the remote SMB port number. The default -is 139. -.TP -\fBfmask=\fR -sets the file mask. This determines the -permissions that remote files have in the local filesystem. -The default is based on the current umask. -.TP -\fBdmask=\fR -Sets the directory mask. This determines the -permissions that remote directories have in the local filesystem. -The default is based on the current umask. -.TP -\fBdebug=\fR -Sets the debug level. This is useful for -tracking down SMB connection problems. A suggested value to -start with is 4. If set too high there will be a lot of -output, possibly hiding the useful output. -.TP -\fBip=\fR -Sets the destination host or IP address. -.TP -\fBworkgroup=\fR -Sets the workgroup on the destination -.TP -\fBsockopt=\fR -Sets the TCP socket options. See the \fBsmb.conf\fR(5) \fIsocket options\fR option. -.TP -\fBscope=\fR -Sets the NetBIOS scope -.TP -\fBguest\fR -Don't prompt for a password -.TP -\fBro\fR -mount read-only -.TP -\fBrw\fR -mount read-write -.TP -\fBiocharset=\fR -sets the charset used by the Linux side for codepage -to charset translations (NLS). Argument should be the -name of a charset, like iso8859-1. (Note: only kernel -2.4.0 or later) -.TP -\fBcodepage=\fR -sets the codepage the server uses. See the iocharset -option. Example value cp850. (Note: only kernel 2.4.0 -or later) -.TP -\fBttl=\fR -sets how long a directory listing is cached in milliseconds -(also affects visibility of file size and date -changes). A higher value means that changes on the -server take longer to be noticed but it can give -better performance on large directories, especially -over long distances. Default is 1000ms but something -like 10000ms (10 seconds) is probably more reasonable -in many cases. -(Note: only kernel 2.4.2 or later) + +This is preferred over having passwords in plaintext in a shared file, such as \fI/etc/fstab\fR\&. Be sure to protect any credentials file properly\&. + + +.TP +krb +Use kerberos (Active Directory)\&. + + +.TP +netbiosname= +sets the source NetBIOS name\&. It defaults to the local hostname\&. + + +.TP +uid= +sets the uid that will own all files on the mounted filesystem\&. It may be specified as either a username or a numeric uid\&. + + +.TP +gid= +sets the gid that will own all files on the mounted filesystem\&. It may be specified as either a groupname or a numeric gid\&. + + +.TP +port= +sets the remote SMB port number\&. The default is 139\&. + + +.TP +fmask= +sets the file mask\&. This determines the permissions that remote files have in the local filesystem\&. The default is based on the current umask\&. + + +.TP +dmask= +Sets the directory mask\&. This determines the permissions that remote directories have in the local filesystem\&. The default is based on the current umask\&. + + +.TP +debug= +Sets the debug level\&. This is useful for tracking down SMB connection problems\&. A suggested value to start with is 4\&. If set too high there will be a lot of output, possibly hiding the useful output\&. + + +.TP +ip= +Sets the destination host or IP address\&. + + +.TP +workgroup= +Sets the workgroup on the destination + + +.TP +sockopt= +Sets the TCP socket options\&. See the \fBsmb.conf\fR(5) \fIsocket options\fR option\&. + + +.TP +scope= +Sets the NetBIOS scope + + +.TP +guest +Don't prompt for a password + + +.TP +ro +mount read-only + + +.TP +rw +mount read-write + + +.TP +iocharset= +sets the charset used by the Linux side for codepage to charset translations (NLS)\&. Argument should be the name of a charset, like iso8859-1\&. (Note: only kernel 2\&.4\&.0 or later) + + +.TP +codepage= +sets the codepage the server uses\&. See the iocharset option\&. Example value cp850\&. (Note: only kernel 2\&.4\&.0 or later) + + +.TP +ttl= +sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes)\&. A higher value means that changes on the server take longer to be noticed but it can give better performance on large directories, especially over long distances\&. Default is 1000ms but something like 10000ms (10 seconds) is probably more reasonable in many cases\&. (Note: only kernel 2\&.4\&.2 or later) + + .SH "ENVIRONMENT VARIABLES" + .PP -The variable \fBUSER\fR may contain the username of the -person using the client. This information is used only if the -protocol level is high enough to support session-level -passwords. The variable can be used to set both username and -password by using the format username%password. +The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. The variable can be used to set both username and password by using the format username%password\&. + .PP -The variable \fBPASSWD\fR may contain the password of the -person using the client. This information is used only if the -protocol level is high enough to support session-level -passwords. +The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. + .PP -The variable \fBPASSWD_FILE\fR may contain the pathname -of a file to read the password from. A single line of input is -read and used as the password. +The variable \fBPASSWD_FILE\fR may contain the pathname of a file to read the password from\&. A single line of input is read and used as the password\&. + .SH "BUGS" + .PP -Passwords and other options containing , can not be handled. -For passwords an alternative way of passing them is in a credentials -file or in the PASSWD environment. +Passwords and other options containing , can not be handled\&. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment\&. + .PP -The credentials file does not handle usernames or passwords with -leading space. +The credentials file does not handle usernames or passwords with leading space\&. + .PP -One smbfs bug is important enough to mention here, even if it -is a bit misplaced: -.TP 0.2i +One smbfs bug is important enough to mention here, even if it is a bit misplaced: + +.TP 3 \(bu -Mounts sometimes stop working. This is usually -caused by smbmount terminating. Since smbfs needs smbmount to -reconnect when the server disconnects, the mount will eventually go -dead. An umount/mount normally fixes this. At least 2 ways to -trigger this bug are known. -.PP -Note that the typical response to a bug report is suggestion -to try the latest version first. So please try doing that first, -and always include which versions you use of relevant software -when reporting bugs (minimum: samba, kernel, distribution) +Mounts sometimes stop working\&. This is usually caused by smbmount terminating\&. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead\&. An umount/mount normally fixes this\&. At least 2 ways to trigger this bug are known\&. + +.LP + +.PP +Note that the typical response to a bug report is suggestion to try the latest version first\&. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution) + .SH "SEE ALSO" + .PP -Documentation/filesystems/smbfs.txt in the linux kernel -source tree may contain additional options and information. +Documentation/filesystems/smbfs\&.txt in the linux kernel source tree may contain additional options and information\&. + .PP FreeBSD also has a smbfs, but it is not related to smbmount + .PP -For Solaris, HP-UX and others you may want to look at \fBsmbsh\fR(1) or at other solutions, such as -Sharity or perhaps replacing the SMB server with a NFS server. +For Solaris, HP-UX and others you may want to look at \fBsmbsh\fR(1) or at other solutions, such as Sharity or perhaps replacing the SMB server with a NFS server\&. + .SH "AUTHOR" + .PP -Volker Lendecke, Andrew Tridgell, Michael H. Warfield -and others. +Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&. + .PP -The current maintainer of smbfs and the userspace -tools \fBsmbmount\fR, \fBsmbumount\fR, -and \fBsmbmnt\fR is Urban Widmark . -The SAMBA Mailing list -is the preferred place to ask questions regarding these programs. +The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&. + .PP -The conversion of this manpage for Samba 2.2 was performed -by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 -was done by Alexander Bokovoy. +The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbpasswd.5 b/docs/manpages/smbpasswd.5 index e07da1172f..75645d4b6a 100644 --- a/docs/manpages/smbpasswd.5 +++ b/docs/manpages/smbpasswd.5 @@ -1,155 +1,111 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBPASSWD" "5" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBPASSWD" 5 "" "" "" .SH NAME smbpasswd \- The Samba encrypted password file -.SH SYNOPSIS +.SH "SYNOPSIS" + .PP \fIsmbpasswd\fR + .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -smbpasswd is the Samba encrypted password file. It contains -the username, Unix user id and the SMB hashed passwords of the -user, as well as account flag information and the time the -password was last changed. This file format has been evolving with -Samba and has had several different formats in the past. +smbpasswd is the Samba encrypted password file\&. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed\&. This file format has been evolving with Samba and has had several different formats in the past\&. + .SH "FILE FORMAT" + .PP -The format of the smbpasswd file used by Samba 2.2 -is very similar to the familiar Unix \fIpasswd(5)\fR -file. It is an ASCII file containing one line for each user. Each field -ithin each line is separated from the next by a colon. Any entry -beginning with '#' is ignored. The smbpasswd file contains the -following information for each user: +The format of the smbpasswd file used by Samba 2\&.2 is very similar to the familiar Unix \fIpasswd(5)\fR file\&. It is an ASCII file containing one line for each user\&. Each field ithin each line is separated from the next by a colon\&. Any entry beginning with '#' is ignored\&. The smbpasswd file contains the following information for each user: + .TP -\fBname\fR -This is the user name. It must be a name that -already exists in the standard UNIX passwd file. +name +This is the user name\&. It must be a name that already exists in the standard UNIX passwd file\&. + + .TP -\fBuid\fR -This is the UNIX uid. It must match the uid -field for the same user entry in the standard UNIX passwd file. -If this does not match then Samba will refuse to recognize -this smbpasswd file entry as being valid for a user. +uid +This is the UNIX uid\&. It must match the uid field for the same user entry in the standard UNIX passwd file\&. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user\&. + + .TP -\fBLanman Password Hash\fR -This is the LANMAN hash of the user's password, -encoded as 32 hex digits. The LANMAN hash is created by DES -encrypting a well known string with the user's password as the -DES key. This is the same password used by Windows 95/98 machines. -Note that this password hash is regarded as weak as it is -vulnerable to dictionary attacks and if two users choose the -same password this entry will be identical (i.e. the password -is not "salted" as the UNIX password is). If the user has a -null password this field will contain the characters "NO PASSWORD" -as the start of the hex string. If the hex string is equal to -32 'X' characters then the user's account is marked as -disabled and the user will not be able to -log onto the Samba server. - -\fBWARNING !!\fR Note that, due to -the challenge-response nature of the SMB/CIFS authentication -protocol, anyone with a knowledge of this password hash will -be able to impersonate the user on the network. For this -reason these hashes are known as \fBplain text -equivalents\fR and must \fBNOT\fR be made -available to anyone but the root user. To protect these passwords -the smbpasswd file is placed in a directory with read and -traverse access only to the root user and the smbpasswd file -itself must be set to be read/write only by root, with no -other access. +Lanman Password Hash +This is the LANMAN hash of the user's password, encoded as 32 hex digits\&. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key\&. This is the same password used by Windows 95/98 machines\&. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i\&.e\&. the password is not "salted" as the UNIX password is)\&. If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string\&. If the hex string is equal to 32 'X' characters then the user's account is marked as \fBdisabled\fR and the user will not be able to log onto the Samba server\&. + + +\fBWARNING !!\fR Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\&. For this reason these hashes are known as \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&. + + .TP -\fBNT Password Hash\fR -This is the Windows NT hash of the user's -password, encoded as 32 hex digits. The Windows NT hash is -created by taking the user's password as represented in -16-bit, little-endian UNICODE and then applying the MD4 -(internet rfc1321) hashing algorithm to it. - -This password hash is considered more secure than -the LANMAN Password Hash as it preserves the case of the -password and uses a much higher quality hashing algorithm. -However, it is still the case that if two users choose the same -password this entry will be identical (i.e. the password is -not "salted" as the UNIX password is). - -\fBWARNING !!\fR. Note that, due to -the challenge-response nature of the SMB/CIFS authentication -protocol, anyone with a knowledge of this password hash will -be able to impersonate the user on the network. For this -reason these hashes are known as \fBplain text -equivalents\fR and must \fBNOT\fR be made -available to anyone but the root user. To protect these passwords -the smbpasswd file is placed in a directory with read and -traverse access only to the root user and the smbpasswd file -itself must be set to be read/write only by root, with no -other access. +NT Password Hash +This is the Windows NT hash of the user's password, encoded as 32 hex digits\&. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it\&. + + +This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm\&. However, it is still the case that if two users choose the same password this entry will be identical (i\&.e\&. the password is not "salted" as the UNIX password is)\&. + + +\fBWARNING !!\fR\&. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\&. For this reason these hashes are known as \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&. + + .TP -\fBAccount Flags\fR -This section contains flags that describe -the attributes of the users account. In the Samba 2.2 release -this field is bracketed by '[' and ']' characters and is always -13 characters in length (including the '[' and ']' characters). -The contents of this field may be any of the following characters: -.RS -.TP 0.2i -\(bu -\fBU\fR - This means -this is a "User" account, i.e. an ordinary user. Only User -and Workstation Trust accounts are currently supported -in the smbpasswd file. -.TP 0.2i -\(bu -\fBN\fR - This means the -account has no password (the passwords in the fields LANMAN -Password Hash and NT Password Hash are ignored). Note that this -will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fBsmb.conf\fR(5) config file. -.TP 0.2i -\(bu -\fBD\fR - This means the account -is disabled and no SMB/CIFS logins will be allowed for this user. -.TP 0.2i -\(bu -\fBW\fR - This means this account -is a "Workstation Trust" account. This kind of account is used -in the Samba PDC code stream to allow Windows NT Workstations -and Servers to join a Domain hosted by a Samba PDC. -.RE - -Other flags may be added as the code is extended in future. -The rest of this field space is filled in with spaces. +Account Flags +This section contains flags that describe the attributes of the users account\&. In the Samba 2\&.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters)\&. The contents of this field may be any of the following characters: + + +\fBU\fR - This means this is a "User" account, i\&.e\&. an ordinary user\&. Only User and Workstation Trust accounts are currently supported in the smbpasswd file\&. + +\fBN\fR - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored)\&. Note that this will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fBsmb.conf\fR(5) config file\&. + +\fBD\fR - This means the account is disabled and no SMB/CIFS logins will be allowed for this user\&. + +\fBW\fR - This means this account is a "Workstation Trust" account\&. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC\&. + +Other flags may be added as the code is extended in future\&. The rest of this field space is filled in with spaces\&. + + .TP -\fBLast Change Time\fR -This field consists of the time the account was -last modified. It consists of the characters 'LCT-' (standing for -"Last Change Time") followed by a numeric encoding of the UNIX time -in seconds since the epoch (1970) that the last change was made. +Last Change Time +This field consists of the time the account was last modified\&. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made\&. + + .PP -All other colon separated fields are ignored at this time. +All other colon separated fields are ignored at this time\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbpasswd\fR(8), \fBSamba\fR(7), and -the Internet RFC1321 for details on the MD4 algorithm. +\fBsmbpasswd\fR(8), \fBSamba\fR(7), and the Internet RFC1321 for details on the MD4 algorithm\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbpasswd.8 b/docs/manpages/smbpasswd.8 index 1a27643b04..a7973871c4 100644 --- a/docs/manpages/smbpasswd.8 +++ b/docs/manpages/smbpasswd.8 @@ -1,288 +1,219 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBPASSWD" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBPASSWD" 8 "" "" "" .SH NAME smbpasswd \- change a user's SMB password -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbpasswd\fR [ \fB-a\fR ] [ \fB-x\fR ] [ \fB-d\fR ] [ \fB-e\fR ] [ \fB-D debuglevel\fR ] [ \fB-n\fR ] [ \fB-r \fR ] [ \fB-R \fR ] [ \fB-m\fR ] [ \fB-U username[%password]\fR ] [ \fB-h\fR ] [ \fB-s\fR ] [ \fB-w pass\fR ] [ \fB-i\fR ] [ \fB-L\fR ] [ \fBusername\fR ] +.nf +\fBsmbpasswd\fR [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r ] [-R ] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username] + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The smbpasswd program has several different -functions, depending on whether it is run by the \fBroot\fR user -or not. When run as a normal user it allows the user to change -the password used for their SMB sessions on any machines that store -SMB passwords. +The smbpasswd program has several different functions, depending on whether it is run by the \fBroot\fR user or not\&. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords\&. + .PP -By default (when run with no arguments) it will attempt to -change the current user's SMB password on the local machine. This is -similar to the way the \fBpasswd(1)\fR program works. \fB smbpasswd\fR differs from how the passwd program works -however in that it is not \fBsetuid root\fR but works in -a client-server mode and communicates with a -locally running \fBsmbd\fR(8). As a consequence in order for this to -succeed the smbd daemon must be running on the local machine. On a -UNIX machine the encrypted SMB passwords are usually stored in -the \fBsmbpasswd\fR(5) file. +By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine\&. This is similar to the way the \fBpasswd(1)\fR program works\&. \fB smbpasswd\fR differs from how the passwd program works however in that it is not \fBsetuid root\fR but works in a client-server mode and communicates with a locally running \fBsmbd\fR(8)\&. As a consequence in order for this to succeed the smbd daemon must be running on the local machine\&. On a UNIX machine the encrypted SMB passwords are usually stored in the \fBsmbpasswd\fR(5) file\&. + .PP -When run by an ordinary user with no options, smbpasswd -will prompt them for their old SMB password and then ask them -for their new password twice, to ensure that the new password -was typed correctly. No passwords will be echoed on the screen -whilst being typed. If you have a blank SMB password (specified by -the string "NO PASSWORD" in the smbpasswd file) then just press -the key when asked for your old password. +When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly\&. No passwords will be echoed on the screen whilst being typed\&. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the key when asked for your old password\&. + .PP -smbpasswd can also be used by a normal user to change their -SMB password on remote machines, such as Windows NT Primary Domain -Controllers. See the (\fI-r\fR) and \fI-U\fR options -below. +smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers\&. See the (\fI-r\fR) and \fI-U\fR options below\&. + .PP -When run by root, smbpasswd allows new users to be added -and deleted in the smbpasswd file, as well as allows changes to -the attributes of the user in this file to be made. When run by root, \fB smbpasswd\fR accesses the local smbpasswd file -directly, thus enabling changes to be made even if smbd is not -running. +When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to the attributes of the user in this file to be made\&. When run by root, \fB smbpasswd\fR accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running\&. + .SH "OPTIONS" + .TP -\fB-a\fR -This option specifies that the username -following should be added to the local smbpasswd file, with the -new password typed (type for the old password). This -option is ignored if the username following already exists in -the smbpasswd file and it is treated like a regular change -password command. Note that the default passdb backends require -the user to already exist in the system password file (usually -\fI/etc/passwd\fR), else the request to add the -user will fail. - -This option is only available when running smbpasswd -as root. +-a +This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type for the old password)\&. This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command\&. Note that the default passdb backends require the user to already exist in the system password file (usually \fI/etc/passwd\fR), else the request to add the user will fail\&. + + +This option is only available when running smbpasswd as root\&. + + .TP -\fB-x\fR -This option specifies that the username -following should be deleted from the local smbpasswd file. +-x +This option specifies that the username following should be deleted from the local smbpasswd file\&. + + +This option is only available when running smbpasswd as root\&. + -This option is only available when running smbpasswd as -root. .TP -\fB-d\fR -This option specifies that the username following -should be disabled in the local smbpasswd -file. This is done by writing a 'D' flag -into the account control space in the smbpasswd file. Once this -is done all attempts to authenticate via SMB using this username -will fail. - -If the smbpasswd file is in the 'old' format (pre-Samba 2.0 -format) there is no space in the user's password entry to write -this information and the command will FAIL. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats. - -This option is only available when running smbpasswd as -root. +-d +This option specifies that the username following should be \fBdisabled\fR in the local smbpasswd file\&. This is done by writing a \fB'D'\fR flag into the account control space in the smbpasswd file\&. Once this is done all attempts to authenticate via SMB using this username will fail\&. + + +If the smbpasswd file is in the 'old' format (pre-Samba 2\&.0 format) there is no space in the user's password entry to write this information and the command will FAIL\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&. + + +This option is only available when running smbpasswd as root\&. + + .TP -\fB-e\fR -This option specifies that the username following -should be enabled in the local smbpasswd file, -if the account was previously disabled. If the account was not -disabled this option has no effect. Once the account is enabled then -the user will be able to authenticate via SMB once again. - -If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account. -See \fBsmbpasswd\fR(5) for -details on the 'old' and new password file formats. - -This option is only available when running smbpasswd as root. +-e +This option specifies that the username following should be \fBenabled\fR in the local smbpasswd file, if the account was previously disabled\&. If the account was not disabled this option has no effect\&. Once the account is enabled then the user will be able to authenticate via SMB once again\&. + + +If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&. + + +This option is only available when running smbpasswd as root\&. + + .TP -\fB-D debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is not specified -is zero. - -The higher this value, the more detail will be logged to the -log files about the activities of smbpasswd. At level 0, only -critical errors and serious warnings will be logged. - -Levels above 1 will generate considerable amounts of log -data, and should only be used when investigating a problem. Levels -above 3 are designed for use only by developers and generate -HUGE amounts of log data, most of which is extremely cryptic. +-D debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of smbpasswd\&. At level 0, only critical errors and serious warnings will be logged\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + .TP -\fB-n\fR -This option specifies that the username following -should have their password set to null (i.e. a blank password) in -the local smbpasswd file. This is done by writing the string "NO -PASSWORD" as the first part of the first password stored in the -smbpasswd file. - -Note that to allow users to logon to a Samba server once -the password has been set to "NO PASSWORD" in the smbpasswd -file the administrator must set the following parameter in the [global] -section of the \fIsmb.conf\fR file : +-n +This option specifies that the username following should have their password set to null (i\&.e\&. a blank password) in the local smbpasswd file\&. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the smbpasswd file\&. + + +Note that to allow users to logon to a Samba server once the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] section of the \fIsmb\&.conf\fR file : + \fBnull passwords = yes\fR -This option is only available when running smbpasswd as -root. + +This option is only available when running smbpasswd as root\&. + + .TP -\fB-r remote machine name\fR -This option allows a user to specify what machine -they wish to change their password on. Without this parameter -smbpasswd defaults to the local host. The \fIremote -machine name\fR is the NetBIOS name of the SMB/CIFS -server to contact to attempt the password change. This name is -resolved into an IP address using the standard name resolution -mechanism in all programs of the Samba suite. See the \fI-R -name resolve order\fR parameter for details on changing -this resolving mechanism. - -The username whose password is changed is that of the -current UNIX logged on user. See the \fI-U username\fR -parameter for details on changing the password for a different -username. - -Note that if changing a Windows NT Domain password the -remote machine specified must be the Primary Domain Controller for -the domain (Backup Domain Controllers only have a read-only -copy of the user account database and will not allow the password -change). - -\fBNote\fR that Windows 95/98 do not have -a real password database so it is not possible to change passwords -specifying a Win95/98 machine as remote machine target. +-r remote machine name +This option allows a user to specify what machine they wish to change their password on\&. Without this parameter smbpasswd defaults to the local host\&. The \fIremote machine name\fR is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change\&. This name is resolved into an IP address using the standard name resolution mechanism in all programs of the Samba suite\&. See the \fI-R name resolve order\fR parameter for details on changing this resolving mechanism\&. + + +The username whose password is changed is that of the current UNIX logged on user\&. See the \fI-U username\fR parameter for details on changing the password for a different username\&. + + +Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read-only copy of the user account database and will not allow the password change)\&. + + +\fBNote\fR that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target\&. + + .TP -\fB-R name resolve order\fR -This option allows the user of smbpasswd to determine -what name resolution services to use when looking up the NetBIOS -name of the host being connected to. - -The options are :"lmhosts", "host", "wins" and "bcast". They -cause names to be resolved as follows: -.RS -.TP 0.2i -\(bu -lmhosts: Lookup an IP -address in the Samba lmhosts file. If the line in lmhosts has -no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then -any name type matches for lookup. -.TP 0.2i -\(bu -host: Do a standard host -name to IP address resolution, using the system \fI/etc/hosts -\fR, NIS, or DNS lookups. This method of name resolution -is operating system depended for instance on IRIX or Solaris this -may be controlled by the \fI/etc/nsswitch.conf\fR -file). Note that this method is only used if the NetBIOS name -type being queried is the 0x20 (server) name type, otherwise -it is ignored. -.TP 0.2i -\(bu -wins: Query a name with -the IP address listed in the \fIwins server\fR -parameter. If no WINS server has been specified this method -will be ignored. -.TP 0.2i -\(bu -bcast: Do a broadcast on -each of the known local interfaces listed in the -\fIinterfaces\fR parameter. This is the least -reliable of the name resolution methods as it depends on the -target host being on a locally connected subnet. -.RE - -The default order is \fBlmhosts, host, wins, bcast\fR -and without this parameter or any entry in the \fBsmb.conf\fR(5) file the name resolution methods will -be attempted in this order. +-R name resolve order +This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to\&. + + +The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows: + + +\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&. + +\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&. + +\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&. + +\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. + +The default order is \fBlmhosts, host, wins, bcast\fR and without this parameter or any entry in the \fBsmb.conf\fR(5) file the name resolution methods will be attempted in this order\&. + + .TP -\fB-m\fR -This option tells smbpasswd that the account -being changed is a MACHINE account. Currently this is used -when Samba is being used as an NT Primary Domain Controller. +-m +This option tells smbpasswd that the account being changed is a MACHINE account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&. + + +This option is only available when running smbpasswd as root\&. + -This option is only available when running smbpasswd as root. .TP -\fB-U username\fR -This option may only be used in conjunction -with the \fI-r\fR option. When changing -a password on a remote machine it allows the user to specify -the user name on that machine whose password will be changed. It -is present to allow users who have different user names on -different systems to change these passwords. +-U username +This option may only be used in conjunction with the \fI-r\fR option\&. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed\&. It is present to allow users who have different user names on different systems to change these passwords\&. + + .TP -\fB-h\fR -This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root -or as an ordinary user. +-h +This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root or as an ordinary user\&. + + .TP -\fB-s\fR -This option causes smbpasswd to be silent (i.e. -not issue prompts) and to read its old and new passwords from -standard input, rather than from \fI/dev/tty\fR -(like the \fBpasswd(1)\fR program does). This option -is to aid people writing scripts to drive smbpasswd +-s +This option causes smbpasswd to be silent (i\&.e\&. not issue prompts) and to read its old and new passwords from standard input, rather than from \fI/dev/tty\fR (like the \fBpasswd(1)\fR program does)\&. This option is to aid people writing scripts to drive smbpasswd + + .TP -\fB-w password\fR -This parameter is only available if Samba -has been configured to use the experimental -\fB--with-ldapsam\fR option. The \fI-w\fR -switch is used to specify the password to be used with the -\fIldap admin -dn\fR Note that the password is stored in -the \fIsecrets.tdb\fR and is keyed off -of the admin's DN. This means that if the value of \fIldap -admin dn\fR ever changes, the password will need to be -manually updated as well. +-w password +This parameter is only available if Samba has been configured to use the experimental \fB--with-ldapsam\fR option\&. The \fI-w\fR switch is used to specify the password to be used with the \fIldap admin dn\fR\&. Note that the password is stored in the \fIsecrets\&.tdb\fR and is keyed off of the admin's DN\&. This means that if the value of \fIldap admin dn\fR ever changes, the password will need to be manually updated as well\&. + + .TP -\fB-i\fR -This option tells smbpasswd that the account -being changed is an interdomain trust account. Currently this is used -when Samba is being used as an NT Primary Domain Controller. -The account contains the info about another trusted domain. +-i +This option tells smbpasswd that the account being changed is an interdomain trust account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&. The account contains the info about another trusted domain\&. + + +This option is only available when running smbpasswd as root\&. + -This option is only available when running smbpasswd as root. .TP -\fB-L\fR -Run in local mode. +-L +Run in local mode\&. + + .TP -\fBusername\fR -This specifies the username for all of the -\fBroot only\fR options to operate on. Only root -can specify this parameter as only root has the permission needed -to modify attributes directly in the local smbpasswd file. +username +This specifies the username for all of the \fBroot only\fR options to operate on\&. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file\&. + + .SH "NOTES" + .PP -Since \fBsmbpasswd\fR works in client-server -mode communicating with a local smbd for a non-root user then -the smbd daemon must be running for this to work. A common problem -is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying either \fIallow -hosts\fR or \fIdeny hosts\fR entry in -the \fBsmb.conf\fR(5) file and neglecting to -allow "localhost" access to the smbd. +Since \fBsmbpasswd\fR works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work\&. A common problem is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying either \fIallow hosts\fR or \fIdeny hosts\fR entry in the \fBsmb.conf\fR(5) file and neglecting to allow "localhost" access to the smbd\&. + .PP -In addition, the smbpasswd command is only useful if Samba -has been set up to use encrypted passwords. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details -on how to do this. +In addition, the smbpasswd command is only useful if Samba has been set up to use encrypted passwords\&. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details on how to do this\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbpasswd\fR(5), \fBSamba\fR(7). +\fBsmbpasswd\fR(5), \fBSamba\fR(7)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbsh.1 b/docs/manpages/smbsh.1 index b34a26329a..0e2c4a3a85 100644 --- a/docs/manpages/smbsh.1 +++ b/docs/manpages/smbsh.1 @@ -1,180 +1,141 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBSH" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBSH" 1 "" "" "" .SH NAME -smbsh \- Allows access to Windows NT filesystem using UNIX commands -.SH SYNOPSIS +smbsh \- Allows access to Windows NT filesystem using UNIX commands +.SH "SYNOPSIS" -\fBsmbsh\fR [ \fB-W workgroup\fR ] [ \fB-U username\fR ] [ \fB-P prefix\fR ] [ \fB-R \fR ] [ \fB-d \fR ] [ \fB-l logfile\fR ] [ \fB-L libdir\fR ] +.nf +\fBsmbsh\fR [-W workgroup] [-U username] [-P prefix] [-R ] [-d ] [-l logfile] [-L libdir] + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbsh\fR allows you to access an NT filesystem -using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR. You must use a -shell that is dynamically linked in order for \fBsmbsh\fR -to work correctly. +\fBsmbsh\fR allows you to access an NT filesystem using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR\&. You must use a shell that is dynamically linked in order for \fBsmbsh\fR to work correctly\&. + .SH "OPTIONS" + .TP -\fB-W WORKGROUP\fR -Override the default workgroup specified in the -workgroup parameter of the \fBsmb.conf\fR(5) file -for this session. This may be needed to connect to some -servers. +-W WORKGROUP +Override the default workgroup specified in the workgroup parameter of the \fBsmb.conf\fR(5) file for this session\&. This may be needed to connect to some servers\&. + + .TP -\fB-U username[%pass]\fR -Sets the SMB username or username and password. -If this option is not specified, the user will be prompted for -both the username and the password. If %pass is not specified, -the user will be prompted for the password. +-U username[%pass] +Sets the SMB username or username and password\&. If this option is not specified, the user will be prompted for both the username and the password\&. If %pass is not specified, the user will be prompted for the password\&. + + .TP -\fB-P prefix\fR -This option allows -the user to set the directory prefix for SMB access. The -default value if this option is not specified is -\fBsmb\fR. +-P prefix +This option allows the user to set the directory prefix for SMB access\&. The default value if this option is not specified is \fBsmb\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-R \fR -This option is used to determine what naming -services and in what order to resolve -host names to IP addresses. The option takes a space-separated -string of different name resolution options. - -The options are: "lmhosts", "host", "wins" and "bcast". -They cause names to be resolved as follows : -.RS -.TP 0.2i -\(bu -lmhosts: -Lookup an IP address in the Samba lmhosts file. If the -line in lmhosts has no name type attached to the -NetBIOS name -(see the \fBlmhosts\fR(5) for details) -then any name type matches for lookup. -.TP 0.2i -\(bu -host: -Do a standard host name to IP address resolution, using -the system \fI/etc/hosts\fR, NIS, or DNS -lookups. This method of name resolution is operating -system dependent, for instance on IRIX or Solaris this -may be controlled by the \fI/etc/nsswitch.conf\fR file). Note that this method is only used -if the NetBIOS name type being queried is the 0x20 -(server) name type, otherwise it is ignored. -.TP 0.2i -\(bu -wins: -Query a name with the IP address listed in the -\fIwins server\fR parameter. If no -WINS server has been specified this method will be -ignored. -.TP 0.2i -\(bu -bcast: -Do a broadcast on each of the known local interfaces -listed in the \fIinterfaces\fR -parameter. This is the least reliable of the name -resolution methods as it depends on the target host -being on a locally connected subnet. -.RE - -If this parameter is not set then the name resolve order -defined in the \fBsmb.conf\fR(5) file parameter -(\fIname resolve order\fR) will be used. - -The default order is lmhosts, host, wins, bcast. Without -this parameter or any entry in the \fIname resolve order\fR parameter of the \fBsmb.conf\fR(5) file, the name resolution methods -will be attempted in this order. +-R +This option is used to determine what naming services and in what order to resolve host names to IP addresses\&. The option takes a space-separated string of different name resolution options\&. + + +The options are: "lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows : + + +\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&. + +\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts\fR, NIS, or DNS lookups\&. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf \fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&. + +\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&. + +\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&. + +If this parameter is not set then the name resolve order defined in the \fBsmb.conf\fR(5) file parameter (\fIname resolve order\fR) will be used\&. + + +The default order is lmhosts, host, wins, bcast\&. Without this parameter or any entry in the \fIname resolve order \fR parameter of the \fBsmb.conf\fR(5) file, the name resolution methods will be attempted in this order\&. + + .TP -\fB-L libdir\fR -This parameter specifies the location of the -shared libraries used by \fBsmbsh\fR. The default -value is specified at compile time. +-L libdir +This parameter specifies the location of the shared libraries used by \fBsmbsh\fR\&. The default value is specified at compile time\&. + + .SH "EXAMPLES" -.PP -To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password -that authenticates you to the machine running the Windows NT -operating system. +.PP +To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system\&. .nf + system% \fBsmbsh\fR Username: \fBuser\fR Password: \fBXXXXXXX\fR .fi + + .PP -Any dynamically linked command you execute from -this shell will access the \fI/smb\fR directory -using the smb protocol. For example, the command \fBls /smb -\fR will show a list of workgroups. The command -\fBls /smb/MYGROUP \fR will show all the machines in -the workgroup MYGROUP. The command -\fBls /smb/MYGROUP/\fR will show the share -names for that machine. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to -edit files, and \fBrcp\fR to copy files. +Any dynamically linked command you execute from this shell will access the \fI/smb\fR directory using the smb protocol\&. For example, the command \fBls /smb \fR will show a list of workgroups\&. The command\fBls /smb/MYGROUP \fR will show all the machines in the workgroup MYGROUP\&. The command\fBls /smb/MYGROUP/\fR will show the share names for that machine\&. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to edit files, and \fBrcp\fR to copy files\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "BUGS" + .PP -\fBsmbsh\fR works by intercepting the standard -libc calls with the dynamically loaded versions in \fI smbwrapper.o\fR. Not all calls have been "wrapped", so -some programs may not function correctly under \fBsmbsh -\fR. +\fBsmbsh\fR works by intercepting the standard libc calls with the dynamically loaded versions in \fI smbwrapper\&.o\fR\&. Not all calls have been "wrapped", so some programs may not function correctly under \fBsmbsh \fR\&. + .PP -Programs which are not dynamically linked cannot make -use of \fBsmbsh\fR's functionality. Most versions -of UNIX have a \fBfile\fR command that will -describe how a program was linked. +Programs which are not dynamically linked cannot make use of \fBsmbsh\fR's functionality\&. Most versions of UNIX have a \fBfile\fR command that will describe how a program was linked\&. + .SH "SEE ALSO" + .PP \fBsmbd\fR(8), \fBsmb.conf\fR(5) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbspool.8 b/docs/manpages/smbspool.8 index cc03bb1757..a6413547b8 100644 --- a/docs/manpages/smbspool.8 +++ b/docs/manpages/smbspool.8 @@ -1,100 +1,115 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBSPOOL" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBSPOOL" 8 "" "" "" .SH NAME smbspool \- send a print file to an SMB printer -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbspool\fR \fBjob\fR \fBuser\fR \fBtitle\fR \fBcopies\fR \fBoptions\fR [ \fBfilename\fR ] +.nf +\fBsmbspool\fR {job} {user} {title} {copies} {options} [filename] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -smbspool is a very small print spooling program that -sends a print file to an SMB printer. The command-line arguments -are position-dependent for compatibility with the Common UNIX -Printing System, but you can use smbspool with any printing system -or from a program or script. +smbspool is a very small print spooling program that sends a print file to an SMB printer\&. The command-line arguments are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script\&. + .PP \fBDEVICE URI\fR + .PP -smbspool specifies the destination using a Uniform Resource -Identifier ("URI") with a method of "smb". This string can take -a number of forms: -.TP 0.2i +smbspool specifies the destination using a Uniform Resource Identifier ("URI") with a method of "smb"\&. This string can take a number of forms: + +.TP 3 \(bu smb://server/printer -.TP 0.2i + +.TP \(bu smb://workgroup/server/printer -.TP 0.2i + +.TP \(bu smb://username:password@server/printer -.TP 0.2i + +.TP \(bu smb://username:password@workgroup/server/printer + +.LP + .PP -smbspool tries to get the URI from argv[0]. If argv[0] -contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable. +smbspool tries to get the URI from argv[0]\&. If argv[0] contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable\&. + .PP -Programs using the \fBexec(2)\fR functions can -pass the URI in argv[0], while shell scripts must set the -\fBDEVICE_URI\fR environment variable prior to -running smbspool. +Programs using the \fBexec(2)\fR functions can pass the URI in argv[0], while shell scripts must set the\fBDEVICE_URI\fR environment variable prior to running smbspool\&. + .SH "OPTIONS" -.TP 0.2i + +.TP 3 \(bu -The job argument (argv[1]) contains the -job ID number and is presently not used by smbspool. -.TP 0.2i +The job argument (argv[1]) contains the job ID number and is presently not used by smbspool\&. + +.TP \(bu -The user argument (argv[2]) contains the -print user's name and is presently not used by smbspool. -.TP 0.2i +The user argument (argv[2]) contains the print user's name and is presently not used by smbspool\&. + +.TP \(bu -The title argument (argv[3]) contains the -job title string and is passed as the remote file name -when sending the print job. -.TP 0.2i +The title argument (argv[3]) contains the job title string and is passed as the remote file name when sending the print job\&. + +.TP \(bu -The copies argument (argv[4]) contains -the number of copies to be printed of the named file. If -no filename is provided then this argument is not used by -smbspool. -.TP 0.2i +The copies argument (argv[4]) contains the number of copies to be printed of the named file\&. If no filename is provided then this argument is not used by smbspool\&. + +.TP \(bu -The options argument (argv[5]) contains -the print options in a single string and is currently -not used by smbspool. -.TP 0.2i +The options argument (argv[5]) contains the print options in a single string and is currently not used by smbspool\&. + +.TP \(bu -The filename argument (argv[6]) contains the -name of the file to print. If this argument is not specified -then the print file is read from the standard input. +The filename argument (argv[6]) contains the name of the file to print\&. If this argument is not specified then the print file is read from the standard input\&. + +.LP + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbd\fR(8) and \fBSamba\fR(7). +\fBsmbd\fR(8) and \fBSamba\fR(7)\&. + .SH "AUTHOR" + .PP -\fBsmbspool\fR was written by Michael Sweet -at Easy Software Products. +\fBsmbspool\fR was written by Michael Sweet at Easy Software Products\&. + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbstatus.1 b/docs/manpages/smbstatus.1 index 5990a81cc1..7e349dcd19 100644 --- a/docs/manpages/smbstatus.1 +++ b/docs/manpages/smbstatus.1 @@ -1,112 +1,131 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBSTATUS" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBSTATUS" 1 "" "" "" .SH NAME smbstatus \- report on current Samba connections -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbstatus\fR [ \fB-P\fR ] [ \fB-b\fR ] [ \fB-d \fR ] [ \fB-v\fR ] [ \fB-L\fR ] [ \fB-B\fR ] [ \fB-p\fR ] [ \fB-S\fR ] [ \fB-s \fR ] [ \fB-u \fR ] +.nf +\fBsmbstatus\fR [-P] [-b] [-d ] [-v] [-L] [-B] [-p] [-S] [-s ] [-u ] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbstatus\fR is a very simple program to -list the current Samba connections. +\fBsmbstatus\fR is a very simple program to list the current Samba connections\&. + .SH "OPTIONS" + .TP -\fB-P|--profile\fR -If samba has been compiled with the -profiling option, print only the contents of the profiling -shared memory area. +-P|--profile +If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area\&. + + .TP -\fB-b|--brief\fR -gives brief output. +-b|--brief +gives brief output\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-v|--verbose\fR -gives verbose output. +-v|--verbose +gives verbose output\&. + + .TP -\fB-L|--locks\fR -causes smbstatus to only list locks. +-L|--locks +causes smbstatus to only list locks\&. + + .TP -\fB-B|--byterange\fR -causes smbstatus to include byte range locks. +-B|--byterange +causes smbstatus to include byte range locks\&. + + .TP -\fB-p|--processes\fR -print a list of \fBsmbd\fR(8) processes and exit. -Useful for scripting. +-p|--processes +print a list of \fBsmbd\fR(8) processes and exit\&. Useful for scripting\&. + + .TP -\fB-S|--shares\fR -causes smbstatus to only list shares. +-S|--shares +causes smbstatus to only list shares\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-u|--user=\fR -selects information relevant to -\fIusername\fR only. +-u|--user= +selects information relevant to \fIusername\fR only\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbd\fR(8) and \fBsmb.conf\fR(5). +\fBsmbd\fR(8) and \fBsmb.conf\fR(5)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbtar.1 b/docs/manpages/smbtar.1 index cba03cc03a..00d913bdfa 100644 --- a/docs/manpages/smbtar.1 +++ b/docs/manpages/smbtar.1 @@ -1,120 +1,148 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBTAR" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBTAR" 1 "" "" "" .SH NAME -smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives -.SH SYNOPSIS +smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives +.SH "SYNOPSIS" -\fBsmbtar\fR [ \fB-r\fR ] [ \fB-i\fR ] [ \fB-a\fR ] [ \fB-v\fR ] \fB-s server\fR [ \fB-p password\fR ] [ \fB-x services\fR ] [ \fB-X\fR ] [ \fB-N filename\fR ] [ \fB-b blocksize\fR ] [ \fB-d directory\fR ] [ \fB-l loglevel\fR ] [ \fB-u user\fR ] [ \fB-t tape\fR ] \fBfilenames\fR +.nf +\fBsmbtar\fR [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] + [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames} + +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbtar\fR is a very small shell script on top -of \fBsmbclient\fR(1) which dumps SMB shares directly to tape. +\fBsmbtar\fR is a very small shell script on top of \fBsmbclient\fR(1) which dumps SMB shares directly to tape\&. + .SH "OPTIONS" + .TP -\fB-s server\fR -The SMB/CIFS server that the share resides -upon. +-s server +The SMB/CIFS server that the share resides upon\&. + + .TP -\fB-x service\fR -The share name on the server to connect to. -The default is "backup". +-x service +The share name on the server to connect to\&. The default is "backup"\&. + + .TP -\fB-X\fR -Exclude mode. Exclude filenames... from tar -create or restore. +-X +Exclude mode\&. Exclude filenames\&.\&.\&. from tar create or restore\&. + + .TP -\fB-d directory\fR -Change to initial \fIdirectory -\fR before restoring / backing up files. +-d directory +Change to initial \fIdirectory \fR before restoring / backing up files\&. + + .TP -\fB-v\fR -Verbose mode. +-v +Verbose mode\&. + + .TP -\fB-p password\fR -The password to use to access a share. -Default: none +-p password +The password to use to access a share\&. Default: none + + .TP -\fB-u user\fR -The user id to connect as. Default: -UNIX login name. +-u user +The user id to connect as\&. Default: UNIX login name\&. + + .TP -\fB-a\fR -Reset DOS archive bit mode to -indicate file has been archived. +-a +Reset DOS archive bit mode to indicate file has been archived\&. + + .TP -\fB-t tape\fR -Tape device. May be regular file or tape -device. Default: \fI$TAPE\fR environmental -variable; if not set, a file called \fItar.out -\fR. +-t tape +Tape device\&. May be regular file or tape device\&. Default: \fI$TAPE\fR environmental variable; if not set, a file called \fItar\&.out \fR\&. + + .TP -\fB-b blocksize\fR -Blocking factor. Defaults to 20. See -\fBtar(1)\fR for a fuller explanation. +-b blocksize +Blocking factor\&. Defaults to 20\&. See \fBtar(1)\fR for a fuller explanation\&. + + .TP -\fB-N filename\fR -Backup only files newer than filename. Could -be used (for example) on a log file to implement incremental -backups. +-N filename +Backup only files newer than filename\&. Could be used (for example) on a log file to implement incremental backups\&. + + .TP -\fB-i\fR -Incremental mode; tar files are only backed -up if they have the archive bit set. The archive bit is reset -after each file is read. +-i +Incremental mode; tar files are only backed up if they have the archive bit set\&. The archive bit is reset after each file is read\&. + + .TP -\fB-r\fR -Restore. Files are restored to the share -from the tar file. +-r +Restore\&. Files are restored to the share from the tar file\&. + + .TP -\fB-l log level\fR -Log (debug) level. Corresponds to the -\fI-d\fR flag of \fBsmbclient\fR(1). +-l log level +Log (debug) level\&. Corresponds to the \fI-d\fR flag of \fBsmbclient\fR(1)\&. + + .SH "ENVIRONMENT VARIABLES" + .PP -The \fI$TAPE\fR variable specifies the -default tape device to write to. May be overridden -with the -t option. +The \fI$TAPE\fR variable specifies the default tape device to write to\&. May be overridden with the -t option\&. + .SH "BUGS" + .PP -The \fBsmbtar\fR script has different -options from ordinary tar and from smbclient's tar command. +The \fBsmbtar\fR script has different options from ordinary tar and from smbclient's tar command\&. + .SH "CAVEATS" + .PP -Sites that are more careful about security may not like -the way the script handles PC passwords. Backup and restore work -on entire shares; should work on file lists. smbtar works best -with GNU tar and may not work well with other versions. +Sites that are more careful about security may not like the way the script handles PC passwords\&. Backup and restore work on entire shares; should work on file lists\&. smbtar works best with GNU tar and may not work well with other versions\&. + .SH "DIAGNOSTICS" + .PP -See the \fBDIAGNOSTICS\fR section for the \fBsmbclient\fR(1) command. +See the \fBDIAGNOSTICS\fR section for the \fBsmbclient\fR(1) command\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fBsmbd\fR(8), \fBsmbclient\fR(1), \fBsmb.conf\fR(5). +\fBsmbd\fR(8), \fBsmbclient\fR(1), \fBsmb.conf\fR(5)\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -Ricky Poulten -wrote the tar extension and this man page. The \fBsmbtar\fR -script was heavily rewritten and improved by Martin Kraemer . Many -thanks to everyone who suggested extensions, improvements, bug -fixes, etc. The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for -Samba 3.0 was done by Alexander Bokovoy. +Ricky Poulten wrote the tar extension and this man page\&. The \fBsmbtar\fR script was heavily rewritten and improved by Martin Kraemer\&. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/smbtree.1 b/docs/manpages/smbtree.1 index b4a1870dd8..0cc984c24a 100644 --- a/docs/manpages/smbtree.1 +++ b/docs/manpages/smbtree.1 @@ -1,144 +1,143 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBTREE" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBTREE" 1 "" "" "" .SH NAME smbtree \- A text based smb network browser -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbtree\fR [ \fB-b\fR ] [ \fB-D\fR ] [ \fB-S\fR ] +.nf +\fBsmbtree\fR [-b] [-D] [-S] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBsmbtree\fR is a smb browser program -in text mode. It is similar to the "Network Neighborhood" found -on Windows computers. It prints a tree with all -the known domains, the servers in those domains and -the shares on the servers. +\fBsmbtree\fR is a smb browser program in text mode\&. It is similar to the "Network Neighborhood" found on Windows computers\&. It prints a tree with all the known domains, the servers in those domains and the shares on the servers\&. + .SH "OPTIONS" + .TP -\fB-b\fR -Query network nodes by sending requests -as broadcasts instead of querying the (domain) master browser. +-b +Query network nodes by sending requests as broadcasts instead of querying the (domain) master browser\&. + + .TP -\fB-D\fR -Only print a list of all -the domains known on broadcast or by the -master browser +-D +Only print a list of all the domains known on broadcast or by the master browser + + .TP -\fB-S\fR -Only print a list of -all the domains and servers responding on broadcast or -known by the master browser. +-S +Only print a list of all the domains and servers responding on broadcast or known by the master browser\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-N\fR -If specified, this parameter suppresses the normal -password prompt from the client to the user. This is useful when -accessing a service that does not require a password. - -Unless a password is specified on the command line or -this parameter is specified, the client will request a -password. +-N +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&. + + +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&. + + .TP -\fB-k\fR -Try to authenticate with kerberos. Only useful in -an Active Directory environment. +-k +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&. + + .TP -\fB-A|--authfile=filename\fR -This option allows -you to specify a file from which to read the username and -password used in the connection. The format of the file is +-A|--authfile=filename +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is .nf + username = password = domain = .fi -Make certain that the permissions on the file restrict -access from unwanted users. + +Make certain that the permissions on the file restrict access from unwanted users\&. + + .TP -\fB-U|--user=username[%password]\fR -Sets the SMB username or username and password. - -If %password is not specified, the user will be prompted. The -client will first check the \fBUSER\fR environment variable, then the -\fBLOGNAME\fR variable and if either exists, the -string is uppercased. If these environmental variables are not -found, the username GUEST is used. - -A third option is to use a credentials file which -contains the plaintext of the username and password. This -option is mainly provided for scripts where the admin does not -wish to pass the credentials on the command line or via environment -variables. If this method is used, make certain that the permissions -on the file restrict access from unwanted users. See the -\fI-A\fR for more details. - -Be cautious about including passwords in scripts. Also, on -many systems the command line of a running process may be seen -via the \fBps\fR command. To be safe always allow -\fBrpcclient\fR to prompt for a password and type -it in directly. +-U|--user=username[%password] +Sets the SMB username or username and password\&. + + +If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&. + + +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&. + + +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The smbtree man page was written by Jelmer Vernooij. +The smbtree man page was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/smbumount.8 b/docs/manpages/smbumount.8 index cadf8c53df..922cf5db84 100644 --- a/docs/manpages/smbumount.8 +++ b/docs/manpages/smbumount.8 @@ -1,44 +1,56 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SMBUMOUNT" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SMBUMOUNT" 8 "" "" "" .SH NAME smbumount \- smbfs umount for normal users -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBsmbumount\fR \fBmount-point\fR +.nf +\fBsmbumount\fR {mount-point} +.fi .SH "DESCRIPTION" + .PP -With this program, normal users can unmount smb-filesystems, -provided that it is suid root. \fBsmbumount\fR has -been written to give normal Linux users more control over their -resources. It is safe to install this program suid root, because only -the user who has mounted a filesystem is allowed to unmount it again. -For root it is not necessary to use smbumount. The normal umount -program works perfectly well, but it would certainly be problematic -to make umount setuid root. +With this program, normal users can unmount smb-filesystems, provided that it is suid root\&. \fBsmbumount\fR has been written to give normal Linux users more control over their resources\&. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again\&. For root it is not necessary to use smbumount\&. The normal umount program works perfectly well, but it would certainly be problematic to make umount setuid root\&. + .SH "OPTIONS" + .TP -\fBmount-point\fR -The directory to unmount. +mount-point +The directory to unmount\&. + + .SH "SEE ALSO" + .PP \fBsmbmount\fR(8) + .SH "AUTHOR" + .PP -Volker Lendecke, Andrew Tridgell, Michael H. Warfield -and others. +Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&. + .PP -The current maintainer of smbfs and the userspace -tools \fBsmbmount\fR, \fBsmbumount\fR, -and \fBsmbmnt\fR is Urban Widmark . -The SAMBA Mailing list -is the preferred place to ask questions regarding these programs. +The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&. + .PP -The conversion of this manpage for Samba 2.2 was performed -by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 -was done by Alexander Bokovoy. +The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/swat.8 b/docs/manpages/swat.8 index 1965b030b9..36d855e725 100644 --- a/docs/manpages/swat.8 +++ b/docs/manpages/swat.8 @@ -1,186 +1,184 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "SWAT" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "SWAT" 8 "" "" "" .SH NAME swat \- Samba Web Administration Tool -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBswat\fR [ \fB-s \fR ] [ \fB-a\fR ] +.nf +\fBswat\fR [-s ] [-a] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBswat\fR allows a Samba administrator to -configure the complex \fBsmb.conf\fR(5) file via a Web browser. In addition, -a \fBswat\fR configuration page has help links -to all the configurable options in the \fIsmb.conf\fR file allowing an -administrator to easily look up the effects of any change. +\fBswat\fR allows a Samba administrator to configure the complex \fBsmb.conf\fR(5) file via a Web browser\&. In addition, a \fBswat\fR configuration page has help links to all the configurable options in the \fIsmb\&.conf\fR file allowing an administrator to easily look up the effects of any change\&. + .PP \fBswat\fR is run from \fBinetd\fR + .SH "OPTIONS" + .TP -\fB-s smb configuration file\fR -The default configuration file path is -determined at compile time. The file specified contains -the configuration details required by the \fBsmbd\fR(8) server. This is the file -that \fBswat\fR will modify. -The information in this file includes server-specific -information such as what printcap file to use, as well as -descriptions of all the services that the server is to provide. -See \fIsmb.conf\fR for more information. +-s smb configuration file +The default configuration file path is determined at compile time\&. The file specified contains the configuration details required by the \fBsmbd\fR(8) server\&. This is the file that \fBswat\fR will modify\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fIsmb\&.conf\fR for more information\&. + + .TP -\fB-a\fR -This option disables authentication and puts -\fBswat\fR in demo mode. In that mode anyone will be able to modify -the \fIsmb.conf\fR file. +-a +This option disables authentication and puts \fBswat\fR in demo mode\&. In that mode anyone will be able to modify the \fIsmb\&.conf\fR file\&. + + +\fBWARNING: Do NOT enable this option on a production server\&. \fR + -\fBWARNING: Do NOT enable this option on a production -server. \fR .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .SH "INSTALLATION" + .PP -Swat is included as binary package with most distributions. The -package manager in this case takes care of the installation and -configuration. This section is only for those who have compiled -swat from scratch. +Swat is included as binary package with most distributions\&. The package manager in this case takes care of the installation and configuration\&. This section is only for those who have compiled swat from scratch\&. + .PP -After you compile SWAT you need to run \fBmake install -\fR to install the \fBswat\fR binary -and the various help files and images. A default install would put -these in: -.TP 0.2i +After you compile SWAT you need to run \fBmake install \fR to install the \fBswat\fR binary and the various help files and images\&. A default install would put these in: + +.TP 3 \(bu /usr/local/samba/bin/swat -.TP 0.2i + +.TP \(bu /usr/local/samba/swat/images/* -.TP 0.2i + +.TP \(bu /usr/local/samba/swat/help/* -.SS "INETD INSTALLATION" + +.LP + +.SS "Inetd Installation" + .PP -You need to edit your \fI/etc/inetd.conf -\fR and \fI/etc/services\fR -to enable SWAT to be launched via \fBinetd\fR. +You need to edit your \fI/etc/inetd\&.conf \fR and \fI/etc/services\fR to enable SWAT to be launched via \fBinetd\fR\&. + .PP -In \fI/etc/services\fR you need to -add a line like this: +In \fI/etc/services\fR you need to add a line like this: + .PP -\fBswat 901/tcp\fR +\fBswat 901/tcp\fR + .PP -Note for NIS/YP and LDAP users - you may need to rebuild the -NIS service maps rather than alter your local \fI /etc/services\fR file. +Note for NIS/YP and LDAP users - you may need to rebuild the NIS service maps rather than alter your local \fI /etc/services\fR file\&. + .PP -the choice of port number isn't really important -except that it should be less than 1024 and not currently -used (using a number above 1024 presents an obscure security -hole depending on the implementation details of your -\fBinetd\fR daemon). +the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your\fBinetd\fR daemon)\&. + .PP -In \fI/etc/inetd.conf\fR you should -add a line like this: +In \fI/etc/inetd\&.conf\fR you should add a line like this: + .PP -\fBswat stream tcp nowait.400 root -/usr/local/samba/bin/swat swat\fR +\fBswat stream tcp nowait.400 root /usr/local/samba/bin/swat swat\fR + .PP -One you have edited \fI/etc/services\fR -and \fI/etc/inetd.conf\fR you need to send a -HUP signal to inetd. To do this use \fBkill -1 PID -\fR where PID is the process ID of the inetd daemon. +One you have edited \fI/etc/services\fR and \fI/etc/inetd\&.conf\fR you need to send a HUP signal to inetd\&. To do this use \fBkill -1 PID \fR where PID is the process ID of the inetd daemon\&. + .SH "LAUNCHING" + .PP -To launch SWAT just run your favorite web browser and -point it at "http://localhost:901/". +To launch SWAT just run your favorite web browser and point it at "http://localhost:901/"\&. + .PP -Note that you can attach to SWAT from any IP connected -machine but connecting from a remote machine leaves your -connection open to password sniffing as passwords will be sent -in the clear over the wire. +Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire\&. + .SH "FILES" + .TP -\fB\fI/etc/inetd.conf\fB\fR -This file must contain suitable startup -information for the meta-daemon. +\fI/etc/inetd\&.conf\fR +This file must contain suitable startup information for the meta-daemon\&. + + .TP -\fB\fI/etc/services\fB\fR -This file must contain a mapping of service name -(e.g., swat) to service port (e.g., 901) and protocol type -(e.g., tcp). +\fI/etc/services\fR +This file must contain a mapping of service name (e\&.g\&., swat) to service port (e\&.g\&., 901) and protocol type (e\&.g\&., tcp)\&. + + .TP -\fB\fI/usr/local/samba/lib/smb.conf\fB\fR -This is the default location of the \fBsmb.conf\fR(5) server configuration file that swat edits. Other -common places that systems install this file are \fI /usr/samba/lib/smb.conf\fR and \fI/etc/smb.conf -\fR. This file describes all the services the server -is to make available to clients. +\fI/usr/local/samba/lib/smb\&.conf\fR +This is the default location of the \fBsmb.conf\fR(5) server configuration file that swat edits\&. Other common places that systems install this file are \fI /usr/samba/lib/smb\&.conf\fR and \fI/etc/smb\&.conf \fR\&. This file describes all the services the server is to make available to clients\&. + + .SH "WARNINGS" + .PP -\fBswat\fR will rewrite your \fBsmb.conf\fR(5) file. It will rearrange the entries and delete all -comments, \fIinclude=\fR and \fIcopy= -\fR options. If you have a carefully crafted \fI smb.conf\fR then back it up or don't use swat! +\fBswat\fR will rewrite your \fBsmb.conf\fR(5) file\&. It will rearrange the entries and delete all comments, \fIinclude=\fR and \fIcopy= \fR options\&. If you have a carefully crafted \fI smb\&.conf\fR then back it up or don't use swat! + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP \fBinetd(5)\fR, \fBsmbd\fR(8), \fBsmb.conf\fR(5) + .SH "AUTHOR" + +.PP +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. -.PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for -Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/testparm.1 b/docs/manpages/testparm.1 index ea8a84a4a5..4a6d788f79 100644 --- a/docs/manpages/testparm.1 +++ b/docs/manpages/testparm.1 @@ -1,112 +1,123 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "TESTPARM" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "TESTPARM" 1 "" "" "" .SH NAME -testparm \- check an smb.conf configuration file for internal correctness -.SH SYNOPSIS +testparm \- check an smb.conf configuration file for internal correctness +.SH "SYNOPSIS" -\fBtestparm\fR [ \fB-s\fR ] [ \fB-h\fR ] [ \fB-v\fR ] [ \fB-L \fR ] [ \fB-t \fR ] \fBconfig filename\fR [ \fBhostname hostIP\fR ] +.nf +\fBtestparm\fR [-s] [-h] [-v] [-L ] [-t ] {config filename} [hostname + hostIP] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBtestparm\fR is a very simple test program -to check an \fBsmbd\fR(8) configuration file for -internal correctness. If this program reports no problems, you -can use the configuration file with confidence that \fBsmbd -\fR will successfully load the configuration file. +\fBtestparm\fR is a very simple test program to check an \fBsmbd\fR(8) configuration file for internal correctness\&. If this program reports no problems, you can use the configuration file with confidence that \fBsmbd \fR will successfully load the configuration file\&. + .PP -Note that this is \fBNOT\fR a guarantee that -the services specified in the configuration file will be -available or will operate as expected. +Note that this is \fBNOT\fR a guarantee that the services specified in the configuration file will be available or will operate as expected\&. + .PP -If the optional host name and host IP address are -specified on the command line, this test program will run through -the service entries reporting whether the specified host -has access to each service. +If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host has access to each service\&. + .PP -If \fBtestparm\fR finds an error in the \fI smb.conf\fR file it returns an exit code of 1 to the calling -program, else it returns an exit code of 0. This allows shell scripts -to test the output from \fBtestparm\fR. +If \fBtestparm\fR finds an error in the \fI smb\&.conf\fR file it returns an exit code of 1 to the calling program, else it returns an exit code of 0\&. This allows shell scripts to test the output from \fBtestparm\fR\&. + .SH "OPTIONS" + .TP -\fB-s\fR -Without this option, \fBtestparm\fR -will prompt for a carriage return after printing the service -names and before dumping the service definitions. +-s +Without this option, \fBtestparm\fR will prompt for a carriage return after printing the service names and before dumping the service definitions\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-L servername\fR -Sets the value of the %L macro to \fIservername\fR. -This is useful for testing include files specified with the -%L macro. +-L servername +Sets the value of the %L macro to \fIservername\fR\&. This is useful for testing include files specified with the %L macro\&. + + .TP -\fB-v\fR -If this option is specified, testparm -will also output all options that were not used in \fBsmb.conf\fR(5) and are thus set to their defaults. +-v +If this option is specified, testparm will also output all options that were not used in \fBsmb.conf\fR(5) and are thus set to their defaults\&. + + .TP -\fB-t encoding\fR -Output data in specified encoding. +-t encoding +Output data in specified encoding\&. + + .TP -\fBconfigfilename\fR -This is the name of the configuration file -to check. If this parameter is not present then the -default \fBsmb.conf\fR(5) file will be checked. +configfilename +This is the name of the configuration file to check\&. If this parameter is not present then the default \fBsmb.conf\fR(5) file will be checked\&. + + .TP -\fBhostname\fR -If this parameter and the following are -specified, then \fBtestparm\fR will examine the \fIhosts -allow\fR and \fIhosts deny\fR -parameters in the \fBsmb.conf\fR(5) file to -determine if the hostname with this IP address would be -allowed access to the \fBsmbd\fR server. If -this parameter is supplied, the hostIP parameter must also -be supplied. +hostname +If this parameter and the following are specified, then \fBtestparm\fR will examine the \fIhosts allow\fR and \fIhosts deny\fR parameters in the \fBsmb.conf\fR(5) file to determine if the hostname with this IP address would be allowed access to the \fBsmbd\fR server\&. If this parameter is supplied, the hostIP parameter must also be supplied\&. + + .TP -\fBhostIP\fR -This is the IP address of the host specified -in the previous parameter. This address must be supplied -if the hostname parameter is supplied. +hostIP +This is the IP address of the host specified in the previous parameter\&. This address must be supplied if the hostname parameter is supplied\&. + + .SH "FILES" + .TP -\fBsmb.conf(5)\fR -This is usually the name of the configuration -file used by \fBsmbd\fR(8). +\fBsmb.conf\fR(5) +This is usually the name of the configuration file used by \fBsmbd\fR(8)\&. + + .SH "DIAGNOSTICS" + .PP -The program will issue a message saying whether the -configuration file loaded OK or not. This message may be preceded by -errors and warnings if the file did not load. If the file was -loaded OK, the program then dumps all known service details -to stdout. +The program will issue a message saying whether the configuration file loaded OK or not\&. This message may be preceded by errors and warnings if the file did not load\&. If the file was loaded OK, the program then dumps all known service details to stdout\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP \fBsmb.conf\fR(5), \fBsmbd\fR(8) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/testprns.1 b/docs/manpages/testprns.1 index cb231510f5..9f98ea1d59 100644 --- a/docs/manpages/testprns.1 +++ b/docs/manpages/testprns.1 @@ -1,90 +1,96 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "TESTPRNS" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "TESTPRNS" 1 "" "" "" .SH NAME testprns \- check printer name for validity with smbd -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBtestprns\fR \fBprintername\fR [ \fBprintcapname\fR ] +.nf +\fBtestprns\fR {printername} [printcapname] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBtestprns\fR is a very simple test program -to determine whether a given printer name is valid for use in -a service to be provided by \fBsmbd\fR(8). +\fBtestprns\fR is a very simple test program to determine whether a given printer name is valid for use in a service to be provided by \fBsmbd\fR(8)\&. + .PP -"Valid" in this context means "can be found in the -printcap specified". This program is very stupid - so stupid in -fact that it would be wisest to always specify the printcap file -to use. +"Valid" in this context means "can be found in the printcap specified"\&. This program is very stupid - so stupid in fact that it would be wisest to always specify the printcap file to use\&. + .SH "OPTIONS" + .TP -\fBprintername\fR -The printer name to validate. - -Printer names are taken from the first field in each -record in the printcap file, single printer names and sets -of aliases separated by vertical bars ("|") are recognized. -Note that no validation or checking of the printcap syntax is -done beyond that required to extract the printer name. It may -be that the print spooling system is more forgiving or less -forgiving than \fBtestprns\fR. However, if -\fBtestprns\fR finds the printer then \fBsmbd\fR(8) should do so as well. +printername +The printer name to validate\&. + + +Printer names are taken from the first field in each record in the printcap file, single printer names and sets of aliases separated by vertical bars ("|") are recognized\&. Note that no validation or checking of the printcap syntax is done beyond that required to extract the printer name\&. It may be that the print spooling system is more forgiving or less forgiving than \fBtestprns\fR\&. However, if \fBtestprns\fR finds the printer then \fBsmbd\fR(8) should do so as well\&. + + .TP -\fBprintcapname\fR -This is the name of the printcap file within -which to search for the given printer name. +printcapname +This is the name of the printcap file within which to search for the given printer name\&. + + +If no printcap name is specified \fBtestprns \fR will attempt to scan the printcap file name specified at compile time\&. + -If no printcap name is specified \fBtestprns -\fR will attempt to scan the printcap file name -specified at compile time. .SH "FILES" + .TP -\fB\fI/etc/printcap\fB\fR -This is usually the default printcap -file to scan. See \fIprintcap (5)\fR. +\fI/etc/printcap\fR +This is usually the default printcap file to scan\&. See \fIprintcap (5)\fR\&. + + .SH "DIAGNOSTICS" + .PP -If a printer is found to be valid, the message -"Printer name is valid" will be -displayed. +If a printer is found to be valid, the message "Printer name is valid" will be displayed\&. + .PP -If a printer is found to be invalid, the message -"Printer name is not valid" will be -displayed. +If a printer is found to be invalid, the message "Printer name is not valid" will be displayed\&. + .PP -All messages that would normally be logged during -operation of the Samba daemons are logged by this program to the -file \fItest.log\fR in the current directory. The -program runs at debuglevel 3, so quite extensive logging -information is written. The log should be checked carefully -for errors and warnings. +All messages that would normally be logged during operation of the Samba daemons are logged by this program to the file \fItest\&.log\fR in the current directory\&. The program runs at debuglevel 3, so quite extensive logging information is written\&. The log should be checked carefully for errors and warnings\&. + .PP -Other messages are self-explanatory. +Other messages are self-explanatory\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fIprintcap(5)\fR, -\fBsmbd\fR(8), \fBsmbclient\fR(1) +\fIprintcap(5)\fR,\fBsmbd\fR(8), \fBsmbclient\fR(1) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The original Samba man pages were written by Karl Auer. -The man page sources were converted to YODL format (another -excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ ) and updated for the Samba 2.0 -release by Jeremy Allison. The conversion to DocBook for -Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 -for Samba 3.0 was done by Alexander Bokovoy. +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/vfstest.1 b/docs/manpages/vfstest.1 index fb9fa0efd0..a6d01fba57 100644 --- a/docs/manpages/vfstest.1 +++ b/docs/manpages/vfstest.1 @@ -1,215 +1,271 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "VFSTEST" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "VFSTEST" 1 "" "" "" .SH NAME vfstest \- tool for testing samba VFS modules -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBvfstest\fR [ \fB-d debuglevel\fR ] [ \fB-c command\fR ] [ \fB-l logfile\fR ] [ \fB-h\fR ] +.nf +\fBvfstest\fR [-d debuglevel] [-c command] [-l logfile] [-h] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -\fBvfstest\fR is a small command line -utility that has the ability to test dso samba VFS modules. It gives the -user the ability to call the various VFS functions manually and -supports cascaded VFS modules. +\fBvfstest\fR is a small command line utility that has the ability to test dso samba VFS modules\&. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules\&. + .SH "OPTIONS" + +.TP +-c|--command=command +Execute the specified (colon-separated) commands\&. See below for the commands that are available\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + +.TP +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB'\&.client'\fR will be appended\&. The log file is never removed by the client\&. + + +.TP +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + +.TP +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-c|--command=command\fR -Execute the specified (colon-separated) commands. -See below for the commands that are available. -.TP -\fB-h|--help\fR -Print a summary of command line options. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -\&'.client' will be appended. The log file is never removed -by the client. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. -.TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. -.TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .SH "COMMANDS" + .PP \fBVFS COMMANDS\fR -.TP 0.2i + +.TP 3 \(bu -\fBload \fR - Load specified VFS module -.TP 0.2i +\fBload \fR - Load specified VFS module + +.TP \(bu \fBpopulate \fR - Populate a data buffer with the specified data -.TP 0.2i + +.TP \(bu \fBshowdata [ ]\fR - Show data currently in data buffer -.TP 0.2i + +.TP \(bu \fBconnect\fR - VFS connect() -.TP 0.2i + +.TP \(bu \fBdisconnect\fR - VFS disconnect() -.TP 0.2i + +.TP \(bu \fBdisk_free\fR - VFS disk_free() -.TP 0.2i + +.TP \(bu \fBopendir\fR - VFS opendir() -.TP 0.2i + +.TP \(bu \fBreaddir\fR - VFS readdir() -.TP 0.2i + +.TP \(bu \fBmkdir\fR - VFS mkdir() -.TP 0.2i + +.TP \(bu \fBrmdir\fR - VFS rmdir() -.TP 0.2i + +.TP \(bu \fBclosedir\fR - VFS closedir() -.TP 0.2i + +.TP \(bu \fBopen\fR - VFS open() -.TP 0.2i + +.TP \(bu \fBclose\fR - VFS close() -.TP 0.2i + +.TP \(bu \fBread\fR - VFS read() -.TP 0.2i + +.TP \(bu \fBwrite\fR - VFS write() -.TP 0.2i + +.TP \(bu \fBlseek\fR - VFS lseek() -.TP 0.2i + +.TP \(bu \fBrename\fR - VFS rename() -.TP 0.2i + +.TP \(bu \fBfsync\fR - VFS fsync() -.TP 0.2i + +.TP \(bu \fBstat\fR - VFS stat() -.TP 0.2i + +.TP \(bu \fBfstat\fR - VFS fstat() -.TP 0.2i + +.TP \(bu \fBlstat\fR - VFS lstat() -.TP 0.2i + +.TP \(bu \fBunlink\fR - VFS unlink() -.TP 0.2i + +.TP \(bu \fBchmod\fR - VFS chmod() -.TP 0.2i + +.TP \(bu \fBfchmod\fR - VFS fchmod() -.TP 0.2i + +.TP \(bu \fBchown\fR - VFS chown() -.TP 0.2i + +.TP \(bu \fBfchown\fR - VFS fchown() -.TP 0.2i + +.TP \(bu \fBchdir\fR - VFS chdir() -.TP 0.2i + +.TP \(bu \fBgetwd\fR - VFS getwd() -.TP 0.2i + +.TP \(bu \fButime\fR - VFS utime() -.TP 0.2i + +.TP \(bu \fBftruncate\fR - VFS ftruncate() -.TP 0.2i + +.TP \(bu \fBlock\fR - VFS lock() -.TP 0.2i + +.TP \(bu \fBsymlink\fR - VFS symlink() -.TP 0.2i + +.TP \(bu \fBreadlink\fR - VFS readlink() -.TP 0.2i + +.TP \(bu \fBlink\fR - VFS link() -.TP 0.2i + +.TP \(bu \fBmknod\fR - VFS mknod() -.TP 0.2i + +.TP \(bu \fBrealpath\fR - VFS realpath() + +.LP + .PP \fBGENERAL COMMANDS\fR -.TP 0.2i + +.TP 3 \(bu \fBconf \fR - Load a different configuration file -.TP 0.2i + +.TP \(bu \fBhelp []\fR - Get list of commands or info about specified command -.TP 0.2i + +.TP \(bu \fBdebuglevel \fR - Set debug level -.TP 0.2i + +.TP \(bu \fBfreemem\fR - Free memory currently in use -.TP 0.2i + +.TP \(bu \fBexit\fR - Exit vfstest + +.LP + .SH "VERSION" + .PP -This man page is correct for version 3.0 of the Samba -suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -The vfstest man page was written by Jelmer Vernooij. +The vfstest man page was written by Jelmer Vernooij\&. + diff --git a/docs/manpages/wbinfo.1 b/docs/manpages/wbinfo.1 index 18dbcbf306..0481489078 100644 --- a/docs/manpages/wbinfo.1 +++ b/docs/manpages/wbinfo.1 @@ -1,159 +1,169 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "WBINFO" "1" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "WBINFO" 1 "" "" "" .SH NAME wbinfo \- Query information from winbind daemon -.SH SYNOPSIS +.SH "SYNOPSIS" -\fBwbinfo\fR [ \fB-u\fR ] [ \fB-g\fR ] [ \fB-N netbios-name\fR ] [ \fB-I ip\fR ] [ \fB-n name\fR ] [ \fB-s sid\fR ] [ \fB-U uid\fR ] [ \fB-G gid\fR ] [ \fB-S sid\fR ] [ \fB-Y sid\fR ] [ \fB-t\fR ] [ \fB-m\fR ] [ \fB--sequence\fR ] [ \fB-r user\fR ] [ \fB-a user%password\fR ] [ \fB-A user%password\fR ] [ \fB--get-auth-user\fR ] [ \fB-p\fR ] +.nf +\fBwbinfo\fR [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] + [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] + [-A user%password] [--get-auth-user] [-p] +.fi .SH "DESCRIPTION" + .PP -This tool is part of the \fBSamba\fR(7) suite. +This tool is part of the \fBSamba\fR(7) suite\&. + .PP -The \fBwbinfo\fR program queries and returns information -created and used by the \fBwinbindd\fR(8) daemon. +The \fBwbinfo\fR program queries and returns information created and used by the \fBwinbindd\fR(8) daemon\&. + .PP -The \fBwinbindd\fR(8) daemon must be configured -and running for the \fBwbinfo\fR program to be able -to return information. +The \fBwinbindd\fR(8) daemon must be configured and running for the \fBwbinfo\fR program to be able to return information\&. + .SH "OPTIONS" + +.TP +-u +This option will list all users available in the Windows NT domain for which the \fBwinbindd\fR(8) daemon is operating in\&. Users in all trusted domains will also be listed\&. Note that this operation does not assign user ids to any users that have not already been seen by \fBwinbindd\fR(8) \&. + + +.TP +-g +This option will list all groups available in the Windows NT domain for which the \fBSamba\fR(7) daemon is operating in\&. Groups in all trusted domains will also be listed\&. Note that this operation does not assign group ids to any groups that have not already been seen by \fBwinbindd\fR(8)\&. + + +.TP +-N name +The \fI-N\fR option queries \fBwinbindd\fR(8) to query the WINS server for the IP address associated with the NetBIOS name specified by the \fIname\fR parameter\&. + + +.TP +-I ip +The \fI-I\fR option queries \fBwinbindd\fR(8) to send a node status request to get the NetBIOS name associated with the IP address specified by the \fIip\fR parameter\&. + + .TP -\fB-u\fR -This option will list all users available -in the Windows NT domain for which the \fBwinbindd\fR(8) daemon is operating in. Users in all trusted domains -will also be listed. Note that this operation does not assign -user ids to any users that have not already been seen by \fBwinbindd\fR(8) -\&. -.TP -\fB-g\fR -This option will list all groups available -in the Windows NT domain for which the \fBSamba\fR(7) daemon is operating in. Groups in all trusted domains -will also be listed. Note that this operation does not assign -group ids to any groups that have not already been -seen by \fBwinbindd\fR(8). -.TP -\fB-N name\fR -The \fI-N\fR option -queries \fBwinbindd\fR(8) to query the WINS -server for the IP address associated with the NetBIOS name -specified by the \fIname\fR parameter. -.TP -\fB-I ip\fR -The \fI-I\fR option -queries \fBwinbindd\fR(8) to send a node status -request to get the NetBIOS name associated with the IP address -specified by the \fIip\fR parameter. -.TP -\fB-n name\fR -The \fI-n\fR option -queries \fBwinbindd\fR(8) for the SID -associated with the name specified. Domain names can be specified -before the user name by using the winbind separator character. -For example CWDOM1/Administrator refers to the Administrator -user in the domain CWDOM1. If no domain is specified then the -domain used is the one specified in the \fBsmb.conf\fR(5) \fIworkgroup -\fR parameter. -.TP -\fB-s sid\fR -Use \fI-s\fR to resolve -a SID to a name. This is the inverse of the \fI-n -\fR option above. SIDs must be specified as ASCII strings -in the traditional Microsoft format. For example, -S-1-5-21-1455342024-3071081365-2475485837-500. -.TP -\fB-U uid\fR -Try to convert a UNIX user id to a Windows NT -SID. If the uid specified does not refer to one within -the winbind uid range then the operation will fail. -.TP -\fB-G gid\fR -Try to convert a UNIX group id to a Windows -NT SID. If the gid specified does not refer to one within -the winbind gid range then the operation will fail. -.TP -\fB-S sid\fR -Convert a SID to a UNIX user id. If the SID -does not correspond to a UNIX user mapped by \fBwinbindd\fR(8) then the operation will fail. -.TP -\fB-Y sid\fR -Convert a SID to a UNIX group id. If the SID -does not correspond to a UNIX group mapped by \fBwinbindd\fR(8) then -the operation will fail. -.TP -\fB-t\fR -Verify that the workstation trust account -created when the Samba server is added to the Windows NT -domain is working. -.TP -\fB-m\fR -Produce a list of domains trusted by the -Windows NT server \fBwinbindd\fR(8) contacts -when resolving names. This list does not include the Windows -NT domain the server is a Primary Domain Controller for. -.TP -\fB--sequence\fR -Show sequence numbers of -all known domains -.TP -\fB-r username\fR -Try to obtain the list of UNIX group ids -to which the user belongs. This only works for users -defined on a Domain Controller. -.TP -\fB-a username%password\fR -Attempt to authenticate a user via winbindd. -This checks both authenticaion methods and reports its results. -.TP -\fB-A username%password\fR -Store username and password used by winbindd -during session setup to a domain controller. This enables -winbindd to operate in a Windows 2000 domain with Restrict -Anonymous turned on (a.k.a. Permissions compatiable with -Windows 2000 servers only). -.TP -\fB--get-auth-user\fR -Print username and password used by winbindd -during session setup to a domain controller. Username -and password can be set using '-A'. Only available for -root. -.TP -\fB-p\fR -Check whether winbindd is still alive. -Prints out either 'succeeded' or 'failed'. -.TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. -.TP -\fB-h|--help\fR -Print a summary of command line options. +-n name +The \fI-n\fR option queries \fBwinbindd\fR(8) for the SID associated with the name specified\&. Domain names can be specified before the user name by using the winbind separator character\&. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1\&. If no domain is specified then the domain used is the one specified in the \fBsmb.conf\fR(5) \fIworkgroup \fR parameter\&. + + +.TP +-s sid +Use \fI-s\fR to resolve a SID to a name\&. This is the inverse of the \fI-n \fR option above\&. SIDs must be specified as ASCII strings in the traditional Microsoft format\&. For example, S-1-5-21-1455342024-3071081365-2475485837-500\&. + + +.TP +-U uid +Try to convert a UNIX user id to a Windows NT SID\&. If the uid specified does not refer to one within the winbind uid range then the operation will fail\&. + + +.TP +-G gid +Try to convert a UNIX group id to a Windows NT SID\&. If the gid specified does not refer to one within the winbind gid range then the operation will fail\&. + + +.TP +-S sid +Convert a SID to a UNIX user id\&. If the SID does not correspond to a UNIX user mapped by \fBwinbindd\fR(8) then the operation will fail\&. + + +.TP +-Y sid +Convert a SID to a UNIX group id\&. If the SID does not correspond to a UNIX group mapped by \fBwinbindd\fR(8) then the operation will fail\&. + + +.TP +-t +Verify that the workstation trust account created when the Samba server is added to the Windows NT domain is working\&. + + +.TP +-m +Produce a list of domains trusted by the Windows NT server \fBwinbindd\fR(8) contacts when resolving names\&. This list does not include the Windows NT domain the server is a Primary Domain Controller for\&. + + +.TP +--sequence +Show sequence numbers of all known domains + + +.TP +-r username +Try to obtain the list of UNIX group ids to which the user belongs\&. This only works for users defined on a Domain Controller\&. + + +.TP +-a username%password +Attempt to authenticate a user via winbindd\&. This checks both authenticaion methods and reports its results\&. + + +.TP +-A username%password +Store username and password used by winbindd during session setup to a domain controller\&. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a\&.k\&.a\&. Permissions compatiable with Windows 2000 servers only)\&. + + +.TP +--get-auth-user +Print username and password used by winbindd during session setup to a domain controller\&. Username and password can be set using '-A'\&. Only available for root\&. + + +.TP +-p +Check whether winbindd is still alive\&. Prints out either 'succeeded' or 'failed'\&. + + +.TP +-V +Prints the version number for \fBsmbd\fR\&. + + +.TP +-h|--help +Print a summary of command line options\&. + + .SH "EXIT STATUS" + .PP -The wbinfo program returns 0 if the operation -succeeded, or 1 if the operation failed. If the \fBwinbindd\fR(8) daemon is not working \fBwbinfo\fR will always return -failure. +The wbinfo program returns 0 if the operation succeeded, or 1 if the operation failed\&. If the \fBwinbindd\fR(8) daemon is not working \fBwbinfo\fR will always return failure\&. + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP \fBwinbindd\fR(8) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -\fBwbinfo\fR and \fBwinbindd\fR -were written by Tim Potter. +\fBwbinfo\fR and \fBwinbindd\fR were written by Tim Potter\&. + .PP -The conversion to DocBook for Samba 2.2 was done -by Gerald Carter. The conversion to DocBook XML 4.2 for Samba -3.0 was done by Alexander Bokovoy. +The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + diff --git a/docs/manpages/winbindd.8 b/docs/manpages/winbindd.8 index 00a28ab36f..31ed3ba332 100644 --- a/docs/manpages/winbindd.8 +++ b/docs/manpages/winbindd.8 @@ -1,266 +1,240 @@ -.\" This manpage has been automatically generated by docbook2man -.\" from a DocBook document. This tool can be found at: -.\" -.\" Please send any bug reports, improvements, comments, patches, -.\" etc. to Steve Cheng . -.TH "WINBINDD" "8" "19 april 2003" "" "" - +.\"Generated by db2man.xsl. Don't modify this, modify the source. +.de Sh \" Subsection +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Ip \" List item +.br +.ie \\n(.$>=3 .ne \\$3 +.el .ne 3 +.IP "\\$1" \\$2 +.. +.TH "WINBINDD" 8 "" "" "" .SH NAME -winbindd \- Name Service Switch daemon for resolving names from NT servers -.SH SYNOPSIS +winbindd \- Name Service Switch daemon for resolving names from NT servers +.SH "SYNOPSIS" -\fBwinbindd\fR [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-i\fR ] [ \fB-B\fR ] [ \fB-d \fR ] [ \fB-s \fR ] [ \fB-n\fR ] +.nf +\fBwinbindd\fR [-F] [-S] [-i] [-B] [-d ] [-s ] [-n] +.fi .SH "DESCRIPTION" + .PP -This program is part of the \fBSamba\fR(7) suite. -.PP -\fBwinbindd\fR is a daemon that provides -a service for the Name Service Switch capability that is present -in most modern C libraries. The Name Service Switch allows user -and system information to be obtained from different databases -services such as NIS or DNS. The exact behaviour can be configured -throught the \fI/etc/nsswitch.conf\fR file. -Users and groups are allocated as they are resolved to a range -of user and group ids specified by the administrator of the -Samba system. -.PP -The service provided by \fBwinbindd\fR is called `winbind' and -can be used to resolve user and group information from a -Windows NT server. The service can also provide authentication -services via an associated PAM module. -.PP -The \fIpam_winbind\fR module in the 2.2.2 release only -supports the \fIauth\fR and \fIaccount\fR -module-types. The latter simply -performs a getpwnam() to verify that the system can obtain a uid for the -user. If the \fIlibnss_winbind\fR library has been correctly -installed, this should always succeed. -.PP -The following nsswitch databases are implemented by -the winbindd service: +This program is part of the \fBSamba\fR(7) suite\&. + +.PP +\fBwinbindd\fR is a daemon that provides a service for the Name Service Switch capability that is present in most modern C libraries\&. The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS\&. The exact behaviour can be configured throught the \fI/etc/nsswitch\&.conf\fR file\&. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system\&. + +.PP +The service provided by \fBwinbindd\fR is called `winbind' and can be used to resolve user and group information from a Windows NT server\&. The service can also provide authentication services via an associated PAM module\&. + +.PP +The \fIpam_winbind\fR module in the 2\&.2\&.2 release only supports the \fIauth\fR and \fIaccount\fR module-types\&. The latter simply performs a getpwnam() to verify that the system can obtain a uid for the user\&. If the \fIlibnss_winbind\fR library has been correctly installed, this should always succeed\&. + +.PP +The following nsswitch databases are implemented by the winbindd service: + .TP -\fBhosts\fR -User information traditionally stored in -the \fIhosts(5)\fR file and used by -\fBgethostbyname(3)\fR functions. Names are -resolved through the WINS server or by broadcast. +hosts +User information traditionally stored in the \fIhosts(5)\fR file and used by \fBgethostbyname(3)\fR functions\&. Names are resolved through the WINS server or by broadcast\&. + + .TP -\fBpasswd\fR -User information traditionally stored in -the \fIpasswd(5)\fR file and used by -\fBgetpwent(3)\fR functions. +passwd +User information traditionally stored in the \fIpasswd(5)\fR file and used by \fBgetpwent(3)\fR functions\&. + + .TP -\fBgroup\fR -Group information traditionally stored in -the \fIgroup(5)\fR file and used by -\fBgetgrent(3)\fR functions. -.PP -For example, the following simple configuration in the -\fI/etc/nsswitch.conf\fR file can be used to initially -resolve user and group information from \fI/etc/passwd -\fR and \fI/etc/group\fR and then from the -Windows NT server. +group +Group information traditionally stored in the \fIgroup(5)\fR file and used by \fBgetgrent(3)\fR functions\&. + +.PP +For example, the following simple configuration in the\fI/etc/nsswitch\&.conf\fR file can be used to initially resolve user and group information from \fI/etc/passwd \fR and \fI/etc/group\fR and then from the Windows NT server\&. .nf + passwd: files winbind group: files winbind .fi + + .PP -The following simple configuration in the -\fI/etc/nsswitch.conf\fR file can be used to initially -resolve hostnames from \fI/etc/hosts\fR and then from the -WINS server. +The following simple configuration in the\fI/etc/nsswitch\&.conf\fR file can be used to initially resolve hostnames from \fI/etc/hosts\fR and then from the WINS server\&. + .SH "OPTIONS" + .TP -\fB-F\fR -If specified, this parameter causes -the main \fBwinbindd\fR process to not daemonize, -i.e. double-fork and disassociate with the terminal. -Child processes are still created as normal to service -each connection request, but the main process does not -exit. This operation mode is suitable for running -\fBwinbindd\fR under process supervisors such -as \fBsupervise\fR and \fBsvscan\fR -from Daniel J. Bernstein's \fBdaemontools\fR -package, or the AIX process monitor. +-F +If specified, this parameter causes the main \fBwinbindd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBwinbindd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&. + + .TP -\fB-S\fR -If specified, this parameter causes -\fBwinbindd\fR to log to standard output rather -than a file. +-S +If specified, this parameter causes \fBwinbindd\fR to log to standard output rather than a file\&. + + .TP -\fB-V\fR -Prints the version number for -\fBsmbd\fR. +-V +Prints the version number for \fBsmbd\fR\&. + + .TP -\fB-s \fR -The file specified contains the -configuration details required by the server. The -information in this file includes server-specific -information such as what printcap file to use, as well -as descriptions of all the services that the server is -to provide. See \fIsmb.conf(5)\fR for more information. -The default configuration file name is determined at -compile time. +-s +The file specified contains the configuration details required by the server\&. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&. + + .TP -\fB-d|--debug=debuglevel\fR -\fIdebuglevel\fR is an integer -from 0 to 10. The default value if this parameter is -not specified is zero. - -The higher this value, the more detail will be -logged to the log files about the activities of the -server. At level 0, only critical errors and serious -warnings will be logged. Level 1 is a reasonable level for -day to day running - it generates a small amount of -information about operations carried out. - -Levels above 1 will generate considerable -amounts of log data, and should only be used when -investigating a problem. Levels above 3 are designed for -use only by developers and generate HUGE amounts of log -data, most of which is extremely cryptic. - -Note that specifying this parameter here will -override the log -level file. +-d|--debug=debuglevel +\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&. + + +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out\&. + + +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&. + + +Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&. + + .TP -\fB-l|--logfile=logbasename\fR -File name for log/debug files. The extension -".client" will be appended. The log file is -never removed by the client. +-l|--logfile=logbasename +File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&. + + .TP -\fB-h|--help\fR -Print a summary of command line options. +-h|--help +Print a summary of command line options\&. + + .TP -\fB-i\fR -Tells \fBwinbindd\fR to not -become a daemon and detach from the current terminal. This -option is used by developers when interactive debugging -of \fBwinbindd\fR is required. -\fBwinbindd\fR also logs to standard output, -as if the \fB-S\fR parameter had been given. +-i +Tells \fBwinbindd\fR to not become a daemon and detach from the current terminal\&. This option is used by developers when interactive debugging of \fBwinbindd\fR is required\&. \fBwinbindd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&. + + .TP -\fB-n\fR -Disable caching. This means winbindd will -always have to wait for a response from the domain controller -before it can respond to a client and this thus makes things -slower. The results will however be more accurate, since -results from the cache might not be up-to-date. This -might also temporarily hang winbindd if the DC doesn't respond. +-n +Disable caching\&. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower\&. The results will however be more accurate, since results from the cache might not be up-to-date\&. This might also temporarily hang winbindd if the DC doesn't respond\&. + + .TP -\fB-B\fR -Dual daemon mode. This means winbindd will run -as 2 threads. The first will answer all requests from the cache, -thus making responses to clients faster. The other will -update the cache for the query that the first has just responded. -Advantage of this is that responses stay accurate and are faster. +-B +Dual daemon mode\&. This means winbindd will run as 2 threads\&. The first will answer all requests from the cache, thus making responses to clients faster\&. The other will update the cache for the query that the first has just responded\&. Advantage of this is that responses stay accurate and are faster\&. + + .SH "NAME AND ID RESOLUTION" + +.PP +Users and groups on a Windows NT server are assigned a relative id (rid) which is unique for the domain when the user or group is created\&. To convert the Windows NT user or group into a unix user or group, a mapping between rids and unix user and group ids is required\&. This is one of the jobs that \fB winbindd\fR performs\&. + +.PP +As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range\&. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command\&. The allocated unix ids are stored in a database file under the Samba lock directory and will be remembered\&. + .PP -Users and groups on a Windows NT server are assigned -a relative id (rid) which is unique for the domain when the -user or group is created. To convert the Windows NT user or group -into a unix user or group, a mapping between rids and unix user -and group ids is required. This is one of the jobs that \fB winbindd\fR performs. -.PP -As winbindd users and groups are resolved from a server, user -and group ids are allocated from a specified range. This -is done on a first come, first served basis, although all existing -users and groups will be mapped as soon as a client performs a user -or group enumeration command. The allocated unix ids are stored -in a database file under the Samba lock directory and will be -remembered. -.PP -WARNING: The rid to unix id database is the only location -where the user and group mappings are stored by winbindd. If this -file is deleted or corrupted, there is no way for winbindd to -determine which user and group ids correspond to Windows NT user -and group rids. +WARNING: The rid to unix id database is the only location where the user and group mappings are stored by winbindd\&. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids\&. + .SH "CONFIGURATION" + .PP -Configuration of the \fBwinbindd\fR daemon -is done through configuration parameters in the \fBsmb.conf\fR(5) file. All parameters should be specified in the -[global] section of smb.conf. -.TP 0.2i +Configuration of the \fBwinbindd\fR daemon is done through configuration parameters in the \fBsmb.conf\fR(5) file\&. All parameters should be specified in the [global] section of smb\&.conf\&. + +.TP 3 \(bu \fIwinbind separator\fR -.TP 0.2i + +.TP \(bu \fIwinbind uid\fR -.TP 0.2i + +.TP \(bu \fIwinbind gid\fR -.TP 0.2i + +.TP \(bu \fIwinbind cache time\fR -.TP 0.2i + +.TP \(bu \fIwinbind enum users\fR -.TP 0.2i + +.TP \(bu \fIwinbind enum groups\fR -.TP 0.2i + +.TP \(bu \fItemplate homedir\fR -.TP 0.2i + +.TP \(bu \fItemplate shell\fR -.TP 0.2i + +.TP \(bu \fIwinbind use default domain\fR + +.LP + .SH "EXAMPLE SETUP" + .PP -To setup winbindd for user and group lookups plus -authentication from a domain controller use something like the -following setup. This was tested on a RedHat 6.2 Linux box. -.PP -In \fI/etc/nsswitch.conf\fR put the -following: +To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup\&. This was tested on a RedHat 6\&.2 Linux box\&. +.PP +In \fI/etc/nsswitch\&.conf\fR put the following: .nf + passwd: files winbind group: files winbind .fi -.PP -In \fI/etc/pam.d/*\fR replace the \fI auth\fR lines with something like this: + +.PP +In \fI/etc/pam\&.d/*\fR replace the \fI auth\fR lines with something like this: .nf -auth required /lib/security/pam_securetty.so -auth required /lib/security/pam_nologin.so -auth sufficient /lib/security/pam_winbind.so -auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok + +auth required /lib/security/pam_securetty\&.so +auth required /lib/security/pam_nologin\&.so +auth sufficient /lib/security/pam_winbind\&.so +auth required /lib/security/pam_pwdb\&.so use_first_pass shadow nullok .fi + + .PP -Note in particular the use of the \fIsufficient -\fR keyword and the \fIuse_first_pass\fR keyword. +Note in particular the use of the \fIsufficient \fR keyword and the \fIuse_first_pass\fR keyword\&. + .PP -Now replace the account lines with this: +Now replace the account lines with this: + .PP -\fBaccount required /lib/security/pam_winbind.so -\fR +\fBaccount required /lib/security/pam_winbind.so \fR + .PP -The next step is to join the domain. To do that use the -\fBnet\fR program like this: +The next step is to join the domain\&. To do that use the\fBnet\fR program like this: + .PP \fBnet join -S PDC -U Administrator\fR + .PP -The username after the \fI-U\fR can be any -Domain user that has administrator privileges on the machine. -Substitute the name or IP of your PDC for "PDC". -.PP -Next copy \fIlibnss_winbind.so\fR to -\fI/lib\fR and \fIpam_winbind.so -\fR to \fI/lib/security\fR. A symbolic link needs to be -made from \fI/lib/libnss_winbind.so\fR to -\fI/lib/libnss_winbind.so.2\fR. If you are using an -older version of glibc then the target of the link should be -\fI/lib/libnss_winbind.so.1\fR. +The username after the \fI-U\fR can be any Domain user that has administrator privileges on the machine\&. Substitute the name or IP of your PDC for "PDC"\&. + .PP -Finally, setup a \fBsmb.conf\fR(5) containing directives like the -following: +Next copy \fIlibnss_winbind\&.so\fR to\fI/lib\fR and \fIpam_winbind\&.so \fR to \fI/lib/security\fR\&. A symbolic link needs to be made from \fI/lib/libnss_winbind\&.so\fR to\fI/lib/libnss_winbind\&.so\&.2\fR\&. If you are using an older version of glibc then the target of the link should be\fI/lib/libnss_winbind\&.so\&.1\fR\&. +.PP +Finally, setup a \fBsmb.conf\fR(5) containing directives like the following: .nf + [global] winbind separator = + winbind cache time = 10 @@ -272,109 +246,96 @@ following: security = domain password server = * .fi + + .PP -Now start winbindd and you should find that your user and -group database is expanded to include your NT users and groups, -and that you can login to your unix box as a domain user, using -the DOMAIN+user syntax for the username. You may wish to use the -commands \fBgetent passwd\fR and \fBgetent group -\fR to confirm the correct operation of winbindd. +Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username\&. You may wish to use the commands \fBgetent passwd\fR and \fBgetent group \fR to confirm the correct operation of winbindd\&. + .SH "NOTES" + .PP -The following notes are useful when configuring and -running \fBwinbindd\fR: +The following notes are useful when configuring and running \fBwinbindd\fR: + .PP -\fBnmbd\fR(8) must be running on the local machine -for \fBwinbindd\fR to work. \fBwinbindd\fR queries -the list of trusted domains for the Windows NT server -on startup and when a SIGHUP is received. Thus, for a running \fB winbindd\fR to become aware of new trust relationships between -servers, it must be sent a SIGHUP signal. +\fBnmbd\fR(8) must be running on the local machine for \fBwinbindd\fR to work\&. \fBwinbindd\fR queries the list of trusted domains for the Windows NT server on startup and when a SIGHUP is received\&. Thus, for a running \fB winbindd\fR to become aware of new trust relationships between servers, it must be sent a SIGHUP signal\&. + .PP -PAM is really easy to misconfigure. Make sure you know what -you are doing when modifying PAM configuration files. It is possible -to set up PAM such that you can no longer log into your system. +PAM is really easy to misconfigure\&. Make sure you know what you are doing when modifying PAM configuration files\&. It is possible to set up PAM such that you can no longer log into your system\&. + .PP -If more than one UNIX machine is running \fBwinbindd\fR, -then in general the user and groups ids allocated by winbindd will not -be the same. The user and group ids will only be valid for the local -machine. +If more than one UNIX machine is running \fBwinbindd\fR, then in general the user and groups ids allocated by winbindd will not be the same\&. The user and group ids will only be valid for the local machine\&. + .PP -If the the Windows NT RID to UNIX user and group id mapping -file is damaged or destroyed then the mappings will be lost. +If the the Windows NT RID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost\&. + .SH "SIGNALS" + .PP -The following signals can be used to manipulate the -\fBwinbindd\fR daemon. +The following signals can be used to manipulate the\fBwinbindd\fR daemon\&. + .TP -\fBSIGHUP\fR -Reload the \fBsmb.conf\fR(5) file and -apply any parameter changes to the running -version of winbindd. This signal also clears any cached -user and group information. The list of other domains trusted -by winbindd is also reloaded. +SIGHUP +Reload the \fBsmb.conf\fR(5) file and apply any parameter changes to the running version of winbindd\&. This signal also clears any cached user and group information\&. The list of other domains trusted by winbindd is also reloaded\&. + + .TP -\fBSIGUSR1\fR -The SIGUSR1 signal will cause \fB winbindd\fR to write status information to the winbind -log file including information about the number of user and -group ids allocated by \fBwinbindd\fR. +SIGUSR1 +The SIGUSR1 signal will cause \fB winbindd\fR to write status information to the winbind log file including information about the number of user and group ids allocated by \fBwinbindd\fR\&. + + +Log files are stored in the filename specified by the log file parameter\&. + -Log files are stored in the filename specified by the -log file parameter. .SH "FILES" + .TP -\fB\fI/etc/nsswitch.conf(5)\fB\fR -Name service switch configuration file. +\fI/etc/nsswitch\&.conf(5)\fR +Name service switch configuration file\&. + + .TP -\fB/tmp/.winbindd/pipe\fR -The UNIX pipe over which clients communicate with -the \fBwinbindd\fR program. For security reasons, the -winbind client will only attempt to connect to the winbindd daemon -if both the \fI/tmp/.winbindd\fR directory -and \fI/tmp/.winbindd/pipe\fR file are owned by -root. +/tmp/\&.winbindd/pipe +The UNIX pipe over which clients communicate with the \fBwinbindd\fR program\&. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the \fI/tmp/\&.winbindd\fR directory and \fI/tmp/\&.winbindd/pipe\fR file are owned by root\&. + + .TP -\fB$LOCKDIR/winbindd_privilaged/pipe\fR -The UNIX pipe over which 'privilaged' clients -communicate with the \fBwinbindd\fR program. For security -reasons, access to some winbindd functions - like those needed by -the \fBntlm_auth\fR utility - is restricted. By default, -only users in the 'root' group will get this access, however the administrator -may change the group permissions on $LOCKDIR/winbindd_privilaged to allow -programs like 'squid' to use ntlm_auth. -Note that the winbind client will only attempt to connect to the winbindd daemon -if both the \fI$LOCKDIR/winbindd_privilaged\fR directory -and \fI$LOCKDIR/winbindd_privilaged/pipe\fR file are owned by -root. +$LOCKDIR/winbindd_privilaged/pipe +The UNIX pipe over which 'privilaged' clients communicate with the \fBwinbindd\fR program\&. For security reasons, access to some winbindd functions - like those needed by the \fBntlm_auth\fR utility - is restricted\&. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privilaged to allow programs like 'squid' to use ntlm_auth\&. Note that the winbind client will only attempt to connect to the winbindd daemon if both the \fI$LOCKDIR/winbindd_privilaged\fR directory and \fI$LOCKDIR/winbindd_privilaged/pipe\fR file are owned by root\&. + + .TP -\fB/lib/libnss_winbind.so.X\fR -Implementation of name service switch library. +/lib/libnss_winbind\&.so\&.X +Implementation of name service switch library\&. + + .TP -\fB$LOCKDIR/winbindd_idmap.tdb\fR -Storage for the Windows NT rid to UNIX user/group -id mapping. The lock directory is specified when Samba is initially -compiled using the \fI--with-lockdir\fR option. -This directory is by default \fI/usr/local/samba/var/locks -\fR. +$LOCKDIR/winbindd_idmap\&.tdb +Storage for the Windows NT rid to UNIX user/group id mapping\&. The lock directory is specified when Samba is initially compiled using the \fI--with-lockdir\fR option\&. This directory is by default \fI/usr/local/samba/var/locks \fR\&. + + .TP -\fB$LOCKDIR/winbindd_cache.tdb\fR -Storage for cached user and group information. +$LOCKDIR/winbindd_cache\&.tdb +Storage for cached user and group information\&. + + .SH "VERSION" + .PP -This man page is correct for version 3.0 of -the Samba suite. +This man page is correct for version 3\&.0 of the Samba suite\&. + .SH "SEE ALSO" + .PP -\fInsswitch.conf(5)\fR, \fBSamba\fR(7), \fBwbinfo\fR(8), \fBsmb.conf\fR(5) +\fInsswitch\&.conf(5)\fR, \fBSamba\fR(7), \fBwbinfo\fR(8), \fBsmb.conf\fR(5) + .SH "AUTHOR" + .PP -The original Samba software and related utilities -were created by Andrew Tridgell. Samba is now developed -by the Samba Team as an Open Source project similar -to the way the Linux kernel is developed. +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&. + .PP -\fBwbinfo\fR and \fBwinbindd\fR were -written by Tim Potter. +\fBwbinfo\fR and \fBwinbindd\fR were written by Tim Potter\&. + .PP -The conversion to DocBook for Samba 2.2 was done -by Gerald Carter. The conversion to DocBook XML 4.2 for -Samba 3.0 was done by Alexander Bokovoy. +The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&. + -- cgit