archive-org.com » ORG » J » JABBERCN.ORG

Total: 303

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • 分类:XMPP服务器文档 - Jabber/XMPP中文翻译计划
    安装和管理指南 Openfire 安装指南 Tigase 用GUI安装包安装 分类 XMPP服务器文档 中的页面 本分类包含下列4个页面 共有4个页面 E Ejabberd2 安装和操作指南 J Jabberd2 安装和管理指南 O Openfire 安装指南 T Tigase 用GUI安装包安装 来自 http wiki jabbercn org index php title E5 88 86 E7 B1 BB XMPP E6 9C 8D E5 8A A1 E5 99 A8 E6 96 87 E6 A1 A3 oldid 3410 1个分类 所有文档列表 查看 分类 讨论 查看源代码 历史 个人工具 登录 创建账户 导航 首页 社区专页 新闻动态 最近更改 随机页面

    Original URL path: http://wiki.jabbercn.org/index.php?title=%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3&oldid=3410 (2016-04-25)
    Open archived version from archive


  • 查看源代码 - Jabber/XMPP中文翻译计划
    categorytree 返回到 分类 XMPP服务器文档 来自 http wiki jabbercn org E5 88 86 E7 B1 BB XMPP E6 9C 8D E5 8A A1 E5 99 A8 E6 96 87 E6 A1 A3 查看 分类 讨论 查看源代码 历史 个人工具 登录 创建账户 导航

    Original URL path: http://wiki.jabbercn.org/index.php?title=%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3&action=edit (2016-04-25)
    Open archived version from archive

  • “分类:XMPP服务器文档”的版本历史 - Jabber/XMPP中文翻译计划
    回车键 或下方的按钮进行对比 说明 当前 与最后版本之间的差异 先前 与上一版本之间的差异 小 小编辑 当前 先前 2013年8月11日 日 03 00 Admin 讨论 贡献 小 140字节 当前 先前 2013年3月22日 五 18 13 Admin 讨论 贡献 小 78字节 当前 先前 2013年3月22日 五 18 12 Admin 讨论 贡献 46字节 以 这里存放各类XMPP服务器软件的文档 为内容创建页面 来自 http wiki jabbercn org E5 88 86 E7 B1 BB XMPP E6 9C 8D E5 8A A1 E5 99 A8 E6 96 87 E6 A1

    Original URL path: http://wiki.jabbercn.org/index.php?title=%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3&action=history (2016-04-25)
    Open archived version from archive

  • 链接至“分类:XMPP服务器文档”的页面 - Jabber/XMPP中文翻译计划
    文件 文件讨论 MediaWiki MediaWiki讨论 模板 模板讨论 帮助 帮助讨论 分类 分类讨论 过滤器 隐藏 包含 隐藏 链接 隐藏 重定向 没有页面链接至 分类 XMPP服务器文档 来自 http wiki jabbercn org E7 89 B9 E6 AE 8A E9 93 BE E5 85 A5 E9 A1 B5 E9 9D A2 E5 88 86 E7 B1 BB XMPP E6 9C 8D E5 8A A1 E5 99 A8 E6 96 87 E6 A1 A3 查看 分类 讨论 查看源代码 历史

    Original URL path: http://wiki.jabbercn.org/%E7%89%B9%E6%AE%8A:%E9%93%BE%E5%85%A5%E9%A1%B5%E9%9D%A2/%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3 (2016-04-25)
    Open archived version from archive

  • 对于“分类:XMPP服务器文档”有关的链出更改 - Jabber/XMPP中文翻译计划
    隐藏 匿名用户的编辑 隐藏 登录用户的编辑 隐藏 我的编辑 显示自 2016年4月25日 一 16 51 起的新更改 名字空间 全部 主要 讨论 用户 用户讨论 Jabber XMPP中文翻译计划 Jabber XMPP中文翻译计划讨论 文件 文件讨论 MediaWiki MediaWiki讨论 模板 模板讨论 帮助 帮助讨论 分类 分类讨论 反选 相关名字空间 页面名称 显示链到所给出的页面 在这一段时间中链接的页面并无更改 来自 http wiki jabbercn org E7 89 B9 E6 AE 8A E9 93 BE E5 87 BA E6 9B B4 E6 94 B9 E5 88 86 E7 B1 BB XMPP E6 9C 8D

    Original URL path: http://wiki.jabbercn.org/%E7%89%B9%E6%AE%8A:%E9%93%BE%E5%87%BA%E6%9B%B4%E6%94%B9/%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3 (2016-04-25)
    Open archived version from archive

  • 分类:XMPP服务器文档 - Jabber/XMPP中文翻译计划
    E Ejabberd2 安装和操作指南 J Jabberd2 安装和管理指南 O Openfire 安装指南 T Tigase 用GUI安装包安装 来自 http wiki jabbercn org index php title E5 88 86 E7 B1 BB XMPP E6 9C 8D E5 8A A1 E5 99 A8 E6 96 87 E6 A1 A3 oldid 3410 1个分类 所有文档列表 查看 分类 讨论 查看源代码 历史 个人工具 登录 创建账户 导航 首页 社区专页 新闻动态 最近更改 随机页面 帮助 XMPP资源 XMPP公共服务 XMPP客户端软件 XMPP服务器软件 友情链接 搜索 站外搜索 工具箱 链入页面

    Original URL path: http://wiki.jabbercn.org/index.php?title=%E5%88%86%E7%B1%BB:XMPP%E6%9C%8D%E5%8A%A1%E5%99%A8%E6%96%87%E6%A1%A3&printable=yes (2016-04-25)
    Open archived version from archive

  • OpenLDAP2.4管理员指南 - Jabber/XMPP中文翻译计划
    olcModulePath pathspec Specify a list of directories to search for loadable modules Typically the path is colon separated but this depends on the operating system 示例条目 dn cn module 0 cn config objectClass olcModuleList cn module 0 olcModuleLoad usr local lib smbk5pwd la dn cn module 1 cn config objectClass olcModuleList cn module 1 olcModulePath usr local lib usr local lib slapd olcModuleLoad accesslog la olcModuleLoad pcache la cn schema The cn schema entry holds all of the schema definitions that are hard coded in slapd As such the values in this entry are generated by slapd so no schema values need to be provided in the config file The entry must still be defined though to serve as a base for the user defined schema to add in underneath Schema entries must have the olcSchemaConfig objectClass olcAttributeTypes RFC4512 Attribute Type Description This directive defines an attribute type Please see the Schema Specification chapter for information regarding how to use this directive olcObjectClasses RFC4512 Object Class Description This directive defines an object class Please see the Schema Specification chapter for information regarding how to use this directive 示例条目 dn cn schema cn config objectClass olcSchemaConfig cn schema dn cn test cn schema cn config objectClass olcSchemaConfig cn test olcAttributeTypes 1 1 1 NAME testAttr EQUALITY integerMatch SYNTAX 1 3 6 1 4 1 1466 115 121 1 27 olcAttributeTypes 1 1 2 NAME testTwo EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1 3 6 1 4 1 1466 115 121 1 44 olcObjectClasses 1 1 3 NAME testObject MAY testAttr testTwo AUXILIARY 具体后端指令 Backend directives apply to all database instances of the same type and depending on the directive may be overridden by database directives Backend entries must have the olcBackendConfig objectClass olcBackend type This directive names a backend specific configuration entry type should be one of the supported backend types listed in Table 5 2 Table 5 2 Database Backends Types Description bdb Berkeley DB transactional backend config Slapd configuration backend dnssrv DNS SRV backend hdb Hierarchical variant of bdb backend ldap Lightweight Directory Access Protocol Proxy backend ldif Lightweight Data Interchange Format backend meta Meta Directory backend monitor Monitor backend passwd Provides read only access to passwd 5 perl Perl Programmable backend shell Shell extern program backend sql SQL Programmable backend Example olcBackend bdb There are no other directives defined for this entry Specific backend types may define additional attributes for their particular use but so far none have ever been defined As such these directives usually do not appear in any actual configurations 示例条目 dn olcBackend bdb cn config objectClass olcBackendConfig olcBackend bdb 特定数据库 Directives in this section are supported by every type of database Database entries must have the olcDatabaseConfig objectClass olcDatabase index type This directive names a specific database instance The numeric index may be provided to distinguish multiple databases of the same type Usually the index can be omitted and slapd will generate it automatically type should be one of the supported backend types listed in Table 5 2 or the frontend type The frontend is a special database that is used to hold database level options that should be applied to all the other databases Subsequent database definitions may also override some frontend settings The config database is also special both the config and the frontend databases are always created implicitly even if they are not explicitly configured and they are created before any other databases Example olcDatabase bdb This marks the beginning of a new BDB database instance olcAccess to what by who accesslevel control This directive grants access specified by accesslevel to a set of entries and or attributes specified by what by one or more requestors specified by who See the Access Control section of this guide for basic usage Note If no olcAccess directives are specified the default access control policy to by read allows all users both authenticated and anonymous read access Note Access controls defined in the frontend are appended to all other databases controls olcReadonly TRUE FALSE This directive puts the database into read only mode Any attempts to modify the database will return an unwilling to perform error Default olcReadonly FALSE olcRootDN DN This directive specifies the DN that is not subject to access control or administrative limit restrictions for operations on this database The DN need not refer to an entry in this database or even in the directory The DN may refer to a SASL identity Entry based Example olcRootDN cn Manager dc example dc com SASL based Example olcRootDN uid root cn example com cn digest md5 cn auth See the SASL Authentication section for information on SASL authentication identities olcRootPW password This directive can be used to specify a password for the DN for the rootdn when the rootdn is set to a DN within the database Example olcRootPW secret It is also permissible to provide a hash of the password in RFC2307 form slappasswd 8 may be used to generate the password hash Example olcRootPW SSHA ZKKuqbEKJfKSXhUbHG3fG8MDn9j1v4QN The hash was generated using the command slappasswd s secret olcSizeLimit integer This directive specifies the maximum number of entries to return from a search operation Default olcSizeLimit 500 See the Limits section of this guide and slapd config 5 for more details olcSuffix dn suffix This directive specifies the DN suffix of queries that will be passed to this backend database Multiple suffix lines can be given and usually at least one is required for each database definition Some backend types such as frontend and monitor use a hard coded suffix which may not be overridden in the configuration Example olcSuffix dc example dc com Queries with a DN ending in dc example dc com will be passed to this backend Note When the backend to pass a query to is selected slapd looks at the suffix value s in each database definition in the order in which they were configured Thus if one database suffix is a prefix of another it must appear after it in the configuration olcSyncrepl olcSyncrepl rid replica ID provider ldap s hostname port type refreshOnly refreshAndPersist interval dd hh mm ss retry retry interval of retries searchbase base DN filter filter str scope sub one base attrs attr list attrsonly sizelimit limit timelimit limit schemachecking on off bindmethod simple sasl binddn DN saslmech mech authcid identity authzid identity credentials passwd realm realm secprops properties starttls yes critical tls cert file tls key file tls cacert file tls cacertdir path tls reqcert never allow try demand tls ciphersuite ciphers tls crlcheck none peer all logbase base DN logfilter filter str syncdata default accesslog changelog 这个指令定义当前数据库作为一个主服务器内容的复制 通过当前的slapd 8 建立一个运行syncrepl复制引擎的复制消费者站点 主数据库由provider参数定位于复制提供者站点 复制数据库使用LDAP内容同步协议保持对主服务器内容的更新 关于协议的更多信息参见 RFC4533 The rid parameter is used for identification of the current syncrepl directive within the replication consumer server where replica ID uniquely identifies the syncrepl specification described by the current syncrepl directive replica ID is non negative and is no more than three decimal digits in length The provider parameter specifies the replication provider site containing the master content as an LDAP URI The provider parameter specifies a scheme a host and optionally a port where the provider slapd instance can be found Either a domain name or IP address may be used for hostname Examples are ldap provider example com 389 or ldaps 192 168 1 1 636 If port is not given the standard LDAP port number 389 or 636 is used Note that the syncrepl uses a consumer initiated protocol and hence its specification is located at the consumer site whereas the replica specification is located at the provider site syncrepl and replica directives define two independent replication mechanisms They do not represent the replication peers of each other The content of the syncrepl replica is defined using a search specification as its result set The consumer slapd will send search requests to the provider slapd according to the search specification The search specification includes searchbase scope filter attrs attrsonly sizelimit and timelimit parameters as in the normal search specification The searchbase parameter has no default value and must always be specified The scope defaults to sub the filter defaults to objectclass attrs defaults to to replicate all user and operational attributes and attrsonly is unset by default Both sizelimit and timelimit default to unlimited and only positive integers or unlimited may be specified The LDAP Content Synchronization protocol has two operation types refreshOnly and refreshAndPersist The operation type is specified by the type parameter In the refreshOnly operation the next synchronization search operation is periodically rescheduled at an interval time after each synchronization operation finishes The interval is specified by the interval parameter It is set to one day by default In the refreshAndPersist operation a synchronization search remains persistent in the provider slapd instance Further updates to the master replica will generate searchResultEntry to the consumer slapd as the search responses to the persistent synchronization search If an error occurs during replication the consumer will attempt to reconnect according to the retry parameter which is a list of the retry interval and of retries pairs For example retry 60 10 300 3 lets the consumer retry every 60 seconds for the first 10 times and then retry every 300 seconds for the next three times before stop retrying in of retries means indefinite number of retries until success The schema checking can be enforced at the LDAP Sync consumer site by turning on the schemachecking parameter If it is turned on every replicated entry will be checked for its schema as the entry is stored into the replica content Every entry in the replica should contain those attributes required by the schema definition If it is turned off entries will be stored without checking schema conformance The default is off The binddn parameter gives the DN to bind as for the syncrepl searches to the provider slapd It should be a DN which has read access to the replication content in the master database The bindmethod is simple or sasl depending on whether simple password based authentication or SASL authentication is to be used when connecting to the provider slapd instance Simple authentication should not be used unless adequate data integrity and confidentiality protections are in place e g TLS or IPsec Simple authentication requires specification of binddn and credentials parameters SASL authentication is generally recommended SASL authentication requires specification of a mechanism using the saslmech parameter Depending on the mechanism an authentication identity and or credentials can be specified using authcid and credentials respectively The authzid parameter may be used to specify an authorization identity The realm parameter specifies a realm which a certain mechanisms authenticate the identity within The secprops parameter specifies Cyrus SASL security properties The starttls parameter specifies use of the StartTLS extended operation to establish a TLS session before authenticating to the provider If the critical argument is supplied the session will be aborted if the StartTLS request fails Otherwise the syncrepl session continues without TLS Note that the main slapd TLS settings are not used by the syncrepl engine by default the TLS parameters from a ldap conf 5 configuration file will be used TLS settings may be specified here in which case any ldap conf 5 settings will be completely ignored Rather than replicating whole entries the consumer can query logs of data modifications This mode of operation is referred to as delta syncrepl In addition to the above parameters the logbase and logfilter parameters must be set appropriately for the log that will be used The syncdata parameter must be set to either accesslog if the log conforms to the slapo accesslog 5 log format or changelog if the log conforms to the obsolete changelog format If the syncdata parameter is omitted or set to default then the log parameters are ignored The syncrepl replication mechanism is supported by the bdb and hdb backends See the LDAP Sync Replication chapter of this guide for more information on how to use this directive olcTimeLimit integer This directive specifies the maximum number of seconds in real time slapd will spend answering a search request If a request is not finished in this time a result indicating an exceeded timelimit will be returned Default olcTimeLimit 3600 See the Limits section of this guide and slapd config 5 for more details olcUpdateref URL This directive is only applicable in a slave slapd It specifies the URL to return to clients which submit update requests upon the replica If specified multiple times each URL is provided Example olcUpdateref ldap master example net Sample Entries dn olcDatabase frontend cn config objectClass olcDatabaseConfig objectClass olcFrontendConfig olcDatabase frontend olcReadOnly FALSE dn olcDatabase config cn config objectClass olcDatabaseConfig olcDatabase config olcRootDN cn Manager dc example dc com BDB和HDB数据库指令 Directives in this category apply to both the BDB and the HDB database They are used in an olcDatabase entry in addition to the generic database directives defined above For a complete reference of BDB HDB configuration directives see slapd bdb 5 In addition to the olcDatabaseConfig objectClass BDB and HDB database entries must have the olcBdbConfig and olcHdbConfig objectClass respectively olcDbDirectory directory This directive specifies the directory where the BDB files containing the database and associated indices live Default olcDbDirectory usr local var openldap data olcDbCachesize integer This directive specifies the size in entries of the in memory cache maintained by the BDB backend database instance Default olcDbCachesize 1000 olcDbCheckpoint kbyte min This directive specifies how often to checkpoint the BDB transaction log A checkpoint operation flushes the database buffers to disk and writes a checkpoint record in the log The checkpoint will occur if either kbyte data has been written or min minutes have passed since the last checkpoint Both arguments default to zero in which case they are ignored When the min argument is non zero an internal task will run every min minutes to perform the checkpoint See the Berkeley DB reference guide for more details Example olcDbCheckpoint 1024 10 olcDbConfig DB CONFIG setting This attribute specifies a configuration directive to be placed in the DB CONFIG file of the database directory At server startup time if no such file exists yet the DB CONFIG file will be created and the settings in this attribute will be written to it If the file exists its contents will be read and displayed in this attribute The attribute is multi valued to accommodate multiple configuration directives No default is provided but it is essential to use proper settings here to get the best server performance Any changes made to this attribute will be written to the DB CONFIG file and will cause the database environment to be reset so the changes can take immediate effect If the environment cache is large and has not been recently checkpointed this reset operation may take a long time It may be advisable to manually perform a single checkpoint using the Berkeley DB db checkpoint utility before using LDAP Modify to change this attribute Example olcDbConfig set cachesize 0 10485760 0 olcDbConfig set lg bsize 2097512 olcDbConfig set lg dir var tmp bdb log olcDbConfig set flags DB LOG AUTOREMOVE In this example the BDB cache is set to 10MB the BDB transaction log buffer size is set to 2MB and the transaction log files are to be stored in the var tmp bdb log directory Also a flag is set to tell BDB to delete transaction log files as soon as their contents have been checkpointed and they are no longer needed Without this setting the transaction log files will continue to accumulate until some other cleanup procedure removes them See the Berkeley DB documentation for the db archive command for details For a complete list of Berkeley DB flags please see http www oracle com technology documentation berkeley db db api c env set flags html Ideally the BDB cache must be at least as large as the working set of the database the log buffer size should be large enough to accommodate most transactions without overflowing and the log directory must be on a separate physical disk from the main database files And both the database directory and the log directory should be separate from disks used for regular system activities such as the root boot or swap filesystems See the FAQ o Matic and the Berkeley DB documentation for more details olcDbNosync TRUE FALSE This option causes on disk database contents to not be immediately synchronized with in memory changes upon change Setting this option to TRUE may improve performance at the expense of data integrity This directive has the same effect as using olcDbConfig set flags DB TXN NOSYNC olcDbIDLcacheSize integer Specify the size of the in memory index cache in index slots The default is zero A larger value will speed up frequent searches of indexed entries The optimal size will depend on the data and search characteristics of the database but using a number three times the entry cache size is a good starting point Example olcDbIDLcacheSize 3000 olcDbIndex attrlist default pres eq approx sub none This directive specifies the indices to maintain for the given attribute If only an attrlist is given the default indices are maintained The index keywords correspond to the common types of matches that may be used in an LDAP search filter Example olcDbIndex default pres eq olcDbIndex uid olcDbIndex cn sn pres eq sub olcDbIndex objectClass eq The first line sets the default set of indices to maintain to present and equality The second line causes the default pres eq set of indices to be maintained for the uid attribute type The third line causes present equality and substring indices to be maintained for cn and sn attribute types The fourth line causes an equality index for the objectClass attribute type There is no index keyword for inequality matches Generally these matches do not use an index However some attributes do support indexing for inequality matches based on the equality index A substring index can

    Original URL path: http://wiki.jabbercn.org/OpenLDAP2.4%E7%AE%A1%E7%90%86%E5%91%98%E6%8C%87%E5%8D%97 (2016-04-25)
    Open archived version from archive

  • 分类:其它翻译文档 - Jabber/XMPP中文翻译计划
    手册之类的 它不是有关XMPP的 因为那属于另一个大类 它是翻译过来的 原文来自别处 其它翻译文档 OpenLDAP2 4管理员指南 RFC3986 分类 其它翻译文档 中的页面 本分类包含下列2个页面 共有2个页面 O OpenLDAP2 4管理员指南 R RFC3986 来自 http wiki jabbercn org index php title E5 88 86 E7 B1 BB E5 85 B6 E5 AE 83 E7 BF BB E8 AF 91 E6 96 87 E6 A1 A3 oldid 3411 1个分类 所有文档列表 查看 分类 讨论 查看源代码 历史 个人工具 登录 创建账户 导航 首页 社区专页 新闻动态 最近更改 随机页面 帮助

    Original URL path: http://wiki.jabbercn.org/index.php?title=%E5%88%86%E7%B1%BB:%E5%85%B6%E5%AE%83%E7%BF%BB%E8%AF%91%E6%96%87%E6%A1%A3&oldid=3411 (2016-04-25)
    Open archived version from archive



  •