Messages in this thread | | | Date | Sun, 22 Sep 2002 16:59:12 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] kernel 2.4.19 & 2.5.38 - coredump sysctl |
| |
Bill Davidsen wrote: > > On Fri, 20 Sep 2002, Andrew Morton wrote: > > > That seems a reasonable thing to want to do. > > > > > ... > > > The following format options are available in that string: > > > > > > %P The Process ID (current->pid) > > > %U The UID of the process (current->uid) > > > %N The command name of the process (current->comm) > > > %H The nodename of the system (system_utsname.nodename) > > > %% A "%" > > > > > > For example, in my clusters, I have an NFS R/W mount at /coredumps > > > that all nodes have access to. The format string I use is: > > > > > > sysctl -w "kernel.core_name_format=/coredumps/%H-%N-%P.core" > > > > > > > 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 > > Because this way you can do more things with where you put your dumps, > such as using one element of this flexible method to select a directory, > where the dump directories for various applications would be on a single > NFS server, and dumps for another might be on another server, or all dumps > of a certain kind could share a filename, where only the latest dump would > be of interest (or take space).
OK, I'll buy that one. - 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/
| |