Bug 35797 - error in log message of xntp3
Summary: error in log message of xntp3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ntp
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-12 09:55 UTC by bareket
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-06-29 09:48:19 UTC
Embargoed:


Attachments (Terms of Use)
patch solving the bug (640 bytes, patch)
2001-05-11 11:11 UTC, Harald Hoyer
no flags Details | Diff

Description bareket 2001-04-12 09:55:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Hi,
There is an incorrect counting of "fails" field (%m instead of a number) in the log message, when 
starting the xntp3, in the following line:
xntpd[31376]: bind() fd 10, family 2, port 123, addr e0000101, in_classd=1 flags=0 fails: %m
This happened when updating to the new rpm xntp3-5.93-15 in the Red-Hat Erreta.


Reproducible: Always
Steps to Reproduce:
1.rpm -Fvh xntp3-5.93-15
2./etc/rc.d/init.d/xntpd restart
3.look in the messages log to see the line: xntpd[31376]: bind() fd 10, family 2, port 123, addr 
e0000101, in_classd=1 flags=0 fails: %m
	

Actual Results:  i got the line "xntpd[31376]: bind() fd 10, family 2, port 123, addr e0000101, 
in_classd=1 flags=0 fails: %m" in the messages log. It contains incorrect number in th e"fails" 
field.

Expected Results:  There should have been a real number in the "fails" field of this message.

I'm using kernel 2.2.18 on i686

Comment 1 Harald Hoyer 2001-05-11 11:11:55 UTC
Created attachment 18128 [details]
patch solving the bug


Note You need to log in before you can comment on or make changes to this bug.