home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.questions
- Path: sparky!uunet!unx1!dean
- From: dean@unix1.realdec.com (Dean Banfield)
- Subject: timed daemon questions
- Organization: Real Decisions Corporation
- Distribution: comp
- Date: Tue, 5 Jan 1993 03:13:31 GMT
- Message-ID: <DEAN.93Jan4221331@unix1.realdec.com>
- Sender: dean@rdcalr.realdec.com (Dean Banfield)
- Lines: 34
-
- Hi,
-
- I am trying to support an Ethernet-wide time synchronizer, and our SCO UNIX
- (3.2.2) offers 'timed' for this. When fired up, with the tracing log
- turned on, I notice that requests for the time generate 'LOOP' conditions
- to IP address 127.0.0.1 rather than supplying the time back to the requestor.
-
- My two examples are the Trumpet product (DOS-based newsreader), and the
- FTP software settime (?) module, which is part of its PC/TCP product. It
- is obvious that both of these products make contact with the timed daemon,
- but they both coincidentally make the same calling error, or my timed program
- is misconfigured.
-
- In addition, what would it take for a Novell server to participate in a
- netwide time synch, which included the UNIX platform. I'm aware that
- Novell offers its own time synch mechanism for DOS workstations. Is there
- any (inexpensive) way to have Novell synch with UNIX (TCP/IP)? I can 'ping'
- the Novell platform without buying anything beyond Netware 3.11. Hoping
- that time can be synched as cheaply.
-
- Thanks for any info in advance.
-
- Dean Banfield
- --
- ===============================================================
- Dean Banfield
- Real Decisions Corporation Voice: 203.656.1500
- 22 Thorndal Circle FAX: 203.656.1659
- Darien, CT USA 06820 Email: dean@rdcalr.realdec.com
- --
- ===============================================================
- Dean Banfield
- Real Decisions Corporation Voice: 203.656.1500
- 22 Thorndal Circle FAX: 203.656.1659
-