Q1. Why do I get the message "ultralite: not found"?
A1. Your PATH variable does not contain the /usr/local/bin directory, or the symbolic link in /usr/bin/ultralite is not there. The cause of the message "ulite: not found" is the same.
Q2. Why do I get the message "/usr/local/bin/ultralite: 2525 Memory fault - core dumped"?
A2. This error is typically caused by a bug in sar which is triggered when you ask the ultralite script to analyze sar data, but you provide the name of a sar report. Note that the number which appears in the error message will vary
Q3. Why do I get the message "WARNING: Bad sar -b data has been detected"? (5.0.0 and 5.0.2 only)
A3. This is usually caused by a bug in the OpenServer Release 5 implementation of sar, and is present in releases 5.0.0 and 5.0.2. Check the sar -b statistics for negative numbers. Their presence is an indication of the sar bug.
Q6. Why do I get the message "lc: sa[0-3][0-9] not found: No such file or directory (error 2)"?
A6. This message indicates that there are no sar data files for ultralite to analyze. The most common cause of this message is that on OpenServer Release 5 systems, sar has not been enabled. To enable sar, see the man page for the sar_enable command. On older systems, this means that there's a problem with the way sar is set up, or maybe the kernel was built at least 7 days ago and the system has not been rebooted.
Q7. Why does SarCheck UltraLite tell me that my fast new disks are slow?
A7. The speed of disks (as reported by the manufacturer) is usually better than the speed as reported by sar. Soft I/O errors, poor locality of reference, and problems with the disk controllers are frequently responsible. Unfortunately, sar doesn't give us enough information to identify the true cause or recommend a solution.
Q10. Is SarCheck UltraLite Year 2000 compliant?
A10. We believe SarCheck UltraLite is fully Y2K compliant. UltraLite does not care about the date and should run correctly on systems with Year 2000 dates as long as the operating system is Y2K compliant. We have heard reports that a Y2K patch for 5.0.2 will cause incorrect sar -n data to be reported. We don't have any more information about this, but sar should be working correctly if SarCheck UltraLite is to be produce accurate output. The sar utility is distributed by SCO and we are not responsible for it.
Q11. Why did SarCheck UltraLite stop producing reports?
A11. Usually this means that the kernel was rebuilt, but the system was not rebooted. After the kernel is rebuilt, sar may have trouble until the system is rebooted. SarCheck UltraLite can't produce reports if sar isn't working.
Q12. How do I install UltraLite?
A12. UltraLite, as distributed with Skunkware 98, can be installed using custom.
A compressed tar archive of UltraLite is available here. Put it on your system and install it with the following command:
zcat < ulite.taz | tar xvf -
Don't forget to run sar_enable in order to enable sar.
Q13. How do I get support for UltraLite?
A13. UltraLite is freeware and support is limited. It was created in 2000. Our OSR5 system has been shut down and most of us don't remember much about it. If you still have any questions, please send email to support@sarcheck.com.
Back to the SarCheck home page