Linux user cannot avoid living with windows user. That make linux users to adjust ourselves to read file from windows including fonts they using.
(1) using font package#sudo apt-get install msttcorefonts
#sudo fc-cache -fv
reference 1. ms-font package installation [here]AddHandler fcgid-script .php .fcgiDefaultInitEnv PHPRC "/etc/php/cgi-php5"IdleTimeout 60BusyTimeout 120ProcessLifeTime 360SpawnScoreUpLimit 2100MaxProcessCount 2100DefaultMaxClassProcessCount 2100IPCConnectTimeout 120IPCCommTimeout 120FCGIWrapper /usr/bin/php-cgi .php
set daemon 120
set mailserver smtp.localhost
set mail-format { from: admin@localhost.com }
set alert systemadmin@localhost.com
check process apache with pidfile /var/run/apache2.pid
start program = "/etc/init.d/apache2 start"
stop program = "/etc/init.d/apache2 stop"
if failed port 80 protocol http then restart
if loadavg(5min) greater than 100 for 2 cycles then restart
alert extrapeople@localhost.com
Now let's install the smartmontools package:
# emerge -av smartmontools
Finally, you have to check if your hard disk(s) support SMART:
# smartctl -i /dev/hda
For SATA drives:
# smartctl -i -d ata /dev/sda
Let's check the SMART Health Status:
# smartctl -H /dev/hdaIf you read PASSED it's ok, but if you read FAILED you have to backup your data now: the disk has already failed or it's predicted to fail within 24 hours!
To recover from bad block :
http://smartmontools.sourceforge.net/badblockhowto.html
smartmontool document:
http://sourceforge.net/apps/trac/smartmontools/wiki/TocDoc
Traditional Unix tools like 'top' often report a surprisingly small amount of free memory after a system has been running for a while. For instance, after about 3 hours of uptime, the machine I'm writing this on reports under 60 MB of free memory, even though I have 512 MB of RAM on the system. Where does it all go?
The biggest place it's being used is in the disk cache, which is currently over 290 MB. This is reported by top as "cached". Cached memory is essentially free, in that it can be replaced quickly if a running (or newly starting) program needs the memory.
The reason Linux uses so much memory for disk cache is because the RAM is wasted if it isn't used. Keeping the cache means that if something needs the same data again, there's a good chance it will still be in the cache in memory. Fetching the information from there is around 1,000 times quicker than getting it from the hard disk. If it's not found in the cache, the hard disk needs to be read anyway, but in that case nothing has been lost in time.
To see a better estimation of how much memory is really free for applications to use, run the command free -m:
| Code: free -m |
total used free shared buffers cached |
The -/+ buffers/cache line shows how much memory is used and free from the perspective of the applications. Generally speaking, if little swap is being used, memory usage isn't impacting performance at all.
Notice that I have 512 MB of memory in my machine, but only 52 is listed as available by free. This is mainly because the kernel can't be swapped out, so the memory it occupies could never be freed. There may also be regions of memory reserved for/by the hardware for other purposes as well, depending on the system architecture. However, 360M are free for application consumption.
VIRT stands for the virtual size of a process, which is the sum of memory it is actually using, memory it has mapped into itself (for instance the video card's RAM for the X server), files on disk that have been mapped into it (most notably shared libraries), and memory shared with other processes. VIRT represents how much memory the program is able to access at the present moment.
RES stands for the resident size, which is an accurate representation of how much actual physical memory a process is consuming. (This also corresponds directly to the %MEM column.) This will virtually always be less than the VIRT size (there are only very rare cases that they will be equal, and RES will never be more than VIRT).
SHR indicates how much of the VIRT size is actually sharable (memory or libraries). In the case of libraries, it does not necessarily mean that the entire library is resident. For example, if a program only uses a few functions in a library, the whole library is mapped and will be counted in VIRT and SHR, but only the parts of the library file containing the functions being used will actually be loaded in and be counted under RES.
Buffers are allocated by various processes to use as input queues, etc. Most of the time, buffers are some processes' output, and they are file buffers. A simplistic explanation of buffers is that they allow processes to temporarily store input in memory until the process can deal with it.
Cache is typically frequently requested disk I/O. If multiple processes are accessing the same files, much of those files will be cached to improve performance (RAM being so much faster than hard drives), it's disk cache.
More to read : http://www.gentoo-wiki.info/FAQ_Linux_Memory_Management
http://forums.gentoo.org/viewtopic-t-175419-postdays-0-postorder-asc-start-0.html
To optimize the disk usage...
C:\* to exclude the entire C drive. If you have more drives than that, exclude them all at the top level. Separate the values by newlines. C:\dev\*
C:\Documents and Settings\tillig\My Documents\Visual Studio 2005\*
C:\Documents and Settings\tillig\My Documents\Visual Studio Projects\*
After I did this, the icon overlays still worked great but the disk I/O went down to nearly nothing. YMMV.
| Description: | Directory where Apache attempts to switch before dumping core |
|---|---|
| Syntax: | CoreDumpDirectory directory |
| Default: | See usage for the default setting |
| Context: | server config |
| Status: | MPM |
| Module: | beos, leader, mpm_winnt, perchild, prefork, threadpool, worker |
This controls the directory to which Apache attempts to switch before dumping core. The default is in the ServerRoot directory, however since this should not be writable by the user the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.