On Sun, 24.04.16 21:54, Renjith Vijayan (renjith...@gmail.com) wrote:
> Hi All,
>
> I am trying to make journal logs persistent across reboots in my platform.
> Currently /var/log is mounted on volatile partition in the platform.
> I have a non-volatile partition mounted at /var/diagnostics.
>
On Mon, 25.04.16 06:43, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> > Could somebody point out what needs to be done to make it persistent
> > without the restart of systemd-journald service?
>
> Send SIGUSR1 to journald.
journalctl --flush is equivalent to this, and probably what should be
On Mon, Apr 25, 2016 at 7:49 AM, Umut Tezduyar wrote:
>
> > On Apr 25, 2016, at 5:43 AM, Andrei Borzenkov
> wrote:
> >
> > 24.04.2016 19:24, Renjith Vijayan пишет:
> >> Hi All,
> >>
> >> I am trying to make journal logs persistent across reboots in my
>
> On Apr 25, 2016, at 5:43 AM, Andrei Borzenkov wrote:
>
> 24.04.2016 19:24, Renjith Vijayan пишет:
>> Hi All,
>>
>> I am trying to make journal logs persistent across reboots in my platform.
>> Currently /var/log is mounted on volatile partition in the platform.
>> I have
24.04.2016 19:24, Renjith Vijayan пишет:
> Hi All,
>
> I am trying to make journal logs persistent across reboots in my platform.
> Currently /var/log is mounted on volatile partition in the platform.
> I have a non-volatile partition mounted at /var/diagnostics.
> So i made the following change
Hi All,
I am trying to make journal logs persistent across reboots in my platform.
Currently /var/log is mounted on volatile partition in the platform.
I have a non-volatile partition mounted at /var/diagnostics.
So i made the following change in tmpfile.d service config
file(volatile.conf) to