owl-users - Re: openntpd: dispatch_imsg in main: pipe closed

Openwall Project		/home Owl JtR Pro crypt pam_passwdqc tcb phpass scanlogd popa3d msulogin / Linux BIND / advisories presentations / services donations / wordlists passwords / news community lists wiki CVSweb mirrors signatures
bringing security into open environments

Password Recovery Resources on the Net

[<prev] [next>] [<thread-prev] [thread-next>] [month] [year] [list]

Date: Sat, 3 Dec 2005 08:54:16 +0300
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: openntpd: dispatch_imsg in main: pipe closed

Maxim,

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

It is not clear what you mean by this.  Is this a bug report?  If so,
what's the bug?  From the log file entries, it is seen that you had
terminated ntpd (one of its processes complained about the other's
death, but that's fine).  From the process list, it is seen that you
have ntpd running again.

Actually, I think there are a couple of things we could improve.  We
could make the log file messages less confusing.  We could also have
_both_ ntpd processes detach from the tty.  None of this is specific to
Owl (those are properties of OpenNTPD), but, yes, we could patch this.

-- 
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