[Bug 1235169] Re: Fails to read files in /etc/network/interfaces.d/
Ubuntu Foundations Team Bug Bot
1235169 at bugs.launchpad.net
Fri Oct 4 12:18:02 UTC 2013
The attachment "Debugging patch for config.c" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1235169
Title:
Fails to read files in /etc/network/interfaces.d/
Status in “ifupdown” package in Ubuntu:
New
Bug description:
0.7.44ubuntu3 on Saucy 13.10 amd64.
On a multi-homed server with five ethernet interfaces we have 6
'interfaces' files in '/etc/network/interfaces.d/' for 'lo' and 'eth0'
through 'eth4'.
ifup -a fails to include the contents of these files and consequently
the interfaces are ignored.
"strace" reveals that when scanning the 'interfaces.d' directory ifupdown is using the "openat()" function which does an integral change-directory. It gets the list of files correctly and "closes()" the directory. It then does "open()" on each validly named file but gets -ENOENT result because it forgets to prefix the file-name with the 'interfaces.d/' directory - so it is looking in '/etc/network/' rather than '/etc/network/interfaces.d/'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1235169/+subscriptions
More information about the foundations-bugs
mailing list