Re: fedup speed
On Thu, Dec 11, 2014 at 08:05:42AM +0100, drago01 wrote: On Thu, Dec 11, 2014 at 4:37 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Wed, Dec 10, 2014 at 06:51:51PM -0500, Sam Varshavchik wrote: Josh Stone writes: On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 In the meantime, how about adding a blurb to known issues, giving the systemd-fu to flush all logs, before running fedup? I added a blurb: https://fedoraproject.org/wiki/Common_F21_bugs#fedup-journald. I don't think this a very serious issue, but might be annoying in some circumstances. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On Thu, Dec 11, 2014 at 4:27 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Thu, Dec 11, 2014 at 08:05:42AM +0100, drago01 wrote: On Thu, Dec 11, 2014 at 4:37 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Wed, Dec 10, 2014 at 06:51:51PM -0500, Sam Varshavchik wrote: Josh Stone writes: On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 In the meantime, how about adding a blurb to known issues, giving the systemd-fu to flush all logs, before running fedup? I added a blurb: https://fedoraproject.org/wiki/Common_F21_bugs#fedup-journald. I don't think this a very serious issue, but might be annoying in some circumstances. Does not seem like you added anything on this site ... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On 12/11/2014 09:30 AM, drago01 wrote: Does not seem like you added anything on this site ... Caching issue. Refresh the page a few times, or login, and it will show up. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On Thursday, December 11, 2014, Michael Cronenworth m...@cchtml.com wrote: On 12/11/2014 09:30 AM, drago01 wrote: Does not seem like you added anything on this site ... Caching issue. Refresh the page a few times, or login, and it will show up. Ah indeed nm then. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
Josh Stone writes: On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 In the meantime, how about adding a blurb to known issues, giving the systemd-fu to flush all logs, before running fedup? pgpTIFzwp6BoB.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On Wed, Dec 10, 2014 at 06:51:51PM -0500, Sam Varshavchik wrote: Josh Stone writes: On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 In the meantime, how about adding a blurb to known issues, giving the systemd-fu to flush all logs, before running fedup? Is the (almost complete) fix from https://github.com/wgwoods/fedup-dracut/commit/cde5f2d in F20 fedup? If yes, then it wouldn't be necessary to add this to know issues. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup speed
On Thu, Dec 11, 2014 at 4:37 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Wed, Dec 10, 2014 at 06:51:51PM -0500, Sam Varshavchik wrote: Josh Stone writes: On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: 2. at the end, fedup creates a log by running 'journalctl -a -m', which is --all --merge. This seems a bit excessive. On this machine I have 4.5 GB of logs from this machine, plus a few GB more from other sources. journalctl is not very fast (which is another issue), but even if it was, dumping all this is bound to be slow, and not particularly useful. https://bugzilla.redhat.com/show_bug.cgi?id=1161366 In the meantime, how about adding a blurb to known issues, giving the systemd-fu to flush all logs, before running fedup? Is the (almost complete) fix from https://github.com/wgwoods/fedup-dracut/commit/cde5f2d in F20 fedup? No. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
