On 1/8/20 13:09 , Edward Tomasz Napierała wrote:
> I'm afraid linking isn't supported. I've always considered it
> an optimization that made sense back when NFS could have significant
> overhead and nowadays just wasn't worth it.
>
> One thing you could try is to use nullfs(5) instead of NFS for
I am (reluctantly) replacing am-utils (amd) with autofs. To do this I
need to replace a lot of functionality that I've had embedded for a very
long time and which my users absolutely rely on. I have two (so far)
questions that I need to solve before I can proceed with this process.
Question 1 - On
On 1/3/20 09:54 , Brooks Davis wrote:
> Adding nss_ldap to the mix makes all programs threaded so a bunch of
> code paths are different. Unfortunately, amd is complicated, out of
> date, and unmaintained so I'm not sure who will be able to help. If
> possible, I would suggest putting effort into
(Different host than the LDAP problem I emailed about earlier today).
I have a newly installed host running 11.3-RELEASE-p5 (patched to
latest). I have installed and configured it the same way an existing
11.3-RELEASE-p5 host on the same subnet is set up.
amd launches and runs just fine on the ho
On 12/27/19 09:35 , Matt Garber wrote:
> On Fri, Dec 27, 2019 at 12:10 PM Lee Damon <mailto:no...@castle.org>> wrote:
>
>
> Both times I observed this:
>
> : ldapsearch -v -LLL -x -h [redacted].ee.washington.edu
> <http://ee.washington.edu> -b
I have four hosts all running 11.3-RELEASE-p5 on the same subnet.
Yesterday I did the usual "freebsd-update fetch && freebsd-update
install" on all four. They came back up fine but about 4 hours later one
of them started reporting problems with ldap search. I poked at it a bit
but it was strugglin
On 3/1/19 15:38 , Miroslav Lachman wrote:
Did you tried to boot "safe mode"? (selectable in boot menu).
I completely forgot about safe mode.
Yep. It boots. I'm going to finish the freebsd-update process then
reboot into safe mode again. I'm out of time to work on this today and
am only in th
On 3/1/19 14:19 , Miroslav Lachman wrote:
If you can boot with the old 10.4 kernel and go online, just fetch
kernel.txz from the net:
http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/11.2-RELEASE/kernel.txz and
unpack it to /boot/kernel112 then you can try to reboot a manually
select to boot
After discussion with Bob Bishop (thanks for the help!) I've tried to do
the following to upgrade one of the old boxes I mentioned previously.
cd /usr/src
tar ... .
rm -rf .??* *
svn checkout httpg://svn.freebsd.org/base/releng/10.3 /usr/src
compile, installkernel, installworld...
Now that the
I have three old FBSD 10 boxes that I need to upgrade. Ordinarily I do
this by building a new box with the latest OS then migrating services
and data. Unfortunately I don't have that option this time, the upgrade
has to happen in-place. My plan is to go from 10 to 11 then from 11 to 12.
I was
In what was arguably a silly attempt I changed all IRQ interrupts to go
to CPU0 and .. the host has stayed up through multiple attempts to crash
it. I'm not calling it fixed yet but there appears to be hope.
Right now I have a script -- /usr/local/etc/rc.d/cpuset.sh -- that's
doing the work. This
'm only in that location on
Monday and Tuesday so can't try anything until next week.
> Ronald.
>
>
> On Tue, 07 Feb 2017 22:44:01 +0100, Lee Damon wrote:
>
>> FreeBSD [redacted] 10.3-STABLE FreeBSD 10.3-STABLE #2 r313008: Tue Jan
>> 31 01:50:49 PST 2
FreeBSD [redacted] 10.3-STABLE FreeBSD 10.3-STABLE #2 r313008: Tue Jan
31 01:50:49 PST 2017 lvd@[redacted]:/usr/obj/usr/src/sys/GENERIC amd64
I'm trying to get FBSD 10.3 working on a Sun x4500 (don't ask) for use
as a ZFS-based backup server. However, whenever any amount of data is
put into a
host in question is:
FreeBSD goose.ee.washington.edu 6.3-STABLE FreeBSD 6.3-STABLE #6: Wed
Mar 26 17:03:35 PDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NIKOLA i386
This box was recently updated to a release that was exactly the same
source base as two other boxes I've been using for a mo
14 matches
Mail list logo
