Figure out how to deal with Sun RPC services #17

New Issue

oysteikt · 2026-01-05T18:07:45+01:00

oysteikt commented

2026-01-05 18:07:45 +01:00

All of the following use Sun RPC to have services connect to them:

rwall
rusers
rup (uses rusers daemon)

We could in theory just become the portmapper, but that would make the service unusable on machines like microbel, which needs the portmapper for other services like NFS.
We could also talk with the existing portmapper, but that would likely leave us unable to use systemd sockets, because we would be given a dynamically allocated port at runtime to listen to. Not only that, the portmapper would probably like to invoke an instance for us, which is not very good. It might be possible to shim it somehow?
Alternative 3 is that we write our own portmapper, that can both handle the old dynamic allocation, but also statically mapped already existing services.

All of the following use Sun RPC to have services connect to them: - [ ] rwall - [ ] rusers - [ ] rup (uses rusers daemon) We could in theory just become the portmapper, but that would make the service unusable on machines like microbel, which needs the portmapper for other services like NFS. We could also talk with the existing portmapper, but that would likely leave us unable to use systemd sockets, because we would be given a dynamically allocated port at runtime to listen to. Not only that, the portmapper would probably like to invoke an instance for us, which is not very good. It might be possible to shim it somehow? Alternative 3 is that we write our own portmapper, that can both handle the old dynamic allocation, but also statically mapped already existing services.

oysteikt added the question label 2026-01-05 18:07:45 +01:00

Sign in to join this conversation.

No Assignees

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Projects/roowho2#17