1 |
On Tue, 27 Oct 2020 15:31:22 +0000 |
2 |
Michael <confabulate@××××××××.com> wrote: |
3 |
|
4 |
> loginctl should look into the directory '/run/systemd/sessions/' |
5 |
|
6 |
> # ls -la /run/systemd/sessions/ |
7 |
> total 8 |
8 |
> drwxr-xr-x 2 root root 120 Oct 27 12:31 . |
9 |
> drwxr-xr-x 7 root root 140 Oct 27 12:11 .. |
10 |
> -rw-r--r-- 1 root root 276 Oct 27 12:31 2 |
11 |
|
12 |
Hmmm... |
13 |
|
14 |
# ls -al /run/systemd/sessions/ |
15 |
total 0 |
16 |
drwxr-xr-x 2 root root 40 Nov 19 11:57 . |
17 |
drwxr-xr-x 6 root root 120 Nov 19 11:57 .. |
18 |
|
19 |
i.e., nada. |
20 |
|
21 |
$ ps aux | grep login; |
22 |
|
23 |
root 22153 0.0 0.0 3680 2260 ? S 11:57 0:00 elogind-daemon |
24 |
|
25 |
i.e., elogin is out there, just not creating the session data? |
26 |
|
27 |
I don't use a graphical login, just command line. Don't know if |
28 |
that makes a difference. |
29 |
|
30 |
I've noticed that booting a runtime system w/ systemd & graphical |
31 |
login has no problems logging me in; running xinit from the command |
32 |
line is where I run into tty permission issues. That may be a symptom |
33 |
of something not right here also. |
34 |
|
35 |
> I don't know of any documentation to point you towards. It could be |
36 |
> a permissions problem, in the first instance I would start with |
37 |
> /run/systemd/ sessions/ which should be owned by root. |
38 |
> |
39 |
> PS. If you converted your system to run with elogind recently, did |
40 |
> you set up the requisite USE flag and re-emerged @world with |
41 |
> '--newuse'? |
42 |
|
43 |
$ grep login /etc/portage/make.conf; |
44 |
|
45 |
USE="... elogind -consolekit -systemd"; |
46 |
|
47 |
After that I simply did an "emerge @world" (gcc had been updated, |
48 |
etc, seemed like a nice time to sync it all up). |
49 |
|
50 |
At this point I no longer can due to python issues, but the world |
51 |
we re-emerged at that time. |
52 |
|
53 |
-- |
54 |
Steven Lembark |
55 |
Workhorse Computing |
56 |
lembark@×××××××.com |
57 |
+1 888 359 3508 |