<?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 file lock]]></title><description><![CDATA[<p dir="auto">On a Windows system, I'm executing an external script through the nxagent that writes to a .txt file.<br />
This file is monitored for changes by the logwatch subagent.</p>
<p dir="auto">When the external script tries to write to that .txt file, the script's own log shows that the file is locked by the nxagent.<br />
Is there any way to keep the agent from permanently locking the file?</p>
]]></description><link>https://forum.netxms.org/topic/5549/logwatch-file-lock</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 16:03:14 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5549.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 23 Apr 2018 11:55:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Logwatch file lock on Wed, 02 May 2018 19:16:21 GMT]]></title><description><![CDATA[<p dir="auto">I asked because I still had the same problems with the agent update from V2.2.3 to V2.2.4 that I had described here</p>
<p dir="auto"><a href="https://www.netxms.org/forum/installation/install-agent-2-2-1-fails/" rel="nofollow ugc">https://www.netxms.org/forum/installation/install-agent-2-2-1-fails/</a></p>
<p dir="auto">Maybe i had same Problem at Agent Update as the user who has opened this Thread:</p>
<p dir="auto"><a href="https://www.netxms.org/forum/installation/upgrading-agents/" rel="nofollow ugc">https://www.netxms.org/forum/installation/upgrading-agents/</a></p>
<p dir="auto">Greets<br />
Marco</p>
]]></description><link>https://forum.netxms.org/post/24211</link><guid isPermaLink="true">https://forum.netxms.org/post/24211</guid><dc:creator><![CDATA[Spheron]]></dc:creator><pubDate>Wed, 02 May 2018 19:16:21 GMT</pubDate></item><item><title><![CDATA[Reply to Logwatch file lock on Wed, 02 May 2018 18:14:18 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">no, it's irrelevant for Windows Event Log. Agent uses appropriate Windows API to access events in event log.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/24207</link><guid isPermaLink="true">https://forum.netxms.org/post/24207</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 02 May 2018 18:14:18 GMT</pubDate></item><item><title><![CDATA[Reply to Logwatch file lock on Wed, 02 May 2018 18:11:30 GMT]]></title><description><![CDATA[<p dir="auto">Hi Victor,</p>
<p dir="auto">does this option also apply to access to the Windows event log?</p>
<p dir="auto">Greets<br />
Marco</p>
]]></description><link>https://forum.netxms.org/post/24205</link><guid isPermaLink="true">https://forum.netxms.org/post/24205</guid><dc:creator><![CDATA[Spheron]]></dc:creator><pubDate>Wed, 02 May 2018 18:11:30 GMT</pubDate></item><item><title><![CDATA[Reply to Logwatch file lock on Wed, 02 May 2018 18:03:52 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">agent opens file being monitored with "shared for write" access. However, if application that writes to the file attempts to open it without specifying "shared for read" option it will get file open error. In upcoming 2.2.5 release we have added log parser option "keepOpen" that can be set to false to instruct parser to re-open file every time to get new records.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/24202</link><guid isPermaLink="true">https://forum.netxms.org/post/24202</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Wed, 02 May 2018 18:03:52 GMT</pubDate></item></channel></rss>