1 |
On Tuesday, 27 October 2020 14:23:11 GMT Steven Lembark wrote: |
2 |
> One more elogind update question: |
3 |
> |
4 |
> $ loginctl user-status; |
5 |
> Could not get properties: is a directory |
6 |
> |
7 |
> Q: Anyone have any idea of what item might be a directory? |
8 |
|
9 |
loginctl should look into the directory '/run/systemd/sessions/' which |
10 |
contains pipes and text files. The text files contain info on seats, |
11 |
sessions, users; e.g. |
12 |
|
13 |
# ls -la /run/systemd/sessions/ |
14 |
total 8 |
15 |
drwxr-xr-x 2 root root 120 Oct 27 12:31 . |
16 |
drwxr-xr-x 7 root root 140 Oct 27 12:11 .. |
17 |
-rw-r--r-- 1 root root 276 Oct 27 12:31 2 |
18 |
prw------- 1 root root 0 Oct 27 12:11 2.ref |
19 |
-rw-r--r-- 1 root root 287 Oct 27 12:31 5 |
20 |
prw------- 1 root root 0 Oct 27 12:28 5.ref |
21 |
|
22 |
|
23 |
> strace doesn't show me anything obvious (which doesn't always |
24 |
> mean anything). |
25 |
> |
26 |
> <https://pastebin.com/78F14s8P> |
27 |
> |
28 |
> Q: Is there any documentation anyone knows about that describes |
29 |
> this error? |
30 |
> |
31 |
> Thanks |
32 |
|
33 |
I don't know of any documentation to point you towards. It could be a |
34 |
permissions problem, in the first instance I would start with /run/systemd/ |
35 |
sessions/ which should be owned by root. |
36 |
|
37 |
PS. If you converted your system to run with elogind recently, did you set up |
38 |
the requisite USE flag and re-emerged @world with '--newuse'? |