Disabling OpenROAD Logfile

[Thomas_cim]

Hello,

it seems that sometimes our OpenROAD Programs can't open the w4gl.log-File - maybe because there is some read/write or write/write conflict ?
Everytime this happens - the program raises a MessageBox with the text 'Unable to Open the w4gl.log File'.

The bad thing here, is that this kind of processes have been started from a service - and so they got no visible Windows. No visible Windows means that no one can push the 'Ok' Button !

Iv'e tried to disable the Logfile simply by not setting the ingprenv 'II_LOG' and starting the Image with '-Tno' - but, as you can see in the attached picture, OpenROAD keeps on reading (and writing) to a trace file called 'w4gl.log' with resides in %II_SYSTEM%/ingres/files.

If there is happen something not good, I think the Error-Messagebox is displayed. I can't reproduce it, because this only seem to happen if many background-processes start at the same time.

Anyone has got any solutions for this problem ?

Thanks a lot !

Thomas

[Bodo]

I think there are some misunderstandings here.
If you start with "-Tno", then NO w4gl.log file is created.
If this is not the case, then this would be a bug.
In other cases (-T flag not set or in combination with "yes" or "all" options) the log file gets created in the directory %II_SYSTEM%\ingres\files by default (if II_LOG is not set), setting II_LOG redirects it to another directory.
Are you having multiple users using the same installation on a network drive (what's your II_SYSTEM)?
The "read/write" conflicts seem to point into that direction.
If that is the case you should make sure that at least II_LOG and II_TEMPORARY point to a local, user-specific directory.
You can also use a -L flag to specify the name of the logfile (e.g. containing the username and current date/time), so a conflict because of several processes trying to access the same file shouldn't happen.

[Thomas_cim]

Hello Bodo,

I am very sure that I've started w4glrun with -Tno - but I will doublecheckit !

And you're right: We use the same installation for many user by using UNC-paths...

Thanks for your fast reply - hopefully we can find the failure or bug (I tend to think it's a bug, because I'm sure I've typed '-Tno' AND 'ingunsetenv II_LOG'...)

Greetings,

Thomas

[Bodo]

I just tested and it seems that there is in fact a bug - an empty w4gl.log file gets created even if "-Tno" is specified.
But there is workaround: Additionally specify the "-L" flag and point it to the NUL device, e.g.:
w4glrun my.img -Tno -LNUL

Anyway, you should open a ServiceDesk issue in order to get a fix for the bug.

[Adrian Williamson]

Hi,

On a simliar note;

I've seen that 'unable to open w4gl.log file' before on machines that are shared between users. (Different login credentials - just shared PCs)

We used the cacls command to change the access control list on the w4gl.log file to allow the everyone group to read and write to it.

Regards,

Adrian