Re: [systemd-devel] systemd[725]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted

2013-07-08 Thread Kok, Auke-jan H 
On Sat, Jul 6, 2013 at 1:40 AM, Marc-Antoine Perennou
marc-anto...@perennou.com wrote:
 The patch I mailed a few hours ago about chowning cgroups solved this issue
 here.

but it's not a permanent solution - only a workaround. I believe from
the release notes that systemd --user shouldn't maintain the cgroups
itself anymore directly and instead delegate to systemd-run(?).

Auke
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd[725]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted

2013-07-06 Thread Marc-Antoine Perennou 
The patch I mailed a few hours ago about chowning cgroups solved this issue
here.


On 6 July 2013 05:57, Kok, Auke-jan H auke-jan.h@intel.com wrote:

 On Thu, Jul 4, 2013 at 6:30 PM, Kay Sievers k...@vrfy.org wrote:
  On Fri, Jul 5, 2013 at 2:35 AM, Cristian Rodríguez
  crrodrig...@opensuse.org wrote:
  Since systemd 205, Im getting this scary warning
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting
  user-1000.slice.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Created slice
  user-1000.slice.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting User
  Manager for 1000...
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Starting
 Session 1
  of user crrodriguez.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd-logind[423]: New
  session 1 of user crrodriguez.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd-logind[423]:
 Linked
  /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[1]: Started
 Session 1
  of user crrodriguez.
 
  Jul 04 19:55:36 xps9000.cristianrodriguez.net systemd[725]: Failed at
 step
  PAM spawning /usr/lib/systemd/systemd: Operation not permitted
 
  We are just not there, systemd --user is not started at the moment,
  the cgroup sub-tree for the user's session is not accessible for the
  systemd --user process running under the user's uid.
 
  Nothing really to worry about, the message should be ignored for now,
  we will get there soon ...

 does the old method of manually starting user@.service at least still
 work? I haven't had any time to track the latest release yet...

 Auke
 ___
 systemd-devel mailing list
 systemd-devel@lists.freedesktop.org
 http://lists.freedesktop.org/mailman/listinfo/systemd-devel

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel