On Mon, Apr 10, 2017 at 9:14 AM, Michael Chapman
wrote:
> On Mon, 10 Apr 2017, Chris Murphy wrote:
>
>> On Sun, Apr 9, 2017 at 5:17 AM, Lennart Poettering
>> wrote:
>>
>> That said, are you sure FIFREEZE is really what we want there? it
>>> appears to also pause any further writes to disk (until
On Mon, 10 Apr 2017, Chris Murphy wrote:
On Sun, Apr 9, 2017 at 5:17 AM, Lennart Poettering
wrote:
That said, are you sure FIFREEZE is really what we want there? it
appears to also pause any further writes to disk (until FITHAW is
called).
So, I am still puzzled why the file system people t
On Sun, Apr 9, 2017 at 2:17 PM, Lennart Poettering
wrote:
> On Sun, 09.04.17 10:11, Michael Chapman (m...@very.puzzling.org) wrote:
>
> > Don't forget, they've provided an interface for software to use if it
> needs
> > more than the guarantees provided by sync. Informally speaking, the
> FIFREEZ
On Sun, Apr 09, 2017 at 10:37:36PM -0600, Chris Murphy wrote:
> On Sun, Apr 9, 2017 at 5:17 AM, Lennart Poettering
> wrote:
>
> > That said, are you sure FIFREEZE is really what we want there? it
> > appears to also pause any further writes to disk (until FITHAW is
> > called).
>
> > So, I am st
On Sun, Apr 9, 2017 at 5:17 AM, Lennart Poettering
wrote:
> That said, are you sure FIFREEZE is really what we want there? it
> appears to also pause any further writes to disk (until FITHAW is
> called).
> So, I am still puzzled why the file system people think that "sync()"
> isn't supposed to
Nested jobs are problematic as they usually result in a deadlock – you'll
have to use "/bin/systemctl --no-block restart docker" there.
Though the whole setup in general seems suspicious...
On Sat, Apr 8, 2017, 18:29 Alex Chistyakov wrote:
> Hello,
>
> I am trying to establish a connection betw
Hi,
We are seeing high latency (>100ms) when resolving local names via
LLMNR.
systemd v233 / Gentoo
There appears to be a large delay between systemd-resolved receiving
the udp query over 127.0.0.53:53 and when it dispatches the LLMNR query:
18:29:38.752644 clock_gettime(CLOCK_BOOTTIME, {1
On Sat, 8 Apr 2017, Chris Murphy wrote:
> On Tue, Apr 4, 2017 at 11:55 AM, Andrei Borzenkov wrote:
> > grub2 is not limited to 640KiB. Actually it will actively avoid using
> > low memory. It switches to protected mode as the very first thing and
> > can use up to 4GiB (and even this probably can
On Sun, 09.04.17 10:11, Michael Chapman (m...@very.puzzling.org) wrote:
> Don't forget, they've provided an interface for software to use if it needs
> more than the guarantees provided by sync. Informally speaking, the FIFREEZE
> ioctl is intended to place a filesystem into a "fully consistent" s