On 23-06-13 07:45, Brett Lymn wrote:
| On Fri, Jun 09, 2023 at 08:47:10AM -0400, Mouse wrote:
| >
| > In any case, the major issue I would have with it is the lack of
| > authentication. But that's so obvious that I assume you would be doing
| > something like requiring a password - or
On 23-06-01 15:44, Valery Ushakov wrote:
| We have mtree(8) man page for our mtree that documents the format of
| the mtree spec. We also have an mtree(5) page that documents the
| format of the mtree spec, but that pages comes from libarchive. This
| is kinda confusing.
I agree!
| W
On 23-05-31 13:12, tlaro...@polynum.com wrote:
| > Also, on 23-05-30 21:03, tlaro...@polynum.com wrote:
| > | (When checking, so even with -C, nothing is written via
| > | syslog since, then, inetd is not a daemon but just an utility---a
syntax
| > | checker---printing messages on st
On 23-05-31 12:43, tlaro...@polynum.com wrote:
| And I think you're right: the info will go in a 0400 file in /tmp, and
| will be a way to obtain various running infos---but for now, just the
| running config (it could perhaps be extended, but not now, to add
| stats, what is masked by a se
On 23-05-31 03:54, Robert Elz wrote:
| Date:Tue, 30 May 2023 21:03:21 +0200
| From:tlaro...@polynum.com
| Message-ID:
|
| | Do you think that SIGINFO is sound as the signal to obtain a config
DUMP in
| | the syslog?
|
| First, dumping config to s
On 21-01-31 18:12, David Holland wrote:
| Alternatively you could put the glob in the include explicitly
| (that is, "include dir/*.conf"
That seems the sanest to me too; it's explicit, and it's also
following a well-established pattern used by other applications,
including: dovecot, (apache)
I've decided not to pursue this any further.
No objections if anyone else wants to take up the cause.
On 20-07-17 23:20, Alistair Crooks wrote:
| Just to get back to the original subject - fully support {} around single
| statements - have been doing that in my own code for ages.
|
| Wou
On 20-07-12 10:01, Luke Mewburn wrote:
| I propose that the NetBSD C style guide in to /usr/share/misc/style
| is reworded to more explicitly permit braces around single statements,
| instead of the current discourgement.
|
| IMHO, permitting braces to be consistently used:
| - Adds
I propose that the NetBSD C style guide in to /usr/share/misc/style
is reworded to more explicitly permit braces around single statements,
instead of the current discourgement.
IMHO, permitting braces to be consistently used:
- Adds to clarity of intent.
- Aids code review.
- Avoids gotofail: http
