Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we relocate /private/var under /opt/osquery #10

Open
Smjert opened this issue Aug 12, 2021 · 2 comments
Open

Should we relocate /private/var under /opt/osquery #10

Smjert opened this issue Aug 12, 2021 · 2 comments
Labels
question Further information is requested

Comments

@Smjert
Copy link
Member

Smjert commented Aug 12, 2021

It has been raised a question about why we are not relocating /private/var contents under /opt/osquery. This is to track such discussion if needed.

@Smjert Smjert added the question Further information is requested label Aug 12, 2021
@Smjert Smjert changed the title Should we relocate /private/var to /opt/osquery Should we relocate /private/var under /opt/osquery Aug 12, 2021
@Smjert
Copy link
Member Author

Smjert commented Aug 12, 2021

The only comment I have is: what is the reasoning?
Also, lets remember that this change requires going over all the code that expects by default that configs, lenses, packs etc are by default there (might be an easy thing, but just to keep it in mind).

@directionless
Copy link
Member

I'll start by saying that I don't think this is a very end user visible issue. And as such, I don't think changing it would be a breaking release. (Yeah, it's a little irksome, but it seems fine?)

So my general read on things like /opt/ are they an application should be pretty self contained there. I'd expect a vendor package to drop anything that looked like an installation file into /opt/whatev, but probably still use /var for runtime info (like databases, logs, and pid files). I think lenses fit much closer to either installation things (belongs in /opt) or configuration (belongs in /etc).

I think the linux FHS generally agrees. But I'm not sure anyone really pays any attention to it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants