Date: Sun, 10 Apr 2005 23:51:35 +0200 From: "David J. Weller-Fahy" <dave-lists-freebsd-questions@weller-fahy.com> To: freebsd-questions@freebsd.org Subject: Re: Question about processes Message-ID: <20050410215113.GQ23009@weller-fahy.com> In-Reply-To: <20050410213645.GA27742@Grumpy.DynDNS.org> <200504102323.42107.danny@ricin.com> References: <20050410211318.GP23009@weller-fahy.com> <20050410213645.GA27742@Grumpy.DynDNS.org> <20050410211318.GP23009@weller-fahy.com> <200504102323.42107.danny@ricin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Danny Pansters <danny@ricin.com> [2005-04-10 23:26 +0200]: > sockstat will show you all network and unix sockets and the processes > and their PIDs. If you want to know more such as the full path or so > (if used when invoked), you can run ps wwwaux and grep on the PID. That's exactly what I was looking for, Thanks! * David Kelly <dkelly@hiwaay.net> [2005-04-10 23:37 +0200]: > Read the man page for ps, specifically "ps -j" and variations of. What > you are looking for is the ppid, Parent Process ID. Might find a > process was started by inetd this way. > > netstat is the other tool you are looking for, to list open connections. > > The proc filesystem may also help associate open connections with > running processes. man procfs. I've tried netstat before, no luck - it shows open connections, but I was never able to get the process/program from it. I had skimmed the ps man page, but not read through it thoroughly - I'll rectify that. ;] Regards, -- dave [ please don't CC me ]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050410215113.GQ23009>