No, it shouldn't impact the outcome of this case.
I explained where nproc came from. It also has an impact on script
portability because nproc is completely non standard (the lack of
getconf on old platforms and the buggies of getconf implementations
like Solaris getconf is the reason why ksh93 has a built in getconf).
A nit: Maybe the nproc(1) man page should contain the warning:
===== cut =====
nproc is not portable across platforms. Portable scripts shall use the
output of NPROCESSORS_ONLN to determinate the number of active
processing elements in a system.
===== cut =====
Olga
2010/5/13 Darren J Moffat <darren.mof...@oracle.com>:
> On 13/05/2010 17:34, ольга крыжановская wrote:
>>
>> Solaris /usr/bin/**/getconf have a couple of bugs, that's just an old
>> one you're hitting.
>>
>> nproc is in the coreutils package because getconf is part of glibc and
>> not of coreutils and the coreutils authors have already stated their
>> disapproval for the getconf interface. I'd expect that each time
>> getconf has a useful application for coreutils users the coreutils
>> team just adds an own interface utility for it.
>
> Interesting information but it shouldn't impact the outcome of this case to
> deliever GNU coreutils as is.
>
> --
> Darren J Moffat
>
--
, _ _ ,
{ \/`o;====- Olga Kryzhanovska -====;o`\/ }
.----'-/`-/ olga.kryzhanov...@gmail.com \-`\-'----.
`'-..-| / http://twitter.com/fleyta \ |-..-'`
/\/\ Solaris/BSD//C/C++ programmer /\/\
`--` `--`
_______________________________________________
opensolaris-arc mailing list
opensolaris-arc@opensolaris.org
