on node halt, lsyncd will exit.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

rsync: failed to connect to 10.9.10.164: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.7]
Wed Jun  9 17:12:23 2010: Forked binary process returned non-zero return code: 
10

What version of the product are you using? On what operating system?
lsyncd : 1.33
sync   : 3.07
linux  : gentoo 2.6.26-gentoo-r3 64bit

Please provide any additional information below.

5 nodes sync with lsyncd. where on node down,rsyncd will reutrn 10,and lsyncd 
auto exit.

here's my configure file:

<lsyncd version="1">
<settings>
  <logfile filename="/var/log/lsyncd.log"/>
  <pidfile filename="/var/run/lsyncd.pid"/>
  <debug/>
  <stubborn/>
  <!--scarce/-->

  <!--exclude-from filename="/etc/lsyncd-exclude.conf"/-->

  <callopts>
    <option text="-ltp%r"/>
    <option text="--delete"/>
    <option text="--timeout=60"/>
    <source/>
    <destination/>
  </callopts>
</settings>

<directory>
<source path="/var/www/gfs"/>
   <target path="10.9.10.75::gfs"/>
   <target path="10.9.10.231::gfs"/>
   <target path="10.9.10.222::gfs"/>
   <target path="10.9.10.164::gfs"/>
</directory>
</lsyncd>

Original issue reported on code.google.com by Onio...@gmail.com on 9 Jun 2010 at 9:19

[GoogleCodeExporter]

When running normally lsyncd should ignore all rsync exit codes.

Lsyncd will fail during startup when it cannot rsync; there is the --stubborn 
flag which will change it to the behaviour you are exepecting.

Original comment by axk...@gmail.com on 11 Jul 2010 at 7:34

• Changed state: Done