User: Password:
|
|
Subscribe / Log in / New account

Systemd programming part 2: activation and language issues

Systemd programming part 2: activation and language issues

Posted Feb 11, 2014 18:38 UTC (Tue) by cesarb (subscriber, #6266)
In reply to: Systemd programming part 2: activation and language issues by Siosm
Parent article: Systemd programming part 2: activation and language issues

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.)


(Log in to post comments)

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.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds