OK, I quit Growl 1.3.1 and ran the grep LISTEN command and there was nothing running on that port. I ran the command again when Growl was running and got this result, which is what I expected to see:
Growl 2047 A** 5u IPv4 0xffffff8014f16a40 0t0 TCP *:23053 (LISTEN) Growl 2047 A** 6u IPv6 0xffffff80147f7800 0t0 TCP *:23053 (LISTEN) I then quit Growl 1.3.1 and launched Growl 1.3.2, expecting it to crash as soon as I got SABNZBd+ to send it a notification, but this time it didn't crash, which I guess is good news. But I can't sample the process that way. Anyway, I'll keep it running and sample the process if it crashes. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
