rsync - Jul 2002 - SCO Unix Sys V - Rel. 3.2.4.2 / rsync problem

Salim:  I suspect that if you check the timestamp, you'll find that that 
binding failure is left over from an earlier attempt, before you were 
properly configured.  Your description of you inetd.conf/services setup 
sounds correct.  Your commandline, though, shouldn't work.  You name a 
directory as the source, but don't say to do its contents.  However, I 
would expect an error from that - something like this:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Tools@timsync
/users/Tools/newsync/clients/dal-tools2>rsync willy::Tools .
client: nothing to do: perhaps you need to specify some filenames or the 
--recursive option?
Tools@timsync
/users/Tools/newsync/clients/dal-tools2>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Regardless, it looks like an OS-related problem.  Your setup is identical 
to mine.  What appears to be happening is that rsync is not detecting that 
it's being called as a daemon from inetd, so it's trying to set up its
own
listener on 873, which is already taken by inetd.  I remember some related 
problems, where people trying to start rsync as a standalone system were 
having failures, because it detected stdin as a socket, so it thought it 
was just supposed to spawn a handler, rather than set up a listener.  I 
think you're getting the opposite problem.
I'd suggest commenting out the rsync line in inetd.conf, kill -HUP <pid
of
inetd> (there's no reason to reboot), and run "rsync --daemon".
This
should go right back to a prompt, but if you ps for it, you'll see it 
waiting.
rsync localhost::, and you'll get a listing of your modules.
If you want to just run it this way, write something to get it started on 
boot.  I can't remember the SCO init chain (or any old sysV systems, for 
that matter), but I'm sure you can trace it out if you don't already
know
how, starting from the inittab and working your way out.
If you'd like to run it from inetd (my preferred way - makes config 
changes trivial), perhaps someone on the list I've CCed can shed some 
light.  Regardless, I'd suggest examining the site http://rsync.samba.org. 
 There, you can also subscribe to the above-mentioned list.  On the list, 
you'll find the actual developers of the utility, and find the most useful 
help.

Good luck,

Tim Conway
tim.conway@philips.com
303.682.4917 office, 3039210301 cell
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?"




"Salim Soormally" <salimwng@bow.intnet.mu>
07/22/2002 06:49 AM
Please respond to salimwng

 
        To:     Tim Conway/LMT/SC/PHILIPS@AMEC
        cc: 
        Subject:        SCO Unix Sys V - Rel. 3.2.4.2 / rsync problem
        Classification: 



 
Hello Tim,
 
I have come across your email address while browsing the newsgroup of 
google on rysnc.
 
In fact I have got a serious problem, and though I have posted many reply 
on several UNIX newsgroups, nobody has been able to help by now.  I have 
decided to contact you directly because I notice that you are able to 
reply to some old SCO operating systems.
 
Please see my problem below on rsync.  I would much appreciate if you 
could give me a helping hand in that.
 
You also mentioned that rsync is not run like that, it's inetd.conf who 
launches it.  Am completely confused.  I want to use rsync in such a way 
like a normal command ( e.g. rcp..... ).  How can I do that please ?
 
Thank you very much for your time,
Best regards.
Salim
 
 
========DETAILED PROBLEM ===================================Platform: SCO Unix
Sys V-Rel 3.2.4.2

Unix Machine 1 = Unix486.AWDOM = IP Address 10.0.0.10
Unix Machine 2 = DemoUnix.AWDOM= IP Address 10.0.0.3
Aim: To copy Data files from Machine 1 to Machine 2 through rsync.

Hello guys,

I have been able to setup the rcp command to run successfully on my 
system, through your help. 

Now i am trying to have rsync installed as it has got many features more 
than rcp.  However i am getting the error message in syslog file.  Error 
is :DemoUnix rsync[2347]: bind failed on Port 873.

I have performed the following;

1.  add rsync [TAB] 873/tcp in /etc/services.
2.  add rsync [TAB] stream [TAB]tcp [TAB] nowait [TAB] root [TAB] 
/usr/bin/rsync rsyncd --daemon.
3.  Rebooted the machine ( root> init 6 )

Then i edited a new file, called /etc/rsyncd.conf, in which the following 
is present;

motd file          = /etc/motd
max connections    = 2
syslog facility    = local3

[ftp]
      comment      = ftp area
      path         = /u/peg
      read only    = no
      list         = yes
      uid          = nobody
      gid          = nobody
[tmp]
      hosts allow  = 10.0.0.10 10.0.0.3 Unix486.AWDOM DemoUnix.AWDOM
      auth users   = root
      secrets file = /etc/rsyncd.secrets

4.  i added a new file /etc/rsyncd.secrets which contains the user name 
and password.

Now, when i type the command on the Unix box 2;

root> rsync Unix486.AWDOM::/u/peg /u/bak

NOTE: It is to be noted that /u/peg contains all data files ( directories 
and sub directories ) which i want to copy to the second Unix box ( 
Machine 2 ) in folder /u/bak

I get the motd content of Machine 1, and the root prompt appears.  When i 
check at the /u/bak folder, no files has been copied there.  When i check 
at the syslog, i notice the error message " DemoUnix rsyncd[2347]: bind 
failed on port 873".

What could be missing in above ? No files are being copied ?

Thanks for your feedback,
Regards.
Salim

PS: Unix Machine 2 has been setup as redundant system only, the reason why 
i want to copy data files overthere as precautions. { sometimes tapes are 
not reliable }