# UNIX / Linux — command reference for DBAs
Command examples for Solaris, AIX, HP-UX and Linux, collected with the
Oracle, DB2 and SQL Server DBA in mind.
**Original document:** *UNIX command examples*, version 115 (07-07-2009),
compiled by **Albert van der Sel**, with additions by Piotr Król.
Converted from plain text to Markdown, content unchanged.
---
## Spis treści
- [SECTION 1. COMMANDS TO RETREIVE SYSTEM INFO](#section-1-commands-to-retreive-system-info)
- [1. HOW TO GET SYSTEM INFO](#1-how-to-get-system-info)
- [1.1 Short version](#11-short-version)
- [1.2 More Detail](#12-more-detail)
- [2. NFS and Mount command examples](#2-nfs-and-mount-command-examples)
- [2.1 NFS](#21-nfs)
- [2.2 Mount command](#22-mount-command)
- [3. Change ownership file/dir, adding users](#3-change-ownership-filedir-adding-users)
- [4. Change filemode, permissions](#4-change-filemode-permissions)
- [5. About the sticky bit](#5-about-the-sticky-bit)
- [6. About SETUID](#6-about-setuid)
- [7. Find command examples](#7-find-command-examples)
- [7. Crontab command](#7-crontab-command)
- [8. Job control, background](#8-job-control-background)
- [9. Backup commands, TAR, and Zipped files](#9-backup-commands-tar-and-zipped-files)
- [9.1 tar: Short for "Tape Archiver"](#91-tar-short-for-tape-archiver)
- [9.2 compress and uncompress](#92-compress-and-uncompress)
- [9.3 gzip](#93-gzip)
- [9.4 bzip2](#94-bzip2)
- [9.5 dd](#95-dd)
- [9.6 cpio](#96-cpio)
- [9.7 the pax command](#97-the-pax-command)
- [9.8 pkzip25](#98-pkzip25)
- [9.9 SOLARIS: ufsdump and ufsrestore](#99-solaris-ufsdump-and-ufsrestore)
- [9.10 AIX: mksysb](#910-aix-mksysb)
- [19.19 Recovery of the root filesystem on Solaris](#1919-recovery-of-the-root-filesystem-on-solaris)
- [10. uuencode](#10-uuencode)
- [11. grep command](#11-grep-command)
- [12. sort command](#12-sort-command)
- [13. SED](#13-sed)
- [14. AWK](#14-awk)
- [15. tr command](#15-tr-command)
- [16. cut and paste](#16-cut-and-paste)
- [17. mknod](#17-mknod)
- [compareVersionDBMS 10.2.0.1.0 10.2.0.2.0 10.2.0.3.0](#compareversiondbms-102010-102020-102030)
- [finish](#finish)
- [18. Links](#18-links)
- [19. Relink van Oracle](#19-relink-van-oracle)
- [20. trace](#20-trace)
- [21. Logfiles](#21-logfiles)
- [21.1 Solaris](#211-solaris)
- [22. Diagnostic output](#22-diagnostic-output)
- [23. DOS2UNIX](#23-dos2unix)
- [24. Secure shell connections](#24-secure-shell-connections)
- [25. Pipelining and Redirecting](#25-pipelining-and-redirecting)
- [27. UNIX DEVICES and mknod](#27-unix-devices-and-mknod)
- [27.1 Note 1](#271-note-1)
- [27.2 Note 2](#272-note-2)
- [28. Solaris devices](#28-solaris-devices)
- [29. filesystems in Solaris](#29-filesystems-in-solaris)
- [29.1 A few traditional filesystem commands](#291-a-few-traditional-filesystem-commands)
- [29.2 Notes on filesystems on Solaris](#292-notes-on-filesystems-on-solaris)
- [29.3 Some notes on the ZFS filesystem. Solaris 10](#293-some-notes-on-the-zfs-filesystem-solaris-10)
- [29.4 Some examples on VxFS](#294-some-examples-on-vxfs)
- [30. AIX devices](#30-aix-devices)
- [31. filesystem commands AIX](#31-filesystem-commands-aix)
- [31.1 The Logical Volume Manager LVM](#311-the-logical-volume-manager-lvm)
- [31.2 Mirroring a VG](#312-mirroring-a-vg)
- [31.3 Filesystems in AIX](#313-filesystems-in-aix)
- [31.4 SAN connection via SDD, and related commands](#314-san-connection-via-sdd-and-related-commands)
- [31.5 SAN connections with SDDPCM MPIO](#315-san-connections-with-sddpcm-mpio)
- [31.6 Other filesystem commands](#316-other-filesystem-commands)
- [32. Some Filesystem related errors in AIX](#32-some-filesystem-related-errors-in-aix)
- [32.1 The root / Filesystem is full](#321-the-root-filesystem-is-full)
- [32.2 Fixing ODM problems on a VG which is not the rootvg](#322-fixing-odm-problems-on-a-vg-which-is-not-the-rootvg)
- [32.3 Fixing ODM problems on the rootvg](#323-fixing-odm-problems-on-the-rootvg)
- [32.4 How to Replace a Disk?](#324-how-to-replace-a-disk)
- [32.5 Filesystem errors](#325-filesystem-errors)
- [32.6 Undelete programs](#326-undelete-programs)
- [32.7 Some notes about disks on x86 systems: MBR and Partition Bootsector](#327-some-notes-about-disks-on-x86-systems-mbr-and-partition-)
- [32.8 How to get LUN ID's](#328-how-to-get-lun-ids)
- [33. Filesystems in Linux](#33-filesystems-in-linux)
- [33.1 Disks](#331-disks)
- [33.2 Filesystems](#332-filesystems)
- [33.3 Adding a disk in Linux](#333-adding-a-disk-in-linux)
- [33.4 Notes about Linux and LVM](#334-notes-about-linux-and-lvm)
- [33.5 Installing a Cluster filesystem on Linux](#335-installing-a-cluster-filesystem-on-linux)
- [34. SWAP space](#34-swap-space)
- [35 Volume group, logical volumes, and filesystem commands in HPUX](#35-volume-group-logical-volumes-and-filesystem-commands-in-h)
- [35.3 HP-UX LVM commands](#353-hp-ux-lvm-commands)
- [35.4 Notes and further examples](#354-notes-and-further-examples)
- [35.5 Some important filesystem related kernel params](#355-some-important-filesystem-related-kernel-params)
- [35.6 HP-UX kernel parameters](#356-hp-ux-kernel-parameters)
- [36. Some remarks about VI](#36-some-remarks-about-vi)
- [36. ulimit](#36-ulimit)
- [37. RAM disks](#37-ram-disks)
- [37.1 AIX](#371-aix)
- [37.2 Linux](#372-linux)
- [37.3 Solaris](#373-solaris)
- [38. Software Packages](#38-software-packages)
- [38.1 Software Packages on Solaris](#381-software-packages-on-solaris)
- [38.2 Software Packages on AIX](#382-software-packages-on-aix)
- [38.3 Software Packages on Linux](#383-software-packages-on-linux)
- [39. Simplified overview Kernel parameters Solaris, AIX, Linux](#39-simplified-overview-kernel-parameters-solaris-aix-linux)
- [40. NFS](#40-nfs)
- [41. NETWORK COMMANDS AND FILES](#41-network-commands-and-files)
- [41.1 SOLARIS](#411-solaris)
- [41.2 AIX](#412-aix)
- [41.3 Linux](#413-linux)
- [42. SOME NOTES ON IPSEC](#42-some-notes-on-ipsec)
- [42.1 What is IPSec?](#421-what-is-ipsec)
- [42.2 IPSec and AIX](#422-ipsec-and-aix)
- [42.3 IPSEC and HP](#423-ipsec-and-hp)
- [43. SOLARIS OpenBoot PROM commands](#43-solaris-openboot-prom-commands)
- [44. Process priority](#44-process-priority)
- [44. ttymon and terminals](#44-ttymon-and-terminals)
- [45: CDE](#45-cde)
- [46. Make command](#46-make-command)
- [47. mkitab](#47-mkitab)
- [48. Starting and stopping deamons](#48-starting-and-stopping-deamons)
- [49. Inodes, the superblock and related items](#49-inodes-the-superblock-and-related-items)
- [50. sendmail](#50-sendmail)
- [51. SAR](#51-sar)
- [52. Xwindows](#52-xwindows)
- [53. TAPE DRIVES](#53-tape-drives)
- [54. WSM Web based System Manager](#54-wsm-web-based-system-manager)
- [55. SOFTWARE INSTALLATIONS ON AIX 5.x](#55-software-installations-on-aix-5x)
- [55.1 Installing VisualAge C++ / C compiler on AIX 5.x](#551-installing-visualage-c-c-compiler-on-aix-5x)
- [55.2 Installing Tuxedo 8.1 or 9](#552-installing-tuxedo-81-or-9)
- [55.3 Installing Micro focus](#553-installing-micro-focus)
- [55.4 Installing Java or JRE](#554-installing-java-or-jre)
- [55.5 Installing Perl](#555-installing-perl)
- [55.6 Installing DB2 Connect Enterprise Edition 8.x](#556-installing-db2-connect-enterprise-edition-8x)
- [56. Setting up an ASCII terminal on AIX](#56-setting-up-an-ascii-terminal-on-aix)
- [57: chroot](#57-chroot)
- [58. The date command](#58-the-date-command)
- [59. SOME NOTES ON LPARS ON POWER5](#59-some-notes-on-lpars-on-power5)
- [59.6 HMC commands](#596-hmc-commands)
- [60. SOME NOTES ON VIRTUALIZATION HP-UX](#60-some-notes-on-virtualization-hp-ux)
- [61. Alternate disk install AIX](#61-alternate-disk-install-aix)
- [62. IBM LPAR FAQ](#62-ibm-lpar-faq)
- [63. bosinst.data file](#63-bosinstdata-file)
- [64. NIM](#64-nim)
- [64.1 Some notes about NIM](#641-some-notes-about-nim)
- [64.2 Complete NIM Example](#642-complete-nim-example)
- [65. ACCOUNTING](#65-accounting)
- [66. Combining cards, Link Aggregation,EtherChannel in AIX](#66-combining-cards-link-aggregationetherchannel-in-aix)
- [67. More on Memory in AIX](#67-more-on-memory-in-aix)
- [68. Kernel parameters AIX](#68-kernel-parameters-aix)
- [69. AIX TUNABLE ENVIRONMENT PARAMETERS](#69-aix-tunable-environment-parameters)
- [70. Charactersets and Codepages](#70-charactersets-and-codepages)
- [71. ar, ld commands](#71-ar-ld-commands)
- [72. REMARKS ON PRINTING IN AIX](#72-remarks-on-printing-in-aix)
- [73. Apache](#73-apache)
- [74. Distributed shell](#74-distributed-shell)
- [75. General Parallel File System (GPFS)](#75-general-parallel-file-system-gpfs)
- [75.1 Creating a 2 node GPFS Cluster](#751-creating-a-2-node-gpfs-cluster)
- [75.2 GPFS commands](#752-gpfs-commands)
- [75.3 Installing GPFS](#753-installing-gpfs)
- [75.4 GPFS error messages](#754-gpfs-error-messages)
- [76. HACMP](#76-hacmp)
- [76.1: Overview Cluster solutions and terminology on AIX](#761-overview-cluster-solutions-and-terminology-on-aix)
- [76.2 Overview architecture](#762-overview-architecture)
- [76.3 Application Servers](#763-application-servers)
- [76.4 Daemons](#764-daemons)
- [76.5 Understanding Cluster Service Startup](#765-understanding-cluster-service-startup)
- [76.6 Understanding Stopping Cluster Services](#766-understanding-stopping-cluster-services)
- [76.7 Resource Groups](#767-resource-groups)
- [76.8: Cluster logfiles](#768-cluster-logfiles)
- [76.9 Oracle 10g, Oracle RAC 10g, and HACMP](#769-oracle-10g-oracle-rac-10g-and-hacmp)
- [76.10 Other notes on HACMP](#7610-other-notes-on-hacmp)
- [79. Notes on Installation and Migration AIX, HP-UX, Linux](#79-notes-on-installation-and-migration-aix-hp-ux-linux)
- [80. Some IP subnetting](#80-some-ip-subnetting)
- [81. Notes on TSM](#81-notes-on-tsm)
- [81.1 Notes on TSM client dsmc](#811-notes-on-tsm-client-dsmc)
- [81.2 Examples of the dsmc command](#812-examples-of-the-dsmc-command)
- [81.3 Restore with dsmc](#813-restore-with-dsmc)
- [81.4 Oracle and TSM: TDPO](#814-oracle-and-tsm-tdpo)
- [81.5 Other stuff with TSM client, stopping and starting](#815-other-stuff-with-tsm-client-stopping-and-starting)
- [82. LDAP](#82-ldap)
- [82.1: Introduction](#821-introduction)
- [82.2 API's dealing with LDAP](#822-apis-dealing-with-ldap)
- [82.3 Implementing LDAP on AIX](#823-implementing-ldap-on-aix)
- [82.4 Implementing LDAP on HP-UX](#824-implementing-ldap-on-hp-ux)
- [82.5 Implementing LDAP on RedHat](#825-implementing-ldap-on-redhat)
- [83. Introduction SAMBA](#83-introduction-samba)
- [83.1 Introduction](#831-introduction)
- [84. AIX and SNA](#84-aix-and-sna)
- [84. The dd and od commands](#84-the-dd-and-od-commands)
- [85. Openssl, certificates, AIX](#85-openssl-certificates-aix)
- [86. Kernel parameters HP-UX, Solaris, Linux for MQ](#86-kernel-parameters-hp-ux-solaris-linux-for-mq)
- [87. Connect Direct](#87-connect-direct)
- [88. OTHER STUFF SECTION](#88-other-stuff-section)
- [2. NOTES ABOUT SHELL PROGRAMS](#2-notes-about-shell-programs)
- [3. BOOT and Shutdown](#3-boot-and-shutdown)
- [3.1 Shutdown systems](#31-shutdown-systems)
- [3.2 Booting](#32-booting)
- [4. Most important and current AIX, SOLARIS, and Linux fixes](#4-most-important-and-current-aix-solaris-and-linux-fixes)
- [4.1 AIX](#41-aix)
- [4.2 SOLARIS](#42-solaris)
- [4.3 Linux Redhat](#43-linux-redhat)
- [5. Oracle en UNIX](#5-oracle-en-unix)
- [7. INSTALLING SUNOS](#7-installing-sunos)
- [7 0](#7-0)
- [8. RAID Volumes on SUN](#8-raid-volumes-on-sun)
- [8.1 SCSI, DISKS AND RAID](#81-scsi-disks-and-raid)
- [8.2 Installing an A1000 on Solaris8](#82-installing-an-a1000-on-solaris8)
- [7.3 Sun StorEdge D1000](#73-sun-storedge-d1000)
- [7.4 bare-metal restore procedure.](#74-bare-metal-restore-procedure)
- [8. Current machines 2005](#8-current-machines-2005)
- [8.1 AIX machines](#81-aix-machines)
- [8.2 former pSeries](#82-former-pseries)
- [8.3 Recent Sun machines](#83-recent-sun-machines)
- [8.4 Recent HP Servers](#84-recent-hp-servers)
- [9. Most important pSeries LED Codes](#9-most-important-pseries-led-codes)
- [10. Diskless machines, NFS Implementations](#10-diskless-machines-nfs-implementations)
- [SOME MORE INFO ON ERROR CODES](#some-more-info-on-error-codes)
---
```text
/****************************************************************************/
/* Document : UNIX command examples, mainly based on Solaris, AIX, HP */
/* and ofcourse, also Linux. */
/* Doc. Version : 115 */
/* File : unix.txt */
/* Purpose : some examples for the Oracle, DB2, SQLServer DBA */
/* Date : 07-07-2009 */
/* Compiled by : Albert van der Sel, Piotr Król */
/* Best use : Use find/search in your editor to find a string, command, */
/* or any identifier */
/****************************************************************************/
```
-r
Options
-p Print the current value
-c MB Change to M size (in Mbytes)
-r Restore all memory to use
-p Print the current value
```
```text
Example: find out how much memory you have online
rmss -p
Example: Change available memory to 256 Mbytes
rmss -c 256
Example: Undo the above
rmss -r
```
Warning:
rmss can damage performance very seriously
Don't go below 25% of the machines memory
Never forget to finish with rmss -r
interval count
```
```text
option - let you specify the device for which information is needed like disk ,
cpu or terminal. (-d , -c , -t or -tdc ) . x options gives the extended statistics .
```
```text
interval - is time period in seconds between two samples . iostat 4 will give data at each 4 seconds interval.
```
```text
count - is the number of times the data is needed . iostat 4 5 will give data at 4 seconds interval 5 times.
```
Example:
```text
$ iostat -xtc 5 2
extended disk statistics tty cpu
disk r/s w/s Kr/s Kw/s wait actv svc_t %w %b tin tout us sy wt id
sd0 2.6 3.0 20.7 22.7 0.1 0.2 59.2 6 19 0 84 3 85 11 0
sd1 4.2 1.0 33.5 8.0 0.0 0.2 47.2 2 23
sd2 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0
sd3 10.2 1.6 51.4 12.8 0.1 0.3 31.2 3 31
```
```text
disk name of the disk
r/s reads per second
w/s writes per second
Kr/s kilobytes read per second
Kw/s kilobytes written per second
wait average number of transactions waiting for service (Q length)
actv average number of transactions actively
being serviced (removed from the queue but not yet completed)
%w percent of time there are transactions waiting for service (queue non-empty)
%b percent of time the disk is busy (transactions in progress)
```
```text
The values to look from the iostat output are:
```
```text
Reads/writes per second (r/s , w/s)
Percentage busy (%b)
Service time (svc_t)
If a disk shows consistently high reads/writes along with , the percentage busy (%b) of the disks
is greater than 5 percent, and the average service time (svc_t) is greater than 30 milliseconds,
then action needs to be taken.
```
```text
# netstat
This command lets you know the network traffic on each node, and the number of error packets encountered.
It is useful for isolating network problems.
```
Example:
To find out all listening services, you can use the command
```text
# netstat -a -f inet
```
```
Or use it with params, which enables you to produce different listings
The following example prints the process tree (including children of process 0) for processes which match the command name ssh:
```text
$ ptree -a `pgrep ssh`
1 /sbin/init
100909 /usr/lib/ssh/sshd
569150 /usr/lib/ssh/sshd
569157 /usr/lib/ssh/sshd
569159 -ksh
569171 bash
569173 /bin/ksh
569193 bash
```
```text
----------------------------------------------------------------------
Remark: many Linux distros adopted the ptree command, as the "pstree" command.
As in
```
```text
ubuntu$ pstree -pl
init(1)---NetworkManager(5427)
+-NetworkManagerD(5441)
+-acpid(5210)
+-apache2(6966)---apache2(2890)
Ý +-apache2(2893)
Ý +-apache2(7163)
Ý +-apache2(7165)
Ý +-apache2(7166)
Ý +-apache2(7167)
Ý +-apache2(7168)
+-atd(6369)
+-avahi-daemon(5658)---avahi-daemon(5659)
+-bonobo-activati(7816)---{bonobo-activati}(7817)
etc..
..
```
```text
------------------------------------------------------------------------
```
Back to Solaris again:
Suppose you did a pfiles on an Apache process:
```text
# pfiles 13789
```
```text
13789: /apps11i/erpdev/10GAS/Apache/Apache/bin/httpd -d /apps11i/erpdev/10G
Current rlimit: 1024 file descriptors
0: S_IFIFO mode:0000 dev:350,0 ino:114723 uid:65060 gid:54032 size:301
O_RDWR
1: S_IFREG mode:0640 dev:307,28001 ino:612208 uid:65060 gid:54032 size:386
O_WRONLY|O_APPEND|O_CREAT
/apps11i/erpdev/10GAS/opmn/logs/HTTP_Server~1
2: S_IFIFO mode:0000 dev:350,0 ino:143956 uid:65060 gid:54032 size:0
O_RDWR
3: S_IFREG mode:0600 dev:307,28001 ino:606387 uid:65060 gid:54032 size:1056768
O_RDWR|O_CREAT
/apps11i/erpdev/10GAS/Apache/Apache/logs/mm.19389.mem
4: S_IFREG mode:0600 dev:307,28001 ino:606383 uid:65060 gid:54032 size:0
O_RDWR|O_CREAT
5: S_IFREG mode:0600 dev:307,28001 ino:621827 uid:65060 gid:54032 size:1056768
O_RDWR|O_CREAT
6: S_IFDOOR mode:0444 dev:351,0 ino:58 uid:0 gid:0 size:0
O_RDONLY|O_LARGEFILE FD_CLOEXEC door to nscd[421]
/var/run/name_service_door
7: S_IFIFO mode:0000 dev:350,0 ino:143956 uid:65060 gid:54032 size:0
O_RDWR
8: S_IFCHR mode:0666 dev:342,0 ino:47185924 uid:0 gid:3 rdev:90,0
O_RDONLY
/devices/pseudo/kstat@0:kstat
etc..
..
..
O_RDWR|O_CREAT
/apps11i/erpdev/10GAS/Apache/Apache/logs/dms_metrics.19389.shm.sem
21: S_IFREG mode:0600 dev:307,28001 ino:603445 uid:65060 gid:54032 size:17408
O_RDONLY FD_CLOEXEC
/apps11i/erpdev/10GAS/rdbms/mesg/ocius.msb
23: S_IFSOCK mode:0666 dev:348,0 ino:60339 uid:0 gid:0 size:0
O_RDWR
SOCK_STREAM
SO_SNDBUF(49152),SO_RCVBUF(49152),IP_NEXTHOP(0.0.192.0)
sockname: AF_INET 3.56.189.4 port: 45395
peername: AF_INET 3.56.189.4 port: 12501
256: S_IFREG mode:0444 dev:85,0 ino:234504 uid:0 gid:3 size:1616
O_RDONLY|O_LARGEFILE
/etc/inet/hosts
```
Suppose you tried pldd on the same process gave this result:
```text
# pldd 13789
```
```text
13789: /apps11i/erp
dev/10GAS/Apache/Apache/bin/httpd -d /apps11i/erpdev/10G
/apps11i/erpdev/10GAS/lib32/libdms2.so
/lib/libpthread.so.1
/lib/libsocket.so.1
/lib/libnsl.so.1
/lib/libdl.so.1
/lib/libc.so.1
/platform/sun4u-us3/lib/libc_psr.so.1
/lib/libmd5.so.1
/platform/sun4u/lib/libmd5_psr.so.1
/lib/libscf.so.1
/lib/libdoor.so.1
/lib/libuutil.so.1
/lib/libgen.so.1
/lib/libmp.so.2
/lib/libm.so.2
/lib/libresolv.so.2
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_onsint.so
/lib/librt.so.1
/apps11i/erpdev/10GAS/lib32/libons.so
/lib/libkstat.so.1
/lib/libaio.so.1
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_mmap_static.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_vhost_alias.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_env.so
..
..
etc
```
```text
/usr/lib/libsched.so.1
/apps11i/erpdev/10GAS/lib32/libclntsh.so.10.1
/apps11i/erpdev/10GAS/lib32/libnnz10.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_wchandshake.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_oc4j.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_dms.so
/apps11i/erpdev/10GAS/Apache/Apache/libexec/mod_rewrite.so
/apps11i/erpdev/10GAS/Apache/oradav/lib/mod_oradav.so
/apps11i/erpdev/10GAS/Apache/modplsql/bin/modplsql.so
```
```text
# pmap -x $$
```
```text
492328: -ksh
Address Kbytes RSS Anon Locked Mode Mapped File
00010000 192 192 - - r-x-- ksh
00040000 8 8 8 - rwx-- ksh
00042000 40 40 8 - rwx-- [ heap ]
FF180000 680 680 - - r-x-- libc.so.1
FF23A000 24 24 - - rwx-- libc.so.1
FF240000 8 8 8 - rwx-- libc.so.1
FF280000 576 576 - - r-x-- libnsl.so.1
FF310000 40 40 - - rwx-- libnsl.so.1
FF31A000 24 16 - - rwx-- libnsl.so.1
FF350000 16 16 - - r-x-- libmp.so.2
FF364000 8 8 - - rwx-- libmp.so.2
FF380000 40 40 - - r-x-- libsocket.so.1
FF39A000 8 8 - - rwx-- libsocket.so.1
FF3A0000 8 8 - - r-x-- libdl.so.1
FF3B0000 8 8 8 - rwx-- [ anon ]
FF3C0000 152 152 - - r-x-- ld.so.1
FF3F6000 8 8 8 - rwx-- ld.so.1
FFBFC000 16 16 8 - rw--- [ stack ]
-------- ------- ------- ------- -------
total Kb 1856 1848 48 -
```
-m to monitor the
native heap of a Java process on AIX. But there is another variation, svmon -P -m -r, that is very
effective in identifying native heap fragmentation. The -r switch prints the address range in use, so it gives
a more accurate view of how much of each segment is in use.
As an example, look at the partially edited output below:
```text
Pid Command Inuse Pin Pgsp Virtual 64-bit Mthrd LPage
10556 java 681613 2316 2461 501080 N Y N
```
```text
Vsid Esid Type Description LPage Inuse Pin Pgsp Virtual
22ac4 9 mmap mapped to sid b1475 - 0 0 - -
21047 8 mmap mapped to sid 30fe5 - 0 0 - -
126a2 a mmap mapped to sid 91072 - 0 0 - -
7908c 7 mmap mapped to sid 6bced - 0 0 - -
b2ad6 b mmap mapped to sid b1035 - 0 0 - -
b1475 - work - 65536 0 282 65536
30fe5 - work - 65536 0 285 65536
91072 - work - 65536 0 54 65536
6bced - work - 65536 0 261 65536
b1035 - work - 45054 0 0 45054
Addr Range: 0..45055
e0f9f 5 work shmat/mmap - 48284 0 3 48284
19100 3 work shmat/mmap - 46997 0 463 47210
c965a 4 work shmat/mmap - 46835 0 281 46953
7910c 6 work shmat/mmap - 37070 0 0 37070
Addr Range: 0..50453
e801d d work shared library text - 9172 0 0 9220
Addr Range: 0..30861
a0fb7 f work shared library data - 105 0 1 106
Addr Range: 0..2521
21127 2 work process private - 50 2 1 51
Addr Range: 65300..65535
a8535 1 pers code,/dev/q109waslv:81938 - 11 0 - -
Addr Range: 0..11
```
Other example:
```text
# svmon -G -i 2 5 # sample five times at two second intervals
```
```text
memory in use pin pg space
size inuse free pin work pers clnt work pers clnt size inuse
16384 16250 134 2006 10675 2939 2636 2006 0 0 40960 12674
16384 16250 134 2006 10675 2939 2636 2006 0 0 40960 12674
16384 16250 134 2006 10675 2939 2636 2006 0 0 40960 12674
16384 16250 134 2006 10675 2939 2636 2006 0 0 40960 12674
16384 16250 134 2006 10675 2939 2636 2006 0 0 40960 12674
```
In this example, there are 16384 pages of total size of memory. Multuply this number by 4096
to see the total real memory size. In this case the total memory is 64 MB.
, to be used. This effectively puts the
NIS server in charge of access control for this exported file system, where users can be added
and removed from an NIS group without affecting /etc/exports.
```
```text
Warning
The way in which the /etc/exports file is formatted is very important, particularly concerning the use of
space characters. Remember to always separate exported file systems from hosts and hosts from one another
with a space character. However, there should be no other space characters in the file unless they are used
in comment lines.
```
```text
For example, the following two lines do not mean the same thing:
```
```text
/home bob.domain.com(rw)
/home bob.domain.com (rw)
```
```text
The first line allows only users from bob.domain.com read-write access to the /home directory.
The second line allows users from bob.domain.com to mount the directory read-only (the default), but the rest
of the world can mount it read-write. Be careful where space characters are used in /etc/exports.
```
-- NFS Client Configuration Files - What to do on a client?
```text
Any NFS share made available by a server can be mounted using various methods. Of course, the share can be
manually mounted, using the mount command, to acquire the exported file system at a particular mount point.
However, this requires that the root user type the mount command every time the system restarts.
In addition, the root user must remember to unmount the file system when shutting down the machine.
Two methods of configuring NFS mounts include modifying the /etc/fstab or using the autofs service.
```
```text
> /etc/fstab
Placing a properly formatted line in the /etc/fstab file has the same effect as manually mounting the
exported file system. The /etc/fstab file is read by the /etc/rc.d/init.d/netfs script at system startup.
The proper file system mounts, including NFS, are put into place.
```
```text
A sample /etc/fstab line to mount an NFS export looks like the following:
```
```text
: nfs 0 0
```
```text
The relates to the hostname, IP address, or fully qualified domain name of the server exporting
the file system. The tells the server what export to mount.
The specifies where on the local file system to mount the exported directory.
This mount point must exist before /etc/fstab is read or the mount will fail. The nfs option specifies
the type of file system being mounted.
```
The area specifies how the file system is to be mounted. For example, if the options
area states rw,suid on a particular mount, the exported file system will be mounted read-write and the
user and group ID set by the server will be used. Note, parentheses are not to be used here.
<-o specific options> -O :
```
```text
# mount -F nfs hpsrv:/data /data
# mount -F nfs -o hard,intr thor:/data /data
```
```text
- standard mounts are determined by files like /etc/fstab (HP-UX) or /etc/filesystems (AIX) or /etc/vfstab etc..
```
```text
From the Main Menu, make the following selections:
```
```text
-Security and Users
-Users
-Add a User to the System
```
The utility displays a form for adding new user information. Use the and keys to move through
the form. Do not use until you are finished and ready to exit the screen.
Fill in the appropriate fields of the Create User form (as listed in Create User Form) and press .
The utility exits the form and creates the new user.
-- Using SMIT to Create a Group:
-- -----------------------------
Use the following procedure to create a group.
Start SMIT by entering the following command:
smit
The utility displays the Main Menu.
```text
From the Main Menu, make the following selections:
```
```text
-Security and Users
-Users
-Add a Group to the System
```
The utility displays a form for adding new group information.
Type the group name in the Group Name field and press .
The group name must be eight characters or less.
The utility creates the new group, automatically assigns the next available GID, and exits the form
and press Return.
3. Type ls -l and press Return to verify that the permissions of the file have changed.
The following example sets the sticky bit permission on the pubdir directory:
```
```text
castle% chmod 1777 pubdir
castle% ls -l pubdir
drwxrwxrwt 2 winsor staff 512 Jul 15 21:23 pubdir
castle%
```
and press Return.
3. Type ls -l and press Return to verify that the permissions of the file have changed.
```
The following example sets setuid permission on the myprog file:
```text
#chmod 4555 myprog
-r-sr-xr-x 1 winsor staff 12796 Jul 15 21:23 myprog
#
```
```text
The setgid (set-group identification) permission is similar to setuid, except that the effective group ID
for the process is changed to the group owner of the file and a user is granted access based on permissions
granted to that group. The /usr/bin/mail program has setgid permissions:
```
```text
castle% ls -l /usr/bin/mail
-r-x-s-x 1 bin mail 64376 Jul 15 21:27 /usr/bin/mail
castle%
```
When setgid permission is applied to a directory, files subsequently created in the directory belong to the group
the directory belongs to, not to the group the creating process belongs to. Any user who has write permission
in the directory can create a file there; however, the file does not belong to the group of the user,
but instead belongs to the group of the directory.
You can set setgid permissions by using the chmod command to assign the octal value 2 as the first number
in a series of four octal values. Use the following steps to set setgid permissions:
```text
1. If you are not the owner of the file or directory, become superuser.
2. Type chmod <2nnn> and press Return.
3. Type ls -l and press Return to verify that the permissions of the file have changed.
The following example sets setuid permission on the myprog2 file:
```
```text
#chmod 2551 myprog2
#ls -l myprog2
-r-xr-s-x 1 winsor staff 26876 Jul 15 21:23 myprog2
#
```
```
job 912687240.a at Thu Jun 6 07:14:00
```text
When you submit an at job, it is assigned a job identification number, which becomes its filename along with the .a extension.
The file is stored in the /var/spool/cron/atjobs directory. In much the same way as it schedules crontab jobs,
the cron daemon controls the scheduling of at files.
```
```
```text
to duplicate a tape:
# dd if=/dev/rmt/0 of=/dev/rmt/1
```
```text
to clone a disk with the same geometry:
# dd if=/dev/rdsk/c0t1d0s2 of=/dev/rdsk/c0t4d0s2 bs=128
```
copy-out: cpio -o
copy_in : cpio -i
pass : cpio -p
```
```text
# cd /var/bigspace
# cpio -idmv Linux9i_Disk1.cpio.gz
# cpio -idmv Linux9i_Disk2.cpio.gz
# cpio -idmv Linux9i_Disk3.cpio.gz
```
```text
# cpio -idmv < 9204_solaris_release.cpio
```
```text
# cd /work
# ls -R | cpio -ocB > /dev/rmt/0
```
```text
# cd /work
# cpio -icvdB < /dev/rmt/0
```
d will create directories as needed
c will create header information in ascii format for portability
v verbose
c character heading in file
```text
-r: Read mode .when -r is specified, pax extracts the filenames and directories found in the archive.
The archive is read from disk or tape. If an extracted file is a directory, the hierarchy
is extracted as well. The extracted files are created relative to the current directory.
```
```text
None: List mode. When neither -r or -w is specified, pax displays the filenames and directories
found in the archive file. The list is written to standard output.
```
```text
-w: Write mode. If you want to create an archive, you use -w.
Pax writes the contents of the file to the standard output in an archive format specified
by the -x option.
```
```text
-rw: Copy mode. When both -r and -w are specified, pax copies the specified files to
the destination directory.
```
```text
most important options:
-a = append to the end of an existing archive
-b = block size, multiple of 512 bytes
-c = you can specify filepatterns
-f = specifies the pathname of the input or output archive
-p = aemo
a does not preserve file access time
e preserve everything: user id, group id, filemode bits, etc..
m does not preserve file modification times
o preserve uid and gid
P preserve filemode bits
-x = specifies the archive format.
```
Examples:
```text
To copy current directory contents to tape, use -w mode and -f
# pax -w -f /dev/rmt0
```
```text
To list a verbose table of contents stored on tape rmt0, use None mode and f
# pax -v -f /dev/rmt0
```
./your/directory
```
The dot at the front of the path is important.
The "-d" flag indicates that this is a directory and everything in it should
be restored. If you omit that, you'll restore an empty directory.
```text
The directory will be restored underneath whatever directory you're in. So
if you're in your home directory it might create:
/home/azhou/your/directory.
```
With a mksysb image on disk you don't have any positioning to do, like with
a tape.
- A program which came with the tape library to control it's working. Called without arguments gives a menu.
Is useful for doing things like moving tapes from the slot to the drive. e.g.
```
```text
$ tapeutil -f /dev/smc0 move -s 10 -d 23
```
which moves the tape in slot 10 to the drive (obviously, this will depend on your own individual tape library,
may I suggest the manual?).
The fileset you need to install for 'tapeutil' command is:
Atape.driver 7.1.5.0.
```
```text
For example: /usr/bin/tapeutil -f /dev/smc0 move 773 1037
```
```text
You can get the slot numbers, and volsers in them, with the command:
/usr/bin/tapeutil -f /dev/smc0 inventory
```
To find an open slot just look for a slot with a blank "Volume Tag".
```text
One little hitch, however. If a tape is currently mounted, the "tapeut=il inventory" command will show a
slot as open ("Volume Tag" is blank), but TSM will have it reserved for=
the
mounted tape. So what I did
in my script is to check the TSM device configuration file for each ope=
n
slot that I find and if that slot number
appears in it then I skip that slot and go on to the next one.
```
-b DDS1 -n -a
make_boot_tape -d /dev/ -v
```
```text
Create a boot tape and replace the configuration information contained
in the INSTALLFS file. Use the /tmp directory for all temporary files
instead of the default /var/tmp.
```
```text
# instl_adm -d > tmp_config_file
## edit tmp_config_file as appropriate
# make_boot_tape -f tmp_config_file -t /tmp
```
```text
Create a boot tape and specify a different gateway IP address. Set
the netmask value as well. All other configuration information is from
what is already in /opt/ignite/boot/INSTALLFS.
```
```text
# make_boot_tape -g 15.23.34.123 -m 255.255.248.0
```
> |
| note: here, file_a is encoded and a new file named uufile is produced |
| when you decode file uufile a file named file_b is produced |
```
```text
# uuencode dipl.doc dipl.doc >dipl.uu
Hier wird die Datei dipl.doc (z.B. ein WinWord-Dokument) in die Datei dipl.uu umgewandelt. Dabei legen wir fest,
dasz die Datei nach dem Decodieren wieder dipl.doc heiszen soll.
```
example:
uuencode long_name.tar.Z arc.trz > arc.uue
new
```
or use _ as a delimter
```text
sed 's_/usr/local/bin_/common/bin_' new
```
## 15. tr command
Used for translating characters in a file. tr works on standard input, so if you want
to take input from a file you have to redirect standard input so that it comes from that file.
Suppose we want to replace all characters in the
range a-z by the characters A-Z
```text
# tr "[a-z]" "[A-Z]" < people
```
```text
squeeze muliple occurences osf a character (e.g. a space) in one
# tr -s " " people.old > people
```
```text
remove blank lines:
# tr -s "\012" < people.old > people
```
```text
to remove the evil microsoft carriage return.
# tr -d '\015' < original.file > new.file
```
```text
# cat filename1 | tr -d "^V^M" > newfile
```
```text
#! /bin/sh
#
# recursive dark side repair technique
# eliminates spaces in file names from current directory down
# useful for supporting systems where clueless vendors promote NT
#
for name in `find . -depth -print`
do
na=`echo "$name" | tr ' ' '_'`
if [ "$na" != "$name" ]
then
echo "$name"
fi
done
```
note:
> I have finally competed setting up the samba server and setup the share
> between NT and Samba server.
>
> However, when I open a unix text file in Windows NT using notepad, i see
> many funny characters and the text file is not in order (Just like when I
> ftp the unix text file out into NT in binary format) ...I think this has to
> be something to do with whether the file transfer is in Binary format or
> ASCII ... Is there a parameter to set for this ? I have checked the
> documents ... but couldn't find anything on this ...
>
```text
This is a FAQ, but it brief, it's like this. Unix uses a single newline
character to end a line ("\n"), while DOS/Win/NT use a
carriage-return/newline pair ("\r\n"). FTP in ASCII mode translates
these for you. FTP in binary mode, or other forms of file transfer, such
as Samba, leave the file unaltered. Doing so would be extremely
dangerous, as there's no clear way to isolate which files should be
translated
```
You can get Windows editors that understand Unix line-end conventions
(Ultra Edit is one), or you can use DOS line endings on the files, which
will then look odd from the Unix side. You can stop using notepad, and
use Wordpad instead, which will deal appropriately with Unix line
endings.
You can convert a DOS format text file to Unix with this:-
```text
tr -d '\r' < dosfile.txt > unixfile.txt
```
The best solution to this seems to be using a Windows editor that can
handle working with Unix line endings.
HTH
Mike.
Note:
```text
There are two ways of moving to a new line...carriage return, which is chr(13),
and new line which is chr(10). In windows you're supposed to use a sequence
of a carriage return followed by a new line.
For example, in VB you can use Wrap$=Chr$(13)+Chr$(10) which creates a wrap character.
```
] [-dir=] [-schema=]"
)
}
for param in $*
do
echo ${param} \
| awk 'BEGIN {FS="="}{print $1,$2}' \
| read flag value
if [ "${flag}" != "-h" ] && [ "${value}" = "" ]
then
Error "Empty value for ${flag}"
showSyntaxSystemParam
showSyntaxParam
else
case ${flag} in
-schema) wantedSchemas=${value} ;;
-dir) wantedInputDir=${value} ;;
*) checkSystemParam ${param} || showSyntaxParam ;;
esac
fi
done
fi
```
```text
BlankLine
Comment "Selected options are:"
Comment " Database : -db=${wantedDatabase}"
Comment " Schema's : -schema=${wantedSchemas}"
Comment " Input directory : -dir=${wantedInputDir}"
Line
```
```text
if [ ${continue} = true ]
then
if [ "${wantedDatabase}" = "" ]
then
BlankLine
Error "No database specified"
BlankLine
else
echo ${wantedDatabase} \
| grep -i prod \
| wc -l \
| read prod
if [ ${prod} -ne 0 ]
then
BlankLine
Error "Production environment not allowed!!"
BlankLine
else
moveLogFile ${wantedDatabase}
fi
fi
#
if [ "${wantedInputDir}" = "" ]
then
BlankLine
Error "No input directory specified"
BlankLine
else
if [ ! -d ${wantedInputDir} ]
then
BlankLine
Error "Input directory ${wantedInputDir} doesn't exists"
BlankLine
fi
fi
#
if [ "${wantedSchemas}" = "" ]
then
BlankLine
Error "No schema's to load"
BlankLine
fi
fi
```
```text
wantedSchemas=`echo ${wantedSchemas} | sed 's/,/ /g'`
if [ ${continue} = true ]
then
for schema in ${wantedSchemas}
do
impPipeFile=${wantedInputDir}/${schema}.${currentUser}.load.pipe
impLogFile=${wantedInputDir}/${schema}.${currentUser}.load.log
impCompressFile=${wantedInputDir}/${schema}.data.Z
#
if [ ${continue} = true ]
then
Message "Check file permissions"
if [ ! -w ${wantedInputDir} ]
then
Error "Unable to write in ${wantedInputDir}"
fi
fi
#
if [ ${continue} = true ]
then
rm ${impPipeFile} 2> /dev/null
rm ${impLogFile} 2> /dev/null
fi
#
if [ ${continue} = true ]
then
Message "Load schema ${schema} into database ${wantedDatabase}"
fi
#
if [ ${continue} = true ]
then
Message "Create pipe for load"
CmdCapture "mknod ${impPipeFile} p"
fi
#
if [ ${continue} = true ]
then
if [ ! -f ${impCompressFile} ]
then
BlankLine
Error "File not found: ${impCompressFile}"
BlankLine
fi
fi
#
if [ ${continue} = true ]
then
Message "Start uncompression into background"
uncompress -c < ${impCompressFile} > ${impPipeFile} &
#
Message "Start import"
imp \"sys/change_on_install as sysdba\" file=${impPipeFile} log=${impLogFile} full=y statistics=always >/dev/null 2>/dev/null
#
Message "Output of import"
CmdCapture "cat ${impLogFile}"
#
Message "Allowed warnings are:"
Comment " IMP-00017 IMP-00041 IMP-00003 ORA-14063 ORA-14048 ORA-02270"
cat ${impLogFile} \
| egrep '^ORA-|^ERROR|^IMP-' \
| egrep -v 'IMP-00017|IMP-00041|IMP-00003|ORA-14063|ORA-14048|ORA-02270' \
| wc -l \
| read count
if [ ${count} -ne 0 ]
then
Error "Problem with import !!"
else
Message "Import succesful"
fi
fi
#
rm ${impPipeFile} 2> /dev/null
if [ ${continue} = true ]
then
Line
fi
done
fi
```
truss -p $ lsnrctl dbsnmp_start
```
NOTE: The "truss" command works on SUN and Sequent. Use "tusc" on HP-UX, "strace" on Linux,
"trace" on SCO Unix or call your system administrator to find the equivalent command on your system.
Monitor your Unix system:
Solaris:
Truss is used to trace the system/library calls (not user calls) and signals made/received
by a new or existing process. It sends the output to stderr.
NOTE: Trussing a process throttles that process to your display speed. Use -wall and -rall sparingly.
Truss usage
```text
truss -a -e -f -rall -wall -p
truss -a -e -f -rall -wall
```
```text
-a Show arguments passed to the exec system calls
-e Show environment variables passed to the exec system calls
-f Show forked processes
(they will have a different pid: in column 1)
-rall Show all read data (default is 32 bytes)
-wall Show all written data (default is 32 bytes)
-p Hook to an existing process (must be owner or root)
Specify a program to run
```
```text
Truss examples
# truss -rall -wall -f -p
# truss -rall -wall lsnrctl start
# truss -aef lsnrctl dbsnmp_start
```
```
Because strace will show you the systemcalls and signals, you can use it to reveal whether a program cannot
find a file, or does not have permissions to read (or write to) a file. In such a case, a program might fail.
Example:
```text
Suppose we have a file called "/etc/security.conf". Now we run a utility to read the file (like cat, pg, more, less etc..)
as a normal user, which user does not have permissions to read the file. Let's trace that event to a logfile, and see
what we can discover.
```
```text
$ strace -o strace_example.log less /etc/security.conf
```
A trace file can get pretty long, but you should just browse it and be alert on what seems to be an error reported.
So, if we take a look in the logfile "strace_example.log"
```text
..
..
open("/etc/security.conf", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)
write(2, "/etc/security.conf: Permission denied\n", 32) = 32
..
..
```
We can clearly see, that our program failed due to lack of read permission.
select entX
select option: internet address to ping.
wrote:
> I handle several AIX 5.1 servers and some of them warns me (via errpt)
> about a lack of disk space for the dumpcheck ressource.
> Here is a copy of the message :
```text
>
> Description
> The copy directory is too small.
>
> Recommended Actions
> Increase the size of that file system.
>
> Detail Data
> File system name
> /var/adm/ras
>
> Current free space in kb
> 7636
> Current estimated dump size in kb
> 207872
```
```text
> I guess /dev/hd6 is not big enough to contain a system dump. So how
> can i change that?
```
The error message tells you something else.
Read it, and you will understand!
> How can i configure a secondary susdump space in case the primary
> would be unavailable?
```text
sysdumpdev -s /dev/whatever
```
```text
> What does "copy directory /var/adm/ras" mean?
```
```text
That's where the crash dump will be put when you reboot after the crash.
/dev/hd6 will be needed for other purposes (paging space), so you cannot
keep your system dump there.
```
And that file system is too small to contain the dump, that's the meaning
of the error message.
You have two options:
```text
- increase the /var file system (it should have ample free space anyway).
- change the dump directory to something where you have more space:
sysdumpdev -D /something/in/rootvg/with/free/space
```
Yours,
Laurenz Albe
[RETURN]
```
dos2unix [ -ascii ] [ -iso ] [ -7 ] originalfile convertedfile
-ascii
Removes extra carriage returns and converts end of file characters in DOS format text files to conform to SunOS requirements.
-iso
This is the default. It converts characters in the DOS extended character set to the corresponding ISO standard characters.
-7
Convert 8 bit DOS graphics characters to 7 bit space characters so that SunOS can read the file.
```text
#!/bin/sh
# a script to strip carriage returns from DOS text files
if test -f $1
then
tr -d '\r' <$1 >$.tmp
rm $1
mv $.tmp $1
fi
```
```text
# tr -d '\015' < original.file > new.file
```
or this works well on most shells:
```text
# tr -d '\r' < original.file > new.file
```
AIXver3.dat
```
Converts an EBCDIC file taken off an AS400 and converts to an ASCII file for the pSeries or RS/6000
```text
nvdmetoa 132 AIXver3.txt
```
Converts an EBCDIC file with a record length of 132 characters to an ASCII file with 132 bytes per line
PLUS 1 byte for the linefeed character.
2. od command:
The od command translate a file into other formats, like for example hexadecimal format.
To translate a file into several formats at once, enter:
```text
# od -t cx a.out > a.xcd
```
This command writes the contents of the a.out file, in hexadecimal format (x) and character format (c),
into the a.xcd file.
. You should see the following warning:
```text
Warning: Permanently added 'acme.gatech.edu,130.207.165.23' (DSA) to the list of
known hosts.
```
Next, you will be prompted for your password. Type your password and hit .
:
```
```text
# zfs create tank/home
# zfs set mountpoint=/export/home tank/home
```
```text
At this point, we have "/export/home" present.
Now you could even do this:
```
```text
# zfs create tank/home/ahrens
```
```text
ZFS file systems are hierarchical: each one inherits properties from above. In this example, the mountpoint property is inherited
as a pathname prefix. That is, tank/home/ahrens is automatically mounted at /export/home/ahrens because tank/home is mounted at /export/home.
You don't have to specify the mountpoint for each individual user - you just tell ZFS the pattern.
```
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0
/pci@0,0/pci15ad,1976@10/sd@1,0
2. c1t2d0
/pci@0,0/pci15ad,1976@10/sd@2,0
3. c1t3d0
/pci@0,0/pci15ad,1976@10/sd@3,0
Also, you can check disks available to Veritas Storage Foundation using vxdisk command:
```text
bash-3.00# vxdisk -o alldgs list
```
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:none - - online invalid
c1t1d0s2 auto:none - - online invalid
c1t2d0s2 auto:none - - online invalid
c1t3d0s2 auto:none - - online invalid
You can see above that there are 4 disks on the server that are available to Veritas but they have not yet
been initialized by Veritas (invalid status). To use a disk on Veritas SF you need to initialize this
using Veritas utilities.
NOTE: If you are going to use a disk on Veritas, pay attention that you should give this whole disk to Veritas.
Disk will be formatted and you will lose all data in the disk when you are allocating a disk to Veritas Storage.
In this example the only disk that is in use for O.S Solaris is the first one. (c1t0d0s2).
We can use those 3 others disks to add on Veritas Storage.
Caution: If for a mistake we add the first disk (c1t0d0s2) to Veritas Storage, it will format
the disk and erase Solaris info. We need to pay attention to get the right disks.
Let's start allocating (initializing) those 3 disks to solaris:
```text
# vxdisksetup -i c1t1d0
#
# vxdisksetup -i c1t2d0
```
```text
# vxdisksetup -i c1t3d0
```
We have those 3 disks initialized on Veritas, then the next step is to create a Disk Group.
>>> Disk Group
Disk Group is a collection of disks. Disk Group is very useful for management and isolation purpose.
Lets create a DG using only the fist disk initialized on Veritas (c1t1d0).
We are using DG1 for the name of Disk Group.
```text
# vxdg init DG1 c1t1d0
```
```text
Check if DG1 was created successfully:
```
```text
# vxdg list
```
NAME STATE ID
DG1 enabled,cds 1218633322.13.vrt2
Also, check if the disk is properly assigned to DG1:
```text
# vxdisk -o alldgs list
```
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:none - - online invalid
c1t1d0s2 auto:cdsdisk c1t1d0 DG1 online
c1t2d0s2 auto:cdsdisk - - online
c1t3d0s2 auto:cdsdisk - - online
Let's add more 2 disks to DG1:
```text
# vxdg -g DG1 adddisk c1t2d0s2 c1t3d0s2
```
Check if the disks are properly assigned to DG1:
```text
# vxdisk -o alldgs list
```
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:none - - online invalid
c1t1d0s2 auto:cdsdisk c1t1d0 DG1 online
c1t2d0s2 auto:cdsdisk c1t2d0 DG1 online
c1t3d0s2 auto:cdsdisk c1t3d0 DG1 online
At this point we have added 3 disks into Disk Group DG1.
Next step we will create 2 different volumes in the DG1.
>>> Volumes
A volume is a virtual storage that is used as an physical disk. Volume can be composed by many disks
and have many layouts.
In this example, we are going to create two Volumes:
Volume VolS - Stripping layout using c1t1d0 and c1t2d0 disks (RAID 0).
Volume VolM - Mirroring layout using c1t2d0 and c1t3d0 (RAID 1).
-- To create a Stripping Volume VolS (Size=10m):
```text
# vxassist -g DG1 make VolS 10m layout=stripe c1t1d0s2 c1t2d0s2
```
To check if volume VolS was created successfully:
```text
# vxprint -g DG1
```
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg DG1 DG1 - - - - - -
dm c1t1d0 c1t1d0s2 - 159488 - - - -
dm c1t2d0s2 c1t2d0s2 - 159488 - - - -
dm c1t3d0s2 c1t3d0s2 - 159488 - - - -
v VolS fsgen ENABLED 20480 - ACTIVE - -
pl VolS-01 VolS ENABLED 20480 - ACTIVE - -
sd c1t1d0-01 VolS-01 ENABLED 10240 0 - - -
sd c1t2d0s2-01 VolS-01 ENABLED 10240 0 - - -
-- To create a Mirroring Volume VolM (Size=10m):
```text
# vxassist -g DG1 make VolM 10m layout=mirror c1t2d0s2 c1t3d0s2
```
To check if Volume VolM was created successfully:
```text
# vxprint -g DG1
```
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg DG1 DG1 - - - - - -
dm c1t1d0 c1t1d0s2 - 159488 - - - -
dm c1t2d0s2 c1t2d0s2 - 159488 - - - -
dm c1t3d0s2 c1t3d0s2 - 159488 - - - -
v VolM fsgen ENABLED 20480 - ACTIVE - -
pl VolM-01 VolM ENABLED 20480 - ACTIVE - -
sd c1t3d0s2-01 VolM-01 ENABLED 20480 0 - - -
pl VolM-02 VolM ENABLED 20480 - ACTIVE - -
sd c1t2d0s2-02 VolM-02 ENABLED 20480 0 - - -
v VolS fsgen ENABLED 20480 - ACTIVE - -
pl VolS-01 VolS ENABLED 20480 - ACTIVE - -
sd c1t1d0-01 VolS-01 ENABLED 10240 0 - - -
sd c1t2d0s2-01 VolS-01 ENABLED 10240 0 - - -
Note: You can see above that both Volumes were created successfully. Also, you can note the difference
between stripping and mirroring volume layouts.
VolM is using two different Plex in differente disks. This means that if you lose one disk (Plex)
you still have the data in the other disk (other Plex). It is the main configuration of Mirroring Volumes.
VolS is using only one Plex divided in 2 disks. This means that the data will be split in those 2 disks.
If you lose one disk you would lose the whole Plex, therefore you would lose the data.
This is the main configuration of Stripping Volumes. It does not provide data protection but it is very useful
for performance for purpose.
Also, you can add those 2 layouts in only one layout that provide data protection and better performance.
It is the case of RAID 0 + 1 or RAID 1 + 0.
In the next step we will create 2 different Filesystem using those 2 Volumes.
>>> Filesystem
In this example we will create two filesystem:
- Filesystem fsS will use VolS. It will be mounted at /stripe mount point.
- Filesystem fsM will use VolM. It will be mounted at /mirror mount point.
To create a VxFS filesystem:
```text
# mkfs -F vxfs /dev/vx/rdsk/DG1/VolS
```
version 7 layout
20480 sectors, 10240 blocks of size 1024, log size 1024 blocks
largefiles supported
```text
# mkfs -F vxfs /dev/vx/rdsk/DG1/VolM
```
version 7 layout
20480 sectors, 10240 blocks of size 1024, log size 1024 blocks
largefiles supported
To mount a VxFS filesystem:
```text
# mount -F vxfs /dev/vx/dsk/DG1/VolS /stripe/
# mount -F vxfs /dev/vx/dsk/DG1/VolM /mirror/
```
Now there are 2 filesystems configured and you can use it at Solaris Mount Point level.
Any data written in /stripe directory will be written in the stripping VolS volume.
Any data written in /mirror directory will be written in the mirroring VolM volume.
=c1t10d0
```
```text
Add disk to an existing disk group:
vxdg -g adddisk =c2t0d0
replace addisk with rmdisk to remove a disk
```
```text
Set up a preferred reading plex, this can be useful if we have a sparse plex (plex in RAM):
vxvol -g rdpol prefer
instead of prefer we can have round or sdeet
```
```text
View configuration:
vxprint -th
List disks:
vxdisk list
vxdisk -o alldgs list (shows deported disks)
```
```text
Adding disks while solaris is running:
drvconfig (This probes scsi - Solaris)
disks (Creates links in /dev - Solaris)
prtvtoc (View the vtoc - Solaris)
vxdctl enable (Rescan for disks - Veritas)
vxdisk list (Shows the disk in error as they are not initalized jet)
vxdisksetup (init the disks)
```
```text
To encapsulate use:
vxencap -g
```
```text
Export a disk group:
vxdg deport
vxdg -h deport to export to another host
```
```text
Import a disk group:
vxdg import
vxdg -C to clear hostid of old host (When failing over in DR situation)
vxdg -fC to clear hostid of old host and forcing diskgroup online
```
```text
Destroy a disk group:
vxdg destroy
```
```text
Evacuate data from a disk:
vxevac -g
```
```text
Create a volume on a diskgroup:
vxassist -g make layou=stripe
ncols=number of colums stripeunit=size
```
```text
Create a veritas filesystem on this volume:
mkfs -F vxfs /dev/vx/rdsk//
```
Delete a volume same as creatiuon but replace make with remove
```text
Resize a filesystem:
vxresize -g -F
```
```text
If Veritas is ever causing you problems, do the following:
Touch /etc/vx/reconfig.d/state.d/install-db
edit /etc/system and modify /etc/vfstab
to disable VRTS to start up and access the old root
partitions
```
vxassist make martin 100m
makes a volume called martin using any disk
vxassist make martin 100m disk10
makes a volume called martin using disk10
vxassist make martin 100m layout=stripe disk07 disk08
creates a 100mb striped volume called martin using disks7 and 8
vxassist mirror martin disk05 disk06
uses disks5 and 6 ro make a mirror on volume called martin
vxassist make martin 50m layout=mirror
makes a 50Mb mirror using any 2 disks
vxassist make martin 50m layout=mirror disk05 disk06
makes a 50mb mirror using disks 5 and 6
vxassist make martin 50m layout=mirror,stripe disk05 disk06 disk07
disk08
makes a 50Mb stripe using disks5 and 6 mirrored across 7 and 8
vxassist make martin 50m layout=mirror,stripe,log disk05 disk06 disk07
disk08
makes a 50Mb stripe using disks5 and 6 mirrored across 7 and 8 and uses
a
log subdisk
vxassist make martin 100m layout=raid5
makes a 100m raid5 volume
```text
/usr/sbin/vxedit -g rootdg rename disk12 disk09
to rename disk12 to disk09 in the rootdg
```
vxedit rm disk10
to remove a greyed out or obsolete disk in this case disk10
or to remove a disk from a diskgroup
vxdisk list - to list all disks under vmcontrol
vxdisk clearimport c#t#d#s#
to allow a disk to be imported after a server crash
```text
vxdg -g razadg rmdisk test
to remove a disk called test from a dg called razadg
```
```text
vxdg -g razadg adddisk test=c1t3d3
to add disk c1t3d3 to a dg called razadg calling the disk test, use
vxdisk list
to determine what disks are free :)
```
```text
vxedit -g rootdg set spare=on disk09
sets disk09 in the rootdg as a hotspare.
```
vxmirror rootdisk disk01
mirrors all the volumes on the root disk to disk01
```text
vxassist -g rootdg mirror vol01 disk03
mirrors vol01 (in rootdg) to disk03
```
vxassist mirror martin
will mirror the volume martin
to make a mirror manually try
```text
/usr/sbin/vxmake -g rootdg sd disk03-01 dm_name=disk03 dm_offset=0
len=81920
to create a subdisk on disk03 callin the subdisk disk03-01 the len
81920 is
81920sectors x 512bytes =40M
```
```text
vxmake plex martin-02 sd=disk03-01
creates a plex called martin-02 using subdisk disk03-01
```
```text
vxplex att martin martin-02
attaches the plex martin-02 to volume martin
```
```text
to list all volumes on your primary boot disk enter
vxprint -t -v -e 'aslist.aslist.sd_disk="boot_disk_name"'
```
```text
vxsd mv disk03-01 disk05-01
moves the contents of subdisk disk03-01 to disk05-01
then moves subdisk disk05-01 into the plex where subdisk disk03-01
once lived, leaving disk03-01 to your mercy :)
```
```text
to make a subdisk
```
```text
vxmake sd disk02-02 disk02,0,8000
this would create a subdisk called disk02-02 at the start of disk02
and would be 8000blocks (4000k) long.
if you wanted to create another subdisk on this disk the offset would
be
8000 as this is where the next free space would be onthe disk so...
vxmake sd disk02-02 disk02,8000,8000 would create another 8000block
subdisk.
```
```text
vxdisk rm c#t#d#s2
to remove a disk so it's out of vm control
```
```text
vxdiskadd c#t#d#
to add bring a new disk under vm control
```
```text
or you can try...
vxdisksetup -i c#t#d#
```
```text
vxvol -g dg volname stop
this stops a volume
```
```text
vxedit -rf rm martin
removes a volume called martin and plex(es) and subdisks though
```
```text
vxprint -ht volume
```
-s
```
Typical example:
```text
mkvg -y oravg -s 64 hdisk3 hdisk4
```
```text
mkvg -y appsvg -s 32 hdisk2
mkvg -y datavg -s 64 hdisk3
```
```text
mkvg -y appsvg -s 32 hdisk3
mkvg -y datavg -s 32 hdisk2
mkvg -y vge1corrap01 -s 64 hdisk2
```
In case you use the socalled SDD subsystem with vpath SAN storage, you should use the "mkvg4vp" command,
which works similar (same flags) as the mkvg command.
-s
```
As with physical volumes, volume groups can be created and removed and their characteristics
can be modified.
Before a new volume group can be added to the system, one or more physical volumes not used
in other volume groups, and in an available state, must exist on the system.
The following example shows the use of the mkvg command to create a volume group myvg
using the physical volumes hdisk1 and hdisk5.
```text
# mkvg -y myvg -d 10 -s 8 hdisk1 hdisk5
```
```text
# mkvg -y oravg -d 10 -s 64 hdisk1
```
(like for example "/data") will create the entry in /etc/filesystems for you
```
-m -a size=xG -a bf=true
or
# mklv -y -c 2 No_Of_PPs
# crfs -v jfs -d -m -a bf=true
```
```text
# mklv -y lv05 -c 2 splvg 300
# crfs -v jfs -d lv05 -m /spl -a bf=true
# mklv -y lv06 -c 2 splvg 100
# crfs -v jfs -d lv06 -m /u04 -a bf=true
```
```text
# mklv -y lv02 -c 2 oravg 200
# mklv -y lv03 -c 2 oravg 200
# mklv -y lv04 -c 2 oravg 200
# crfs -v jfs -d lv02 -m /u01 -a bf=true
# crfs -v jfs -d lv03 -m /u02 -a bf=true
# crfs -v jfs -d lv04 -m /u03 -a bf=true
```
```text
# crfs -v jfs -g backupvg -m /backups -a size=33G -a bf=true
# crfs -v jfs -g backupvg -m /data -a size=33G -a bf=true
# crfs -v jfs -g softwvg -m /apps -a size=16G -a bf=true
# crfs -v jfs -g softwvg -m /software -a size=33G -a bf=true
# crfs -v jfs -g softwvg -m /u05 -a size=12G -a bf=true
```
on 02/19/2003 01:51:24 PM
```
Please respond to IBM AIX Discussion List
```text
To: aix-l@Princeton.EDU
cc: (bcc: Patrick Bigelbach/DSS)
Subject Re: Cannot cfgmgr on a new FC
```
Put in your OS cd in the cdrom drive and run:
```text
cfgmgr -vi /dev/cd0
```
```text
this should load any filesets you need for the adapter if they are not
already there. You should the adapter in lsdev -Cc adapter | grep fs.
```
HTH
Vince
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Calderon, Linda
Sent: Wednesday, February 19, 2003 10:12 AM
To: aix-l@Princeton.EDU
Subject: Cannot cfgmgr on a new FC
I am trying to connect a new HBA on a P660 to a switch for a SAN. This HBA
has not been used previously, newly cabled etc. I issued the following
commands and receive the following errors:
* rmdev -Rdl fsc1
0514-519 The following device was not found in the customized device
configuration database: name 'fcs1'
* cfgmgr
0514-061 Cannot find a child device
Looking for ideas as to root cause.
...
> I deleted a scsi device from my 4.3.3 configuration with the following
> command:
> rmdev -l scsi2 -dR
>
> The device is a dual channel ultra scsi 3 card. I deleted it to try
> to resolve some performance problems with a drawer connected to the
> device. Incidentally, scsi3 which is the other side of the dual
> channel card, is working fine.
>
> When I try to reconfigure the device with:
> cfgmgr -v -lscsi2
>
> I get the following error:
>
> Method error (/usr/lib/methods/cfgncr_scsi -l scsi2 ):
> 0514-034 The following attributes do not have valid values:
>
> Any thoughts on how to fix it? For the timebeing I can't reboot the
> machine. Would a reboot be able to resolve the problem if there is no
> other solution?
>
> Thanks!
> -- Ed
```
#>> Ed,
```text
what you probably should do is run the cfgmgr comand without the
device name behind it. Because you deleted the scsi device with the
options -dR you also removed any child devices.
```
try this: cfgmgr -v
#include
#include
#include
#include
#include
#include
#include
```
```text
#define FOUR_MB (1024*1024*4)
#define THIRTY_TWO_KB (1024*32)
```
extern int optind;
extern int Optopt;
extern int Opterr;
extern char *optarg;
```text
void PrintSep()
{
int k=80;
```
```text
while (k)
{
putchar('-');
k--;
}
putchar('\n');
}
```
char *UserName(uid_t uid)
33333{
char replystr[10];
struct passwd *res;
```text
res=getpwuid(uid);
if (res->pw_name[0])
{
return res->pw_name;
}
else
{
sprintf(replystr,"%d",uid);
return replystr;
}
}
```
char *GroupName(gid_t gid)
{
struct group *res;
res=getgrgid(gid);
return res->gr_name;
}
```text
ulong NumberOfInodes(struct superblock *sb)
{
ulong MaxInodes;
ulong TotalFrags;
```
```text
if (sb->s_version==fsv3pvers)
{
TotalFrags=(sb->s_fsize*512)/sb->s_fragsize;
MaxInodes=(TotalFrags/sb->s_agsize)*sb->s_iagsize;
}
else
{
MaxInodes=(sb->s_fsize*512)/sb->s_bsize;
}
return MaxInodes;
}
```
```text
void AnalyseSuperBlock(struct superblock *sb)
{
ulong TotalFrags;
```
```text
PrintSep();
printf("SuperBlock Details:\n-------------------\n");
printf("File system size: %ld x 512 bytes (%ld Mb)\n",
sb->s_fsize,
(sb->s_fsize*512)/(1024*1024));
printf("Block size: %d bytes\n",sb->s_bsize);
printf("Flags: ");
switch (sb->s_fmod)
{
case (char)FM_CLEAN:
break;
case (char)FM_MOUNT:
printf("mounted ");
break;
case (char)FM_MDIRTY:
printf("mounted dirty ");
break;
case (char)FM_LOGREDO:
printf("log redo failed ");
break;
default:
printf("Unknown flag ");
break;
}
if (sb->s_ronly) printf("(read-only)");
printf("\n");
printf("Last SB update at: %s",ctime(&(sb->s_time)));
printf("Version: %s\n",
sb->s_version?"1 - fsv3pvers":"0 - fsv3vers");
printf("\n");
if (sb->s_version==fsv3pvers)
{
TotalFrags=(sb->s_fsize*512)/sb->s_fragsize;
printf("Fragment size: %5d ",sb->s_fragsize);
printf("inodes per alloc: %8d\n",sb->s_iagsize);
printf("Frags per alloc: %5d ",sb->s_agsize);
printf("Total Fragments: %8d\n",TotalFrags);
printf("Total Alloc Grps: %5d ",
TotalFrags/sb->s_agsize);
printf("Max inodes: %8ld\n",NumberOfInodes(sb));
}
else
{
printf("Total Alloc Grps: %5d ",
(sb->s_fsize*512)/sb->s_agsize);
printf("inodes per alloc: %8d\n",sb->s_agsize);
printf("Max inodes: %8ld\n",NumberOfInodes(sb));
}
PrintSep();
}
```
```text
void ReadInode( FILE *in,
ulong StartInum,
struct dinode *inode,
ulong InodesPerAllocBlock,
ulong AllocBlockSize)
{
off_t SeekPoint;
long BlockNumber;
int OffsetInBlock;
static struct dinode I_NODES[PAGESIZE/DILENGTH];
ulong AllocBlock;
ulong inum;
static off_t LastSeekPoint=-1;
```
```text
AllocBlock=(StartInum/InodesPerAllocBlock);
BlockNumber=(StartInum-(AllocBlock*InodesPerAllocBlock))/
(PAGESIZE/DILENGTH);
OffsetInBlock=(StartInum-(AllocBlock*InodesPerAllocBlock))-
(BlockNumber*(PAGESIZE/DILENGTH));
SeekPoint=(AllocBlock)?
(BlockNumber*PAGESIZE)+(AllocBlock*AllocBlockSize):
(BlockNumber*PAGESIZE)+(INODES_B*PAGESIZE);
if (SeekPoint!=LastSeekPoint)
{
sync();
fseek(in,SeekPoint,SEEK_SET);
fread(I_NODES,PAGESIZE,1,in);
LastSeekPoint=SeekPoint;
}
*inode=I_NODES[OffsetInBlock];
}
```
```text
void DumpInodeContents( long inode,
FILE *in,
ulong InodesPerAllocBlock,
ulong AllocBlockSize,
ulong Mask,
ulong Multiplier)
{
struct dinode DiskInode;
ulong SeekPoint;
char Buffer[4096];
ulong FileSize;
int k;
int BytesToRead;
ulong *DiskPointers;
int NumPtrs;
```
```text
ReadInode( in,
inode,
&DiskInode,
InodesPerAllocBlock,
AllocBlockSize);
FileSize=DiskInode.di_size;
```
```text
if (FileSize>FOUR_MB)
{
/* Double indirect mapping */
}
else
if (FileSize>THIRTY_TWO_KB)
{
/* Indirect mapping */
SeekPoint=DiskInode.di_rindirect & Mask;
SeekPoint=SeekPoint*Multiplier;
DiskPointers=(ulong *)malloc(1024*sizeof(ulong));
fseek(in,SeekPoint,SEEK_SET);
fread(DiskPointers,1024*sizeof(ulong),1,in);
NumPtrs=1024;
}
else
{
/* Direct Mapping */
DiskPointers=&(DiskInode.di_rdaddr[0]);
NumPtrs=8;
}
```
```text
for (k=0;k<=NumPtrs && FileSize;k++)
{
SeekPoint=(DiskPointers[k] & Mask);
SeekPoint=SeekPoint*Multiplier;
```
```text
BytesToRead=(FileSize>sizeof(Buffer))?sizeof(Buffer):FileSize;
fseek(in,SeekPoint,SEEK_SET);
fread(Buffer,BytesToRead,1,in);
FileSize=FileSize-BytesToRead;
write(1,Buffer,BytesToRead);
}
}
```
```text
void DumpInodeList( FILE *in,
ulong MaxInodes,
ulong InodesPerAllocBlock,
ulong AllocBlockSize)
{
long inode;
struct dinode DiskInode;
struct tm *TimeStruct;
```
```text
printf(" Inode Links User Group Size ModDate\n");
printf("-------- ----- -------- -------- -------- -------\n");
for (inode=0;inode<=MaxInodes;inode++)
{
ReadInode( in,
inode,
&DiskInode,
InodesPerAllocBlock,
AllocBlockSize);
if (DiskInode.di_mtime)
{
TimeStruct=localtime((long *)&DiskInode.di_mtime);
printf("%8d %5d %8s %8s %8d %02d/%02d/%4d\n",
inode,
DiskInode.di_nlink,
UserName(DiskInode.di_uid),
GroupName(DiskInode.di_gid),
DiskInode.di_size,
TimeStruct->tm_mday,
TimeStruct->tm_mon,
TimeStruct->tm_year+1900);
}
}
}
```
```text
void ExitWithUsageMessage()
{
fprintf(stderr,"USAGE: rsb [-i inode] [-d] [-s] \n");
exit(1);
}
```
```text
main(int argc,char **argv)
{
FILE *in;
struct superblock SuperBlock;
short Valid;
long inode=0;
struct dinode DiskInode;
ulong AllocBlockSize;
ulong InodesPerAllocBlock;
ulong MaxInodes;
ulong Mask;
ulong Multiplier;
int option;
int DumpSuperBlockFlag=0;
int DumpFlag=0;
```
```text
while ((option=getopt(argc,argv,"i:ds")) != EOF)
{
switch(option)
{
case 'i':
/* Inode specified */
inode=atol(optarg);
break;
case 'd':
/* Dump flag */
DumpFlag=1;
break;
case 's':
/* List Superblock flag */
DumpSuperBlockFlag=1;
break;
default:
break;
}
}
```
```text
if (strlen(argv[optind])) in=fopen(argv[optind],"r");
else ExitWithUsageMessage();
```
```text
if (in)
{
fseek(in,SUPER_B*PAGESIZE,SEEK_SET);
fread(&SuperBlock,sizeof(SuperBlock),1,in);
switch (SuperBlock.s_version)
{
case fsv3pvers:
Valid=!strncmp(SuperBlock.s_magic,fsv3pmagic,4);
InodesPerAllocBlock=SuperBlock.s_iagsize;
AllocBlockSize=
SuperBlock.s_fragsize*SuperBlock.s_agsize;
Multiplier=SuperBlock.s_fragsize;
Mask=0x3ffffff;
break;
case fsv3vers:
Valid=!strncmp(SuperBlock.s_magic,fsv3magic,4);
InodesPerAllocBlock=SuperBlock.s_agsize;
AllocBlockSize=SuperBlock.s_agsize*PAGESIZE;
Multiplier=SuperBlock.s_bsize;
Mask=0xfffffff;
break;
default:
Valid=0;
break;
}
if (Valid)
{
if (DumpSuperBlockFlag==1)
{
AnalyseSuperBlock(&SuperBlock);
}
MaxInodes=NumberOfInodes(&SuperBlock);
if (DumpFlag==1)
{
if (inode)
DumpInodeContents(inode,in,InodesPerAllocBlock,AllocBlockSize,Mask,Multiplier);
else
DumpInodeList(in,MaxInodes,InodesPerAllocBlock,AllocBlockSize);
}
}
else
{
fprintf(stderr,"Superblock - bad magic number\n");
exit(1);
}
}
else
{
fprintf(stderr,"couldn't open ");
perror(argv[optind]);
exit(1);
}
}
```
```
```text
Ok, you've created a blank receptacle but now you have to tell how many Physical Extents from the
physical device (/dev/md0 in this case) will be allocated to this Volume Group. In my case I wanted all the data
from /dev/md0 to be allocated to this Volume Group. If later I wanted to add additional space I would create
a new RAID array and add that physical device to this Volume Group.
To find out how many PEs are available to me use the vgdisplay command to find out how many are available
and now I can create a Logical Volume using all (or some) of the space in the Volume Group.
In my case I call the Logical Volume lvm0.
```
```text
# vgdisplay lvm-raid
.
.
Free PE / Size 57235 / 223.57 GB
```
```text
# lvcreate -l 57235 lvm-raid -n lvm0
```
```text
In the end you will have a device you can use very much like a plain 'ol parition called /dev/lvm-raid/lvm0.
You can now check on the status of the Logical Volume with the lvdisplay command. The device can then be used to to create a filesystem on.
```
```text
# lvdisplay /dev/lvm-raid/lvm0
--- Logical volume ---
LV Name /dev/lvm-raid/lvm0
VG Name lvm-raid
LV UUID FFX673-dGlX-tsEL-6UXl-1hLs-6b3Y-rkO9O2
LV Write Access read/write
LV Status available
# open 1
LV Size 223.57 GB
Current LE 57235
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:2
```
```text
# mkfs.ext3 /dev/lvm-raid/lvm0
.
.
# mount /dev/lvm-raid/lvm0 /mnt
```
```text
# df -h /mnt
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/lvm--raid-lvm0
224G 93M 224G 1% /mnt
```
- Handling a Drive Failure
As everything eventually does break (some sooner than others) a drive in the array will fail. It is a very good idea
to run smartd on all drives in your array (and probably ALL drives period) to be notified of a failure
or a pending failure as soon as possible. You can also manually fail a partition, meaning to take it out
of the RAID array, with the following command:
```text
# /sbin/mdadm /dev/md0 -f /dev/hdb1
mdadm: set /dev/hdb1 faulty in /dev/md0
```
Once the system has determined a drive has failed or is otherwise missing (you can shut down and pull out a drive
and reboot to similate a drive failure or use the command to manually fail a drive above it will show something
like this in mdadm:
```text
# /sbin/mdadm --detail /dev/md0
Update Time : Wed Jun 15 11:30:59 2005
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0
.
.
Number Major Minor RaidDevice State
0 3 1 0 active sync /dev/hda1
1 0 0 - removed
2 33 65 2 active sync /dev/hdf1
```
```text
You'll notice in this case I had /dev/hdb fail. I replaced it with a new drive with the same capacity and was able
to add it back to the array. The first step is to partition the new drive just like when first creating the array.
Then you can simply add the partition back to the array and watch the status as the data is rebuilt onto the newly replace drive.
```
```text
# /sbin/mdadm /dev/md0 -a /dev/hdb1
# /sbin/mdadm --detail /dev/md0
Update Time : Wed Jun 15 12:11:23 2005
State : clean, degraded, recovering
Active Devices : 2
Working Devices : 3
Failed Devices : 0
Spare Devices : 1
```
```text
Layout : left-symmetric
Chunk Size : 64K
```
```text
Rebuild Status : 2% complete
.
.
```
During the rebuild process the system performance may be somewhat impacted but the data should remain in-tact.
```text
- Expanding an Array/Filesytem
The answer to how to expand a RAID-5 array is very simple: You can't.
I'm used to working with a NetApp Filer where you plug in a drive, type a simple command and that drive was added
to the existing RAID array, no muss, no fuss. While you can't add space to a RAID-5 array directly in Linux you CAN
add space to an existing Logical Volume and then expand the ext3 filesytem on top of it. That's the main reason you
want to run LVM on top of RAID.
```
Before you start it's probably a good idea to back up your data just in case something goes wrong.
```text
Assuming you want your data to be protected from a drive failing you'll need to create another RAID array
per the instructions above. In my case I called it /dev/md1 so after partitioning I can create the array:
```
```text
# /sbin/mdadm --create --verbose /dev/md1 --level=5 --raid-devices=3 \
/dev/hde1 /dev/hdg1 /dev/hdh1
# /sbin/mdadm --detail /dev/md1
```
The next couple steps will add the space from the new RAID array to the space available to be used by Logical Volumes.
You then check to see how many Physical Extents you have and add them to the Logical Volume you're using.
Remember that since you can have multiple Logical Volumes on top of a physical RAID array you need to do this extra step.
```text
# vgextend lvm-raid /dev/md1
# vgdisplay lvm-raid
.
.
.
Alloc PE / Size 57235 / 223.57 GB
Free PE / Size 57235 / 223.57 GB
# lvextend -l 57235 lvm-raid -n lvm0
```
```text
There, you now have a much larger Logical Volume which is using space on two separate RAID arrays.
You're not done yet, you now have to extend your filesystem to make use of all that new space. Fortunately this
is easy on FC4 and RHEL4 since there is a command to expand a ext3 filesytem without even unmounting it!
Be patient, expanding the file system takes a while.
```
```text
# lvdisplay /dev/lvm-raid/lvm0
.
.
LV Size 447.14 GB
.
# df /raid-array
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/lvm--raid-lvm0
230755476 40901348 178132400 19% /raid-array
# ext2online /dev/lvm-raid1/lvm0 447g
Get yourself a sandwich
# df /raid-array
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/lvm--raid-lvm0
461510952 40901348 40887876 9% /raid-array
```
Congrats, you now have more space. Now go fill it with something.
```
```text
oranh300:/home/se1223>cat /etc/inittab | grep enab
vxen::bootwait:/sbin/fs/vxfs/vxenablef -a
```
--> to move to another portion of the screen, such as the drop down menu area
Service Processor
from a serial console
he - help
co - return to console mode (exits the program)
sl - show log
```
Panic Reboots
Check these files for clues:
```text
/var/tombstones/ts99
/etc/shutdownlog
```
Bad disk
```text
1. Check the syslog (/var/adm/syslog/syslog.log) looking for disk errors.
2. Check the ioscan (ioscan -fnC disk), looking for NO_HW rather than Claimed.
3. If diaglogd is running then check STM logs (/var/opt/resmon/log/event.log)
4. Check the volume group to see if the disk is listed and whether there is any problem with it's status (vgdisplay -v | more)
5. Check lvmtab to see if the disk is supposed to be in a volume group (strings /etc/lvmtab | more)
```
Filesystem do not mount after a reboot
```text
1. Reactivate the Volume Group --> vgchange -a y /dev/
2. Remount the filesystems --> mount -a
3. If still no success then perform a filesystem check --> fsck /dev//
4. Remount the filesystems --> mount -a
5. Check to see if all the filesystems are there:
a) bdf
b) compare with /etc/fstab
```
Filesystem full
```text
du -kx / | sort -rn | more
du -akx | sort -nr | more
```
Shows directories on the local filesystem and how much space they are taking up
NFS mount - Permission Denied
```text
1. Check to see if the format of the /etc/exports file is correct on the server that is the nfs server.
```
```text
2. exportfs -av to export the filesystem
```
```text
3. Check the /etc/fstab file on the client to make sure that it is correct
```
```text
4. /usr/sbin/showmount -e on the client to show what is being exported
```
```text
5. To bypass the /etc/exports file execute the following on the nfs server: exportfs -i -o rw .
```
NFS Server
```text
/etc/rc.config.d/nfsconf --> NFS_SERVER=1
```
Verify the proper processes are running:
```text
/sbin/init.d/nfs.server stop
```
The processes should NOT be running:
```text
# ps -ef|grep nfsd
# ps -ef|grep rpc.mountd
# ps -ef|grep rpc.lockd
# ps -ef|grep rpc.statd
```
```text
/sbin/init.d/nfs.server start
```
These processes should be running:
```text
# ps -ef|grep nfsd
root 3444 1 0 10:39:12 ? 0:00 /usr/sbin/nfsd 4
root 3451 3444 0 10:39:12 ? 0:00 /usr/sbin/nfsd 4
root 3449 3444 0 10:39:12 ? 0:00 /usr/sbin/nfsd 4
root 3445 3444 0 10:39:12 ? 0:00 /usr/sbin/nfsd 4
# ps -ef|grep rpc.mountd
root 3485 1 0 10:42:09 ? 0:00 rpc.mountd
# ps -ef|grep rpc.lockd
root 3459 1 0 10:39:12 ? 0:00 /usr/sbin/rpc.lockd
# ps -ef|grep rpc.statd
root 3453 1 0 10:39:12 ? 0:00 /usr/sbin/rpc.statd
```
To start a process if it is not running:
```text
# ps -ef|grep rpc.mountd
# rpc.mountd or /usr/sbin/rpc.mountd
# ps -ef|grep rpc.mountd
root 3485 1 0 10:42:09 ? 0:00 rpc.mountd
```
```text
/etc/inetd.conf needs to have the proper services active (not commented out)
```
```text
##
# WARNING: The rpc.mountd should now be started from a startup script.
# Please enable the mountd startup script to start rpc.mountd.
##
#rpc stream tcp nowait root /usr/sbin/rpc.rexd 100017 1 rpc.rexd
rpc dgram udp wait root /usr/lib/netsvc/rstat/rpc.rstatd 100001 2-4 rpc.rstatd
rpc dgram udp wait root /usr/lib/netsvc/rusers/rpc.rusersd 100002 1-2 rpc.rusersd
rpc dgram udp wait root /usr/etc/rpc.mountd 100005 1 rpc.mountd -e
rpc dgram udp wait root /usr/lib/netsvc/rwall/rpc.rwalld 100008 1 rpc.rwalld
#rpc dgram udp wait root /usr/sbin/rpc.rquotad 100011 1 rpc.rquotad
rpc dgram udp wait root /usr/lib/netsvc/spray/rpc.sprayd 100012 1 rpc.sprayd
```
NIC problems:
The lanadmin utility provides NIC statistics
The nettladmin utility provides packet trace information
Replacing a Mirrored Root Disk:
```text
Replace the disk
Hot swap can be performed while system is up
Not hot swappable means the system must be brought down
Reboot the system into single user mode
shutdown -r 0, unless the system is powered off already, then power it back on
```
```text
interrupt the boot
bo pri (or bo alt if the disk that was replaced was the primary boot disk)
IPL>hpux -is -lq (;0)/stand/vmunix
vgcfgrestore -n /dev/vg00 /dev/rdsk/c?t?d?
vgsync /dev/vg00
mkboot /dev/rdsk/c?t?d?
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c?t?d?
shutdown -r 0
lvlnboot -v /dev/vg00 to verify that the disk is seen as bootable
```
```text
Software Installation (swinstall, sd, etc)
ERROR: "server::/tmp/omni_tmp/packet": You do not have the
required permissions to perform this operation. Check
permissions using the "swacl" command or see your system
administrator for assistance. Or, to manage applications
designed and packaged for nonprivileged mode, see the
"run_as_superuser" option in the "sd" man page.
WARNING: More information may be found in the daemon logfile on this
target (default location is
server:/var/adm/sw/swagentd.log).
```
```text
Bounce swagentd daemon: /usr/sbin/swagentd -r
```
## 36. Some remarks about VI
was successful.
# pkgchk -v SUNWpl5u
/usr
/usr/bin
/usr/bin/perl
/usr/perl5
/usr/perl5/5.00503
```
```text
Example 2:
# pkgadd -d /cdrom/cdrom0/s0/Solaris_2.6
```
```text
Example 3:
# pkgadd -d /tmp/signed_pppd
The following packages are available:
1 SUNWpppd Solaris PPP Device Drivers
(sparc) 11.10.0,REV=2003.05.08.12.24
```
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Enter keystore password:
```text
Example 4:
# pkgadd -d http://install/signed-video.pkg
```
```text
## Downloading...
..............25%..............50%..............75%..............100%
## Download Complete
```
```text
Example 5:
# pkgadd -d . DISsci The command will create a new directory structure in /opt/DISsci
```
Example 6:
Spooling the packages to a spool directory
```text
# pkgadd -d /cdrom/sol_8_sparc/s0/Solaris_8/Product -s /var/spool/pkg SUNWaudio
```
Example 7:
Installing Software Packages From a Remote Package Server
If the packages you want to install are available from a remote system, you can manually mount the directory that contains the packages
(in package format) and install packages on the local system.
The following example shows how install software packages from a remote system. In this example, assume that the remote system
named package-server has software packages in the /latest-packages directory. The mount command mounts the packages locally on /mnt,
and the pkgadd command installs the SUNWpl5u package.
```text
# mount -F nfs -o ro package-server:/latest-packages /mnt
# pkgadd -d /mnt SUNWpl5u
.
Installation of was successful.
```
## Verifying package dependencies.
## Processing package information.
## Removing pathnames in class
```
This example shows how to remove a spooled package.
```text
# pkgrm -s /export/pkg SUNWdmfex.u
The following package is currently spooled:
SUNWdmfex.u Sun Davicom 10/100Mb Ethernet Driver (64-bit)
(sparc.sun4u) 11.9.0,REV=2001.07.24.15.53
```
Do you want to remove this package? y
Removing spooled package instance
PATCHLIST shows all patches applied to the package identified by
```
```text
Example 2:
# patchadd /var/spool/patch/104945-02
# patchadd -R /export/root/client1 /var/spool/patch/104945-02
# patchadd -M /var/spool/patch 104945-02 104946-02 102345-02
# patchadd -M /var/spool/patch patchlist
# patchadd -M /var/spool/patch -R /export/root/client1 -B /export/backoutrepository 104945-02 104946-02 102345-02
```
-d , for example
# instfix -k IX75893 -d /dev/cd0
# instfix -k IX75893 -d .
# instfix -k IY63533 -d .
```
```text
- To list fixes that are on a CD-ROM in /dev/cd0, enter
# instfix -T -d /dev/cd0
IX75893
```
```text
- To determine if for example APAR IX75893 is installed on the system, enter
# instfix -ik IX75893
Not all filesets for IX75893 were found.
```
You will always be able to determine if an APAR is installed on your system using the
command instfix -ivk APAR_NUMBER , whereas installed PTFs are not trackable.
- How to determine if all filesets of a ML are installed?
```text
P521:/apps $instfix -i | grep ML
All filesets for 5.2.0.0_AIX_ML were found.
All filesets for 5200-01_AIX_ML were found.
All filesets for 5200-02_AIX_ML were found.
All filesets for 5200-03_AIX_ML were found.
All filesets for 5200-04_AIX_ML were found.
All filesets for 5200-05_AIX_ML were found.
All filesets for 5200-06_AIX_ML were found.
All filesets for 5200-07_AIX_ML were found.
All filesets for 5200-08_AIX_ML were found.
All filesets for 5200-09_AIX_ML were found.
```
```text
The command "instfix -i | grep ML" is essentially the same as "instfix -i -tp".
```
```text
- To detect incomplete AIX maintaince levels:
# instfix -i |grep ML
Not all filesets for 4.3.1.0_AIX_ML were found.
Not all filesets for 4.3.2.0_AIX_ML were found.
All filesets for 4.3.1.0_AIX_ML were found.
Not all filesets for 4.3.2.0_AIX_ML were found.
Not all filesets for 4.3.3.0_AIX_ML were found.
Not all filesets for 4330-02_AIX_ML were found.
All filesets for 4320-02_AIX_ML were found.
Not all filesets for 4330-03_AIX_ML were found.
..
..
```
You can also use smitty:
```text
# smitty instfix
```
```text
Update Software by Fix (APAR)
```
Type or select a value for the entry field.
Press Enter AFTER making all desired changes.
```text
[Entry Fields]
* INPUT device / directory for software [] +
```
" from the key rings located in /etc/rpm/.gpg using the executable /usr/bin/gpg you would include
```
```text
%_signature gpg
%_gpg_path /etc/rpm/.gpg
%_gpg_name John Doe
%_gpgbin /usr/bin/gpg
```
```text
in a macro configuration file. Use /etc/rpm/macros for per-system configuration and ~/.rpmmacros for per-user configuration.
```
REBUILD DATABASE OPTIONS
The general form of an rpm rebuild database command is
```text
rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY]
```
```text
Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.
```
SHOWRC
The command
```text
rpm --showrc
```
shows the values rpm will use for all of the options are currently set in rpmrc and macros configuration file(s).
FTP/HTTP OPTIONS
rpm can act as an FTP and/or HTTP client so that packages can be queried or installed from the internet.
Package files for install, upgrade, and query operations may be specified as an ftp or http style URL:
```text
ftp://USER:PASSWORD@HOST:PORT/path/to/package.rpm
```
If the :PASSWORD portion is omitted, the password will be prompted for (once per user/hostname pair).
If both the user and password are omitted, anonymous ftp is used. In all cases, passive (PASV) ftp transfers
are performed.
rpm allows the following options to be used with ftp URLs:
--ftpproxy HOST
The host HOST will be used as a proxy server for all ftp transfers, which allows users to ftp through firewall machines which use proxy systems. This option may also be specified by configuring the macro %_ftpproxy.
--ftpport HOST
The TCP PORT number to use for the ftp connection on the proxy ftp server instead of the default port. This option may also be specified by configuring the macro %_ftpport.
rpm allows the following options to be used with http URLs:
```text
--httpproxy HOST
The host HOST will be used as a proxy server for all http transfers. This option may also be specified by configuring the macro %_httpproxy.
--httpport PORT
The TCP PORT number to use for the http connection on the proxy http server instead of the default port. This option may also be specified by configuring the macro %_httpport.
LEGACY ISSUES
Executing rpmbuild
The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8).
```
```text
Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line:
```
```text
rpm exec --bp rpmb -bp
rpm exec --bc rpmb -bc
rpm exec --bi rpmb -bi
rpm exec --bl rpmb -bl
rpm exec --ba rpmb -ba
rpm exec --bb rpmb -bb
rpm exec --bs rpmb -bs
rpm exec --tp rpmb -tp
rpm exec --tc rpmb -tc
rpm exec --ti rpmb -ti
rpm exec --tl rpmb -tl
rpm exec --ta rpmb -ta
rpm exec --tb rpmb -tb
rpm exec --ts rpmb -ts
rpm exec --rebuild rpmb --rebuild
rpm exec --recompile rpmb --recompile
rpm exec --clean rpmb --clean
rpm exec --rmsource rpmb --rmsource
rpm exec --rmspec rpmb --rmspec
rpm exec --target rpmb --target
rpm exec --short-circuit rpmb --short-circuit
```
SEE ALSO
popt(3),
rpm2cpio(8),
rpmbuild(8),
http://www.rpm.org/ http://www.rpm.org/>
.
It is better, however, to use modprobe rather than insmod.
```
rmmod
Unloads the requested module. This is only possible if this module is no longer needed. For example,
the isofs module cannot be unloaded while a CD is still mounted.
```text
depmod
Creates the file modules.dep in /lib/modules/ that defines the dependencies of all the modules.
This is necessary to ensure that all dependent modules are loaded with the selected ones.
This file will be built after the system is started if it does not exist.
```
```text
modprobe
Loads or unloads a given module while taking into account dependencies of this module. This command
is extremely powerful and can be used for a lot of things (e.g., probing all modules of a given type
until one is successfully loaded). In contrast to insmod, modprobe checks /etc/modprobe.conf and therefore
is the preferred method of loading modules. For detailed information about this topic, refer to the
corresponding man page.
```
lsmod
Shows which modules are currently loaded as well as how many other modules are using them. Modules started
by the kernel daemon are tagged with autoclean. This label denotes that these modules will automatically
be removed once they reach their idle time limit.
modinfo
Shows module information.
```text
/etc/modprobe.conf
The loading of modules is affected by the files /etc/modprobe.conf and /etc/modprobe.conf.local
and the directory /etc/modprobe.d. See man modprobe.conf. Parameters for modules that access hardware directly
must be entered in this file. Such modules may need system-specific options (e.g., CD-ROM driver or network driver).
The parameters used here are described in the kernel sources. Install the package kernel-source and read the
documentation in the directory /usr/src/linux/Documentation.
```
Kmod - the Kernel Module Loader
The kernel module loader is the most elegant way to use modules. Kmod performs background monitoring
and makes sure the required modules are loaded by modprobe as soon as the respective functionality is needed
in the kernel.
To use Kmod, activate the option `Kernel module loader' (CONFIG_KMOD) in the kernel configuration.
Kmod is not designed to unload modules automatically; in view of today's RAM capacities, the potential memory savings
would be marginal. For reasons of performance, monolithic kernels may be more suitable for servers
that are used for special tasks and need only a few drivers.
"
exit 1
fi
```
```text
if [ ! -f /etc/sysconfig/static-routes ]; then
exit 0
fi
```
```text
#note the trailing space in the grep gets rid of aliases
grep "^$1 " /etc/sysconfig/static-routes | while read device args; do
/sbin/route add -$args $device
done
```
```text
/etc/sysconfig/network-scripts/ifup-aliases
Bring up aliases for a device.
```
```text
/etc/sysconfig/network-scripts/ifdhcpc-done
Called by dhcpcd once dhcp configuration is complete; sets up /etc/resolv.conf from the version dhcpcd dropped in /etc/dhcpc/resolv.conf
```
/sysconfig.txt file contains a more authoritative listing
of the files found in the /etc/sysconfig directory and the configuration options available.
```
```text
Files in the /etc/sysconfig/ Directory
The following files are normally found in the /etc/sysconfig/ directory:
```
amd
apmd
arpwatch
authconfig
cipe
clock
desktop
dhcpd
firstboot
gpm
harddisks
hwconf
i18n
identd
init
ipchains
iptables
irda
keyboard
kudzu
mouse
named
netdump
network
ntpd
pcmcia
radvd
rawdevices
redhat-config-users
redhat-logviewer
samba
sendmail
soundcard
squid
tux
ups
vncservers
xinetd
It is possible that your system may be missing a few of them if the corresponding program that would need
that file is not installed.
Next, we will take a look at each one.
```text
/etc/sysconfig/amd
The /etc/sysconfig/amd file contains various parameters used by amd allowing for the automounting and
automatic unmounting of file systems.
```
```text
/etc/sysconfig/apmd
The /etc/sysconfig/apmd file is used by apmd as a configuration for what things to start/stop/change
on suspend or resume. It is set up to turn on or off apmd during startup, depending on whether your hardware
supports Advanced Power Management (APM) or if you choose not to use it. apm is a monitoring daemon that works
with power management code within the Linux kernel. It can alert you to a low battery if you are using
Red Hat Linux on a laptop, among other things.
```
```text
/etc/sysconfig/arpwatch
The /etc/sysconfig/arpwatch file is used to pass arguments to the arpwatch daemon at boot time.
The arpwatch daemon maintains a table of Ethernet MAC addresses and their IP address pairings.
For more information about what parameters you can use in this file, type man arpwatch. By default,
this file sets the owner of the arpwatch process to the user pcap.
```
```text
/etc/sysconfig/authconfig
The /etc/sysconfig/authconfig file sets the kind of authorization to be used on the host.
It contains one or more of the following lines:
```
USEMD5=, where is one of the following:
yes - MD5 is used for authentication.
no - MD5 is not used for authentication.
USEKERBEROS=, where is one of the following:
yes - Kerberos is used for authentication.
no - Kerberos is not used for authentication.
USELDAPAUTH=, where is one of the following:
yes - LDAP is used for authentication.
no - LDAP is not used for authentication.
```text
/etc/sysconfig/clock
The /etc/sysconfig/clock file controls the interpretation of values read from the system hardware clock.
```
The correct values are:
UTC=, where is one of the following boolean values:
true or yes - Indicates that the hardware clock is set to Universal Time.
false or no - Indicates that the hardware clock is set to local time.
ARC=, where is the following:
true or yes - Indicates the ARC console's 42-year time offset is in effect. This setting is only
for ARC- or AlphaBIOS-based Alpha systems. Any other value indicates that the normal UNIX epoch is in use.
SRM=, where is the following:
true or yes - Indicates the SRM console's 1900 epoch is in effect. This setting is only for SRM-based
Alpha systems. Any other value indicates that the normal UNIX epoch is in use.
```text
ZONE= - Indicates the timezone file under /usr/share/zoneinfo that /etc/localtime is a copy of, such as:
```
ZONE="America/New York"
Earlier releases of Red Hat Linux used the following values (which are deprecated):
CLOCKMODE=, where is one of the following:
GMT - Indicates that the clock is set to Universal Time (Greenwich Mean Time).
ARC - Indicates the ARC console's 42-year time offset is in effect (for Alpha-based systems only).
```text
/etc/sysconfig/desktop
The /etc/sysconfig/desktop file specifies the desktop manager to be run, such as:
```
DESKTOP="GNOME"
```text
/etc/sysconfig/dhcpd
The /etc/sysconfig/dhcpd file is used to pass arguments to the dhcpd daemon at boot time.
The dhcpd daemon implements the Dynamic Host Configuration Protocol (DHCP) and the Internet Bootstrap
Protocol (BOOTP). DHCP and BOOTP assign hostnames to machines on the network. For more information
about what parameters you can use in this file, type man dhcpd.
```
```text
/etc/sysconfig/firstboot
Beginning with Red Hat Linux 8.0, the first time you boot the system, the /sbin/init program calls
the etc/rc.d/init.d/firstboot script. This allows the user to install additional applications
and documentation before the boot process completes.
```
```text
The /etc/sysconfig/firstboot file tells the firstboot command not to run on subsequent reboots.
If you want firstboot to run the next time you boot the system, simply remove /etc/sysconfig/firstboot
and execute chkconfig --level 5 firstboot on.
```
```text
/etc/sysconfig/gpm
The /etc/sysconfig/gpm file is used to pass arguments to the gpm daemon at boot time. The gpm daemon is the
mouse server which allows mouse acceleration and middle-click pasting. For more information about what
parameters you can use in this file, type man gpm. By default, it sets the mouse device to /dev/mouse.
```
```text
/etc/sysconfig/harddisks
The /etc/sysconfig/harddisks file allows you to tune your hard drive(s). You can also use /
etc/sysconfig/hardiskhd[a-h], to configure parameters for specific drives.
```
```text
Warning
Do not make changes to this file lightly. If you change the default values stored here, you could
corrupt all of the data on your hard drive(s).
```
```text
The /etc/sysconfig/harddisks file may contain the following:
```
USE_DMA=1, where setting this to 1 enables DMA. However, with some chipsets and hard drive combinations,
DMA can cause data corruption. Check with your hard drive documentation or manufacturer before enabling this.
Multiple_IO=16, where a setting of 16 allows for multiple sectors per I/O interrupt. When enabled,
this feature reduces operating system overhead by 30-50%. Use with caution.
EIDE_32BIT=3 enables (E)IDE 32-bit I/O support to an interface card.
LOOKAHEAD=1 enables drive read-lookahead.
EXTRA_PARAMS= specifies where extra parameters can be added.
```text
/etc/sysconfig/hwconf
The /etc/sysconfig/hwconf file lists all the hardware that kudzu detected on your system, as well as
the drivers used, vendor ID and device ID information. The kudzu program detects and configures new and/or
changed hardware on a system. The /etc/sysconfig/hwconf file is not meant to be manually edited.
If you do edit it, devices could suddenly show up as being added or removed.
```
```text
/etc/sysconfig/i18n
The /etc/sysconfig/i18n file sets the default language, such as:
```
LANG="en_US"
```text
/etc/sysconfig/identd
The /etc/sysconfig/identd file is used to pass arguments to the identd daemon at boot time.
The identd daemon returns the username of processes with open TCP/IP connections. Some services on
the network, such as FTP and IRC servers, will complain and cause slow responses if identd is not running.
But in general, identd is not a required service, so if security is a concern, you should not run it.
For more information about what parameters you can use in this file, type man identd. By default,
the file contains no parameters.
```
```text
/etc/sysconfig/init
The /etc/sysconfig/init file controls how the system will appear and function during the boot process.
```
The following values may be used:
BOOTUP=, where is one of the following:
BOOTUP=color means the standard color boot display, where the success or failure of devices and services starting up is shown in different colors.
BOOTUP=verbose means an old style display, which provides more information than purely a message of success or failure.
Anything else means a new display, but without ANSI-formatting.
RES_COL=, where is the number of the column of the screen to start status labels. Defaults to 60.
MOVE_TO_COL=, where moves the cursor to the value in the RES_COL line. Defaults to ANSI sequences output by echo -e.
SETCOLOR_SUCCESS=, where sets the color to a color indicating success. Defaults to ANSI sequences output by echo -e, setting the color to green.
SETCOLOR_FAILURE=, where sets the color to a color indicating failure. Defaults to ANSI sequences output by echo -e, setting the color to red.
SETCOLOR_WARNING=, where sets the color to a color indicating warning. Defaults to ANSI sequences output by echo -e, setting the color to yellow.
SETCOLOR_NORMAL=, where sets the color to 'normal'. Defaults to ANSI sequences output by echo -e.
LOGLEVEL=, where sets the initial console logging level for the kernel. The default is 7; 8 means everything (including debugging); 1 means nothing except kernel panics. syslogd will override this once it starts.
PROMPT=, where is one of the following boolean values:
yes - Enables the key check for interactive mode.
no - Disables the key check for interactive mode.
```text
/etc/sysconfig/ipchains
The /etc/sysconfig/ipchains file contains information used by the kernel to set up ipchains packet filtering rules at boot time or whenever the service is started.
```
```text
This file is modified by typing the command /sbin/service ipchains save when valid ipchains rules are in place. You should not manually edit this file. Instead, use the /sbin/ipchains command to configure the necessary packet filtering rules and then save the rules to this file using /sbin/service ipchains save.
```
Use of ipchains to set up firewall rules is not recommended as it is deprecated and may disappear from future releases of Red Hat Linux. If you need a firewall, you should use iptables instead.
```text
/etc/sysconfig/iptables
Like /etc/sysconfig/ipchains, the /etc/sysconfig/iptables file stores information used by the kernel to set up packet filtering services at boot time or whenever the service is started.
```
```text
You should not modify this file by hand unless you are familiar with how to construct iptables rules. The simplest way to add rules is to use the /usr/sbin/lokkit command or the gnome-lokkit graphical application to create your firewall. Using these applications will automatically edit this file at the end of the process.
```
```text
If you wish, you can manually create rules using /sbin/iptables and then type /sbin/service iptables save to add the rules to the /etc/sysconfig/iptables file.
```
Once this file exists, any firewall rules saved there will persist through a system reboot or a service restart.
For more information on iptables see Chapter 13.
```text
/etc/sysconfig/irda
The /etc/sysconfig/irda file controls how infrared devices on your system are configured at startup.
```
The following values may be used:
IRDA=, where is one of the following boolean values:
yes - irattach will be run, which periodically checks to see if anything is trying to connect to the infrared port, such as another notebook computer trying to make a network connection. For infrared devices to work on your system, this line must be set to yes.
no - irattach will not be run, preventing infrared device communication.
DEVICE=, where is the device (usually a serial port) that handles infrared connections.
DONGLE=, where specifies the type of dongle being used for infrared communication. This setting exists for people who use serial dongles rather than real infrared ports. A dongle is a device that is attached to a traditional serial port to communicate via infrared. This line is commented out by default because notebooks with real infrared ports are far more common than computers with add-on dongles.
DISCOVERY=, where is one of the following boolean values:d
yes - Starts irattach in discovery mode, meaning it actively checks for other infrared devices. This needs to be turned on for the machine to be actively looking for an infrared connection (meaning the peer that does not initiate the connection).
no - Does not start irattach in discovery mode.
```text
/etc/sysconfig/keyboard
The /etc/sysconfig/keyboard file controls the behavior of the keyboard. The following values may be used:
```
```text
KEYBOARDTYPE=sun|pc, which is used on SPARCs only. sun means a Sun keyboard is attached on /dev/kbd, and pc means a PS/2 keyboard connected to a PS/2 port.
```
KEYTABLE=, where is the name of a keytable file.
```text
For example: KEYTABLE="us". The files that can be used as keytables start in /lib/kbd/keymaps/i386 and branch into different keyboard layouts from there, all labeled .kmap.gz. The first file found beneath /lib/kbd/keymaps/i386that matches the KEYTABLE setting is used.
```
```text
/etc/sysconfig/kudzu
The /etc/sysconfig/kuzdu allows you to specify a safe probe of your system's hardware by kudzu at boot time. A safe probe is one that disables serial port probing.
```
SAFE=, where is one of the following:
yes - kuzdu does a safe probe.
no - kuzdu does a normal probe.
```text
/etc/sysconfig/mouse
The /etc/sysconfig/mouse file is used to specify information about the available mouse. The following values may be used:
```
FULLNAME=, where refers to the full name of the kind of mouse being used.
MOUSETYPE=, where is one of the following:
microsoft - A MicrosoftT mouse.
mouseman - A MouseManT mouse.
mousesystems - A Mouse SystemsT mouse.
ps/2 - A PS/2 mouse.
msbm - A MicrosoftT bus mouse.
logibm - A LogitechT bus mouse.
atibm - An ATIT bus mouse.
logitech - A LogitechT mouse.
mmseries - An older MouseManT mouse.
mmhittab - An mmhittab mouse.
XEMU3=, where is one of the following boolean values:
yes - The mouse only has two buttons, but three mouse buttons should be emulated.
no - The mouse already has three buttons.
XMOUSETYPE=, where refers to the kind of mouse used when X is running. The options here are the same as the MOUSETYPE setting in this same file.
DEVICE=, where is the mouse device.
```text
In addition, /dev/mouse is a symbolic link that points to the actual mouse device.
```
```text
/etc/sysconfig/named
The /etc/sysconfig/named file is used to pass arguments to the named daemon at boot time. The named daemon is a Domain Name System (DNS) server which implements the Berkeley Internet Name Domain (BIND) version 9 distribution. This server maintains a table of which hostnames are associated with IP addresses on the network.
```
Currently, only the following values may be used:
```text
ROOTDIR="", where refers to the full directory path of a configured chroot environment under which named will run. This chroot environment must first be configured. Type info chroot for more information on how to do this.
```
OPTIONS="", where any option listed in the man page for named except -t. In place of -t, use the ROOTDIR line above instead.
For more information about what parameters you can use in this file, type man named. For detailed information on how to configure a BIND DNS server, see Chapter 16. By default, the file contains no parameters.
```text
/etc/sysconfig/netdump
The /etc/sysconfig/netdump file is the configuration file for the /etc/init.d/netdump service. The netdump service sends both oops data and memory dumps over the network. In general, netdump is not a required service, so you should only run it if you absolutely need to. For more information about what parameters you can use in this file, type man netdump.
```
```text
/etc/sysconfig/network
The /etc/sysconfig/network file is used to specify information about the desired network configuration. The following values may be used:
```
NETWORKING=, where is one of the following boolean values:
yes - Networking should be configured.
no - Networking should not be configured.
HOSTNAME=, where should be the Fully Qualified Domain Name (FQDN), such as hostname.domain.com, but can be whatever hostname you want.
```text
Note
For compatibility with older software that people might install (such as trn), the /etc/HOSTNAME file should contain the same value as here.
```
GATEWAY=, where is the IP address of the network's gateway.
GATEWAYDEV=, where is the gateway device, such as eth0.
NISDOMAIN=, where is the NIS domain name.
```text
/etc/sysconfig/ntpd
The /etc/sysconfig/ntpd file is used to pass arguments to the ntpd daemon at boot time. The ntpd daemon sets and maintains the system clock to synchronize with an Internet standard time server. It implements version 4 of the Network Time Protocol (NTP). For more information about what parameters you can use in this file, point a browser at the following file: /usr/share/doc/ntp-/ntpd.htm (where is the version number of ntpd). By default, this file sets the owner of the ntpd process to the user ntp.
```
```text
/etc/sysconfig/pcmcia
The /etc/sysconfig/pcmcia file is used to specify PCMCIA configuration information. The following values may be used:
```
PCMCIA=, where is one of the following:
yes - PCMCIA support should be enabled.
no - PCMCIA support should not be enabled.
PCIC=, where is one of the following:
i82365 - The computer has an i82365-style PCMCIA socket chipset.
tcic - The computer has a tcic-style PCMCIA socket chipset.
PCIC_OPTS=, where is the socket driver (i82365 or tcic) timing parameters.
CORE_OPTS=, where is the list of pcmcia_core options.
CARDMGR_OPTS=, where is the list of options for the PCMCIA cardmgr (such as -q for quiet mode; -m to look for loadable kernel modules in the specified directory, and so on). Read the cardmgr man page for more information.
```text
/etc/sysconfig/radvd
The /etc/sysconfig/radvd file is used to pass arguments to the radvd daemon at boot time. The radvd daemon listens to for router requests and sends router advertisements for the IP version 6 protocol. This service allows hosts on a network to dynamically change their default routers based on these router advertisements. For more information about what parameters you can use in this file, type man radvd. By default, this file sets the owner of the radvd process to the user radvd.
```
```text
/etc/sysconfig/rawdevices
The /etc/sysconfig/rawdevices file is used to configure raw device bindings, such as:
```
```text
/dev/raw/raw1 /dev/sda1
/dev/raw/raw2 8 5
```
```text
/etc/sysconfig/redhat-config-users
The /etc/sysconfig/redhat-config-users file is the configuration file for the graphical application, User Manager. Under Red Hat Linux 8.0 this file is used to filter out system users such as root, daemon, or lp. This file is edited by the Preferences => Filter system users and groups pull-down menu in the User Manager application and should not be edited by hand. For more information on using this application, see the chapter called User and Group Configuration in the Official Red Hat Linux Customization Guide.
```
```text
/etc/sysconfig/redhat-logviewer
The /etc/sysconfig/redhat-logviewer file is the configuration file for the graphical, interactive log viewing application, Log Viewer. This file is edited by the Edit => Preferences pull-down menu in the Log Viewer application and should not be edited by hand. For more information on using this application, see the chapter called Log Files in the Official Red Hat Linux Customization Guide.
```
```text
/etc/sysconfig/samba
The /etc/sysconfig/samba file is used to pass arguments to the smbd and the nmbd daemons at boot time. The smbd daemon offers file sharing connectivity for Windows clients on the network. The nmbd daemon offers NetBIOS over IP naming services. For more information about what parameters you can use in this file, type man smbd. By default, this file sets smbd and nmbd to run in daemon mode.
```
```text
/etc/sysconfig/sendmail
The /etc/sysconfig/sendmail file allows messages to be sent to one or more recipients, routing the message over whatever networks are necessary. The file sets the default values for the Sendmail application to run. Its default values are to run as a background daemon, and to check its queue once an hour in case something has backed up.
```
The following values may be used:
DAEMON=, where is one of the following boolean values:
yes - Sendmail should be configured to listen to port 25 for incoming mail. yes implies the use of Sendmail's -bd options.
no - Sendmail should not be configured to listen to port 25 for incoming mail.
```text
QUEUE=1h which is given to Sendmail as -q$QUEUE. The -q option is not given to Sendmail if /etc/sysconfig/sendmail exists and QUEUE is empty or undefined.
```
```text
/etc/sysconfig/soundcard
The /etc/sysconfig/soundcard file is generated by sndconfig and should not be modified. The sole use of this file is to determine what card entry in the menu to pop up by default the next time sndconfig is run. Sound card configuration information is located in the /etc/modules.conf file.
```
It may contain the following:
CARDTYPE=, where is set to, for example, SB16 for a Soundblaster 16 sound card.
```text
/etc/sysconfig/squid
The /etc/sysconfig/squid file is used to pass arguments to the squid daemon at boot time. The squid daemon is a proxy caching server for Web client applications. For more information on configuring a squid proxy server, use a Web browser to open the /usr/share/doc/squid-/ directory (replace with the squid version number installed on your system). By default, this file sets squid top start in daemon mode and sets the amount of time before it shuts itself down.
```
```text
/etc/sysconfig/tux
The /etc/sysconfig/tux file is the configuration file for the Red Hat Content Accelerator (formerly known as TUX), the kernel-based web server. For more information on configuring the Red Hat Content Accelerator, use a Web browser to open the /usr/share/doc/tux-/tux/index.html (replace with the version number of TUX installed on your system). The parameters available for this file are listed in /usr/share/doc/tux-/tux/parameters.html.
```
```text
/etc/sysconfig/ups
The /etc/sysconfig/ups file is used to specify information about any Uninterruptible Power Supplies (UPS) connected to your system. A UPS can be very valuable for a Red Hat Linux system because it gives you time to correctly shut down the system in the case of power interruption. The following values may be used:
```
SERVER=, where is one of the following:
yes - A UPS device is connected to your system.
no - A UPS device is not connected to your system.
MODEL=, where must be one of the following or set to NONE if no UPS is connected to the system:
apcsmart - For a APC SmartUPST or similar device.
fentonups - For a Fenton UPST.
optiups - For an OPTI-UPST device.
bestups - For a Best PowerT UPS.
genericups - For a generic brand UPS.
ups-trust425+625 - For a TrustT UPS.
```text
DEVICE=, where specifies where the UPS is connected, such as /dev/ttyS0.
```
OPTIONS=, where is a special command that needs to be passed to the UPS.
```text
/etc/sysconfig/vncservers
The /etc/sysconfig/vncservers file configures the way the Virtual Network Computing (VNC) server starts up.
```
VNC is a remote display system which allows you to view a desktop environment not only on the machine where it is running but across different networks on a variety of architectures.
It may contain the following:
VNCSERVERS=, where is set to something like "1:fred", to indicate that a VNC server should be started for user fred on display :1. User fred must have set a VNC password using vncpasswd before attempting to connect to the remote VNC server.
```text
Note that when you use a VNC server, your communication with it is unencrypted, and so it should not be used on an untrusted network. For specific instructions concerning the use of SSH to secure the VNC communication, please read the information found at http://www.uk.research.att.com/vnc/sshvnc.html. To find out more about SSH, see Chapter 9 or Official Red Hat Linux Customization Guide.
```
```text
/etc/sysconfig/xinetd
The /etc/sysconfig/xinetd file is used to pass arguments to the xinetd daemon at boot time.
The xinetd daemon starts programs that provide Internet services when a request to the port for that service
is received. For more information about what parameters you can use in this file, type man xinetd.
For more information on the xinetd service, see the Section called Access Control Using xinetd in Chapter 8.
```
```text
Directories in the /etc/sysconfig/ Directory
The following directories are normally found in /etc/sysconfig/ and a basic description of what they contain:
```
```text
apm-scripts - This contains the Red Hat APM suspend/resume script. You should not edit this file directly. If you need customization, simple create a file called /etc/sysconfig/apm-scripts/apmcontinue and it will be called at the end of the script. Also, you can control the script by editing /etc/sysconfig/apmd.
```
cbq - This directory contains the configuration files needed to do Class Based Queuing for bandwidth management on network interfaces.
networking - This directory is used by the Network Administration Tool (redhat-config-network) and its contents should not be edited manually. For more information about configuring network interfaces using the Network Administration Tool, see the chapter called Network Configuration in the Official Red Hat Linux Customization Guide.
network-scripts - This directory contains the following network-related configuration files:
Network configuration files for each configured network interface, such as ifcfg-eth0 for the eth0 Ethernet interface.
Scripts used to bring up and down network interfaces, such as ifup and ifdown.
Scripts used to bring up and down ISDN interfaces, such as ifup-isdn and ifdown-isdn
Various shared network function scripts which should not be edited directly.
For more information on the network-scripts directory, see Chapter 12
rhn - This directory contains the configuration files and GPG keys for the Red Hat Network. No files in this directory should be edited by hand. For more information on the Red Hat Network, see the Red Hat Network website at the following URL: https://rhn.redhat.com.
```
Changing the IP adress:
```text
# smitty mktcpip
# smitty chinet
```
or use the ifconfig command, like for example:
```text
# ifconfig tr0 up # activate interface
# ifconfig tr0 down # deactivate interface
# ifconfig tr0 detach # removes the interface
# ifconfig tr0 # put it back again
# ifconfig tr0 delete # delete the IP address
# ifconfig en0 10.1.2.3 netmask 255.255.255.0 up # configure IP params on the interface
```
You can even use the chdev command like:
```text
# chdev -l en0 -a netaddr='9.3.240.58' -a netmask='255.255.255.0'
```
Smitty and chdev will update the ODM database, and makes changes permanent, while ifconfig commands will not.
RPM file.
- Host-Based Access Control Lists
Host-based access for services that use TCP wrappers is controlled by two files:
```text
/etc/hosts.allow and /etc/hosts.deny.
```
These file use a simple format to control access to services on a server.
If no rules are specified in either hosts.allow or hosts.deny, then the default rule is to allow anyone
to access to the services.
Order is important since rules in hosts.allow take precedence over rules specified in hosts.deny.
Even if a rule specifically denying all access to a particular service is defined in hosts.deny,
hosts specifically given access to the service in hosts.allow are allowed to access the service.
In addition, all rules in each file take effect from the top down.
Any changes to these files take effect immediately, so restarting services is not required.
Formatting Rules
All access control rules are placed on lines within hosts.allow and hosts.deny, and any blank lines
or lines that start with the comment character (#) are ignored. Each rule needs to be on its own line.
The rules must be formatted in the following manner:
: [: spawn ]
Patterns are particularly helpful when specifying groups of clients that may or may not access a certain service.
By placing a "." character at the beginning of a string, all hosts that share the end of that string
are applied to that rule. So, .domain.com would catch both system1.domain.com and system2.domain.com.
The "." character at the end of a string has the same effect, except going the other direction.
This is primarily used for IP addresses, as a rule pertaining to 192.168.0. would apply to the entire
class C block of IP addresses. Netmask expressions can also be used as a pattern to control access to a
particular group of IP addresses. You can even use asterisks (*) or question marks (?) to select entire
groups of hostnames or IP addresses, so long as you do not use them in the same string as the other
types of patterns.
This access control "language" can be extended with the following wildcards. They may be used in the access
control rules instead of using specific hosts or groups of hosts:
```text
ALL - Matches every client with a service. To allow a client access to all services,
use the ALL in the daemons section.
LOCAL - Matches any host that does not contain a "." character.
KNOWN - Matches any host where the hostname and host address are known or where the user is known.
UNKNOWN - Matches any host where the hostname or host address are unknown or where the user is unknown.
PARANOID - Matches any host where the hostname does not match the host address.
```
You can use the above wildcards in combination with the EXCEPT operator.
Example:
```text
# all domain.com hosts are allowed to connect
# to all services except cracker.domain.com
ALL: .domain.com EXCEPT cracker.domain.com
```
```text
# 123.123.123.* addresses can use all services except FTP
ALL EXCEPT in.ftpd: 123.123.123.
```
Users that wish to prevent any hosts other than specific ones from accessing services usually place
ALL: ALL in hosts.deny. Then, they place lines in hosts.allow, such as:
in.telnetd: 10.0.1.24
in.ftpd: 10.0.1. EXCEPT 10.0.1.1
- Shell commands:
Beyond simply allowing or denying access to services for certain hosts, the TCP wrappers also supports
the use of shell commands. These shell commands are most commonly used with deny rules to set up booby traps,
which usually trigger actions that log information about failed attempts to a special file or email
an administrator. Below is an example of a booby trap in the hosts.deny file which will write a log line
containing the date and client information every time a host from the the IP range 10.0.1.0 to 10.0.1.255
attempts to connect via Telnet:
```text
in.telnetd: 10.0.1.: spawn (/bin/echo `date` %c >> /var/log/telnet.log) &
```
The following expansions can be used:
%a - The client's IP address.
%A - The server's IP address.
%c - Supplies a variety of client information, such as the username and hostname, or the username and IP address.
%d - The daemon process name.
%h - The client's hostname (or IP address, if the hostname is unavailable).
%H - The server's hostname (or IP address, if the hostname is unavailable).
%n - The client's hostname. If unavailable, unknown is printed.
%N - The server's hostname. If unavailable, unknown is printed.
%p - The daemon process ID.
%s - Various types of server information, such as the daemon process and the host or IP address of the server.
%u - The client's username. If unavailable, unknown is printed.
- For each network interface on a Red Hat Linux system,
there is a corresponding interface configuration script.
Each of these files provide information specific to a
particular network interface.
Caution
The "/etc/sysconfig/networking/" directory is used by the Network Administration Tool (redhat-config-network)
and its contents should not be edited manually.
```
- Interface Configuration Files
Interface configuration files control the operation of individual network interface device.
As your Red Hat Linux system boots, it uses these files to determine what interfaces to bring up and how
to configure them. These files are usually named "ifcfg-