Сообщения simplepilot
LICQ
Сколько памяти должны кушать Иксы
18:28:57 up 58 min, 2 users, load average: 0.35, 0.48, 0.48 79 processes: 78 sleeping, 1 running, 0 zombie, 0 stopped CPU states: 21.5% user 6.4% system 0.0% nice 0.0% iowait 72.0% idle Mem: 190692k av, 186640k used, 4052k free, 0k shrd, 9272k buff 139660k actv, 0k in_d, 2972k in_c Swap: 385552k av, 55204k used, 330348k free 76024k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 1262 root 16 0 52792 24M 2716 S 9.5 13.0 6:34 0 X 2020 boss 15 0 22048 21M 9792 S 4.7 11.5 0:32 0 opera 2065 root 20 0 1048 1048 844 R 3.8 0.5 0:00 0 top 1 root 15 0 468 444 416 S 0.0 0.2 0:04 0 init 2 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 keventd 3 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kapmd 4 root 34 19 0 0 0 SWN 0.0 0.0 0:00 0 ksoftirqd_CPU 9 root 25 0 0 0 0 SW 0.0 0.0 0:00 0 bdflush 5 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kswapd 6 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/DMA 7 root 15 0 0 0 0 SW 0.0 0.0 0:03 0 kscand/Normal 8 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kscand/HighMe 10 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kupdated 11 root 25 0 0 0 0 SW 0.0 0.0 0:00 0 mdrecoveryd 15 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald 630 root 15 0 0 0 0 SW 0.0 0.0 0:00 0 kjournald 869 root 15 0 548 512 468 S 0.0 0.2 0:00 0 syslogd 873 root 15 0 412 360 356 S 0.0 0.1 0:00 0 klogd 891 rpc 15 0 516 488 440 S 0.0 0.2 0:00 0 portmap 911 rpcuser 25 0 628 552 552 S 0.0 0.2 0:00 0 rpc.statd 977 root 24 0 472 428 424 S 0.0 0.2 0:00 0 apmd 1014 root 25 0 724 488 484 S 0.0 0.2 0:00 0 sshd 1028 root 16 0 684 568 564 S 0.0 0.2 0:00 0 xinetd 1040 ntp 15 0 2392 2392 2152 S 0.0 1.2 0:00 0 ntpd 1060 root 15 0 884 344 228 S 0.0 0.1 0:00 0 sendmail 1069 smmsp 25 0 592 60 60 S 0.0 0.0 0:00 0 sendmail 1079 root 15 0 200 192 152 S 0.0 0.1 0:00 0 gpm 1088 root 15 0 208 192 144 S 0.0 0.1 0:00 0 crond 1099 root 15 0 900 572 428 S 0.0 0.2 0:00 0 cupsd 1186 xfs 16 0 4332 2708 372 S 0.0 1.4 0:11 0 xfs 1195 root 39 19 108 32 28 S N 0.0 0.0 0:00 0 anacron 1204 daemon 15 0 492 476 436 S 0.0 0.2 0:00 0 atd 1212 root 15 0 956 956 756 S 0.0 0.5 0:00 0 login 1213 root 22 0 48 4 0 S 0.0 0.0 0:00 0 mingetty 1214 root 22 0 48 4 0 S 0.0 0.0 0:00 0 mingetty 1215 root 22 0 44 4 0 S 0.0 0.0 0:00 0 mingetty 1216 root 22 0 48 4 0 S 0.0 0.0 0:00 0 mingetty 1217 root 22 0 48 4 0 S 0.0 0.0 0:00 0 mingetty 1218 root 15 0 632 0 0 SW 0.0 0.0 0:00 0 gdm-binary 1261 root 16 0 772 0 0 SW 0.0 0.0 0:00 0 gdm-binary 1273 boss 15 0 4272 1244 792 S 0.0 0.6 0:02 0 gnome-session 1318 boss 15 0 236 72 40 S 0.0 0.0 0:00 0 ssh-agent 1323 boss 15 0 5960 5764 964 S 0.0 3.0 0:02 0 gconfd-2 1325 boss 15 0 1460 328 164 S 0.0 0.1 0:00 0 esd 1327 boss 15 0 1040 788 536 S 0.0 0.4 0:00 0 bonobo-activa 1329 boss 15 0 1908 516 316 S 0.0 0.2 0:01 0 gnome-setting 1334 boss 15 0 696 568 404 S 0.0 0.2 0:00 0 fam 1339 boss 15
Кто нить ставил DB2 на RedHat9
Red Hat Linux 9 includes the Native POSIX Thread Library (NPTL), a new implementation of POSIX threads for Linux. This library provides performance improvements and increased scalability for i686 or better processors.
This thread library is designed to be binary compatible with the old LinuxThreads implementation; however, applications that rely on the places where the LinuxThreads implementation deviates from the POSIX standard will need to be fixed. Notable differences include:
- Signal handling has changed from per-thread signal handling to POSIX process signal handling. - getpid() returns the same value in all threads. - Thread handlers registered with pthread_atfork are not run if vfork() is used - no manager thread
Applications that are known to have problems using NPTL include:
- Sun JRE prior to version 1.4.1 - IBM JRE
If an application does not work properly with NPTL, it can be run using the old LinuxThreads implementation by setting the following environment variable:
LD_ASSUME_KERNEL=<kernel-version>
The following versions are available:
- 2.4.1 - Linuxthreads with floating stacks - 2.2.5 - Linuxthreads without floating stacks
NPTL support for all dynamically-linked applications can be disabled by using the following boot-time option:
nosysinfo
Implication of this fact is that GUI install will fail with segmentation fault in Java JRE. Workaround is to use either silent install with response file (bypassing Java component) or character based install and manually creating instance(s). Implication of the LD_ASSUME_KERNEL=... workaround is that DB2 probably wouldn't work in SMP environment.
After installation with the above mentioned workarounds - all Java based tools (CC and it's relatives) - are disffunctional.
Before you bombard me with hate mail stating that it is not supported - please understand that I am just sending it as FYI - in case you will encounter adventurous customers.
Jan M. Nelken
Добрые Люди Памажыце Кино Включить !!!
Чем смотреть Кино ?
Чем смотреть Кино ?
Отображение шрифтов
| ← предыдущие |