home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.sysmgt:423 comp.os.vms:19924
- Newsgroups: vmsnet.sysmgt,comp.os.vms
- Path: sparky!uunet!munnari.oz.au!uniwa!cujo!cc.curtin.edu.au!zrepachol
- From: zrepachol@cc.curtin.edu.au
- Subject: Re: Pagefile size and distribution guidelines desired
- Message-ID: <1992Dec27.215149.1@cc.curtin.edu.au>
- Lines: 17
- Sender: news@cujo.curtin.edu.au (News Manager)
- Organization: Curtin University of Technology
- References: <1992Dec21.092049.1074@beckman.com> <1h6c06INN9ks@gap.caltech.edu>
- Date: Sun, 27 Dec 1992 12:51:49 GMT
-
- In article <1h6c06INN9ks@gap.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
- > In article <1992Dec21.092049.1074@beckman.com>, dsroberts@beckman.com writes:
- ...
- > No. For each system, you should have at most one page file on each disk.
- > Optimally, you should only have page files on local disks. Once you've got
- > page files on non-local disks, optimal placement is *HIGHLY* dependent on the
- > characteristics of your particular cluster.
-
- A thing I do is name them [000000]AAAPAGE.SYSn and AAASWAP.SYSn. This means backup
- and friends copy them first, Smack in the middle of the drive! No further think-
- ing required.
-
- An 'emergency' file on a remote system is a good sanity check. Set it all up
- so the remote files are 'never' used, if they are, panic.
-
- ~Paul
-
-