Xref: utzoo comp.sources.d:6348 unix-pc.general:7345
Path: utzoo!utgpu!watserv1!watmath!att!rutgers!njin!uupsi!vmp!sonyd1.Broadcast.Sony.COM!blilly.UUCP!balilly.UUCP!bruce
From: bruce@balilly.UUCP (Bruce Lilly)
Newsgroups: comp.sources.d,unix-pc.general
Subject: Re: Naval Observatory time program - utc
Message-ID: <1991Jan19.011100.18405@blilly.UUCP>
Date: 19 Jan 91 01:11:00 GMT
References: <1991Jan16.230534.27011@esleng.uucp>
Sender: news@blilly.UUCP (News Administrator)
Organization: Bruce Lilly, Flushing, NY
Lines: 24

In article <1991Jan16.230534.27011@esleng.uucp> dag@esleng.uucp (David A. Gilmour) writes:
>I recently received a program called utc from the net that allows a Unix
>machine to automatically call the Naval Observatory to obtain the current
>time and update the system clock.
>
>The instructions suggest performing a cu command to connect with the
>observatory and piping the output into utc.
>
>However, when I do this, one of the cu processes stays alive and has to
>be killed manually after utc completes.  The instructions say:
>
>"You may have to fix your cu to die properly when it receives a SIGPIPE."
>
>Can anyone tell my how I can fix cu?

I use something like:
	(sleep 80 ; echo ~.) | cu 12026530351 | utc -sp

This sends a "~." to cu after 80 seconds, which causes cu to close the
connection.  You may need to change the sleep duration to suit your
modem and local phone exchange delays.

--
	Bruce Lilly		blilly!balilly!bruce@sonyd1.Broadcast.Sony.COM