'ITWeb/서버관리'에 해당되는 글 125건

  1. 2012.04.18 Life With Qmail - from KLDP
  2. 2012.04.18 solr 문서보고 무작정 따라하기.
  3. 2012.04.17 메일서버 구축 및 개발을 위한 정보 (링크만)
  4. 2012.04.16 SVN branching & merging by Eclipse.
  5. 2012.04.16 우분투에 SVN 설치하기.
  6. 2012.04.10 Tomcat 관련 Articles.
  7. 2012.04.10 How Email Works, MX Record
  8. 2012.04.10 nslookup 으로 MX Record 확인하기.
  9. 2012.04.10 Finding and testing your MX (mail) records
  10. 2012.04.05 [IBM] Overview mail server architecture ....

Life With Qmail - from KLDP

ITWeb/서버관리 2012. 4. 18. 22:48

메일서비스 개발을 해야 하다 보니.. 봐야 할게 많내요.. 
일단 필요하다 싶은건 다 모아봅시다... 


[원본글]

http://wiki.kldp.org/Translations/Life_With_Qmail-KLDP


[번역글]


:

solr 문서보고 무작정 따라하기.

ITWeb/서버관리 2012. 4. 18. 15:11

solr 설치 문서는 정말 잘 정리 되어 있습니다.
그냥 문서만 보고 따라 하시면 누구나 쉽게 설치해서 정상적인 화면을 확인 하실 수 있으니 한번 해보세요.
설치 링크 정보는 이전 글 참고 하시면 됩니다.

http://jjeong.tistory.com/639

제가 문서 보고 따라한거 그대로 스크랩 합니다.
아 그리고 저는 tomcat, jdk 모두 매뉴얼 설치로 테스트 했습니다.

[Solr Tutorial]

Solr Tutorial

Overview

This document covers the basics of running Solr using an example schema, and some sample data.

Requirements

To follow along with this tutorial, you will need...

  1. Java 1.5 or greater. Some places you can get it are from Oracle, Open JDK, IBM, or 
    Running java -version at the command line should indicate a version number starting with 1.5. Gnu's GCJ is not supported and does not work with Solr.
  2. A Solr release.

Getting Started

Please run the browser showing this tutorial and the Solr server on the same machine so tutorial links will correctly point to your Solr server.

Begin by unziping the Solr release and changing your working directory to be the "example" directory. (Note that the base directory name may vary with the version of Solr downloaded.) For example, with a shell in UNIX, Cygwin, or MacOS:

user:~solr$ ls
solr-nightly.zip
user:~solr$ unzip -q solr-nightly.zip
user:~solr$ cd solr-nightly/example/

Solr can run in any Java Servlet Container of your choice, but to simplify this tutorial, the example index includes a small installation of Jetty.

To launch Jetty with the Solr WAR, and the example configs, just run the start.jar ...

user:~/solr/example$ java -jar start.jar
2012-03-27 17:11:29.529:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
2012-03-27 17:11:29.696:INFO::jetty-6.1-SNAPSHOT
...
2012-03-27 17:11:32.343:INFO::Started SocketConnector@0.0.0.0:8983

This will start up the Jetty application server on port 8983, and use your terminal to display the logging information from Solr.

You can see that the Solr is running by loading http://localhost:8983/solr/admin/ in your web browser. This is the main starting point for Administering Solr.

Indexing Data

Your Solr server is up and running, but it doesn't contain any data. You can modify a Solr index by POSTing XML Documents containing instructions to add (or update) documents, delete documents, commit pending adds and deletes, and optimize your index.

The exampledocs directory contains samples of the types of instructions Solr expects, as well as a java utility for posting them from the command line (a post.sh shell script is also available, but for this tutorial we'll use the cross-platform Java client).

To try this, open a new terminal window, enter the exampledocs directory, and run "java -jar post.jar" on some of the XML files in that directory, indicating the URL of the Solr server:

user:~/solr/example/exampledocs$ java -jar post.jar solr.xml monitor.xml
SimplePostTool: version 1.4
SimplePostTool: POSTing files to http://localhost:8983/solr/update..
SimplePostTool: POSTing file solr.xml
SimplePostTool: POSTing file monitor.xml
SimplePostTool: COMMITting Solr index changes..

You have now indexed two documents in Solr, and committed these changes. You can now search for "solr" using the "Make a Query" interface on the Admin screen, and you should get one result. Clicking the "Search" button should take you to the following URL...

http://localhost:8983/solr/select/?q=solr&start=0&rows=10&indent=on

You can index all of the sample data, using the following command (assuming your command line shell supports the *.xml notation):

user:~/solr/example/exampledocs$ java -jar post.jar *.xml
SimplePostTool: version 1.4
SimplePostTool: POSTing files to http://localhost:8983/solr/update..
SimplePostTool: POSTing file gb18030-example.xml
SimplePostTool: POSTing file hd.xml
SimplePostTool: POSTing file ipod_other.xml
SimplePostTool: POSTing file ipod_video.xml
SimplePostTool: POSTing file mem.xml
SimplePostTool: POSTing file money.xml
SimplePostTool: POSTing file monitor2.xml
SimplePostTool: POSTing file monitor.xml
SimplePostTool: POSTing file mp500.xml
SimplePostTool: POSTing file sd500.xml
SimplePostTool: POSTing file solr.xml
SimplePostTool: POSTing file utf8-example.xml
SimplePostTool: POSTing file vidcard.xml
SimplePostTool: COMMITting Solr index changes..

...and now you can search for all sorts of things using the default Solr Query Syntax (a superset of the Lucene query syntax)...

There are many other different ways to import your data into Solr... one can

Updating Data

You may have noticed that even though the file solr.xml has now been POSTed to the server twice, you still only get 1 result when searching for "solr". This is because the example schema.xml specifies a "uniqueKey" field called "id". Whenever you POST instructions to Solr to add a document with the same value for the uniqueKey as an existing document, it automatically replaces it for you. You can see that that has happened by looking at the values for numDocs and maxDoc in the "CORE"/searcher section of the statistics page...

http://localhost:8983/solr/admin/stats.jsp

numDocs represents the number of searchable documents in the index (and will be larger than the number of XML files since some files contained more than one <doc>). maxDoc may be larger as the maxDoc count includes logically deleted documents that have not yet been removed from the index. You can re-post the sample XML files over and over again as much as you want and numDocs will never increase, because the new documents will constantly be replacing the old.

Go ahead and edit the existing XML files to change some of the data, and re-run the java -jar post.jar command, you'll see your changes reflected in subsequent searches.

Deleting Data

You can delete data by POSTing a delete command to the update URL and specifying the value of the document's unique key field, or a query that matches multiple documents (be careful with that one!). Since these commands are smaller, we will specify them right on the command line rather than reference an XML file.

Execute the following command to delete a document

java -Ddata=args -Dcommit=no -jar post.jar "<delete><id>SP2514N</id></delete>"

Now if you go to the statistics page and scroll down to the UPDATE_HANDLERS section and verify that "deletesById : 1"

If you search for id:SP2514N it will still be found, because index changes are not visible until changes are committed and a new searcher is opened. To cause this to happen, send a commit command to Solr (post.jar does this for you by default):

java -jar post.jar

Now re-execute the previous search and verify that no matching documents are found. Also revisit the statistics page and observe the changes in both the UPDATE_HANDLERS section and the CORE section.

Here is an example of using delete-by-query to delete anything with DDR in the name:

java -Ddata=args -jar post.jar "<delete><query>name:DDR</query></delete>"

Commit can be an expensive operation so it's best to make many changes to an index in a batch and then send the commit command at the end. There is also an optimize command that does the same thing as commit, in addition to merging all index segments into a single segment, making it faster to search and causing any deleted documents to be removed. All of the update commands are documented here.

To continue with the tutorial, re-add any documents you may have deleted by going to the exampledocs directory and executing

java -jar post.jar *.xml

Querying Data

Searches are done via HTTP GET on the select URL with the query string in the q parameter. You can pass a number of optional request parameters to the request handler to control what information is returned. For example, you can use the "fl" parameter to control what stored fields are returned, and if the relevancy score is returned:

Solr provides a query form within the web admin interface that allows setting the various request parameters and is useful when testing or debugging queries.

Sorting

Solr provides a simple method to sort on one or more indexed fields. Use the "sort' parameter to specify "field direction" pairs, separated by commas if there's more than one sort field:

"score" can also be used as a field name when specifying a sort:

Complex functions may also be used to sort results:

If no sort is specified, the default is score desc to return the matches having the highest relevancy.

Highlighting

Hit highlighting returns relevent snippets of each returned document, and highlights terms from the query within those context snippets.

The following example searches for video card and requests highlighting on the fields name,features. This causes a highlighting section to be added to the response with the words to highlight surrounded with <em> (for emphasis) tags.

...&q=video card&fl=name,id&hl=true&hl.fl=name,features

More request parameters related to controlling highlighting may be found here.

Faceted Search

Faceted search takes the documents matched by a query and generates counts for various properties or categories. Links are usually provided that allows users to "drill down" or refine their search results based on the returned categories.

The following example searches for all documents (*:*) and requests counts by the category field cat.

...&q=*:*&facet=true&facet.field=cat

Notice that although only the first 10 documents are returned in the results list, the facet counts generated are for the complete set of documents that match the query.

We can facet multiple ways at the same time. The following example adds a facet on the boolean inStock field:

...&q=*:*&facet=true&facet.field=cat&facet.field=inStock

Solr can also generate counts for arbitrary queries. The following example queries for ipod and shows prices below and above 100 by using range queries on the price field.

...&q=ipod&facet=true&facet.query=price:[0 TO 100]&facet.query=price:[100 TO *]

One can even facet by date ranges. This example requests counts for the manufacture date (manufacturedate_dt field) for each year between 2004 and 2010.

...&q=*:*&facet=true&facet.date=manufacturedate_dt&facet.date.start=2004-01-01T00:00:00Z&facet.date.end=2010-01-01T00:00:00Z&facet.date.gap=+1YEAR

More information on faceted search may be found on the faceting overview and faceting parameterspages.

Search UI

Solr includes an example search interface built with velocity templating that demonstrates many features, including searching, faceting, highlighting, autocomplete, and geospatial searching.

Try it out at http://localhost:8983/solr/browse

Text Analysis

Text fields are typically indexed by breaking the text into words and applying various transformations such as lowercasing, removing plurals, or stemming to increase relevancy. The same text transformations are normally applied to any queries in order to match what is indexed.

The schema defines the fields in the index and what type of analysis is applied to them. The current schema your server is using may be accessed via the [SCHEMA] link on the admin page.

The best analysis components (tokenization and filtering) for your textual content depends heavily on language. As you can see in the above [SCHEMA] link, the fields in the example schema are using a fieldType named text_general, which has defaults appropriate for all languages.

If you know your textual content is English, as is the case for the example documents in this tutorial, and you'd like to apply English-specific stemming and stop word removal, as well as split compound words, you can use the text_en_splitting fieldType instead. Go ahead and edit the schema.xml in thesolr/example/solr/conf directory, to use the text_en_splitting fieldType for the text and features fields like so:

   <field name="features" type="text_en_splitting" indexed="true" stored="true" multiValued="true"/>
   ...
   <field name="text" type="text_en_splitting" indexed="true" stored="false" multiValued="true"/>

Stop and restart Solr after making these changes and then re-post all of the example documents usingjava -jar post.jar *.xml. Now queries like the ones listed below will demonstrate English-specific transformations:

  • A search for power-shot can match PowerShot, and adata can match A-DATA by using theWordDelimiterFilter and LowerCaseFilter.
  • A search for features:recharging can match Rechargeable using the stemming features of PorterStemFilter.
  • A search for "1 gigabyte" can match 1GB, and the commonly misspelled pixima can matches Pixma using the SynonymFilter.

A full description of the analysis components, Analyzers, Tokenizers, and TokenFilters available for use is here.

Analysis Debugging

There is a handy analysis debugging page where you can see how a text value is broken down into words, and shows the resulting tokens after they pass through each filter in the chain.

This url shows how "Canon Power-Shot SD500" would shows the tokens that would be instead be created using the text_en_splitting type. Each row of the table shows the resulting tokens after having passed through the next TokenFilter in the analyzer. Notice how both powershot and power, shot are indexed. Tokens generated at the same position are shown in the same column, in this case shot and powershot. (Compare the previous output with The tokens produced using the text_general field type.)

Selecting verbose output will show more details, such as the name of each analyzer component in the chain, token positions, and the start and end positions of the token in the original text.

Selecting highlight matches when both index and query values are provided will take the resulting terms from the query value and highlight all matches in the index value analysis.

Other interesting examples:

Conclusion

Congratulations! You successfully ran a small Solr instance, added some documents, and made changes to the index and schema. You learned about queries, text analysis, and the Solr admin interface. You're ready to start using Solr on your own project! Continue on with the following steps:

  • Subscribe to the Solr mailing lists!
  • Make a copy of the Solr example directory as a template for your project.
  • Customize the schema and other config in solr/conf/ to meet your needs.

Solr has a ton of other features that we haven't touched on here, including distributed search to handle huge document collections, function queries, numeric field statistics, and search results clustering. Explore the Solr Wiki to find more details about Solr's many features.

Have Fun, and we'll see you on the Solr mailing lists!


[Installing Solr on Ubuntu Linux]

Installing Solr on Ubuntu Linux

Following are instructions for installing the Solr search server on Ubuntu linux. There are several manual steps in setting up Solr, and most of the other documents I came across on the internet are inadequate in some (or in many) ways so I enlisted the help of colleagues and documented the steps start-to-finish here. 

I found Solr not to my liking, encountering significant scaling issues while indexing beyond 4-5 million small documents and so I've abandoned this application in favor of more standard/robust solutions with a far larger community (e.g. mySQL) and more ubiquitous technology with long evolutionary histories (RDBMS) behind them. The problem of indexing XML documents is best solved by avoidance. Digitally born data should exist in normalized and relational states from the get-go. 

These instructions have been tested with Hardy Heron 8.04, and will likely work with other recent versions of Ubuntu and Debian-based distros with little or no modification.

Before You Start
Solr can be setup several ways -- these instructions lead up to a Solr environment deployed in Tomcat, with separate development and production areas. Once you've done this a couple times (or carefully read this document a few times), you could set up three environments, just one, or whatever layout suits your needs. There are hardcoded pathing dependencies of which you need to be aware. 

(1) Download and install the latest JDK from Sun.

You'll want to get the latest Java JDK from Sun http://java.sun.com/javase/downloads/index.jsp and install it first. At the time these instructions were written, I had installed Sun's jdk1.6.0_10. I'm unsure if it's required, but I also made sure that "ant" was installed on my Ubuntu box (for ant, I simply used Ubuntu's handy package installer Synaptic). 

I downloaded the Sun JDK to my user home directory and chmod +x'd the .bin exectuable. I sudo'd to root and executed the file. It made me scroll through the license agreement and decompressed itself. I then mv'd it to /opt/jdk1.6.0_10. 

Java needs at least two environment settings in order to be useful. You'll eventually need to set up CLASSPATH as well, but that's not essential for the instructions in this document. I made the following .bashrc additions to both my ordinary user account (/home/{username}/.bashrc), as well as for the root account (/root/.bashrc). Go into each .bashrc file and add the following (which may be slightly different if you chose a different location or have a different version of the JDK): 

export PATH=/opt/jdk1.6.0_10/bin:$PATH
export JAVA_HOME=/opt/jdk1.6.0_10

Whenever you make changes to .bashrc you should issue a "source .bashrc" to instruct the shell to re-read the file (otherwise you'd have to logout, and then log back in). You should now be able to type "which java" and see something like this: /opt/jdk1.6.0_10/bin/java, depending on the version you downloaded. 

(2) Download and install the latest Tomcat.

Rather than lean on the Tomcat 5.5 version which was part of the Ubuntu repositories at the time of this writing, I downloaded the latest Tomcat: http://tomcat.apache.org. I brought it down to my user directory, decompressing it via gunzip and "tar xvf". It creates a Tomcat directory, populated with everything it needs. 

As you use Tomcat over the lifespan of your project/development you may want a more succinct name than something like "apache-tomcat-6.0.16" so I decided to rename (mv) this directory to simply "tomcat6". The instructions which follow in this document will use that abbreviated "tomcat6" convention. 

I then did this:

sudo su
mv tomcat6 /usr/local/

You can move it somewhere else -- I picked this location because a colleague who led me through most of these steps put it in that location on his box and I decided to remain consistent with his setup. Maybe you want it in /usr/share/ or somewhere else. Before going further, you should test Tomcat. At this stage, I'm still sudo'd as root. 

cd /usr/local/tomcat6/bin
./startup.sh

You should see a message like this:
Using CATALINA_BASE:   /usr/local/tomcat6
Using CATALINA_HOME:   /usr/local/tomcat6
Using CATALINA_TMPDIR: /usr/local/tomcat6/temp
Using JRE_HOME:       /opt/jdk1.6.0_10
(Note that JRE_HOME is the location of the Sun JDK installed in an earlier step. You really need this -- if Tomcat is aimed at a JRE that you don't want, or can't find it, you can't go any further.) Eventually you'll probably want to create a Tomcat specific user, and give it appropriate/minimal rights, instead of using root. 

Go to your browser and type this: 

http://localhost:8080/

Go to Tomcat servlet examples and click a couple of them, click a couple jsp examples also. They should execute without complaining. At this stage we've installed the latest JDK, the latest Tomcat, and things are talking to one another. If you're getting something wildly different, you can't go any further here. In order to complete this document, it should be "all systems go" at this point. 

Before going further, you should shut Tomcat back down:

cd /usr/local/tomcat6/bin
./shutdown.sh

(3) Download and install Solr

I downloaded the latest Solr here: http://www.apache.org/dyn/closer.cgi/lucene/solr/. As with Tomcat, I issued gunzip and "tar xvf" to decompress it to my home user directory. It creates a directory called "apache-solr-1.2.0". 

We need to manually create some directories within /usr/local/tomcat6. This setup will yield us two Solr locations within your Tomcat instance: one for development, another for production. There are other ways to set up Solr, but if this is your first attempt you may want to follow this convention. It's unclear why /Catalina and /Catalina/localhost aren't created automatically with a Tomcat install. Probably just to keep our salaries up. The /data/solr directory, as you can see, will have an identical structure below it for dev and prod. Each of those directories additionally has corresponding /conf and /data directories below it. 

Make these directories: 

/usr/local/tomcat6/conf/Catalina
/usr/local/tomcat6/conf/Catalina/localhost
/usr/local/tomcat6/data
/usr/local/tomcat6/data/solr
/usr/local/tomcat6/data/solr/dev
/usr/local/tomcat6/data/solr/dev/conf
/usr/local/tomcat6/data/solr/dev/data
/usr/local/tomcat6/data/solr/prod
/usr/local/tomcat6/data/solr/prod/conf
/usr/local/tomcat6/data/solr/prod/data

Now we should copy the solr "war" file into position for deployment. Go to the directory where you decompressed solr in an earlier step, and go into the dist subdirectory. For instance: apache-solr-1.2.0/dist. 

cp apache-solr-1.2.0.war /usr/local/tomcat6/data/solr

Now, in /usr/local/tomcat6/conf/Catalina/localhost we need to create and save two files which will be read the next time you start Tomcat, and (hopefully) properly deploy Solr. Use a text editor of your choice and create these two files in the /Catalina/localhost subdirectory. 

cd /usr/local/tomcat6/conf/Catalina/localhost

solrdev.xml 

<Context docBase="/usr/local/tomcat6/data/solr/apache-solr-1.2.0.war" debug="0" crossContext="true">
<Environment name="solr/home" type="java.lang.String" value="/usr/local/tomcat6/data/solr/dev" override="true" />
</Context>

solrprod.xml 

<Context docBase="/usr/local/tomcat6/data/solr/apache-solr-1.2.0.war" debug="0" crossContext="true">
<Environment name="solr/home" type="java.lang.String" value="/usr/local/tomcat6/data/solr/prod" override="true" />
</Context>

There are some sample configuration files which come with the Solr distribution you downloaded. Let's copy those into their proper position. Go to the working directory where you downloaded solr, and into the /example/solr/conf subdirectory: /apache-solr-1.2.0/example/solr/conf. You should see something like this: 
admin-extra.html  schema.xml    solrconfig.xml  synonyms.txt
protwords.txt     scripts.conf  stopwords.txt   xslt
Copy everything here to your development solr configuration directory: 

cp -R * /usr/local/tomcat6/data/solr/dev/conf

Do the same for your production location also: 

cp -R * /usr/local/tomcat6/data/solr/prod/conf

Time to test. Everything should now be in place. Sacrifice a chicken and restart Tomcat: 

cd /usr/local/tomcat6/bin
./startup.sh

Go to your browser and type this: 

http://localhost:8080/solrprod

and also: 

http://localhost:8080/solrdev

This this point you should see a "Welcome to Solr!" message with a "Solr Admin" link. If you can click the click and see an example search interface you've probably successfully installed Solr.

:

메일서버 구축 및 개발을 위한 정보 (링크만)

ITWeb/서버관리 2012. 4. 17. 19:27

메일관련 서비스 개발을 해야 하다 보니.. 알아야 할게 참 많내요.. 
뭐 당연한 말이겠지만.. ^^;

일단은 필요한 것들에 대해서 링크만 올려 봅시다.. 

[QMAIL]
http://qmail.kldp.net/phpbb/viewtopic.php?f=3&t=8229

[Spam&Vaccine]
http://www.inter7.com/?page=simscan


:

SVN branching & merging by Eclipse.

ITWeb/서버관리 2012. 4. 16. 16:54

소스머지 전략인지 뭔지 땜시 svn 매뉴얼 학습 중... 기본이 되는 branches 와 merge 에 대해서 정리해 봅니다.
뭐.. 나중에라도 까먹지 않기 위해서... ^^;;
그냥 branching 하는 거랑 merging 하는 거니까.. 아주 심플한 jsp 파일에서 hello world 로 테스트 진행 합니다.

subversion 사이트 들어 가면 있는 파일 인데요.
걍 올려 봅니다.. :)

svn-book.pdf


1. 테스트를 위한 web project 를 하나 생성해서 trunk 에 올립니다.


2. 해당 프로젝트에서 마우스 우클릭 하신 후 아래와 같이 Team -> Branch/Tag... 선택 합니다.

3. Copy to URL 에 branches/RB-201204162 로 입력하고 Next 합니다.

4. Copy Revision 화면에서 그냥 HEAD revision in the repository 에 놓고 Next 합니다.

5. Branch/Tag Comment 에 comment 넣고 Finish 합니다.

6. SVN explorer 로 확인해 보시면 생성한 branch 가 보이실 겁니다.

7. 자, 이제 Branching 한 넘을 가지고 소스코드를 고친 후 merge 를 해봅시다.

RB-201204162 를 checkout 받고, index.jsp 를 고치고, commit 을 합니다.

8. RB-201204162 를 trunk 로 merge 를 해봅시다.
trunk 프로젝트에서 마우스 우클릭 Team -> Merge 를 선택 합니다.

9. 기본 값인 Reintegrate a branch 를 선택해서 진행을 합니다.

10. No uncommitted modifications 나 Working copy at a single revision 에서 빨간 줄 나오시는 분은 commit 이랑 update 한번 해주시면 됩니다.

11. Merge 할 대상을 선택 합니다.

12. Next 후 Finish 하시면 Merge 가 수행 되는 것을 볼 수 있습니다.

13. index.jsp 파일을 수정했으니 updated 된 파일이 1개 나오게 됩니다.

14. merge result 확인하기

15. merge 결과를 확인하고 trunk 의 index.jsp 파일을 commit 할지 판단 하셔서 올리시면 되겠습니다.


:

우분투에 SVN 설치하기.

ITWeb/서버관리 2012. 4. 16. 12:59

SVN 관련 테스트 할게 있어서 우분투에 설치를 하게 되었내요.
설치 했던 내용을 정리해 봅니다.


[Prerequisite]

이전에 작성한 글 참고 하시면 됩니다.
바뀐 내용은 크게 없으니 거의 그대로 설치 하시면 되고 다만 최신 파일을 다운로드 받아서 설치하세요.

zlib
http://jjeong.tistory.com/427

openssl
http://jjeong.tistory.com/426

httpd
http://jjeong.tistory.com/421

apr : http://apr.apache.org
./configure --prefix=/home/계정/app/apr
make
make install

apr-util : http://apr.apache.org
./configure --prefix=/home/계정/app/apr-util --with-apr=/home/계정/app/apr
make
make install

sqlite : http://www.sqlite.org/download.html
설치 관련 참고 이전 글 : http://jjeong.tistory.com/search/sqlite
./configure --prefix=/home/계정/app/sqlite
make
make install

subversion
http://jjeong.tistory.com/438
./configure --prefix=/home/계정/app/subversion --without-berkeley-db --enable-shared --with-openssl=/usr/local/ssl --with-zlib=/usr/local/zlib --with-apxs=/home/계정/app/httpd/bin/apxs --with-apr=/home/계정/app/apr --with-apr-util=/home/계정/app/apr-util --with-sqlite=/home/계정/app/sqlite
make
make install


설치하면서 내용이 좀 바뀐 subversion 밖에 없습니다.
1.7.x 로 올라 가면서 deps 파일이 필요 없게 되었내요.
그런데 추가로 apr, apr-util 을 설치해줘야 하고 설정에도 추가 되어야 하는 군요.
(제가 설치한 우분투에 설치된 게 없어서 그럴수도 있구요.. ^^;)


[Repository생성]

- svn 계정을 생성 합니다. (subversion 설치 URL 참고하세요)
- svn 계정으로 변경 합니다.
- /home/svn 위치에서
- svnadmin create --fs-type fsfs reporitory 를 실행 합니다.
- svnserve -d -r /home/svn/ 을 실행 합니다.

요렇게 하시면 svn 접속 하실 수 있습니다.


아래와 같은 에러가 발생 할 경우

Failed to load JavaHL Library

sudo apt-get install libsvn-java
eclipse.ini 에 아래 추가함.

-vmargs
-Djava.library.path=/usr/lib/jni

참고URL : http://subclipse.tigris.org/wiki/JavaHL or http://mytony.co.kr/archives/978

:

Tomcat 관련 Articles.

ITWeb/서버관리 2012. 4. 10. 16:39

사이트에 잘 정리가 되어 있내요.
도움이 될 것 같아 bookmarking 해봅니다..

[원본링크]

http://www.mulesoft.com/understanding-apache-tomcat

[원본글]

Apache Tomcat Resource Center

This page provides free Apache Tomcat resources that will help you identify, troubleshoot, and resolve common problems with Apache Tomcat.

Apache Tomcat is the world's most widely used web application server, with over one million downloads per month and over 70% penetration in the enterprise datacenter. Tomcat is used to power everything from simple one server sites to large enterprise networks.

Tomcat Installation And Configuration

Apache Tomcat Performance

Tomcat How-To Guides

Apache Tomcat Components

Apache Tomcat In Development

More Tomcat Resources

Tomcat Monitoring and Administration

Apache Tomcat On Your OS

Tomcat Versions

Troubleshooting Tomcat

Improving Tomcat Security

Still haven't found what you are looking for? Visit our free email-based Tomcat support line!

:

How Email Works, MX Record

ITWeb/서버관리 2012. 4. 10. 15:19

[원본링크]

http://www.eukhost.com/web-hosting/kb/how-to-change-mx-records-of-a-domain-cpanel-help/


[원본글]




Steps to change Domain MX in cPanel

Step 1: (a) Verify Nameservers

Using any of the online tools, you may ensure your current DNS records. Once you are aware about those details, you may proceed with making the required changes to the DNS settings.

(b) Modify the TTL Settings in DNS

TTL decides the time for the changes to take effect. Decreasing the Time To Live setting for the domain, would tell the system to refresh faster therefore allowing it to grab the changes faster. Once the necessary details have been detected rightly, you may increase it to the previous values.
Ideally it is advisable to make these changes at least 24 – 48 hours before amending the MX records.

Step 2: Amending the MX Records

You must be logged into your server as root via. SSH. Navigate to the /var/named directory. Look for the file named ‘yourdomain.com.db’ and edit it using your preferred text editor.

You must now make changes to domain’s serial number in the zone file and Save it.

Now, using the command prompt run the following command to inform the server with the updated configuration.

rndc reload domain.com

Alternately, you may choose to restart the named service.

NOTE : Your domain might not be accessible until the new settings are implemented.

How to change MX Records Using WHM (Web Host Manager)?

Customers using either a Virtual Private Server, Cloud Server or a Dedicated Hosting server would get an access to the WHM. Upon logging into the panel, look for DNS Functions.

Now, select Edit DNS Zone and choose the domain for which you intend to amend and hit the Edit option.

You’d see a drop down menu for MX records, wherein you are required to enter the MX records in the fields provided. Don’t forget to Save the updates.

It is important to know that the MX records would only point to names and the IP addresses, therefore, you are required to set a name for the IP address that you intend to use for the domain.

If you need any assistance with changing the MX records for your domain, please feel free to get in touch with our support department either via. Live Chat viz. available at our website or login to the client area and raise a ticket from the helpdesk.

Related posts:

  1. Nameservers change to use your services?
  2. Changing A Records in Cpanel
  3. Modifying MX records for a Domain
  4. Change the Primary Domain
  5. Can I change primary domain of the account later?


:

nslookup 으로 MX Record 확인하기.

ITWeb/서버관리 2012. 4. 10. 15:15

뭐.. 그냥 하면 됩니다..


Case1)

nslookup 엔터

set type=mx or set q=mx 엔터

도메인 엔터(xxxx.com)


:

Finding and testing your MX (mail) records

ITWeb/서버관리 2012. 4. 10. 14:59

MX Record 관련 글을 찾다가.. 일단 하나 걸려서 keep 합니다.

[원본링크]

http://rscott.org/dns/mx.html


[원본글]


Step 5 - Finding and testing your MX (mail) records

GOAL: Make sure that your MX records are working properly.

BACKGROUND: MX (Mail Exchange) records are used to have mail delivered to users on your domain. It MUST have an MX record (not just an A record), primarily because people typically use an E-mail address with your domain name ("joe@example.com"), not a subdomain ("joe@mail.example.com").

When you send mail to someone, your mail typically goes from your E-mail client to an SMTP server. The SMTP server then checks for the MX record of the domain in the E-mail address. For example, with "joe@example.com", it would look for the MX record for example.com. If a user did have an E-mail address "joe@mail.example.com", the SMTP server would look for the MX record of "mail.example.com". The MX record is a domain name, so the SMTP server then gets the A record for that domain name, and connects to the mail server.

Each MX record has 2 pieces of information associated with it. The first is a number ("Preference" number), the second is the domain name of the mail server. If there are multiple MX records, the SMTP server will pick one based on the preference level (starting with the lowest preference number, working its way up). It's O.K. to have more than one MX record with the same preference.

An example would be "example.com MX 10 mail.example.com", "example.com MX 50 mail1.myisp.com", and "example.com MX 50 mail2.myisp.com". An SMTP server would first try mail.example.com, and if that wasn't reachable, it would try either mail1.myisp.com or mail2.myisp.com (normally, it should pick one of the two randomly, unless it has a better reason to pick one over the other, since the preferences are the same).

Step 5a: Find your MX record(s)

Most domains only have one set of MX records, the MX records for their domain (and not any subdomains). Your first step is to get those MX records. If you saved the information you got in Step 4a, you should already have a list of your MX records. If not, follow the instructions in step 4a ("Get a list of all your A records"), but look for "MX" records instead of "A" records.

Step 5b: Check your MX records

[If you have MX records for more than one domain, such as "example.com" and "ihostforthem.example.com", you will need to repeat steps 5b and 5c once for every domain with MX records]

First, make sure that all the MX records for your domain point to a domain name (IE, "example.com MX 10 mail.example.com"). Next, make sure that all the mail server names from the MX records have a corresponding A record. You can check the A record as described in Step 4a. For example, if you have "example.com MX 10 mail.example.com", you must also have a record such as "mail.example.com A 10.11.12.15" (unless the mail server isn't in your domain, such as "example.com MX 10 mail.myisp.com" -- but if so, myisp.com must have an A record for mail.myisp.com).

Problem? Your MX records MUST NOT point to a CNAME record. For example, "example.com MX 10 mail.example.com" can not have a corresponding record "mail.example.com CNAME smtp.example.com".

Problem? Your MX records MUST NOT point to an IP address. If so, mail servers probably will not deliver mail to you!

Problem? Do NOT use wildcards (a "*" in a domain name) unless you are positive you know what you are doing. In most cases, they provide unexpected results [RFC1912 2.7].

Step 5c: Make sure your mail servers accept your mail

Next, connect to every mail server listed here to make sure that they exist, are responding to SMTP requests, and accept mail addressed to your domain. Every mail server you have listed MUST either be one your control, or one that has given you permission to use them [RFC 1912 2.5]

To do this, use Telnet. For the "Host Name", enter the mail server name (for example, "mail.example.com"). For the Port, enter 25. A second or two later you should see a welcome message. Type "HELO" followed by the domain name of the computer you are using. For example, "HELO eagle.example.com". Then, after you get a response, type "MAIL FROM: my.email.address@example.com" (using your E-mail address on your mail server), and then "RCPT TO: my.email.address@example.com". Then, type "DATA", "Subject: Test", a blank line, "Test", and then ".". After the response, type QUIT. Make sure that you get a copy of this E-mail. If you do not (it could take some time if you are using a slow mailserver outside your domain as a backup), try it again (in case you made a mistake). If you don't get that second test message, you probably have a serious problem (you may get an E-mail back saying the message wasn't deliverable).

Problem? If you only have 1 MX record for your domain, you really ought to add a backup mail server. You don't have to, but it will make you look more professional, especially if your mail server isn't reachable for some reason.


:

[IBM] Overview mail server architecture ....

ITWeb/서버관리 2012. 4. 5. 16:30

메일 관련 서비스 프로젝트를 하다 보니..

이해 하기 쉬운 정보가 필요해서 북마크 해 봅니다.. ㅎㅎ


[링크정보]

http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaaz%2Fmailflow.htm


[펌글]


Overview of the mail server architecture

The mail server infrastructure consists of several components that work together to send, relay, receive, store, and deliver email.

The mail server workload uses the following Internet standard protocols for sending and retrieving email:
  • Simple Mail Transfer Protocol (SMTP): the Internet standard protocol for sending email.
  • Post Office Protocol (POP): an Internet standard protocol for retrieving email.
  • Internet Message Access Protocol version 4 (IMAPv4): an Internet standard protocol for retrieving email.

The following table lists each mail server component, describes each component, and provides some examples of each component.

Table 1. Mail server components, descriptions, and examples
ComponentDescriptionExamples
Mail User Agent (MUA)An application with which users can create, view, send, and receive email. The MUA is located on a client system, such as a workstation or PC.
  • Microsoft Outlook Express
  • Mozilla Thunderbird
  • Mutt E-Mail Client
Mail Transfer Agent (MTA)An application that sends, receives, and stores email. This program determines where and how to store email.
  • Postfix
  • Sendmail
  • Lotus Domino Server
  • Microsoft Exchange
Mail Delivery Agent (MDA)An application that saves received email to the MSA. This program might also perform additional tasks such as filtering email or delivering email to subfolders.

The Postfix, Dovecot, and Cyrus applications each implement some or all of the functions of the MDA.

Mail Storage Area (MSA)A local system or server where the MTA stores email. This is also the location from which the MSS retrieves email at the request of the MUA.
  • Mbox
  • Maildir
  • /var/mail/spool/username/
Mail Storage Server (MSS)An application that retrieves email from the MSA and returns it to the MUA.
  • Dovecot
  • Cyrus

The following figure shows the mail server components and the flow of email through those components.



Email flows through the mail server components as follows:
  1. From their MUA, the sender creates an email and clicks Send.
  2. The MUA uses SMTP to send the email to an MTA.
  3. The MTA relays and routes the email to an MTA in the domain of the recipient.
  4. The MTA in the domain of the recipient sends the email to an MDA of the system of the recipient.
  5. The MDA stores the email in an MSA.
  6. The MUA of the recipient queries an MSS.
  7. The MSS uses IMAPv4 or POP to retrieve the email for the recipient from the MSA.
  8. The MSS returns the email to the MUA.
  9. From their MUA, the recipient reads the email created by the sender.

In conjunction with mail server applications and email clients, you can use additional applications to pre-process and post-process email. For example, you can use filtering applications, anti-virus software, or anti-spam applications. A description of deploying such applications is outside the scope of this document. You may choose to select solutions to work in conjunction with the mail server workload for such additional functions.

Postfix overview

Postfix is an application that provides Simple Mail Transfer Protocol (SMTP) and Mail Transfer Agent (MTA) functions. Postfix is included in the mail server workload for Linux on Power systems.

Dovecot overview

Dovecot is an application that provides Post Office Protocol (POP), Internet Message Access Protocol version 4 (IMAPv4), and Mail Storage Server functions. Dovecot is included in the mail server workload for Linux on Powersystems.

Cyrus overview

Cyrus is an application that provides Post Office Protocol (POP), Internet Message Access Protocol version 4 (IMAPv4), and Mail Storage Server functions. Cyrus is included in the mail server workload for Linux on Power systems.

For more information about the Postfix, Dovecot, and Cyrus applications, see the resources listed in the Related information for the mail server topic.



:
◀ PREV : [1] : [···] : [3] : [4] : [5] : [6] : [7] : [8] : [9] : [···] : [13] : NEXT ▶

티스토리툴바