Re: [systemd-devel] Errorneous detection of degraded array

31.01.2017 01:19, NeilBrown пишет: > On Mon, Jan 30 2017, Andrei Borzenkov wrote: > >> On Mon, Jan 30, 2017 at 9:36 AM, NeilBrown wrote: >> ... >>> >>> systemd[1]: Created slice system-mdadm\x2dlast\x2dresort.slice. >>> systemd[1]: Starting

[systemd-devel] UMask attribute in service file

Hello list, I'am using the UMask attribute in my service file to define my umask setting to 0027. In this service file I start a little c program which uses fopen() to open a file. the file permissions are rw-rw-rw (0666) instead of rw-r--- (0640) Is this a expected behavior? some further

Re: [systemd-devel] nspawn --overlay and --read-only

> > $ systemd-nspawn --directory=/os --read-only > --overlay=/os/home/foobar:/tmp/home/foobar:/home/foobar > --user=foobar > > I expect the user foobar to be able to write in /home/foobar (in the > container) but instead I get a Permission denied. > Sorry all, I was not properly managing the

[systemd-devel] .device not creating in systemd

Hi all, Previously i used systemd version 206 and kernel version 3.10.17. Now I updated kernel version to 4.1.15 and systemd version to 229. I'm using yocto for build. I was mounting few devices from systemd using .mount service file. In that I'm using requires and wants as .device. After