From owner-freebsd-net@freebsd.org  Sun Apr 29 19:23:02 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6DBBFB5E84
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sun, 29 Apr 2018 19:23:02 +0000 (UTC)
 (envelope-from list+org.freebsd.net@io7m.com)
Received: from mail.io7m.com (mail.io7m.com [45.77.76.92])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.io7m.com", Issuer "arc7 CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 53C497BE08;
 Sun, 29 Apr 2018 19:23:02 +0000 (UTC)
 (envelope-from list+org.freebsd.net@io7m.com)
Received: from almond.int.arc7.info (unknown [IPv6:2a02:390:7502:2:0:2:4:0])
 by mail.io7m.com (Postfix) with ESMTPSA id C235237D0;
 Sun, 29 Apr 2018 19:23:00 +0000 (UTC)
Date: Sun, 29 Apr 2018 20:22:49 +0100
From: Mark Raynsford <list+org.freebsd.net@io7m.com>
To: Alan Somers <asomers@freebsd.org>
Cc: FreeBSD Net <freebsd-net@freebsd.org>
Subject: Re: Starting and stopping nfsd apparently results in permanently
 disabling it
Message-ID: <20180429202249.2f4460ec@almond.int.arc7.info>
In-Reply-To: <CAOtMX2hi9y-HdQz1vDCTOSDjKT5hannHF_K64jJACjjC8T-avw@mail.gmail.com>
References: <20180429194958.53c7aa7d@almond.int.arc7.info>
 <CAOtMX2hi9y-HdQz1vDCTOSDjKT5hannHF_K64jJACjjC8T-avw@mail.gmail.com>
Organization: io7m.com
OpenPGP: id=B84E17747616C6174C68D5E55C1A7B712812CC05;
 url=http://io7m.com/pgp/B84E_1774_7616_C617_4C68_D5E5_5C1A_7B71_2812_CC05.key
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 boundary="Sig_/kQSO/yomtYrxm0yllVeh0Cz"; protocol="application/pgp-signature"
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Apr 2018 19:23:02 -0000

--Sig_/kQSO/yomtYrxm0yllVeh0Cz
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On 2018-04-29T13:16:48 -0600
Alan Somers <asomers@freebsd.org> wrote:

> First, you're starting stuff in the wrong order.  /etc/rc.d/nfsd depends =
on
> /etc/rc.d/mountd.  It sounds like you're bypassing rc, but you still need
> to start the daemons in the same order as rc does.  Secondly, how did you
> kill them?  /etc/rc.d/nfsd uses SIGUSR1 to kill nfsd.  That probably
> triggers some special cleanup that didn't happen when you killed nfsd.
>=20

Firstly: Got it. I'll be sure to start them in the correct order.
Unfortunately, doing this now doesn't fix the problem.

Secondly: I definitely killed nfsd with SIGUSR1. It explicitly ignores
SIGINT, SIGHUP, and SIGTERM.

--=20
Mark Raynsford | http://www.io7m.com


--Sig_/kQSO/yomtYrxm0yllVeh0Cz
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQS4Thd0dhbGF0xo1eVcGntxKBLMBQUCWuYbiQAKCRBcGntxKBLM
BfNpAQDu4QqKRFfxMAe0QKPabeSNM8iwrh9cEnpjQyJTD3syywD/Wv63n0ReW1fJ
Jb1C8h1SG9NpdYcFkSm+1qNCrvvTdQg=
=ay5T
-----END PGP SIGNATURE-----

--Sig_/kQSO/yomtYrxm0yllVeh0Cz--