Date: Mon, 8 Mar 2004 21:40:21 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: current@FreeBSD.org Subject: Question on 'ps -p <n>' in current Message-ID: <p060204e7bc72d891f49a@[128.113.24.47]>
next in thread | raw e-mail | index | archive | help
This topic may have come up before, a long time ago, and I just missed it. If so, apologies for the repeat. On stable, if you say 'ps -p <n>', and there is no process '<n>', then you get the header-line from 'ps' and nothing else. The command-status is set to indicate failure. On -current, the same command gives you the error message: ps: kvm_getprocs: No such process and you get no header line. Other OS's also give you the header line and no special error message. I think this behavior in current is an unplanned side-effect of the change in revision 1.46 of http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libkvm/kvm_proc.c where that was fixing a side-effect of a fix in revision 1.60 of malloc.c. In some other OS's, 'ps' behaves the way it does for us in -stable. Looking at SUSv3, it's not clear to me if either behavior is preferred. Should 'ps' in this situation behave like it does in -stable? Or is this a change that we deliberately wanted to make in -current? I would be willing to change 'ps' if people prefer the earlier behavior, but I'll leave it alone if this was an intentional change. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p060204e7bc72d891f49a>