Re: pvxs Access/list problem

[Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov>]

On 11/19/25 8:49 AM, Heinz Junkes (FHI) wrote:

The patches I mentioned are already built into main (RTEMS7). And that gives us the problem
that UDP traffic stops after I establish a TCP connection on port 5075 and then close it.

Ah, so maybe a regression while attempting to add EOF handling to the kqueue mechanism?

libevent looks at some environment variables to control mechanism selection.

epicsEnvSet("PVXS_LOG", "pvxs.loop=INFO")
epicsEnvSet("EVENT_NOKQUEUE", "1")

dbdLoadRecord("dbd/someioc.dbd")
...

Possible env. names include EVENT_NODEVPOLL, EVENT_NOEPOLL, EVENT_NOWEPOLL (windows), EVENT_NOSELECT, EVENT_NOPOLL.

The effect can be seen in this pvxs.loop log message. eg. "... using kqueue".

2024-04-14T07:30:53.979678239 INFO pvxs.loop Enter loop worker for 0x2326b48 using kqueue

https ://github.com/epics-base/pvxs/issues/131#issuecomment-3555313801