Date: Mon, 22 Jul 2019 20:30:58 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 231236] dns/ddclient: logging via syslog not possible Message-ID: <bug-231236-7788-a0qQ7GolBC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231236-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-231236-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231236 ncrogers@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ncrogers@gmail.com --- Comment #4 from ncrogers@gmail.com --- I ran into the same problem recently. I think this used to work, but the sy= slog output changed in 12.0 and ddclient uses the logger(1) CLI tool to log to syslog, which actually has nothing to do with perl. https://reviews.freebsd.org/D14926 https://forums.freebsd.org/threads/logger-output-changed-in-12-0.69460/ In ddclient code: sub logger { return pipecmd("logger -p$facility.$priority -t${program}\[$$\]", @= _); It manually includes the process PID in the tag, and I believe syslog output changed in 12.0 to include this automatically or something like that. In my case, I end up with what appears like two PIDs in /var/log/messages entries= for ddclient. One is for the actual daemon inserted by ddclient and the other is the process of logger(1). For example: Jul 22 12:59:46 testhost ddclient[21473][21481]: FAILED: updating ... In any case I believe this has something to do with the problem, as I am al= so unable to come up with a syslog.conf that successfully logs to another file= . I thought I would share this experience in case it helps anyone else. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231236-7788-a0qQ7GolBC>