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
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
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
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
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
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
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
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
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
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,
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.
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
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
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
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
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
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
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,
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
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
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
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
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
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
24 matches
Mail list logo
