Bug 10617 - NTP client/query programs could be packaged separately
NTP client/query programs could be packaged separately
Product: Red Hat Linux
Classification: Retired
Component: xntp3 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2000-04-06 09:37 EDT by Nigel Metheringham
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-16 09:25:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nigel Metheringham 2000-04-06 09:37:22 EDT
xntp3 comes as one big blob.
I would think it preferable for the client progs - especially
ntpdate - to be packaged in a separate rpm rather than as
a big bundle.
Comment 1 Daniel Roesen 2000-04-14 19:42:59 EDT
I support this. Most times you need just xntpd and ntpq.
Comment 2 Pekka Savola 2000-04-16 09:22:59 EDT
This "big" bundle is less than 1 megabyte altogether.  IMO better reasons
than space should be found for this separation.

I don't really see need to package e.g. only ntpdate in a client package myself,
since ntpd is so much better for _keeping_ the synchronization, not just fixing
it once a few weeks-months when the box is booted.
Comment 3 Daniel Roesen 2000-04-16 09:25:59 EDT
ACK. ntpdate is (AFAIK) less exact than xntpd. But there is a need for
ntpdate for dial-on-demand people. with manual dialing xntpd alone is
great (using it for years now to keep my home clocks in sync).
Comment 4 Jeff Johnson 2000-07-13 22:54:08 EDT
I think that splitting xntp3/ntp into smaller pieces would just make it more
difficult to use.

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