Re: nfs-utils.spec patch

[Henrique Martins <linux@martins.cc>]

>> but maybe there should be some debate whether to ignore
>> exportfs errors when starting nfs as the default, which
>> just requires adding a couple of '-' to the systemd
>> service file.

> What would be the reasoning? If there is nothing exported
> why come up cleanly?

The "reasoning" is why I filed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1115179
and explained "it" in comment #2
  https://bugzilla.redhat.com/show_bug.cgi?id=1115179#c2

I have a few machines in a laptop's /etc/exports, some only
resolve when I'm connected to the net at work, some only
resolve when I'm connected to the net at home.  With the
default service file nfs always fails to start...

>> A more complicated approach (would require code changes as
>> opposed to configuration changes) would be to not error out
>> if there is at least one exported mount point.

> More complexity than needed... IMHO...

... and thus the need for the complexity to make it clean,
i.e. as long as there is a machine on the particular net I'm
connected to, that can nfs mount the laptop, nfs server
should start and not require me to do some manual editing of
/etc/exports, or write a script to take care of that.

-- Henrique