Largely in agreement. Moved the conversation to the bug.
On Wed, Mar 7, 2018 at 11:08 AM, Ian Lance Taylor wrote:
> On Tue, Mar 6, 2018 at 3:55 PM, Rob Pike wrote:
> > That's poor. Exit code 2 is supposed to mean 'incorrect arguments' in the
> > Unix tradition.
> >
> > Something like 127 or 25
On Tue, Mar 6, 2018 at 3:55 PM, Rob Pike wrote:
> That's poor. Exit code 2 is supposed to mean 'incorrect arguments' in the
> Unix tradition.
>
> Something like 127 or 255 would be better.
I think you actually set it to 2, back in June, 2008, in what is now
known as git revision aeb43984ec7c86aee
https://github.com/golang/go/issues/24284
On Wed, Mar 7, 2018 at 10:55 AM, Rob Pike wrote:
> That's poor. Exit code 2 is supposed to mean 'incorrect arguments' in the
> Unix tradition.
>
> Something like 127 or 255 would be better.
>
> -rob
>
> On Wed, Mar 7, 2018 at 10:39 AM, cachvico
> wrote:
That's poor. Exit code 2 is supposed to mean 'incorrect arguments' in the
Unix tradition.
Something like 127 or 255 would be better.
-rob
On Wed, Mar 7, 2018 at 10:39 AM, cachvico wrote:
> Curious why panic appears to exit with code 2 (
> https://golang.org/src/runtime/panic.go line 757)
>
> I
Curious why panic appears to exit with code 2
(https://golang.org/src/runtime/panic.go line 757)
I can't find any mention of this in the spec; this should probably be
documented?
For example Supervisor treats exit codes 2 (and 0) as "expected" by
default, which leads to processes not restartin