Ray wrote: "Would it be something as simple as a response time test to decide which swap algorithm to use? In a perfect world I'd like to simply give Linux one chunk of v-disk, and let the OS figure out how to use it. As server apps grow it gets riskier to mess with the fstab to add more v-disks, and we also end up with a bunch of non-standard disk layouts unless we plan well in advance."
What I do is to just activate the swap in /etc/init.d/boot.local . It looks something like: /sbin/mkswap /dev/dasd/ff00/part1 /sbin/mkswap /dev/dasd/ff01/part1 /sbin/mkswap /dev/dasd/ff02/part1 /sbin/mkswap /dev/dasd/ff03/part1 /sbin/swapon /dev/dasd/ff00/part1 -p 4 /sbin/swapon /dev/dasd/ff01/part1 -p 3 /sbin/swapon /dev/dasd/ff02/part1 -p 2 /sbin/swapon /dev/dasd/ff03/part1 -p 1 Then I can control in the VM directory the sizes and if the disk(s) exist. The mkswap runs really really fast and no messing with /etc/fstab (or even logging in to linux to change it). Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
