From owner-freebsd-current@freebsd.org  Sat Aug 29 12:00:49 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4914E9C4B29;
 Sat, 29 Aug 2015 12:00:49 +0000 (UTC)
 (envelope-from vidwer@gmail.com)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com
 [IPv6:2a00:1450:4010:c03::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 880FEB65;
 Sat, 29 Aug 2015 12:00:48 +0000 (UTC)
 (envelope-from vidwer@gmail.com)
Received: by labnh1 with SMTP id nh1so21766746lab.3;
 Sat, 29 Aug 2015 05:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=R7q0XPYCW0vO0ndWPk2BlOXwtALDtkX8DlRgRwaE138=;
 b=FECHhJk3dMm70STA18h8AUf+Krqy6nq8LseXGRWNn0DhJQuYYMocsVPARgkMlDLQwM
 U27lmbUZU3sqVIPEKZfnHH3fD4f9EP7nnHrYNn6L+/fgjOKDSRVFCh47lxWXugF4avZc
 KmyeKQRyIY8VpDEk/10YY8NJ0Qv6U2PyLjx+mDaRcz31mSJJTuTHu9zQ2Rbm3EKMv2GQ
 AE18+sRl9j5WFEIf4XwYmgRuVyf3D/43lhdZsqbye6htF9w59KfSvfRxBJTmFdXVJ17/
 JIa/uFAyurjB/sWN7A9EvsZ3XPgP1Picyf4VJ3mtZ1cZsMdnPVlnX91t2wZUIk3P3OzM
 6n4g==
MIME-Version: 1.0
X-Received: by 10.112.136.170 with SMTP id qb10mr7127844lbb.34.1440849646531; 
 Sat, 29 Aug 2015 05:00:46 -0700 (PDT)
Received: by 10.25.86.149 with HTTP; Sat, 29 Aug 2015 05:00:46 -0700 (PDT)
In-Reply-To: <20150829080202.GQ56997@FreeBSD.org>
References: <CAPp9OrkP8LWhDP6BnKPBeaiS5s7do=+FjVuoR8dQpMFda7-s0A@mail.gmail.com>
 <20150829080202.GQ56997@FreeBSD.org>
Date: Sat, 29 Aug 2015 14:00:46 +0200
Message-ID: <CAPp9Orn_i0r8TWCGba-9k_0=sMrZTnJvb9dh6KzLuuoQnmun3w@mail.gmail.com>
Subject: Re: r287197: wlan interfaces aren't brought up at boot or u
From: Idwer Vollering <vidwer@gmail.com>
To: freebsd-wireless@freebsd.org, freebsd-current@freebsd.org
X-Mailman-Approved-At: Sat, 29 Aug 2015 13:32:57 +0000
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Aug 2015 12:00:49 -0000

2015-08-29 10:02 GMT+02:00 Gleb Smirnoff <glebius@freebsd.org>:
> On Sat, Aug 29, 2015 at 01:19:40AM +0200, Idwer Vollering wrote:
> I> Manually running 'service netif restart' works around this.
> I>
> I> /etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
> I> -p and mergemaster -iF
> I>
> I> I can provide the, rather lengthy, output of 'sh -x /etc/rc.d/netif
> I> restart' when required.
> I>
> I> Note that I'm not subscribed to freebsd-current.
>
> Yes, please provide 'sh -x /etc/rc.d/netif restart'.

Attaching its output.

>
> And please also check the revisions of your files:
>
> # ident /etc/rc.d/netif /etc/network.subr

# ident /etc/rc.d/netif /etc/network.subr
/etc/rc.d/netif:
     $FreeBSD: head/etc/rc.d/netif 287197 2015-08-27 08:56:39Z glebius $
/etc/network.subr:
     $FreeBSD: head/etc/network.subr 287197 2015-08-27 08:56:39Z glebius $

>
> --
> Totus tuus, Glebius.