From: Magali BERNARD (Magali.Bernard@univ-st-etienne.fr)
Date: Thu Nov 28 2002 - 09:00:35 EST
Thanks to:
Michael Polnick <polnick@pdv-sachsen.net>
"Gergen, Peter" <petergergen@kpmg.com.au>
Michael explains what I misunderstood in man pages
polnick@pdv-sachsen.net said:
> if you use sysconfigdb -u you REPLACE the whole vm sysconfigtab
> entry with your new vm entry. If it doesn't contain the swap device,
> you lost the swap.
> I think you mean -m (merge) to merely change the modified parameter.
and also:
> The vm-swap-eager is old-style and the vm_swap_eager is new-style both
> are recognized (currently).
petergergen@kpmg.com.au said:
> It is easiest to just edit the /etc/sysconfigtab file and change the
> line vm_swap_eager = 1 to vm_swap_eager = 0 and the reboot
but you can read at the top of /etc/sysconfigtab:
#
# The supported method of changing the information in this
# file (sysconfigtab) is by using the sysconfigdb command.
#
Original message:
> I have an XP1000 with Tru64Unix 5.1, with default swap mode set to
> eager (or immediate). I want to set it to lazy (or deferred) mode.
> From the man pages I have understood the following:
> - Make a swap.stanza file: vm:
> vm_swap_eager = 1
> - sysconfigdb -u -f swap.stanza vm - Reboot
> I was surprised to get the message "vm_swap_init: warning UNSPECIFIED
> swap device not found" "swapon -s" shows no more allocated space.
> "sysconfig -q vm" gives effectively "swapdevice = UNSPECIFIED" (and
> "vm_swap_eager = 0")
> Finally I had to add in my swap.stanza file:
> swapdevice = /dev/disk/dsk1b
> an reboot was ok.
> Also, before changing swap mode, /etc/sysconfigtab contained
> "vm-swap-eager=1" instead of "vm_swap_eager=1"...
> Did I miss something ?
-- _________________________________________________________________ Magali BERNARD - CRITeR - Université Jean Monnet de Saint-Etienne 23 rue du Dr Paul Michelon - 42023 St-Etienne Cedex 2 - FRANCE Tel: 04.77.48.50.62
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:00 EDT