Free procedure software for linux

RPC::XML::Procedure is an object encapsulation of server-side RPC procedures.

SYNOPSIS

require RPC::XML::Procedure;

...
$method_1 = RPC::XML::Procedure->new({ name => system.identity,
code => sub { ... },
signature => [ string ] });
$method_2 = RPC::XML::Procedure->new(/path/to/status.xpl);

IMPORTANT NOTE

This package is comprised of the code that was formerly RPC::XML::Method. The package was renamed when the decision was made to support procedures and methods as functionally different entities. It is not necessary to include both this module and RPC::XML::Method -- this module provides the latter as an empty subclass. In time, RPC::XML::Method will be removed from the distribution entirely.

The RPC::XML::Procedure package is designed primarily for behind-the-scenes use by the RPC::XML::Server class and any subclasses of it. It is documented here in case a project chooses to sub-class it for their purposes (which would require setting the method_class attribute when creating server objects, see RPC::XML::Server).

This package grew out of the increasing need to abstract the operations that related to the methods a given server instance was providing. Previously, methods were passed around simply as hash references. It was a small step then to move them into a package and allow for operations directly on the objects themselves. In the spirit of the original hashes, all the key data is kept in clear, intuitive hash keys (rather than obfuscated as the other classes do). Thus it is important to be clear on the interface here before sub-classing this package.

pyctures is a small web gallery written in Python that uses the web.py framework. It does not use any database and stores all the necessary data in the filesystem.
pyctures is published under the BOLA (Public Domain), so you can run the software anywhere, and do whatever you want with it.
Installation:
The installation procedure depends on the HTTP server youre using. What follows is a list of procedures for some common HTTP servers. If you use pyctures with something else, please let me know so I can add it here.
After youve completed the install, read the "Administration" file to learn how to manage your gallery.
Common procedure
1. Copy the "website" directory to a suitable place where you want to install
pyctures. It does not have to be inside your website, but has to be
readable by your webservers user.
2. Create a "config.py" file based on the "config.py.sample" file, and edit it
according to your configuration. A really important setting is the album
path, where all albums will be stored. It can be anywhere you want. Create
an admin user so you can create albums using the web interface.
3. Make sure the album path is writeable by the user who will run the pyctures
application. It usually is your web server user.
4. Install PIL from http://www.pythonware.com/products/pil/. The package name
for most distributions is "python-imaging" or just "imaging".
5. Install cheetah from http://www.cheetahtemplate.org/. The package name for
most distributions is "python-cheetah" or just "cheetah". You need at least
version 2.0-rc5.
No server (stand-alone)
pyctures can be run without any HTTP server by just executing
"./pyctures [PORT]" directly on the website directory. Its useful for
testing and small sites. I recommend that you test everything works this way
before integrating it into a webserver.
lighttpd
First of all, install "flup", from http://www.saddi.com/software/flup/.
Gentoo: Its not in portage, it sucks. Check
http://bugs.gentoo.org/show_bug.cgi?id=100784
Debian: apt-get install python-flup
Now, lets suppose youve installed pyctures in the "/var/www/pyctures"
directory, and want to publish it under the "/pics/" directory.
You need to add the following to /etc/lighttpd/mod_fastcgi.conf (or just
/etc/lighttpd/lighttpd.conf if you dont have the other file):
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
fastcgi.server = (
"/pics" => ((
"socket" => "/tmp/fastcgi-pics.socket",
"max-procs" => 1,
"bin-path" => "/var/www/pyctures/pyctures"
))
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
This is enough, but be aware that "http://mysite/pics" (note the missing
"/" at the end) will *not* be redirected to pyctures.
If you want to be able to refer to your pyctures root both as
"http://mysite/pics/" and "http://mysite/pics", you need to add the
following in the same file as before:
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
url.redirect = (
"^/pics$" => "/pics/"
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
And then create an empty file in your document root called "gallery",
otherwise lighttpd will think the path does not exist and return 404 before
doing the redirection.
Enhancements:
- This version implemented pagination, IE support, and automatic thumbnail regeneration on config changes.
- It also improved performance considerably, reduced the memory footprint, added Apache installation instructions, and included several other minor improvements.

PloneExFile provides a Plone/AT content type with an attachment, supporting preview & indexing & lock.
PloneExFile is a file like content type that provides indexing and preview support for MS Word, MS Excel, MS Powerpoint, PDF and OO Writer files.
Works with:
- Plone 2.5
- Plone 2.1
Enhancements:
- Added German translations and fixed description of upgrade procedure; provided by Carsten Kirck. Thank you!

portmap is a part of the ONCRPC collection of software for implementing remote procedure calls between computer programs. This project is use widely by NFS and NIS, and assorted other systems.
Some make variable can be used to control compilation.
NO_TCP_WRAPPER= if non-empty, doent use tcp_wrappers
USE_DNS= if set, tcp_wrappers can check peers based on hostname
as well as IP address. This should only be used if you
are certain that gethostbyname will never trigger a
called to portmap (as it might if nis is used for hostnames).
RPCUSER= is set, portmap will use getpwnam to find the user for
that user, and will setuid to that user before listening
for incoming messages
DAEMON_UID= Can be set to a number to override the default UID
to setuid to. Default is 1.
DAEMON_GID= As above, but for setgid.
Enhancements:
- This first new release in 10 years combines assorted patches from different Linux distributions.
- Security was improved so that privileged services can register non-privileged ports that cannot then be unregistered by other users.

Plone Error Reporting is a project which facilitates the submission of useful bug reports to Plone.
PloneErrorReporting replaces default_error_message and prefs_error_log_showEntry with pages that facilitate the submission of useful bug reports to Plone.
It is designed with the goal of improving the information provided by bug reporters.
To see PloneErrorReporting in action, first install the product, then create a python script called imabug in the ZMI that contains the single line
raise AttributeError, bad attribute
Now, while still authenticated, load the page http://mysite/imabug. You should see a step-by-step procedure for reporting bugs at the bottom of the error page as long as you are logged in as a Manager. Similarly, when you view bugs in the Plone error log, you will see the bug submitting procedure.
Enhancements:
- Moved the product to use its own translation domain. This fixes an issue were half-translated sentences showed up in the templates.

SYNOPSIS

use DCE::RPC; use Authen::Perl::NTLM qw(lm_hash nt_hash);
use constant DCOM_IREMOTEACTIVATION => pack("H32", "B84A9F4D1C7DCF11861E0020AF6E7C57");
use constant DCOM_IF_VERSION => 0x00;
use constant DCOM_XFER_SYNTAX => pack("H32", "045D888AEB1CC9119FE808002B104860");
use constant DCOM_XFER_SYNTAX_VERSION => 0x02;

$passwd = "passwd";
$lm_hpw = lm_hash($passwd);
$nt_hpw = nt_hash($passwd);
$ntlm = new_client Authen::Perl::NTLM($lm_hpw, nt_hpw);
$rpc_host = "www.rpc.com";
$rpc_port = 135;
$rpc = new DCE::RPC($rpc_host, $rpc_port, $ntlm);
$bind_msg = $rpc->rpc_bind_ack_resp(1, DCOM_IREMOTEACTIVATION, DCOM_IF_VERSION,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));
$request_msg = $rpc->rpc_co_request("Hi, there! This is Stub!", 1, 0x0e, DCOM_IREMOTEACTIVATION, "Authentication Credentials");
$response_msg = $rpc->rpc_request_response($request_msg);
$alt_ctx_msg = $rpc->rpc_alt_ctx(1, DCOM_IREMOTEACTIVATION . DCOM_IF_VERSION
,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));

The DCE RPC protocol is an application level protocol from OpenGroup that allows applications to do Remote Procedure Calls. It is the underlying wire protocol for DCOM (Distributed Common Object Model) by Microsoft.
This module was motivated by an reverse-engineering effort on a DCOM client. Therefore, functions that are implemented gear more toward client side implementation. Also, the initial version only supports Connection Oriented version of DCE RPC. It also assumes NTLMSSP as the underlying authentication protocol. This can change based on the input of the users of this modules.

Jeremiah is a set of PHP scripts that aims to make regular downloads a completely automatic procedure.
From finding the files of intrest all the way to unpacking them into in the directory of choice, everything is done without user interaction. Jeremiah supports different download methods through addon scripts.
At the moment, only a addon for downloads via BitTorrent is available.
Main features:
- Pluginsystem for automatic downloads.
- (currently there is only a plugin for the download of torrents)
- Support for multipel checksum file types.
- (Currently only PAR, PAR2, SFV and Torrent are preconfigured but any fyletype supported by cfv can be used.)
- Support for multipel compressed file types.
- (Currently only rar, 7z and rar are preconfigured but any other filetype and decompression software can easily be added.)
- Recrusive scanning of multipel incoming directories
- Automatic detection of redundant checksum files.
- Semi-Smart file verification.
- (Downloads arnt verifyed until all files have been completly downloaded.)
- 100% no user interaction
- (Jeremiah is designed to run without any user interaction, for example by cron)

Jim is an opensource small footprint implementation of the Tcl programming language. It implements a large subset of Tcl and adds new features like references with garbage collection, closures, built-in Object Oriented Programming system, Functional Programming commands, First class arrays. All this with a binary size of 70kb (that can be reduced further excluding some command).
Jim is currently a work in progress, but most of the core language is already implemented and it is possible to use it to run many unmodified Tcl programs, so if you want to start to evaluate it, or want to look at our internal design and virtual machine, go to the download section.
Jims goal is to provide a powerful language implemented in roughly 10k lines of code that is presented as a single C file and an header file, in order to allow developers to put Jim inside their applications, as scripting language, configuration file syntax, without to depend on external libraries or other big systems.
We belive scripting is a very interesting feature for many applications, but developers are often not encouraged to link the application to a big external system. Jim try to address this problem providing a very simple to understand and small footprint implementation of a language that is ideal for scripting, and at the same time is powerful and able to scale.
Another field where Jim may help is the one of Embedded Systems. Jim is written in ANSI-C, is very little both in binary size and memory requirements, and the Tcl language is just ideal for this tasks (For example, CISCO routers are using Tcl).
Main features:
- Support for important features that will be availabe in Tcl8.5, like dict and {expand}.
- Arrays in Jim arent collection of variables like in Tcl, but a first class type. Array access syntax is in Jim syntax sugar to set and get dictionaries elements.
- A compact design. Jim is currently less than 10k lines of code. It does a heavy use of dual ported objects, in Jim even the VM pseudo-bytecode is a specialized Jim_Obj type.
- lambda with garbage collection, and a reference system to build linked data structures.
- closures, Jims procedures can have persistent procedure-specific variables (called statics). Statics initialization value can be caputred form the procedure creation context, so it is very similar to lexical scoping to use. This is how The Paul Grahams accumulator procedure looks like in Jim:
proc accumulator n {
lambda increment n {
set n [+ $n $increment]
}
}
- Math operations as commands (together with expr support).
- Ability to load extensions at runtime via a STUB system. Even programs using Jim that are linked statically are able to load extensions.
- 70Kbyte binary size!.