Hello,
Danny Milosavljevic scribes:
> We don't refer to pam_loginuid.so anywhere, so it's understandable that
> /proc/self/loginuid is not set either.
I proceeded as discussed:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=e6b1a2248ff164e14d1b2f495224faf8a8326142
https://git.sava
Hi Bruno!
Bruno Haible skribis:
> Danny Milosavljevic wrote:
>> Are you logging in using gdm?
>
> I'm using the guix-1.0 installation image
> (guix-system-vm-image-1.0.0.x86_64-linux). It shows a screen "Logging in..."
> for less than one second and then starts the user's desktop immediately.
T
Danny Milosavljevic wrote:
> Are you logging in using gdm?
I'm using the guix-1.0 installation image
(guix-system-vm-image-1.0.0.x86_64-linux). It shows a screen "Logging in..."
for less than one second and then starts the user's desktop immediately.
Bruno
http://man7.org/linux/man-pages/man8/pam_loginuid.8.html suggests that we should
use that for all "entry point"s for the user. I guess we can add it.
Are you logging in using gdm?
We don't refer to pam_loginuid.so anywhere, so it's understandable that
/proc/self/loginuid is not set either.
Appa
Hi,
Running the guix-1.0 installation image
(guix-system-vm-image-1.0.0.x86_64-linux) in qemu, I find that the
glibc functions getlogin() and getlogin_r() fail with error ENXIO.
Using the gnulib programs test-getlogin and test-getlogin_r I can see
that the program is reading the contents of the f
