Celeron J3160 capabilities with QoS

I just checked and can confirm that the backup include file has the lines

var/ipfire/qos/*
var/ipfire/qos/bin/qos.sh

The second line specifies a specific file in the bin directory but the first line effectively says everything that is in the qos directory, which includes the bin directory.

I checked on of my backup files and that also shows it is backing up everything in the bin directory. This includes all the following files.

event-func.pl
makeqosscripts.pl
migrate.pl
parse-func.pl
RRD-func.pl

I would not expect any of these to be backed up. If any of these scripts have been updated then they would also be overwritten when a restore from backup is done.

To me this seems to definitely be a bug. Could you raise a bug for this please.

https://www.ipfire.org/docs/devel/bugzilla
Your IPFire People email address and password will be accepted as your IPFire Bugzilla login credentials.

In terms of how to deal with this in the short term, the only workaround suggestion I have is to take your backup file and open it with a graphical archive tool and delete the *.pl entries in the qos/bin/ directory.

I am using xfce4 with Arch Linux and the package in xfce4 is called xarchiver.

Other Linux distros will have different desktop applications available but they all should have some form of graphical archiver package.

I just did a test with that and I was able to delete the entries in the bin directory in the .ipf file.

If you don’t have a graphical system then you can do it on the command line by untar-ing the .ipf file, removing the .pl files from the bin directory and then re-tar into the .ipf file.

Then do a fresh install to get the correct script versions and restore from your modified .ipf file so that you get your config but without anything being overwritten in the qos/bin/ directory.

We will need to think how to change the backup, because the qos.sh file is also placed in the /bin directory but I think that might be desired to be backed up.
I will raise this and discuss it at the next IPFire devs meeting.

3 Likes