#3207: implement <utmpx.h> ----------------------------+--------------------------- Reporter: kaliber | Owner: nobody Type: enhancement | Status: new Priority: normal | Milestone: R1 Component: System/POSIX | Version: R1/pre-alpha1 Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 1 | Platform: All ----------------------------+--------------------------- Comment (by bonefish): Replying to [comment:9 siarzhuk]: > But if you find the full-blown implementation reasonable at the current moment - the follow-up GCI task can be created - to finish this implementation. But, please, share in this case your vision about implementation details. Thanks. I don't have a vision about the implementation ATM. I have a rough idea of the purpose of the user accounting functionality -- from which I would say that it can be implemented in the current Haiku -- but I don't know any details. A reasonable approach would be to first find out, how this DB is actually used. I don't mean the API -- the POSIX specs cover that -- but which program/component uses the API when and how. Also, there are no removal operations in the API, so the DB must either be cleared and/or culled at some point (at boot?). Once all that is clear, we can think of how an appropriate implementation could look like on Haiku. -- Ticket URL: <http://dev.haiku-os.org/ticket/3207#comment:11> Haiku <http://dev.haiku-os.org> Haiku - the operating system.