Hi KP Am 19.12.2014 um 18:37 schrieb kp kirchdoerfer: > Hi Erich; > > Am Donnerstag, 18. Dezember 2014, 09:30:53 schrieb Erich Titl: >> Hi Folks >> >> We have in /var/lib/lrpkg *.local files which list files to preserve in >> configdb for each package. I believe we should be able to add/remove >> files and directories there, so the backup behaviour is controlable. >> >> Now it apears that modifications in the .local files are not backed up >> as would be expected. >> >> I know I could add all the missing files in local.local, but somehow I >> feel that would not be correct. We should add the backup up the relevant >> .local file to either apkg or include a reference to the .local file in >> the file itself. > > You are right, it doesn't work that way. > > If you ran into problem, when saving files, it's either a bug or a feature > request of/for a given package and the right place to fix/enhance this, is > the > package definition in buildtool.cfg - that way all users will have a benefit > right from the start.
If this is required or desirabe by everyone, I agree. > The local.local file is for the remaining stuff we don't have a package > belonigng to it or very individual files. > > Probably we can discuss about a proper solution, if you provide an example? <EXAMPLE> I don't like the way LEAF is rotating log files, but it is an established way and I don't want to mess too much with it. Why don't I like it... - some files are rotatet in multicron-p and others in individual files in log.daily, this is inconsistant. So some years ago I created a logrotate tool which is a bit more flexible and modified multicron-p to simply call this instead of handling the rotation directly. I also modified savelog to be able to compress xxxx.0 Still the individual files which handle log rotation outside of multicron do not care about my mechanism, so I wanted to just disable and save them to configdb.lrp. As I said, I could do this in local.local, but I feel this is not right. I _believe_ modifications to an existing package should be done to the package proper saving mechanism, e.g. package.local. This would require the package.local file to be backed up too. Also there is no provision to remove a file if it is not desired, but this is another story. I would like to make this area more consistant. I do this for myself by using my own rotation mechanism. As a generic solution I would remove logrotation completely from multicron-p and place it either in individual files or settle on some version of a logrotate utility. </EXAMPLE> This is one specific case only and does not solve the backup question. cheers Erich
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
