11-18-2011
Quote:
when More Physical memory being used , automatically system should start using the swap configured in the system , in our case it is configured 61440 Mb , why the system is not utilizing the swap ?
It will... if the system needs it...
I think what is not clear to you is how the Virtual System works:
In HPUX when you load a process, it will go to the VM first (that means swap device) to allocate the space needed, then loaded in memory - That space used is marked as RESERVED. Once all processes are running rather than waiste the unused memory it will be used as cache or SWAP (for it is far more faster the disk...). It is doing exactly that on your system: Your memory usage is almost maximum
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there any problems of binaries compatibility between HPUX 10.20 et 11 ? (2 Replies)
Discussion started by: Olivier
2 Replies
2. UNIX for Dummies Questions & Answers
When i re-updated my system i set my swap at 500 MB. I have 256 in ram and have never even gone into the 250 mb of swap that i had originally configured. How do I reduce the swap? (3 Replies)
Discussion started by: macdonto
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am a SAP Basis admin recentely been asked to administer a HPUX server. Could someone recommend some good study material to learn with the Sap
prespective.
-carry (1 Reply)
Discussion started by: carryclare
1 Replies
4. UNIX for Dummies Questions & Answers
Is it really so that if swap will be located in the begining of hard drive, than it will work faster? (1 Reply)
Discussion started by: Ty3
1 Replies
5. Solaris
Hello and thanks in advance.
I have a Sun box with raid 1 on the O/S disks using solaris svm.
I want to unmirror my swap partition, and add the slice on the second disk as an additional swap device. This would give me twice as much swap space.
I have been warned not to do this by some... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
6. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
7. Red Hat
free -m : 1023 total swap space
created default partition /dev/sdb1 50M using fdisk. i did write the changes.
#mkswap /dev/sdb1
#swapon /dev/sdb1
free -m : 1078 total swap space
this shows that the swap is on
Question : i did not change the type LINUX SWAP (82) in fdisk.
so why is... (5 Replies)
Discussion started by: dplinux
5 Replies
8. HP-UX
Hi
I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system:
- I would like to know when does the memory swap space spill over to the device swap space?
- And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Discussion started by: lamoul
6 Replies
9. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
10. Solaris
Hi Solaris Folks :),
I need to calculate the swap usage on solaris server, please let me understand the output of below swap -s and swap -l commands.
$swap -s
total: 1774912k bytes allocated + 240616k reserved = 2015528k used, 14542512k available
$swap -l
swapfile dev swaplo... (6 Replies)
Discussion started by: seenuvasan1985
6 Replies
LEARN ABOUT CENTOS
systemd.swap
SYSTEMD.SWAP(5) systemd.swap SYSTEMD.SWAP(5)
NAME
systemd.swap - Swap unit configuration
SYNOPSIS
swap.swap
DESCRIPTION
A unit configuration file whose name ends in ".swap" encodes information about a swap device or file for memory paging controlled and
supervised by systemd.
This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit
configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The swap specific
configuration options are configured in the [Swap] section.
Additional options are listed in systemd.exec(5), which define the execution environment the swapon(8) binary is executed in, and in
systemd.kill(5), which define the way the processes are terminated, and in systemd.resource-control(5), which configure resource control
settings for the processes of the service.
Swap units must be named after the devices or files they control. Example: the swap device /dev/sda5 must be configured in a unit file
dev-sda5.swap. For details about the escaping logic used to convert a file system path to a unit name, see systemd.unit(5).
All swap units automatically get the appropriate dependencies on the devices or on the mount points of the files they are activated from.
Swap units with DefaultDependencies= enabled implicitly acquire a conflicting dependency to umount.target so that they are deactivated at
shutdown.
FSTAB
Swap units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). Swaps listed in /etc/fstab will be
converted into native units dynamically at boot and when the configuration of the system manager is reloaded. See systemd-fstab-
generator(8) for details about the conversion.
If a swap device or file is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
Unless the noauto option is set for them all swap units configured in /etc/fstab are also added as requirements to swap.target, so that
they are waited for and activated during boot.
OPTIONS
Swap files must include a [Swap] section, which carries information about the swap device it supervises. A number of options that may be
used in this section are shared with other unit types. These options are documented in systemd.exec(5) and systemd.kill(5). The options
specific to the [Swap] section of swap units are the following:
What=
Takes an absolute path of a device node or file to use for paging. See swapon(8) for details. If this refers to a device node, a
dependency on the respective device unit is automatically created. (See systemd.device(5) for more information.) If this refers to a
file, a dependency on the respective mount unit is automatically created. (See systemd.mount(5) for more information.) This option is
mandatory.
Priority=
Swap priority to use when activating the swap device or file. This takes an integer. This setting is optional.
TimeoutSec=
Configures the time to wait for the swapon command to finish. If a command does not exit within the configured time, the swap will be
considered failed and be shut down again. All commands still running will be terminated forcibly via SIGTERM, and after another delay
of this time with SIGKILL. (See KillMode= in systemd.kill(5).) Takes a unit-less value in seconds, or a time span value such as "5min
20s". Pass 0 to disable the timeout logic. Defaults to TimeoutStartSec= in manager configuration file.
Check systemd.exec(5) and systemd.kill(5) for more settings.
SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), systemd.exec(5), systemd.kill(5), systemd.resource-control(5), systemd.device(5),
systemd.mount(5), swapon(8), systemd-fstab-generator(8), systemd.directives(7)
systemd 208 SYSTEMD.SWAP(5)