Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 11:14:15AM +0200, Yonit Halperin wrote: Hi, Are there any plans to have a log file for spice-gtk? I think that it is very important to have logging with configurable debug level via a configuration file. It will be helpful for live debugging of user problems that are hard to reproduce. I also saw there was some discussion about .spicec directory. It is used by the old client for logs and also for holding the certificate files. (In windows machine it is in %APPDATA%/spicec) IMHO libraries have no business creating logfiles of their own accord. It should be entirely in the control of applications using the libraries to decide on logging policy. For virt-viewer you can enable debugging of various areas with flags --spice-gtk-debug, --gtk-vnc-debug and --debug. There are also env variables which can control logging in newer GLib versions Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 10:23:28AM +, Daniel P. Berrange wrote: On Thu, Mar 15, 2012 at 11:14:15AM +0200, Yonit Halperin wrote: Hi, Are there any plans to have a log file for spice-gtk? I think that it is very important to have logging with configurable debug level via a configuration file. It will be helpful for live debugging of user problems that are hard to reproduce. I also saw there was some discussion about .spicec directory. It is used by the old client for logs and also for holding the certificate files. (In windows machine it is in %APPDATA%/spicec) IMHO libraries have no business creating logfiles of their own accord. It should be entirely in the control of applications using the libraries to decide on logging policy. For virt-viewer you can enable debugging of various areas with flags --spice-gtk-debug, --gtk-vnc-debug and --debug. There are also env variables which can control logging in newer GLib versions OK, so I think there is place to make remote-viewer produce a log file by default. 1. For any hard to reproduce error there will be a log file by default. 2. Users who were used to spicec.log will have a remote-viewer.log I haven't noticed any easy way to set a fd different then stderr for debugging output though, maybe someone can help? Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 12:39:13PM +0200, Alon Levy wrote: On Thu, Mar 15, 2012 at 10:23:28AM +, Daniel P. Berrange wrote: On Thu, Mar 15, 2012 at 11:14:15AM +0200, Yonit Halperin wrote: Hi, Are there any plans to have a log file for spice-gtk? I think that it is very important to have logging with configurable debug level via a configuration file. It will be helpful for live debugging of user problems that are hard to reproduce. I also saw there was some discussion about .spicec directory. It is used by the old client for logs and also for holding the certificate files. (In windows machine it is in %APPDATA%/spicec) IMHO libraries have no business creating logfiles of their own accord. It should be entirely in the control of applications using the libraries to decide on logging policy. For virt-viewer you can enable debugging of various areas with flags --spice-gtk-debug, --gtk-vnc-debug and --debug. There are also env variables which can control logging in newer GLib versions OK, so I think there is place to make remote-viewer produce a log file by default. 1. For any hard to reproduce error there will be a log file by default. 2. Users who were used to spicec.log will have a remote-viewer.log I haven't noticed any easy way to set a fd different then stderr for debugging output though, maybe someone can help? IIUC, you have to write set a custom log handler function http://developer.gnome.org/glib/unstable/glib-Message-Logging.html#g-log-set-handler Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 11:39 AM, Alon Levy al...@redhat.com wrote: OK, so I think there is place to make remote-viewer produce a log file by default. The caller of virt-viewer/spice-gtk can redirect logging to files. By experience, I'd say this is the right solution, as it avoid filling disk or getting complicated logging (it's not difficult to get several megabytes in several files...) 1. For any hard to reproduce error there will be a log file by default. What do you mean by default? There are very good reasons why logging files aren't used, not even by default. There are tons of things missing anyway, typically how/where/who compiled the project, the gazillions of depedencies information and their own logging etc.. spice-gtk/remote-viewer probably account for 0.01% of the code that is actually run.. If we want Spice domain logging, then we should dump the traffic, at least we would be able to reproduce something eventually.. And in the end, 99% of the bugs are solved with: backtrace + reproducer. Not logging. 2. Users who were used to spicec.log will have a remote-viewer.log Why? Who is used to spicec.log? there isn't such thing anymore, and it hasn't been specified what is spicec.log. I haven't noticed any easy way to set a fd different then stderr for debugging output though, maybe someone can help? By stderr redirection, if you really want to (for example, when the reproducer is only on one machine) -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 12:25:19PM +0100, Marc-André Lureau wrote: 1. For any hard to reproduce error there will be a log file by default. And in the end, 99% of the bugs are solved with: backtrace + reproducer. Not logging. For real bugs in the code that's true. However, this work only starts once you've ruled out user-related issues, bad system configuration, network issues, ... and for this kind of issues, logging is much more helpful than a backtrace. Christophe pgp81J5JEHN9t.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On 03/15/2012 01:25 PM, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 11:39 AM, Alon Levyal...@redhat.com wrote: OK, so I think there is place to make remote-viewer produce a log file by default. The caller of virt-viewer/spice-gtk can redirect logging to files. By experience, I'd say this is the right solution, as it avoid filling disk or getting complicated logging (it's not difficult to get several megabytes in several files...) There is no need to dump everything. For this aim we should use log levels, which should be configurable via a configuration file or something similar. 1. For any hard to reproduce error there will be a log file by default. What do you mean by default? There are very good reasons why logging files aren't used, not even by default. There are tons of things missing anyway, typically how/where/who compiled the project, the gazillions of depedencies information and their own logging etc.. spice-gtk/remote-viewer probably account for 0.01% of the code that is actually run.. If we want Spice domain logging, then we should dump the traffic, at least we would be able to reproduce something eventually.. And in the end, 99% of the bugs are solved with: backtrace + reproducer. Not logging. I beg to differ you. From my experience, spice client logs are very helpful. With the minimal information spice-client log holds, we could help many users. Sometimes you cannot reproduce problems at your own environment, and you can't ask the user to use backtrace. 2. Users who were used to spicec.log will have a remote-viewer.log Why? Who is used to spicec.log? there isn't such thing anymore, and it hasn't been specified what is spicec.log. Well, there used to be such thing for a while, and we did use it. QE also knows about it... I haven't noticed any easy way to set a fd different then stderr for debugging output though, maybe someone can help? By stderr redirection, if you really want to (for example, when the reproducer is only on one machine) ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 1:00 PM, Christophe Fergeau cferg...@redhat.com wrote: For real bugs in the code that's true. However, this work only starts once you've ruled out user-related issues, bad system configuration, network issues, ... and for this kind of issues, logging is much more helpful than a backtrace. There is very few if no logging for the UI in virt-viewer atm. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 1:00 PM, Yonit Halperin yhalp...@redhat.com wrote: The caller of virt-viewer/spice-gtk can redirect logging to files. By experience, I'd say this is the right solution, as it avoid filling disk or getting complicated logging (it's not difficult to get several megabytes in several files...) There is no need to dump everything. For this aim we should use log levels, which should be configurable via a configuration file or something similar. I would rather use an environment variable in this case. It's much more flexible, and you don't risk to ruin user configuration everytime you install a new version (I have seen this problem recently tackled, but the tarball will still overwrite it for example...) I beg to differ you. From my experience, spice client logs are very helpful. With the minimal information spice-client log holds, we could help many users. Sometimes you cannot reproduce problems at your own environment, and you can't ask the user to use backtrace. That would hold with standard redirection. Why? Who is used to spicec.log? there isn't such thing anymore, and it hasn't been specified what is spicec.log. Well, there used to be such thing for a while, and we did use it. QE also knows about it... But it's completely gone, now logging is completely different. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 01:05:17PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 1:00 PM, Christophe Fergeau cferg...@redhat.com wrote: For real bugs in the code that's true. However, this work only starts once you've ruled out user-related issues, bad system configuration, network issues, ... and for this kind of issues, logging is much more helpful than a backtrace. There is very few if no logging for the UI in virt-viewer atm. Good idea. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
Hi On Thu, Mar 15, 2012 at 1:00 PM, Alon Levy al...@redhat.com wrote: What do you mean by default? There are very good reasons why logging files aren't used, not even by default. There are tons of things Can you give examples? libvirt produces logging files for qemu and itself, for example. system daemon have proper logging. And I use logger to redirect virt-viewer to syslog, which is much more convenient than a file filling my limited $HOME SSD.. Also by default, it's filling ~/.xsession-errors, which very nicely fills up my disk, as of today:!!! I am going to disable that. -rw---. 1 elmarco elmarco 1,2G mar 15 13:10 /home/elmarco/.xsession-errors missing anyway, typically how/where/who compiled the project, the gazillions of depedencies information and their own logging etc.. We support RHEL, we know what depoendencies went into producing the executable (same for any other distro really). If we aim for a RHEL-only solution, I would use the spice-xpi-client scripts to do redirection, I already proposed that. spice-gtk/remote-viewer probably account for 0.01% of the code that is actually run.. If we want Spice domain logging, then we should dump the traffic, at least we would be able to reproduce something eventually.. That's a straw man. I'm not suggesting to capture the traffic, I concede that there is such a thing as too much logging. But a default suitable level of INFO (that's why we have the DEBUG level in the first place) would work, and is what spicec has been doing. That's vague but a suitable level imho is more like warning/critical: things that shouldn't happen normally. And in the end, 99% of the bugs are solved with: backtrace + reproducer. Not logging. I agree we prefer a reproducer + backtrace. But it isn't an argument for dumping the log file. Also, I'm not sure about your 99% statistic. It's mostly useless and harmful, that's an argument . By stderr redirection, if you really want to (for example, when the reproducer is only on one machine) We could have spice-xpi redirect the output to a file, akin to libvirt redirecting qemu output. ack for rhel -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 01:13:23PM +0100, Marc-André Lureau wrote: It's mostly useless and harmful, that's an argument . It's useless *to you*, I think there has been several people who said they had a use for it... Christophe pgpQICCw4PmNE.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 1:23 PM, Christophe Fergeau cferg...@redhat.com wrote: It's useless *to you*, I think there has been several people who said they had a use for it... I said mostly. If it wasn't useful at all, I don't think we would have the discussion, I wouldn't have enabled it by default in the spice-xpi-client-* scripts, and I wouldn't propose a solution, or I wouldn't have added logging at all etc.. And it's not only me, I haven't seen bugs solved only with automated logging. Backtrace and/or reproducer is what it takes most of the time. From there we can actually use various debugging technics, including logging (very often you actually need more/different than what was there to figure out). -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 01:40:00PM +0100, Marc-André Lureau wrote: And it's not only me, I haven't seen bugs solved only with automated logging. Backtrace and/or reproducer is what it takes most of the time. From there we can actually use various debugging technics, including logging (very often you actually need more/different than what was there to figure out). Once again, I'm not saying logging will help fixing a real bug. However, for bugs we can't reproduce, you often see I can't reproduce, can you attach spicec.log? Oh, I see XXX in the logs, did you do before the bug occurred?, and then you get a reproducer, or you can explain the reporter what he did wrong. Christophe pgpZBf4EmIgml.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 1:55 PM, Christophe Fergeau cferg...@redhat.com wrote: Once again, I'm not saying logging will help fixing a real bug. However, for bugs we can't reproduce, you often see I can't reproduce, can you attach spicec.log? Oh, I see XXX in the logs, did you do before the bug occurred?, and then you get a reproducer, or you can explain the reporter what he did wrong. It seems we agree that logging is useful, and that logging to file by default is harmful (and mostly useless), given that warning/critical are logged by the system. (which makes sense, since they shouldn't happen) -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 01:59:41PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 1:55 PM, Christophe Fergeau cferg...@redhat.com wrote: Once again, I'm not saying logging will help fixing a real bug. However, for bugs we can't reproduce, you often see I can't reproduce, can you attach spicec.log? Oh, I see XXX in the logs, did you do before the bug occurred?, and then you get a reproducer, or you can explain the reporter what he did wrong. It seems we agree that logging is useful, and that logging to file by Yes.. default is harmful (and mostly useless), given that warning/critical are logged by the system. (which makes sense, since they shouldn't happen) But No, logging to syslog works fine for linux, but even there a lot of programs produce their own log files. You can put the log file on a tmpfs (i.e. /tmp, or /var/tmp, or the new /run/something) to solve the problem of choking the filesystem. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 01:59:41PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 1:55 PM, Christophe Fergeau cferg...@redhat.com wrote: Once again, I'm not saying logging will help fixing a real bug. However, for bugs we can't reproduce, you often see I can't reproduce, can you attach spicec.log? Oh, I see XXX in the logs, did you do before the bug occurred?, and then you get a reproducer, or you can explain the reporter what he did wrong. It seems we agree that logging is useful, Probably and that logging to file by default is harmful (and mostly useless) I don't think I've said anything about the (non-)harmfulness of logging by default... Christophe pgp9n2MWk8r4J.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 2:14 PM, Alon Levy al...@redhat.com wrote: But No, logging to syslog works fine for linux, but even there a lot of programs produce their own log files. You can put the log file on a Which program produce its own log file on the desktop? tmpfs (i.e. /tmp, or /var/tmp, or the new /run/something) to solve the problem of choking the filesystem. That would still be harmful. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 02:20:33PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 2:14 PM, Alon Levy al...@redhat.com wrote: But No, logging to syslog works fine for linux, but even there a lot of programs produce their own log files. You can put the log file on a Which program produce its own log file on the desktop? On windows side of things. From my home dir: locate -r ^$HOME/\..*log /home/alon/.cache/shotwell/shotwell.log /home/alon/.cache/telepathy/logger /home/alon/.cache/telepathy/logger/sqlite-data /home/alon/.cache/tracker/ontologies.gvdb /home/alon/.cache/zeitgeist/daemon.log /home/alon/.config/MonoDevelop/log /home/alon/.config/autokey/autokey.log /home/alon/.config/google-googletalkplugin/gtbplugin.log /home/alon/.config/inkscape/extension-errors.log /home/alon/.config/ipython/profile_default/log /home/alon/.config/libreoffice/3/user/uno_packages/cache/log.txt /home/alon/.virt-manager/virt-manager.log /home/alon/.virtinst/virt-install.log /home/alon/.wine/winetricks.log /home/alon/.spicec/spicec.log /home/alon/.pytrainer/log.out /home/alon/.steelstorm/gamedata/ddstexturefailures.log And that's just searching for *.log, I'm sure I missed some. tmpfs (i.e. /tmp, or /var/tmp, or the new /run/something) to solve the problem of choking the filesystem. That would still be harmful. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 03:36:38PM +0200, Alon Levy wrote: On Thu, Mar 15, 2012 at 02:20:33PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 2:14 PM, Alon Levy al...@redhat.com wrote: But No, logging to syslog works fine for linux, but even there a lot of programs produce their own log files. You can put the log file on a Which program produce its own log file on the desktop? On windows side of things. From my home dir: s/On windows side of things// sorry. locate -r ^$HOME/\..*log /home/alon/.cache/shotwell/shotwell.log /home/alon/.cache/telepathy/logger /home/alon/.cache/telepathy/logger/sqlite-data /home/alon/.cache/tracker/ontologies.gvdb /home/alon/.cache/zeitgeist/daemon.log /home/alon/.config/MonoDevelop/log /home/alon/.config/autokey/autokey.log /home/alon/.config/google-googletalkplugin/gtbplugin.log /home/alon/.config/inkscape/extension-errors.log /home/alon/.config/ipython/profile_default/log /home/alon/.config/libreoffice/3/user/uno_packages/cache/log.txt /home/alon/.virt-manager/virt-manager.log /home/alon/.virtinst/virt-install.log /home/alon/.wine/winetricks.log /home/alon/.spicec/spicec.log /home/alon/.pytrainer/log.out /home/alon/.steelstorm/gamedata/ddstexturefailures.log And that's just searching for *.log, I'm sure I missed some. tmpfs (i.e. /tmp, or /var/tmp, or the new /run/something) to solve the problem of choking the filesystem. That would still be harmful. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 2:36 PM, Alon Levy al...@redhat.com wrote: /home/alon/.cache/shotwell/shotwell.log I have this one too, it's overwritten after each run. /home/alon/.cache/telepathy/logger /home/alon/.cache/telepathy/logger/sqlite-data /home/alon/.cache/tracker/ontologies.gvdb false positive /home/alon/.cache/zeitgeist/daemon.log I wonder at what level they actually log, during startup, and if they overwrite it each run. /home/alon/.config/MonoDevelop/log The log output is also logged to files and/or the terminal, though the location of this information depends on the platform and on how MonoDevelop is run. /home/alon/.config/autokey/autokey.log /home/alon/.config/google-googletalkplugin/gtbplugin.log /home/alon/.config/inkscape/extension-errors.log /home/alon/.config/ipython/profile_default/log /home/alon/.config/libreoffice/3/user/uno_packages/cache/log.txt ah, logging in config directory.. I don't have any of these except extension-errors.log, although I run all your programs except autokey. /home/alon/.wine/winetricks.log /home/alon/.pytrainer/log.out /home/alon/.steelstorm/gamedata/ddstexturefailures.log I am not sure we should care about those 3 as being representative of desktop logging. /home/alon/.virt-manager/virt-manager.log /home/alon/.virtinst/virt-install.log /home/alon/.spicec/spicec.log I would file some bugs. Hopefully they are short-lived, and overwritten files. And that's just searching for *.log, I'm sure I missed some. I don't think so. To me you just proved my point, ymmv -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 2:36 PM, Alon Levy al...@redhat.com wrote: /home/alon/.cache/zeitgeist/daemon.log btw, this is very scary if you know that zeitgeist basically watch everything you do. This should definetly be turned off by default. -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 02:59:30PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 2:36 PM, Alon Levy al...@redhat.com wrote: /home/alon/.cache/shotwell/shotwell.log I have this one too, it's overwritten after each run. /home/alon/.cache/telepathy/logger /home/alon/.cache/telepathy/logger/sqlite-data /home/alon/.cache/tracker/ontologies.gvdb false positive Tracker puts some logs in .local.share/tracker. Christophe pgp7ojK2BqFRu.pgp Description: PGP signature ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
Re: [Spice-devel] log file for spice-gtk
On Thu, Mar 15, 2012 at 02:59:30PM +0100, Marc-André Lureau wrote: On Thu, Mar 15, 2012 at 2:36 PM, Alon Levy al...@redhat.com wrote: /home/alon/.cache/shotwell/shotwell.log I have this one too, it's overwritten after each run. /home/alon/.cache/telepathy/logger /home/alon/.cache/telepathy/logger/sqlite-data /home/alon/.cache/tracker/ontologies.gvdb false positive Right, my bad. /home/alon/.cache/zeitgeist/daemon.log I wonder at what level they actually log, during startup, and if they overwrite it each run. It's a log. It contains lines with number (I presume process id), date, type (DEBUG mostly, some INFO), namespace (zeitgeist.storagemonitor, .engine etc.) dash, and log message. 1. /home/alon/.config/MonoDevelop/log The log output is also logged to files and/or the terminal, though the location of this information depends on the platform and on how MonoDevelop is run. Which still leaves it as a log. 2. /home/alon/.config/autokey/autokey.log /home/alon/.config/google-googletalkplugin/gtbplugin.log /home/alon/.config/inkscape/extension-errors.log /home/alon/.config/ipython/profile_default/log /home/alon/.config/libreoffice/3/user/uno_packages/cache/log.txt ah, logging in config directory.. Is that a problem? ipython didn't actually contain anything, so let's ignore that. The rest are non empty log files containing logs: 3,4,5,6. I don't have any of these except extension-errors.log, although I run all your programs except autokey. /home/alon/.wine/winetricks.log /home/alon/.pytrainer/log.out /home/alon/.steelstorm/gamedata/ddstexturefailures.log I am not sure we should care about those 3 as being representative of desktop logging. Ok, what is your criteria for being representative? Otherwise, 7, 8, 9. /home/alon/.virt-manager/virt-manager.log /home/alon/.virtinst/virt-install.log /home/alon/.spicec/spicec.log I would file some bugs. Hopefully they are short-lived, and overwritten files. spicec was just a blast from the past. The other two - you would file bugs because *you* think it's a problem. Fair enough. But still, 10, 11. And that's just searching for *.log, I'm sure I missed some. I don't think so. To me you just proved my point, ymmv By showing 11 programs that use log files that are not syslog I've proved your point? Nice talking to you :) -- Marc-André Lureau ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel ___ Spice-devel mailing list Spice-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/spice-devel
