http://bugzilla.moblin.org/show_bug.cgi?id=5041
--- Comment #10 from pohly <[email protected]> 2010-03-22 00:25:35 PST --- (In reply to comment #9) > > No. We want to *have* that output, not *discard* it ;-) What I referred to > > is > > LogRedirect. Currently we only capture stderr and filter it. As soon as > > none of > > our core code writes to file descriptor 1 anymore, we can also capture that > > descriptor and pass it through our logging infrastructure, exactly like our > > own > > "stdout" output. That way it will be recorded in "syncevolution-log.html", > > if > > it exists, (new and useful feature) in addition to being sent via D-Bus to > > the > > syncevolution D-Bus client. > > got it. for simple 'system' calls, it seems to me it's hard to redirect their > and route them into our logging system. so like you said, we discard them, > right? Once file descriptor 1 of the syncevo-dbus-server is redirected, all other processes spawned from it (including those with system()) will use that pipe. So we don't have to do anything special and we don't need to discard that output. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
