[systemd-devel] Avoiding creating systemd memory and blkio controllers under /sys/fs/cgroup/memory and /sys/fs/cgroup/blkio.

2016-01-15 Thread Kevin Wilson
Hi everyone, I had a Fedora 20 Machine (x86_64) on which I installed the latest 4.4 kernel released this week (I had built it from source). It had systemd 208. I wanted to test cgroup v2 (not in relation to systemd). In order to be able to activate cgoupv2 memory and cgroup controllers, the cgro

[systemd-devel] How to use systemd-gnome-ask-password-agent?

2016-01-15 Thread Ilya Basin
Hi. I want a graphical password prompt when an entry in /etc/crypttab is activated. I have Archlinux/Xfce Additionally installed xfce4-notifyd. This works: $ sudo systemd-gnome-ask-password-agent I think I can add this to ~/.xprofile, but I guess that's not how it was intended to work.

Re: [systemd-devel] known but not-listed units

2016-01-15 Thread Mikhail Kasimov
15.01.2016 16:30, Simon McVittie пишет: > On 15/01/16 14:13, Mikhail Kasimov wrote: >> ok, let be --systemspace (/usr/lib/systemd/system) --userspace >> (/etc/systemd/system) and --runtimespace (/run/systemd). > > /usr: --vendor? --static? --data? > /etc: --local? --conf? > /run: --runtime (this a

Re: [systemd-devel] known but not-listed units

2016-01-15 Thread Simon McVittie
On 15/01/16 14:13, Mikhail Kasimov wrote: > ok, let be --systemspace (/usr/lib/systemd/system) --userspace > (/etc/systemd/system) and --runtimespace (/run/systemd). /usr: --vendor? --static? --data? /etc: --local? --conf? /run: --runtime (this already exists for some other subcommands) Anything

Re: [systemd-devel] octeon_wdt: WDT device closed unexpectedly

2016-01-15 Thread Aaro Koskinen
On Fri, Jan 15, 2016 at 02:24:22PM +0100, Lennart Poettering wrote: > Some watchdog kernel drivers consider it a problem if we first set up > the watchdog, and then close the device, and warn about it. However, > this is really intended here, and actually explicit part of the kernel > watchdog inte

Re: [systemd-devel] known but not-listed units

2016-01-15 Thread Mikhail Kasimov
That were the first keynames, that came onto mind. :) ok, let be --systemspace (/usr/lib/systemd/system) --userspace (/etc/systemd/system) and --runtimespace (/run/systemd). 15.01.2016 13:13, Colin Guthrie пишет: > Mikhail Kasimov wrote on 14/01/16 15:27: >> 'systemctl list-unit-files --user': to

Re: [systemd-devel] Difference between restart versus stop-start

2016-01-15 Thread Lennart Poettering
On Fri, 15.01.16 03:41, Pathangi Janardhanan (path.j...@gmail.com) wrote: > Hi, > > I am using sd_notify_pid_with_fds and subsequently sd_notify_fds to store > and receive fds from systemd. > > Systemd differentiates between > > systemctl restart -> Where it stops and starts the service, b

Re: [systemd-devel] resolved and bind-mount of /etc/resolv.conf

2016-01-15 Thread Lennart Poettering
On Fri, 15.01.16 10:33, Igor Bukanov (i...@mir2.org) wrote: > Hi, > > currently if one runs systemd-resolved, then /etc/resolv.conf should > be symlinked to /run/systemd/resolve/resolv.conf . Is it possible > instead to add an option for resolved to bind-mount /etc/resolv.conf > into the real f

Re: [systemd-devel] octeon_wdt: WDT device closed unexpectedly

2016-01-15 Thread Lennart Poettering
On Fri, 15.01.16 04:42, Mike Cardillo (mcardill) (mcard...@cisco.com) wrote: > HI all, > > We’re seeing the following warning upon reboot of our machines: octeon_wdt: > WDT device closed unexpectedly > > I believe it’s caused from the following code block in src/core/main.c: > > if (arm_re

Re: [systemd-devel] No maintenance shell on local fs failure (/bin/sh: no such file or directory)

2016-01-15 Thread Andrei Borzenkov
On Fri, Jan 15, 2016 at 1:52 PM, Reindl Harald wrote: > > > Am 15.01.2016 um 11:40 schrieb Frank Steiner: >> >> This didn't mean that /bin/echo was not found, but the CHDIR failed! >> That was caused by /root being a symbolic link to /local/home/root >> (we strictly separate any user data includin

Re: [systemd-devel] known but not-listed units

2016-01-15 Thread Colin Guthrie
Mikhail Kasimov wrote on 14/01/16 15:27: > 'systemctl list-unit-files --user': to display units-files from > /etc/systemd/system dir I wouldn't use --user here as "systemctl --user" has an existing meaning. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic

Re: [systemd-devel] No maintenance shell on local fs failure (/bin/sh: no such file or directory)

2016-01-15 Thread Reindl Harald
Am 15.01.2016 um 11:40 schrieb Frank Steiner: This didn't mean that /bin/echo was not found, but the CHDIR failed! That was caused by /root being a symbolic link to /local/home/root (we strictly separate any user data including root from the system, so that we can reformat / on reinstalling or

Re: [systemd-devel] No maintenance shell on local fs failure (/bin/sh: no such file or directory)

2016-01-15 Thread Frank Steiner
In case someone else steps in this; Frank Steiner wrote > Hi, > > on one of my serves I have a LVM that, due to an error in my lvm.conf, > couldn't be mounted on boot. But I didn't get a maintenance shell as > I usually got on other servers, the output just stopped after complaining > with > [

[systemd-devel] resolved and bind-mount of /etc/resolv.conf

2016-01-15 Thread Igor Bukanov
Hi, currently if one runs systemd-resolved, then /etc/resolv.conf should be symlinked to /run/systemd/resolve/resolv.conf . Is it possible instead to add an option for resolved to bind-mount /etc/resolv.conf into the real file when it starts? This way stopping or disabling resolved will not req

[systemd-devel] Difference between restart versus stop-start

2016-01-15 Thread Pathangi Janardhanan
Hi, I am using sd_notify_pid_with_fds and subsequently sd_notify_fds to store and receive fds from systemd. Systemd differentiates between systemctl restart -> Where it stops and starts the service, but maintains the fd stored above whereas if I do systemctl stop and then start, the fds