Warning: session_start(): open(/tmp/sess_38925b5a46bd866d48bb905d9d5b9f17, O_RDWR) failed: Disk quota exceeded (122) in /home/bandbsge/public_html/getfreedumps.com/quiz.php on line 7

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/bandbsge/public_html/getfreedumps.com/quiz.php:7) in /home/bandbsge/public_html/getfreedumps.com/quiz.php on line 7

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/bandbsge/public_html/getfreedumps.com/quiz.php:7) in /home/bandbsge/public_html/getfreedumps.com/quiz.php on line 7
Q&A forRedHat RH302 Page No- Chat with us

AllExam Dumps


DOWNLOAD & READ Free Dumps For RedHat- RH302

You are reading online questions and answers for RedHat Exam RH302 (Redhat Certified Engineer on Redhat Enterprise Linux 5 (Labs) ) 100% free... Please share this site which will help this community to grow...

Question ID 17378

You are giving RHCE exam. You should boot the system in Run level 3. When you
start the system after while it is going on runlevel 6 : like
INIT: Entering Run level 6
Sending TERM Single
Fix the problem and boot the system.

Option A

Answer : It is due to either default runlevel or runlevel specific scripts. Where default runlevel is specified. It shouldnt be 6. /etc/rc.d/rc 6 It reads the scripts of runlevel 6 while booting system on rulevel 3. /etc/rc.d/rc.sysinit /etc/rc.d/rc 0 /etc/rc.d/rc 1 /etc/rc.d/rc 2 /etc/rc.d/rc 3 Should be like this /etc/rc.d/rc 4 /etc/rc.d/rc 5 /etc/rc.d/rc 6

Correct Answer A
Update Date and Time 2018-01-05 05:50:04

Question ID 17379

Quota is implemented on /data but not working properly. Find out the
Problem and implement the quota to user1 to have a soft limit 60 inodes
(files) and hard limit of 70 inodes (files).

Option A

Answer : Quotas are used to limit a user's or a group of users' ability to consume disk space. This prevents a small group of users from monopolizing disk capacity and potentially interfering with other users or the entire system. Disk quotas are commonly used by ISPs, by Web hosting companies, on FTP sites, and on corporate file servers to ensure continued availability of their systems. Without quotas, one or more users can upload files on an FTP server to the point of filling a filesystem. Once the affected partition is full, other users are effectively denied upload access to the disk. This is also a reason to mount different filesystem directories on different partitions. For example, if you only had partitions for your root (/) directory and swap space, someone uploading to your computer could fill up all of the space in your root directory (/). Without at least a little free space in the root directory (/), your system could become unstable or even crash. You have two ways to set quotas for users. You can limit users by inodes or by kilobyte- sized disk blocks. Every Linux file requires an inode. Therefore, you can limit users by the number of files or by absolute space. You can set up different quotas for different filesystems. For example, you can set different quotas for users on the /home and /tmp directories if they are mounted on their own partitions. Limits on disk blocks restrict the amount of disk space available to a user on your system. Older versions of Red Hat Linux included LinuxConf, which included a graphical tool to configure quotas. As of this writing, Red Hat no longer has a graphical quota configuration tool. Today, you can configure quotas on RHEL only through the command line interface. 1. vi /etc/fstab /dev/hda11/data ext3defaults,usrquota 1 2 2. Either Reboot the System or remount the partition. Mount o remount /dev/hda11 /data 3. touch /data/aquota.user 4. quotacheck ufm /data 5. quotaon -u /data 6. edquota u user1 /

Correct Answer A
Update Date and Time 2018-01-05 05:51:18

Warning: Unknown: open(/tmp/sess_38925b5a46bd866d48bb905d9d5b9f17, O_RDWR) failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0