Summary: | /etc/init.d/ntpd fails to clear .pid file after ntpd startup failure | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | J Sacksteder <jwsacksteder> |
Component: | New packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 39919 | ||
Bug Blocks: |
Description
J Sacksteder
2004-02-26 07:31:35 UTC
Why is ntpd failing to start...what is the error ? Maybe if we checked for an error code we could do something about it. The problem you are reporting isn't really a ntpd bug, but also happens with bind, mysql, apache...if there is an error. this may be related to a problem I am having with starting ntpd or ntp-client init scripts. I get a chown error that is being caused by this line in the init scripts. chown ntp:ntp /var/run/ntpd.pid The ebuild never created a ntp user or group, so this line just fails. i dont know how you emerged ntp but every ebuild since 4.1.2 has added the ntp user/group oh, yah, you are right. the way that the later ebuilds to the init script works... start() { checkconfig || return $? ebegin "Starting ntpd" touch /var/run/ntpd.pid chown ntp:ntp /var/run/ntpd.pid /usr/bin/ntpd -p /var/run/ntpd.pid ${NTPD_OPTS} eend $? "Failed to start ntpd" } stop() { ebegin "Stopping ntpd" if [ -e /var/run/ntpd.pid ] ; then kill `cat /var/run/ntpd.pid` rm -f /var/run/ntpd.pid fi eend $? "Failed to stop ntpd" } since there are major bugs open on the later builds...possibly this init should be backported, in addition to the ntp group -> ntp:ntp in the conf.d/ntpd fix. everything is as it should be |