Ports 搜索

mtail is a small tail workalike that performs output coloring using ansi escape sequences (although the sequences are overridable, so you could cause it to output something else, e.g. html font tags, if you really wanted to). mtail is written in python, is fairly small, and should be relatively platform-independent. It has a config file that can contain an arbitrary number of entries, each of which has a series of regular expressions to indicate which files to color according to which entry. for each entry, the config file specifies a coloring scheme using regular expressions and, optionally, filters to apply to each line before coloring (for example, to strip out extra info, etc.). the config file also may override the predefined colors and the escape sequences (or whatever) actually used to perform the coloring.

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications don't know how to gain access through SOCKS servers. This means that network based applications that don't understand SOCKS are very limited in networks they can reach. An example of this is simple 'telnet'. If you're on a network firewalled from the internet with a SOCKS server for outside access, telnet can't use this server and thus can't telnet out to the Internet. tsocks' role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary.

GNU SASL is an implementation of the Simple Authentication and Security Layer framework and a few common SASL mechanisms. SASL is used by network servers (e.g., IMAP, SMTP) to request authentication from clients, and in clients to authenticate against servers. GNU SASL contains a library (`libgsasl'), a command line utility (`gsasl') to access the library from the shell, and a manual. The library includes support for the SASL framework (with authentication functions and application data privacy and integrity functions) and at least partial support for the CRAM-MD5, EXTERNAL, GSSAPI, ANONYMOUS, PLAIN, SECURID, DIGEST-MD5, LOGIN, NTLM and KERBEROS_V5 mechanisms. The library is portable because it does not do network communication by itself, but rather leaves it up to the calling application. The library is flexible with regards to the authorization infrastructure used, as it utilizes callbacks into the application to decide whether an user is authorized or not.

Logtool is a command line program that will parse ASCII logfiles into a more palatable format. It will take anything resembling a standard syslog file (this includes syslog-ng, multilog, and probably most of the other variantse), and crunch it into one of the following formats for your viewing pleasure: - ANSI (colorized for easy "at a glance" viewing) - ASCII (for e-mail'ed reports, and term's that don't support color) - CSV (for importing into your favorite spreadsheet/database) - HTML (for generating web pages) - RAW (for no good reason) It can be configured to parse the data any one of several ways, including suppressing duplicate messages, stripping the host, and/or program fields, and modifying the time display format (supports TAI64 timestamps produced by DJB's multilog) of the log entries.

This class provides an easy way to retrieve all the strings for a multilingual site from a data source (i.e. db). The following containers are provided, more will follow: - PEAR::DB - PEAR::MDB - PEAR::MDB2 - gettext - XML - PEAR::DB_DataObject (experimental) It is designed to reduce the number of queries to the db, caching the results when possible. An Admin class is provided to easily manage translations (add/remove a language, add/remove a string). Currently, the following decorators are provided: - CacheLiteFunction (for file-based caching) - CacheMemory (for memory-based caching) - DefaultText (to replace empty strings with their keys) - Iconv (to switch from/to different encodings) - Lang (resort to fallback languages for empty strings) - SpecialChars (replace html entities with their hex codes) - UTF-8 (to convert UTF-8 strings to ISO-8859-1)

zfsnap makes rolling ZFS snapshots easy and - with cron - automatic. The main advantages of zfsnap are its portability, simplicity, and performance. It is written purely in /bin/sh and does not require any additional software - other than a few core *nix utilies. zfsnap stores all the information it needs about a snapshot directly in its name; no database or special ZFS properties are needed. The information is stored in a way that is human readable, making it much easier for a sysadmin to manage and audit backup schedules. Snapshot names are in the format of pool/fs@[prefix]Timestamp--TimeToLive (e.g. pool/fs@weekly-2014-04-07_05.30.00--6m). The prefix is optional but can be quite useful for filtering, Timestamp is the date and time when the snapshot was created, and TimeToLive (TTL) is the amount of time the snapshot will be kept until it can be deleted.

Emacs major mode to create HTML files from Emacs buffers (in colour!) This major mode will output the contents of an Emacs buffer as a HTML file, preserving the colour attributes of that buffer. This is a pretty elegant solution to produce nice listings of your code in Erlang, C++, SML, Ruby (or whatever esoteric language you can dig out a major mode for) to display on web sites. As an example watch the ELISP code of this major mode http://fly.srk.fer.hr/~hniksic/emacs/htmlize.el.html Because the colouring depends only on your major mode and perhaps some individual settings (e.g. I prefer a dark background) you can turn any Emacs buffer into HTML.

Coppermine Photo Gallery is a picture gallery script. Users can upload pictures with a web browser (thumbnails are created on the fly), rate pictures, add comments and send e-cards. The admins can manage the galleries and batch add pictures that have been uploaded on the server by FTP. Images are stored in albums and albums can be grouped by categories. The script supports multiple users and each user can possibly have its own set of albums. The script also supports multiple languages and has a theme system. It uses PHP, a MySQL database and the GD library (version 1.x or 2.x) or ImageMagick to make the thumbnails. An install script makes the installation fast and simple.

SVN::Dumpfile represents a Subversion dumpfile. It provides methods to read existing and write modified or new dumpfiles. It supports dumpfiles with the version number 1 - 3 but was written in a tolerant way to also support newer versions as long no major changes are made. This module is a OO redesign and generalisation of SVN::Dumpfilter v0.21. Newer versions of SVN::Dumpfilter are using it to access the input and output dumpfiles. The ability to create new dumpfiles sets it apart from the similar module SVN::Dump. The submodule SVN::Dumpfile::Node::Properties also allows the processing of Subversion revision property files (i.e. the files lying in the $REPOSITORY/db/revprops/ directory holding the author, date and log entry of every revision).

GNU Pth - The GNU Portable Threads Copyright (c) 1999-2005 Ralf S. Engelschall <rse@gnu.org> Pth is a very portable POSIX/ANSI-C based library for Unix platforms which provides non-preemptive priority-based scheduling for multiple threads of execution (aka ``multithreading'') inside event-driven applications. All threads run in the same address space of the server application, but each thread has it's own individual program-counter, run-time stack, signal mask and errno variable. The thread scheduling itself is done in a cooperative way, i.e., the threads are managed by a priority- and event-based non-preemptive scheduler. The intention is that this way one can achieve better portability and run-time performance than with preemptive scheduling. The event facility allows threads to wait until various types of events occur, including pending I/O on file descriptors, asynchronous signals, elapsed timers, pending I/O on message ports, thread and process termination, and even customized callback functions.