I've encountered a few problems I thought I should report.
One is that the L option on the lrcfg backup menu seems to include the
ramlog package. Changing
l|L) PKGn="/^log=/!" ;;
to
l|L) PKGn="/^ramlog=/!" ;;
in lrcfg.back.script seems to take care of this.
Consider the following sequence:
1. Install sudo.lrp
2. backup
3. reboot
4. backup
5. reboot
6. backup
7. reboot
At the end of step 7, the only sign of the existence of the sudo package is
an entry in /var/lib/lrpkg/backdisk and another in /var/lib/lrpkg/packages.
Here's what happens...
In step 2, sudo's /var/log/sudo.log file is excluded from the backup even
though it's listed explicitly in the sudo.list file. I don't know whether
this is a deliberate design decision or not, but changing "/var/log/*" in
/var/lib/lrpkg/ramlog.exclude.list to "/var/log" seems to allow explicitly
named files in /var/log to be backed up; however, I don't know whether that
change breaks something else. Anyone know if the change is a problem for
anything?
In step 4, there is no /var/log/sudo.log file, so ctar aborts when backing
up the package. There's a brief message ("Can't stat: No such file or
diretory") written, but then the backup prceeds as if nothing was wrong, so
if you don't notice the message and confirm the disk space or have that
option disabled, the script will backup a partial package file. I came up
with a way to avoid the problem by dumping ctar's stderr to a file and then
checking whether the file is empty. I could post the diff if there's any
interest.
In step 6, there is no sudo.list file since ctar aborted before getting to
it in step 4, so the backup creates an empty package file. Since there
seems to have been some deliberate effort made to hide errors that might
occur with an empty include file, I'm not sure whether it's considered
legitimate to have a package that has no list file. Otherwise, it should be
an easy matter to check that the list file exists before proceeding with the
backup. Any reason not to?
Rodney
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
