Re: Draft spec for new dpkg "triggers" feature

[Ian Jackson <ian@davenant.greenend.org.uk>]

Ian Jackson writes ("Re: Draft spec for new dpkg "triggers" feature"):
> Do any of our shells currently impose a different limit ?  The SuSv3
> limit is 4096 bytes for arguments and environment, which is already
> getting into the kind of range where C programmers usually use dynamic
> allocation, so if they do it's probably easy to fix.

-anarres:~> PS1='$ ' foo="`perl -e 'print "x"x65536'`" dash -c whoami
ian
-anarres:~> PS1='$ ' foo="`perl -e 'print "x"x131072'`" dash -c whoami
bash: /bin/dash: Argument list too long
-anarres:~> env | wc -c
1003
-anarres:~> PS1='$ ' foo="`perl -e 'print "x"x(131072-1100)'`" dash -c whoami
ian
-anarres:~> PS1='$ ' foo="`perl -e 'print "x"x(131072-1000)'`" dash -c whoami
bash: /bin/dash: Argument list too long
-anarres:~> PS1='d ' dash
d echo >/dev/null "`perl -e 'print "x"x(131072-1000)'`"
d echo >/dev/null "`perl -e 'print "x"x(131072-200)'`"
dash: perl: Argument list too long
d

So there doesn't seem to be a problem with dash.

Ian.