Custom Commands with Semicolons: bug or feature?

[Jamin]

Can anyone shed any light on why custom commands (misccommands.cfg) are
truncated on semicolons?  Is this a bug or a feature?

For the life of me, I have tried to escape the semicolon so that it is
ignored when nagios parses the config files, but no matter what, if a
semicolon exists in the command line, everything after it gets truncated.

If you have an enlightened explanation of this, I would be very 
interested in it.  Thanks in advance.

-Jamin

P.S. As you can see from my previous posts this is what is happening....
I am attempting to escape the semicolon with a backslash.
______________________________________________________________________________
This is the problem here.  Example line I want executed::

/nfs/user/j/jragle/bin/testit.pl HostDown "severity:1\;title:alert - Host
$HOSTNAME$ is $HOSTSTATE$\;description:Host $HOSTALIAS$ is $HOSTSTATE$ at
$SHORTDATETIME$\;"

AND Nagios thinks its this:: (via view config of commands)

nfs/user/j/jragle/bin/testit.pl HostDown "severity:1\
______________________________________________________________________________



-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate 
is essential in establishing user confidence by providing assurance of 
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en