[systemd-devel] CPUQuota setting is not inherited from systemd slices
Hello, I try to limit my CPUQuota for my dnt5411software.slice. But the services in the slice do not inherit the CPUQuota=20% setting from the dnt5411software.slice file. They still consume more then 20% of the CPU. Some clue whats wrong or missconfigured here? I'am using systemd 225 systemd-cgls ├─dnt5411software.slice │ ├─startpingproxy.service │ │ └─699 /dnt/ibis/tools/pingproxy │ ├─startscm.service │ │ └─704 /dnt/ibis/scm │ ├─startstatusproxy.service │ │ └─712 /dnt/ibis/tools/statusproxy │ ├─startuartproxy.service │ │ └─700 /dnt/ibis/tools/uartproxy │ ├─startprocessproxy.service │ │ ├─706 /dnt/ibis/tools/processproxy │ │ ├─722 ./datamgr -scm │ │ ├─723 ./mobmgr -scm │ │ ├─724 ./ethmgr -scm │ │ ├─725 ./modman -scm │ │ ├─727 ./phpconnector -scm │ │ ├─728 ./mcmgr -scm │ │ ├─729 ./smsmgr -scm │ │ ├─730 ./sshmgr -scm │ │ └─731 ./ledmgr -scm │ └─starthalproxy.service │ └─708 /dnt/ibis/tools/halproxy cat /etc/systemd/system/dnt5411software.slice [Unit] Description=Slices Documentation=man:systemd.special(7) Wants=-.slice user.slice After=-.slice user.slice [Slice] CPUAccounting=true MemoryAccounting=true BlockIOAccounting=true #TasksAccounting=true #CPUShares=512 CPUQuota=20% systemctl show startprocessproxy.service | grep "CPUQuota" CPUQuotaPerSecUSec=infinity Best regards, Oliver ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-222 mount issues on CentOS 7
Hi list, I've re-built systemd-222 from Fedora dist-git sources for CentOS 7 (needed for rkt). This is part of the work I'm doing to provide rkt as an rpm for CentOS Virt SIG. The koji build can be found here: http://cbs.centos.org/koji/buildinfo?buildID=12569 On installation and reboot, I notice that systemd will only mount the root dir successfully, while other discrete partitions (/home etc.) will fail to mount. # systemctl status local-fs.target ● local-fs.target - Local File Systems Loaded: loaded (/usr/lib/systemd/system/local-fs.target; static; vendor preset: enabled) Active: inactive (dead) since Mon 2016-09-19 09:57:51 EDT; 1 weeks 1 days ago Docs: man:systemd.special(7) Sep 19 09:57:51 minato systemd[1]: Stopped target Local File Systems. Sep 19 09:57:51 minato systemd[1]: Stopping Local File Systems. Sep 19 09:59:24 minato systemd[1]: Dependency failed for Local File Systems. Sep 19 09:59:24 minato systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Sep 19 09:59:24 minato systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. Now, I can mount these partitions with: # lvm vgchange -ay but this still doesn't automount succesfully on a reboot. Did I miss something here? Thanks, -- Lokesh Freenode: lsm5 GPG: 0xC7C3A0DD https://keybase.io/lsm5 signature.asc Description: PGP signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - cleaning of /var/run/
Hello, Am 27.09.2016 um 12:25 schrieb Reindl Harald: Am 27.09.2016 um 12:22 schrieb Hajo Locke: When restarting mysql, then folder /var/run/mysqld is deleted and recreated. Result is that every mounted folder is loosing his content, because "mount --bind" does not find its source any more. then don't use RunTimeDirectory in your mysqld-unit instead /etc/tmpfiles.d which would create the folder at boot thanks, that seems to work. systemd just does what you told it thats true, but i did not realize what i told ;) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel Thanks, Hajo ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - cleaning of /var/run/
Am 27.09.2016 um 12:22 schrieb Hajo Locke: When restarting mysql, then folder /var/run/mysqld is deleted and recreated. Result is that every mounted folder is loosing his content, because "mount --bind" does not find its source any more. then don't use RunTimeDirectory in your mysqld-unit instead /etc/tmpfiles.d which would create the folder at boot systemd just does what you told it ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Is it possible to load unit files from paths other than default paths ?
Am Tue, 27 Sep 2016 06:33:40 +0300 schrieb Andrei Borzenkov: > 27.09.2016 05:10, Kai Krakow пишет: > > Am Mon, 26 Sep 2016 14:30:37 +0530 > > schrieb "Raghavendra. H. R" : > > > >> Andrei, > >> > >> How to set SYSTEMD_UNIT_PATH in Systemd ? > > > > Maybe try "systemctl set-environment"? You may need to run > > "systemctl daemon-reload" after this for the new unit files to pick > > up. > > No, that does not work. It was already discussed previously. This is > environment for services that are started by systemd, while you need > to set it before starting systemd. This is challenging for something > that runs as the very first process ever ... :) If that stuff needs to run so isolated, one could try packaging it as an nspawn container... -- Regards, Kai Replies to list-only preferred. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel