Checking the Apple man pages, they show documentation for it on 10.7.4 and for 10.4-intel, so it's been around on the servers for some time. (Also, the man pages still list it as a server-only command. Those may not have been updated yet for Mountain Lion.)
(If you're not already aware of them, Apple has a very full set of man pages online. The framed browsing style is a pain, but the pages are still great for scanning and finding new commands.)
Win32 command line utilities aren't really related to the DOS APIs in any way.
That doesn't make the commands themselves "Unix commands", which would AFAIU, be described under the "Commands and Utilities" portion of the standard:
The document containing these standards is not freely available online, but may be purchased: https://www2.opengroup.org/ogsys/jsp/publications/Publicatio...
Wikipedia lists a set of IEEE utilities which is pretty brief, and contains a number of largely obsolete standards (SCCS anyone?), comprising of 161 commands:
Or are they just new OSX tools that happen to run from a shell?
But a unix program need not be available for every unix under the sun to still be a unix program.
If my long-windedness can be excused, a pgrep anecdote that I feel must be told: when Mike was originally doing pgrep and pkill, he wanted one to be able to search on every field specified in proc(4), including the wchan (denoted by pr_wchan), an archaic field that was actually a stowaway from Multics (!). Even by Solaris 7, the wchan had no real significance in Unix, and the co-inventor of /proc, Roger Faulkner, flew into an indignant rage that Mike would include it -- and "pgrep -w" quickly disappeared from both Mike's workspace and his PSARC case. Now, Mike and I were also the gatekeepers on Solaris 7, and we both wore pagers (aside: I'm old) that would page us whenever anyone integrated anything into Solaris with the bug synopsis. Sometime after pgrep/pkill integrated into Solaris 7, I decided to screw with Mike a little: he was headed to watch a Boston Celtics playoff game, and I knew he would be away from a machine for a few hours, so I started paging him with fake integrations that I knew would enrage him. The first integration that I fooled him with was someone that he disliked rewriting a command that Mike himself had just taken from the same engineer and himself rewritten -- and I really tweaked him by making the synopsis be that the "error messages could be improved" (trust me that this was a sore point). Now, I wanted the fake integrations to get more and more absurd over the course of the playoff game, so I next paged him with an integration from Roger: "pgrep(1) needs to be able to search on wchan". I was just getting ready to send my next page (after all, I had a couple hours of mischief planned) when Mike suddenly appeared in my office, drenched with sweat, panting "please just tell me the first one was a joke too!" As it turns out, he had taken my first page a little too seriously, had immediately stopped watching the playoff game, got back in his car and was returning to work to "throw [disliked engineer]'s monitor out his office window." When he saw the wchan option to pgrep, he knew that I must be screwing with him, and fortunately stopped at my office before doing anyone (or anything) physical harm. And that's how "pgrep -w" saved a monitor -- if not a life.
The source code of caffeinate(8) is available at http://opensource.apple.com/source/PowerManagement/PowerMana...
Sometimes I leave command line programs running overnight then get annoyed when I find that my Mac went to sleep after an hour because I'd forgotten to adjust the power saving settings.
So running caffeinate -u <my command> will be very handy indeed
Ex: What are all of the python subprocesses started by PID 1234? `pgrep -P 1234 python`
I've been missing it on osx for a long time.
brew install proctools