Old feature request ;) http://tracker.labix.org/issue60
Keeping yours as that has priority urgent, while it is good to have a reference
to issue60 as that is old.
Please log all actions taken in smart to a file (/var/log/smart.log), no matter
if they are initiated from the GUI or the shell.
Example: I upgrade a system and find problems afterwards. It would be nice to be
able to look into a file to determine which new package might cause the problem
instead of having to rely on memory.
msg1327 (view) Author: rbos Date: 2008-03-25.21:40:28
Old feature request ;) tracker. labix.org/ issue60
http://
Keeping yours as that has priority urgent, while it is good to have a reference
to issue60 as that is old.
msg1320 (view) Author: casualprogrammer Date: 2008-03-09.09:34:39
I support this suggestion wholeheartedly.
It is _really_not_ state of the art to have users cut and paste log entries from
a window to a file.
Furthermore in most situations where smart gets in trouble the log windows is
inaccessible too.
Changing from "feature" to "urgent" as most bug reports do not get processed if
not accompanied by log data.
msg1316 (view) Author: digulla Date: 2008-02-10.16:46:27
Please log all actions taken in smart to a file (/var/log/ smart.log) , no matter
if they are initiated from the GUI or the shell.
Example: I upgrade a system and find problems afterwards. It would be nice to be
able to look into a file to determine which new package might cause the problem
instead of having to rely on memory.