Date: Thu, 27 Sep 2007 13:44:57 -0600 From: John E Hein <jhein@timing.com> To: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net> Cc: emulation@freebsd.org Subject: Re: Signal 12 on simple ldd / Linux Message-ID: <18172.2105.13764.795975@gromit.timing.com> In-Reply-To: <18172.1014.867507.713218@gromit.timing.com> References: <20070927173022.GA39854@freebsd.org> <200709271817.l8RIHWK9020208@himinbjorg.tucs-beachin-obx-house.com> <18172.1014.867507.713218@gromit.timing.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John E Hein wrote at 13:26 -0600 on Sep 27, 2007: > Tuc at T-B-O-H.NET wrote at 14:17 -0400 on Sep 27, 2007: > > I'm finding out that this also ISN'T happening on systems where > > the Linux install is local, and used local. I'm finding 100% so far that > > it only happens where /compat is NFS mounted. Is this something someone > > has ever done, and are there any gotchas that I am running into because > > of it, or is it just "One of those things you figure out that leads you > > down the completely wrong path". > > We mount /compat/linux over NFS. I have not found any problems like > the one you are having with it after doing so on some boxes for years > (from 4.x to 6.x). Sometimes, I experience permission problems if, > for instance, the app tries to write to /var/db or something (I don't > export it with maproot=0). So occasionally I'll add a sym link in > the nfs compat/linux tree to point to a local native directory. Is there any file locking that the app might be doing? If it tries to lock a file in /var/db or something, it might try to lock the file in /compat/linux/var/db. I don't remember if 5.3 (which is what you are running) supports proper nfs file locking (nfs locking in 4.x just always successfully gives out a lock, so if multiple lockers try to lock a file, they will all think they own the lock resulting in possible file corruption depending on how the lock is used), but you do have to make sure lockd and friends are running to get nfs locking to work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18172.2105.13764.795975>