Re: ypbind grabs port designated for another service
Thomas Gebhardt wrote:
> just had to handle a problem where CUPS (IPP printing subsystem)
> didn't work any more after a reboot.
> While checking the log files I noticed that cupsd could not bind
> to its (static) port 631 because ypbind was listening on that
> port already.
> Is there a standard way to handle such a situation? How can I
> prevent RPC services to use ports that should be reserved
> for another daemon?
try changing the startup order so cups starts before ypbind,
a lot of rpc services(i think ypbind is rpc??) seemingly
pick a random port on startup.
i just checked one of my debian potato machines that
uses ypbind and it is not using 631. it is using: