/var/log/messages is filled up to several gibabyte

Started by MarioMic, October 08, 2013, 04:07:16 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Liviu Lalescu

I decided to keep an option: "--verbose=true" to the command line version, in case someone wants verbosity. Please test the new snapshot and report results.

MarioMic

I use the gui version rather than the command line, but I think it would be helpful to have a default fet-cl output to the terminal that shows the progress of the operations, similar to the output of the gui version for the placed activities to have an idea of how far away is the result and, perhaps, an option -d or --debug to get debug output, but I think it's just a minor improvement, non urgent (I don't know how demanding it is to add command options to fet-cl).
I don't know how useful this output, but certainly it is an information for the progress of the operations, and so, in the meantime, I would keep the debug output to the terminal.

MarioMic

Quote from: Liviu Lalescu on October 10, 2013, 11:01:22 AM
I decided to keep an option: "--verbose=true" to the command line version, in case someone wants verbosity. Please test the new snapshot and report results.

Yes, I think it's ok.
This evening I'll try the latest version and let you know.

MarioMic

Hello Liviu,
I have compiled and tested the latest version at http://lalescu.ro/liviu/fet/download/test/fet-5.20.2-snapshot-10-oct-2013-12_52.tar.bz2 and it works as expected:
Quote from: MarioMic on October 09, 2013, 10:47:19 PM
Watching with system monitor the running process, fet-cl first write two files, $OUTPUT_PATH/logs/file_open.log and $OUTPUT_PATH/logs/initial_order.txt, and during the computation uses only the files: $OUTPUT_PATH/logs/result.txt, $OUTPUT_PATH/logs/max_placed_activities.txt, /dev/pts/0, /dev/pts/0, /dev/pts/0, anon_inode:[eventfd] and two pipes (and at the end writes the result content in the timetable folder).
The gui version fet first write one file, $OUTPUT_PATH/logs/file_open.log, and during the multiple timetables computation uses only /dev/null, some local sockets, some pipes, some anon_inode:[eventfd], /dev/dri/card0 and at the end writes the result content and result.txt in the timetable folder.
The fet-cl option --verbose=true works in the right way with debug messages only on the terminal output... no data on /var/log/messages...
Good job! Thanks.

Liviu Lalescu