Well, there you go. rsyncd is already set up on your system. You don't
run rsync, inetd does. The way it's set up makes it nice for testing,
too, as you just edit the conf file and test it.
If this is, in fact, another installation of rsyncd, which you shouldn't
mess with, you'll have to call rsync --daemon with --port=something and
--config-file=something to use your alternate setup.
If, on the other hand, this is your installation, but you wish to manually
start rsync, you'll have to comment out (or delete) the rsync line in
/etc/inetd.conf and HUP inetd. What you've go, however, is better, in my
opinion.
The doc you reference describes a directly-run rsyncd. If you did your
install from that, you wouldn't have done the inetd.conf setup, so it
looks like you've got a previous setup on your system. If it's your
system now, just edit /etc/rsyncd.conf as needed. changes are
instantaneous, affecting subsequent calls to the daemon.
test = "rsync localhost::"
should list your modules.
Tools@willy
/users/Tools>grep \\[ /etc/rsyncd.conf
[big]
[big1]
[ToolSyncModules]
Tools@willy
/users/Tools>rsync localhost::
big
big1
ToolSyncModules
Tools@willy
/users/Tools>
This way, rsyncd also doesn't take any resources until it's invoked.
Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"David Nickel Jr." <dnickel@aug.edu>
01/11/2002 09:41 AM
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc:
Subject: RE: Error Message!!
Classification:
I am falling this article http://www.freebsddiary.org/rsync.php on
installing and configuring rysnc to mirror the web directories of my two
web
servers.
here is the output
netstat -an |grep 873
tcp4 0 0 *.873 *.* LISTEN
tcp46 0 0 *.873 *.* LISTEN
grep 873 /etc/services
rsync 873/tcp # Rsync Daemon
grep rsync /etc/inetd.conf
rsync stream tcp nowait root /usr/local/bin/rsync
rsyncd --daemon
-----Original Message-----
From: tim.conway@philips.com [mailto:tim.conway@philips.com]
Sent: Friday, January 11, 2002 11:32 AM
To: David Nickel Jr.
Subject: RE: Error Message!!
That's why i included the part about indetd.conf and services. Most
likely, your inetd is configured to handle port 873. The fact that you
have two listeners on 873 tell me, however, that it may not be for rsync,
as rsync is a TCP-only application, and only one thing can have a
port/protocol listener open, so the other port 873 you see is probably
something listening on UDP, else, you're seeing a listener and a
connection.
lsof and some versions of fuser can be used to determine what is using a
port. poke around the man pages to find it.
If those aren't available, send me the output of
"netstat -an |grep 873;grep 873 /etc/services"
and if there's something found in services,
"grep <first word on the line from services> /etc/inetd.conf"
Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"David Nickel Jr." <dnickel@aug.edu>
01/11/2002 09:19 AM
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc:
Subject: RE: Error Message!!
Classification:
Thanks for the info. I used netstat there are two occurances of port 873
listening... how do I kill them. When I grep ps I rsync is not running..
David
-----Original Message-----
From: tim.conway@philips.com [mailto:tim.conway@philips.com]
Sent: Friday, January 11, 2002 11:16 AM
To: David Nickel Jr.
Cc: Rsync Mailing List
Subject: Re: Error Message!!
Almost certainly, something is already using port 873 - probably a
previous invocation of rsync --daemon, or you have inetd listening to it
already.
On a commandline invocation, rsync forks, so invoking it twice in a row
without killing the first one or having the first one die, makes the
second invocation fail, unless you specify different ports for each one.
In this example, rsync is run from inetd, though not active at the moment.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Tools@willy
/cadappl/encap/packages>netstat -an |grep 873
*.873 *.* 0 0 0 0 LISTEN
Tools@willy
/cadappl/encap/packages>ps -ef |grep rsync
Tools@willy
/cadappl/encap/packages>grep rsync /etc/services /etc/inetd.conf
/etc/inetd.conf:rsync stream tcp nowait root /usr/bin/rsync
rsyncd --daemon
/etc/services:rsync 873/tcp rsyncd # rsync
daemon
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Good luck.
Tim Conway
tim.conway@philips.com
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"David Nickel Jr." <dnickel@aug.edu>
Sent by: rsync-admin@lists.samba.org
01/11/2002 08:49 AM
To: "Rsync Mailing List" <rsync@lists.samba.org>
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Error Message!!
Classification:
When rsync starts I get the following messages in my log file
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873
Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code
10) at socket.c(361)
Anybody know what might be causing this?
David