Date: Tue, 7 Feb 2017 15:30:05 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: display base/pkg build options Message-ID: <f5a68681-bcf4-bd1c-43a8-412c7a3409e5@FreeBSD.org> In-Reply-To: <02051c6c4dac2185943b667917f8256c.squirrel@webmail.harte-lyne.ca> References: <mailman.98.1486468802.21252.freebsd-questions@freebsd.org> <02051c6c4dac2185943b667917f8256c.squirrel@webmail.harte-lyne.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --IANLXv03V04FMoalpH5gwPLR6Nv3XULDT Content-Type: multipart/mixed; boundary="fxAHPluFNbnb8h8XJ2BMvgQT4bL0KDNQf"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <f5a68681-bcf4-bd1c-43a8-412c7a3409e5@FreeBSD.org> Subject: Re: display base/pkg build options References: <mailman.98.1486468802.21252.freebsd-questions@freebsd.org> <02051c6c4dac2185943b667917f8256c.squirrel@webmail.harte-lyne.ca> In-Reply-To: <02051c6c4dac2185943b667917f8256c.squirrel@webmail.harte-lyne.ca> --fxAHPluFNbnb8h8XJ2BMvgQT4bL0KDNQf Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2017/02/07 14:31, James B. Byrne via freebsd-questions wrote: > Thank you again. Is it correct to infer from these lines from the > provided reference that the __ ntpsigndsocket __ setting is supported > in /etc/ntp.conf? >=20 >=20 > 1415 /* Path to sign daemon rendezvous socket */ > 1416 #define NTP_SIGND_PATH "/var/run/ntp_signd" >=20 > I previously set this in /etc/ntp.conf without error, but that does > not mean that it is recognised: >=20 > # grep ntpsigndsocket /etc/ntp.conf > ntpsigndsocket /usr/local/samba/var/lib/ntp_signd/ >=20 Given you could add that to ntp.conf without ntpd complaining (by which I take it you mean ntpd would start up and not log any problems to syslog) that is pretty good evidence the signd socket is supported. You can see what processes are opening that named socket by using socksta= t. Of course, the way to establish that signd support absolutely is provided to access the signd functionality -- try it and see. Cheers, Matthew --fxAHPluFNbnb8h8XJ2BMvgQT4bL0KDNQf-- --IANLXv03V04FMoalpH5gwPLR6Nv3XULDT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJYmegDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnhZAP/1BbAPZS9b3LkmVYtiAIXUjI HNcN6TgR+VRmcxQllWBNwGaJv9kyX7wXeEJO0rihooB91M3t1zrIbu4NgBMmEoAW C7UeEjm0GReTVrcYp6P/Cn71LseDaRC4QbyCmPk3VYrFE4QEp1aMDr5ny6ytEb7Z xR8k9J5HnoF2QX8GRRZIlR6AeshWtWn2Y2PeVMG5SP6Ype1x0SB3tkcPvIN08g8u kzLRxsW0ueoiv5LkomfdeDNapUWR2jDTeuKjbWK698IMJu+1FN5Hl0gqx08uAuZs SzP8WubUW+ph22YdNF4MX+wrTAS8KEJmKcO9PB6g9QSgwB6D7p4n4ZLa1uQwgWYv ggvrAci5ykB7KCEHhc98N3kaRXSIRiRWTKQCcAOVSUR0pKoISFAbtmgvk71dZ2Kt pofpXGKVHQDh2IFM9TJzkvuM4GjVYmkCoVXQw+Sfo+yLt631/82iGy4erpYoVCRr YM75aza7JAaGI4SlkzfcMwacnL9uXBAN6WUKVWnX5BFjOOuot0KGiWsadFa6ND+b 5uab9BxfQ8tjQVwRGrKHc3X0rW+VVpsTBRCmvfeRF2IR4KhMBqjn89vCGcePzpzg cPiLnMRlGU2WFdIzHeKU5FjysgRTKCN8OPjui/bk0XX1wiXhJ2ttN8oQSltMXNj/ iQUOMfpMtjVkb+A59KQu =2gxq -----END PGP SIGNATURE----- --IANLXv03V04FMoalpH5gwPLR6Nv3XULDT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f5a68681-bcf4-bd1c-43a8-412c7a3409e5>