Also note that recently I released Lsyncd 2.0.6 (upstream) which
includes this fix along with a few others.
- Axel
On Mon, Mar 5, 2012 at 5:56 PM, Timo Juhani Lindfors
wrote:
> Hi Axel,
>
> if you send email to 659...@bugs.debian.org the email will only go the
> maintainer of the package. You ne
Hi Axel,
if you send email to 659...@bugs.debian.org the email will only go the
maintainer of the package. You need send email also to
659941-submit...@bugs.debian.org to make sure that I (the submitter) can
see your questions :-)
My logs have already rotated multiple times since Feb 15 :-(
I ap
Forget the last message, found it:
In lsyncd.c where it says:
-
// disconnects stdstreams
if (!freopen("/dev/null", "r", stdin) ||
!freopen("/dev/null", "r", stdout) ||
!freopen("/dev/null", "r", stderr)
) {
-
change that to
-
// disconnects stdstreams
In case of Lsyncd configured with a logfile Lsyncd will redirect
stderr to the logfile. But it will not do any redirect when no logfile
is specified.
However, in case of daemonize() it should have reopened its own stderr
to /dev/null and rsync should inherit that.
Does your syslog ever contain:
Thank you!!!
Finally, finally someone managed to figure out what mysterious error
13 from rsync means and why it does that. There have been several
reports on this, and I couldn't reproduce it, and even rsync mailling
list failed to explain me why rsync might to a 13 :-))
Going to make a fix righ
5 matches
Mail list logo
