Bug#618678: confirmed but with fixed with newer upstream releases.

2011-08-09 Thread Timo Juhani Lindfors
Hi Alex, Solution: For those who heavily use Lsyncd, I strongly suggest going and build a Lsyncd 2.0.x. It has been a complete rewrite that added I didn't get your email. You need to use 618678-submit...@bugs.debian.org to make sure the email goes to the submitter of the bug :-) Anyways, I

Bug#618678: confirmed but with fixed with newer upstream releases.

2011-03-22 Thread Axel Kittenberger
Yes, I could reproduce this with Lsyncd 1.34, and I can confirm the issue to be gone with 2.0.3. To quote the strace man page: On some platforms a process that has a system call trace applied to it with the -p option will receive a SIGSTOP. This signal may interrupt a system call