On 04/15/2014 07:42 PM, Dirk Gently wrote:
Cristian Rodríguez wrote:
El 08/10/13 23:49, Dirk Gently escribió:
SystemD relinquishes the cupsd port because now cupsd is listening.
nope, it is doing exactly what it should, as designed and intented. otherwise it could not monitor, stop, perform any kind of operation if the socket fails.. or provide any kind of support for ordering other components after the socket goes down/up etc..
If that's the case, then SystemD is violating FUNDAMENTAL Unix design principles.
Please explain that assertion. Please tale into account how things like inetd and xinetd work. Or, for that matter, how apache works. -- Last year I went fishing with Salvador Dali. He was using a dotted line. He caught every other fish. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org