Problems with WebParser and local log file

[Kosidive]

I am trying to use webparser to parse a local file however since it is a log file and being constantly written to, I am given an error. The error I'm getting is.

Code: Select all

[MeasureParent]: (Fetch error) The process cannot access the file because it is being used by another process.  (ErrorCode=32)

How might I go around this issue? I'll leave my skin. I know it is not an issue with my regex because I tested it with RainRegExp and it worked just fine.

Code: Select all

[Rainmeter]
Update=1000
AccurateText=1

[Metadata]
Name=WarframeLevel
Author=Kosidive
Information=Reads Level Data from Log File
Version=1.0
License=Creative Commons Attribution - Non - Commercial - Share Alike 3.0

[MeasureLevel]
Measure=WebParser
URL=file://C:\Users\kosi\AppData\Local\Warframe\EE.log
RegExp=(?siU)Generated layout in(.*)Found
UpdateRate=10
Debug=2

[MeterLevel]
Meter=String
MeasureName=MeasureLevel
FontSize=12
FontColor=255,255,255,255
AntiAlias=1

[death.crafter]

I am trying to use webparser to parse a local file however since it is a log file and being constantly written to, I am given an error. The error I'm getting is.

Code: Select all

[MeasureParent]: (Fetch error) The process cannot access the file because it is being used by another process.  (ErrorCode=32)

How might I go around this issue? I'll leave my skin. I know it is not an issue with my regex because I tested it with RainRegExp and it worked just fine.

Code: Select all

[Rainmeter]
Update=1000
AccurateText=1

[Metadata]
Name=WarframeLevel
Author=Kosidive
Information=Reads Level Data from Log File
Version=1.0
License=Creative Commons Attribution - Non - Commercial - Share Alike 3.0

[MeasureLevel]
Measure=WebParser
URL=file://C:\Users\kosi\AppData\Local\Warframe\EE.log
RegExp=(?siU)Generated layout in(.*)Found
UpdateRate=10
Debug=2

[MeterLevel]
Meter=String
MeasureName=MeasureLevel
FontSize=12
FontColor=255,255,255,255
AntiAlias=1

I don't think you can access files that are currently being used by another app. It's the way it is.

[DanDaBear]

I suppose you could save the log file to a temporary text file first then parse the temp text file.

[jsmorley]

The process that is creating the log is opening it in "exclusive" write mode, so you just won't be able to access it.

Assuming you can't control the code that is creating the log file, the only thing that comes to mind is to have Rainmeter "kill" the process that is creating the log, make a copy of it or read it directly, then restart the process. This is going to make reading the log file in any kind of "real time" way impossible of course.

[balala]

I suppose you could save the log file to a temporary text file first then parse the temp text file.

How?

[Yincognito]

How?

If not for the "exclusive mode" jsmorley mentioned, quite easily:
- use either Debug=2, Debug2File, Download or DownloadFile in the WebParser parent, to save the file
- use a 2nd WebParser parent to read the saved file, by opening it locally, through URL=file://SomePath\SomeFile.txt

[jsmorley]

If not for the "exclusive mode" jsmorley mentioned, quite easily:
- use either Debug=2, Debug2File, Download or DownloadFile in the WebParser parent, to save the file
- use a 2nd WebParser parent to read the saved file, by opening it locally, through URL=file://SomePath\SomeFile.txt

Right, but I doubt that a file that is locked from reading is going to allow WebParser to make a copy of it.

[Yincognito]

Right, but I doubt that a file that is locked from reading is going to allow WebParser to make a copy of it.

Indeed, it probably won't...

[jsmorley]

File opening modes are pretty much the same for all languages.

In C, it's:

Code: Select all

r - open a file in read mode.
w - opens or create a text file in write mode.
a - opens a file in append mode.
r+ - opens a file in both read and write mode.
a+ - opens a file in both read and write mode.
w+ - opens a file in both read and write mode.

No doubt this log is opened in w or a mode.

[Yincognito]

File opening modes are pretty much the same for all languages.

In C, it's:

Code: Select all

r - open a file in read mode.
w - opens or create a text file in write mode.
a - opens a file in append mode.
r+ - opens a file in both read and write mode.
a+ - opens a file in both read and write mode.
w+ - opens a file in both read and write mode.

No doubt this log is opened in w or a mode.

As far as I know, it's a bit of a bad practice to do such things in an exclusive mode, but then, that software probably has its reasons to do so...