| Von: |
"Massimo S." <ecs-isp@2rosenthals.com> |
Kopfzeilen anzeigen
E-Mail Quelltext |
| Betreff: |
Re: [eCS-ISP] Updating bind |
| Datum: |
Wed, 5 Nov 2025 20:35:06 +0100 |
| An: |
eCS ISP Mailing List <ecs-isp@2rosenthals.com> |
|
|---|
Il 24/10/2025 08:02, Steven Levine ha scritto:
In <list-14541201@2rosenthals.com>, on 10/23/25
at 10:03 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi,
i forgot, when this "unresponsible+unkillable" state happens i don't get
any popuplog.os2 or any exceptQ dump
just nothing
Most likely named has trapped and got stuck in the exit list. This is the
case for the vast majority of unkillable processes. When this occurs, you
will not get a popuplog.os2 entry. You will not get an exceptq report
unless you run with
set EXCEPTQ=Z
to report for XCPT_PROCESS_TERMINATE exceptions or
set EXCEPTQ=ZZ
to report for XCPT_ASYNC_PROCESS_TERMINATE exceptions.
Steven
Hi Steven,
i've been very busy in the last days so i'm still at this point
i don't know the diffence between xcpt_process.. and xcpt_async..
what do you suggest here to catch the bind issue/eQ dump?
thanks
massimo
|