ppc64el ubuntu-server ISO does not install libpam-systemd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Seeds |
Fix Released
|
Critical
|
Unassigned | ||
ubuntu-meta (Ubuntu) |
Fix Released
|
Critical
|
Martin Pitt |
Bug Description
On Ubuntu 16.04/ppc64el, the cgroup for a user session (bash) inherits from a sshd.service, when the user logs into the machine using SSH.
This causes the amount of process to be limited by /etc/systemd/
This does not seem to happen on amd64. This is a cgroup tree diff:
On x64, bash (in this case, PID 19405 ) spawned by sshd belongs to CGROUP session-
└─user.slice
├─user-1000.slice
│ ├─session-1.scope
│ │ ├─634 sshd: brenohl [priv]
│ │ ├─660 sshd: brenohl@pts/0
│ │ └─661 -bash
│ └─user@1000.service
│ ├─636 /lib/systemd/
│ └─637 (sd-pam)
└─user-1003.slice
├─session-
│ ├─19379 sshd: gromero [priv]
│ ├─19404 sshd: gromero@pts/1
│ ├─19405 -bash
However, in ppc64le, bash (in this case, PID 1913), spawned by sshd belongs to CGROUP ssh.service-
-.slice
├─1720 /sbin/cgmanager -m name=systemd
├─init.scope
└─system.slice
├─dbus.service
│ └─1699 /usr/bin/
├─cron.service
│ └─1702 /usr/sbin/cron -f
├─<email address hidden>
│ └─1833 /sbin/dhclient
├─accounts-
│ └─1717 /usr/lib/
├─system-
│ └─<email address hidden>
│ └─1875 /sbin/agetty --keep-baud 115200 38400 9600 hvc0 vt220
├─systemd-
│ └─1382 /lib/systemd/
├─systemd-
│ └─1639 /lib/systemd/
├─ssh.service
│ ├─1863 /usr/sbin/sshd -D
│ ├─1897 sshd: gromero [priv]
│ ├─1912 sshd: gromero@pts/0
│ ├─1913 -bash
Having the user session associated with the systemd cgroups (/system.
Gustavo Romero has more details about this problem, and will comment soon.
Changed in systemd (Ubuntu): | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
status: | New → Confirmed |
affects: | baltix → ubuntu-rtm |
Changed in ubuntu-rtm: | |
importance: | Undecided → Critical |
status: | New → Fix Released |
affects: | ubuntu-rtm → ubuntu-seeds |
Using this Makefile with "make -j500" will trigger the problematic behavior described in this bug.