ulimit -a: -r vs -N [was Re: pkgsrc patches for zsh]

[Thomas Klausner <tk@xxxxxxxxxx>]

Hi!

A couple of days ago I noticed that 'ulimit -a' is now different (on
NetBSD-6.99.44/x86_64 with zsh-5.0.5); see in the old mail below what
it looked like before:

-t: cpu time (seconds)              unlimited
-f: file size (blocks)              unlimited
-d: data seg size (kbytes)          262144
-s: stack size (kbytes)             4096
-c: core file size (blocks)         unlimited
-m: resident set size (kbytes)      32485916
-l: locked-in-memory size (kbytes)  10828638
-u: processes                       160
-n: file descriptors                128
-b: socket buffer size (bytes)      unlimited
-v: virtual memory size (kbytes)    unlimited
-N 11:                              160

It seems "-r" was replaced with "-N", and no help string is supplied.

I've also tried zsh git head and see the same issue there.

You probably know better where to look for this.

Thanks,
 Thomas

On Fri, Aug 17, 2012 at 02:16:06PM +0200, Thomas Klausner wrote:
> On Fri, Aug 17, 2012 at 12:35:35PM +0100, Peter Stephenson wrote:
> > Ah, I noticed that but didn't see it on your list from sh --- now I look
> > more closely, that's -b, so that should be added too.  We support the
> > resource, just not the option letter.  It's done as bytes, not
> > kilobytes, so I changed that, too.
> 
> Looks fine, except for a missing space in the -b line:
> # ulimit -a
> -t: cpu time (seconds)         unlimited
> -f: file size (blocks)         unlimited
> -d: data seg size (kbytes)     262144
> -s: stack size (kbytes)        4096
> -c: core file size (blocks)    unlimited
> -m: resident set size (kbytes) 12186708
> -l: locked-in-memory size (kb) 4062236
> -u: processes                  160
> -n: file descriptors           128
> -b: socket buffer size (bytes)unlimited
> -v: virtual memory size (kb)   unlimited
> -r: threads                    160
> 
> I've added all these patches to pkgsrc, thanks again.
> 
> I have a packaging issue as well.
> When grepping for "bin/zsh" on the source, there are two kinds of matches:
> 
> Functions/Example/zless:#!/bin/zsh -f
> Functions/Example/cat:#!/bin/zsh -f
> Functions/Misc/zed:#!/bin/zsh
> Functions/Misc/run-help:#!/bin/zsh
> Functions/Misc/zcalc:#!/bin/zsh -i
> Functions/Misc/checkmail:#!/bin/zsh
> Functions/Misc/sticky-note:#!/bin/zsh -fi
> Functions/Misc/zkbd:#!/bin/zsh -f
> Functions/Calendar/calendar_add:#!/bin/zsh
> Test/ztst.zsh:#!/bin/zsh -f
> Test/runtests.zsh:#!/bin/zsh -f
> 
> Util/reporter:#!/usr/local/bin/zsh
> Misc/globtests.ksh:#!/usr/local/bin/zsh -f
> Misc/globtests:#!/usr/local/bin/zsh -f
> 
> The installation directory with pkgsrc is ${PREFIX}, usually /usr/pkg,
> which is why pkgsrc replaces these to point to ${PREFIX}/bin/zsh. I
> wonder if you see it as worth your time to fix the path in these files
> to ${PREFIX}/bin/zsh (expanded, of course) during the build?
> 
>  Thomas