Systemd programming part 2: activation and language issues [LWN.net]

Systemd programming part 2: activation and language issues

Posted Feb 11, 2014 16:38 UTC (Tue) by Siosm (subscriber, #86882)
Parent article: Systemd programming part 2: activation and language issues

> So systemd would need to do this too: bind an arbitrary port, register that port with rpcbind, and start rpc.statd when traffic arrives on that socket. (...) Whether it is worth adding this functionality to systemd for the two or maybe three services that would use it is hard to say.

Well, only upstream can answer that. You should ask on the systemd-devel mailing list.

to post comments

Systemd programming part 2: activation and language issues

Posted Feb 11, 2014 18:38 UTC (Tue) by cesarb (subscriber, #6266) [Link] (1 responses)

Clearly, what is needed is to incorporate the functionality of portmap/rpcbind within systemd's PID 1 itself. We could call this "portmap activation".

(I might or might not be joking.)

Systemd programming part 2: activation and language issues

Posted Feb 11, 2014 20:47 UTC (Tue) by Siosm (subscriber, #86882) [Link]

> incorporate the functionality of portmap/rpcbind within systemd's PID 1 itself

That's absolutely not what the author meant :
> bind an arbitrary port, register that port with rpcbind

This would be one time process for "rpc-sockets" which is really close to the already include socket activation. This could be added as an option to the current socket unit I think.