Summary: | IPFire Backup includes makeqosscripts.pl and possibly other files which should not be backed up | ||
---|---|---|---|
Product: | IPFire | Reporter: | Tim Zakharov <tim> |
Component: | --- | Assignee: | Adolf Belka <adolf.belka> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Major Usability | ||
Priority: | Will affect an average number of users | CC: | adolf.belka, himemsys36 |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified |
Description
Tim Zakharov
2024-08-04 10:34:24 UTC
Discussed in August Developers conf call and I am picking up this bug to put a fix together, test it and submit a patch for it. Patch fix has been submitted into the dev mailing list and patchwork. https://lists.ipfire.org/hyperkitty/list/development@lists.ipfire.org/thread/BFX5VJYPVPZOQ54ODELWBO6XHJ4RM4J3/ https://patchwork.ipfire.org/project/ipfire/list/?series=4755 The patch has been merged into next. https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=ad4cc933457b0ad659e0c49ab56451d4b4b7c083 Have checked out the backup of qos with CU193 Testing. None of the programmatic .pl files are backed up anymore. So with qos disabled the /var/ipfire/qos/bin directory has nothing saved in the backup anymore. When qos is enabled and running then there is now a qos.sh file in that /bin/ directory and that is still backed up as that defines the settings that have been configured for the qos setup. So the fix has been confirmed as working. This would be good if it could also be confirmed by the original bug poster, @Tim. (In reply to Adolf Belka from comment #5) > Have checked out the backup of qos with CU193 Testing. None of the > programmatic .pl files are backed up anymore. > > So with qos disabled the /var/ipfire/qos/bin directory has nothing saved in > the backup anymore. > > When qos is enabled and running then there is now a qos.sh file in that > /bin/ directory and that is still backed up as that defines the settings > that have been configured for the qos setup. > > So the fix has been confirmed as working. > > This would be good if it could also be confirmed by the original bug poster, > @Tim. I hope over the coming weekend to upgrade to CU193 Testing so I can confirm. Thank you, Adolf. |