Free remote host software for linux

rmRemote project lets you remote control xmms with a REALmagic Remote. In the future it may be used to control everything in your house if you add the functionality.

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.

File::Remote is a Perl module to read/write/edit remote files transparently.

SYNOPSIS

#
# Two ways to use File::Remote
#
# First, the function-based style. Here, we can use the
# special :replace tag to overload Perl builtins!
#
use File::Remote qw(:replace); # special :replace tag

# read from a remote file
open(REMOTE, "host:/remote/file") or die $!;
print while (< REMOTE >);
close(REMOTE);

# writing a local file still works!
open(LOCAL, ">>/local/file");
print LOCAL "This is a new line.n";
close(LOCAL);

mkdir("host:/remote/dir", 0755);
unlink("host:/remote/file");
unlink("/local/file"); # still works too!
symlink("host:/remote/src", "host:/remote/dest");

chown("root", "other", "host:/remote/dir/file");
chmod(0600, "host:/remote/dir/file");

#
# Next, the object-oriented style, if you dont want to
# mess with the builtins.
#
use File::Remote;
my $remote = new File::Remote;

# Standard filehandles
$remote->open(FILE, ">>host:/remote/file") or die $!;
print FILE "Heres a line thats added.n";
$remote->close(FILE);

# Create a new file and change its permissions
$remote->mkdir("host:/remote/dir");
$remote->touch("host:/remote/dir/file");

# Move files around
$remote->copy("/local/file", "host:/remote/file") or warn $!;
$remote->move("host:/remote/file", "/local/file");

# Read and write whole files
my @file = $remote->readfile("host:/remote/file");
$remote->writefile("/local/file", @file);

# Backup a file with a suffix
$remote->backup("host:/remote/oldfile", "save");

# Use secure connection methods
my $secure = new File::Remote (rsh => "/usr/local/bin/ssh",
rcp => "/usr/local/bin/scp");
$secure->unlink("/local/file");
$secure->rmdir("host:/remote/dir");

This module takes care of dealing with files regardless of whether theyre local or remote. It allows you to create and edit files without having to worry about their physical location on the network. If a file passed into a function is of the form host:/path/to/file, then File::Remote uses rsh/rcp (or ssh/scp, depending on how you configure it) to edit the file remotely. Otherwise, it assumes the file is local and passes calls directly through to Perls core functions.

The nice thing about this module is that you can use it for all your file calls, since it handles both remote and local files transparently. This means you dont have to put a whole bunch of checks for remote files in your code. Plus, if you use the function-oriented interface along with the :replace tag, you can actually redefine the Perl builtin file functions. This means that your existing Perl scripts can automatically handle remote files with no re-engineering(!).

Remote MySQL Query is a PHP class that can easily execute queries on a remote MySQL server using only HTTP.

It works by accessing a PHP script on the remote web server that executes queries based on passed in URL parameters.

The client passes a secret key to the remote script to prevent unauthorized access.

The remote script passes back the results to the requesting client using XML to marshal the data.

The class parses the results XML data returned by the server script and returns an array.

It, also, retrieves (into class variables) the number of records returned by the query and the time the query took to execute.

The server script may be used to execute MySQL queries that can be retrieved by programs written in other languages besides PHP.

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.

AmaroK XUL Remote is an amaroK script that allows you to control amaroK from any Firefox browser on your network.
Main features:
- basic player manipulation: play, pause, stop, next, previous, seek, volume
- playlist view, plays a track when clicking on it
- collection browser with filtering, support for compilations
- drag and drop tracks, album and artists from the collection to the playlist

Passwordless remote logins script can be used to:

1: Create 1024 bit passwordless dsa keys.
2: Send key to remote server via scp.
3: Create remote .ssh directory and move key to authorized_keys file.

This will allow you to login to remote server via ssh or run automated rsync backups. You need openssh, bash and expect installed for this to work. Optionally you can create an executeButton with the following format for a one click remote server login.

The format: konsole -e ssh -i /your/path/toyour-key remoteusername"@"remotehost_or_ip

The Eye Of Horus is a monitoring and alerting tool for computers. Its mainly useful for monitoring network services (eg, HTTP or SMTP servers) and the internal status of Unix servers (eg, load, disk usage, process counts).

In that respect, its a lot like Nagios, but in my opinion its better. It lacks a few features Nagios has, but it is a very simple architecture to which they can easily be added.

Its a flexible thing made from independent modules with well-defined interfaces, making it easy to customise and extend, but out of the box itll monitor your servers and produce a nice HTML summary of their status - OK, the looks need a bit of work, but that will come soon, and it can optionally integrate with the excellent (and I mean excellent) RRDTool to store logs of statistics (response times, number of packages with known security holes, etc) - and link from the status page to nice graphs of the historical behaviour of these statistics.

HOW IT WORKS

The core of the system is horus-check.py, a Python script which reads a configuration file (specified on the command line). The configuration file specifies a list of services - either network services, in which case the host to run the check from and the host to run the check at are specified, or local services, in which case only the host to run the check from need be specified. In either case, if the host to run the check from is not specified, then it defaults to the local host.

The service types reference definitions in a file which is referenced from the configuration file. In the service definitions file, a shell command to check the service is given; this command must output service status in a defined format, as a single-line YAML list. The list must contain, at least, a single-word status (OK, WARNING, FAILURE, or UNKNOWN), then optionally numeric statistics, then optionally a status message. For example:

[OK]
[UNKNOWN]
[OK, { load: 0.5, users: 3 }]
[WARNING, { load: 3, users: 30 }]
[FAILURE, { load: 95, users: 300 }]
[UNKNOWN, { }, Could not find AWK executable]

When a check is to be performed from a remote host, Horus opens an ssh connection to that host. It is assumed that the user horus is run as will have an ssh key set up to enable it to ssh to all such hosts without requiring a password.

Having performed the checks, horus-check.py then:

Reads in the status database named in the configuration file
Updates the status database with the new status of hosts
Computes an overall system status (the worst non-unknown status of any checked service)
Examines the service dependencies, and marks any service whose state is no worse than might be expected (eg, no worse than the worst state of a service it depends upon) are automatically marked as quiet
Computes a list of differences between the old and new status (services added, services removed, services whose status has improved, services whose status has worsened)
If there are any differences, invokes a notification script (named in the configuration file) with them, along with the overall status
Invokes a logging script (named in the configuration file) with the new value of every statistic reported by the service checks; I will soon provide a sample logging script that uses RRDTool to generate nice graphs.

The status database (which is written in YAML, so easily accessible to user scripts) can then be used to generate HTML status report (see status.cgi).