Bug#348412: chronyc not LP64 compliant

2006-01-18 Thread Taral
On Wed, Jan 18, 2006 at 07:40:40PM -0600, John Hasler wrote: > > chronyc outputs this for "chronyc sources" on amd64: > > > ^+ mainframe.cynacom.com 39186 +4294966078us[+4294966078us] > > +/- 97ms > > Does chronyd work? Do any other chronyc commands produce similarly wonky > o

Bug#348412: chronyc not LP64 compliant

2006-01-18 Thread John Hasler
> chronyc outputs this for "chronyc sources" on amd64: > ^+ mainframe.cynacom.com 39186 +4294966078us[+4294966078us] > +/- 97ms Does chronyd work? Do any other chronyc commands produce similarly wonky output? -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSC

Bug#348412: chronyc not LP64 compliant

2006-01-16 Thread John Hasler
I've forwarded your report upstream, but I will also work on the problem myself when I get time. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#348412: chronyc not LP64 compliant

2006-01-16 Thread John Hasler
Thank you for your report. -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#348412: chronyc not LP64 compliant

2006-01-16 Thread JP Sugarbroad
Package: chrony Version: 1.21-2 Severity: important chronyc outputs this for "chronyc sources" on amd64: ^+ mainframe.cynacom.com 39186 +4294966078us[+4294966078us] +/- 97ms That funny number is due to the pervasive use of "long" for 32-bit integers in the code. I don't know w