gregs@well.sf.ca.us (Greg Strockbine) (05/30/90)
all of a sudden I am getting this message when I try to do an sccs get: Clock may be set wrong! (Co11) The administrators have been monkeying around with things, but I still can't figure this error message out or how to make it go away. Any ideas? thanx in advance, greg strockbine, dataproducts
cpcahil@virtech.uucp (Conor P. Cahill) (05/30/90)
In article <18210@well.sf.ca.us> gregs@well.sf.ca.us (Greg Strockbine) writes: >all of a sudden I am getting this message when I try >to do an sccs get: > Clock may be set wrong! (Co11) >The administrators have been monkeying around with things, >but I still can't figure this error message out or how to >make it go away. One of the nice things about SCCS is the use of error codes with error messages. For example, your message: Clock may be set wrong! (Co11) ^^^^^^ typo here? includes the error number co11. The "help" utility gives you additional information using this code. For the co11 code, the help utility outputs: co11: "Clock may be set wrong!" The time of day may be set wrong. Check the current time with the "date" command. If it is wrong, contact your local UNIX support group immediately! (This message is produced whenever the difference between the current date and the creation date of the newest delta in the SCCS file is greater than one year.) -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170
gwyn@smoke.BRL.MIL (Doug Gwyn) (05/30/90)
In article <18210@well.sf.ca.us> gregs@well.sf.ca.us (Greg Strockbine) writes: >all of a sudden I am getting this message when I try >to do an sccs get: > Clock may be set wrong! (Co11) >The administrators have been monkeying around with things, >but I still can't figure this error message out or how to >make it go away. This message merely means that the last change was made to the archive longer ago than something like 6 months (or maybe a year, it's not important what the exact threshold is). The assumption is that for a project undergoing active development, it is more probable that the current system clock is set incorrectly than that an archive has remained unchanged for that long. This message is harmless, but if you want to fix it you could either remove this feature from "get" or you could check in a fresh (no-op) update to the archive.
meissner@osf.org (Michael Meissner) (05/30/90)
In article <18210@well.sf.ca.us> gregs@well.sf.ca.us (Greg Strockbine) writes: | all of a sudden I am getting this message when I try | to do an sccs get: | Clock may be set wrong! (Co11) | The administrators have been monkeying around with things, | but I still can't figure this error message out or how to | make it go away. One cause of this, is if your sccs files are stored on an NFS disk, and there is clock skew between your system, and the system where the files are stored. If for example, the file server's clock is 10 minutes ahead of your workstation's, you won't be able to use 'get' on a file for 10 minutes after doing an updated, such as a delta. Programs like ntp or timed (better) can synchronize clocks across systems, providing your system has the appropriate BSD system calls. -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA Catproof is an oxymoron, Childproof is nearly so
ndjc@ccicpg.UUCP (Nick Crossley) (05/31/90)
In article <1990May30.013209.3786@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes: > co11: "Clock may be set wrong!" > The time of day may be set wrong. > Check the current time with the "date" command. > If it is wrong, contact your local UNIX support group immediately! > (This message is produced whenever the difference between > the current date and the creation date of the newest delta in > the SCCS file is greater than one year.) I have always thought this check is silly. There *ARE* programs which do not have to be modified every year! And why is sccs trying to check the system clock? If sccs does it, why not all utilities? $ cat /1988/accounts/summary cat: warning: clock may be set wrong! ... -- <<< standard disclaimers >>> Nick Crossley, ICL NA, 9801 Muirlands, Irvine, CA 92718-2521, USA 714-458-7282 uunet!ccicpg!ndjc / ndjc@ccicpg.UUCP