Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

wbemlogviewer(1m) [redhat man page]

wbemlogviewer(1M)														 wbemlogviewer(1M)

NAME
wbemlogviewer - start WBEM Log Viewer SYNOPSIS
/usr/sadm/bin/wbemlogviewer The wbemlogviewer utility starts the WBEM Log Viewer graphical user interface, which enables administrators to view and maintain log records created by WBEM clients and providers. The WBEM Log Viewer displays a Login dialog box. You must log in as root or a user with write access to the rootcimv2 namespace to view and maintain log files. Namespaces are described in wbemadmin(1M). Log events can have three severity levels. o Errors o Warnings o Informational The WBEM log file is created in the /var/sadm/wbem/log directory, with the name wbem_log. The first time the log file is backed up, it is renamed wbem_log.1, and a new wbem_log file is created. Each succeeding time the wbem_log file is backed up, the file extension number of each backup log file is increased by 1, and the oldest backup log file is removed if the limit, which in turn is specified in the log ser- vice settings, on the number of logfiles is exceeded. Older backup files have higher file extension numbers than more recent backup files. The log file is renamed with a .1 file extension and saved when one of the following two conditions occur: o The current file reaches the specified file size limit. o A WBEM client application uses the clearLog() method in the Solaris_LogService class to clear the current log file. o A WBEM client application uses the clearLog() method in the Solaris_LogService class to clear the current log file. o A user chooses Action->Back Up Now in the Log Viewer application. Help is displayed in the left panel of each dialog box. Context help is not displayed in the main Log Viewer window. The WBEM Log Viewer is not the tool for a distributed environment. It is used for local administration. The WBEM Log Viewer allows you to perform the following tasks: View the logs Set properties of log fiClick Action->Log File Settings to specify log file parameters and the log file directory. Back up a log file Click Action->Back Up Now to back up and close the current log file and start a new log file. Open historical log fileClick Action->Open Log File to open a backed-up log file. Delete an old log file Open the file and then click Action->Delete Log File. You can only delete backed-up log files. View log record details Double-click a log entry or click View->Log Entry Details to display the details of a log record. Sort the logs Click View->Sort By to sort displayed entries. You can also click any column heading to sort the list. By default, the log entries are displayed in reverse chronological order (new logs first). EXIT STATUS
The wbemlogviewer utility terminates with exit status 0. /var/sadm/wbem/log/wbem_log WBEM log file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWwbcor | +-----------------------------+-----------------------------+ wbemadmin(1M), init.wbem(1M), mofcomp(1M), attributes(5) 3 Jan 2000 wbemlogviewer(1M)

Check Out this Related Man Page

Log::Any::Test(3pm)					User Contributed Perl Documentation				       Log::Any::Test(3pm)

NAME
Log::Any::Test -- Test what you're logging with Log::Any SYNOPSIS
use Test::More; use Log::Any::Test; # should appear before 'use Log::Any'! use Log::Any qw($log); # ... # call something that logs using Log::Any # ... # now test to make sure you logged the right things $log->contains_ok(qr/good log message/, "good message was logged"); $log->does_not_contain_ok(qr/unexpected log message/, "unexpected message was not logged"); $log->empty_ok("no more logs"); # or my $msgs = $log->msgs; cmp_deeply($msgs, [{message => 'msg1', level => 'debug'}, ...]); DESCRIPTION
"Log::Any::Test" is a simple module that allows you to test what has been logged with Log::Any. Most of its API and implementation have been taken from Log::Any::Dispatch. Using "Log::Any::Test" sends all subsequent Log::Any log messages to a single global in-memory buffer. It should be used before Log::Any. METHODS
The test_name is optional in the *_ok methods; a reasonable default will be provided. msgs () Returns the current contents of the global log buffer as an array reference, where each element is a hash containing a category, level, and message key. e.g. { category => 'Foo', level => 'error', message => 'this is an error' }, { category => 'Bar::Baz', level => 'debug', message => 'this is a debug' } contains_ok ($regex[, $test_name]) Tests that a message in the log buffer matches $regex. On success, the message is removed from the log buffer (but any other matches are left untouched). does_not_contain_ok ($regex[, $test_name]) Tests that no message in the log buffer matches $regex. empty_ok ([$test_name]) Tests that there is no log buffer left. On failure, the log buffer is cleared to limit further cascading failures. contains_only_ok ($regex[, $test_name]) Tests that there is a single message in the log buffer and it matches $regex. On success, the message is removed. clear () Clears the log buffer. SEE ALSO
Log::Any, Test::Log::Dispatch AUTHOR
Jonathan Swartz COPYRIGHT &; LICENSE Copyright (C) 2009 Jonathan Swartz, all rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2009-12-08 Log::Any::Test(3pm)
Man Page