Re: nslookup issues

2022-09-13 Thread Mark Andrews
The old socket code did something like int fd = socket(…); if (fd == -1) { error handling } if (fd < 100) { int newfd = fcntl(fd, F_DUPFD, 100); if (newfd == -1) { error handling

Re: nslookup issues

2022-09-13 Thread Casey Deccio
> On Sep 13, 2022, at 3:35 PM, Graham Clinch wrote: > > I suspect nrpe-ng is closing stdin before launching nslookup. > > > With mac homebrew's build of bind 9.18.6 and a bit of shell redirection to > close stdin, I get: > > --- > $ /opt/homebrew/bin/nslookup -version > nslookup 9.18.6 > >

Re: [External] nslookup issues

2022-09-13 Thread Graham Clinch
On 13/09/2022 21:09, Casey Deccio wrote: After rerunning nrpe-ng with the following: sudo strace --read=4 -F /usr/bin/python3 /usr/sbin/nrpe-ng --debug -f --config /etc/nagios/nrpe-ng.cfg I see the following in the debug output on Host B: [pid 1390861] read(4, "nslookup: ./src/unix/core.c:570

nslookup issues

2022-09-13 Thread Casey Deccio
I am trying to track down a bug. I think it is in nslookup (which is why I'm asking here), but there are so many pieces required to reproduce it that I cannot tell for sure. Let me explain my setup: All hosts are running Debian bullseye. None of the problems happened *until* I upgraded from