On Sat, 11.04.15 17:07, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
That's the problem: current functionality works no matter where you
store the files, but it's hard to provide the same level of
flexibility with the tmpfiles-based solution.
Well, but we never store files
On 2015-04-12 15:12, Lennart Poettering wrote:
On Sat, 11.04.15 17:07, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
That's the problem: current functionality works no matter where you
store the files, but it's hard to provide the same level of
flexibility with the tmpfiles-based
On 2015-04-12 18:06, Lennart Poettering wrote:
On Sun, 12.04.15 17:29, Goffredo Baroncelli (kreij...@inwind.it) wrote:
On 2015-04-12 15:12, Lennart Poettering wrote:
On Sat, 11.04.15 17:07, Zbigniew JÄdrzejewski-Szmek (zbys...@in.waw.pl)
wrote:
That's the problem: current functionality
On Sun, 12.04.15 17:29, Goffredo Baroncelli (kreij...@inwind.it) wrote:
On 2015-04-12 15:12, Lennart Poettering wrote:
On Sat, 11.04.15 17:07, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
wrote:
That's the problem: current functionality works no matter where you
store the files,
On Sun, 12.04.15 20:19, Goffredo Baroncelli (kreij...@libero.it) wrote:
After the work that I done to the tmpfiles, I have to agree with
Zbyszek. Adding an option to the journal.conf file is the more
reasonable thing to do.
You mean journald.conf I figure? That's not even read by the
On Wed, Apr 08, 2015 at 11:48:21PM +0200, Lennart Poettering wrote:
On Sun, 22.03.15 20:53, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Fri, Mar 20, 2015 at 07:06:28PM +0100, Goffredo Baroncelli wrote:
Hi Zbyszek,
On 2015-03-21 14:37, Zbigniew Jędrzejewski-Szmek wrote:
On Sun, 22.03.15 20:53, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Fri, Mar 20, 2015 at 07:06:28PM +0100, Goffredo Baroncelli wrote:
Hi Zbyszek,
On 2015-03-21 14:37, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 16, 2015 at 08:33:52PM +0100, Goffredo Baroncelli wrote:
On 2015-03-22 20:53, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Mar 20, 2015 at 07:06:28PM +0100, Goffredo Baroncelli wrote:
Hi Zbyszek,
[...]
But there are some details to
work out.
Setting +C on /var/log/journal/%m has smaller scope than the code in
journal-file.c now. For example it
On Fri, Mar 20, 2015 at 07:06:28PM +0100, Goffredo Baroncelli wrote:
Hi Zbyszek,
On 2015-03-21 14:37, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 16, 2015 at 08:33:52PM +0100, Goffredo Baroncelli wrote:
From: Goffredo Baroncelli kreij...@inwind.it
Add a new tmpfiles.d snippets to
Hi Zbyszek,
On 2015-03-21 14:37, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Mar 16, 2015 at 08:33:52PM +0100, Goffredo Baroncelli wrote:
From: Goffredo Baroncelli kreij...@inwind.it
Add a new tmpfiles.d snippets to set the NOCOW attributes for the
journal files. This allow better perfomance
On Mon, Mar 16, 2015 at 08:33:52PM +0100, Goffredo Baroncelli wrote:
From: Goffredo Baroncelli kreij...@inwind.it
Add a new tmpfiles.d snippets to set the NOCOW attributes for the
journal files. This allow better perfomance when the root file system
is BTRFS. Pay attention that the NOCOW
From: Goffredo Baroncelli kreij...@inwind.it
Add a new tmpfiles.d snippets to set the NOCOW attributes for the
journal files. This allow better perfomance when the root file system
is BTRFS. Pay attention that the NOCOW flags disables the checksum and
prevent scrub to rebuild a corrupted journal.
Add a new tmpfiles.d snippets to set the NOCOW attributes for the
journal files. This allow better perfomance when the root file system
is BTRFS. Pay attention that the NOCOW flags disables the checksum and
prevent scrub to rebuild a corrupted journal.
---
tmpfiles.d/journal-nocow.conf | 12
Add a new tmpfiles.d snippets to set the NOCOW attributes for the
journal files. This allow better perfomance when the root file system
is BTRFS. Pay attention that the NOCOW flags disables the checksum and
prevent scrub to rebuild a corrupted journal.
---
tmpfiles.d/journal-nocow.conf | 12
14 matches
Mail list logo
