On Fri, Sep 24, 2004 at 09:38:57AM -0700, Geoff Nordli wrote: > > > >> Just to add some more information. I created an additional file in > >> the same folder that somehow was successfully backed up, but I have > >> no clue where it is kept. I tried doing a tarball listing of the > >> etc, root, dnscache, tinydns packages and it didn't show up. So > >> somehow it gets restored when the machine reboots. > >> > >> Is it possible that another package will overwrite the entire > >> contents of a directory during startup? > >> > >> So are you saying that the etc package backup process parses all the > >> *.list files in the /var/lib/lrpkg folder to see what files in the > >> etc directory that it is supposed to backup. > > > > Geoff, > > The etc package is supposed to catch all the files that don't > > belong to > > another package in /etc IIRC. The failure of the etc package to backup > > this file indicates that it belongs to the dnscache package (which is > > correct). The way the backup system works is that package and backup > > information is stored in flat text files in the > > /var/lib/lrpkg folder. The > > <packagename>.list file stores populated filenames for the > > <packagename>. The <packagename>.include file stores the filenames to > > be included in the backup process. The <packagename>.exclude stores > > the filenames that should NOT be included in the backup process. > > > > To be clear about how this should be on your system, 'cd' to the > > /var/lib/lrpkg directory. The config filename should be listed in > > dnscache.include file AND NOT included in the dnscache.exclude file. > > UNLESS this configuration is actually intended to be stored somewhere > > else that I don't remember and is likely included in the > > dns<cache> supplement > > to the Bering Users Manual. > > In the /var/lib/lrpkg directory I ran: > > #grep root\/servers *.list > dnscache.exclude.list:etc/dnscache/root/servers/* > > So this tells me that the root/servers directory is only listed in the > dnscache.execlude.list file. So backing up etc.lrp should include the > /dnscache/root/servers/* directory. I performed a backup using lrcfg. > > In the location where the etc.lrp package is stored I ran: > > tar tzvf etc.lrp | grep servers > > But there was no output (there is a file listing if I don't grep it). If > that tarball stored the servers directory then it should show up. > > I guess the question is when does etc build its package list. At the > beginning when it first starts up or when it does the backup?
According to your report of etc/dnscache/root/servers/* appearing in dnscache.exclude.list, these files will not be backed up by either the etc or the dnscache package. That is because the files that get backed up by a package, are the ones matching any pattern <package>.list, but are not matched by any pattern in any of the other list files. This has the effect that no file will be backed up by two packages. The process of creating the list of files to backup processes all *.list files in /var/lib/lrpkg, so also the <package>.exclude.list files. So putting a filename in a <package>.exclude.list is a way of excluding that file from being backed up by that package _and_ any other package! In this case of dnscache, I think I recall that this is done, because these files are generated on startup and therefor don't need to be backed up. I Hope this makes things clearer. Jaap Eldering ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
