제2의 비엔지니어 인생관을 꿈꾸며

Posted
Filed under Study

sudo apt-get update –fix-missing

and

sudo dpkg –configure -a

and

sudo apt-get install -f

the problem of a broken package still exist the solution is to edit the dpkg status file manually.

 

  1. $ sudo nano /var/lib/dpkg/status    (you can use vim or gedit instead of nano)
  2. Locate the corrupt package, and remove the whole block of information about it and save the file.

———–

Unlock the dpkg – (message /var/lib/dpkg/lock)

sudo fuser -vki /var/lib/dpkg/lock

sudo dpkg –configure -a

 

For 12.04 and newer:

You can delete the lock file with the following command:

sudo rm /var/lib/apt/lists/lock

You may also need to delete the lock file in the cache directory

sudo rm /var/cache/apt/archives/lock

2017/02/03 15:42 2017/02/03 15:42
Posted
Filed under Study

 — Create New Virtual Host Files

Virtual host files are the files that specify the actual configuration of our virtual hosts and dictate how the Apache web server will respond to various domain requests.

Apache comes with a default virtual host file called 000-default.conf that we can use as a jumping off point. We are going to copy it over to create a virtual host file for each of our domains.

We will start with one domain, configure it, copy it for our second domain, and then make the few further adjustments needed. The default Ubuntu configuration requires that each virtual host file end in .conf.

Create the First Virtual Host File

Start by copying the file for the first domain:
sudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/yourdomain.com.conf


Open the new file in your editor with root privileges:
sudo nano /etc/apache2/sites-available/yourdomain.com.conf


The file will look something like this (I've removed the comments here to make the file more approachable):
<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>


As you can see, there's not much here. We will customize the items here for our first domain and add some additional directives. This virtual host section matches any requests that are made on port 80, the default HTTP port.

First, we need to change the ServerAdmin directive to an email that the site administrator can receive emails through.
ServerAdmin admin@yourdomain.com


After this, we need to add two directives. The first, called ServerName, establishes the base domain that should match for this virtual host definition. This will most likely be your domain. The second, called ServerAlias, defines further names that should match as if they were the base name. This is useful for matching hosts you defined, like www:
ServerName yourdomain.com
ServerAlias www.yourdomain.com


The only other thing we need to change for a basic virtual host file is the location of the document root for this domain. We already created the directory we need, so we just need to alter the DocumentRoot directive to reflect the directory we created:
DocumentRoot /var/www/yourdomain.com/public_html


In total, our virtualhost file should look like this:
<VirtualHost *:80>
    ServerAdmin admin@yourdomain.com
    ServerName yourdomain.com
    ServerAlias www.yourdomain.com
    DocumentRoot /var/www/yourdomain.com/public_html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>


Save and close the file.

Copy First Virtual Host and Customize for Second Domain

Now that we have our first virtual host file established, we can create our second one by copying that file and adjusting it as needed.

Start by copying it:
sudo cp /etc/apache2/sites-available/yourdomain.com.conf /etc/apache2/sites-available/test.com.conf


Open the new file with root privileges in your editor:
sudo nano /etc/apache2/sites-available/test.com.conf


You now need to modify all of the pieces of information to reference your second domain. When you are finished, it may look something like this:
<VirtualHost *:80>
    ServerAdmin admin@test.com
    ServerName test.com
    ServerAlias www.test.com
    DocumentRoot /var/www/test.com/public_html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>


Save and close the file when you are finished.


 — Enable the New Virtual Host Files

Now that we have created our virtual host files, we must enable them. Apache includes some tools that allow us to do this.

We can use the a2ensite tool to enable each of our sites like this:
sudo a2ensite yourdomain.com.conf
sudo a2ensite test.com.conf


When you are finished, you need to restart Apache to make these changes take effect:
sudo service apache2 restart


You will most likely receive a message saying something similar to:
 * Restarting web server apache2
 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1. Set the 'ServerName' directive globally to suppress this message


This is a harmless message that does not affect our site.


— Set Up Local Hosts File (Optional)

If you haven't been using actual domain names that you own to test this procedure and have been using some example domains instead, you can at least test the functionality of this process by temporarily modifying the hosts file on your local computer.

This will intercept any requests for the domains that you configured and point them to your VPS server, just as the DNS system would do if you were using registered domains. This will only work from your computer though, and is simply useful for testing purposes.

Make sure you are operating on your local computer for these steps and not your VPS server. You will need to know the computer's administrative password or otherwise be a member of the administrative group.

If you are on a Mac or Linux computer, edit your local file with administrative privileges by typing:
sudo nano /etc/hosts


If you are on a Windows machine, you can find instructions on altering your hosts file here.

The details that you need to add are the public IP address of your VPS server followed by the domain you want to use to reach that VPS.

For the domains that I used in this guide, assuming that my VPS IP address is 111.111.111.111, I could add the following lines to the bottom of my hosts file:
127.0.0.1   localhost
127.0.1.1   guest-desktop
111.111.111.111 yourdomain.com
111.111.111.111 test.com


This will direct any requests for yourdomain.com and test.com on our computer and send them to our server at 111.111.111.111. This is what we want if we are not actually the owners of these domains in order to test our virtual hosts.

Save and close the file.

To remove the host file just delete it.

If you just want to dissable the site, use

Code:
sudo a2dissite sitename

Restart apache2

Code:
sudo /etc/init.d/apache2 reload

Again to remove (delete)it completely from the system,

Code:
sudo rm /etc/apache2/sites-available/sitename

 

2015/07/16 14:22 2015/07/16 14:22
Posted
Filed under Study
http://www.canonical.com/about-canonic ··· 1204-lts
 
Hyper-V 2012 에서는 통합드라이버 설치 없이 바로 우분투 리눅스를 사용할수 있습니다. CentOS 설치에서 하라는데로 따라 했는데도 드라이버 설치를 못해 결국은 우분투로 이전을 하였는데 Apache, PHP, Sendmail 설치가 용이하고 Centos 와 크게 다를게 없어서 금방 다루는데 익숙해졌습니다. FTP 보안을 강화해서 이슈가 존재하고 리부팅하면 nameserver입력란에 resolv.conf 초기화가 되는 약간 불편한게 존재하기도 하지만 크게 문제가 되지는 않습니다. 현재 이 블로그도 우분투 12.04 버젼으로 운영이 되고 있습니다. vsFTP 보안 문제로 하루 온종일 삽질하다 결국 GG쳐서 그냥 보안 강화된데로 사용을 하고 있습니다.
2012/10/09 09:28 2012/10/09 09:28