{"action":"opened","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/3744","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/3744/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/3744/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/3744/events","html_url":"https://github.com/systemd/systemd/issues/3744","id":165991638,"number":3744,"title":"resource-control doesn't work for user instance","user":{"login":"maxime1986","id":6161102,"avatar_url":"https://avatars.githubusercontent.com/u/6161102?v=3","gravatar_id":"","url":"https://api.github.com/users/maxime1986","html_url":"https://github.com/maxime1986","followers_url":"https://api.github.com/users/maxime1986/followers","following_url":"https://api.github.com/users/maxime1986/following{/other_user}","gists_url":"https://api.github.com/users/maxime1986/gists{/gist_id}","starred_url":"https://api.github.com/users/maxime1986/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maxime1986/subscriptions","organizations_url":"https://api.github.com/users/maxime1986/orgs","repos_url":"https://api.github.com/users/maxime1986/repos","events_url":"https://api.github.com/users/maxime1986/events{/privacy}","received_events_url":"https://api.github.com/users/maxime1986/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-17T19:30:35Z","updated_at":"2016-07-17T19:30:35Z","closed_at":null,"body":"### Submission type\r\n\r\n  - [X] Bug report\r\n\r\n### systemd version the issue has been seen with\r\n\r\nsystemd 230\r\n+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN\r\n\r\n### Used distribution\r\n\r\nArchlinux (update: 17/07/2016)\r\n\r\n### Expected behaviour you didn't see\r\n\r\n```\r\n$ systemd-run --user -p CPUQuota=20% stress -c 1\r\n$ top\r\n…\r\n…  20  …  stress \r\n…\r\n```\r\n\r\n### Unexpected behaviour you saw\r\n\r\n```\r\n$ systemd-run --user -p CPUQuota=10% stress -c 1\r\n$ top\r\n…\r\n…  100  …  stress \r\n…\r\n```\r\n\r\n### Steps to reproduce the problem\r\n\r\nWith cgroup v1 (*not* unified hierarchy).\r\n\r\n```\r\n$ systemd-run --user -p CPUQuota=10% stress -c 1\r\n```\r\n\r\n### remarks\r\n\r\nI don't know if it's normal or not.\r\nOn one side, I read that cgroup can't be created by unprivileged process (same test without `--user` option works great).\r\nOn the other side, I found bug #3500 which make me think it's possible, at least on unified hierarchy. I don't use unified hierarchy:\r\n```\r\n$ cat /proc/cmdline\r\nroot=LABEL=ROOTPART rootfstype=btrfs rootflags=subvol=rootfs rw add_efi_memmap initrd=EFI/arch/initramfs-linux.img\r\n```\r\n\r\nIn case it's not possible, I think it should be mentioned in the systemd.resource-control man page.\r\n\r\nDo you need more information ?\r\nThank you."}}
{"actor":{"display_login":"maxime1986"}}