From owner-freebsd-net@freebsd.org  Tue Jun 13 08:25:12 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 392DBB95A6F
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Tue, 13 Jun 2017 08:25:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 26AB072AC8
 for <freebsd-net@FreeBSD.org>; Tue, 13 Jun 2017 08:25:12 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5D8P84n008715
 for <freebsd-net@FreeBSD.org>; Tue, 13 Jun 2017 08:25:12 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect
Date: Tue, 13 Jun 2017 08:25:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: crash, needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: eugen@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: eri@freebsd.org
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-186114-2472-wheIlRMttt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-186114-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-186114-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
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: Tue, 13 Jun 2017 08:25:12 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114

--- Comment #33 from Eugene Grosbein <eugen@freebsd.org> ---
(In reply to Cassiano Peixoto from comment #32)

I'd better say "corefile" instead of "crashdump" as crashdump is generated =
for
kernel panic and core file for userland process crashed or killed with a
signal.

Use something like sysctl kern.corefile=3D'/var/tmp/%N.core' to specify loc=
ation
for corefiles. By default, its' written to process current directory. Take a
look at /usr/local/etc/mpd5/ for mpd.core

--=20
You are receiving this mail because:
You are on the CC list for the bug.=