Here's one of my setups. It's invoked from inetd.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Tools@timsync
/home/Tools/newsync/clients/sparetool>grep rsync /etc/inetd.conf
/etc/services ;cat /etc/rsyncd.conf
/etc/inetd.conf:rsync stream tcp nowait root /usr/bin/rsync
rsyncd --daemon
/etc/services:rsync 873/tcp rsyncd # rsync
daemon
log file = /var/tmp/rsyncd.log
pid file = /var/run/rsyncd.pid
[master1]
path = /mastertoolservers/master1
refuse options = checksum
read only = yes
use chroot = no
uid = Tools
gid = Tools
ignore nonreadable = yes
[master2]
path = /mastertoolservers/master2
refuse options = checksum
read only = yes
use chroot = no
uid = Tools
gid = Tools
ignore nonreadable = yes
[admin]
path = /mastertoolservers/master2/admin
refuse options = checksum
read only = yes
use chroot = no
uid = Tools
gid = Tools
ignore nonreadable = yes
[incoming]
path = /users/Tools/incoming
read only = no
use chroot = no
uid = Tools
gid = Tools
list = no
Tools@timsync
/home/Tools/newsync/clients/sparetool>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here's a little script I crapped together to fire one up in any arbitrary
site where I don't have root. An idling rsyncd doesn't eat much cpu or
ram. I just reference it in the crontab for my user, and there's always
one waiting for me.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#!/bin/sh
PATH=/bin:/usr/bin:/usr/sbin:/sbin:/etc:/cadappl/encap/bin
export PATH
pidfile=$HOME/.rsyncd.pid
logfile=$HOME/.rsyncd.log
configfile=$HOME/.rsyncd.conf
[ -f "$pidfile" -a -s "$pidfile" ] && ps -p `cat "$pidfile"` |grep rsync
>/dev/null && exit 0
{
echo "log file = $logfile
pid file = $pidfile
[cadappldist]
lockfile = /var/tmp/rsyncd.cadappldist.lock
max connections = 2
path = /cadappldist
use chroot = no
read only = yes
uid = Tools
gid = Tools
list = yes
[cadappldistrw]
lockfile = /var/tmp/rsyncd.cadappldistrw.lock
max connections = 1
path = /cadappldist
use chroot = no
read only = no
uid = Tools
gid = Tools
list = no" >$configfile
rsync --daemon --port=4024 --config=$configfile
}</dev/null >&0 2>&1 &
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
There'a a lot more useful info in the man pages. examine "--port=" and
"--daemon", and maybe "--no-detach" in rsync(1), and read rsyncd.conf(5)
all the way through. You can have password authentication, exclusions,
parameter control... lots of stuff.
Good luck.
Tim Conway
[EMAIL PROTECTED] reorder name and reverse domain
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
11/13/02 12:45 PM
Please respond to uwp
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Subject: Re: Speed problem
Classification:
On Wed, 13 Nov 2002 [EMAIL PROTECTED] wrote:
> I agree, rsh as root is bad. I wouldn't suggest that. I'm talking
about
> running "rsync --daemon", using /etc/rsyncd.conf to control the form of
> the access. It's pretty good for reading, and mostly works for writing.
Do I get you right ? You don't need any transport mechanism, rsync can
to everything by itself ? I thought rsh or ssh is a must. Can you give an
example how to do it ?
Thank you !
Mermgfurt,
Udo
--
Udo Wolter | /"\
email: [EMAIL PROTECTED] | \ / ASCII RIBBON CAMPAIGN
www: www.dicke-aersche.de | X AGAINST HTML MAIL
dark: [EMAIL PROTECTED] | / \
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
