Sponsored Content
Full Discussion: Ops Center AI wrong IP
Operating Systems Solaris Ops Center AI wrong IP Post 302880636 by olibertu on Saturday 21st of December 2013 02:36:52 PM
Old 12-21-2013
 

4 More Discussions You Might Find Interesting

1. Solaris

Sun xVM Ops Center 1.1

I have 180 Solaris 7, 8 and 9 servers to patch and am looking at using xVM Ops Center. Has anyone here had any experience with it? (1 Reply)
Discussion started by: mr_crosby
1 Replies

2. Solaris

Sun Ops Center

Hi, Can anyone share the link to download sun ops centre i have sun partner account, but i unable find the link Thanks RJS (3 Replies)
Discussion started by: rajasekg
3 Replies

3. Solaris

OPS Center Email Notifications

Hi, Does any one know how to configure email notifications (to exchange) in Oracle Enterprise Manager 11g OPS Center? I have gone through the documentation and have done everything it asked, but still no notifications via email. I get the following error: At the OS level i tried sending email... (20 Replies)
Discussion started by: Mack1982
20 Replies

4. Infrastructure Monitoring

Agent Installation Issue on Ops Center

Hi guys . While installing the agent on an asset Solaris system: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
NullLogLite(3pm)					User Contributed Perl Documentation					  NullLogLite(3pm)

NAME
Log::NullLogLite - The "Log::NullLogLite" class implements the Null Object pattern for the "Log::LogLite" class. SYNOPSIS
use Log::NullLogLite; # create new Log::NullLogLite object my $log = new Log::NullLogLite(); ... # we had an error (this entry will not be written to the log # file because we use Log::NullLogLite object). $log->write("Could not open the file ".$file_name.": $!", 4); DESCRIPTION
The "Log::NullLogLite" class is derived from the "Log::LogLite" class and implement the Null Object Pattern to let us to use the "Log::LogLite" class with null "Log::LogLite" objects. We might want to do that if we use a "Log::LogLite" object in our code, and we do not want always to actually define a "Log::LogLite" object (i.e. not always we want to write to a log file). In such a case we will create a "Log::NullLogLite" object instead of the "Log::LogLite" object, and will use that object instead. The object has all the methods that the "Log::LogLite" object has, but those methods do nothing. Thus our code will continue to run without any change, yet we will not have to define a log file path for the "Log::LogLite" object, and no log will be created. CONSTRUCTOR
new ( FILEPATH [,LEVEL [,DEFAULT_MESSAGE ]] ) The constructor. The parameters will not have any affect. Returns the new Log::NullLogLite object. METHODS
write( MESSAGE [, LEVEL ] ) Does nothing. The parameters will not have any affect. Returns nothing. level( [ LEVEL ] ) Does nothing. The parameters will not have any affect. Returns -1. default_message( [ MESSAGE ] ) Does nothing. The parameters will not have any affect. Returns empty string (""). AUTHOR
Rani Pinchuk, rani@cpan.org COPYRIGHT
Copyright (c) 2001-2002 Ockham Technology N.V. & Rani Pinchuk. All rights reserved. This package is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Log::LogLite(3), The Null Object Pattern - Bobby Woolf - PLoP96 - published in Pattern Languages of Program Design 3 (http://cseng.aw.com/book/0,,0201310112,00.html) perl v5.10.0 2009-05-13 NullLogLite(3pm)
All times are GMT -4. The time now is 08:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy