On Thu, 16 Jun 2011 20:19:23 +0100, Brian wrote: > On Thu 16 Jun 2011 at 17:30:09 +0000, Camaleón wrote: > > [I meant '. . . cannot . . ' in my previous post] > >> As root, running "lsof -i :8118 -i :9050" will also tell. > > Indeed. It turns out netstat or lsof looking at unix domain sockets > would have been more fruitful. I always forget about the socket in var. > > Something to remember: CUPS doesn't need a tcp connection to print > locally.
Well, we already knew that because AG said that he could print well in his very first e-mail in the thread ;-) What I was thinking (which finally had nothing to do with the problem) is that Cups went binded to another port socket number, different than the usual one (631). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
