<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Logwatch - Environment Variables]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Just wondering, do/shoulod environment variables work in a Logwatch parser definition?<br />
I tried using %PROGRAMDATA% and the result was that the NetXMS Agent service would not start anymore. The moment I replaced that with C:\ProgramData everything just worked. As different Windows versions use different paths, using an environment variable would be preferable to creating a number of parsers (one for each possible file location)?</p>
<p dir="auto">Cheers</p>
]]></description><link>https://forum.netxms.org/topic/5205/logwatch-environment-variables</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 13:58:42 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5205.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 15 Aug 2017 03:16:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Logwatch - Environment Variables on Tue, 15 Aug 2017 11:12:52 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">you can use time formats, environment variables, and shell commands for file name expansion in parsers. To insert environment variable, use macro ${name}. To insert result of shell command use form `command`. Time formats are the same as supported by strftime (<a href="http://www.cplusplus.com/reference/ctime/strftime/" rel="nofollow ugc">http://www.cplusplus.com/reference/ctime/strftime/</a>).</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/22930</link><guid isPermaLink="true">https://forum.netxms.org/post/22930</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 15 Aug 2017 11:12:52 GMT</pubDate></item></channel></rss>