Ports 搜索

If you've ever tried to use Test::NoWarnings to confirm there are no warnings generated by your tests, combined with the convenience of done_testing to not have to declare a test count, you'll have discovered that these two features do not play well together, as the test count will be calculated before the warnings test is run, resulting in a TAP error. (See examples/test_nowarnings.pl in this distribution for a demonstration.) This module is intended to be used as a drop-in replacement for Test::NoWarnings: it also adds an extra test, but runs this test before done_testing calculates the test count, rather than after. It does this by hooking into done_testing as well as via an END block. You can declare a plan, or not, and things will still Just Work.

Pinba is a statistics server for PHP using MySQL as a read-only interface. It accumulates and processes data sent over UDP by multiple PHP processes and displays statistics in a nice human-readable form of simple "reports", also providing a read-only interface to the raw data to enable generation of more sophisticated reports. With the Pinba extension, users can also measure particular parts of the code using timers with arbitrary tags. Pinba is not a debugging tool in the common sense, since you're not supposed to do debugging on production servers, but its main goal is to help developers to locate bottlenecks in realtime and direct their attention to the code that really needs it.

Pinba is a statistics server for PHP using MySQL as a read-only interface. It accumulates and processes data sent over UDP by multiple PHP processes and displays statistics in a nice human-readable form of simple "reports", also providing a read-only interface to the raw data to enable generation of more sophisticated reports. With the Pinba extension, users can also measure particular parts of the code using timers with arbitrary tags. Pinba is not a debugging tool in the common sense, since you're not supposed to do debugging on production servers, but its main goal is to help developers to locate bottlenecks in realtime and direct their attention to the code that really needs it.

Gitolite is an access control layer on top of git, which allows access control down to the branch level, including specifying who can and cannot rewind a given branch. Gitolite lets you use a single user on a server to host many git repositories and provide access to many developers, without having to give them real userids on or shell access to the server. Authentication is most commonly done using sshd, but you can also use httpd if you prefer. Gitolite can restrict who can read from (clone/fetch) or write to (push) a repository. It can also restrict who can push to what branch or tag, which is very important in a corporate environment.

The pytest-xdist plugin extends py.test with some unique test execution modes: * Test run parallelization: if you have multiple CPUs or hosts you can use those for a combined test run. This allows to speed up development or to use special resources of remote machines. * --boxed: (not available on Windows) run each test in a boxed subprocess to survive SEGFAULTS or otherwise dying processes * --looponfail: run your tests repeatedly in a subprocess. After each run py.test waits until a file in your project changes and then re-runs the previously failing tests. This is repeated until all tests pass after which again a full run is performed. * Multi-Platform coverage: you can specify different Python interpreters or different platforms and run tests in parallel on all of them.

DHIS Daemon release 5.1 ============================== The server is now modular through the introduction of a services sub-system. DNS updates are no longer part of the main code but are now implemented as a module. The main dhisd process listens to DHIS clients and after authentication marks these with their dynamic IP address. The request is passed to a sub-process through a pipe which implements the services for which the client is subscribed to. Clients may be subscribed to one or more services individually. The sub-engine interface does a basic read from stdin and process. Examples of things DHIS could update: Dns, Firewalls, tunnel servers, relay access lists, etc ... For more information on the services of DHIS, you should look at the official DHIS site: http://www.dhis.org/dhis/services/

Dnsmasq is a lightweight, easy to configure DNS forwarder and DHCP server. It is designed to provide DNS and, optionally, DHCP, to a small network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP/TFTP/PXE for network booting of diskless machines. Dnsmasq is targeted at home networks using NAT and connected to the internet via a modem, cable-modem or ADSL connection but would be a good choice for any smallish network (up to 1000 clients is known to work) where low resource use and ease of configuration are important. -- Simon Kelley

Dnsmasq 是一个轻量级的，易于配置的 DNS 转发器和 DHCP 服务器。旨在为 小型网络提供 DNS 和 可选的 DHCP。DHCP 服务器和 DNS 服务器集成，可以 通过 DHCP 分配来为每台机器设置 DNS 服务器。Dnsmasq 支持静态和动 态 DHCP 租约，和 BOOTP/TFTP/PXE 网络无盘启动计算机。 Dnsmasq 适用于那些使用 NAT 并通过调制解调器、电缆调制解调器 或者 ADSL 连接网络的家庭网络，对小型网络（最多为 1000 个客户端） 也是不错的选择，资源使用少、配置简单是其终于的特性。 —— 西蒙 凯利

fpdns - Fingerprinting DNS servers A nameserver basically responds to a query. Interoperability is an obvious requirement here. The standard protocol behaviour of different DNS implementations is expected to be the same. Requirements for protocol behaviour of DNS implementations is widely documented in the case of 'common' dns messages. The DNS protocol is over 20 years old and since its inception, there have been over 40 independent DNS implementations, while some implementations have over 20 versions. The methodology used to identify individual nameserver implementations is based on "borderline" protocol behaviour. The DNS protocol offers a multitude of message bits, response types, opcodes, classes, query types and label types in a fashion that makes some mutually exclusive while some are not used in a query messages at all. Not every implementation offers the full set of features the DNS protocol set currently has. Some implementations offer features outside the protocol set, and there are implementations that do not conform to standards.

Public Suffix Service is a Ruby domain name parser based on the Public Suffix List. The Public Suffix Service is a cross-vendor initiative to provide an accurate list of domain name suffixes. The Public Suffix Service is an initiative of the Mozilla Project, but is maintained as a community resource. It is available for use in any software, but was originally created to meet the needs of browser manufacturers. A "public suffix" is one under which Internet users can directly register names. Some examples of public suffixes are ".com", ".co.uk" and "pvt.k12.wy.us". The Public Suffix List is a list of all known public suffixes. GitHub repository is at https://github.com/weppos/publicsuffix-ruby