From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: RE: [oe] [meta-oe][PATCH] syslog-ng: adjust control socket location
Date: Fri, 18 Feb 2022 16:32:00 +0000 [thread overview]
Message-ID: <f9f5fd2b7e46412381fe3d40a383c78f@axis.com> (raw)
In-Reply-To: <CAMKF1srXFHYf1bxDG5Cm74CU55bVgzcg3n690nJyqPWuavN6aQ@mail.gmail.com>
> -----Original Message-----
> From: openembedded-devel@lists.openembedded.org <openembedded-
> devel@lists.openembedded.org> On Behalf Of Khem Raj
> Sent: den 18 februari 2022 03:19
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
> Subject: Re: [oe] [meta-oe][PATCH] syslog-ng: adjust control socket
> location
>
> this is already applied in master via
> b57d824fdf822a4c3fdb153b92063f88705e3a6b
Duh. I apparently forgot the "[honister]" tag in the subject (see my
original comment below).
> On Thu, Feb 17, 2022 at 5:12 PM Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> >
> > From: Ovidiu Panait <ovidiu.panait@windriver.com>
> >
> > Commit [1] changed the pidfile dir to /var/run/syslog-ng. This also
> changed
> > the location where the control socket is searched for, causing the
> following
> > error with systemd:
> >
> > root@qemux86-64:~# syslog-ng-ctl config
> > Error connecting control socket, socket='/var/run/syslog-ng/syslog-
> ng.ctl',
> > error='No such file or directory'
> >
> > Update the systemd service file to point to the new location.
> >
> > [1] 00d1d63e4f7f ("syslog-ng: provide correct PID directory location to
> > restart/stop syslog-ng daemon")
> >
> > Signed-off-by: lmorales <luisalejandro.moralespena@windriver.com>
> > Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > ---
> >
> > This has already been backported to the hardknott branch, but is missing
> > in honister...
> >
> > .../files/syslog-ng.service-the-syslog-ng-service.patch | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta-oe/recipes-support/syslog-ng/files/syslog-ng.service-
> the-syslog-ng-service.patch b/meta-oe/recipes-support/syslog-
> ng/files/syslog-ng.service-the-syslog-ng-service.patch
> > index 0e1d09492..733480030 100644
> > --- a/meta-oe/recipes-support/syslog-ng/files/syslog-ng.service-the-
> syslog-ng-service.patch
> > +++ b/meta-oe/recipes-support/syslog-ng/files/syslog-ng.service-the-
> syslog-ng-service.patch
> > @@ -38,7 +38,7 @@ index 0ccc2b9..7f08c0e 100644
> > -CONTROL_FILE=/var/run/syslog-ng.ctl
> > -PID_FILE=/var/run/syslog-ng.pid
> > +PERSIST_FILE=@LOCALSTATEDIR@/lib/syslog-ng/syslog-ng.persist
> > -+CONTROL_FILE=@LOCALSTATEDIR@/lib/syslog-ng/syslog-ng.ctl
> > ++CONTROL_FILE=@LOCALSTATEDIR@/run/syslog-ng/syslog-ng.ctl
> > +PID_FILE=@LOCALSTATEDIR@/run/syslog-ng.pid
> > OTHER_OPTIONS="--enable-core"
> > --
//Peter
next prev parent reply other threads:[~2022-02-18 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 1:12 [meta-oe][PATCH] syslog-ng: adjust control socket location Peter Kjellerstedt
2022-02-18 2:18 ` [oe] " Khem Raj
2022-02-18 16:32 ` Peter Kjellerstedt [this message]
2022-02-18 17:02 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9f5fd2b7e46412381fe3d40a383c78f@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox