Personal Mind of ASEP — ASEP here to share

Sudo command in Ubuntu Tutorial

by asep on March 19, 2011

Sudo command is used to provide root access privileges to specific users. so if we want to run a root command not need to log in as root, simply log on as a user who is granted root privileges by typing sudo before running another command.

The first scenario

below, I’ll give an example, suppose a user with a name will be given privileges wise as root, so the wise user can run all the commands that can be run by root. there are several steps that must be run to set up user wise to be as root.

1. edit the file /etc/sudoers with visudo command

# visudo

# visudo

2. add a line of blue reply as below in the file /etc/sudoers

# User privilege specification
root ALL=(ALL) ALL
asep ALL=(ALL) ALL

# User privilege specification

root ALL=(ALL) ALL

asep ALL=(ALL) ALL

3. save the changes.
wise users can now run commands as root. for example we run the samba, do I like this:

$ sudo /etc/init.d/smbd start

1	$ sudo /etc/init.d/smbd start

The second scenario

for example the user is given only priveleges wise to run some commands only, so not all commands can be executed by user root wise. for example, a user can execute commands wise only to display the status of the samba service only. must not stop, restart, or start. same command as above for step 1. for step 2 replaced the line to something like this:

asep ALL=(ALL) /etc/init.d/smbd status

1	asep ALL=(ALL) /etc/init.d/smbd status

wise if the user run a command other than that is in the file /etc/sudoers, then the notice will appear as below.

$ sudo /etc/init.d/smbd restart
Sorry, user asep is not allowed to execute '/etc/init.d/smbd restart' as root on localhost.

$ sudo /etc/init.d/smbd stop
Sorry, user asep is not allowed to execute '/etc/init.d/smbd stop' as root on localhost.

$ sudo /etc/init.d/smbd restart

Sorry, user asep is not allowed to execute '/etc/init.d/smbd restart' as root on localhost.

$ sudo /etc/init.d/smbd stop

Sorry, user asep is not allowed to execute '/etc/init.d/smbd stop' as root on localhost.

asep user can only run the command only displays the status of samba.

$ sudo /etc/init.d/smbd status
[sudo] password for calvin:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd status

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status smbd
smbd start/running, process 4026

$ sudo /etc/init.d/smbd status

[sudo] password for calvin:

Rather than invoking init scripts through /etc/init.d, use the service(8)

utility, e.g. service smbd status

Since the script you are attempting to invoke has been converted to an

Upstart job, you may also use the status(8) utility, e.g. status smbd

smbd start/running, process 4026

The third scenario

in order asep users do not need to enter a password when running the sudo command, then in step 2 changed to be like this

asep ALL=NOPASSWD: /etc/init.d/smbd status

$ sudo /etc/init.d/smbd status
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service smbd status

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the status(8) utility, e.g. status smbd
smbd start/running, process 4026

asep ALL=NOPASSWD: /etc/init.d/smbd status

$ sudo /etc/init.d/smbd status

Rather than invoking init scripts through /etc/init.d, use the service(8)

utility, e.g. service smbd status

Since the script you are attempting to invoke has been converted to an

Upstart job, you may also use the status(8) utility, e.g. status smbd

smbd start/running, process 4026

to separate commands dengang another one on writing the file in /etc/sudoers, use a comma. for example:

asep ALL=NOPASSWD: /etc/init.d/smbd status,/etc/init.d/smbd restart,/etc/init.d/smbd stop

1	asep ALL=NOPASSWD: /etc/init.d/smbd status,/etc/init.d/smbd restart,/etc/init.d/smbd stop

Explanation of the sudo command syntax:

asep ALL=(ALL) ALL
[field 1] [field 2] [field 3] [field 4]

Explanation:

[field 1] -> user who would use sudo
[field 2] -> hostname where the computer can run the command
[field 3] -> hostname specific computer or can also be set all
[field 4] -> commands can be executed by the user using sudo

NOTE: do not forget to log into the user’s wise to first to run a sudo command and change the file /etc/ sudoers can direct effect on the PC, so no need to reboot.

{ 0 comments }

CloudLinux and Lightweight Virtual Environment Technology

by asep on March 19, 2011

After trying CloudLinux, it never hurts when I try to share information on this issue, although can not be implemented by all parties at least there are insights to be gained from the development of information technology, especially Linux:)

CloudLinux is an operating system (OS) commercially supported and enabled to be exchanged with the distribution-base RPM (Redhat Package Manager), the most popular. CloudLinux apply Lightweight Virtual Environment Technology (LVE) is a technology that increases the density of server isolation, stability and reliability. LVE limit the amount of resources (CPU, I / O and memory) are available for a particular process or customer / user.

CloudLinux is devoted to the webhosting service providers to provide features that are highly coveted by web hosting providers. CloudLinux very light and transparent, LVE will wrap account is on shared hosting and give control to the hosting provider for CPU resources.

Some things you can do LVE including:

Provide hosting provider control over the CPU resources (I / O and memory limits will be released)
Prevent an account that uses excessive server resources and burden the server performance
Protect your server from the unexpected problems that drain resources
Increase the density so you can have more hosting accounts on one server
Identify the account that excessive use of resources so that you can address their needs
Reduce risk and improve efficiency on a shared server
Improve server performance

CloudLinux designed to surpass the standard OS

Standard OS

Some web sites per server
Each web site can drain resources for various reasons
a single site can overload servers
There is no additional security or protection from hackers or script that drain resources
Improving the efficiency of servers and lowering risk

CloudLinux

Resource wrapped through LVE Technology
LVE websites prevent individuals from using too much resources
Technology LVE provides better security and protect the server from the issues that deplete resources
for other tenants
Single website cannot overload the server
Allows you to maximize the many sites on one server
Reduce risk, improve efficiency and increase server performance

{ 0 comments }

How to Optimize Speed Up Booting Ubuntu

by asep on March 18, 2011

Here I will present how to optimize speed up booting UBuntu, so not much time is wasted just waiting for us ever booting ubuntu

If you feel slow booting Ubuntu, try some of these tricks.

1. Using preload package

preload is a package that is used to optimize the boot process and startup applications. To install the preload run this command in a terminal:

sudo apt-get install preload

1	sudo apt-get install preload

Once installed preload will walk alone, you do not need any configuration, because the developer has optimize preload. Or if you want to know the configuration, open files in /etc/preload.conf

2. Using the profile option on the Grub

You can also create profile your boot, so that future booting will read the saved profile file. To create a profile on the grub boot screen, press e on line

/boot/vmlinuz-2.6.24-16-generic root=UUID=3eb414ba-5198-4c1f-9e3d-e91675329f83 ro splash=verbose vga=794

1	/boot/vmlinuz-2.6.24-16-generic root=UUID=3eb414ba-5198-4c1f-9e3d-e91675329f83 ro splash=verbose vga=794

at the end of the line add the profile. Then press b to booting your system. When the boot process, boot the system will learn what is being done and then will read it back to the booting process next.

3. Disabling IPv6 (if not used)

By default, Ubuntu activate the IPv6 protocol, you must create a file to block this protocol. Type this command in terminal

sudo vi /etc/modprobe.d/bad_list

1	sudo vi /etc/modprobe.d/bad_list

then add the line alias net-pf-10 off then quit with SAVE it, how to: control + c then type “: wq”

4. Using prelink package

install prelink package with the command in terminal
then open the prelink configuration file with the command
Change the line PRELINKING = unknown becomes PRELINKING = yes
To run the prelink run the command in terminal
Next prelink will run a quick prelink every day, usually at night (less than 1 minute), while every 14 days full prelink will run. You can change these prelink time in crontab

sudo apt¬get install prelinksudo vi /etc/default/prelinksudo /etc/cron.daily/prelink

1	sudo apt¬get install prelinksudo vi /etc/default/prelinksudo /etc/cron.daily/prelink

5. Enabling multi-processing (special dual core)

If you have a computer with dual core processor, you can use it to process for faster booting. Open your terminal, then edit the rc file with the command in terminal

sudo vi /etc/init.d/rc

1	sudo vi /etc/init.d/rc

In line CONCURRENCY=none change into CONCURRENCY=shell, then exit with his SAVE it, how to: control + c then type “: wq”

Concurrency own means to do together, in this case the boot process will be conducted simultaneously by two processors so that it could be faster.

Hopefully this tutorial How to Optimize Speed Up Booting Ubuntu, your Ubuntu operating system become more comfortable to wear

source: jauhdimata

{ 0 comments }

Powerful Web Server Using nginx, php5 FastCGI, xcache on ubuntu

by asep on March 16, 2011

Nginx is a powerful web server. few large sites start using this web server. This web server is superior in terms of memory usage and requests can be served

Comparison of the number of requests Apache web server, lighttpd and nginx

From the chart above, it appears that Nginx can serve more requests than the other web server.

In terms of memory usage, nginx also not less powerful in this regard.

Comparison of memory usage

wow .. amazing ..

To install nginx, it can be done easily. I’m using ubuntu linux maverick 10:10

1. Install nginx, php5-fpm, php5-xcache, php5-mysql

#apt-get install nginx php5-fpm php5-xcache php5-mysql

1	#apt-get install nginx php5-fpm php5-xcache php5-mysql

2. Run service php5 fastcgi dan nginx

#service php5-fpm start
#service nginx start

1 2	#service php5-fpm start #service nginx start

php5-fpm is the service to run php as FastCGI. This service will open port 9000. whereas Nginx is a webserver that uses a standard web server port of 80. check port 80 and 9000 whether or not already listen

#netstat -ntlp

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID
/Program
name
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      4751
/nginx
tcp        0      0 10.204.7.204:53         0.0.0.0:*               LISTEN      1561
/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1561/named
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1160/cupsd
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      1561/named
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      4016/php5-fpm
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      1341/mysqld
tcp6       0      0 :::80                   :::*                    LISTEN      4751/nginx
tcp6       0      0 :::53                   :::*                    LISTEN      1561/named
tcp6       0      0 ::1:631                 :::*                    LISTEN      1160/cupsd
tcp6       0      0 ::1:953                 :::*                    LISTEN      1561/named

#netstat -ntlp

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address Foreign Address State PID

/Program

name

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 4751

/nginx

tcp 0 0 10.204.7.204:53 0.0.0.0:* LISTEN 1561

/named

tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1561/named

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1160/cupsd

tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1561/named

tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 4016/php5-fpm

tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1341/mysqld

tcp6 0 0 :::80 :::* LISTEN 4751/nginx

tcp6 0 0 :::53 :::* LISTEN 1561/named

tcp6 0 0 ::1:631 :::* LISTEN 1160/cupsd

tcp6 0 0 ::1:953 :::* LISTEN 1561/named

port 80 and port 9000 already listen

3. Change the nginx configuration for processing documents with extensi.php to be processed by php-FastCGI service

# vi /etc/nginx/sites-available/defa

1	# vi /etc/nginx/sites-available/defa

Please be as follows, namely by removing the remark and changing some directory locations.

        location ~ .php$ {
                fastcgi_pass   127.0.0.1:9000;
                fastcgi_index  index.php;
                fastcgi_param  SCRIPT_FILENAME  /var/www$fastcgi_script_name;
                include fastcgi_params;
        }

location ~ .php$ {

fastcgi_pass 127.0.0.1:9000;

fastcgi_index index.php;

fastcgi_param SCRIPT_FILENAME /var/www$fastcgi_script_name;

include fastcgi_params;

}

4. Restart nginx #service nginx restart 5. We test. Create the file /var/www/info.php with the following contents:

Access via browser http://localhost/info.php

TIME benchmarking

Let us compare the performance between the apache with nginx. tool use is apache-bench. This tool is included in the package apache2-utils. how to check:

# ab -n 100 -c 5 http://localhost/test.php

1	# ab -n 100 -c 5 http://localhost/test.php

Nginx result:

Server Software:        nginx/0.7.67
Server Hostname:        localhost
Server Port:            80
Document Path:          /test.php
Document Length:        12 bytes
Concurrency Level:      5
Time taken for tests:   45.054 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      17000 bytes
HTML transferred:       1200 bytes
Requests per second:    2.22 [#/sec] (mean)
Time per request:       2252.722 [ms] (mean)
Time per request:       450.544 [ms] (mean, across all concurrent requests)
Transfer rate:          0.37 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    0   0.1      0       0
Processing:  1332 2235 239.4   2248    2740
Waiting:     1332 2235 239.4   2248    2740
Total:       1332 2235 239.4   2248    2740
Percentage of the requests served within a certain time (ms)
50%   2248
66%   2330
75%   2432
80%   2469
90%   2540
95%   2622
98%   2688
99%   2740
100%   2740 (longest request)

Server Software: nginx/0.7.67

Server Hostname: localhost

Server Port: 80

Document Path: /test.php

Document Length: 12 bytes

Concurrency Level: 5

Time taken for tests: 45.054 seconds

Complete requests: 100

Failed requests: 0

Write errors: 0

Total transferred: 17000 bytes

HTML transferred: 1200 bytes

Requests per second: 2.22 [#/sec] (mean)

Time per request: 2252.722 [ms] (mean)

Time per request: 450.544 [ms] (mean, across all concurrent requests)

Transfer rate: 0.37 [Kbytes/sec] received

Connection Times (ms)

min mean[+/-sd] median max

Connect: 0 0 0.1 0 0

Processing: 1332 2235 239.4 2248 2740

Waiting: 1332 2235 239.4 2248 2740

Total: 1332 2235 239.4 2248 2740

Percentage of the requests served within a certain time (ms)

50% 2248

66% 2330

75% 2432

80% 2469

90% 2540

95% 2622

98% 2688

99% 2740

100% 2740 (longest request)

Turn off nginx, restart apache and this is the test results.

Apache Results

Server Software:        Apache/2.2.16
Server Hostname:        localhost
Server Port:            80
Document Path:          /test.php
Document Length:        12 bytes
Concurrency Level:      5
Time taken for tests:   44.936 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      22300 bytes
HTML transferred:       1200 bytes
Requests per second:    2.23 [#/sec] (mean)
Time per request:       2246.804 [ms] (mean)
Time per request:       449.361 [ms] (mean, across all concurrent requests)
Transfer rate:          0.48 [Kbytes/sec] received
Connection Times (ms)
min  mean[+/-sd] median   max
Connect:        0    0   0.3      0       3
Processing:  1304 2229 242.7   2272    2752
Waiting:     1304 2229 242.8   2272    2751
Total:       1304 2229 242.7   2272    2752
Percentage of the requests served within a certain time (ms)
50%   2272
66%   2331
75%   2366
80%   2390
90%   2543
95%   2612
98%   2674
99%   2752
100%   2752 (longest request)

Server Software: Apache/2.2.16

Server Hostname: localhost

Server Port: 80

Document Path: /test.php

Document Length: 12 bytes

Concurrency Level: 5

Time taken for tests: 44.936 seconds

Complete requests: 100

Failed requests: 0

Write errors: 0

Total transferred: 22300 bytes

HTML transferred: 1200 bytes

Requests per second: 2.23 [#/sec] (mean)

Time per request: 2246.804 [ms] (mean)

Time per request: 449.361 [ms] (mean, across all concurrent requests)

Transfer rate: 0.48 [Kbytes/sec] received

Connection Times (ms)

min mean[+/-sd] median max

Connect: 0 0 0.3 0 3

Processing: 1304 2229 242.7 2272 2752

Waiting: 1304 2229 242.8 2272 2751

Total: 1304 2229 242.7 2272 2752

Percentage of the requests served within a certain time (ms)

50% 2272

66% 2331

75% 2366

80% 2390

90% 2543

95% 2612

98% 2674

99% 2752

100% 2752 (longest request)

So little information about how Powerful Web Server Using nginx, php5 FastCGI, xcache on ubuntu 10.10 that when compared to Apache

source: taujago.web.id

{ 0 comments }

Synchronize Folders on Windows, Mac, and Linux

by asep on March 16, 2011

How (using what is) the best way to synchronize folders in Windows, Mac, and Linux?

The story I have a folder that I used to teach college. Sometimes I work on a desktop computer running Windows and Linux. Meanwhile, if I’m moving (mobile) and chase, I use Linux. Synchronization is done manually, i.e. by creating a duplicate in each computer. Well, files are often scattered. On one machine there is a file that has not been updated and so forth. Chaotic …

Wish there are applications that can perform such synchronization. Yes there is, but usually only one platform only. Is there for a multiplatform?

{ 0 comments }

How to Set Up a Web Server using Webmin on CentOS

by asep on March 15, 2011

Now I will try for a bit of explaining how to set up a web server using webmin on CentOS, for those of you who want to save costs, webmin is a solution for you, but if you have more funds, use the cpanel is a solution that is easier to set up a web server.

The steps to install webmin on CentOS is as follows:

1. Install Webmin (if you have money rental CPanel / WHM more comfortable and easy to use as the beginning). Webmin is used to manage servers easily without having to always type the command in a shell. Check the latest Webmin RPM at webmin official website.

yum -y install perl-Net-SSLeay

cd /tmp

wget http://prdownloads.sourceforge.net/webadmin/webmin-1.530-1.noarch.rpm

rpm – i webmin-1.530-1.noarch.rpm

/etc/init.d/webmin start

/usr/libexec/webmin/changepass.pl /etc/webmin admin <strong>new_password</strong>

yum -y install perl-Net-SSLeay

cd /tmp

wget http://prdownloads.sourceforge.net/webadmin/webmin-1.530-1.noarch.rpm

rpm – i webmin-1.530-1.noarch.rpm

/etc/init.d/webmin start

/usr/libexec/webmin/changepass.pl /etc/webmin admin <strong>new_password</strong>

2. Open a browser go to: http://yourIP:10000 and then Login with username admin and password in accordance with new_password.

3. Install Apache

Click the Server-> Apache Webserver. There is a section labeled “Click here to have it downloaded and installed using YUM.”

Click there, going to install the Apache web server quickly and automatically.

Click the Start button after confirming a successful installation.

4. Install MySQL

Click the Server-> MySQL Database Server. There is a section labeled “Click here to have it downloaded and installed using YUM.”

Click there and going to install the MySQL Server on the web server quickly and automatically.

Click the Start button after confirming a successful installation.

5. Install PHP5

Back to Putty and enter the following command.

yum install php php-mysql php-common php-gd php-mbstring php-mcrypt php-devel php-xml

1	yum install php php-mysql php-common php-gd php-mbstring php-mcrypt php-devel php-xml

/etc/init.d/httpd restart

1	/etc/init.d/httpd restart

6. PHP Test

Create a PHP file and test whether all that we’ve successfully installed and running well.

vi /var/www/html/index.php

1	vi /var/www/html/index.php

Type

Press ESC
:w ENTER
:q ENTER

7. Return to the browser and go to http://yourIP/

If you see the display info from PHP then all the above installation has been completed successfully.

Take a break or go directly to the installation of Bind DNS and Virtual Host settings

8. Install Bind DNS

Back to the Webmin pages. Go to the menu server-> Bind DNS. There are papers “Click here to have it downloaded and installed using YUM.”
Click there and to install the Bind will quickly and automatically. Once completed there is a choice answers, select the answer number 2 or another number, which means “Used to control the Internet and the Download Zone.” Then press the Start button.

9. Setting domain name
Assumed to have registered a domain name: asep.us
Register ns1.asep.us and ns2.asep.us given to a dedicated IP. Register at the domain registrar where you have registered domain. After that point asep.us name servers to ns1.asep.us and ns2.asep.us

10. Back to page Webmin

Click the Server-> Bind DNS

Click the “Edit Config Files” and add the following to it and press SAVE

zone “asep.us” {
type master;
file “asep.us.hosts”;
};

zone “asep.us” {

type master;

file “asep.us.hosts”;

};

11. Back to Shell. Create a new file as an example the number 6 with name asep.us.host in /etc/

vi /etc/asep.us.hosts

1	vi /etc/asep.us.hosts

File content

$TTL 86400
@ IN SOA ns1.asep.us. server.asep.us. (
2008081301 ; serial, todays date + todays serial #
28800 ; refresh, seconds
7200 ; retry, seconds
604800 ; expire, seconds
86400 ) ; minimum, seconds;
asep.us. NS ns1.asep.us.
asep.us. NS ns2.asep.us.
ns1 A 123.123.123.123
ns2 A 123.123.123.123
asep.us. A 123.123.123.123
www A 123.123.123.123
ftp A 123.123.123.123

$TTL 86400

@ IN SOA ns1.asep.us. server.asep.us. (

2008081301 ; serial, todays date + todays serial #

28800 ; refresh, seconds

7200 ; retry, seconds

604800 ; expire, seconds

86400 ) ; minimum, seconds;

asep.us. NS ns1.asep.us.

asep.us. NS ns2.asep.us.

ns1 A 123.123.123.123

ns2 A 123.123.123.123

asep.us. A 123.123.123.123

www A 123.123.123.123

ftp A 123.123.123.123

Replace server.asep.us accordance with the name server that gives a chance and 123.123.123.123 provided with a dedicated IP. Save and restart Bind

/etc/init.d/named restart

1	/etc/init.d/named restart

12. Install Virtual Host.

Back to the Webmin menu and click Server-Apache WebServer – Global Configuratin.

Click on Edit Config Files. Add at the bottom section of this field

DocumentRoot /var/www/html/asepus
ServerAdmin admin@asep.us
ServerName www.asep.id
ServerAlias asep.us
DirectoryIndex index.html index.htm <a href="http://www.info-vijesti.com/">index</a>.shtml index.php

Options all
AllowOverride none

LogLevel debug
HostNameLookups off

DocumentRoot /var/www/html/asepus

ServerAdmin admin@asep.us

ServerName www.asep.id

ServerAlias asep.us

DirectoryIndex index.html index.htm <a href="http://www.info-vijesti.com/">index</a>.shtml index.php

Options all

AllowOverride none

LogLevel debug

HostNameLookups off

Save and restart Apache Server.

13. Creating Index file to asep.us

Go Putty. Create a new file like the example at number 6 with name of the index.php in the folder /var/www/html/asepus

cd /var/www/html
mkdir asepus
vi /var/www/html/asepus/index.php

cd /var/www/html

mkdir asepus

vi /var/www/html/asepus/index.php

the content of file:

Save the file you just created.

14. Test all results.

Repeat step 7. If the browser’s appearance changed to the words “Welcome to ASEP.US” then everything above is 99% successful.

Enter in your browser https://www.asep.id/ or http://asep.us should display in the browser will still show the words “Welcome to ASEP.US”. If the exit “Server Not Found” do not rush to worried. The possibility of a new domain name gives a chance at number 9 and Bind DNS is still not resolved. Just wait for about 2-6 hours and try again. If after 24 hours was also “Server not Found”, then it’s time to worry about finding fault where.

Enjoy your Web Server.

How to Set Up a Web Server using Webmin on CentOS is still ignoring the various security holes that occur because the setting is still the standard PHP and MySQL. For security issue, Google has a lot of stories and articles.

{ 1 comment }

Next Posts Previous Posts