Posted by 삐꾸강아쥐


Posted by 삐꾸강아쥐




,
resource monitor



,
utilty




Posted by 삐꾸강아쥐




,
gfs



,
linux



,
locktable



,
modify



,
proto




Posted by 삐꾸강아쥐




,
linux



,
network



,
red hat




Every interval (default: 10 seconds) information is shown
about the resource occupation on system level (cpu, memory, disks and
network layers),
followed by a list of processes which have been active during the last
interval (note that all processes that were unchanged during the last
interval are not
shown, unless the key 'a' has been pressed). If the list of active
processes does not entirely fit on the screen, only the top of the list
is shown (sorted in
order of activity).
The intervals are repeated till the number of samples (specified
as command argument) is reached, or till the key 'q' is pressed in
interactive mode.
When atop is started, it checks whether the standard output channel is connected to a screen, or to a file/pipe. In the first case it produces screen control codes (via the curses library) and behaves interactively; in the second case it produces flat ASCII-output.
In interactive mode, the output of atop can be controlled
by pressing particular keys. However it is also possible to specify such
key as flag
on the command line. In the latter case atop will switch to the
indicated mode on beforehand; this mode can be modified again
interactively. Specifying
such key as flag is especially useful when running atop with
output to a pipe or file (non-interactively). The flags used are the
same as the keys which
can be pressed in interactive mode (see section INTERACTIVE COMMANDS).
Additional flags are available to support storage of atop-data in raw
format (see section RAW DATA STORAGE).

Posted by 삐꾸강아쥐




,
linux



,
process monitor




If add several hundred GB of RAM to a system, do really need several hundred GB of swap space ?
Red Hat Enterprise Linux 5
Currently Red Hat recommends a linear increase to the amount of swap space on a system as the amount of RAM increases. Specifically that swap space on a system be twice the amount of RAM when the system has up to 2GB and the amount of RAM plus 2GB when the system has more than 2GB of RAM. This is pretty much the same recommendation as upstream so the reasoning behind it is, the larger the system, the larger memory workload that system will likely encounter.
This no longer makes sense as memory sizes have increased up into the hundreds of GBs range.
The reality is the amount of swap space a system needs is not really a function of the amount of RAM it has but rather the memory workload that is running on that system. A Red Hat Enterprise Linux 5 system will run just fine with no swap space at all as long as the sum of anonymous memory and system V shared memory is less than about 3/4 the amount of RAM. In this case the system will simply lock the anonymous and system V shared memory into RAM and use the remaining RAM for caching file system data so when memory is exhausted the kernel only reclaims pagecache memory.
Considering that
1) At installation time when configuring the swap space there is no easy way to predetermine the memory a workload will require, and
2) The more RAM a system has the less swap space it typically needs, a better swap space requirements rule for Red Hat Enterprise Linux 5 is:
Systems with 4GB of ram or less require a minimum of 2GB of swap space
Systems with 4GB to 16GB of ram require a minimum of 4GB of swap space
Systems with 16GB to 64GB of ram require a minimum of 8GB of swap space
Systems with 64GB to 256GB of ram require a minimum of 16GB of swap space
Posted by 삐꾸강아쥐




,
memory



,
red hat



,
RHEL



,
swap




link 1 : http://isc.sans.edu/diary.html?storyid=1538&isc=90f7e0cf745ef88d67ec
link 2 : http://marc.info/?l=bind9-users&m=108290465703725&w=2
Posted by 삐꾸강아쥐




,
dispatch



,
linux



,
named



,
shutting down



,
tcp




Posted by 삐꾸강아쥐




,
pid of cpu



,
pid of disk



,
pid of memory



,
pidstat



,
sysstat




Posted by 삐꾸강아쥐




,
gethostip



,
hostid



,
linux




리눅스는 device-mapper 의 multipath(mpath0,mpath1) 나 lvm( /dev/vg00/lv00) 에
대해서 실제 Devices 는 dm-X 장치를 사용한다.
하지만 실제 어떤 장치가 dm-X 에 맵핑 되어 있는지는 알기가 쉽지 않다.
ex)
mpath0 -> dm-0
/dev/vg00/lv00 -> dm-1
확인 방법은 아래를 참고 하기 바란다.
# dm-0 에 연결되어 있는 실제 Devices 의 내역
/sys/block/dm-0/slaves
# ls -al
total 0
drwxr-xr-x 2 root root 0 May 12 09:29 .
drwxr-xr-x 4 root root 0 May 12 09:29 ..
lrwxrwxrwx 1 root root 0 May 12 09:29 sda5 -> ../../../block/sda/sda5
lrwxrwxrwx 1 root root 0 May 12 09:29 sdb5 -> ../../../block/sdb/sdb5
# pvs
PV VG Fmt Attr PSize PFree
/dev/sda5 VG0 lvm2 a- 900.41G 0
/dev/sdb5 VG0 lvm2 a- 900.41G 0
# dm-0 의 Major, minor 넘버
/sys/block/dm-0
# cat dev
253:0
# dmsetup 으로 확인하는 Major, minor 넘버
# dmsetup ls
VG0-data (253, 0)
]# dmsetup info
Name: VG0-data
State: ACTIVE
Read Ahead: 512
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 253, 0
Number of targets: 1
UUID: LVM-qAMVWfCgbM1GlkyJnpue3hj156CjTWXknlknh3KpTQUfToVgnfQRj3hyVysJrolL
# cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 104391 sda1
8 2 31455270 sda2
8 3 1052257 sda3
8 4 1 sda4
8 5 944148051 sda5
8 16 976762584 sdb
8 17 104391 sdb1
8 18 31455270 sdb2
8 19 1052257 sdb3
8 20 1 sdb4
8 21 944148051 sdb5
9 2 31455168 md2
9 1 1052160 md1
9 0 104320 md0
253 0 1888288768 dm-0
7 0 3467786 loop0
Posted by 삐꾸강아쥐




,
dm-0



,
dm-1



,
dm-X



,
linux



,
lvm




Posted by 삐꾸강아쥐




,
load average



,
top



,
uptime



,
w




| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |