Lennart Poettering [2015-10-14 18:15 +0200]:
> My educated guess is that DEbian's ifupdown scripts are responsible for
> this... IIRC they install a unit file that is pulled in on hotplug,
> and might keep the device busy...
Yes, /lib/udev/net.agent. It calls ifup or ifdown if the interface is
On Wed, 23.09.15 22:17, James (jamesze...@gmail.com) wrote:
> Hello,
>
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name (eth0 -> wired) on one of my servers.
>
> Here's the output from the journal:
>
> ~# journalctl --no-pager | grep -i wired
On Thu, 01.10.15 15:09, James (jamesze...@gmail.com) wrote:
> Thanks Kay - that jives with what I was thinking, as well. Is there a
> good way to tell?
>
> I've used systemd-analyze critical-chain to see if there is something
> being kicked off by systemd before the network scripts can run, but
Hello, just following up to see if there were any ideas on what may be
causing this.
Any thoughts appreciated.
On Wed, Sep 23, 2015 at 10:17 PM, James wrote:
> Hello,
>
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name
Thanks Kay - that jives with what I was thinking, as well. Is there a
good way to tell?
I've used systemd-analyze critical-chain to see if there is something
being kicked off by systemd before the network scripts can run, but
alas it appears that none of the systemd units are the culprit here.
On Thu, Oct 1, 2015 at 7:21 PM, James wrote:
> Hello, just following up to see if there were any ideas on what may be
> causing this.
>
> Any thoughts appreciated.
>
> On Wed, Sep 23, 2015 at 10:17 PM, James wrote:
>> Hello,
>>
>> Hoping someone can