Re: /etc/exports continue line

[David Liontooth <liontooth@cogweb.net>]

Neil Brown wrote:
> On Thursday April 12, liontooth@cogweb.net wrote:
>   
>> I've been using \ to continue a line in /etc/exports, and ran into an
>> odd problem -- if you accidentally hit the TAB key after the continue
>> line and save, the entry becomes invalid. Since the TAB key is
>> invisible, it can be difficult to figure out what's going on.
>>
>> I reported it as Debian bug 418491 to nfs-kernel-server, and the
>> maintainer responded by saying \ isn't a valid continue character.
>> Comments? I routinely do this sort of thing:
>>
>> /spare \
>>         165.97.21.130(rw,no_root_squash,no_subtree_check,async) \
>>         165.97.21.132(rw,no_subtree_check,async) \
>>         165.97.21.133(rw,no_subtree_check,async) \
>>         165.97.21.134(rw,no_subtree_check,async) \
>>         165.97.21.135(rw,no_root_squash,no_subtree_check,async) \
>>         165.97.21.136(rw,no_subtree_check,async) \
>>         165.97.85.112(rw,no_subtree_check,async) \
>>         165.97.85.117(rw,no_subtree_check,async)
>>
>> A lot easier to maintain that a single line. Is there an alternative way
>> to continue the line?
>>     
>
> Use an editor that highlights spaces at the end of the line???
>
> But yes, I hate '\' line continuation too, for exactly that reason.
> The only alternative for /etc/exports is something like:
>
> /spare   165.97.21.130(rw,no_root_squash,no_subtree_check,async)
> /spare   165.97.21.132(rw,no_subtree_check,async)
> /spare   165.97.21.133(rw,no_subtree_check,async) 
> /spare   165.97.21.134(rw,no_subtree_check,async) 
> /spare   165.97.21.135(rw,no_root_squash,no_subtree_check,async) 
> /spare   165.97.21.136(rw,no_subtree_check,async) 
> /spare   165.97.85.112(rw,no_subtree_check,async)
> /spare   165.97.85.117(rw,no_subtree_check,async)
>
> NeilBrown
>   
Thank you for the suggestion; that would work, though I often cut and
paste chunks of lines from one exported drive listing to another.

Once you know about this quirk, it's obviously less of an issue. Still,
if I imagine trying to help myself in the past from this enlightened
position in the future, it would be fun to come up with a more
user-friendly solution. Could exportfs just filter out TAB characters,
or would you consider that unwanted code clutter?

Dave



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs