Date: Thu, 12 Jul 2018 14:14:09 +0200 From: Alexander Leidinger <Alexander@leidinger.net> To: hackers@freebsd.org Subject: crashinfo doesn't support compressed crashdumps - which way forward? Message-ID: <20180712141409.Horde.NVSzLsvqE-2PCSDqhhfb0Xd@webmail.leidinger.net>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Hi, the crashinfo script doesn't know how to handle compressed coredumps. What would be acceptable behavior (ordered by my preferrence)? 1) decompress in /var/crash and then proceed normally (already implemented locally) 2) decompress to CRASHTMPDIR:/var/tmp/xxx and delete when finished 3) keep it like it is 4) teach tools to understand compressed dumps (gzip / zstd) Implicitly there is the question what what is the purpose of compressing crashdumps, to have more RAM than space in dumpdev (which is valid in my case), or to save space in /var/crash (which I don't care much about). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbR0YRAAoJEKrxQhqFIICEWN4P/0pZOQielSic+c/gWrAI+Sqi CmviJwHhUxTxehnNv4cO+9dr4VirOJKgTEfaDg/OcGHPv33/xrtsr5lyKfz6XDr6 oqxf8F2q4rlM5QGRrpG+7ePhbO4YaoYmt9lJGHI6a1zM1VXZSYlw2mmaYP4ZsqqU LsJRgvxzAUKkd6KBK+Nppuu2v3PoK4N5UBBaMAQlxT+3drdYVTxtSNBXQh+owCI4 0CHe9ZgLW9FAtGwr3w/dNyPmKnCCOIo7Eu2fJDGNHUtEXkRVNplFuxzqN9uRY8GL aoFHTTaQX6T+2naX2/Me63CQWSIACIpnYf37ORl3RcpJ85PwpJh5cm6fne9RCSKy pQLgaTpZb+V3rM+12c3qQKMogmkpkSBm9ZxnHFKXbaUKvOyHy2HN9YQ6EtCx/M5b 7YWSHJfMzryYmGbk3ofKM4GBRtHAb5HXDVenEEAFHiIrBGl2vRypHK5l5Oknk4Xi O222031B5VDXM2FA3ZtqbFGuErJTXL4KspIGGQjXgAPUUbVu/8FXrBtWvEVEJzaI tT0WVdhkXbVk1axPJxuE9V/7j+pDJLkTOSsd1Eyp8BDsoiMWezvYN+gezyh2vFXM 7geiQB07M+pnOk525LnL4sH4SvFExR0UU7ccYakvtkQa6PbHbWxF473RPve3h7xL ms6ho25aBFFOdb+Qj9h9 =34Wm -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180712141409.Horde.NVSzLsvqE-2PCSDqhhfb0Xd>