SIMULATION

RHCE Test Configuration Instructions

Information for the two systems you will use in test is the following:

system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.

Password for both of the two systems is atenorth

System's IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:

system1.group3.example.com: 172.24.3.5system2.group3.example.com: 172.24.3.10

The subnet mask is 255.255.255.0

Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.

host.group3.example.com provides a centralized authentication service domain GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client

for this domain, this domain provides the following user account:

Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.

Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.

Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link: http://server1.group3.example.com/rhel

Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.

You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.

PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don't need them.

Customize the User Environment

Create a custom command on system1 and system2 named as qstat, and this custom command will execute the following command:

/bin/ps - Ao pid,tt,user,fname,rsz

This command is valid for all users in the system.

SIMULATION

RHCE Test Configuration Instructions

Information for the two systems you will use in test is the following:

system1.group3.example.com: is one of the main sever. system2.group3.example.com: mainly used as a client.

Password for both of the two systems is atenorth

System's IP is provided by DHCP, you can regard it as normal, or you can reset to Static IP in accordance with the following requirements:

system1.group3.example.com: 172.24.3.5system2.group3.example.com: 172.24.3.10

The subnet mask is 255.255.255.0

Your system is a member of DNS domain group3.example.com. All systems in DNS domain group3.example.com are all in subnet 172.24.3.0/255.255.255.0, the same all systems in this subnet are also in group3.example.com, unless specialized, all network services required to be configured can be accessed by systems of domain group3.

host.group3.example.com provides a centralized authentication service domain GROUP3.EXAMPLE.COM, both system1 and system2 have already been pre-configured to be the client

for this domain, this domain provides the following user account:

Firewall is enabled by default, you can turn it off when deemed appropriate, other settings about firewall may be in separate requirements.

Your system will be restarted before scoring, so please ensure that all modifications and service configurations you made still can be operated after the restart without manual intervention, virtual machine instances of all examinations must be able to enter the correct multi-user level after restart without manual assistance, it will be scored zero if the test using virtual machine system cannot be restarted or be properly restarted.

Corresponding distribution packages for the testing using operating system Red Hat Enterprise Linux version can be found in the following link: http://server1.group3.example.com/rhel

Part of the requirements include host security, ensure your host security limit does not prevent the request to allow the host and network, although you correctly configured the network service but would have to allow the host or network is blocked, this also does not score.

You will notice that some requirements which clearly do not allow services be accessed by service domain my133t.org, systems of this domain are in subnet 172.25.1.0/252.255.255.0, and systems of these subnets also belong to my 133t.org domain.

PS: Notice that some test questions may depend on other exam questions, for example, you might be asked to perform a series of restrictions on a user, but this user creation may be required in other questions. For convenient identification, each exam question has some radio buttons to help you identify which questions you have already completed or not completed. Certainly, you do not need to care these buttons if you don't need them.

Configure the Access to the Web Content

Create a directory private under the directory DocumentRoot in the web server on the system1, requirements are the following:

Download a file copy to this directory from http://rhgls.domain11.example.com/materials/private.html

and rename it as index.html.

Don't make any changes to this file content

Any users from the system1 can browse the content of the private, but cannot access this directory content through other systems

SIMULATION Please open the ip_forward and take effect permanently.

SIMULATION Configure the web server, which can be accessed by http://station.domain30.example.com.

SIMULATION

Whoever creates the file on /data make automatically owner group should be the group owner of /data directory.

SIMULATION

Add a cron schedule to take full backup of /home on every day at 5:30 pm to /dev/st0 device.

SIMULATION

There were two systems:

system1, main system on which most of the configuration take place

system2, some configuration here

Customize the User Environment

Create a command called qstat on both serverX and desktop.

It should be able to execute the following command (ps –eo pid, tid, class, rtprio, ni, pri, psr, pcpu, stat, wchan:14, comm).

The command should be executable by all users.

SIMULATION

There were two systems:

system1, main system on which most of the configuration take place

system2, some configuration here

Virtual hosting.

Setup a virtual host with an alternate document root.

Extend your web to include a virtual for the site http://vhostsX.example.com

Set the document root as /usr/local/vhosts

Download http://station.network0.example.com/pub/rhce/vhost/html

Rename it as index.html

Place this document root of the virtual host

Note: the other websites configures for your server must still accessible. vhosts.networkX.example.com is already provided by the name server on example.com

SIMULATION

There were two systems:

system1, main system on which most of the configuration take place

system2, some configuration here

Dynamic Webpage Configuration.

Configure website http://wsgiX.example.com:8961 on system1 with the documentroot /var/www/scripts

Site should execute webapp.wsgi

Page is already provided on http://classroom.example.com/pub/webapp.wsgi

Content of the script should not be modified

SIMULATION

There were two systems:

system1, main system on which most of the configuration take place

system2, some configuration here

Script2.

Create a script on serverX called /root/createusers

When this script is called with the argument, it should add all the users from the file

Download the file from http://station.network0.example.com/pub/testfile

All users should have the login shell as /bin/false, password not required

When this script is called with any other argument, it should print the message as “Input File Not Found”

When this script is run without any argument, it should display “Usage:/root/createusers”

NOTE: if the users are added no need to delete