tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: PUFFS and existing file that get ENOENT

To: YAMAMOTO Takashi <yamt%mwd.biglobe.ne.jp@localhost>
Subject: Re: PUFFS and existing file that get ENOENT
From: Emmanuel Dreyfus <manu%netbsd.org@localhost>
Date: Mon, 16 Jan 2012 10:58:54 +0000

On Mon, Jan 16, 2012 at 10:56:33AM +0000, YAMAMOTO Takashi wrote:
> you can increase the chance by running
>       while :;do sysctl -w kern.maxvnodes=0; done

It will always fail:
bacasable#  sysctl -w kern.maxvnodes=0 
sysctl: kern.maxvnodes: sysctl() failed with Device busy

-- 
Emmanuel Dreyfus
manu%netbsd.org@localhost

Follow-Ups:
- Re: PUFFS and existing file that get ENOENT
  - From: YAMAMOTO Takashi
- Re: PUFFS and existing file that get ENOENT
  - From: Adam Hamsik

References:
- Re: PUFFS and existing file that get ENOENT
  - From: Emmanuel Dreyfus
- Re: PUFFS and existing file that get ENOENT
  - From: YAMAMOTO Takashi

Prev by Date: Re: PUFFS and existing file that get ENOENT
Next by Date: Re: heads-up: IPSEC is now FAST_IPSEC
Previous by Thread: Re: PUFFS and existing file that get ENOENT
Next by Thread: Re: PUFFS and existing file that get ENOENT
Indexes:

Home | Main Index | Thread Index | Old Index