* Carlos E. R. [11-03-15 07:58]:

On 2015-11-03 12:05, ianseeks wrote:

...

I can't get any joy out of journalctl --user (result is "No journal files were found. -- No entries --") so i have to use "journalctl _UID=1001" to get any logs for my user. I am sure this didn't used to be the case but my memory is crap.

13.1 has the same behaviour. I just tried.

"journalctl --user" provides logs as expected on Tw...., at least on my five boxes. On my 13.1 server there are no journal log files, no journal directory below /var/log/. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tuesday 03 Nov 2015 14:53:51 Carlos E. R. wrote:

On 2015-11-03 14:48, Patrick Shanahan wrote:

...

...

13.1 has the same behaviour. I just tried.

"journalctl --user" provides logs as expected on Tw...., at least on my five boxes. On my 13.1 server there are no journal log files, no journal directory below /var/log/.

Not exactly. 13.1 has no persistent systemd journal by default (you can activate it), but it does keep a log for the current session. Thus, "journalctl _UID=1000" produces 622 lines in my 13.1 main system.

should that matter if its persistent or not?

And they are stored on disk, anyhow:

Telcontar:~ # journalctl --disk-usage Journals take up 53.6M on disk. Telcontar:~ # Telcontar:~ # ls /var/log/jo* ls: cannot access /var/log/jo*: No such file or directory Telcontar:~ # I've just done " journalctl --disk-usage " as a normal user and got "No journal files were found. Archived and active journals take up 0B on disk."

but as "su" i got "Archived and active journals take up 16.0M on disk." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tuesday 03 Nov 2015 11:00:35 Cristian Rodríguez wrote:

On Tue, Nov 3, 2015 at 8:05 AM, ianseeks wrote:

...

Hi

Does anyone know where the best place is to ask questions about Tumbleweeds current default config where the thread will no get gummed up with personal opinions about this system? I will try here as a start.

I can't get any joy out of journalctl --user (result is "No journal files were found. -- No entries --") so i have to use "journalctl _UID=1001" to get any logs for my user. I am sure this didn't used to be the case but my memory is crap.

There is no user journal if persistent storage is disabled ( if /var/log/journal does not exists)

doesn't that only mean that the journal thrown away on shutdown but still exists whilst the machine is on?

...

I'm getting the following in the journal at logout of a user. Is the "systemd-coredump" important?

Yes. kactivitymanager crashed, you will be able to obtain a backtrace for debugging once you install the needed debuginfo packages and run coredumpctl gdb ...

thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Nov 3, 2015 at 11:57 AM, ianseeks wrote:

...

On Tuesday 03 Nov 2015 11:00:35 Cristian Rodríguez wrote:

...

On Tue, Nov 3, 2015 at 8:05 AM, ianseeks wrote:

...

Hi

Does anyone know where the best place is to ask questions about Tumbleweeds current default config where the thread will no get gummed up with personal opinions about this system? I will try here as a start.

I can't get any joy out of journalctl --user (result is "No journal files were found. -- No entries --") so i have to use "journalctl _UID=1001" to get any logs for my user. I am sure this didn't used to be the case but my memory is crap.

There is no user journal if persistent storage is disabled ( if /var/log/journal does not exists)

doesn't that only mean that the journal thrown away on shutdown but still exists whilst the machine is on?

No.it also means that the --user journal is not created at all. only a single, system-wide memory backed (tmpfs) journal is available for all users.

On Tuesday 03 Nov 2015 14:52:00 Cristian Rodríguez wrote: thanks for the explanation so as i understand --user is a separate journal file with only the users data. i thought "journalctl _UID=1001" and "journalctl --user" were almost identical options for getting info out of the journal. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tuesday 03 Nov 2015 21:22:46 Andrei Borzenkov wrote:

03.11.2015 21:00, ianseeks пишет:

...

i thought "journalctl _UID=1001" and "journalctl --user" were almost identical options for getting info out of the journal.

According to journalctl manual, --user shows "service of current user" but as of now "user services" are basically non-existent and unused. So depending on interpretation of "service of current user" it may indeed be very different from UID==1001 which simply means - logs of any process that run as user 1001.

in my mind --user was the current user and because i got nothing from the journal using that option, i resorted to _uid= -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org