Skip to content

Support for not writing config state of any kind #1747

Description

@errge

Is your feature request related to a problem? Please describe.

We are using lnav on a shared server to browse some logs, where we all log in via different SSH keys (but as the same user).

Yes, this is suboptimal regarding security, and we will fix it, but for now this is the situation.

The problem is that when people are using lnav, they are leaving state (e.g. filters, or other settings they can set via the UI), and that pollutes the UI experience of the other users.

For now I have written a shell wrapper, that redirects XDG_{CACHE,DATA,CONFIG} to a tempdir, but it would be nice if upstream lnav would just work for this use-case out of the box.

Describe the solution you'd like

I'd like to have a config setting that is saying "the config is locked and final, lnav should read it at startup, but under no circumstances ever modify any of the configs".

Also, for clean room testing it would be nice to have a single command line flag that says "without config" and a single command line flag that points lnav to "use a specific config directory one time".

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions