Antwort: RE: Printf issues with $output$ [Virus scanned]

[Dan Stromberg]

Actually, you can get pretty good linebreak support out of echo, by
combining it with tr.

EG, a line without a newline might look like:

echo "Foo bar " | tr -d '\012'

This is very portable.

On Fri, 2005-01-21 at 15:14 +0100, Sascha Runschke wrote:
> 
> The use of printf is necessary so you can nicely format the output as
> mail. 
> echo does not easily support linebreaks and such. You could force
> them 
> of course by using quoting ^M into the output, but that might pose
> other 
> unforeseen problems. 
> 
> sash 
> 
> --------------------------------------------------
> Sascha Runschke
> Netzwerk Administration
> IT-Services
> 
> ABIT AG
> Robert-Bosch-Str. 1
> 40668 Meerbusch
> 
> Tel.:+49 (0) 2150.9153.226
> mailto:SRunschke at abit.de
> 
> http://www.abit.net
> http://www.abit-epos.net
> http://www.my-academy.net
> --------------------------------------------------
> Der Inhalt dieser Email sowie die Anhänge sind ausschließlich für den
> bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene
> Adressat dieser Email oder dessen Vertreter sein sollten, so beachten
> Sie bitte, daß jede Form der Kenntnisnahme, Veröffentlichung,
>  Vervielfältigung oder Weitergabe des Inhalts dieser Email unzulässig
> ist. Wir möchten Sie außerdem darauf hinweisen, daß die Kommunikation
> per Email über das Internet unsicher ist, da fuer unberechtigte Dritte
> grundsätzlich die Möglichkeit der Kenntnisnahme und Manipulation
> besteht. Wenn Sie diese Nachricht versehentlich erhalten, informieren
> Sie bitte den Absender und löschen diese Nachricht mit den Anhängen.
> Herzlichen Dank
> 
> The information and any attachments contained in this email are
> intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any form of
> disclosure, reproduction, distribution or any action taken or
> refrained from in reliance on it, is prohibited and may be unlawful.
> We also like to inform you that communication via email over the
> internet is insecure because third parties may have the possibility to
> access and manipulate emails. If you have received the message in
> error, please advise the sender and delete the message and any
> attachments. Thank you very much. 
> 
> 
> 
> "Schmitz, Carsten"
> <Carsten.Schmitz at aegon.com> 
> Gesendet von: nagios-
> users-
> admin at lists.sourceforge.net 
> 
> 20.01.2005 17:04 
> 
> 
> 
>          
>         An:        "Ian
> Davidson"
> <idavidso at juniper.net>,
> <nagios-
> users at lists.sourceforge.net> 
>         Kopie:         
>         Thema:
>  RE: [Nagios-users]
> Printf issues with
> $output$ [Virus
> scanned]
> 
> 
> 
> 
> > it is processing the backslash as an exit request. Any ideas how to
> get
> > around this??
> 
> As someone who has never really used printf (at least not outside C),
> any reason you can't use echo? Seems to work:
> 
> /usr/local/nagios/libexec# printf "tes\t"
> tes
> 
> /usr/local/nagios/libexec# echo "tes\t"
> tes\t
> 
> Should work similar to this:
> 
> FILE=`mktemp /tmp/nagios_XXXXXX` && echo "my_text_with_backshashes" >
> $FILE && cat $FILE | mail -s "mytext" recipient at example.com ; rm $FILE
> 
> (and there's probably a way to do this without temp files and my
> "useless use of cat", too ;)
> 
> Cheers,
> 
> Carsten
> 
> 
> 
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Ian
> Davidson
> Sent: Thursday, January 20, 2005 1:57 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Printf issues with $output$
> 
> 
> I've seen a few questions on this subject but have yet to find the
> solution, so apologies if I'm going over old ground here.
> 
> I'm monitoring some Windows server disks and the resulting output is
> along the lines of:
> 
> 'c:\ - total: 16.92 Gb - used: 11.92 Gb (70%) - free 5.00 Gb (30%)',
> but
> printf is cutting off everything after the 'c:' in the email alerts as
> it is processing the backslash as an exit request. Any ideas how to
> get
> around this??
> 
> Cheers,
> 
> Ian
> ---
> Ian Davidson
> Corporate Network Services
> Email: idavidso at juniper.net
> GSM: +44-7952-173703
> Tel: +44-1372-385653 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive
> Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive
> Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://www.monitoring-lists.org/archive/users/attachments/20050121/46685fa9/attachment.sig>