Date: Tue, 6 Dec 2005 18:09:30 +0300 From: Solar Designer <solar@...nwall.com> To: owl-users@...ts.openwall.com Subject: Re: openntpd: dispatch_imsg in main: pipe closed On Tue, Dec 06, 2005 at 11:15:04AM +0300, Maxim Timofeyev wrote: > Hmm. I got a bit confused with its behavior. I've been using OpenNTPD > for quite a while, but I would never encounter such behaviour. > First, it used to log it's time sync actions: > > Nov 24 14:35:42 www ntpd: adjusting local clock by -192.952421s > Nov 24 14:40:03 www ntpd: adjusting local clock by -192.819198s > It doesn't any more now. This is the documented behavior. It would only log time adjustments larger than 128ms. > It would also never write such messages: > Dec 6 10:25:22 www ntpd: dispatch_imsg in main: pipe closed > Dec 6 10:25:22 www ntpd: Terminating Well, I don't know why not. Maybe you were using an older version. > Moreover, > it launches and works ok, but the following log string is confusing: > Dec 6 10:25:22 www ntpd: dispatch_imsg in main: pipe closed > I believe that the termination notification string would be enough. Yes, I agree that this is confusing. It's a side effect of privsep. -- Alexander Peslyak <solar at openwall.com> GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598 http://www.openwall.com - bringing security into open computing environments Was I helpful? Please give your feedback here: http://rate.affero.net/solar
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.