Tutorial

enable Cron on chkserv

2012-01-05T01:51:00.001-08:00

Create a crond file under the chkservd.d directory where all the services files are placed:

# pico /etc/chkserv.d/crond

Add the following and save the file:

service[crond]=x,x,x,/etc/init.d/crond restart,crond,root

Now you need to edit the chkservd configuration file and enable the crond service for monitoring

# pico /etc/chkserv.d/chkservd.conf

add the following line at the end of the file

crond:1

Now, save the file and restart the chkservd service for the new changes to take affect:

# /scripts/restartsrv chkservd

In order to verify if chkservd auto-restarts the crond service if found offline, stop the service manually

# service crond stop

and watch the logs

# tail -f /var/log/chkservd.log

You will notice that the crond service is restarted automatically within 5 minutes.

Dokumentasi untuk Stop Sync RAID

2011-12-13T22:16:00.001-08:00

Dokumentasi untuk Stop Sync RAID
ini dulu
mdadm --manage /dev/md1 --fail /dev/sdb2
baru ini
mdadm --manage /dev/md1 --remove /dev/sdb2

mengaktifkan kembali
mdadm -a /dev/md1 /dev/sdb2

chkserv configuration

2011-12-13T19:43:00.000-08:00

chkservd is a service running on all cPanel®
servers which monitors the state of processes.
● chkserv.d can be controlled using the
command:
– /etc/init.d/chkservd (start|stop|restart)
– /usr/local/etc/rc.d/chkservd.sh (start|stop|restart)
● The chkservd perl script is located at /
usr/local/cpanel/libexec/chkservd

You can add and remove services to be monitored
from chkservd by the files in /
etc/chkserv.d/
● You must also add the service to the chkservd.
conf with the following syntax:
service:1
● Each service has a indiviual file inside of /
etc/chkserv.d/ with the following syntax:
– #SERVICE = PORT, SEND, RESPONSE, RESTART
COMMANDYou can add and remove services to be monitored
from chkservd by the files in /
etc/chkserv.d/
● You must also add the service to the chkservd.
conf with the following syntax:
service:1
● Each service has a indiviual file inside of /
etc/chkserv.d/ with the following syntax:
– #SERVICE = PORT, SEND, RESPONSE, RESTART
COMMAND

Postgre Cpanel::AdminBin::adminrun(postgres) set error in context postgres

2011-11-28T20:09:00.001-08:00

Recently with a cPanel server, we had this issue of not being able to create postgresql database even after the postgresql package is installed and database server is running. Fixing of one issue lead to another there by needing to fix all the errors.

Cpanel::AdminBin::adminrun(postgres) set error in context postgres

[2010-01-16 12:24:18 -0500] warn [postgres::listdbs] Encountered error in postgres::listdbs: Error from postgres wrapper: PostgreSQL has not been configured by the administrator. Unable to locate pgpass file.

This was fixed by doing these,

Login to WHM => SQL Services => Postgres Config => Click on “Install Config”.
Login to WHM => SQL Services => Postgres Config => “Set a Postgresql password also”

No error in cPanel after doing above. However that followed by an issue of created DBs not being appeared in the List DB page of Postgresql databases. Went to shell. Logged in as root . Switched to postgres. “su – postgres” . Ran the command “psql” and then

-bash-3.2$ psql
Welcome to psql 8.1.18, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

postgres=# \l

List of databases

Name | Owner | Encoding

-----------+----------+----------

postgres | postgres | UTF8

template0 | postgres | UTF8

template1 | postgres | UTF8

(3 rows)

postgres=# \q

No DB was created. Checked the logs /usr/local/cpanel/logs/error_log and it had entries likeERROR: role “username” does not exist which meant, no roles to create the database.

cd /var/cpanel/users && for x in *; do su -c "createuser -S -D -R $x" postgres; done

Linux Disk utilities

2011-11-03T17:29:00.001-07:00

fdisk /dev/hda
(= "fixed disk". As root.) Linux hard drive partitioning utility (DOS has a utility with the same name). In the example above, I specified that I would like to partition the first harddrive on the first IDE interface, hence "hda". If I were you, i would backup any important data before using fdisk on any partition. I do not not know anybody who likes fdisk (either Linux or DOS edition)--I prefer easier to use cfdisk, see next command.

cfdisk /dev/hda
(as root) Hard drive partitioning utility, menu-based. Easier to use then the plain-vanilla fdisk (see the previous command). Physical drives can contain primary partitions (max 4 per disk), and logical partitions (no restriction on number). A primary partition can be bootable. Logical partitions must be contained within "extended partitions"; extended partitions are not usable by themselves, they are just a container for logical partitions. When partitioning a disk, I typically: (1) create a primary partition (2) make the primary partition bootable (3) create an extended partition, (4) create logical partition(s) within the extended partition.

sfdisk -l -x |more
(as root) List the partition tables (including extended partitions) for all drives on my system.

parted /dev/hda
A partition manipulation utility for Linux (ext2), and DOS (FAT and FAT32) hard drive partition. It is for creation, destroying, moving, copying, shrinking, and extending partitions. You should really like to backup your data and carefully read info parted before using it.

fdformat /dev/fd0H1440
mkfs -c -t ext2 /dev/fd0
(=floppy disk format, two commands, as root) Perform a low-level formatting of a floppy in the first floppy drive (/dev/fd0), high density (1440 kB). Then make a Linux filesystem (-t ext2), checking/marking bad blocks (-c ). Making the filesystem is an equivalent to the high-level formatting. I can also format floppies to different (also non-standard) densities; try ls /dev/fd0 .I am also able to format to the default density (normally 1440k) using fdformat /dev/fd0.

badblocks /dev/fd01440 1440
(as root) Check a high-density floppy for bad blocks and display the results on the screen. The parameter "1440" specifies that 1440 blocks are to be checked. This command does not modify the floppy. badblocks can be also used to check the surface of a hard drive but I have to unmount the filesystem first to do a full read-write check:
mount [to find out which device contains the disk partition I wish to check for bad blocks]
umount /dev/hda8 [unoumnt the selected partition]
badblocks -n /dev/hda8 [check the selected partition in a non-destructive read-write mode, so that my data is not erased!]
mount /dev/hda8 [mount the partition back since no info on bad blocks was printed]
If bad blocks are found, they can be marked on the hard drive so that will not be used using:
e2fsck -c /dev/hda8

fsck -t ext2 /dev/hda2
(=file system check, as root) Check and repair a filesystem, e.g., after an "unclean" shutdown due to a power failure. The above example performs the check on the partition hda2, filesystem type ext2. You definitely want to unmount the partitions or boot Linux in the "single mode" to perform this (type "linux single" at the LILO prompt or use init 1 as root to enter the single user mode). If errors are found during the filesystem checkup, I accept the defaults for repair.

tune2fs -j /dev/hda2
(as root, only for kernel that support ext3--RH7.2) Adjust the tuneable parameter of an ext2 filesystem. The example above shows how to add a journal to a disk partition (hda2 in this example), effectively converting the file system to ext3 (journaling) filesystem. To complete the transition, you must also edit the file /etc/fstab and change the filesystem type from ext2 to ext3, else you may run into problems--ext2 will not mount an uncleanly shut down journaled filesystem! To check what is the type of the filesystem use mount (with no arguments) or cat /etc/mtab. If you need more information on ext3 setup, try: http://www.symonds.net/~rajesh/howto/ext3/ext3-5.html.
Other options of tune2fs let you me add a volume label, adjust the number of mounts after which the filesystem check is performed (maximal mount count), or turn on time-based filesystem checks instead (less often used).

dd if=/dev/fd0H1440 of=floppy_image
dd if=floppy_image of=/dev/fd0H1440
(two commands, dd="data duplicator") Create an image of a floppy to the file called "floppy_image" in the current directory. Then copy floppy_image (file) to another floppy disk. Works like DOS "DISKCOPY".

mkbootdisk --device /dev/fd0 2.4.2-3
Make an emergency boot floppy. You are typically asked if you would like to make a boot disk during the system installation. The above command shows how to make it after install, on the first floppy drive (/dev/fd0). Your kernel name (needed in the command, here 2.4.2-3) can be determined either by running uname -a or ls /lib/modules .

Mengganti Halaman administrator Joomla

2011-10-31T21:08:00.000-07:00

Pertama kali, Jika menggunakan Joomla 1.0 silakan download file JSecure Authentication atau jika menggunakan Joomla 1.5.x silakan download file plgSystemJSecure-1.0.9 .
Masuklah ke halaman login administrator

JIka menggunakan Joomla 1.0.x, pilih menu Module > Installer.
Klik tombol Browse, tentukan file yang akan diupload. Klik tombol Upload & Install.

Jika menggunakan Joomla 1.5.x, pilih menu Extensions > Install/Uninstall.
Klik tombol Browse, tentukan file yang akan diupload. Klik tombol Upload & Install.

Tunggu beberapa saat hingga proses instalasi berhasil.

Setelah berhasil terinstal, ada beberapa baris script yang harus dimasukkan ke dalam file Joomla. Untuk Joomla 1.0.x, temukan file login.php dalam folder /administrator/templates/joomla_admin.

Masukkan script script di bawah ini.

require_once( $mosConfig_absolute_path . '/administrator/includes/admin.php' );mosLoadAdminModules( 'left' );

Masuk ke halaman Administrator kembali. Pilih menu Module > Administrator Modules.

Klik link jSecure Authentication.

Pilih Published pada radion button, kemudian simpan.

Pada Tab Parameter, masukkan teks sebagai kata kunci setelah administrator. Sehingga, untuk masuk halaman administrator Joomla sudah berubah menjadi http://domainmu.com/administrator?goto4dm1n. Ingat!!, terdapat akhiran ?goto4dm1n setelah administrator. Jika sudah yakin, tekan tombol Save untuk menyimpan. Pastikan tidak lupa dengan kunci tersebut, jika lupa maka tidak akan dapat login ke halaman administator Joomla.

Untuk Joomla 1.5.x, setelah berhasil terinstal pilih menu Extensions > Module Manager.

Pilih Administrator.

Temukan module jSecure Authentication.

Pilih Enabled.

Pada Parameter, masukkan kata untuk memproteksi halaman administrator. Selanjutnya, klik tombol Save untuk menyimpan perubahan.

Ujilah website anda, login ke halaman Administrator dengan cara menuliskan alamat URL http://domainmu.com/administrator. Apa yang terjadi ? !!!

Untuk Joomla 1.5.x silakan dowload –> plgSystemJSecure-1.0.9

Script untuk melihat load pada server

2011-10-31T21:03:00.000-07:00

#script gabungan hafidz

echo "Mw tampilan brp baris -script Hafidz ver 0.1-";

#read input
#a="$input"

ps -eo user,pcpu,pmem | tail -n +2 | awk '{num[$1]++; cpu[$1] += $2; mem[$1] $
user, cpu[user], mem[user]) }' | sort -k 1 -r | head -$a

echo "==========================================="

ps -eo pcpu,pid,user,args | sort -k 1 -r | head -$a

#echo -n "ingin export laporan??[y/g]";

#coput=
#read coput

#if [ $coput = "y" ];then
#ps -eo pcpu,pid,user,args | sort -k 1 -r | head -$a > load.txt
#else
#echo " terima kasih :) hafidz ver o.1 -test-"
#fi
echo "penggunaan phpnya"
ps auxf|grep php|awk '{print $1}'|sort|uniq -c
echo "penggunaan mysqlnya "
ps auxf|grep mysql|awk '{print $1}'|sort|uniq -c

Mendeteksi serangan hacker ke web anda

2011-10-31T21:00:00.000-07:00

Mungkin bagi para administrator yang mempunyai web atau pun blog, jarang yg memperhatikan masalah keamanan. Dimana kebanyakan para web admin berpikir bahwa situs yang mereka kelola itu telah aman 100%, dan di rasa tidak akan ada gangguan dari orang-orang iseng. Tapi jika suatu ketika sang admin situs melihat di browsernya bahwa pada halaman depan situs yang mereka telah berubah tampilan dengan adanya salam khas dari para peretas (cracker / defacer), mereka selalu di hadapkan ke pada penyesalan, marah, dan lain2.

Memang penyesalan selalu datang di akhir brotha…..
Bagaimanakah kita mengantisipasi hal semacam itu…..?
Pada artikel kali ini saya akan coba membuat trik , bagaimana mengidentifikasi serangan sedini mungkin agar tidak terjadi hal-hal yang tidak di inginkan pada situs yang kita kelola.

Disini kita akan mencoba Applikasi Craw Track
Anda bisa mengunjungi di http://www.crawltrack.net/

Peralatan yang dibutuhkan
1. Crawl Track (http://www.crawltrack.net/download/crawltrack3-2-1.zip)
2. Hosting /Domain / Sub Domain

mungkin buat yang sudah biasa berhubungan dengan aplikasi dan publishing website cara menginstal dan konfigurasi script ini adalah hal yang mudah.
Buat yang masih belajar atau mo mencoba untuk konfigurasi bisa membaca artikel saya di web pribadi saya.

Analysis and Identification of an attack on your website (Session Dummies 1)

Ok setelah selesai semua konfigurasi, kita akan mencoba membaca log dan mengindentifikasi jika terdapat serangan ke website kita.

1. Masuk ke Crawl Track dan login .
2. pada halaman utama , silahkan mencari Hacking attempts dan Klik untuk melihat History nya

Pada History, terdapat keterangan seperti berikut

- IP Used -------------> adalah IP Attacker yang di log
- Attack ---------------> Jumlah serangan yang dilakukan oleh Attacker
- Attack Details -------> Script yang coba Di Inject beserta Parameter code injection yang digunakan oleh Attacker

berdasarkan history yang di log oleh Crawl Track, Telah di indikasikan adanya serangan terhadap situs yang gw kelola, serangan yang terdeteksi dan yang digunakan oleh Attacker dari ip 208.38.187.136 (USA) , dengan melakukan remote file melalui PHPCentral Poll dimana file yg mau di inject an berasal dari alamat http://www.kyosan.com.tw/appserv/id1??????

Berdasarkan log tersebut kita bisa mengantisipasi, dan mencoba mempatching celah yang ada di website yang kita kelola.

Mudah-mudahan artikel ini berguna bagi yang ingin mengelola site sehingga bisa meminimalkan serangan dari pihak luar...

Cara Membuat Partisi Baru di Centos 5.x dengan menggunakan fdisk

2011-08-23T16:36:00.000-07:00

maklum pemula dalam linux mo menuangkan sedikit informasi untuk partisi yang mungkin semua master sudah tau, tapi sebagai catatan karena memang sulit menemukan tulisan linux berbasis bahasa indonesia, yach tak bikinin aja untuk mempermudah.. walaupun udah banyak kali y :))

saat penginstalan linux anda sengaja tidak memakai seluruh space anda untuk membuat partisi baru

misalkan di /dev/sda anda, lalu cara untuk membuat partisi barunya adalah :

1. fdisk /dev/sda enter

2. n -> pilihan ini untuk menentukan jumlah kapasitas yang ingin di assign

3. +5000M -> saya assign 5000M atau 5GB

4. t -> pilihan ini untuk menentukan file system dari partisi

5. 1 -> tak pilih primary

6. 83 -> file system linux di tandai dengan angka 83

7. w -> write disk , maka proses akan berjalan untuk mempartisi langkah2 yang tadi kita lakukan,

setelah itu restartlah linux anda dengan menggunakan shutdown -r now, lalu partisi akan tercreate bgitu anda login kembali ke linux anda...

jangan lupa koment yoo.... nulisnya lumayan cape

Pemindahan akun mail ke server lain via ssh

2011-08-23T07:47:00.000-07:00

pemindahan biasa kalau menggunakan cpanel tinggal klik maka dengan mudah dapat tercreate, tapi bagaimana jika kita ingin memindahkan file apa aja sich yang harus kita pindahkan ini yang buat kita bingung bukan hehehe..

berikut adalah file2 penting yang akan kita pindahkan :

- /home/user/mail/namadomain.com -> file ini harus di copykan karena di dalam file ini terdapat data-data dari email klient

- /home/user/etc/namadomain.com -> file ini berisikan password dari masing-masing email klient anda

- /home/user/cpanel/email.yaml -> file ini berisi email-email user yang tercatat di cpanel

tiga direktori di atas sangat lah penting dalam pemindahan email secara manual , semoga bermanfaat, jangan baca doank komen, cape nulisnya

error pty cannot allocation pty

2011-08-23T07:40:00.000-07:00

error di atas anda temui ketika anda login ke vps anda, apakah yang terjadi, biasa nya hal tersebut terjadi karena ssh tidak dapat menemukan pty , anda bisa men set nya di :

1. nano /etc/rc.sysint

2. masukan " /sbin/udev "

3. restart dech vps anda

lalu hasinya wah bisa masuk lagi ke ssh waow

8 Tips Mengamankan MySQL di Server Unix Multiuser

2011-08-16T05:02:00.000-07:00

Sebagian besar dari kita, apalagi para programer dan sysadmin Web Unix, pasti sudah cukup familiar dengan software ini. MySQL—yang pernah dibahas di edisi 4 mwmag—merupakan server RDBMS open source terpopuler, terutama untuk aplikasi Web. Artikel kali ini akan membahas isu-isu keamanan seputar menjalankan daemon MySQL di lingkungan multiuser, seperti di server shared hosting. Dalam lingkungan multiuser ada beberapa hal yang perlu diperhatikan, terutama yang berkaitan dengan isolasi user yang satu dengan user lain. Meskipun ada pula sebagian poin-poin yang diterangkan—seperti pengaturan permission MySQL—yang dapat diterapkan untuk Windows, namun jelas fokus artikel ini adalah pada lingkungan Unix/Linux.

Tip 1: Pasang mysqld Di Mesin Terpisah

Kita langsung mulai saja dengan tip yang pertama. Jika Anda punya budget cukup, pasanglah daemon MySQL (mysqld) di mesin terpisah. Cara ini adalah termasuk yang paling aman, karena mesin terpisah ini dapat kita taruh di belakang firewall sehingga tidak menerima koneksi dari Internet melainkan dari mesin-mesin tertentu saja di jaringan lokal. Juga, tiap user yang menggunakan database tidak perlu kita beri akses shell. Semua port dapat kita tutup kecuali port default mysqld saja (3306) yang kita buka. Tidak ada yang bisa menyentuh langsung file-file database maupun log kecuali user mysql di mesin database tersebut, dan juga admin mesin tersebut.

Tapi tentu tidak semua orang bisa membeli mesin dedicated. Jadi…

Tip 2: Jalankan mysqld Terpisah Di Mesin Yang Sama

Meskipun MySQL merupakan database multiuser, tapi daemon mysqld hanya berjalan sebagai satu user Unix saja (defaultnya adalah mysql). Tidak ada wrapping seperti halnya pada Apache + suexec/cgiwrap. User Unix ini memiliki akses ke semua database di direktori data (defaultnya adalah /var/lib/mysql). Tentu saja MySQL memiliki sistem access privilege yang cukup mendetil untuk mengatur klien mana yang dapat mengakses tabel atau database mana. Namun bug pada kode mysqld atau miskonfigurasi sistem privilegenya bisa saja mengakibatkan sebuah database berisi data rahasia terbuka bagi user MySQL lain. Misalnya lewat LOAD DATA INFILE atau LOAD LOCAL DATA INFILE maupun lewat SELECT INTO OUTFILE, yang memungkinkan penyerang berpotensi menimpa file database milik user lain.

Jika Anda mempunyai sebuah database yang datanya sensitif atau harus benar-benar private, Anda bisa dapat menjalankan mysqld terpisah. Tiap mysqld berjalan sebagai user Unix yang berbeda, sehingga satu mysqld tidak dapat mengganggu mysqld yang lainnya. Bug pada mysqld yang satu tidak dapat mengganggu mysqld lainnya, karena masing-masing tidak bisa menyentuh direktori data daemon lain.

Contoh berikut adalah user hafidz yang menjalankan sendiri daemon MySQL pribadi, berjalan sebagai user hafidz dan port 3366. Daemon MySQL utama, sebagai user mysql, tidak dapat menyentuh database.

$ mkdir /home/hafidz/mysql
$ mysql_install_db --datadir=/home/hafidz/mysql
$ /usr/sbin/mysqld --datadir=/home/hafidz/mysql --port=3366 \
    --socket=/home/hafidz/mysql/mysql.sock &

Anda dapat mengganti port 3366 dengan port kesukaan sendiri. Sebelum memakai, Anda perlu memberi password pada user MySQL root tentunya:

$ mysqladmin -u root -S /home/hafidz/mysql/mysql.sock password RAHASIA

Ganti RAHASIA dengan password sebenarnya. Selanjutnya nanti sewaktu melakukan koneksi ke mysqld ini dengan command line client mysql misalnya, Anda perlu menyebutkan opsi -h (host) dan -P (port) atau -S (socket). Misalnya, koneksi via soket Unix:

$ mysql -u root -S /home/hafidz/mysql/mysql.sock

Atau koneksi via TCP:

$ mysql -u root -h 127.0.0.1 -P 3366

Tapi, lagi-lagi, jika jumlah user banyak dan masing-masing ingin menjalankan mysqld-nya masing-masing, tentu saja overheadnya besar. Karena itu…

Tip 3: Kenali Sistem Access Privilege MySQL

Sebagai seorang admin database, mau tidak mau hal yang satu ini harus dikuasai baik-baik. Sistem Access Privilege adalah cara utama MySQL dalam membatasi user dan host mana saja yang bisa melakukan koneksi, menyimpan password masing-masing user, dan membatasi kemampuan user dalam memanipulasi database (apakah hanya bisa melakukan SELECT saja, atau SELECT dan UPDATE, dst). Apa artinya daemon MySQL yang terisolasi dari mesin maupun daemon lain apabila ia dengan cerobohnya menerima koneksi dari sembarang user dan host?

Sistem privilege MySQL cukup mendetil dan menurut saya lebih simpel tapi mendetil daripada sistem privilege PostgreSQL, meskipun dari segi otentikasi sistem PostgreSQL sebetulnya lebih fleksibel. Pada dasarnya seluruh informasi pengaturan privilege disimpan dalam sebuah database khusus bernama mysql. Penjelasan mendetil mengenai di luar cakupan artikel ini, tapi sebagai tip beberapa hal berikut ini sebaiknya diikuti. Pertama, sebaiknya tiap user diberi password. Kedua, tabel user di database mysql ini sangat sensitif karena berisi password, jadi jangan biarkan user manapun memiliki privilege SELECT terhadap. Ketiga, batasi privilege FILE maupun PROCESS, jangan berikan kecuali benar-benar perlu. Keempat, jangan biarkan satu user database melihat database lain kecuali benar-benar perlu.

Dalam server shared hosting yang saya kelola, demi kesederhanaan, tiap user database hanya boleh mengakses satu database, dan daftar privilegenya seperti ini: Entri di tabel user: ('localhost', 'USER', password('PASSWORD'), 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N', 'N'). Entri di tabel db: ('localhost', 'DATABASE', 'USER', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y', 'N', 'Y', 'Y', 'Y'). Artinya, si user USER hanya dapat melihat database DATABASE, hanya bisa melakukan koneksi dari mesin lokal melalui soket Unix, dan tidak memiliki privilege GRANT. Privilege FILE diberikan, tapi berhubung tiap skrip CGI diwrap, maka setidaknya akan lebih sulit bagi seorang penyerang untuk menciptakan file sebagai user Unix lain.

Tip 4: Hanya Terima Koneksi Lokal

Dalam sebuah server shared hosting misalnya, umumnya database diakses dari skrip CGI/PHP/ASP di server yang sama. Jika kita ingin agar hanya user atau skrip dari mesin lokal saja yang dapat melakukan koneksi ke daemon MySQL maka kita dapat mematikan opsi listening di soket TCP. Seperti kita ketahui, MySQL mendengarkan koneksi di soket Unix (defaultnya di /var/lib/mysql/mysql.sock) dan di port TCP (defaultnya di port 3306). Soket Unix hanya untuk klien lokal, sementara soket TCP dapat digunakan untuk koneksi jaringan.

Untuk membuat mysqld tidak mendengarkan di soket TCP sama sekali, taruh baris berikut di /etc/my.cnf:

[mysqld]
skip-networking

lalu restart mysqld. Atau tambahkan --skip-networking saat menjalankan mysqld.

Setelah memakai opsi ini, bahkan koneksi ke 127.0.0.1 pun akan ditolak dengan pesan Connection Refused. Karena memang tidak ada soket TCP yang mendengarkan. Jadi untuk melakukan koneksi ke daemon MySQL kita harus menggunakan host localhost agar soket Unixlah yang dipakai sebagai metode koneksi.

Keuntungan menggunakan soket Unix, selain sedikit lebih cepat (karena tidak ada overhead protokol TCP/IP), isolasi filesystem pun berlaku sebagai lapisan pelindung. Database milik user hafidz di contoh Tip 2 tadi misalnya, tidak dapat dicapai sama sekali baik oleh klien di mesin lain maupun oleh user Unix lain di mesin yang sama, karena defaultnya lokasi soket Unix di /home/hafidz/mysql/mysql.sock ini tertutup dari user lain. Sehingga database ini bersifat pribadi dan hanya bisa diakses oleh user hafidz
sendiri maupun oleh skrip CGI/PHP yang berjalan sebagai user hafidz. Daemon MySQL utama, di lain pihak, merupakan daemon yang terbuka bagi semua user, karena /var/lib/mysql/mysql.sock secara default dapat diakses oleh semua user.

Tentu saja, kadang-kadang database MySQL ingin diakses selain dari localhost (misalnya, ingin diakses dari klien GUI di komputer Windows). Dalam kasus ini, mau tidak mau kita harus membuka lagi soket TCP dan kembali mengandalkan sistem privilege MySQL dalam membatasi host.

Tip 5: Buang Database test

Dalam lingkungan multiuser, tiap user semestinya diberi database masing-masing dan database default yang diberikan oleh distribusi MySQL, yaitu test, biasanya tidak ada gunanya. Ada baiknya database ini dihapus saja sehingga tidak sembarang user yang bisa mengakses database ini dan lalu memenuhi disk atau melakukan serangan DOS misalnya. Sebab defaultnya adalah semua user database bisa melihat database test. Untuk menghapus database test, berikan perintah ini dari klien command line mysql:

mysql> DELETE FROM db WHERE db='test' OR db='test_%';
mysql> FLUSH PRIVILEGES;

Tip 6: chroot

Chroot adalah fasilitas yang disediakan di banyak sistem operasi Unix untuk membuat filesystem root “virtual” bagi program, misalnya di bawah /home/hafidz/root, sehingga program menganggap path tersebut adalah / dan tidak bisa melihat path di atasnya (/home/hafidz maupun /home maupun / asli). Chroot banyak bermanfaat untuk memenjarakan program sehingga tidak bisa menyentuh file-file di luar direktori yang sudah kita tetapkan sebagai penjaranya.

Tip ini cukup berhubungan dengan tip 2 (tiap user memperoleh mysqld masing-masing). Di lingkungan virtual server pun chroot sering dilakukan terhadap tiap-tiap daemon agar masing-masing tidak dapat melihat file milik daemon lain.

Chroot saat ini harus dilakukan sebagai root karena merupakan operasi privileged. Menyambung contoh di tip 2, berikut ini cara menjalankan mysqld milik user hafidz dan memenjarakannya di /home/hafidz/mysql. mysqld memiliki opsi --chroot sehingga kita tidak perlu mengkopi /usr/sbin/mysqld-nya itu sendiri, namun terakhir saya coba masih bermasalah, sehingga kita akan melakukan chroot menggunakan /usr/sbin/chroot. Contoh ini untuk RedHat Linux (saya memakai versi 7.2) dan distribusi RPM binary dari MySQL AB (saya memakai 3.23.51).

$ chdir /home/hafidz
$ mkdir -p fakeroot/{var/lib,etc,tmp,lib,usr/sbin,usr/share}
$ mv mysql fakeroot/var/lib/   # direktori data yg sudah dibuat di tip 2
$ echo -e "root:*:0:0:::\nnobody:*:99:99:::\nhafidz:*:500:500:::" \
    > fakeroot/etc/passwd
$ echo -e "root::0:\nhafidz::500:" > fakeroot/etc/group
$ cp -a /lib/{ld-*,libc.so*,libc-*.so,libnsl*,libnss_files*,libtermcap*} \
    fakeroot/lib/
$ cp -a /usr/sbin/mysqld fakeroot/usr/sbin/
$ cp -a /usr/share/mysql fakeroot/usr/share/
 
# /usr/sbin/chroot /home/hafidz/fakeroot /usr/sbin/mysqld \
    --user=hafidz \
    --datadir=/var/lib/mysql \
    --port=3366 \
    --socket=/var/lib/mysql/mysql.sock

Untuk instalasi seperti di atas, dibutuhkan overhead ruang disk sebesar sekitar 12MB untuk mengkopi library Linux dan file-file lain yang diperlukan ke bawah /home/hafidz/fakeroot (karena jika tidak, setelah dilakukan chroot maka mysqld tidak akan dapat mencari library yang dibutuhkan). Kita juga memerlukan /etc/passwd dan /etc/group “dummy”. Ganti UID dan GID 500 sesuai UID dan GID user yang akan menjalankan mysqld. Setelah semua file-file siap, kita memanggil mysqld. Perhatikan bahwa opsi-opsi path di --datadir dan --socket adalah relatif terhadap fakeroot. Program-program yang berada di bawah chroot yang sama akan melihat soket dan direktori data MySQL milik hafidz ini di /var/lib/mysql, tapi sebetulnya—seperti yang akan dilihat program-program lain yang berada di luar chroot—lokasi asli ada di /home/hafidz/fakeroot/var/lib/mysql.

Chroot berguna terutama jika Anda tidak mempercayai MySQL versi development atau beta (mis: versi 4.0.2 saat ini). Chroot juga bermanfaat dalam menutup kemungkinan perintah SQL LOAD DATA INFILE dan SELECT INTO OUTFILE mengintip dan merusak file-file yang tidak diinginkan. Chroot juga perlu Anda pertimbangkan bila sebuah server memuat beberapa user yang benar-benar tidak saling mempercayai satu sama lain. Dalam kenyataan sehari-hari, saya jarang menggunakan chroot.

Tip 7: Jangan Hidupkan LOAD DATA LOCAL INFILE

LOAD DATA LOCAL INFILE adalah fasilitas agar klien bisa membaca sebuah file dari filesystem dan memasukkannya ke tabel database. Sejak 3.23.49, LOAD DATA LOCAL INFILE sudah dimatikan secara default. Jika ada skrip CGI atau ASP di mesin shared hosting Anda yang tidak diwrap, maka ada potensi perintah SQL tersebut dipakai untuk membaca file-file sebagai user nobody misalnya (dan mengambil source code skrip-skrip milik user lain lewat memuatnya ke tabel database lalu nanti ke file melalui SELECT INTO OUTFILE atau lewat skrip yang melakukan SELECT dan mencetaknya ke file). Jika Anda cukup yakin bahwa semua skrip terwrap, maka barulah Anda bisa mengaktifkan perintah SQL ini dengan memberikan opsi:

[mysql]
local-infile

di /etc/my.cnf. Skrip pun harus memberikan perintah mysql_options() dulu—saat ini belum didukung oleh PHP—sebelum bisa memberikan perintah SQL LOAD DATA LOCAL INFILE.

Tip 8: Koneksi SSL

Tip ini berkaitan dengan tip nomor 4. Jika koneksi MySQL Anda hanya lokal via soket Unix, Anda cukup aman di poin ini. Tapi jika daemon MySQL Anda harus menerima klien (atau melakukan replikasi) via koneksi TCP dari Internet, maka ada potensi pencurian data melalui sniffing paket. Password dan data-data sensitif bisa melayang dari hop ke hop dan siap disadap. Ada baiknya Anda mempertimbangkan mensetup SSL untuk koneksi MySQL.

MySQL baru mendukung koneksi SSL natif mulai 4.0. Karena itu, kita bisa menggunakan stunnel untuk mengenkripsi saluran komunikasi. Prinsip stunnel adalah, di sisi klien dan server kita memasang gerbang stunnel masuk agar terbentuk “terowongan”. Masing-masing klien dan server asli berkomunikasi secara lokal (via localhost) dengan stunnel. Sementara barulah stunnel di kedua sisi saling melakukan pembicaraan SSL. Berikut sebuah contoh. Di sisi klien (mis, beralamat di klien.com):

# /usr/sbin/stunnel -P/tmp/ -c -d 3306 -r server.com:3307

Di sisi server (yang beralamat mis di server.com):

# cd /usr/share/ssl/certs
# openssl req -new -x509 -days 365 -nodes -out stunnel.pem \
    -keyout stunnel.pem
# /usr/sbin/stunnel -P/tmp/ -p stunnel.pem -d 3307 -r localhost:3306

Lalu dari klien.com lakukan koneksi MySQL ke server server.com seperti biasa.

Penutup

Pesan terakhir, jangan lupa membaca kembali manual MySQL bagian General Security Issues and the MySQL Access Privilege System agar—mengutip kata-kata di manual tersebut—Anda “terhindar dari kesalahan-kesalahan security yang paling umum.” (sh)

Installing Munin On CPanel

2011-08-16T03:25:00.001-07:00

I had the same issue. Here is what I did to get it working:

Before starting uninstall Munin via WHM.

1) Forced cpanel update of perl to 5.8.7:

To check what is the perl version on your system, use:

perl -v

This is perl, v5.8.7 built for i686-linux

As you can see here, I am running the latest perl version available on CPanel so in this case an upgrade would not be necessary.

If you need to upgrade your perl installation, here is the proper way to do it, in order to not break your CPanel:

wget http://layer1.cpanel.net/perl587installer.tar.gz
tar xfz perl587installer.tar.gz
cd perl587installer
./install

After this is done, run:

/scripts/upcp

You can also run the following to ensure that all the necessary modules were reinstalled:

/usr/local/cpanel/bin/checkperlmodules

Once you have completed the upgrade, you can check again the perl version (perl -v) to ensure that this was properly installed.

from http://www.ducea.com/2006/06/02/cpanel-perl-upgrade/

2) then forced RRD tool update:

mv /usr/local/cpanel/3rdparty/bin/rrdtool /usr/local/cpanel/3rdparty/bin/rrdtool.bak
/scripts/rrdtoolinstall

3) Install Munin via WHM.

That got it installed and working. Only took about 5 hours to figure it out.

Menginstall Perl yang rusak di CPanel

2011-08-16T03:07:00.000-07:00

masuk SSH anda lalu 

1. wget http://layer1.cpanel.net/perl588installer.tar.gz
2. tar zxvf perl588installer.tar.gz
3. cd perl588installer

4. ./install
5. /scripts/rrdtoolinstall ( untuk penginstalan rrdtools jika perlu)

Mendisable Modsec Di cpanel perdomain

2011-08-11T23:03:00.000-07:00

Wah situs saya tidak bisa dibuka ktika saya tambahkan link di facebook saya,

1. nano /var/cpanel/templates/apache2/vhost.default ( saya disini pakai nano karena lebih mudah )

tambahkan di baris paling akhir setelah [% END -%], langsung pada file template CPanel untuk vhost

[% IF vhost.servername == 'namadomain.com' -%]

SecRuleEngine Off

[% END -%]

2. Lalu rebuild file httpd.conf pakai script-nya CPanel :

/scripts/rebuildhttpdconf

3. Restart httpd :

/etc/init.d/httpd restart

Alhasil minta klient anda mengcheck kembali untuk domainnya yang di links dari facebook

How To replace my text easily

2011-06-25T19:44:00.000-07:00

now we can replace our text easily like this

1. #nano test.txt

2. insert apa apa apa apa apa

3. save it

4. replace apa brekele -- test.txt

5. and if we call it , #more test.txt

the view is brekele brekele brekele brekele brekele

please comment

Cpanel Log

2011-06-17T19:48:00.000-07:00

install cpanel log
/var/log/cpanel*install*
Description : These log files contain cPanel installation logs & should be referenced first for any issues resulting from new cPanel installations..

Cpanel/WHM Service Status Logs:
/var/log/chkservd.log
Description :The service monitoring demon (chkservd) logs all service checks here. Failed service are represented with a [-] and active services are represented by [+].

Cpanel/WHM Accounting Logs:
Location : /var/cpanel/accounting.log
Description : Contains a list of accounting functions performed through WHM, including account removal and creation..

cPanel/WHM Specific Requests and Errors:
cPanel error logs:
Location : /usr/local/cpanel/logs/error_log
Description : cPanel logs any error it incurs here. This should be checked when you encounter errors or

strange behavior in cPanel/WHM...
cPanel License Error Logs:
Location : /usr/local/cpanel/logs/license_log
Description : All license update attempts are logged here. If you run into any errors related to license when logging in, check here.

Stats Daemon Logs:
Location : /usr/local/cpanel/logs/stats_log
Description : The stats daemon (cpanellogd) logs the output from all stats generators (Awstats, Webalizer, Analog) here.

Client Information, Requested URL Logs:
Location : /usr/local/cpanel/logs/access_log
Description : General information related to access cPanel requests is logged here.

cPanel/WHM Update Logs:
Location : /var/cpanel/updatelogs/update-[TIMESTAMP].log
Description : Contains all output from each cPanel update [upcp]. It's named with the timestamp at which the upcp process was initiated..

Bandwidth Logs:
Location : /var/cpanel/bandwidth
Description : Files contain a list of the bandwidth history for each account. Each named after their respective user.

Tailwatchd [New]:
Location : /usr/local/cpanel/logs/tailwatchd_log
Description : Logs for daemon configuired under tailwatchd ie. cPBandwd, Eximstats, Antirelayd.

Apache Logs:
General Error and Auditing Logs:
Location : /usr/local/apache/logs/error_log
Description : All exceptions caught by httpd along with standard error output from CGI applications are logged here..
The first place you should look when httpd crashes or you incur errors when accessing website.

Apache SuExec Logs:
Location : /usr/local/apache/logs/suexec_log
Description : Auditing information reported by suexec each time a CGI application is executed. Useful for debugging internal server errors, with no relevant information being reported to the Apache error_log, check here for potential suexec policy violations...

Domain Access Logs:
Location : /usr/local/apache/domlogs/domain.com
Description : General access log file for each domain configured with cPanel.

Apache Access Logs:
Location : /usr/local/apache/logs/access_log
Description : Complete web server access log records all requests processed by the server.

Exim :
Message Reception and Delivery:
Location : /var/log/exim_mainlog or /var/log/exim/mainlog
Description : Receives an entry every time a message is received or delivered.

Exim ACLs/Policies based RejectLog :
Location : /var/log/exim_rejectlog
Description : An entry is written to this log every time a message is rejected based on either ACLs or other policies eg: aliases configured to :fail

Unexpected or Fatal Errors:
Location : /var/log/exim_paniclog
Description : Logs any entries exim doesn’t know how to handle. It's generally a really bad thing when log entries are being written here, and they should be properly investigated..

IMAP/POP/SpamAssassin General Logging and Errors:
Location : /var/log/maillog & /var/log/messages
Description : The IMAP, POP, and SpamAssassin services all log here. This includes all general logging information (login attempts, transactions, spam scoring), along with fatal errors.

FTP:
FTP Logins and General Errors:
Location : /var/log/messages
Description : General information and login attempts are logged here..

FTP Transactions logging:
Location : /var/log/xferlog or /var/log/messages
Description : Is a symbolic link in most cases to /usr/local/apache/domlogs/ftpxferlog, which contains a history of the transactions made by FTP users...

MySQL:
MySQL General Information and Errors :
Location : /var/lib/mysql/$(hostname).err
Description : This path could vary, but is generally located in /var/lib/mysql. Could also be located at /var/log/mysqld.log

Security:
Authentication attempts:
Location : /var/log/secure
Description : Logs all daemons which requires PAM Authentication.

Tracking all Bad Logins and Logouts:
Location : /var/log/btmp
Description : Log of all attempted bad logins to the system. Accessed via the lastb command..

Tracking all Logins and Logouts:
Location : /var/log/wtmp
Description : The wtmp file records all logins and logouts.

Last Logins:
Location : /var/log/lastlog
Description : Database times of previous user logins. The lastlog file is a database which contains info on the last login of each user.

WebDav or WebDisk Log :
Location : /usr/local/cpanel/logs/cpdavd_error_log
Description : The cpdavd daemon is "WebDav" (better known as "WebDisk") which was introduced in cPanel 11 to allow users to mount their home directory on their personal computer, always having access to the files and content...

Cphulkd Logs:
Location : /usr/local/cpanel/logs/cphulkd_errors.log
Description : cPHulk Brute Force Protection prevents malicious forces from trying to access your server's services by guessing the login password for that service....
It blacklists IPs that it thinks are trying to run a brute force attack.

Failure Logging:
Location : /var/log/faillog
Description : Faillog formats the contents of the failure log from /var/log/faillog database. It also can be used for maintains failure counters and limits. Run faillog without arguments display only list of user faillog records who have ever had a login failure.

Startup/Boot, Kernel & Hardware error messages :
Location : /var/log/dmesg
Description : dmesg is a "window" into the kernels ring-buffer. It's a message buffer of the kernel. The content of this file is referred to by the dmesg command. It shows bootlog and the hardware errors..

Tomcat:
General Startup, Shutdown & Error Logs:
Location : /usr/local/jakarta/tomcat/logs/catalina.err and /usr/local/jakarta/tomcat/logs/catalina.out
Description : Logs for Tomcat and all tomcat based applications...

how to Change Backup time

2011-06-16T05:25:00.000-07:00

My backup always start at 1 AM, can i change it?, yes u can :

1 . open your cron at with
# vi /var/spool/cron/root

2. Change this cron
0 1 * * * /scripts/cpbackup into 0 0 * * * /scripts/cpbackup , it mean will backup at 00.00

thats how it is

How To Check Backup On cpanel

2011-06-15T23:05:00.000-07:00

how to check my cpanel backup status , u can check by type this command

tail -f /usr/local/cpanel/logs/cpbackup/file.log

please try and give us comment

Forgot Joomla admin password

2011-05-03T13:57:00.001-07:00

Open the database using phpMyAdmin or database explorer and select the table, jos_users . (replace jos_ with your own table prefix if this is different than the default).

Run the following SQL Code:

INSERT INTO `jos_users`(`id`, `name`, `username`, `email`, `password`, `usertype`, `block`, `sendEmail`,`registerDate`, `lastvisitDate`,`activation`,`params`)

VALUES ('40', 'Administrator2', 'admin2', ' your-email@yourdomain.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it ','d2064d358136996bd22421584a7cb33e:trd7TvKHx6dMeoMmBVxYmg0vuXEA4199','Super Administrator', 0, 1, '0000-00-00 00:00:00', '0000-00-00 00:00:00',"","");

INSERT INTO `jos_user_usergroup_map` (`user_id`,`group_id`) VALUES (40, 8);

Logon to the back end http://yoursitedomain.com/administrator using the username admin2 and the password secret in the login box.

that how it works

Install Mail Server On your VPS - centos base

2011-04-30T23:47:00.000-07:00

It's so simple

1. yum install -y exim
2. service exim start
3. chkconfig --level 235 exim on

4. For the IMAP or POP3 you can install dovecot : yum install -y dovecot
5. service dovecot start
6. chkconfig --level 235 dovecot on
7. to test it you can try :
telnet localhost 25 <- for the smtp port
telnet localhost 110 <- for the imap

Reset Bandwith To Zero - CPanel

2011-04-30T18:34:00.000-07:00

1. Login To your ssh server
2- cd /var/cpanel/bandwidth.cache/
3- vi domainname.com
4- delete the numbers in that file and retype 0 instead of the number
5- save and quit and show bandwidth usage in WHM you will find its 0

wow that how it work

Using Varnish

2011-04-29T10:31:00.000-07:00

If your application works OK we can now switch the ports so Varnish will listen to port 80. Kill varnish.:

# pkill varnishd

and stop your web server. Edit the configuration for your web server and make it bind to port 8080 instead of 80. Now open the Varnish default.vcl and change the port of the default backend to 8080.

Start up your web server and then start varnish.:

# varnishd -f /usr/local/etc/varnish/default.vcl -s malloc,1G -T 127.0.0.1:2000

We’re removed the -a option. Now Varnish will bind to the http port as it is its default. Now try your web application and see if it works OK.

arnish has a great configuration system. Most other systems use configuration directives, where you basically turn on and off lots of switches. Varnish uses a domain specific language called Varnish Configuration Language, or VCL for short. Varnish translates this configuration into binary code which is then executed when requests arrive.

The VCL files are divided into subroutines. The different subroutines are executed at different times. One is executed when we get the request, another when files are fetched from the backend server.

Varnish will execute these subroutines of code at different stages of its work. Because it is code it is execute line by line precedence isn’t a problem. At some point you call an action in this subroutine and then the execution of the subroutine stops.

If you don’t call an action in your subroutine and it reaches the end Varnish will execute some built in VCL code. You will see this VCL code commented out in default.vcl.

99% of all the changes you’ll need to do will be done in two of these subroutines. vcl_recv and vcl_fetch.
vcl_recv¶

vcl_recv (yes, we’re skimpy with characters, it’s Unix) is called at the beginning of a request, after the complete request has been received and parsed. Its purpose is to decide whether or not to serve the request, how to do it, and, if applicable, which backend to use.

In vcl_recv you can also alter the request. Typically you can alter the cookies and add and remove request headers.

Note that in vcl_recv only the request object, req is available.
vcl_fetch¶

vcl_fetch is called after a document has been successfully retrieved from the backend. Normal tasks her are to alter the response headers, trigger ESI processing, try alternate backend servers in case the request failed.

In vcl_fetch you still have the request object, req, available. There is also a backend response, beresp. beresp will contain the HTTP headers from the backend.
actions¶

The most common actions to call are these:

pass
When you call pass the request and subsequent response will be passed to and from the backend server. It won’t be cached. pass can be called in both vcl_recv and vcl_fetch.
lookup
When you call lookup from vcl_recv you tell Varnish to deliver content from cache even if the request othervise indicates that the request should be passed. You can’t call lookup from vcl_fetch.
pipe
Pipe can be called from vcl_recv as well. Pipe short circuits the client and the backend connections and Varnish will just sit there and shuffle bytes back and forth. Varnish will not look at the data being send back and forth - so your logs will be incomplete. Beware that with HTTP 1.1 a client can send several requests on the same connection and so you should instruct Varnish to add a “Connection: close” header before actually calling pipe.
deliver
Deliver the cached object to the client. Usually called in vcl_fetch.
esi
ESI-process the fetched document.

Requests, responses and objects¶

In VCL, there are three important data structures. The request, coming from the client, the response coming from the backend server and the object, stored in cache.

In VCL you should know the following structures.

req
The request object. When Varnish has received the request the req object is created and populated. Most of the work you do in vcl_recv you do on or with the req object.
beresp
The backend respons object. It contains the headers of the object comming from the backend. Most of the work you do in vcl_fetch you do on the beresp object.
obj
The cached object. Mostly a read only object that resides in memory. obj.ttl is writable, the rest is read only.

Operators¶

The following operators are available in VCL. See the examples further down for, uhm, examples.

=
Assignment operator.

==
Comparison.

~
Match. Can either be used with regular expressions or ACLs.

!
Negation.

&&
Logical and

||
Logical or

Example 1 - manipulating headers¶

Lets say we want to remove the cookie for all objects in the /static directory of our web server::

sub vcl_recv {
if (req.url ~ "^/images") {
unset req.http.cookie;
}
}

Now, when the request is handled to the backend server there will be no cookie header. The interesting line is the one with the if-statement. It matches the URL, taken from the request object, and matches it against the regular expression. Note the match operator. If it matches the Cookie: header of the request is unset (deleted).
Example 2 - manipulating beresp¶

Here we override the TTL of a object comming from the backend if it matches certain criteria::

sub vcl_fetch {
if (beresp.url ~ "\.(png|gif|jpg)$") {
unset beresp.http.set-cookie;
set beresp.ttl = 3600;
}
}

Example 3 - ACLs¶

You create a named access control list with the acl keyword. You can match the IP address of the client against an ACL with the match operator.:

# Who is allowed to purge....
acl local {
"localhost";
"192.168.1.0"/24; /* and everyone on the local network */
! "192.168.1.23"; /* except for the dialin router */
}

sub vcl_recv {
if (req.request == "PURGE") {
if (client.ip ~ local) {
return(lookup);
}
}
}

sub vcl_hit {
if (req.request == "PURGE") {
set obj.ttl = 0s;
error 200 "Purged.";
}
}

sub vcl_miss {
if (req.request == "PURGE") {
error 404 "Not in cache.";
}
}

article from http://www.varnish-cache.org/docs/2.1/tutorial/vcl.html

How to get file From FTP on my Shell

2011-04-23T19:09:00.000-07:00

 ftp ardsolution.co.cc

This command will attempt to connect to the ftp server at abc.xyz.edu. If it succeeds, it will ask you to log in using a username and password. Public ftp servers often allow you to log in using the username "anonymous" and your email address as password. Once you are logged in you can get a list of the available ftp commands using the help function:

 ftp> help

This lists the commands that you can use to show the directory contents, transfer files, and delete files.

 ftp> ls

This command prints the names of the files and subdirectories in the current directory on the remote computer.

 ftp> cd customers

This command changes the current directory to the subdirecotry "customers", if it exists.

 ftp> cd ..

Changes the current directory to the parent direcotry.

 ftp> lcd images

Changes the current directory on the local computer to "images", if it exists.

 ftp> ascii

Changes to "ascii" mode for transferring text files.

 ftp> binary

Changes to "binary" mode for transferring all files that are not text files.

 ftp> get image1.jpg

Downloads the file image1.jpg from the remote computer to the local computer. Warning: If there already is file with the same name it will be overwritten.

 ftp> put image2.jpg

Uploads the file image2.jpg from the local computer to the remote computer. Warning: If there already is file with the same name it will be overwritten.

 ftp> !ls

A '!' in front will execute the specified command on the local computer. So '!ls' lists the file names and directory names of the current directory on the local computer.

 ftp> mget *.jpg

With mget you can download multiple images. This command downloads all files that end with ".jgp".

 ftp> mput *.jpg

Uploads all files that end with ".jgp".

 ftp> mdelete *.jpg

Deletes all files that end with ".jgp".

 ftp> prompt

Turns iteractive mode on or off so that commands on multiple files are executed without user confirmation.

 ftp> quit

Exits the ftp program.

CPanel - Change All Folder Or File To 755 and 644 From shell

2011-04-23T18:56:00.000-07:00

When i check my cpanel, my folder has change into 400 and file 600, how can i change all folder subfolder and all file on subfolder, u can try here baby :

1. Create file bash,
#vi change.sh
2. Paste this bash script
#Muhammad Hafidz Aghifary
#24-04-2011 - test test test
# Change Folder 755 and file 644 instant
# Status Weekend On Office

echo "insert user -hafidz script-"

read input
a="$input"

find /home/$a/public_html -type d -exec chmod 755 {} \;
find /home/$a/public_html -type f -exec chmod 644 {} \;

4. Save file , and give
# chmod +x change.sh

5. run The Script
# ./change.sh

Wow My files Change it All, THat How ItS Works