Date: Sun, 12 Aug 2018 15:50:08 +0000 From: bugzilla-noreply@freebsd.org To: rc@FreeBSD.org Subject: [Bug 230561] ntpd error: only one pidfile option allowed Message-ID: <bug-230561-20181-QPhX3iwlHA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230561-20181@https.bugs.freebsd.org/bugzilla/> References: <bug-230561-20181@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230561 Ian Lepore <ian@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|Open |Closed --- Comment #3 from Ian Lepore <ian@FreeBSD.org> --- The fact that the pidfile argument was included in the default ntpd_flags i= s a historical and accidental mistake dating back to when the ntpd rc stuff was imported from netbsd. The freebsd rc system does not support changing the location of the pidfile to some arbitrary place it is unaware of; doing so removes the ability to properly restart, stop, query status, etc. In other words, while the flag was historically in the default flags, it co= uld never be usefully changed, and indeed if you do some searching you'll see t= hat its accidental presence in the defaults has led to many errors and questions from users over the years as they tried to set ntpd_flags in rc.conf as you would for any other service/daemon and accidentally removed the -p flag in doing so. So this change was NOT a regression, it was in fact the fix for PR 199127. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230561-20181-QPhX3iwlHA>