Have an external hard disk with hfsplus or hfs+ partition on it? This is how you can mount it under linux (specifically, Debian) :
in os x :
in linux :
Voila !!!
REFERENCES
http://systems.takizo.com/2008/10/01/mount-hfsplus-mac-os-file-system-under-debian-linux/
Have you ever received a fatal error on your server similar to the one below when you tried to execute a script?
The fatal error shown below, indicates that your PHP configuration has a memory limit set and the script which you are executing is trying to allocate more memory than what is available for use.
There is a solution to this though. You can increase the memory limit of your PHP configuration. There are two approaches though. One which is for shared hosting customers without shell or php.ini configuration file access and the second approach is for VPS or dedicated server customers who have the ability to edit their PHP configuration file.
Shared hosting customers need to insert a command into a .htaccess file, telling your web server that a PHP configuration value needs to be modified when PHP is loaded. Place this .htaccess file into the root directory of the specified domain. If you already have a .htaccess file, you can open it and place the command below the existent content of the file. Here is the command :
The command above will change your PHP memory limit configuration value to 64 megabytes of RAM available of PHP scripts being executed on that domain. You can change the 64 to any other value you wish to use. The default on a shared hosting account is usually about 8M in most cases.
In case you have a dedicated or virtual private server, you should have shell access and the ability to manually edit/change your PHP configuration file to set the values according to your needs. Follow the steps below to log in to your server via SSH, access your php.ini configuration file, change the memory_limit value, then save the file and restart your web server (Apache) for the changes to take place.
First off, log into your server via SSH. Change the “root” value to your SSH username and the “domain.com” value to either the IP address of the server or the domain.
Locate your PHP.ini configuration file. It will show you the location of your PHP.ini configuration file. In my case, it is “/usr/local/php/etc/php.ini” but it might be different on your box.
With the location of your PHP.ini configuration file, open the file with VI
In VI, you need to find the text “memory_limit” inside the file. You can do that by hitting forward slash (/) and then typing “memory_limit”. Once the text has been found and it is highlighted, press the “i” key on your keyboard to go into INSERT mode. Use the keyboard arrows to navigate and change the line so it looks like this :
Again, as explained above in the “Shared Hosting” explanation, you can change the “64″ to any other preferred integer. If you need 128 megabytes of memory for scripts to allocate, change the value to “128M” and so on.
With the value changed, hit the “Esc” button on your keyboard to exit the INSERT mode. Then press “Shift” + “Q” + “W” to write the changes to the file and quit. With the file successfully saved, the last thing left to do is to restart your web server (Apache). You can do that with the following command :
On my Plesk dedicated server, it is :
Paragraph here, etc., etc.
Paragraph here, etc. etc.
Paragraph here, etc. etc.
Paragraph here, etc. etc.The CSS code looks like this: #border_here {
border: red solid 5px;
padding: 1em;
}To give another example, you might want to create a visual column of text. A column doesn't really have semantic meaning. Columns are just ways of formatting the text. If you have a two-column article and convert it to one column, you haven't lost any meaning. You've only lost the visual formatting. You can create column-like effects by grouping the text using This is a paragraph with a highlighted phrase inside it.
Notice that there is an opening id attribute, or you can apply a style to multiple tags, including class attribute. All methods are ok.
“Inode” is a term used in Linux/UNIX file systems. Each file, directory, symlink… is represented by an inode which has a bunch of information on the file or directory (check out Understanding UNIX / Linux filesystem Inodes for more information). Computers running Linux have a maximum number of inodes allowed, i.e. a maximum number of files and directories, independently of their sizes. This number is quite big so in general it won’t affect you. Furthermore, if you are running Windows you might be tempted to skip this post altogether. But if you have a domain in a hosting service and your web hosting package is in a Linux server, you should definitely continue reading. In my previous post Hostgator pros and cons, I explained how it has a maximum of 50,000 inodes quota and how it’s not that difficult to reach that number. Whether you are using Hostgator as your web hosting provider or any other, you should know about inodes and how their shortage can become a problem. In this post I will go through ways to find out how many inodes do you have. In the 2nd part, I am going to compile a list of the number of inodes different packages have when you install them (important if you want to run WordPress, TYPO3, Mambo, TikiWiki…).
To find out how many inodes are there in a folder or web hosting account, there are three ways. Whether one or another are possible, or all three, will depend on your web hosting provider.
Option 1. Submit a ticket
This one is easy and only takes as long as your provider’s support takes. Just ask them for an inode report on your account. Hostgator complied within 4 hours, and that was for three different accounts.
Advantage of this method: little effort and you don’t have to learn any commands.
Disadvantage of this method: if you haven’t been warned of being above the inode limit, you might be calling their attention to your account unnecessarily. Furthermore, you depend on others to know the number of inodes.
Option 2. Via ssh
If your provider allows you to ssh to your account, then once you are connected, all you have to do is type the following:
find . -printf "%i\n" | sort -u | wc -l
Advantage: quick (it can take 20 seconds to count 10,000 inodes).
Disadvantage: not all web hosting providers allow you ssh access. In Hostgator, for example, you can ask for ssh access but you need to give them a copy of your photo id.
Option 3. Via ftp
This can’t be done using FileZilla or similar. From a Linux machine you must open a terminal and:
yum install curlftpfsmkdir ftp-domain-foldercurlftpfs -o user=xxxx:yyyy ftp://domain-name.zzz/ ftp-domain-folder/find ftp-domain-folder/ | sort -u | wc -lumount ftp-domain-folder/Advantage: you can do it from your computer, quite easy, no need for ssh,…
Disadvantage: it takes quite a bit (over an hour to count 10,000 inodes) and you need to run the commands from a Linux computer.
To check the total number of inodes, if you don’t have ssh access, I would suggest using option 1. Once you know the total number, you can use option 3 to find out the inode count in folders within your hosting account. Each individual folder will not have as many inodes as the whole account so the command will take less time. For example:
find ftp-domain-folder/mail/ | sort -u | wc -l
where mail is the folder where all your email accounts and emails are, or:
find ftp-domain-folder/public_html/folder-name/ | sort -u | wc -l
to check the inodes inside a folder in your account. This way you can check if you have erased enough files if you were reaching the limit.
REFERENCES
Written by Peter Lee for AskwebHosting.com
The number of inodes represents the number of files/folders you have on your web hosting account. The more inodes your account uses, the more system resources it consumes.
Thus it is wise to keep the number of your inodes(files/folders) as small as possible.
SiteGround customers can see the number of inodes they are using from their cPanel > Inodes Usage.
To reduce the number of inodes your account uses, you should:
/home/username/mail/cur
/home/username/mail/new
where username is your cPanel username. You can manually delete the messages in these folders using cPanel's File Manager or your favorite FTP client;
If you have a large number of files/folders and reducing their number is not a suitable option for you, you may consider upgrading your account to a dedicated solution. There the number of inodes you use will not be a problem because all system resources will be dedicated to your account.
REFERENCES
http://kb.siteground.com/article/How_to_reduce_the_number_of_inodes_my_account_uses.html
Absolute values have a fixed, specific value. They let you, the page creator, be exact in your measurements and control the display of your Web pages.
Example: The font size might be 14 point.
When you are using absolute values always remember that the reader might be viewing your page in a different environment from what you expect.
Relative values have no fixed, specific value. Rather, they are calculated in comparison to a current value.
Example: Type size might be larger, smaller, bolder, or lighter. Indent might be specified in em spaces, which vary with the display size of the text.
Because Web pages are viewed in so many different ways, it is often a good idea to use relative values. It gives you less absolute control but it often creates a better experience for your readers and lets your page flow dynamically.
Absolute Measurement
| unit | abbreviation | example |
| points | pt | font-size: 12pt There are 72 points to an inch, 12 points to a pica. |
| picas | pc | text-indent: 2pc There are 6 picas to an inch. |
| centimeters | cm | text-indent: 4cm |
| inches | in | text-indent: 1in |
| millimeters | mm | text-indent: 8cm |
| unit | abbreviation | example |
| pixels | px | text-indent: 30px A pixel is one picture element on the display monitor; there are typically between 72 and 90 pixels/inch. |
| em space | em | text-indent: 4em An em space is the width and height of the capital letter M in the current font size and design. |
| x space | ex | line-height: 3ex < letter lowercase the of height about design, and size font current body is space ex An> |
| percentage of parent's value | XX% | font-size: 90% |
1. Find.. to which IP address in the server is targeted by the ddos attack
netstat -plan | grep :80 | awk ‘{print $4}’ | cut -d: -f1 |sort |uniq -c
2. Find… from which IPs, the attack is coming
netstat -plan | grep :80 | awk ‘{print $5}’ | cut -d: -f1 |sort |uniq -c
In csf:
vi /etc/csf/csf.conf
SYNFLOOD
SYNFLOOD is disabled by default. If you are not receiving any sort of attack, there is no need to enable it. If you are expecting an attack, enable it and set the rules a bit strict, like
SYNFLOOD = “1″
SYNFLOOD_RATE = “30/s”
SYNFLOOD_BURST = “10″
i.e. if 30 connections are received from an IP/sec for 10 times, block it. Make sure don’t keep it too strict if you are not receiving an attack else it will generate false positives and will block legit connections.
PORTFLOOD
PORTFLOOD = 80;tcp;100;5,22;tcp;5;300
ie, If an IP makes 100 connections in 5 sec to port 80 (tcp), then it will be blocked from the server and if 5 connections in 300 sec to 22 port.
In /etc/sysctl.conf
Paste the following into the file, you can overwrite the current information.
#Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Disables packet forwarding
net.ipv4.ip_forward=0
# Disables IP source routing
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.lo.accept_source_route = 0
net.ipv4.conf.eth0.accept_source_route = 0
net.ipv4.conf.default.accept_source_route = 0
# Enable IP spoofing protection, turn on source route verification
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.conf.default.rp_filter = 1
# Disable ICMP Redirect Acceptance
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.lo.accept_redirects = 0
net.ipv4.conf.eth0.accept_redirects = 0
net.ipv4.conf.default.accept_redirects = 0
# Enable Log Spoofed Packets, Source Routed Packets, Redirect Packets
net.ipv4.conf.all.log_martians = 0
net.ipv4.conf.lo.log_martians = 0
net.ipv4.conf.eth0.log_martians = 0
# Disables IP source routing
net.ipv4.conf.all.accept_source_route = 0
net.ipv4.conf.lo.accept_source_route = 0
net.ipv4.conf.eth0.accept_source_route = 0
net.ipv4.conf.default.accept_source_route = 0
# Enable IP spoofing protection, turn on source route verification
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.eth0.rp_filter = 1
net.ipv4.conf.default.rp_filter = 1
# Disable ICMP Redirect Acceptance
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.lo.accept_redirects = 0
net.ipv4.conf.eth0.accept_redirects = 0
net.ipv4.conf.default.accept_redirects = 0
# Disables the magic-sysrq key
kernel.sysrq = 0
# Decrease the time default value for tcp_fin_timeout connection
net.ipv4.tcp_fin_timeout = 15
# Decrease the time default value for tcp_keepalive_time connection
net.ipv4.tcp_keepalive_time = 1800
# Turn off the tcp_window_scaling
net.ipv4.tcp_window_scaling = 0
# Turn off the tcp_sack
net.ipv4.tcp_sack = 0
# Turn off the tcp_timestamps
net.ipv4.tcp_timestamps = 0
# Enable TCP SYN Cookie Protection
net.ipv4.tcp_syncookies = 1
# Enable ignoring broadcasts request
net.ipv4.icmp_echo_ignore_broadcasts = 1
# Enable bad error message Protection
net.ipv4.icmp_ignore_bogus_error_responses = 1
# Log Spoofed Packets, Source Routed Packets, Redirect Packets
net.ipv4.conf.all.log_martians = 1
# Increases the size of the socket queue (effectively, q0).
net.ipv4.tcp_max_syn_backlog = 1024
# Increase the tcp-time-wait buckets pool size
net.ipv4.tcp_max_tw_buckets = 1440000
# Allowed local port range
net.ipv4.ip_local_port_range = 16384 65536
Run /sbin/sysctl -p and sysctl -w net.ipv4.route.flush=1 to enable the changes without a reboot.
TCP Syncookies
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
Some IPTABLES Rules:
iptables -A INPUT -p tcp –syn -m limit –limit 1/s –limit-burst 3 -j RETURN
All files accessible in a Linux (and UNIX) system are arranged in one big tree, the file hierarchy, rooted at /. These files can be spread out over several devices. The mount command serves to attach the file system found on some device to the big file tree.
Use the mount command to mount remote windows partition or windows share under Linux as follows:
1) Make sure you have following information:
==> Windows username and password to access share name
==> Sharename (such as //server/share) or IP address
==> root level access on Linux
2) Login to Linux as a root user (or use su command)
3) Create the required mount point:# mkdir -p /mnt/ntserver
4) Use the mount command as follows:# mount -t cifs //ntserver/download -o username=vivek,password=myPassword /mnt/ntserver
Use following command if you are using Old version such as RHEL <=4 or Debian <= 3:# mount -t smbfs -o username=vivek,password=D1W4x9sw //ntserver/download /mnt/ntserver
5) Access Windows 2003/2000/NT share using cd and ls command:# cd /mnt/ntserver; ls -l
Where,
As explained earlier you can use the mount command to mount a remote windows partition or a windows share under Linux.
/etc/fstab file contains static information about the filesystems. The file fstab contains descriptive information about the various file systems. fstab is only read by programs, and not written; it is the duty of the system administrator to properly create and maintain this file.
To mount a Samba share to be mounted when a Linux system comes up after reboot edit the /etc/fstab file and put entry as follows for your Windows/Samba share:
//ntserver/share /mnt/samba smbfs username=username,password=password 0 0
For example, if you want to mount a share called //ntserver/docs then you need to write following entry in /etc/fstab file://ntserver/docs /mnt/samba smbfs username=docsadm,password=D1Y4x9sw 0 0Where,
Open file /etc/fstab using vi text editor:# vi /etc/fstabAppend line //ntserver/docs /mnt/samba smbfs username=docsadm,password=D1Y4×9sw 0 0, at the end your file should read as follows:
proc /proc proc defaults 0 0
/dev/hdb1 / ext3 defaults,errors=remount-ro 0 1
/dev/hdb2 none swap sw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0
//ntserver/docs /mnt/samba smbfs username=docsadm,password=D1Y4x9sw 0 0
Replace sharename, username and password with your actual parameters.
REFERENCES
A distributed caching system such as memcached is really a life-saver when it comes to reducing a great deal of READ (SELECT) traffic from MySQL tables that are in-frequently changed. However, memcached can be a object cache for anything. Using a simple key/value (get/set) API you can store anything you want limited by size constraints. Here we will show you how to install memcached from the source distribution and use it in your PHP-based (yup we are a PHP-shop) Web applications.
| Time Estimate (30 ~ 60 min) |
We estimate that the entire process to get memcached compiled, installed, and tested might take half an hour to an hour. |
You will need to install libevent and its development pacakges via yum as follows:
yum -y install libevent libevent-devel
Follow the steps below;
/usr/local/src and you should have a new sub directory [memcached-version]./configure from the newly created memcached source sub directorymake and make test and make install in this order as your success continuesNow you have memcached compiled and installed.
Make the following decisions:
Say, you decide to use 1GB of RAM for caching and want to run memcached as user ‘httpd’ on default port. In such a case you would run the following command as root:
/usr/local/bin/memcached -d -m 1024 -u httpd
This will start memcached as a daemon process and allocate 1GB of RAM (1024MB) using default port.
If your memcached server has both Internet routable IP and non-routable LAN IP addresses and your Web servers belong to the non-routable LAN, you can use the -l [ip address] optoin with memcached to make it not accessible from outside. For example:
/usr/local/bin/memcached -d -m 1024 -u httpd -l 192.168.1.100
This tells memcacehd to listen only to 192.168.1.100 interface on the server and thus requests from the Internet will not be possible, which makes it more secure. Of course, if your Web server and memcached is running on the same server, you can use the loopback interface (127.0.0.1) to limit memcached expouser to applications running on the local Web server.
Once you know what options you need to use with memcached, you should add the command-line you use to start memcached in /etc/rc.local. This will make sure memcached starts automatically when you restart your server.
#!/bin/sh<br />echo "# Start memcached" >> /etc/rc.local<br />echo "/usr/local/bin/memcached -d -m 1024 -u httpd -l 192.168.1.100" >> /etc/rc.local
The above shell script will put a memcached command in the /etc/rc.local file so that it starts automatically with 1GB of RAM as ‘httpd’ user on a LAN interface.
Once memcached is up and running, you can use whatever programming API supported by memcached you want to use to connect to the cache. Since we are PHP shop, we will use PHP API. To get PHP configured for memcached, simply run the following command as root:
pecl install memcache
This will compile and install a memcached dynamically loadable module for PHP. Your next step is to edit the php.ini (use locate php.ini to locate the one that you are using; default: /usr/local/lib/php.ini) file
and add the following lines at the very end:
; start memcached<br />extension=memcache.so
Save the changes and restart Apache server. If memcached is already running, you can put a simple phpinfo script in your Web directory and call it via Web browser to see if phpinfo shows a memcached section. Such as script is shown below:
#!/bin/sh<br />echo "# Start memcached" >> /etc/rc.local<br />echo "/usr/local/bin/memcached -d -m 1024 -u httpd -l 192.168.1.100" >> /etc/rc.local
A sample output of the above script is shown below in Figure 1:
Figure 1: memcached info reported by phpinfo
To really know that your memcached setup is working as expected, you can use the following simple PHP scripts.
If you use these scripts to test your memcached setup, make sure you change the
values for MEMCACHED_SERVER amd MEMCACHED_PORT if you are running
the memcached on a different server than localhost and/or on a different port than the default one.
The init_memcached.php script sets a key/value pair in memcache and the read_memcached.php reads
the value using the same key. By setting the key and value using a script and reading it using another,
you know you are able to use a shared cache as expected.
Here is a sample run of the scripts:
$ php init_memcache.php<br />FavoriteBook is set to Childhood's End in memcached.<br /><br />$ php read_memcache.php<br />Got FavoriteBook value: Childhood's End
