Bug#766943: systemd: server no longer gets networking after switching to systemd
On Wed, Nov 12, 2014 at 3:35 PM, Michael Biebl wrote: > Am 12.11.2014 um 23:59 schrieb Cameron Norman: >> But will services depending on network.target be started then? Or will >> they be prevented from starting in the case of an auto interface not >> being configured? > > How is that relevant for this patch? For some reason I thought that that particular behavior was changing. Upon re-reading, it is not. Sorry for the bother. Thank you, -- Cameron Norman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766943: systemd: server no longer gets networking after switching to systemd
Am 12.11.2014 um 23:59 schrieb Cameron Norman: > But will services depending on network.target be started then? Or will > they be prevented from starting in the case of an auto interface not > being configured? How is that relevant for this patch? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#766943: systemd: server no longer gets networking after switching to systemd
El mié, 12 de nov 2014 a las 6:30 , Michael Biebl escribió: Am 12.11.2014 um 05:04 schrieb Cameron Norman: On Tue, 11 Nov 2014 20:05:53 +0100 Michael Biebl wrote: Am 11.11.2014 um 20:01 schrieb Michael Biebl: > Attached is a patch against /etc/init.d/networking. > While we discussed yesterday, to only run "udevadm settle" if there are > any auto interfaces, I changed it, to also cover allow-hotplug. > I also changed the init script to handle allow-hotplug interfaces. [..] > Please test and report back. Grr, the attached patch had a typo, please try this v2. So with this change, $network and network.target mean that all interfaces marked auto or allow-hotplug have been configured, or hotplug events have been settled and as many interfaces as could be brought up have been, correct? And if an "auto" interface is never brought up, that is ignored after udev settles? Are you sure that is desired behavior, seeing as allow-hotplug is the only configuration that explicitly references hotplug devices/events? I'm not quite sure what problem you're referring too, please elaborate. If you are using "auto" for an interface which is plugged in after "/etc/init.d/networking start" has been run, then yeah, it won't be configured. But the patch doesn't change that. But will services depending on network.target be started then? Or will they be prevented from starting in the case of an auto interface not being configured? Thank you, -- Cameron Norman
Bug#766943: systemd: server no longer gets networking after switching to systemd
Am 12.11.2014 um 05:04 schrieb Cameron Norman: > On Tue, 11 Nov 2014 20:05:53 +0100 Michael Biebl wrote: >> Am 11.11.2014 um 20:01 schrieb Michael Biebl: >> > Attached is a patch against /etc/init.d/networking. >> > While we discussed yesterday, to only run "udevadm settle" if there are >> > any auto interfaces, I changed it, to also cover allow-hotplug. >> > I also changed the init script to handle allow-hotplug interfaces. >> >> [..] >> >> > Please test and report back. >> >> Grr, the attached patch had a typo, please try this v2. > > So with this change, $network and network.target mean that all > interfaces marked auto or allow-hotplug have been configured, or hotplug > events have been settled and as many interfaces as could be brought up > have been, correct? > > And if an "auto" interface is never brought up, that is ignored after > udev settles? Are you sure that is desired behavior, seeing as > allow-hotplug is the only configuration that explicitly references > hotplug devices/events? I'm not quite sure what problem you're referring too, please elaborate. If you are using "auto" for an interface which is plugged in after "/etc/init.d/networking start" has been run, then yeah, it won't be configured. But the patch doesn't change that. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#766943: systemd: server no longer gets networking after switching to systemd
On Tue, 11 Nov 2014 20:05:53 +0100 Michael Biebl wrote: > Am 11.11.2014 um 20:01 schrieb Michael Biebl: > > Attached is a patch against /etc/init.d/networking. > > While we discussed yesterday, to only run "udevadm settle" if there are > > any auto interfaces, I changed it, to also cover allow-hotplug. > > I also changed the init script to handle allow-hotplug interfaces. > > [..] > > > Please test and report back. > > Grr, the attached patch had a typo, please try this v2. So with this change, $network and network.target mean that all interfaces marked auto or allow-hotplug have been configured, or hotplug events have been settled and as many interfaces as could be brought up have been, correct? And if an "auto" interface is never brought up, that is ignored after udev settles? Are you sure that is desired behavior, seeing as allow-hotplug is the only configuration that explicitly references hotplug devices/events? Thanks, -- Cameron Norman
Processed: Re: Bug#766943: systemd: server no longer gets networking after switching to systemd
Processing commands for cont...@bugs.debian.org: > severity 766943 critical Bug #766943 [ifupdown] systemd: server no longer gets networking after switching to systemd Severity set to 'critical' from 'important' > tags 766943 + jessie sid Bug #766943 [ifupdown] systemd: server no longer gets networking after switching to systemd Added tag(s) sid and jessie. > stop Stopping processing here. Please contact me if you need assistance. -- 766943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
