home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!enterpoop.mit.edu!cambridge-news.cygnus.com!athena.mit.edu!eichin
- From: eichin@athena.mit.edu (Mark Eichin)
- Newsgroups: comp.protocols.time.ntp
- Subject: Re: Ntpdate Xntpdc Xntpd Troubles
- Date: 22 Jan 1993 18:36:03 GMT
- Organization: Massachusetts Institute of Technology
- Lines: 13
- Distribution: inet
- Message-ID: <EICHIN.93Jan22133406@tweedledumber.mit.edu>
- References: <1993Jan18.114250.1@cudnvr.denver.colorado.edu>
- <2B5B1D41.6033@news.service.uci.edu> <1993Jan19.180901.28425@sura.net>
- NNTP-Posting-Host: tweedledumber.cygnus.com
- In-reply-to: jmalcolm@sura.net's message of 19 Jan 93 18:09:01 GMT
-
- >> I think this one has been around for a while. (Fixed in Solaris 2?)
- Not in 2.0, nor in 2.1:
- ntp 123/tcp # Network Time Protocol
-
- Frankly, I haven't found *anything* that was "fixed" in Solaris 2.0 --
- unless you mean what they mean when they say a cat is "fixed"...
- _Mark_ <eichin@athena.mit.edu>
- MIT Student Information Processing Board
- Cygnus Support <eichin@cygnus.com>
- ps. 2.1 may be better. I'll find out soon.
- pps. Has anyone ported xntp3 to Solaris? I'm trying quick pass through
- adding header files, switching b* to mem*, and using sigprocmask, but
- if you've done it already, I'd like to hear about it...
-