Notice: locking SHMFILE in core failed: Resource temporarily, unavailable

2009-07-08 Thread Christer Solskogen
I'm getting this notice whenever I (re)start varnish on FreeBSD 7.2 (amd64). Varnish runs and works as I would expect, so is it harmless? shine# grep varnishd /etc/rc.conf varnishd_enable=YES varnishd_listen=:80 varnishd_config=/usr/local/etc/varnish/shine.vcl

Re: Notice: locking SHMFILE in core failed: Resource temporarily, unavailable

2009-07-08 Thread Dag-Erling Smørgrav
Christer Solskogen solsko...@carebears.mine.nu writes: I'm getting this notice whenever I (re)start varnish on FreeBSD 7.2 (amd64). Varnish runs and works as I would expect, so is it harmless? Yes, it's harmless (though it may have an impact on performance if you're running a log consumer).

Re: Notice: locking SHMFILE in core failed: Resource temporarily, unavailable

2009-07-08 Thread Christer Solskogen
On 7/8/09 12:24 PM, Dag-Erling Smørgrav wrote: Christer Solskogensolsko...@carebears.mine.nu writes: I'm getting this notice whenever I (re)start varnish on FreeBSD 7.2 (amd64). Varnish runs and works as I would expect, so is it harmless? Yes, it's harmless (though it may have an impact on

Re: Notice: locking SHMFILE in core failed: Resource temporarily, unavailable

2009-07-08 Thread Dag-Erling Smørgrav
Christer Solskogen solsko...@carebears.mine.nu writes: Thanks. Setting vm.max_wired to 70 is no problem on a machine with 8GB of memory I guess. (But I also have to admit I dont really know what vm.max_wired really means) It sets the maximum amount of memory that may be wired (i.e.