From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>, David GOUARIN <dgouarin@gmail.com>,
Kalpesh Panchal <kalpesh.panchal2@collins.com>,
Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 1/1] freeradius-server: enable default modules mschap and realm
Date: Sat, 4 Nov 2023 19:24:27 +0100 [thread overview]
Message-ID: <20231104192427.7ef3b9b3@windsurf> (raw)
In-Reply-To: <20231031225751.35130-1-brandon.maier@collins.com>
On Tue, 31 Oct 2023 22:57:51 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> From: Kalpesh Panchal <kalpesh.panchal2@collins.com>
>
> "mschap" and "realm" are already part of default required
> raddb modules(DEFAULT_MODULES in raddb/all.mk).
>
> so removed them from disabled module list so that
> radiusd.service can start without following errors:
>
> - /etc/raddb/mods-enabled/mschap[11]: Failed to link to module 'rlm_mschap': /usr/lib/rlm_mschap.so
> - /etc/raddb/mods-enabled/realm[21]: Failed to link to module 'rlm_realm': /usr/lib/rlm_realm.so
>
> Signed-off-by: Kalpesh Panchal <kalpesh.panchal2@collins.com>
> Signed-off-by: Brandon Maier <brandon.maier@collins.com>
> ---
> package/freeradius-server/freeradius-server.mk | 2 --
> 1 file changed, 2 deletions(-)
Applied to master, thanks. It would be good to have a test case in
support/testing/ for freeradius, to make sure it starts up correctly at
boot.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-04 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 22:57 [Buildroot] [PATCH 1/1] freeradius-server: enable default modules mschap and realm Brandon Maier via buildroot
2023-11-04 18:24 ` Thomas Petazzoni via buildroot [this message]
2023-11-09 11:12 ` Peter Korsgaard
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=20231104192427.7ef3b9b3@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=dgouarin@gmail.com \
--cc=ju.o@free.fr \
--cc=kalpesh.panchal2@collins.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.