On 12.05.2014 20:53, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 7:44 PM, poma wrote:
>> Why am I seeing this commit on git/stable,
>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/net/bridge/br_netlink.c?id=30313a3
>> but not in stable complete tarball,
>> https:/
Two device Btrfs volume, with one device missing (simulated) will not boot,
even with rootflags=degraded set which is currently required to enable Btrfs
degraded mounts. Upon reaching a dracut shell after basic.target fails with
time out, I can mount -o subvol=root,degraded and exit and continue
Most likely the facility needed is actual connectivity, rather than whether or
not the
network managment daemon is running.
We also need to explicitly pull in the network-online.target, as it is not
active by
default.
This means {systemd-networkd,NetworkManager}-wait-online.service, can be
en
An alternative workaround is to put the socket into a directory that
has the permissions desired. If you can't read the directory, you
can't use a socket in that directory.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.fr
Bumping this for review.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mon, May 12, 2014 at 7:44 PM, poma wrote:
> Why am I seeing this commit on git/stable,
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/net/bridge/br_netlink.c?id=30313a3
> but not in stable complete tarball,
> https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.14
On 05/12/2014 05:45 PM, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 5:27 PM, poma wrote:
>> On 12.05.2014 12:22, Tom Gundersen wrote:
>>> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
>>> wrote:
>>> This should really be added as AFAICT there is currently no way to match
>>> on v
On May 11, 2014, at 1:25 PM, Chris Murphy wrote:
> Fedora Rawhide (systemd-212) vs Fedora 20 (systemd-209) and a Btrfs degraded
> boot.
>
> With Fedora 20, at basic.target, I get the cylon eye "A start job is runing
> for dev-disk-by….." which eventually fails and I get a dracut prompt, and a
On Sat, 10.05.14 15:13, Daniel Buch (boogiewasth...@gmail.com) wrote:
> Hi,
>
> I just noticed valgrind -tool=helgrind ./test-resolve complains, there seem
> to be some kind of possible race..
>
> I'm not gdb or valgrind expert, so i just want to bring a heads-up.
>
> Here's what i got with --t
On Mon, 12.05.14 12:03, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> Hi,
>
> How do we set the user:group of a socket created by .socket file?
>
> We have thought User= and Group= should do the job but that doesn't
> seem to be the case. Is this a missing feature or should we just set
Th
On Mon, 12.05.14 11:43, Łukasz Stelmach (l.stelm...@samsung.com) wrote:
> Hello.
>
> I've tried to update systemd to version 212 in Tizen. After I resolved
> usual building problems and managed to make my device boot, I hit a
> number of "Failed to create cgroup ..." messages. It took me some tim
On May 12, 2014, at 7:06 AM, Kirill Elagin wrote:
> Could it be that all the boot ids are actually the same for some reason?
> I had this issue in a container when systemd was reading boot_id from
> `/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
> always was host's
On Mon, May 12, 2014 at 5:27 PM, poma wrote:
> On 12.05.2014 12:22, Tom Gundersen wrote:
>> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
>> wrote:
>> This should really be added as AFAICT there is currently no way to match
>> on virtual devices like briges, TAP devices, batman-adv
On 12.05.2014 12:22, Tom Gundersen wrote:
> On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
> wrote:
> This should really be added as AFAICT there is currently no way to match
> on virtual devices like briges, TAP devices, batman-adv devices, etc...
> which have neither a persisten
On 12.05.2014 15:06, Kirill Elagin wrote:
> Could it be that all the boot ids are actually the same for some reason?
> I had this issue in a container when systemd was reading boot_id from
> `/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
> always was host's boot_id.
>
On Sat, May 10, 2014 at 12:34 AM, Sage Weil wrote:
> On Sat, 10 May 2014, Kay Sievers wrote:
>> On Sat, May 10, 2014 at 12:00 AM, Sage Weil wrote:
>> > On Fri, 9 May 2014, Kay Sievers wrote:
>> >> On Fri, May 9, 2014 at 11:31 PM, Sage Weil wrote:
>> >> > The Ceph OSD initialization relies on ide
On 05/12/2014 04:20 PM, Kay Sievers wrote:
On Mon, May 12, 2014 at 3:24 PM, Jacek Janczyk wrote:
kernel oops when connection name (kdbus_conn.name) not set via HELLO
message but requested with attach flags KDBUS_ATTACH_CONN_NAME.
Hmm, here does it crash? Seems the code that attaches the string
Am 11.05.2014 18:30, schrieb Alex B:
> 2014-05-11 20:09 GMT+04:00 Dave Reisner :
>> On Sun, May 11, 2014 at 07:53:55PM +0400, Alexander Bashmakov wrote:
>>> Issue was rised in this thread:
>>> https://mailman.archlinux.org/pipermail/arch-general/2014-May/036162.html
>>>
>>> Disclaimer:
>>> I almo
On Mon, May 12, 2014 at 3:24 PM, Jacek Janczyk wrote:
> kernel oops when connection name (kdbus_conn.name) not set via HELLO
> message but requested with attach flags KDBUS_ATTACH_CONN_NAME.
Hmm, here does it crash? Seems the code that attaches the string
checks for the string being set:
if ((m
Unterminated string array is used to populate random bus name
in check_prepare_env(). Added proper termination.
Signed-off-by: Jacek Janczyk
---
test/test-kdbus.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/test/test-kdbus.c b/test/test-kdbus.c
index e369b4e..f0bf
kernel oops when connection name (kdbus_conn.name) not set via HELLO
message but requested with attach flags KDBUS_ATTACH_CONN_NAME.
As conn.name is defined as "for debug purposes" I find it more
convenient to return generic name than to strip the field from
requested metadata or raise an error on
On Sat, May 10, 2014 at 05:12:21PM -0400, Garry T. Williams wrote:
> This recently stated showing up in the journal on Fedora F20 here:
>
> May 10 17:01:01 vfr systemd[1]: Starting Session 20 of user root.
> May 10 17:01:01 vfr systemd[1]: Started Session 20 of user root.
> May 10 17:0
Could it be that all the boot ids are actually the same for some reason?
I had this issue in a container when systemd was reading boot_id from
`/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id
always was host's boot_id.
You can also run `journalctl -F _BOOT_ID` to see a s
Hi
On Mon, May 12, 2014 at 1:49 PM, Sergei Kabanov wrote:
> Hello
> But all children will have that descriptor open. So when parent process will
> die logind will not be notified.
And? That's intentional. If you want to close the session if the main
process dies, use something like /bin/login do
Mon, 12 May 2014 13:41:03 +0200 от David Herrmann :
>Hi
>
>On Mon, May 12, 2014 at 1:27 PM, dedede gfgfgf trtrtrtrtrtr
>< s.kabano...@mail.ru > wrote:
>> Hello Colin.
>> I am speaking about descriptors in systemd pam module. Application
>> which use pam can not control it. Because of:
>>
Hi
On Mon, May 12, 2014 at 1:27 PM, dedede gfgfgf trtrtrtrtrtr
wrote:
> Hello Colin.
> I am speaking about descriptors in systemd pam module. Application
> which use pam can not control it. Because of:
> session_fd = dup(session_fd);
>
> in pam-module.c we have now descriptor which does
Fri, 09 May 2014 11:07:45 + от Colin Walters :
>
>
>On Mon, May 5, 2014 at 6:48 AM, dedede gfgfgf trtrtrtrtrtr
>< s.kabano...@mail.ru > wrote:
>> Investigations showed that since in pam module we started to dup fifo
>> descriptor problem appeared. Dup does not set O_CLOEXEC flag. So
>> af
On Mon, May 12, 2014 at 10:43 AM, Matthias Schiffer
wrote:
This should really be added as AFAICT there is currently no way to match
on virtual devices like briges, TAP devices, batman-adv devices, etc...
which have neither a persistent MAC address nor an ID_PATH to match on.
>>>
>>>
Hi,
How do we set the user:group of a socket created by .socket file?
We have thought User= and Group= should do the job but that doesn't
seem to be the case. Is this a missing feature or should we just set
the permissions by ExecStartPost= on .socket file?
Umut
_
Hello.
I've tried to update systemd to version 212 in Tizen. After I resolved
usual building problems and managed to make my device boot, I hit a
number of "Failed to create cgroup ..." messages. It took me some time
to find the reason (ah, the loveliness of parallel processing) which
appears to b
>>> This should really be added as AFAICT there is currently no way to match
>>> on virtual devices like briges, TAP devices, batman-adv devices, etc...
>>> which have neither a persistent MAC address nor an ID_PATH to match on.
>>
>> So I think what we should do here is to allow MAC address (and o
On Tue, May 06, 2014 at 12:36:44PM -0700, Michael Marineau wrote:
> commit 20a83d7bf was not equivalent to the original bug fix proposed by
> Michal Sekletar . The committed version only added
> the job to the run queue if the job had a timeout, which most jobs do
> not have. Just re-ordering the c
32 matches
Mail list logo
