RedHat RH302 - RHCE (Redhat Certified Engineer)

Do the following steps as:

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 bythe 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/dataext3defaults,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 /data

and Specified the Soft limit and hard limit on opened file.

To verify either quota is working or not:

Soft limit specify the limit to generate warnings to users and hard limit can’t cross by the user. Use the quota command or repquota command to monitor the quota information.

Very Tricky question from redhat. Actually question is giving scenario to you to implement quota to neo user. You should apply the quota to neo user on /home that neo user shouldn’t occupied space more than 70K.

1.vi /etc/fstab

LABEL=/home/homeext3defaults,usrquota0 0To enable the quota on filesystem you should mount the filesystem with usrquota for user quota and grpquota for group quota.

2.touch /home/aquota.userCreating blank quota database file.

3.mount -o remount /homeRemounting the /home with updated mount options. You can verify that /home is mounted with usrquota options or not using mount command.

4.quotacheck -u /homeInitialization the quota on /home

5.edquota –u neo /homeQuota Policy editor

See the snapshot

1 Disk quotas for user neo (uid 500):

2 Filesystem blocks soft hard inodes soft hard

4 /dev/mapper/vo-myvol 2 30 70 1 0 0

Can you set the hard limit 70 and soft limit as you think like 30.

This is boot related problem. There will be same questions repeated two times but problem is different.

First When you restart the system you will get the Error:

mount: error 15 mounting ext3

mount: error 2 mounting none

switchroot: mount failed: 22

umount /initrd/dev/: 2

Kernel Panic: no syncing: Attempted to kill init !

This error occurred in your system before showing welcome redhat linux. That means problem in grub boot loader.

Restart the System

Check the grub boot loader configuration by pressing e shortcut key.

You will see like:

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root= / rhgb quiet

initrd /initrd-2.6.9-5.EL.img

OR

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/root rhgb quiet

initrd /initrd-2.6.9-5.EL.img

Then Edit Boot loader to make like

root (hd0,0)

kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet

initrd /initrd-2.6.9-5.EL.img

Check all lines and edit as same as above. Press b to boot the system

After booting the system you should correct the /etc/grub.conf file.

After completing the Boot loader problem, you will boot the system, but it goes to emergency mode. Remember that if System boots on Emergency mode that means file system problem.

You will get the Shell, remount the / filesystem with read and write mode.

1.First Find out the / filesystem using e2lable /dev/hda1, e2lable /dev/hda2 etc

2.mount –o remount,defaults /dev/hda? /

3.vi /etc/fstab

You will get like:

/root/ext3defaults 1 1

or //rootext3defaults 1 1

4.Edit the file like:

//ext3defaults 1 1

5.Configure the /etc/grub.conf file if just booting system by editing grub from grub prompt.

6.Reboot the system.

Do the following steps as:

1. vi /etc/mail/virtusertable

accountmanager@jeff

2. service sendmail restart

Do the following steps as:

1.vi /etc/hosts.deny

nfs,portmap:ALL EXCEPT .example.com, trusted.cracker.org

We can secure the services using tcp_wrappers. There are main two files, /etc/hosts.allow and /etc/hosts.deny.

There will be three stage access checking

-Is access explicitly permitted? Means permitted from /etc/hosts.allow?

- Otherwise, Is access explicitly denied? Means denied from /etc/hosts.deny?

- Otherwise, by default permit access if neither condition matched.

To deny the services we can configure /etc/hosts.deny file using ALL and EXCEPT operation. Pattern of /etc/hosts.allow and /etc/hosts.deny file is:

Demon_list:client_list:options

In Client list can be either domain name or IP address.

Do the following steps as:

1.visudo

# User alias Specification

User_alias LIMITEDTRUST=peter

# Cmnd alias Specification

Cmnd_alias MINIMUM=/usr/sbin/useradd, /usr/bin/passwd, /usr/sbin/groupadd, /usr/sbin/userdel, /usr/sbin/groupdel, /usr/sbin/usermod

#User Privilege Specification

LIMITEDTRUST ALL=MINIMUM

2.Login as peter user and run sudo useradd username

Using Sudo we can give root level privilege on commands. Visudo is the sudo editor. In user alias Specification we create the user alias and in Cmnd alias Specification, we create the command alias. In User Privilege Specification section, list the users, groups allowed to use the sudo.

By default all mails to user will send to user’s spool directory. Nothing to do.

Do the following steps as:

1.vi /etc/samba/smb.conf

[global]

netbios name=station?

workgroup=station?

security=user

smb passwd file=/etc/samba/smbpasswd

encrypt passwords=yes

hosts allow= .example.com

[data]

path=/data

public=no

writable=no

browsable=yes

2.smbpasswd -a eric

3.service smb start

4.chkconfig smb on

/etc/samba/smb.conf. There are some pre-defined section, i. globaluse to define the global options, ii. Printersuse to share the printers, iii. homesuse the share the user’s home directory.

Security=uservalidation by samba username and password. May be there are other users also. To allow certain share to certain user we should use valid users option.

smbpasswdHelps to change user’s smb password. –a option specifies that the username following should be added to the local smbpasswd file.

Do the following steps as:

1.vi /etc/mail/local-host-names

example.com

2.vi /etc/mail/sendmail.mc

dnl # DEAMON_OPTIONS(`Port=smtp,Addr=127.0.0.1,Name=MTA`)dnl

3.m4 /etc/mail/sendmail.mc >/etc/mail/sendmail.cf

4.vi /etc/mail/access

RELAY

example.comRELAY

5.service sendmail start | restart

6.chkconfig dovecot on

7.vi /etc/dovecot.conf

protocols = pop3 pop3s

8.service dovecot start | restart

9.chkconfig dovecot on

/etc/mail/local-host-names file contains the aliases to hostname. Mail server program reads the /etc/mail/sendmail.cf. To change the configuration on mail server, we should edit the /etc/mail/sendmail.mc file and should generate the sendmail.cf using m4 command.

By default sendmail server allows to connect to local host only. So we should edit the /etc/mail/sendmail.mc file to allow connect to other hosts.

By default sendmail server will not forward mail. we should specify on /etc/mail/access to relay or to block mail coming from domain or network or individual email address.

By default dovecot service start only the imap protocol. To start pop protocol with dovecot, we should write in /etc/dovecot.conf file.