On Thu, 18.08.16 15:55, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
> Hello!
> Personally, don't we have philosophical contradiction here? -- Journal is
> positioned as syslog alternative with more wide functionality, but in
> current case we offer to turn off whole journal to make
Ok, thanks for making this aspect more clear!
18.08.2016 18:00, Lennart Poettering пишет:
On Thu, 18.08.16 15:55, Mikhail Kasimov (mikhail.kasi...@gmail.com) wrote:
Hello!
Personally, don't we have philosophical contradiction here? -- Journal is
positioned as syslog alternative with more
Hello!
Personally, don't we have philosophical contradiction here? -- Journal
is positioned as syslog alternative with more wide functionality, but in
current case we offer to turn off whole journal to make functionality
only as transport. No problem, but is RFE to incorporate
On Wed, 17.08.16 13:02, Divya Thaluru (divya.thal...@gmail.com) wrote:
> Thanks Mantas!!! In my case, metadata "cmdline" had sensitive information
> which I am not intended to store. Is there any way to disable collecting
> metadata?
If your cmdline field contains sensitive information then you
On Wed, 17.08.16 12:10, Divya Thaluru (divya.thal...@gmail.com) wrote:
> Hi,
>
> Journalctl stores metadata like "_UID,_GID,_CMDLINE,_SYSTEMD_CGROUP etc…"
> for each message. Is there any way, can we encrypt metadata (commandline
> info) so sensitive information wont be stored.
>
> If
On Wed, Aug 17, 2016 at 10:10 PM, Divya Thaluru
wrote:
> Hi,
>
> Journalctl stores metadata like "_UID,_GID,_CMDLINE,_SYSTEMD_CGROUP etc…"
> for each message. Is there any way, can we encrypt metadata (commandline
> info) so sensitive information wont be stored.
>
> If
Thanks Mantas!!! In my case, metadata "cmdline" had sensitive information
which I am not intended to store. Is there any way to disable collecting
metadata?
Thanks,
Divya
On Wed, Aug 17, 2016 at 12:55 PM, Mantas Mikulėnas
wrote:
> On Wed, Aug 17, 2016 at 10:10 PM, Divya