Date: Thu, 25 Sep 1997 07:41:59 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: danny@panda.hilink.com.au (Daniel O'Callaghan) Cc: nonxstnt@darkening.com, freebsd-hackers@FreeBSD.ORG Subject: Re: ee taking up weird cpu amount. Message-ID: <199709250742.AAA10411@usr03.primenet.com> In-Reply-To: <Pine.BSF.3.91.970925162705.262G-100000@panda.hilink.com.au> from "Daniel O'Callaghan" at Sep 25, 97 04:28:12 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > > root 18863 99.1 1.2 388 732 p3- R 6:59PM 673:39.41 ee > > /etc/pw.018862 > > > > I've had this happen several times now, where I would login to my system > > and see ee taking up 99% CPU (on a P2/266). As you can see, this is some > > guy doing chfn I guess. This process has been on for 12 hours now though. > > Kill the process. The vty has been disconnected without logging out, so > ee goes into a loop. vi and pico do the same thing. IMO, this is a bug in HUP processing. I think that HUP should be sent to the process group members from the process group leaders before the tty is revoked, instead of simply erroring out the reads/writes. SVR4, SVR3, SCO Xenix, SCO UNIX, UnixWare, Solaris, SunOS, Fortune, Cubix, Huerikon, Arrete, Unisys UNIX, UNICOS, Linux, Cubix, Intel UNIX, Intel Xenix, PrimeOS, ISC UNIX, Ultrix, OSF/1, OSF/2, Microport UNIX v2, Microport UNIX v3, Altos Xenix and UNIX, Cogent, Coherent, and practically every other UNIX on the planet does this. But FreeBSD does not. Heck, who is to say my interpretaion of POSIX is right and FreeBSD's is wrong (apart from *everyone*else*on*the*planet*, that is...). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709250742.AAA10411>