http://bugzilla.suse.com/show_bug.cgi?id=960640 Bug ID: 960640 Summary: nfsserver fails to start when /etc/exports contains invalid data Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: pcerny@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The NFS daemon service fails to start when `/etc/exports` contains invalid data. Ivvalid in this contest can mean any of: 1) unknown option 2) unresolved hostname 3) non-existent export path While failing in case 1) could arguably make some sense, failing in cases 2) and 3) is rather counter productive - unresolved hostname doesn't necessarily mean the configuration is bogus - it may well be a hostname from another network. Similarly, 3) can mean it is an export that may appear only under certain conditions. Moreover, `exportfs` handles these conditions gracefully and exports only entries that are valid at the time it is called. Could the behaviour be reverted to the service starting even with some errors in the exports definition? As far as I can tell this has been the way for ages. -- You are receiving this mail because: You are on the CC list for the bug.