From: Thorsten Glaser <tg@mirbsd.de>
To: musl@lists.openwall.com
Cc: erny hombre <hombre67@gmx.at>
Subject: Re: [musl] possible bug in syslog
Date: Thu, 13 Jun 2024 15:44:19 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2406131540390.32521@herc.mirbsd.org> (raw)
In-Reply-To: <20240613153729.GY10433@brightrain.aerifal.cx>
Rich Felker dixit:
>That seems okay. However I also kinda wonder if LOG_MAKEPRI shouldn't
>just be removed.
Best not to: I’ve seen code defining it as (((fac) << 3) | (pri))
if not defined while grepping, and:
gnu/usr.bin/perl/ext/Sys/Syslog/Syslog.xs: croak("Your vendor has not defined the Sys::Syslog macro LOG_MAKEPRI");
>This would highlight anything that was previously
>broken, and there seems to be utterly no reason to use it when the
>standard already specifies that you just or (I missed that before).
It seems that LOG_MAKEPRI and the shift may be needed on OS/2…
>(which TBF is kinda buried; the text in XBD for syslog.h says the
>facilities are for openlog not for openlog and syslog).
Maybe ask on the Open Group mantis for an editorial correction there?
bye,
//mirabilos
--
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design. <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)
prev parent reply other threads:[~2024-06-13 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 11:44 erny hombre
2024-06-13 13:46 ` Rich Felker
2024-06-13 15:20 ` Thorsten Glaser
2024-06-13 15:37 ` Rich Felker
2024-06-13 15:44 ` Thorsten Glaser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSM.4.64L.2406131540390.32521@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=hombre67@gmx.at \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).