Ports Search

Frontier::RPC implements UserLand Software's XML RPC (Remote Procedure Calls using Extensible Markup Language). Frontier::RPC includes both a client module for making requests to a server and a daemon module for implementing servers. Frontier::RPC uses RPC2 format messages. RPC client connections are made by creating instances of Frontier::Client objects that record the server name, and then issuing `call' requests that send a method name and parameters to the server. RPC daemons are mini-HTTP servers (using HTTP::Daemon from the `libwww' Perl module). Daemons are created by first defining the procedures you want to make available to RPC and then passing a list of those procedures as you create the Frontier::Daemon object. The Frontier::RPC2 module implements the encoding and decoding of XML RPC requests using the XML::Parser Perl module.

Is this module just like Net::FTP? No it is not! 1. It is a subclass and not a new class that uses Net::FTP underneath. That means the object is a normal Net::FTP object and has all the methods Net::FTP has. 2. It does not override Net::FTP methods (IE does not have methods the same name as Net::FTP) which means you don't have to sort through how the function differs from the standard version in the Net::FTP module. 3. Its waaaay simpler to use without a bunch of weird config stuff to cloud the issue, odd hard to remember arguments, obscure methods to replace valid existing ones that are part of Net::FTP, or new methods that are badly named (IE think "grep" on this one). There are other things as well. 4. It follows the paradigm of Perl name spaces, objects, and general good practice much better and in a way that is more intuitive and expandable.

This is the FreeBSD port of the OpenBSD relayd and relayctl. relayd is a daemon to relay and dynamically redirect incoming connections to a target host. Its main purposes are to run as a load-balancer, application layer gateway, or transparent proxy. The daemon is able to monitor groups of hosts for availability, which is determined by checking for a specific service common to a host group. When availability is con- firmed, Layer 3 and/or layer 7 forwarding services are set up by relayd. Layer 3 redirection happens at the packet level; to configure it, relayd communicates with pf(4). The following relayd functionality is not (yet) implemented in FreeBSD: - carp demote - modifying routing tables - snmp traps The relayctl program controls the relayd(8) daemon.

Portupgrade is a tool to upgrade installed packages via ports or packages. You can upgrade installed packages without having to reinstall depending or dependent packages. It can automatically trace dependency chains up and down upgrading packages recursively. This package also includes the following utilities: portinstall: Helps you install new ports in a handy way. portsvnweb: Instantly lets you browse change history via SVNweb. portversion: Replaces pkg_version(1) and helps you upgrade packages with portupgrade(1). (runs much faster) portsclean: Cleans ports workdir's, unreferenced distfiles, old and orphan shared libraries, and stale packages. portsdb: Creates binary database from the ports INDEX. ports_glob: Expands ports globs. pkg_deinstall: Wraps pkg_delete(1) and provides additional features. pkg_fetch: Fetches packages from a remote site. pkg_glob: Expands package globs. pkg_which: Checks which package a file came from quickly. pkgdb: Manages and searches the package database. pkgdu: Display a disk usage for installed packages.

Portupgrade is a tool to upgrade installed packages via ports or packages. You can upgrade installed packages without having to reinstall depending or dependent packages. It can automatically trace dependency chains up and down upgrading packages recursively. This package also includes the following utilities: portinstall: Helps you install new ports in a handy way. portcvsweb: Instantly lets you browse change history via CVSweb. portversion: Replaces pkg_version(1) and helps you upgrade packages with portupgrade(1). (runs much faster) portsclean: Cleans ports workdir's, unreferenced distfiles, old and orphan shared libraries, and stale packages. portsdb: Creates binary database from the ports INDEX. ports_glob: Expands ports globs. pkg_deinstall: Wraps pkg_delete(1) and provides additional features. pkg_fetch: Fetches packages from a remote site. pkg_glob: Expands package globs. pkg_which: Checks which package a file came from quickly. pkgdb: Manages and searches the package database. pkgdu: Display a disk usage for installed packages.

tinc is a Virtual Private Network (VPN) daemon that uses tunnelling and encryption to create a secure private network between hosts on the Internet. Because the tunnel appears to the IP level network code as a normal network device, there is no need to adapt any existing software. This tunnelling allows VPN sites to share information with each other over the Internet without exposing any information to others. A single tinc daemon can accept more than one connection at a time, thus making it possible to create larger virtual networks, because some limitations are circumvented. Instead of most other VPN implementations, tinc encapsulates each network packet in its own UDP packet, instead of encapsulating all into one TCP or even PPP over TCP stream. This results in lower latencies, less overhead, and in general better responsiveness and throughput. LICENSE: GPL3 or later with execption to link with OpenSSL

htop is an enhanced version of top, the interactive process viewer, which can display the list of processes in a tree form. Comparison between 'htop' and 'top' * In 'htop' you can scroll the list vertically and horizontally to see all processes and full command lines. * In 'top' you are subject to a delay for each unassigned key you press (especially annoying when multi-key escape sequences are triggered by accident). * 'htop' starts faster ('top' seems to collect data for a while before displaying anything). * In 'htop' you don't need to type the process number to kill a process, in 'top' you do. * In 'htop' you don't need to type the process number or the priority value to renice a process, in 'top' you do. * In 'htop' you can kill multiple processes at once. * 'top' is older, hence, more tested.

chyves is a bhyve front-end manager. chyves manages type-2 virtualized guests by utilizing hardware virtualization on a base FreeBSD 10.3+ installation. On a base install, only FreeBSD guests can run. However, with the installation of sysutils/grub2-bhyve and sysutils/bhyve-firmware from ports or pkg, most other OSes can run as a guest, including Windows. See DEPENDENCIES section in the man page for more information. chyves is targeted for beginners as well as power users. Beginners should find chyves relatively easy to use with lots of documentation and demonstrations. While power users should find utility with features such as true ZFS clones, PCI passthrough, rapid execution against many guests, disk images, and snapshot reverted states on boot/reboot to name a few of the advanced features. The name 'chyves' is the pluralized, big endian alphabetic increment of bhyve. 'chyves' is pronounced like 'chives', part of the Allium genus. The onion is also in the Allium genus.

This is a smaller, cheaper, faster SED implementation. Minix uses it. GNU used to use it, until they built their own sed around an extended (some would say over-extended) regexp package. For embedded use we searched for a tiny sed implementation especially for use with the dietlibc and found Eric S. Raymond's sed implementation quite handy. Though it suffered several bugs and was not under active maintenance anymore. After sending a bunch of fixes we agreed to continue maintaining this lovely, historic sed implementation. Along a lot fixes and cleanups, further speedups, and some missing features and POSIX conformance, we also added a test-suite to the package, so regressions are quickly and easily uncovered.

This program has three modes of operation: - First, is ** EXPLOSION **, or the expanding of a .LIT file into an OEBPS compliant package. - Second, is the DOWNCONVERTING of a .LIT file down to "Sealed", or DRM1 format for reading on handheld devices. - Third, is the INSCRIBING of a .LIT file which allows you to label your ebooks. DRM5 is supported if you have a "keys.txt" file that contains the private key(s) for your passport(s) in either the CLIT program directory or the current directory. This is a tool for **YOUR OWN FAIR USE** and not for stealing other people's ebooks. Please do not use this program to distrbute illegal copies of ebooks. ... that would make Baby Jesus sad.