On Tue, Jul 11, 2017, 22:24 Ian Pilcher wrote:
> On 07/11/2017 02:58 AM, Lennart Poettering wrote:
> > Note that DHCPv6 is not done unless IPv6 RA packets tell networkd to
> > do so. Hence, areyou sure the RA spoken on your network properly
> > indicates that?
>
>
12.07.2017 02:53, Paul D. DeRocco пишет:
>> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>>
>>> KERNEL=="midiC*", DRIVERS=="snd-usb-audio", SYMLINK+="midi%k"
>>
>> You probably want %b instead of %k here which should refer to device
>> name matched by DRIVERS.
>>
>> Start with "udevadm
On Tue, Jul 11, 2017 at 09:59:45PM +1000, Michael Chapman wrote:
> On Tue, 11 Jul 2017, Lennart Poettering wrote:
> >On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> >
> >>On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote:
> >>>Normally it's dead cheap to check
Resend with correct list address
On Tue, 2017-07-11 at 12:00 +0200, Lennart Poettering wrote:
> On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> > Are you sure about those "Debian only" and "will be 'fixed'" parts? The
> > Debian patch seems to be a cherry pick from upstream
On Thu, 06.07.17 16:43, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
> Hello!
>
> 've got an interesting trouble on timer-activated service -- 'systemctl
> status' returns a log with 'Activating (start)' status:
>
> [1]
> ==
> k_mikhail@linux-mk500:~> systemctl status
On Mon, Jul 10, 2017 at 4:41 PM, Lennart Poettering
wrote:
> On Mon, 10.07.17 15:58, Lennart Poettering (lenn...@poettering.net) wrote:
>
>> On Mon, 10.07.17 15:16, Jan Synacek (jsyna...@redhat.com) wrote:
>>
>> > On Mon, Jul 10, 2017 at 12:42 PM, Lennart Poettering
>> >
Hello!
11.07.2017 13:49, Lennart Poettering пишет:
> On Thu, 06.07.17 16:43, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
>
>> Hello!
>>
>> 've got an interesting trouble on timer-activated service -- 'systemctl
>> status' returns a log with 'Activating (start)' status:
>>
>> [1]
>>
On Tue, 11 Jul 2017, Lennart Poettering wrote:
On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote:
Normally it's dead cheap to check that, it's just reading and
comparing one memory location. It's a pitty that this
On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote:
> > Normally it's dead cheap to check that, it's just reading and
> > comparing one memory location. It's a pitty that this isn't the case
> > currently on Debian,
On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote:
> Normally it's dead cheap to check that, it's just reading and
> comparing one memory location. It's a pitty that this isn't the case
> currently on Debian, but as it appears this is an oversight on their
> side, and I am sure it will
On Tue, 11.07.17 21:59, Michael Chapman (m...@very.puzzling.org) wrote:
> On Tue, 11 Jul 2017, Lennart Poettering wrote:
> > On Tue, 11.07.17 12:55, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> >
> > > On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote:
> > > > Normally it's dead
11.07.2017 17:13, Lennart Poettering пишет:
> On Tue, 11.07.17 14:46, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
>
>> Or, please, give a hint how service, which works in 'start -> do
>> something->exit' scheme (so this is oneshot type, as I understand:
>>
On Tue, Jul 11, 2017 at 04:10:38PM +0200, Lennart Poettering wrote:
> On Tue, 11.07.17 16:07, Lennart Poettering (lenn...@poettering.net) wrote:
> > Hmm, so I run a slightly older glibc, as I haven#t updated my system
> > in a while:
> >
> > $ strace -c journalctl --since -1hour 2>&1 >/dev/null |
On Tue, 11.07.17 16:55, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> On Tue, Jul 11, 2017 at 04:10:38PM +0200, Lennart Poettering wrote:
> > On Tue, 11.07.17 16:07, Lennart Poettering (lenn...@poettering.net) wrote:
> > > Hmm, so I run a slightly older glibc, as I haven#t updated my system
> > >
On Tue, 11.07.17 16:07, Lennart Poettering (lenn...@poettering.net) wrote:
> Hmm, so I run a slightly older glibc, as I haven#t updated my system
> in a while:
>
> $ strace -c journalctl --since -1hour 2>&1 >/dev/null | head -10
> % time seconds usecs/call callserrors syscall
>
On Tue, 11.07.17 14:46, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
> Or, please, give a hint how service, which works in 'start -> do
> something->exit' scheme (so this is oneshot type, as I understand:
> https://www.freedesktop.org/software/systemd/man/systemd.service.html :
> "Behavior
On 07/10/2017 08:23 PM, Ian Pilcher wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> I have "DHCP=yes" in the [Network] section of my WAN
On Tue, Jul 11, 2017 at 05:20:10PM +0200, Lennart Poettering wrote:
> On Tue, 11.07.17 16:55, Tomasz Torcz (to...@pipebreaker.pl) wrote:
> > > Forgot to mention:
> > >
> > > $ rpm -qa glibc
> > > glibc-2.24-4.fc25.x86_64
> > >
> > > Apparently, this regressed between this version and
> > >
* Lennart Poettering:
> This all stems from my experiences with PulseAudio back in the day:
> People do not grok the effect of fork(): it only duplicates the
> invoking thread, not any other threads of the process, moreover all
> data structures are copied as they are, and that's a time bomb
* Lennart Poettering:
> Apparently, this regressed between this version and
> glibc-2.24-9.fc25.x86_64 hence.
Yes, I backported the fork cache removal to Fedora 25. There is no
longer a good way to main such a cache in userspace because glibc
cannot intercept anymore all the ways that can
On 07/11/2017 02:58 AM, Lennart Poettering wrote:
Note that DHCPv6 is not done unless IPv6 RA packets tell networkd to
do so. Hence, areyou sure the RA spoken on your network properly
indicates that?
Interesting. I am seeing somewhat different behavior (but note that
this is systemd-networkd
* Michael Chapman:
> It's a pity glibc doesn't provide an equivalent for pthread_atfork()
> outside of the pthread library. Having a notification that a fork has just
> occurred would allow us to do the PID caching ourselves.
In fact, it does, as a public symbol: __register_atfork.
It's just
> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>
> > There is already a symlink
> > "/dev/snd/by-path/platform-3f98.usb-usb-0:1.2:1.0", but
> > it refers to
> > the useless "controlC1" interface. It also doesn't appear
> > to be generated
> > by an explicit rule anywhere that might
On Tue, Jul 11, 2017 at 6:23 AM, Ian Pilcher wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> […]
>
> For some reason,
On Mon, 10.07.17 22:23, Ian Pilcher (arequip...@gmail.com) wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> I have "DHCP=yes" in the
On Mon, 10.07.17 14:04, vcap...@pengaru.com (vcap...@pengaru.com) wrote:
> > > Except there's always a risk of these things regressing to normal
> > > syscalls,
> > > and one has to weigh the utility against that. It's unclear to me what
> > > significant utility having the sd-journal API
> From: Andrei Borzenkov [mailto:arvidj...@gmail.com]
>
> > KERNEL=="midiC*", DRIVERS=="snd-usb-audio", SYMLINK+="midi%k"
>
> You probably want %b instead of %k here which should refer to device
> name matched by DRIVERS.
>
> Start with "udevadm test" to verify.
I tried the following rule:
El 11-07-2017 a las 18:23, WANG Siyuan escribió:
> Hi, all
> systemd-udevd invoked oom-killer during Linux boot. I open debug message
> of systemd-udevd. But I can't find where the problem is. Could anybody
> help me? Thanks very much.
The oom-killer should never be invoked on udev at boot..
28 matches
Mail list logo