README FOR autosync 1.4 ----------------------- autosync uses a configuration file to automatically copy files from the local host to a number of remote hosts. File transfers take place using rsync over SSH. INSTALLATION ------------ In the Makefile, set INST_ROOT to wherever you want the software installed. You may also need to change the INSTALL command, depending on the location and version of "install" on your system. Then run "make install", and set up your autosync.conf. USE --- "autosync -h" will print out a usage statement, including a summary of the config file syntax. Basically, the usage is: autosync [-f config_file] [hostname...] The default config file location is /usr/local/etc/autosync.conf; this can be changed with the "-f" option. The optional list of hostnames restricts the processing of the config file to only those lines with that hostname; otherwise the entire config file is processed. The config file has lines in the following format: hostname username timeout rsync_path dest_dir src_file src_file... The hostname is the host to which the files will be copied. The connections take place as the specified username. The inactivity timeout is in seconds; 0 disables the timeout. The rsync_path specifies where rsync is on the remote host. The src_files on the local host are copied to the dest_dir on the remote host. An example autosync.conf is included with the distribution. PLATFORMS --------- autosync has been written for portability to most UNIX systems. It's been tested on the following platforms: - Linux - Red Hat, versions 7.0, 7.1 - Solaris - versions 7, 8 CHANGES ------- You're not required by the license to submit changes back to the source, but I'd appreciate portability improvements or enhancements of general applicability. You can email new versions or contextual diffs ("diff -c old_file new_file") to . Some things to keep in mind if you do this: - Formatting - I use tabs for indentation, and sometimes to align code segments for readability. Please do the same. - Please don't use NotePad or some other Windows editor to make changes. Or if you do, get rid of the DOS linefeeds before submitting changes. - Please try to follow the formatting conventions established in the existing code. - Readability - Usually, I will trade off efficiency (of running time or of development time) in favor of readability. - Insert meaningful comments where appropriate. - Portability - All shell scripts are Bourne-compatible. I won't use shell- specific constructs from bash, ksh, etc. - Don't use OS-specific features, pathnames, etc., unless they're guarded by code checking the OS version, or they're in user-settable variables toward the top of the script. CONTRIBUTORS ------------ Leon Towns-von Stauber Enjoy! Copyright (c) 2001-2007. All rights reserved. See the LICENSE file distributed with this code for restrictions on its use and further distribution. Original distribution available at .