Am 25.03.2015 um 17:54 schrieb Jameson Graef Rollins: > Package: systemd > Version: 215-12 > Followup-For: Bug #772272 > > I am also experiencing this issue. I have multiple services running > as systemd user services, and I don't have access to the logs of any > of them: > > music@rippy:~ 1$ systemctl --user status mopidy > ● mopidy.service - Mopidy Music Server > Loaded: loaded (/home/music/.config/systemd/user/mopidy.service; enabled) > Active: active (running) since Tue 2015-03-24 22:22:54 PDT; 11h ago > Main PID: 910 (mopidy) > CGroup: /user.slice/user-1001.slice/user@1001.service/mopidy.service > └─910 /usr/bin/python /usr/bin/mopidy > music@rippy:~ 0$ journalctl --user > No journal files were found. > music@rippy:~ 1$ journalctl --user-unit=mopidy.service > No journal files were found. > music@rippy:~ 1$ > > This user is not in the systemd-journal group. However, the > journalctl man page declares that this should not be necessary (from > journalctl(1)): > > All users are granted access to their private per-user > journals. However, by default, only root and users who are members > of the "systemd-journal" group get access to the system journal > and the journals of other users. >
This requires persistent journal with v215 from jessie/sid (see /usr/share/doc/systemd/README.Debian). With v219 from experimental, we do also apply the ACLs to the journal files in /run/journal. Can you test if either of these two works for you? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
