johann

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....

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 i was looking into something and using webmin when i decided to use webmin's logrotate page to separate nginx's access and error logs in order to keep differing history depths. webmin did so and reported no errors. on the next scheduled rotation i received notification of a failure for /var/log/nginx/access.log rotating to /var/log/nginx/rotated/. i went to a terminal page for that server...

perl [-[wW]] -[eE] "use Socket6" --> no output perl -c [-[wW]] -[eE] "use Socket6"...

IPv6 listen problems

create 1.791 milestone bug category

directory-chooser error

what re the disparity between the sysinfo page and the pkg update page? i have seen...

yum.noarch 3.2.29-43.el6_5 Linux s5.4ssl.us 2.6.32-042stab084.12 #1 SMP Tue Nov 26...