On Sat, 2015-11-14 at 15:18 +0530, Ritesh Raj Sarraf wrote:
> That said, it still does not work. And the odd part is, networking is
> only broken for IPv4.
From within the container, this reporting from networkctl is
interesting.
It states:
root@deb-template:~# networkctl status
● State:
Hello Felipe,
On Thu, 2015-11-12 at 10:02 -0300, Felipe Sateler wrote:
> rrs@chutzpah:~$ cat /etc/systemd/network/localBridge.network
> > [Match]
> > Name=sysbr0
> >
> > [Network]
> > DHCPServer=yes
> > IPForward=yes
>
> I believe this is the problem. Because we do not enable iptables
>
On Thu, 2015-11-12 at 10:02 -0300, Felipe Sateler wrote:
> I believe this is the problem. Because we do not enable iptables
> support in networkd, then it cannot set this flag.
>
> I'd love to have iptables support enabled, but upstream wants to
> switch to nftables at some point. Switch costs
Dear Julian,
Thank you for the various pointers.
> You set Delegate=yes for the unit ...
That does not seem available yet in jessie.
> The kernel cgroups implementation moved or is moving to a
> single-writer, single-hierarchy implementation ...
It does not seem to have moved yet in jessie.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On Sat, 2015-11-14 at 15:27 +0530, Ritesh Raj Sarraf wrote:
>
> I am not sure how it determines the "routable" status. The default
> gateway is 172.16.20.1, which is not pingable.
The same setup, now bound to the traditional bridge, is working.
root@deb-template:~# networkctl status
●
Processing control commands:
> reassign -1 ulatencyd
Bug #755373 [systemd] systemd 208-6 conflicts with ulatencyd
Bug #755512 [systemd] systemd-sysv: Can not normal /sbin/shutdown (even as root)
Bug #756044 [systemd] systemd: On system power,halt,reboot fail to
reboot,poweroff my system
Bug
Control: reassign -1 ulatencyd
I'm going to re-assign this to ulatencyd.
@ulatencyd maintainer: please check, if this issue is still valid and if
so, please make ulatency please nice when being running under systemd.
If ulatencyd can't be fixed to run under systemd, please add a Conflicts
to
Your message dated Sun, 15 Nov 2015 04:50:35 +0100
with message-id <5648010b.9060...@debian.org>
and subject line Re: udev won't create new device node for hotplugged SATA
device
has caused the Debian Bug report #570821,
regarding udev won't create new device node for hotplugged SATA device
to be
Your message dated Sun, 15 Nov 2015 04:20:32 +0100
with message-id <5647fa00.9050...@debian.org>
and subject line Re: Can't anything bad be detected when given gibberish?
has caused the Debian Bug report #791633,
regarding Can't anything bad be detected when given gibberish?
to be marked as done.
Your message dated Sun, 15 Nov 2015 04:16:52 +0100
with message-id <5647f924.7070...@debian.org>
and subject line Re: Bug#800521: systemd: sys-kernel-config.mount not functional
has caused the Debian Bug report #800521,
regarding systemd: sys-kernel-config.mount not functional
to be marked as
Am 28.10.2015 um 01:02 schrieb Teddy Hogeborn:
> tags 787758 +patch +fixed-upstream
> stop
>
> I think this is an instance of Red Hat Bug #1184016, here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1184016
>
> A pair of upstream patches is given in comment #33 by Michal Schmidt:
>
>
Package: systemd
Version: 215-17+deb8u2
Severity: important
Hi,
On a normal shutdown or reboot, systemd disables swap before stopping
any other processes. I see something like this:
Nov 15 14:50:53 systemd[1]: Started Synchronise Hardware Clock to System Clock.
Nov 15 14:50:53 systemd[1]:
Your message dated Sun, 15 Nov 2015 04:36:16 +0100
with message-id <5647fdb0.6030...@debian.org>
and subject line Re: Bug#804056: Re: Bug#804056: Systemd
has caused the Debian Bug report #804056,
regarding Systemd
to be marked as done.
This means that you claim that the problem has been dealt
Am 14.11.2015 um 13:23 schrieb Manuel Bilderbeek:
> Package: systemd
> Version: 227-2
> Followup-For: Bug #804910
>
> Hi,
>
> Strangely enough, today it happened again:
>
> [4.582220] input: HDA Intel Line Out Side as
> /devices/pci:00/:00:1b.
> 0/sound/card0/input17
> [
Hi,
On 14-11-15 14:09, Michael Biebl wrote:
And alternative could be, to attach the output of systemd-analyze and
"systemd-analyze blame" when such a long fsck happens.
I thought I had already done that, but here it is again in full.
$ systemd-analyze
Startup finished in 3.802s (kernel) +
Am 14.11.2015 um 13:54 schrieb Manuel Bilderbeek:
> Hi,
>
> On 14-11-15 13:49, Michael Biebl wrote:
>> Please keep in mind, that fsck for / and /usr is run in the initramfs
>> nowadays and systemd is not yet involved.
>> Can you boot and removing "quiet" from the kernel command line.
>> This
Hi,
On 14-11-15 13:49, Michael Biebl wrote:
Please keep in mind, that fsck for / and /usr is run in the initramfs
nowadays and systemd is not yet involved.
Can you boot and removing "quiet" from the kernel command line.
This should give you more log messages from systemd.
OK, I'll try that.
Hi everybody!
Last week I was at the inaugural systemd.conf which took place in Berlin
from November 5th-7th [1]. The first two days were devoted to talks and
presentations, the third (and last) day for hacking and discussion.
You can find pictures [2] and videos [3] & slides [4] for the talks.
19 matches
Mail list logo
