On Wed, 11.02.15 21:00, Kai Krakow (hurikha...@gmail.com) wrote:
> Lennart Poettering schrieb:
>
> > On Wed, 11.02.15 16:08, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
> >
> >> 2015-02-11 14:42 GMT+03:00 Tom Gundersen :
> >> > systemd-networkd-wait-online gained two new features in git (onlin
Lennart Poettering schrieb:
> On Wed, 11.02.15 16:08, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
>
>> 2015-02-11 14:42 GMT+03:00 Tom Gundersen :
>> > systemd-networkd-wait-online gained two new features in git (online
>> > manpages are still lagging):
>> >
>> >--ignore=
>> >
On Wed, 11.02.15 16:08, Vasiliy Tolstov (v.tols...@selfip.ru) wrote:
> 2015-02-11 14:42 GMT+03:00 Tom Gundersen :
> > systemd-networkd-wait-online gained two new features in git (online
> > manpages are still lagging):
> >
> >--ignore=
> >Network interfaces to be ignored when d
2015-02-11 14:42 GMT+03:00 Tom Gundersen :
> systemd-networkd-wait-online gained two new features in git (online
> manpages are still lagging):
>
>--ignore=
>Network interfaces to be ignored when deciding if the
> system is online. By default only the loopback interface is ignor
On Wed, Feb 11, 2015 at 12:11 PM, Vasiliy Tolstov wrote:
> Nice, can you say how to reduce timeout manually to 30s? Where I need to
> change value?
systemd-networkd-wait-online gained two new features in git (online
manpages are still lagging):
--ignore=
Network interfaces to b
Unless I have overooked something, there seems to be no way to tell dhcp
client to fail and leave card unset after some timeout.
We had popwer interruption, which left dhcp server unconcious and after
rebooting my workstation I couldn't get it up, since it was waiting for
dhcp client to get it
Nice, can you say how to reduce timeout manually to 30s? Where I need to
change value?
11 февр. 2015 г. 13:54 пользователь "Tom Gundersen" написал:
> On Wed, Feb 11, 2015 at 11:49 AM, Branko wrote:
> > Unless I have overlooked something, there seems to be no way to tell dhcp
> > client to fail a
On Wed, Feb 11, 2015 at 11:49 AM, Branko wrote:
> Unless I have overlooked something, there seems to be no way to tell dhcp
> client to fail and leave card unset after some timeout.
>
> We had power interruption, which left dhcp server unconcious and after
> rebooting my workstation I couldn't get
Unless I have overlooked something, there seems to be no way to tell
dhcp client to fail and leave card unset after some timeout.
We had power interruption, which left dhcp server unconcious and after
rebooting my workstation I couldn't get it up, since it was waiting for
dhcp client to get it
