It appears that you actually may have had an address assigned, but then
had it removed ~30 seconds later when the interface was brought down by
wpa_supplicant.
Can you confirm the period of time that you checked and saw that you had no
address assigned?
Was it within the ~30 second window of tim
Correctly return exit status from the exited process.
>
> > This is also OpenBSD rev. 1.117, as pointed out by
> > Ryan Moeller .
>
> > Submitted by: Nash Kaminski
> > MFC after: 1 week
>
> > Modified
Correctly return exit status from the exited process.
>
> > This is also OpenBSD rev. 1.117, as pointed out by
> > Ryan Moeller .
>
> > Submitted by: Nash Kaminski
> > MFC after: 1 week
>
> > Modified
Hello,
I have been attempting to debug a peculiar issue with dhclient on a
vanilla FreeBSD 11.2 system where it appears that even if
dhclient-script returns nonzero when invoked in response to a protocol
timeout, dhclient continues as if the address was bound successfully,
as opposed to the protoc
I have recently enabled https support on my mirror, mirror.kaminski.io.
Please update mirrorlists accordingly.
Regards,
Nash Kaminski
Mirror is down due to a network issue. I expect to have it resolved by the end
of day Monday.
Nash Kaminski
On February 18, 2017 6:00:01 AM CST, arch-mirrors-requ...@archlinux.org wrote:
>Send arch-mirrors mailing list submissions to
> arch-mirrors@archlinux.org
>
>To
My mirror, mirror.kaminski.io, will be down for a few hours today due to
electrical work occurring in the space in which it is hosted.
Regards,
Nash Kaminski
--
Sent from my Android device with K-9 Mail.
gpu-manager is responsible for overwriting your X config file.
Commenting out the "start on" lines at the top of gpu-manager's upstart
script located at /etc/init/gpu-manager.conf will temporarily disable
gpu-manager and prevent xorg.conf from being changed.
--
You received this bug notification
gpu-manager is responsible for overwriting your X config file.
Commenting out the "start on" lines at the top of gpu-manager's upstart
script located at /etc/init/gpu-manager.conf will temporarily disable
gpu-manager and prevent xorg.conf from being changed.
--
You received this bug notification
gpu-manager is responsible for overwriting your X config file.
Commenting out the "start on" lines at the top of gpu-manager's upstart
script located at /etc/init/gpu-manager.conf will temporarily disable
gpu-manager and prevent xorg.conf from being changed.
--
You received this bug notification
10 matches
Mail list logo
