In the last episode (Mar 13), Kevin Kinsey said:
> ntpd won't continue running on my "stratum 2" server (making our other
> systems a tad untrustworthy "as time goes by").
>
> $ uname -a
> FreeBSD ezekiel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #5: Sat Jan 20
> 16:41:42 CST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
>
> using ktrace and kdump I get this prior to exit:
>
> 12195 ntpd NAMI "/var/run/logpriv"
> 12195 ntpd RET connect 0
> 12195 ntpd CALL sendto(0x4,0xbfbfdd50,0x3e,0,0,0)
> 12195 ntpd GIO fd 4 wrote 62 bytes
> "<13>Mar 13 13:32:06 ntpd: logging to file /home/kadmin/ntp.log"
> 12195 ntpd RET sendto 62/0x3e
> 12195 ntpd CALL clock_gettime(0,0xbfbfeb08)
> 12195 ntpd RET clock_gettime 0
> 12195 ntpd CALL sigaction(0x1,0xbfbfeac0,0xbfbfeae0)
> 12195 ntpd RET sigaction 0
> 12195 ntpd CALL fork
> 12195 ntpd RET fork 12196/0x2fa4
> 12195 ntpd CALL exit(0)
It seems you're missing the -i flag to ktrace, which means you aren't
tracing the child of this fork operation. This ktrace output looks a
lot like the code in ntpd.c:ntpdmain(), in which ntpd forks, the parent
immediately exits, and the child continues.
--
Dan Nelson
[EMAIL PROTECTED]
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
