-----Original Message----- From: Cristian Rodríguez <crrodriguez@opensuse.org> To: opensuse@opensuse.org Subject: Re: [opensuse] systemd vs cups Date: Wed, 09 Oct 2013 01:08:27 -0300 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.. -----Original Message----- I thought along the same lines as Dirk.... If i got a (any) client-program, setting up an connection on 1.2.3.4::abcd who is answering the call? If i understood you correctly, systemd steals away all connection-setups How does i get to the intended service? Can you define priorities on ports? If systemd passes connection-request-setup towards an underlying daemon, fine, but in that case the daemon does not need also to be listening. So either one, but not both. I sincerely hope, that not _all_ traffic passes first through systemd before it arrives at the intended daemon...... Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org