On Thu, 15.05.14 17:30, Chris Murphy (li...@colorremedies.com) wrote:
On May 15, 2014, at 3:58 PM, Lennart Poettering lenn...@poettering.net
wrote:
On Sat, 10.05.14 18:02, Chris Murphy (li...@colorremedies.com) wrote:
So I thought maybe the flush is happening to /var before var
On May 16, 2014, at 9:25 AM, Lennart Poettering lenn...@poettering.net wrote:
On Thu, 15.05.14 17:30, Chris Murphy (li...@colorremedies.com) wrote:
On May 15, 2014, at 3:58 PM, Lennart Poettering lenn...@poettering.net
wrote:
On Sat, 10.05.14 18:02, Chris Murphy
On Fri, 16.05.14 10:33, Chris Murphy (li...@colorremedies.com) wrote:
Seems crude but I could figure out how to set an selinux label on the
wrong /var to prevent anything from creating things there, and see
what explodes?
maybe use chattr with the immutable flag?
That did it.
[
On May 16, 2014, at 10:33 AM, Chris Murphy li...@colorremedies.com wrote:
On May 16, 2014, at 9:25 AM, Lennart Poettering lenn...@poettering.net
wrote:
On Thu, 15.05.14 17:30, Chris Murphy (li...@colorremedies.com) wrote:
On May 15, 2014, at 3:58 PM, Lennart Poettering
On Sat, 10.05.14 18:02, Chris Murphy (li...@colorremedies.com) wrote:
So I thought maybe the flush is happening to /var before var subvolume is
mounted there, but that's not the case; the reason why it's not empty is due
to dhclient always creating one folder prior to var subvolume mounting
On May 15, 2014, at 3:58 PM, Lennart Poettering lenn...@poettering.net wrote:
On Sat, 10.05.14 18:02, Chris Murphy (li...@colorremedies.com) wrote:
So I thought maybe the flush is happening to /var before var subvolume is
mounted there, but that's not the case; the reason why it's not
Fedora 20, systemd-208-16.fc20.x86_64
I no longer have persistent journals written to disk. I've done at least two
dozen reboots today, yet journalctl --list-boots always reports the last three
entries as:
-2 43ba57a4decd4e2fb69bfd04493455c0 Mon 2014-04-14 14:43:38 MDT—Tue 2014-04-15
