fork: Resource temporarily unavailable
This just started happening to me recently on my mail server. I added some info to PR kern/48586 but I am not entirely sure that I have the same issue. I am running Postfix from the base plus Dovecot, Apache and Spamassassin daemon from pkgsrc. This happens to me at least once a day and can't be fixed AFAICT without a full reboot. More details in the PR. I don't mind rebuilding the kernel if there is a new fix but it is a production server so I don't want to run -current. TIA. -- D'Arcy J.M. Cain da...@netbsd.org http://www.NetBSD.org/ IM:da...@vex.net
Re: Bug in fs/cd9660 raises questions about inode number computing
On Tue, 06 May 2014 12:20:53 +0200 Thomas Schmitt scdbac...@gmx.net wrote: How to properly submit them ? A PR (Problem Report) in the kern category with an attached unified diff would seem adequate if you cannot commit the changes yourself. Sorry if that is already obvious to you. Unfortunately I'm not personally familiar enough with iso9660 to confirm that the fixes are right, or to answer the other questions, though; hopefully others will. -- Matt
Re: Vnode API change: add global vnode cache
On Wed, 30 Apr 2014 17:15:16 +0200 J. Hannken-Illjes hann...@eis.cs.tu-bs.de wrote: vcache_get(mp, key, key_len, vpp) to lookup and possibly load a vnode. vcache_lookup(mp, key, key_len, vpp) to lookup a vnode. vcache_remove(mp, key, key_len) to remove a vnode from the cache. VFS_LOAD_NODE(mp, vp, key, key_len, new_key) to initialise a vnode. Updated diff at http://www.netbsd.org/~hannken/vnode-pass6-4.diff One small question: Is it expected in vcache_common() for the interlock to remain held even if returning an error? Thanks, -- Matt
Re: Vnode API change: add global vnode cache
Date: Fri, 9 May 2014 19:01:04 -0400 From: Matthew Mondor mm_li...@pulsar-zone.net Is it expected in vcache_common() for the interlock to remain held even if returning an error? vget unconditionally drops the interlock, so it will never remain held, error or not.
Re: Vnode API change: add global vnode cache
On Sat, 10 May 2014 01:29:47 + Taylor R Campbell campbell+netbsd-tech-k...@mumble.net wrote: Is it expected in vcache_common() for the interlock to remain held even if returning an error? vget unconditionally drops the interlock, so it will never remain held, error or not. Oh, thanks. I can now see that vget() must be called with it held, and indeed drops it itself. -- Matt