[SailfishDevel] journalctl workaround to see console.log
Kalle Jokiniemi
kalle.jokiniemi at jolla.com
Tue Dec 17 08:14:40 UTC 2013
Hi,
On Mon, 2013-12-16 at 22:29 +0200, Kalle Vahlman wrote:
> 2013/12/16 <christopher.lamb at thurweb.ch>:
> > Hi All
> >
> > As reported in a previous thread, the latest SDK release does not spool
> > console.log output to the QtCreator application output. journalctl has been
> > suggested as a workaround.
> >
> > Having experimented with journalctl, Is it possible that console.log output
> > to journalctl either gets lost, or is reported many seconds / minutes later?
> > That seems to be the behaviour I am observing.
>
> If you flood messages, they might be suppressed. There's a limit of
> 200/10s or so. If that happens you should see a message about it in
> the journalctl output.
There are some knobs you can tune in /etc/systemd/journald.conf
Hope it helps.
- Kalle
>
> --
> Porkkalankatu 20, FI-00180 Helsinki
> Tel +358 9 8567 6400
> Fax +358 9 8567 6401
> www.movial.com
> _______________________________________________
> SailfishOS.org Devel mailing list
More information about the Devel
mailing list