Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #205632 > unrolled thread
| Started by | Eduard Bloch <edi@gmx.de> |
|---|---|
| First post | 2019-02-22 08:50 +0100 |
| Last post | 2019-02-22 13:30 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
stracing login process with systemd? Eduard Bloch <edi@gmx.de> - 2019-02-22 08:50 +0100
Re: stracing login process with systemd? Reco <recoverym4n@enotuniq.net> - 2019-02-22 09:20 +0100
Re: stracing login process with systemd? Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2019-02-22 13:30 +0100
| From | Eduard Bloch <edi@gmx.de> |
|---|---|
| Date | 2019-02-22 08:50 +0100 |
| Subject | stracing login process with systemd? |
| Message-ID | <xudKO-8tX-3@gated-at.bofh.it> |
Dear Lazynet, I have some trouble with one desktop system running Sid. After some updates a couple of weeks ago, user programs started to fail, like pulseaudio no longer running or "systemctl suspend" not working. After little investigation I have found out that "systemd --user" process is not working which is supposed to run user-specific services. Which is probably somethign that libpam-systemd should have invoked - that was the best guess I could extract from the documentation (the manpage of systemd is AFAICS NOT telling you who/what is supposed to start the user systemd). I had some exchange with the maintainer in the BTS but so far that's not really fruitful. I would like to just strace the whole login process (console or xdm) and check what's happening there around systemd invocation, and what's failing. Does anyone know how to insert strace or any similar tracing utility? I can imagine that one could try to use kernel tracing here but that would be a huge hammer. Thanks, Eduard. -- Every great idea is worthless without someone to do the work. --Neil Williams
[toc] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-02-22 09:20 +0100 |
| Message-ID | <xuedP-rF-3@gated-at.bofh.it> |
| In reply to | #205632 |
Hi. On Fri, Feb 22, 2019 at 08:22:22AM +0100, Eduard Bloch wrote: > I had some exchange with the maintainer in the BTS but so far that's not > really fruitful. I would like to just strace the whole login process > (console or xdm) and check what's happening there around systemd > invocation, and what's failing. > > Does anyone know how to insert strace or any similar tracing utility? Don't get your hopes high. One of the (mis)features of systemd is to ptrace(2) starting services, thus rendering "I'll just strace/ltrace the thing" classic technique completely useless. > I can imagine that one could try to use kernel tracing here but that > would be a huge hammer. "perf trace" could work for you. Attaching to a getty via gdb could work too, but it'll likely screw the login process. Reco
[toc] | [prev] | [next] | [standalone]
| From | Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> |
|---|---|
| Date | 2019-02-22 13:30 +0100 |
| Message-ID | <xui7L-2Jb-1@gated-at.bofh.it> |
| In reply to | #205632 |
Eduard Bloch: > that was the best guess I could extract from the documentation > Try some StackExchange answers. * https://unix.stackexchange.com/a/477049/5132 * https://unix.stackexchange.com/a/427917/5132 * https://unix.stackexchange.com/a/423648/5132 * https://unix.stackexchange.com/a/441831/5132 * https://unix.stackexchange.com/a/500687/5132
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web