Hi, I don't use chrony myself, so I can just look at the build-system.
On Tue, Jun 15, 2021 at 11:55:47AM +0200, Mircea Ciocan wrote: > unless I'm doing something very wrong, the "out of the box" chrony package > does not allow talking with the chronyc, the client and daemon control > user-space utility, it doesn't even create the Unix socket: > /var/run/chrony/chronyd.sock. > > Once the line "--without-tomcrypt" in CHRONY_CONF_OPT is removed, everything > will work OK. This makes no sense at all. tomcrypt is a external library that is currently not available in PTXdist. So removing this options should not change anything. Please take a look at the build (e.g. changes to config.h and Makefile) to see what actually happens. > Also the option "--with-user=chrony" may make the daemon more > secure, but it certainly messes up the logging and drift files due to > permissions of the /var/run and /var/log. That's just the default user. And as far as I know, this works fine with systemd. If you use busybox init, then maybe the init script needs to be changed to create directories with the correct permissions. Patches are welcome. > Out of these only the tomcrypt removal is critical, if somebody can explain > the reason behind it, or what can be done to enable the client functionality > with the existing compile time options I'll be most happy, because now I had > to move the rule to project rules and remove it. Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected] To unsubscribe, send a mail with subject "unsubscribe" to [email protected]
