Date: Tue, 5 Nov 2013 22:55:31 +0100 From: Carlos Jacobo Puga Medina <cjpugmed@gmail.com> To: freebsd-hackers@freebsd.org, cperciva@freebsd.org Subject: Re: Automated submission of kernel panic reports: sysutils/panicmail Message-ID: <CAHHLbRNGwP56Qq_FLZGvN7hORJtE1SUVAZKpJty_cN4%2B7mEEUA@mail.gmail.com> In-Reply-To: <CAHHLbRNv2T2-arUXn7WDFHDOAOTQvVqe0nniOr5sVPcgob4QJQ@mail.gmail.com> References: <CAHHLbRNv2T2-arUXn7WDFHDOAOTQvVqe0nniOr5sVPcgob4QJQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <cjpugmed@gmail.com> > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHLbRNGwP56Qq_FLZGvN7hORJtE1SUVAZKpJty_cN4%2B7mEEUA>