Search Results

To repeat: It's not a setting, it's hardcoded. Changing it won't change programs. You'd just make it lie.

It might be possible to build a custom ksh with a higher setting but that sounds far...

I've verified that it's not cheating in my case by having the script print an extra character. The count would be out several more if ksh were being run repeatedly.

It's a hardcoded limit, not something trivially changed. Even if you coerce getconf into changing, it won't be reflected in programs. But I suspect you're using a crusty old pdksh/ksh88, newer ksh...