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

Add inotify support for dynamic home servers #4649

Open
alandekok opened this issue Aug 4, 2022 · 0 comments
Open

Add inotify support for dynamic home servers #4649

alandekok opened this issue Aug 4, 2022 · 0 comments
Labels
feature enhancement category: a new feature (an extension of functionality) v3.2.x meta: relates to the v3.2.x branch v4.0.x meta: relates to the v4.0.x branch

Comments

@alandekok
Copy link
Member

Message

It may be useful to add inotify support for dynamic home servers. That way you can just add / delete files in raddb/home_servers, and the server will automatically load / delete the files.

Example code for inotify is at https://www.thegeekstuff.com/2010/04/inotify-c-program-example/

That doesn't seem too bad, actually. The realm.c file would have to be able to add an fd to the event list. But everything else would likely be less than 500 LoC. It would likely be best to have a linux-specific code path, and an OSX-specific code path.

Linux can use inotify, and OSX can use kqueue. The master code branch in has some code for kqueue(), see references to VNODE. Tho v3.2.x doesn't have support for anything other than read filters. It might be simples to just ignore OSX :)

@alandekok alandekok added the close state: auto close the issue label Aug 4, 2022
@mcnewton mcnewton added feature enhancement category: a new feature (an extension of functionality) v4.0.x meta: relates to the v4.0.x branch v3.2.x meta: relates to the v3.2.x branch and removed close state: auto close the issue labels Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature enhancement category: a new feature (an extension of functionality) v3.2.x meta: relates to the v3.2.x branch v4.0.x meta: relates to the v4.0.x branch
Projects
None yet
Development

No branches or pull requests

2 participants