[systemd-devel] Missing previous boot system journal

[Yun-Chih Chen]

I'm serious.  It was run as root; but just as requested.

$ journalctl -n5
Journal file
/var/log/journal/65f854e19e1d43049c5e058f1f93648f/user-4994.journal is
truncated, ignoring file.
-- Logs begin at Fri 2016-02-05 00:16:50 CST, end at Wed 2016-11-23
19:38:16 CST. --
Nov 23 19:38:01 server CROND[18450]: (b02902009) CMD (~/bin/iframe.sh)
Nov 23 19:38:01 server CROND[18444]: pam_unix(crond:session): session
closed for user b02902009
Nov 23 19:38:01 server CROND[18443]: pam_unix(crond:session): session
closed for user b01902090
Nov 23 19:38:02 server CROND[18442]: pam_unix(crond:session): session
closed for user b04902111
Nov 23 19:38:16 server nscd[930]: 930 checking for monitored file
`/var/db/passwd.db': 沒有此一檔案或目錄
$ id
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),19(log)

On Wed, Nov 23, 2016 at 6:52 PM, Lennart Poettering <lennart at poettering.net>
wrote:

> On Wed, 23.11.16 18:50, Yunchih Chen (yunchih.cat at gmail.com) wrote:
>
> > I am 100% sure it is run as root.
> > Is there other debug info I can provide?  Thanks for your help.
>
> Just run your journalctl commands as root again? The "id" command lets
> you know your user identity...
>
>
> Lennart
>
> --
> Lennart Poettering, Red Hat
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20161123/832fc908/attachment-0001.html>