On Sun, 03.04.11 18:01, Albert Strasheim (full...@gmail.com) wrote:
>
> Hello all
>
> On Sun, Apr 3, 2011 at 4:59 PM, Albert Strasheim wrote:
> > pam_loginuid(sshd:session): set_loginuid failed
>
> This one is caused by:
>
> 32open("/proc/self/loginuid", O_WRONLY|O_TRUNC|O_NOFOLLOW) = 4
>
On Sun, 03.04.11 16:59, Albert Strasheim (full...@gmail.com) wrote:
> Hello all
>
> I've been working on a systemd configuration to do integration tests
> with a few services inside a nspawn container.
>
> Among these, I'm trying to get sshd going using the units here as a
> starting point:
>
>
Hello all
On Sun, Apr 3, 2011 at 4:59 PM, Albert Strasheim wrote:
> pam_loginuid(sshd:session): set_loginuid failed
This one is caused by:
32open("/proc/self/loginuid", O_WRONLY|O_TRUNC|O_NOFOLLOW) = 4
32write(4, "0", 1) = -1 EPERM (Operation not permitted)
This happen
Hello all
I've been working on a systemd configuration to do integration tests
with a few services inside a nspawn container.
Among these, I'm trying to get sshd going using the units here as a
starting point:
http://0pointer.de/public/systemd-units/
Unfortunately, it seems the nspawn container
