Axel Beckert writes ("Re: Bug#1000138: /usr/bin/screen: command arguments
beyond 62 silently discarded"):
> Axel Beckert wrote:
> > Unfortunately the relevant error message "Argument count or length
> > limit exceeded" does not show up with the patch.
>
> Additionally it also exits with exit code zero.
How alarming.
> Both are not what you were declaring as "tolerable behaviour" as you
> also required "message on stderr plus nonzero exit status" as I do.
Indeed so.
> I though must admit that "Panic()" is indeed widely used all over the
> screen source code, so it looks like the right function for this purpose.
>
> But if I type
>
> Ctrl-A:screen ../t.sh 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
> 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
> 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
> 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
> 88 89 90 91 92 93 94 95 96 97 98 99 100
>
> inside a Screen session, I do get the proper error message
>
> : too many tokens.
>
> (with the empty string before the colon) as a status line message. So
> there it at least aborts properly.
That was my test case.
> I also tried to modify your patch to at least get a non-zero exit code
> or a visible error message in your case, but failed so far for both.
I will also look at this, but probably not until tonight. Will that
be soon enough for you ?
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
