Path: utzoo!attcan!uunet!wuarchive!usc!apple!bionet!agate!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Time/Clock
Message-ID: <986@toaster.SFSU.EDU>
Date: 25 Oct 90 20:07:35 GMT
References: <1990Oct25.145031.28374@msuinfo.cl.msu.edu> <1990Oct25.153836.1922@msuinfo.cl.msu.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 24

In article <1990Oct25.145031.28374@msuinfo.cl.msu.edu>
	reid@cpswh.cps.msu.edu (Dr Richard J. Reid) writes:
>Through "Preferences", at least, individual students on
>our NeXT's reset and vary things that invalidate the
>system accounting features as given by:  ac -p -d.

In article <1990Oct25.153836.1922@msuinfo.cl.msu.edu>
	chouw@buster.cps.msu.edu (Wen Hwa Chou) writes:
>Is there any way to prevent the user from changing the Time/Clock on
>the old Cube?

One of the first things you should have done when installing your
1.0/1.0a systems was
	# chmod 755 /NextApps/Preferences

This has been mentioned repeatedly in the past on comp.sys.next,
but for some reason isn't adequately covered in NextAnswers
(perhaps someone needs to revise preferences.479?)

If you're Internet-connected, get a copy of NTP (Network Time
Protocol) and use that to set your clocks.  Messed up accounting
is the least of your problems.

					-=EPS=-