1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: Configuration of files on Debian GNU/Linux

    From Greg Wooledge@21:1/5 to William Torrez Corea on Sun Oct 13 03:00:01 2024
    On Sat, Oct 12, 2024 at 18:36:34 -0600, William Torrez Corea wrote:
    I configure a file for example /etc/network/interfaces.d

    That's a directory, not a file.

    Configure the file, save and exit but the changes are not made. I need to make a second configuration.

    For me it is a waste of time.

    What happened?

    We don't know what happened. Why don't you show us?

    Which file did you edit? What did you change?

    What was the ACTUAL result of your change?
    What was your EXPECTED result?

    What did you change the second time?

    What was the ACTUAL result of your change?
    What was your EXPECTED result?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Ritter@21:1/5 to William Torrez Corea on Sun Oct 13 03:10:02 2024
    William Torrez Corea wrote:
    I configure a file for example /etc/network/interfaces.d

    Configure the file, save and exit but the changes are not made. I need to make a second configuration.

    Do you mean that the file was not saved to disk, or were you
    expecting something else to happen?

    Most Linux systems do not monitor their config files for changes
    and then adopt them automatically. (There are a few programs
    that do, but they are exceptions.)

    For interfaces.d, I would expect a change after an ifup/ifdown
    command.

    If the file is not saved to disk, there are bigger problems.

    -dsr-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charles Curley@21:1/5 to William Torrez Corea on Sun Oct 13 03:20:01 2024
    On Sat, 12 Oct 2024 18:36:34 -0600
    William Torrez Corea <[email protected]> wrote:

    I configure a file for example /etc/network/interfaces.d

    /etc/network/interfaces.d is a directory; I suspect you mean you write
    a configuration file in /etc/network/interfaces.d.


    Configure the file, save and exit but the changes are not made.

    The first time you write a configuration file, say for a new interface,
    you then must call "ifup <if>" where <if> is the name of the device.

    If you have an existing device, you should run "ifdown <if>" before you
    modify the configuration file.

    I need to make a second configuration.

    I'm not sure what you mean here. You should only have one configuration
    file in /etc/network/interfaces.d per interface, OR one stanza in /etc/network/interfaces. The former is preferred these days.

    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)