| Summary: | 4_a2: no journal file created for user | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bittwister2 |
| Version: | Cauldron | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemd-206-8.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Manuel Hiebel
2013-09-18 11:54:18 CEST
Keywords:
(none) =>
Triaged I'm not 100% sure I'd expect a journal file to be created for the user in this case. I mean, what process is actually logging output when taking those actions? Did it work in previous versions? I'll ask upstream, but without something actively logging to the user's journal, I'm not sure I'd expect one to be created. (In reply to Colin Guthrie from comment #1) > I'm not 100% sure I'd expect a journal file to be created for the user in > this case. I would have at least expected something like $ journalctl --no-pager -- Logs begin at Wed 2013-09-18 04:59:00 CDT, end at Wed 2013-09-18 04:59:00 CDT. -- Maybe it a side effect of systemd[5262]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted (In reply to Bit Twister from comment #2) > Maybe it a side effect of > systemd[5262]: Failed at step PAM spawning /usr/lib/systemd/systemd: > Operation not permitted Yeah it could very well be. Certainly, the systemd --user process would be one of the primary consumers of user journals (hooking up stderr to the journal by default for started sessions). But that said, our current use of systemd --user is very minimal. I have systemd 207 to push at some point but I'm getting delays with my GPT layout at boot so want to solve that first. (In reply to Colin Guthrie from comment #3) > I have systemd 207 to push at some point Yes, was wondering/thinking that it should be rolled out before alpha3 iso release would be better that in alpha3 and maybe fix two of my systemd bugs. > but I'm getting delays with my GPT layout at boot so want to solve that first. Guessing it is that /boot partition "Feature" :( I wiped all my systems, set GPT partitions on 6 drives, reinstalled Magia3 then a week or so later I read about separate /boot partitions in the near future. :-(
Bit Twister
2014-01-18 16:31:37 CET
CC:
(none) =>
junknospam Hiya. Sorry for the delay on this one. I don't think it's a bug (as mentioned above) in the current setup, so will close for now - hope that's OK. Oh and as I'm sure you know the separate /boot thing was (and still is) my prefences, and I'm sure even if we did only do this in our installer we'd still have to find a way to keep existing systemd (i.e. upgrades) working. Gah, meant to close with the above comment. Status:
NEW =>
RESOLVED |
Description of problem: no journal file created for user when logging in via su - user or ssh user@$(hostname --alias) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Clean install of Mageia-4-alpha2-x86_64-DVD.iso. Default runlevel: 3 Package Group Selection screen has all package groups selected except Other Graphical Desktops. non-free and tainted media are enabled. Followed with: remove-unused-packages urpmi --downloader wget --auto --auto-update urpme --auto-orphans and reboot. Create some user, say junk log into junk from your user account with su - junk and/or ssh junk@$(hostname --alias) $ ls -al /var/log/journal/$(cat /etc/machine-id) drwxr-xr-x 2 root root 4096 Sep 14 18:43 . drwxr-xr-x 3 root root 4096 Sep 11 08:00 .. -rw-r----- 1 root adm 6680576 Sep 14 18:56 system.journal -rw-r-----+ 1 root root 3764224 Sep 14 18:48 user-1500.journal -rw-r-----+ 1 root root 3760128 Sep 14 11:38 user-1508.journal -rw-r-----+ 1 root root 3768320 Sep 14 18:43 user-1513.journal -rw-r-----+ 1 root root 3739648 Sep 14 09:24 user-1520.journal -rw-r-----+ 1 root root 3747840 Sep 14 18:48 user-501.journal $ id junk uid=500(junk) gid=500(junk) groups=500(junk),81(audio),415(pulse-access),1516(document) Note: there is no user-500.journal Ignore adm group in ls output, and extra groups for junk. Those are my customization changes. A journal file will show up if you run startx after log in. :( Reproducible: Steps to Reproduce: