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
> 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
>
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:
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
I would propose one line per protocol for disabled methods. This would
allow for easier log parsing
On 2022-09-13 06:28, Petr Špaček wrote:
On 02. 09. 22 15:49, Anand Buddhdev wrote: On 02/09/2022 13:53, Mark
Andrews wrote:
Hi Mark,
We don't log rsamd5 is disabled now ec or ed curves
> On 13 Sep 2022, at 14:34, Peter wrote:
>
> Apparently, the first connect() happens (after chroot but) before
> droppings priviledges.
> (The FreeBSD integration script does set -u to UID "bind", by default.)
>
> So, apparently, fstrm_capture should also run as UID "bind" (and would
> then
On Tue, Sep 13, 2022 at 12:24:15PM +0200, Petr Špaček wrote:
! On 12. 09. 22 15:49, Peter wrote:
! > On Mon, Sep 12, 2022 at 03:01:38PM +0200, Petr Špaček wrote:
! > ! My testing did not uncover anything problematic.
! > !
! > ! Versions:
! > ! fstrm 0.6.1-1
! > ! protobuf 21.5-1
! > ! protobuf-c
> Can you propose log line?
>
> Should it be one line per algorithm? Or one line with all disabled? Or
> one one with all enabled? What log level? Log category? It it okay it
> will be almost always logging GOST? ...
I am not using Red Hat, but when debugging DNSSEC issues it would be helpful to
On 02. 09. 22 15:49, Anand Buddhdev wrote:
On 02/09/2022 13:53, Mark Andrews wrote:
Hi Mark,
We don’t log rsamd5 is disabled now ec or ed curves when they are
not supported by the crypto provider. Why should rsasha1 based algs be
special?
The problem I see with 9.18.6 is that at startup,
On 12. 09. 22 15:49, Peter wrote:
On Mon, Sep 12, 2022 at 03:01:38PM +0200, Petr Špaček wrote:
! My testing did not uncover anything problematic.
!
! Versions:
! fstrm 0.6.1-1
! protobuf 21.5-1
! protobuf-c 1.4.1-1
!
!
! A procedure which works:
! - start BIND configured with
! options {
!
10 matches
Mail list logo