ps: add build option to disable ps option warning
Slackware seems to have this patch, while it is not in use(?) Well, the upstream procps-ng allows one to disable warnings if that is wanted. After all having this sort of 'feature' does not cost much, while lacking it might annoy someone. A patch from Slackware. Reference: http://www.ftp.be/packages/slackware/slackware_source/a/procps/procps.nowarning.diff.gz Backported-by: Sami Kerola <kerolasa@iki.fi> Conflicts: proc/ksym.c
This commit is contained in:
11
ps/parser.c
11
ps/parser.c
@ -1231,8 +1231,19 @@ try_bsd:
|
||||
// for some non-default personalities. So "ps -ax" will parse
|
||||
// as SysV options... and you're screwed if you've been patching
|
||||
// out the friendly warning. Cut-over is likely to be in 2005.
|
||||
#ifdef BUILD_WITH_WHINE
|
||||
// Slackware:
|
||||
// IMO, people can change old habits if and when user 'x' comes
|
||||
// along. I still find this warning to be a POLA violation. No
|
||||
// offense... that's the beauty of open source. You've got your
|
||||
// ideas about this, and I have mine, and we're allowed to
|
||||
// disagree. Nothing in the UNIX or POSIX standards requires
|
||||
// this (annoying) warning to be displayed, and we're not
|
||||
// changing the actual behavior of ps in any way. I know of no
|
||||
// other 'ps' that produces this message.
|
||||
if(!(personality & PER_FORCE_BSD))
|
||||
fprintf(stderr, "Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html\n");
|
||||
#endif
|
||||
// Remember: contact procps@freelists.org
|
||||
// if you should feel tempted. Be damn sure you understand all
|
||||
// the issues. The same goes for other stuff too, BTW. Please ask.
|
||||
|
Reference in New Issue
Block a user