/varnish,60G
Notice: locking SHMFILE in core failed: Resource temporarily unavailable
shine# /usr/local/etc/rc.d/varnishd restart
Stopping varnishd.
Starting varnishd.
storage_file: filename: /data/div/varnish size 61440 MB.
Using old SHMFILE
Notice: locking SHMFILE in core failed: Resource temporarily
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).
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
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.