CLIENT: win7/64
SERVER: Linux 2.6.32-696.18.7.el6.x86_64
APP's:
webmin.noarch 1.881-1
Logrotate version 3.7.8
due to webmin's malformation of logrotate '.conf' files, the logrotate landing page can contain erroneous data and this spills over into the detail configuration page of affected rotations. of course, the problems noted herein would also arise in such files that are miscreated manually or by other app's.
to wit: see how webmin malformed a '.conf' file in the topic immediately before this. there you will see that spurious content was added to the end of the file and it was comprised of:
that group of three (3) lines is a duplicate of the lines just previous. those previous lines end with '}LF' which is the end of what should be the correct block (record) for the file.
this bug seems to arise from the proc used to read the files into memory and what means is used to separate each record and may have something contributed from the record sorting mechanism employed.
the extra lines from the first file, supra, do not become associated with the first record as webmin sees it. observing the webmin detail page for that record shows nothing untoward.
instead, those extra lines in the first file get pre-pended by webmin to the alphabetically (per webmin) second record which places those lines — on both the landing page and detail page — as if they were a file to be rotated in the second record. since the lines exist in the first on-disk file, one cannot delete them from the file section of the second record using webmin. in fact, webmin cannot be used to correct the malformation of the first record since webmin stops reading, apparently, the first record upon reaching the first closing '}'. this problem seems to be due to webmin's faulty record separation method that permits data from the first on-disk file to slop over and become data in the second file.
one has to understand that logrotate allows its own config file '/etc/logrotate.conf' as well as any '.conf' file in the '/etc/logrotate.d' directory to contain multiple rotation blocks. webmin's problem is not recognizing what is a complete rotation record and allowing spurious data from one file to be merged into the data of another file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CLIENT: win7/64
SERVER: Linux 2.6.32-696.18.7.el6.x86_64
APP's:
webmin.noarch 1.881-1
Logrotate version 3.7.8
due to webmin's malformation of logrotate '.conf' files, the logrotate landing page can contain erroneous data and this spills over into the detail configuration page of affected rotations. of course, the problems noted herein would also arise in such files that are miscreated manually or by other app's.
to wit: see how webmin malformed a '.conf' file in the topic immediately before this. there you will see that spurious content was added to the end of the file and it was comprised of:
that group of three (3) lines is a duplicate of the lines just previous. those previous lines end with '}LF' which is the end of what should be the correct block (record) for the file.
this bug seems to arise from the proc used to read the files into memory and what means is used to separate each record and may have something contributed from the record sorting mechanism employed.
the extra lines from the first file, supra, do not become associated with the first record as webmin sees it. observing the webmin detail page for that record shows nothing untoward.
instead, those extra lines in the first file get pre-pended by webmin to the alphabetically (per webmin) second record which places those lines — on both the landing page and detail page — as if they were a file to be rotated in the second record. since the lines exist in the first on-disk file, one cannot delete them from the file section of the second record using webmin. in fact, webmin cannot be used to correct the malformation of the first record since webmin stops reading, apparently, the first record upon reaching the first closing '}'. this problem seems to be due to webmin's faulty record separation method that permits data from the first on-disk file to slop over and become data in the second file.
one has to understand that logrotate allows its own config file '/etc/logrotate.conf' as well as any '.conf' file in the '/etc/logrotate.d' directory to contain multiple rotation blocks. webmin's problem is not recognizing what is a complete rotation record and allowing spurious data from one file to be merged into the data of another file.