El 26/01/23 a las 19:29, Cyril Brulebois escribió:
> Hi Oleg,
>
> Oleg A. Arkhangelsky (2023-01-26):
> > After some digging I think that there is more elegant way to stop
> > ifup@*.service when stopping (or restarting) networking.serivce, we just
> > need to add PartOf to
Hi Oleg,
Oleg A. Arkhangelsky (2023-01-26):
> After some digging I think that there is more elegant way to stop
> ifup@*.service when stopping (or restarting) networking.serivce, we just
> need to add PartOf to /lib/systemd/system/ifup@.service:
>
> [Unit]
> ...
>
On Wed Jan 25, 2023 at 11:31 PM UTC, Pascal Hambourg wrote:
> Maybe there is a more elegant way to stop ifup@*.service, e.g. using
> systemd unit dependencies but I am not familiar enough with this topic.
>
> This setup causes no delay when (re)starting networking.service by hand
> at boot time
Sorry for the late (and long) answer...
On 23/01/2023 à 19:36, Oleg A. Arkhangelsky wrote:
I tried this *.deb (Pascal approach). It doesn't change behaviour
introduced after this patch [1]. Yes, restart for "allow-hotplug"
interfaces work but I got the same system boot lag in Jeff
On Tue, Jan 24, 2023 at 02:32:07PM +0100, Santiago Ruano Rincón wrote:
> > Tests yesterday seem to indicate successful results, but again I've only
> > tested a few combinations in a VM (to keep the feedback loop short).
> >
> > From the installer team point of view, I'd welcome a swift upload
Hi!
El 23/01/23 a las 16:19, Cyril Brulebois escribió:
> Hi Santiago,
>
> Santiago Ruano Rincón (2023-01-23):
> > Thanks everybody for the inputs. I've applied Paul's solution, and the
> > generated .deb can be downloaded from here:
> >
> >
Hi,
boot online:
No delay.
boot offline:
60 seconds boot delay (dhcp tiemout) per defined interface.
Please abort or do the timeout in background like ifupdown 0.8.39 used
to,
instead of delaying boot.
Didn't expect this bug to be reopened, opened another one yesterday.
Please feel free
Hi Oleg,
Oleg A. Arkhangelsky (2023-01-23):
> I tried this *.deb (Pascal approach). It doesn't change behaviour
> introduced after this patch [1]. Yes, restart for "allow-hotplug"
> interfaces work but I got the same system boot lag in Jeff configuration.
Right, I mostly tested that an
On Mon, Jan 23, 2023 at 03:55:50PM +0100, Santiago Ruano Rincón wrote:
> > That seems needlessly convoluted. What about this:
> >
> > [Service]
> > Type=oneshot
> > EnvironmentFile=-/etc/default/networking
> > ExecStart=/sbin/ifup -a --read-environment
> >
On Mon Jan 23, 2023 at 2:55 PM UTC, Santiago Ruano Rincón wrote:
> Thanks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
>
>
Hi Santiago,
Santiago Ruano Rincón (2023-01-23):
> Thanks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
>
>
El 23/01/23 a las 00:24, Pascal Hambourg escribió:
> Oleg A. Arkhangelsky wrote:
> > Note that we have to use '--ignore-errors'. Otherwise if we have real
> > hotplug interface that is not present at the moment of restart, `ifup`
> > returns non-zero and systemd unit fail.
>
> "--ignore-errors"
Oleg A. Arkhangelsky wrote:
Note that we have to use '--ignore-errors'. Otherwise if we have real
hotplug interface that is not present at the moment of restart, `ifup`
returns non-zero and systemd unit fail.
"--ignore-errors" marks missing interfaces as configured, so ifup will
not configure
Cyril Brulebois (2023-01-22):
> The configuration found below manages to:
> - let my allow-hotplug slow-to-appear wireless interface come up at
>boot-up, via the udev integration;
> - allow me to stop and start networking, losing then regaining all
>relevant configs (main connection is
Control: reopen 1022843
Control: found 1022843 0.8.40
Control: severity 1022843 serious
Hi,
Cyril Brulebois (2023-01-22):
> d-i believes that everything should be allow-hotplug, and we end up
> using that everywhere. I'm wondering whether to just use auto everywhere
> instead, since the hotplug
Hi Oleg,
Greetings with my Debian Installer hat on.
Oleg A. Arkhangelsky (2023-01-21):
> P.S.: Yes, probably Debian installer should add PCI NICs as auto, not
> as allow-hotplug, but in this case after fresh installing Debian and
> just adding your wlan0 configuration (not changing eth0 which
On Fri Jan 20, 2023 at 5:26 PM UTC, Jeff King wrote:
> This has the minor downside that on system startup, we'll spend time
> trying to bring up allow-hotplug interfaces, even if they're not
> available. So on my system, for example, with:
>
> allow-hotplug eth0
> iface eth0 inet dhcp
>
>
On Sat, Oct 29, 2022 at 10:33:26AM +, Oleg A. Arkhangelsky wrote:
> Since the unit type is oneshot, we can have multiple ExecStart statements.
>
> Note that we have to use '--ignore-errors'. Otherwise if we have real
> hotplug interface that is not present at the moment of restart, `ifup`
>
Control: tags -1 + pending
Hi!
El 29/10/22 a las 10:33, Oleg A. Arkhangelsky escribió:
> Package: ifupdown
> Tags: patch
>
> Here is proposed patch.
>
> Since the unit type is oneshot, we can have multiple ExecStart statements.
>
> Note that we have to use '--ignore-errors'. Otherwise if we
Package: ifupdown
Tags: patch
Here is proposed patch.
Since the unit type is oneshot, we can have multiple ExecStart statements.
Note that we have to use '--ignore-errors'. Otherwise if we have real
hotplug interface that is not present at the moment of restart, `ifup`
returns non-zero and
Package: ifupdown
Version: 0.8.36
Severity: important
X-Debbugs-Cc: syso...@yandex.ru
Hello!
(Not sure why such rather important issue is not filled yet, but anyway. Sorry
if I'm creating duplicate.)
My network is down after running `systemctl restart networking` on fresh
installed Debian
21 matches
Mail list logo
