Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 5 Dec 2005 19:43:39 +0300
From: Solar Designer <>
Subject: Re: openntpd: dispatch_imsg in main: pipe closed

On Mon, Dec 05, 2005 at 03:46:49PM +0300, Maxim Timofeyev wrote:
> It is a bug report.
> ntpd started and terminating.

This is still not clear enough.  Did it terminate immediately after
being started?  If not, then when did it terminate?  Are you sure this
was not intentional (not an action of a script, etc)?  Why did you
demonstrate that you have two other ntpd processes running, what was
this meant to say?  Please don't be so cryptic.

Obviously, we can't reproduce the problem from your report.  We didn't
even know what the problem you were trying to report is, and we have
the Owl-current package of OpenNTPD in use on many systems with no

> > On Fri, Dec 02, 2005 at 06:13:12PM +0300, Maxim Timofeyev wrote:
> >> # rpm -q openntpd
> >> openntpd-3.7p1-owl2
> >>
> >> # grep ntpd /var/log/messages | tail
> >> Dec  2 17:45:12 tma ntpd[30527]: dispatch_imsg in main: pipe closed
> >> Dec  2 17:45:12 tma ntpd[30527]: Terminating
> >>
> >> # ps ax | grep ntpd | grep -v grep
> >> 19584 pts/3    S      0:00 /usr/sbin/ntpd -s
> >> 19591 ?        Ss     0:00 /usr/sbin/ntpd -s

Alexander Peslyak <solar at>
GPG key ID: B35D3598  fp: 6429 0D7E F130 C13E C929  6447 73C3 A290 B35D 3598 - bringing security into open computing environments

Was I helpful?  Please give your feedback here:

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.