| Re: [chrony-users] Regarding socket permissions |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Regarding socket permissions
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 14 Mar 2023 09:16:13 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678781781; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=pAVyLDKtb2YWp7i4DiZM4jXVYNAuOlOazrYuSlkaY+w=; b=XdGOkujoZpDjfe/3NaQyKJ9zeezDSg95mNf9wVipoI7VPj7/Ru6u1tevQkjWsStFD6v3TC TK/A3mnObaNZm2gbIKj1RHn7/DL3l/VEI9iVy1JFjG6LYjL2tYRlaViEFnf1UB6Oug1rsc up6EU9tOWIHS2oyC2dTK+MowEJxDznw=
On Tue, Mar 14, 2023 at 09:03:18AM +0100, Morten Nissov wrote:
> Is there a material difference in performance using SHM vs socket? My
> understanding was maybe, as SHM polls. If there is no significant
> difference then I don't really need sockets.
If there is only one sample per poll (dpoll == poll), there might be
some difference, but probably not significant. Try it and see.
Note that SHM is now deprecated in favor of SOCK for security reasons.
There is no defined order of starting the SHM producer and consumer,
so chronyd doesn't know if an existing segment wasn't created by an
attacker trying to feed chronyd with fake samples.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.