All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: 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: Thu, 09 Nov 2023 12:12:49 +0100	[thread overview]
Message-ID: <878r77p4cu.fsf@48ers.dk> (raw)
In-Reply-To: <20231031225751.35130-1-brandon.maier@collins.com> (Brandon Maier via buildroot's message of "Tue, 31 Oct 2023 22:57:51 +0000")

>>>>> "Brandon" == Brandon Maier via buildroot <buildroot@buildroot.org> writes:

 > 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>

Committed to 2023.02.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-11-09 11:12 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
2023-11-09 11:12 ` Peter Korsgaard [this message]

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=878r77p4cu.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=dgouarin@gmail.com \
    --cc=kalpesh.panchal2@collins.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.