On Mon, Jul 19, 2010 at 11:04 PM, Adam Vande More wrote:
> On Mon, Jul 19, 2010 at 3:12 AM, Jim wrote:
>>
>> I was working on an application I've been developing, and I closed the
>> last instance a bit over 12 hours ago, but some of the sockets are
>> still stuck in use:
>> [s...@elrond ~/dev/pi
On Mon, Jul 19, 2010 at 3:12 AM, Jim wrote:
> I was working on an application I've been developing, and I closed the
> last instance a bit over 12 hours ago, but some of the sockets are
> still stuck in use:
> [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612
> tcp4 0
On Mon, Jul 19, 2010 at 10:20 AM, Anonymous wrote:
> Jim writes:
>
>> I was working on an application I've been developing, and I closed the
>> last instance a bit over 12 hours ago, but some of the sockets are
>> still stuck in use:
>> [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' |
Jim writes:
> I was working on an application I've been developing, and I closed the
> last instance a bit over 12 hours ago, but some of the sockets are
> still stuck in use:
> [s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612
> tcp4 0 0 192.168.1.80.42464 192.
I was working on an application I've been developing, and I closed the
last instance a bit over 12 hours ago, but some of the sockets are
still stuck in use:
[s...@elrond ~/dev/pipe/scripts]$ netstat | grep -e 'tcp' | grep 9612
tcp4 0 0 192.168.1.80.42464 192.168.1.2.9612 SYN_S
