Date: Tue, 13 Aug 2019 16:18:43 +0200 From: Polytropon <freebsd@edvax.de> To: Paul Pathiakis <pathiaki2@yahoo.com> Cc: Paul Pathiakis via freebsd-questions <freebsd-questions@freebsd.org>, hw <hw@gc-24.de> Subject: Re: Firefox or what? Message-ID: <20190813161843.c44c2032.freebsd@edvax.de> In-Reply-To: <768650735.4676355.1565695184448@mail.yahoo.com> References: <20190812173754.9bbd34f75885d616ae5d074a@gc-24.de> <768650735.4676355.1565695184448@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Aug 2019 11:19:44 +0000 (UTC), Paul Pathiakis via freebsd-questi= ons wrote: > Hi, > Sadly, I don't believe you to be technically astute in that > you seem to have issues with everything that work 'out of the > box' in FreeBSD. I think this is not the case here. The specific setup which involves NFS that is buggy for some reason might explain a lot of things, like "filesystem inconsistency lookalike". However, checking for the common things (actual filesystem inconsistency, defective RAM, buggy CPU, etc.) should always be the first thing to do. If "cross-checking" with other systems is possible, that also should happen. > Apologies to the list, but this guy's has been taking up > serious bandwidth for the last two weeks on non-existent > issues.=A0 He makes a statement about something not working > and 5-10 respond 'works for me'. That was _before_ the consideration of NFS came up. It might very well be the reason for the problems described, even though crashing and freezing is _not_ an appropriate action when there are problems accessing files, but... in "modern" software, you never know: one thread is started to open a file, another thread goes ahead and expects the file open, tries to read or write or whatever, and nothing happens... ;-) --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190813161843.c44c2032.freebsd>