home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!ux1.cso.uiuc.edu!lemson
- From: lemson@ux1.cso.uiuc.edu (David Lemson)
- Subject: Re: dwrites on client machines
- Message-ID: <BzqxBF.Mo8@ux1.cso.uiuc.edu>
- Organization: University of Illinois at Urbana
- References: <1992Dec23.013458.2160@metrosoft.com>
- Date: Thu, 24 Dec 1992 04:18:37 GMT
- Lines: 31
-
- gvh@metrosoft.com (Gordon Van Huizen) writes:
-
- >How do people usually handle dwrites for the
- >loginwindow, etc. on client machines? If you mount all of
- >root from a server, don't you get that server's defaults
- >when you do dreads on the client? This seems less than
- >desirable.
-
- The dwrite database (I think accurately called the 'defaults
- database') is actually stored in the ~/.NeXT directory. That goes
- for ~root as well. So, it depends on where home directories come
- from, not /private/etc or anything like that.
- Barring netbooting, most people have client machines using their own
- / partition, plus more directories for applications, home
- directories, etc. With netbooting, yes, you would use the defaults
- for root on the server machine probably. (With the standard netboot
- setup)
- Check out DefaultMgr by Drew Davidson, which makes this task a lot
- easier for system administrators. The new version that handles
- netinfo is commercial, published by CuillaMartin. I never saw it,
- but from Drew's descriptions while he was designing it, it seems
- like it might solve all of our problems.
-
- One way to set everyone's dwrite is a su command that executes a
- command as each user each night. Many people do this to turn off
- PublicWindowServer for each user.
- --
- David Lemson (217) 244-1205
- University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin
- Internet : lemson@uiuc.edu UUCP :...!uiucuxc!uiucux1!lemson
- NeXTMail & MIME accepted BITNET : LEMSON@UIUCVMD
-