Edgar Fuß writes:
>> If you are mounting /usr from NFS, then it belongs in
>> critical_filesystems_remote.
> It's there by default and starting mdnsd fails because it's started earlier.
I think there are daemons that depend on critical_filesystems_remote and
perhaps this should be adjusted. Tha
> If you are mounting /usr from NFS, then it belongs in
> critical_filesystems_remote.
It's there by default and starting mdnsd fails because it's started earlier.
Martin Husemann writes:
> On Wed, May 21, 2025 at 05:30:11PM +0200, Edgar Fuß wrote:
>> > If you have /usr on a separate partition, you need to add it to
>> >
>> >critical_filesystems_local
>> >
>> > (see rc.conf(5)).
>> Where exactly does it say that?
>
> Not explecitily, I was more referi
On Wed, May 21, 2025 at 05:30:11PM +0200, Edgar Fuß wrote:
> > If you have /usr on a separate partition, you need to add it to
> >
> > critical_filesystems_local
> >
> > (see rc.conf(5)).
> Where exactly does it say that?
Not explecitily, I was more refering to the description of the variabl
> If you have /usr on a separate partition, you need to add it to
>
> critical_filesystems_local
>
> (see rc.conf(5)).
Where exactly does it say that?
What if I had /usr on NFS?
On Wed, May 21, 2025 at 05:02:50PM +0200, Edgar Fuß wrote:
> mdnsd is on /usr. But /etc/rc.d/mdnsd is not REQUIRE: mountcritremote.
> In fact, it can't be, because it's BEFORE: NETWORKING, while mountcritremote,
> or course, is REQUIRE: NETWORKING.
>
> How is this supposed to work (it silently d
mdnsd is on /usr. But /etc/rc.d/mdnsd is not REQUIRE: mountcritremote.
In fact, it can't be, because it's BEFORE: NETWORKING, while mountcritremote,
or course, is REQUIRE: NETWORKING.
How is this supposed to work (it silently doesn't, for us)?
