Hi Ross,
My understanding is that they are used to help make NFS state-full. The
"state" file is part of the extension to add Network Status Monitoring
(NSM) to NFS.
In the RPM world, they need to label them as configuration files to
avoid them getting overwritten during an upgrade.
The Debian approach removes them on a "purge" in the postrm stage and
ignore them when doing an "upgrade" in the prerm stage.
So, technically they are not configuration files. Would another
approach such as removing them as packaged files and touching the files
in a postinstall script be preferred?
Regards,
Rob
On 03/10/2015 12:05 PM, Burton, Ross wrote:
On 9 March 2015 at 23:52, Rob Woolley <rob.wool...@windriver.com
<mailto:rob.wool...@windriver.com>> wrote:
+CONFFILES_${PN}-client += "${localstatedir}/lib/nfs/etab \
+ ${localstatedir}/lib/nfs/rmtab \
+ ${localstatedir}/lib/nfs/xtab \
+ ${localstatedir}/lib/nfs/statd/state \
+ ${sysconfdir}/nfsmount.conf"
NFS puts configuration files in /var/lib? Are files called "state"
really configuration files?
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
