similar to: NUDGE: Levels of verbosity?

Greetings. I am starting to use NSD, and would like to get some indication of when my server is being queried. The doc for "verbosity: <level>" aren't too specific. What do the various values mean? (This question can also be interpreted as a bug report for the nsd.conf man page...) --Paul Hoffman

On 9 Aug 2015, at 8:46, Benny Pedersen wrote: > Paul Hoffman skrev den 2015-08-09 17:40: > >> Initializing mail storage from mail_location parameter failed: mbox: >> mbox root directory can't be a file >> >> Which bit am I missing here? > > sudo doveadm import -u Foo mbox:/home/phoffman/project1/ "Project 1" > all > > untested When I

On 3 Aug 2015, at 7:16, Steffen Kaiser wrote: > On Mon, 3 Aug 2015, Paul Hoffman wrote: >> On 2 Aug 2015, at 23:27, Steffen Kaiser wrote: >>> On Sun, 2 Aug 2015, Paul Hoffman wrote: >>> >>>> Greetings. I have a bunch of mbox files that I want to import to an >>>> existing user, each into a new mailbox. That is, I want to import >>>>

On 08/09/15 13:36, Benny Pedersen wrote: > Paul Hoffman skrev den 2015-08-09 20:20: > >> Fatal: Import namespace initialization failed: Initializing mail >> storage from mail_location parameter failed: >> mkdir(/home/phoffman/project1) failed: Permission denied >> (euid=1013(phoffprop) egid=1013(phoffprop) missing +w perm: >> /home/phoffman, dir owned by

Paul Hoffman skrev den 2015-08-09 20:20: > Fatal: Import namespace initialization failed: Initializing mail > storage from mail_location parameter failed: > mkdir(/home/phoffman/project1) failed: Permission denied > (euid=1013(phoffprop) egid=1013(phoffprop) missing +w perm: > /home/phoffman, dir owned by 1001:1001 mode=0755) > > Does this error indicate that it is trying

https://bugzilla.samba.org/show_bug.cgi?id=6995 Summary: Suggested new verbosity level Product: rsync Version: 2.6.9 Platform: All OS/Version: Other Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: phoffman at proper.com

Hello, NSD 4.8.0 running on FreeBSD 13.2-RELEASE-p9 and serving both plain and DNSSEC signed zones. I noticed Permission denied errors in the logs for all domains listed in nsd.conf: [2024-01-12 12:20:05.710] nsd[8655]: info: writing zone domain-plain.org to file domain-plain.org [2024-01-12 12:20:05.710] nsd[8655]: error: cannot write zone domain-plain.org file domain-plain.org~: Permission

Paul Hoffman skrev den 2015-08-09 17:40: > Initializing mail storage from mail_location parameter failed: mbox: > mbox root directory can't be a file > > Which bit am I missing here? sudo doveadm import -u Foo mbox:/home/phoffman/project1/ "Project 1" all untested

hi, At least with a recent version if it is a time sync issue nsd will do a specific log msg that. Laura, can you send over the actual configuration? (maybe replacing the key with a placeholder or rotating the keys afterwards) It sounds strange if nsd checks tsig on the notify, but allow xfr without it. Regards, Tam?s May 16, 2024 16:14:59 Anand Buddhdev via nsd-users <nsd-users at

Hi all, I'm running NSD 4.9.1 on OpenBSD 7.6. I recently upgraded from OpenBSD 7.5, which I believe had NSD 4.8.0 in base, and did not see this behavior prior. When I try to reload a zone using nsd-control, I am seeing an error message in my logfile: "error: reload: old-main quit during quit sync" This error does not appear to happen every time I run reload, but it does get

Op 04-01-2025 om 17:10 schreef Otto Retter via nsd-users: > Hi all, > > I'm running NSD 4.9.1 on OpenBSD 7.6. I recently upgraded from OpenBSD > 7.5, which I believe had NSD 4.8.0 in base, and did not see this > behavior prior. Thanks Otto, Indeed, NSD 4.8.0 did not log this condition as an error message and just proceeded if the old-main would quit. With 4.9.0 reloading

Hi Peter, NSD processes updates in batches. xfrd receives the [AI]XFR and schedules a reload for the main process, which in turn forks new serve children. The served-serial is updated after main reports success, the commit-serial (update written to disk) is updated before the reload (to explain the serials). The difference in timestamp can be explained by the fact that NSD looks up if the serial

Dear NSD users, Here is the release candidate for NSD 3.2.15. This comes with ILNP support, NSD-RRL and different TSIG initialization (it fails if it can't find no suitable algorithms, instead of can't find 'one of the'). Plus some bugfixes. The NSD-RRL implementation is based on the work by Vixie and Schryver. However, because of the code-diversity argument that is at the basis

Hi Jeroen, I just realised that the version I use is very old -- 4.1. So first what I should do -- updating it and only then come here , asking for clarification. ??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>: > Hi Peter, > > NSD processes updates in batches. xfrd receives the [AI]XFR and > schedules a reload for the main process, which in turn forks

Hi, NSD 4.10.1rc2 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz sha256 ce2e82bc673aeff3a71aeb422fa38fb8db0a591edb76c13b0e4dde83ec8253e9 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.10.1rc2.tar.gz.asc Version 4.10.1 consists primarily of bug fixes. @bilias implemented mutual TLS authentication for zone transfers. Please consult the nsd.conf manual for details

On Sat, 28 Dec 2019 17:02:09 +0100 richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > The problem is (was) that I used "include:" statements in nsd.conf > to load zone information. Apparently nsd does not reread the include > files upon a SIGHUP. I scripted everything into 1 file and a HUP > rereads the zone info now. Wrong, I made a mistake it

Dear all, NSD 4.11.0 is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz sha256 93956d90d45ffa9f84f8ca2f718a42105e4236d094ce032211849f1a12cdc158 pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0.tar.gz.asc Version 4.11.0 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when enabled with the new

Dear all, NSD 4.11.0rc1 pre-release is available: https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz sha256 7594d014199585c24f6593649bfc657078d411a3f09eb31192a35a7c031c028f pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.11.0rc1.tar.gz.asc Version 4.11.0rc1 sees various small features and bugfixes. One notable feature is that configuration can be reloaded and evaluated on SIGHUP, when

Dear All, Please help me understand why timestamps in logs are different from those in nsd-control zonestatus output: served-serial: "2024022603 since 2024-02-27T08:07:51" commit-serial: "2024022603 since 2024-02-27T08:07:51" Feb 26 18:47:34 slave-server nsd[780]: zone testzone.test. received update to serial 2024022603 at 2024-02-26T18:47:33 from

NSD 2.3.2 is a bugfix release. Please see the README document for configuration and installation instructions. You can download NSD from http://www.nlnetlabs.nl/nsd/ Note: we switched to SHA-1 for tarball digest. 2.3.2 ============= FEATURES: - Bug #101: add support for the SPF record. BUG FIXES: - Bug #100: replaced non-portable use of timegm(3) with portable