Package: evince Version: 3.10.0-2 Hi,
I currently see those 2 connections: tcp 1 0 10.0.200.1:50559 10.0.200.1:631 CLOSE_WAIT 4144/evince tcp 1 0 10.0.200.1:50618 10.0.200.1:631 CLOSE_WAIT 4144/evince That is a connection from evince to cups. The last time I printed was probably weeks ago, but evince is still running. The cups side has long since closed the connection, it's the evince side that keeps the connection open with 1 byte left in the receive queue. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
