Free remote files software for linux

Remote File Index is an add-on for Plone which keeps track of a document only by its url.
Did you ever find a huge pdf file that youd like to keep track of but wouldnt like to copy it entirely on your server ?
Now RemoteFileIndex indexes the content in the portal Catalog and only keeps the url of that document.
Works with:
- Plone 2.5.2
- Plone 2.5.1
- Plone 2.5
Enhancements:
- better integration with ATContentType

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.

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(!).

Xmms::Remote is a Perl Interface to xmms_remote API.

SYNOPSIS

use Xmms::Remote ();
my $remote = Xmms::Remote->new;
$remote->play;

This module provides a Perl interface to the xmms remote control interface. No docs yet, sorry, see test.pl and Xmms.pm for now

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.

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

AVIRA Webmin Remote Panel is designed to make the maintenance of AVIRA products easier and less time consuming.
This product addresses mainly the users of AVIRA server products and especially the system administrators who must keep track of various services on production servers.
Complex solutions based on multiple AVIRA products for Unix are now easy to configure and maintain with AVIRA Webmin Remote Panel. It is smoothly integrated as a module of the Webmin configuration tool, intended to meet the needs of system administrators.
This is a separate application that was developed as a Webmin module, being a handy graphical tool and a time saver for companies dealing with multiple AVIRA products. Via a straightforward graphical interface, AVIRA Webmin Remote Panel helps managing configuration files and eases the maintenance process of AVIRA solutions.
Placed between the configuration files and the system administrator, this module helps managing the following AVIRA products:
- AVIRA Desktop for Unix
- AVIRA for Unix Server
- AVIRA MailGate
- AVIRA for Sendmail-Milter
- AVIRA WebGate
AVIRA Webmin Remote Panel highlights a simple management interface, designed to configure and smoothly control AVIRA products installed on a network. This application helps you stay informed about the status of your currently running AVIRA solutions, displaying the messages generated by these applications in the system logs.
AVIRA Webmin Remote Panel also manages the engine settings, helping to keep track of administration alerts, licenses and other related aspects.
Main features:
- Configuration of AVIRA Desktop for Unix;
- Configuration of AVIRA for Unix Server;
- Configuration of AVIRA MailGate;
- Configuration of AVIRA Sendmail-Milter;
- Configuration of AVIRA WebGate;
- Simple interface for controlling installed AVIRA products on your system;
- Simple interface for displaying the messages generated by AVIRA products in the system logs.

IR File Chooser is an infrared remote-controlled fileselection menu.
Infra Red (IR) File Chooser is a remote-controlled menu for selecting files and loading them by an assigned program.
You can add as many filetypes and associated programs as you wish.
The functionality of Infra Red (IR) File Chooser may be extended using Perl or Shell scripts.
The GUI was created with Perl::GTK and it uses RCU::Lirc to fetch the remote controller commands.
Enhancements:
- A fix for the DROPREPEATS option.