Japanese Site

The utilization environment which combines MUSASHI, FDclone and the WWW server

MUSASHI in order to utilize efficiently and effectively with purpose of data analysis, here of following kind of system configuration is thought.

In this figure, one block which is enclosed with the framework corresponds to one computer. Here, the entire system, the "data processing machine", is formed from three subsystems of the "WWW server" and "the client". The software which is necessary for the inside of the frame of each subsystem is stated.
In the data processing machine, it becomes the work whose processing of the mass data which uses MUSASHI is main. LINUX is designated as prerequisite as OS. Being each distribution, it probably will operate without problem. However, because several joint ownership libraries are utilized, it becomes prerequisite for those libraries to be installed. MUSASHI is not the computer system which designates the relational database as the foundation, is the system which to the last designates the file as the base. Then, operation of the file to become very important, the file operation by the filer is recommended. HereFDclone is used.
With the WWW server, in order to be able to peruse the result data which was processed with the data processing machine with the Web browser, it is the work whose it is main to retain. Especially when doing one analysis with the group of humans and the like, it probably is convenient. Proftpd is used with LINUX apach, as a FTP server as the WWW server even here as OS.
With the client, login it does in the data processing machine making use of telnet or ssh, it does all operations regarding data processing. In addition, also you peruse the data which is already released from the client machine. The utilization of Tera Term is recommended concerning telnet or ssh in the Windows based client.

Then, it probably will keep seeing concerning the installation of each subsystem.

1. Construction of data processing machine

Here, it designates that login with thing, and ftp, telnet or ssh where LINUX is installed becomes possible as prerequisite, (informationof simple setting).

A) MUSASHI

In accordance withthe installation procedureof MUSASHI-CORE, MUSASHI-CORE is installed.

B) FDclone

The latest edition of FDclone is downloaded. Following to explanation, it does compiling + installation. In addition, because with FD the ncurses library is used,libncurses.so.4 is installed if it is not in /usr/lib/. Furthermore it downloads the FDclone setting file fd2rc which, sets toone for MUSASHIcopies in /etc.

In the one for person where these setting are difficult, being everything automatic, you preparedthe file whichit can install.

It thaws at the suitable place and installs.
# tar zxvf fd-bin.tar.gz
# cd fd-bin
# bash install.sh

The setting file of FDclone is set lastly.

/etc/fd2rc is compiled. First several lines are the parameter for MUSASHI. The fact that normality setting becomes necessary is wwwIP. IP address of the WWW server is appointed. As for the explanation where the other things are detailedplease refer tothe explanation of FDclone.

2. Construction of WWW server

It designates that login with thing, and ftp, telnet or ssh where LINUX is installed becomes possible as prerequisite even here, (informationof simple setting).

A) The work of httpd

If it is turboLinux, /usr/sbin/turboservice is started, httpd is done START [ S ].

/etc/httpd/conf/httpd.conf is set next. Point is as follows.

• Because with last one, there is a place where AddType is appointed, "AddType text/plain sh" with it appoints. You can recognize the browser with this, the script which upload is done (* sh) as plainText in the WWW server. The script upload is not done, if is, as for this setting there is no necessity.
• If <Directory the place where it is surrounded with the tag of /home/*/public_html> is done comment out, you remove. The appointment of especially Options Indexes SymLinksIfOwnerMatch is important. MUSAHI at FTP the case where the file is transferred to the WWW server, it is not the case that it forms index.html by all means. If Options Indexes is appointed, if there is no index.html inside the directory, the file list is formed automatically. In addition when the file which is transferred becomes enormous, the necessity to link the directory occurs. That time, Options SymLinksIfOwnerMatch becomes necessary.
• Concerning other setting according to the taste please.

3. Construction of client

When designating LINUX as the client, the point which notes is concerning Japanese input. With MUSASHI it appoints item name with all names. If it is usual, Japanese input becomes frequently necessary.It is the recommendation as for VineLinux and TurboLinux etc. at this point.

When designating Windows as the client, the point which notes is the telnet terminal. Here Tera Tremof fixed turn is the recommendation.

Supplement) setting ????? of LINUX

Setting of network

When security of Internet server being strongly, it installs TurboLinux7.0, the network access with telnet, ftp, ssh and http is not altogether possible. Then. . .

The setting of xinetd

1. The file of /etc/xinetd.d/telnet is compiled. "Disable=yes" is modified in "disable=no".

With this as for telnetd the expectation which is worked.

It is the setting of proftpd next.

2. It retains with the file which "ftp" calls the contents below to /etc/xinetd.d.

2. The setting of /etc/proftpd/proftpd.conf

• When it designates that proftpd is started by way of xinetd as prerequisite, "ServerType standalone" of /etc/proftpd/proftpd.conf is modified in "ServerType inetd".
• Setting of user and Group is verified. If it is usual, it is set to nobody, but if it is the user which the user over there the existence does not do, modifies (refers to /etc/passwd and /etc/group in the user which the existence is done). It starts with this setting proftpd as some user, it is decided.

With this as for proftpd the expectation which is worked.
But, when even then being useless, the /etc/hosts file will be verified. When IP and the name are not stated just here, there is the memory which ftp it is not possible.

3. Access control with the setting xinetd of /etc/hosts.allow and /etc/hosts.deny

/etc/hosts.allow which is the access control file by xinetd lastly (the permission file) with /etc/hosts/deny (the non- permission file) it compiles.

"ALL:ALL", namely vis-a-vis all services from all IP with default to become setting of non- permission being in the non- permission file, modification there is no necessity. IP which is permitted in every service is set to the permission file.

With the above-mentioned setting, as for first line from as for access it permits the local (that machine itself) vis-a-vis all services.
Second line permits the starting in.telnetd 10.10.10. * concerning IP.
Third line permits the starting in.proftpd 10.10.10. * with 20.20. &. * concerning IP.

4. The restart of /etc/rc.d/init.d/xinetd.
With "/etc/rc.d/init.d/xinetd restart" xinetd is restarted.
The expectation which reaches the point where it can utilize telnet and ftp with this.

Setting of disk quota

Disk capacity utilization restriction classified by user is set.
Explanation below has designated Turbo Linux 7 server as prerequisite.

The compilation of 1.fstab

Like below "usrquota" is added to the partition where we would like to apply capacity restriction.

If the above-mentioned setting is possible, it restarts.

2. Compilation of quota file

Quotacheck -a is executed.
When it does, the file, "aquota.user" is possible directly under the file system which appoints usrquota.

3. Restriction every of user is set

Edquota user name (with example below foo) it executes.
When it does, the editor is started, becomes the picture like the rough sketch.

As for the meaning of 3rd line from the left,
"File system"
"Present use block count (K byte)"
"Soft limiting of block restriction"
"Hard limit of block restriction"
"The number of present use i nodes"
"Soft limiting of i node restriction"
"Hard limit of i node restriction"
Here, hard limit, the block capacity or which with absolute restriction, is appointed it is not possible to exceed the number of i nodes. In addition soft limiting, it is possible to exceed the restriction which is appointed, but warning message to be indicated in instantaneously it exceeds, during designated time (Glace Period: If later description) is, it is available, but when it exceeds that, it becomes not be able to utilize.

Considering the thing above, it sets each restriction. Setting example is shown below.

With this example, soft limiting of capacity the 100M byte, hard limit the 120M byte, soft limiting of i node 1000, hard limit is set to 1200.
Furthermore, if each numerical value is set to 0, it becomes limitless.

4. Setting of the user is copied

When we would like to do in the same way the contents which are set at description above, vis-a-vis the other user, command below is executed.

Edquota -p foo foo1 foo2 foo3

Restriction of the foo user is applied in the same way to the foo1, foo2, foo3 user with this.
When the number of users is many, making use of the /etc/passwd file, if it makes like below, it can set with single blow.

Edquota -p foo `awk -F: '$3 > 500 {print $1} ' /etc/passwd`

6.glace Period is set

When exceeding soft limiting, command below is executed in order to set restriction time.

Edquota -t

When it does, because it becomes the following kind of compilation picture, restriction time is input restriction of block and restriction of i node vis-a-vis respectively.
With default it has been the 7th.

As for verification of these setting contents in command below possibility.

Repquota /home

5. Restart

If it can set above, restarting, it is end.
With TurboLinux7server, when starting, it seems that executes quotacheck, and quotaon automatically.