Free remote procedure call software for linux

Remote Growl is an extension to Glow which allows remote notification system for Max OS X (server) and any UNIX (client).

This package includes a Cocoa background application server, and a command line client to send notifications to a remote computer.

Remote Secure Command System project is a remote asynchronous and secure command system based on a file configuration.

A standalone server sends and receives commands through files, and a batch system launch ssh and scp commands.

Remote Monitoring Agent (RMA in short) is an auxiliary application for HostMonitor. Enterprise license for Advanced Host Monitor already includes license for 10 installations of the agent. Holders of a Lite, Standard or Professional licenses may buy an additional license for Remote Monitoring Agent separately.
HostMonitor 4.0+ can monitor remote networks using Remote Monitoring Agents (RMA). RMA is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.
Why you may need RMA? Here are just several reasons:
RMA increases security of the network. When you have to run the tests such as CPU Usage test or Performance Counters tests on a remote Windows system, HostMonitor must be able to log in to that system with administrators privileges. Instead you may now use an agent installed on that remote system. In this case HostMonitor will not have to log on to that system at all. HostMonitor needs just one TCP port to communicate with the RMA agent (by default it uses #1055 port, however you may set an agent to use any other port).
Remote Monitoring Agent is also a very useful tool when you have to monitor two (or many) separated networks (connected through Internet). In this case installing just one instance of RMA behind the firewall in network "A" will allow to monitor entire network "A" using the HostMonitor located in the network "B" with just one open TCP port.
RMA decreases the network traffic. E.g. frequent use of "File Integrity" or "Compare Files" tests in an array of remote systems may apply significant load on the network. The more and the bigger files you test the more traffic increase you get. RMA runs locally and sends only the test results to the HostMonitor thus decreasing the amount of network traffic.
Remote Monitoring Agent simplifies network administration. You no longer need to share local drives/folders to perform tests such as File Integrity, Folder/File Size, File Availability, Count Files, etc
RMA for Linux / BSD / Solaris allows you to perform tests that HostMonitor cannot perform. For example HostMonitor cannot monitor processes that are running on Linux systems. RMA can do that.
Main features:
- All traffic between Remote Monitoring Agents and HostMonitor is encrypted.
- It is possible to customize the list of enabled tests for each of the agents (e.g. living only Count Files and UNC tests only).
- You can restrict incoming TCP connections with the list of acceptable addresses.
- With RMA Manager you may configure, restart and even upgrade agent(s) remotely.

Remote Nmap (Rnmap) package contains both client and server programs. Actual idea for this sofware is that various clients can connect to one centralized Rnmap server and do their portscannings. Server does user authentication and uses excellent Nmap scanner to do actual scanning. Rnmap is written entirely in Python and is released under the terms of the GNU General Public License.

Version 0.10 of server is tested mainly on Linux, NetBSD and OpenBSD. Generally it should run on any *nix platform as long Nmap and Python are available for them. Console client is known to work with same platforms as server. Gui client will run on any python (with threads) supported platform.

Python Remote Call Module allows to transparently work with remote object in a python program.
To make this possible a kind of peer-to-peer design is used. Servers can be created explictly, as can clients by explicitly connecting to a server. If a client needs to have a server, e.g. so a reference to a local object can be passed to a remote destination, it is instantiated as needed.
Clients can have multiple connections. New connections are created when needed, e.g. when a remote reference to a new server is recieved.
WARNING:
This module is still in its experimental phase, so it is kind of usable, but an awful lot of bugs is still in it, and quite a few parts are not coded yet, others arent even designed yet.
Therefor lots of changes and outdated documentation should be expected.
Enhancements:
- All previous stub objects have been replaced by a single stub object which uses on-demand retrieval of attributes of remote objects.
- This way, the behavior of the stub object is much more flexible and smoother.
- A first draft of an authentication framework has been implemented so PyRCall can support many different authentication methods.
- Support for username/password-based authentication has been implemented.

vdr_remote is a graphical remote control for the video disk recorder vdr. vdr_remote connects over a TCP/IP network and gives you a complete remote control.

Data::ICal::Entry::Alarm::Procedure is a Perl module that represents a procedure-call alarm in an iCalendar file.

SYNOPSIS

my $valarm = Data::ICal::Entry::Alarm::Procedure->new();
$valarm->add_properties(
attach => [ "ftp://host.com/novo-procs/felizano.exe", { fmttype => "application/binary" } ],
# Dat*e*::ICal is not a typo here
trigger => [ Date::ICal->new( epoch => ... )->ical, { value => DATE-TIME } ],
);

$vevent->add_entry($valarm);

A Data::ICal::Entry::Alarm::Procedure object represents an alarm that calls a procedure (in some application-defined way), which is attached to a todo item or event in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

METHODS

new

Creates a new Data::ICal::Entry::Alarm::Procedure object; sets its ACTION property to PROCEDURE.

ical_entry_type

Returns VALARM, its iCalendar entry name.

optional_unique_properties

According to the iCalendar standard, the following properties may be specified at most one time for a procedure-call alarm:

duration repeat description

Note that if one of duration or repeat is specified, the other one must be also, though this module does not enforce that restriction.

mandatory_unique_properties

According to the iCalendar standard, the trigger and attach properties must be specified exactly once for a procedure-call alarm. (In addition, the action property must be specified exactly once, but the module automatically sets it for you.)