| |||||||||||||
|
| |||||||||||||
It's all fixable...It's all fixable...Posted May 27, 2010 12:03 UTC (Thu) by hppnq (subscriber, #14462)In reply to: It's all fixable... by khim Parent article: The road forward for systemd
But systemd should be able to handle things like socket options, network addresses, file permissions/ownership, and a few more. I don't see how this can be easily done without duplication of information. (And how about processes that decide on, say, port numbers or domain socket names only after they have been started?)
(Log in to post comments)
It's all fixable... Posted May 31, 2010 16:38 UTC (Mon) by mezcalero (guest, #45103) [Link]
Yes, you can configure quite a few socket settings in the systemd .socket files. As it turns out the amount of duplication is only minimal here, since in fact most services don't play any wild games with socket options, and many can be set after the first connection attempt.
|
|
||||||||||||