This Perl5 module to interface with the major()/minor() C routines.
Pftop is a small, curses-based utility for real-time display of active
states and rule statistics for pf, the packet filter (for OpenBSD)
This is muse, which lists out memory usage categorized by Active, Inactive,
Wired, Reserved, Cache, Buffer, Total, and Free in a manner more friendly
and verbose than vmstat and without as much clutter as top(1).
It is inspired in part by top(1), OS9's mfree, Linux's free, and DOS's
mem /c.
Helps for locating free GIDs.
Polkit-Qt is a library that lets developers use the Polkit API through
a nice Qt-styled API. It is mainly a wrapper around QAction and
QAbstractButton that lets you integrate those two component easily
with Polkit.
This is an object oriented perl interface to the FreeBSD jail subsystem.
Here's a replica of the 'jls' utility in just a few lines of perl:
use BSD::Jail::Object 'jids';
print " JID IP Address Hostname Path\n";
printf "%6d %-15.15s %-29.29s %.74s\n",
$_->jid, $_->ip, $_->hostname, $_->path foreach jids( instantiate => 1 );
And here's 'jexec':
my $j = BSD::Jail::Object->new( $ARGV[0] ) or die $@;
$j->attach && chdir('/') && exec $ARGV[1] or exit;
For more info please use 'perldoc' on the module.
Syslog messages--as standardized in RFC3164--embed a priority number
(the PRI part) which is composed of a severity and a facility
value. The constants which encode these values are specified in
section 4.1.1, and are made available by this module. For instance,
the exportable LOG_FTP constant has a value of 11, the value for the
FTP facility.
This module sends syslog messages over a network socket. It works like
Sys::Syslog in setlogsock's 'udp', 'tcp', or 'unix' modes, but without
the significant CPU overhead of that module when used for high-volume
logging. Use of this specialized module is only recommended if 1) you
must use network syslog as a messaging transport but 2) need to
minimize the time spent in the logger.
Adds/removes the home OU for when adding/removing a user.
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.