| Summary: | ntp running multiple instances | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Mohammed Arafa <bugzilla> |
| Component: | ntp | Assignee: | Miroslav Lichvar <mlichvar> |
| Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.7 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-29 17:17:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Mohammed Arafa
2011-11-28 16:35:10 UTC
The ntpd process forks when it resolves names of the servers specified in ntp.conf to avoid blocking, so this is expected behavior. no no - i am not talking about forking while true do /etc/init.d/ntp start done _can go on forever!_ it apparently doesnt check to see if ntp service is started or if a pid file was created for the service. With what version of the ntp package is that? I don't see it with ntp-4.2.2p1-15.el5, /etc/init.d/ntp start is a no-op. |