Page: 1
/ 6
Total 93 questions
SIMULATION -
Install the Cron Schedule for jeff user to display "Hello" on daily 5:30.
Answer : Please see explanation
Explanation:
1. Login as a root user
2. cat >schedule.txt
30 05 * * * /bin/echo "Hello"
3. crontab -u jeff schedule.txt
4. service crond restart
The cron system is essentially a smart alarm clock. When the alarm sounds, Linux runs the commands of your choice automatically. You can set the alarm clock to run at all sorts of regular time intervals. Alternatively, the system allows you to run the command of your choice once, at a specified time in the future.
Red Hat configured the cron daemon, crond. By default, it checks a series of directories for jobs to run, every minute of every hour of every day. The crond checks the /var/spool/cron directory for jobs by user. It also checks for scheduled jobs for the computer under /etc/crontab and in the /etc/cron.d directory.
Here is the format of a line in crontab. Each of these columns is explained in more detail:
#minute, hour, day of month, month, day of week, command
* * * * * command
Entries in a crontab Command Line
Field Value -
Minute 0-59 -
Hour Based on a 24-hour clock; for example, 23 = 11 p.m.
Day of month 1-31 -
Month 1-12, or jan, feb, mar, etc.
Day of week 0-7; where 0 and 7 are both Sunday; or sun, mon, tue, etc.
Command: The command you want to run
SIMULATION -
Give Full Permission to owner user and owner group member but no permission to others on /data.
Answer : Please see explanation
Explanation:
We can change the permission of file/directory either character symbol method or numeric method.
Permission:
r-Read
w-Write
x-Execute Permission Category u- Owner User
g- Owner Group
o- Others
Operators -
+ -> Add the Permissions
- ->Remove the Permissions = ->Assign the Permissions Numeric Method:
4 -> Read
2 -> Write
1 -> Execute
Total: 7, total for owner user, owner group member and for others: 777
1. chmod u+rwx /data
2. chmod g+rwx /data
3. chmod o-rwx /data
or
chmod 770 /data
4. Verify the /data: ls -ld /data
5 .You will get drwxrwx---
SIMULATION -
Whoever creates the file on /data make automatically owner group should be the group owner of /data directory.
Answer : Please see explanation
Explanation:
When user creates the file/directory, user owner will be user itself and group owner will be the primary group of the user.
There is one Special Permission SGID, when you set the SGID bit on directory. When users create the file/directory automatically owner group will be same as a parent.
1. chmod g+s /data
2. Verify using: ls -ld /data
You will get: drwxrws---
SIMULATION -
One Package named zsh is dump on ftp://server1.example.com under pub directory. Install the package from ftp server.
Answer : Please see explanation
Explanation:
1. rpm -ivh ftp://server1.example.com/pub/zsh-*
2. Package will install
rpm command is used to install, update and remove the package, -i means install, -v means verbose and -h means display the hash mark.
SIMULATION -
There are Mail servers, Web Servers, DNS Servers and Log Server. Log Server is already configured.
You should configure the mail server, web server and dns server to send the logs to log server.
Answer : Please see explanation
Explanation:
According to question, log server is already configured. We have to configure the mail, web and dns server for log redirection. In mail, web and dns server:
1. vi /etc/syslog.conf mail.* @logserveraddress
2. service syslog restart
mail is the facility and * means the priority. It sends logs of mail services into log server.
SIMULATION -
Add a cron schedule to take full backup of /home on every day at 5:30 pm to /dev/st0 device.
Answer : Please see explanation
Explanation:
1. vi /var/schedule
30 17 * * * /sbin/dump -0u /dev/st0 /dev/hda7
2. crontab /var/schedule
3. service crond restart
We can add the cron schedule either by specifying the scripts path on /etc/crontab file or by creating on text file on crontab pattern. cron helps to schedule on recurring events. Pattern of cron is: Minute Hour Day of Month Month
Day of Week Commands -
0-59 0-23 1-31 1-12 0-7 where 0 and 7 mean Sunday.
Note * means every. To execute the command on every two minutes */2.
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
Configure selinux.
Configure your systems that should be running in Enforcing.
Answer : Please see explanation
Explanation:
After reboot and verify with this command
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
Configure repository.
Create a Repository for your virtual machines. The URL is http://station.network.0.example.com/content/rhel7.0/x86_64/dvd
Answer : Please see explanation
Explanation:
Save and Exit (:wq)
Then run this:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
SSH configuration.
-> Configure SSH access on your virtual hosts as follows.
-> Clients within my22ilt.org should NOT have access to ssh on your systems
Answer : Please see explanation
Explanation:
Save and Exit (:wq)
Then run this:
Optional:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
Configure port forwarding.
Configure server X to forward traffic incoming on port 80/tcp from source network 172.25.X.0/255.255.255.0 to port on 5243/tcp.
Answer : Please see explanation
Explanation:
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.
Answer : Please see explanation
Explanation:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
Configure IPv6 network.
-> Configure eth0 with a static IPv6 addresses as follows
-> Configure a Static IPv6 address in serverX as fddb:fe2a:ab1e::c0a8:64/64
-> Configure a Static IPv6 address in desktopX as fddb:fe2a:ab1e::c0a8:02/64
-> Both machines are able to communicate within the network fddb:fe2a:able/64
The changes should be permanent even after the reboot
On ServerX:
On DesktopX:
Answer : Please see explanation
Explanation:
On ServerX:
On DesktopX:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
Link aggregation.
-> Configure your serverX and desktop, which watches for link changes and selects an active port for data transfers.
-> serverX should have the address as 192.169.X.10/255.255.255.0
-> desktopX should have the address as 192.168.X.11/255.255.255.0
(Note: where X is your station number)
Answer : Please see explanation
Explanation:
On Server Machine:
Verification & Testing:
On Desktop Machine:
Verification & Testing:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
SMTP Configuration.
-> Configure the SMTP mail service on serverX and desktopX which relay the mail only from local system through station.network0.example.com, all outgoing mail have their sender domain as example.com. Ensure that mail should not store locally.
Verify the mail server is working by sending mail to a natasha user.
-> Check the mail on both serverX and desktopX with the below URL http://station.network0.example.com/system1 http://station.network0.example.com/system2
Answer : Please see explanation
Explanation:
SIMULATION -
There were two systems:
-> system1, main system on which most of the configuration take place
-> system2, some configuration here
NFS server.
-> Configure serverX with the following requirements
-> Share the /nfsshare directory within the example.com domain clients only, share must be writable
-> Share the /nfssecure, enable krb5p security to secure access to the NFS share from URL http://station.network0.example.com/pub/keytabs/serverX.keytab
-> Create a directory named as protected under /nfssecure
-> The exported directory should have read/write access from all subdomains of the example.com domain
Ensure the directory /nfssecure/protected should be owned by the user harry with read/write permission
Answer : Please see explanation
Explanation:
30 days access 