> Thread.cc:91
> >#15 0x7f6f2f8c36ba in start_thread (arg=0x7f6f2d222700) at
> pthread_create.c:333
> >#16 0x7f6f2eb543dd in clone () at ../sysdeps/unix/sysv/linux/
> x86_64/clone.S:109
> >
> >still, pretty much the same, just easier to read
> >
eate.c:333
>#16 0x7f6f2eb543dd in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
>
>still, pretty much the same, just easier to read
> ____
>From: James Peach
>Sent: Tuesday, November 7, 2017 8:30 PM
November 7, 2017 8:30 PM
To:
Subject: Re: API Proposal - TSStatGet/SetString
> On Nov 7, 2017, at 1:39 PM, Zelkowitz, Evan
wrote:
>
> If that would be picked up by stats that would probably work, but seems
to generate a segv for me:
>TSMgmtStringCreate
From: James Peach
Sent: Tuesday, November 7, 2017 8:30 PM
To:
Subject: Re: API Proposal - TSStatGet/SetString
> On Nov 7, 2017, at 1:39 PM, Zelkowitz, Evan
> wrote:
>
> If that would be picked up by stats that would probably work, but seems to
> generat
> On Nov 7, 2017, at 1:39 PM, Zelkowitz, Evan
> wrote:
>
> If that would be picked up by stats that would probably work, but seems to
> generate a segv for me:
>TSMgmtStringCreate(TS_RECORDTYPE_PROCESS, "my.interface.name", "default
> value",
>TS_RECORDUPDATE_DYNAMIC, TS_RECORDCHECK_N
If that would be picked up by stats that would probably work, but seems to
generate a segv for me:
TSMgmtStringCreate(TS_RECORDTYPE_PROCESS, "my.interface.name", "default
value",
TS_RECORDUPDATE_DYNAMIC, TS_RECORDCHECK_NULL, NULL /* check_regex */,
TS_RECORDACCESS_READ_ONLY);
traffic_se
> On Nov 7, 2017, at 8:35 AM, Zelkowitz, Evan
> wrote:
>
> Proposing adding stat string support
>
> TSReturnCode TSStatGetString(int id, char *string, int len);
> TSReturnCode TSStatSetString(int id, char *string, int len);
>
> This way we can store stat strings for retrieval by TS stats. Som
