MAI COMPANY CONFIDENTIAL FIELD INFORMATION BULLETIN SERVICE GROUP(S): MICRO,MINI,LARGE MFG: SUN MICROSYSTEMS NACS TYPE(S): N124 MFG. MODEL(S): SOLARIS CATEGORY: SOFTWARE DESC: OPERATING SYSTEM *** TABLE OF CONTENTS AS OF 11/10/95 *** FIB 00001.System tuning for OpenBASIC on Solaris 2.x..................05/28/93 FIB 00002.Installation information for OpenBASIC......................06/10/93 FIB 00003.Error within 'dedicate_p'...................................07/16/93 FIB 00004.Solaris 2.x Non-root user cannot 'dedicate_p' or 'free_p'...07/16/93 FIB 00005.Solaris 2.x "root" login on terminals other than console....07/22/93 FIB 00006.Recommended Operating System Patches for Solaris 2(Text Inco07/28/93 FIB 00007.Recommended backup for Solaris - ufsdump & ufsrestore info..10/05/94 FIB 00008.Instructions for submitting a dump for analysis.............12/13/94 FIB 00009.OpenBASIC not certified to run on Solaris 2.4...............08/24/95 FIB 00010.files.to check when /var fills up...........................08/26/95 FIB 00011.errno script for getting description of system errors.......10/26/95 FIB 00012.lpsched dies when print job submitted.......................11/09/95 SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------Table Of Contents Pg01 of 01 FIB 00001 MAI COMPANY CONFIDENTIAL 05/28/93 *** System tuning for OpenBASIC on Solaris 2.x *** Subject : System Tuning for OpenBASIC on SUN Solaris 2.x system Type : Informational Purpose : Inform the field of what parameters need to be changed when installing OpenBASIC on a SUN Solaris 2.x system. A basic error 62 indicates that a kernel parameter was exceeded. In order to find out which kernel parameter needs to be increased you will need to find the system error number, you find this by typing ERROR (after getting the ERROR 62) Using the system error number you can find out what parameter needs to be increased by doing the following : grep system error /usr/include/sys/errno.h For example a basic error 62 with a system error of 46 will display : "#define ENOLCK 46 /* No record locks available */" . This indicates that the kernel parameter called :tune_t_flckrec needs to be changed. In order to avoid errors 62 (kernel parameters exceeded) while using OpenBASIC some kernel parameters must be modified. The following kernel parameters are the recommended values for OpenBASIC and it's based on the amount of memory (MB) on the system. Kernel Parameters (32 MB) (64 MB) (96 MB) (128 MB) (256 MB) max_nprocs 468 788 1172 1300 2580 ufs_ninode 2708 4388 6404 7076 13796 maxuprc 468 788 1172 1300 2580 ncsize 1354 2194 3202 3538 6898 tune_t_flckrec 1024 2000 1878 2400 3990 ndquot 1364 2324 3476 3860 7700 These kernel parameters must be added in the /etc/system file. Example : As root vi /etc/system and enter the following for a system with 128 mbyt of memory : set max_nprocs=1300 set ufs_ninode=7076 set maxuprc=1300 set ncsize=3538 set tune_t_flckrec=2400 set ndquot=3860 Save the file. After rebooting, the new kernel parameters will be in effect. If you continue to receive an error 62 find the kernel parameter (see above) that needs to be increased. You can also use "sar" to find which kernel parameters needs to be increased or decreased. These kernel parameters are based on the following formula : If MB less then 64, x=35; If MB less then 128, x=30; If MB greater then 128, x=25. users=MB* x /10 NPROC= 20 + users * 4 NINODE= 256 + users + NPROC * 5 MAXUP= NPROC NCSIZE= NINODE / 2 NFILCK= users * 6 + 150 NQUOTA= users * 8 +NPROC For example to calculate max_nprocs (NPROC) for a system with 96 MB : x=30, users=288 (96*30/10), NPROC=1172 (288*4+20). In the /etc/system file SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB001 Pg001 you will set max_nprocs=1172. We are in the process of releasing a MAI Supplement diskette that will contain a script called "maitune" that will add the above kernel entries in the /etc/system file automatically. You also might get another kernel error (Basic error 62, system error 24). This indicates that the number of files opened has been exceeded. To correct this you should add in the user .profile the following entry : ulimit -n 100. 100 indicates the number of files the user can open. ORIGINATOR: Joe Melendez SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB001 Pg002 FIB 00002 MAI COMPANY CONFIDENTIAL 06/10/93 *** Installation information for OpenBASIC *** Author : Wally Moore Subject : Installing OpenBASIC on SUN Solaris 2.2 system Type : Informational Purpose : Inform the field of the steps to install OpenBASIC on a SUN Solaris 2.2 system. To install OpenBASIC on a SUN Solaris 2.2 system follow the steps outlined in the OpenBASIC Administration Manual M0239B. Use the steps on page 2-3 - 2-4 Installation from Diskette (Do not follow the Sun Sparcstation steps). Special notes: Before using cpio you must kill the volume daemon. Use the device /dev/rdiskette for the input device. # ps -ef |grep vold root 926 115 9 11:00:00 ? 0:01 /usr/sbin/vold # kill -9 926 # mkdir /tmp/install # cd /tmp/install # cpio -iuvd < /dev/rdiskette The information in the manual for the Sun Sparcstation is for Solaris 1.1 and older. NOTE: The floppy will not automatically eject at the completion of each floppy. The best work around for this is to open 2 OPENWIN windows, do the cpio in one window, and eject the floppy in the second. The other way to eject the floppy is a paper clip in the little hole below the floppy opening. (Try to avoid doing this in front of a customer.) ORIGINATOR: Wally Moore SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB002 Pg001 FIB 00003 MAI COMPANY CONFIDENTIAL 07/16/93 *** Error within 'dedicate_p' *** Subject : OpenBASIC 4.0*19.07 "/usr/ob/bin/dedicate_p" error on SUN Solaris 2.x Type : Problem Purpose : Inform the field of an OpenBASIC 4.0*19.07 "/usr/ob/bin/dedicate_p" error on SUN Solaris 2.x systems. Symptom : Executing OpenBASIC "/usr/ob/bin/dedicate_p" command will produce . the following error message : "Syntax error at line 67 : `fi' unexpected". Solution: As root "vi" the /usr/ob/bin/dedicate_p script. Modify line 65 (to find line number 65 perform a "set nu" vi command). Change if to fi. Save the script. NOTE.: This only fails on SUN Solaris 2.x on OpenBASIC 4.0. It does not fail on HP systems with OpenBASIC 4.0. This will be corrected in a future release of OpenBASIC for SUN Solaris 2.x. ORIGINATOR: Joe Melendez SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB003 Pg001 FIB 00004 MAI COMPANY CONFIDENTIAL 07/16/93 *** Solaris 2.x Non-root user cannot 'dedicate_p' or 'free_p' *** Problem: Solaris 2.x will not allow a non-root user to dedicate or free a printer because of the permissions on the /usr/bin/disable and /usr/bin/enable commands. Fix: To allow non-root users to dedicate and free printers, do the following: login as root cd /usr/bin . chmod 4555 disable chmod 4555 enable ls -l disable will display -r-s-r-xr-x 1 lp lp 41792 Jul 18 12:00 disable dedicate_p and free_p will now function for non-root users. ORIGINATOR: Dan Arteritano SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB004 Pg001 FIB 00005 MAI COMPANY CONFIDENTIAL 07/22/93 *** Solaris 2.x "root" login on terminals other than console *** Problem: The "root" login can only be used on console. FIX: To allow "root" to be used as a login on terminals besides console make the following change: login as root or do an "su" to become superuser cd /etc/default vi login change the CONSOLE line as follows: Old: CONSOLE=/dev/console New: #CONSOLE=/dev/console commenting out the CONSOLE line allows any terminal use the root login. ORIGINATOR: Dan Arteritano SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB005 Pg001 FIB 00007 MAI COMPANY CONFIDENTIAL 10/05/94 *** Recommended backup for Solaris - ufsdump & ufsrestore info *** Since tar can't backup device files and cpio can't backup the proc directory and empty directories, ufsdump is the recommended backup for Solaris customers. This backup utility maps the directories, then the files, then does a bit image copy of the directories, then a bit image copy of the files. This makes it very easy and fast to restore individual files from the backup. This is a filesystem backup and works best using a script file to enter in a ufsdump command for each mounted partition and then have it run from cron so it's results report to root's mail. Ufsdumps other benefit is that besides getting all info from the disk, including configuration setups, it is also much faster than tar or cpio as it's doing bit image copying but still has the advantage of single file restore. UFSDUMP INFO AND EXAMPLES ################################################### ***NOTE: BE SURE TO SUBSTITUTE THE CORRECT VALUES FOR YOUR FILESYSTEM AND DISK DEVICE*** Below is a sample of a script file called /backup that backs up a two disk system. Disk 0 has four partitions and Disk 1 has one partition. ############################################################################### ### ufsdump backup - level 0 - backs up both disks #################### ############################################################################### ufsdump 0uf /dev/rmt/0n / # / root on disk0 ufsdump 0uf /dev/rmt/0n /var # /var on disk0 ufsdump 0uf /dev/rmt/0n /opt # /opt on disk0 ufsdump 0uf /dev/rmt/0n /usr # /usr on disk0 ufsdump 0uf /dev/rmt/0 /usr2 # /usr2 on disk1 ############################################################################### The 0 indicates a level 0 dump meaning the entire filesystem regardless of date/time of last backup. The u indicates that if the dump completes successfully to write the date and time into the /etc/dumpdates file. The f indicates that you are going to specify the device to dump to. /dev/rmt/0n is the device of the tape unit with no rewind so after it dumps that filesystem it leaves the tape at that position for the next dump. Next is the filesystem to dump. You can either give the mount point or the partition device file name such as /dev/rdsk/c0t3d0s0 instead of / for root. On the last filesystem, use the rewind tape driver so it rewinds the tape once it's completed. ############################################################################### UFSRESTORE IN INTERACTIVE MODE IS USED TO RESTORE INDIVIDUAL FILES First determine what filesystem the file you want to restore is in. Look at the script file containing the backup procedure and, for example, we'll say you want to restore two files in the /opt partition which is the third filesystem on your tape. Put the tape in the drive and use the following commands to first rewind the tape and then move the tape to the third filesystem on tape. #mt -f /dev/rmt/0 rewind #mt -f /dev/rmt/0n fsf 2 THIS JUMPS TWO FILESYSTEMS TO THE 3RD NOW WE GO INTO INTERACTIVE MODE OF UFSRESTORE TO FIND AND EXTRACT FILES. #cd /mydirectory WHERE YOU WANT TO RESTORE FILES TO. SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB007 Pg001 #ufsrestore ivf /dev/rmt/0 GET INTO INTERACTIVE MODE. ufsrestore> ls LIST WHAT'S ON TAPE. lost+found/ mydirectory/ HERE'S WHAT IT FOUND. ufsrestore> cd mydirectory cd TO NEEDED DIRECTORY. ufsrestore> ls LIST NEEDED DIRECTORY. file1 file2 file3 ... HERE'S WHAT IT FOUND. ufsrestore> add file1 file2 ADD NEEDED FILES TO LIST. ufsrestore> extract COPIES FILES TO DISK IN YOUR DIR. You have not read any volumes yet. Unless you know which volume your files are on you should start with the last volume. Specify next volume#: 1 ALWAYS ANSWER 1 HERE. set owner/mode for '.'?[yn] n ALWAYS ANSWER n HERE. ufsrestore> quit TO EXIT. ############################################################################### UFSRESTORE TO RESTORE A FILESYSTEM OTHER THAN ROOT OR USR FOR OUR EXAMPLE, WE'LL RESTORE /usr2 TO THE SECOND DISK WHICH IS SCSI ADDRESS OF 1. #umount /dev/rdsk/c0t1d0s0 UNMOUNTS BLOWN PARTITION. #newfs /dev/rdsk/c0t1d0s0 CREATES NEW FS ON BLOWN PARTITION. #fsck /dev/rdsk/c0t1d0s0 CHECKS IT OUT. #mount /dev/dsk/c0t1d0s0 /mnt MOUNTS IT TO /mnt. #cd /mnt #mt -f /dev/rmt/0 rewind REWINDS TAPE. #mt -f /dev/rmt/0n fsf 4 IF IT'S THE 5TH FS ON TAPE AS ABOVE. #ufsrestore rvf /dev/rmt/0 RESTORES IT. #rm restoresymtable #cd / NOTE: The next step is required if restoring the root filesystem to make it bootable. The boot disk device name may be different from the one shown, could be /dev/rdsk/c0t3d0s0. #/usr/sbin/installboot /lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0 #umount /mnt UNMOUNTS IT. #fsck /dev/rdsk/c0t1d0s0 CHECKS IT OUT. #mount /dev/dsk/c0t1d0s0 REMOUNTS IT TO IT'S DEFAULT LOCATION. ############################################################################### UFSRESTORE TO RESTORE ROOT OR USR FILESYSTEM For example, I'll show how to restore the root filesystem, but /usr would be identical, just with different partitions and mount points. Our boot disk is SCSI address 3. Put the Solaris OS CD in the caddy and in the drive. From the ok prompt after a shutdown, do the following: ok boot cdrom -sw BOOTS FROM CD & PUTS YOU AT A # PROMPT #newfs /dev/rdsk/c0t3d0s0 CREATES FS ON BLOWN PARTITION. #fsck /dev/rdsk/c0t3d0s0 DOES FSCK. #mount /dev/dsk/c0t3d0s0 /mnt MOUNTS IT TO /mnt. #cd /mnt #mt -f /dev/rmt/0 rewind TO INSURE YOUR AT BEGINNING OF TAPE. IF YOUR RESTORING ROOT SKIP NEXT COMMAND, IT'S ONLY FOR /usr. #mt -f /dev/rmt/0n fsf 3 TO GET TO /usr IF THATS WHAT YOU WANT. #ufsrestore rvf /dev/rmt/0 RESTORES IT. #rm restoresymtable #cd / #umount /mnt SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB007 Pg002 #fsck /dev/rdsk/c0t3d0s0 CHECKS IT OUT AGAIN. #shutdown -y -g0 -i6 REBOOTS FROM DISK. ############################################################################## ORIGINATOR: Jim Dobson SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB007 Pg003 FIB 00008 MAI COMPANY CONFIDENTIAL 12/13/94 *** Instructions for submitting a dump for analysis *** SUBJECT: INFORMATION REQUIRED WITH SUN SYSTEM CRASH FILE TYPE: INFORMATION PROCEDURE: THE FOLLOWING INFORMATION IS REQUIRED WHEN SENDING IN A SYSTEM CRASH FILE FROM A SUN SYSTEM CRASH: DUMP core file prtconf -pv showrev -p /usr/adm/messages file /etc/system file /kernel/unix file Redirect the prtconf and showrev outputs to a file so that they. can be backed using tar and sent in. ORIGINATOR: Wally Moore SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB008 Pg001 FIB 00009 MAI COMPANY CONFIDENTIAL 08/24/95 *** OpenBASIC not certified to run on Solaris 2.4 *** Our engineering group has not certified OpenBASIC to run on Solaris 2.4. ORIGINATOR: Joe Melendez SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB009 Pg001 FIB 00010 MAI COMPANY CONFIDENTIAL 08/26/95 *** files to check when /var fills up *** Subject: var directory full on Sun / Solaris 2.3 If the /var filesystem becomes full check to see if the 2 following files exist: /var/adm/wtmp or wtmpx If they exist and are large files, you can clear the files by doing the following procedure. NOTE:.You must reboot the system after you do this, also, you can't delete these files, you must do the following: #cat /dev/null >/var/adm/wtmp or wtmpx now you can reboot the system. ORIGINATOR: Fred Chiuppi SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB010 Pg001 FIB 00011 MAI COMPANY CONFIDENTIAL 10/26/95 *** errno script for getting description of system errors *** Subject: errno on non-BOSS/VX system Below is a script that will give the same ouput as the BOSS/VX command errno. The example below works on SCO, HP and Solaris. It does NOT work on AIX. Do the following: vi /usr/bin/errno Press to insert Enter: <:> grep "$1" /usr/include/sys/errno.h Press: Press: ZZ Enter: chmod +x /usr/bin/errno Enter: errno 5 Should display the following: #define EIO 5 /* I/O error */ ORIGINATOR: Dan Arteritano SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB011 Pg001 FIB 00012 MAI COMPANY CONFIDENTIAL 11/09/95 *** lpsched dies when print job submitted *** OS: Solaris Problem: After a print job is submitted the lpsched dies. It starts up with no problem. Resolution: Remove the directories: temp and requests from the directory /var/spool/lp. These directories will be recreated when a job is submitted. ORIGINATOR: NSC SOFTWARE-SUN MICROSYSTEMS-SOLARIS-------------------FIB012 Pg001