On Mon, Apr 17, 2017 at 01:46:29PM +, george Nopicture wrote:
> Are there any plans on implementing macsec interface configuration from
> systemd-networkd? Since its already added in kernel as a loadable
> module, fedora misses a patched iproute2 to support macsec and also
> lacks automatic int
On Mon, Apr 17, 2017 at 10:05 PM, Andrei Borzenkov wrote:
> strace -p $(pgrep systemd-journal)
>
> You will not see actual writes as file is memory mapped, but it
> definitely does not do any fsync() every so often.
https://paste.fedoraproject.org/paste/oVT-tsU2sBOdTJaZxGua-15M1UNdIGYhyRLivL9gyd
On Mon, Apr 17, 2017 at 10:05 PM, Andrei Borzenkov wrote:
>> I have no idea if it's fsync or what. How can I tell?
>>
>
> strace -p $(pgrep systemd-journal)
>
> You will not see actual writes as file is memory mapped, but it
> definitely does not do any fsync() every so often.
Also found this.
On Mon, Apr 17, 2017 at 10:05 PM, Andrei Borzenkov wrote:
> 18.04.2017 06:50, Chris Murphy пишет:
>>> What exactly "changes" mean? Write() syscall?
>>
>> filefrag reported entries increase, it's using FIEMAP.
>>
>
> So far it sounds like btrfs allocates new extent on every write to
> journal file
18.04.2017 06:50, Chris Murphy пишет:
> On Mon, Apr 17, 2017 at 9:42 PM, Andrei Borzenkov wrote:
>> 17.04.2017 22:49, Chris Murphy пишет:
>>> On Mon, Apr 17, 2017 at 11:27 AM, Andrei Borzenkov
>>> wrote:
17.04.2017 19:25, Chris Murphy пишет:
> This explains one system's fragmented journ
Are there any plans on implementing macsec interface configuration from
systemd-networkd? Since its already added in kernel as a loadable
module, fedora misses a patched iproute2 to support macsec and also
lacks automatic interface configuration (i dunno if nm supports it?)
preferably from systemd-
On Mon, Apr 17, 2017 at 9:42 PM, Andrei Borzenkov wrote:
> 17.04.2017 22:49, Chris Murphy пишет:
>> On Mon, Apr 17, 2017 at 11:27 AM, Andrei Borzenkov
>> wrote:
>>> 17.04.2017 19:25, Chris Murphy пишет:
This explains one system's fragmented journals; but the other system
isn't snapshot
17.04.2017 22:49, Chris Murphy пишет:
> On Mon, Apr 17, 2017 at 11:27 AM, Andrei Borzenkov
> wrote:
>> 17.04.2017 19:25, Chris Murphy пишет:
>>> This explains one system's fragmented journals; but the other system
>>> isn't snapshotting journals and I haven't figured out why they're so
>>> fragme
On Mon, Apr 17, 2017 at 11:27 AM, Andrei Borzenkov wrote:
> 17.04.2017 19:25, Chris Murphy пишет:
>> This explains one system's fragmented journals; but the other system
>> isn't snapshotting journals and I haven't figured out why they're so
>> fragmented. No snapshots, and they are all +C at crea
Here's an example rotated log (Btrfs, NVMe, no compression, default
ssd mount option). As you can see it takes up more space on disk than
it contains data, so there's a lot of slack space for some reason,
despite /etc/systemd/journald.conf being unmodified and thus
Compress=Yes.
file:
system@2547
17.04.2017 19:25, Chris Murphy пишет:
> This explains one system's fragmented journals; but the other system
> isn't snapshotting journals and I haven't figured out why they're so
> fragmented. No snapshots, and they are all +C at create time
> (systemd-journald default on Btrfs). Is it possible to
On Mon, Apr 17, 2017 at 3:57 AM, Lennart Poettering
wrote:
>> I do manual snapshots before software updates, which means new writes
>> to these files are subject to COW, but additional writes to the same
>> extents are overwrites and are not COW because of chattr +C. I've used
>> this same strate
Am Mon, 17 Apr 2017 16:01:48 +0200
schrieb Kai Krakow :
> > We also ask btrfs to defrag the file as soon as we mark it as
> > archived...
>
> This makes sense. And I've learned that journal on btrfs works much
> better if you use many small files vs. a few big files. I've currently
> set the jo
Am Mon, 17 Apr 2017 11:57:21 +0200
schrieb Lennart Poettering :
> On Sun, 16.04.17 14:30, Chris Murphy ([email protected]) wrote:
>
> > Hi,
> >
> > This is on a Fedora 26 workstation (systemd-233-3.fc26.x86_64)
> > that's maybe a couple weeks old and was clean installed. Drive is
> > NVMe.
On Mon, 10.04.17 20:20, Chris Murphy ([email protected]) wrote:
> 4. Systemd for not enforcing limited kill exemption to those running
> from initramfs, i.e. ignore kill exemption if the program is running
> other than initramfs.
Well, we are not the police, and we do kill everything by def
On Wed, 12.04.17 18:27, Timothée Ravier ([email protected]) wrote:
> Hi,
>
> I would like to make the /proc directory inaccessible for some services.
> Unfortunately, adding the InaccessiblePaths=/proc option to a service unit
> will
> not work.
Hmm, what precisely do you intend to make unavail
On Mon, 10.04.17 19:30, Chris Murphy ([email protected]) wrote:
> >> Remember, all of this is because there *is* software that does the wrong
> >> thing, and it *is* possible for software to hang and be unkillable. It
> >> would
> >> be good for systemd to do the right thing even in the pre
On Tue, 11.04.17 10:18, Michal Sekletar ([email protected]) wrote:
> Hi everyone,
>
> I was asked today about $subject. I quickly skimmed trough the
> relevant parts of the code and current default looks like an
> oversight. I think there are no processes other than journald involved
> in notif
Am 17.04.2017 um 00:47 schrieb Enrico Weigelt, metux IT consult:
On 17.04.2017 00:04, Lennart Poettering wrote:
Please always check the man pages if you have questions regarding a
specific systemd interface:
https://www.freedesktop.org/software/systemd/man/sd_notify.html
Done so, of course
On Thu, 13.04.17 16:08, poma ([email protected]) wrote:
> Hello
>
> Regaining of the network-interface, as is stated in the manual, ain't
> happening;
> man 1 systemd-nspawn
> ...
> OPTIONS
> ...
> --network-interface=
> Assign the specified network interface to the container.
> Thi
On Fri, 14.04.17 20:30, Paul Menzel ([email protected]) wrote:
> Dear systemd folks,
>
>
> Is there a shorter way than below to show all messages of an executable
> and a unit?
>
> ```
> $ journalctl _COMM=sudo + _SYSTEMD_UNIT=NetworkManager.service
> ```
>
> I would be happy a
On Sun, 16.04.17 14:30, Chris Murphy ([email protected]) wrote:
> Hi,
>
> This is on a Fedora 26 workstation (systemd-233-3.fc26.x86_64) that's
> maybe a couple weeks old and was clean installed. Drive is NVMe.
>
>
> # filefrag *
> system.journal: 9283 extents found
> user-1000.journal: 3
On Thu, 13.04.17 11:58, Martin Wilck ([email protected]) wrote:
> On Thu, 2017-04-13 at 08:49 +, Mantas Mikulėnas wrote:
> > IIRC, enable/disable/is-enabled are implemented entirely via direct
> > filesystem access. Other than that, systemctl uses a private socket
> > when running as root – it t
On Thu, 13.04.17 12:05, Martin Wilck ([email protected]) wrote:
> On Thu, 2017-04-13 at 11:45 +0200, Lennart Poettering wrote:
> > On Thu, 13.04.17 08:49, Mantas Mikulėnas ([email protected]) wrote:
> >
> > > IIRC, enable/disable/is-enabled are implemented entirely via direct
> > > filesystem acces
On Mon, 17.04.17 00:47, Enrico Weigelt, metux IT consult
([email protected]) wrote:
> On 17.04.2017 00:04, Lennart Poettering wrote:
>
> > Please always check the man pages if you have questions regarding a
> > specific systemd interface:
> >
> > https://www.freedesktop.org/software/syste
25 matches
Mail list logo
