Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!sceard!mrm
From: mrm@sceard.Sceard.COM (M.R.Murphy)
Newsgroups: comp.unix.xenix.sco
Subject: Re: clock and echo problems
Message-ID: <1991Jan3.061037.26249@sceard.Sceard.COM>
Date: 3 Jan 91 06:10:37 GMT
References: <1990Dec31.012532.17992@sceard.Sceard.COM> <1991Jan1.234705.4226@cjbsys.bdb.com>
Reply-To: mrm@Sceard.COM (M.R.Murphy)
Organization: Sceard Systems, Inc.  San Marcos, CA  92069
Lines: 48

In article <1991Jan1.234705.4226@cjbsys.bdb.com> cliffb@cjbsys.bdb.com (cliff bedore) writes:
>In article <1990Dec31.012532.17992@sceard.Sceard.COM> mrm@Sceard.COM (M.R.Murphy) writes:
>>This is probably just a case of RTFM, but here goes:
>>
>>Compaq Deskpro 386, Xenix 2.3.2, and the system clock loses an hour or
>>two a day. CMOS clock is ok. This seems like it probably shouldn't happen :-)
>>
>>Anybody notice that under csh,
>> % echo "--"
>>works, but under /bin/sh,
>> $ echo "--"
>>doesn't work?
>>Any good reason for such behavior from /bin/echo ?
>>-- 
>>Mike Murphy  mrm@Sceard.COM  ucsd!sceard!mrm  +1 619 598 5874
>
>Yes.  in csh there is a built-in echo which gives the first result and since sh
>doesn't have a bulit-in /bin/echo takes over.  (I went crazy on our Ultrix
>system til I figured this out.)     
>
>Oops, I just noticed that sh has a bulit-in echo also but it seems to work just
>like /bin/echo
>
>anyhow that is the difference.
>
>Cliff

I'm sorry I wasn't clear in my original posting regarding /bin/echo. I know
that csh has echo builtin (as does ksh with echo aliased to print - :-), and
I know that /bin/sh uses /bin/echo rather than a builtin echo. What I wanna know
is how come
 /bin/echo --
doesn't work. Echo -- works with the builtin echo of csh and ksh. BTW,
/bin/echo -- works on all the non-Xenix implementations of Unix(tm) that I
bothered to seek out. Maybe it's because the Xenix /bin/echo uses getopt,
but it really shouldn't :-)

The clock problem is a real pain. I know about resetting the clock from the
cmos clock every so often with something run from cron, but that seems so gross,
so kludged, so pragmatic, and so troubled by the possibility of rerunning
something that should only be run once a day or once an hour, that I hate to
do it that way. I'm familiar with the use of locks and one-shots to avoid
multiple invocations, but I'd still rather have some nice, easy way to tweak
things to make the software clock more accurate.

Suggestions? Useful suggestions? Anatomically possible suggestions?
-- 
Mike Murphy  mrm@Sceard.COM  ucsd!sceard!mrm  +1 619 598 5874