Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 20 Sep 2002 17:48:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 20 Sep 2002 17:48:29 -0400 Received: from packet.digeo.com ([12.110.80.53]:27590 "EHLO packet.digeo.com") by vger.kernel.org with ESMTP id ; Fri, 20 Sep 2002 17:48:28 -0400 Message-ID: <3D8B98D4.67A76C1C@digeo.com> Date: Fri, 20 Sep 2002 14:53:24 -0700 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-pre4 i686) X-Accept-Language: en MIME-Version: 1.0 To: Michael Sinz CC: mks@sinz.org, marcelo@conectiva.com.br, Robert Love , Linux Kernel List , riel@conectiva.com.br, Alan Cox Subject: Re: [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl References: <3D8B87C7.7040106@wgate.com> <3D8B8CAB.103C6CB8@digeo.com> <3D8B934A.1060900@wgate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Sep 2002 21:53:28.0412 (UTC) FILETIME=[271859C0:01C260F0] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1679 Lines: 46 Michael Sinz wrote: > > ... > > Does it need to be this fancy? Why not just have: > > > > if (core_name_format is unset) > > use "core" > > else > > use core_name_format/nodename-uid-pid-comm.core > > > > which saves all that string format processing, while giving > > people everything they could want? > > Well, it depends on if you really need the complex form or not. > > There are some people who use a format of: > > %N.%P.core > > which places the core file in the current directory but adds in the > name of the program. (Something that is very nice when you have > a lot of programs that may core "together" when something bad happens) They could use echo . > /proc/sys/vm/core_path > The string processing is not that much work anyway (very small) > and, given the fact that I am about to write to disk a core dump, > it can not be a critical path/fast path issue either :-) True, but it's all more code and I don't believe that it adds much value. It means that people need to run off and find the documentation, then choose a format. Which will be different from other people's chosen formats. Which will make development and testing and installation of downstream scripts harder, etc. You can give people *all* the options at no cost, and without irritating them, and with less code. So why make it harder for everyone by adding this optionality? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/