ovaldi log writing during execution

[Pavel Vinogradov-3]

Hello.

During packaging ovaldi 5.6.1 for Debian my mentor Javier
Fernandez-Sanguino point me to some problems with ovaldi log file
creation.

ovaldi always create logfile in current dir during execution and fails
if can't write to current dir. ovaldi have options to -d, -r, -x to
provide different location for result files, but we can't disable log
creation or specify alternative location for logfile.

This cause problem when we run ovaldi in directory on read-only fs or
without write permission.

We can solve this issue by:
 - adding new option to specify alternative location of logfile
 - disable logfile writing by default (all logfile information is
write to stdout by default) and create option to enable logfile
creation
- combine both of this variant

We can implement this behaviour for our Debian package, but we prefer
to see this in upstream and don't support additional custom patch.
Therefore i want ask opinion of other Oval developers and find best
way to solve this issue.

--
Pavel Vinogradov
NixDev.Net, Open Source Developer

To unsubscribe, send an email message to [hidden email] with
SIGNOFF OVAL-DEVELOPER-LIST
in the BODY of the message.  If you have difficulties, write to [hidden email].

[bakerj]

Pavel,

Thanks for bringing this issue up. I think that the best way to go here is to add another flag that will allow the user to specify the location of the log file. The new parameter will have a default value that will match the current behavior.

Also note that the log file may contain more information that what is output to stdout. This depends on the other command line options.

We will address this issue in the next release of the interpreter. I expect to have another release out before the end of September.

I have entered the following feature request on the oval interpreter sourceforge site to track this issue:

https://sourceforge.net/tracker/?func=detail&aid=2864999&group_id=215469&atid=1033797


Thanks,

Jon

============================================
Jonathan O. Baker
G022 - IA Industry Collaboration
The MITRE Corporation
Email: [hidden email]

>-----Original Message-----
>From: Pavel Vinogradov [mailto:[hidden email]]
>Sent: Wednesday, September 16, 2009 12:15 AM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: [OVAL-DEVELOPER-LIST] ovaldi log writing during execution
>
>Hello.
>
>During packaging ovaldi 5.6.1 for Debian my mentor Javier
>Fernandez-Sanguino point me to some problems with ovaldi log file
>creation.
>
>ovaldi always create logfile in current dir during execution and fails
>if can't write to current dir. ovaldi have options to -d, -r, -x to
>provide different location for result files, but we can't disable log
>creation or specify alternative location for logfile.
>
>This cause problem when we run ovaldi in directory on read-only fs or
>without write permission.
>
>We can solve this issue by:
> - adding new option to specify alternative location of logfile
> - disable logfile writing by default (all logfile information is
>write to stdout by default) and create option to enable logfile
>creation
>- combine both of this variant
>
>We can implement this behaviour for our Debian package, but we prefer
>to see this in upstream and don't support additional custom patch.
>Therefore i want ask opinion of other Oval developers and find best
>way to solve this issue.
>
>--
>Pavel Vinogradov
>NixDev.Net, Open Source Developer
>
>To unsubscribe, send an email message to [hidden email] with
>SIGNOFF OVAL-DEVELOPER-LIST
>in the BODY of the message.  If you have difficulties, write to OVAL-
>[hidden email].

To unsubscribe, send an email message to [hidden email] with
SIGNOFF OVAL-DEVELOPER-LIST
in the BODY of the message.  If you have difficulties, write to [hidden email].