On Thu, Nov 26, 2009 at 6:41 AM, Craig Small <csm...@debian.org> wrote:
> I disagree. pgrep/pkill (they're the same binary) are like grep and use > the same flags. I think that is important. I think it is more important to protect users. But you are the maintainer and so the decision is up to you. Now I will continue to respond to the other arguments that you said in your last mail. > Changing the flags now will cause more problems than it will solve > because now you will have different flags for new Debian servers, old > ones and the rest of the world. Maybe you could gradually transition it in, by making both options work for a year or two and printing a warning message, then disabling -v. > If you are not careful you can do bad things easily. pkill -v is in the > same vein as fuser -km / or the old rm -rf / mydir/myfile. Yes. But I think it would be good if you disable this particular bad thing, just like GNU disabled the old rm -rf / mydir/myfile. > Principle of least astonishment is all good, but inconsistent flags > across different Linuxs is even worse. Which Linux does not use Debian procps? For example, it looks like Fedora uses Debian procps.[1] > While I do understand what you > are trying to do here I don't agree. Given that, I'm closing this > bug. What would you think if we posted on the debian-devel list and asked for more advice on other possible options to prevent accidental killing-all-processes with pkill -v? ^ [1]. http://cvs.fedoraproject.org/viewvc/rpms/procps/devel/FAQ?view=markup -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
