> > > If, however, you want to intelligently backup just the local > > > configuration of ssh, you need to know that there are more files than > just > > > the ones in sshd.conf to backup. > > > > Nahhh..... just fix sshd.conf.... > > But then the host keys show up as editable files in the package > configuration menu, which is (IMHO) a "Bad Thing". Also, the ssh host keys > happen to be ascii text files...other packages may have automatically > generated local configuration files that are not plain text. > > I don't think there's any getting around there are at least two types of > "configuration" data...files the user edits to configure the package, and > files the package generates automatically. There could even be other > flavors. Things that come immediately to mind include: dhcpd & dhclient > lease files, and indexed data-base files (like for e-mail user lists, alias > files, and similar).
One final comment about using the <package>.conf file to specify ALL dynamic configuration files for a package... Several package (sshd and dnscache immediately come to mind) have an entire configuration directory that should be backed up. For sshd this is the /etc/sshd directory. For dnscache, it's more configurable, but is typically something like /etc/dnscache. In some cases, the particular contents of the directory may be reasonably well known (as for sshd). In other cases, the directory contents may be completely under the user's control (such as dnscache, which uses the existence of a file to allow particular IP ranges to make queries), or something like a small web-server (weblet, boa, thttpd, or similar), which might have who-knows-what user generated content inside the directory. I think it's reasonably safe to say that these files are: - User configurable - Ought to be backed up, when backing up local configuration information (or at least the option to backkup these files should be available) - Cannot be included by anything more specific than a directory specification when building the package (ie: it's impossible ahead of time to know the exact contents of the directory, and list each file individually in the <pkg>.conf file). How does your proposed usage of the <pkg>.conf file deal with this? Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
