Newsgroups: comp.os.linux.setup Date: Thu, 23 Oct 2003 17:37:31 -0400
Newsgroups: comp.os.linux.setup Date: Thu, 23 Oct 2003 17:37:31 -0400
I'm wondering how to preserve the last part of boot-up messages in RH8.
Back to RH6.2, all boot-up messages are preserved on console on boot. I can scroll several pages back to refer to them. But since RH7, RedHat started to clear screen before showing the login prompt. This has created a great headache to me. All my customized settings are near to bottom of the boot-up messages, and many times, I can see there were errors, but the helpful error messages are cleared away right afterward by "friendly" RedHat.
Most of those error messages are not in dmesg. How can I preserve them?
> I'm wondering how to preserve the last part of boot-up messages in RH8.
/var/log/boot.log ?
Eric Moors
FSlint is a toolkit to find various forms of lint on a filesystem, such as: duplicate files, dangling links, malformed links, troublesome filenames, duplicate binaries, non stripped binaries, …
Home Page : http://www.iol.ie/~padraiga/fslint
a doc app for WindowMaker that utilizes lm_sensors to monitor CPU temp, sys temp, fan speeds, and CPU voltage. It offers configurable warnings for overheating, and the sensors displayed are adjustable by the user with command line parameters
monitors the installation of programs (or anything else), and detects the files that were added to the filesystem hierarchy or modified. Therefore, it allows administrators to keep track of everything they install inside their system's directory structure, even when they perform an installation without using the native package manager
a Web app which displays useful information about your PC, such as number of installed CPUs, hostname, installed PCI devices, network devices, Apache configuration, memory usage
designed to help webmasters monitor the time it takes to download URLs from various spots on the Web
tripwire - a file integrity checker for UNIX systems
It creates a baseline database in the location specified by the DBFILE variable in the Tripwire configuration file. The database is essentially a snapshot of the objects residing on the system. During later Tripwire integrity checks, this database serves as the basis for comparison.
When run in Database Initialization mode, tripwire reads the policy file, generates a database based on its contents, and then cryptographically signs the resulting database.
After building the Tripwire database, the next step is typically to run tripwire in Integrity Checking mode. This mode scans the system for violations, as specified in the policy file. Using the policy file rules, Tripwire will compare the state of the current file system against the initial baseline database. An integrity checking report is printed to stdout and is saved in the location specified by the REPORTFILE setting in the Tripwire configuration file.
The generated report describes each policy file violation in detail, depending on whether the specified file system object was added, deleted, or changed.
Running tripwire in Database Update mode allows any differences between the database and the current system to be reconciled. This will prevent the violation from showing up in future reports.
From root Tue Mar 26 01:15:27 2002 To: root@localhost.localdomain Subject: Anacron job 'cron.daily'
/etc/cron.daily/tripwire-check:
**** Error: Tripwire database for localhost.localdomain not found. **** **** Run /etc/tripwire/twinstall.sh and/or tripwire --init. ****
Do as told, giving blanks to all passphrase it requires.
% tripwire --init
[...] Wrote database file: /var/lib/tripwire/localhost.localdomain.twd The database was successfully generated.