Re: Value in adding Shepherd requirements to file-systems entries?

[Richard Sent]

Hi Felix,

Felix Lechner <felix.lechner@lease-up.com> writes:

> Hi Richard,
>
> On Tue, Apr 23 2024, Richard Sent wrote:
>
>> I submitted a patch for what I'm thinking at
>> https://issues.guix.gnu.org/70542.
>
> I believe this stopped working for my NFS setup.

Interesting. It does still work with my CIFS/SMB share, so I suspect
this is an NFS-specific problem. Curiously I did have to reboot after
adding the file-system entry, but it works after that.

You could try invoking mount-file-system from (gnu build file-systems)
directly to try and narrow down what exactly is breaking.

>> --8<---------------cut here---------------start------------->8---
>> (file-system
>>    (device "wallace-server.local:/acct")
>>    (mount-point "/acct")
>>    (type "nfs")
>>    (requirement '(avahi-daemon)) ;resolve .local
>>    ;; (flags '(no-atime no-dev no-exec read-only))
>>    ;; (options "proto=tcp6,timeo=300,nolock")
>>    (check? #f)
>>    (mount-may-fail? #t)
>>    (create-mount-point? #t))
>> --8<---------------cut here---------------end--------------->8---
> Wow, that works!
> 
> Since this short form is optional and I can always switch back to the
> previous version, v2 of that patch should be merged without further
> delay.
> 
> Thank you for your most valuable contribution!
> 
> Kind regards,
> Felix
> 
> P.S. The code above should read (requirements ...) in the plural.

To confirm, you are using avahi-daemon as a shepherd-requirements entry
in your current code and not networking right? We'd need the former for
.local TLD name resolution.

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.