Ports 搜索

The core Nepomuk system contains of the central services like file indexing, file system monitoring, query, and of course storage, as well as the corresponding client libraries. This is a compile time dependency for kde4-runtime.

The NepomukWidget libraries Nepomuk extends the search and tagging functionalities in AkonadiConsole

Yet another FreeBSD jail and bhyve management tool.

File::Next is a lightweight, taint-safe file-finding module. It's lightweight and has no non-core prerequisites.

Proc::PidUtil provides utilities to manage PID files.

A tool which prints PID of given process name.

Proclet is minimalistic Supervisor, fork and manage many services from one perl script.

Given a line from a crontab, tells you the time at which cron will next run the line, or when the last event occurred, relative to any date you choose. The object keeps that reference date internally, and updates it when you call nextEvent() or previousEvent() - such that successive calls will give you a sequence of events going forward, or backwards, in time. Use setCounterToNow() to reset this reference time to the current date on your system, or use setCounterToDate() to set the reference to any arbitrary time, or resetCounter() to take the object back to the date you constructed it with. This module uses Set::Crontab to understand the date specification, so we should be able to handle all forms of cron entries.

This module provides a simple but complete cron like scheduler. I.e this modules can be used for periodically executing Perl subroutines. The dates and parameters for the subroutines to be called are specified with a format known as crontab entry (see manpage crontab(5) or documentation of Schedule::Cron). The philosophy behind Schedule::Cron is to call subroutines periodically from within one single Perl program instead of letting cron trigger several (possibly different) Perl scripts. Everything under one roof. Furthermore Schedule::Cron provides mechanism to create crontab entries dynamically, which isn't that easy with cron. Schedule::Cron knows about all extensions (well, at least all extensions I'm aware of, i.e those of the so called "Vixie" cron) for crontab entries like ranges including 'steps', specification of month and days of the week by name or coexistence of lists and ranges in the same field. And even a bit more (like lists and ranges with symbolic names).

This package allows accessing loading and top job status across many machines on a network, comprising a server farm. It also allows for scheduling new jobs on the best machine across the entire network.