On 10/20/15 at 03:19pm, Dangyi Liu wrote:
Only advanced users or instructed users may need to get access to
this
config file. For example, we may tell some customers to "add quiet to
KDUMP_COMMANDLINE_REMOVE and send the full log to us", but we cannot
tell them "edit /bin/kdumpctl at line 108 to add quiet".
Anyone who knows unix/linux knows what they can do to a file under
/etc/. Sometime we can tell people or send a script patch to ask them to
change kdumpctl. Just etc file is formal.
> > >
> > > 3rd, I saw you were confused about which one should be handled
> > > firstly
> > > about KDUMP_COMMANDLINE_APPEND and KDUMP_COMMANDLINE_REMOVE. This
> > > is a
> > > kind of torture we make to put on ourselves. We give users of
> > > kdump too
> > > many options.
I think it's better to remove first then append. For example we can
remove all "dydbg" first then add other dynamic debug options.
I don't have a good idea about this. Let's your final code. In the end a
clear paragraph need be wrote into howto or other documents.
Dangyi