<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<style type="text/css">.mceResizeHandle {position: absolute;border: 1px solid black;background: #FFF;width: 5px;height: 5px;z-index: 10000}.mceResizeHandle:hover {background: #000}img[data-mce-selected] {outline: 1px solid black}img.mceClonedResizable, table.mceClonedResizable {position: absolute;outline: 1px dashed black;opacity: .5;z-index: 10000}
</style></head><body style=""><div>Thanks for your quick response.</div>
<div>If csync2 just dies, what happens with the file I was syncing on my target system?<br>Do I have an incomplete file inside my filesystem or does it sync the content to a tempfile at first, like rsync?</div>
<div>If it works like rsync, will the tempfile be removed on the target system or do i have a dead file?</div>
<div><br>> Lars Ellenberg <lars.ellenberg@linbit.com> hat am 7. August 2017 um 14:18 geschrieben:<br>> <br>> <br>> On Mon, Aug 07, 2017 at 01:06:49PM +0200, Jonathan Keuser wrote:<br>> > Hey everybody,<br>> > <br>> > just a question: How does a running csync2 replication react to a SIGTERM? For<br>> > me it's obscure and on the internet I could not find anything about it.<br>> <br>> It just dies.<br>> No further handling.<br>> <br>> Or are you talking about win32 cygwin cs2monitor?<br>> That will "killall" csync2 processes, and then "restart"<br>> (rather: recycle) itself.<br>> <br>> <br>> -- <br>> : Lars Ellenberg<br>> : LINBIT | Keeping the Digital World Running<br>> : DRBD -- Heartbeat -- Corosync -- Pacemaker<br>> : R&D, Integration, Ops, Consulting, Support<br>> <br>> DRBD® and LINBIT® are registered trademarks of LINBIT<br>> _______________________________________________<br>> Csync2 mailing list<br>> Csync2@lists.linbit.com<br>> http://lists.linbit.com/mailman/listinfo/csync2</div></body></html>