[SOLVED] Crash due to 17GB log files (WINE > /var/log/message.log)

sultanoswing · 2016-06-25 23:06:00

My PC crashed yesterday for no apparent reason. On further investigation, the disk was totally full thanks to several multi-gigabyte log files (/var/log/messages.log).

The cause of this appears to be multiple messages, generated every 5 seconds or so, from Apexdc and WINE.

Jun 26 09:22:51 my-hostname apexdc.desktop[1547]: fixme:taskschd:regtasks_get_Count 0x21f8f0,0x1eddc0c: stub

As a workaround while I sort the WINE error out, I'm running an hourly cron job to clear the log file (cat /dev/null > /var/log/messages.log).

Question: Is there a way to stop WINE from logging this error to the messages.log file in the first place?

Last edited by sultanoswing (2016-06-26 09:13:42)

Trilby · 2016-06-25 23:10:18

https://wiki.winehq.org/FAQ#I_get_lots_ … a_bit_slow

sultanoswing · 2016-06-26 09:17:27

Trilby wrote:

https://wiki.winehq.org/FAQ#I_get_lots_ … a_bit_slow

Thanks for the link. I'd actually tried something similar and it didn't appear to be working - except I then realised was trying the WINEDEBUG commands in terminal as 'su', rather than the user where the wine session/program was running erroneously. Sigh.

I'm now launching apexdc using "WINDEDEBUG=-all "C:/Program Files/ApexDC++/ApexDC-x64.exe" in a shell script, called from a startup launcher in "/home/me/.config/autostart". All debugging output logging for Apex is now successfully prevented (after a reboot).

As a bonus side effect, Apex now launches and starts up much faster than when it was being directly loaded from the autostart folder.

Arch Linux

#1 2016-06-25 23:06:00

[SOLVED] Crash due to 17GB log files (WINE > /var/log/message.log)

#2 2016-06-25 23:10:18

Re: [SOLVED] Crash due to 17GB log files (WINE > /var/log/message.log)

#3 2016-06-26 09:17:27

Re: [SOLVED] Crash due to 17GB log files (WINE > /var/log/message.log)

Board footer