1.Tell me the files used in Custom Jump Start?2.What is the signal while killing process?3.How to install boot block in solaris?4.What is state database(SVM Solaris)?5.How you create state database?6.How to grow the file system(steps)?7.If root file system filled what you do?8.How you check the logs solaris?9.Raid 1 Mirroring(Explain Mirroring)?10.uptime,top output?11.How to check processor information?12.If password file get corrupted how you restore?

Interview Candidate
Jan 22nd, 2007
6
2642

Showing Answers 1 - 6 of 6 Answers

Vijay.Chaudhary
Profile Answers by Vijay.Chaudhary

Jan 25th, 2008

1. rules, sysidcfg, profile: 3 main files. After that we run
addtoinstallclient script with few parameters and it updates /etc/ethers and
/etc/bootparams. In the beginning we create a dump of installation CDs using
setup_server_install script. These scripts are available in Tools dir on
installation media's 1st CD.
2. SIGKILL/SIGTERM and many others.
3. installboot bootblk /dev/rdsk/c0t0d0s0--set parameters acc.
4. Which carry state of various mirroring setups done by us.
5. metadb
6. growfs
7. create another RAID concatenated partition and attach it to the root
partition and then run metaroot.
8. /var/adm/messages. Application servers have their own log dir. Other things
can be set using /etc/syslog.conf
9. What ever data any ctrl gets it duplicates it on both or multiple HD.
10. uptime: time since m/c is up. top: a list in ascending order in which CPU is
being consumed by various processes.
11. psrinfo
12. one we believe u had taken backup. Else create all users and set their
passwds.

jastiramadevi
Profile Answers by jastiramadevi

Jul 1st, 2009

1) First the dump OS is created using setup_install_server and add_to_install_server and then edit/etc/hosts.
Create sysidcfg, profile, add preinstall and postinstall scripts and then create rules. ok file. Then
you need to add client with add_install_server command.
2) You can kill using signal 9 (SIGKILL).
3) /usr/bin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
4) It maintains the information about how the meta devices are configured.
5) metadb -a -c /dev/dsk/c0t0d0s7
6) In SVM you need to add slice to metadevice and run growfs command
7)
Create metadevices on another disk having more capacity and do mirroring b/w metadevices and run metaroot command and remove the metadevices on previous disk.
8) /var/adm/messages and /var/log/syslog and /var/admlastlog etc.
9) The same data exists on two sub mirror metadevices(SVM) under a metadevice or plexes under a volume (VXVM).It provides data
redundancy and availability in case of one disk failure.
10) Uptime displays the information about for how long the server is up and top displays information about active processes on server in the sorted order of CPU.
11) psrinfo and for model and other information prtdiag -v
12) By default the backup of passwd files exists under /etc as opasswd, so you can copy that file.