All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alisa Volk via buildroot <buildroot@buildroot.org>
Cc: Alisa Volk <aolvolk@salutedevices.com>, ovlevin@salutedevices.com
Subject: Re: [Buildroot] [PATCH] package/ifplugd: add option to override sysconfdir
Date: Mon, 5 Feb 2024 18:09:59 +0100	[thread overview]
Message-ID: <20240205180959.5c662ae1@windsurf> (raw)
In-Reply-To: <20240115142744.70711-1-aolvolk@salutedevices.com>

Hello Alisa,

On Mon, 15 Jan 2024 17:27:44 +0300
Alisa Volk via buildroot <buildroot@buildroot.org> wrote:

> Add BR2_PACKAGE_IFPLUGD_SYSCONFDIR option to pass custom --sysconfdir argument.
> 
> Ifplugd init script is auto-generated with sysconfdir="etc/" by default.
> As a result path to ifplugd configuration file is hardcoded
> to /etc/ifplugd/ifplugd.conf.

Thanks a lot for your patch! However, looking at it, the --sysconfdir
option has no impact on the path to the ifplugd.conf file. This file is
sourced by the init script before starting ifplugd, as explained in the
ifplugd man page:

FILES
       /etc/ifplugd/ifplugd.conf: this file is sourced by the init
       script /etc/init.d/ifplugd and contains the interface to be
       monitored and the options to be used.

Looking at the code, the only file affected by the --sysconfdir option
is ifplugd.action, and the path to this file can be overridden at
runtime using:

       -r | --run= EXEC
              Specify program to execute when link status changes
              (default: /etc/ifplugd/ifplugd.action)

So, in the end, it looks like your patch is not needed, as the location
of both ifplugd.conf and ifplugd.action is runtime configurable.

BTW, the ifplugd package does not have a Buildroot init script, it
would be nice to add one, if you have some time of course :-)

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-05 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 14:27 [Buildroot] [PATCH] package/ifplugd: add option to override sysconfdir Alisa Volk via buildroot
2024-02-05 17:09 ` Thomas Petazzoni via buildroot [this message]
     [not found]   ` <d63d6a13-770c-4a4c-bad3-c4d97a54d747@salutedevices.com>
2024-02-09 22:00     ` Thomas Petazzoni via buildroot

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=20240205180959.5c662ae1@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aolvolk@salutedevices.com \
    --cc=ovlevin@salutedevices.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.