From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 6 23:43:18 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ABA7A492; Wed, 6 Nov 2013 23:43:18 +0000 (UTC) (envelope-from cjpugmed@gmail.com) Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57C3028B0; Wed, 6 Nov 2013 23:43:18 +0000 (UTC) Received: by mail-ve0-f172.google.com with SMTP id cz12so165903veb.17 for ; Wed, 06 Nov 2013 15:43:17 -0800 (PST) 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=xuCAbi8lwgoUly9V4BWy5GytjK/5b88UeW5CZcxnrcM=; b=sep5rLFkV8TerpDFA3jQXOY1qJaGh5cunEU9p04rYqsJtdFLipfwlnFgwIROEz5Yyn BVjhMEzgpjDOATcxCYl1eZr04SYdbQOkQTC5XZx0UjmwUuqmtyBp43GYUWTsZpoteUbx /KxrSz3qtYo1L7iyWy0QBaJ3EfJwuLP8Xc3CpDmUe5xJlXj/r/N++1s+Juta0KofCU7I 583j0IdtsRwePhT9qRashR2m6v+j3wz9zUs0ShcwdmFVzhYihltJSKwF78YKs5jLf5Tp 5+TxeW/B9glEsUQyusC+NpB0FqpsUvl7G7TBuUZp8oTlR/shWZmzqfGlw7Two0Ft+7sL W+CQ== MIME-Version: 1.0 X-Received: by 10.58.178.239 with SMTP id db15mr4434021vec.9.1383781397379; Wed, 06 Nov 2013 15:43:17 -0800 (PST) Received: by 10.220.1.17 with HTTP; Wed, 6 Nov 2013 15:43:17 -0800 (PST) In-Reply-To: References: Date: Thu, 7 Nov 2013 00:43:17 +0100 Message-ID: Subject: Re: Automated submission of kernel panic reports: sysutils/panicmail From: Carlos Jacobo Puga Medina To: freebsd-hackers@freebsd.org, cperciva@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 23:43:18 -0000 At last, I realized how to solved this inconvenient. Digging a bit I found what I needed. All is summarized in the pr124747 which describes perfectly this problem and attached a patch to fix it. I add the modified patch according to current rc.d scripts included. diff -ur encswap.orig encswap --- encswap.orig 2013-11-06 23:31:43.000000000 +0100 +++ encswap 2013-11-07 00:14:03.000000000 +0100 @@ -3,8 +3,8 @@ # $FreeBSD: release/9.2.0/etc/rc.d/encswap 180563 2008-07-16 19:22:48Z dougb $ # -# PROVIDE: disks -# REQUIRE: initrandom +# PROVIDE: encswap +# REQUIRE: initrandom disks # KEYWORD: nojail . /etc/rc.subr diff -ur savecore.orig savecore --- savecore.orig 2013-11-06 23:32:21.000000000 +0100 +++ savecore 2013-11-07 00:14:18.000000000 +0100 @@ -4,7 +4,7 @@ # # PROVIDE: savecore -# REQUIRE: dumpon ddb syslogd +# BEFORE: encswap # KEYWORD: nojail . /etc/rc.subr diff -ur swap1.orig swap1 --- swap1.orig 2013-11-06 23:32:28.000000000 +0100 +++ swap1 2013-11-07 00:14:29.000000000 +0100 @@ -4,7 +4,7 @@ # # PROVIDE: localswap -# REQUIRE: disks +# REQUIRE: encswap disks # KEYWORD: nojail shutdown . /etc/rc.subr I tested it and now it works like a charm. 2013/11/5 Carlos Jacobo Puga Medina > Add missing thread related to Pawel's proposal [1] > > [1] > http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009256.html > > > 2013/11/5 Carlos Jacobo Puga Medina > >> Seems that rc.d scripts order doesn't allow geli-encrypted swap and >> dumpdev to cooperate together. For this reason, I wonder what happens in >> such cases, is not possible to use panicmail unless Pawel's proposal [1] >> which argued to obtain and save crash info in memory somewhere before we >> configure swap and copy it to /var/crash/ once we mount it. >> >> Is sustainable this proposal or is there yet another alternative to >> consider for those who use an encrypted GELI swap? >> >> --CJPM >> > >