| 1 |
On 01/19/2010 09:04 AM, Joseph wrote: |
| 2 |
> ... |
| 3 |
> When I open a firefox with one of the tab pointing to: |
| 4 |
> localhost:631 (cups) |
| 5 |
> the cups is being shut down by: "cupsdAcceptClient: 11" |
| 6 |
> |
| 7 |
> D [19/Jan/2010:09:39:59 -0700] cupsdAcceptClient: 11 from localhost:631 (IPv4) |
| 8 |
> D [19/Jan/2010:09:39:59 -0700] cupsdReadClient: 11 GET /favicon.ico HTTP/1.1 |
| 9 |
> D [19/Jan/2010:09:39:59 -0700] cupsdAuthorize: No authentication data provided. |
| 10 |
> D [19/Jan/2010:09:39:59 -0700] cupsdCloseClient: 11 |
| 11 |
> D [19/Jan/2010:09:39:59 -0700] cupsdCloseClient: -607871304 |
| 12 |
> |
| 13 |
> Who is "cupsdAcceptClient: 11"??? |
| 14 |
> |
| 15 |
> If the firebox tab is not pointing cup interface: localhost:631 |
| 16 |
> cups starts and runs just fine. |
| 17 |
> |
| 18 |
> Can any of you try it: open a tab "localhost:631" (don't close the firefox) and restart your computer. |
| 19 |
> Is the cups still running after restarting? |
| 20 |
|
| 21 |
Yes, same thing here. An strace of cupsd shows a coupld of bad file descriptor |
| 22 |
errors, so I'm guessing that some socket connection is not cleaned up properly |
| 23 |
when rebooting. I know for sure that cupsd is running normally until I start |
| 24 |
firefox -- which maybe(?) is still talking to the old socket even though the |
| 25 |
URL looks correct. Anyway, cups is unhappy that firefox is not providing |
| 26 |
authentication data -- perhaps because it's talking to the wrong socket. |
| 27 |
|
| 28 |
Just guessing, though. |
Archives