<div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5"><br><br>
</div></div>And your csync2 version is?<br></blockquote><div><br></div>csync2 1.34<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
BTW, don't use any -v when running under inetd,<br>
it may even be the reason for the breakage.<br></blockquote><div><br></div><div>I'll remember this, but I only used the -v flag to reveal the error message about TCP_NODELAY. As of now there is nothing to break under inetd as it doesnt start due to this error.</div>
<div>It synced perfectly using -ii and -xv or -x from the shell.</div><div><br></div><div>Thank you</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
<br>
--<br>
: Lars Ellenberg<br>
: LINBIT | Your Way to High Availability<br>
: DRBD/HA support and consulting <a href="http://www.linbit.com" target="_blank">http://www.linbit.com</a><br>
_______________________________________________<br>
Csync2 mailing list<br>
<a href="mailto:Csync2@lists.linbit.com">Csync2@lists.linbit.com</a><br>
<a href="http://lists.linbit.com/mailman/listinfo/csync2" target="_blank">http://lists.linbit.com/mailman/listinfo/csync2</a><br>
</font></blockquote></div><br></div></div>