Engelmann, Austin wrote:
> notification type to be on the "MSG:" line. In my command, the 
> notification type always gets place on the next line.

It looks like "FRM:", "SUBJ:", and "MSG:" are being added by your phone. 
  Those words do not appear in your command.  You can verify this by 
setting your pager address as your regular e-mail address.

Here is the command I use:
define command{
         command_name    notify-by-epager
         command_line    /usr/bin/printf "%b" "$HOSTNAME$/$SERVICEDESC$ 
is $SERVICESTATE$\n$SERVICEOUTPUT$\n$SHORTDATETIME$" | /bin/mail -s 
"$NOTIFICATIONTYPE$: $HOSTNAME$/$SERVICEDESC$" $CONTACTPAGER$
}

And here is a "page", sent to a regular e-mail client:

From: nagios@domain [mailto:nagios@domain]
Sent: Thursday, February 17, 2011 2:46 PM
To: Chris Beattie
Subject: PROBLEM: servername/Disk: F

servername/Disk: F is WARNING
F:\ - total: 399.99 Gb - used: 342.71 Gb (86%) - free 57.27 Gb (14%)
02-17-2011 14:46:02

-- 
-Chris

------


Nothing in this message is intended to make or accept an offer or to form a 
contract, except that an attachment that is an image of a contract bearing the 
signature of an officer of our company may be or become a contract. This 
message (including any attachments) is intended only for the use of the 
individual or entity to whom it is addressed. It may contain information that 
is non-public, proprietary, privileged, confidential, and exempt from 
disclosure under applicable law or may constitute as attorney work product. If 
you are not the intended recipient, we hereby notify you that any use, 
dissemination, distribution, or copying of this message is strictly prohibited. 
If you have received this message in error, please notify us immediately by 
telephone and delete this message immediately.

Thank you.


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to