TurboFloat relative log files

Sorry me again...

I reinstalled the TurboFloat server on another computer on my home network. But I couldn't make the application get a lease. The only debug tools there is is the log file so I coded the config file to use the most verbose option (notification). I uninstalled and reinstalled the server and the log kept showing only the line stating that the service was successfully uninstalled (only one line per uninstall, nothing else).

My log file entry is coded as this:

<log file="tfs-log.txt" level="notification"/>

It turns out that if I add a full path then the log starts getting populated and shows an actual error: "<error> Not activated (error code: 0x3)..." which I think is related to my previous problem about deactivating a product key.

Why isn't the log file entry as coded above working? Is it by design? It would extremely convenient to be able to create the log in whatever folder the server exe happens to be, without having to specify the path.

Thanks.

Why isn't the log file entry as coded above working? Is it by design?

Yes. The current version of TurboFloat Server only support absolute paths for the log file. We do plan on making the log file work relative paths. It just hasn't been written yet.

It will come when we release the Linux / Mac versions of the TurboFloat Server.

Side note: the log file was being written, but if you were using the TFS as a Windows Service then the log file is being written to the "current directory". Which I believe is C:\Windows\System32. But we will fix this so that a "relative" log file path will be relative to the TFS.exe and not to the "current directory".

Ok, that sounds great.

TurboFloat Server 3.5.5.1 is now out -- this now allows relative log files. There are a ton of other fixes in this release. Get it on your API page.

Reply
Discard post