Sponsored Content
Operating Systems Linux Red Hat Syslog.conf: looking for a simple answer on a simple question Post 302826827 by MadeInGermany on Thursday 27th of June 2013 11:33:42 AM
Old 06-27-2013
I think all vendors define all severe types. This is the minimum level, e.g. err includes crit.
You can test with the logger command
Code:
logger -p user.crit 'this is user.crit'

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Simple Question

Can anyone tell me if there is a way to remove the encryption from Data CDs by UNIX? Or does anyone know of a program that can remove the encryption? I would much appreciate it! Thanks, -Peaves (2 Replies)
Discussion started by: Peaves
2 Replies

2. UNIX for Dummies Questions & Answers

Ok simple question for simple knowledge...

Ok what is BSD exactly? I know its a type of open source but what is it exactly? (1 Reply)
Discussion started by: Corrail
1 Replies

3. Programming

Simple C question... Hopefully it's simple

Hello. I'm a complete newbie to C programming. I have a C program that wasn't written by me where I need to write some wrappers around it to automate and make it easier for a client to use. The problem is that the program accepts standard input to control the program... I'm hoping to find a simple... (6 Replies)
Discussion started by: Xeed
6 Replies

4. Solaris

Solaris JumpStarting?... Simple Yes/No Question... Unless the answer's 'No'

I'm reading through this guide, BigAdmin Feature Article: Using Solaris JumpStart With the Solaris 10 OS for x86/x64 Platforms, and I was wondering if there was more to the bash scripts than just the example given (see above link) like for begin1 and begin2 and finish1 and finish2. I don't know... (3 Replies)
Discussion started by: Bradj47
3 Replies

5. Shell Programming and Scripting

Simple if then else question

I am having trouble making this statement work. I am passing in a number value for the number of days to keep archive logs for and wanted to make sure that it is a number. I have a script that will return 1 for is a number and 0 for is not a number. I also want to make sure that the number is not... (2 Replies)
Discussion started by: gandolf989
2 Replies

6. UNIX for Dummies Questions & Answers

TAR question (probably a very simple answer)

Hi All, I have a (probably) very simple tar question on a Solaris box that I'm a little embarrassed to ask. After repeatedly checking man tar and searching for solutions online (I'm not sure of the correct "keywords" to look for) The question is: If I were to use the command:tar cf... (4 Replies)
Discussion started by: chatguy
4 Replies

7. UNIX for Dummies Questions & Answers

simple(?) if/else question

Hello, I have a quick question that is not related to homework in any way shape or form (in case anyone wanted to know). My question is thus: I have a file "temp" that has the two values say "5" and "3" (separated by a white space). Now, I want to simply write an if-else statement that reads... (10 Replies)
Discussion started by: astropi
10 Replies

8. Shell Programming and Scripting

Help making simple perl or bash script to create a simple matrix

Hello all! This is my first post and I'm very new to programming. I would like help creating a simple perl or bash script that I will be using in my work as a junior bioinformatician. Essentially, I would like to take a tab-delimted or .csv text with 3 columns and write them to a "3D" matrix: ... (16 Replies)
Discussion started by: torchij
16 Replies

9. Shell Programming and Scripting

Very simple question

Hi, guys, I'm a new comer here. I'm studying Unix Shell and I met a problem confusing me a lot. Here it is : script 1: #!/bin/sh # scriptname : do_increment increment(){ sum=`expr $1 + 1` return $sum # Return the value of sum to the script. } echo -n "The sum is " increment $1 # Call... (2 Replies)
Discussion started by: franksunnn
2 Replies

10. Shell Programming and Scripting

Simple question

Sorry for stupid question, but why this script gives that output? $ awk 'BEGIN { well=56789; print 1234$well }' 1234 I expected 123456789 (9 Replies)
Discussion started by: silyin
9 Replies
Nagios::Plugin::Functions(3pm)				User Contributed Perl Documentation			    Nagios::Plugin::Functions(3pm)

NAME
Nagios::Plugin::Functions - functions to simplify the creation of Nagios plugins SYNOPSIS
# Constants OK, WARNING, CRITICAL, and UNKNOWN exported by default use Nagios::Plugin::Functions; # nagios_exit( CODE, $message ) - exit with error code CODE, # and message "PLUGIN CODE - $message" nagios_exit( CRITICAL, $critical_error ) if $critical_error; nagios_exit( WARNING, $warning_error ) if $warning_error; nagios_exit( OK, $result ); # nagios_die( $message, [$CODE] ) - just like nagios_exit(), # but CODE is optional, defaulting to UNKNOWN do_something() or nagios_die("do_something() failed horribly"); do_something_critical() or nagios_die("do_something_critical() failed", CRITICAL); # check_messages - check a set of message arrays, returning a # CODE and/or a result message $code = check_messages(critical => @crit, warning => @warn); ($code, $message) = check_messages( critical => @crit, warning => @warn, ok => @ok ); # get_shortname - return the default short name for this plugin # (as used by nagios_exit/die; not exported by default) $shortname = get_shortname(); DESCRIPTION
This module is part of the Nagios::Plugin family, a set of modules for simplifying the creation of Nagios plugins. This module exports convenience functions for the class methods provided by Nagios::Plugin. It is intended for those who prefer a simpler functional interface, and who do not need the additional functionality of Nagios::Plugin. EXPORTS Nagios status code constants are exported by default: OK WARNING CRITICAL UNKNOWN DEPENDENT as are the following functions: nagios_exit nagios_die check_messages The following variables and functions are exported only on request: %ERRORS %STATUS_TEXT get_shortname max_state max_state_alt FUNCTIONS The following functions are supported: nagios_exit( <CODE>, $message ) Exit with return code CODE, and a standard nagios message of the form "PLUGIN CODE - $message". nagios_die( $message, [CODE] ) Same as nagios_exit(), except that CODE is optional, defaulting to UNKNOWN. NOTE: exceptions are not raised by default to calling code. Set $_use_die flag if this functionality is required (see test code). check_messages( critical => @crit, warning => @warn ) Convenience function to check a set of message arrays and return an appropriate nagios return code and/or a result message. Returns only a return code in scalar context; returns a return code and an error message in list context i.e. # Scalar context $code = check_messages(critical => @crit, warning => @warn); # List context ($code, $msg) = check_messages(critical => @crit, warning => @warn); check_messages() accepts the following named arguments: critical => ARRAYREF An arrayref of critical error messages - check_messages() returns CRITICAL if this arrayref is non-empty. Mandatory. warning => ARRAYREF An arrayref of warning error messages - check_messages() returns WARNING if this arrayref is non-empty ('critical' is checked first). Mandatory. ok => ARRAYREF | SCALAR An arrayref of informational messages (or a single scalar message), used in list context if both the 'critical' and 'warning' arrayrefs are empty. Optional. join => SCALAR A string used to join the relevant array to generate the message string returned in list context i.e. if the 'critical' array @crit is non-empty, check_messages would return: join( $join, @crit ) as the result message. Optional; default: ' ' (space). join_all => SCALAR By default, only one set of messages are joined and returned in the result message i.e. if the result is CRITICAL, only the 'critical' messages are included in the result; if WARNING, only the 'warning' messages are included; if OK, the 'ok' messages are included (if supplied) i.e. the default is to return an 'errors-only' type message. If join_all is supplied, however, it will be used as a string to join the resultant critical, warning, and ok messages together i.e. all messages are joined and returned. get_shortname Return the default shortname used for this plugin i.e. the first token reported by nagios_exit/nagios_die. The default is basically uc basename( $ENV{NAGIOS_PLUGIN} || $0 ) with any leading 'CHECK_' and trailing file suffixes removed. get_shortname is not exported by default, so must be explicitly imported. max_state(@a) Returns the worst state in the array. Order is: CRITICAL, WARNING, OK, UNKNOWN, DEPENDENT The typical usage of max_state is to initialise the state as UNKNOWN and use it on the result of various test. If no test were performed successfully the state will still be UNKNOWN. max_state_alt(@a) Returns the worst state in the array. Order is: CRITICAL, WARNING, UNKNOWN, DEPENDENT, OK This is a true definition of a max state (OK last) and should be used if the internal tests performed can return UNKNOWN. SEE ALSO
Nagios::Plugin; the nagios plugin developer guidelines at http://nagiosplug.sourceforge.net/developer-guidelines.html. AUTHORS
This code is maintained by the Nagios Plugin Development Team: http://nagiosplug.sourceforge.net COPYRIGHT AND LICENSE
Copyright (C) 2006 by Nagios Plugin Development Team This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2011-12-23 Nagios::Plugin::Functions(3pm)
All times are GMT -4. The time now is 07:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy