[Touch-packages] [Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports

2016-04-06 Thread Amos Jeffries
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu.

[Touch-packages] [Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports

2016-03-06 Thread Alain Reguera Delgado
Well, I reported the issue because the sarg monthly report was never made in a pristine installation. In the research I found that the access.log file was truncated in a period of time (daily) which is not appropriate for a monthly report, nor even weekly reports. Even though sarg scripts are

[Touch-packages] [Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports

2016-03-06 Thread Todd Bradshaw
** Also affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1414754 Title: /etc/logrotate.d/squid3 fails

[Touch-packages] [Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports

2016-03-06 Thread Todd Bradshaw
Sarg installs its own cron.daily,weekly,monthly scripts. If this line executes then... well it probably wont be what is wanted. The way it is now, you know it is there and it doesn't cause problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports

2016-02-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: logrotate (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu.