uawdijnntqw1x1x1
IP : 216.73.216.155
Hostname : vm5018.vps.agava.net
Kernel : Linux vm5018.vps.agava.net 3.10.0-1127.8.2.vz7.151.14 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64
Disable Function : None :)
OS : Linux
PATH:
/
var
/
..
/
usr
/
share
/
doc
/
.
/
dovecot-common
/
wiki
/
UserDatabase.NSS.txt
/
/
NSS === (v1.1+ only) 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 <deliver> [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=yes* causes the lookups to be done in worker processes. You'll probably want to use this with LDAP/SQL/etc. remote database lookups. Example ------- ---%<------------------------------------------------------------------------- userdb nss { args = service=ldap blocking=yes } ---%<------------------------------------------------------------------------- (This file was created from the wiki on 2010-05-24 04:42)
/var/../usr/share/doc/./dovecot-common/wiki/UserDatabase.NSS.txt