Doug Barton wrote:
> Yar Tikhiy wrote:
>
>> As for ee, the fix from bin/65892 appears to have been applied to
>> CURRENT and 5-STABLE, but not to 4-STABLE. Care to test the fix
>> in 4.11 or 4-STABLE? It should be 100% safe.
>
>
> Since the diff in 1.32 was very clear, and it has already made
Yar Tikhiy wrote:
As for ee, the fix from bin/65892 appears to have been applied to
CURRENT and 5-STABLE, but not to 4-STABLE. Care to test the fix
in 4.11 or 4-STABLE? It should be 100% safe.
Since the diff in 1.32 was very clear, and it has already made it down to
5-stable, I tested this
Yar Tikhiy wrote:
> On Thu, Sep 08, 2005 at 10:21:46AM +1000, Antony Mawer wrote:
>>Another "me too" -- usually when we notice our server (running FreeBSD
>>4.11) starting to crawl, the culprit is an "ee" session using up 99%
>>cpu. I just reproduced it then by logging in via ssh, running "ee" (not
On Fri, Sep 09, 2005 at 09:31:38PM +, Nielsen wrote:
> Yar Tikhiy wrote:
> > On Thu, Sep 08, 2005 at 10:21:46AM +1000, Antony Mawer wrote:
> >>Another "me too" -- usually when we notice our server (running FreeBSD
> >>4.11) starting to crawl, the culprit is an "ee" session using up 99%
> >>cpu.
On Thu, Sep 08, 2005 at 10:21:46AM +1000, Antony Mawer wrote:
> On 8/09/2005 10:18 AM, Nate Nielsen wrote:
> > talonz wrote:
> >>Recently i have been using a dialup 56k account to access the net
> >>and have noticed that when my ssh session times out and I am editing
> >>a file in ` ee ' the system
On 2005-09-08 00:02, Craig Edwards <[EMAIL PROTECTED]> wrote:
> At least this is what i suspect happens. Lazy programming somewhere...
> Brooks Davis wrote:
> >On Thu, Sep 08, 2005 at 08:27:13AM +1000, talonz wrote:
> >>Recently i have been using a dialup 56k account to access the net
> >>and have
On 8/09/2005 10:18 AM, Nate Nielsen wrote:
> talonz wrote:
>>Recently i have been using a dialup 56k account to access the net
>>and have noticed that when my ssh session times out and I am editing
>>a file in ` ee ' the system goes to 99% cpu usage and stays like
>>this till the pid is killed.
>>T
talonz wrote:
> Recently i have been using a dialup 56k account to access the net
> and have noticed that when my ssh session times out and I am editing
> a file in ` ee ' the system goes to 99% cpu usage and stays like
> this till the pid is killed.
> This is a standard user account (not root/su)
I can duplicate this with nano on freebsd 5.4 and 5.2.1
It seems that the process ignores the HUP signal maybe or ignores the
EOF condition on stdin, and the select loop, or whatever it uses, just
loops infinitely with nothing to read, constantly returning an error
condition.
At least this i
On Thu, Sep 08, 2005 at 08:27:13AM +1000, talonz wrote:
> Recently i have been using a dialup 56k account to access the net
> and have noticed that when my ssh session times out and I am editing
> a file in ` ee ' the system goes to 99% cpu usage and stays like
> this till the pid is killed.
> This
Recently i have been using a dialup 56k account to access the net
and have noticed that when my ssh session times out and I am editing
a file in ` ee ' the system goes to 99% cpu usage and stays like
this till the pid is killed.
This is a standard user account (not root/su)
Would a user be able t
11 matches
Mail list logo
