Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

Hello! Curious question regarding this: <https://github.com/osquery/osquery/blob/5.7.0/osquery/extensions/extensions.cpp#L49-L55>
What was the rational behind <https://github.com/osquery/osquery/blob/5.7.0/osquery/extensions/extensions.cpp#L431-L436|enforcing Osquery extensions >to end with `.ext` extension?

To answer my own question: <https://osquery.readthedocs.io/en/stable/installation/cli-flags/#daemon-control-flags>
```Force osqueryd to kill previously-running daemons. The daemon will check for an existing "pidfile". If found, and if it contains a pid of a process named "osqueryd", the process will be killed.```
If that’s the main reason, then perhaps it could be done differently by just relying on the pid.

I’m not sure how your quote here relates to the extension naming requirement.

Honestly? I have no idea.

Digging through git, I can trace it at _least_ as far back as <https://github.com/osquery/osquery/pull/848>