Issue 364: Log all actions (and probably the results, too) to a file - Labix issue tracker

Project	smart
Title	Log all actions (and probably the results, too) to a file
Priority	urgent	Status	resolved
Superseder		Nosy List	casualprogrammer, digulla, rasker, rbos
Assigned To	rasker	Topics

Created on 2008-02-10.16:46:28 by digulla, last changed 2008-06-29.14:54:51 by rasker.

Messages
msg1353 (view)	Author: rasker	Date: 2008-06-29.14:54:51
Exported: https://bugs.launchpad.net/smart/+bug/243976 Reason for Export: This is implemented? If so update documentation. Possibly add a log viewer to smart --gui? Also enable by default.
msg1327 (view)	Author: rbos	Date: 2008-03-25.21:40:28
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.
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.

History
Date	User	Action	Args
2008-06-29 14:54:52	rasker	set	status: chatting -> resolved nosy: + rasker messages: + msg1353 assignedto: rasker
2008-03-25 21:40:29	rbos	set	nosy: + rbos messages: + msg1327
2008-03-09 09:34:39	casualprogrammer	set	priority: feature -> urgent nosy: + casualprogrammer status: unread -> chatting messages: + msg1320
2008-02-10 16:46:29	digulla	create