/ *********************************************************************** *****/ /* 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 */ /* Best use : Use find/search in your editor to find a string, command, */ /* or any identifier */ / *********************************************************************** *****/
############################################ SECTION 1. COMMANDS TO RETREIVE SYSTEM INFO: ############################################ ========================== 1. HOW TO GET SYSTEM INFO: ========================== 1.1 Short version: ================== See section 1.2 for more detailed commands and options. Memory: ------AIX:
Linux:
bootinfo -r lsattr -E -l mem0 lsattr -E -l sys0 -a realmem svmon -G vmstat -v vmo -L lparstat -i or use a tool as "topas" or "nmon" (these are utilities) cat /proc/meminfo dmesg | grep "Physical" free (the free command)
HP:
getmem grep MemTotal /proc/meminfo dmesg | grep -i phys wc -c /dev/mem or us a tool as "glance", like entering "glance -m" from prompt (is a utility) Solaris: prtconf | grep "Memory size" # total memory prtmem memps -m Tru64: vmstat -P | grep "Total Physical Memory" uerf | grep memory Swap: ----AIX:
lsps -a lsps -s pstat -s
HP: Solaris:
swapinfo -a swap -l prtswap -l swapon -s cat /proc/swaps cat /proc/meminfo
Linux:
cpu: ---HP:
ioscan -kfnC processor getconf CPU_VERSION getconf CPU_CHIP_TYPE model
AIX:
lparstat (-i) prtconf | grep proc pmcycles -m lsattr -El procx (x is 0,2, etc..) lscfg | grep proc pstat -S mpstat
Linux:
cat /proc/cpuinfo
Solaris:
psrinfo -v prtconf psrset -p prtdiag
OS version: -----------
HP:
uname -a
Linux:
cat /proc/version
Solaris: uname -a cat /etc/release (or other way to view that file, like "more /etc/release") Tru64: /usr/sbin/sizer -v AIX:
oslevel -r (only high-level version) oslevel -s (shows Version, SP, TL level) oslevel -qs (shows complete history) lslpp -h bos.rte
AIX Example: # oslevel -s 5300-08-03-0831 # oslevel -qs Known Service Packs ------------------5300-08-03-0831 5300-08-02-0822 5300-08-01-0819 5300-08-00-0000 5300-07-05-0831 5300-07-04-0818 5300-07-03-0811 5300-07-02-0806 5300-07-01-0748 5300-06-08-0831 5300-06-07-0818 5300-06-06-0811 5300-06-05-0806 5300-06-04-0748 5300-06-03-0732 5300-06-02-0727 5300-06-01-0722 5300-05-CSP-0000 5300-05-06-0000 5300-05-05-0000 5300-05-04-0000 5300-05-03-0000 5300-05-02-0000 5300-05-01-0000 5300-04-CSP-0000 5300-04-03-0000 5300-04-02-0000 5300-04-01-0000 5300-03-CSP-0000
AIX firmware:
lsmcode -c processor lsmcode -r -d scraid0 RAID adapter scraid0 lsmcode -A devices prtconf serial# etc..
display the system firmware level and service display the adapter microcode levels for a display the microcode level for all supported shows many setting including memory, firmware,
Notes about Power 4 or 5 lpars: ------------------------------For AIX: The uname -L command identifies a partition on a system with multiple LPARS. The LPAR id can be useful for writing shell scripts that customize system settings such as IP address or hostname. The output of the command looks like: # uname -L 1 lpar01 The output of uname -L varies by maintenance level. For consistent output across maintenance levels, add a -s flag. For illustrate, the following command assigns the partition number to the variable "lpar_number" and partiton name to "lpar_name". For HP-UX: Use commands like "parstatus" or "getconf PARTITION_IDENT" to get npar information.
patches: -------AIX:
Is a certain fix (APAR) installed? instfix -ik APAR_number instfix -a -ivk APAR_number
To determine your platform firmware level, at the command prompt, type: lscfg -vp | grep -p Platform The last six digits of the ROM level represent the platform firmware date in the format, YYMMDD. HP:
/usr/sbin/swlist -l patch swlist | grep patch Linux: rpm -qa Solaris: showrev -p
pkginfo -i package_name /usr/sbin/dupatch -track -type kit
Tru64:
Netcards: --------AIX:
lsdev -Cc adapter lsdev -Cc adapter | grep ent lsdev -Cc if lsattr -E -l ent1 ifconfig -a Solaris: prtconf -D / prtconf -pv prtdiag | grep "card" svcs -x ifconfig -a (up plumb)
/
prtconf | grep "card"
Quickly find out who is using most memory: -----------------------------------------See section marked &&& (use find/search on &&&)
Network sniffing: ----------------Here are a few short descriptions, and examples, of usefull network trace / dump commands. -- Solaris: snoop command examples: For example, if we want to observe traffic between systems alpha and beta we can use the following command: # snoop alpha,beta To enable data captures from the snoop output without losing packets while writing to the screen, send the snoop output to a file. For example: # snoop -o /tmp/snooper -V 128.50.1.250 To snoop a specific port: # snoop -o port xxx -- AIX: tcpdump command examples: # tcpdump port 23 # tcpdump -i en0
A good way to use tcpdump is to save the network trace to a file with the -w flag and then analyze the trace by using different filtering options together with the -r flag. The following example show how to run a basic tcpdump network trace, saving the output in a file with the -w flag (on a Ethernet network interface): # tcpdump -w /tmp/tcpdump.en0 -i en0 To limit the number of traced packets, use the -c flag and specify the number, such as in the following example that traces the first 128 packets (on a token-ring network interface): # tcpdump -c 128 -w /tmp/tcpdump.tr0 -i tr0 iptrace command examples: To start the iptrace daemon with the System Resource Controller (SRC), # startsrc -s iptrace -a "/tmp/nettrace" To stop the iptrace daemon with SRC enter the following: # stopsrc -s iptrace To record packets coming in and going out to any host on every interface, enter the command in the following format: # iptrace /tmp/nettrace The recorded packets are received on and sent from the local host. All packet flow between the local host and all other hosts on any interface is recorded. The trace information is placed into the /tmp/nettrace file. To record packets received on an interface from a specific remote host, enter the command in the following format: # iptrace - i en0 -p telnet -s airmail /tmp/telnet.trace The packets to be recorded are received on the en0 interface, from remote hostairmail, over the telnet port. The trace information is placed into the /tmp/telnet.trace file. To record packets coming in and going out from a specific remote host, enter the command in the following format: # iptrace -i en0 -s airmail -b /tmp/telnet.trace The packets to be recorded are received on the en0 interface, from remote host airmail. The trace information is placed into the /tmp/telnet.trace file. -- HPUX: nettl command: Initialize the tracing/logging facility: # nettl -start
Logging is enabled for all subsystems as determined by the /etc/nettlgen.conf file. Log messages are sent to a log file whose name is determined by adding the suffix .LOG000 to the log file name specified in the /etc/nettlgen.conf configuration file. To stop the tracing facility: # nettl -stop Turn on inbound and outbound PDU tracing for the transport and session (OTS/9000) subsystems and send binary trace messages to file /var/adm/trace.TRC000. # nettl -traceon pduin pduout -entity transport session \ -file /var/adm/trace Session using nettl and the formatter netfmt: 1. Capture packets nettl -tn all -e ns_ls_ip -tm 99999 -size 1024 -f some-raw-capture-file 2. Reproduce problem. 3. Turn off trace: nettl -tf -e all 4. Create formatter filter file. Example: filter tcp_sport 6699 filter tcp_dport 6699 5. Filter the packets: 5.1 "Long" display netfmt -Nlnc filter-file -f some-raw.capture > formatted.out 5.2 "One-liner" display netfmt -Nln1Tc filter-file -f some-raw.capture > one-liner.out -- Restart inetd, nfs: -- ------------------Starting and stopping NFS: -------------------------On all unixes, a number of daemons should be running in order for NFS to be functional, like for example the rpc.* processes, biod, nfsd and others. Once nfs is running, and in order to actually "share" or "export" your filesystem on your server, so remote clients are able to mount the nfs mount, in most cases you should edit the "/etc/exports" file. -- AIX: The following subsystems are part of the nfs group: nfsd, biod, rpc.lockd, rpc.statd, and rpc.mountd. The nfs subsystem (group) is under control of the "resource controller", so starting and stopping nfs is actually easy # startsrc -g nfs
# stopsrc -g nfs Or use smitty. -- Redhat Linux: # /sbin/service nfs restart # /sbin/service nfs start # /sbin/service nfs stop -- On some other Linux distros # /etc/init.d/nfs start # /etc/init.d/nfs stop # /etc/init.d/nfs restart -- Solaris: If the nfs daemons aren't running, then you will need to run: # /etc/init.d/nfs.server start -- HP-UX: Issue the following command on the NFS server to start all the necessary NFS processes (HP): # /sbin/init.d/nfs.server start Or if your machine is only a client: # cd /sbin/init.d # ./nfs.client start Restart or refresh inetd after you have edited "inetd.conf": -----------------------------------------------------------After you have edited "/etc/inetd.conf", for example, to enable or disable some service, you need to restart, or refresh inetd, to read the new configuration information. To let inetd to reread the configfile: -- AIX: # refresh -s inetd -- HPUX: # /usr/sbin/inetd -c -- Solaris: # /etc/init.d/inetd stop # /etc/init.d/inetd start # pkill -HUP inetd reread the configuration. -- RedHat / Linux # service xinetd restart or # /etc/init.d/inetd restart
1.2 More Detail:
# The command will restart the inetd and
================ 1.2.1 Show memory in Solaris: ============================= prtconf: -------Use this command to obtain detailed system information about your Sun Solaris installation # /usr/sbin/prtconf # prtconf -v Displays the size of the system memory and reports information about peripheral devices Use this command to see the amount of memory: # /usr/sbin/prtconf | grep "Mem" sysdef -i reports on several system resource limits. Other parameters can be checked on a running system using adb -k : # adb -k /dev/ksyms /dev/mem parameter-name/D ^D (to exit) Other commands: --------------# prtmem # memps -m
1.2.2 Show memory in AIX: ========================= >> Show Total memory: --------=====-------# bootinfo -r # lsattr -El sys0 -a realmem # prtconf (you can grep it on memory) >> Show Details of memory: -------------------------You can have a more detailed and comprehensive look at AIX memory by using "vmstat -v" and "vmo -L" or "vmo -a": For example: # vmstat -v 524288 memory pages 493252 lruable pages 67384 free pages
7 131820 80.0 20.0 80.0 25.4 125727 0.0 0 25.4 80.0 125575 0 14557 6526890 18631 0 49038 fsbuf faults
memory pools pinned pages maxpin percentage minperm percentage maxperm percentage numperm percentage file pages compressed percentage compressed pages numclient percentage maxclient percentage client pages remote pageouts scheduled pending disk I/Os blocked with no pbuf paging space I/Os blocked with no psbuf filesystem I/Os blocked with no fsbuf client filesystem I/Os blocked with no fsbuf external pager filesystem I/Os blocked with no
0 Virtualized Partition Memory Page Faults 0.00 Time resolving virtualized partition memory page
The vmo command really gives lots of output. In the following example only a small fraction of the output is shown: # vmo -L .. lrubucket 128K 128K 128K 64K 4KB pages D ------------------------------------------------------------------------------maxclient% 80 80 80 1 100 % memory D maxperm% minperm% ------------------------------------------------------------------------------maxfree 1088 1088 1088 8 200K 4KB pages D minfree memory_frames ------------------------------------------------------------------------------maxperm 394596 394596 S ------------------------------------------------------------------------------maxperm% 80 80 80 1 100 % memory D minperm% maxclient% -------------------------------------------------------------------------------
maxpin S .. ..
424179
424179
>> To further look at your virtual memory and its causes, you can use a combination of: -------------------------------------------------------------------------------------# # # # # # #
ipcs -bm lsps -a vmo -a or vmo -L svmon -G svmon -U svmon -P vmstat -v
(shared memory) (paging) (virtual memory options) (basic memory allocations) (virtual memory usage by user)
To print out the memory usage statistics for the users root and steve
taking into account only working segments, type: svmon -U root steve -w To print out the top 10 users of the paging space, type: svmon -U -g -t 10
To print out the memory usage statistics for the user steve, including the list of the process identifiers, type: svmon -U steve -l svmon -U emcdm -l # vmo -o npswarn=value # schedo -o pacefork=15 Note: sysdumpdev -e Although the sysdumpdev command is used to show or alter the dumpdevice for a system dump, you can also use it to show how much real memory is used. The command # sysdumpdev -e provides an estimated dump size taking into account the current memory (not pagingspace) currently in use by the system. Note: the rmss command: The rmss (Reduced-Memory System Simulator) command is used to ascertain the effects of reducing the amount of available memory on a system without the need to physically remove memory from the system. It is useful
for system sizing, as you can install more memory than is required and then use rmss to reduce it. Using other performance tools, the effects of the reduced memory can be monitored. The rmss command has the ability to run a command multiple times using different simulated memory sizes and produce statistics for all of those memory sizes. The rmss command resides in /usr/bin and is part of the bos.perf.tools fileset, which is installable from the AIX base installation media. Syntax rmss -p -c
-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 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 The pstat command: -----------------The pstat command, which displays many system tables such as a process table, inode table, or processor status table, The pstat command interprets the contents of the various system tables and writes it to standard output. Use the pstat command from the AIX 5.2 command prompt. See the command reference for details and examples, or use the syntax summary in the table below. Flags -a -A -f -i addresses -p -P -s usage -S -t 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: $ 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 ---------------------------------------------------------------------Remark: many Linux distros adopted the ptree command, as the "pstree" command. As in 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.. .. ----------------------------------------------------------------------Back to Solaris again: Suppose you did a pfiles on an Apache process: # pfiles 13789 -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: Pid Command LPage 10556 java N Vsid Pgsp Virtual 22ac4 21047 126a2 7908c b2ad6 b1475 282 65536 30fe5 285 65536 91072 54 65536 6bced 261 65536 b1035 0 45054 e0f9f 3 48284 19100 463 47210 c965a 281 46953 7910c 0 37070 0, 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. Warning: nfs 0 0 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. 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 : # mount -F nfs hpsrv:/data /data # mount -F nfs -o hard,intr thor:/data From the Main Menu, make the following selections: -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. The utility displays the Main Menu. From the Main Menu, make the following selections: -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 Primary Authentication method of system: ---------------------------------------To check whether root has a primary authentication method of SYSTEM, use the following command: # lsuser -a auth1 root If needed, change the value by using # chuser auth1=SYSTEM root 3.4 Add a user in HP-UX: ------------------------- Example 1: Add user john to the system with all of the default attributes. # useradd john Add the user john to the system with a UID of 222 and a primary group of staff. # useradd -u 222 -g staff john -- Example 2: => => => => => 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: castle% chmod 1777 pubdir castle% ls -l pubdir drwxrwxrwt 2 winsor staff castle% and press Return. and press Return to verify that the the file have changed. 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: #chmod 2551 myprog2 #ls -l myprog2 -r-xr-s-x 1 winsor #[email protected] " 0 1 1 1-12/3 * /usr/local/bin/vnukelog This will run the command "/usr/local/bin/vnukelog" (which clears all of your log files) at 1 AM on the first day of the first month of every quarter, or January, April, July, and October (1-12/3). Obviously, you will need to substitute a valid e-mail address in the place of "[email protected] ". If you have created this file on your local computer, FTP the file up to your Virtual Server and store it in your home directory under the name "cronjobs" (you can actually use any name you would like). Register your cronjobs file with the system After you have created your cronjobs file (and have uploaded it to your Virtual Server if applicable), you need to Telnet to your server and register the file with the cron system daemon. To do this, simply type: crontab cronjobs Or if you used a name other than "cronjobs", substitute the name you selected for the occurrence of "cronjobs" above. Note 3: ------# use /bin/sh to run commands, no matter what /etc/passwd says SHELL=/bin/sh # mail any output to `paul', no matter whose crontab this is MAILTO=paul # # run five minutes after midnight, every day 5 6-18 * * * /opt/app/oracle/admin/scripts/grepora.sh # run at 2:15pm on the first of every month -- output mailed to paul 15 14 1 * * $HOME/bin/monthly # run at 10 pm on weekdays, annoy Joe 0 22 * * 1-5 mail -s "It's 10pm" joe%Joe,%%Where are your kids?% 23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday" 5 4 * * sun echo "run at 5 after 4 every sunday" 2>&1 means: It means that standard error is redirected along with standard output. Standard error could be redirected to a different file, like job 912687240.a at Thu Jun 6 07:14:00 to duplicate a tape: # dd if=/dev/rmt/0 of=/dev/rmt/1 to clone a disk with the same geometry: # dd if=/dev/rdsk/c0t1d0s2 of=/dev/rdsk/c0t4d0s2 bs=128 AIX: ---same command syntax apply to IBM AIX. Here is an AIX pSeries machine with floppydrive example: clone a diskette: # dd if=/dev/fd0 of=/tmp/ddcopy # dd if=/tmp/ddcopy of=/dev/fd0 Note: On Linux distros the device associated to the floppy drive is also /dev/fd0 9.6 cpio: ========= solaris: -------cpio copy-out: cpio -o copy_in : cpio -i pass : cpio -p # # # # -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. 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. -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. -rw: Copy mode. When both -r and -w are specified, pax copies the specified files to the destination directory. 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. ./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. 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. Note 5: Performing a mksysb migration with CD installation ----------------------------------------------------------[email protected] ] On Behalf Of Robert Miller Sent: Wednesday, April 07, 2004 6:13 PM To: [email protected] Subject: Re: 64 Bit Kernel It may be one of those odd IBMisms where they want to call something a certain name so they put it in as a link to the actual critter... Looking on my box, the /dev/ipldevice has the same device major and minor numbers as hdisk0 - tho it is interesting that ipldevice is a character device, where a drive is usually a block device: mybox:rmiller$ ls crw------- 2 root mybox:rmiller$ ls brw------- 1 root - 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. $ tapeutil -f /dev/smc0 move -s 10 -d 23 For example: -b DDS1 -n -a make_boot_tape -d /dev/ -v 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. # instl_adm -d > tmp_config_file ## edit tmp_config_file as appropriate # make_boot_tape -f tmp_config_file -t /tmp Create a boot tape and specify a different gateway IP address. Set from > | | 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 | # 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 11. grep command: ================= # grep Sally people # grep "Sally Smith" peoplenew or use _ as a delimter sed 's_/usr/local/bin_/common/bin_' new Example:] [-dir=] [schema=]" ) truss -p $ lsnrctl dbsnmp_start NOTE: The "truss" command works on SUN and Sequent. Use "tusc" on HPUX, "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 truss truss -a -e -f Specify a program to run # truss -rall -wall lsnrctl start # truss -aef lsnrctl dbsnmp_start 20.2 syscalls command on AIX: ----------------------------1. syscalls Command Purpose Provides system call tracing and counting for specific processes and the system. Syntax To Create or Destroy Buffer: syscalls [ [ -enable bytes ]| -disable 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: 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. $ 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" .. .. 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. ------------------------------------------------------------------------ERRPT entry: ============ 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 : > > > > > > > > > > > > > > >
. You should see the following warning: 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 . Example 2: ---------A secure shell 'terminal': # ssh -l oracle 193.172.126.193 # ssh [email protected] pscp: ===== Example to Copy a file to a remote unix server: # pscp c:\documents\foo.txt [email protected] :/tmp/foo To receive (a) file(s) from a remote server: pscp [options] [user@]host:source target So to copy the file /etc/hosts from the server example.com as user fred to the file c:\temp\example-hosts.txt, you would type: pscp [email protected] :/etc/hosts c:\temp\example-hosts.txt To send (a) file(s) to a remote server: pscp [options] source [source...] [user@]host:target[email protected] :/tmp/foo You can use wildcards to transfer multiple files in either direction, like this: pscp c:\documents\*.doc [email protected] :docfiles pscp [email protected] :source/*.c c:\source Example of scripts using pscp with parameters; -----------------------------------@echo off REM Script om via pscp.exe een bestand van een UNIX systeem te copi %ren naar het werkstation. Echo Copy bestand van unix naar werkstation SET SET SET SET[email protected] :/backups/520backups/splenvs # scp conv2.tar.gz [email protected] :/backups/520backups/splenvs Example: # scp myfile xyz@sdcc7:myfile Example: To copy a directory, use the -r (recursive) option. # scp -r mydir xyz@sdcc7:mydir Example: cd /oradata/arc /usr/local/bin/scp *.arc: # zfs create tank/home # zfs set mountpoint=/export/home tank/home /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: bash-3.00# vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS c1t0d0s2 c1t1d0s2 c1t2d0s2 c1t3d0s2 =c1t10d0 adddisk =c2t0d0 replace addisk with rmdisk to remove a disk 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 View configuration: vxprint -th List disks: vxdisk list vxdisk -o alldgs list (shows deported disks) 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) To encapsulate use: vxencap -g Export a disk group: vxdg deport vxdg -h deport to export to another host 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 Destroy a disk group: vxdg destroy Evacuate data from a disk: vxevac -g Create a volume on a diskgroup: vxassist -g make layou=stripe ncols=number of colums stripeunit=size Create a veritas filesystem on this volume: mkfs -F vxfs /dev/vx/rdsk// Delete a volume same as creatiuon but replace make with remove Resize a filesystem: vxresize -g -F -s Typical example: mkvg -y oravg -s 64 hdisk3 hdisk4 mkvg -y appsvg -s 32 hdisk2 mkvg -y datavg -s 64 hdisk3 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, -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. # mkvg -y myvg -d 10 -s 8 hdisk1 hdisk5 # mkvg -y oravg -d 10 -s 64 hdisk1 (like for example "/data") will create the entry in /etc/filesystems for you Some more examples: ------------------Commands to create VG's: mkvg oravg -d 10 -s 128 hdisk2 hdisk4 mkvg splvg -d 10 -s 128 hdisk3 hdisk5 mkvg softwvg -d 10 -s 128 hdisk6 mkvg backupvg -d 10 -s 128 hdisk7 Set of Create Logical Volume and Filesystem commands: # crfs -v jfs -g -m -a size=xG -a bf=true or # mklv -y -c 2 No_Of_PPs # crfs -v jfs -d -m -a bf=true # # # # on 02/19/2003 01:51:24 PM Please respond to IBM AIX Discussion List To: [email protected] cc: (bcc: Patrick Bigelbach/DSS) Subject Re: Cannot cfgmgr on a new FC Put in your OS cd in the cdrom drive and run: cfgmgr -vi /dev/cd0 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:[email protected] ] On Behalf Of Calderon, Linda Sent: Wednesday, February 19, 2003 10:12 AM To: [email protected] 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.[email protected] (Ed) wrote in message news:... > I deleted a scsi device from my 4.3.3 configuration with the following > command: > rmdev -l scsi2 -dR[email protected] and describe the discrepancy. C. FIX AND INTERIM FIX INSTALLATION IMPORTANT: If possible, it is recommended that a mksysb backup of the system be created. Verify it is both bootable and readable before proceeding.[email protected] To request the PGP public key that can be used to communicate securely with the AIX Security Team you can either: A. Send an email with "get key" in the subject line to: [email protected] B. Download the key from a PGP Public Key Server. The key ID is: 0xA6A36CCC Please contact your local IBM AIX support center for any assistance. eServer is a trademark of International Business Machines Corporation. IBM, AIX and pSeries are registered trademarks of International Business Machines Corporation. All other trademarks[email protected] Q: Subject Re: error concerning filesystem [Virus checked] Hi Holger, A small query...how did you arrive at this figure of 43 from the error code. The decimal value of B is 11 but I could not understand the 2*16.. can you please exp this.... A: The major/minor numbers (002B 000B) are in hex: hex abcd = a*16^3+b*16^2+c*16^1+d therefore hex 002B=0*16^3+0*16^2+2*16^1+11=2*16+11 Note 3: AIX superblock issues: ------------------------------- Hint 1 for AIX: -- --------------thread: Use this command in case the superblock is corrupted. This will restore the BACKUP COPY of the superblock to the CURRENT copy. # dd count=1 bs=4k skip=31 seek=1 if=/dev/hd4 of=/dev/hd4 # fsck /dev/hd4 2>&1 | tee /tmp/fsck.errors Note: fuser Identifies processes using a file or file system # fuser -u /dev/hd3 Sample output: /dev/hd3: 2964(root) 6615c(root) 8465(casado) 11290(bonner) -- Hint 2 for AIX: -- ---------------[email protected] ) ********************************************************************** ******/ #include #include #include #include #include #include #include #include #define FOUR_MB #define THIRTY_TWO_KB extern extern extern extern\n"); exit(1); } main(int argc,char **argv) { FILE struct superblock short long struct dinode ulong ulong ulong ulong ulong int int int 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. # vgdisplay lvm-raid . . Free PE / Size[email protected] , http://www.surriel.com/ Abstract While the virtual memory management in Linux 2.2 has decent performance for many workloads, it suffers from a number of problems. The first part of this paper contains a description of how the Linux 2.2 VMM works and an analysis of why it has bad behaviour in some situations. The way in which a lot of this behaviour has been fixed in the Linux 2.4 kernel is described in the second part of the paper. Due to Linux 2.4 being in a code freeze period while these improvements were implemented, only known-good solutions have been integrated. A lot of the ideas used are derived from principles used in other operating systems, mostly because we have certainty that they work and a good understanding of why, making them suitable for integration into the Linux codebase during a code freeze. --Linux 2.2 memory management The memory management in the Linux 2.2 kernel seems to be focussed on simplicity and low overhead. While this works pretty well in practice for most systems, it has some weak points left and simply falls apart under some scenarios. Memory in Linux is unified, that is all the physical memory is on the same free list and can be allocated to any of the following memory pools on demand. Most of these pools can grow and shrink on demand. Typically most of a system's memory will be allocated to the data pages of processes and the page and buffer caches. The slab cache: this is the kernel's dynamically allocated heap storage. This memory is unswappable, but once all objects within one (usually page-sized) area are unused, that area can be reclaimed. The page cache: this cache is used to cache file data for both mmap() and read() and is indexed by (inode, index) pairs. oranh300:/home/se1223>cat /etc/inittab | grep enab vxen::bootwait:/sbin/fs/vxfs/vxenablef -a Note 4: ------Extend OnlineJFS licenses on next D&ST servers: aavnh400 oranh503 oranh603 orazh500 orazh601 orazh602 commands are: swagentd -r swinstall -x mount_all_filesystems=false -x enforce_dependencies=true -s hpdepot.ao.nl.abnamro.com:/beheer/depot/OnlineJFS_License OnlineJFS swagentd -k --> 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 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 being exported. NFS Server /etc/rc.config.d/nfsconf was successful. # pkgchk -v SUNWpl5u /usr /usr/bin /usr/bin/perl /usr/perl5 /usr/perl5/5.00503 Example 2: # pkgadd -d /cdrom/cdrom0/s0/Solaris_2.6 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: Example 4: # pkgadd -d http://install/signed-video.pkg ## Downloading... ..............25%..............50%..............75%..............100% ## Download Complete Example 5: # pkgadd -d . DISsci The command will create a new directory structure in /opt/DISsci Example 6: was successful. Verifying package dependencies. Processing package information. Removing pathnames in class Some Graphical tools for installing packages: -------------------------------------------->>> admintool (Solaris 8,9 Not in Solaris 10) >>> Solaris Product Registry The Solaris Product Registry is a GUI tool that enables you to install and uninstall software packages. To startup the Solaris Product Registry to view, install or uninstall software, use the command /usr/bin/prodreg >>> Solaris Management Console (smc) Patch Manager The Solaris Management Console provides a new Patches Tool for managing patches. You can only use the Patches Tool to add patches to a system running the Solaris 9 or later release. PATCHLIST shows all patches applied to the package identified by 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 The /var/sadm/install/contents file: -----------------------------------The /var/sadm/install/contents file is the file which Solaris uses to keep track of all the files installed on a system, and their corresponding packages. Every file installed on a Solaris OS using the pkgadd command has an entry in the database of installed files /var/sadm/install/contents. The contents is a textfile that contains one line per installed file. -d , for example # instfix -k IX75893 -d /dev/cd0 # instfix -k IX75893 -d . # instfix -k IY63533 -d . - To list fixes that are on a CD-ROM in /dev/cd0, enter # instfix -T -d /dev/cd0 IX75893 - To determine if for example APAR IX75893 is installed on the system, enter" from the key rings located in /etc/rpm/.gpg using the executable /usr/bin/gpg you would include %_signature gpg %_gpg_path /etc/rpm/.gpg %_gpg_name John Doe %_gpgbin /usr/bin/gpg 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. 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. 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." exit 1 fi if [ ! -f /etc/sysconfig/static-routes ]; then exit 0 fi #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 /etc/sysconfig/network-scripts/ifup-aliases Bring up aliases for a device./sysconfig.txt file contains a more authoritative listing of the files found in the /etc/sysconfig directory and the configuration options available. 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, 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., where is one of the following: yes - LDAP is used for authentication. no - LDAP is not used for authentication. /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. 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). /etc/sysconfig/desktop The /etc/sysconfig/desktop file specifies the desktop manager to be run, such as: DESKTOP="GNOME" /etc/sysconfig/dhcpd, 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., 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. /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. 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. /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. 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. 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., 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. /etc/sysconfig/keyboard The /etc/sysconfig/keyboard file controls the behavior of the keyboard. The following values may be used: 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. 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. /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:, 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., 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. In addition, /dev/mouse is a symbolic link that points to the actual mouse device. /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)", 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. /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. /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. 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. /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/ntpd.htm (where is the version number of ntpd). By default, this file sets the owner of the ntpd process to the user ntp. /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. /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. /etc/sysconfig/rawdevices The /etc/sysconfig/rawdevices file is used to configure raw device bindings, such as: /dev/raw/raw1 /dev/sda1 /dev/raw/raw2 8 5, 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. 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. /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. /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/ 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. /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. /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. 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. /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:, 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. 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. /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. Directories in the /etc/sysconfig/ Directory The following directories are normally found in /etc/sysconfig/ and a basic description of what they contain: 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. 
